Sensors Master Plan: Difference between revisions
From Modelado Foundation
imported>Wpinfold (Created page with "{| border="0" cellspacing="0" cellpadding="0" class="ta1"<colgroup><col width="44"/><col width="202"/><col width="279"/><col width="239"/><col width="200"/><col width="228"/>...") |
imported>Wpinfold No edit summary |
||
| Line 1: | Line 1: | ||
{| border=" | {| border="1" cellspacing=0 class="wikitable"<colgroup><col width="215"/><col width="188"/><col width="279"/><col width="244"/><col width="228"/><col width="195"/><col width="181"/></colgroup> | ||
| | |- class="ro3" | ||
| colspan="4" style="text-align:center;width:139.49pt; " class="ce3" | <p>Blueprint</p> | |||
| colspan="3" style="text-align:center;width:148pt; " class="ce3" | <p>Implementation</p> | |||
| colspan="4" style="text-align: | |||
| colspan="3" style="text-align: | |||
|- class="ro3" | |- class="ro3" | ||
| style="text-align:left;width:130.99pt; " class="ce3" | <p>High Level Purpose</p> | | style="text-align:left;width:130.99pt; " class="ce3" | <p>High Level Purpose</p> | ||
| style="text-align:left;width:180.99pt; " class="ce3" | <p>Goals/Objectives</p> | | style="text-align:left;width:180.99pt; " class="ce3" | <p>Goals/Objectives</p> | ||
| Line 19: | Line 11: | ||
| style="text-align:left;width:113.5pt; " class="ce11" | <p>Targets/Metrics</p> | | style="text-align:left;width:113.5pt; " class="ce11" | <p>Targets/Metrics</p> | ||
| style="text-align:left;width:139.01pt; " class="ce11" | <p>Timing/Milestones</p> | | style="text-align:left;width:139.01pt; " class="ce11" | <p>Timing/Milestones</p> | ||
|- class="ro4" | |- class="ro4" | ||
| style="text-align:left;width:130.99pt; " class="ce4" | <p>Safety on 'roads' - this includes pathways that are not traditional roads. </p> | | style="text-align:left;width:130.99pt; " class="ce4" | <p>Safety on 'roads' - this includes pathways that are not traditional roads. </p> | ||
| style="text-align:left;width:180.99pt; " class="ce4" | <p>Environment: determine measures of need within it</p> | | style="text-align:left;width:180.99pt; " class="ce4" | <p>Environment: determine measures of need within it</p> | ||
| Line 30: | Line 19: | ||
| style="text-align:left;width:113.5pt; " class="ce4" | <p>As sensor adoption grows, types of application does as well</p> | | style="text-align:left;width:113.5pt; " class="ce4" | <p>As sensor adoption grows, types of application does as well</p> | ||
| style="text-align:left;width:139.01pt; " class="ce4" | <p>Meetings: </p><p>February in Portland; another meeting in June</p> | | style="text-align:left;width:139.01pt; " class="ce4" | <p>Meetings: </p><p>February in Portland; another meeting in June</p> | ||
|- class="ro5" | |||
|- class="ro5" | |||
| style="text-align:left;width:130.99pt; " class="ce5" | <p>How do we improve? Understand what is happening in our environment and how sensors, etc can help.</p> | | style="text-align:left;width:130.99pt; " class="ce5" | <p>How do we improve? Understand what is happening in our environment and how sensors, etc can help.</p> | ||
| style="text-align:left;width:180.99pt; " class="ce5" | <p>Make use of feedback collection for improvement</p> | | style="text-align:left;width:180.99pt; " class="ce5" | <p>Make use of feedback collection for improvement</p> | ||
| Line 41: | Line 27: | ||
| style="text-align:left;width:113.5pt; " class="ce5" | | | style="text-align:left;width:113.5pt; " class="ce5" | | ||
| style="text-align:left;width:139.01pt; " class="ce5" | <p>GCTC- Document report of blueprint by March</p> | | style="text-align:left;width:139.01pt; " class="ce5" | <p>GCTC- Document report of blueprint by March</p> | ||
|- class="ro5" | |- class="ro5" | ||
| style="text-align:left;width:130.99pt; " class="ce5" | <p>Quality of life</p> | | style="text-align:left;width:130.99pt; " class="ce5" | <p>Quality of life</p> | ||
| style="text-align:left;width:180.99pt; " class="ce5" | <p>Identify data flows:</p><p>-Who owns them?</p><p>-Address security concerns</p><p>-Privacy/conflicts</p><p>-Application</p> | | style="text-align:left;width:180.99pt; " class="ce5" | <p>Identify data flows:</p><p>-Who owns them?</p><p>-Address security concerns</p><p>-Privacy/conflicts</p><p>-Application</p> | ||
| Line 51: | Line 34: | ||
| style="text-align:left;width:148pt; " class="ce10" | <p>Share emerging best solutions with other cities</p> | | style="text-align:left;width:148pt; " class="ce10" | <p>Share emerging best solutions with other cities</p> | ||
| style="text-align:left;width:113.5pt; " class="ce16" | | | style="text-align:left;width:113.5pt; " class="ce16" | | ||
| style="text-align:left;width:139.01pt; " class=" | | style="text-align:left;width:139.01pt; " class="ce5" | | ||
|- class="ro4" | |- class="ro4" | ||
| style="text-align:left;width:130.99pt; " class="ce5" | <p>Identify transportation root issues through data</p> | | style="text-align:left;width:130.99pt; " class="ce5" | <p>Identify transportation root issues through data</p> | ||
| style="text-align:left;width:180.99pt; " class="ce5" | <p>Determining energy needs of transportation infrastructure</p> | | style="text-align:left;width:180.99pt; " class="ce5" | <p>Determining energy needs of transportation infrastructure</p> | ||
| Line 62: | Line 42: | ||
| style="text-align:left;width:148pt; " class="ce14" | <p>Coming together doesn’t stop existing actions in lone transportation clusters</p> | | style="text-align:left;width:148pt; " class="ce14" | <p>Coming together doesn’t stop existing actions in lone transportation clusters</p> | ||
| style="text-align:left;width:113.5pt; " class="ce16" | | | style="text-align:left;width:113.5pt; " class="ce16" | | ||
| style="text-align:left;width:139.01pt; " class="ce5" | | | style="text-align:left;width:139.01pt; " class="ce5" | | ||
|- class="ro1" | |- class="ro1" | ||
| style="text-align:left;width:130.99pt; " class="ce5" | <p>Data-driven transportation system</p> | | style="text-align:left;width:130.99pt; " class="ce5" | <p>Data-driven transportation system</p> | ||
| style="text-align:left;width:180.99pt; " class="ce5" | <p>Identify trade-offs of a robust sensor system</p> | | style="text-align:left;width:180.99pt; " class="ce5" | <p>Identify trade-offs of a robust sensor system</p> | ||
| Line 73: | Line 50: | ||
| style="text-align:left;width:148pt; " class="ce14" | <p>Identify city resources - how?</p> | | style="text-align:left;width:148pt; " class="ce14" | <p>Identify city resources - how?</p> | ||
| style="text-align:left;width:113.5pt; " class="ce16" | | | style="text-align:left;width:113.5pt; " class="ce16" | | ||
| style="text-align:left;width:139.01pt; " class="ce5" | | | style="text-align:left;width:139.01pt; " class="ce5" | | ||
|- class="ro6" | |- class="ro6" | ||
| style="text-align:left;width:130.99pt; " class="ce6" | | | style="text-align:left;width:130.99pt; " class="ce6" | | ||
| style="text-align:left;width:180.99pt; " class="ce5" | <p>What technology challenges exist and who can help solve?</p> | | style="text-align:left;width:180.99pt; " class="ce5" | <p>What technology challenges exist and who can help solve?</p> | ||
| Line 84: | Line 58: | ||
| style="text-align:left;width:148pt; " class="ce14" | <p>Send email with invite to Google group</p> | | style="text-align:left;width:148pt; " class="ce14" | <p>Send email with invite to Google group</p> | ||
| style="text-align:left;width:113.5pt; " class="ce16" | | | style="text-align:left;width:113.5pt; " class="ce16" | | ||
| style="text-align:left;width:139.01pt; " class="ce5" | | | style="text-align:left;width:139.01pt; " class="ce5" | | ||
|- class="ro7" | |- class="ro7" | ||
| style="text-align:left;width:130.99pt; " class="ce5" | | | style="text-align:left;width:130.99pt; " class="ce5" | | ||
| style="text-align:left;width:180.99pt; " class="ce5" | <p>Need to consider what solutions will be available when (5G) and other future solutions arrive - how do we stay ahead of the curve?</p> | | style="text-align:left;width:180.99pt; " class="ce5" | <p>Need to consider what solutions will be available when (5G) and other future solutions arrive - how do we stay ahead of the curve?</p> | ||
| Line 95: | Line 66: | ||
| style="text-align:left;width:148pt; " class="ce14" | <p>Identifify sub-work groups and have virtual report outs following sub-group meetings</p> | | style="text-align:left;width:148pt; " class="ce14" | <p>Identifify sub-work groups and have virtual report outs following sub-group meetings</p> | ||
| style="text-align:left;width:113.5pt; " class="ce16" | | | style="text-align:left;width:113.5pt; " class="ce16" | | ||
| style="text-align:left;width:139.01pt; " class="ce5" | | | style="text-align:left;width:139.01pt; " class="ce5" | | ||
|- class="ro1" | |- class="ro1" | ||
| style="text-align:left;width:130.99pt; " class="ce7" | | | style="text-align:left;width:130.99pt; " class="ce7" | | ||
| style="text-align:left;width:180.99pt; " class="ce7" | <p>Vulnerability analysis - what's the backup plan?</p> | | style="text-align:left;width:180.99pt; " class="ce7" | <p>Vulnerability analysis - what's the backup plan?</p> | ||
| Line 107: | Line 75: | ||
| style="text-align:left;width:113.5pt; " class="ce17" | | | style="text-align:left;width:113.5pt; " class="ce17" | | ||
| style="text-align:left;width:139.01pt; " class="ce15" | | | style="text-align:left;width:139.01pt; " class="ce15" | | ||
|} | |} | ||
Latest revision as of 23:27, February 12, 2017
Blueprint |
Implementation | |||||
High Level Purpose |
Goals/Objectives |
Strategies/Approach |
Contributors Board |
Collaboration Plan |
Targets/Metrics |
Timing/Milestones |
Safety on 'roads' - this includes pathways that are not traditional roads. |
Environment: determine measures of need within it |
Different types of sensors- mobile, stationary, on-person |
Cities: Columbus, Baltimore, Chattanooga, Greeneville, DC, Milan, Florence |
Google Group pages for sensors use cases |
As sensor adoption grows, types of application does as well |
Meetings: February in Portland; another meeting in June |
How do we improve? Understand what is happening in our environment and how sensors, etc can help. |
Make use of feedback collection for improvement |
Forum for mapping problems to available solutions (per city) |
Identify stakeholders / involvement to make big sensor/communication approaches happen |
Chattanooga- 360 degree light cameras with fiber for video- there is interest in collaboration |
GCTC- Document report of blueprint by March | |
Quality of life |
Identify data flows: -Who owns them? -Address security concerns -Privacy/conflicts -Application |
Sensor types: predictive, descriptive, timing |
Share emerging best solutions with other cities |
|||
Identify transportation root issues through data |
Determining energy needs of transportation infrastructure |
Adaptive network gateways to aid in city transportation |
Coming together doesn’t stop existing actions in lone transportation clusters |
|||
Data-driven transportation system |
Identify trade-offs of a robust sensor system |
Look at solvable issue and then hardware solution |
Identify city resources - how? |
|||
What technology challenges exist and who can help solve? |
How do we use hardware efficiently - build, re-use infrastructure? |
Send email with invite to Google group |
||||
Need to consider what solutions will be available when (5G) and other future solutions arrive - how do we stay ahead of the curve? |
Consider approaches for extreme scenarios (EMP) |
Identifify sub-work groups and have virtual report outs following sub-group meetings |
||||
Vulnerability analysis - what's the backup plan? |
||||||