Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF MARCH 27, 2009 FBO #2678
SPECIAL NOTICE

70 -- Notice of Intent Joint Mapping Tool Appliance - Notice of Intent

Notice Date
3/25/2009
 
Notice Type
Special Notice
 
NAICS
541512 — Computer Systems Design Services
 
Contracting Office
Other Defense Agencies, United States Transportation Command, USTRANSCOM Command Acquisition, 508 Scott Drive, Bldg 1900, Scott AFB, Illinois, 62225, United States
 
ZIP Code
62225
 
Solicitation Number
HTC711-09-0008
 
Point of Contact
Scott B. Amos, Phone: 6182294925, Carey N Gropp,, Phone: 618-229-2469
 
E-Mail Address
scott.amos@ustranscom.mil, carey.gropp@ustranscom.mil
 
Small Business Set-Aside
N/A
 
Description
Notice of Intent United States Transportation Command (USTRANSCOM) Notice of Intent to Award on a Sole Source Basis THIS IS A NOTICE OF INTENT TO AWARD ON A SOLE SOURCE BASIS ANNOUNCEMENT, A MARKET SURVEY FOR INFORMATION ONLY. THIS IS NOT A REQUEST FOR PROPOSAL OR QUOTE. PLEASE DO NOT REQUEST A COPY OF A SOLICITATION, AS ONE DOES NOT CURRENTLY EXIST. NO REIMBURSEMENT WILL BE MADE FOR ANY COSTS ASSOCIATED WITH PROVIDING INFORMATION IN RESPONSE TO THIS SYNOPSIS OR ANY FOLLOW-UP INFORMATION REQUESTS. THE PURPOSE OF THIS ANNOUNCEMENT IS TO ACCESS THE MARKET’S CAPABILITY AND TO GAIN KNOWLEDGE OF POTENTIAL VENDORS. 1.) USTRANSCOM Contracting Office intends to solicit on a sole source basis under the authority of FAR 6.302-1, Only One Responsible Source and No Other Supplies or Services Will Satisfy Agency Requirements. At this time, the Government knows only one source that is capable of meeting the Governments requirements, as follows: a.) USTRANSCOM J3/CIP and SDDC/TEA-SA have a requirement to develop an enterprise Geographic Information System (GIS) framework on the Secure Internet Protocol Router Network (SIPRNET) that would support the production and dissemination of relevant TCJ3-FC Critical Infrastructure Program (CIP) data to USTRANSCOM and Defense CIP (DCIP) stakeholders. The Enterprise GIS framework must provide CIP users with a geospatial data storage and production environment with the ability to publish CIP geospatial data and analysis results for dissemination to other USTRANSCOM personnel and DCIP partners. The system shall allow CIP users to store and produce GIS data and geospatial analysis products using geospatial analysis software (e.g. ArcGIS Desktop). b.) CIP users must have the capability to publish a Web Map Service (WMS) and Web Feature Service (WFS) that provides USTRANSCOM CIP data to TCJ3-FC approved users and systems within USTRANSCOM and the DCIP community. Customers requiring CIP data may include, but not be limited to, the Strategic Mission Assurance Data System (SMADS), the National Geospatial-Intelligence Agency’s (NGA) Palanterra, and the Mission Assurance Division’s Homeland Defense Mission Assurance Portal (HD-MAP). The system shall allow users to publish a WMS and WFS that provides the NGA’s base-map data and imagery for areas of interest worldwide for use by ArcGIS Desktop users. The base-map/imagery WMS/WFS shall support geospatial analysis capabilities and map production throughout the Command. These web services shall allow users to access to the Vector Map (VMAP) and Urban VMAP (UVMAP) data, imagery from the Commercial Satellite Imagery Library (CSIL), and the Homeland Security Infrastructure Program (HSIP) 133 Cities Imagery, in addition to other NGA-acquired commercial data sources worldwide (e.g. NAVTEQ streets, points of interest, and land use). In addition, users of the system, at a minimum, require the following system capabilities: c.) Incorporate elevation data such as Digital Elevation Models (DEM), Digital Terrain Elevation Data (DTED), and Light Detection and Ranging (LiDAR) products. d.) Publish a metadata catalog that allows personnel to search USTRANSCOM GIS data holdings, to include CIP data. The metadata catalog should also provide a data download capability (in multiple formats – i.e. text, Excel, shapefile, Personal Geodatabase). e.) Incorporate hazard model data such as the Defense Threat Reduction Agency (DTRA) Hazard Prediction and Assessment Capability (HPAC), the Consequences Assessment Tool Set (CATS), and the Integrated Weapons of Mass Destruction Toolset (IWMDT). f.) Incorporate weather data from the Air Force Weather Agency (AFWA) and the Naval Meteorology and Oceanography Center to include weather radar data, meteorological satellite imagery, weather forecast model data, and hurricane/tropical storm tracks and wind fields. g.) Incorporate natural hazard information to include earthquake, hurricane, flood, volcano, and wildfires. This should include, but not be limited to, natural hazard risk data from the Department of Transportation (DOT)-sponsored Natural Disaster Study by the Federal Emergency Management Agency. h.) Allow navigation controls that allow for zooming and panning of world-wide map displays. i.) Layer display controls that allow users to select and de-select the visible layers in the map display. j.) Search and filter the data layers by attributes on all the available data fields. k.) Search and filter the data layers by geographic location, user-defined extents, and proximity to features from other data layers. l.) Select map features to identify and view the associated attribute information. m.) Enable tooltips so information can be displayed for select map features when moused-over. n.) Enable hyperlinks to additional information (such as CIP reports, intelligence reports, and threat assessments) when clicked on in the map display. o.) Define buffer areas and geo-fence based on a data layer and/or feature. For example, a user should be able to select oil pipeline features of interest and define a buffer area and/or geo-fence around those features. p.) Perform distance and area measurements from within the map interface. q.) Generate multi-modal routes based on user-defined start and end point locations. r.) Determine multi-modal re-routes based on user-defined avoidance and hazard areas. Display location coordinates in multiple geographic and projected coordinate systems to include the World Geodetic Coordinate System of 1984 (WGS84) (in decimal degrees and degrees minutes seconds), Universal Transverse Mercator (UTM) Grid, Military Grid Reference System (MGRS), and the United States National Grid (USNG). s.) Incorporate worldwide earthquake information from the United States Geologic Survey, including all the data fields available from the USGS M2.5+ Earthquakes Atom feed. The fields include the earthquake event id, magnitude, region, date/time, latitude/longitude, depth and URL to the USGS specific event page. Historic significant earthquakes should also be included. t.) Incorporate wildfire information from the Geospatial Multi-Agency Coordination (GeoMAC) Team. The wildfire information should include the current fires, current fire perimeters, all fires/perimeters for the current year, and historic fires/perimeters. u.) Integrate tsunami information from the National Oceanic and Atmospheric Administration Historical tsunami events. v.) Incorporate current and forecast flooding information from the National Weather Service (NWS) Advanced Hydrologic Prediction Services (AHPS). w.) Incorporate natural hazard risk data from the Department of Transportation (DOT). These datasets include earthquake, hurricane, flood, and landslide hazard information from the Federal Emergency Management Agency’s Natural Disaster Study. x.) Integrate the natural hazard layers from the latest Homeland Infrastructure Security Program (HSIP) Gold dataset. These layers include the following seismic hazards, earthquake fault lines/zones, historical tropical storms, landslides, volcanoes, and tornado touchdown points. y.) Users must be able to search and filter natural hazard information by attributes and location. The ability to define a buffer area and geo-fence based on a specific natural hazard event is required. For example, in the event of a significant earthquake, users must be able to define a geo-fence of a specific distance from the earthquakes’ epicenter to be notified of shipments moving into the affected area. z.) Classified as Limited Distribution (LIMDIS) by DoD Information Security Program, in compliance with and in implementation of Executive Order 12356, "National Security Information," Information Security Oversight Directive No. 1. National Security Information" (32 CFR Part 2001). 2.) The Government intends to acquire a commercial item using FAR Part 12. Interested organizations may submit their capabilities and qualifications to perform the effort in writing to the identified point of contact. Such capabilities/qualifications will be evaluated solely for determining whether or not to conduct this procurement on a competitive basis. A determination by the Government not to compete this proposed effort on a full and open competition basis, based upon responses to this notice, is solely within the discretion of the Government. Be advised that this notice does not constitute an obligation upon the Government to pursue any follow-on contract action, in part or whole, with potential vendors. All interested sources must respond to this Notice of Intent by 2:00pm, Central Standard Time, on 8 April 2009. E-Mail responses to Mr. Scott Amos scott.amos@ustranscom.mil. If you have any questions, please call Mr. Scott Amos at (618) 229-4925.
 
Web Link
FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=a6ee5ccf00f88cbbbb48f490484d06a4&tab=core&_cview=1)
 
Place of Performance
Address: 508 Scott Drive, Scott AFB, Illinois, 62225-5357, United States
Zip Code: 62225-5357
 
Record
SN01777507-W 20090327/090325220136-a6ee5ccf00f88cbbbb48f490484d06a4 (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  © 1994-2020, Loren Data Corp.