Integrated Service and Information Management: B-Division (ISIM-B) Tom Colacioppo, CCM, CSEP New York City Transit Project Manager New York, NY

Transcription

1 Integrated Service and Information Management: B-Division (ISIM-B) Tom Colacioppo, CCM, CSEP New York City Transit Project Manager New York, NY

2 Build it and they will come

3 And they did

4 Key Presentation Take-Aways What is ISIM-B and what will it deliver? How we incorporated our lessons learned into ISIM.

5 ISIM-B: What Will it Provide? Situational Awareness Schedule Based Train Tracking Train Arrival Times Integrated Information Key Performance Indicators Enhanced (Rules-Based) Service Delivery Information Data Mining Capabilities M1: ISIM-B Signal System Elevators/Escalators LiftNet Subway Incident Reporting System (SIRS) Unified Timekeeping System (UTS) UGOS Work-Train Manifest Voice Traction Power SCADA o o o o ElevatorStatus Escalator Status Subway Incidents Crew Information GO Information Work Train Info Login Info 3 rd Rail Power Fan Status ISIM-B User Status Requests/ M3: ISIM-B Office System M4: PA/CIS II Train Event Data Flagging Zones Car Status A-Division Train Locations Bus Locations Train Position and Train Health Train Position and Schedules Train Performance Data Rapid Scheduling System (RSS/HASTUS) Train Event Recorders RCC Flagging System (RCCF) Rolling Stock Maintenance Information System (RSMIS) External Train Arrival Time Bus Schedules & On-Time Performance Communications Based Train Control (CBTC) Data Warehouse

6 ISIM-B: Comparision of Divisions A Division B Division

7 Lessons Learned And Why We Manage Them Repeat our Successes Correct Our Mistakes GOAL: Continuously Improve our Process

8 LL1 Resisting the Temptation of Declaring Premature Success Gives a false sense of accomplishment Established a clear set of expectations Removed all ambiguous requirements

9 LL2: Memorializing the Wants and Needs of all Users and Stakeholders Followed a Systems Engineering approach Issued a Project Purpose Memorandum Developed a Concept of Operations Embedded Stakeholders into the Design and Construction Teams Purpose: Objectives: Provide consistent and timely information about the current state of B-Division service to staff and customers, moving the agency towards centralized monitoring and control Capability Current Operation ISIM-B Project Better management of safety and security by improving information sharing and decision making Better customer information by improving the quality, accuracy and timeliness of communication Time Better service management by improving service monitoring and regulation Better operational plans and schedules by improving analysis of historical service data Long-term Goal Centralized service monitoring, control and customer information at the RCC N3 Provide operational staff with a terminal to terminal, shared graphical view of the current and projected train timetable, and the ability to easily and quickly implement necessary unplanned changes. N4 Provide operational staff with real-time graphical Divisional performance information by line. N5 Provide operational staff with real-time graphical train performance data (inc. schedule adherence). N6 Provide customers with consistent and timely train arrival predictions for stations. N7 Provide consistent and timely service performance information to customers. N8 Provide customers and operational staff with consistent and timely information and predictions about disruption to the train service. N9 Publish consistent and timely service information, predictions and data via the internet. V Oct-2012 N1 Provide operational staff with a shared N10 Provide operational staff view/awareness of the state of the railroad with a consistent view of inc. assets, staff, incidents, faults, etc. incident details, response plans and operating instructions. N2 Provide operational staff with real-time train data, including train location, interval ID, N11 Provide operational origin/destination, car numbers and crew alarms to alert staff to details (inc. non-revenue trains). predetermined combinations of events that represent an increased risk of incident. Management of N12 Provide operational staff Service Safety and with a shared and consistent Management Security view of all completed operational registers. N13 Provide the timely and open access to all the data ISIM-B recorded by ISIM-B such that it may be queried/analyzed/ mined/reported on, using both COTS and custom tools. Customer Information Planning and N14 Provide a replay facility Analysis that uses data recorded by ISIM-B to flexibly replay events using a model board representation. N15 Enable the phased deployment of data collection and distribution capabilities, allowing N18 Record data in a manner that meets differences in data and presentation to operate statutory logging, quality and integrity record consistently together. keeping requirements. N16 Data source and information N19 Tolerate any fault, planned maintenance distribution flexibility, minimizing constraints or upgrade/enhancement so that data quality in their provision and upgrade (inc. CBTC). degrades and recovers both gracefully and recognizably. N17 Highly reliable and available, tolerating faults, planned maintenance or N20 Standardize on a single source for upgrade/enhancement without disabling the each data and standardize operational whole ISIM-B system. processes.

10 LL3: The Need for Lifecycle Tracing NYCT began tracing early Contract Specs included traced requirements Test Procedures required to identified all requirements being tested

11 LL3: Software Engineering Tracing Scheme V and V Report Test Procedures AWOs Prototyping Code PROTO ConOps UR Specification CRD Rqmts Doc (SFRD/SRS) FEAT Software Design (SDD) DE Code (SCI)

12 LL4: The User Interface should Enhance the Operational Experience Need to prepare for the next generation of user Contract Human Factors Engineer(s) Formalized prototyping process Use of informational balloons/pop-ups Seek a college intern to represent the next generation of user

13 LL5: Enhanced Service Delivery through Information Develop an Operations and Scenario Rules Document Codify Institutional Knowledge Develop a set of Performance Indicators - Branch Capacity - Branch Availability - Branch Throughput - Wait Assessment

14 LL5: String-lines Being Proactive

15 LL5: Optimize Operations

16 LL5: Implementing Change

17 Additional Lessons Learned User and Stakeholder involvement throughout the project Project Transparency Incorporate interim milestones Maintain focus on Goals and Objectives Maintenance Team s involvement early Keep projects to a manageable size