I3 Consortium Action Cluster: Difference between revisions

From OpenCommons
Jump to navigation Jump to search
No edit summary
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 13: Line 13:
|challenges=Communities are currently approaching smart cities deployments as a series of siloed structures.  It is difficult to turn silos into networks which allow data to be leveraged between known and future applications and devices.
|challenges=Communities are currently approaching smart cities deployments as a series of siloed structures.  It is difficult to turn silos into networks which allow data to be leveraged between known and future applications and devices.
|solutions=I3 injects a user-directed routing system between silos so individual data streams can be managed (activated, deactivated, etc) over time as devices, applications, and services evolve over time.
|solutions=I3 injects a user-directed routing system between silos so individual data streams can be managed (activated, deactivated, etc) over time as devices, applications, and services evolve over time.
|requirements=Create open consortium operational framework that allows wide range of participants in the program
|requirements=*Create open consortium operational framework that allows wide range of participants in the program
Prioritize features from master requirements and contributed proof-of-concept development efforts
*Prioritize features from master requirements and contributed proof-of-concept development efforts
Schedule beta development/integration efforts and testing in operational settings
*Schedule beta development/integration efforts and testing in operational settings
Release demonstration/field trial software for consortium level testing
*Release demonstration/field trial software for consortium level testing
Release opensource software for general availability
*Release opensource software for general availability
|kpi=The goal of I3 is to increase the leverage of IOT device data within a city or some other smart community.  For example, if a single IOT device can drive 2 applications instead of one, it means the IOT device and deployment costs can be amortized over two applications instead of one.  In some situations, this means the city does not have to reinvest in dedicated IOT devices for the second application.  The greater the leverage ratio, the lower the justification threshold (and possibly funding requirement).
|kpi=The goal of I3 is to increase the leverage of IOT device data within a city or some other smart community.  For example, if a single IOT device can drive 2 applications instead of one, it means the IOT device and deployment costs can be amortized over two applications instead of one.  In some situations, this means the city does not have to reinvest in dedicated IOT devices for the second application.  The greater the leverage ratio, the lower the justification threshold (and possibly funding requirement).
|measurement=Costs can be be modeled for an siloed approach to IOT and these costs can be compared to an I3-centric network approach.
|measurement=Costs can be be modeled for an siloed approach to IOT and these costs can be compared to an I3-centric network approach.
Line 24: Line 24:
|impacts=I3 will allow IOT related expenses by the city to be minimized by providing a managed tool to that increases the leverage ratio of IOT investments.  This same technology also makes more data available to applications and thereby increases their overall potential feature set (intelligence).
|impacts=I3 will allow IOT related expenses by the city to be minimized by providing a managed tool to that increases the leverage ratio of IOT investments.  This same technology also makes more data available to applications and thereby increases their overall potential feature set (intelligence).
|demonstration=We are planning to have a working demonstration system (with some limits on application and device support) ready for demonstration in late 2018.  General availability is expected for R1.0 of the system in 2019.
|demonstration=We are planning to have a working demonstration system (with some limits on application and device support) ready for demonstration in late 2018.  General availability is expected for R1.0 of the system in 2019.
|chapter=Open Data
|supercluster=Data
|supercluster=Data
|year=2018, 2019
|year=2018, 2019
|tag=Open Data
|title=I3 Consortium Action Cluster
|title=I3 Consortium Action Cluster
|replicability=The I3 project will be released as opensource software allowing the efforts of the I3 Consortium to be replicated by others upon general availability.
|replicability=The I3 project will be released as opensource software allowing the efforts of the I3 Consortium to be replicated by others upon general availability.
}}
}}

Latest revision as of 23:53, January 24, 2023


I3 Consortium Action Cluster
GCTC logo 344x80.png
I3Header.png
I3 Consortium
Team Organizations 21iqlabs
Acad
Adwayusa
Affirma
Amazon
Arcortex
Atlastekgroup
Aurigontech
Avata
Binghamton
CDW
CHLA
Cisco
City of Pasadena
CMI
Consensys
Coral Gables
Cradlepoint
DCC
Discoveryiot
Dps
Dsg
Eandt Strategies
EMtruth
Ericsson
ESRI
ETCenter
Etcusc
Ether2
EY
Fantasmo
Fic
Helium
I3-iot
Indigostrat
INRIA
IOTA
ISI
Kaspect
Kiana Analytics
Korea University
Konectcity
Kotra Dallas
KPMG
Long Beach
Marshall
Melrok
Mimocloud
Metro
Microsoft
Neo Technology
Netobjex
Niksun
Nokia
Nutanix
Oracle
Orange Barrel Media
Pacbell
Penta Security
Prgs
Price
Process Intel
Profound-tech
Quaychain
Rdsea
Rossier
Safeenv
Samsung
SCAG
Smartlink
Smartp3
Sprint
Stellangigi
SustainOC
Syncromatics
Tech Mahindra Telus
T-mobile
Traction-Labs
Urban-California
USC
USD group
Valarm
Vdms
Verizon
VHH
Walker Real Estate Advisors
Warnerbros
WDC
Wearabouts
Wizr
WWT
Zetta Advisory
Team Leaders Jerry Power
Participating Municipalities Los Angeles CA
Las Vegas NV
Status Concept only Stage
Document Download

Description

The I3 project is creating a tool that will allow independent device owners to directly manage how the data streams from their IOT devices are delivered to applications. Opensource Project software includes support for privacy, trust, and incentive management.

Requirements and proof-of-concepts complete. Consortium management structure in process. Demonstration systems in process. R1.0 beta software in design.

Challenges

Communities are currently approaching smart cities deployments as a series of siloed structures. It is difficult to turn silos into networks which allow data to be leveraged between known and future applications and devices.

Solutions

I3 injects a user-directed routing system between silos so individual data streams can be managed (activated, deactivated, etc) over time as devices, applications, and services evolve over time.

Major Requirements

  • Create open consortium operational framework that allows wide range of participants in the program
  • Prioritize features from master requirements and contributed proof-of-concept development efforts
  • Schedule beta development/integration efforts and testing in operational settings
  • Release demonstration/field trial software for consortium level testing
  • Release opensource software for general availability

Performance Targets

Key Performance Indicators (KPIs) Measurement Methods

The goal of I3 is to increase the leverage of IOT device data within a city or some other smart community. For example, if a single IOT device can drive 2 applications instead of one, it means the IOT device and deployment costs can be amortized over two applications instead of one. In some situations, this means the city does not have to reinvest in dedicated IOT devices for the second application. The greater the leverage ratio, the lower the justification threshold (and possibly funding requirement).

Costs can be be modeled for an siloed approach to IOT and these costs can be compared to an I3-centric network approach.

Standards, Replicability, Scalability, and Sustainability

The I3 project is an opensource project with the expectation that the I3 consortium members will provide software drivers (standard and non-standard) needed to support their devices and applications.

Cybersecurity and Privacy

The I3 system is a real-time IOT traffic management that distributes data in accordance with IOT device owner directives. Device owners can change their directives at any time. Permission from users, based on requests from applications, are based on recorded opt-in instructions. I3 also plans a real-time security feature that alerts on detection of misbehaving devices.

Impacts

I3 will allow IOT related expenses by the city to be minimized by providing a managed tool to that increases the leverage ratio of IOT investments. This same technology also makes more data available to applications and thereby increases their overall potential feature set (intelligence).

Demonstration/Deployment

We are planning to have a working demonstration system (with some limits on application and device support) ready for demonstration in late 2018. General availability is expected for R1.0 of the system in 2019.