Electronic Commerce B2B eCommerce Issues MIS 6453 -- Spring 2006 Instructor: John Seydel, Ph.D.
8/22/2006 TPTF MIS Update Kate Horne Pat Harris. TPTF8/22/2006 Agenda Review proposed site map...
-
Upload
adela-shaw -
Category
Documents
-
view
213 -
download
0
Transcript of 8/22/2006 TPTF MIS Update Kate Horne Pat Harris. TPTF8/22/2006 Agenda Review proposed site map...
TPTF8/22/2006
Agenda
• Review proposed site map• Discuss role of MIS task force• Obtain clarification on 12.3 (d)
TPTF8/22/2006
My MIS
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.
TPTF8/22/2006
Reports and Extracts
Landing page for Reports and Extracts displays user-defined reports
Left navigation displays protocol sections – clicking a section expands the menu to display subsections
TPTF8/22/2006
Reports and Extracts
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.
TPTF8/22/2006
Reports and Extracts
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.
TPTF8/22/2006
Notices and Alerts
Notices and alerts are displayed in a similar way to Reports.
The landing page displays user-defined notices.
Notices may be marked as read and deleted from this view.
TPTF8/22/2006
Notices
The left menu allows users to navigate to a protocol section and view notices available to their role/company.
Users can select notices to display on My Notices or My MIS page.
Clicking on the notice name will display actual notices.
TPTF8/22/2006
MIS web portal TPTF Task Force
• Objectives – THANKS for your help!
• MIS portal Objectives – High Level Scope
• Organization – who’s on the team?
• Next Steps – Deliverables, Task Force participation and review points
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.
TPTF8/22/2006
MIS portal TPTF Task Force - Objectives
• Participate
– Help develop Use Cases, Testing scenarios, other deliverables
– Assist in the review process by sharing with and gathering input from the larger market participant community
• Clarify
– Be there to answer our questions around Protocol intent, portal functionality, and content presentation.
• Review / Approve
– As deliverables are produced, help us ensure quality by reviewing and certifying correctness
• Be the Voice of our Customer!
TPTF8/22/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.
A content area, where data such as Engineering Studies, monthly reports, policies and procedures, special forms, etc. can be posted and accessed.
A dashboard style application for display of Market Participant specific information. (NOTE: this is an optional add-in, a nice-to-have)
A messaging system for posting notifications and requests.
Authenticated access to applications (a launch pad) as described in the Protocols.
Search engine and query tools
TPTF8/22/2006
MIS portal team – Who? Includes the Task Force
Kathy HagerProgram Director
Pat HarrisMIS Web Portal
Project manager
Nancy BenderAdministration
Shawn CatoeTechnical Architect
Brett EconomidesProject Controller
Revis TaylorBusiness Analyst
Kate HorneUI / Content Design
Jane CatesTechnical Writer
Belaji KrishnaswamyTech Architect
MIS / TPTF
Task Force
TPTF8/22/2006
MIS portal plan – next steps
P
Protocols -- translated into Requirements, formally documented
Requirements -- break down into Use Cases, and then into Test Scenarios
Use Cases
Test Cases
Site Map
UserRoles
Wire-frames
Proto-type
Security Review
Site map becomes screen flow -- wireframes are detailed screen designs
DesignDocument
Mar ‘07Security and authentication are defined, audited