IMIS IoT

OVERVIEW

On 22 April 2015 the Open Geospatial Consortium (OGC®) issued a Request for Quotations/Call for Participation (RFQ/CFP) for the OGC Incident Management Information Sharing (IMIS) Internet of Things Pilot (IoT) Pilot – called IMIS IoT. This Pilot will prototype and demonstrate standards-based approaches to address a series of challenges that hinder effective use of large numbers of diverse sensors for use in emergency response and disaster response situations.

Technical requirements for this initiative is described in detail in Annex B of the RFQ/CFP found on the OGC Requests page here:

http://www.opengeospatial.org/standards/requests/133

SCHEDULE

Key events and milestones for the IMIS IoT initiative are shown in the following table
 

Schedule Event / Milestone

Date

RFQ/CFP Issued

22 April 2015

RFQ/CFP Questions due for Webinar

1 May 2015

Prospective Bidder’s Q&A Webinar

4 May 2015

Deadline to submit questions on RFQ/CFP to OGC

11 May 2015

Proposals due to OGC

22 May 2015

Project Kickoff Workshop

9-10 July 2015

Project Plan refined following Kickoff Workshop

17 July 2015

Draft reports complete

6 November 2015

Capability development and Interim Demonstrations complete

22 December 2015

Conduct final demonstration

11 January 2016 (e)

Springboard Test Environment setup complete

15 January 2016

Final reports complete

29 January 2016

Project end date

1 February 2016

(e) – Estimated date subject to modification

SPONSORS

  • US Department of Homeland Security (DHS) Science and Technology (S&T)
  • The IJIS Institute

CONTEXT of IMIS IoT Pilot

Incident responders move within a field of operation. The goal is to characterize the environment of the field as efficiently and safely as possible. For this reason, response teams make use of modern sensing and communications technology to achieve two domains of awareness:

  • The situation in the field of operation and vicinity
  • The status of each response team member and response resource.

Sensors used for incident response may be deployed for use or carried by response team members. Deployed sensors can either be fixed or mobile, e.g. carried by individual responders, autonomous vehicles, or drones. Fixed sensors remain at a deployment location, but might have the capability to be quickly relocated and re-integrated if necessary. Sensor platforms include communications functionality; they may provide relay and data collection functionality as well. Wearable sensors may provide environmental information but primarily monitor the biometric conditions of each team member. 

NOTIONAL SYSTEM DESIGN

An implementation architecture and deployed system design for incident management sensor “Things” will be developed, refined, and documented during the course of the pilot activity based on the pilot scope, the capabilities of the selected pilot participants, and the needs of the agreed upon target response scenario and associated use cases. An initial system design solution is shown below. For more information about the technologies, number of components, and type of sensors to be implemented for the pilot refer to the RFQ/CFP Annex B. This design depicts the manner in which relevant components are to be connected to provide the “just works” functionality for incident responders that the Pilot aims to demonstrate.

RFQ/CFP Documents

  • Main Body
  • Annex A (Interoperability Program Process Framework, WBS, Concept of Operations, Communications Plan, Code of Conduct)
  • Annex B (Technical Requirements and Architecture)

Bidder’s Quick Start Guide

This section provides a short roadmap for navigating the RFQ and as a guide for organizations that have no previous OGC initiative experience in order to reduce the time required to respond, and feel more confident that their responses fulfill the requirements of the RFQ. However, this section should not be seen as a replacement for any of the material found in the official RFQ/CFP.

Step 1: Read the Response Templates

First understand what your response should look like by reviewing the two response templates OGC provides.

  • Technical contribution -- what you plan to do
  • Cost Estimating template (spreadsheet) (whether you are requesting cost share funding or only proposing in-kind)

Step 2: Study the Technical Requirements (Annex B)

The work to be performed in the initiative is described in the Annex B. You may propose to contribute to as many of the requirements as you would like; you are not expected to propose to provide all requirements in Annex B. Furthermore, you may propose to provide any of the deliverables that best suit your expertise or interests.

Step 3: Review Annex A

Annex A provides important information about how the OGC Initiative process works and what will be required of you if selected. You should be aware of this information and adhere to those guidelines if you are selected to participate in the project.

Step 4: Ask Questions - Register for the Bidder's Q&A Webinar

  • Submit questions by email to: imis-iot-responses [at] opengeospatial.org
  • Register and attend the Q&A Webinar (see RFQ/CFP Request page for additional details)

Date: 4 May 2015, 1000-1130 am EDT - check your local time here:  http://www.timeanddate.com/

Registration required (see Initiative Request page) 

  • Review the Clarification document (link forthcoming after the Q&A Webinar)

Step 5: Respond

Follow the instructions the RFQ/CFP Main Body (especially Section 6: Proposal Submission Information) to submit your response.

The IMIS IoT RFQ/CFP, Response Templates and related information can be found on the Initiative Request page located here:

http://www.opengeospatial.org/standards/requests/133