Draft CWMD RPM Deployment Statement of Work.pdf

STATEMENT OF WORK

(SOW)

Radiation Portal Monitor Program (RPMP) Deployment Contract for

U.S. Department of Homeland Security

Countering Weapons of Mass Destruction (CWMD) Office

Acquisition Directorate

February 2020

Contents

STATEMENT OF WORK (SOW)

1. OBJECTIVE

2. SCOPE OF WORK

A. General Scope

3. BACKGROUND

4. REQUIREMENTS

4.1. Program Management and Integration

4.1.1. Program Management Plan

4.2. Ancillary Equipment to support Remote Operations

4.3. Deployment/Decommissioning of RPMs

4.4. Deployment, Installation and operations support

4.5. Human Machine Interface (HMI) and Programmable Logic Controller (PLC) Requirements

4.6. Graphical User Interface (GUI) Integration

4.7. Deployment, scheduling and cost estimates

4.8. Site Survey

4.9. Design Processes

4.10. Design Engineering

4.10.1. Standard Designs

4.10.2. Customized or Site-Specific Design Engineering

4.10.3. Design Management and Oversight

4.10.4. Design Reviews and Engineering Surveys

4.11. Construction Management

4.11.1. Construction Quality, Health and Safety

4.12. Equipment Delivery and Installation

4.13. Commissioning

4.14. Decommissioning

4.15. Site Closeout

4.16. Decommissioning of Low Use/No Use Systems

4.17. Training Material Support

4.18. Inventory Management

4.19. Technical data

4.20. Configuration Management

4.21. Program Integration

4.22. Program Websites and Information Technology

4.23. Logistics

4.23.1. Import/Export Control Licenses

4.23.2. Shipping, Packaging, and Storage in Continental United States (CONUS) and Outside Continental United States (OCONUS)

4.23.3. Management of Government Furnished Property, Radiation Portal Monitors

4.23.4. Translation and Interpreter Services

4.23.5. OCONUS Host-Country Logistics

4.24. Inspection, Testing and Turnover

4.25. Warehouse

5. DELIVERABLES

6. Other Contract Details

6.1. Place(s) of Performance

6.2. Period of Performance

6.3. Funding Requirements

6.4. DHS Furnished Information

6.5. Special Requirements

I. Points of Contact

II. Applicable Documents

1. OBJECTIVE

The objective of this acquisition is for the Countering Weapons of Mass Destruction Office (CWMD) to execute the programmatic radiation portal monitor (RPM) deployment roles and responsibilities. This acquisition provides CWMD the capability to deploy and install radiation detection and related systems at points of entry into the US and other locations identified by Department of Homeland Security (DHS) that addresses capability gaps in four areas: radiological/nuclear (R/N) detection on-site process inefficiencies, R/N alarm adjudication process inefficiencies, R/N detection technology performance limitations, and rapidly degrading/aging R/N detection and support equipment.

While CWMD funds and executes research and development projects through national laboratories and research organizations, the CWMD radiation portal monitor program (RPMP) continues to provide the framework and capability to execute acquisition and deployment activities required to field radiation scanning and interdiction systems across the five vectors in accordance with legislative mandates as well as global architectural and operational requirements. The fielded systems are required to meet government standards for scanning and interdiction of illicit radioactive materials and to minimize the hinderance to legitimate trade and travel.

The focus for this acquisition is on the deployment activities of radiation portal monitoring solutions across the following vectors:

1. Land Borders (including ferry crossings)

2. Seaports

3. International Airports

4. Preclearance Airports (passenger/bags)

5. International Mail and Express Consignment Courier Facilities (ECCF)

6. Railroad Crossings

2. SCOPE OF WORK

A. General Scope

The contractor shall perform the tasks described in this statement of work (SOW). CWMD is procuring from the contractor the following deployment services, which are described in greater detail in Section 4.

RPM deployment sites will vary by vector, the number and type of RPMs needed by site, and the annual frequency of deployments per the RPMP priority list. The duration for a deployment varies and can extend over fiscal and calendar years. There is no standard time for a deployment. Most deployments will be completed using a design-build delivery method within a twelve-month period. Other RPM deployments that are complicated or requiring extensive coordination may take longer. Most sites are previously developed with infrastructure (i.e., previously designed locations with infrastructure that typically do not require soil borings, environmental assessments, and similar field investigations).

Program Element/Project Major Tasks Key Milestones and Deliverables

Program Management Program and sub-contract management for RPM deployments.

Monthly Status Reports

Radiation Detection Equipment (RDE) Infrastructure and Coordination

Provide the system infrastructure (e.g., historical information, technical data, and access for CWMD) to other DHS RDE projects. Maintain appropriate technical and operational databases.

Access to capability and information and submission of analytical and other reports as required

RDE Planning Support Strategic and Operational Planning for RPMP and related RDE activities.

Development of intermediate and long-term plans to support acquisition, deployment, and operations of RPMs.

Deliverables as requested

Determine modern system components

Identify and modernize system components such as Programmable Logic Controllers, Graphical User Interface Integration

Provide analysis of possible efficiencies

Deployment Execute RPM deployment, conduct site survey develop site designs, perform on-site construction, commission RPMs, perform site closeout, manage system configuration, perform system calibration, and develop schedules.

Survey Reports, Designs, Commissioning Documentation, Weekly Deployment Status Teleconference minutes, and Schedules

Site Surveys Determine and validate project requirements.

Conceptual design and site survey report; Survey Reports include background radiation effects

Design Determine RPM deployment design that includes engineering such as soil borings, environmental assessments

Produce 30%, 60%, 90% & 100% designs as required

Site Management Provide construction oversight for quality control and construction key milestones

Quality Control Report

Construction Install RPM systems and ancillary equipment

Daily Construction Execution Report and red line issued for construction

Functional Check Energize the RPM system to determine deployability

At warehouse

Calibration Ensure the algorithms and parameters of each system are within its associated detection capabilities

Allows RPM system to proceed to be commissioned

Commissioning Verifies all sub-processes are completed (training, operational readiness, calibration, and field acceptance testing)

Equipment list, Operations Manual, Training materials;

Ready for Go-Live and 48hr burn-in

Go-Live and 48hr burn-in Provide support for scanning cargo or vehicles to determine potential problems

CBP Acceptance

Decommissioning Remove unused and underused systems

RPM warehoused

Logistics (Inventory Management, packaging, and shipping)

Refurbish as necessary, store, maintain, check functionality at warehouse before shipping, and manage inventory of RPMs and ancillary equipment.

Inventory reports

The Contractor will perform the requirements necessary for installation of individual sites, support efforts including development of Concept of Operations (CONOPS), training and other initiatives as directed, provide Contractor's deployment management efforts including configuration management, logistics, and other management and oversight tasks as necessary. The work sought by the CWMD RPMP office shall be specified on an individual task order basis and issued by the Contracting Officer. A task order issued may incorporate multiple sites, regions, or other logical groupings. Additionally, Program-wide Task Orders will be issued to cover Program-level Management and other requirements that are not directly allocable to a single effort.

3. BACKGROUND

The Pacific Northwest National Laboratory (PNNL) has performed RPM deployment and installation since the beginning of the RPM program for CWMD, previously the Domestic Nuclear Defense Office (DNDO). PNNL will continue the RPM deployment and installation until the CWMD contract is in place. This statement of work (SOW) consist of capabilities for RPM site surveys, site designs, construction including site manager, ancillary equipment installation, calibration, commissioning, RPM acceptance from U.S. Customs and Border Protection (CBP), and a CWMD contract line item (CLIN) for RPM logistics including but not limited to shipping and warehousing of RPMs. CWMD’s intent is to have contract CLINs that can provide a complete and useable RPM lane including the ancillary equipment.

This intent requires unique resources, expertise, and flexibility.

4. REQUIREMENTS

The RPMP is required to field RPMs with the goal of effectively scanning containerized cargo, commercial conveyances, and Privately-Owned Vehicles (POV) entering the US for the presence of illegal or illicit radioactive materials. The configurations for equipment deployed for effective cargo scanning, as required by legislative and operational directives, should minimize impediments and adverse impacts to the flow of commerce.

The Contractor shall perform the following activities:

4.1. Program Management and Integration

The Contractor shall effectively manage its services to the CWMD RPM program, serve as the central coordinator and integrator for its site installation activities, and provide other services such as warehousing for the RPM program. The Contractor shall provide technical support for program planning activities such as the cause and effect results from system upgrades.

4.1.1. Program Management Plan

The Contractor shall prepare, for approval by the RPM Program Office, a Program

General Technical and Engineering

Investigate technical issues and provide technical support.

Technical Manuals and Technical Reports

Management Plan (PMP) to define its approach for managing work under this contract.

The Contractor shall develop procedures and associated processes for implementing the PMP. The specific requirements for the PMP shall be defined in a task order and will contain as a minimum:

a. Program organization of work/tasks via a work breakdown structure with a

WBS dictionary

b. Staffing and resource requirements

c. Organizational roles and responsibilities

d. Management of subcontractors

e. Management of foreign subcontractors

f. Quality Assurance

g. Quality Control

h. Design & Construction Submittal process

i. Design & Construction RFI process

j. Contract modification request process

k. Material management

l. Project controls and reporting for budget, accounting, and schedule

m. Export control licensing

n. Website structure and functionality

o. Management and reporting of cash flow/financing requirements

p. Invoicing

q. Risk Management

r. Training

s. Security

t. Site Access

u. Environmental, health, and safety

v. Hazard, hardship, and incentive fees

w. Property Management

4.2. Ancillary Equipment to support Remote Operations

The Contractor shall procure ancillary equipment in accordance with approved specifications, and CWMD guidance. Several ancillary equipment systems are used to support the operation of RPMs. These systems assist CBP in interdiction activities such as managing alarms for containers/vehicles, enabling remote operations, and helping to provide a safe and secure operational environment for the CBP officers. Operations of the terminal/port and site conditions dictate RPM deployment configurations. The following ancillary equipment systems may be employed at staffed and Remotely Operated sites:

1. Vehicle Identification System (VIS) Requirements: Each primary lane at seaport

RPM deployments will be equipped with VIS. The VIS provides a set of clear images to aid in identifying all vehicles and/or containers transiting through the RPM. It captures and transmits digital images as part of the information relayed from the RPM system to the CBP supervisor computer. Images of all containers/vehicles are stored for a preset period, while images of alarming containers/vehicles are maintained indefinitely as part of alarm records for the port and are included in archive data forwarded to PNNL for analysis. Overall, VIS improves CBP’s capability to 1) identify scanned containers/vehicles, and 2) provide information on “port runners” to other law enforcement agencies. Detailed guidance and specifications for the design and deployment of the VIS are provided in DD-063, RPM VIS Camera – Design, Installation, and Maintenance Guidance for IQ862NE Cameras. This document provides the necessary guidance to design VIS field deployments and prescribes only those elements necessary for the correct function of the components that support the RPM system. Key parameters include the following:

• location of cameras to identify vehicles and capture container numbers and other data (such as chassis number, driver identification, or license plate number)

• lighting, including location for effective performance and the minimum lighting to achieve sufficient intensity

• camera settings to optimize the capture of high-quality images

• key interface requirements, including control signals, power, and Ethernet connection.

2. Area Video Surveillance Requirements: Detailed guidance and specifications for the design and deployment of an area video surveillance system are provided in DD- 064, ASC – Design, Installation, and Maintenance Guidance for the ACUIX Analog PTZ High-Speed Dome Camera. The video surveillance system is an independent system providing remote closed-circuit television monitoring of the primary and/or secondary RPMs and the secondary inspection area or lay-down yards. Each camera is enclosed in protective housing and should be mounted to provide an unobstructed view of the RPMs or lay-down yard. The housing protects the camera and pan-tilt-zoom (PTZ) module from weather and may include a small heater.

Digital ASCs transmit video signals to a monitor in the CBP booth over the LAN.

PTZ cameras must be controllable from multiple locations via the RPM LAN Ethernet network. A network video recorder located in the CBP booth or another secure CBP location records video transmissions. Encryption hardware is required in the booth if there is a need for wireless video transmission. Wired transmission over fiber requires a fiber-to-copper converter (conversion may be achieved with a dedicated media converter or through an Ethernet switch). The surveillance system must be equipped with a motion- detection-based alarm feature to facilitate monitoring of unauthorized activities.

3. Intercom System Requirements: The intercom subsystem provides two-way communications between CBP staff in the booth and vehicle drivers at the primary RPM lanes. The system may transmit analog or digital voice data. The selection of an analog or digital system is dictated by site conditions and the proposed operational environment at the terminal/port.

Digital or Voice over Internet Protocol audio is transmitted over the RPM-RO LAN.

Lane intercom speaker’s units must be installed near the exit of each primary RPM lane. The lane speakers must be located so that a driver can easily access the speaker without having to exit the vehicle while stopped at the primary RPM lane gate arm or traffic light. The intercom control unit must be installed at the CBP booth or another secure CBP location. Location of the intercom control unit will be defined during the design process.

Lane intercom installation guidance follows:

• Signs must clearly identify the lane intercom.

• Intercoms must be installed at all primary RPMs, as necessary, downstream of the RPM near the gate arm or traffic light, if used.

• Pedestals to support lane intercoms should be designed for ruggedness and visibility.

4. Traffic Management System Requirements: The traffic management system consists of gate arms, traffic lights, signage, and pavement markings. A Programmable Logic Controller (PLC) and Human Machine Interface (HMI) are used to implement traffic control logic and provide both a convenient interface for CBP officers to control these features and a remote override control. A traffic light control signal consists of a red and green light, one per RPM-RO lane. The traffic control system directs the driver to proceed through the primary RPM lane exit if the green light is illuminated or to stop for further instructions if the red light stays illuminated. The signal must be clearly visible to the vehicle driver and mounted to avoid obstructing the driving lane. The red/green condition of the traffic light and the open/closed condition of the gate arms are shown on the HMI in the CBP booth.

5. Network Infrastructure: The portal monitors and VIS cameras communicate with the supervisor computer and monitor computers (if used) through network connections. At some ports, this will be a dedicated closed network. If the port is connected to the Port Radiation Inspection and Detection (PRIDE) system, the RPM components will be connected to each other through the CBP network. The network infrastructure at all RPM installations must be designed and installed in accordance with guidance provided by CBP OIT. This will ensure PRIDE compatibility and facilitate transition of the site to PRIDE in the future.

The various components are connected through Ethernet switches and Category 6 cable. Cable rated for outside plant use must be used in all locations where the cable may be exposed to water. Any outside plant Category 6 cable runs within a building must be limited to a maximum of 50 ft (15 m) unless encased in metal conduit. Also, when one end of a Category 6 cable is located outside (e.g., at an RPM) and the other end is in a building (e.g., in a LAN room or CBP booth), surge suppressors must be installed at both ends of the cable. Riser-rated cable must be used inside building spaces not considered air supply or return space. Whether or not an air space is part of the air handling system must be verified. Plenum-rated cable shall be used in air supply or return spaces. The maximum run length for Category 6 cable is 240 ft (73 m) for a single run. Ethernet switches must be used to change between cable types.

Category 6 cable may not be spliced. Fiber optic cable is to be used for all runs over 240 ft (73 m). The RPM system uses standard commercial Fast Ethernet switches and UPSs. The switches must be on the OIT approved list.

6. Optical Character Recognition (OCR) and Reconciliation Software: The OCR and reconciliation software are required at most seaport rail gate RPM deployments.

Rail gate RPM systems include a VIS to capture images of the containers as they pass through the RPMs. The VIS images are stored in the RPM8 SQL database along with the container scan data by the RPM8 system software. The containers are then loaded onto rail cars for transport to various destinations in the United States. Before CBP releases the containers for shipment, the rail Consist report is reviewed to verify that all containers were scanned by the RPM system. This Consist reconciliation can be performed manually; however, this is a time-consuming process. The OCR software that is deployed prepares and stores an alpha-numeric character string of the container identification numbers derived from the VIS images stored in the RPM8 database. The results of the OCR software are stored in the metadata field of the SQL database.

Detailed guidance and specifications for the deployment of the OCR and reconciliation software are provided in ED-053, Optical Character Recognition Software Requirements Specification, and in ED- 005, Optical Character Recognition and Consist Reconciliation Software Design Description.

7. RPM-RO Operational Requirements: Deployment of RPM-RO systems at seaports enables reduction of the number of CBP officers required for RPM operation and for interdiction of alarming containers/vehicles. In addition, this system eliminates space use in the terminal/port. RPM-ROs are designed to operate automatically at terminal exit gates or rail access points without the immediate presence of CBP officers or associated booths. CBP officers, located at a nearby CBP command booth, direct and monitor RPM-RO operation through visual and audio surveillance and interaction with vehicle drivers. The CBP officers can then effectively respond to alarms at a primary RPM-RO location from a CBP booth located nearby or via a roving CBP response team.

The following surveillance and communication technologies are integrated with the

RPM-RO:

• VIS equipped with two fixed cameras for each RPM, to provide viewing and identification capabilities for the backs and sides of alarming containers/vehicles as they pass through the RPM-RO (where necessary, additional area lighting must be provided to permit clear viewing/imaging of the containers/vehicles)

• one or more ASCs to remotely track movement of alarming containers/vehicles from the primary RPM scanning area to the secondary inspection area

• an intercom system for CBP officers to communicate with vehicle drivers

• a traffic control system, including a PLC, for controlling vehicle traffic through the RPMs

• OCR software for managing container/vehicle images

• reconciliation software for RPM-ROs deployed at rail yard access points to verify that all containers loaded onto rail cars were identified and scanned.

8. Table 1 summarizes the components required for the RPM-RO, as well as additional deployment information. Vehicles and cargo passing through an RPM trigger radiation measurement by the system’s detector panels and image capture by the VIS. Radiation measurement and alarm data are transmitted to the CBP supervisor computer for display and storage. The CBP supervisor computer also processes VIS image data to extract container/vehicle identification information. This data must be automatically compared to container inventories (“consists”) to verify 100% monitoring coverage.

Table 1 Components and Requirements for the RPM-RO

Contractor shall provide a comprehensive list of all ancillary equipment/spare parts for CWMD approval. Contractor shall submit for CWMD approval any request for ancillary equipment/spare parts currently not listed. Criteria for selecting and purchasing ancillary equipment/spare parts shall be that equipment deemed necessary to deliver an operational and specification-compliant new and refurbished RPM systems.

4.3. Deployment/Decommissioning of RPMs

The Contractor shall perform the necessary activities and contracting to deploy/decommission RPMs and associated ancillary equipment. The Contractor shall provide the logistics support necessary (transportation, lift equipment, material control including a secured laydown yard, etc.) for deploying/decommissioning RPMs.

4.4. Deployment, Installation and operations support

The Contractor shall support the required efforts to deploy, install, and operate RPMs and ancillary equipment at selected CBP sites. The Contractor shall prepare Technical Report(s), as required, detailing the significant deployment events/observations and lessons learned. The Contractor shall maintain an updated configuration database providing detailed information regarding each deployment.

4.5. Human Machine Interface (HMI) and Programmable Logic Controller (PLC) Requirements The contractor shall integrate the HMI and PLC to provide the ability to remotely monitor and control RPMs. Currently the government will provide the HMI and PLC as GFE. The Contractor will review the HMI and PLC configuration to optimize system design.

HMI and PLC requirements specific to RO operations are provided below:

• HMI will support remote monitoring of multiple RPMs across the DHS1Net enterprise network, including alarming status. The HMI will provide the remote user with an audio and visual indication of an alarm of a remotely monitored lane.

• HMI and PLC shall support the remote reset of RPM alarms.

• HMI and PLC shall support the control of traffic control system elements from a remote location (across the DHS1Net enterprise network).

• Backup power is provided for HMI and PLC components with equivalent capability to the backup power required for the RPM system.

4.6. Graphical User Interface (GUI) Integration

The contractor shall integrate a server-based application that aggregates data from an all-purpose interface device to provide an integrated user experience for CBP officers in a Central Command Center. The application communicates with the all-purpose interface device using a reverse proxy configured apache service hosted on the site’s RO site server (RSS). This enables CBP officers to have full situational awareness and control over multiple remote lanes. The GUI server hosts a web-based application officers can access from workstations via Chrome web browser (GUI detailed guidance and specifications provided as GFE).

4.7. Deployment, scheduling and cost estimates

The contractor shall evaluate the level of the installation effort at each site, as specified by CWMD RPM priority. The Contractor shall develop a detailed schedule for each site and update. The Contractor shall determine a cost estimate for planning and scheduling.

Each site estimate shall include the applicable equipment, design, installation, and other labor costs as provided per the contractor unit cost.

4.8. Site Survey

Site surveys provide a baseline of requirements for decisions by the Government and stakeholder. The process starts with a review of existing data, includes development of a contact and coordination plan, and continues through the survey. The Contractor shall collect as much pertinent information as possible about the site configuration, infrastructure, and operations of the deployment site to allow for completion of an engineering design for infrastructure construction, installation, operation, and sustainment of R/N detection/interdiction equipment, components, and infrastructure.

Survey data informs the technical approach for each site and is used to produce a preliminary conceptual design. The Contractor shall document a site survey by a report, in a briefing package, and in a conceptual design that includes background radiation effects that affects RPM performance. The Contractor shall establish roles and responsibilities of all parties and principals involved in the deployment process and formulate stakeholder relationships. This objective may be addressed during deployment project approval process involving negotiations between CBP, and project sponsor (e.g., the port authority, landlord, and terminal operator).

4.9. Design Processes

The Contractor will produce designs utilizing a progressive design model of development and reviews (i.e., a 30%-60%-90%-100% design phase approach as needed based on site complexity). The designs will be stamped by a registered professional engineer. Alternately, contractor will provide design input comprising standard RPM features tailored to the site need. The stakeholders' architect/engineer will incorporate into the overall design if the port is undergoing reconfiguration.

The Contractor shall provide design inputs or complete designs for R/N detection system construction, installation, and operation. The design includes RDE equipment, supporting infrastructure, ancillary equipment, network connectivity requirements, and other support equipment or services needed for R/N interdiction operations.

The Contractor team maybe augmented by radiation physicists and detection equipment subject matter experts (SMEs). The information provided will contain sufficient detail (to the designated A&E) to allow for completion of a 100% design to secure relevant permits, construction of infrastructure, installation of system and components, and execution of R/N interdiction CONOPS at the points of entries. Site design may also include network design for connecting radiation detection panels to the CBP network and for radiation scan information to be transmitted through PRIDE to CBP headquarters.

4.10. Design Engineering

The Contractor shall provide design engineering that promotes design efficiencies, including the use of design services and the application of lessons learned. The Contractor will provide existing standard designs, which includes the reference library of previously modified standard designs and designs developed for site specific requirements.

4.10.1. Standard Designs

The Contractor shall standardize the installation designs to the maximum extent practicable. The Contractor shall maintain and update sets of standard designs for the installation of RPM equipment for all vector configurations.

The Contractor shall ensure that standard system designs satisfy equipment installation and operating requirements for GFE and contractor acquired property.

The Contractor shall ensure the traceability of requirements between all RPM design specifications, design documents, and acceptance testing documents and procedures.

4.10.2. Customized or Site-Specific Design Engineering

The Contractor shall customize designs or, if necessary, develop new site-specific designs to meet site design requirements and system needs. The detailed site designs shall meet the requirements of the CBP design standards, and CWMD provided guidance and design standards.

4.10.3. Design Management and Oversight

The Contractor shall provide design management, and oversight for these projects. If necessary, the Task Order may require use of domestic or host country (pre-clearance sites) design firms. The Contractor shall provide engineering and consulting services to U.S. agencies and their contractors as required. The Contractor shall review, comment on, refine and/or modify designs provided by third parties.

4.10.4. Design Reviews and Engineering Surveys

The Contractor shall conduct engineering surveys, conceptual design reviews, preliminary design reviews, construction readiness reviews, communication reviews, and other engineering meetings. The contractor shall be responsible for all other surveys and reports necessary to meet local standards/codes to include, wind loading, geographical surveys, soil and any other necessary studies.

4.11. Construction Management

The Contractor shall provide construction oversight, when the site owner/operator (e.g., General Service Administration (GSA), port authority, terminal operator, or construction management contractor) provides overall construction and installation services. For construction oversight, Contractor will establish specific hold points to confirm that the deployment meets the approved design and specifications critical to the efficacy of RPM scanning. The hold point inspections may relate to infrastructure construction or equipment installation as needed. When directed, Contractor shall provide contracted construction and installation services in addition to construction oversight.

Installation may include the following in new or modified form: CBP booth installation, radiation detection system installation, ancillary equipment installation and integration.

Construction services may also include the demolition of old equipment and facilities, and removal of debris and unwanted materials. The Contracting Officer (CO) shall be notified in writing whenever asbestos, lead, or other hazardous material abatement construction services are encountered or required.

4.11.1. Construction Quality, Health and Safety

The Contractor shall ensure that quality control/assurance, environment, safety, health, and design requirements are met by subcontractors. The Contractor shall ensure all permits and local inspections are obtained as required.

The Contractor shall report all quality, health, and safety reportable and recordable incidents to the COR.

4.12. Equipment Delivery and Installation

RPM systems, control and battery boxes, and associated supervisory and monitor computers are typically provided as GFE. Ancillary equipment (traffic control systems, network switches, visual identification systems, etc.) is typically provided and installed by the contractor.

The Contractor will acquire the appropriate services, ancillary equipment, and spare parts to support the installation and operability of the detection equipment.

4.13. Commissioning

Prior to commissioning, the RPM is calibrated and tested to ensure detection objectives are met. The process verifies all sub-processes are completed (training, operational readiness, calibration, and field acceptance testing); the equipment list is complete and accurate; and all input for the operations manual is delivered and accurate. The RPM systems then “go-live” and begin scanning cargo or vehicles while being monitored for potential problems. After 48 hours of problem-free operation, the commissioning plan is signed by the site manager, a CBP headquarters representative, and the local CBP port representative. The site is officially turned over to CBP and commissioning is complete.

The contractor will ensure RPM vendor service and repair support during the commissioning process.

4.14. Decommissioning

The Contractor shall remove the RPMs from the previous location and provide them for immediate reuse or return them to inventory, as directed by CWMD. The Contractor will also evaluate the field worthiness of the decommissioned RPMs and make a recommendation to CWMD.

4.15. Site Closeout

Site closeout activities include transmission of final commissioning/acceptance documents to CBP, punch list completion (if any), submittal of redline drawings, and providing of cumulative record drawings to CWMD. Where appropriate, the CWMD PM may direct contractor under this task to assist CBP in the development of both national and site-specific Standard Operating Procedures that minimize safety risks and appropriately address alarm events once the systems are operational.

4.16. Decommissioning of Low Use/No Use Systems

When directed by CWMD PM, contractor shall remove systems from the field (decommission) and return systems and/or components to inventory, as appropriate.

4.17. Training Material Support

The Contractor shall review copies of all existing training material and documentation, as required. CWMD may direct contractor to provide the following:

• Updated RPM training materials for existing system upgrades or enhanced features.

• Training materials for new radiation detection equipment that may be used to replace currently fielded equipment.

• Contractor will utilize existing training materials and develop additional materials, as required, for CBP operator training.

4.18. Inventory Management

The Contractor shall conduct a study of the current RPM inventory managed by PNNL.

The Contractor shall produce a plan that addresses inventory transition from PNNL to identify, track, and manage of RPMP property owned by the Government where equipment requiring control (e.g., RPMs, computers) and propose a property management approach. This shall include the fielding of RPM-RP and RPM recapitalization. In the proposed property management approach, property numbers shall be identified and tracked to account for the equipment, custodian, and location. When RPMP equipment owned by the Government is moved, commissioned, or decommissioned, the proposed contractor property management system shall be updated to maintain accountability of government purchased property. CWMD RPMP property shall remain in the custody of contractor prior to commissioning. After commissioning and upon acceptance by CBP, contractor shall prepare a DHS Form 560-3 for CWMD to transfer ownership of the property to CBP.

4.19. Technical data

The Contractor shall provide to CWMD electronic copies of all RPM vendor and contractor integration technical design and technical data, manuals (operator, installation, and maintenance), recommended spare parts lists, and contractor-developed information on troubleshooting/repair. The Contractor shall maintain and provide a configuration database of all sites commissioned, including those not yet transitioned;

logic diagrams to isolate faults and ascertain corrective actions; and a list of identification data for end items and their major components. For operational configurations, contractor shall provide a list of recommended system design changes to CWMD. For approved design changes, contractor shall track and report implementation.

4.20. Configuration Management

The Contractor shall provide configuration management procedures for all design and installation activities. The Contractor's configuration management procedures must complement and support the CWMD RPM program Configuration Management Plan.

4.21. Program Integration

The Contractor shall coordinate simultaneous design, construction, and integration activities at multiple site locations. The contractor shall designate a single point of contact (Task Order Manager) for delivery order to address all project operations.

4.22. Program Websites and Information Technology

The Contractor shall develop and manage a website that will facilitate program communication and reporting. The Web-Based Reporting System shall have the capacity to contain all documents, including task orders, proposals, reporting requirements and other documents related to task/delivery orders awarded under the Contractor's contract.

The system shall require a strong password for access to the system and require a single password from each person to be entered only once in the system a single access point to the system. Roles will be assigned to each user to determine their access to the sections of the system. The system manager should be able to add and remove access capability quickly.

4.23. Logistics

The Contractor shall refurbish RPMs as necessary, store, maintain, check functionality at warehouse before shipping, and manage inventory of RPMs and associated ancillary equipment. CWMD’s logistics must support the intent to provide a complete and useable RPM lane including the ancillary equipment.

4.23.1. Import/Export Control Licenses

The Contractor shall obtain the necessary export licenses for all equipment either purchased or manufactured in the United States and shipped to CWMD partner countries (e.g., pre-clearance sites) or purchased overseas and shipped to an CWMD partner country. The Contractor shall provide Export Control Classification Number (ECCNs) for all equipment purchased, regardless of the point of origin or destination, and shall provide this information upon delivery.

4.23.2. Shipping, Packaging, and Storage in Continental United States (CONUS) and

Outside Continental United States (OCONUS) The Contractor shall ship equipment and material to CONUS sites and OCONUS Preclearance sites. Once in country (e.g., OCONUS Preclearance sites), the Contractor is responsible for the safe storage, transportation, maintenance and security of all GFE and Contractor purchased equipment. This responsibility will remain with the Contractor until the entire system is accepted by the U.S. Government.

4.23.3. Management of Government Furnished Property, Radiation Portal Monitors

Management of GFE such as RPMs will be specified in the individual Task Order. The Contractor shall coordinate with PNNL who currently manages the RPM inventory for shipping of any equipment specified as GFE.

4.23.4. Translation and Interpreter Services

The Contractor shall provide translators and/or interpreters to translate deliverables, letters and faxes, reports, meeting and training materials, and other miscellaneous items required for the CWMD program and provide interpreters for assistance in conducting meetings with host country (e.g., Preclearance sites) representatives.

4.23.5. OCONUS Host-Country Logistics

The Contractor shall assist CWMD in preparing briefing materials for presentation at meetings in the host country (Preclearance sites).

The Contractor shall procure host country (Preclearance sites) transportation services, host country meeting facilities, supplies, and other services necessary to support host country team meetings, site visits, acceptance testing, workshops and exercises, and other activities.

4.24. Inspection, Testing and Turnover

The Contractor shall provide technical and logistical support for inspection, testing, and assessment of deployed systems and the capability of operators prior to the transfer of operational responsibility to a Preclearance sites and the Sustainability Program, in accordance with the CWMD/CBP Inspection, Testing and Turnover Guide. The Contractor shall provide Test Plans and reports identified in the CWMD documents as applicable.

4.25. Warehouse

The contractor shall provide 20000 sqft of secure warehouse storage facilities for RPM’s and all materials required to sustain operational availability of RPM’s. The contractor shall provide all required personnel, processes and equipment necessary to operate warehouse facilities to include storage racks, handling equipment, receiving, shipping, maintenance area, inventory and maintenance management software. Contractor shall follow the set process for supporting the operational availability:

• Receive equipment from decommissioned sites from CBP

• Test and inspect equipment to determine if materiel is to be refurbished or harvested for parts or retired

• Refurbish/ Harvest parts/ Retire

• Store equipment and manage inventories and provide maintenance and inventory data

• Pre-deployment test

• Package/crate for deployment

• Deploy

5. DELIVERABLES

The Contractor shall deliver reports as specified in the Reporting Requirements Checklist.

6. Other Contract Details

6.1. Place(s) of Performance.

For the purposes of this SOW, the work described shall be performed at the following location(s):

1. United States Points of Entry

2. OCONUS preclearance sites

3. DHS facilities (CWMD, CBP, and others)

4. DOE facilities (PNNL’s Richland, WA facilities, other National

Laboratories)

5. RPM manufacturer’s facilities

6. Warehouse facilities

7. Other locations at the direction or approval of CWMD

6.2. Period of Performance.

The period of performance is a base period of 12 months with four (4) 12-month option periods.

6.3. DHS Furnished Information.

Non-Disclosure Agreement (NDA)

6.4. Special Requirements

A. Safeguarding Sensitive Information.

CWMD funded activities are required to implement information security standards defined by the NIST 800-60. The following is the mapping of SOW tasks and related information to the NIST information types and impact levels:

POWELL, JAVOIL

The SOW does not specifically state OCONUS locations.

Blue, Tisha Add OCONUS here.

POWELL, JAVOIL

Changed the format

Blue, Tisha I prefer not to mention a time here. This is still market research. If we give the dates you will receive calls asking if we are on schedule. We still don’t know the schedule

We do not provide a funding amount to industry.

SOW Task Information to be held by the Supplier

Line of Business/Mission Area Information

Information Type (Impact Levels-C, I, A) Project Management Project management information Management and Support

Supply Chain Management

Inventory Control ((L, L, L) Logistics Management (L, L, L) Goods Acquisition (L, L, L) Services Acquisition (L, L, L)

Information & Technology Management

Lifecycle/Change Management (L, M, L) Information Security ((L, M, L) Information Sharing (N/A, N/A, N/A)

Inventory Management

Inventory Reports

Radiation Detection Equipment (RDE) Infrastructure and Coordination

RDE historical information RDE technical data RDE logistical data

RDE Planning Plans: Acquisition, deployment, operations

Homeland Security

Border and Transportation Security (M, M, M) Catastrophic Defense (M, M, M)*

*DEVIATION: The security categorization for Catastrophic Defense information under this task is determined to be (M, M, M) rather than the provisional (H, H, H)

RATIONALE:

Confidentiality: The confidentiality impact level is the effect of unauthorized disclosure of catastrophic defense information on the ability of responsible agencies to monitor and assess the leadership, motivations, plans, and intentions of foreign and domestic terrorist groups and their state and non-state sponsors. The data and information furnished and developed during the course of the task are unclassified. These data are sensitive in that they include, among other data and information, information on plans and status of detection capabilities and operations. It is assessed that the effect of unauthorized disclosure of such information does not have the same impact as the rationale used in developing the recommendation of NIST SP 800-60, Volume

2. The effects of unauthorized disclosure of information under this task cannot reasonably be expected to jeopardize fulfillment of catastrophic defense missions and is not anticipated to result in threat to human life, critical infrastructures, or key national assets. As such, the confidentiality impact level for catastrophic defense information is moderate.

Integrity: The integrity impact level is based on the specific mission and the data supporting that mission. CWMD seeks confidence in the data

Solutions and scanning systems analyses and development

Validated Needs Engineering Reports Configuration Reports

Solutions Acquisition Deployment Survey Reports

Site Designs On-Site Construction Details Commissioning Documentation Deployment Status Deployment Schedules

Decommissioning Schedules Training Training Materials General Technical and Engineering Assistance

Technical Manuals Technical Reports

Blue, Tisha Specify what is the websites name. What is NDA? Are you referring to nondisclosure agreement?

SOW Task Information to be held by the Supplier

Line of Business/Mission Area Information

Information Type (Impact Levels-C, I, A) and information to be used in tasks as well as that used to information supported missions and functions. Unauthorized modification or destruction might adversely affect system readiness but are not likely to result in loss of human life, unacceptable damage to critical infrastructures, or damage to or loss of key national assets. As such, the assessed integrity impact level for catastrophic defense information is moderate.

Availability: The availability impact level is based on the time required to re-establish access to catastrophic defense information. Disruption of access to or use of catastrophic defense information under the effort is not anticipated to have a severe adverse effect on CWMD missions and functions, assets, or individuals. Mission serve under this effort are time sensitive but are assessed to be tolerant of delays. Short-term disruption of access is not likely to result in mission capability degradation or catastrophic consequences for human life, critical infrastructures, or key national assets. As such, the assessed availability impact level for catastrophic defense information is moderate.

B. Sensitive Information Incident Reporting Requirements.

1. All sensitive, non-PII information incidents involving DHS information or data shall be reported to the DHS Enterprise Security Operations Center (ESOC) within 24 hours of discovery. When notifying ESOC, The Supplier shall also notify the DOE CERT function who will, in turn, notify US-CERT in accordance with US- CERT standards and guidelines. The Supplier shall not include any sensitive information in the subject or body of any e-mail. To transmit sensitive information, the Supplier shall use FIPS 140-2 Security Requirements for Cryptographic Modules compliant encryption methods to protect sensitive information in attachments to email. Passwords shall not be communicated in the same email as the attachment.

2. Sensitive Information Incident Response Requirements.

a. All determinations related to sensitive information incidents, including response activities, notifications to affected individuals and/or Federal agencies, and related services will be made in consultation with the DHS Headquarters or Component Chief Information Officer (CIO) and Headquarters or Component Privacy Officer.

b. The Supplier shall provide full access and cooperation for all activities determined by DHS to be required to ensure an effective incident response, including providing all requested images, log files, and event information to facilitate rapid resolution of sensitive information incidents.

3. Incident response activities determined to be required by DHS may include, but are not limited to, the following:

a. Inspections,

b. Investigations,

c. Forensic reviews, and

d. Data analyses and processing.

4. DHS, in cooperation with The Supplier, may obtain the assistance from other Federal agencies and/or third-party firms to aid in incident response activities.

I. Points of Contact

The DHS POCs are as follows:

Contracting Officer – Tisha Blue, 202-447-05989, tisha.blue@hq.dhs.gov

DHS CWMD may change the individual designated as a POC upon notice to contractor and contract person of such change.

Changed to RFI. No website

Blue, Tisha Don’t need this section as of yet. This is for related documents to the RFP not the RFI. I deleted section all together