quarterly progress report · 2019-08-09 · mitigation identified by columbus, usdot site visit in...

1

Quarterly Progress Report

Award Information

Title Award # Awardee

Smart City Challenge Demonstration

DTFH6116H00013 City of Columbus

Report Information

Date Submitted Submitted To Period Covered by Report

May 18, 2017 Kate Hartman January 2017 - March 2017

Project Scope

Scope Statement

Implementation of the Smart Columbus Smart City Demonstration consisting of 15 projects spread across 2 enabling Technologies and 4 Districts:

1. Columbus Connected Transportation Network (CCTN) 1. Connected Vehicle Environment 2. Smart Street Lighting 3. Transit Pedestrian Collision Avoidance System

2. Integrated Data Exchange (IDE) 4. IDE

3. Residential District 5. Common Payment System 6. Multi-Modal Trip Planning Application 7. Smart Mobility Hubs 8. Mobility Assistance for People with Cognitive Disabilities

4. Commercial District 9. Connected Electric Automated Vehicles

5. Downtown District 10. Delivery Zone Availability 11. Enhanced Permit Parking 12. Event Parking Management

6. Logistics District 13. Truck Platooning 14. Oversize Vehicle Routing 15. Interstate Truck Parking Availability

2

Financial Status

Task Financial Summary (See Note 1)

Note 1: After last quarter’s report we agreed the City’s labor cost would all stay within Program Management. Task 3 was to be broken down by its two components and Task 4 was to be broken down by its four components. We are still working on breaking task 3 and 4 into the components and anticipate reporting expenses that way on the next quarterly report.

Costs Incurred vs Budgeted Costs

Costs Incurred vs Obligated Federal Funding

Direct Labor Hours Worked (See Note 2)

3

Note 2: Some hours were estimated on the last quarterly report. There are no estimated hours on this report. The cumulative hours column was adjusted to reflect actual hours worked to-date, from project start through the end of this quarter.

Budget vs Cost to Date Summary (See Note 3)

Note 3: There is a significant delta between budgeted costs and costs to date. This delta is a result of two factors: an over estimation of how quickly spend on the project would ramp up when the budget estimates were put together in July of 2016; and an assumption that Non-Federal (cost share) spending would constitute 47% of the budgeted spend ($5.9M) in the first year of the project. Cost share spending has been zero to this point.

Costs Incurred by Cost Element (See Note 4)

$0.00

$6,260,272.00

$15,650,680.00

$1,582,076.43$0.00

$10,000,000.00

$20,000,000.00

$30,000,000.00

$40,000,000.00

$50,000,000.00

$60,000,000.00

$70,000,000.00

31-Aug Q4-16 Q1-17 Q2-17 Q3-17 Q4-17

Running Budget

Running Costs

4

Note 4: Some labor hours were estimated in the previous quarterly report. There are no estimated hours in this report. The cumulative column for Direct Labor and Fringe Benefits and Insurance Costs reflects adjustments made to correct for the estimated hours.

Estimated Cost to Complete (See Note 5)

Note 5: After last quarter’s report we agreed the City’s labor cost would all stay within Program Management. Task 3 was to be broken down by its two components and Task 4 was to be broken down by its four components. We are still working on breaking Task 3 and 4 into the components and anticipate reporting expenses that way on the next quarterly report.

DBE Update

Invoices Submitted

Invoice # $ Amount Date Notes/Comments

1

$788,127.96

3/17/2017

This was submitted as a pre-reimbursement request. It is expected it will be resubmitted by 4/28/2017 with requested changes made.

Federal Financial Report

Status

1) See signed copy of the Federal Financial Report.

5

Schedule Update

Key Tasks/Milestones Completed This Quarter/Milestones Scheduled for Upcoming Quarter

Task Name and Deliverable Due Date Status

Task A: Project Management

Quarterly Progress Report for 2016 Q4 1/30/2017 Final Delivered

Project Schedule and Monthly Report Updates for January 1/31/2017 Final Delivered

Partnership /Stakeholder Status Summary 2/23/2017 Final Delivered

Project Schedule and Monthly Report Updates for February 2/28/2017 Final Delivered

Project Schedule and Monthly Report Updates for March 3/31/2017 Final Delivered

Project Schedule and Monthly Report Updates for April 4/30/2017 Final Delivered

Quarterly Progress Report for 2017 Q1 4/30/2017 Final Delivered

Project Management Plan Refresh 5/24/2017 In Progress 75%

Project Schedule and Monthly Report Updates for May 5/31/2017 Not Initiated

Project Schedule and Monthly Report Updates for June 6/30/2017 Not Initiated

Task B: Systems Engineering Approach

Integrated Data Exchange Product Vision 1/19/2017 Final Delivered

Systems Engineering Management Plan (SEMP) 2/2/2017 Final Delivered

Concept of Operations (ConOps) Outline 3/16/2017 Final Delivered

Smart Street Lighting ConOps 4/17/2017 Draft Delivered

Oversized Vehicle Routing Project Vision 4/17/2017 Draft Delivered

Interstate Truck Parking Availability Product Vision 4/17/2017 Draft Delivered

Multi-Modal Trip Planning Application ConOps 5/1/2017 In Progress 95%

Transit Pedestrian Collision Avoidance System Trade Study 5/1/2017 In Progress 95%

Systems Engineering Management Plan (SEMP) 508 Compliant 5/4/2017 In Progress 90%

Common Payment System ConOps 5/8/2017 In Progress 85%

Delivery Zone Availability ConOps 5/8/2017 In Progress 85%

Enhanced Permit Parking ConOps 5/15/2017 In Progress 75%

Event Parking Management ConOps 5/15/2017 In Progress 75%

Connected Vehicle Environment ConOps 5/19/2017 In Progress 65%

Mobility Assistance for People with Cognitive Disabilities ConOps 5/22/2017 In Progress 60%

Truck Platooning ConOps 5/22/2017 In Progress 60%

6

Task Name and Deliverable Due Date Status

Connected Electric Autonomous Vehicle ConOps 6/2/2017 In Progress 50%

Smart Mobility Hubs ConOps 6/2/2017 In Progress 50%

System Architecture and Standards Plan 6/12/2017 In Progress 20%

Demonstration Site Map and Installation Schedule 6/19/2017 In Progress 20%

Transit Pedestrian Collision Avoidance System Test Plan 6/27/2017 In Progress 15%

Task C: Performance Measurement

Performance Measurement Plan 7/7/2017 In Progress 10%

Task D: Data Privacy Requirements

Data Privacy Plan 11/8/2017 Not Initiated

Task E: Data Management and Support for Independent Evaluation

Independent Evaluation Support Plan 8/23/2017 Not Initiated

Data Management Plan 10/11/2017 Not Initiated

Task F: Safety Management and Safety Assurance

Safety Management Plan 7/18/2017 In Progress 5%

Human Use Approval Summary 8/2/2017 In Progress 5%

Task G: Communications and Outreach

A Smart City Demonstration Website 11/18/2016 Final Delivered

Communications and Outreach Plan 1/25/2017 Final Delivered

508 Communications and Outreach Plan 5/24/2017 In Progress

Task H: International Collaboration

International Collaboration Meeting 9/30/2017 Not Initiated

Task I: Participation in Relevant ITS Architecture and Standards Development Effort

Architecture Meeting and Report 9/30/2017 Not Initiated

Task J: Interim and Final Reports

Smart City Demonstration Interim Reports 9/29/2017 Not Initiated

7

Key Activities / Accomplishments

Task A – Program Management

Activities/Accomplishments in January

1) Conducted 30 minute USDOT weekly calls on 1/23/2017 and 1/30/2017. -Discussed the monthly report, working group follow-ups and next steps, Linden Innovation Session in February, engagement of FHWA Ohio, and ConOps Training for February.

2) Conducted 60 minute bi-weekly Smart City meeting with USDOT on 1/24/2017. -Discussed timeframe for Independent Evaluator Performance Work Statement, USDOT staff support for working groups, potential for IRB, deployment of the Integrated Data Exchange, upcoming deliverables and milestones, and partnership agreement status.

3) Submitted the Quarterly Report for 4th Quarter 2016 and Project Management Plan update submitted to USDOT on 1/30/2017.

4) Submitted Monthly Status Report and Schedule Update with Partnership/Stakeholder Status Summary for January on 1/31/2017.

5) For the Partnership/Stakeholder Status Summary see the Leveraged Partner Resources Status Summary section of the report.

Activities/Accomplishments in February

1) Formalized Weekly Status meetings between Columbus, HNTB, and PB teams on 2/13/2017, 2/20/2017, and 2/28/2017. -Discussed work accomplished previous week, what needs improvements, critical path items, goals and deliverables, and coordination of the project leads and working group chairs for the upcoming week and look ahead for the next four weeks.

2) Conducted 30 minute USDOT weekly calls on 2/6/2017, 2/13/2017, 2/20/2017, and 2/27/2017. -Discussed working groups with proposed slides, Linden outreach, updates, schedule, agreement updates, and ConOps Training

3) Conducted 60 minute bi-weekly Smart City meeting with USDOT on 2/10/2017 and 2/21/2017. -Discussed task updates, upcoming deliverables and working group meetings, risks and risk mitigation identified by Columbus, USDOT Site visit in March, SharePoint information that should be posted.

4) Received USDOT comments on PMP update and Quarterly progress report on 2/10/2017. -Reviewed comments and discussed with team to incorporate into 4/30/2017 Quarterly Report and next PMP update.

5) Submitted Monthly Report and Schedule Update with Partnership/Stakeholder Status Summary for February on 2/28/2017.


8

Activities/Accomplishments in March

1) Conducted Weekly Status meetings between Columbus, HNTB and PB teams on 3/6/2017, 3/13/2017, 3/20/2017, and 3/27/2017. -Discussed work accomplished previous week, what needs improvements, critical path items, goals and deliverables, and coordination of the project leads and working group chairs for the upcoming week and look ahead for the next four weeks.

2) Conducted 30 minute USDOT weekly calls on 3/6/2017, 3/13/2017, 3/20/2017, and 3/27/2017. - Discussed ConOps approach to delivery of the 15 projects, Linden outreach, schedule, deliverables; Communications Plan, System Engineering Management Plan, ongoing outreach to commercial and residential district.

3) Conducted 60 minute bi-weekly Smart City meeting with USDOT on 3/7/2017 and 3/21/2017. -Discussed ConOps approaches and due dates, core Performance Measurement team and new meetings, IDE development, upcoming meetings and events, risk register, and update of the System Engineering Management Plan.

4) Policy meeting to discuss autonomous vehicles on 3/22/2017. -Reviewed grant commitments, discussed previous regulatory analysis, the Federal Automated Vehicles Policy from September 2016, ODOT, and Ohio Turnpike approach to AV implementation.

5) Submitted Monthly Status Report and Schedule Update with Partnership/Stakeholder Status Summary for March on 3/31/2017.


Activities to be Performed Next Quarter – April to June 2017

1) Continue to conduct weekly status meetings between Columbus, HNTB, and WSP (PB) on Mondays.

2) Continue to conduct USDOT 30 minute weekly meetings on Mondays.

3) Continue to conduct bi-weekly Smart City 60 minute meetings with USDOT on Tuesdays.

4) Participate in policy meeting to discuss autonomous vehicles on 4/13/2017.

5) Submit Draft Quarterly Status Report for 1st Quarter of 2017 on 4/18/2017.

6) Submit Monthly Status Report and Schedule Update with Partnership/Stakeholder Status Summary for April by 4/30/2017.

7) Submit Quarterly Status Report for 1st Quarter of 2017 by 4/30/2017.

8) Policy meeting to discuss autonomous vehicles on 5/4/2017.

9) Begin to address any Quarterly Status Report for 1st Quarter of 2017 comments and begin development of Quarterly Progress Report for 2nd Quarter of 2017 by 5/15/2017.

10) Submit Monthly Status Report and Schedule Update with Partnership/Stakeholder Status Summary for May by 5/31/2017.

9

11) Submit Monthly Report and Schedule Update with Partnership/Stakeholder Status Summary for June by 6/30/2017.

Task B – Systems Engineering Approach


1) The first Working Group meeting on Data and Analytics occurred on 1/6/2017. -Discussion on data and analytics performance measures and benchmarking with lessons learned from Seattle, London, and Chicago. The product vision was presented and updated, and next steps moving forward for the development of the IDE.

2) Participated in bi-weekly USDOT CV Pilot Technical Roundtable on 1/6/2017 and 1/20/2017.

3) The first Working Group meeting on Autonomous Vehicles occurred on 1/17/2017. -User needs were presented, updated, proposed, and next steps for refining moving forward occurred.

4) Draft Engineering Process Decision Matrix submitted to USDOT for review/approval on 1/17/2017.

5) Conducted the Scrum Kick-off workshop with USDOT on 01/17/2017 – 01/18/2017 to engage the development team, define the definition of done for a product, introduce the roles of the product owner, and finalized the product vision for the IDE.

6) Began daily conference call for the IDE on 1/19/2017 for Scrum Kick-off and Sprint 1 project development on Product Vision. Updated the SEMP, assigned user stories and sizing documentation following Scrum Kickoff meeting.

7) The first Working Group meeting on Smart Street Lighting occurred on 1/19/2017. -User needs were discussed, updated, proposed, and next steps for refining moving forward occurred.

8) The first Working Group meeting on Smart Logistics occurred on 1/20/2017. -User needs were discussed, updated, proposed, and next steps for refining moving forward occurred.

9) The first Working Group meeting on Mobility Assistance occurred on 1/24/2017. -User needs were discussed, updated, proposed, and next steps for refining moving forward occurred.

10) Began bi-weekly conference call retrospective meeting on 1/24/2017 with USDOT on Scrum Kick-off and IDE project development schedule. -Discussed the Sprint 1 on governance for data publishing, domain name and SSL certification.

11) The first Working Group meeting on Transit/ Ped Safety occurred on 1/26/2017. -User needs were discussed, updated, proposed, and next steps for refining moving forward occurred.

12) The first Working Group meeting on Connected Travelers occurred on 1/26/2017. -The Working Group is for the Common Payment System and Multi-Modal Trip Planning Application projects. -User needs were discussed, updated, proposed, and next steps for refining moving forward

10

occurred.

13) Continued to conduct conference calls three to four days a week with USDOT on SEMP development and for submittal to USDOT on 2/2/2017.

14) Continued developing User Needs and draft ConOps for USDOT projects.


1) Updated SE decision matrix and dependency matrix per the inputs from project leads.

2) Continued developing user needs for the USDOT projects.

3) Conducted IDE Sprint Round 1 review meeting on 2/1/2017. -Discussed the four user stories, nine points, and seven chores related to certificates, tools, and control platform.

4) Completed conference calls with USDOT on SEMP and updated SEMP based on comments/feedback received and submitted SEMP to USDOT on 2/2/2017.

5) Participated in bi-weekly USDOT CV Pilot Technical Roundtable on 2/3/2017 and 2/17/2017.

6) Continued participating in bi-weekly conference call retrospective meeting with USDOT on IDE project development on 2/7/2017. -Discussed artifacts, chores, and stories.

7) The first Working Group meeting on Truck Platooning occurred on 2/8/2017 -User needs were discussed, updated, proposed, and next steps for refining moving forward occurred.

8) Met at the Ohio State University Assistive Technology Center to discuss the range of cognitive disabilities on 2/14/2017.

9) Hosted and participated in Systems Engineering/ ConOps training by USDOT on 2/15/2017 – 2/16/2017.

10) Conducted in IDE Sprint 2 review meeting on 2/15/2017. - Discussed the six user stories, eleven points, and four chores related the IDE data manager and roadmap.

11) Attended USDOT CV Pilot Technical Roundtable on 2/21/2017 – 2/23/2017.

12) Attended COTA Assessment Facility Tour on 2/24/2017 for Mobility Assistance for People with Cognitive Disabilities project.


1) The second Working Group meeting on Downtown Parking occurred on 3/1/2017 -Further discussion on user needs, direction for the project, and possible solutions.

2) Conducted Sprint 3 review for IDE Architecture and Governance on 3/1/2017. -Present the definition of “Done” items for stakeholder review; for the Product Owner and Development Team.

3) The first Working Group meeting for First Mile Last Mile project on user needs held on 3/2/2017.

11

-User needs were presented, updated, proposed, and next steps for refining moving forward occurred.

4) Sent ConOps outline to USDOT on 3/2/2017 and teleconference to discuss with USDOT on 3/16/2017.

5) Conducted Truck Platooning meeting with Peloton on 3/6/2017 to discuss technical requirements.

6) Smart Columbus IDE Team bi-weekly meeting with USDOT on 3/7/2017 and 3/21/2017. -Discussed existing user stories statuses and preparation for platform framework.

7) Conducted SEMP Comment Resolution discussion with USDOT on 3/8/2017.

8) Attended the COTA Mobility Advisory Board meeting on 3/8/2017 to gain insights and identify additional user needs for the Mobility Assistance Application project.

9) Conducted and attended the all-day Smart Columbus and COTA coordination meeting on 3/9/2017. -Clarified expectations and learn how COTA’s new payment system will affect the Smart Columbus projects. –Coordinated with COTA on the following projects: Common Payment System, Multi-Modal Trip Planning App, Mobility Assistance App, and Transit & Pedestrian Collision Avoidance System.

10) Conducted the second Working Group meeting on Autonomous Vehicles occurred on 3/13/2017. -Continued discussions on research/data needed to further develop user needs, preliminary route locations, the direction for the project, and possible solutions.

11) Bi-weekly Truck Platooning meetings with project lead and working group co-chairs to discuss ConOps, tractor trailer requirements, routes for platooning , technology limitations on 3/17/2017 and 3/28/2017.

12) Weekly Multi-Modal Trip Planning and Common Payment System meetings with project lead and working group co-chairs to discuss ConOps, COTA existing trip planning tool, integration and needs on 3/15/2017, 3/22/2017, and 3/30/2017.

13) SEMP update submitted to USDOT on 3/16/2017 based on USDOT comments.

14) Participated in App & Town Companion discussion on 3/16/2017 for people with cognitive mobility assistance project. Mass Factory provided a detailed overview and provided answers to technical questions.

15) Participated in CV Pilot Technical Roundtable calls on 3/17/2017 and 3/31/2017.

16) Bi-weekly Transit and Pedestrian Safety meeting with project leads and working group co-chairs to discuss draft Trade Study on 3/21/2017.

17) Mobility Assistance Draft Trade Study submitted to Columbus on 3/21/2017.

18) Bi-weekly Connected Vehicle meeting with project lead and working group co-chairs to discuss ConOps on 3/22/2017.

19) Met with Ohio Trucking Association to refine user needs for truck platooning and smart

12

logistics projects on 3/23/2017.

20) Bi-weekly Downtown Parking meeting with project lead and working group co-chairs to discuss ConOps, existing conditions, coordination and constraints with other City projects on 3/23/2017.

21) Bi-weekly Autonomous Vehicles meeting with project lead and co-chairs to discuss ConOps, coordination, and constraints on 3/23/2017.

22) Bi-weekly Mobility Assistance meeting with project lead and working group chair to discuss Trade Study and ConOps on 3/24/2017.

23) OSU performed high-level test of the Mass Factory Compagnon App for mobility assistance project on 3/27/2017.

24) Held Sprint 1 Planning Session for IDE Sprint 2 on 3/28/2017. -Discussed Sprint 2 backlog containing the user stories, with a velocity of nine points and seven chores along with acceptance criteria.

25) Conducted a meeting with Department of Public Safety on Signal Pre-Empt for First Responders on 3/28/2017 for CVE.

26) Six hour ConOps preliminary review with USDOT for Smart Street Lighting, Common Payment and Multi-Modal Trip Planning. Preliminary review of Truck Parking Availability Product Vision. Both on 3/29/2017.

27) Met with Local Motors to discuss EAV capabilities/products on 3/29/2017.

28) Downtown Parking ConOps meeting with City stakeholders from Parking Violations Bureau on 3/30/2017 to discuss existing conditions and process and discuss user needs.

29) Bi-weekly Smart Street Lighting meeting with project lead and working group co-chairs to discuss ConOps on 3/31/2017.


1) Continue Smart Columbus IDE Team bi-weekly meeting with project lead and co-chairs on Mondays to discuss status of the coordination with the other projects, current sprint, backlog, stories, chores, and any blockers ahead.

2) Continue bi-weekly Transit and Pedestrian Safety meeting with project leads and working group co-chairs to discuss draft Trade Study, system requirements, system architecture, performance measures, and other items on Tuesdays.

3) Continue Smart Columbus IDE Team bi-weekly meeting with USDOT on Tuesdays to discuss status of the current the sprint, backlog, stories, and chores.

4) Continue weekly Multi-Modal Trip Planning and Common Payment System meetings with project lead and working group co-chairs to discuss ConOps, system requirements, system architecture, performance measures, and other items on Wednesdays.

5) Continue bi-weekly Connected Vehicle meeting with project lead and working group co-chairs to discuss ConOps, system requirements, system architecture, performance measures, and other items on Wednesdays.

13

6) Continue weekly Smart Mobility Hub meetings with project lead and working group co-chairs to discuss ConOps, system requirements, system architecture, performance measures, and other items on Wednesdays.

7) Continue bi-weekly Smart Street Lighting meeting with project lead and working group co-chairs to discuss ConOps, system requirements, system architecture, performance measures, and other items on Wednesdays.

8) Continue bi-weekly Downtown Parking meeting with project lead and working group co-chairs to discuss ConOps, system requirements, system architecture, performance measures, and other items on Thursdays.

9) Continue bi-weekly Autonomous Vehicles meeting with project lead and co-chairs to discuss ConOps, system requirements, system architecture, performance measures, and other items on Thursdays.

10) Continue bi-weekly Mobility Assistance meeting with project lead and working group chair to discuss Trade Study and system requirements, system architecture, performance measures, and other items on Fridays.

11) Continue to participate in bi-weekly CV Pilot Technical Roundtable calls on Fridays.

12) Conduct FHWA truck platooning call for Caltrans/PATH/Volvo on 4/3/2017.

13) Conduct IDE daily Standing Scrum Meetings for Sprint 1 for IDE Platform Framework from 4/3/2017 – 4/11/2017.

14) Draft Mobileye trade study to City on 4/5/2017.

15) Conduct a conference with call with a transit pedestrian collision avoidance system manufacturer on 4/7/2017.

16) Hold a coordination meeting for chairs and technical leads on 4/7/2017.

17) Ohio State University to perform high-level test of the Wayfinder App on 4/10/2017.

18) Conduct Truck Platooning meeting with Midwest Logistics on 4/11/2017.

19) Translational Data Analytics with OSU City on 4/17/2017.

20) Submit Smart Street Lighting ConOps Draft on 4/17/2017.

21) Submit Oversized Vehicle Data Product Vision on 4/17/2017.

22) Submit Interstate Truck Parking Availability Product Vision on 4/17/2017.

23) Hold Sprint 2 Planning Session for Sprint 2 for IDE Platform Framework on 4/18/2017.

24) Conduct IDE daily Standing Scrum Meetings for Sprint 2 for IDE Platform Framework from 4/19/2017 – 5/2/2017.

25) Conduct a meeting with Siemens for a technical discussion on 4/18/2017.

26) Conduct the third Working Group meeting on Connected Vehicles on 4/19/2017 to review the draft ConOps and continue discussion on user needs.

27) Conduct a meeting to review the draft ConOps for the Downtown Delivery Zone Availability

14

and Enhanced Permit Parking projects with project working group chairs, project leads, and stakeholders on 4/20/2017.

28) Conduct the second Working Group meeting on Smart Logistics on 4/28/2017 to continue discussion on user needs and available data.

29) Submit Multi-Modal Trip Planning ConOps Draft on 5/1/2017.

30) Submit Transit Pedestrian Collision Avoidance System Trade Study on 5/1/2017.

31) Submit Oversized Vehicle Data Walkthrough Agenda on 5/2/2017.

32) Submit Interstate Truck Parking Availability Walkthrough Agenda on 5/2/2017.

33) Continue to hold additional IDE related sprints reviews, sprint planning sessions and scrum meetings on IDE Architecture and Governance from 5/3/2017 – 6/30/2017.

34) Conduct Oversized Vehicle Data Walkthrough on 5/3/2017.

35) Conduct Interstate Truck Parking Availability Walkthrough on 5/3/2017.

36) The second Working Group meeting on Truck Platooning occurs on 5/3/2017 to continue discussion for the ConOps.

37) Coordination and scheduling meeting for delivery of the Systems Requirements Specifications documents by 5/5/2017. Begin work on the System Requirements Specifications documents by 5/31/2017.

38) Coordination and scheduling meeting for delivery of the Systems Requirements Specifications documents by 5/5/2017.

39) Submit Delivery Zone Availability ConOps Draft on 5/8/2017.

40) Submit Common Payment System ConOps Draft on 5/8/2017.

41) Submit second draft of the Smart Street Lighting ConOps Draft on 5/9/2017.

42) Coordination and scheduling meeting for delivery of the Systems Requirements Specifications documents on 5/13/2017. Begin work on Demonstration Site Map and Installation Schedule by 5/30/2017.

43) Submit Enhanced Permit Parking ConOps Draft on 5/15/2017.

44) Submit Event Parking Management ConOps Draft on 5/15/2017.

45) Conduct the third Working Group meeting on autonomous vehicles on 5/15/2017 to review and discuss the draft ConOps and performance measures.

46) Submit Multi-Modal Trip Planning Walkthrough Agenda on 5/16/2017.

47) Submit Transit Pedestrian Collision Avoidance System Walkthrough Agenda on 5/16/2017.

48) Conduct Multi-Modal Trip Planning Walkthrough on 5/17/2017.

49) Conduct Transit Pedestrian Collision Avoidance System Walkthrough on 5/17/2017.

50) Submit Connected Vehicle Environment ConOps on 5/19/2017.

15

51) Attend COTA Accessible Transportation Advisory Committee meeting on 5/22/2017.

52) Submit Mobility Assistance ConOps Draft on 5/22/2017.

53) Submit Truck Platooning ConOps Draft on 5/22/2017.

54) Participate in the USDOT Low-speed Automated Shuttle Deployment Information-sharing Working Group Meeting on 5/23/2017.

55) Submit Delivery Zone Availability Walkthrough Agenda on 5/23/2017.

56) Submit Common Payment System Walkthrough Agenda on 5/23/2017.

57) Submit Smart Street Lighting Walkthrough Agenda on 5/24/2017.

58) Conduct Common Payment System Walkthrough on 5/24/2017.

59) Conduct Delivery Zone Walkthrough on 5/24/2017.

60) Conduct Smart Street Lighting Walkthrough on 5/25/2017.

61) Submit Enhanced Permit Parking Walkthrough Agenda on 5/30/2017.

62) Submit Event Parking Management Walkthrough Agenda on 5/30/2017.

63) Conduct Enhanced Permit Parking Walkthrough on 5/31/2017.

64) Conduct Event Parking Management Walkthrough on 5/31/2017.

65) Submit Connected Electric Automated Vehicle ConOps Draft on 6/2/2017.

66) Submit Smart Mobility Hubs ConOps Draft on 6/2/2017.

67) Submit Connected Vehicle Environment Walkthrough Agenda on 6/5/2017.

68) Conduct Connected Vehicle Environment Walkthrough on 6/6/2017.

69) Submit Mobility Assistance Walkthrough Agenda on 6/6/2017.

70) Conduct Mobility Assistance Walkthrough on 6/7/2017.

71) Submit Truck Platooning Walkthrough Agenda on 6/7/2017.

72) Conduct Truck Platooning Walkthrough Agenda on 6/8/2017.

73) Submit System Architecture and Standards Plan Draft on 6/12/2017.

74) Submit Demonstration Site Map and Installation Schedule on 6/19/2017.

75) Submit Connected Electric Automated Vehicle Walkthrough Agenda on 6/19/2017.

76) Submit Smart Mobility Hubs Walkthrough Agenda on 6/19/2017.

77) Conduct Connected Electric Automated Vehicle Walkthrough on 6/20/2017.

78) Conduct Smart Mobility Hubs Walkthrough on 6/20/2017.

79) Submit Transit Pedestrian Collision Avoidance System Test Plan Draft on 6/27/2017.

80) Begin work on the Interface Control Documents by 6/27/2017.

16

Task C – Performance Measurement


1) Participated in bi-weekly US DOT CV Pilot Perf Measures / IE / Human Use Approval Meeting on 1/3/2017, 1/17/2017, and 1/31/2017.

2) Met with USDOT at HQ to discuss Columbus Evaluation, Performance Measurement and Data on 1/12/2017.


1) Participated in bi-weekly US DOT CV Pilot Perf Measures / IE / Human Use roundtable on 2/14/2017.

2) Attended meeting with new USDOT Performance Measurement lead to discuss the process and requirements on 2/23/2017.


1) Participated in bi-weekly USDOT CV Pilot Perf Measures / IE / Human Use roundtable meeting on 3/14/2017.

2) Coordinated with OSU in performance measure meeting on 3/16/2017.


1) Continue to participate in bi-weekly USDOT CV Pilot Perf Measures / IE / Human Use roundtable meetings on Tuesdays.

2) Attend the USDOT Performance Measurement Webinar on 4/6/2017.

3) Begin bi-weekly performance measure meeting starting on 4/20/2017 with USDOT.

4) Conduct coordination and scheduling meeting for delivery of the Performance Measurement Plan on 4/27/2017.

5) Begin draft Performance Management Plan and coordinate with the project leads by 5/10/2017.

Task D – Data Privacy Requirements


1) No work to report.


1) USDOT contact was provided to Columbus team and relayed to the Columbus Department of Technology.




17

1) Conduct a meeting on 4/21/2017 with Department of Technology, Public Service, and City Attorney’s office to discuss the IDE, data flows, privacy, NIST 800-53, HIPPA, PCI Compliance, IRS, and Ohio R.C. 1347.

Task E – Data Management and Support for Independent Evaluation




1) Reviewed Data Management Plan from USDOT received on 2/7/2017.




1) Begin discussions with Independent Evaluator on 5/4/2017 with bi-weekly performance measures call.

2) Begin coordination with the Independent Evaluator for the development of the Plan by 5/11/2017.

3) Begin Data Management discussions with IDE team and project leads by mid-May.

Task F – Safety Management and Safety Assurance




1) Participated in IRB 101 online learning session on 2/9/2017.




1) Coordination with technical leads regarding IRB needs to begin by 4/24/2017.

2) Begin IRB engagement for the Human Use Approval Summary by 5/5/2017.

3) Coordination with technical leads regarding Safety Management plan to begin by 5/19/2017.

4) Begin work on the draft Safety Management Plan by 5/30/2017.

18

Task G – Communications and Outreach


1) Submitted Communications/Outreach Plan, Crisis Communication Plan, brand standards and disposition of comments to USDOT on 1/25/2017.

2) Continued copywriting/editing: edited weekly e-newsletters (13 issued through January 2017).

3) Linden innovation session planning and outreach to community partners:

• Sent out meeting notification e-blast to email lists; posted on website

• Hand distributed fliers to North and South Linden Area Commissions and Linden-McKinley STEM High School

• Briefed pastors and other community leaders

• Further developed program and user needs questions

• Sought and secured donations; confirmed program direction with Core Communication Team and PMO

• Coordinated logistics

• Proceeding with designating a Linden liaison A document containing the framework, plan and desired outcome of the Linden Innovation Sessions continues to evolve as planning continues.

4) Participated and presented at TRB from 1/8/2017 to 1/12/2017. (for your awareness)

5) Continued development of communications toolkit and organizing files on the SharePoint site; initiated messaging development process.

6) Initiated conversations for development of the Arts Plan.


1) Launched updates to the Smart Columbus website per USDOT comments received.

2) Continued copywriting/editing: edited weekly e-newsletters.

3) Commenced coordination of Crisis Communications training.

4) Continued development of communications toolkit and organizing files on the SharePoint site; initiated messaging development process.

5) Initiated conversations for development of the Smart Columbus Arts Plan and scheduled kick-off meeting on 3/2/2017.

6) Created framework for media calendar.

7) Submitted revision to Communications/Outreach Plan, Crisis Communication Plan, and brand standards on 2/10/2017. Received feedback from USDOT on 2/17/2017.

8) Held Linden Innovation Sessions 2/10/2017 and 2/11/2017; next steps: draft thank you notes; finalize development of post-event survey with PMO; assemble raw note and formulate meeting summary for distribution to appropriate contacts.

19


1) Held strategy session for organizing and setting goals for Smart Columbus Arts Plan and Culture & Creativity Working Group with arts and community partners on 3/2/2017.

2) Bi-weekly core communication team meeting on 3/7/2017 and 3/21/2017 to discuss progress and next steps for program outreach.

3) Linden future engagement strategy meeting on 3/8/2017 and 3/17/2017.

4) Attended and represented at the Neighborhood Design Center Linden Kickoff Meeting on 3/11/2017.

5) Participated in weekly integrated communications meeting 3/15/2017; participated in communications strategy session with project management office (involving media relations, social media, etc.) 3/15/2017.

6) As an outcome from the 3/13/17 Autonomous Vehicle Working group meeting, additional outreach planning for the commercial district is being investigated.

7) Communications and Outreach Plan update submitted to USDOT on 3/17/2017 and received final approval. Next steps included sharing with communications working group and project personnel as well as sharing final Crisis Communications Plan with all applicable parties.

8) Held meetings with sub-consultants for planning and preparation of scope and budget through July 2018.

9) Linden Innovation Sessions: Post-Linden event survey finalized on 3/22/2017 and submitted to USDOT for review; confirmed next steps in engagement strategy/planning session with engineering team.

10) Continued development of media relations strategy, social media relations strategy, editorial calendar build-out and editorial board planning.

11) Attended Delivery Zone Open House on 3/30/2017. -Leveraged Columbus’ Division of Traffic Management Short North Parking Engagement to obtain feedback from the public on delivery zones in the Short North and downtown.


1) Continue 60 minute weekly Integrated Communication Team Meetings on Wednesdays.

2) Attend Delivery Zone Open Houses on 4/4/2017, 4/11/2017, and 4/12/2017. -Leverage Columbus’ Division of Traffic Management Short North Parking Engagement to obtain feedback from the public on delivery zones in the Short North and downtown.

3) Hold Easton engagement strategy meeting on 4/6/2017. -Meeting with Easton Towne Center representatives for a coordination and approach for the user needs development and verification.

4) Revise and finalize the Smart Columbus brand and messaging by the end of April.

5) Refine a Smart Columbus social media strategy by May.

6) Approval on 508 compliant Communications and Outreach Plan by end of May.

20

7) Launch Smart Columbus Blog by June. -The Communications and Outreach Plan identifies that a website and blog strategy will be developed. The website is live and we want to establish the blog as way to keep general audiences aware of the project status.

8) Update as needed the Communications and Outreach Plan in June.

9) Ongoing media relations efforts to specific audiences. -Continue efforts for engaging the media to inform the public of ongoing progress.

Table of Events Attended and Upcoming Events (Synopsis of Activities in Task G)

Date Event

February 9, 2017 Smart State Forum

February 10-11, 2017 Linden Innovation Session

February 13, 2017 TRB Webinar

March 8, 2017 COTA Mobility Advisory Board

March 30, 2017

April 4, 2017

April 10-11, 2017

Delivery Zone Open Houses

April 10, 2017 Columbus Library Service Managers

April 18, 2017 OSU - School of Environmental & Natural Resources Breakfast

May 12, 2017 Columbus Chamber Government Day

Task H – International Collaboration


1) Participated in conference call for Transport for London information exchange call on 1/6/2017.




1) Held WebEx with London to discuss Cubic DMP on 3/1/2017.

2) Held Truck platooning call with the Dutch Consulate on 3/8/2017. Dutch provided information on their truck platooning experiences.


21

1) No work anticipated.

Task I – Participation in Relevant ITS Architecture and Standards Development Efforts


1) Participated in SAE J2945/2- Dedicated Short Range Communications (DSRC) Performance Requirements for V2V Safety Awareness Comment Resolution discussion on 1/25/2017.






1) No work anticipated.

Task J – Interim and Final Reporting








1) Begin gathering information for the Year One interim report by 6/1/2017.

22

Subcontractor Status Summary

Key Tasks/ A summary of Subcontractor Coordination and Management Activities

Status of Key Procurements and sub-contract awards in January

1) No key procurements or sub-contract awards made this month

Status of Key Procurements and sub-contract awards in February


Status of Key Procurements and sub-contract awards in March


Future Key Procurements and sub-contract awards in the Next Quarter – April to June 2017

1) Plan to request approval of USDOT to add CJI Research as a sub-consultant to the Communications contract with Engage. This is a professional research firm to assist with in conducting and analyzing data from focus groups and surveys. Plan to add Schulman IRB as a sub-consultant to the ITS Program Management and Program Initialization contract with HNTB. They will be used as the institutional review board (IRB) to establish necessary research protocols to obtain Human Use Approvals.

Leveraged Partner Resources Status Summary

Summary of activities related to Leveraged Partner Resources

Status of Key Procurements and sub-contract awards

1) The next pages contain the Partnership/Stakeholder Status Summary from March 2017 (end of 1st Quarter 2017).

Smart City ScheduleCooperative Agreement No. DTFH6116H00013

Partnership/Stakeholder Status Summary

Partner Priority Primary Draft Agreemen

t sent

Negotiatin

g Ag

reem

ent

Agreem

ent

Executed

Agreem

ent S

ent

to USD

OT

Total Value OfferingAffiliated USDOT Projects USDOT District Served

Affiliated Electrification Initiatives

Potential to Serve Greater Columbus Region

Partner Implementation Starts

AT&T 1 USDOT 3/14/2017 1,000,000$

$100,000 IoT Security consulting, $900,000 in equipment and data services. AT&T has committed to provide in‐kind partnering to the City to assist with the deployment of the Columbus Connected Transportation Network (CCTN). The proposed partnering includes professional services and technical support resources; communications and data management technologies; USB cellular modems and SIM cards and connectivity; hardware to support communications and data management services. 2 Residential No QTR 3 CY 2017

Autodesk 2 USDOT X X 3/20/2017 3/22/2017 219,060$

4‐yr subscription to Infraworks, an information modeling platform that uses 3‐D visualizations and real‐world data to plan major engineering projects, on‐site training, continued technical support.

Visualization of TBD project

Residential, Commercial, Downtown, Logistics No 2018

AWS 1 USDOT 12/6/2016 X 1,000,000$

$750,000 Service credits, $250,000 Professional Services. Credits to AWS Cloud services and AWS Professional Services. AWS will also provide solution architecture and best practices guidance to the Recipient. 4 IDE 5.2 Yes QTR 2 CY 2017

Continental 1 USDOT 12/21/2016 X 1,000,000$

Continental will deploy a roadside infrastructure sensing system in a phased approach, with one intersection to be deployed and beta tested before additional intersections are fitted. Intersections will demonstrate DSRC communication systems to enable communication between roadside and onboard systems; API interfaces on cloud backend comprised of APIs for accessing data from both onboard and roadside V2X systems; basic safety messages to demonstrate the effectiveness of the CCTN on alleviating transportation‐related issues such as intersection safety warnings, traffic management, automated system to regulate the flow of traffic according to real time traffic information, in‐car productivity and safety, V2X warnings based on driver profile, route optimization or navigation, and reduced traffic congestion through load balancing via rerouting services enhanced with real time navigation data. 1 TBD No QTR 3 CY 2017

Partnership Relationship to Program and ProjectsStatus

Nationa

l Partners

Page 1 of 6 3/30/2017




t sent

Negotiatin

g Ag

reem

ent

Agreem

ent

Executed

Agreem

ent S

ent

to USD

OT






Mobileye 2 USDOT 12/14/2016 X 1,950,000$ Cost of 300 units and data monitoring for 1 year. Installation of Mobileye's Shield +TM technology on transit buses. 1, 3

Residential, Commercial, Downtown, Logistics Yes QTR 4 CY 2017

NXP 1 USDOT 12/2/2016 X 2,500,000$

Wireless communication modules that allow cars to securely exchange data, such as hazard warnings, over distances of more than a mile to prevent accidents and improve traffic flow. 1, 9, 11

CCTN, Commercial, Downtown Yes QTR 3 CY 2017

Sidewalk Labs USDOT 12/29/2016 X 230,000$

$200,000 staff, $30,000 travel. Flow technology, an analytics platform that the Recipient can use to identify traffic‐prone areas and parts of a city that are underserved by public transportation — all by using traffic patterns culled from aggregated, anonymized data. From that information the software can suggest solutions like ride‐sharing, new transportation access or a rerouting of traffic to better serve the community. 5,6,7 Residential No QTR 3 CY 2017

Battelle 1 USDOT 3/13/2017 X 1,000,000$ In‐kind program staff support 1 CCTN No QTR 2 CY 2017

Columbus Partnership 1 USDOT 11/21/2016 X 3/31/2017 3/31/2017 13,000,000$

$500K for program staff support; $7.5M in private sector in‐kind programs and private sector commitments for electrification; and $5M in facilitating in‐kind CV/AV transportation research 9 Commercial 2.2, 4.1, 4.2, 4.3, 5.3, 5.4 Yes QTR 2 CY 2017

Econolite 1 USDOT 12/28/2016 X 900,000$ $700,000 firmware licenses; $200,000 analytics software licenses 1 CCTN Yes QTR 4 CY 2017

Experience Columbus 1 USDOT 10/7/2016 X 100,000$ Cash from parking providers and organizer of parking collaborators to support parking application 12 Downtown No 2018

Page 2 of 6 3/30/2017




t sent

Negotiatin

g Ag

reem

ent

Agreem

ent

Executed

Agreem

ent S

ent

to USD

OT






Franklin County 2 USDOT 12/29/2016 $ 4,000,000 $3M program, $1M cash 1, 9, 13, 14CCTN, Commercial, Logistics 2.1, 5.2, 5.4 Yes QTR 2 CY 2017

GCAC (Arts) 2 USDOT 12/29/2016 X 2/23/2017 2/24/2017 1,000,000$ $1M cash to support communication, education and awareness of smart city programs 7 Residential No QTR 1 CY 2017

HERE 3 USDOT 1,000,000$ Mapping, application development 6, 12 Residential, Downtown Yes QTR 4 CY 2017

Honda 2 USDOT 12/29/2016 X 3,200,000$ $1.6M Labor, $1.54M hardware, $0.6M software 1 CCTN 4.1, 4.2, 4.3 Yes 2018

INRIX 3 USDOT $ 178,000 Data and application development 12 Downtown No QTR 2 CY 2017

MassFactory 2 USDOT Mobility application 8 Residential Yes QTR 3 CY 2017

MORPC 1 USDOT X X 1/5/2017 1/5/2017 600,000$ $600K cash for EV charging station design and installation 4 IDE 2.1, 2.3, 5.2 Yes QTR 2 CY 2017

Local Partners

Page 3 of 6 3/30/2017




t sent

Negotiatin

g Ag

reem

ent

Agreem

ent

Executed

Agreem

ent S

ent

to USD

OT






ODOT 2 USDOT X X 3/22/2017 3/22/2017 7,000,000$ In‐kind staff support and data services All All Yes QTR 2 CY 2017

OSU 2 USDOT X X 12/21/2016 1/19/2017 $ 15,000,000

$2M cash for USDOT projects; $5M in‐kind EV program support; and $8M in‐kind program support for mobility, smart grid and related areas All All 2.1, 5.3, 5.4 Yes QTR 2 CY 2017

Peloton 3 USDOT 2/6/2017 X TBD Truck platooning demonstration 13 Logistics No QTR 2 CY 2017

Siemens 2 USDOT X X 1/30/2017 1/30/2017 385,000$

CV controller software upgrade labor and installation; 25 RSU equipment and installation; RSU central management system software; preparation for deployment of one software application 1 CCTN Yes QTR 2 CY 2017

SPARC 1 USDOT 10/6/2016 $ 388,200 $244,800 facilities, $143,400 in‐kind staffing for CV/AV vehicle testing and deployment. 1 CCTN No 2018

AEP 1 Vulcan X X 11/30/2016 1/30/2017 22,800,000$

For 2017‐2019 energy efficiency programs, grid modernization including deployment of ten EV charging stations, implementation of 10‐20 MWH of battery storage, fleet electrification, and research in advanced clean energy and V2G connectivity. All Yes QTR 2 CY 2017

Vulcan 1 Vulcan 12/23/2016 X $ 10,000,000 Electrification initiatives All Yes QTR 2 CY 2017USDOE 1 Vulcan Program staff support 4, 9 IDE, Commercial All Yes QTR 1 CY 2017

fleetcarma 2 Vulcan X X 2/9/2017 2/24/2017 $ 900,000 Vehicle telematics equipment supporting fleet electrification decision‐making 2.1, 2.2, 2.3 Yes QTR 2 CY 2017

DC Solar 3 Vulcan X X 2/2/2017 2/24/2017 1,500,000$

DC Solar will partner with the City to deploy eight to ten mobile solar generators or EV charging stations in 11 month increments at locations in the City to be determined. Mobile solar generators and EV charging stations will demonstrate the use of renewable energy sources in support of fleet electrification and power generation. 1.1, 5.2, 5.3, 5.4 Yes QTR 2 CY 2017

Ford 1 Both EV and smart mobility collaboration 1, 7 CCTN, Residential 4.1, 4.2, 4.3 Yes QTR 3 CY 2017

Vulcan

Partners

Page 4 of 6 3/30/2017




t sent

Negotiatin

g Ag

reem

ent

Agreem

ent

Executed

Agreem

ent S

ent

to USD

OT






Daimler 1 Both EV and smart mobility 1, 7 CCTN, Residential 2.3, 4.1, 4.2, 4.3 Yes QTR 3 CY 2017

Bosch 2 Vulcan EV and smart mobility 5.1, 5.2, 5.3, 5.4 No QTR 3 CY 2017ODW 1 USDOT truck platooning drayage company 13 Logistics No QTR 2 CY 2017FSP 1 USDOT truck platooning drayage company 13 Logistics No QTR 2 CY 2017

COTA 1 USDOT TBD In‐kind staff 1, 3, 4, 5, 6, 7, 8, 9CCTN, IDE, Residential, Commercial 5.2 Yes QTR 2 CY 2017

CenturyLink 1 USDOT IDE‐related services 2 CCTN YesFifth Third Bank 1 USDOT mobile payment system 5 Residential Yes

IPS 2 USDOT parking applications 12 Downtown YesKey Bank 1 USDOT mobile payment system 5 Residential Yes

United Healthcare 2 USDOT 6,7,8 Residential YesBMW 1 Vulcan EV and smart mobility 7 Residential 4.1, 4.2, 4.3 YesBYD 1 Vulcan EV OEM 4.1, 4.2, 4.3 Yes

ChargePoint Vulcan EV infrastructure 5.1, 5.2, 5.3, 5.4, 5.5 YesEVgo Vulcan EV infrastructure 5.1, 5.2, 5.3, 5.4, 5.5 YesGM 1 Vulcan EV and smart mobility 4.1, 4.2, 4.3 Yes

Greenlots Vulcan EV infrastructure YesNissan 1 Vulcan EV OEM 4.1, 4.2, 4.3 Yes

Proterra 3 Vulcan data services 2.1, 2.2, 4.2 YesSmith Electric 3 Vulcan EV OEM 5.1, 5.2, 5.3, 5.4, 5.5 Yes

VW/Audi 1 Vulcan EV OEM 4.1, 4.2, 4.3 Yes

Workhorse 1 Vulcan EV OEM 4.1, 4.2, 4.3 YesXL Hybrids 1 Vulcan EV OEM 4.1, 4.2, 4.3 YesCleverCiti 1 USDOT X parking detection and management system 10, 12 Downtown Yes

Kapsch 1 USDOT X parking management, detectioon and CV technology 1, 10, 12 CCTN, Downtown YesEricsson 1 USDOT data security, IoT TBD TBDSiriusXM 2 USDOT CV technology 1 CCTN Yes

Miovision 2 USDOT Traffic data collection and analytics at 10 intersections 1, 10 CCTN, Downtown NoCivis Analytics 3 USDOT data analytics

Covisint 3 USDOT CV‐related support/integrator

Cubic 3 USDOT dataDassault 3 USDOT CV‐related support/integratorEverCar Vulcan EV carshareKPMG 3 USDOT program management

Vindowhd 3 USDOTInex Technologies 1 USDOT parking hardware

Parking Panda 1 USDOT parking reservation and finder application

Anticipated

New

Partners

Potential Partners

Page 5 of 6 3/30/2017




t sent

Negotiatin

g Ag

reem

ent

Agreem

ent

Executed

Agreem

ent S

ent

to USD

OT






Smarking 1 USDOT parking back office managementSpotwise 1 USDOT parking detection, enforcement and analytics

ParkWhiz 1 USDOT parking payment and analyticsMetabyte 1 USDOT IDE‐related data services

Honk Mobile 1 USDOT mobile parking payment and detectionVoice Park 1 USDOT mobile parking payment and detectionCloudParc 1 USDOT mobile parking payment and detectionTrapeze 2 USDOT

Passport Inc. 1 USDOT mobile parking payment and detectionParkifi 1 USDOT

Spot Hero 1 USDOTParkmobile 1 USDOT

Genetec 1 USDOT LPR technologyXerox 3 USDOT mobile payment system

Libelium 2 USDOT X smart parking ‐ loading zones ‐ sensorsGoogle dotMaps 1 USDOT ROW permit management system

Wisekey 3 USDOT IDE‐related services, data analytics

Ricardo 3 USDOT X X program management ‐ system integrator

Investigated

Page 6 of 6 3/30/2017

23

Schedule Update

Current schedule for the project

Status of schedule

1) The next pages contains the approved Table of Deliverables for the approved March 2017 Monthly Update (end of 1st Quarter 2017).

2) The email of the Quarterly Progress Report contains the MS Project file of the March 2017 schedule (end of 1st Quarter 2017).

24

Risk Status

A summary of risks identified

The Risk log has currently has 22 risks identified to varying threats to the project with three sections.

There are three overarching headers in the risk log; Risk Identification, Qualitative Baseline Assessment,

and Monitoring & Control. The Risk Identification section contains risk identification by categories,

individual project, and description. The Qualitative Baseline Assessment weights the risk with the

probability of occurrence, impacts to the schedule, and costs, and a ranking calculated from it. Monitoring

& Control has the status and associated notes.

Risk Log

Smart Columbus Risk Register

No. Name Risk Group Category Project Phase

Typ

e

Description (Cause, Effect) Risk TriggerEngage

USDOT

Probability of

OccurrenceImpact to Cost

Impact to

Schedule

On or

near

CP?

Rank Status Status Notes as of 03-28-2017

1Multi-Modal Trip Planning is

limited to COTA Services onlyTechnical Residential

6-Multi-Modal Trip

PlanningDesign

Thr

eat If at the time of deployment, COTA is

the only confirmed provider. Will limit

user access to services.

Confirmation of MMTPA service

providersYes Moderate Low Low No 12

Act

ive

2 FMLM providers not available Technical Residential7-Smart Mobility

HubsDesign

Thr

eat If at the time of deployment, we have

not confirmed FMLM service providers

we will not improve existing conditions.

Submittal of demonstration site map

and installation scheduleYes Moderate Low Low No 12

Act

ive

3Cannot Recruit 3000 Aftermarket

Safety Device (ASD) ParticipantsTechnical Outreach 1-CV Environment Deployment

Thr

eat

At conclusion of installation, less than

3000 units have been installed.

Reduces amount of data collected and

extends schedule

Number of signed up interested

participants by the time installation

begins

Yes High Low Moderate No 20

Act

ive

4 Media driven scope creep Organizational Outreach All All Phases

Thr

eat

Media mis-interprets or misrepresents

the message/real scope of the project.

Creates expectation to include more

scope in the project.

Media event Yes High Low Low No 16

Act

ive

5Media driven negative perception

of projectOrganizational Outreach All All Phases

Thr

eat

Media mis-interprets or misrepresents

the scope of the project. Creates

negative response and lack of

participation/support by the

users/public.

Media event Yes Moderate Moderate Moderate No 18

Act

ive

6 Parking permit technology Technical Downtown11-Enhanced

Permit ParkingConcept

Thr

eat City preference for license plate reader

(LPR) over RFID and ultra high

frequency readers.

Technology decision during concept

developmentYes High Moderate Moderate No 24

Act

ive

7Delivery zone availability

application developmentUsability Downtown

10-Delivery Zone

AvailabilityDeployment

Thr

eat Development of end user application

not in the scope, but identified as a user

need.

Deployment phase Yes High High Moderate Yes 28

Act

ive

8City not able to use designated

partnerTechnical All All Deployment

Thr

eat

City is unable to accept partner

offerings.Decision on partner agreement Yes High Moderate Moderate Yes 24

Act

ive

9

Wi-Fi coverage not sufficient to

improve access to

educational/employment

resources.

Technical CCTN2-Smart Street

LightingDesign

Thr

eat

During field testing, system does not

meet service expectations. Access to

educational/ employments services not

realized.

SDD Yes High Moderate Low No 20

Act

ive

10Development required for OBUs &

RSUs to meet requirements.Technical CCTN All Procurement

Thr

eat Off-the-shelf OBUs & RSUs do not meet

requirements. Delay

deployment/change in scope.

During vendor pre-qual/assessment

processYes Moderate Moderate High Yes 21

Act

ive

11Product does not meet technical

specifications.Technical CCTN All Deployment

Thr

eat Off-the-shelf application does not meet

specifications. Delay

deployment/change in scope.

During lab testing Yes Moderate Low High Yes 18

Act

ive

12Unforeseen procurement process

duration with CitySchedule All All Procurement

Thr

eat

Unable to shorten typical procurement

process. Delayed schedule.

During the RFQs / Procurement

processYes Moderate Low High Yes 18

Act

ive

13Unforeseen procurement process

duration with partnersSchedule All All Procurement

Thr

eat

Unexpected change in partner delivery

date. Delayed schedule.

When installation is scheduled to

beginYes Moderate Low High Yes 18

Act

ive

14 Timeframe to install on AEP assets Schedule CCTN 1-CV Environment Deployment

Thr

eat

Do not have authorization to attach to

AEP poles. Delayed Schedule.During deployment phase No High Low High Yes 24

Act

ive

15

Equipment attachment point on

poles not high enough and limits

coverage.

Technical CCTN 1-CV Environment Deployment

Thr

eat Existing infrastructure cannot support

additional equipment at the required

height. Delayed schedule/increase cost.

During deployment phase No Moderate Low High No 18

Act

ive

Monitoring & ControlQualitative Baseline AssessmentRisk Identification

Risk Register 3/31/17

Smart Columbus Risk Register

No. Name Risk Group Category Project Phase

Typ

e

Description (Cause, Effect) Risk TriggerEngage

USDOT

Probability of

OccurrenceImpact to Cost

Impact to

Schedule

On or

near

CP?

Rank Status Status Notes as of 03-28-2017

Monitoring & ControlQualitative Baseline AssessmentRisk Identification

16Lack of "Mobility Assistance"

resourcesTechnical Residential

8-Mobility

Assistance for

People with

Cognitive

Disabilities

Deployment

Thr

eat

Limited ability to fully test the Mobility

Assistance application and application

does not provide benefit to people with

Cognitive Disabilities

During field testing Yes High Low Low No 16

Act

ive

Testing in process now.

17Sensitive PII becomes

compromisedTechnical IDE 3-IDE Deployment

Thr

eat Data privacy safeguard policies are

circumvented and personally identifiable

information (PII) is compromised

During deployment phase Yes Low Moderate High Yes 14

Act

ive

18Legislation for the deployment of

the planned autonomous shuttles Legislative Logistics

9-Connected

Electric Automated

Vehicle

Deployment

Thr

eat

Legislation will likely be required for the

deployment of AV on City streets

Appropriate legislation not in place

prior to deployment commencingYes High High High Yes 32

Act

ive

19Significantly more stakeholders to

coordinate with than anticipatedSchedule All All Concept

Thr

eat

Due to the enthusiasm and interest in

the Smart Columbus Program, there

have been many more players to

coordinate with to allow appropriate

time to listen and respond to user

needs.

Concept of Operation development Yes High Moderate Moderate Yes 24

Act

ive

20

Legislation for automated trucks

and truck platooning on public

streets

Legislative Logistics13-Truck

PlatooningDeployment

Thr

eat

Legislation will likely be required related

to following distance for trucks engage

in platooning on public streets and

highways.

Deployment phase yes Moderate Low High Yes 18

Act

ive

21

Partners: SPARC, local partner in

the City’s grant application,

delayed their ground breaking

development

Schedule Logistics

9-Connected

Electric Automated

Vehicle

DeploymentT

hrea

t

SPARC, a committed local partner in

the City’s grant application, has not yet

broken ground on their development,

which is the City’s proposed primary

site for vehicle testing prior to

deployment.

During deployment phase Yes High Moderate Low No 20

Act

ive

22COTA Mobility Assistance Call

Center Support LiabilityOrganizational Residential

8-Mobility

Assistance for

People with

Cognitive

Disabilities

Concept

Thr

eat

COTA is not able to provide call center

support, as it creates a "special duty"

that may result in COTA being held

liable for negligence related to mobility

app user care.

Upon COTA legal team making a

decision.Yes High Low Low No 16

Act

ive

Could OSU alternately staff a call center?

Risk Register 3/31/17

25

Issues/Concerns/ Other See note in the risk section.