sunguide sm software development project status meeting march 9, 2004

SunGuideSunGuideSMSM Software Development Project Software Development Project

Status Meeting Status Meeting March 9, 2004March 9, 2004

March 9, 2004SunGuide Status Meeting 2

AgendaAgenda

Time Item Lead

2:00 – 2:05 Introductions Hsia and all participants

2:05 – 2:25 Configuration Management: CM during development CM during / after deployment

Dellenback / Heller

2:25 – 2:50 Districts’ TMC and Software Deployment Schedule Updates (Sorted by scheduled or planned deployment date)

Faquir - District 4 Bitting - District 7Martinez - District 6 Campo - MDXBirosak - District 1 Vega - District 2Rivera - District 5 McCrary - District 3Birenbaum - Turnpike Enterprise

2:50 – 2:55 MOU between FDOT and TxDOT, Software License Updates: TransGuide, and TxSoftware Sublicense Modification for D2

Hsia / Dellenback

2:55 – 3:15 Computer Size Estimates for TMC Dellenback

3:15 – 3:30 Break

3:30 – 4:00 Project Status Report: Development status GUI / Map Screen Snapshots Cost and schedule status Action item follow-up

Dellenback

4:00 – 4:15 New device drivers: Driver details Cost and schedule

Dellenback

4:15 – 4:30 Open Discussion / Action Item Summary Dellenback


AgendaAgenda

Time Item Lead



Dellenback / Heller




Hsia / Dellenback


3:15 – 3:30 Break


Dellenback


Dellenback



Configuration Management Configuration Management

Definition: The process of selecting items whose configuration and change status will be controlled (baseline items), defining the process by which those items will be controlled, and then implementing that process.

Following slides:– Project view of CM– Statewide view of CM


Project View of CM


SunGuideSunGuideSMSM Software CM Requirement Software CM Requirement

Scope of Services Requires

– Use of Rational© ClearCase© for Configuration Management (CM)

– Initial delivery of CM baseline corresponding to software before modifications

– Delivery of CM repositories with each release


CM RepositoriesCM Repositories

Active Repositories

– ClearCase repository utilized for baselines

– Microsoft© Visual Source Safe© (VSS) for daily development

– Department repository per SwRI Software Engineering Process (SEI CMM-Level 3)

– Project web-site for delivered documents

Backed up daily through Division IT services


Daily CM ProcessDaily CM Process

Visual Source Safe is tightly integrated with Microsoft Visual Studio

Developers responsible for check-in and check-out cycles:– Encourage daily check-in / check-out– Facilitates coordinated builds– Multiple projects under VSS are active

MS Windows share backed up by Division IT group


Department Process RepositoryDepartment Process Repository

All artifact deliveries to FDOT placed in department CM repository:

– Maintained by administrative support staff

– Part of SEI CMM approved process

– Backed up by Division IT group


SunGuide.datasys.swri.edu SunGuide.datasys.swri.edu Project Web SiteProject Web Site

Contains copies of all deliverables

Maintained by project staff

Updated as deliveries made via email

Source backed up by division IT group


ClearCase RepositoryClearCase Repository

Initial Baseline (delivered) consists of source code and documents from– Chart II Incident Management– TxDOT Traffic Operations Division

Deferred baselined source code:– TransGuide

Three More baselines anticipated– Release 1– Release 2a– Release 2b

Resides on Microsoft Windows share

Backed up by Division IT group


Baseline Release PreparationBaseline Release Preparation

Prior to release of baseline perform

– Functional Configuration Audit

• Formal test

• Report is written

– Physical Configuration Audit

• Delivery media prepared

• Delivery media all “parts” to build baseline

• Report is written

Copy to Department Repository


Statewide View of CM


CM Common TermsCM Common Terms

Baseline Item: A product of an effort which is to be maintained under configuration management. Typical baseline items include plans, ITS Architectures, Standards, specifications, and software source code.

Engineering Change Requests (ECRs): A formal request for a change to requirements.

Configuration Management Board (CMB): A group of people responsible for evaluating and approving or disapproving proposed changes to baseline items, and for ensuring implementation of approved changes.

Configuration Manager: Person selected by the CMB to manage the configuration management activities; including the oversight of the CMB.


Statewide PerspectiveStatewide Perspective

Centralized Baseline

Issue submission

CMB composition and purpose

Configuration Management Process


CM Centralized BaselineCM Centralized Baseline

Statewide Configuration Management Repository

Project Repository

Project Repository

Master SunGuideSM products are stored in a central location:– Documents– Source code– Installation scripts

For each active development project:– Code copied to a project

repository– Development occurs

against the local repository– After acceptance testing,

moved back to statewide location


CM Issue SubmissionCM Issue Submission

Statewide Issues/ECRs

CMB

Review

Issues

Approved

No

Local Issues

Local Issues

Local Development

Issues

Implement ECRsYes

District Staff District Staff Central Office Staff

FDOT ContractorsTurnpike Staff

Local Issues

ECR is submitted

Reviewed by CMB

If approved:

– ECP (Engineering Change

Proposal) that contains

cost and schedule

– If ECP is approved:

• ECO (Engineering

Change Order) issued


CM CMBCM CMB

Purpose

– Select Configuration Manager

– Evaluate proposed changes (ECRs)

– Approve/Disapprove ECRs

– Interact with Other Organizations


CMB CompositionCMB Composition

Configuration Manager

Board

District 1 District 5District 2 District 6District 3 District 7District 4 MDXTurnpike EnterpriseBroward CountyLee County

Baseline Item Experts

FDOT Consultants

Central Office


CM Process - SummaryCM Process - Summary

Identify Issue

Review Locally and Resolve (if possible)

Develop and Submit ECR to Statewide System

Review ECR with CMB

If ECR approved, software developer generates a ECP that

contains cost and schedule

FDOT reviews and approves ECP and provides a ECO to the

software developer

Software developer implements ECO

Release product

Install product


CM Questions / Comments


AgendaAgenda

Time Item Lead



Dellenback / Heller




Hsia / Dellenback


3:15 – 3:30 Break


Dellenback


Dellenback



Discussion TopicsDiscussion Topics

Status of current ITS construction projects

Planned ITS deployments

Deployment specific questions:

– Server operating system:

• Microsoft Server 2000

• Microsoft Server 2003

– Workstation operating system:

• Microsoft Server XP


AgendaAgenda

Time Item Lead



Dellenback / Heller




Hsia / Dellenback


3:15 – 3:30 Break


Dellenback


Dellenback



Software License IssuesSoftware License Issues

SwRI / FDOT License– License executed before the contract started.– TxDOT informed SwRI on January 22, 2004 that TransGuide software was

on “hold”.

TxDOT / FDOT MOU– FDOT provided TxDOT with comments and legal opinion on March 2, 2004

FDOT / TransGuide License– FDOT provided TxDOT with customized License Agreement on February

19, 2004

SwRI / FDOT Sublicense for District 2

FDOT / WsDOT Term of Use

FDOT / MDX Joint Program Agreement (JPA)


AgendaAgenda

Time Item Lead



Dellenback / Heller




Hsia / Dellenback


3:15 – 3:30 Break


Dellenback


Dellenback



History of Computer Sizing History of Computer Sizing EstimatesEstimates

SwRI asked during Kick-off meeting to provide sizing estimates (Action Item #9).

SwRI has performed initial sizing analysis and provided a sizing report to FDOT on February 5, 2004.

Provides a technique to “estimate” computer needs.

Contents are preliminary and conservative: document will be updated as software testing continues.


Computer Sizing Estimates: Computer Sizing Estimates: Conceptual DeploymentConceptual Deployment


Computer ConfigurationsComputer Configurations

Workstations:– Microsoft Windows XP, Internet Explorer 6.01 or greater– SVG Viewer 3.0 or greater– 2.4 to 3.0 GHz processor– 512 MB RAM– 20 GB disk

SunGuideSM Database Server (these requirements will vary widely based on how much data the SunGuideSM implementation chooses to log and the backup policies implemented by the SunGuideSM implementation computer staff):

– Microsoft Server 2000– Oracle 9i– > 2.4 GHz processor– > 2 GB RAM (Oracle likes RAM – the more the better)– 70 GB of disk using RAID architecture (this disk space will vary based

on the amount of historical information logged to the database) SunGuideSM Application Servers (SunGuideSM processes):

– Microsoft Server 2000– Executive Handler – > 2.4 GHz processor– 1 GB RAM– 36 GB of disk


SizingSizingTableTable

Used to estimate computing resources

Process can be “mixed and matched”

Impacts:– Number of users– Number of devices– Multi processors

District specific evaluations will be made during initial stages of implementation


Sample Sample ExerciseExercise

Assumed:– 100 DMSs– 200 Detectors– 10 simultaneous uses

Summary:– Need a database server– 3 dual processor

application servers (provides growth capacity)

Note:– Size estimates will be re-

evaluated after integration (and probably go down) Application

Servers Only


AgendaAgenda

Time Item Lead



Dellenback / Heller




Hsia / Dellenback


3:15 – 3:30 Break


Dellenback


Dellenback



Project Web SiteProject Web Site

http://sunguide.datasys.swri.edu


Release-Oriented Release-Oriented Development ApproachDevelopment Approach

Release 1 Release 2a Release 2b not in scope


Scope of SunGuideScope of SunGuideSMSM Effort Effort

Release 1:– Core software framework:

• Database• Process viewer• Status logger• User interface• Map

– DMS subsystem, drivers for:• NTCIP Florida MIB• Mark IV version 2.5

– CCTV subsystem, drivers for:• NTCIP camera support• American Dynamics 2050 switch

– Traffic Detection, driver for:• Bitrans 238I-95

– Incident management subsystem

Release 2a:

– Core software framework upgrade

– Center-to-Center

– FDOT Central office configuration

– Ramp metering

– CCTV subsystem, drivers:

• SunGuideSM protocol

– RWIS

– Archive data

– HAR

– Web server

– Emergency evacuation

Release 2b:

– Inventory and maintenance


Status of Release 1 ActivitiesStatus of Release 1 Activities

Project Management:– PM / Meetings / Reviews– Process documents– Interface Control Documents (ICDs)

Core software framework:– Database– Process viewer– Status logger– User interface– Map

DMS subsystem, drivers for:– NTCIP Florida MIB– Mark IV version 2.5

CCTV subsystem, drivers for:– NTCIP camera support– American Dynamics 2050 switch

Traffic Detection, driver for:– Bitrans 238I-95

Incident management subsystem


Status of Release 2a ActivitiesStatus of Release 2a Activities

CCTV subsystem, drivers for:– SunGuideSM protocol camera support – stopped per FDOT

request

Ramp Metering:– Developing requirements– Plan to perform a site visit to WashDOT operations facility


Screens: Executive HandlerScreens: Executive Handler


Screens: Executive Handler - Screens: Executive Handler - continuedcontinued


Screens: MapsScreens: Maps


Screens: Maps - continuedScreens: Maps - continued


Screens: XML Client TesterScreens: XML Client Tester


Deliverable StatusDeliverable Status

Pending:

– Final version of Software Requirements Specification

Future documents:

– Software Design Document:

• HTML based

• See next page

– Software Acceptance Test Plan

– Software Integration Plan

All available on project web site.


SDD SnapshotsSDD Snapshots


Cost StatusCost Status

Release 1:

– Budget amount: $3,208,052

– As of 2/11/04, ~$997,000 has been expended

Release 2a:

– Budget amount: $2,074,276

– As of 1/2/04, $34,631 has been expended

Release 2b:

– Budget amount: $245,311

– As of 1/2/04, $0 has been expended


Schedule StatusSchedule Status

Current schedule is posted to project web site

Overall project status:– Ahead in many places– SunGuideSM is operational in the lab:

• Support processes (executive, logging)• GUI• Map• Data Bus• DMS:

– Mark IV– NTCIP

• CCTV:– Master process– NTCIP driver– “Pelco” driver (for testing purposes only)

• TSS:– Master process– Simulator process (up to 1000’s of detectors)

• Incident management


Schedule Status - continuedSchedule Status - continued

Current areas of concern:– Documents:

• None

– Lack of final device drivers

– Baseline software (TransGuide component)


DMS Functional Thread:DMS Functional Thread:GUI - Data Bus – DMS Subsystem - DeviceGUI - Data Bus – DMS Subsystem - Device


CCTV Functional Thread:CCTV Functional Thread:XML Simulator - Data Bus – CCTV Subsystem - DeviceXML Simulator - Data Bus – CCTV Subsystem - Device


TSS Functional Thread:TSS Functional Thread:Device Simulator - TSS Subsystem - Data Bus – XML SimulatorDevice Simulator - TSS Subsystem - Data Bus – XML Simulator



Project status meeting after ITS America (April 26 – 28 in San Antonio) on April 29th– Agenda:

• Project status• See SunGuideSM operating in a multi-server, multi-

workstation environment with REAL EQUIPMENT• Meet the development team

DMS Milestone Demo:– District 4: Schedule still being evaluated


SwRI Development LabsSwRI Development Labs


Action ItemsAction Items


Action Items - continuedAction Items - continued


General Comments / Feedback on Project Status


AgendaAgenda

Time Item Lead



Dellenback / Heller




Hsia / Dellenback


3:15 – 3:30 Break


Dellenback


Dellenback



Draft Contract Amendment List:Draft Contract Amendment List:Sent by Central ITS Office on 2/9/04Sent by Central ITS Office on 2/9/04


Device DriversDevice Drivers

Device functionality isolated by “ICDs” (Interface Control Documents)

Subsystems are “generic” and not specific to device functionality

Device drivers easy to add once base subsystem is complete and operational


Device Drivers In BAFO That Were Device Drivers In BAFO That Were Approved For ImplementationApproved For Implementation

DMS:

– NTCIP

– Mark IV (v 2.5)

CCTV (Cameras):

– NTCIP

– SunGuideSM (Stopped development)

Video Switch:

– American Dynamics 2050 (Stopped development)

Traffic Detectors:– BiTrans 238I-95

Ramp Metering:– WsDOT (firmware)

RWIS:– NTCIP

HAR


SwRI Asked To Evaluate Adding SwRI Asked To Evaluate Adding New Devices to Development EffortNew Devices to Development Effort

IP-Video Device Driver

EIS RTMS TSS Device Driver

Wavetronix RTMS TSS Device Driver

3M (Canonga) Microloop TSS Device Driver

Trailblazer Device Driver and GUI Support

Intelligent Devices Incorporated (IDI) Support

Barco / Argus:

– Video Switch Device Driver

– Wall Configuration Software

DTS Video Switch


All Development Efforts Include…All Development Efforts Include…

The device driver compliant with the appropriate SunGuideSM device driver Interface Control Document (ICD).

Development efforts will include:– Design– Peer Review– Implementation– Testing– Integration


IP VideoIP Video

Scope:– SwRI will develop an IP-Video video switch device

driver that will instruct “decoders” to listen to “encoders”.

– The device driver will issue SNMP commands to the following decoders:

• CorTec• Teleste• VBrick• iMpath

Assumptions:– SwRI will not be performing inter-operability testing

between different brands of encoders and decoders.


RTMS TSS Device Driver(s)RTMS TSS Device Driver(s)

Scope:– A device driver for a Electronic Integrated System (EIS) RTMS device

will be developed.– A device driver for a Wavetronix SmartSensor device will be

developed.– A device driver for a 3M Canoga, model C400/C800/C990E device will

be developed.

Assumptions:– The serial port of the EIS RTMS device shall be connected to a terminal

(port) server so that a TCP/IP interface can be used to retrieve data.– TCP/IP interface of the Wavetronix RTMS device shall be used to

retrieve data.– The serial port of the 3M device shall be connected to a terminal (port)

server so that a TCP/IP interface can be used to retrieve data.

Notes:– Concurrent development of these drivers will results in a cost savings.


Trailblazer Device Driver and GUI Trailblazer Device Driver and GUI SupportSupport

Scope: – Develop a device driver (to be included in the DMS

subsystem) to support Trailblazer devices, SunGuideSM protocol will be used to communicate to the devices.

– Develop a GUI that will provide the operator with the capability to request display modifications on a Trailblazer.

– Development staff will travel to Miami for two on-site test periods (up to four days each).


Intelligent Devices Incorporated Intelligent Devices Incorporated (IDI) Support(IDI) Support

Scope:– Work with FDOT staff to identify candidate devices– Observe NTCIP testing with FDOT staff– Once devices accepted by FDOT, perform integration testing with

SunGuideSM software framework

Assumptions:– FDOT will procure all devices– All NTCIP compliance testing to be performed by FDOT (TERL)– No software development effort by SwRI


DTS Video SwitchDTS Video Switch

Scope:– SwRI will develop video switch driver that will instruct the DTS video

system to connect video inputs to video outputs.– The device driver shall be compliant with the SunGuideSM CCTV Video

Switch Interface Control Document (ICD) interface

Assumptions:– SwRI assumes that camera control and video switching both need to

be supported by this driver.– SwRI needs protocol documents from DTS before we can initiate and

design or development.– SwRI needs access a FDOT provided DTSS unit for testing and

development. SwRI has included funds to travel to FDOT specified locations.

Note: – The estimated cost SwRI has provided is an conservative costs; SwRI

has been given limited access to technical information about how to communicate to the DTS switch from an external source.

– Non-disclosure has been put in place – waiting for technical detail.


Barco / ArgusBarco / Argus

Scope:– SwRI is proposing two applications:

• Video switch device driver:– SwRI will develop a video switch driver that will instruct the video

wall to change displays in the “Barco Windows”.– The device driver shall be compliant with the SunGuideSM CCTV Video

Switch Interface Control Document (ICD) interface

• Video wall configuration software:– SwRI will extend the SunGuideSM GUI to allow the Barco video wall to

be reconfigured using SunGuideSM software.– The software will allow virtual windows to be defined and input

streams associated with each of these windows.– Note: this software would replace the Barco provided software for

configuring the video wall.

Assumptions:– SwRI requires access to a Barco unit for fact finding. – SwRI requires a Barco software development environment at SwRI.– SwRI requires access to DTS development staff for questions / answers.


Device Driver CostsDevice Driver Costs

SwRI was asked to evaluate the current device driver costs

Current device drivers were included in the BAFO approved by FDOT

New drivers can be added:– SwRI based cost estimates on some assumptions (see

previous slides)– SwRI has developed cost estimates– Schedule impact may vary based on timing and number

of new drivers added


Device Driver Costs - continuedDevice Driver Costs - continued

IP-Video Device Driver: $134,322

EIS RTMS TSS Device Driver: $103,684

Wavetronix RTMS TSS Device Driver: $103,684

3M (Canonga) Microloop TSS Device Driver: $129,074

Trailblazer Device Driver and GUI Support: $56,381

Intelligent Devices Incorporated (IDI) Support: $89,910

Barco / Argus:

• Video Switch Device Driver: $184,788

• Wall Configuration Software: $178,471

DTS Video Switch: $202,003


Device Driver Costs - continuedDevice Driver Costs - continued

Cost reductions:

– CCTV American Dynamics Driver: ~$69,000

– CCTV SunGuideSM Driver: ~$52,000

Net cost impact to project:

– Additions: $1,182,317

– Reductions: $123,000

– NET: $1,061,317


Tentative ScheduleTentative Schedule


AgendaAgenda

Time Item Lead



Dellenback / Heller




Hsia / Dellenback


3:15 – 3:30 Break


Dellenback


Dellenback



Future MeetingsFuture Meetings

Outreach Meeting: March 10th (1:45 to 2:00)

Next Status Meeting:– April 29th (in conjunction with ITS America):

• Status Report• Significant software demonstration

Need to schedule:– Software Design Review

Need to confirm:– May Status Meeting– June Status Meeting


Questions / Comments


Action Item RecapAction Item Recap

Number Person Action

39

40

41

42

43

44

45

sunguide sm software development project status meeting march 9, 2004

Documents

configuration manager

software source code

controlled baseline

typical baseline items

processvisual source

project staffupdated

project website

microsoft windows sharebacked