Updated ISC 2 Basic DRAFT PWS v2.5.pdf

Intercontinental Ballistic Missile (ICBM)

Integration Support Contract (ISC) 2.0

Performance Work Statement

For

ICBM Systems Directorate (ICBMSD)

Air Force Nuclear Weapons Center (AFNWC)

DATE XXX

Contents

1.0 GENERAL INFORMATION AND SCOPE

1.3. ISC SCOPE

1.4 OTHER INFORMATION

2.0. TRANSITION

2.3. Transition Plan

2.4. Data Transition

2.5. Deliverables

2.6. Phase Out

3.0. GENERAL REQUIREMENTS .............................................. Error! Bookmark not defined.

3.1. Applicability

3.2. Role of the Contractor ......................................................... Error! Bookmark not defined.

3.3. Compliance

3.4. Inherently Governmental Functions

3.5. Non-Disclosure Agreements (NDAs)

3.6. Organizational Conflicts of Interest (OCIs)

3.7. Travel/Temporary Duty (TDY)

4.0. TECHNICAL REQUIREMENTS

4.1. General

4.2. Weapon System Sustainment Requirements

4.3. Acquisition Program Requirements

4.4. Integration Offices Requirements

4.5. Directorate & Functional Offices Requirements

5.0. SECURITY REQUIREMENTS

5.1. Compliance

5.2. Security Clearances

5.3. Visit Requests

5.4. Trustworthiness Determination

5.5. Personnel Reliability Program

5.6. Security Training

5.7. Handling Classified and Sensitive Information and Material

5.8. Operational Security (OPSEC)

5.9. Communications Security (COMSEC)

6.0 PHYSICAL SECURITY

6.1. Facilities

6.2. Key Control

6.3. Lock Combinations

6.4. Industrial Security

6.5. Controlled/Restricted Areas

7.0. INFORMATION ACCESS REQUIREMENTS

7.4. Government Rights in Data and Software (GRIDS)

7.5. Records

8.0 INSTALLATION PROCEDURES

8.1. Regulation Compliance

8.2. Base Access ........................................................................ Error! Bookmark not defined.

8.3. Pass and Identification Items

8.4. Disposition of Base Identification Media ........................... Error! Bookmark not defined.

8.5. Contractor Identification in Government Workplace

8.6. Emergency Evacuation Procedures

8.7. Antiterrorism Considerations

8.8. Access to Worksite

8.9. Alternate Facilities

8.10. Conservation of Utilities

8.11. Continuation of Essential DoD Contractor Services During Crisis

9.0. CONTRACT MANAGEMENT

9.1. Contracting Officer’s Representative (COR)

9.2. Non-Personal Services

9.3. Associate Contractor Agreements

9.4. Quality Control

9.5. Quality Control Plan (QPC)

9.6. Government Inspection/Evaluation

9.7. Cost Control

9.8. Performance Evaluation ...................................................... Error! Bookmark not defined.

9.9. Minor Non-conformance

9.10. Major Non-conformance

9.11. Non-Conformance Self-Identification

9.12. Access to Contractor Facilities

9.13. Normal Days and Hours of Operation

9.14. In/Out Processing

10.0. CONTRACTOR PERSONNEL MANAGEMENT ............. Error! Bookmark not defined.

10.1. All Contractor personnel shall be U.S. citizens. ............... Error! Bookmark not defined.

10.2. Human Resource Acquisition and Retention .................... Error! Bookmark not defined.

10.3. Contractor Staffing

10.4. Workforce Stability

10.5. Contractor Personnel Administration. .............................. Error! Bookmark not defined.

10.6. Contractor Personnel Training .......................................... Error! Bookmark not defined.

10.7. Contractor Manpower Reporting

10.8. Rehabilitation Act Compliance (Section 508)

11.0. GOVERNMENT-FURNISHED PROPERTY (GFP), EQUIPMENT (GFE), &

INFORMATION (GFI) (IAW FAR 52.245-1)

11.6. Nuclear Weapons Related Material (NWRM)

11.7. Use of Personal Equipment

11.8. GFE in Alternate Work Sites

11.9. Protection from Loss

11.10. Safeguarding Government Property

12.0. SAFETY

APPENDIX C

C1.0. Program Requirements

C1.1. Mishap Notification

C1.2. General Safety Requirements:

C2.0. Section II – Specific Requirements

C2.1.Pedestrian Crosswalks

C2.2. Motor Vehicles

C2.3. Walking – Working Surfaces

C2.4. Personal Protective Equipment

C2.5. System Modification-Which Alters Form, Fit or Function

C2.6. Materials Handling and Storage

C2.7. Hearing Conservation Program Elements

C2.8. Medical and First Aid

C2.9. Explosive Safety Requirements

C2.10. Foreign Object Damage (FOD) Awareness, Prevention and Responsibilities

C2.11. Housekeeping

C2.12. General Fall Protection

ATTACHMENT A - COMPLIANCE DOCUMENTS ................. Error! Bookmark not defined.

ATTACHMENT B - REFERENCE DOCUMENTS .................... Error! Bookmark not defined.

ATTACHMENT C - MODELS..................................................... Error! Bookmark not defined.

ATTACHMENT D - CDRL REFERENCE TABLE .................... Error! Bookmark not defined.

ATTACHMENT E - ACRONYMS............................................... Error! Bookmark not defined.

APPENDIX F – LABOR CATEGORY TABLE .......................... Error! Bookmark not defined.

1. INTRODUCTION

a. PURPOSE

The ICBM Systems Directorate (ICBMSD) requires a broad range of professional program management, acquisition, engineering, scientific, research, financial, and administrative support to execute effective and responsive integrated lifecycle acquisition and sustainment for both the

Minuteman III (MMIII) and the next-generation Ground Based Strategic Deterrent (GBSD)

ICBMs. This contract will augment Government resources, enabling successful execution of

ICBMSD’s responsibility as ICBM weapon system integrator.

This document provides scope, general requirements, and a description of the types of services required from the Integration Support Contract (ISC). It is not intended to specify to the

Contractor how to perform the required services. It is in no way intended to suppress innovative ideas or approaches for performing required services. Specific requirements will be detailed in individual Task Order PWSs.

b. ICBMSD MISSION AND DESCRIPTION

The mission of the ICBMSD is to deliver 400 combat capable nuclear missiles that are safe, secure, and effective. ICBMSD currently consists of 3 bodies of responsibility: “MMIII SPO”, “GBSD SPO”, and “Directorate & Functional Offices”.

NOTE: Organizational charts and descriptions in this and any Task Order PWS are for illustrative purposes only. The Government reserves the right to update/change the ICBMSD organizational structure at any time before or during the contract period.

MMIII SPO Mission and Description

The MMIII SPO mission is to develop, acquire, modify, and sustain the nation’s MMIII nuclear deterrent force.

The Acquisition Branch exists to mitigate sustainment risks through execution of ACAT I, II, or III programs. These programs operate in parallel to sustainment items, which in turn are tied to MMIII Work Breakdown Structure (WBS) elements.

o Note: The Services section in the Acquisition Branch is responsible for preparation and award of service contracts used by the ICBMSD. Due to conflict of interest issues, the ISC does not include support for the Services section.

The Integration Branch provides specialty engineering and technical support to MMIII acquisition and sustainment programs/projects as well as select functional areas of support to GBSD.

The Sustainment Branch ties together the components of the WBS (Propulsion, Guidance, RS/RV, Ground Mechanical, Ground Electrical, and IIE) and Field Support to best sustain product delivery.

GBSD SPO Mission and Description

The GBSD SPO mission is develop, acquire, modify, and sustain the nation’s next generation nuclear deterrent.

Directorate & Functional Offices Mission and Description

The Directorate Functional Offices provide policy and governance support with the mission of organizing, training, and equipping both SPOs.

c. ICBMSD CONTRACT SUPPORT

ICBMSD manages many contract actions, as illustrated below.

MMIII SSCs

MMIII SSCs provide the preponderance of sustaining engineering support to the MMIII subsystems. Each SSC includes the sustaining engineering efforts for that subsystem and any relevant Operations and Maintenance (O&M) support tasks required to sustain the subsystem that are not accomplished on a different contract or by an organic entity.

Other Contracts

Other ICBMSD contracts include Prime contracts for ACAT and/or non-ACAT programs, software IV&V, specific program support contracts, etc.

NOTE: Organizational charts and descriptions in this and any Task Order PWS are for illustrative purposes only. The Government reserves the right to update/change the ICBMSD organizational structure at any time during the contract period.

d. ADDITIONAL INFORMATION

“Contractor”

Unless otherwise stated, the use of “Contractor” refers to the ISC Contractor and their

Subcontractors. All references to other Contractors will be specifically stated (e.g. Subsystem

Contractors, NSCCA/PATE Contractors, etc.).

Proposal Preparation Cost

Proposal preparation costs are not allowed as a direct charge to this contract.

Lists and Examples

All lists or examples provided in this and any Task Order PWS are for illustrative purposes only and not intended to be all inclusive.

2. ISC SCOPE

2.1. Overall Contract Scope

The main function of the ISC is to augment ICBMSD Government resources, enabling successful execution of their responsibility as ICBM weapon system integrator.

2.1.1. The contractor shall support effective and responsive integration throughout the lifecycles of ICBM weapon systems by providing knowledge, experience, and resources across a broad range of diverse professional disciplines and functional capabilities. These disciplines and capabilities include areas such as acquisition, administration, business analysis, cybersecurity, engineering, finance, integration, mission effectiveness, Nuclear Surety, Program Management, research, risk management, science, strategy development, sustaining engineering, System

Engineering (SE), system safety and security, technical assessment, etc.

2.1.2. The Contractor is responsible for providing solutions that directly support the

ICBMSD mission in terms of cost, schedule, performance, and risk.

2.1.3. The Contractor shall provide System Engineering and Integration service. The

Systems Engineering process consists of evolving functional and design requirements. It has as its goal the achievement of the proper balance between operational, economic, and logistics factors. It employs a sequential and iterative methodology to reach cost effective sustainment solutions. Information developed from this process is used to plan and integrate the engineering effort for the system as a whole.

2.1.4. This contract is designed to be flexible and allow for workforce adjustments to gain efficiencies based on changing requirements, policy, realities of the industrial base, and Government capability. The nature of this work will, at times, require the

Contractor to respond quickly to stringent deadlines.

2.1.5. The dynamic nature of both ICBM weapon systems requires unique and diverse support while synergistically utilizing cross-cutting support.

2.1.5.1. The Contractor has the flexibility and responsibility to manage its workforce in the most effective and cost efficient manner to meet requirements, to include aggregating resources at various levels of the organization as required.

2.1.5.2. Effectiveness and efficiency gains may span all functional disciplines, however, execution of programs and other government requirements shall not be sacrificed solely for the purpose of cost reduction.

2.1.6. ISC 2.0 requires many types of contract deliverables, such as information, advice, opinions, alternatives, analyses, evaluations, processes to eliminate waste, standardizing best practices, reducing cycle times/cost of doing business, documentation, recommendations to complement the Government’s organic resources in accomplishing its mission, etc.

2.1.7. Objectives and Key Results (OKRS)

ICBMSD continually develops OKRs to increase operational credibility, strengthen enterprise partnerships, and optimize directorate resources. Typically these are reviewed and adjusted on a quarterly basis.

The OKRs are a critical focus area and provide the general direction for activities and support. The OKRs fall within 2 categories:

a. Committed – There is agreement that it will be achieved and programs/ functions are willing to adjust schedules and resources to ensure that they reach 100%

b. Aspirational – Expresses where the organization would like to go, even though there is a lack of clarity in execution and/or the necessary resources to deliver the OKR

There are three ICBMSD-level OKRs:

Increased Operational Credibility

Strengthened Enterprise Partnerships

Optimized Directorate Resources

2.1.7.1. ISC scope includes supporting and helping to achieve all OKRs throughout the ICBMSD as stated in the Award Fee Plan.

2.2. MMIII Scope

The MMIII is in the Operation and Support Phase of its life cycle. The MMIII System Program

Office (SPO) is responsible for sustainment of the MMIII operational force in a state of readiness, such that national defense strategies involving these systems can be successfully executed, if required.

2.2.1. Weapon System Sustainment

2.2.1.1. The ISC contractor shall perform all efforts necessary to support the SPO in sustaining the MMIII.

2.2.1.2. Weapon System Sustainment includes:

Incorporation of changes to ICBM Systems in response to requirements for performance improvements

Appropriate use of advances in technology

Correction of system deficiencies

Determining the need for and executing life extension programs

Implementation of policies mandated by Congress or directed by other higher authorities

Addressing threat or safety driven changes or other changes in the operational or support environment

2.2.2. Sustaining Engineering

The AFMC definition of Sustaining Engineering is: “Engineering effort on systems, products, or materials, required to resolve technical or supportability deficiencies revealed in operational service.”

2.2.2.1. The ISC contractor shall provide sustaining engineering

2.2.2.2. A major portion of Sustaining Engineering efforts for ICBMs are dedicated to assessment of ICBM weapon system status relating to key performance requirements. It includes:

Assessing deficiency indicators

Defining the characteristics and causes of deficiencies

Determining the impact on the affected product

Identifying and evaluating alternative solutions

Recommending preferred solution

Designing, integrating and validating the solution

2.2.2.3. It includes all associated efforts (e.g. engineering and technical data, modeling, simulation, and testing) which are integral to the completion of the overall engineering task as well as the engineering effort necessary to define and specify necessary embedded system and associated test system software changes after establishment of an initial software production baseline.

2.2.3. Changes and Modifications

Requirements for changes or modifications to fielded systems are usually applicable at the subsystem or lower level and performed primarily by subsystem support contractors.

Satisfying these requirements involves activities that potentially impact system-level performance.

2.2.3.1. A primary focus of the ISC 2.0 for the MMIII SPO is to ensure any modifications or changes to the system will maintain and/or improve system-level performance. Successful accomplishment of this goal will require processes such as:

Weapon system and subsystem performance assessment

Systems requirement determination

Trade studies

Subsystem/item specifications

Configuration management and control

Test and evaluation

Application of streamlined program management techniques

2.2.3.2. The ISC Contractor shall support the MMIII SPO in managing the efforts/contracts required to integrate and incorporate changes and modifications, and sustain the MMIII.

2.2.4. Performance Parameters

Top-level system performance parameters that reflect the adequacy of MMIII force readiness are availability, reliability, accuracy, and hardness. These parameters represent performance values below which the system cannot be allowed to fall unless coordinated decisions are made to allow such degradation based on funding and program considerations. As the MMIII force continues to age and is modified and upgraded, opportunities for changes in capability and performance effectiveness are introduced.

At the subsystem/system-level, numerical values have been established for availability, reliability, and accuracy. The actual numerical values are outside the classification scope of this document and will not be specified herein. Hardness is specified at the subsystem-level and there are no numerical threshold values established at the system-level for this performance parameter.

2.2.4.1. The Contractor’s responsibilities relative to these top level system performance parameters will consist of working alongside the Government to continually assess operational performance, determine and report current performance capabilities of the MMIII weapon system compared to baseline values, and identify as early as possible in the assessment process potential areas of performance degradation that would impact capability.

2.2.4.2. The Contractor shall provide the engineering services necessary to determine the basic causes of potential System Performance degradation.

2.2.4.3. This process is performed primarily at the subsystem-level, but can also be required at the system-level. It includes using engineering analysis techniques such as:

Design analysis

Testing

Evaluation of operational data

Reliability modeling

Failure Modes and Effects Analysis (FMEA)

Physical failure analysis

Other conventional engineering problem identification techniques

2.2.5. Corrective Actions

2.2.5.1. IPTs and/or subsystem Contractors develop corrective actions. The ISC contractor shall work with the Government to evaluate those actions, plan resources, and implement the government-approved solution.

2.2.5.2. In cases where the proposed solution involves actions outside the scope of

Contractor responsibilities the Government will implement the solution.

The Contractor’s role is monitoring and assessing the effectiveness of the corrective action, and reporting results.

2.2.6. Translating Operational Parameters

Field operations introduce factors that are outside the control of designers (maintenance management policies and procedures, storage, supply, transportation, procurement of replacement spares, materials, parts, and pieces to support maintenance, utilization, and environment). Because of this, operational values of reliability, maintainability, and availability are typically not used directly for contractual requirements.

2.2.6.1. The ISC Contractor is responsible for translating required operational performance parameters into inherent design performance parameters that can be used to define, measure, and evaluate programs. The translation process will ensure traceability between the proposed design performance parameters and the top-level system operational performance values.

2.3. GBSD Scope

2.3.1. GBSD Acquisition

(U) The GBSD acquisition program is a total system recapitalization for the MMIII ICBM

Weapon System (WS). This includes new missile systems, new Command and Launch

(C&L) systems, support systems and the conversion of the MMIII silos and Launch

Centers (LCs).

(U) The AF must balance the need for an ICBM system design that is operationally capable through 2075, while minimizing program risk to meet a 2028 delivery schedule.

2.3.1.1. The ISC Contractor shall work with and provide the necessary support for the Government to successfully accomplish the GBSD acquisition within program constraints

2.3.2. GBSD Enterprise

(U) In addition, the GBSD Enterprise includes the ICBM Fuze Modernization Program, Mk21A Program, and the Advance Planning section that is responsible to manage Science

& Technology (S&T) Studies, Demonstration & Validation, and S&T Roadmaps.

2.3.2.1. The ISC Contractor shall work with and provide the necessary support for the Government to successfully accomplish the other acquisition programs included in the GBSD Enterprise

2.4. Directorate Offices Scope

The Directorate Offices provide a thin layer of management to equip and provide organization and training for the ICBMSD.

2.4.1. The contractor shall provide the necessary support for the Government to successfully equip and provide organization and training for the ICBMSD.

2.4.2. The Contractor shall provide expertise representing the major areas of Sustainment, Acquisition, Integration, to provide an overarching perspective to senior leadership and assist in developing a clear understanding of the current status of MMIII and

GBSD.

3. CONTRACT REQUIREMENTS

3.1. Applicability

All requirements in this Basic PWS apply to all Task Orders, unless specifically waived by the

PCO.

3.2. Decision Authority

All decisions relative to programs supported by the Contractor are the sole responsibility of the

Government. The Government is ultimately responsible for meeting cost, schedule, technical, and performance objectives. As the system integrator, the Government is the decision authority.

3.2.1. All work shall be performed in coordination and cooperation with pertinent overseeing government personnel.

3.3. Compliance

3.3.1. All work shall be in accordance and compliance with laws, regulations, directives, policies, operating instructions, and other applicable publications

3.3.2. The contractor shall acquire and follow current versions of these publications.

3.3.3. All work performed/accomplished in a network or system shall be performed using applicable, approved government networks/systems, unless specifically directed otherwise

3.4. Contractor Staffing

3.4.1. All Contractor personnel shall be U.S. citizens.

3.4.2. The Contractor shall establish processes and assign appropriate resources to effectively administer contract requirements.

3.4.3. The Contractor shall be responsible for the employment, guidance, supervision, and training of all personnel assigned to perform tasks under this contract.

3.4.4. The Contractor shall provide the number of FTE and CME required by each TO.

For purposes of this contract, Full-Time Equivalents (FTEs) and Contractor Manpower

Equivalents (CMEs) are defined as follows:

FTE is defined as a Contractor employee (non-interchangeable), dedicated to a specific labor category position and assigned to a specific effort.

FTEs are based on 1880 hours annually.

A CME is defined as a number of hours provided for a specific labor category. The hours may be fulfilled by multiple individuals within the specified labor category

(interchangeable).

Required CME support may be up to 1880 hours annually.

3.4.5. The Contractor shall provide properly qualified labor possessing the appropriate education, training, trustworthiness determination/security clearance and experience/skills IAW the PWS requirements.

A master list of potential labor categories for use in the TOs of this contract is located in

Appendix F of this document. The labor category table identifies associated required qualifications. The skill level for which an individual qualifies is dependent upon relevant education, experience and capabilities of the individual which equips that person to perform within the assigned functional area.

3.4.5.1. The Contractor shall meet the labor category requirements identified in each TO PWS.

3.4.5.2. Any experience/education qualification shall be related to the functional area.

3.4.5.3. If there is no listing of minimum credentials, Contractor judgment and standards are acceptable when proposing and providing capability.

The Government is not responsible for the training of Contractor Employees to meet qualification requirements. Training of Contractor personnel is the sole responsibility of the

Contractor unless otherwise approved.

3.4.6. In the event that Government-unique training is necessary, training may be charged directly to a respective CLIN provided that CO approval is obtained prior to the training.

3.4.7. Contracted employees shall demonstrate progressive experience within the minimum qualification determination years. Progression is defined as the act of moving forward and proceeding in a career course.

3.5. Workforce Adaptability

3.5.1. Contractor personnel shall work alongside Government personnel as part of a team and may be required to act on behalf of the government.

3.5.2. The contractor shall ensure consistent, quality support throughout any priority/program transitions.

3.5.3. Contractor personnel shall “flex” as requirement priorities are adjusted by the

Government.

3.5.4. In the event of initiation or cancellation of programs/projects, the contractor shall adjust the workforce to support Government requirements.

3.5.5. In addition to “steady-state” support, the contractor shall accommodate surge requirements. “Surge” is defined as short-term work required to meet urgent needs, short-term non-urgent needs, or specific short-term deliverables outside typical program support requirements.

3.6. Contractor Behavior

3.6.1. Contractor personnel shall act as responsible agents and representatives of the

ICBMSD, the United States Air Force (USAF), the Department of Defense (DoD), and the Federal Government in accordance with (IAW) governing laws and regulations.

3.6.2. Contractor behavior shall be professional and reflect positively on the government

3.6.3. The contractor shall present an unblemished appearance in regards to ethics, discretion, protection of information, etc.

3.6.4. The contractor shall foster and maintain good working relationships with internal and external stakeholders and other ICBMSD contracted personnel.

3.6.5. The contractor shall collaborate with internal and external stakeholders as needed to accomplish requirements and tasks.

3.6.6. Work shall be performed in coordination with the applicable Subsystem Support

Contractor(s) (if applicable) and/or other contracted personnel.

3.7. Workforce Stability

3.7.1. The contractor shall provide uninterrupted quality support and continuity of capability.

3.7.2. The Contractor shall minimize turnover and manage personnel to minimize the impact of any turnover and/or disruption to the customer and/or mission.

3.7.3. The Contractor shall ensure continuation of services during personnel gaps due to sickness, leave, and voluntary or involuntary termination from employment such that there is no negative impact to the Government mission or schedule.

3.7.4. The contractor shall provide a qualified replacement within 45 calendar days from the date of any vacancy.

3.7.4.1. If a replacement cannot be provided within 45 calendar days from the date of vacancy, the Contractor shall notify the CO and provide a corrective plan as soon as the issue becomes known. The CO may issue a CAR as defined in paragraph 9.4 of this document.

3.7.4.2. If the contractor determines that eliminating the vacated position would be an efficiency (due to changes in requirements, staffing efficiencies, management strategy, etc.), the contractor shall notify the PCO and submit rationale, including clearly detailing how fulfillment of the government’s requirements will not be impacted by the change. The PCO will evaluate the rationale and make a determination.

3.7.5. The Government reserves all rights of direct removal (permanent or temporary) of personnel for security, safety, or health reasons, upon discovery of fraudulent credentials/qualifications, or when Contractor personnel behave in an unprofessional manner that would be considered unacceptable by a reasonable person. The request will be provided in writing by the CO.

3.7.5.1. The Contractor shall provide a qualified replacement within 45 calendar days, at no additional cost to the government.

3.8. Contractor Manpower Reporting

3.8.1. The Contractor shall provide total accountability, accuracy, disclosure, control, forecasting, estimating, and overall management of all cost-based control activities in the form of monthly status reports (MSR), expenditure reports, invoices, proposals, and limitation of funds/costs notifications, etc.

3.8.2. The Contractor and its subcontractors’ accounting systems shall provide traceability of all man-hours and cost reimbursable elements (travel, supplies/materials, computer lease charges, etc.) to individual task order funding Accounting

Classification Reference Numbers (ACRNs), and information shall be provided as requested.

3.8.3. The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for

Integration Support via a secure data collection site.

3.8.3.1. The Contractor shall completely fill in all required data fields at http://www.ecmra.mil. Contractors may direct questions to the Contractor

Manpower Reporting Application (CMRA) help desk.

3.8.3.2. Reporting inputs shall be for the labor executed for each Government

Fiscal Year (FY) (1 October through 30 September) during the contract period of performance.

3.8.3.3. All data shall be reported no later than 31 October of each calendar year

(inputs may be reported any time during the FY).

3.9. Inherently Governmental Functions

Execution of this contract will require Contractor personnel to work in close association with the government to the extent that the Contractor will be highly visible representatives and may be required to act on behalf of the government, however, this contract does not require nor authorize the Contractor to perform Inherently Governmental Functions.

As the system integrator, the Government is the decision authority. All decisions relative to programs supported by the Contractor are the sole responsibility of the Government. Thus, all work on this contract is to be performed in coordination and cooperation with the pertinent, overseeing government personnel.

3.9.1. The Contractor shall NOT perform inherently governmental functions as defined in

Federal Acquisition Regulation (FAR) 7.503 and Office of Federal Procurement

Policy (OFPP) Policy Letter 11–01, Performance of Inherently Governmental and

Critical Functions.

http://www.ecmra.mil/

3.9.2. The Contractor shall NOT counsel, mentor, make judgment and/or discretionary decisions or perform any other activities related to supervision of Government personnel.

3.9.3. The Contractor shall NOT provide nor accept contractual direction to/from other contractors. The authority to direct contractors belongs to the government.

3.9.4. If the Contractor believes that any action constitutes or may be perceived to constitute an Inherently Governmental Function, the Contractor shall notify the CO immediately.

3.10. Non-Personal Services

3.10.1. The Contractor shall manage its own employees and guard against any actions that constitute or resemble personal services. The Government will neither supervise

Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances will the Government assign tasks or work schedules to individual Contractor employees.

3.10.2. The Contractor shall notify the CO immediately if the Contractor believes any actions constitute or are perceived to constitute personal services, or are thought to be outside the scope of this contract.

3.10.3. Required tasks/work will be tasked through a Contractor Official Tasking Point of

Contact (COT POC).

3.10.4. The COT POC shall record Government-assigned tasks in the designated task tracking system.

3.10.5. The contractor shall designate all FTE positions as COT POCs.

3.10.6. CME positions are not required to be designated as a COT POC. As such, CME positions will receive tasking through the task tracking system.

3.11. Non-Disclosure Agreements (NDAs)

The Contractor may need to access other companies' proprietary information in order to perform the requirements of this contract. Also, contractors and major subcontractors must effectively share information concerning the status of programs and technical issues in order to competently and conscientiously support the ICBMSD. NDAs are required to facilitate this open communication and appropriately protect information. Violation of an NDA is considered a major security violation.

3.11.1. The Contractor shall obtain and maintain NDAs with all applicable Government, corporate, supplier, and sub-tier vendors with proprietary, restricted, competition sensitive, or any other restricted data that will be used or accessed during the execution of this contract.

3.11.2. The Contractor shall provide a copy of each NDA to the PCO.

3.12. Associate Contractor Agreements (ACAs)

3.12.1. The Contractor shall enter into ACAs for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirements.

3.12.2. All costs associated with the agreements shall be included in the negotiated cost of this contract.

3.12.3. A copy of any such agreements shall be provided to the CO for review before execution by the cooperating Contractors.

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

3.12.5. Agreements shall ensure the greatest degree of cooperation to meet the terms of the contract.

3.12.6. ACAs shall include the following general information:

Identification of associate Contractors and their relationships.

Identification of the program involved and relevant Government contracts of the associate Contractors.

Description of associate Contractor interfaces by general subject matter.

Specific categories of information to be exchanged or support to be provided.

Basis for sharing essential information, data, technical knowledge, expertise, and/or resources

Expiration date or event of the ACA.

Identification of potential conflicts between relevant Government contracts and the ACA, including agreements on protection of proprietary data and restrictions on employees.

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

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

3.13. Organizational Conflicts of Interest (OCIs)

Contractor personnel performing work under this contract may receive, have access to, or participate in development of proprietary or Source Selection information (e.g. cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent OCI as defined in FAR 9.5.

As such, this contract includes a specific special OCI H-clause with particular restrictions on the

ISC Contractor. The purpose of OCI restrictions is to assure objectiveness of all Contractor recommendations to the Government and create a cooperative relationship for the integration of

SSC and other contract efforts.

3.13.1. The Contractor shall notify the Government CO immediately should they become aware that any access or participation may result in an actual, potential, or perceived OCI

3.13.2. The contractor shall promptly submit a plan to the CO to avoid or mitigate any such

OCI. The Contractor’s mitigation plan will be accepted solely at the discretion of the government CO. In the event the CO unilaterally determines that an OCI cannot be satisfactorily avoided or mitigated, the CO may affect other remedies as deemed necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

3.14. Travel/Temporary Duty (TDY)

3.14.1. The Contractor shall travel in support of this effort, based on requirements in individual task orders.

3.14.2. The contractor shall travel to other government or contractor facilities, local or distant, as required to fulfil the requirements of this contract.

3.14.3. Travel outside of core business hours may be required to meet mission needs.

3.14.4. The Contractor shall obtain written approval for travel requirements prior to costs being incurred from the designated government program/effort lead.

3.14.4.1. At the Government’s request, the Contractor shall prepare and submit to the COR or government designee, a Travel Approval Request (TAR) for

CONUS/OCONUS travel (and/or a Letter of Authorization (LOA) for

Contractor employees to travel on military aircraft) prior to traveling.

3.14.4.2. All travel requests shall include the number of personnel, destination, purpose, dates, number of days, and the cost estimate of required travel.

Requests may also be required to include more detailed plans, agendas, itineraries, etc. on a case-by-case basis.

The COR or Government designee has the authority to approve CONUS TARs and other travel requests. The COR or Government designee will submit OCONUS

TARs and other travel requests to the CO for approval.

NOTE: *The Government is under no obligation to reimburse the Contractor for any travel in which prior written approval has not been received.*

3.14.5. Travel shall be accomplished using commercial air, Government air, and/or other conventional modes.

3.14.6. The Contractor shall use the lowest cost mode of transportation commensurate with mission requirements.

3.14.7. Costs for travel shall be billed IAW the regulatory implementation of Public Law

99-234, Federal Civilian Employee and Contractor Travel Expense Act of 1985, FAR 31.205-46 Travel Costs and Joint Travel Regulations.

3.14.8. Total travel expenses shall not exceed the travel dollars estimated/funded in the respective Task order CLIN.

3.14.9. Travel to/from contractor’s work facility and primary government work facility is not considered TDY travel under this contract.

3.15. Rehabilitation Act Compliance (Section 508)

Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d) requires that when

Federal agencies develop, procure, maintain, or use electronic information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who do not have disabilities, unless an undue burden would be imposed on the agency.

Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.

3.15.1. All services performed in response to this requirement shall comply with Section

508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d), and the

Architectural and Transportation Barriers Compliance Board Electronic and

Information Technology (EIT) Accessibility Standards (36 CFR part 1194).

3.15.2. The Contractor shall support the Government in its compliance with Section 508 throughout the development and implementation of the work to be performed.

4. TRANSITION REQUIREMENTS

4.1. The Contractor shall coordinate and accomplish transition of all responsibilities and system-level tasks from the ISC 1.0 Contractor to the ISC 2.0 Contractor and ICBMSD, including transfer of all data, tools, models used in performance of system-level support tasks, Systems Engineering, Sustaining Engineering, Acquisition Program Support, FDE

Support, Knowledge Transfer, etc.

4.2. The contractor shall coordinate activities between the ICBMSD, other Contractors, and customers to ensure gaps in service do not occur.

4.3. Transition Plan

4.3.1. The contractor shall submit a Transition Plan, identifying, at a minimum:

Tasks to be transferred

The person responsible for each task transfer

Exit criteria when transfer of responsibility for each task is considered complete

A proposed schedule reflecting completion of each task leading to total transition completion no later than the agreed-upon date

Key transition issues, risks, and mitigation strategies

4.3.2. The Contractor shall, in cooperation with the ISC 1.0 Contractor, execute the transition plan once approved by the Government

4.4. Data Transition

4.4.1. Historical data, generated before this ISC contract, including technical drawings, test data, aging surveillance data, reports and other technical, sustainment, and programmatic data are essential for successful sustainment and integration functions of this contract and the ICBM system. The majority of this data resides on a single database, but data may also exist throughout the ICBMSD to include hard copy data, CDs, and electronic data on internal share drives. During transition, the ISC

2.0 Contractor will be provided access to existing data management systems and databases. Access to existing databases may require signing a NDA.

4.4.2. The contractor shall coordinate and accomplish transition of all data from the ISC

1.0 contractor to the ISC 2.0 Contractor and ICBMSD

4.4.3. After award, the ISC 2.0 Contractor shall work with the ISC 1.0 Contractor (and

Subcontractors as required) to create a mutually agreed upon migration process for the capture and archive of ICBM data into designated Government systems.

4.4.4. The contractor shall submit a Data Transition Plan identifying, at a minimum:

Process for reviewing, categorizing, organizing and managing historical

ICBMSD data.

o The review process shall add efficiencies to government data and may include removal of non-essential data, re-marking data, re-categorizing data, and general data organization as needed to improve the integrity and applicability of historical data.

Tasks and processes for managing transition of ICBMSD data

Transition schedule

Any issues regarding data or license rights

How the IDE will interface with other ICBM data systems (if applicable)

4.4.5. The Contractor shall implement the Data Transition Plan upon Government approval.

4.5. Deliverables

4.5.1. The contractor shall provide a monthly report on transition progress until transition is complete.

4.5.2. The contractor shall provide to the Government contracting officer a copy of the transfer documents attesting responsibility transfer is complete.

4.6. Phase Out

4.6.1. In the event a follow-on contract is planned and solicited, the contractor shall provide information and supporting documentation related to labor resources and associated cost information, to be used for follow-on procurement activities.

4.6.2. In the event a follow-on contract is awarded to other than the ISC 2.0 contractor (or if operations revert to government organic support), the contractor shall:

4.6.2.1. Cooperate to the extent required to permit an orderly change over to the new support provider.

4.6.2.2. Provide familiarization to the new support provider.

4.6.2.3. Fully continue integration services during the phase-out familiarization period.

With regard to the successor contractor’s access to incumbent employees, a recruitment notice may be placed in each facility.

5. TECHNICAL/PROGRAMMATIC REQUIREMENTS

5.1. General

5.1.1. The contractor shall provide the support necessary to fulfil the ICBMSD mission of delivering 400 combat capable nuclear missiles that are safe, secure, and effective.

5.1.2. The contractor shall support effective and responsive integration throughout the lifecycles of ICBM weapon systems

5.1.3. The Contractor shall provide knowledge and experience across a broad range of diverse professional engineering, non-engineering technical and management support in multiple disciplines and functional areas throughout the lifecycle of

ICBM weapon systems, as detailed in individual Task Orders.

5.1.4. The Contractor shall maintain awareness of progress, technical issues, and status of

ICBMSD programs and efforts to ensure integration with the weapon systems and smooth transition to follow-on lifecycle phases.

5.1.5. The contractor shall recommend and incorporate process and resource efficiencies, including application of streamlined program management techniques and other industry best practices.

5.1.6. The Contractor shall augment and fill knowledge/expertise gaps on Source

Selection Evaluation Boards (SSEBs) by acting as non-decision-making advisors for Source Selections and related activities, IAW current DoD Source Selection procedures and the FAR as supplemented.

5.2. Weapon System Sustainment Requirements

5.2.1. The contractor shall provide resources and perform tasks to support the government in sustainment of the MMIII Weapon System, IAW applicable task orders.

5.3. Acquisition Program Requirements (MMIII and GBSD)

5.3.1. The contractor shall provide resources and perform tasks to support the government in execution of ACAT I, II, or III programs for both the MMIII and GBSD weapon systems, as detailed in applicable task orders.

5.4. Integration Offices Requirements

5.4.1. The contractor shall provide resources, knowledge, and expertise in high-demand/low-density functions for ICBM weapon systems and programs, as detailed in applicable task orders.

5.4.2. This support shall span all ICBMSD organizations and associated Task Orders

5.4.3. The contractor shall support the ICBMSD Data Management Office (DMO) in areas such as Data Management, Configuration Management, interface control, Systems Engineering, Risk Management, Technical Order Management Agency

(TOMA) support, Model Based Systems Engineering (MBSE), etc., as detailed in applicable task orders

5.4.4. The contractor shall support ICBMSD Specialty Engineering as detailed in applicable task orders, including support for Nuclear Surety, Nuclear Certification, Nuclear Hardness and Survivability, System Safety, Corrosion Prevention &

Materials Engineering, Environmental Engineering, System Security, etc.

5.4.5. The contractor shall support ICBMSD Test and Assessment as detailed in applicable task orders, including operational test launch, operational flight testing, weapon system assessment, modeling and simulation, test management, the

Strategic Missile Integration Complex, etc.

5.4.6. The contractor shall support the ICBMSD Alternate Lead Developmental Test

Organization (Alt-LDTO) as detailed in applicable task orders

5.4.7. The contractor shall support ICBMSD Diminishing Manufacturing Sources and

Material Shortages (DMSMS) efforts as detailed in applicable task orders

5.5. Directorate & Functional Offices Requirements

5.5.1. The contractor shall provide resources and perform tasks to support the government in providing policy and governance support with the mission of organizing, training, and equipping both SPOs, as detailed in applicable task orders.

5.5.2. The contractor shall support the ICBMSD Engineering office as detailed in applicable task orders

5.5.3. The contractor shall support ICBMSD Financial Management (FM) as detailed in applicable task orders

5.5.4. The contractor shall support the ICBMSD Product Support and Transition office as detailed in applicable task orders

5.5.5. The contractor shall support ICBMSD Portfolio Management as detailed in applicable task orders

5.5.6. The contractor shall support ICBMSD Information Technology (IT) and

Cybersecurity as detailed in applicable task orders

5.5.7. The contractor shall support the ICBMSD Lead Project office as detailed in applicable task orders

5.5.8. The contractor shall support ICBMSD Force Development Evaluation (FDE) as detailed in applicable task orders

5.5.9. The contractor shall support ICBMSD scheduling as detailed in applicable task orders

5.5.10. The contractor shall support MMIII demilitarization (DEMIL) as detailed in applicable task orders

5.5.11. The contractor shall support ICBMSD Operations Management as detailed in applicable task orders

5.5.12. The contractor shall support the ICBMSD Security office as detailed in applicable task orders

5.6. Meetings

5.6.1. Appropriate functional contractor personnel shall participate in, contribute to, and provide technical and programmatic expertise for meetings, reviews, and boards involving the program

Meeting examples:

o Conferences o Depot Repair Enhancement/Performance Quality Increase (PQI) Activities o Engineering meetings o Integrated Product Team (IPT) Meetings o Integrated Test Team Meetings (ITT) o Team meetings o Management meetings o Provisioning meetings o Technical Interchange Meetings o Working group meetings o Etc.

Program and Technical Review examples o Deficiency Reviews o Integrated Baseline Reviews o Life Cycle Management Reviews o Modification Design Reviews o Physical Configuration Audit o Program Management Reviews o Program Reviews o Program Technical Reviews o Technical Design Reviews o Technical Reviews o Test Readiness Review o Etc.

Board examples o Baseline Control Boards o Configuration Control Boards o Configuration Management Boards o Guidance Review Boards o Risk Management Boards o Safety Review Board (SRB) o Technical Evaluation Review Boards o Technical Review Boards o Etc.

5.6.2. The contractor shall provide administrative and logistical support for meetings (e.g.

planning, preparing agendas, scheduling, obtaining call-in numbers, sending invites, distributing materials, etc.).

5.6.3. The contractor shall develop and provide presentation materials

5.6.4. The contractor shall capture, coordinate, and distribute minutes when applicable

5.6.5. The contractor shall manage action items (e.g. track, provide answers, close, etc.)

5.6.6. The contractor shall present/brief on behalf of the assigned program when needed

5.6.7. The contractor shall develop, provide, and maintain team charters when applicable

5.7. Knowledge Transfer

The intent of Knowledge Transfer is to improve the core ICBM life cycle support competencies and capabilities of Air Force personnel

5.7.1. The Contractor shall facilitate and perform transition of industrial ICBM technical expertise and knowledge to the ICBM organic workforce.

5.7.2. Contractor Subject Matter Experts shall mentor SPO personnel and facilitate the sharing of ICBM-related knowledge between Contractor and System Program SPO personnel.

6. DATA REQUIREMENTS

6.1. Contract Data Requirements Lists (CDRLs)

A master list of potential CDRLs is provided as Attachment # of this document. Each Task Order on this contract will specify which of the CDRLs from the master list are required for that Task

Order.

6.1.1. The Contractor shall complete and submit data deliverables IAW the CDRLs.

6.2. Government Rights in Data and Software (GRIDS)

6.2.1. IAW **reference**, the Government retains unlimited…