Information Systems Network (ISN)

1
Information Systems Network (ISN) System
Requirements Proof-of-Concept

• Chris Hill
• Mixon/Hill, Inc.
• March 17, 2008

2
Agenda

• Purpose of Meeting
• ISN Background
• ISN Progress
• ISN System Requirements Specification
• ISN Proof-of-Concept

3
Describing the Need

• Traffic and weather dont stop at jurisdictional
  boundaries
• Consequences can spill over
• Major incidents and events can have long distance
  effects
• External events can overwhelm what I know and can
  control

4
Describing the Need

• Need notification, data access, and data exchange
• Prefer local presentation (native to existing
  systems), but could be a remote web page
• May cover incidents, events, or weather
• May affect highways and transit

5
ISN Objective

• ISN provides an integrated view of transportation
  events across jurisdictional boundaries
• ISN intended to support agency management and
  operations tasks
• Desire is to share information in real time

6
ISN Limitations

• ISN does not change collection of data or
  exercise of control within jurisdictions
• Does not add or modify sensors
• Does not add or modify signs or traveler
  information outlets
• No control of latency in originating systems
• Agencies chose what info to share and what to use

7
ISN Progress

• Concept of Operations complete
• ISN Architecture complete
• User Survey complete
• System Requirements draft prepared submitted to
  Project Team
• Peer review by TRANSCOM UMd disposition of
  comments complete

8
Requirements Development

• ISN developed using systems engineering approach
• In general, system requirements specification
  defines what the system will do, but not how
• Objective is to have well-written, verifiable,
  and testable requirements
• Requirements precede system design

9
Requirement Categories

• Functional overall describes what the system
  will do
• Interfaces primarily defines standards for both
  user and system-system interfaces
• Constraints items that limit how the system can
  be implemented often standards

10
Requirements Categories

• Data identifies all the desired data elements
  based on user survey
• Performance and quality such as number of
  users latency of data
• Security access restrictions and role of system
  administrators

11
Requirements Categories

• Training/documentation for administrators and
  users
• External organization, oversight, and policies

12
Example Functional Requirements
ID Requirement Source Criticality
F-001 The ISN shall allow a system administrator to configure ISN components. Arc. 3.2 H
F-001-001 The Administration/Configuration component shall allow a system administrator to configure information about member agencies. ConOps 3.2.2 ConOps 3.3.1 H
F-001-002 The Administration/Configuration component shall allow a system administrator to define a location for each data interface. Arc. 4.2 H
F-001-003 The Administration/Configuration component shall allow a system administrator to activate or deactivate a data feed. MHI H
F-002 The ISN shall publish alerts containing summary information of issues affecting travel within the I-95 corridor. ConOps 3.2.1 ConOps 3.3.1 H
F-002-001 The Publishing Services component shall publish alerts about traffic-related information received from contributing agencies. ConOps 3.2.1 ConOps 3.3.1 H
13
System Requirements Specification

• Current document defines requirements for
  ultimate system
• Addresses all needs identified during member
  survey
• Address a Corridor-wide system with interfaces to
  other systems (e.g., archive, probe data system)

14
Proof-of-Concept

• POC Approach submitted to Project Team
• Identify a subset of must have requirements
  from the full set
• Implement these through data sharing between two
  geographically separated regional information
  systems
• Conduct acceptance tests and perform evaluation
  with users

15
Proof-of-Concept

• POC will take place between TRANSCOM RA-web in
  NY/NJ/CT and RITIS in National Capital Region
• Initial meetings and agreement in-principle
• POC would be performed over next 12-months

16
Questions?

• Bill Stoeckert
• I-95 Corridor Coalition
• wstoeckert_at_yahoo.com
• Chris Hill
• Mixon Hill
• chris.hill_at_mixonhill.com