Att1-SOFRAPTORIVBase-PWS-Draft.pdf

W900KK-19-R-0078 – Attachment 1

Performance Work Statement for Special Operations Forces Requirements Analysis, Prototyping, Training, Operations, and Rehearsal

(SOF RAPTOR) IV

16 July 2018

PREPARED BY:

U.S. ARMY PROGRAM EXECUTIVE OFFICE FOR SIMULATION

TRAINING AND INSTRUMENTATION (PEO STRI), PRODUCT

MANAGER, SPECIAL OPERATIONS FORCES TRAINING SYSTEMS

(PdM STS)

12211 SCIENCE DRIVE, ORLANDO, FL, 32826

TABLE OF CONTENTS

1 SCOPE

1.1 BACKGROUND

2 APPLICABLE DOCUMENTS

2.1 GOVERNMENT DOCUMENTS

3 REQUIREMENTS

3.1 DESCRIPTION

3.2 SOF RAPTOR IV CORE COMPETENCIES

4 OVERARCHING REQUIREMENTS

4.1 PROGRAM MANAGEMENT

4.2 SYSTEM DESIGN

4.3 SYSTEMS MANAGEMENT SUPPORT

4.4 CONSUMABLES AND EXPENDABLES

4.5 CONFIGURATION MANAGEMENT

4.6 QUALITY ASSURANCE AND CONTROL AND DATA MANAGEMENT

4.7 FACILITY INTERFACE SUPPORT

4.8 REVIEWS AND MEETINGS

4.9 POST AWARD CONFERENCE

4.10 GOVERNMENT PURPOSE RIGHTS

4.11 SYSTEM SAFETY TASKS

4.12 SYSTEM TEST AND EVALUATION

5 SECURITY

5.1 ANTITERRORISM (AT)/OPERATIONS SECURITY (OPSEC)

5.2 OPSEC PROGRAM

5.3 CYBERSECURITY/INFORMATION TECHNOLOGY (IT) TRAINING

5.4 CYBERSECURITY/IT CERTIFICATION

5.5 HANDLING OR ACCESS TO CLASSIFIED INFORMATION

5.6 THREAT AWARENESS REPORTING PROGRAM (TARP)

5.7 TECHNOLOGY CONTROL

5.8 FACILITY CLEARANCE AND INDIVIDUAL CLEARANCES AT THE APPROPRIATE LEVEL

5.9 PRE-SCREEN APPLICANTS USING E-VERIFY PROGRAM

5.10 INFORMATION ASSURANCE

5.11 RISK MANAGEMENT FRAMEWORK (RMF)

6 CONTRACTING MANPOWER REPORTING APPLICATION (CMRA)

Performance Work Statement (PWS) For

Special Operations Forces Requirements Analysis, Prototyping, Training, Operations and Rehearsal (SOF RAPTOR IV)

1 SCOPE

This Performance Work Statement (PWS) defines the requirements for the management, design, development, testing, integrating, installing, documenting, and delivering of future Task Orders in support of the Special Operations Forces Requirements Analysis, Prototyping, Training, Operations and Rehearsal IV (SOF RAPTOR IV). The SOF RAPTOR IV contract will provide training support to USSOCOM forces and Other SOF-like Government Agencies units in support of training for Counter Terrorism (CT), Counter Narco-Terrorism (CNT), Counter Proliferation (CP) and Unconventional Warfare (UW) missions. This acquisition is a new effort that will continue training support currently provided by the SOF RAPTOR III contract. Special Operation Forces (SOF) training is unique and requires rapid Realistic Military Training (RMT) solutions that challenge and develop our nation’s most elite SOF warfighters.

This requires a flexible contract vehicle capable of executing complex Full Mission Profile (FMP) exercises and rapid technology insertions.

1.1 Background

The United States Special Operations Command (USSOCOM) and its component commands: United States Army Special Operations Command (USASOC), Air Force Special Operations Command (AFSOC), Naval Special Warfare Command (NAVSPECWARCOM), Joint Special Operations Command (JSOC), and Marine Special Operations Command (MARSOC) have a requirement to conduct training, mission planning, preview, and rehearsal using a mix of live, virtual and constructive simulation applications. These are often at various stages of distributed simulation capabilities and configurations. The Product Manager for Special Operations Forces Training Systems (PM STS), under the SOF RAPTOR, SOF RAPTOR II, and SOF RAPTOR III contracts, has executed these projects in support USSOCOM and SOF Component Command requirements.

2 APPLICABLE DOCUMENTS

The following documents listed form a part of this PWS to the extent specified herein.

In the event of a conflict between documents referenced herein and the contents of this PWS, the contents of this PWS take precedence. Nothing in this PWS, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained.

2.1 Government Documents

a. Department of Defense (DoD) Security Instructions, Directives, and Manuals.

b. AR 25-1, Army Knowledge Management and Information Technology, 25 June 2013.

c. AR 25-2, Information Assurance, 24 October 2007.

d. Documented process for Software Development: DI IPSC 81436A, DI IPSC

81441A, DI IPSC 81442A.

e. AR 381-12, Threat Awareness and Reporting Program.

f. Army Directive 2014-05, Policy of Implementation Procedures for Common Access Card Credentialing and Installation Access for Uncleared Contractors.

g. AR 530-1, Operations Security (OPSEC).

h. DODD 8570.01, Information Assurance Training, Certification, and Workforce Management.

i. Defense Federal Acquisition Regulation Supplement (DFARS).

j. FAR 52.204-2, Security Requirements.

k. DOD 5220 22-M, Industrial Security Regulation.

l. DOD 5200.1M, Acquisition Systems Protection Program.

m. International Traffic in Arms Regulations (ITAR) / Export Administration Regulation (EAR).

n. DOD Directive 2040.2, International Transfers of Technology, Articles, and Services.

o. DOD 5230.24, Distribution Statement for Use on Technical Documents.

p. DOD Instruction 1322.28 Realistic Military Training (RMT), dated13 May 2014.

3 REQUIREMENTS

3.1 Description

SOF RAPTOR IV is a flexible and responsive contract vehicle designed to deliver services and capability to United States Special Operations Command (USSOCOM) forces and SOF-like Other Government Agency (OGA) organizations with Counter Terrorism (CT), Counter Narco Terrorism (CNT), Counter Proliferation and Unconventional Warfare (UW) missions. Special Operations Forces (SOF) requirements are typically unique, challenging, and time sensitive requiring highly skilled and experienced individuals to perform the tasks. Task Orders (TO) under this contract regularly include advanced (tier 1/tier 2) SOF support. Contractors performing SOF RAPTOR IV TOs often require a staff that includes highly skilled individuals with this advanced tier 1/tier 2 SOF experience. Contractor shall support a SOF RAPTOR IV Integrated Product Team (IPT) that includes Government and subcontractors (as appropriate) to facilitate professional and timely management.

This PWS identifies general parameters and expectations for SOF RAPTOR IV, while full user requirements will be outlined within individual TOs.

3.2 SOF RAPTOR IV Core Competencies

3.2.1 Requirements Analysis

Contractor shall conduct analyses to identify and evaluate requirements, as directed, and develop implementation and integration approaches for selected efforts. The analyses may consist of, but are not limited to, Analysis of Alternatives (AoA), new technology concept exploration, market surveys, feasibility studies, specifications, and generation of white papers that address, but are not be limited to, the items below:

a. Identification of enhancements and modifications to maintain currency with operational systems.

b. Identification of deficiencies and recommended solutions.

c. Maintaining interfaces with applicable contractors and appropriate Government agencies to stay abreast of changes to the weapon systems.

d. Gathering of required data from the weapon system contractors or other sources.

e. Acquiring source design criteria and data necessary to accomplish analyses.

f. Addressing system concurrency issues.

g. Interfacing with other contractors in pursuit of additional data.

h. Performing data collection and assessment of systems.

i. Planning and execution of experiments.

j. Recommending hardware and software tools which are anticipated to improve efficiency and effectiveness of the systems.

3.2.2 Prototyping

Contractor shall provide prototyping capabilities to evaluate new designs or enhancing existing items, systems, or services. Prototyping capabilities include, but are not limited to, the following:

a. Proof-of-Principle Prototype: verifying key functional aspects of the intended design.

b. Working Prototype: represents all or nearly all of the functionality of the final product.

c. Visual Prototype: represents the size and appearance, but not the functionality, of the intended design.

d. Form Study Prototype: preliminary type of visual prototype in which the geometric features of a design are emphasized, with less concern for color, texture, or other aspects of the final appearance.

e. User Experience Prototype: represents enough of the appearance and function of the product that it can be used for user research.

f. Functional Prototype: captures both function and appearance of the intended design, though it may be created with different techniques and even different scale from final design.

g. Paper Prototype: a printed or hand-drawn representation of the user interface of a software product (commonly used for early testing of a software design).

3.2.3 Training

Contractor shall provide training services and products to support the full scope of SOF training objectives.

a. Training services include, but are not limited to, consulting, planning, teaching, coordinating, evaluation, assessment and logistics including materials, facilities, and training support. Contractor shall be capable of supporting SOF training from scripting and concept development to after action reviews encompassing all training/education tasks. Training packages include, but are not limited to, classroom instruction, curriculum and Program of Instruction (POI) development, Field Training Exercises (FTX), Full Mission Profiles (FMP), Emergency Deployment Readiness Exercises (EDRE), new equipment training, train-the-trainer, Standing Operating Procedures (SOP) development, language training, and leadership/staff training.

b. Training products include, but are not limited to, software, training aids, and SOF training material solutions. Contractor shall be capable of providing materiel support to meet all SOF training requirements. Contractor shall be capable of providing custom engineering and design support for SOF unique training devices.

3.2.4 Operation Rehearsals

3.2.4.1 Software Support

Contractor shall provide software support including, but not limited to, analysis, design, coding, integration, installation, and testing. Contractor shall provide software products that incorporate ease of operation, maintenance, updates and modifications. Software products will be managed using applicable on-site configuration processes and procedures. Software changes will be submitted to, and approved by the Government prior to incorporation into system baselines. Contractor shall ensure software is maintained with all appropriate revisions and updates. A Software Specification Review (SSR), if required, will be included at In-Process Reviews (IPRs). Contractor shall provide software support including, but are not limited to, the following:

a. Implement an integrated software environment.

b. Support the use of automated tools.

c. Implement an efficient process for software life cycle maintenance.

3.2.4.2 Engineering Support

Contractor shall provide systems engineering and technical management support including, but not be limited to, the following.

a. Technology Readiness Level (TRL) assessments.

b. Detailed technical analyses translating user capability objectives into requirements, specifications, or other documentation, as required.

c. Review, analyze, and provide recommendations on proposed technical approaches and solutions, specifications, test plans, engineering drawings, technical review packages, etc.

d. Risk assessments and mitigation plans.

e. Generating technology development strategies, and systems engineering and system architecture documentation.

f. Assistance with managing the technical baseline and supporting configuration, interface, and technical data management activities.

g. Operational performance analysis and modeling and simulation.

h. Technical reviews and analyses, such as Reliability, Availability, and Maintainability (RAM) engineering, manufacturing and production engineering, product assurance, and system integration and interoperability, and validation and verification.

i. Technological trend assessment/analysis to identify opportunities for advancement of current capabilities.

3.2.4.3 Operations and Maintenance System Support

Contractor shall provide system support to sustain, maintain, and operate SOF RAPTOR systems, as required, including but not limited to the following.

a. SOF interoperability.

b. Technology insertion and integration.

c. Hardware and software upgrades.

d. Verification and Validation (V&V) of hardware and software upgrades.

e. Operations and Maintenance (O&M) support: (Logistics, Configuration Management, Data Management, Quality Assurance, Quality Control and infrastructure enhancements).

f. Obsolescence efforts.

g. Simulator relocation.

h. Provide qualified, and as applicable, certified, instructors and subject matter experts.

i. Rapid database production and geospatial accuracy checks in support of SOF systems and exercises.

j. Transportation of items to and from an off-site facility for repair.

k. Providing tools, test equipment, calibration equipment, or other equipment needed to support maintenance of SOF equipment.

l. Performing test equipment calibration, as required, in accordance with the manufacturer’s recommendations.

m. Repair of components and other hardware elements to include commercial hardware.

n. Test repaired or replaced items to ensure conformance to the required functional and performance parameters after corrective maintenance has been performed.

4 OVERARCHING REQUIREMENTS

The Contractor shall provide assistance and support for all facets of SOF RAPTOR IV including, but not limited to, business advice to the customer, perform contracting assistance and analysis functions using a wide range of contracting, acquisition, and analysis methods and types, and to provide assistance to the Government in the acquisition of Special Operations Forces systems, equipment and services. The Contractor shall provide additional general and functional acquisition and logistics support to the Government as required/defined by the individual Task Orders to include, but not limited to.

4.1 Program Management

The Contractor shall have current and relevant levels and breadth of acquisition program management experience and expertise. The Contractor shall manage scheduling tasks to ensure services and deliveries are identified, planned, tracked, and reported as required by the individual Task Order. Scheduling shall include, but not limited to, milestones, major reviews, key events, interdependencies, testing, and deliveries as appropriate depending on the complexity of the Task Order. These tasks shall be executed if and when directed by the documentation of each individual Task Order.

Risk Management shall be an essential task in the program management of Task Orders, and discussed in an IPT environment as required. Support may include, but is not be limited to:

a. Program/project status reporting and information flow.

b. Weekly face to face Task Order update meetings.

c. Preparation for and participation in program management, execution, and technical reviews.

d. Analysis and evaluation of program/ project progress and status.

e. Development and implementation of acquisition, logistics, and test plans and acquisition strategies.

f. Development of required acquisition documentation and briefing material.

4.2 System Design

The Contractor shall perform trade off analysis and make every effort to identify Commercial-Off-The-Shelf (COTS) technologies that can be baselined and integrated into a final product/ solution. The design concept shall incorporate an open systems approach. This shall be based on an engineering strategy to choose specifications and standards adopted by industry standards bodies or de facto standards (set by the marketplace) for selected system interfaces, products, practices, and tools. Selected designs and specifications shall be based on performance, cost, industry acceptance, long term availability and supportability, and upgrade potential.

4.3 Systems Management Support

The Contractor shall provide various types of Systems Management Support necessary to support, maintain, and operate the SOF systems. These tasks shall be executed if and when directed by the PWS of each individual Task Order.

4.4 Consumables and Expendables

The Contractor is responsible for providing consumables and expendables used in the maintenance, servicing, and utilization of SOF RAPTOR IV program requirements, and used in the administrative and operational support of SOF RAPTOR IV sites, as required.

4.5 Configuration Management

The Contractor shall provide Configuration Management (CM) for existing, developed, and procured SOF RAPTOR IV assets and possibly the systems they interact with, as directed by individual Task Orders. This includes, but is not limited to, CM of existing SOF RAPTOR IV system documentation, hardware, software, technical data and reports. The CM shall be monitored and reviewed through the IPT process as required.

CM functions include development of configuration management portions of acquisition documentation, change control documentation, specifications and specification maintenance documentation; analysis of the acquisition Contractors’ configuration management program and data deliveries for accuracy, completeness and compliance with referenced requirements, and providing recommendations or solutions when inaccurate or non-compliant; organizing and maintaining complete configuration management files including configuration identification, change control and status accounting records, as well as supporting the implementation of CM plans.

4.6 Quality Assurance and Control and Data Management

The Contractor shall provide quality assurance and control, and data management functions for SOF RAPTOR IV training systems. Data Management functions include, but are not limited to, development of data management portions of acquisition documentation; tracking and reporting Contractors’ data delivery status; attendance and participation at pre- and post-award data and program reviews and providing findings and recommendations; submission of data accession lists of all internally generated documents developed in the performance of this contract, and development and maintenance of paper and automated archival systems of all covered documentation.

The Contractor shall provide their own Quality Assurance Plan (QAP) which augments the Government produced Quality Assurance Surveillance Plan (QASP) to assure quality and proper oversight throughout the SOF RAPTOR IV contract.

4.7 Facility Interface Support

The Contractor shall provide planning, analyses, and implementation in order to meet facility requirements of SOF RAPTOR IV systems; to include civil, architectural, structural, mechanical and electrical subsystems as required. The Contractor shall participate in site surveys, site preparation, trainer facility design reviews, and device installation, and shall coordinate with each affected site. If the IPT decides that changes are required, the Contractor shall include required changes in the final baseline documentation. These tasks shall be executed if and when directed by the documentation of each individual Task Order.

4.8 Reviews and Meetings

System Requirements Review (SRR)/ System Functional Review (SFR), Preliminary Design Review (PDR), Critical Design Review (CDR), Test Ready Review (TRR), and any other review and/or meeting event that might be necessary to develop/ field a product will be identified in the Task Order’s documentation. These reviews and events shall be conducted in accordance with best engineering practices and will depend on the level of complexity of the Task Order.

4.8.1 Technical Interchange Meetings (TIM)

Technical Interchange Meetings shall be conducted to resolve technical issues associated with meeting requirements in an IPT environment, if required and identified in the individual Task Order. The Contractor shall coordinate all activities, serve as the point of contact, and provide all the necessary information to support the TIM, capture all results, and distribute findings as appropriate. TIMs shall be held at either the Contractor facility or at a Government facility. The specific location dates and duration of the TIMs will depend upon the complexity of the TO and overall effectiveness of the IPT. TIMs will be chaired in accordance with the direction provided by the Government in the TO documentation. The Contractor shall be prepared to explain the reasoning, assumption, and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the tasks required by the contract. The Contractor shall have key personnel and support available to carry out the TIM, and shall make available facilities for Government-only meetings during all TIMs.

subcontractors shall attend TIMs when required to address key elements. Except where noted herein, TIMs shall be considered fulfilled when all of the following items are completed:

a. A formal meeting has been conducted and the result of the TIM is presented to the Government.

b. All topics required for discussion and presentation have been covered.

c. All action items requiring Contractor response have been resolved.

d. Meeting minutes are approved by the TIM members.

4.8.2 In-Process Reviews

IPR shall be conducted as required on individual TOs in order to provide information regarding the status and planned activities of the program. The quantity and scope of IPRs necessary will be determined at the Task Order level and dependent on the Government’s assessment of the effort. IPRs shall include, but are not limited to:

a. A presentation on the status of the overall program, including the system modification design (hardware and software), configuration management, testing, and production.

b. A review of the integrated logistics support program.

c. A presentation of Contractor-assessed risk on the individual effort.

4.9 Post Award Conference

As required per Task Order, the Contractor shall hold a Post Award Conference (PAC).

The purpose of the conference shall be to establish the framework for IPT interaction, clearly delineate understanding of all contractual requirements during the performance period of the contract, and discuss all aspects of the Task Order as part of the IPT.

4.10 Government Purpose Rights

The Contractor shall obtain sufficient rights in technical data, both software and hardware, such that the Government can maintain and modify developed systems using Government personnel or third party contractors. The rights for each Task Order will be specified within the appropriate documentation and shall have precedence.

4.11 System Safety Tasks

As required per Task Order, the Contractor shall establish and maintain an active and effective System Safety Program (SSP) that meets program objectives and ensures that each Task Order system meets the safety requirements specified in the applicable Task Order Specification. The main objectives of the SSP shall be to identify, document, analyze, and resolve (i.e. eliminate, mitigate or reduce the associated risk to a level acceptable to the Government) safety hazards to both personnel and equipment. The Contractor shall include system safety as a topic of discussion during the scheduled program reviews if directed as part of the Task Order.

4.11.1 Safety Assessment

As required per Task Order, the Contractor shall perform a safety assessment of the system(s) to be delivered. The safety assessment shall be a comprehensive evaluation of the safety risks being assumed prior to testing or operation of the modified systems.

The Contractor shall develop and document the specific hazard controls or the precautions to be followed to use the system and shall provide verification of compliance to the safety requirements of the contract. Compliance or non-compliance to the safety requirements shall be presented, along with justification or explanation for non-compliant items, during the TRR (if required on the individual Task Order).

4.12 System Test and Evaluation

As required per Task Order, the Contractor shall plan, coordinate, establish, and implement a Test and Evaluation (T&E) plan that allows the verification and validation of the requirements of the TO. The entry, exit and acceptance criteria for the different test events will depend on the complexity of the order and the Government’s assessment.

4.12.1 Test and Evaluation (T&E) Support

The Contractor shall provide test and evaluation support, as defined by the individual Task Order. Task Orders may include, but are not be limited to:

a. Test planning, to include development of draft test plans and procedures, preparation of Test & Evaluation Master Plans (TEMPs) and other T&E segments of acquisition documentation.

b. Attendance at, or conduct of testing activities to include physical testing, engineering performance analyses, evaluation of measures of effectiveness, engineering performance predictions and trade-off studies.

c. Test analysis to include evaluation of test plans, collection and analysis of test data during developmental and operational testing, drafting of test and evaluation reports.

d. Test support activities to include maintenance of test facility site designs and coordination of supporting activities and equipment to support joint interoperability and other testing, etc.

4.12.2 Verification, Validation, and Certification

The Contractor shall implement a comprehensive program for validation, verification, certification, and testing, within the development process. These tasks shall be executed if and when directed by documentation provided with each individual Task Order.

4.12.3 Test Responsibility

Unless otherwise specified in the Task Order, the Contractor shall be responsible for the performance of all test requirements. The Government reserves the right to perform tests that are deemed necessary to ensure that delivered supplies and services conform to the contracted requirements. These tasks shall be executed if and when directed by the documentation of each individual Task Order.

4.12.4 Test Authority

Test results shall be recorded by a responsible officer within the Contractor’s organization during Contractor’s inspections and certified by the Contracting Officer’s Representative (COR). Government inspection results will be recorded by the PCO’s representative. Specific requirements for Test Authority, if required, will be outlined in the individual Task Order.

4.12.5 Test & Evaluation (T&E) Program Planning

As required per Task Order, the Contractor shall develop and document the structure and objectives of the T&E program for the system modifications. The Contractor shall continuously reassess and refine the T&E program as the system modifications development, production, and testing progresses.

4.12.6 Test Resources and Facilities

The Contractor shall furnish the equipment and personnel required to ensure that all modifications meet the requirements in the applicable Task Order. The Contractor shall ensure that all Contractor personnel, test equipment, other supporting equipment, spare assemblies and parts, test and data logs, and other items necessary for testing are available for the start and during all phases of testing, as required by the individual Task Order.

4.12.7 Test Methods

Tests shall be performed IAW the Government-accepted updated system test procedures. Test, examination, demonstration, inspection, and verification procedures shall be documented in the test procedures. Test results shall be documented in the test procedures. The Contractor shall update existing documentation to reflect the incorporation of the modifications IAW Contract Data Requirements List (CDRL) DI- ADMIN-80925, as required per individual Task Order.

4.12.8 Test Criteria

As required per Task Order, the test criteria for tests and examinations shall include both quantitative and qualitative performance data of the operational system(s).

Quantitative test criteria shall be used to the maximum extent possible. Qualitative data such as video, photographs, and tape recordings, obtained from operational system or subsystem performance, may be used as test criteria whenever quantitative test criteria is not practical or is not measurable, and the requirement for simulation or stimulation realism can only be judged qualitatively. Government approval is required for any test criteria that is not based on actual operational system performance data. Where appropriate, test criteria for individual inspections, tests, demonstrations, and examinations shall consist of both quantitative and qualitative test criteria. As a complement to quantitative test results, qualitative comparisons of visual, video, and aural presentations shall be provided.

4.12.9 T&E Deficiency Reporting System

As required per Task Order, the Contractor shall establish and implement a Deficiency Reporting System for the identification, tracking, and resolution of all hardware and software problems (including tactical subsystem) discovered during the Conformance Inspections. In addition, the Deficiency Reporting System shall be used to track documentation problems including technical manual errors. Deficiencies shall be documented.

4.12.10 Deficiency Report Categories, as required by Task Order

Deficiency Reports (DR) shall be categorized as Priority I through Priority III. During the Joint Final Inspection, the Government will assign DR categories as deemed appropriate. The following are the definitions of the DR categories:

a. Priority I - Serious impact to Training and/or Mission Rehearsal.

b. Priority II - Some impact to Training and/or Mission Rehearsal.

c. Priority III - Administrative and/or documentation.

4.12.11 User Acceptance Testing (UAT)

As required by Task Order, User Acceptance Testing (UAT) will commence upon notification by the Contracting Officer’s Representative (COR). UAT will be conducted on-site (unless otherwise specified by the Government) by a joint Contractor/

Government test team and will consist of tests conducted to verify compliance with the specified performance requirements. UAT will be conducted IAW the Government-accepted test procedures, and the Contractor shall provide the Government with a copy of this revised test procedures prior to UAT.

Deficiency correction verification and validation, including additional cold-starts, will be at the discretion of the Government. The Contractor shall provide the resources, personnel, and equipment necessary to support the tests. Hardware and software configuration item testing and design documentation verification and validation will be conducted as an integral part of UAT. The Government reserves the right to perform additional tests as deemed necessary to ensure compliance with the specified requirements. Deficiencies found during UAT shall be corrected and verified by the Government test team prior to Government acceptance of the modified systems.

Specific requirements to conduct User Acceptance Testing will be outlined at the individual Task Order level.

4.12.12 UAT Entry Criteria

The entry criteria for UAT shall include, but is not limited to, the following:

a. Agreed plan for UAT has been established and test procedures have been accepted by the Government;

b. Software load builds (if required) are witnessed by the Government, complete, verified, and under Government CM control;

c. Post-ship and installation modifications have been successfully accomplished, and all systems are integrated, operational, and ready for testing;

d. Post-ship modification baseline configuration has been recorded and re-established. Contractual and industry standard configuration management processes have been followed, and Contractor generated configuration management logs are available for Government review/inspection;

e. System stability has been demonstrated as acceptable, as determined by the Government;

f. Contractor’s Test Director has certified in writing that the system is ready for

UAT.

4.12.13 UAT Exit Criteria

The exit criteria for UAT shall include, but is not limited to, the following:

a. A cold start has been successfully performed (with Government CM oversight) to establish final software baseline;

b. All deficiencies identified were documented, categorized for severity, and tracked to final resolution (DR sign-off and dismissal);

c. All Priority I, II, and III deficiencies have been corrected;

d. A complete test, using the test procedures, has been run after the final DR ready for re-test, within acceptable regression testing guidelines as determined by the Government.

e. Government mission testing has been performed successfully;

f. A copy of the final test procedure test results has been provided with all results recorded in the contractual testing documentation, including date/time of final results, and red-lines (when necessary);

g. System stability has been demonstrated as acceptable, as determined by the Government;

h. Configuration management baseline (software and hardware) has been maintained throughout DR correction. All configuration management deficiencies identified during UAT have been satisfactorily corrected;

i. UAT has demonstrated that all test and support equipment necessary to execute the complete testing was properly used, documented, and functioned properly;

j. Required QA standards have been satisfied and achieved;

k. Contractor’s Test Director and Government’s Test Director have signed off testing as complete with any conditions specified.

4.12.14 Contractor Logistics Support (CLS) Contractor Liaison

If and when directed by the documentation of the individual Task Order, the Contractor shall establish a liaison, and execute an Associate Contractor Agreement (ACA), if required, with the CLS Contractor to facilitate the following:

a. Use of available CLS personnel to achieve site activation.

b. Coordination with the CLS Contractor to support the existing unmodified portion of the systems during the modifications.

5 SECURITY

Security will be in accordance with the DD Form 254, Department of Defense Contract Security Classification Specification. The Contractor is required to be capable of obtaining and maintaining a facility clearance up to the Top Secret (TS) level and authorized Secret level for safeguarding for this effort. There is no requirement to currently have a Sensitive Compartmented Information Facility (SCIF). The intent of the TS requirement is predominantly for administrative purposes (conduct meetings, information storage) and is not intended for production capability.

5.1 ANTITERRORISM (AT)/OPERATIONS SECURITY (OPSEC)

5.1.1 AT Level I Training

All Contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training in accordance with AR 381-12 within thirty calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The Contractor shall submit certificates of completion for each affected Contractor employee and Subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within thirty calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: http://jko.jten.mil.

5.1.2 Access and general protection policy and procedures

All Contractor employees, including subcontractor employees, requiring access to an Army or USSOCOM controlled installation, facility, or area shall comply with applicable security policies and procedures (provided by the Government representative). This includes policies pertaining to the use or prohibition of electronic recorders, devices, cameras, etc. If the Contractor is required to take photographs or videos on a Government Installation, the Contractor must obtain written permission from the Senior Commander. The Contractor shall also provide all information required for background checks to meet installation and facility access requirements to be completed by the installation Provost Marshal Office, Director of Emergency Services, or Security Office.

The Contractor workforce must comply with all personal identity verification requirements as directed by DoD, HQDA, USSOCOM, USASOC and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in Contractor security matters or processes.

5.1.3 Access and General Protection Policy and Procedures for Contractor Requiring Common Access Card (CAC)

Contractor and all associated subcontractor employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition at any individual facility or installation change, the Government may require changes in Contractor security matters or processes.

Before CAC issuance, the Contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The Contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DOD facility and access, via logon, to DOD networks on-site or remotely; (2) Remote access, via logon, to a DOD network using DOD-approved remote access procedures;

or (3) Physical access to multiple DOD facilities or multiple non-DOD federally controlled facilities on behalf of the DOD on a recurring basis for a period of six months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

5.1.4 iWATCH training

The Contractor and all associated subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity AT Office). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within thirty calendar days of contract award and within thirty calendar days of new employees commencing performance with the results reported to the COR no later than sixty calendar days after contract award.

5.1.5 Army Training Certification Tracking System (ATCTS) Registration

All Contractor employees with access to a Government information system must be registered in the ATCTS at commencement of services, and must successfully complete the DOD Information Assurance Awareness prior to access to the IS, then annually thereafter.

5.2 OPSEC Program

The Contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within ninety calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC Officer, per AR 530-1, and Operations Security. This SOP/Plan will include the Government's critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it. New and existing Contractor employees must complete Level I OPSEC training annually. In addition, the Contractor shall identify an individual to be an OPSEC Coordinator. The Contractor will ensure this individual becomes OPSEC Level II certified per AR 530-1.

5.2.1 Requirement for OPSEC training

Per AR 530-1, new Contractor employees must complete Level I OPSEC training within thirty calendar days of their reporting for duty. All Contractor employees must complete annual OPSEC awareness training. The contract shall ensure all applicable employees have completed OPSEC initial training and annual refresher training and shall certify that their work force has completed the training through the submission of completion certificate(s) to the COR within thirty calendar days of arrival on the installation.

OPSEC training can be accomplished at the Defense Security Services website at:

https://securityawareness.usalearning.gov/opsec

5.3 Cybersecurity/Information Technology (IT) Training

All Contractor employees and associated subcontractor employees must complete the DOD cybersecurity awareness training before issuance of network access and annually thereafter. All Contractor employees working cybersecurity/IT functions must comply with DOD and Army training requirements in DODD 8570.01, DOD 8570.01-M “Information Assurance (IA) Workforce Improvement Program” and AR 25-2 “Information Management/Information Assurance” within six months of employment.

Cybersecurity/Information Technology (IT) training can be accomplished at:

https://ia.signal.army.mil/dodiaa/default.asp.

5.4 Cybersecurity/IT Certification

Per DOD 8570.01-M, Defense Federal Acquisition Regulation Supplement (DFARS)

252.239.7001 “Information Assurance Contractor Training and Certification” and AR 25- 2, states that the Contractor employees supporting cybersecurity/IT functions will be https://securityawareness.usalearning.gov/opsec/ appropriately certified upon contract award. The baseline certification as stipulated in DOD 8570.01-M must be completed upon contract award.

5.5 Handling or Access to Classified Information

Contractor shall comply with FAR 52.204-2 “Security Requirements”. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret”. The Contractor shall comply with (1) Security Agreement (DoD Form 441), including the National Industrial Security Program Operating Manual (DOD 5220.22-M) and (2) any revisions to DOD 5220.22-M.

5.6 Threat Awareness Reporting Program (TARP)

For all Contractors with security clearances, per AR 381-12 Threat Awareness and Reporting Program (TARP), Contractor employees must receive annual TARP training by a counterintelligence agent or other trainer as specified in section 2-4b.

5.7 Technology Control

The Contractor shall adhere to the protection standards and guidance described in DoD 5200.1-M, “the Acquisition Systems Protection Program” to prevent foreign intelligence collection and/or the unauthorized disclosure of information governed by the International Traffic in Arms Regulation (ITAR) and/or the Export Administration Regulation (EAR) during the acquisition process. Distribution of unclassified Critical Program Information (CPI) (see DoD Manual 5200.1-M) shall be made in accordance with DoD directive 2040.2, “International Transfer of Technology, Goods, Services, and Munitions”. All such documents shall be properly marked in accordance with DoD Directive 5230.24, “Distribution Statements on Technical Documents”. Technical documents not subject to distribution are defined in DoD Directive 5230.25, “Withholding of Unclassified Technical Data from Public Disclosure”.

5.8 Facility Clearance and individual clearances at the appropriate level

The Contractor must obtain a Facility Clearance at the appropriate level (IAW the National Industrial Security Program Operating Manual (NISPOM) DoD 5220.22-M) prior to the start of the contract awarded period of performance. Contractor personnel performing work under this contract must have the required security clearance at the appropriate level at the start of the period of performance. Security clearances and Facility Clearance (FCL) requirements are required to be maintained for the life of the contract in accordance with the DD254 attached to the contract.

5.9 Pre-screen applicants using E-Verify Program

The Contractor must pre-screen applicants using the E-verify Program (http://www.dhs.gov/E-Verify) website to meet the established employment eligibility requirements. The vendor must ensure that the applicant has two valid forms of Government issued identification.

SOF RAPTOR IV supports a diverse customer base of unique organizations, which gives its Government and commercial partner’s access to sensitive information, geographic locations, and organizational relationships. Although the acquisition and contractual documentation supporting these efforts are often labeled UNCLASSIFIED, professional discretion is necessary to maintain a good working relationship in a sensitive environment. Contractor personnel and subcontractors assigned to this project will require access to classified information or facilities that process classified information. All Contractor personnel working at specific locations shall be U.S. citizens and possess and maintain an active security clearance. Any submission of an individual without a clearance must be approved by the Government point of contact at the respective component command locations.

5.10 Information Assurance

Personnel performing IA functions must obtain and maintain one of the certifications required for their position and category from the DOD approved 8570-M baseline certifications.

Higher level IAT and IAM certifications satisfy lower level requirements. Certifications listed in Level II or III cells can be used to qualify for Level I. However, Level I certifications cannot be used for Level II or III unless the certification is also listed in the Level II or III cell. For example:

The A+ or Network+ certification qualify only for Technical Level I and cannot be used for Technical Level II positions.

The System Security Certified Practitioner (SSCP) certification qualifies for both Technical Level I and Technical Level II. If the individual holding this certification moved from an IAT Level I to an IAT Level II position, he or she would not have to take a new certification. Higher level CSSP and IASAE certifications do not satisfy lower level requirements.

5.11 Risk Management Framework (RMF)

RMF is the guide for applying the Risk Management Framework to Federal Information Systems.

The Risk Management Framework provides a process that integrates security and risk management activities into the system development life cycle. The risk-based approach to security control selection and specification considers effectiveness, efficiency, and constraints due to applicable laws, directives, Executive Orders, policies, standards, or regulations. The following activities related to managing organizational risk are paramount to an effective information security program and can be applied to both new and legacy systems within the context of the system development life cycle and the Federal Enterprise Architecture.

6 CONTRACTING MANPOWER REPORTING APPLICATION (CMRA)

The Contractor shall provide management functions that meet the requirements of this Task Order. The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services under this contract via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/. Reporting inputs will be for labor executed during the period of performance during each Government Fiscal

Year (FY) which runs from October 1 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 can find User Guides, Frequently Asked Questions and may direct questions to the help desk at http://www.ecmra.mil/.

http://www.ecmra.mil/