(CUI) LM_IDIQ_COMBINED_PWS_12 Jul.docx

CONTROLLED UNCLASSIFIED INFORMATION (CUI)

Performance-Based Work Statement (PWS)

Lockheed Martin (LM) Rotary and Mission Systems (RMS) Support to the Air Force Distributed Common Ground System

(AF DCGS)

FA8527-23-D-XXXX

13 June 2023 Prepared by

AFLCMC/HBG

Warner Robins Air Logistics Center 235 Byron St Robins AFB, GA 31098-1670 QASP updating

DISTRIBUTION STATEMENT D – Distribution authorized to the Department of Defense and U.S. DoD contractors only (Critical Technology) (26 October 2020). Other requests for this document shall be referred to AF GNS Data Management Office or AFLCMC/HBGW Global Network Systems (GNS), 11 Barksdale Street, Bldg 1614, Hanscom AFB, MA 01731

REVISION SUMMARY

Table of Contents

4.1.1 Contract/Order Period of Performance…………………………………………. 11

CONTROLLED UNCLASSIFIED INFORMATION (CUI)

4.5.5.1 Unique Spares

5.6.1 Contractor Compliance…………………………………………………….33

1.0 Description of Services

1.1 Objective(s):

AFLCMC/HBG maintains and deploys worldwide ground systems capable of tasking, receiving, processing, exploiting, correlating, and disseminating Multi-Intelligence (Multi-INT) information in support of Air Force (AF), Joint and coalition war fighters. The DCGS family of ground stations support multiple simultaneous worldwide operations, 24/7, by providing near-real time critical intelligence to the needed user. This allows the war fighter and decision-makers the required intelligence to maintain vigilance against threats from adversaries that would do harm to the United States and its allies. The DCGS family of ground stations provides decision-quality information to commanders and to the National Command Authority as well as up-to-date information on high value targets by providing the capability to collect, exploit, and disseminate that information in near-real time.

The Air Force Distributed Common Ground System (AF DCGS) is the lead Intelligence, Surveillance, and Reconnaissance (ISR) System used by intelligence agencies world-wide. Allowing system upgrades enables the DCGS enterprise network to maintain a high level of Operations Tempo and a high security posture.

The main objective of this contracting effort is the Development, Modernization, Integration, Fielding, Cyber Security and Sustainment activities required to meet AF DCGS/ Operational Requirements Document (ORD) requirements to maintain compliance with the Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) Architecture Framework, and the Joint Technical Architecture guidance to the maximum extent possible. Other DCGS ground and air elements will be supported as directed.

All tasks will be specifically directed by individual Task Descriptions (TD) issued under an Indefinite Delivery, Indefinite Quantity (IDIQ) Contract. Major tasks include program management, Agile project management, material procurement, engineering services, configuration management, data management, software, development, modernization, integration and fielding, and sustainment services, repair activity, sustainment services, data reporting, and travel.

This effort provides support for the Lockheed Martin Rotary and Mission Systems (LM RMS) products and services utilized for collection, correlation of data, collaboration and dissemination of signals of interest and imagery intelligence from airborne, ground, and other systems in order to provide more accurate near-real time actionable intelligence to war fighters. This effort will be accomplished by LM RMS, hereafter known as the Contractor, for the AFLCMC/HBG, hereafter known as the Government. This Performance-Based Work Statement (PWS) provides for the operation and support, as well as modifications of the systems listed below. Modifications include enhancing the capabilities of the systems through changes to the hardware and/or software, including the use of “open source, non-proprietary software”. It also provides for the expansion in the number of the existing sites/users in order to meet overall DCGS mission requirements. Finally, it allows for the incorporation of new capabilities that may be developed and required in order to meet changing DCGS mission requirements. The LM RMS provided products and services to be supported include, but are not limited to, the following within the AF DCGS Ground Segment:

The Contractor shall serve as the Design Agent for these products and services and shall be the single point of responsibility for cybersecurity compliance, configuration control, modification, integration, and sustainment of the baseline products and services. Software will be delivered and integrated using infrastructure as a service (IaaS) techniques to data centers to the greatest extent possible.

The directives and procedures contained in the C2ISR Division Configuration Management (CM) Plan apply to this contract. Contractor software/maintenance organizations shall appoint Configuration Managers. These managers shall provide CM support to their organization and serve as the single point of contact to the AF DCGS program concerning CM matters.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the United States Air Force (USAF) by ensuring support for sustained intelligence, surveillance and reconnaissance (ISR) to the warfighter.

2.0 Services Summary

Ninety percent (90%) of all testing in accordance with (IAW) the approved test procedures shall pass on the first attempt with no Category I (CAT I) Emergency or Category I Urgent deficiencies IAW T.O. 00-35D-54, USAF Deficiency Reporting, Investigation, and Resolution. The remaining 10% shall pass on the second attempt with no CAT I Emergency or Urgent deficiencies.

Consider:

Contractor shall provide documents in accordance with their respective DD Form 1423 at the appropriate time frame of the document to be delivered. The submitted documentation must reflect an accurate and complete representation with no major* and no more than five minor* deficiencies in the initial submission. There shall be no more than one round of revision and resubmission required to correct deficiencies identified in the initial submission. All identified deficiencies must be corrected in the final submittal with their respective DD Form 1423. Corrected documents shall be submitted within five business days.

*Major deficiency: Error in content of material *Minor deficiency: Typographical/grammatical error

4.6, 5.2 The Contractor shall provide qualified personnel (both technical and management) in order to meet all tasks issued under this IDIQ. Upon identification of any shortcomings that will impact tasks assigned by any Task Order associated with this effort, the Contractor shall undertake corrective action, and notify the Government within 15 calendar days.

3.0 Government Property

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

3.2 Government Property to be provided: Government property to be provided shall be identified and directed by individual Task Orders as required.

3.2.1 Support Equipment will be administered IAW Attachment 16 of the IDIQ.

3.2.2 Bonded Stock Operations and Administration: Government bonded stock operations and administration will be provided if a DCGS bonded stock facility is maintained. Administration of this item will be in accordance with Attachment 3 of the IDIQ.

3.2.3 Property Administration: Property Administration will provide for controlling and reporting on in-plant GFP in accordance with the requirements of the PWS. The Government will retain ownership of GFP upon completion of this effort. Administration will be in accordance with Attachments 15 and 18 to the IDIQ.

3.3 Reporting of Government Property: The Contractor shall create and maintain records of all Government property accountable to the contract/order. The Contractor shall record receipt and return of Government-Furnished Property (GFP) in the Item Unique Identification (IUID) Registry.

3.4 Loss of Government Property

3.4.1 Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

3.4.2 Reporting Loss of Government Property: The Contractor shall report loss of Government property using Defense Contract Management Agency (DCMA) / Access to eTools. http://www.dcma.mil/aboutetools.cfm

3.5 Return or Retention of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

For cost type and time-and-material contracts, the Government obtains title to CAP acquired or fabricated by the Contractor to perform tasks under the contract in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. CAP shall be returned to the Government upon completion of the contract unless retained by the Contractor for continued use under a successor contract. If retained by the Contractor for a successor contract, CAP becomes GFP added to the successor contract by modification of both losing and gaining contracts in accordance with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

3.6 DCGS CONTINUOUS INTEGRATION ENVIRONMENT

The Continuous Integration Environment (CIE) is the classified CTE/DGS-X system (using AF DCGS CIE CI/CD tool suites) connected to the AF DCGS weapon system's network to provide Continuous Integration (CI) capabilities: centralized software repository, automated installation, automated testing, system monitoring, and reporting. The CIE is connected to the AF DCGS weapon system and the same tools can be used to execute Continuous Deployment (CD) allowing DCGS to deploy/monitor software solution as well as operations. Information on the CIE and tools is located on Confluence/DCGS/Functional Management/Continuous Integration Environment.

The Government will provide the Contractor access to the DCGS Continuous Integration Environment facilities located at the Warner Robins Life Cycle Management Complex (WRLCMC) in Warner Robins, GA, and to DGS-X, located Langley AFB, VA, to support the efforts performed under this agreement. The CIE is operated and maintained by the 402 SWEG/577 SWESSMXS organization under the direction of the CIE Program Office, AFLCMCWRLCMC/HBGB. Access to CIE’s facilities requires a TS/SCI clearance and must be coordinated in advance with the CIE Program Office (HBGB) and the CIE Site Security Office.

4.0 Technical Requirements

4.1 Period and Place of Performance

4.1.1 Contract/Order Period of Performance: Ordering period for this contract will be five (5) years from contract award. Period of performance for individual requirements will be established in the task order.

4.1.2 Place of Performance: The Contractor’s primary place of performance will be its own facility as well as Government sites within the Continental United States (CONUS) and/or Outside CONUS (OCONUS) as specified in individual task orders. Contracts with performance in designated countries in the United States European Command Area of Responsibility: “Contractor Personnel Supporting U.S. Armed Forces Outside the United States.” As prescribed at DFARS 225.371-5(a)(3), Contracting Activities shall ensure DFARS clause 252.225-7040 is included in solicitations and contracts, including those using Federal Acquisition Regulation (FAR) part 12 procedures for the acquisition of commercial items, with performance in a country east of Sweden, Germany, responsibility (AOR) (designated countries).

4.2 Configuration and Data Management

The Contractor shall conduct CM in accordance with SAE EIA-649. The Contractor shall comply with CM requirements listed below and in accordance with the Contractor’s CM Plan. The contractor shall levy these same CM requirements to any tier of subcontractor. The Contractor shall use a CM process to control and tie, trace, and link all configuration information representing or comprising the system/configuration item. The contractor shall use Digital Engineering (DE) tools for configuration and data management processes, activities, and artifacts. The Contractor shall implement CM addressing Configuration Planning and Management, Configuration Identification, Configuration Change Management, Configuration Status Accounting (CSA), Configuration Verification and Audits, Data Management, and Deficiency Reporting. The Contractor shall generate updates to the CM Plan for Government approval. The Contractor shall measure the CM performance metrics identified in the CM Plan. (A040), DI-SESS-80858, Supplier’s Configuration Management Plan).

4.2.1 Configuration Identification.

The Contractor shall use a documented process for configuration identification IAW the CMP and the following paragraphs. The Contractor shall recommend potential CIs/CSCIs for Government review and selection concurrence utilizing the criteria in the CMP. The Contractor shall mark or label items and information with their applicable identifiers.

The Contractor shall establish and generate a CI and CSCI structure and hierarchy (A097). In addition, the Contractor shall ensure configuration information and artifacts tie, trace, and link from top-level/end item to the lowest component.

The Contractor shall develop Eracent custom software signatures IAW DCGS-PRCD-ENT-0003_Rev-7, Eracent Custom Software Integration Guide.

4.2.2 Configuration Baselines.

The Contractor shall generate the configuration information required for the configuration baselines being established by the Government IAW MIL-STD-961 and shall tie, trace and link all configuration information and artifacts to the lowest component that makes up a configuration baseline(s). The Contractor shall maintain the current approved configuration information creating a new revision to configuration information after a change approval. (A013, DI-IPSC-81442A/T, Software Version Description (SVD) using the government provided template; A032, DI-IPSC-81441A/T, Software Product Specification (SPS), )

4.2.3 Configuration Change Management

The Contractor shall apply configuration control to each CI/CSCI and its components and configuration information. The Contractor shall confirm configuration baselines are maintained and controlled, configuration identification control of all CIs/CSCIs and their associated configuration information is maintained, all configuration information and artifacts are tied, traced and linked, and the ASoT is updated. The Contractor shall support a joint Government/Contractor Configuration Control Board(s) chaired by the Government and IAW the CM

4.2.4 Data Management

The Contractor shall establish a data management program for identifying, generating/acquiring, and controlling technical and management product data and related information. The Contractor shall implement and maintain data management procedures for preparation, quality control, administration and delivery of data required by the CDRL IAW Exhibits X, XX and tie, trace and link the data to build the digital thread. The contractor shall utilize the AFLCMC approved data repository and management tool to deliver CDRL data to the Government in accordance with the CDRLs and the CDRL Instructions that are part of the CDRL package and contract. The Contractor shall maintain data status and delivery schedules for all CDRL items. The Contractor shall provide a central point of contact for data management.

4.2.5 Technical Data

The Contractor shall provide material and labor necessary to maintain engineering drawings (A015, DI-SESS-81000F/T), technical manuals (A018, TM-86-01R), Operation and Maintenance (O&M) manuals (A018, TM-86-01R), and other system documents as it applies to the baseline system and software. All documentation provided shall be prepared and administered IAW the CDRLs.

4.3 Contract Data Requirements List(s) (CDRL)

4.3.1 Task Order Integrated Master Schedules of all planned and contracted work being delivered to any system covered by this IDIQ will be generated, maintained and delivered as assigned by the applicable CDRL per the task order.

The Contractor shall consolidate monthly financial reports into an integrated program level document. This consolidated document will cover all Task Orders covered under the IDIQ.

Actual CDRL requirements will be directed by individual Task Descriptions. The following list is for reference only. Additionally, Agile Methodology may also be directed by individual Task Descriptions. Contractor will use most current Government provided format for CDRL for each Program Increment to ensure configuration management requirements are met. Verification of CDRL format will be accomplished during the PI pre-planning 30 days prior to start of PI work.

ENGINEERING DRAWINGS/ DODAF PRODUCTS

DI-SESS-81000F/T

A022A

TEST PLANS

DI-NDTI-80809B/T

DI-MISC-80508B/T

DI-MISC-80508B/T

DI-MISC-80508B/T

DI-SESS-80639E/T

DI-FNCL-80331A/T

DI-ILSS-81251/T

DI-ILSS-80525/T

DI-SAFT-81563/T

N/A

DI-ENVR-81840/T

DI-QCIC-81722/T

DI-MGMT-

81644B/T

DI-MGMT-80269/T

DI-MISC-81107A/T

DI-MISC-81943/T

DI-MISC-81306/T

4.3.2 Quality of CDRL Deliverable: There shall be no more than one rejection of any deliverable. The Government will reject a deliverable if not in the Government provided format or, if one (1) or more technical errors per 20 pages or one (1) per report for reports fewer than 20 pages. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within ten (10) business days of notification of Government rejection.

4.3.3 Receipt of CDRL Deliverable: CDRL deliverables may be submitted via Wide Area WorkFlow e-Business Suite / Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) or be submitted directly to the MFT member identified on the CDRL. The contractor shall support system integration and evaluation of the baselines using AF DCGS test environments as Agile-based iterative deliveries, in draft though each sprint and finalized when the capability, application, or service is completed to the OA DCGS-provided environment at the designated lab identified in the individual Task Orders. There shall be no more than one (1) late submission(s) of deliverables per quarter. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

4.4 Technical and Administrative Support

The Contractor shall provide support, both technical and administrative, which includes, but is not limited to, the general tasks and responsibilities identified below. The Contractor shall participate in managing the effort to include sprint planning, documenting, and tracking program performance using Jira and Confluence. The Government will provide specific Task Descriptions for each Task Order. Administration of all tasks listed below shall be in accordance with Attachments to the IDIQ, as applicable.

4.4.1 The contractor shall perform Acceptance Testing (AT) and Integration Acceptance Testing (IAT) at the DSIL as required in the individual Task Order. Additionally, the contractor shall provide on-site support at the DSIL to support these test events, the Enterprise Service Desk (ESD), and general support to the Managed Test Environment (MTE) and the Controlled Test Environment (CTE) as required in the individual Task Order.

4.4.2 The contractor shall support the AF DCGS in the migration of any remaining legacy contractor software products and applications to the Open Architecture (OA) DCGS Platform as a Service (PaaS). All new development and or modernization efforts performed by the contractor shall be executed in compliance with OA PaaS and integrate with the OA provided Enterprise Services.

4.4.3 Development activities performed under this IDIQ shall be executed using Agile/SWAP development processes with open source-nonproprietary software. The contractor shall perform Program Increment pre-planning, planning, execution and demonstrations. Specific details on the implementation and requirements of these processes will be defined in the individual Task Orders.

4.5 Sustainment

The main objective of this contracting effort is the Development, Modernization, Integration, Fielding, Cyber Security and Sustainment activities required to meet AF DCGS/ Operational Requirements Document (ORD) requirements to maintain compliance with the Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) Architecture Framework, and the Joint Technical Architecture guidance to the maximum extent possible. Other DCGS ground and air elements will be supported as directed.

All tasks will be specifically directed by individual Task Descriptions (TD) issued under an Indefinite Delivery, Indefinite Quantity (IDIQ) Contract. Major tasks include program management, Agile project management, material procurement, engineering services, configuration management, data management, software, development, modernization, integration and fielding, and sustainment services, repair activity, sustainment services, data reporting, and travel.

4.5.1 Program Management and Administrative Support

The Contractor shall establish and maintain a program management office in support of all tasks related to the IDIQ and its task orders. The Contractor shall also provide a point of contact for the Government. The Contractor shall assign a program manager (PM) responsible to plan, organize staff, administer, and control all IDIQ activities, and to ensure cost, schedule and technical objectives are achieved. The Contractor shall establish budgets, schedules, and specific tasks to meet overall program objectives. Periodic status updates shall be conducted to monitor cost and schedule performance. Contractor’s Progress Status, and Management Report (A006), Cost Funds Status Reports (CFSR) (A005), Contract Work Breakdown Structures (CWBS) (A028), Contract Performance and Cost Report (A052), and Integrated Master Schedules (IMS) (A067) will be submitted to the Government for each task order as required by the applicable Contract Deliverable Requirements Lists (CDRL). The Contractor shall attend/support management meetings as deemed necessary by the Government program office. The Contractor shall assign a Program Manager to each task order. The Contractor may assign PMs to one or more programs as required to meet Task Order requirements. Program Managers shall be available during normal business hours and be available during a regular 40 hour work week.

If a Project is deemed Agile, the Contractor shall support Agile related efforts per this document and/or the individual Task Description, which include, but are not limited to PI Pre-Planning, Planning Events Sprint Planning, scheduled Scrums, and updates to identified Wiki pages and task tracking boards located in a designated area of the collaborative web site(s), i.e. Confluence and JIRA.

4.5.2 Budgetary Cost Information

The Contractor shall provide Budgetary Cost Information (BCI) services, as requested by the Government, which are necessary to meet the requirements contained in this PWS. The Government will consider the BCI provided by the Contractor as planning estimates. The target response time for the Contractor to provide these estimates, once the scope is defined and presented to the Contractor by the Government, is five (5) business days or less. The Contractor shall provide a budgetary estimate for future proposed task orders when directed by the Government. The planning estimate shall specify the number of hours by labor category and material costs based upon the work requirements identified by the proposed task order.

4.5.3 Engineering Services

The Contractor shall provide systems engineering services through non-severable Task Orders when required to modify, expand or sustain LM RMS provided products and services, as directed by the Government, in order to meet evolving mission requirements. These modifications include changes to hardware/software that are intended to increase the capability of the systems to accomplish the overall mission.

The Contractor shall furnish the necessary infrastructure (personnel, facilities, and material) to develop, assemble, test, deliver, install and sustain software as required for the LM RMS provided products and services. The Contractor shall sustain hardware/software as required for their products and services. The Contractor shall support Developmental Testing and Operational Testing events. Additionally, the Contractor shall provide a capacity for CyberSecurity updates, patching, bug fixes, and Deficiency Reporting. The specific requirements will be defined in the Task Descriptions issued with each individual order.

4.5.4 Data Reporting

The Contractor shall consolidate monthly financial reports into an integrated program level document. This consolidated document will cover all Task Orders covered under this IDIQ.

4.5.5 Material Procurement

The Contractor shall procure spares at the required levels to support the LM RMS provided products and services necessary to meet mission requirements as directed by the Government Item Manager. The Contractor shall not change the design of a COTS end item without the prior approval of the Government. The Contractor shall process Purchase Directives (PDs) for acquisition primarily of expense and investment spares. The Contractor shall also process Government PDs for requirements other than spares. The Contractor shall provide the Government item manager assistance in determining buy, repair, or hold/delay requirements, conduct marketing surveys to determine best competitive pricing and delivery dates, accomplish procurement activities including preparation and coordination of procurement documentation, establishment of individual jacket files (electronic acceptable), and contact potential vendors. The Contractor shall receive, inspect, stock, and issue parts and maintain inventory control.

The Contractor shall collect bonded stock information and administer the program in accordance with this PWS and Attachment 3 of the IDIQ. Contractor shall prepare DD250s and assist in support of Bonded Stock Inventory and semi-annual consumption reporting.

4.5.5.1 Unique Spares

Unique spares are defined as spares specifically modified by the Contractor to meet operational system requirements.

4.5.5.2 Replenishment Spares

Replenishment Spares are end item spares that are required for the LM RMS provided products and services that are needed to meet operational requirements.

4.5.5.3 Bonded Stock

Bonded stocks are spares that are supplied by the Government and used for the repair of systems covered by this PWS, as directed by the Government.

4.5.5.4 Specialized Repair Activity (SRA)

The Contractor shall acquire material and services to inspect, test, repair, modify, calibrate, and overhaul equipment produced and utilized, including Government-furnished items. SRA will be accomplished IAW Attachment 15 of the IDIQ.

The majority of the material used in performing this task, including new items, shall be acquired as Contractor Bonded Stock and charged to the Material Procurement CLIN of the associated Task Order. However, raw material, bench stock, nuts, bolts, screws, etc., may be charged to SRA. All repair and maintenance actions for the repair activity and software development facility or purchased services shall be controlled by work orders. All work orders shall include all costs associated with the order, including maintenance, material charged to this item, purchased services, and administrative costs.

The Contractor shall comply with the following as they pertain to the SRA:

Units shall be returned to a serviceable condition and not refurbished to like new. Repairable units received without an unserviceable condition documented will be tested on the SRA System to determine the action required. Details of the condition found will be documented, and SRA action will be performed to correct the condition.

Repairable units will be inspected upon receipt for obvious shipping damage and/or conditions of field repair/rework that could affect diagnosis or cause damage to testing devices.

Cosmetic appearance will be corrected only if the condition affects or will degrade the operational effectiveness of the repairable unit.

4.6 Weapon System Integration Management (WSIM) Manpower Support When directed by a Task Order, the Contractor shall provide WSIM support to the Government. This effort entails liaison with associate contractors, program managers, site representatives, the Government Program Office, and other entities as required regarding upcoming and current system upgrades, system maintenance operations, and new subsystem additions/integrations at its own facility and customer directed sites, as specified in individual Task Orders.

4.7 Subject Matter Experts

The Contractor shall provide Subject Matter Experts (SME). Qualification, duties, and responsibilities of SME personnel shall be contained in individual Task Descriptions. The Contractor shall provide SME representatives the necessary administrative equipment and materials to perform their tasks that are not already provided by the host unit.

4.8 Item Unique Identification (IUID) Requirements

The IUID Program requires each qualifying Air Force (AF) asset to be uniquely identified with a permanent marking per MIL-STD-129P that can sustain its information throughout the life of the asset. The program addresses two categories of assets—those already in the AF inventory and those currently under contract but not currently in the AF inventory. For assets under contract, IUID requirements are specified in Defense Federal Acquisition Regulation Supplement (DFARS) 252-211.7003, Item Identification and Valuation and Department of Defense (DoD) 4100.39-M, Federal Logistics Information System (FLIS). All assets subject to marking must be recorded in the DoD IUID Registry.

4.8.1 IUID Marking Plan

The Contractor’s IUID Marking Plan shall fully detail and document the strategy and scope to be used to meet MIL-STD-130, DoD Standard Practice Identification Marking of US Military Property. The plan must be approved by the government prior to implementation.

4.8.2 IUID Marking Activity and Verification Report.

The contractor shall provide an IUID Marking Activity and Verification Report. A key attribute for the report is the Verification column which indicates pass/fail for each item’s Data Matrix Symbol Quality.

4.9 Packaging: The Contractor shall package and mark material in accordance with the contract/order Air Force Materiel Command (AFMC) Form 158, Packaging Requirements, current AF DCGS Security Classification Guide, and applicable Government regulations. The Contractor shall ensure that classified material is packaged, marked and delivered in accordance with 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM).

4.10 Holidays and Facility Closings: Contractor/subcontractor personnel shall observe holidays and facility closings as directed by the Contractor. Contractor/subcontractor personnel shall only be permitted access to Government facilities when Government personnel are present.

4.11 Travel: The Contractor shall travel to support the various efforts associated with this IDIQ as required by individual task descriptions and directed and approved by the Government Program Manager and Procurement Contracting Officer. The contractor shall comply with destination access and health requirements with a timely coordination of the same, prior to travel. Contractor travel shall be accomplished in accordance with FAR 31.205-46 and shall be approved by the PCO in advance of travel occurring. The format for travel request submission will be as prescribed by the Government PMO/PCO. The PCO and the PM shall be notified of travel at least three (3) business days in advance of the planned travel date whenever possible. The Contractor shall coordinate travel details into country, through country, and out of country in support of OCONUS on-site efforts. These efforts include travel and documentation support for the system administrators, and system installers as necessary, and any other OCONUS travel requirements as defined by the Government PM. Furthermore this task requires the coordination, identification, and managing system administrators’ transition into and out of country once an administrator rotation has been completed.

5.0 General Information

5.1 Continuation of Mission-Essential Services During a Crisis: The Functional Commander or civilian equivalent has determined these services are not mission-essential and will not continue in the event of a crisis.

5.2 Security Requirements

5.2.1 Security Regulations: The Contractor shall comply with the provisions of the National Industrial Security Program Operating Manual (NISPOM) (32 CFR Part 117). The Contractor shall ensure requirements for safeguarding classified information and classified materials, for obtaining and verifying personnel security clearances, for protecting Government property, and for the security of automated and non-automated information systems (AIS) and date are fulfilled. The Contractor’s AIS shall be protected such that unauthorized disclosure of classified and/or sensitive but unclassified information is prevented.

The Contractor will maintain a security program in accordance with this PWS, Intelligence Community Directive (ICD) 503, the Joint DODIIS/Cryptologic SCI Information Systems Security Standards (JDCSISSS), the Contract Security Classification Specification (DD254, Attachment 2), current AF DCGS Security Classification Guide, and any other applicable directives outlined in the individual Task Orders. In case any of these publications contain conflicting guidance as to the classification of information, the higher classification will take precedence.

Additionally, the Contractor’s development systems will be maintained by a security program in accordance with the National Industrial Security Program Operating Manual (NISPOM). Those systems (and/or groups of systems) that are delivered to customer sites have been granted an exemption to NISPOM requirements and to Defense Security Service (DSS) annual auditing requirements.

As the Department of Defense (DoD) makes the transition from DCID 6/3, ICD 503, and JDCSISSS to the Committee on National Security Systems Instruction (CNSSI) 1253 and the National Institute of Standards and Technology (NIST) 800-53 control standards, the Contractor will abide by all required security standards. These security requirements are defined and directed by the Air Force Intelligence, Surveillance, and Reconnaissance Agency (AFISRA) Director of Information Assurance (DIA).

Any full-time Contractor employees occupying physical space on Robins AFB, Georgia, will comply with the AFLCMC/HBG Security Education and Awareness program. The program consists of three components: initial training, annual refresher training, and periodic tailored training.

5.2.2 Operations Security (OPSEC): The purpose of OPSEC is to reduce the vulnerability of USAF missions to adversary collection and exploitation of critical information. The Contractor shall comply with DoD 5205.02E and DoD Manual 5205.02-M to protect United States (U.S.) Government interests.

5.2.3 CyberSecurity:

Provide systems and or software/applications [provided/delivered] that can gain accreditation or are approved and operated under an Authority to Operate (ATO) by the Designated Authorizing Official (DAO).

Software Development:

It is the Government’s objective for the contractor to develop secure, reliable, resilient, assured software:

· The contractor shall develop a secure coding guide which specifies language, required constructs/practices/patterns, prohibited constructs/practices/patterns, software comment requirements

· The contractor shall implement formal (e.g., Fagan) design and code inspections

· The contractor shall verify all code against the Common Weakness Enumeration(CWE), Common Vulnerabilities and Exposures(CVE), Open Web Application Security Project(OWASP)

· The contractor shall perform an origin analysis of all third-party libraries and frameworks used and ensure the versions used in the delivered software have no publicly known vulnerabilities and continue to review for newly reported…