2014-05-07_SOW_(releasable).pdf

STATEMENT OF WORK (SOW)

FOR

RAPID ACQUISITION OF PRODUCTS, STUDIES & DEMOS

(AGILE ACQUISITION STRATEGIC SOURCING IDIQ)

1.0 SCOPE. This Agile Acquisition Strategic Sourcing Indefinite Delivery, Indefinite Quantity (AASS IDIQ) contract will provide a vehicle for Eglin armament customers to execute non-program of record efforts related to the armament mission. The scope of this contract is expected to include weapon/capability studies, demonstration of weapon capabilities, production reports and various ancillary products associated with existing systems and/or new systems. We anticipate this action will be awarded to multiple large businesses, and up to three small businesses with a base year and four option years and a total value not to exceed $490,000,000.

1.1 Background. This Statement of Work (SOW) defines the requirements for design, engineering development, fabrication, demonstrations, studies, test of prototypes, hardware/software modification, data collections and/or analysis in support of demonstrations, development, proof of concept demonstrations and Quick Reactionary Capability (QRC) programs. This may include demonstrations of existing or modified systems and technologies, to determine and/or validate systems capabilities. This may also encompass possible QRC’s, surge activities, short lead-time objectives for existing or non-existing weapons. Additional work could be required from the associated program management, human engineering, and logistic support planning requirements.

1.2 Objective. The primary objective of this contract is to provide rapid response, surge capacity and flexibility to meet the short lead-time, system development, rapid prototyping, demonstrations, hardware mods, proof of concept demonstrations, and system integration efforts. This AASS IDIQ will serve as a contract vehicle to support short-term systems development efforts to satisfy warfighter needs efficiently and expeditiously.

2.0 APPLICABLE DOCUMENTS. In the event of conflict between the documents referenced herein and the contents of this SOW, the contents of this SOW shall be considered a superseding requirement. Referenced specifications and standards specified herein apply and will be further stated in each Delivery Order.

2.1 Government Documents.

a. Applicable portions of the following documents, as referenced and modified by this SOW, form part of this SOW.

(1) MIL-DTL-31000B, Detail Specification: Technical Data Packages, December, 14, 2001

(2) IEEE/EIA 12207 Information Technology-Software Lifecycle Processes, May 27, 1998 http://www.everyspec.com/MIL-SPECS/MIL-SPECS-MIL-DTL/MIL-DTL-31000B_10914/ http://www.everyspec.com/MIL-SPECS/MIL-SPECS-MIL-DTL/MIL-DTL-31000B_10914/ http://www.everyspec.com/MIL-STD/MIL-STD-0300-0499/MIL-STD-498_NOTICE-1_25498/ http://www.everyspec.com/MIL-STD/MIL-STD-0300-0499/MIL-STD-498_NOTICE-1_25498/

(3) AFOSH Standard 161-9 - Exposure to Radio Frequency Radiation, May 1992

(4) AFOSH Standard 161-10 - Health Hazards Control for Laser Radiation, May

(5) DOD-5220.22-M, “National Industrial Security Program Operations Manual” (NISPOM), February 28, 2006

(6) DoD 5220.22-R, “Industrial Security Regulation,” December 4,1985

2.2 Non-Government Documents.

(1) “CMMI® Guidelines for Process Integration and Product Improvement”, Second Edition, Carnegie Mellon Software Engineering Institute, March 20, 2011

3.0 REQUIREMENTS. The contractor shall support mission areas of the Armament Directorate (AFLCMC/EB), Armament Systems Directorate (AFLCMC/XZW) and SOCOM Det 1 (see Appendix A) and its subordinate units as specified and ordered under individual Delivery Orders (DO). The types of efforts the contractor shall be required to perform are exemplified by, but not limited to, the following functional areas: Design, Engineering Development, Fabrication, Demonstration Studies (Demo’s), Testing, Hardware/Software Modification, Data Collections and/or Analysis in support of demonstrations or development. This may include demonstrations of existing or modified systems and technologies, to determine and/or validate systems capabilities. This may also encompass possible Quick Reaction Capabilities, surge activities, short lead time objectives for existing or non-existing weapons. Some requirements may delve into areas associated with program management, human engineering, and logistic support planning. An expanded version of the SOW with additional detailed requirements for each subsection will be made available to interested parties who are vetted and abide by the NOFORN conditions.

3.1 Design, Engineering Development. The contractor shall perform system design activities and related engineering support functions.

3.2 Fabrication. The contractor shall be capable of building mockups, prototypes and production units of subcomponents and/or all up rounds (AURs).

3.3 Testing. Testing shall be accomplished by inspections, analyses, demonstrations, and tests. Component and subsystem testing shall be performed by the contractor to verify component, subsystem, or system characteristics and performance prior to assembly and integration of the total system. Records of inspection and test data shall be kept complete and available to the Government. The Government reserves the right to perform any of the inspections or tests set forth in this statement of work where such inspections or tests are deemed necessary to ensure that supplies and services conform to the prescribed requirements. System qualification shall be accomplished with the total system. System tests, plans, and procedures shall be accomplished/generated by the contractor, approved by the Government, and practiced (dry run) until the deliverables are ready for final http://www.everyspec.com/search_result.php?cx=partner-pub-0685247861072675%3A94rti-pv850&cof=FORID%3A10&ie=ISO-8859-1&q=AFOSH+Standard&siteurl=www.everyspec.com%2FMIL-STD%2FMIL-STD-0300-0499%2FMIL-STD-498_NOTICE-1_25498%2F&ref=&ss=1660j270400j15 http://www.everyspec.com/search_result.php?cx=partner-pub-0685247861072675%3A94rti-pv850&cof=FORID%3A10&ie=ISO-8859-1&q=AFOSH+Standard&siteurl=www.everyspec.com%2FMIL-STD%2FMIL-STD-0300-0499%2FMIL-STD-498_NOTICE-1_25498%2F&ref=&ss=1660j270400j15 http://www.everyspec.com/search_result.php?cx=partner-pub-0685247861072675%3A94rti-pv850&cof=FORID%3A10&ie=ISO-8859-1&q=AFOSH+Standard&siteurl=www.everyspec.com%2FMIL-STD%2FMIL-STD-0300-0499%2FMIL-STD-498_NOTICE-1_25498%2F&ref=&ss=1660j270400j15 http://www.dss.mil/documents/odaa/nispom2006-5220.pdf http://www.dss.mil/documents/odaa/nispom2006-5220.pdf http://biotech.law.lsu.edu/blaw/dodd/corres/html/522022r.htm http://www.amazon.com/CMMI-Development-Integration-Improvement-Engineering/dp/0321711505 http://www.amazon.com/CMMI-Development-Integration-Improvement-Engineering/dp/0321711505 demonstration to Government representatives. Final acceptance shall be accomplished after successful completion of installation, checkout, and final demonstrations. (DI-ILSS- 80134A, DI-NDTI-80566A, DI-NDTI-80603A, DI-NDTI-80809B, Design of Experiments) Tests may consist of the examination of components, subassemblies, and systems in a variety of environments and through range of conditions.

3.4 Hardware/Software Modification. Modifications may consist of any change to existing armament systems including physical and/or logical components to assess an upgrade, degradation, or enhancement to the system’s performance.

3.5 Logistics. Address life cycle elements related to design proposal.

3.6 Demonstrations/Studies. Demonstrations and studies may be performed on early concepts through operational systems and may assess potential contributions to warfighter capabilities through actual performance in an operational environment.

4.0 MANAGEMENT, ADMINISTRATION AND SECURITY.

4.1 Subcontract Management. The contractor shall be responsible for any subcontract management necessary to integrate work performed on this contract and shall be responsible for subcontractor performance on each task. The contractor shall provide a list of all subcontractors with their initial proposal for approval at time of contract award. Any time the contractor desires to add or delete a subcontractor, prior approval of the CO is required. Requests must be submitted in writing within 15 calendar days of desired change.

Under no circumstances will a change be requested or approved within the first 6 months of contract award.

4.2 Small Business Set Aside. Small Business contractors are required to adhere to clause FAR 52.219-14, Limitations on Sub Contracting, at least 50 percent of the total cost of contract performance incurred for personnel shall be expended for employees of the small business prime; this compliance is on a continuous basis. Actual compliance will be monitored through the monthly cost and performance reports.

4.3 Documentation. All required reporting/documentation shall be developed, delivered, or presented as specified in each individual DO.

4.4 Specifications. All required referenced specification and standards will be identified within each DO and will be available as required at the delivery order level.

4.5 Security Administration. The nature of the contract requires contractors to possess a high degree of security awareness. The contractor shall have a sound industrial security program to provide for the protection of classified defense information. Further, Government-furnished equipment/property must be reasonably protected from loss, theft, or unauthorized use. The contractor shall be responsible for understanding security obligations for the formulation of adequate regulatory procedures in the safeguarding of classified defense and other protected information as well as ensuring contractor personnel possesses the appropriate level of security. Contract security requirements and contractor access to classified information shall be in accordance with the “National Industrial Security Program Operating Manual (NISPOM) and as specified in the contract DD Form 254 (Contract Security Classification Specification) and the DO specific DD Form 254.

4.5.1 Contractor Identification. The contractor shall furnish corporate identification badges to all contractor and subcontractor personnel authorized to work on Government installations. Costs for providing the corporate identification badge is the sole responsibility of the Contractor. While in Government facilities, all contractor employees shall conspicuously display their corporate identification badge and any government-issued identification badge above the waist at all times to allow for easy identification as a contractor employee or authorized subcontractor performing work for the contractor. Badges shall be worn at all times when contractor employees are collocated on a Government installation or when on temporary duty (TDY) working with other Government personnel. Subcontractor employees’ identification badges shall identify their respective prime contractor.

4.5.1.1 Contractor personnel and their subcontractors must identify themselves as contractors or subcontractors during all meetings, telephone conversations, in electronic messages, or correspondence related to this contract.

4.5.2 Visitor Group Security Agreement. With the assistance of Industrial Security Office, the contractor shall enter into a Visitor Group Security Agreement.

[reference AF Federal Acquisition Regulation Supplement (AFFARS) Clause 5352.204-9000, Notification of Government Security Activity and Visitor Group Security Agreements].

4.5.3 Classified Visit Requests. The contractor shall be responsible for processing classified visits via the Joint Personnel Adjudication System (JPAS) in support of tasks within DoD. The contractor must determine that the visit is necessary and that the purpose of the visit cannot be achieved without access to, or disclosure of, classified information. Contractors shall establish procedures to ensure positive identification of visitors, appropriate personnel security clearance, and need-to-know prior to the disclosure of any classified information, and ensure that visitors are only afforded access to classified information consistent with the purpose of the visit. Classified visits outside DoD will require Visit Authority Letters (VALs) IAW National Industrial Security Program Operating Manuel (NISPOM), DoD 5220.22-M.

5.0 CONTRACT DATA REQUIREMENTS LIST (CDRL).

5.1 Contract Level Reporting. Contract level reporting is identified in accordance with CDRLs. Below are potential examples of the basic CDRLs in each DO. CDRLs will be determined by each Program Manager who submits a proposal for inclusion into the AASS IDIQ contract.

(1) DI-MGMT-80227 Contractor's Progress, Status and Management Reports

(2) DI-ADMIN-81373 Presentation Material

(3) DI-NDTI-80566 Test Plan

(4) DI-MISC-80711 Scientific & Technical Reports.

6.0 DELIVERY ORDERS (DOs).

6.1 All delivery orders will be competed between Contractors, unless the Contracting Officer limits competition in accordance with one of the exceptions at FAR 16.505(b)(2). Specific performance and data requirements will be delineated in each delivery order. The Contractor shall use the DO procedures in Section H __________of the contract to respond to requests for proposal. Evaluation Procedures for DOs are outlined in Section H ________________

6.2 Pre-performance Conference. A pre-performance conference/teleconference may be conducted with the using organization and contractor personnel within 3 calendar days of DO start date. The purpose of the pre-performance conference shall be for Government and contractor personnel to meet to review DO requirements, schedule, and expectations.

6.3 Delivery Order Closeout. Upon submission of the final invoice in Wide Area Workflow, DCMA will coordinate contract close out.

6.3.1 Delivery Order final invoice submission shall be coded with a “Y” in WAWF under the heading “Final”, and with a “Z” as part of the WAWF invoice number.

Additionally, the WAWF description shall include a statement that the invoice is the final for that delivery order.

6.3.2 The final invoice shall include supporting documentation showing a breakdown by Contract Line Item Number (CLIN) showing totals expended for each CLIN, and shall show the final amounts expended for the prime contractor and all subcontractors.

6.3.3 DO Completion Meeting. When specified in individual DOs, the contractor shall conduct a DO completion meeting with the using organization to present the results and conclusions of work performed under each DO.

6.4 Material Requirements. DOs that require use of materials (other than Government-furnished) shall identify such material requirements in the contractor’s DO proposal.

Material purchases shall be authorized and approved by the CO prior to purchase. Funding for approved material expenditures shall be provided at the DO level. Competitive quotes from at least three vendors are required for material purchases of $3,000 or more. Receipts for material purchases shall be submitted with invoices. Material costs will be reimbursed IAW FAR Part 31, Cost Principles.

6.5 DO Level Reporting. Task requirements will be determined individually by the using organization or functional office and conveyed to the contractor via the DO Statement of Objective (SOO)/Statement of Work (SOW), or Performance Work Statement (PWS) as appropriate. Specific performance and data requirements will be specified in each DO. DO will identify specific required deliverables.

7.0 GOVERNMENT FURNISHED PROPERTY (GFP).

7.1 GFP will be addressed at the individual delivery order level.

7.2 The Government shall provide required technical data, drawings etc., when required at the DO level. The DO will require each respondent to officially request the documents in writing, via e-mail. To validate the documentation release, the request must include: the company’s name, mailing address, e-mail address, point of contact, phone number, current CAGE number and System for Award Management (SAM) registration and certification through the Defense Logistics Agency, Logistics Information Service, Joint Certification Program (JCP). Information for JCP is found at http://www.disa.dla.mil/jcp/. The written request must include acknowledgement of the Responder’s responsibility under the U.S. Export contract laws and regulations to include their DD Form 2345 Militarily Critical Technical Data Agreement.

8.0 ENVIRONMENTAL IMPACT.

8.1 Environmental. The contractor shall develop procedures that comply with all applicable federal, Executive Orders, state and local laws, regulations, ordinances, and standards, as well as Air Force instructions and operating procedures including permit conditions as required by individual delivery orders to include: (DI-SAFT-80106B, DI-

MGMT-81398A)

8.1.1 An environmental impact for applicable tasks in accordance with the National Environmental Policy Act of 1969 and AFI 32-7061.

8.1.2 A Hazard Communication Program in accordance with 29 CFR 1910.1200. The contractor shall provide a copy of this document to the Government upon request.

http://www.disa.dla.mil/jcp/

8.1.3 Hazardous wastes identification, characterization, containerization, transportation, storage, and disposal in accordance with federal guidelines found in Code of Federal Regulations, 40 CFR parts 260-270 and 49 CFR parts 100-177.

8.1.4 Identification of hazardous materials in a hazardous material control plan.

8.1.5 Pollution prevention in accordance with the Pollution Prevention Act of 1990 and Executive Order 12856.

8.1.6 Air pollution and emission controls in accordance with the Clean Air Act and 1990 amendments.

8.1.7 Federal Acquisition, Recycling and Waste Prevention in accordance with Executive Order 12873, 20 Oct 93 which requires the purchase of supplies and services using recycled products and minimization of the amount of waste generated.

8.1.8 Toxics Release Inventory (TRI) requirements established under the Emergency Planning and Community Right-to-Know Act (EPCRA) of 1986.

9.0 GENERAL INFORMATION.

9.1 Place of Performance. The contractor may be required to perform work at Government facilities, its own facilities, or at other facilities. The individual DOs will specify the location where work is to be performed. Work shall be performed at Government, prime contractor (hardware or software developer and/or producer), or subcontractor facilities, unless otherwise approved by the Government CO. Locations of work will be designated in each delivery order. Travel to other Government facilities or other contractor facilities may be required and will be specified in each DO.

9.2 Operational Site.

9.2.1 Contractor access to Government systems/equipment shall be scheduled at least 30 days in advance. Access will be provided during normal site operating hours unless agreed to or specified otherwise in the delivery order. Requirements for other than Government systems/equipment will be specified in individual delivery orders.

9.2.2 The contractor shall schedule his activities to minimize downtime.

9.2.3 During the installation, checkout, and test periods, unless otherwise directed by delivery order, the Government or its representative will maintain and operate the basic systems. The contractor shall be responsible for all modified components and contractor furnished hardware and software during these periods.

9.3 Travel Requirements. The contractor shall be required to travel using commercial air and other conventional modes. Travel requirements will be identified in individual delivery orders. Authorized travel under this item shall be reimbursed at cost as limited by FAR 31.205-46(a).

9.4 Release Authority. Release of reports, data, materials, or other information obtained or generated under this contract is not authorized unless written approval from the CO is provided.

9.5 Organization Conflict of Interest. Some products supplied under the anticipated delivery Orders may include data/requirements that would become part of follow-on performance work statements, statements of work or Statement of Objectives. Also there is the possibility of gaining access to other contractor's proprietary information. Such activities create a signification potential for conflicts of interest as set forth in FAR 9.505-1, 9.505-2, 9.505-3, and 9.505-4. Contractors should not engage in any other contractual or other activities which could create an organizational conflict of interest with its position under this contract; which might impair their ability to render unbiased advice and recommendations; or, in which it may derive an unfair competitive advantage as a result of knowledge, information, and experience gained during the performance of this contract.

Therefore, the Contractor agrees to seek prior written approval of the Contracting Officer before participating in any work that may involve such a conflict. Contracts will further agree to not release, disclose, or use in any way that would permit or result in disclosure to any party outside the government any information provided to the Contractor by the Government during or as a result of performance of this task order. Such information includes, but is not limited to, information submitted to the Government on a confidential basis by other persons. Further, the prohibition against release of Government provided information extends to cover such information whether or not in its original form, where the information has been included in Contractor generated work, or where it is discernible from materials incorporating or based upon such information. This prohibition shall not expire after a given period of time.