RISE_Basic_SOW_v3.pdf

For Official Use Only

Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 1 of 14

Integrated Experiments and Evaluation Division (AFRL/RVE)

R&D Integrated Space Experiments (RISE) Contract

Basic Contract Statement of Work

13 July 2017

1. Mission and Background The RISE contract will support the Air Force’s Space Superiority Service Core mission requirements and Space Enterprise Vision growth areas by providing concept design, development, integration, test and evaluation of new space technologies, innovative, engineering prototypes, and new employment concepts. The Air Force Research Laboratory's Space Vehicles Directorate, Integrated Experiments and Evaluation Division (AFRL/RVE, henceforth ‘RVE’), working with the other technical divisions within the directorate, conducts innovative research and development of ground, high-altitude balloon, near-space, and spaceflight experiments from the mission analyses, systems engineering, integration and testing of components and subsystems through system-level integration and test, and to the execution of experiment mission operations.

2. Scope The objective of this contract is to provide the required research, engineering, and technical management for performing space technology analysis, development, integration, experimentation, demonstration, and evaluation in support of the AFRL/RV mission. When stated within task order (TO) specifications, the contractor shall be capable of performing quick reaction research, analysis, and specification development for engineering prototypes. This includes cradle-to-grave processes and functions, as defined in the Definition paragraph below. When provided Government-procured engineering prototype hardware/software, the contractor shall be capable of short timeline assembly, integration and test to space qualify the engineering prototype vehicle. Components and subsystems requiring integration and test includes, but is not limited to: power, thrusters, structures, mechanisms, sensors, optics, electronics, guidance, navigation, and controls, data processing, communication, ground support equipment, and associated software/firmware.

The Government seeks engineering and technical effort in the following RISE activities:

Engineering, including systems, software, and test engineering Integrated ground experiment design, fabrication, and assembly Flight hardware design, fabrication, and assembly Flight software/firmware development and test Flight payload and experiment platform integration and test Ground system hardware/software development, integration, test, and deployment Assembly, Integration, and Test (AI&T) laboratory research, engineering, design, scheduling, test preparation, operation, personnel training, safety, and maintenance Analytical modeling and analyses and evaluation for all phases of experiment, development and execution from concept design through mission operations, transition and/or closeout (e.g., physics models for emerging/innovative science/technology development and physics/engineering models to verify system design and testing)

Spacecraft launch integration, commissioning, and on-orbit experimentation Mission and operations planning, design and development

DRAFT

Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 2 of 14

Program management, including attendance at technical meetings, reviews, off-sites, or technical conferences stated within to specifications

The contractor shall perform work in the following functional areas: integrated ground experiments, ground support equipment, spacecraft, high-altitude balloon flights, launch vehicles (e.g., orbital and suborbital rockets, space plane, International Space Station (ISS) deployments), platform and subsystem/component design, software design and development, analyses throughout the research and development system engineering process, design optimization and review, testing and evaluation, deployment of experimental assets, and transition phases. Concurrent with these functional areas, technical work is required in the areas of information systems, information assurance and communications security (COMSEC) engineering in order to enable and execute spacecraft, ground, or high altitude balloon experiment integration, test, and mission development.

Performance shall primarily be conducted at the AFRL/RV and Phillips Research Site (PRS) laboratories at Kirtland AFB, NM. On occasion work may have to be performed at Holloman AFB, NM, remote field sites, or other research, integration and launch facilities in the U.S. and/or overseas, as specified in TOs. Specific sites will be identified in TOs and will address location support, facility access, and security requirements.

Definition:

Cradle-to-grave: The cradle-to-grave processes and functions include scientific, technical and systems engineering activities associated with integrated space experiments from the initial concept development stage through the technology transition phase. This includes, but is not limited to, developing and refining requirements, conducting concept design, engineering analyses, trades, and modeling/simulation, and supporting systems engineering reviews (from Alternative Systems Reviews and Preliminary Design Reviews through Critical Design Reviews and System Verification Reviews), with particular emphasis on systems-level integration. Processes required will include AI&T of space systems, and defining workflows, master schedules, test plans, and technical reports with key milestones that include Test Readiness Reviews, Pre-Ship Reviews, Mission Readiness Reviews and post-mission reviews. Further, the activities include: Defining, developing, and/or using the necessary test equipment, ground support equipment, configuration management, data acquisition and analysis tools, flight procedures development, problem fault reporting processes, and ground and flight software. As well as computers and networks, including cyber analysis, and information assurance procedures—all in an appropriately-secure environment.

3. Compliance and Reference Documents Compliance Documents are listed in Attachment 1 and Reference Documents are listed in Attachment 2.

Reporting and documenting requirements are described in the Contract Data Requirements List (CDRL), Attachment 3.

4. Requirements The following requirements for the R&D activities are applicable to the listed RVE functional areas and concurrent technical effort. The contractor shall be capable of expediting these functions and processes to accelerate the integration and test of space-qualified, engineering prototype hardware for rapid response space experiments as stated within TO specifications. Per TO specifications, the contractor may be required to travel to other Government agencies and/or other contractor locations to perform design, integration, and test activities in support of AFRL/RVE integration and test programs.

4.1 Systems, Software, and Test Engineering

4.1.1 Systems engineering is integral to the development and successful execution of a flight experiment. The contractor shall perform systems engineering activities/functions for all aspects of flight experiments from concept definition through final evaluation, including

Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 3 of 14 research, development, design of components, subsystems and fully integrated aerospace systems for flight and test support equipment, to include design trades, risk analyses, and system effectiveness evaluation. Per CDRLs, the contractor shall provide documentation for all systems engineering activities related to individual flight experiments, to include technical input into development of Government Reference Designs (GRD) and transition of flight assets to operational users.

4.1.2 Engineering disciplines/functions shall include:

Systems engineering Electrical engineering Mechanical engineering Software engineering Test planning and design Test instrumentation design Modeling/simulation, analyses, and evaluation Design/planning (specification) of functional and environmental test requirements Performing functional and environmental tests Data reduction, analyses, and reporting Development and fabrication of ground support equipment and software

4.1.3 The basic mechanical, electrical, information system, fabrication design and planning functions shall encompass the following as required in any ground, high-altitude balloon, near-space or space flight experiment, related systems engineering study, or related research and development:

Electronic circuit or power systems Structures and mechanisms Communications systems Data acquisition and data processing Information systems/information assurance /COMSEC engineering Subsystem and system modeling Subsystem and system integration Component-to-system testing Functional and environmental testing Laboratory design, setup, measurement, experimentation Satellite system simulation Troubleshooting at any phase of development, test, or mission operations Setup and calibration of standard and custom test and fabrication equipment Training for participants in the University NanoSats Program (UNP) in spacecraft fabrication, assembly, integration, and test

4.2 Ground and Flight Experiment Hardware Design, Fabrication and Assembly

The contractor shall analyze, design, document, fabricate or acquire, inspect, assemble, perform functional and environmental tests on and validate spacecraft/balloon parts, subassemblies, and components, and the supporting test equipment, fixtures and aerospace/ground systems. Performance requires expert knowledge in the design, fabrication, use, and/or assembly of aerospace and spaceflight-quality parts/components. The contractor shall participate in concept and design reviews and technical interchange meetings.

4.3 Ground and Flight System Software/Firmware Development and Test

Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 4 of 14

The contractor shall design, develop, implement and test software/firmware required for operation of experimental ground systems, payloads, and flight platforms as well as software/firmware to be used in test and evaluation efforts. This involves activities such as modifying existing software/firmware, architecting, writing and documenting new code, integrating and testing new or modified code, programming Field Programmable Gate Arrays (FPGAs), sensor systems and other embedded systems, maintaining software and related databases, and performing software configuration management.

4.4 Assembly, Integration and Test

4.4.1 The contractor shall provide engineering and technical support for component-to-system receipt, safe handling, assembly, integration and testing in the AFRL/RVE AI&T Laboratories or at field locations, test ranges, and other Government or contractor locations.

The contractor shall assemble and integrate the various systems/subsystems mechanically, electrically, and through software. The contractor will work with the test and integration personnel to troubleshoot and resolve any related system or subsystem incompatibilities.

4.4.2 The contractor shall perform ground/laboratory test planning and procedures development, test design and fabrication, test preparation and coordination, and arrange equipment and logistics for the test effort. The contractor shall perform systems-level tests to evaluate performance of spacecraft, balloon, and ground subsystems/systems. The contractor shall perform data reduction, analyses, and review the results of functional and environmental testing of spacecraft, balloon, and ground subsystems/systems. The experimental test results shall be documented and used to validate analytical predictions and mission performance, and to space-qualify the subsystems/systems.

4.4.3 The contractor shall understand and comply with Department of Defense (DoD), NASA, and commercial regulations and standards in the performance of spacecraft assembly, integration and testing when using the AI&T Laboratory equipment to perform space worthiness testing.

4.5 Mission Development and Execution of Ground, Balloon, or Space Experiments, Mission Operations, and Transition of Operations

4.5.1 The contractor shall perform research, mission analyses, and documentation for flight and/or ground experiments to facilitate the Government’s development of mission/system requirements, objectives, constraints, and alternatives. Mission analyses or evaluations shall be accomplished through relevant experimental testing, computer simulation, and/or engineering analyses. For such evaluations, the contractor shall provide data acquisition, processing, analysis, and modeling/simulation tools to be used in the experiment, research, or analysis effort.

4.5.2 The contractor shall provide engineering and technical support for experiment mission development and operations to include:

Mission planning Safety and security planning and procedures Environmental regulation and policy compliance Test and evaluation equipment and laboratory adequacy and applicability Risk analysis and risk management Pre-ground test equipment deployment, setup and operations Pre-launch and launch operations On-orbit, high-altitude, or ground-based experiment operations and management Hardware/software configuration management and control Test data acquisition, reduction, analysis, and verification

Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 5 of 14

Identification of Command, Control, Communications and Computer Systems (C4) systems compatibility prior to transition

Transition of ground or space assets to end users, as required by the Government

4.5.3 Pre-launch and ground operations includes packing, protecting, and shipping complete spacecraft and support equipment to the launch site and performing all pre-launch activities required to integrate the spacecraft onto a rocket, including mechanical installation, functional testing, blanketing, fueling, inspection, fairing closeout, range safety procedures, and day of launch processes. After launch, required functions involve conducting mission/experimental flight operations, anomaly resolution, telemetry archive and analysis, as well as reporting and documentation (e.g., through procedure red-lining and memograms).

4.5.4 The technology transition phase includes: documenting the knowledge gained based on the ground test and flight experiment results, conclusions, lessons learned as part of the program final report, and possibly supporting specific technical requirements to transition flight operations in the event that any residual operational capability is exploited by an external organization.

4.5.5 The contractor shall conduct research, develop and plan for future space system AI&T objectives and programs to be conducted in AFRL/RVE’s AI&T Laboratories, as required.

These shall include:

Development of innovative AI&T capability designs to provide agility and flexibility New AI&T plans that include projected cost, schedule, and technical requirements Improved test operations plans and concepts of operations Advanced test data reduction, data analysis, reporting, and distribution Updated program security guides, mission assurance plans, safety plans, facility management plans, and other documentation required in support of AI&T programs

4.5.6 The contractor shall assist the Government in the assessment of historical programs for lessons-learned to be leveraged into future space programs being integrated and tested in AFRL/RVE’s AI&T Laboratories. The contractor shall travel to other Government agencies and/or other contractor locations, as required, for the purpose of researching historical and lessons learned in support of design and test requirements reviews, briefings to industry, conferences and other meetings related to AFRL/RVE integration and test programs. The contractor shall prepare lessons-learned and document them in monthly Status Reports and briefings and brief those research results applicable to AFRL/RVE’s AI&T Laboratories and other AFRL/RV organizations related to space systems integration and testing, as needed.

4.6 Assembly, Integration and Test Laboratory Support

4.6.1 The contractor shall design, plan, schedule, prepare, upgrade and/or repair, operate, inspect and maintain the RVE AI&T Laboratories’ assembly, integration, and test equipment, instrumentation, tools, and data acquisition and reduction systems. This shall include any space technology systems/subsystems currently occupying space in the laboratory and/or under test.

4.6.2 The contractor shall define test requirements for spacecraft integration and testing per TO or external customer specifications and plan and schedule test equipment operations and flow.

In consultation with Program Managers, the contractor shall organize, coordinate, and manage a test schedule for all tests utilizing the AFRL/RVE AI&T Laboratories, to include de-conflicting and accommodating multiple flight programs’ test schedules in accordance with RVE set mission priorities. The contractor shall document all processes and report them to the Program Manager.

Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 6 of 14

4.6.3 The contractor shall operate and maintain all AI&T Laboratory equipment, clean rooms, and work sites in accordance with applicable manufacturer’s specifications, Air Force compliance documents in Attachment 1, or as stated within TO specifications. The contractor shall perform hardware/software configuration management and documentation control for the equipment, instrumentation, tools, and any space technology systems/subsystems currently under test.

4.6.4 The contractor shall provide personnel training and laboratory safety instruction to cover such issues as vehicle operations, crane operations, hazardous materials, waste management, explosives, laser radiation, welding, cutting, brazing, chemicals, and electrostatic discharge.

4.6.5 In support of operating or maintaining the AI&T Laboratories, the contractor shall be able to procure material, services, or non-real property construction after approval by the Program Manager, in coordination with the Contracting Officer, and following the internal RVE Purchasing Requirements Flow. Justifications for such purchases usually include those: a) as specified by or derived from TO experiment testing requirements, b) as a consequence of breakage, damage, or malfunction of existing instrumentation/equipment, c) as a result of finding instrumentation/equipment inoperable during a maintenance inspection and d) consumables as required by periodic maintenance.

4.6.6 Base laboratory support shall be provided by the Government to the contractor. The contractor will use base support on a rent-free, non-interference basis to include Government-controlled working space, material, equipment, services, or other support which the Government determines can be made available at, or through, any Air Force installation where this contract shall be performed. Specific base support AI&T laboratories and equipment to be furnished are listed in Attachments 4A-D. However, the specific building number and associated base support equipment listed are subject to revision upon notification by the Government. The contractor will immediately report inadequacies, defective base support, or non-availability of support stipulated by the contract schedule, together with a recommended plan for obtaining the required support. The contractor is not authorized to incur any costs resulting from nonsupport prior to CO direction.

5. Program Management

5.1 General

The contractor shall implement contract administrative, financial and task planning and management functions to ensure the on-time, on-budget accomplishment of all authorized TOs and work effort described in Section 4.0. This shall include planning, organizing, staffing, directing and controlling cost, schedule, and performance at the prime and subcontract level to insure compliance with the requirements of multiple, concurrent task orders. The contractor shall have the ability to respond to and manage quick reaction task orders (e.g., 15 day response turnaround), technical work surge requirements, risk assessment and management, and knowledge capture and documentation, as required by the Government.

5.2 Management of Personnel

5.2.1 General: The contractor shall provide for all management and support of contractor personnel. The contractor shall accomplish tasks by providing qualified personnel possessing the appropriate combinations of education, training, security clearance and experience/skills.

All Personnel directly performing the tasks in Task Order Requirements Section are designated as either Critical Personnel or Key Personnel. All others will be considered

Administrative or Corporate Reach back. The contractor shall maintain a stable workforce while minimizing the impact of any turnover and/or disruptions to the Government and/or

Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 7 of 14 mission. The contractor shall ensure continuation of support during personnel absences due to sickness, leave, and voluntary or involuntary termination from employment such that there is no negative impact to the Government mission. Upon notification of a pending vacancy, the contractor shall provide written documentation to the PCO and Government Technical Lead within one (1) business day to ensure task mission remains on schedule toward completion.

5.2.2 Key Personnel: The personnel listed below are considered essential to the work being performed on contract. Prior to proposing, substituting, removing, replacing, or diverting any of the specified individuals, the Contractor shall notify the Contracting Officer 5 working days in advance and shall submit a written request and justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on this Contract. Any proposed substitution of key personnel must meet or exceed the education, experience, and other technical requirements of the personnel being replaced. No change in key personnel shall be made by the Contractor without the prior written consent of the Contracting Officer and The RVE Director. The Contracting Officer will notify the Contractor within 5 working days after receipt of all required information of the decision on the substitution(s). In the event the proposed substitution of key personnel does not meet or exceed the education, experience, and other technical requirements of the personnel being replaced, the Government reserves the right to require continued performance of previously approved key personnel or to require substitution of acceptable replacements for the individuals specified below.

The key personnel listed below may, with the consent of the contracting parties, be amended from time to time during the course of the Contract to either add or delete personnel as appropriate. In the case of a no-notice departure, the contractor shall immediately inform the PCO and Government Technical Lead. This written notification shall include the date and time the position shall be vacant, anticipated replacement date, and management correction action, if needed, to ensure task mission remains on schedule toward completion.

Key Personnel position include: Contract Program Manager, Chief Engineer and Lead Software Engineer.

5.2.3 Removal of Contract Personnel: The contractor shall temporarily or permanently remove personnel from this task order at PCO’s request for the following: 1) Poor performance; 2) Fraudulent qualifications or credentials; 3) Unprofessional conduct; 4) Revocation or suspension of security clearance; and 5) Issues affecting security, health, safety or welfare.

5.2.4 Transition Planning: The contractor will be given a transition period of up to 30 calendar days to provide qualified personnel that meet or exceed the stated qualification requirements per Section 4. The Transition Period will begin from the Basic Contract Order award date.

During the Transition Period the contractor Critical Personnel and Key Personnel shall process and obtain required ID/CAC cards, computer system access requests, and receive workplace and task orientation to ensure the entire team is in-place for period of performance start, in order to fulfill this TO. The contractor shall follow the transition plan submitted as part of the proposal and inform the PCO, Task Order Technical Manager and Government Technical Lead of progress throughout the transition period.

5.2.5 Transition Out Planning and Future Contracts: The Contractor shall participate in organizational, system, process and information knowledge transfer from the Government team (Government, FFRDC, A&AS members), to include 30 days of overlap with existing Contractors, as applicable. The Contractor shall facilitate organizational, system and process

Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 8 of 14 knowledge and information transfer from the Contractor to any new Contractors or Government entities performing portions of this contract during the close out of this contract.

A Transition Out plan must be provided as part of the Task Order Management Plan (TOMP) to the CO, Government Technical Lead and Task Order Technical Manager to track progress to provide adequate transition training to the follow-on contractor. (CDRL AXXX)

5.2.6 Training: The contractor shall be responsible for the employment, training, guidance and supervision of contractor personnel assigned to perform tasks under awarded Task Orders.

However, if Government-unique training is identified to perform their duties, then written approval must be obtained from PCO prior to attending the training. These personnel shall be knowledgeable of and be able to independently apply the guidance found in the compliance and reference documents identified in Attachments 1 and 2.

5.2.7 Identification: All contractor employees shall clearly identify themselves as “contractors” at all times. This includes all communications (telephone, mail, electronic mail (email) and faxes), meetings, attendance sheets, and documents. In addition, contractor personnel shall identify their company affiliation in email signature blocks. All contractor personnel shall display their identification badge, which identifies them as contractor personnel. Contractor-occupied facilities on Government installations such as offices, separate rooms, or cubicles must be clearly identified with contractor supplied signs, name plates or other identification, showing that these are work areas for contractor or subcontractor personnel.

5.2.8 Surge requirement: Surge is defined as temporary work to support mission activities outside of the baseline TO effort in order to meet additional customer needs. The contractor must ensure they can provide this type of flexibility. In the event of a surge need, the contractor will be notified by the CO concerning the additional performance requirements.

5.3 Reviews, Meetings, and Conferences

5.3.1 The contractor shall conduct periodic Program or Task Management Reviews with the

Government Technical Lead and relevant RVE Task Order Technical Managers as specified in TOs. The agenda, date, and location of the review will be mutually agreed to by RVE and the contractor. The contractor shall take meeting minutes and provide these to the government to capture action and activities that transpired at the review. The Government reserves the right to call in emergency reviews of specific tasks with a 1-day notice when mission requirements warrant such off-calendar reviews.

5.3.2 The contractor shall participate in design reviews, off-sites, technical interchange meetings, working groups, or technical conferences with Government and contractor organizations, as required by TOs.

5.4 Release of Information

5.4.1 Public Release: The contractor shall prepare briefings and special technical reports or papers as requested and shall provide the Government with copies of all materials to be presented. If such briefings, reports, or papers are to be released to the public, the contractor shall comply with DFARS 252.204-7000, Disclosure of Information. In this case, the contractor shall provide one copy each to the Contracting Officer, the Government Technical Lead, and to the TO Technical Manager at least 45 days prior to the scheduled release date for OPSEC review.

5.4.2 Acknowledgement of Sponsorship. In the release of information relating to this contract such release shall include a statement to the effect that the project or effort depicted was or is sponsored by the Air Force Research Laboratory. For the purpose of this clause "information" includes but is not limited to material presented in news releases, articles, Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 9 of 14 manuscripts, brochures, advertisements, still and motion pictures, speeches, presentations, meetings, conferences, and symposia. Nothing in the foregoing shall affect compliance with the requirements of the clause of this contract entitled "6. Security Requirements". The contractor shall include this requirement in any subcontracts awarded as a result of this contract.

5.4.3 Non-Disclosure Agreements. The contractor is responsible for obtaining and providing all Non-Disclosure Agreements (NDAs) for personnel supporting AFRL under this contract to protect all proprietary, restricted, competition sensitive, or any other restricted (e.g. non-foreign disclosure due to public law) data that will be used or accessed during the execution of this contract.

5.5 Contract Performance

The Government Technical Lead for the RISE contract will conduct semi-annual (6 months) performance assessments in accordance with the evaluation criteria found in the Past Performance Information Retrieval System (PPIRS) and Contractor Performance Assessment Reporting System (CPARS). Contractor performance will be assessed at the TO level in the following areas: Schedule, cost management, program management, subcontractor management, and other areas determined relevant to the TO. TO performance evaluations will support the overall contract evaluation and performance rating. The RISE contract Government Technical Lead will conduct an annual assessment of contract performance and document the findings in

CPARS.

5.6 Subcontractor Management

The contractor shall be responsible for any subcontract management necessary to integrate work performed on this contract and shall be responsible and accountable for subcontractor performance on this contract. The contractor shall manage work distribution to ensure there is no Organizational Conflicts of Interest (OCI). Contractors may add subcontractors to their team after examination of information that there is no OCI issue or submission and approval of mitigation plan by the CO. If a Subcontractor is contracted to perform the work on a requirement, a signed and processed DD Form 254 between the contractor and subcontractor may be required before the subcontractor begins performance on this contract.

5.7 Cost Control

The contractor shall demonstrate effectiveness in forecasting, managing, and controlling task order costs for Other Direct Costs. The contractor shall provide total accountability, accuracy, disclosure, control, forecasting, estimating, and overall management of all cost-based control activities, including monthly status report, trip reports, certificates of service, invoices, proposals, and limitation of funds.

5.8 Temporary Duty (TDY) Travel

The contractor may be required to travel using commercial air, Government air, and other conventional modes. Travel arrangements will be based on individual tasks, and the cost of travel will be directly reimbursed from task funding. All travel (Outside Continental United States and Continental United States (OCONUS & CONUS)) requires prior coordination by the Government Technical Lead. Additionally, all OCONUS travel must be approved in advance by the PCO or Government Technical Lead designated by the PCO. Minimal local travel may be required. In no case will the total travel for each task exceed the travel dollars estimated/funded in the individual tasks/subtasks. Travel to other government facilities or other contractor facilities may be required. All travel requirements (including plans, agenda, itinerary, dates) shall be pre-approved by the Government Technical Lead or PCO; and is on a strictly cost

Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 10 of 14 reimbursable basis. Costs for travel shall be billed in accordance with the regulatory implementation of Public Law 99-234, Federal Civilian Employee and Contractor Travel Expense Act of 1985 and FAR 31.205-46 Travel Costs and Joint Travel Regulations. The contractor shall, at no charge to the Government, submit a Notice of Excess Commercial Airline Ticket Cost report when the use of other than least costly air travel is required to complete a Government directed task (A002, A007, AXXX).

6. Security Requirements

6.1 Clearance Requirements

The contractor shall establish and implement information and physical security programs governing their efforts in accordance with the applicable DD254 Contract Security Classification Specification. Contractor personnel shall have a minimum of a Secret clearance. Where certain AI&T Laboratories have higher security requirements, the contractor personnel shall have a current DoD Top Secret/SCI clearance or higher, per TO specifications. The Government will provide the contractor with system security classification guidance and instructions as required.

6.2 Technical Assistance Agreement (TAA)

The contractor shall comply with the U.S. State Department’s ITAR (22 CFR Parts 120-130 and Amendments), the Arms Export Control Act, Defense Trade Security Initiatives, State Department, USAF, and Department of Defense policies relative to the ITAR and exporting and importing data especially for non-Foreign Military Sales cases. The contractor shall obtain a TAA with each of the foreign nations identified by the Government Technical Lead at the time of any resulting contract and for the duration of this contract within 90 days after notification, with the appropriate agencies, such as the Department of State, to export and receive technical data (direct commercial sales) to Federal Acquisition Regulation (FAR) Part 12/FAR Part 15 contract activities. The contractor shall maintain the TAA for the duration of the task order.

6.3 Government Data Systems Access

6.3.1 Performance under this effort may require access to unclassified Air Force computer systems

(standalone and networked). The contractor shall comply with local procedures for obtaining approval for employees to access required Air Force computer systems.

6.3.2 The contractor is prohibited from attaching any computer hardware to the PRS network, or running any computer software unless it 1) is Government furnished equipment, or 2) has been certified and accredited according to current PRS Operating Instructions. Any such requests for reconfiguration, upgrade, or addition of computer hardware or software must be approved by the PRS Designated Approval Authority (DAA) Representative via the contractor's submission of a written request to the Program Manager (PM). Contractor use of computer modems on any machine attached to the PRS network is prohibited unless prior written approval is obtained from the PRS DAA Representative. Use of commercial internet service providers is prohibited unless prior written approval is given by the PRS DAA Representative.

6.3.3 Contractor personnel using any PRS information technology assets shall comply with all PRS computer security requirements. In addition, should contractor personnel require access to PRS computer networks or databases, they shall inform the PM or Deputy PM, who will arrange for the contractor personnel to complete the required documentation for a new computer account. The contractor shall notify the PM or Deputy PM within one workday of any contractor personnel who no longer requires an open account and shall take action to close the computer account with the appropriate PRS office within that same workday.

Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 11 of 14

6.3.4 All contractor personnel who will be using C4 systems belonging to the federal Government to generate, process, store, transfer, or communicate information shall attend mandatory C4 systems security training.

6.3.5 All contractor personnel who perform daily network management control or administration of information flow responsibilities (i.e., Workgroup Manager or System Administrator) are required to be certified Information Assurance (IA) network professionals, a certification that is obtained by completing Air Force provided interactive computer-based training (CBT).

These IA CBTs are in addition to the mandatory C4 systems security training mentioned above.

6.3.6 The contractor shall notify the PM of any Government C4 system problems or issues which come to their attention that may impact the contractor's task schedule.

6.3.7 All contractor personnel who require access to PRS C4 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 PM that the Government grant contractor employee(s) interim access to the PRS C4 network while awaiting the results of a NAC. Interim access to the PRS C4 network will only be granted after the contractor employees obtain at least a local background file 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.

6.3.8 Communications Security (COMSEC) Monitoring. All communications with DoD organizations are subject to Communications Security (COMSEC) review. Contractor personnel will be aware that telecommunications networks are continually subject to interception by unfriendly intelligence organizations. The DoD has authorized the military departments to conduct COMSEC monitoring and recording of telephone calls originating from or terminating at DoD organizations. Therefore civilian contractor personnel are advised that any time they place a call to or receive a call from a USAF organization they are subject to COMSEC procedures. The Contractor will assume the responsibility for ensuring wide and frequent dissemination of the above information to all employees dealing with official DoD information.

7. Associate Contractor Agreements

7.1 The contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government's requirement.

The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the R&D Integrated Space Experiments (RISE) program, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract.

7.2 ACAs shall include the following general information:

(1) Identify the associate contractors and their relationships.

(2) Identify the program involved and relevant Government contracts of associate contractors.

(3) Describe the associate contractor interfaces by general subject matter.

(4) Specify the categories of information to be exchanged or support to be provided.

(5) Include the expiration date (or event) of the ACA.

(6) Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

7.3 A copy of such agreement shall be provided to the CO for review before execution of the document by the cooperating contractors.

Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 12 of 14

7.4 Nothing in the foregoing shall affect compliance with the requirements of the clause at 5352.209-9002, Organizational Conflict of Interest.

7.5 The contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

7.6 Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

7.7 All costs associated with the agreements are included in the negotiated cost of this contract.

Agreements may be amended by the Government during the performance of this contract.

8. Deliveries Task order specific.

Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 13 of 14

Attachment 1: Compliance Documents The contractor shall comply with those tasks specifically applicable to contractor personnel in the latest version of these documents. Documents can be found at http://www.e-publishing.af.mil

AFI 10-701, Operations Security (OPSEC) AFI 11-202, Volume 3: General Flight Rules AFI 21-113, Air Force Metrology and Calibration (AFMETCAL) Management AFI 24-301, Vehicle Operations AFI 31-601, Industrial Security Program Management AFI 32-7042, Waste Management AFI 32-7086, Hazardous Materials Management AFI 33-112, Information Technology Hardware Asset Management AFI 33-119, Air Force Messaging AFI 33-200, Information Assurance (IA) Management AFI 61-204, Disseminating Scientific and Technical Information AFI 91-202, US Air Force Mishap Prevention Program, AFRL Supplement 1 AFI 91-207, US AF Traffic Safety Program AFI 99-103, Capabilities Based Test and Evaluation AFMAN 91-201, Explosives Safety Standards AFMCI 23-201, Logistics Material Control Activity Operating Instruction AFOSHSTD 48-139, Laser Radiation Protection Program AFOSHSTD 48-22, Occupational Exposure to Hazardous Chemicals in Laboratories AFOSHSTD 91-46, Materials Handling and Storage Equipment AFOSHSTD 91-5, Welding, Cutting and Brazing AFOSHSTD 91-501, Air Force Consolidated Occupational Safety Standard AFOSHSTD 91-66, General Industrial Operations AFOSHSTD 91-68, Chemical Safety AFRLI 21-101, Tool and Equipment Management Program AFRLI 21-102, General Logistics Program Management and Responsibilities AFRLI 21-103, Quality Assurance Program AFRLI 21-104, Technical Data Management (TDM) AFRLI 21-105, AFRL Foreign Object Damage Prevention Program AFRLI 21-107, AFRL Electrostatic Discharge Control Program AFRLI 61-103, AFRL Research Test Management AFRLI 91-101, Laboratory System Safety Program AFRLMAN 99-103, AFRL Flight Test and Evaluation DoD 4145.26M, DoD Contractor’s Safety Manual for Ammunition and Explosives DoD 5200.2-R, Personnel Security Program DoD 6055.9-STD, DoD Ammunition and Explosive Safety Standards DoD-5220.22-M, National Industrial Security Program Operating Manual (NISPOM) FAR (Federal Aviation Regulations) 101, Part D, Unmanned Free-Flying Balloons KAFBI 48-106, Workplace Written Hazard Communication Program KAFBI 48-109, Laser Hazard Control Program KAFBI 91-201, Transportation Procedures for Hazardous Material, Radioactive Materials and Explosives KAFBI 91-521, Lockout/Tagout Program MIL-STD-882D, Standard Practice for System Safety Phillips Research Site (PRS) OI 21-101, Tool and Equipment Management PRS OI 31-401, Managing the Information Security Program PRS OI 36-12, Contract Personnel In/Out Processing Procedures PRS OI 91-101, Environment, Safety, and Occupational Health RV OI 61-1201 (OSS&E and Lifecycle SE) RV Supplement to AFRLI 61-103 (AFRL Research Test Management)

Attachment 2: Reference Documents

Source Selection Information ‐‐ See FAR 2.101 and 3.104. Page 14 of 14

The contractor shall reference the latest version of these documents. Documents can be found at http://www.e-publishing.af.mil and http://www.assistdocs.com

AFHDBK 11-203, Weather for Aircrews: Flying Operations AFI 10-1202, Space Test Program (STP) Management AFI 11-208, DoD Notice to Airmen (NOTAM) System AFI 33-106, Managing High Frequency Radios, Land Mobile Radios, and the Military Affiliate Radio System AFI 33-210, Air Force Certification and Accreditation (C&A) Program (AFCAP) AFOSHSTD 91-100, Aircraft Flightline-Ground Operations and Activities AFPD 61-1, Management of Science and Technology AFSPCI 33-202, Information Assurance AFSPCMAN 91-710, Range Safety User Requirements AFSPCMAN 91-710, Volume 1: Air Force Space Command Range Safety Policies and Procedures AFSPCMAN 91-710, Volume 2: Range Safety User Requirements Manual - Flight Safety Requirements AFSPCMAN 91-710, Volume 3: Range Safety User Requirements Manual – Launch Vehicles, Payloads, and Ground Support Systems Requirements AFSPCMAN 91-710, Volume 6: Range Safety User Requirements Manual – Ground and Launch Personnel, Equipment, Systems, and Material Operations Safety Requirements AFSPCMAN 91-710, Volume 7: Range Safety User Requirements Manual – Glossary of References, Abbreviations, and Acronyms, and Terms DoD-HDBK-343, Design, Construction, and Testing Requirements for One-Of-A-Kind Space Equipment EWR 127-1, Eastern/Western Range Safety Policies and Procedures MIL-HDBK-340A, Test Requirements for Launch, Upper-Stage, and Space Vehicles MIL-STD-1512, Electro-explosive Subsystems, Electrically Initiated, Design Requirements and Test Methods MIL-STD-1576, Electro-explosive Subsystem Safety Requirements and Test Methods for Space Systems MIL-STD-1540C, Test Requirements for Launch, Upper-Stage, and Space Vehicles MIL-STD-1540D, Product Verification Requirements for Launch, Upper-Stage, and Space Vehicles United Launch Alliance Atlas V Launch Vehicle User’s Guide (latest version) United Launch Alliance Delta IV Launch Vehicle User’s Guide (latest version)

Attachment 3: CDRLs

Attachments 4A-D: Base Support Lists to be provided separately from the basic SOW.