STS_RFI PWS DRAFT.pdf

PERFORMANCE WORK STATEMENT (PWS)

for the

Signatures Technical Support (STS) Indefinite-Delivery/Indefinite-Delivery (IDIQ) Contract

Part 1: GENERAL INFORMATION

1. GENERAL: This is a non-personal services contract to provide Signatures Technical Support (STS) services to the National Ground Intelligence Center’s (NGIC’s) Scientific and Technical Intelligence Signatures Branch (STS-ST). The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1 Description of Services/Introduction: Unless otherwise identified herein, the Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, and materials necessary to perform STS services as defined in this Performance Work Statement (PWS). The Contractor shall perform to the standards in this contract.

1.2 Background: As part of the Defense Intelligence Analysis Production (DIAP) Program, NGIC STS-ST collects, models, processes, analyzes signature data to produce and disseminate scientific and technical intelligence (S&TI) products of rotary wing vehicles (i.e., helicopters and unmanned aerial systems), ground systems (e.g., tanks, rocket launchers, armored personnel carriers, light trucks, etc.), artillery and munitions (e.g., rocket propelled grenades, mortars, Improvised Explosive Devices (IEDs)), and other targets of interest to the Intelligence Community (IC). The Signatures Division produces and analyzes collected data to determine the signatures of foreign materiel, primarily in the infrared, radar, acoustic, infrasonic, magnetic, electromagnetic, and seismic spectrums/modalities. Computer Aided Design (CAD) modeling and predictive codes are used as a method for determining signatures. The collection of signature events in multiple modalities requires the Contractor to utilize hardware and software methods to create programmable synchronized sensor collection platforms that address both technical collection requirements and limitations that prevent accomplishment of those requirements. Likewise, processing of collected data may require modification or creation of software tools that find, illuminate, and segment signatures for the production of signature products.

The Contractor shall support every aspect of the signature’s Collection, Processing, Exploitation/Analysis, and Dissemination (CPED) process and generate scientific & database tools across the entire CPED.

1.3 Objectives: The contract objectives are to accomplish the CPED of infrared and geophysical (i.e., seismic, acoustics, magnetic, infrasonic, and electromagnetic emissions) signatures against foreign ground systems of interest to the U.S. Army and generate foreign system CAD models to support predictive signatures efforts.

1.4 Scope: The Contractor shall provide technical and engineering professional services including the following:

- Procurement of sensor systems and peripheral systems.

- Sensor system integration, maintenance, and logistics.

- Signature collection support.

- Data entry, formatting and processing.

- Signature data analysis and exploitation.

- Production and dissemination of finished signature intelligence products approved by STS-ST subject matter experts (SMEs).

- Production or modification of software signatures analysis tools to generate signature products.

- Database/library support for all signatures – legacy and new (This will be government owned property).

- Foreign threat system CAD modeling.

The Contractor shall accomplish the following:

- Integration of time synchronized, multimodal sensor platforms able to collect high quality signature data for the production of signature intelligence.

- Collect signatures for each modality to the format specified by the customer, including all necessary metadata and target ground truth.

- Procure/produce, implement, and maintain signature CPED software tools.

- Asses collected data and determine collection quality and sensor operation.

- Analyze collected signature data with thorough knowledge of the collected signature modality in order to provide science and technical intelligence about the target.

- Use/improve and maintain signature database that allows for the efficient packaging and sharing of signature data.

- Provide venues to disseminate finished signature intelligence products through S&TI Signatures’ web presence, NGIC’s SPIRIT, and/or Signatures Portal.

- Effective production of CAD models relevant to predictive signatures work.

1.5 Period of Performance: The period of performance consists of one (1) 12- month base period and four

(4) 12-month option periods. FAR 52.217-8 also applies. The Period of Performance is TBD.

1.6 General Information

1.6.1 Quality Control: The Contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS and in compliance with contract requirements.

The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services.

1.6.2 Quality Assurance: The Government shall evaluate the Contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government must do to ensure that the Contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.3 Recognized Holidays:

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day

1.6.4 Hours of Operation: The Contractor is responsible for conducting business, between the hours of 7:30 am and 4:30 pm, Monday thru Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. For other than firm fixed price contracts, the Contractor will not be reimbursed when the government facility is closed for the above reasons. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.6.5 Place of Performance: The work to be performed under this contract will occur primarily at the Contractor’s office and on-site at NGIC in Charlottesville, Virginia, when not on a collection mission. The Contractor’s site may be their existing office, or a facility/location within seventy-five (75) miles of the NGIC, whichever is closer. NGIC’s Signatures collection mission is primarily performed at test ranges in the Continental United States (CONUS). The Contractor may need to work on-site at the NGIC when transferring data into NGIC’s network, when processing data from the STS-ST data repository, and when servicing CPED software installed on Government owned computers. The Contractor may work off-site at all other times.

1.6.6 Type of Contract: This is a single-award indefinite-delivery/indefinite-quantity (IDIQ) contract.

Task orders types may include (TBD).

1.6.7 Security Requirements: Contractor personnel performing work under this contract must have a Secret clearance for off-site work, and a Top Secret/Sensitive Compartmented Information (TS/SCI) clearance for individuals who will work on-site at the NGIC at time of the proposal submission, and must maintain the level of security required for the life of the contract. The security requirements are in accordance with the DD254.

1.6.7.1 Physical Security: The Contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured when working on-site at the NGIC.

1.6.7.2 Common Access Card (CAC)/Badge Control. The Contractor shall establish and implement methods of making sure all CACs/badges issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: No CACs/badges issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to secured areas. The Contractor shall immediately report any occurrences of lost or duplicate CACs/badges to the Contracting Officer.

1.6.7.2.1. The Contractor shall prohibit the use of Government issued CACs/badges by any persons other than the Contractor’s employees. The Contractor shall prohibit the accessing of secured areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.

1.6.8 Special Qualifications: TBD.

1.6.9 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officer’s Representative (COR), and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings the contracting officer will apprise the Contractor of how the Government views the Contractor's performance and the Contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.

1.6.10 Contracting Officer Representative (COR): The COR will be identified by separate designation letter. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance:

maintain written and oral communications with the Contractor concerning technical aspects of the contract:

issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the KO and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the IDIQ or resulting task orders.

1.6.11 Key Personnel: The following personnel are considered key personnel by the government: Program Manager (PM) and Senior Subject Matter Expert (SME). The Contractor shall provide a PM responsible for the performance of all work on the IDIQ. The name of this person and an alternate who shall act for the Contractor when the manager is absent shall be designated in writing to the KO. The PM or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The PM or alternate shall be available between 7:30 am to 4:30 pm, Monday thru Friday except Federal holidays or when the government facility is closed for administrative reasons. The Contractor shall provide phone numbers at which the key personnel may be contacted on an as needed basis, for the purpose of consultation from collectors as situations may arise on a collection mission that may require their expertise for the success of the collection mission. The Contractor shall notify the COR and KO of any changes in key personnel. The Contractor shall ensure all key personnel replacements/ personnel assigned to this contract meet or exceed the qualifications required by the PWS. Qualifications for key personnel are listed below: The PM shall have

- Oversight of Contractor personnel working on-site and off-site.

- Ability to manage multiple ongoing Contractor tasks within the CPED for each unique collection or data request and know what each contractor employee should be doing on the contract.

The Senior SME shall have

- Design knowledge of all collection platforms built by the Contractor.

- Knowledge of all aspects of the CPED and standard operating procedures (SOPs).

- Availability for consultation from collectors on a collection mission on an as needed basis.

1.6.12 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties shall identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. Contractor personnel working on-site will be required to obtain and wear badges in the performance of this contract.

1.6.13 Contractor Travel: Contractor may be required to travel to Government and non-Government facilities, within the CONUS during the performance of this contract to attend meetings, conferences and data collection events. The contractor may be required to travel to off-site collection locations and to ship collection equipment to these locations in support of this PWS. The COR shall pre-approve all travel associated with this contract. Authorized travel costs are subject to the limitation of funds clause and may be reimbursed in accordance with FAR 31.205-46.

1.6.14 Other Direct Costs (ODCs): This category includes contractor travel (ref. 1.6.13) and materials.

1.6.15 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to, or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the KO immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the KO to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the KO; and in the event the KO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the KO may effect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.16 PHASE IN/PHASE OUT PERIOD: To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have personnel on board, during the sixty (60) day phase in/phase out periods. During the phase in period, the Contractor shall become familiar with performance requirements in order to commence full performance of services on the contract start date.

1.6.17 Training: The Contractor shall ensure the required levels of training are provided to all contract personnel employed under this contract.

PART 2: DEFINITIONS & ACRONYMS

2. DEFINITIONS AND ACRONYMS:

2.1. DEFINITIONS:

2.1.1. CONTRACTOR. A supplier or vendor having a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.2. CONTRACTING OFFICER. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.3. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.4. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.5. DELIVERABLE. Anything that can be physically delivered but may include non-physical things such as meeting minutes.

2.1.6. KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.7. MAINTENANCE. Ensures signature collection related GFP, software and database are mission ready. This includes but is not limited to: sensor check-ups, sensor adjustments, sensor repairs, sensor measurement verification, CPED software updates, CPED software debugging and records of such maintenance.

2.1.8. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.9. QUALITY ASSURANCE. The government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.10. QUALITY ASSURANCE SURVEILLANCE PLAN (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.11. QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.12 SENSOR CONTROLLER. An integrated electronic device capable of interfacing with the sensor or sensors for the purpose of operating and maintaining the collection sensors to execute signature collection tasks.

2.1.13. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.14. WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.15. WORK WEEK. Is defined as Monday through Friday, unless specified otherwise.

2.2. ACRONYMS:

3D Three Dimensional ACOR Alternate Contracting Officer's Representative AFARS Army Federal Acquisition Regulation Supplement AR Army Regulation ASAP As Soon As Possible CAC Common Access Card CAD Computer-Aided Design CCE Contracting Center of Excellence CD Compact Disc CFR Code of Federal Regulations CMR Contractor Manpower Reporting CONUS Continental United States (excludes Alaska and Hawaii) COR Contracting Officer Representative COTR Contracting Officer's Technical Representative COTS Commercial Off the Shelf CPARS Contractor Performance Assessment Report System CPED Collection, Processing, Exploitation, and Dissemination CPU Central Processing Unit cUAS Counter UAS DA Department of the Army DAC Department of the Army Civilian DD250 Department of Defense Form 250 (Receiving Report) DD254 Department of Defense Contract Security Requirement List DFARS Defense Federal Acquisition Regulation Supplement DMDC Defense Manpower Data Center DOD Department of Defense DVD Digital Video Disc FAR Federal Acquisition Regulation FSC Federal Service Code GFE Government Funded Equipment GFP Government Furnished Property GOTS Government Off the Shelf GPS Global Positioning System GUI Graphical User Interfaces HIPAA Health Insurance Portability and Accountability Act of 1996 IDE Integrated Development Environments IMD Intelligence Mission Data INSCOM Intelligence and Security Command IPR In Process Review IR Infrared JTR Joint Travel Regulation JWICS Joint Worldwide Intelligence Communications System KO Contracting Officer MS Microsoft MuSES Multi-Service Electro-Optic Signature NGIC National Ground Intelligence Center NIPR Non-Secure Internet Protocol Router OCI Organizational Conflict of Interest OCONUS Outside Continental United States (includes Alaska and Hawaii) ODC Other Direct Costs PIPO Phase In/Phase Out POC Point of Contact

PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QAP Quality Assurance Program QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Program S&TI Scientific and Technical Intelligence SCIF Sensitive Compartmented Information Facility SIPR Secure Internet Protocol Router SME Subject Matter Expert SOP Standard Operating Procedures SPIRIT System Parametric Information Relational Intelligence Tool SSO Special Security Officer STS Signature Technical Support STS-ST S&TI Signatures Branch TE Technical Exhibit TO Task Order TS/SCI Top Secret/Sensitive Compartmented Information UAS Unmanned Aerial System UAV Unmanned Aerial Vehicle UIC Unit Identification Code

PART 3: GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1. Services: The Government will provide personnel to assist with collections (See Para 5.2).

3.2 Facilities: The Government will furnish the necessary workspace at the NGIC for contractor personnel performing on site.

3.3 Utilities: The Government will provide all utilities for the Contractor’s use at the NGIC in performance of tasks outlined in this PWS. The Contractor shall instruct employees in utilities conservation practices.

The contractor shall be responsible for operating under conditions that preclude the waste of utilities, such as turning off the water faucets or valves after using the required amount.

3.4 Equipment: The Government will provide access to basic computers (Central Processing Unit (CPU), Joint Worldwide Intelligence Communications System (JWICS), Secure Internet Protocol Router (SIPR) & Non-Secure Internet Protocol Router (NIPR), monitor, keyboard, and printer) and phones for Contractor use at the NGIC. Computers include standard Windows programs to include unclassified email to accomplish and disseminate computerized logging, shift schedules, reports and other business related applications. The Government will grant access to the items listed in the Government Furnished Property (GFP) List (REFERENCE TBD). The Contractor shall use sound industrial practices to safeguard and protect Government property in their possession or custody, and must return in proper order before the end of the period of performance.

3.5 Materials: The Government will provide all government rules, regulations, and manuals required to perform duties at the facility, including all necessary administrative forms. The Government will also provide any necessary project descriptions, program briefing material, pertinent information, and other documentation required in the performance of on-site work.

PART 4: CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 General: The Contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Section 3 of this PWS.

4.2 Secret Facility Clearance: The contractor shall possess and maintain a SECRET facility clearance from the Defense Security Service. The Contractor’s employees, performing work in support of this contract shall be granted a SECRET security clearance from the Defense Industrial Security Clearance Office. The Contractor’s employees, performing work on-site at NGIC in support of this contract shall be granted a TS/SCI security clearance from the Defense Industrial Security Clearance Office. The DD 254 is provided as Attachment.

4.3. Materials/Equipment: All equipment, hardware, and software purchased, produced or modified under this contract with contract dollars belongs to the Government and must be surrendered to the Government at the end of the contract. Material purchases will be approved by the COR or the Government technical representative.

PART 5: SPECIFIC TASKS

5. Specific Tasks:

5.1. BASIC SERVICES:

The Contractor shall provide services to produce and execute an effective Geophysical and EO/IR modality CPED workflow. CAD modeling may be necessary to support predictive signature work. The Contractor shall provide signature technical support as follows:

5.2. SIGNATURE SENSOR PLATFORM SPECIFICATION, PROCUREMENT, INTEGRATION AND

MAINTENANCE:

The Contractor will have access to the STS-ST’s electro-optic/Infrared (EO/IR) and geophysical (acoustic, infrasound, seismic, and magnetic) sensors and calibrators as GFP, which shall be secured at its site for the duration of the contract. The Contractor shall be responsible of providing maintenance to the government owned sensors. The Contractor shall ensure that collection sensor controller’s input/output devices are working properly and that drivers are up to date, including those required for peripheral equipment. The Contractor shall specify, propose, procure, and evaluate sensors and peripheral equipment for the government when deemed necessary by the COR and/or STS-ST branch chief. The Contractor will implement, as needed for the collection requirements, a universal time synchronized collection platform that integrates all or many of the needed sensor modalities and required sensor operation(s) for the accurate and safe collection of the specified target signatures. The Contractor shall properly program and configure sensors and in particular the EO/IR sensors for a given collection scenario. Geophysical sensors are to be set for the proper frequency response and the maximum signal without saturation. EO/IR sensor programming may change based upon source type, intensity of source, distance, angle, azimuth to source, and lens used. The Contractor shall calibrate and operate/test the sensors so that sensors are known to be functioning correctly for the targets of interest before being sent to the field. The Contractor shall make the sensors available for government personnel use upon request from the COR or STS-ST branch chief, and shall verify that the sensors are returned in good working order. The contractor shall research, as needed, methods to remotely control various commercial sensors and then integrate into STS-ST’s suite of sensors.

Alternatively, the Contractor may use its own sensor suite as long and they meet collection requirements and can accomplish a successful STS-ST CPED mission.

5.3. SIGNATURE DATA COLLECTION:

The Contractor, along with the STS-ST SMEs, shall form a team that collect signature data, ground truth and their associated metadata, (equipment settings, time, weather, distance, location, and other necessary information) of targets of interest per NGIC’s DIAP Program. The team may only be the contractor in many cases, but may include STS-ST SMEs, DACs and military/reserve soldiers if additional resources are needed. Collection will take place in the United States and its territories. The Contractor shall possess U.S. citizenship and be able to travel CONUS. Collection may occur in remote locations and require portable instrumentation that the Contractor shall carry/transport, setup/configure, and operate correctly to collect useful signatures.

5.3.1. Pre-Collection:

The Contractor shall review the collection requirements with the STS-ST SMEs before creating a collection plan and selecting the sensors. The Contractor shall verify that all necessary collection equipment, either GFP or contractor owned, has been properly maintained, configured and programed per Task 5.2. The Contractor shall have fully trained field collection personnel before they carry the collection platform to the field. The GFP infrasound collection array does not require programming or synchronizing with other systems, but should be confirmed for correct operation before being sent to the field. Lossless data acquisition is required to create the desired high-fidelity signature. Metadata shall be recorded for all collected signature data.

5.3.2. Field Operation During Signature Collection Events:

The Contractor shall interface, as soon as a collection is approved, with range/field points of contact (POC) for ingress/egress, and sensor locations on the range/field. The Contractor doing field collection shall be knowledgeable of EO/IR, imaging and non-imaging infrared and geophysical field measurement techniques and practices including the calibration of sensors and the collection/recording of ground truth and metadata.

The Contractor shall assess raw EO/IR and geophysical signatures data collected in the field, and make necessary adjustments to collection equipment and procedures to address any data quality issues such as sensor gain and saturation. The Contractor shall collect and record all metadata associated with the field collect such as GPS locations of all sensors and sources, universal time of events, and necessary metadata.

When necessary the Contractor shall make minor repairs, both mechanical and electrical, to collection sensors and peripheral equipment as required or needed for a collection. The Contractor shall ensure the integrity of the collected data by adhering to collection protocols concerned with media handling and security.

5.3.3. Post-Collection:

The Contractor shall log all returned range/field GFP into STS-ST’s inventory and confirm the equipment is operating correctly. All malfunctioning equipment shall be reported to Branch Chief of STS-ST and the COR. Collected raw data, except for classified targets, shall be considered UNCLASSIFIED until processed. Collected data shall be burned to CD, DVD, or approved hard or solid state drive and shall follow existing government SOPs and/or consult with the SSO for data residing within a SCIF. The Contractor shall make every effort to get the raw data to NGIC in a timely fashion. Data storage devices entering the SCIF shall not exit the SCIF. Sufficient resources shall be provided to the Contractor as Other Direct Costs (ODC) to cover the cost of purchase of data storage media/devices. Questions not clearly answered by the DD-254 or related to raw data return or security classification level of raw data shall be presented to the COR for clarification.

5.4 SIGNATURE DATA PROCESSING:

The Contractor shall process raw geophysical and IR signature data, ground truth, and metadata from a collection, NGIC’s archival holdings, or from a trusted partner collection to produce data processed for the production of signatures. The Contractor shall derive, as necessary, or otherwise follow existing SOPs to apply data reduction routines to process raw signature data. The Contractor shall immediately notify the COR if an error(s) exist within a SOP, and shall modify a SOP at the direction of the COR. All modified SOPs are marked as of the date last modified, an electronic copy of the modified SOP is presented to the COR, and the old version shall be archived for future reference. The Contractor shall, from an understanding of the expected signature, evaluate raw data to select portions for further analysis by Signature Division’s analysts or for packaging for customer use. The Contractor shall interpret raw data to extract information about the sensor (operational parameters and proper functioning) at the time of the collection and judge the quality of the collected data. The Contractor shall maintain and update collection metadata files so that processed data remains meaningful and valid for signature analysts and customers.

The Contractor shall use STS-ST’s quality assurance/quality control software and attach processed data and its metadata for review by STS-ST SMEs before entering a data set into the database. The contractor may also be required as necessary to modify the quality assurance/quality control software to allow new sensors and metadata into the workflow. All quality assurance/quality control software shall have an open architecture that allows further modifications to the software to be made after the end of the contract.

5.5 SIGNATURE DATA ANALYSIS AND EXPLOITATION:

The Contractor shall analyze raw or processed signature data with its associated ground truth and metadata to produce signature data and extract S&T intelligence from the signature data for customers. The final analysis of acoustic, infrasonic, seismic, and EO/IR data will be done by the Government’s STS-ST SMEs.

The Contractor shall use and/or modify computational methods including, specifically, methods written in C/C++, Java and MatLab to analyze and validate signature data. The specific code to be used shall be confirmed with the COR before implementation. The Contractor may use government off the shelf (GOTS) and commercial off the shelf (COTS) analysis software packages or may need to explore additional software packages that provide the required functionality for signature analysis and extraction of intelligence information. All software shall be approved for operation within a SCIF. The Contractor shall maintain and update metadata files to include analysis methods and techniques so that analyzed data remains meaningful and valid for STS-ST’s customers and other analyst.

5.6 SIGNATURE PRODUCT ARCHIVAL AND DISSEMINATION SUPPORT:

5.6.1 Archival Support:

The Contractor shall enter data sets (e.g., raw, processed, and analyzed signature data; ground truth; and metadata) in the STS-ST signature data repository, and use quality assurance/quality control tools on processed and analyzed signature data before loading into STS-ST’s signature database. The Contractor shall assist STS-ST SMEs in controlling/preserving the integrity of data stored on legacy media with a limited lifespan.

5.6.2 Dissemination Support:

The Contractor shall participate in discussions with STS-ST SMEs, Signatures Portal POCs, and/or SPIRIT database POCs related to signature data, metdata and ground truth formatting for efficient signature package ingestion into, and discoverability through Signatures Portal and/or SPIRIT. In parallel, the Contractor shall maintain and update data on the STS-ST’s existing signature web presence and assist STS- ST SMEs in the dissemination of signature packages to customers. The Contractor shall make every effort to modify the existing STS-ST web presence such that the data, metadata and ground truth format agreed upon for Signatures Portal and/or SPIRIT is compatible with the STS-ST signature web presence (See Task 5.8).

5.7 SIGNATURE SOFTWARE AND DATABASE CODING SUPPORT:

The Contractor shall refine existing technical software tools to support the analysis, processing, and dissemination of signature data. The Contractor may furnish and utilize specialized software development tools or Integrated Development Environments (IDE) to author processing, analysis, or data visualization tools. Minimally, software coding will include MatLab, C/C++, Java, SQL or other coding for a relational database management system. The Contractor shall support efforts or design data entry or sharing interfaces in the database and Graphical User Interfaces (GUIs), visualization of collected signature data in the field, calibrate data, and prepare data for entry into STS-ST’s database for signature customers. The Contractor shall thoroughly document all code. All software has to be approved for operation within a SCIF. Prior to the implementation, the contactor shall coordinate with the COR to ensure that the user interface is intuitive. The Contractor shall prepare user interface documents that provide the information and data required to STS-ST and its customers. All signature software, and database coding support software produced by the Contractor for STS-ST shall have an open architecture that allows further development after the end of the contract. The Contractor is not responsible for 2nd party COTS software but only for any integration software that the Contractor custom designs to integrate COTS software for the Government.

5.8 ELECTRONIC WEB PUBLISHING AND PROGRAMMING SUPPORT:

The Contractor shall prepare and assist STS-ST in the electronic distribution of intelligence products upon multiple domains to include SIPRNET and JWICS security classification networks. The Contractor shall work as a technical automation specialist and web content programmer. The Contractor shall be responsible for requirements analysis, design, implementation and maintenance of web-enabled databases, including Oracle, and web application programs (such as HTML, XML, Perl, Java, and SQL). The Contractor shall generate new intuitive applications for intelligence dissemination. The Contractor shall expand upon current processes to create improved workflow for intelligence documents and data.

5.8 SIGNATURE TRAINING SUPPORT:

The Contractor shall train other collectors (Military, Civilians and contractors) on use of collection devices for various environmental and operating scenarios, and author SOP for the correct operation of collection equipment for various environmental and operating scenarios. The Contractor shall develop training material for new processes that were researched, developed, implemented and tested for the NGIC. The Contractor shall train analysts and produce SOPs on use of signature processing devices and techniques, analysis methods, and dissemination methods. Video teleconference may be used to facilitate training.

5.9 SIGNATURE DIVISION REPRESENTATION SUPPORT:

The Contractor shall support events including briefings, phone and video conferences, and at other Department of Defense (DOD) sites, conferences, and working group meetings and provide STS support services while in attendance at signature community events. As such the Contractor shall appear and be professional in his/her actions and duties as they bear upon the image and integrity of the INSCOM, the NGIC and STS-ST. The Contractor does not represent or speak on behalf of the United States Government. The Contractor shall provide and give briefings on STS-ST’s signature results and findings and shall report to the NGIC Signatures Division the minutes of attended meetings and conferences.

5.10 CAD MODELING SUPPORT:

The Contractor along with STS-ST’s SMEs shall form a team to create CAD models for the purpose of producing signatures using predictive codes. The Contractor shall have the knowledge, skill, and ability to use three-dimensional (3D) CAD. All sources of information and computational methods form the basis of the process. The Contractor shall, as requested, derive and implement new methods that capture the physical attributes of the target and accurately convey them in a CAD model. Specific emphasis is on the CAD modeling of foreign threat systems.

The Contractor shall use raw intelligence data (images, line drawings, verbal descriptions, etc.) to produce CAD files that are useful to a wide range of customers. The Contractor shall assess the raw data in order to produce high fidelity CAD models. The Contractor shall have and utilize knowledge, skill, and experience with a variety of 3D CAD programs (e.g.; ProE, Rhino 3D, SolidWorks) and the Contractor shall have knowledge, skill and experience with 3D CAD techniques and their application. The Contractor shall prepare reports describing the conditions and targets under which a measurement took place. The Contractor shall prepare reports for customers that provide the information and data required. The Contractor shall develop processes based upon customer standards that ascertain the accuracy of CAD models.

5.11 DELIVERABLES AND REPORTING REQUIREMENTS:

All deliverables and submission requirements are provided on Technical Exhibit 2. Below is a description of each deliverable. The monthly reports and the progress reviews may be used to monitor performance.

5.11.1 Post Award Conference/Periodic Progress Meetings:

The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with FAR Subpart 42.5. The KO, COR, and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance.

At these meetings the KO will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced.

Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government. The deliverables are a briefing and meeting minutes from the Contractor’s perspective.

5.11.2 Quality Control Plan:

The Contractor shall develop a QCP (Microsoft Office document) to be used as a guide and to rigorously document the implementation of the required management, QA and QC actions to achieve the specified results of this contract. The QCP is due 30 days after the start of the contract and shall be updated as required.

5.11.3 Monthly Progress Report:

The Contractor shall submit monthly a written progress report to the KO and COR throughout the life of the contract. Monthly progress reports are due by the fifteenth calendar day of the following month.

Progress reports shall include but not be limited to the following:

5.11.3.1. Progress achieved since the last report – includes preparation for and actual signature collections, software tool coding work, signature data entries and data management, and data requests.

5.11.3.2. Major elements of progress achieved to date on all tasks not covered in above item 5.11.3.1. This progress is for longer termed tasks that span more than one month to indicate the status/schedule.

5.11.3.3. Significant problems encountered and problem solutions implemented during the period. Note:

problems concerning delays should be reported to the COR as soon as possible (ASAP).

5.11.3.4. Problems remaining and proposed solutions. If problems are due to Government inaction, they should be noted and the COR should be notified ASAP.

If the COR requires a report change, he/she will return it to the Contractor for correction. The COR will return the report within thirty (30) calendar days of its receipt; otherwise, the progress report shall be considered accepted.

5.11.4 Monthly Financial Reports and Wide Area Work Flow:

The Contractor shall submit monthly a financial report to the COR throughout the life of the contract.

Monthly financial reports are due by the fifteenth calendar day of the following month. Expenditures shall be identified by category (i.e., labor, travel, materials). Travel and material expenses shall be itemized.

Funds used during the period covered, as well as total funds expended to date shall be reported. If actual amounts for the current period are not available, the Contractor shall substitute estimated amounts.

Estimated amounts shall be distinguished from actual amounts. All reports shall be forwarded to the government in electronic formats. The Contractor shall use Wide Area Work Flow (WAWF) to submit invoices for payment.

5.11.5 In Process Reviews (IPR):

The Contractor shall conduct quarterly Progress Review (IPR) meetings at either the contractor site or the NGIC. The Contractor shall provide minutes of the meeting and an electronic copy of presented materials, including PowerPoint viewgraphs, to the COR within fifteen (15) calendar days after the meeting date. If applicable, IPR technical reports shall be submitted to the COR fifteen (15) days after the IPR.

5.11.6 Technical Reports and Technical Briefings:

The Contractor shall deliver all documentation (as needed) created for technical reports including collection plans, SOPs and briefings to the COR and the appropriate SME for review prior to final delivery to the Government or for presentation. A satisfactory review of a report by the COR will conclude the requirements of that particular task.

5.11.7 Documentation:

The Contractor shall provide detailed electronic documentation (as needed) in support of each task for technical designs of hardware/software or software tools for analysis and processing. Minimally, documentation shall include: explanation of all basic theory, equations, algorithms, and specific applications; description and specifications of Contractor written computer code; and explanations of any other methods used to process information.

5.11.8 Computer Software End Items:

The Contractor shall provide to the NGIC any software or scripts produced/modified for hardware control or processing, analysis, or dissemination (as needed). The contractor shall provide the government with source code as well as compiled code and documentation for any contractor-produced software under this effort.

5.11.9 Collection Hardware End Items:

The Contractor shall purchase sensors and ancillary items. Purchase of sensors should be made with enough time before the end of the POP in order to allow vendors, if necessary, to produce new units.

Specialized signature collection sensor vendors often have to build the required units due to low inventory or a one-of-a-kind build that may take longer than anticipated and delivery may occur after the POP. In this case the Contractor shall immediately notify the KO and COR of such a timeline, and discuss a mutually agreable delivery plan. In case of audit this PWS directs the auditor that Government guidance allows the Contractor to deliver specialized signature sensors after the POP due to circumstances beyond the Contractor’s control. No purchase shall be made after the POP. Ancillary items include batteries, carrying bags, recording media, battery chargers, electronic cables for sensor communications and any other small items that are necessary to create a sensor package ready for field use.

5.12 CONTRACTOR MANPOWER REPORTING (CMR) (Only applies to Army Customers):

The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor shall report ALL Contractor manpower (including subcontractor manpower) required for performance of this contract. The Contractor shall completely fill in all the information in the format using the following web address https://Contractormanpower.army.pentagon.mil. The required information includes: (1) Contracting Office, Contracting Officer, Contracting Officer’s Technical Representative (COTR) or also know as the Contracting Officer’s Representative (COR); (2) Contract number, including task and delivery order number; (3) Beginning and ending dates covered by reporting period; (4) Contractor's name, address, phone number, e-mail address, identity of Contractor employee entering data; (5) Estimated direct labor hours (including sub-Contractors); (6) Estimated direct labor dollars paid this reporting period (including sub-Contractors); (7) Total payments (including sub-Contractors); (8) Predominant Federal Service Code (FSC) reflecting services provided by Contractor (and separate predominant FSC for each sub-Contractor if different); (9) Estimated data collection cost; (10) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the Contractor with its UIC for the purposes of reporting this information); (11) Locations where Contractor and sub-Contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website); (12) Presence of deployment or contingency contract language; and (13) Number of Contractor and sub- Contractor employees deployed in theater this reporting period (by country). As part of its submission, the Contractor shall provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period shall be the period of performance not to exceed 12 months ending September 30 of each government fiscal year and must be reported by 31 October of each calendar year.

Contractors may use a direct XML data transfer to the database server or fill in the fields on the website.

The XML direct transfer is a format for transferring files from a Contractor’s system to the secure website without the need for separate data entries for each required data element at the website. The specific formats for the XML direct transfer may be downloaded from the website.

PART 6: APPLICABLE PUBLICATIONS

6. APPLICABLE PUBLICATIONS (CURRENT EDITIONS)

6.1. The Contractor shall abide by all applicable regulations, publications, manuals, and local policies and procedures at the NGIC and at all other Government facilities and ranges where collection or briefings pertinent to the CPED may occur. Security policies and procedures are detailed in the DD254 and SCI Addendum.

TECHNICAL EXHIBIT 1: PERFORMANCE REQUIREMENTS SUMMARY (PRS)

Performance requirements will be identified in each task order. Below contractor service requirements applicable to this IDIQ are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement.