PERFORMANCE WORK STATEMENT FOR

704 TEST GROUP ADVANCED TEST AND LOGISTICS ASSISTANCE SERVICES

CONTRACT

TASK ORDER 001

VERSION 001

04 September 2025

Prepared by: 704 Test Group

1.0 INTRODUCTION

The 704th Test Group (TG) will leverage a single award Indefinite Delivery, Indefinite Quantity (ID/IQ) contract, Advanced Test and Logistics Assistance Services (ATLAS) Contract, to provide logistics and test support services across the 704th TG. The 704 TG is comprised of the 746th Central Inertial and GPS Test Facility (CIGTF), 846th Test Squadron Holloman High Speed Test Track (HHSTT), 586 Flight Test Squadron, National RCS Test Facility (NRTF), OL-A Directed Energy Combined Test Force (DE-CTF), OL-AC Aerospace Survivability and Safety and the 704th Test Support Squadron (TSS). Each squadron is responsibility for specific areas of critical national defense testing and experimentation efforts. The ATLAS contract will support the broad test support and logistics requirements of the 704th Test Group in the execution of critical national defense acquisition and development efforts as directed by the Secretary of War and Component Chiefs of Staff.

2.0 PURPOSE

The objective of the ATLAS Task Order 001 (TO 001) is to execute efficient and effective logistics and test support for the 704th Test Group programs throughout all critical testing and experimentation areas.

3.0 SCOPE / MISSION

This ATLAS TO 001 requires the ID/IQ Contractor to perform 704 TG requirements, including:

• Procurements

• Equipment service, maintenance and repair

• Material shipment

• Ad-Hoc response

All performance activities will be captured using an Online Workflow Management System (OWMS) outlined in section 5.5.

4.0 PERIOD AND PLACE OF PERFORMANCE

The Period of Performance (PoP) for the ATLAS TO 001 is five (5) years from the date of award.

4.1 Primary places of performance will be Holloman Air Force Base (HAFB), High Energy Laser Support Facility (HELSTF), White Sands Missile Range (WSMR), Wright- Patterson Air Force Base. Places of performance may also include locations in the United States, current partner nations, or locations as otherwise directed.

4.1.1 All contractor personnel requiring access to any of the places of performance to perform work under this contract must comply with all installation security and access control procedures. The contractor shall be responsible for vetting all personnel and ensuring compliance with applicable DoD and installation-level directives.

4.1.2 For routine physical access, the contractor shall submit a list of all personnel, including any subcontractors, requiring access to the Contracting Officer’s Representative (COR). The list shall be on company letterhead and include the contract number, work site location, start and end dates, full names, issuing state of identification or driver’s license, social security number, date of birth and citizenship/permanent resident number of all employees. The COR will provide the necessary documents for processing installation passes. The COR may update required format and information to meet installation access requirements.

4.1.3 All personnel requiring unescorted access will undergo a background check.

The government reserves the right to deny access to any individual found to be a security risk. The contractor shall not be relieved of their performance obligations if personnel are denied access. All personnel shall display their installation identification at all times. Upon completion or termination of the contract, the contractor shall ensure all issued passes and credentials are returned to the issuing office.

4.2 The Contractor program management team shall be available to attend key meetings at Holloman Air Force Base and other locations, as may be directed by the Contracting Officer Representative (COR).

The Contractor shall host a weekly meeting at a mutually agreed upon day and time to discuss contract execution and deliverable activities. The purpose of the weekly meeting is to provide the Contractor a forum to present and discuss any contract execution problems requiring 704 TG assistance, present contract financial status updates, and identify successes outside of the normal course of duty. The Contractor shall not recap the status of routine requirements where no concerns exist. Rather, the Contractor shall prepare and submit a written list of routine work details including, but not limited to, number of active procurements, equipment maintenance and repair status, task orders projected to be delivered on-time, task orders projected to be delayed or late, and other topics as directed by the COR or program manager. The Contractor shall submit its written weekly updates to the COR and their support team by end of business or 5:00pm Mountain Standard Time (MST) one (1) day prior to the meeting.

The Contractor shall present its adherence to contract requirements and performance metrics by means of biannual Performance Metrics Report (PMR) meetings. The PMR meetings shall take place each May and November, or as otherwise directed by the COR, at a mutually agreed upon location. The Contractor shall present a ninety-five percent (95%) complete PMR presentation to the COR and their support team by end of business or 5:00pm MST ten (10) calendar days prior to each PMR meeting. Changes to the presentation are authorized once delivered, at the discretion of the COR and their support team. If corrections need to be made during the PMR presentation, the COR will confirm the data to be corrected and the Contractor will record the corrections and update the final version of the presentation. The final version of the PMR presentation shall be presented to the COR and their support team not later than five (5) business days following the conclusion of the PMR.

Factors outside of the Contractor’s control may occur during the performance of the contract. During the PMR, the Contractor may request relief against contract metrics by presenting compelling justification for the relief. The relief process applies to all support requests.

The Contractor shall maintain effective communication with the COR and their support team, and responsible 704th Test Group project officer(s) and their support teams. Any informational exchanges pertaining to the implementation of 704 TG activity conducted by the Contractor by means of communication applications or cell phone (text/voice) shall be accurately summarized by email with a courtesy copy (CC) to the COR and their support team. Communications via phone text/voice related to task order execution for ongoing support do not need to be summarized and archived via email (e.g coordination with COR, project officer or program manager for details to execute impending repair of precision fabrication equipment).

5.0 PERFORMANCE REQUIREMENTS

The following sections are required capabilities and performance characteristics of the supplies and services sought in this TO 001.

5.1 Procurements

5.1.1 The Contractor shall provide ad-hoc purchases of equipment, services, and other support to meet 704 TG mission requirements, including the capability to source internationally and from local or regional vendors.

5.1.2 The Contractor shall be prepared to provide equipment, services, and support to all phases of the equipment lifecycle, including, but not limited to, procurement, delivery, installation, distribution, scheduled maintenance, inventory, technical manuals, records, initial and sustainment training, infrastructure, transfer of property, and disposition of property.

5.1.3 The Contractor shall be prepared to provide purchase of metals to include:

• Round steel rod (various diameters and lengths)

• Aluminum rod (various diameters and lengths)

• Steel bar stock (various dimensions and lengths)

• Aluminum bar stock (various dimensions and lengths)

• Sheet steel (various thicknesses and dimensions)

• Steel tubing (various diameters, thicknesses and lengths)

• Aluminum sheet (various thicknesses and dimensions)

• Galvanized sheet steel (various gages and dimensions)

5.1.4 The Contractor shall provide consumable materials for material fabrication to include welding supplies, Computer Numerical Control (CNC) machining equipment, and other materials at the direction of the Government COR, PM or authorized squadron Project Officer.

5.1.5 The Contractor shall be prepared to procure components and parts for the sustainment and operation of “LOIS” and “LARD” Humanetics aerospace dummies to support test operations.

5.1.6 The Contractor shall be prepared to procure fabrication equipment, heavy equipment and related components indentified in section 5.2, but not limited to specifically identified equipment.

5.1.7 The Contractor shall provide metals processing of components and assemblies to include heat treat processing, annealing, corrosion protection, metallurgical analysis, non-destructive inspection (NDI) and other similar processes.

5.1.8 The Contractor shall provide metal protection of components and assemblies to include powder coating, painting, anodizing, Alodine, passivation, eoncoat, and other similar processes.

5.1.9 The Contractor shall provide machined parts and assemblies manufactured in accordance with government provided drawings and tolerances.

5.1.10 The Contractor shall be prepared to procure instrumentation, sensors, and calibration equipment to support test operations

5.1.10.1 The Contractor shall provide procurement of instrumentation and sensor devices, to include but not limited to, for the measure of pressure, load, heat, and acceleration. Instrumentation or sensor component with no suitable substitute shall be identified in the associated task order. Specific instrumentation and sensor performance requirements will be provided with the task order and if suitable substitutes are acceptable.

5.1.10.2 The Contractor shall, to the maximum extent possible, procure instrumentation and sensors with valid calibration that exceed 6 months beyond the delivery dates.

5.1.10.3 The Contractor shall be prepared to procure calibration services and certification for sensors and instrumentation that are unable to be procured with adequate calibration dates. Additionally, the Contractor shall be prepared to procure calibration services for government furnished equipment that requires recalibration to support test operations.

5.1.11 The Contractor shall be complied to provide a wide array materials supporting test operations. A limited list of representative consumables and products are included below.

• Gases o Helium o Nitrogen o Argon o Propane o Other

• Potable Water

• Lavatory facilities

• Cat 5 fiber optic cable

• Cat 6 fiber optic cable

• Aerospace hand tools

• General hand tools

• Data loggers

• Electrical cable

• Electrical connectors

• Air Filters

• Personal protective equipment

• Milling tools and components

• Various hardware

• Cutting wheels

• Cutting blades

• Waterbags

• Pyro tape

• Camera and camera equipment

5.1.12 The Contractor shall comply with all Defense Federal Acquisition Regulation (DFAR) requirements and restrictions in the procurement of all associated materials and services associated with all performance requirements of this task order.

5.2 Equipment Service, Repair and Maintenance

5.2.1 The Contractor shall provide service, repair and maintenance services for fabrication equipment to include but not limited to: Electrical Discharge Machining (EDM) equipment, horizontal lathe, horizontal CNC machining equipment, vertical CNC machining equipment, horizontal CNC lathe, manual milling machines, and air compressor equipment and related components.

5.2.1.1 For fabrication equipment with active warranty the Contractor shall provide qualified area vendor technician or manufacturer certified technician to complete approved repair, service or maintenance to maintain equipment warranty.

5.2.1.2 For fabrication equipment with no active warranty the Contractor shall provide competent technician with appropriate certifications to complete equipment repair, service or maintenance..

5.2.2 The Contractor shall be prepared to provide service, repair and maintenance services for heavy equipment to include but not limited to gantry crane(s), water truck(s), excavator(s), backhoe(s) and other related equipment and components.

5.2.2.1 For equipment with active warranties the Contractor shall utilize approved vendor technicians to maintain equipment warranties.

5.2.2.2 For equipment without active warranties the Contractor shall utilize competent technicians with appropriate certifications.

5.3 Procurement Request Form

5.3.1 The Contractor shall develop a Procurement Request (PR) form, made available and submitted via OWMS. The Contractor shall also provide an offline version of the PR form and be responsible for receiving and uploading the offline form data into the OWMS. The Contractor shall develop and implement an OWMS-based solution that identifies previously procured items and allows users to select items for order or reorder. The Contractor shall make all procurement items searchable within the OWMS.

At a minimum, the PR must capture the following data from a requestor or by the Contractor in coordination with the requestor:

• PR Number

• PR Creation date

• Procurement Title / Description

• Funding Squadron

• Funding Project (JOCAS)

• Job Order Number (JON)

• Project Officer / POC Contact Information

• Preparer / Requestor Name and Contact Information

• Delivery Location

• No Later Than Delivery Date

• Estimated Procurement Receipt Date

• Shipment Origin

• Shipment Destination

• General Comments Field

• Purchasing Instructions Field

• Line Item Procurement Request List that Includes:

o Item Description o Item Part / Model Number o Recommended Vendor o Recommended Manufacturer o Brand Name Only or Equals Acceptable o Quantity Requested o Unit of Measure Requested o Original Equipment Manufacturer o Selected Vendor for Procurement o Quantity Ordered o Unit of Measure Ordered o Unit Price (USD) o Extended Price (USD) o Estimated Shipping Cost to Delivery Location o Lead Time / Estimated Delivery o Equipment Manufacture Country of Origin o ECCN / USML Category (as appropriate) o Schedule B Number or Harmonized Tariff Code o Property Type (e.g., Government Furnished Equipment, Contractor Acquired Property, Consumable) o Installation Requirements o Material Handling Requirements o Interim, En Route, or Temporary Storage Requirements o Line Items Specific Temperature Control Requirements o Expiration Date for Perishable /Shelf-Life Items o HAZMAT Classification o General Comments Field o Purchasing Instructions Field

5.3.2 Upon receipt of a PR submitted via the OWMS, the Contractor shall conduct a quality control review to ensure all PR-required fields are completed, and ensure the Contractor understands the request requirements. The Contractor shall be prepared to coordinate any adjustments, recommendations, and clarifications with the requestor, as needed.

5.3.3 The Contractor shall provide a procurement cost estimate via the OWMS within three (3) business days from the date the quality control review is concluded. The Contractor shall execute purchase orders within one (1) business day upon a PR approval by the 704 TG project manager, COR, or authorized squadron Project Officer.

5.4 Material Shipment

5.4.1 The Contractor shall provide shipment of test equipment and test articles to

CONUS and OCONUS locations to support test execution.

5.4.2 The Contractor shall adhere to ITAR and export restrictions when applicable

5.4.3 The Contractor shall develop a Shipping Request Form (SRF), made available for completion and submission via an OWMS. The Contractor shall also make available, an offline version of the SRF. In situations when a requestor cannot or does not have access to the OWMS, or sufficient resources available to create a SRF, the Contractor shall provide remote or on-site customer service support, including receiving a request over the phone and creating and submitting the SRF on the requestor’s behalf. The Contractor shall be responsible for receiving and uploading offline SRF requests into the OWMS. Additionally, the Contractor shall be responsible for receiving, processing, and uploading any ad hoc, time sensitive SRF requests into the OWMS. The Contractor shall coordinate SRF discussions and clarifications with requestors, as needed.

5.4.4 At a minimum, the SRF must capture the following data from a requestor or by the

Contractor in coordination with the requestor:

• Contractor Assigned SRF Number

• Shipment Title / Description

• Funding Unit

• Group Program Manager to include phone and email

• Unit Program Manager to include phone and email

• Shipment Requestor Contact Information, including email and phone

• Shipment Origin

• Shipment Destination

• Total Value of Shipment (in U.S. Dollars)

• Estimated Cargo Weight (Gross)

• Final Cargo Weight (Gross)

• Estimated Cargo Dimensions

• Final Cargo Dimensions

• Temperature-control Requirements (Ambient, Refrigerated, Frozen)

• Requested Mode of Transit (Air, Surface)

• Requested Shipment Tracking Options (e.g., Carrier Status

Tracking, GPS, RFID, etc.)

• No Later Than Required Delivery Date

• Identify Shipment as Repair, Replace, or Calibration Shipment

• Date Equipment Available for Pickup

• Pickup Location Organization, Address, and Point of Contact

Details

• Actual Pickup Date

• Estimated Contractor Warehouse Receipt Date

• Actual Contractor Warehouse Receipt Date

• Shipment Origin Organization, Address, and Point of Contact

Details

• Delivery Destination Organization, Address, and Point of

Contact Details

• Ultimate Consignee Organization, Address, and Point of

Contact Details

• As applicable, Intermediate Consignee Organization, Address, and Point of Contact Details

• End-User Organization, Address, and Point of Contact Details

• Requestor Shipment Reference

• General Comments Field

• Delivery Instructions Field

• Import/Export Comments Field

• Line Item Inventory List o Line Item Description o Model / Catalog Number o Vendor o Manufacturer o Quantity o Unit of Measure o Export Control Classification Number (ECCN) (If applicable) o U.S. Munitions List (USML) Category o 10-digit Schedule B Number or 8-digit Harmonized Tariff

Code, as applicable o Material / Equipment Manufacture Country of Origin o Line Item Specific Temperature Control Requirements o Shelf Life / Expiration Date for Perishable Items o Hazardous Material (HAZMAT) / Dangerous Goods

Classification o Material Handling Requirements Field o General Comments Field

5.4.5 The Contractor shall prepare shipments for domestic and international transport in accordance with industry best practices and in accordance with all laws and regulations for any mode of transit, routing, and contents. The Contractor shall also document, handle, store, transport, and deliver all shipments including, but not limited to, hazardous and environmentally sensitive material in accordance with applicable laws, regulations, and best commercial practices.

5.4.6 The Contractor shall identify shipments with simple and plainly visible placards that include the respective SRF number, 704 Test Group funding program, quantity ‘X of X’ packing units, and special handling or storage condition requirements. The Contractor shall also be prepared to accommodate any additional special shipment requirements, such as following Return Merchandise Authorization (RMA) instructions.

5.4.7 The Contractor shall present a plan for mitigating and handling shipment loss and damage risks in accordance with FAR 52.247- 22 and DFARS 252.247-7007 clause requirements on contract.

5.4.8 The Contractor shall ensure cargo transport timeliness by delivering ninety-five percent (95%) of shipments on or before a requested delivery date. The Contractor may ask to change a requested delivery date, but in doing so must specify the events requiring a requested change. Deliveries made after a requested delivery date but subject to an approved date change shall be identified during each PMR.

5.4.9 The Contractor shall provide the COR, Program Manager and squadron project officer with a freight savings analysis and other applicable justification for approval prior to conducting direct-vendor shipments.

5.4.10 The Contractor shall obtain and report shipment data in a manner that will allow requestors to easily identify the status of their shipments. The shipment status data must be updated within one (1) business day of a change in shipment status and be available in the OWMS. The shipment status shall be presented in a clear, concise, and user-friendly format to facilitate the tracking of all relevant data and information. The test group defines “user-friendly” as a format that conveys salient information on high-level shipping status in a simple and easily understood manner. At a minimum each shipment shall include the following details to allow a requestor to further investigate the status of a shipment:

• Estimated destination delivery date

• Actual destination delivery date and time

• Selected Carrier / Freight Forwarder

• Carrier / Freight Forwarder Tracking Number

5.5 Online Workflow Management System

5.5.1 704 Test Group defines the OWMS as a large-scale application software package that supports business processes, information flows, reporting, and data analytics in complex organizations.

5.5.2 704 Test Group defines “real-time” as the actual time during which an event or action takes place. The time shall be identified using United States Mountain Standard Time.

5.5.3 The Contractor shall develop and deliver an OWMS that delineates functions across the logistics services required in this task order.

5.5.4 The OWMS must be capable of accepting all logistics service requests, request tracking, accepting request revisions with a date/time stamp, generating reports, storing language terminology glossaries, and serving as a repository for all contract required documents as identified in this task order.

5.5.5 The OWMS must reflect current information, updated in real- time, for all submitted requests. Examples of current information include status updates, shipment tracking by location, and financial data (i.e., funding levels, obligations, commitments, actuals, invoices).

5.5.6 The OWMS must be capable of accepting user-defined queries and producing reports based on those queries.

5.5.7 To the maximum extent possible, the Contractor shall establish the use of drop down menu and radio button functionality in the OWMS for all request types, workflows, and search functions to facilitate data standardization.

5.5.8 The Contractor shall enable the OWMS to accept cloning of all request types for reuse, either in their entirety or in part.

5.5.9 The OWMS shall be searchable, filterable, compartmentally organized, and auditable for each request type. This functionality must incorporate the ability for truncated searches, wildcard searches and other common search methods to broaden results. 704 Test Group intent is to allow search algorithms that function in a more lenient way than hard search algorithms that only match specific and rigid results.

5.5.10 The OWMS must be capable of robust budget / financial reporting and recordkeeping, tied to real-time logistics estimates, funding levels, obligations, commitments, and actual invoiced costs. This capability must be filterable down to the individual squadron and program level.

5.5.11 All logistics services request types shall use an integrated and interoperable workflow process. It is requirement that the COR and program manager and his / her team have the capability to move any submitted request type from one workflow review step to any other review step during the process.

The Contractor shall ensure the COR, the Program Manager and his / her team can accomplish this requirement without having to submit a request for the Contractor to execute.

5.5.12 The Contractor shall configure the OWMS to allow the COR. the Program

Manager and their team to make any change to all request types at any time without the request starting over in the review process. For example, the COR, the Program Manager and his / her team shall have the ability to change line-item details to include quantities, materials, and procurement details to modify task order to meet squadron requirements. Contractor shall notify the COR, the program manager and their team of changes which make original delivery dates and deadlines associated with Task Order to be unachievable and offer solutions (e.g split delivery or other accommodations). .

5.5.13 The OWMS shall be configured to identify the actual workflow review status for each request type by using the phrase “Current Action Required”.

5.5.14 During and without disrupting the workflow review process of submitted requests, the Contractor shall develop and implement a process that alerts Squadron Commanders, Directors or their designees when a request exceeds one-hundred thousand ($100,000) so the notified party can approve or deny the request. The COR will advise the Contractor the names of individuals to be alerted.

5.5.15 The Contractor shall develop and make available a searchable executive reports section within the OWMS. This section shall allow for searched as described in other parts of this PWS.

5.5.16 The OWMS accounts of the COR, the Program Manager and his / her team shall have permission for unassisted and unrestricted access to all invoices pertaining to equipment purchases, transportation, and any others expenses associated with logistics support services that have been placed or archived in the OWMS.

5.5.17 The Contractor shall establish, provide, and maintain real-time shipment tracking information. These tracking details shall be available to all users by means of a single radio button titled “Where is My Stuff”. Upon clicking the radio button, a request box shall appear asking the user to enter a shipping request number (SRF). Once a SRF number is submitted, the results screen shall include the following details: estimated date of delivery, date shipment departed air or surface origin, date received at intermodal transit point (if applicable), date departed intermodal transit point (if applicable), arrival date at customs entry point (if applicable), customs clearance date (if applicable), loading status on truck or other vessel, departure date from customs facility (if applicable), and date of delivery to final destination.

5.5.18 The Contractor shall enable web-based and password protected access to the OWMS for all authorized users.

5.5.19 The Contractor shall develop an OWMS access request form for review and approval by the COR or the Program Manager. Users will be granted access after COR or Program Manager approval.

5.5.20 The Contractor is responsible for creating and maintaining an OWMS authorized user list based on the request forms approved by the COR, the Program Manager and their team. The Contractor shall ensure the list includes the following for each authorized user:

• First / Last Name

• Organization Name (no acronyms)

• Organization Address (city / state / postal code)

• Email

• Phone Number

5.5.21 The Contractor shall provide OWMS initial training for all authorized users.

At a minimum, training shall include OWMS access and usage, navigation, functionality and capabilities. The Contractor shall also provide follow-on/refresher training based on OWMS updates and / or specific user training as necessary or directed by the COR, the Program Manager or their staff.

5.5.22 The Contractor shall provide OWMS users with information technology

(IT) assistance to answer questions, take corrective actions, and resolve OWMS system errors.

5.5.23 The Contractor shall develop and deliver OWMS procedures manual and user quick-reference guide for preparing, submitting, and revising all request types.

5.5.24 The Contractor shall ensure information presented for government review is accurate and resulting documents align with data included in the support request. Requests that include documents with missing or unclear information shall be failed at any step during the review process.

5.5.25 The Contractor shall deactivate a user account not used after ninety (90) days, and delete a user account not used after one hundred twenty (120) days. These actions shall be undertaken by the Contractor without prior approval by the COR, the Program Manager or their team. On the first business day at the start of a new quarter, the Contractor shall provide the COR, the Program Manager and their team a report of deactivated and deleted accounts.

5.5.26 The Contractor shall develop all logistics request forms and make them available for retrieval and submission via the OWMS. The Contractor shall make all offline logistics request forms available via email.

5.5.26.1 The Contractor shall be responsible for receiving and uploading the offline logistics requests and data into the OWMS.

5.5.27 The Contractor shall be responsible for receiving, processing, and uploading ad-hoc and time-sensitive logistics requests into the OWMS.

5.5.28 The Contractor shall establish procedures to generate logistics requests on behalf of all OWMS users, when requested. This applies in situations where a user does not have access to the OWMS and must rely on submitting a logistics request via email, telephone, or other method.

5.5.29 The Contractor shall develop and implement a plan to receive and manage customer service feedback for all logistics services and record the details in the OWMS.

5.5.30 The Contractor shall provide software / hardware configuration to operate and maintain the OWMS performance, function, and design.

5.5.31 The Contractor shall maintain the OWMS for peak availability of ninety-nine point five percent (99.5%), and conduct configuration management / system maintenance as necessary or as directed by the COR or Program Manager.

5.5.32 The OWMS is required to be available twenty-four (24) hours a day, seven

(7) days a week.

5.5.33 The Contractor shall provide the COR, the Program Manager, and all OWMS users advanced notification of system downtime for maintenance, configuration, and / or modification. The Contractor shall provide the advanced notifications via email and a notification screen on the OWMS at least twenty-four (24) hours prior to system downtime.

5.5.34 All data created, transferred, received, and contained within the OWMS is considered to be U.S. Government property and intellectual data.

5.5.35 The Contractor shall adhere to the following information security requirements:

5.5.35.1 The OWMS must have no direct interface between the

Contractor’s IT network and any Air Force network. The Contractor’s OWMS shall be internet based and accessible from computers and devices linked to the Air Force network.

5.5.35.2 The Contractor must comply with DoD cyber security standards as described in DFARS Section 204.73, Federal Information Processing Standards (FIPS) Publication 200, National Institute of Standards and Technology (NIST) Special Publication 800-53, as revised, and DoD Instruction 5220.22-M National Industrial Security Program Operating Manual (NISPOM), as updated and amended.

5.5.35.3 The OWMS is an unclassified system. The Contractor shall properly handle all documents according to their markings.

5.5.35.4 The Contractor shall be prepared to handle sensitive information.

Additionally, the OWMS shall not be used to collect, store or record For Official Use Only (FOUO) information or Controlled Unclassified Information (CUI).

5.5.35.5 The OWMS shall not be used to collect, store or record Personally

Identifiable Information (PII) of U.S. citizens and aliens lawfully admitted for permanent residence. The Contractor shall use pseudonym generating or masking software built into the OWMS to protect personal information.

6.0 CONTRACT DATA REQUIREMENTS LIST (CDRL)

A001 Contractor Standard Operating Procedures: The Contractor shall prepare, submit, and maintain, in detail, a “Materials Transit and Customs Clearance” Standard Operating Procedure (SOP) as related to the execution of the task order. The SOP shall also include a quality assurance plan for all shipments.

A002 Performance and Cost Report: The Contractor shall prepare, submit, and maintain, in detail, Government approved “Performance Cost Report”.

A003 Management Plan: The Contractor shall prepare, submit, and maintain, in detail, a “Management Plan” as related to the execution of the task order.

A004 Report of Receipts, Inventory, Adjustments, and Shipments of Government Property: The Contractor shall prepare, submit, and maintain, in detail, a “Loss, Stolen, and Damaged Report” as related to the execution of this task order.

A005 Accident/Incident Report: The Contractor shall submit and maintain, in detail, a “Significant Incident Reports (SIR)” as related to the execution of this Task Order.

A006 704 Test Group Master Government Property List (MGPL) Accountability Reports:

The Contractor shall submit, in detail, “MGPL Accountability Reports” to include all Government Furnished Equipment (GFE), Government Furnished Material (GFM), Government Furnished Property (GFP), and Contractor Acquired Property (CAP).

A007 Transfer of Property (TOP) Ownership: The Contractor shall submit a TOP Cover Letter and TOP Inventory List, immediately following the physical transfer of property to the ultimate consignee or designated partner nation representative.

A008 Phase-out Transition Plan: The Contractor shall submit and maintain, in detail, a

“Phase-out Transition Plan” as related to the execution of this Task Order.

A009 Interface Design Description: The Contractor shall submit and maintain, in detail, an “Interface Design Description” as related to the execution of the OWMS.

7.0 SECURITY CONSIDERATIONS AND OPERATING CONSTRAINTS

The ATLAS contract may involve handling of classified information. Any handling, generating or access to classified information shall be conducted in accordance with the Contract Security Classification Specification, DD Form 254 incorporated into the contract. The Contractor shall be prepared to make available at least one (1) contract employee with a TOP SECRET security clearance. This individual may be a Contractor direct employee or sourced through other reach back channels. The Contractor shall ensure the individual is available to access 704 Test Group, in person, via secure video teleconference, or secure email within twenty-four (24) hours of receipt of direction by 704 Test Group to review classified information and/or receive classified briefings. 704 Test Group is the sole determining party to identify a need-to-know basis for accessing classified information. Therefore, only at the direction of 704 Test Group will the individual(s) have access to classified information at the 704 Test Group facilities or networks.