Specifications.docx

Requirements for permanent, retractable shelter for a large robot The National Geodetic Survey (NGS) operates a field-based, outdoor GNSS antenna calibration facility at its Corbin, VA location. Outdoor antenna calibration requires that the antenna be mounted on the end of a robotic arm, in such a way that the antenna has an unobstructed view of the sky for observing satellite signals. Furthermore, the antenna must be located away from large reflecting objects (e.g. metal roofs, sides of buildings, fences) which may generate erroneous reflected signals.

NGS is separately purchasing a large industrial robot for the absolute antenna calibration program. This class of robot is not rated for outdoor use, and NGS will restrict operations to periods when environmental conditions (temperature, humidity, rain, wind) are within specification. However, there will be lengthy non-operational periods when the robot must be protected from environmental conditions when not in use. The robot will be permanently affixed to a concrete pad and cannot be simply warehoused when not in operation.

Therefore, NGS seeks a sheltering structure that can be permanently mounted over the robot. To be useful for the intended purpose, the shelter structure must meet the following requirements:

· Structure must be motorized so it can be opened and closed from a Windows10 PC via software commands.

· The structure can be opened or closed manually, in the event of a power failure.

· Open configuration:

· When open, the structure must provide a fully unobstructed view of the sky for 360 deg azimuth; a structure with a single “door” opening is insufficient

· To provide adequate clearance for the robot’s operations, the structure must retract so that all parts of the structure are less than 55” off of the ground.

· To avoid creating unnecessary surfaces which generate unwanted reflected signals, the structure should fully retract and should not have any flat surfaces which remain visible during operations (such as a slide-off roof)

· Closed configuration:

· To protect the robot from environmental conditions which are out of specification, the structure must be weather-proof, capable of sustaining high winds, driving rain, and snow loads.

· To make it possible to maintain suitable environmental conditions of the interior when closed, the structure must be capable of retrofitting for later addition of an environmental control unit, if necessary, and have adequate seals.

· To provide adequate room for housing the robot, the *minimum* interior dimensions shall be 100” horizontal and 90” vertical.

· The structure must be designed so that it can be permanently affixed to a concrete pad with dimensions 12’ x 12’

· Structure should be of clamshell design and have no flat surfaces to minimize surfaces that can generate reflected signals. A dome configuration would be an ideal shape.

See attachment A., for a dimensions sheet for the Kawasaki RS050N robot, which is typical of the type of robotic arm that will be housed in this structure. These dimensions are provided to help potential quoters determine if their structure will allow operations as specified above.

The contractor shall only supply hardware and software and product license and will not require the use of any contractor owned equipment. The contractor will not have remote access to any government owned equipment. The contractor shall ensure the hardware and software provided disables “phone home” or similar capabilities.

The contractor shall include the necessary product support and supporting documentation for the hardware and software that allows the sanitization (following NIST Special Publications 800-88 Guidelines for Media Sanitization, http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-88r1.pdf) of the hardware and software upon the disposal of the product.

The contractor shall provide sufficient document demonstrating the software being provided complies with Office of Management and Budget Memorandum M-07-18 entitled Ensuring New Acquisitions Include Common Security Configurations and the FAR 39.101(d) regulations involving NIST common security configuration checklists including United States Government Configuration Baseline (USGCB) initiative. More information is available at National Checklist Program (NCP), (http://checklists.nist.gov), is the U.S. government repository of publicly available security checklists (or benchmarks) that provide detailed low-level guidance on setting the security configuration of operating systems and applications.

The contractor shall provide sufficient documentation which demonstrates the acquiring information technology has implemented common security configurations. Common security configurations are available from the National Institute of Standards and Technology’s website at http://checklists.nist.gov.

The contractor shall ensure that the product being purchased complies with the Homeland Security Presidential Directive 12 (HSPD-12) requirements from FAR 4.1302 stating: (a) In order to comply with FIPS PUB 201, agencies must purchase only approved personal identity verification products and services. (b) Agencies may acquire the approved products and services from the GSA, Federal Supply Schedule 70, Special Item Number (SIN) 132-62, HSPD-12 Product and Service Components, in accordance with ordering procedures outlined in FAR Subpart 8.4.

The contractor shall ensure that the product being purchased complies with Internet Protocol Version 6 (IPv6) requirements from FAR part 11.002 requirements which state that unless the agency Chief Information Officer waives the requirement, when acquiring information technology using Internet Protocol, the requirements documents must include reference to the appropriate technical capabilities defined in the USGv6 Profile (NIST Special Publication (SP) 500-267- http://www.nist.gov/itl/antd/usgv6.cfm) and the corresponding declarations of conformance defined in the USGv6 Test Program (http://www-x.antd.nist.gov/usgv6/index.html). To meet this requirement each DOC acquisition of IP protocol technology must express requirements for IPv6 capabilities in terms of the USGv6 Profile (i.e., using the USGV6 Capabilities Check List) and vendors must be required to document their product’s support of the requested capabilities through the USGv6 test program (reference http://www.antd.nist.gov/usgv6/) using the USGv6 Suppliers Declaration of Conformity.

The contractor shall provide sufficient document demonstrating the software being provided meets the following:

1) The standard installation, operation, maintenance, updates and/or patching of software shall not alter the configuration settings from the approved USGCB/other secure configuration.

2) Applications designed for normal end users shall run in the standard user context without elevated system administration privileges.

The contractor shall provide all supporting documentation or a reference to obtain the necessary material which describes the security capabilities, the design and development processes and the testing and evaluation procedures used by the product or services being provided for this acquisition. The contractor must provide all supporting documentation or a reference to obtain the necessary material which describes all product or service updates and enhancements as they are implemented. The product or service supporting documentation could be the user and system administrator guides, which is documents the functional properties of the security controls employed to permit the analysis and testing of the security controls.

If the vendor proposes the use of cloud services, NOS requires an integrated technical solution which meets the security requirements below. For any cloud services being used by the contractor to support this acquisition, the following conditions must be met:

a. Comply with DOC and NOAA Information Technology Security Policies;

b. Must use Cloud Services that are covered under the Federal Risk Authorization Management Program (FedRAMP; http://www.fedramp.gov/) ,

c. NOS IT Security Program and Program Office Information System Security Officer (ISSO) must review appropriate FedRAMP package(s) and conduct a risk assessment of the appropriate FedRAMP package(s) and associated cloud services prior to using any cloud service(s),

d. The use of the cloud services must have either received an NOS or NOAA Authorization to Operate (ATO) or have a NOAA or NOS approved risk acceptance for the pending ATO,

e. The contractor must provide the necessary information to support the documentation of the security posture (NIST Special Publications 800-53 Security and Privacy Controls for Federal Information Systems and Organizations) covering the contractor’s solution (the solution can consist of [mobile/web] application/ database/ network operating systems (aka, virtual machines)),

f. The contractor must ensure all NOAA information and contractor solution resides within the United States.

g. Integrate into DOC, NOAA and NOS enterprise solutions for systems management and incident management systems. Systems management and incident management examples include Enterprise Continuous Monitoring Operations (IBM Bigfix), enterprise logging/analysis (Arcsight), enterprise incident management, enterprise vulnerability management (Tenable Security Center), enterprise systems management (Microsoft Systems Center Configuration Manager/Redhat Satellite/JAMF Software Casper Suite), and enterprise endpoint anti-virus/anti-malware management (Intel McAfee ePolicy Orchestrator). If integration is not possible, vendor working with the government-identified Information System Security Officer must obtain a risk acceptance from Authorizing Official and Co-Authorizing Official.

Provide Government with full administrative control to the master account, subscription administrator or its equivalent. A master account, subscription administrator is defined as a highest (or root) privileged level access mechanism that has control over the information technology resources residing within the cloud subscription/boundary assigned to this contract. The Contractor will ensure that only the activities supporting this contract reside within the master account, subscription administrator or its equivalent. The Contractor must relinquish all administrative control and/or access to resources residing within the cloud subscription/boundary assigned to this contract. The Government may grant access to the Contractor as needed.