sunguide sm software development project status meeting (via teleconference) october 4, 2005 cdrl...

SunGuideSunGuideSMSM Software Development Project Software Development Project

Status Meeting (via teleconference)Status Meeting (via teleconference)October 4, 2005October 4, 2005

CDRL 1-8.3.22CDRL 1-8.3.22

October 4, 2005SunGuide Status Meeting (teleconference) 2

AgendaAgenda

Time Item Lead

8:30 – 8:35 Introductions Liang Hsia

8:35 – 8:45 License Update - WsDOT TOU, MDX JPA, SwRI License Liang Hsia

8:45 – 9:00 TMC and Software Deployment Schedule Updates

D1 D2 D3D4 D5 D6D7 MDXTurnpike EnterpriseLee County

9:00 – 9:15 Project Status Report Steve Dellenback

9:15 – 9:20 District 2 Deployment Status Steve Dellenback

9:20 – 9:25 Next Three Month Plan Steve Dellenback

9:25 – 9:30 Break

9:30 – 11:10

Proposed ECO #2.0 requirements:IM through Center-to-CenterRoad RangerToll Tag ReaderPerformance Measures

John Bonds /Liang Hsia /Steve Dellenback

11:10 – 11:25 C2C Project & State EOC Communications Update Jim Mosser

11:25 – 11:30 Closing remarks, action items, and adjourn Liang Hsia


Introductions


AgendaAgenda

Time Item Lead








9:25 – 9:30 Break

9:30 – 11:10






License Updates - continuedLicense Updates - continued

FDOT / WsDOT Term of Use (TOU):– WsDOT provided FDOT with standard TOU on February 11, 2004.– FDOT provided recommendation on to WsDOT on March 13, 2004.– FDOT provided comments to the WsDOT’s Office of General Counsel’s

August 21, 2004.– WsDOT began working on FDOT’s comments on August 26, 2004.– FDOT requested status on September 14, 2004, October 7, 2004 and

November 5, 2004.– FDOT & WsDOT attorneys and project managers had teleconference on

November 30, 2004.

– New Option:• WsDOT would license to “Southwest Patents”• “Southwest Patents” would license to FDOT• This resolves the indemnification issue• July 12, 2005 Letter to Gummada Murthy, WsDOT Director, Maintenance

&Operations• August 1, 2005 Letter from WsDOT• WSDOT provided SwRI with draft license on September 12, 2005 that

had some very “tough” insurance clauses• SwRI returning recommended language to WSDOT during week of

October 3, 2005



FDOT / MDX Joint Program Agreement (JPA)

– FDOT provided MDX with preliminary JPA on December 3, 2003.

– MDX provided FDOT with draft final JPA on June 23, 2004.

– FDOT worked on Locally Funded Agreement and MDX JPA.

– FDOT forwarded updated JPA and sublicense to MDX on October 26, 2004

– FDOT developed a draft Software General and On-Site Support Agreement to address MDX’s software support concerns on February 11, 2005.

– FDOT forwarded the updated JPA to MDX on June 7, 2005.



SwRI / FDOT / Lee County Sublicense– Lee County provided FDOT with official letter for participation on

July 27, 2004– FDOT and SwRI started documentation preparation on July 30, 2004– SwRI provided FDOT with draft language on September 10, 2004– FDOT forwarded sublicense to Lee County on October 26, 2004

FDOT issued iFlorida Data Collection Process (DCP) notice to proceed on September 8, 2004.

Dynamap License: – System Planning Office and Office of Information Systems are

finalizing the license agreement on September 14, 2004.– Kevin Thibault approved the $130,000 GDT Procurement on October

19, 2004.– Statewide license effective on March 31, 2005.



FDOT / SwRI SunGuide License– August 12, 2005 FDOT Office of General Counsel completed

preliminary review of draft final version.


License Updates - License Updates - Oracle Oracle continuedcontinued

Transportation Management Center Date Required OIS Licensed Processor Current License Duration

District 1 Ft. Myers RTMC Sun 12/31/06 2

District 1 Sarasota RTMC Sat 12/31/11

District 2 Jacksonville RTMC Sun 12/31/06 2 10/3/03 to 10/3/08

District 3 Pensacola RTMC Mon 12/31/07

District 3 Tallahassee RTMC Wed 12/31/08

District 4 Ft. Lauderdale RTMC Mon 1/31/05 2 10/3/03 to 10/3/08

District 4 West Palm RTMC Mon 12/31/12

District 5 Orlando RTMC Mon 12/31/07 4 6/6/05 to 6/6/10

District 6 Miami RTMC Thu 6/30/05 2 10/3/03 to 10/3/08

District 7 Tampa RTMC Sun 4/30/06 2 10/3/03 to 10/3/08

Lee County RTMC Sat 12/31/05

Miami-Dade Expressway RTMC Thu 6/30/05 2

Statewide TMC & Testing Lab Tue 5/31/05 2 10/3/03 to 10/3/08

Turnpike Pompano RTMC Mon 12/31/12

Turnpike Turkey Lake RTMC Mon 12/31/12


License Updates – Support AgreementLicense Updates – Support Agreement

Software general and on-site support requirements were discussed on December 7, 2004

Draft final Software General and On-Site Support Agreement has been forwarded to SwRI on February 11, 2005

SwRI returned comments to FDOT on April 20, 2005

Summary and updated Support document were distributed on July 1, 2005

CMB approved support (for one year) on July 19, 2005


AgendaAgenda

Time Item Lead








9:25 – 9:30 Break

9:30 – 11:10






Reports by Deployment and Reports by Deployment and Possible Integration SchedulePossible Integration Schedule

District 4

District 2

District 6

MDX

District 7

District 1

Lee County

District 5

District 3

Turnpike Enterprise


District 4 ScheduleDistrict 4 Schedule

June 13-17, 2005: SunGuideSM software deployed at D4 TMC

August 12, 2005: 45 CCTV available

August 16 Software Design & Maintenance Training

October 2005: Complete I/95/I595 Video Monitor System


District 6 RTMCDistrict 6 RTMC

August 29, 2005: Milestone Demonstration

November 1-3, 2005: FAT

November 7-11, 2005: SunGuideSM software deployment

November 15-16: Administrator and Operator Trainings

November 9, 2005: I-95 Package B project completion

1st Quarter 2006: Ramp Meters, C2C


MDX ScheduleMDX Schedule

March 2006 SunGuideSM Software Release 2 deployment at MDX

March 2006 MDX TMC Operational



June 2006 Building Construction Finish3rd Quarter 2006 SunGuideSunGuideSM Software Deployment



Sep 6-9, 2005Sep 6-9, 2005 SunGuideSunGuideSM Deployment Deployment



FY 2004FY 2004 Orlando RTMC retrofit and upgrade Orlando RTMC retrofit and upgradeSeptember 8, 2004 -September 8, 2004 - iFlorida Data Collection Process iFlorida Data Collection ProcessDecember 2005 December 2005 FY 2004-2005FY 2004-2005 iFlorida C2C between Districts 2 and 5 iFlorida C2C between Districts 2 and 5


Turnpike RTMCTurnpike RTMC

SunNavSM Development

April-December 2004: SunNav 1.2 Release • NTCIP Drivers for DMS• DMS GUI Field Sorting

November 2005 SunNav 2.0 (Final Completion)

• Web-based XML Release• NTCIP Camera Driver• Replication of Data• Incident Management Dynamic

Expansion• Response Plan Upgrades

1st Qaurter 2006 SunGuideSM Software• Center-to-Center Interface Module


District 1District 1

May 2005 I-75 Safety Barrier System upgrade December 2006 SunGuideSM Deployment at Ft. Myers RTMC

FY 2011 (2005) Sarasota RTMC


District 3District 3

FY 2007 Pensacola RTMC FY 2007 Pensacola RTMC FY 2008 Tallahassee RTMCFY 2008 Tallahassee RTMC


Lee County Bridge Incident Lee County Bridge Incident ManagementManagement

July 27, 2004 Lee County Public Works sent letter to FDOT

indicating Lee County’s participation in

SunGuide Software Project

TBD SunGuide Software deployment


C2C ScheduleC2C Schedule

February 16, 2004 SunGuideSM and C2C Project Team completed Interface Control

Document(ICD)

February 20, 2004 SunGuideSM and C2C Project Coordination Teleconference

March 9, 2004 SunGuideSM & C2C Project Coordination Meeting

1st Quarter 2006 C2C deployment among Districts 4, 6,and Turnpike


AgendaAgenda

Time Item Lead








9:25 – 9:30 Break

9:30 – 11:10






Project Web SiteProject Web Site

http://sunguide.datasys.swri.edu


Release-Oriented Release-Oriented Development ApproachDevelopment Approach


Status of Release 1.1Status of Release 1.1

Software deployed in District 4

Issues that have occurred:– Patch 4 has been released and installed to address several bugs

and operational improvements requested– Meeting on October 11, 2005 to discuss additional enhancements

to messaging requirements– Vicon CCTV issue (being worked by Vicon with SwRI input)

Milestone Demonstration:– SunGuide R1.1 (Patch 4) was installed and demonstrated in

Miami, included:• DMS• CCTV• TSS• Video Wall


Status of Release 2 ActivitiesStatus of Release 2 Activities

Ramp Metering:– Complete:

• Subsystem• Drivers:

– TSS driver complete– RM driver complete

• GUI

– Undergoing integration testing in San Antonio

– Issues:• Deployment timing (to occur in 2006):

– Training– Software support


Status of Release 2 Activities: Status of Release 2 Activities: continuedcontinued

Emergency Evacuation:– Design initiated– Development initiated– SwRI has determined that a number of existing web sites

provide what was asked for in the SunGuide requirements– SwRI has been provided with “Evacuation Zone” shape

files– SwRI is progressing along developing a web site with

links to available web site

– FDOT Change requested: discussed later in the presentation



Emergency Evacuation:– Complete (based on FDOT’s approval of requirement

modifications)

Data Archive:– Complete– Integration testing

Web Server:– Complete– “C2C Powered”



Center-to-Center:– Complete– Integration testing– Testing labs:

• D4 deployment• D6 deployment

– Note: FDOT has recommended additional requirements that will be part of Release 2.1 (or greater) – discussion about the requirements will occur later



HAR:– Complete– Integration Testing

Trailblazer– Complete– Integration Testing– Need to test with a unit in

the field (potential “crc” issue)

Safety Barrier– Complete– Integration Testing



Inventory and Maintenance (IMS):– Complete– Integration Testing


Deliverable StatusDeliverable Status

SwRI waiting for FDOT comments:– None critical

Future documents to be provided by SwRI:– Updated testing documents:

• SIP• SICP

– Updated development documents:• SDD• SUM• VDD

All documents delivered to FDOTare available on the project web site.

http://SunGuide.datasys.swri.edu


Cost Status (as of 9/30/05)Cost Status (as of 9/30/05)Note: numbers approximate due to end of FYNote: numbers approximate due to end of FY

Release 1:– Allocated: $4,335,554– Spent: $4,316,560

Release 2:– Allocated: $2,732,303 (includes Travel Time)– Spent: $2,068,527

Deployments:– Allocated: $282,303– Spent: $76,798

Support - on-site support and FDOT directed support (thru 6/2008):– Allocated: $548,219– Spent: $175,045


Spending Curves Spending Curves (only funds approved through June 2006)(only funds approved through June 2006)


Schedule StatusSchedule Status

Current areas of concern:– Documents:

• None– Software:

• Ramp Meter is significantly over-budget– Contractual:

• ECO is in the process of being developed (authorizes 24x7 support and Travel Time subsystem)

– Release 2.0:• FAT• Deployment

To be scheduled:– Trailblazer testing (during deployment)– Ramp Metering testing (early 2006)


Schedule Status - continuedSchedule Status - continuedCurrent Reporting PeriodCurrent Reporting Period


24x7 Support24x7 Support

SwRI will utilize professional staff– Hector Imuguez– Brent Becker– SunGuide developers

Process:– A “SunGuide” number will be provided– Either SwRI staff or answering service will answer– Issues tracked using “Footprints”

• Web based issue tracking, allows:– FDOT review of issues– FDOT submittal of issues

• Web based FAQ


Events to Be Scheduled/ConfirmedEvents to Be Scheduled/Confirmed

Future status meetings that need to be confirmed:– November status meeting will occur during FAT

Testing:– Release 2 FAT: November 1st, 2nd and 3rd

Milestone Demonstrations:

– Milestone Demo #3: D4, D6 and MDX Functionality of C2C, CCTV and DMS to be demonstrated


AgendaAgenda

Time Item Lead








9:25 – 9:30 Break

9:30 – 11:10






District 2 Deployment StatusDistrict 2 Deployment Status

D2 Servers (Dell) provided to SwRI:– Database loaded and configured– Applications loaded and configured– Extensive “stress testing” of 125+ TSS sensors– American Dynamics (AD) CCTV: protocol problem that

had to be resolved by AD Installation:

– Started week of October 3rd

– CCTVs must be retrofited– DMS devices with IDI translators to be re-configured

Training:– October 5th and 6th


AgendaAgenda

Time Item Lead








9:25 – 9:30 Break

9:30 – 11:10






Next Three MonthsNext Three Months

October 2005– All release 2.0 development is complete:

• Design• Code• Unit Test

– Integration testing– Initiate 24x7 support

November:– FAT (Nov 1-3)– D6 Install / Training– Final R2.0 cleanup

December– Future enhancments


AgendaAgenda

Time Item Lead








9:25 – 9:30 Break

9:30 – 11:10






C2C RequirementsC2C Requirements

Discussed in previous status meetings:– C2C #1: The CCTV switching function shall support the

switching of C2C video sources to a Barco Video Wall.

– C2C #2: SunGuide shall provide a mechanism to include DMS devices from available from the C2C interface when generating a IM response plan.

– C2C #3: When SunGuide receives a DMS request from another center a configurable parameter shall be provided as to whether or not an operator has to approve the posting of the DMS request to the MAS subsystem.

– C2C #4: Device requests received via the C2C interface shall be validated


New C2C Functionality New C2C Functionality ImplicationsImplications

Barco Wall viewing:

– No SunGuide software implication

– Configuration of wall (the SunGuide software retrieves the configuration for display to the operator)


New C2C Functionality New C2C Functionality Implications – con’tImplications – con’t

DMS Devices from other centers:– Link Editor:

• Retrieve C2C devices (aka remote devices)• Allow users to select either local or remote devices

– IM:• Need to subscribe for C2C DMS and HAR devices• When traversing a “device link tree” will need to check

status of local and remote devices (if remote is not available, skip the node but do NOT stop traversing the link tree)

• Commands will need to be sent to either MAS (if local devices) or to C2C (if remote devices) when the following occur:– Plan execution– Plan modification (see issue below)– Plan termination

– GUI:• Need to be able to distinguish between local and remote

devices when a response plan is displayed


New C2C Functionality New C2C Functionality Implications – con’tImplications – con’t

Prompt option for remote centers:– Startup up option that will require C2C DMS/HAR

requests (received from other centers) to be “manually” approved

– Sample screen (design not finalized):


Road Ranger RequirementsRoad Ranger Requirements

Requirements derived from “Road Ranger Procedure Draft Version 6”, Traffic Operations

Driven by statewide data collection requirements

Does not address data collection mechanism

Interface is at computer-to-computer level


Road Ranger Subsystem ConceptRoad Ranger Subsystem Concept

D4 SMARTsoftware

Wireless data receiver

SunGuide Software C2C

reports

Data warehouseStat OfficesOthers

Road Ranger ICD (XML Schema)


Road Ranger Data RequirementsRoad Ranger Data Requirements

TM001D SunGuide shall acquire and store the following data that is collected at the beginning of the Road Ranger Service Patrol Vehicle Operator's shift:A. DateB. Shift start timeC. Operator nameD. Truck numberE. RouteF. Beginning vehicle mileage

This data shall be available to support the generation of reports concerning Road Ranger operations.

Traceability:A001->S006->TM001->TM001D



TM002D The following data collected at each stop shall be stored by SunGuide and made available for report generation and reviewing through the SunGuide GUI:

A. Dispatch timeB. Arrival timeC. License numberD. StateE. Vehicle typeF. Direction of travel (NB, SB, EB, WB)G. Mile markerH. How discoveredI. Lanes/Shoulder blockedJ. Cause for stopK. Services providedL. Depart timeM. Comment card (Y/N)

Traceability:A001->S006->TM001->TM002D



TM002D1 The following data collected about the vehicle type at each stop shall be stored and linked to the road ranger report containing the data:

a. Passengerb. Pickup or vanc. RV or busd. Single-unit trucke. Tractor trailerf. Motorcycleg. N/A

Traceability: A001->S006->TM001->TM002D->TM002D1



TM002D2 The following data collected by the Road Ranger about how it was discovered at each stop shall be stored and linked to the road ranger report containing the data:

a. Drive upb. Saw and changed routec. Road Ranger dispatchd. Notified by other Road Ranger operator/supervisore. FHP dispatch/officerf. Other




TM002D3 The following data collected about the cause for the stop shall be stored and linked to the road ranger report containing the data:a Accident (crash)b. Vehicle fire c. Disabledd. Abandonede. Debrisf. Pedestriang. Other




TM002D4The following data collected about what services were provided at each stop shall be stored and linked to the road ranger report containing the data:a. Extinguish fireb. First aidc. Absorbentd. Remove debrise. Relocate (to safer location)(> 250 feet) f. Tireg. Fuelh. Fluidsi. Mechanicalj. Jump startk. Called wreckerl. Secure loadm. Mobile phone calln. Directionso. Transportedp. Unable to locateq. Blocked lane/traffic controlr. Tagged abandoned vehicles. Relocate vehicle from travel lane (< 250 feet)t. Notify FDOT for road repairu. Other - describev. No service - occupiedw. No service - abandoned




TM002D5 The following data collected at the end of each road ranger shall be stored by SunGuide and linked to the road ranger reporting the data.

A. Shift end timeB. Ending vehicle mileage


TM003D The road ranger operator data shall be collected monthly and be able to be exported to Microsoft Excel or other compatible format.

Traceability: A001->S006->TM001->TM003D



TM004D SunGuide shall support the compilation and report generation quarterly.


TM005D SunGuide shall store the road ranger data for a minimum of 12 months and have it available for review and report generation within 120 seconds of when a specific piece of data is requested.




TM006D SunGuide shall interface with and be able to download road ranger data collected by road rangers using a portable device. The data shall be exported from the portable device in comma delimitated text format (CSV) as a flat file and transfer shall be through a serial RS-232 interface.



Toll Tag Reader requirementsToll Tag Reader requirements

Derived from:Derived from:

ODSI-SRS-1.2Software Requirements SpecificationVersion 1.2December 7, 2004

ORLANDO-ORANGE COUNTY EXPRESSWAY AUTHORITY525 South Magnolia Avenue

Orlando, Florida 32801-4414



TM018SunGuide shall accept data from toll tag readers and use that data to calculate the elapsed time of travel between the geographic location where the tag was initially read and the geographic location where the tag was read again.

TM001S Processing associated with collection, fusion, and dissemination of real-time toll tag data feeds shall introduce a latency of no more than two (2) minutes.

TM002S SunGuide shall allow users to perform system configuration activities without introducing latency greater than 2 minutes in the real-time processing of the toll tag with the exception of the addition, removal, or modifications to AVI collection



TM003S The Toll Tag reader function shall be operational 99.9% the time, measured annually.

TM003S1 Operational shall be defined as that the system is running and that no internal errors have occurred.

TM004S The Toll Tag reader function shall report and archive speed and travel time calculations to three decimal places of precision.



TM005S The Toll Tag reader function shall include an AVI data collection function.

TM005S1 The AVI data collection system shall be able to process AVI Tag data from Amtech Type II and Type III AVI tags, including "E-PASS", “OPASS”, "SunPass", and “LeeWay” AVI Tags.

TM005S2 The AVI data collection system shall receive AVI Tag data from the toll collection agency AVI Data Collection Sensors, or alternatively poll the Data Collection Sensors.

TM005S3 Users shall be able to add AVI Data Collection Sensors to the SunGuide system. Changes will take effect when the system is restarted.

TM005S4 Users shall be able to modify AVI Data Collection Sensors that have already been added to the SunGuide system. Changes will take effect when the system is restarted.

TM005S5 The SunGuide system shall interface with Data Collection modules using a standardized interface that is documented and approved by FDOT.



TM005S6 Raw AVI data collected by SunGuide shall include the following:

– Transponder ID - unique AVI tag identifier,– Reader ID - Data collection sensor that made– the tag read,– Lane ID - lane in which the tag was read,– Time stamp - time when the tag was read,– Fault Information - fault information from the– data source.

TM006S The SunGuide system shall gather external AVI collection device status data.

TM006S1 The SunGuide system shall determine the status of the Toll Collection Agency’s AVI Data Collection Sensors.

TM006S2 The AVI data collection system shall report errors in AVI Data Collection Sensors.



TM007S SunGuide shall ensure that toll tag customers remain anonymous in the system.

TM007S1 The SunGuide system shall encrypt AVI transponder IDs.

TM008S The Data Server shall filter out duplicate tag reads (i.e. reads of the same AVI transponder, at the same data collection site, in a given time.)

TM009S SunGuide shall archive AVI Tag read data.

TM009S1 AVI Tag read data shall be archived with encrypted transponder IDs.

TM009S2 Raw AVI Tag read data shall be archived in the same format in which it was received, except that the transponder ID shall be encrypted.


Performance Measures Performance Measures RequirementsRequirements

Waiting on FDOT to define


AgendaAgenda

Time Item Lead








9:25 – 9:30 Break

9:30 – 11:10





Video sharing Video sharing over the over the

ITS WAN for C2C ITS WAN for C2C CommunicationsCommunications

Nick Adams - Central OfficeJim Mosser - PB Farradyne

Status of the scope Status of the scope modification to modification to

accomplish video accomplish video sharing?sharing?

Viewing other center’s videoViewing other center’s video

Districts will view other center’s video on their video wall via the Barco controller and Universal Decoder.

No Trans-coding equipment required and video will be sent in “native format” (Originating District vendor/MPEG 2 or 4) Video will be decoded by the Barco Universal Decoder.

SunGuide scope change required as mentioned above.

Hardware vs. Software Hardware vs. Software DecodingDecoding

SunGuide will route video to the Barco controller to be decoded by the Universal Decoder.

If software decoding takes place at the Districts, it will occur outside SunGuide

C2C Video(MPEG-2 or 4)

SunGuide C2CControl & data

(XML)

(Fiber or Microwave)

ITS WAN FW & SW: ITS WAN Firewall & Switch

C2C Video MPEG-2 or 4

Legend:

SunGuide Control Data

District VideoMPEG-2 or MPEG-4

Analog video

D: Decoder

E: Encoder

(A): Center A Type or Vendor Equipment

(B): Center B Type or Vendor Equipment

Center B Equipment

...

...SunGuide

ITS WANFW & SW

Monitor D(B)MPEG-2

DistrictSwitch

...

CCTVE(B)MPEG-2

CCTVE(B)MPEG-2

...

VideoWall

D(U)

CCTVE(B)MPEG-4

CCTVE(B)MPEG-4

... ...

Center A Equipment

... ...SunGuide

ITS WANFW & SW

MonitorD(A)MPEG-2

DistrictSwitch

...

CCTV E(A)MPEG-2

CCTV E(A)MPEG-2

...

VideoWall

D(U)

CCTV E(A)MPEG-4

CCTV E(A)MPEG-4

...... D(A)MPEG-2Monitor

D(A)MPEG-4Monitor

D(B)MPEG-2Monitor

D(B)MPEG-4Monitor

C2C Video Sharingwithout Trans-coding

Sunrise

Tall’eeFHP

ITSTest-bed

Microwave fromTallahassee FHP

to Turnpike fiber atSunrise (McArthur)

TurnpikePompano

CCTV CCTV CCTV

Workstations

Ethernet

Video Wall

Barco UD

Workstations

Ethernet

Video Wall

Barco UD

Eh(???)

C2C fiber in District 4 cablealong Commercial Blvdthen I-95 and District 6

cable along I-95 & SR 836

C2C fiber inDistrict 4 cable

along I-595

C2C fiber inTurnpike cablealong Turnpike

ITS WAN South Florida Deployment

CCTV CCTV CCTV

Workstations

Ethernet

Video Wall

Barco UDITS WAN Eq’t

District 6

C2C fiber inDistrict 6 cablealong SR 836

District 4CCTVCCTVCCTV

Workstations

Ethernet

Video Wall

Barco UD

ITS WAN Eq’t

CCTVCCTVCCTV

Eh(???)

Ds(iMPath)

Eh(iMPath) Eh(iMPath)

Eh(iMPath) Eh(iMPath) Eh(iMPath)

Ds(iMPath)

Ds(iMPath)Ds(iMPath)Dh(Vbrick) Dh(Vbrick)

Eh(Vbrick) Eh(Vbrick)Eh(Vbrick)

ITS WAN Eq’t

Eh(iMPath)

ITS WAN Management

ITS WAN Eq’t

Eh(???)

Dh(???) Ds(???)

(LeasedMAN)

Eh(iMPath) Ds(VBrick)Encoder hardware Decoder software

Ledgend

Video for the State EOCVideo for the State EOC8/19/05 meeting8/19/05 meeting

Short term goal = “Webserver Video”

Snap shots from web-servers as provided by SunGuide (or streaming video provided by District Webserver facilities)

Long term goal = “Full Motion Video”

EOC to look into MAN link to fiber part of ITS WAN. CO to look into “SunGuide without devices” solution.

QUESTIONS?QUESTIONS?

Nick Adams – Central Office(850) 410-5608 or

[email protected]

Jim Mosser - PB Farradyne 754-224-6966 or [email protected]


AgendaAgenda

Time Item Lead








9:25 – 9:30 Break

9:30 – 11:10



