210 likes | 301 Views
SDP Maintenance RSTWG 1 st Semiannual Meeting. June 1, 2009 Prepared by Consensus Systems Technologies (ConSysTec). Agenda. Overview of SDP Project SDP Library Production Cycle Registration Site Update/Maintenance Requirements and Procedures
E N D
SDP Maintenance RSTWG1st Semiannual Meeting June 1, 2009 Prepared by Consensus Systems Technologies (ConSysTec)
Agenda • Overview of SDP Project • SDP Library • Production Cycle • Registration Site • Update/Maintenance Requirements and Procedures • Experience with SDP Schema and other documentation • Review Recommendations for revision • Action Items • Next Webinar to go over changes
Project Plan Topics • Two Year Project • Project Plan Topics • SDP Operations & Maintenance (O&M) Start Up • SDP Maintenance Tasks • Operations Tasks • Technical Assistance Tasks • Project Management
Plan Details • Task 1: O&M Start Up; • Task 2: Maintain SDP XML Schema with RSTWG • Task 3: Update Custom Scripts • Task 4: Incorporate New Applications • Task 5: Maintain Web Site Operations • Task 6: Process Data (including support collection, conversion and processing of SDP Documents) • Task 7: Technical Assistance to New Users • Task 8: Technical Assistance to WDMS Users • Task 9: Continuation of Technical Assistance from previous contract • Task 10: Program Management and Year 2 Project Development
Target Agencies for 2009 Validated Near Ready CDTA LI Bus MNR MTA Bus NFTA NYCT Bus & Rail RGRTA LIRR Westchester / Bee-Line Work in Progress • CENTRO • CoachUSA • WDMS Users
SDP Library Available at: www.consystec.com/tsdea/rstwg/docs.html Password Protected for SDP RSTWG members
Library Categories • SDP and SCP XML Schemas • SDP Concept of Operations / Functional Requirements • SDP Guidance • Quick Start • Part 1: Executive Summary • Part 2: SDP Requirements Guidance Document • Part 3: SDP Programmers Manual • Statewide Deployment Plan
Part 2: SDP Guidance • Chapter 1: SDP Requirements Guidance Overview • Chapter 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 Header • 10.2 Transfers: Transfer Cluster and Connection Segment; and Event Connection • 10.3 Service and Block • 10.4 Route Grouping • Chapter 11: Conformance Requirements related to SDP XML Document • Appendices • Appendix A: Special Considerations for Rail Transit • Appendix B: Glossary and Acronyms • Appendix C: Resources • Appendix D: Notation for the Conceptual Data Reference Model
Part 3: SDP Programmer’s Manual • Overview (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 Database • with Conceptual Data Reference Model (in cdm format for Sybase PowerDesigner) • Tutorial on the SDP XML Schema • Application Design Reference Manuals • SDP and Metadata with SDP XML Metadata Schema
Data Mapper Scripts / Applications • Data 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) • Applications • Timetable Publisher (TriMet) • Dynamic Timetable Generator
Automated Registration of SDP Documents FUTURE: Prototype Version
High Level SDP Maintenance Requirements Description 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 Requirements Determine 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 Submission Evaluation Revision Final Approval Rollout Plan
SDP RSTWG Roles & Responsibilities • SDP 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 Changes • Needed by new or revised downstream applications • Errata or correction to previous version • SDP requirement changed or needed to be constrained, refined, or updated
Criteria for Determining Update • Will 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 Issues • Multiple day types in Trip element • Schedule Calendar XML Schema • Pattern and short turn trips • Exact match of Pattern.eventList and Trip.tripTimeList