starnet implementation
DESCRIPTION
STARNET Implementation. Warren Tighe Siemens ITS January 5, 2006. Presentation Outline. The goals of STARNET Similar efforts around the country Implementation plan and process The role of Siemens ITS Scope of work Time schedule. The Goals of STARNET. - PowerPoint PPT PresentationTRANSCRIPT
STARNET Implementation
Warren Tighe
Siemens ITS
January 5, 2006
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 2
Presentation Outline
• The goals of STARNET
• Similar efforts around the country
• Implementation plan and process
• The role of Siemens ITS
• Scope of work
• Time schedule
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 3
The Goals of STARNET
• STARNET = Sacramento Transportation Area Network
• Connect the region’s real-time transportation management systems
• Allow sharing or real-time data between systems and between users
• Allow sharing of live video
• Provide real-time information to the public via 511 and other outlets
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 4
Why Build STARNET?
• Make travel easier and safer• Gather and disseminate more and better real-
time travel information – Better travel decisions – time, mode, route
• Provide transportation system managers with more and better real-time information– Including information from other agencies– Better operational decisions and actions
• Allow shared use of field devices when appropriate– Better use of resources and better operation
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 5
Transp Managers See Whole Picture
Without STARNET With STARNET
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 6
Sacramento Traffic Signal
System
Sacramento Traffic Signal
System
Sac County Traffic Signal
System
Sac County Traffic Signal
SystemSac County
CCTV System
Sac County CCTV System
Sacramento CCTV System
Sacramento CCTV System
RT LRT Ops Management
System
RT LRT Ops Management
System
RT Bus Ops Management
System
RT Bus Ops Management
System
RT CCTV System
RT CCTV System
Caltrans Freeway
Detector System
Caltrans Freeway
Detector System
CHP Incident Tracking
System (CAD)
CHP Incident Tracking
System (CAD)Caltrans CCTV System
Caltrans CCTV System
C/T Freeway Dynamic Signs
System
C/T Freeway Dynamic Signs
System
Roseville Traffic Signal
System
Roseville Traffic Signal
System
Roseville CCTV System
Roseville CCTV System
Elk Grove Traffic Signal
System
Elk Grove Traffic Signal
System
SACOG Travel Info
System
SACOG Travel Info
System
Sac Bee Travel Info
System
Sac Bee Travel Info
System
Some STARNET Components
Communications Network
Communications Network
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 7
Examples of More Components
• SACOG travel data repository
• Sac County dynamic signs system
• Citrus Heights traffic signal system
• Yolo County Transit management system
• Caltrans weather information system
• Sheriff & police incident tracking systems
• Union Pacific Railroad train tracking system
• Etc.
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 8
Travel Information
• STARNET can be a boon for 511
• Gather more real-time information from more sources
• Travel information servers are just more nodes on the network
Caltrans Systems
Caltrans Systems
County Systems
County Systems
Travel Info Systems
Travel Info Systems
Transit Systems
Transit Systems
City SystemsCity Systems
Communications Network
Communications Network
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 9
Examples Elsewhere
• I-95 corridor• Milwaukee-Chicago-Gary corridor• New York statewide (IEN)• Texas statewide• New York City area (TRANSCOM)• San Francisco Bay area• Los Angeles County (IEN and RITTS)• Etc.• Many similar systems now being implemented
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 10
The Nature of STARNET
• A system of systems• A network of systems• Peer-to-peer communications• Owned and used by multiple agencies• Open to all agencies – may come and go• Use to get data and/or send data• Agencies participate only as desired• Dependent on no one agency or vendor• Just like the Internet
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 11
Interface to Agency Systems
• Build translators as needed to accommodate existing systems.
• Develop new systems where needed.
• Future systems should come with standard interface ready to plug in.
New System with Standard
Interface
New System with Standard
Interface
Existing System with Translator
Existing System with Translator
TranslatorTranslator
Communications Network
Communications Network
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 12
What Do We Implement First?
• Can’t afford to do everything at once
• Prioritize
• Plan a staged implementation
• Make it flexible and expandable (scalable)
• Allow for on-going change
• Identify on-going funding
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 13
What Process is Needed?
• Must design it in order to build it
• Must have requirements in order to design it
• Must have user needs in order to identify requirements
• Must have a concept of operations in order to understand and document user needs
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 14
The Process
Concept of OperationsConcept of Operations
User NeedsUser Needs
RequirementsRequirements
DesignDesign
Build & TestBuild & Test
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 15
Part of Systems Engineering
Systems Eng Management Plan
Concept of Operations
System Requirements
High-Level Design & Subsystem Requirements
Detailed Design Unit Testing
Subsystem Verification
System Verification
& Deployment
System Validation
Operation & Maintenance
Validation Plan
Acceptance Testing Plan
Integrator’s Testing Plan
Operation and Maintenance Plan
Software Coding Hardware Fabrication
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 16
PlanPlan
PlanPlan
The Process Will Repeat
SEMP
Con Ops
Sys Req.
High- Level Design
Design Unit Test
Subsys
Test
System Test &Deploy
Validate
Build
Operate (use)Operate (use)
SEMP
Con Ops
Sys Req.
High- Level Design
Design Unit Test
Subsys
Test
System Test &Deploy
Validate
Build
Cutover
Operate
Each maintenance change, enhancement, upgrade, or
replacement
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 17
The Role of Siemens
• Siemens ITS contracted by SACOG to provide Systems Engineering Assistance during STARNET implementation.
• We will, effectively, serve as specialty staff to the stakeholders.
• We have done this for several other center-to-center networks around the country.
• We will strive to fully understand the stakeholder needs and guide STARNET implementation accordingly.
• A separate firm will be hired to perform system integration. Siemens will help write the RFP and oversee that effort.
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 18
Siemens Work Plan
• Task 1 – Systems Engineering Management Plan
• Task 2 – Concept of Operations
• Task 3 – Requirements & Testing Plan
• Task 4 – High Level Design + Hire System Integrator
• Task 5 – Oversee System Integration
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 19
Systems Engineering Management Plan
• Work break down structure for overall STARNET implementation (more than just the Siemens work)
• Time schedule and interdependencies• Control gates – where formal approval is
needed to continue• Resources needed for each step and where
they will come from• Specific management plans – see next slide
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 20
Specific Management Plans
• Stakeholders Cooperation Plan• System Integration Services Procurement
Plan• System Verification (testing) Plan• Documentation Plan• Configuration Management Plan• Operations and Maintenance Plan• Data Management Plan• Interface Control Plan
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 21
Concept of Operations
• Goals of STARNET, and list of stakeholders• Use of STARNET
– Who will use it?– How will they use it?– Where, when, why, etc.?– Describe operational scenarios
• Constraints (e.g., funding)• Opportunities (e.g., low hanging fruit)• Validation metrics – how do we know if we
succeeded?
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 22
User Needs
• Extract from Concept of Operations
• A list of needs
• Written in plain language that stakeholders can easily understand and check
• Check that all are justified by the Concept of Operations
• Check that none are missed
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 23
System Requirements
• Derive from User Needs• A list of technical requirements• Written in concise, short, technical,
unambiguous statements – precise and quantitative
• Basis for system integration contract, design, and acceptance testing
• Intended for technical specialists• Check that all User Needs are addressed,
and that all Requirements are justified
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 24
High Level Design
• General concepts and architecture
• A guide for prospective system integrators
• Will not limit creativity and opportunities available from prospective system integrators
• Use for cost estimating and feasibility checks
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 25
Stakeholder Involvement
• BIG role up front:– Concept of Operations– User Needs– Specialty management plans– RFP for system integrator
• Less involved during detailed design and build stage – mainly system integrator
• Increasing role as parts ready for review and testing, then training and documentation
• Fully engaged again when using the system
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 26
Like Tule Fog for a While
Systems Eng Management Plan
Concept of Operations
System Requirements
High-Level Design & Subsystem Requirements
Detailed Design Unit Testing
Subsystem Verification
System Verification
& Deployment
System Validation
Operation & Maintenance
Validation Plan
Acceptance Testing Plan
Integrator’s Testing Plan
Operation and Maintenance Plan
Software Coding Hardware Fabrication
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 27
Next Steps
• Review draft documents from Siemens– System Engineering Management Plan– Strawman Concept of Operations
• Attend one-day workshop on Concept of Operations– Review and discuss strawman Con Ops– Brainstorm improvements to concept of
operations– Agree on refined Concept of Operations and
User Needs
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 28
Schedule of Stakeholder Activities• Concept of Operations workshop in latter half of
February – includes User Needs.• Review various specialty management plans in
latter half of March.• Review System Requirements and Verification
(testing) Plan in late May and in June. • Go on vacation in July.• Review high level design and other documents in
August.• Review RFP for system integrator in September.
• Review proposals, and interview firms, in December.
• System Integrator on board by March 07.
Feb 06Feb 06
MarMar
AprApr
MayMay
JunJun
JulJul
AugAug
SepSep
OctOct
NovNov
DecDec
Mar 07Mar 07
ST
AR
NE
T I
mpl
emen
tatio
n
Sie
men
s IT
S
Jan
06
Slid
e 29
Questions and Discussion