FINAL_PWS_FA704615R0001-0003_21_Oct_15.docx
DOCX document 44 KB Posted
- Attached to
- Fighter Test Services (FTS) Industry Day Federal contract opportunity
- Solicitation number
- FA7046-15-R-0001
About this file
Task Order 0003 PWS
View the file
Other files for this federal contract opportunity
Show all 27
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
FA7046-15-R-0001
PERFORMANCE WORK STATEMENT
Task Order 0003 AFOTEC/A-3Z Fighter Test Services 21 October 2015
1.0 SCOPE
This effort shall be conducted pursuant to the provisions of the Fighter Test Services (FTS) contract Performance Work Statement (PWS) paragraphs 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6 and 3.7. The objective of this effort encompasses aspects of the following FTS Core Competencies: Mission Level, Man-in-the-Loop Modeling and Simulation (Requirements and Verification, Validation and Accreditation (VV&A)). This task order supports operational assessments (OA) and initial operational test and evaluation (IOT&E) of modernization efforts for the F-22 aircraft and 4th generation fighter aircraft upgrade programs. The contractor shall work in a collaborative test environment with some or majority of tasks being performed jointly. Place of classified performance is AFOTEC/A3Z, Bldg 20129, Kirtland AFB, NM. The contractor shall perform the task in sections 3.0 and 5.0 as applicable.
1.1. Background. AFOTEC Det 6, headquartered at Nellis AFB, NV, is the lead for all AFOTEC fighter and fighter system OT&E with the exception of the F-35. Det 6 is currently tasked to conduct testing of the F-22A Increment 3.2B and Tactical Mandates upgrade programs. Operational test activities for these programs will occur at test ranges and test facilities to include the Nevada Test and Training Range (NTTR), Utah Test and Training Range (UTTR), Eglin Gulf Test and Training Range (EGTTR) and the Air Combat Simulation (ACS). The ACS, located at the Lockheed Martin contractor facility in Marietta, GA, was accredited for use in determining mission level effectiveness during F-22A IOT&E and Increment 3.1 FOT&E. Although not accredited as a test capability, the ACS was used for scenario development in FOT&E Increment 1, FOT&E Increment 2, and FOT&E Increment 3.2A. AFOTEC plans to use the ACS for F-22A Increment 3.2B scenario development and mission level effectiveness evaluation which will require VV&A of the simulator.
2.0 APPLICABLE DOCUMENTS
2.1. FTS Guidance. Guidance contained in the FTS PWS Section 2.0 applies to this task order.
2.2. Operational Test Related Documents. The following documents are also applicable to this task order (the contractor shall use the most current version):
2.2.1. F-22A Enhanced Global Strike Capability Production Document (CPD), 4 Jan 2007 (classified)
2.2.2. Concept of Operations Air Force Global Strike (GS) and Global Persistent Attack (GPA) CONOPS (in CPD), 23 Apr 07
2.2.3. Operational Capability Definition Document for F-22A increment 3.2A Modernization Program, Rev A, 27 Apr 2011 (in its entirety)
2.2.4. F-22A Operational Capability Definition Document (OCDD) for Increment 3, Rev A 3.2B (classified), 21 Dec 11 (in its entirety)
2.2.5. F-22A Increment 3.2B Test and Evaluation Master Plan (TEMP), V15, 7 Jan 2013 (or most current version, in its entirety)
2.2.6. F-22A IOT&E 3.2B Initial Test Design Briefing, 6 Dec 2011 (in its entirety)
2.2.7. AFI 33-332 Records Management Program, most current version (paragraphs 1, 1.1, 1.3, 2, 5, 5.1, 5.2, 5.3, 5.4, and 5.5)
3.0 PERFORMANCE REQUIREMENTS
3.1. Management Requirements. The contractor shall provide a management structure to ensure efficient management of this effort in compliance with Section 3.1 through 3.6.2 of the A3Z Fighter Test Services Performance Work Statement (PWS). (A001, A002, A003)
3.2. Test Capabilities. The contractor shall augment the government in performing the following tasks:
3.2.1. Review and edit test capability requirements for modeling and simulation tools to support M&S in OT&E. Identify and provide input on shortfalls, trade-off analyses, and recommend approaches to solve M&S issues. (A004)
3.2.2. Identify, participate in the development, modification, verification, and/or validation of modeling and simulation tools that represent real world entities by means of computer models, virtual tools involving real people operating simulated systems and live tools involving real people operating real systems. (A004)
3.2.3. Participate in the development and coordination of, and support the approval of verification, validation, and accreditation (VV&A) plans and/or reports for the AARI, ACS, and other M&S tools. Review M&S tool developer's verification and validation (V&V) plans and reports and identify and provide input on test capability risk areas and/or limitations. (A004)
3.2.4. Train government personnel in the basic concepts, foundations associated with models and simulations.
3.2.5. Review, participate in the development of, and or application of data management and analysis techniques, methodologies and tools for M&S during OT&E.
3.2.6. Review and provide inputs on modifications required to AARI graphical displays, user interfaces, and weapon models beyond existing AARI toolset to meet test execution and data requirements. (A004)
3.2.7. Review and provide input on test facilities and the use of these test facilities with the configurations of hybrid environments such as the USAF's Benefield Anechoic Chamber (BAF) or the USN's Air Combat Environment Test and Evaluation Facility (ACETEF). (A004)
3.2.8. Review and provide inputs on the uses and limitations of constructive models such as BRAWLER, ESAMS, and Threat Modeling and Analysis Program (TMAP) in their stand alone format.
3.2.9. Review and provide input on the uses of model confederations and simulations such as Digital Integrated Air Defense System (DIADS), Boeing's Virtual Warfare Center (VWC) or Lockheed Martin's ACS.
3.3. Test Planning. The contractor shall augment the government in performing the following tasks:
3.3.1. Provide modeling and simulation inputs to develop and/or revise the Initial Test Design (ITO) and the Test Concept.
3.3.2. Provide input to develop and/or revise the modeling and simulation methodologies in OA and OT&E test plans, DMAPs, DTPs, test planning briefings, and schedules. (A004)
3.3.3. Provide modeling and simulation expertise to participate in the development of and/or revise AFOTEC portions of test documentation such as test team charters, test and evaluation master plans (TEMPs), and integrated test plans. (A004)
3.3.4. Review and provide input on fighter capabilities with special emphasis on the kill chain (i.e., the Find, Fix, Track, Target, Engage, and Assess (F2T2EA) and the interactions needed to adequately model the kill chain.
3.3.5. Provide input to describe both the detailed phases of engagement (i.e., the phenomenology of detection, tracking, etc.) as well as the overall impacts on lethality or survivability.
3.3.6. Use M&S results to assist in refining test plans and procedures.
3.3.7. Provide input to establish procedures and criteria for validation and verification to support the AFOTEC accreditation process.
3.4. Test Execution. The contractor shall augment the government in performing the following tasks:
3.4.1. Participate in the execution of test plans, data management and analysis plans, and detailed test procedures.
3.4.2. Review and provide input for the use of Mod/Sim in developing test procedures, conducting test team training, executing test rehearsals and assessing readiness to test. Analyze M&S results and provide operational validation evidence input supporting AFOTEC accreditation.
3.5. Test Evaluation. The contractor shall augment the government in performing the following tasks:
3.5.1. Participate in the collection, compilation, review, and analysis of test data.
3.5.2. Test Reporting. The contractor shall augment the government in performing the following tasks:
3.5.3. Provide inputs to briefings as a part of the report coordination process. M&S accreditation inputs should indicate whether the M&S can be used as intended and, where not, specify the limitations for that use or caveats to be placed on the results.
3.5.4. Participate in the development of, and provide inputs to, quick-look, interim, and final reports.
4.0 SERVICE SUMMARY ITEMS
| Performance Objective |
| PWS Ref |
| Performance Threshold |
| Provide responsive Task Order/team management including quick response to contingencies, Task Order modifications or change orders. |
| 3.1 |
| Clear, consistent, and timely written and verbal communication (i.e., returns phone calls, emails or other communication attempts within 1 working day) with no more than 1 customer complaint per quarter. |
| Deliverables are completed in an accurate and timely manner. |
| All |
| Within each task order, no more than one late document per month and no more than five calendar days late. No more than two sets of corrections/edits and all corrections must be accomplished within two working days. |
| Contractor successfully meets requirements of Task Order. |
| All |
| Contractor receives no more than two formal customer complaints/contract discrepancy reports per Task Order. The contractor successfully resolves customer complaints within 10 working days of receipt, 100% of the time. |
| Assured Task Order Cost/Schedule Control. |
| 3.1.1 |
| The Monthly Status and Funds & Man-Hour Expenditure Reports will be used as tracking tools to identify impact on budget and schedule. Actual task order expenditures shall be within 10% of approved task order price. Meets task order schedule requirements. |
| Comply with applicable portions of the DD Form 254 for Task Order requirements. |
| All |
| Compliance is mandatory; no failures to meet security requirements are acceptable. Each security infraction, inadvertent disclosure and violation must be identified to the government within 1 working day and resolved within 30 working days to the government’s satisfaction. |
5.0 GENERAL INFORMATION
5.1. The Government will neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for individual Contractor employees. It shall be the responsibility of the Contractor to manage their employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the Contractor feels that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor’s further responsibility to notify the PCO immediately.
5.2. Contracting Officer Authorization. The Contracting Officer shall be the only individual authorized to direct and/or redirect the effort or in any way amend any of the terms of this contract, other than those instances specifically delegated to an Administrative Contracting Officer or a Termination Contracting Officer by a contract clause of this contract or in writing by the Procuring Contracting Officer (PCO). For purposes of this contract "the Contracting Officer" is the individual located at the issuing office, and may be abbreviated as "CO" or "PCO". Any changes made by the contractor WITHOUT CO authority will be made at the contractor's own risk.
5.3. Hours of Work and Contract Holidays. The contractor shall provide services Monday through Friday, except for Federal Holidays. Occasional weekend work may be required and will be coordinated between the Government and the contractor. The prices/costs in Section B of the contract include holiday observances; accordingly, the Government will not be billed for such holidays, except when services are required by the Government and are actually performed on a holiday. Holidays in addition to those reflected in this contract, which are designated by the Government, will be billable provided the assigned Contractor employee was available for performance and was precluded from such performance. The following days are contract holidays:
| (1) | New Year’s Day |
| (2) | Martin Luther King’s Birthday |
| (3) | Presidents’ Day |
| (4) | Memorial Day |
| (5) | Independence Day |
| (6) | Labor Day |
| (7) | Columbus Day |
| (8) | Veterans Day |
| (9) | Thanksgiving Day |
| (10) | Christmas Day |
5.4. Government Downtime for Various Authorities Including the President, Secretary of Defense, Secretary of the Air Force, AFOTEC/CC, or Base Commander of any Government Installation where work is performed.
5.4.1. Base Closures Due to Emergencies. From time to time, the AFOTEC or Base Commander, of any Government installation where work is performed, may decide to close all or part of the base in response to an unforeseen emergency or similar occurrence. Sample emergencies include, but are not limited to, adverse weather such as snow or flood, an act of God such as a tornado or earthquake, acts of war or terrorism, computer failures or a base disaster such as a natural gas leak or fire. Contractor personnel are "non-essential personnel" for purposes of any instructions regarding the emergency.
5.4.1.1. Contractor shall be officially dismissed upon notification of a base closure in accordance with paragraph 5.3.2. Contractor shall promptly secure all government furnished property appropriately and evacuate in an expedient but safe manner.
5.4.1.2. With regard to work under the contract, the government shall retain the following options:
5.4.1.2.1. Government may grant a time extension in the contract, delayed by the closure equal to the time of the closure, subject to the availability of funds
5.4.1.2.2. Government may forego the work. The contractor will not be paid for work not performed.
5.4.1.2.3. Government may reschedule the work on any day satisfactory to both parties.
5.4.1.2.4. The government may, in its discretion, permit the contractor to perform at an off-site location during the period of base closure if meaningful work can be accomplished. Contractor shall certify to the government by letter within 5 businesses days of returning to work the nature and scope of the work completed off-site. Contractor shall be permitted to bill the government at the labor rates identified in the contract.
5.4.1.2.5. In rare instances, Government may request that the Contractor continue on-site performance during the base closure period. Such a request shall be subject to agreement by Contractor.
5.4.2. Base Closure Notification Procedures.
5.4.2.1.1. After an official decision to close the base has been made by the AFOTEC or Base Commander, of any Government installation where work is performed, local television and radio stations will be notified of the closure.
5.4.2.1.2. The Contractor is directed to listen or watch one of the local radio or television stations for notification of a base closure. Contractor should follow instructions intended for non-essential personnel.
5.4.2.1.3. The contractor will not receive any other form of notification of a base closure from the government. The Contractor is responsible for notification of his or her employees.
5.4.2.1.4. If the decision to close all or part of the base is made during the duty day, and the AFOTEC or Base Commanders of any Government installation where work is performed, decision is transmitted through official notification channels, the Contractor shall follow the instructions as given. Contractor personnel shall notify their COR and act in accordance with the Contracting Officer’s Representative’s (COR) instruction.
5.4.3. Base Closure Due to Non-Emergencies. The AFOTEC or Base Commander, of any Government installation where work is performed, may elect to close all or part of Kirtland Air Force base or any other Government installation where work is performed, for non-emergency reasons such as time-off award, base open house, etc. In the event of a non-emergency base closure, the COR and the Contractor shall jointly choose a course of action within the following options:
5.4.3.1. Option 1: If there is a need for the service during the base closure the Contractor may continue on-site work. Contractor shall bill the Government in accordance with the contract.
5.4.3.2. Option 2: If there is a need for work during the base closure but access will not be available, the Contractor may work off-site provided meaningful work may be accomplished. Contractor shall certify to the government by letter within 5 business days or returning on-site the nature and scope of the work completed off-site. Contractor shall bill the Government at the labor rates specified in the contract.
5.4.3.3. Option 3: If there is no need for the service during the scheduled base closure, contractor shall not work on or off-site. Government may grant a time extension by the closure equal to the amount of time of the closure, subject to the availability of funds. The government will not be liable for time not worked.
5.5. Relocation Costs
5.5.1. Relocation costs are prohibited unless approved by the Contracting Officer.
5.5.2. In rare circumstances, the Government or Contractor may request a permanent change of station for a contractor employee when it is in the best interest of the Government to meet program objectives. In such a circumstance, upon negotiation with and approved by the Contracting Officer, the contractor may charge relocation costs as “travel” costs under CLIN 0003 of this contract/task order.
5.5.3. Per FAR 31.205-35(b)(2), the contractor must adhere to its established policy or practice when charging relocation costs to this contract/task order. In addition, the contractor shall comply with all requirements of FAR 31.205-35 – Relocation Costs, and shall refund or credit the relocation costs to the Government if the employee resigns, is terminated, or is reassigned in such manner that the employee no longer provides support to this contract within 12 months of the date of the move for which relocation costs are charged.
5.5.4. In no event shall relocation costs be allowable without prior written approval of the Contracting Officer.
5.6. Government Furnished Property-Base Support. The government will provide on-site work space, support equipment, software, administrative equipment, and supplies. The contractor will abide by government directives, Air Force, AFOTEC and MAJCOM and local base instructions pertaining to the proper use and protection of government furnished equipment, security, and access to and use of government facilities and property. The contractor is not required to maintain this equipment.
5.7. Travel Requirements. Contractors may be required to travel to military installations for team meetings, test events, etc. Travel to non-military locations may also be required. Prior to travel, all travel requirements must be coordinated through the COR, who will then obtain approval from AFOTEC/CC. Travel will be cost reimbursable (no fee) in accordance with the Joint Travel Regulation. A travel ceiling will be established for the basic period and each option.
5.8. Transition. It is anticipated some important work will be in progress through the phase-in and phase-out periods of this contract. Interruptions or delays to the work would impact the mission. It is essential that attention be given to minimizing the interruption. Therefore, the contract must provide for maximum cooperation between successor and incumbent while insuring that no work receives inadequate attention during phase-in/phase-out. The contractor shall plan for the transfer of work control delineating the method for processing and assigning tasks during phase-in/phase-out.
5.8.1. Phase-In. As a successor, the FTS contractor shall insure a smooth transition with the incumbent Fighter OTES contractor during the phase-in period. The contractor shall develop plans for assumption of awarded Task Orders. The contractor must provide an orderly transition of work acceptance and accomplishment so that impact to program is minimized. Phase-in period is 90 calendar days.
5.8.2. Phase-Out. The FTS incumbent shall ensure a smooth transition with the successor during phase-in period, prior to completion of contractual performance. The contractor shall aid the successor in the development of plans, procedures and methods for assumption of all on-going work. The contractor must provide an orderly transition of work acceptance and accomplishment so that full control by the successor is achieved by the end of the new phase-in period. Phase-out period is 90 calendar days.
5.9. Period of Performance: Proposed - Effort is 60 months from date of award. Basic: From Date of Award for twelve months. Option 1 : 12 month period from end date of basic period. Option 2: 12 month period from end date of Option 1. Option 3: 12 month period from end date of Option 2. Option 4: 12 month period from end date of Option 3.
5.10. Contract Data Requirements List (DD 1423s). With the exception of contractor management documents (e.g. Monthly Status Reports), and the identified CDRLs, all documents and reports generated are to be U.S. Government reports. All documents shall be marked with applicable classification markings and the following statement: Export Control Warning. WARNING- This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et. seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et. seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25. Hard copy reports and physical media shall be delivered to:
AFOTEC Det 1 Attn: Contracting Officer’s Representative 187 N. Flightline Road Edwards AFB, CA 93524
The contractor shall provide or participate in:
5.10.1. Management Plan (A001) Reference Paragraph 3.1. Management plan shall be presented in contractor format at the time of proposal submittal.
5.10.2. Funds & Manpower Expenditure (A002) and Status Reports (A003) - Reference paragraph 3.1. Manpower expenditures should be broken out by program such as F-22A Increment 3.2B IOT&E. Funds expenditure reporting may be combined across programs.
5.10.3. Conference Minutes (A004) - Reference paragraphs 3.2.1, 3.2.2, 3.2.3, 3.2.6, 3.2.7, 3.3.2, and 3.3.3. When requested by the COR, the contractor will summarize the results of meetings and conferences attended. Contractor trip report format is acceptable. Reports shall be submitted to the COR within five working days following the return of the contractor representative to his place of employment.
6.0 SECURITY REQUIREMENTS
6.1. Security
6.1.1. The contractor shall comply with all security requirements in accordance with DD Form 254, DoD Contractor Security Classification Specification.
6.1.2. The contractor will require access to classified and Special Access Program source data up to and including Top Secret Special Compartmented Information (SCI). The contractor must have a Top Secret Security Clearance current within five years and be SAP and SCI eligible. The contractor must have a current clearance in place by the first day of the task order.
6.1.2.1. The contractor shall provide the government with required information for program access requests to include justifications, letters of compelling need, and any other information to support program access packages. The contractor must ensure they are accurate and complete IAW applicable guidance.
6.1.3. The contractor submits classified visit requests via the Joint Personnel Adjudication System (JPAS) in support of tasks within the DoD. Classified visits outside of the DoD require Visit Authorization Letters in accordance with the National Industrial Security Program Operating Manual. Direct requests must be approved by AFOTEC with coordination by the COR/test manager prior to travel.
6.1.4. Report to an appropriate authority any information or circumstances of which they are aware may pose a threat to the security of DOD personnel, contractor personnel, resources and classified or unclassified defense information. Contractor employees shall be briefed by their immediate supervisor upon initial on-base assignment.
6.1.5. Any failure to adhere to security regulations will result in a security incident and will be processed according to DoDM 5200.01, Volume 3, SAF/AQ Security Pamphlet 5, AFI 16-1404, AFMAN 14-304, JAFAN 6.0, 1-301a (10), and/or DoD 5105.21-M-1.
6.2. Cybersecurity
The contractor shall:
6.2.1. Comply with DoD 5400.7-R, Chapter 4, DoD Freedom of Information Act Program, and AFI 33 332, Privacy Act Program requirements. These regulations set policies and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding official material.
6.2.2. Report to an appropriate authority any information or circumstances, of which they are aware, that may pose a threat to the security of DoD personnel, contractor personnel, resources, and/or classified or unclassified defense information. Contractor employees shall be briefed by their immediate supervisor upon their initial on-base assignment.
6.2.3. The contractor is prohibited from attaching any computer hardware to the Air Force network, or running any computer software unless it has been certified and accredited according to current USAF Instructions. Any such requests for reconfiguration, upgrade, or addition of computer hardware or software must be approved by the Cybersecurity Office via the contractor's submission of a written request to the COR. Contractor use of computer modems, thumb drives, and external hard drives on any machine attached to the Air Force network is prohibited. Use of commercial internet service providers is prohibited.
6.2.4. Contractor personnel using computer assets shall comply with all computer security requirements. In addition, should contractor personnel require access to computer networks or databases, they shall inform the COR or Alternate COR, who will arrange for the contractor personnel to complete the required documentation for a new computer account. The contractor shall notify the COR or Alternate COR within one workday of any contractor personnel who no longer require an open account and shall take action to close the computer account with the appropriate office within that same workday.
6.2.5. All contractor personnel who will be using IT systems belonging to the federal Government to generate, process, store, transfer, or communicate information shall attend mandatory systems security training. The format for the training will be completion of the DoD IAA Cyber Awareness Challenge Course. The training must be completed prior to application for an account on the AF Network. The contractor shall inform the COR when the training has been completed. The notice shall include the contract number and any applicable task order number, names of contractor personnel who attended and dates of training.
6.2.6. The contractor shall immediately notify the COR of any Government IT system problems or issues which come to their attention which may impact the contractor's or the Government's ability to access the systems.
6.2.7. No foreign nationals are authorized to work on this effort.
6.2.8. All contractor personnel who require access to Government IT systems are required to obtain a National Agency Check (NAC) consistent with Public Trust Positions (Standard Form 85P or most current form). The contractor may submit a request to the COR that the government grant contractor employee(s) interim access to the C4 network while awaiting the results of a NAC. Interim access to the Government network will only be granted after the contractor employees obtain at least a local background files check, and have submitted the appropriate documentation to obtain a NAC. These requests will be processed in accordance with government information security regulations and policy, and must include Security Office and the Cybersecurity Office. These requests may be subject to disapproval. In no case will a contractor be given access to the network, including a group account, until a favorable NAC has been completed or interim access granted by the Security Office. Any interim accesses that may be granted may be rescinded at any time by the PCO, COR, Directorate Security Office or Cybersecurity Office. The requirements for a full NAC shall not be authorized to work under this effort.
7.0 SAFETY REQUIREMENTS
7.1. Safety Considerations. The contractor shall plan for and implement safety procedures and protective equipment to reduce/negate injury to personnel engaged in activities supporting this contract. Safety areas of concern include but not limited to ground, flight, occupational, and environmental safety. Contractor will comply with all applicable OSHA, Federal, State and Local regulations.
7.2. Program Safety Considerations. The contractor shall support field events. Contractor employees shall be trained and certified IAW applicable OSHA standards as required. The contractor shall maintain current training records and/or certificates of completion and provide them to the Government upon request.
8.0 ORGANIZATIONAL CONFLICT OF INTEREST
In accepting and performing the work required by this task order, and all amendments thereto, the contractor certifies that the requirements of clause 5352.209-9000, Organizational Conflict of Interest (OCI) have been or will be adhered to. The contractor must immediately bring any OCI issues to the attention of the Procuring Contract Officer and the Contracting Officers Representative for a determination of whether a mitigation plan is required.
9.0 CONTRACTOR FULL-TIME EQUIVALENT REPORTING
CONTRACTOR Full-Time Equivalent Reporting: The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for AFOTEC via a secure data collection site. Data will be collected and reported at both the task order and specific program level. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil. Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year. Contractors may direct questions to the CMRA help desk.
*Reporting Period: Contractors are required to input data by 31 October of each year.
Uses and Safeguarding of Information: Information from the secure website is considered to be proprietary in nature when the contract number and the contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.
User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link. However, user manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.
Attachment 1:
Applicable to All
| 1. |
| Title 18, U.S. Code |
| Crimes and Criminal Procedures |
| 2. |
| Title 50, U.S. Code |
| War and National Defense |
| 3. |
| EO 12829 |
| National Industrial Security Program - |
Note: Source: The provisions of Executive Order 12829 (PDF format), as amended by Executive Order 12885, Vol. 58, No. 240, December 16, 1993
| 4. |
| EO 12968 |
| Access to Classified Information - |
NOTE: Amended by: EO 13467, June 30, 2008 See: Final rule of March 26, 1997 (62 FR 17683); Final rule of July 1, 1997 (62 FR 36984); EO 13284, January 23, 2003; EO 13311, July 29, 2003; EO 13462, February 29, 2008; EO 13516, October 28, 2009; EO 13539, April 21, 2010; EO 13549, August 18, 2010
| 5. |
| EO 13526 |
| Classified National Security Information, 29 Dec 09 |
| 6. |
| EO 13526 |
| Presidential Implementation Memo, 29 Dec 09 |
| 7. |
| EO 13556 |
| Controlled Unclassified Information, 4 Nov 10 |
| 8. |
| DoD 5200.1.PH-1 |
| Classified Information Nondisclosure Agreement (SF 312) and Verbal Attestation Briefing Pamphlet |
| 9. |
| DoDD 5200.2-R |
| PERSONNEL SECURITY PROGRAM |
| 10. |
| DODD 5210.50 |
| Unauthorized Disclosure of Classified Information to the Public |
| 11. |
| DODD 5210.83 |
| Department of Defense Unclassified Controlled Nuclear Information (DoD UCNI) |
| 12. |
| DoDM 5200.01 |
VOL. 1
DOD INFORMATION SECURITY PROGRAM: OVERVIEW, CLASSIFICATION, AND DECLASSIFICATION
| 13. |
| DoDM 5200.01 |
VOL. 2
DOD INFORMATION SECURITY PROGRAM: MARKING OF CLASSIFIED INFORMATION
| 14. |
| DoDM 5200.01 |
VOL. 3
DOD INFORMATION SECURITY PROGRAM: PROTECTION OF CLASSIFIED INFORMATION
| 15. |
| DoDM 5200.01 |
VOL. 4
DOD INFORMATION SECURITY PROGRAM: CONTROLLED UNCLASSIFIED INFORMATION (CUI)
| 16. |
| NSA/CSS EPL 04-02-J Annex A |
| NSA/CSS Evaluated Products List for Optical Media Destruction Devices |
SCI Documents
| 17. |
| EO 12333 |
| United States Intelligence Activities |
| 18. |
| ICD 101 |
| Intelligence Community Policy Systems, |
16 Jan 2009
| 19. |
| ICD 503 |
| Intelligence Community Information Technology Systems Security: Risk Management, Certification and Accreditation, |
15 Sep 2008
| 20. |
| ICD 700 |
| Protection of National Intelligence |
21 Sep 2007
| 21. |
| ICD 702 |
| Technical Surveillance Countermeasures, |
18 Feb 2008
| 22. |
| ICD 703 |
| Protection of SCI and Sources & Methods |
| 23. |
| ICD 704 |
| Personnel Security Standards and Procedures Governing Eligibility for Access to Sensitive Compartmented Information and Other Controlled Access Program Information, |
1 Oct 2008
| 24. |
| ICD 704.1 |
| Personnel Security Investigative Standards and Procedures Governing Eligibility for Access to Sensitive Compartmented Information and Other Controlled Access Program Information |
2 October 2008
| 25. |
| ICPG 704.2 |
| Personnel Security Investigative Standards and Procedures Governing Eligibility for Access to Sensitive Compartmented Information and Other Controlled Access Program Information |
2 October 2008
| 26. |
| ICPG 704.3 |
| Denial or Revocation of Access to Sensitive Compartmented Information, Other Controlled Access Program Information, and Appeals Process |
2 October 2008
| 27. |
| ICPG 704.4 |
| Reciprocity of Personnel Security Clearance and Access Determinations |
2 Oct 2008
| 28. |
| ICPG 704.5 |
| Intelligence Community Personnel Security Database Scattered Castles |
2 Oct 2008
| 29. |
| ICD 705 |
| Sensitive Compartmented Information Facilities |
26 May 2010
| 30. |
| ICD 705-1 |
| Physical and Technical Security Standards for Sensitive Compartmented Information Facilities, |
17 Sep 2010
| 31. |
| ICS 705-2 |
| Standards for the Accreditation and Reciprocal Use of Sensitive Compartmented Information Facilities |
17 Sep 2010
| 32. |
| IC Tech Spec- for ICD/ICS 705 |
| Technical Specifications for Construction and Management of Sensitive Compartmented Information Facilities |
5 May 2011
| 33. |
| DoD 5105.21-M-1 |
| Sensitive Compartmented Information Administrative Security Manual |
| 34. |
| DoDI 5200.01 |
| DoD Information Security Program and Protection of Sensitive Compartmented Information |
9 Oct 2008
| 35. |
| Joint DoDIIS |
| Cryptologic SCI Information Systems Security Standards |
| 36. |
| AFI 14-303 |
| Release of Intelligence to US Contractors |
01 April 1999
| 37. |
| AFMAN14-304 |
| THE SECURITY, USE AND DISSEMINATION OF SENSITIVE COMPARTMENTED INFORMATION (FOUO) |
01 May 1999
SAP Documents
| 38. |
| DoD Instruction 0-5205.11 |
| Management, Administration, and Oversight of DoD SAPs |
| 39. |
| SAF/AG Security Pamphlet 5 Security |
| Guide to Conducting Preliminary Inquiries & Formal Investigations (In Special Access Programs) |
Feb 1998
| 40. |
| JAFAN 6/0 Manual |
| Special Access Program Security Manual- Revision 1 |
29 May 2008
| 41. |
| JAFAN 6/3 |
| Protecting SAP Information within Information Systems |
15 Oct 2004
| 42. |
| JAFAN 6/4 |
| SAP Tier Review Process |
9 May 2006
| 43. |
| JAFAN 6/9 |
| Physical Security Standards for SAP Facilities Annexes |
23 Mar 2004
| 44. |
| AFI 16-701 |
| Special Access Programs |
1 Nov 1995
| 45. |
| AFOTECI 16-701 |
| Special Access Programs |
| 46. |
| AFOTEC Sup to 16-701 |
| Marking Guide for Air Force Special Access Programs |
47.
AFOTEC, Detachment, Operating Locations Standard Operating Procedures
48.
AFOTEC, Detachment, Operating Locations Master System Security Plans and Annexes
Collateral Documents
| 49. |
| DoD 5200.08-R, IC1 May 2009 |
see also
DTM-09-012
DTM-08-004
PHYSICAL SECURITY PROGRAM
| 50. |
| DoD 5230.30-M |
| DOD MANDATORY DECLASSIFICATION REVIEW (MDR) PROGRAM |
| 51. |
| DoD 5220.22-M |
SUPPLEMENT 1
NATIONAL INDUSTRIAL SECURITY PROGRAM OPERATING MANUAL SUPPLEMENT
| 52. |
| AFI 10-245 |
| Antiterrorism |
21 Sep 2012
| 53. |
| AFI 31-101 |
| Integrated Defense (FOUO) |
| 54. |
| AFI 31-101,Vol 1 |
| The Air Force Physical Security Program |
| 55. |
| KAFBI 31-101 |
| Physical Security |
| 56. |
| AFPD 31-1 |
| Integrated Defense |
| 57. |
| AFI 31-401, |
| Information Security Program Management |
| 58. |
| AFI31-401 AFGM1 |
| Air Force Guidance Memorandum to AFI 31-401, Information Security Program Management |
| 59. |
| AFOTEC Sup to 31-401 |
| Managing the AFOTEC Information Security Program Management |
| 60. |
| AFI 31-501 |
| Personnel Security Program Management |
| 61. |
| AFPD 31-601 |
| Industrial Security |
| 62. |
| AFOTEC Sup to 10-245 |
| Protection of AFOTEC Personnel and Facilities |
| 63. |
| Air Force |
| Declassification Guide for Historical Records |
| 64. |
| CAPCO |
| Controlled Access Program Coordination Office Marking Guide |
| 65. |
| AFSSI 5020 |
| Communication and Information Remanance Security |
ISOO
| 66. |
| ISOO |
| Marking Classified National Security Information |
| 67. |
| ISOO |
| ISOO Directive 1, 28 Jun 10 |
| 68. |
| 32 CFR Parts 2001 and 2003 |
| ISOO, Classified National Security Information; Final Rule |
Information Assurance Documents
| 69. |
| DoD 5400.7-R |
| DOD FREEDOM OF INFORMATION ACT PROGRAM |
| 70. |
| DoD 8570.01-M, IC3 |
| Information Assurance Workforce Improvement Program |
| 71. |
| DODI 4525.8 |
| DOD Official Mail Management |
| 72. |
| DODM 4525.8 |
| DOD Official Mail Manual |
| 73. |
| AFI 33-201 V2 |
| COMMUNICATIONS SECURITY (COMSEC) USER REQUIREMENTS |
| 74. |
| AFI 33-201 V3 |
| No longer available |
| 75. |
| AFI 33-201 V4 |
| CRYPTOGRAPHIC ACCESS PROGRAM |
| 76. |
| AFI 33-201 V5 |
| CRYPTOGRAPHIC ACCESS PROGRAM |
| 77. |
| AFI 33-201 V9 |
| OPERATIONAL INSTRUCTIONS FOR SECURE VOICE DEVICES |
| 78. |
| AFI 33-203 |
| Emission Security |
| 79. |
| AFI 33-212 |
| Reporting COMSEC Deviations |
| 80. |
| AFI 33-215 |
| CONTROLLING AUTHORITIES FOR COMSEC KEYING MATERIAL (KEYMAT) |
| 81. |
| AFI 33-219 |
| Telecommunications Monitoring and Assessment Program (TMAP) |
| 82. |
| AFI 33-230 |
| INFORMATION ASSURANCE ASSESSMENT AND ASSISTANCE PROGRAM |
| 83. |
| AFMAN 37-123 |
| Management of Records |
| 84. |
| AFPD 33-1 |
| Information Resources Management |
| 85. |
| AFPD 33-2 |
| Information Assurance Program |
| 86. |
| AFOTECI 99-103 |
| AFOTEC OT&E Guide |
| 87. |
| AFSPC SGN Instruction 33-101 |
| Secure Global Network |
| 88. |
| AFSPC SGN Instruction 33-102 |
| Certificate Management |
| 89. |
| AFSPC SGN Instruction 33-103 |
| Secure Global Network Matrices, Incident Reporting |
| 90. |
| AFSSI 4100 |
| Communications Security Program |
| 91. |
| AFSPC SGN Instruction 33-104 |
| Information Condition (INFOCON) Compliance |
92.
NRO Network Communications Security Manual 95.1
OPSEC Documents
| 93. |
| CJCSI 3213.01D |
| Joint Operations Security |
| 94. |
| NSDD No. 298 |
| National Operations Security Program |
| 95. |
| DODD 5205.02E |
| DoD Operations Security (OPSEC) Program, Mar 06 |
| 96. |
| DoDM 5205.2-M |
| DoD Directive Operations Security Program Manual, Nov 08 |
| 97. |
| JOINT PUBLICATION 3-13.1 |
| Electronic Warfare, Jan 07 |
| 98. |
| DODI 5200.39 |
| Critical Program Information (CPI) Protection within the Department of Defense, Jul 08 |
| 99. |
| AFI 10-701 |
| Operations Security (OPSEC), Jun 11 |
| 100. |
| Kirtland Sup to AFI10-701 |
| Operations Security (OPSEC) |
| 101. |
| AFI 10-704 |
| Military Deception, Aug 05 |
| 102. |
| AFPD 10-7 |
| Information Operations, Change 1, Sept 09 |
| 103. |
| AFOTEC |
| OPSEC Plan, 1 Oct 12 |
NATO Documents
| 104. |
| DODD 5100.55 |
| United States Security Authority for North Atlantic Treaty Organization Affairs (USSAN) |
| 105. |
| USSAN 1-70 |
| Implementation of the North Atlantic Treaty Organization Industrial Security Procedures |
| 106. |
| AFI 31-406 |
| Applying North Atlantic Treaty Organization (NATO) Protection Standards |
CNWDI- RD/FRD
| 107. |
| DODI 5210.02 |
| Access to and Dissemination of Restricted Data and Formerly Restricted Data |
NC2-ESI
| 108. |
| AFI 13-502 |
| Safeguarding Nuclear Command and Control Extremely Sensitive |
File details come from the government source that posted it. Updated .