june 1, 2009 prepared by consensus systems technologies (consystec) sdp maintenance rstwg 1 st...
TRANSCRIPT
June 1, 2009
Prepared byConsensus Systems Technologies
(ConSysTec)
SDP Maintenance RSTWG1st Semiannual Meeting
AgendaOverview of SDP ProjectSDP LibraryProduction CycleRegistration SiteUpdate/Maintenance Requirements and
ProceduresExperience with SDP Schema and other
documentationReview Recommendations for revisionAction ItemsNext Webinar to go over changes
Project Plan TopicsTwo Year ProjectProject Plan Topics
SDP Operations & Maintenance (O&M) Start Up
SDP Maintenance TasksOperations TasksTechnical Assistance TasksProject Management
Plan DetailsTask 1: O&M Start Up;Task 2: Maintain SDP XML Schema with RSTWGTask 3: Update Custom ScriptsTask 4: Incorporate New ApplicationsTask 5: Maintain Web Site OperationsTask 6: Process Data (including support
collection, conversion and processing of SDP Documents)
Task 7: Technical Assistance to New UsersTask 8: Technical Assistance to WDMS UsersTask 9: Continuation of Technical Assistance from
previous contractTask 10: Program Management and Year 2
Project Development
Target Agencies for 2009
Validated Near Ready
CDTALI BusMNRMTA BusNFTANYCT Bus & RailRGRTA
LIRRWestchester / Bee-Line
Work in Progress
CENTROCoachUSAWDMS Users
SDP Library
Available at: www.consystec.com/tsdea/rstwg/docs.html
Password Protected for SDP RSTWG members
Library CategoriesSDP and SCP XML SchemasSDP Concept of Operations / Functional
RequirementsSDP Guidance
Quick StartPart 1: Executive SummaryPart 2: SDP Requirements Guidance
Document Part 3: SDP Programmers Manual
Statewide Deployment Plan
Part 2: SDP GuidanceChapter 1: SDP Requirements Guidance
OverviewChapter 2: SDP XML Schema Model Overview Chapter 3: SDP Conceptual Reference Model
Overview Chapter 4: Agency Registration Branch Chapter 5: Service Branch Chapter 6: Transit Network Branch Chapter 7: Transit Gazetteer Branch Chapter 8: Transit Facility Branch Chapter 9: Schedule Calendar Date, Day Type
and Versioning Issues
Part 2: SDP Guidance (cont) Chapter 10: Advanced Topics
10.1 Route and Timetable Header10.2 Transfers: Transfer Cluster and Connection
Segment; and Event Connection10.3 Service and Block10.4 Route Grouping
Chapter 11: Conformance Requirements related to SDP XML Document
Appendices Appendix A: Special Considerations for Rail
TransitAppendix B: Glossary and AcronymsAppendix C: Resources Appendix D: Notation for the Conceptual Data
Reference Model
Part 3: SDP Programmer’s ManualOverview (to Programmer’s Guide) A Guide to Translating Native Data to SDP
Appendix A: SDP Guidance XML Template (includes code lists and element definitions)
Guidance on Building a Physical Database from the SDP with MS Access Databasewith Conceptual Data Reference Model (in cdm
format for Sybase PowerDesigner) Tutorial on the SDP XML Schema Application Design Reference ManualsSDP and Metadata with SDP XML Metadata
Schema
Data Mapper Scripts / ApplicationsData Mapper Scripts
Long Island Bus to SDP (LIBus2Sdp)Bee-line to SDP (Beeline2Sdp)MTABus
Based on data extracts from the WDMS (WDMS2Sdp)NYCT Bus to SDP (STIF2Sdp)NYCT Rail to SDP (RTIF2Sdp)Rochester, Capital District, and Niagara Regions (Gtfs2Sdp) SDP XML to SDP (Xml2Csv) Data Validation of SDP csv format (CheckSDPcsv) SDP Document to GTFS files (Sdp2gtfs)
ApplicationsTimetable Publisher (TriMet)Dynamic Timetable Generator
SDP Production Cycle
Downstream User: TRIPS123
Automated Registration of SDP Documents
FUTURE:Prototype Version
High Level SDP Maintenance RequirementsDescription of General Requirements Develop and maintain an inventory of programs, procedures
and documentation needed for the successful use of the SDP by Transit Operators and technical staff
Identify standard, reoccurring maintenance activities and special or lower frequency maintenance events.
Determine the timing of a standard maintenance cycle Determine the roles and responsibilities for standard
maintenance activities. Determine the regional process for changing the requirements
of the SDP and implementing them. The proposed steps in the process that need to be defined include the following: Submission, Evaluation, Revision, Final Approval and Rollout.
Identify the committee that supports the change process, including the membership, roles and responsibilities.
High Level SDP Maintenance RequirementsDetermine the timing of a standard maintenance cycle Identify a preliminary list of events and conditions that might
trigger a need to update the SDP requirements. Develop criteria for determining which updates, changes and
ongoing maintenance activities can be fast tracked and completed by the project’s maintenance team, without proceeding through the full regional assessment and approval process.
Identify a mechanism for encouraging the submission of “lessons learned” and incorporating key points as appropriate into the SDP Users Manual and the SDP Maintenance Plan.
Develop a process for further delineating roles and responsibilities as the usage of the SDP expands, and as budgets, agencies and requirements change.
Maintain a Change Log, so the history and sequence of changes is understood and can support recovery of the system, if needed.
Ensure that the budget process supports the needed staffing, tools and training
Update Procedures
1. Submission2. Evaluation3. Revision4. Final
Approval5. Rollout Plan
(1) Convene Regional SDP Review Committee-- Evaluate change
requests
(2) Review Recommended Extensions / Changes to
the SDP Functional Requirements
(3) Update SDP XML Document and publish changes, algorithms,
communications/impacts
Submissions for changes:(1) SEP Process for extensions and XML changes (includes ConOps, Use Cases, extended functional requirements, impact analysis on current users/systems(2) lessons learned, updates to non-interface documents
Approve Updates in
SDP Functional Req’ts
Okay
Revise
(3a) Update Guidance Documents and Templates
(3b) Update translation applications under TSDEA maintenance & Operators
develop internal procedures
(3c) Update TSDEA tools, processing applications and
interfaces, as needed
(4) Set up regression testing framework for native data registration, translation
application testing, portal and downstream application
testing.
Do extensions support existing
systems?
No
Yes
Testing Complete?
No
(5) Rollout Complete
Yes
Changes, updates,
extensions to consider?
Yes
NoMaintenance
Cycle Complete
Submission
Evaluation
Review
Approve
Rollout Plan
SDP RSTWG Roles & ResponsibilitiesSDP RSTWG will review all proposed changes to the
SDP Functional Requirements and related Implementation Methods (e.g., SDP XML Schema).
Changes will be approved by at least a 2/3rds majority of RSTWG members. If a member is not present, then they shall be given an additional week to vote on the Group’s approach to the change request.
A change request may be postponed to the next meeting.
A request for a significant change will necessitate a proposal to NYSDOT. A significant change is one deemed “significant” by the RSTWG.
Events & Conditions that Trigger ChangesNeeded by new or revised downstream
applicationsErrata or correction to previous versionSDP requirement changed or needed to be
constrained, refined, or updated
Criteria for Determining UpdateWill not significantly impact the validity of
previous SDP Schema versions (e.g., the change is “upwardly compatible”)
Current Update Recommendationsfrom NGTSIP Wiki Page and other issues
Potential IssuesMultiple day types in Trip elementSchedule Calendar XML SchemaPattern and short turn tripsExact match of Pattern.eventList and
Trip.tripTimeList