9/12/2006TPTF

MIS portal Update

Pat Harris

A portal is a web site or service that offers a broad array of resources and services such as e-mail, forums, search engines, and on-line reference material.

Lead from the Front9/12/2006

Agenda

• Phase 1 – Current Status – we have a vendor!– Plan: when? what?

• Phase 2– Expectations: what’s next– Prototypes: a preview opportunity

• Next Steps– How you can help– What we’ll be doing until next briefing

Lead from the Front9/12/2006

Phase 1: Current Status – we have a vendor!

• Check out Enterpulse at www.Enterpulse.com

• Why Enterpulse?– Response included approach, references– Proposed project team did the presentation – very professional– Emphasis on quality, testing, frequent review cycles– Focus on human factors and web site usability– References were excellent

• Areas of Expertise:– Specialty in web solutions– Service Oriented Architecture (SOA)

Lead from the Front9/12/2006

Phase 1: Statement of Work

• Covers Conceptual Design

– Goes through December to reach Conceptual Design

– Review points are Requirements, Use Cases, Wire Frames, Site Map and Test Cases

– Final deliverable will be a Conceptual Design document plus a plan, timeline and budget estimate for Phase 2

Lead from the Front9/12/2006

Phase 1 – Milestones and timeline

7/3 12/29

12/29

Conceptual Design Document

9/30

Requirements To TPTF

9/25

Vendor Onsite

11/24

Use Cases Complete

10/22

Detail Site Map

11/4

Wire Frames Complete

10/9

TML Gap Analysis

7 - 9

8/7

Project Team On Site

9/11

Reqmts to IDA7/5

Staffing, Planning

We are HERE Phase 1 Timeline Worm

Lead from the Front9/12/2006

MIS portal – Project Objectives (scope)

Configurable ‘MyPage’, for content access according to user preferences.

Authentication System that enables levels of access to data/applications by role

Single sign on capability, passing credentials through to applications as they are loaded

Categorization of data as PUBLIC, SECURE, and CERTIFIED.

Dynamic-update area, where data such as temperature, load requirements and forecasts, and system information may be captured either automatically or posted manually by ERCOT.

Search engine and query tools

A content area, where data such as Engineering Studies, monthly reports, policies and procedures, special forms, etc. can be posted and accessed.

A messaging system for posting notifications and requests.

Authenticated access to applications (a launch pad) as described in the Protocols.

Nice to haves:

A dashboard style application for display of Market Participant specific information.

Replacement of TML site.

Lead from the Front9/12/2006

Phase 1: Budget Tradeoffs – require Change Request

• A dashboard style application for display of Market Participant specific information.– PJM system would serve as a model– Includes capability to download Market Participant-specific data for local

data review, analysis, manipulation– Requires documentation of exactly what data, presentation methods,

and clear requirements– Estimated cost: $500,000

• Replacement of TML site.– Requires a review of existing content & functionality for what should

move to new MIS– Requires that we re-evaluate all pre-Nodal protocols for content

expectations– Requires Protocol revision – Estimated cost: $500,000 - $700,000

Lead from the Front9/12/2006

MARKET INFORMATION SYSTEM(MIS)

USER DIRECTORY

Policy Server

Personalization

My Page

Logging

Access Mgmt

IDENTITY VERIFICATION via Dig Certs

Log UserActivity

Authenticate User

FederationSvc Mgt

Propagate UserData

Manage Authentication

Procedures

USER DATA

ERCOT.COM

UI Presentation

Uniform Look and feel, standard presentation style

Portal Admin

Administration of Users and content

Content Integration

Provide hooks for integrating backend services

Authentication

App

AppAppBackend

Applications

Search

Phase 1: VVHLD

Lead from the Front9/12/2006

Phase 2 –Expectations

• Phase 2 timeline worm

1/2007 1/2009

2/1

Proto 1 - Screens

10/1

FAT 2

1/1/2008

ITEST 2 3/1

Adjust, train, document

7/1/2008

Transition to Home Team

8/26

Build2- EMS, MMS, CRR

5/1/2007

Build1- SCED

3/17

Proto2 - some content

5/31/2007

FAT 1

7/14

ITEST 1

10/15/2008RELEASE 2

3/1 - 10/1Cycle 1

10/1/2007 - 10/1/2008Cycle 2

1/1 - 3/1Prototyping

Lead from the Front9/12/2006

Phase 2: Sample wire frame – My Page

Only entities with access to secure or certified information may access the MIS.

The MIS, however, will contain links to all information – public, secure and certified – specified in the protocols.

Lead from the Front9/12/2006

Phase 2: Sample Reports & Extracts Landing Page

Landing page for Reports and Extracts displays user-defined reports

Left navigation displays protocol sections – clicking a section expands the menu to display subsections

Lead from the Front9/12/2006

Phase 2: Sample Reports and Extracts subsection

Clicking a subsection displays all reports and extracts available for this role/company (secure and certified)

Users can select reports to display on My Reports or My MIS page

Or, click the report name to view or download.

Lead from the Front9/12/2006

Phase 2: Sample Reports and Extracts data request

This is an example of a daily report that may be viewed as a web page, downloaded or requested via web service.

Older reports may be accessed by clicking Archives.

Lead from the Front9/12/2006

Next Steps: What we need from TPTF

• Active participation from the MIS Task Force

• Reviews and timely approvals at specified points:

– Requirements review Sept 29

– Site Map & Wire frames Oct 15

– User Roles / Authentication model Nov 1

– Use Cases Nov 15

– Conceptual Design Dec 1

Lead from the Front9/12/2006

Next Steps:

• Finalize the vendor Statement of Work – this week

• Vendor onsite – Sept. 21

• Integrate them into the team

– Sited together

– Participate in meetings w/task force

– Design! Build! Document! Review!