RFQ Issued Date:
14 February 2013
RFQ Written Comments
due: 5pm EST on 21 February 2013
Proposals Due Date:
5pm EST on 4 March 2013
Go Directly to the Request for Quotation Document
Go Directly to the Request for Quotation Clarifications
Overview
The Open
Geospatial Consortium (OGC®) has issued a Request for Quotations/Call for
Participation (RFQ/CFP) to solicit proposals in response to requirements for the
OGC Geo4NIEM Project. The Geo4NIEM Initiative will result in recommendations to
enhance the geospatial capabilities within the National Information Exchange
Model (NIEM). Sponsors have identified specific Information Exchange Packages
(IEPs) from Department of Homeland Security (DHS), Justice/Law Enforcement
domain, and the Maritime domain as representative examples for investigation in
this initiative.
The
RFQ/CFP is available below. Deadline
for submitting questions on the RFQ/CFP is 5pm EST on 21 February 2013. Responses are due by 5 pm EST on 4 March
2013.
The Point
of Contact is Lew Leinenweber: techdesk [at] opengeospatial [dot] org (techdesk [at] opengeospatial [dot] org).
Geo4NIEM
Initiative sponsors are:
- Program
Manager – Information Sharing Environment (PM-ISE)
- National
Information Exchange Model – Program Management Office (NIEM PMO)
The focus
of Geo4NIEM project will be to address requirements in the context of the
following information exchange domain areas:
Justice/Law
Enforcement. The Justice/Law Enforcement domain in NIEM is
defined by the Global Justice XML Data Model (Global JXDM). The Global Justice
XML Data Model (Global JXDM) is an XML-based framework that enables the US justice
and public safety communities to effectively share information at all levels.
Maritime
Domain Awareness. The Maritime domain supports the effective
understanding of anything associated with global maritime that could impact the
United States' security, safety, economy, or environment. NIEM facilitates this
understanding through effective, timely sharing of vital, secure information
among many key partners by representing vessels, people, cargo, and
maritime locations and activities.
The
Geo4NIEM Project has been organized to address specific functional requirements
to meet the following objectives:
- Develop
recommendations for the inclusion and standard use of embedded GML with NIEM
IEP documents (IEPDs).
- Develop
recommendations for the standardized use of Naming and Design Rules and the use
of adaptors (e.g. NIEM wrapper for GML).
- Test and
demonstrate use of a standardized embedded GML and adaptors within NIEM IEPDs.
- Develop
Architecture documentation and a fact sheet for the use of embedded GML and
adaptors for use with NIEM IEPDs.
- Develop
Recommendations for the inclusion of a Geospatial Domain within NIEM.
Click a link below to download individual files or a
complete package for the RFQ/CFP.
DOWNLOAD RFP/CFP
PACKAGE (as .zip archive)
Complete Geo4NIEM RFQ/CFP (pdf zip format)
Complete Geo4NIEM RFQ/CFP (doc zip format)
INDIVIDUAL FILES
Geo4NIEM RFQ Main Body (pdf)
Geo4NIEM RFQ Main Body (doc)
Geo4NIEM RFQ Annex A (pdf)
Geo4NIEM RFQ Annex A (doc)
Geo4NIEM RFQ Annex B (pdf)
Geo4NIEM RFQ Annex B (doc)
RFQ/CFP RESPONSE
TEMPLATES (not included in above package)
Geo4NIEM RFQCFP Template Proposal (doc)
Geo4NIEM Template Spreadsheet (xls)
QUESTIONS:
Prospective bidders are invited to submit written questions
by email regarding the RFQ to the OGC Technical Desk email address here:
techdesk [at] opengeospatial [dot] org.
CLARIFICATIONS
Response to questions and any other clarifications are
posted here:
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists [dot] opengeospatial [dot] org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template