9/12/2006 TPTF MIS portal Update Pat Harris A portal is a web site or service that offers a broad array of resources and services such as , forums, search engines, and on-line reference material.
Lead from the Front 9/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 Front 9/12/2006 Phase 1: Current Status – we have a vendor! Check out Enterpulse at 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 Front 9/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 Front 9/12/2006 Phase 1 – Milestones and timeline We are HERE Phase 1 Timeline Worm
Lead from the Front 9/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 Front 9/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 Front 9/12/2006 Phase 1: VVHLD
Lead from the Front 9/12/2006 Phase 2 –Expectations Phase 2 timeline worm
Lead from the Front 9/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 Front 9/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 Front 9/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 Front 9/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 Front 9/12/2006 Next Steps: What we need from TPTF Active participation from the MIS Task Force Reviews and timely approvals at specified points: –Requirements reviewSept 29 –Site Map & Wire framesOct 15 –User Roles / Authentication modelNov 1 –Use CasesNov 15 –Conceptual DesignDec 1
Lead from the Front 9/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!