1 / 10

MPIM vs IDM: High-Level Architecture and Functional Specifications

This document provides an overview of MPIM (Market Participant Identity Management) and IDM (Identity Management) projects, including VeriSign Digital Certificates. It includes high-level architecture diagrams, functional specifications, conceptual system design feedback, and requirement document changes.

alline
Download Presentation

MPIM vs IDM: High-Level Architecture and Functional Specifications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. INF MP Identity Management Jeff Floyd ERCOT Public

  2. Agenda • MPIM vs. IDM • High-Level Architecture Diagram • Functional Specifications • Understanding Feedback • Conceptual System Design Feedback • Requirement Document Changes • Questions TPTF Meeting

  3. MPIM vs. IDM • Market Participant Identity Management consists of the following projects: • Identity Management (IDM) • VeriSign Digital Certificates • MPIM Requirement document and Conceptual System Design Document apply to the IDM portion of the project. • IDM will interact with VeriSign project to create the digital certificate • Certificate Renewal, requirements and delivery of that will be through the VeriSign Digital Certificate project (60013_01). ERCOT Public

  4. High-Level Architecture Diagram ERCOT Public

  5. Functional Specifications ERCOT Public

  6. Functional Specifications cont. ERCOT Public

  7. Functional Specifications cont. ERCOT Public

  8. Understanding the Feedback Template • Text in Black is from the original requirement document (v.90). • Text in Blue is the comment provided or the text added to reflect feedback received. • If text has been removed, it will be shown in the feedback excel as strikethrough ERCOT Public

  9. Conceptual System Design Feedback ERCOT Public

  10. Requirement Document Changes The following changes were made to the requirement document: ERCOT Public

More Related