Sun Guide SM Software Development Project Status Meeting

Sun. Guide. SM Software Development Project Status Meeting November 9, 2004 Sun. Guide Status Meeting 1

Agenda Time Item 10: 00 – 10: 05 Introductions 10: 05 – 10: 10 License Updates: - Tx. DOT and FDOT - Trans. Guide - WSDOT TOU Lead Liang Hsia - MDX JPA - GDT - Sw. RI/FDOT Modification Liang Hsia 10: 10 – 10: 20 TMC and Software Deployment Schedule Updates D 1 D 2 D 3 D 4 D 5 D 6 D 7 MDX Turnpike Enterprise 10: 20 – 10: 50 Project Status Report Steve Dellenback 10: 50 – 11: 00 Sun. Guide. SM and TIM Coordination Meeting Briefing Liang Hsia 11: 00 – 11: 10 Sun. Guide. SM Training Steve Dellenback 11: 10 – 11: 20 Canoga Micro Loops Steve Dellenback 11: 20 – 11: 35 Sun. Guide. SM Demonstration and/or Screen Review Robert Heller 11: 35– 11: 40 Open Discussion / Action Item Summary All Sun. Guide Status Meeting November 9, 2004 2

Introductions Sun. Guide Status Meeting November 9, 2004 3

Agenda Time Item 10: 00 – 10: 05 Introductions 10: 05 – 10: 10 License Updates: - Tx. DOT and FDOT - Trans. Guide - WSDOT TOU Lead Liang Hsia - MDX JPA - GDT - Sw. RI/FDOT Modification Liang Hsia 10: 10 – 10: 20 TMC and Software Deployment Schedule Updates D 1 D 2 D 3 D 4 D 5 D 6 D 7 MDX Turnpike Enterprise 10: 20 – 10: 50 Project Status Report Steve Dellenback 10: 50 – 11: 00 Sun. Guide. SM and TIM Coordination Meeting Briefing Liang Hsia 11: 00 – 11: 10 Sun. Guide. SM Training Steve Dellenback 11: 10 – 11: 20 Canoga Micro Loops Steve Dellenback 11: 20 – 11: 35 Sun. Guide. SM Demonstration and/or Screen Review Robert Heller 11: 35– 11: 40 Open Discussion / Action Item Summary All Sun. Guide Status Meeting November 9, 2004 4

License Updates l Sw. RI / FDOT Sublicense – License executed on August 29, 2003 before the contract started. – License updated on September 5, 2003 covering distribution source code to other Florida governmental entities. – Tx. DOT informed Sw. RI on January 22, 2004 that Trans. Guide software was on “hold”. – License amended on April 12, 2004 (to support District 2 and name change) Sun. Guide Status Meeting November 9, 2004 5

License Updates l For a FDOT / Tx. DOT partnership to occur two things are needed: – MOU and License: • FDOT provided Tx. DOT with comments and legal opinion on March 2, 2004 • Tx. DOT provided FDOT with draft MOU and License on March 16, 2004 • FDOT forwarded draft MOU & License to Tx. DOT on October 18, 2004 – Tx. DOT Software License (solves Trans. Guide license issue) • Tx. DOT provided FDOT with a license on June 30, 2004 (included previous FDOT requests for content). • FDOT signed license on August 10, 2004. • Tx. DOT acknowledged the receiving of the FDOT signed license on August 23, 2004. • Tx. DOT signed license on August 30, 2004 and sent to FDOT on September 20, 2003. • FDOT Requested Trans. Guide software on October 4, 2004. • FDOT Received Trans. Guide software on October 19, 2004. Sun. Guide Status Meeting November 9, 2004 6

License Updates - continued l 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. Sun. Guide Status Meeting November 9, 2004 7

License Updates - continued l 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 Sun. Guide Status Meeting November 9, 2004 8

License Updates - continued l Sw. RI / FDOT / Lee County Sublicense – Lee County provided FDOT with official letter for participation on July 27, 2004 – FDOT and Sw. RI started documentation preparation on July 30, 2004 – Sw. RI provided FDOT with draft language on September 10, 2004 – FDOT forwarded sublicense to Lee County on October 26, 2004 l FDOT issued i. Florida Data Collection Process (DCP) notice to proceed on September 8, 2004. l GDT 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 Sun. Guide Status Meeting November 9, 2004 9

Agenda Time Item 10: 00 – 10: 05 Introductions 10: 05 – 10: 10 License Updates: - Tx. DOT and FDOT - Trans. Guide - WSDOT TOU Lead Liang Hsia - MDX JPA - GDT - Sw. RI/FDOT Modification Liang Hsia 10: 10 – 10: 20 TMC and Software Deployment Schedule Updates D 1 D 2 D 3 D 4 D 5 D 6 D 7 MDX Turnpike Enterprise 10: 20 – 10: 50 Project Status Report Steve Dellenback 10: 50 – 11: 00 Sun. Guide. SM and TIM Coordination Meeting Briefing Liang Hsia 11: 00 – 11: 10 Sun. Guide. SM Training Steve Dellenback 11: 10 – 11: 20 Canoga Micro Loops Steve Dellenback 11: 20 – 11: 35 Sun. Guide. SM Demonstration and/or Screen Review Robert Heller 11: 35– 11: 40 Open Discussion / Action Item Summary All Sun. Guide Status Meeting November 9, 2004 10

Reports by Deployment and Possible Integration Schedule l District 4 l District 6 l MDX l District 7 l District 1 l District 2 l District 5 l District 3 l Turnpike Enterprise Sun. Guide Status Meeting November 9, 2004 11

District 4 Schedule l September 2004 District 4 moves equipment to new TMC l October 12, 2004 Sun. Guide. SM Software Team performs Milestone Demonstration l December 2004 Sun. Guide. SM Software Team provides TMC operators with software training l January 2005 Sun. Guide. SM Software Team sets up the District 4 software Sun. Guide Status Meeting November 9, 2004 12

District 4 Milestone Demonstration Sun. Guide Status Meeting November 9, 2004 13

District 4 Schedule l December 2004 I 95/I 595 Video Monitoring Project Starts. l January 2005 District 4 TMC Grand Opening. January 2005 Complete I 95/I 595 Video Monitoring and Detector System l Sun. Guide Status Meeting November 9, 2004 14

District 6 RTMC Sun. Guide Status Meeting November 9, 2004 15

District 6 Schedule l June 25, 2004 l April 2005 Ramp metering subsystem to be and tested l June 2005 Sun. Guide. SM Software Release 2 includes Ramp metering system l July 2005 Sun. Guide Status Meeting New TMC Grand Opening installed deployment I-95 Package B project completion November 9, 2004 16

MDX Schedule l April 7, 2003 MDX sent letter to ITS Office about participating in Sun. Guide. SM Project l April 25, 2003 FDOT Responded, Welcoming MDX’s participation l December 3, 2003 FDOT provided MDX with a draft Joint Program Agreement l June 2005 Sun. Guide. SM Software Release 2 deployment at MDX l October 2005 MDX TMC Operational Sun. Guide Status Meeting November 9, 2004 17

District 7 RTMC November 2005 April 2006 Sun. Guide Status Meeting Building Construction Finish Sun. Guide. SM Software Deployment November 9, 2004 18

District 2 RTMC FY 2004 FY 2006 Sun. Guide Status Meeting I-95 N ITS Improvement Sun. Guide. SM Deployment (Tentative) November 9, 2004 19

District 5 RTMC FY 2004 September 8, 2004 December 2005 FY 2004 -2005 Sun. Guide Status Meeting Orlando RTMC retrofit and upgrade i. Florida Data Collection Process i. Florida C 2 C between Districts 2 and 5 November 9, 2004 20

Turnpike RTMC Sun. Guide Status Meeting November 9, 2004 21

Turnpike Schedule l March 2004 Sun. Nav 1. 1 Test l April 2004 Sun. Nav 1. 2 Development l June 2005 Observe D 4, D 6, & MDX C 2 C Deployment Sun. Guide Status Meeting November 9, 2004 22

District 1 May 2005 December 2006 FY 2011 (2005) Sun. Guide Status Meeting I-75 Safety Barrier System upgrade Sun. Guide. SM Deployment at Ft. Myers RTMC Sarasota RTMC November 9, 2004 23

District 3 FY 2007 Pensacola RTMC FY 2008 Tallahassee RTMC Sun. Guide Status Meeting November 9, 2004 24

Lee County Bridge Incident Management July 27, 2004 Lee County Public Works will participate in Sun. Guide Software Sun. Guide Status Meeting November 9, 2004 25

C 2 C Schedule l February 16, 2004 Sun. Guide. SM and C 2 C Project Team completed Interface Control Document (ICD) l February 20, 2004 Sun. Guide. SM and C 2 C Project Coordination Teleconference l March 9, 2004 Sun. Guide. SM & C 2 C Project Coordination Meeting l June, 2005 C 2 C deployment among Districts 4, 6, and MDX Sun. Guide Status Meeting November 9, 2004 26

Agenda Time Item 10: 00 – 10: 05 Introductions 10: 05 – 10: 10 License Updates: - Tx. DOT and FDOT - Trans. Guide - WSDOT TOU Lead Liang Hsia - MDX JPA - GDT - Sw. RI/FDOT Modification Liang Hsia 10: 10 – 10: 20 TMC and Software Deployment Schedule Updates D 1 D 2 D 3 D 4 D 5 D 6 D 7 MDX Turnpike Enterprise 10: 20 – 10: 50 Project Status Report Steve Dellenback 10: 50 – 11: 00 Sun. Guide. SM and TIM Coordination Meeting Briefing Liang Hsia 11: 00 – 11: 10 Sun. Guide. SM Training Steve Dellenback 11: 10 – 11: 20 Canoga Micro Loops Steve Dellenback 11: 20 – 11: 35 Sun. Guide. SM Demonstration and/or Screen Review Robert Heller 11: 35– 11: 40 Open Discussion / Action Item Summary All Sun. Guide Status Meeting November 9, 2004 27

Project Web Site http: //sunguide. datasys. swri. edu Sun. Guide Status Meeting November 9, 2004 28

Release-Oriented Development Approac Sun. Guide Status Meeting November 9, 2004 29

Status of Release 1 Activities l Project Management: – PM / Meetings / Reviews – Process documents – Interface Control Documents (ICDs) l Core software framework: – Database – User administration – Executive handler – Status logger – User interface – Map – Data Bus l DMS: – General Subsystem – NTCIP Florida MIB driver – Mark IV version 2. 5 driver Sun. Guide Status Meeting November 9, 2004 30

Status of Release 1 Activities continued l CCTV Control: – General Subsystem – NTCIP 1205 driver l Video Switching – General Subsystem – IP Video switching driver l Video Wall – General Subsystem – Barco/Argus video wall driver l Traffic Detection, driver for: – General Subsystem – Bitrans B 238 -I 4 driver – RTMS (EIS and Wavetronix) driver Sun. Guide Status Meeting November 9, 2004 31

Status of Release 1 Activities continued l Incident Management: – GUI – Subsystem – TIM coordination l Training: – Training Plan – Classes being adjusted – Material being developed l Testing – Integration testing – Document development l Documents: – Software User’s Manual (SUM – Version Description Document (VDD) – Software Design Document (SDD) Sun. Guide Status Meeting November 9, 2004 32

Status of Release 2 Activities l l HAR – Requirements refined – Design initiated l l Emergency Evacuation: – Requirements refined and provided to FDOT – Design initiated Center-to-Center – Requirements refined – Design initiated l Data Archive – Requirements refined – Design initiated RWIS – Requirements refined – Design initiated l Inventory and Maintenance – Requirements to be refined l Optional Service: – i. Florida Data Collection Process (DCP) Ramp Metering: – Design activities initiated – Initial GUI design completed – High level design completed Web Server – Requirements refined – Design initiated Sun. Guide Status Meeting November 9, 2004 33

Development Activity Software development for Release 1 is complete l Current Release 1 activities: – Integration Testing – System Testing – Endurance Testing – Documentation (ICDs and SDD) l l Release 2 activities: – Design – Prototyping (preview in the December meeting) – Coding to start soon Sun. Guide Status Meeting November 9, 2004 34

Development Schedule l For the last 12 months: – Factory Acceptance Testing in San Antonio on November 17 -19, 2004 – Deployment in District 4 on December 2, 2004 l Recent developments: – District 4 ready to deploy late January, early February 2005 – Additional review time for testing documents – FDOT’s request to add District 4 DMS Message rules to the Incident Management Subsystem PRIOR to Release 1 testing l New Schedule: – Factory Acceptance Testing in San Antonio on January 1012, 2005 – Deployment in District 4 on January 24, 2004 Sun. Guide Status Meeting November 9, 2004 35

Deliverable Status l Sw. RI waiting for FDOT comments: – Concept of Operations – Version Description Document l Future documents to be provided by Sw. RI: – Software Integration Case Procedures (final version) – Software User’s Manual (draft and final version) – Software Design Document (final version) – District 4 Deployment Plan (draft and final version) All documents delivered to FDOT are available on the project web site. http: //Sun. Guide. datasys. swri. edu Sun. Guide Status Meeting November 9, 2004 36

Cost Status l Release 1: – Budget amount: $3, 863, 374 – As of 9/24/04, ~$3, 257, 000 has been expended l Release 2: – Budget amount: $2, 568, 339 – As of 9/24/04, ~$254, 000 has been expended l Adjustments: – Reductions (funds back to FDOT): • Eliminating DTS Efforts: $75, 009. 71 • Combining 2 a and 2 b: $66, 827. 29 (this includes a “training adjustment” to add classes) – Additions: • i. Florida DCP Task: $64, 531. 00 • Distinct 4 Message Rules: $30, 854. 32 Sun. Guide Status Meeting November 9, 2004 37

Spending Curve Sun. Guide Status Meeting November 9, 2004 38

Schedule Status l Current areas of concern: – Documents: • None – Software: • None Sun. Guide Status Meeting November 9, 2004 39

Schedule Status – continued Last Reporting Period Sun. Guide Status Meeting November 9, 2004 40

Schedule Status - continued Current Reporting Period Sun. Guide Status Meeting November 9, 2004 41

Functional Threads Sun. Guide Status Meeting November 9, 2004 42

Schedule Status - continued l Integration/Testing: – Proceeding well – Continuing long term “endurance” testing l “Factory” Acceptance Testing: – Tentatively January 10 -12 in San Antonio l Future status meetings that need to be scheduled: – December 8, 2004 (“short” meeting in Jacksonville) l Future reviews that need to be scheduled: – Release 2 Software Design Review: sometime early 2005, will be held once other Release 1 and Release 2 enhancement requests are complete Sun. Guide Status Meeting November 9, 2004 43

Agenda Time Item 10: 00 – 10: 05 Introductions 10: 05 – 10: 10 License Updates: - Tx. DOT and FDOT - Trans. Guide - WSDOT TOU Lead Liang Hsia - MDX JPA - GDT - Sw. RI/FDOT Modification Liang Hsia 10: 10 – 10: 20 TMC and Software Deployment Schedule Updates D 1 D 2 D 3 D 4 D 5 D 6 D 7 MDX Turnpike Enterprise 10: 20 – 10: 50 Project Status Report Steve Dellenback 10: 50 – 11: 00 Sun. Guide. SM and TIM Coordination Meeting Briefing Liang Hsia 11: 00 – 11: 10 Sun. Guide. SM Training Steve Dellenback 11: 10 – 11: 20 Canoga Micro Loops Steve Dellenback 11: 20 – 11: 35 Sun. Guide. SM Demonstration and/or Screen Review Robert Heller 11: 35– 11: 40 Open Discussion / Action Item Summary All Sun. Guide Status Meeting November 9, 2004 44

TIM Coordination Meeting l Meeting: – Held: Thursday, October 22, 2004 – Where: Orlando RTMC l Attendees: – Mike Akridge, FDOT – Elizabeth Mc. Crary, FDOT – Liang Hsia, FDOT – Dong Chen, FDOT – Steve Corbin, FDOT – Denny Pedrick, FDOT – James Bitting, FDOT – Kendra Blackforce, TPK – Ranzy Whiticker, TPK – Mike Meincke, TPK – Mike Washburn, TPK Sun. Guide Status Meeting November 9, 2004 – – – – – Nelson Figueroa, FDOT Larry Rivera, FDOT Paul Dixon, FHP Mark Roberts, FDOT Brenda Young, FDOT Jennifer Heller, FDOT Robert Heller, Sw. RI Bret Sadler, Sw. RI Walt Townsend, ITS-Siemens Charles Wallace, PBF 45

TIM Coordination Meeting: Capability for Consideration l Link to Computer Aided Dispatch (CAD) system, which is a standard, statewide system. Sun. Guide. SM has a C 2 C capability through which CAD data could be transmitted but logic would need to be added when received in Sun. Guide. SM. l Some districts have adopted three levels of incidents based on both severity (length) of the incident and lane closures. This was not in the IM requirements per se (there are three “levels”: Minor, Moderate and Severe that are functions of user-defined percentages of lanes blocked). The new MUTCD uses three levels based on time (which are similar to Florida’s time-based criteria. The conclusion was that the definition of incident severity (and their labels) should be user configurable, and that the history of an incident’s evolution should be fully reproducible. (Note: there must be some commonalities in order to report and measure performance at a statewide level. ) l District 4 has proposed a standard template for DMS messages that is being implemented in Sun. Guide. SM. Sun. Guide Status Meeting November 9, 2004 46

TIM Coordination Meeting: Capability for Consideration – con’t l The software should associate a lane configuration with each TSS link on the map. When the operator clicks on a link to create an incident, automatically pre-select the lane configuration associated with that link. (Currently, when an operator creates an incident, they must manually choose a lane configuration for the location associated with the incident. ) l In the message sign control GUI, add a way to bring up a camera that can see the sign, in order to confirm message activation. l When logging incident data, include TSS data so that “end of congestion” time can be tracked as well as closure of incidents. l The TIM group suggested identifying incident data by region (rural and urban), route, number of accidents, time to clear and recover from incidents, vehicle types, and highest location of incidents. The TIM Group needs to refine these requirements, including explicit reporting requirements. Sun. Guide Status Meeting November 9, 2004 47

TIM Coordination Meeting: Capability for Consideration – con’t l It was suggested that incidents should identify types of vehicles involved in the incident (CV/auto, auto/auto, CV/CV, multiple vehicles of all types, etc. ). l Sun. Guide. SM needs to include the statewide TIM performance measures currently being researched. l Sun. Guide. SM ‘s geo-location system is based entirely on lat-long. It will be important to add mile marker locations, particularly in view of a possible deployment of location reference markers extensively throughout the state. This process needs to be automated. Also, freeway cross streets are common reference points, so a quicker way for operators to locate them is desirable. Similarly, it needs to be determined whether it is necessary to include the link-node system. l Sun. Guide. SM has a flag to indicate that a hazardous material is involved in the incident, but the type of material is not captured. A set of HAZMAT categories at least, or actual chemicals at most, should be added. Sun. Guide Status Meeting November 9, 2004 48

TIM Coordination Meeting: Capability for Consideration – con’t l It is further suggested that other data, such as ambient lighting, be added. The TIM Program will need to specify all such data that are not currently being captured. l The contacts list currently has to be created for each incident. The capability to have contact groups should be added, and incidents should be able to have pre-designated groups to notify, by severity level and perhaps even other criteria. (Note: these pre-designated groups would be a minimum given the incident. ) l Dispatching of Road Rangers should be automated in the software. l The use of PDAs for Road Ranger logging needs to be recognized and the ability to upload these data be added. l Consider changing the DMS editor to allow selecting multiple signs to update with the same message, dragging one sign into another to copy text, etc. Also, when adding a sign to an incident response plan midstream, allow its proposed message to be populated automatically. l Add Incident Management reporting capabilities. Districts are to submit examples of their desired reports. Sun. Guide Status Meeting November 9, 2004 49

Agenda Time Item 10: 00 – 10: 05 Introductions 10: 05 – 10: 10 License Updates: - Tx. DOT and FDOT - Trans. Guide - WSDOT TOU Lead Liang Hsia - MDX JPA - GDT - Sw. RI/FDOT Modification Liang Hsia 10: 10 – 10: 20 TMC and Software Deployment Schedule Updates D 1 D 2 D 3 D 4 D 5 D 6 D 7 MDX Turnpike Enterprise 10: 20 – 10: 50 Project Status Report Steve Dellenback 10: 50 – 11: 00 Sun. Guide. SM and TIM Coordination Meeting Briefing Liang Hsia 11: 00 – 11: 10 Sun. Guide. SM Training Steve Dellenback 11: 10 – 11: 20 Canoga Micro Loops Steve Dellenback 11: 20 – 11: 35 Sun. Guide. SM Demonstration and/or Screen Review Robert Heller 11: 35– 11: 40 Open Discussion / Action Item Summary All Sun. Guide Status Meeting November 9, 2004 50

Hands-On Training l On November 5, 2004 Sw. RI received the following comment: – Section 2. 1. 9 – Page 6: It states that this is not a hands on Training Course. This needs to be so the operators will get a feel and fully understand how to operate the system. l Sw. RI’s Position: – Sw. RI received request for hands-on training. – Sw. RI had planned on having a laptop version of the software for the instructor to use. – Happy to alter the training for hands-on. – Problem is hardware. Will the Districts have a test environment with field equipment to support training? l Discussion? Sun. Guide Status Meeting November 9, 2004 51

Agenda Time Item 10: 00 – 10: 05 Introductions 10: 05 – 10: 10 License Updates: - Tx. DOT and FDOT - Trans. Guide - WSDOT TOU Lead Liang Hsia - MDX JPA - GDT - Sw. RI/FDOT Modification Liang Hsia 10: 10 – 10: 20 TMC and Software Deployment Schedule Updates 10: 20 – 10: 50 Project Status Report 10: 50 – 11: 00 Sun. Guide. SM and TIM Coordination Meeting Briefing Liang Hsia 11: 00 – 11: 10 Sun. Guide. SM Training Steve Dellenback 11: 10 – 11: 20 Canoga Micro Loops Steve Dellenback 11: 20 – 11: 35 Sun. Guide. SM Demonstration and/or Screen Review Robert Heller 11: 35– 11: 40 Open Discussion / Action Item Summary All Sun. Guide Status Meeting November 9, 2004 D 1 D 2 D 3 D 4 D 5 D 6 D 7 MDX Turnpike Enterprise Steve Dellenback 52

Canoga Loop Background l Limitations of older 3 M devices: must poll the device often (essentially every vehicle): – C 822/C 824 – C 922/C 924 (new version of the above) l 3 M has a newer product: – "Traffic Monitoring Card" (numbered as 942/944) – Works in conjunction with the C 922/C 924 – Provides the capability to establish a monitoring interval in the range of 1 second to 15 minutes – Driver can then poll at this interval, the device will provide average speed, occupancy, volume for the specified interval – The device can be polled for the last 300 intervals (i. e. it keeps a history of 300 intervals) or you can request the data for the last 500 vehicles (i. e. it keeps a history of the last 500 vehicle reads) l Same protocol is used for all above devices (some additional messages to support the Traffic Management Card Sun. Guide Status Meeting November 9, 2004 53

Canoga Loop Issues: Discussion Topics l Use of 170 controllers – Sw. RI would recommend using Sun. Guide. SM application servers rather than 170 s if the communications infrastructure supports the protocol bandwidth l Price of Canoga units – How do they compare to RTMS or other devices? l Installation costs – How do they compare to other devices? l Does FDOT want a Canoga driver for Sun. Guide. SM? Sun. Guide Status Meeting November 9, 2004 54

Agenda Time Item 10: 00 – 10: 05 Introductions 10: 05 – 10: 10 License Updates: - Tx. DOT and FDOT - Trans. Guide - WSDOT TOU Lead Liang Hsia - MDX JPA - GDT - Sw. RI/FDOT Modification Liang Hsia 10: 10 – 10: 20 TMC and Software Deployment Schedule Updates D 1 D 2 D 3 D 4 D 5 D 6 D 7 MDX Turnpike Enterprise 10: 20 – 10: 50 Project Status Report Steve Dellenback 10: 50 – 11: 00 Sun. Guide. SM and TIM Coordination Meeting Briefing Liang Hsia 11: 00 – 11: 10 Sun. Guide. SM Training Steve Dellenback 11: 10 – 11: 20 Canoga Micro Loops Steve Dellenback 11: 20 – 11: 35 Sun. Guide. SM Demonstration and/or Screen Review Robert Heller 11: 35– 11: 40 Open Discussion / Action Item Summary All Sun. Guide Status Meeting November 9, 2004 55

See Other Presentation Sun. Guide Status Meeting November 9, 2004 56

Action Item Recap Number Person Action 55 56 57 58 59 60 61 Sun. Guide Status Meeting November 9, 2004 57