Integrated Service and Information Management: B-Division (ISIM-B)

Tom Colacioppo, CCM, CSEPNew York City Transit

Project ManagerNew York, NY

Build it and they will come

And they did

Key Presentation Take-Aways

• What is ISIM-B and what will it deliver?• How we incorporated our lessons learned

into ISIM.

ISIM-B: What Will it Provide?Situational Awareness

M3: ISIM-B

Office System

ISIM-B User

Elevators/EscalatorsLiftNet

Communications Based Train Control

(CBTC)

Subway Incident Reporting System

(SIRS)

Unified Timekeeping System (UTS)

UGOS

Work-Train Manifest

Traction Power SCADA

M1:ISIM-B

Signal SystemM4:

PA/CIS II

RCC Flagging System (RCCF)

Rapid Scheduling System

(RSS/HASTUS)

Rolling Stock Maintenance

Information System (RSMIS)

Requests/Status

CrewInformation

Voice

External Train Arrival Time

Bus Schedules & On-Time

Performance

o ElevatorStatus o Escalator Status

GO Information

Car Status

Bus LocationsWork Train Info

Train Position and Train Health

Train Position and Schedules

Flagging Zones

Train Event RecordersTrain Event Data

Subway Incidents

o 3rd Rail Powero Fan Status

A-Division Train Locations

Data WarehouseTrain PerformanceData

Login Info

• Schedule Based Train Tracking

• Train Arrival Times• Integrated Information• Key Performance

Indicators• Enhanced (Rules-Based)

Service Delivery Information

• Data Mining Capabilities

ISIM-B: Comparision of Divisions

A Division B Division

Lessons LearnedAnd Why We Manage Them

• Repeat our Successes• Correct Our Mistakes• GOAL: Continuously Improve our Process

LL1 Resisting the Temptation of Declaring Premature Success

• Gives a false sense of accomplishment• Established a clear set of expectations• Removed all ambiguous requirements

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

ISIM-B

Service Management

Customer Information

Management of Safety and Security

Planning and Analysis

N1 – Provide operational staff with a shared view/awareness of the state of the railroad – inc. assets, staff, incidents, faults, etc.

N4 – Provide operational staff with real-time graphical Divisional performance information by line.

N2 – Provide operational staff with real-time train data, including train location, interval ID, origin/destination, car numbers and crew details (inc. non-revenue trains).

N5 – Provide operational staff with real-time graphical train performance data (inc. schedule adherence).

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.

N15 – Enable the phased deployment of data collection and distribution capabilities, allowing differences in data and presentation to operate consistently together.

N7 – Provide consistent and timely service performance information to customers.

N6 – Provide customers with consistent and timely train arrival predictions for stations.

N8 – Provide customers and operational staff with consistent and timely information and predictions about disruption to the train service.

N10 – Provide operational staff with a consistent view of incident details, response plans and operating instructions.

N11 – Provide operational alarms to alert staff to predetermined combinations of events that represent an increased risk of incident.

N13 – Provide the timely and open access to all the data recorded by ISIM-B such that it may be queried/analyzed/mined/reported on, using both COTS and custom tools.

N14 – Provide a replay facility that uses data recorded by ISIM-B to flexibly replay events using a “model board” representation.

N9 – Publish consistent and timely service information, predictions and data via the internet.

N16 – Data source and information distribution flexibility, minimizing constraints in their provision and upgrade (inc. CBTC).

N18 – Record data in a manner that meets statutory logging, quality and integrity record keeping requirements.

N17 – Highly reliable and available, tolerating faults, planned maintenance or upgrade/enhancement without disabling the whole ISIM-B system.

N19 – Tolerate any fault, planned maintenance or upgrade/enhancement so that data quality degrades and recovers both gracefully and recognizably.

N20 – Standardize on a single source for each data and standardize operational processes.

V0.5 16-Oct-2012

N12 – Provide operational staff with a shared and consistent view of all completed operational registers.

Time

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

Better operational plans and schedules by improving analysis of historical service data

Better service management by improving service monitoring and regulation

Purp

ose:

Obj

ectiv

es:

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

Centralized service monitoring, control and customer information at the RCCCurrent Operation

Long-term Goal

Capa

bilit

y

ISIM-B Project

LL3: The Need for Lifecycle Tracing

• NYCT began tracing early• Contract Specs included traced

requirements• Test Procedures required to identified all

requirements being tested

LL3: Software EngineeringTracing Scheme

ConOps Specification Rqmts Doc(SFRD/SRS)

Software Design(SDD)

Code(SCI)

Prototyping

Test Procedures

V and VReport

UR FEATCRD DE

PROTO

Code

AWOs

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

LL5: Enhanced Service Deliverythrough 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

LL5: String-lines Being Proactive

LL5: Optimize Operations

LL5: Implementing Change

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