Attachment 1 - BASIC PWS.pdf

FA8207-20-R-0003 - ISC 2.0

Basic PWS

INTERCONTINENTAL BALLISTIC MISSILE (ICBM)

INTEGRATION SUPPORT CONTRACT (ISC) 2.0

BASIC PERFORMANCE WORK STATEMENT (PWS)

FOR

AIR FORCE NUCLEAR WEAPONS CENTER (AFNWC)

ICBM ORGANIZATION AT HILL AIR FORCE BASE (AFB)

14 OCTOBER 2020

CONTENTS

1.0. INTRODUCTION ………………………………………………………….……………...…3

2.0. ISC SCOPE …………………………………………………………..……….....…….……...3

3.0. SUPPORT REQUIREMENTS ……….…………….…….……….…….……………………8

4.0. STAFFING REQUIREMENTS …….……….……….……….…………………………….15

5.0. TRANSITION ………….…………………….………….…………….……………………22

6.0. CONTRACT MANAGEMENT …….………….…………….………………….………….24

7.0. SECURITY ….….…......….....….…..........…….….…….….……….…...….…….…….…. 28

8.0. INSTALLATION PROCEDURES …….……………….…………………………………..33

9.0. GOVERNMENT-FURNISHED PROPERTY (GFP), EQUIPMENT (GFE),

MATERIALS (GFM), AND INFORMATION (GFI) ………………..…………………….35

10.0. SAFETY (“APPENDIX C”) ….………….…….……………….……………….…………37

ACRONYM LIST ….…….…….……….………………………….………….……….………..38

1.0. INTRODUCTION

For purposes of this contract, “ICBM Organization” refers to the Minuteman III (MMIII) and Ground Based Strategic Deterrent (GBSD) System Program Offices (SPOs) at Hill AFB.

a. Background The mission of the ICBM Organization at Hill AFB is to deliver 400 combat capable nuclear missiles that are safe, secure, and effective. To this end, the ICBM Organization requires a broad range of professional program management, acquisition, engineering, scientific, research, financial, and administrative support to execute effective and responsive integrated life cycle acquisition and sustainment for both the MMIII and the next-generation GBSD ICBMs. The Integration Support Contract (ISC) will augment Government resources, enabling successful execution of the Government’s responsibility as ICBM Weapon System (WS) integrator.

This document provides scope, general requirements, and a description of the types of services required from the 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. Proposal Preparation Cost Proposal preparation costs are not allowed as a direct charge to this contract.

c. Lists, Examples, Organizational Charts, etc.

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

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

2.0. ISC SCOPE

Unless otherwise stated, “Contractor” refers to the ISC Contractor and their subcontractors. All references to other contractors will be specifically stated (e.g. Subsystem Contractors).

2.1. Overall Contract Scope

The main function of the ISC is to augment Government resources for ICBM WS Systems Engineering and Integration (SE&I).

2.1.1. The Contractor shall support effective and responsive SE&I throughout the life cycles of ICBM WSs 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, Digital Engineering, finance, integration, mission effectiveness, Nuclear Surety, Program Management, research, risk management, science, strategy development, sustaining engineering, Systems Engineering (SE), system safety and security, technical assessment, etc.

2.1.2. The Contractor shall provide SE&I services. The SE 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.3. The Contractor is responsible for providing solutions that directly support the Government’s mission in terms of cost, schedule, performance, and risk.

2.1.4. The Contractor shall support the Government’s strategic priorities. These include increasing operational credibility, strengthening partnerships, optimizing resources, implementing effective governance, and operating with deep knowledge, extreme tenacity, and radical teaming.

2.1.5. The Contractor shall provide continuous yet flexible support in accordance with (IAW) the Government’s prioritization/reprioritization of requirements. 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.6. The dynamic nature of both ICBM WSs requires unique and diverse support while synergistically utilizing cross-cutting support.

2.1.6.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.6.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.7. 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, integration products across all Task Orders, a holistic sight picture, status and trend analysis of the WSs, strategic communication products (roadmap, point papers, position papers, inputs to Higher Headquarters (HHQ) and congressional inquiries, etc.), predictive analysis, Return on Investment (ROI)/sustainment activity analysis, recommendations to complement the Government’s organic resources in accomplishing its mission, etc. See paragraph

3.12 of this document for details on data deliverable requirements.

2.2. MMIII Scope

The MMIII SPO mission is to develop, acquire, modify, and sustain the nation’s MMIII nuclear deterrent force. The MMIII is in the Operation and Support Phase of its life cycle. The MMIII 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.

This is accomplished using both sustainment and acquisition programs.

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. WS 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

• Identification (ID) of potential problems/problem areas

• 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 Air Force Materiel Command (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 WS 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. Sustaining Engineering includes all associated efforts (e.g. engineering and technical data, modeling, simulation, testing, etc.) 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 ISC 2.0 for the MMIII SPO is to ensure any modifications or changes to the system will maintain or improve system-level performance. Successful accomplishment of this goal will require processes such as:

• WS 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 shall consist of working alongside the Government to continually assess operational performance, determine and report current performance capabilities of the MMIII WS 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 ID techniques

2.2.5. Corrective Actions

2.2.5.1. Integrated Product Teams (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.2.7. MMIII Acquisition Programs

Because they are based on mission requirements, acquisition programs can be initiated, postponed, modified, or cancelled at any time.

2.2.7.1. The Contractor shall provide support to Government acquisition teams in meeting program cost, schedule, technical, and performance objectives throughout the acquisition phases of programs.

2.2.7.2. The Contractor shall support acquisition planning and execution of acquisition phase activities consistent with Department of Defense (DoD) 5000 series directives, applicable Air Force Instructions (AFIs), and any other laws and regulations relevant to Acquisition Category (ACAT) acquisition and sustainment programs.

2.2.7.3. In the event of initiation or cancellation of acquisition programs, the Contractor shall adjust the level of support according to Government need.

2.3. GBSD Scope

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

(U) The GBSD acquisition program is a total system recapitalization for the MMIII ICBM 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). 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.

(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 and Technology (S&T) Studies, Demonstration and Validation, and S&T Roadmaps.

2.3.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. 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. Functional Offices Scope

Functional Offices provide policy, governance, organization, training, and functional support in both SPOs.

2.4.1. The Contractor shall provide the necessary support for the Government to successfully provide policy, governance, organization, training and functional support in both SPOs.

2.4.2. The Contractor shall provide expertise representing the major areas of Sustainment, Acquisition, and 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.0. SUPPPORT REQUIREMENTS

3.1. Applicability

All requirements in this Basic PWS apply to all Task Orders, unless specifically waived by the Government Procuring Contracting Officer (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 all applicable laws, regulations, directives, policies, operating instructions, and other applicable publications.

3.3.2. The Contractor shall acquire and follow current versions of laws, regulations, directives, policies, operating instructions, and other applicable publications, unless specifically directed otherwise. Publications listed in this and any Task Order PWS are current as of the writing of the PWS, but are subject to change at any time.

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. General

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

3.4.2. The Contractor shall support effective and responsive integration throughout the life cycles of ICBM WSs.

3.4.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 life cycle of ICBM WSs, as detailed in individual Task Orders.

3.4.4. The Contractor shall maintain awareness of progress, technical issues, and status of ICBM programs and efforts to ensure integration with the WSs and smooth transition to follow-on life cycle phases.

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

3.4.6. The Contractor shall augment and fill knowledge/expertise gaps on Source Selection Evaluation Boards (SSEBs) as needed by specific programs/efforts.

3.4.6.1. The Contractor shall participate in Source Selections and related activities as non-decision-making advisors.

3.4.6.2. All Source Selection support shall be IAW current DoD Source Selection procedures and the Federal Acquisition Regulation (FAR) as supplemented.

3.4.7. The Contractor shall maintain an integrated sight picture of the WSs, including all acquisition and sustainment activities, and perform predictive analysis to determine where additional Government attention is required.

3.4.8. The Contractor shall develop products that effectively communicate WS status and identify what is needed to meet requirements and any support required from outside the SPOs.

3.5. Weapon System Sustainment Requirements

3.5.1. The Contractor shall provide resources and perform tasks to support the

Government in sustaining the MMIII WS, IAW applicable Task Orders.

3.6. Acquisition Program Requirements (MMIII and GBSD Enterprise)

3.6.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 WSs, IAW applicable Task Orders.

3.7. Specialty Engineering and Technical Support Requirements

3.7.1. The Contractor shall provide resources and perform tasks to support the

Government in their mission to provide specialty engineering and technical support to MMIII acquisition and sustainment programs/projects as well as select functional areas of support to GBSD.

3.7.2. This support shall span both SPO organizations and associated Task Orders.

3.7.3. The Contractor shall support the ICBM Data Management Office (DMO) in areas such as Data Management, Configuration Management, interface control, SE, Risk Management, Technical Order Management Agency (TOMA) support, Model Based Systems Engineering (MBSE), Diminishing Manufacturing Sources and Material Shortages (DMSMS), etc., IAW applicable Task Orders.

3.7.4. The Contractor shall support ICBM Specialty Engineering as detailed in applicable Task Orders, including support for Nuclear Surety, Nuclear Certification, Nuclear Hardness and Survivability, System Safety, Corrosion Prevention and Materials Engineering, Environmental Engineering, System Security, etc.

3.7.5. The Contractor shall support ICBM Test and Assessment as detailed in applicable Task Orders, including operational test launch, operational flight testing, WS assessment, modeling and simulation, test management, the Strategic Missile Integration Complex (SMIC), etc.

3.7.6. The Contractor shall support the ICBM Alternate Lead Developmental Test Organization (Alt-LDTO) IAW applicable Task Orders.

3.8. Functional Support Requirements

3.8.1. The Contractor shall provide resources and perform tasks to support the

Government in providing policy, governance, and functional support in both SPOs, IAW applicable Task Orders.

3.8.2. The Contractor shall support ICBM Engineering IAW applicable Task Orders.

3.8.3. The Contractor shall support ICBM Financial Management (FM) IAW applicable

Task Orders.

3.8.4. The Contractor shall support ICBM Product Support and Transition IAW applicable

Task Orders.

3.8.5. The Contractor shall support ICBM Portfolio Management IAW applicable Task

Orders.

3.8.6. The Contractor shall support ICBM Information Technology (IT) and Cybersecurity

IAW applicable Task Orders.

3.8.7. The Contractor shall support the ICBM Lead Project Office IAW applicable Task

Orders.

3.8.8. The Contractor shall support ICBM Force Development Evaluation (FDE) IAW applicable Task Orders.

3.8.9. The Contractor shall support ICBM scheduling IAW applicable Task Orders.

3.8.10. The Contractor shall support MMIII Demilitarization (DEMIL) and disposal IAW applicable Task Orders.

3.8.11. The Contractor shall support ICBM Operations Management IAW applicable Task Orders.

3.8.12. The Contractor shall support ICBM Security IAW applicable Task Orders.

3.9. Meetings

3.9.1. Appropriate functional Contractor personnel shall participate in, contribute to, and provide technical and programmatic expertise for meetings, reviews, and boards.

Meeting examples:

• Conferences

• Depot Repair Enhancement/

Performance Quality Increase (PQI) Activities

• Engineering meetings

• IPT Meetings

• Integrated Test Team Meetings (ITT)

• Team meetings

• Management meetings

• Provisioning meetings

• Technical Interchange Meetings

• Working group meetings

• Etc.

Program and Technical Review examples:

• Deficiency Reviews

• Integrated Baseline Reviews

• Life Cycle Management Reviews

• Modification Design Reviews

• Physical Configuration Audit

• Program Management Reviews

• Program Reviews

• Program Technical Reviews

• Technical Design Reviews

• Technical Reviews

• Test Readiness Review

• Etc.

Board examples:

• Acquisition Oversight Boards

• Baseline Control Boards

• Configuration Control Boards

• Configuration Management Boards

• Guidance Review Boards

• Risk Management Boards

• Safety Review Board (SRB)

• Technical Evaluation Review

Boards

• Technical Review Boards

• Etc.

3.9.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.). (Contract Data Requirements List [CDRL] A002)

3.9.3. The Contractor shall develop and provide presentation materials. (CDRL A003)

3.9.4. The Contractor shall capture, coordinate, and distribute minutes when applicable.

(CDRL A004)

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

(CDRL A059-73)

3.9.6. The Contractor shall present/brief on behalf of the assigned program when needed.

3.9.7. The Contractor shall develop, provide, and maintain team charters when applicable.

(CDRL A059-5)

3.10. Travel/Temporary Duty (TDY)

3.10.1. The Contractor shall travel in support of this effort, based on requirements in individual Task Orders.

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

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

3.10.4. The Contractor shall obtain written approval for travel requirements prior to costs being incurred, from the designated Government program/effort lead. The Government is under no obligation to reimburse the Contractor for any travel in which prior written approval has not been received.

3.10.4.1. At the Government’s request, the Contractor shall prepare and submit to the Contracting Officer Representative (COR) or Government designee, a Travel Approval Request (TAR) for Continental United States (US) (CONUS)/Outside the CONUS (OCONUS) travel prior to traveling.

(CDRL A059-71)

3.10.4.1.1. A Letter of Authorization (LOA) is required in addition to a

TAR for Contractor employees to travel on military aircraft.

(CDRL A059-117)

3.10.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 PCO for approval.

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

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

3.10.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.10.8. Total travel expenses shall not exceed the travel dollars estimated/funded in the respective Task Order Contract Line Item Number (CLIN).

3.10.9. Travel to/from the Contractor’s work facility and primary Government work facility is not considered TDY travel under this contract.

3.11. Knowledge Transfer

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

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

3.11.2. Contractor Subject Matter Experts (SMEs) shall mentor SPO personnel and facilitate the sharing of ICBM-related knowledge between Contractor and SPO personnel.

3.12. Data Deliverables (Contract Data Requirements Lists [CDRLs]) A master list of potential DoD Form 1423s (DD 1423s), Contract Data Requirements Lists, is provided as Section J Attachment 6, Contract Data Requirements Lists (CDRLs).

Due to the quantity and diversity of the programs in the ICBM Organization, the type and magnitude of required support is different for each program. Each program will employ the tasks in the PWSs to the extent needed by that program. This also means that needs for data deliverables will vary based on the program. To this end, CDRLs are not referenced in the PWSs after every paragraph in which they may be required.

CDRLs specifically referenced in the PWSs are to be delivered every time the task required by the referenced paragraph is performed (e.g. monthly status reports, training materials, specialty engineering documentation, etc.).

If a program determines that a formal data deliverable is needed for a paragraph without a CDRL reference (e.g. advice, recommendations, analysis reports, etc.), the Government representative will select the appropriate CDRL from the master list and specify the delivery date/address and any other necessary instructions on the DD 1423. Any additional tailoring will also be documented on the DD 1423 at that time. The CDRL will then be incorporated into the associated task assignment (see paragraph 4.9 of this document).

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

3.12.2. Scientific and Technical Information (STINFO)

DoDI 5230.24, Distribution Statements on Technical Documents, Enclosure 4, Table 5, identifies six (6) authorized distribution statements for STINFO. The Controlling DoD Office (CDO) will review all technical data (e.g. technical reports, test reports, final summaries, briefings, etc.) prior to finalization to ensure the correct STINFO markings (i.e.

distribution statement, export control warning (if applicable), and destruction notice) are applied to all documents.

Note: A distribution statement designation is distinct from, and in addition to, a security classification marking applied IAW DoD Manual (DoDM) 5200.01, Volume 2, DoD Information Security Program: Marking of Classified Information.

3.12.2.1. The Contractor shall mark all technical data, regardless of media or form, with appropriate STINFO markings (i.e. distribution statement, export control warning (if applicable), and destruction notice) as specified on the

CDRL.

3.12.2.2. For written or printed material, the STINFO markings shall appear in full text on the front cover/title page and the abbreviated markings shall appear on subsequent pages as specified in the CDRL.

3.12.2.3. Distribution statements shall include all applicable “reasons” based on the contents of the document.

3.12.2.4. The “date of determination” within each distribution statement shall reflect the date of the document, unless otherwise agreed to upon contract award.

3.13. Records

3.13.1. The Contractor shall create, maintain, and dispose of records that are specifically cited in this and Task Order PWSs, applicable to the work accomplished under this and Task Order PWSs, or required by the provisions of applicable publications and forms.

3.13.2. If requested by the Government, the Contractor shall provide the original record or a reproducible copy of any such record within five (5) working days of receipt of the request.

3.14. Access to Contractor Information

3.14.1. The Contractor shall maintain and store internally-generated data, databases, files, presentation material, etc.

3.14.2. The Contractor shall permit Government access to all information and documentation created in performance of this contract.

3.14.3. At any time and per the Government request, any records, documents, and associated papers shall be available for review or transfer to the Government.

3.14.4. All documentation, programs, tools, databases, records, information, etc. created in performance of this contract shall be transferred to the Government upon completion of the contract, IAW the CDRLs.

3.15. Government Rights in Data and Software (GRIDS) (Section J Attachment 7) In order to continue to execute the ICBM mission beyond the Period of Performance (PoP) of this contract, the Government must have appropriate rights for required data and software.

IAW Defense FAR Supplement (DFARS) 252.227-7013, the Government retains unlimited rights to all data and deliverables developed solely at Government expense.

3.15.1. Rights to data and deliverables not developed solely at Government expense, shall be IAW the GRIDS document.

3.16. Rehabilitation Act Compliance (Section 508)

Section 508 of the Rehabilitation Act of 1973, as amended (29 United States Code (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.16.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 Code of Federal Regulations (CFR) part 1194).

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

3.17. Other Direct Costs (ODCs)

3.17.1. The Contractor shall obtain written approval for ODCs prior to costs being incurred, from the designated Government program/effort lead. The Government is under no obligation to reimburse the Contractor for any ODC in which prior written approval has not been received.

4.0. STAFFING REQUIREMENTS

4.1. All Contractor personnel shall be citizens of the United States of America.

4.2. Personnel/Resource Management

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

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

4.2.3. A Contractor Program Office to administer the ISC 2.0 shall not be a direct cost to the Government.

4.3. Labor Categories and Qualifications

A comprehensive list of labor categories potentially required during the PoP of ISC 2.0 is provided as Section J Attachment 4, Labor Categories and Qualifications. The labor category table defines the education and experience required for each labor category. These qualification requirements are considered by the Government to be the minimum qualifications required for the workforce to be capable of performing the technical requirements of the contract. Also provided in the table are examples of Knowledge, Skills, and Abilities (KSAs) and duties/ responsibilities for each labor category. 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.

If applicable, any additional qualifications required for personnel associated with a specific Task Order will be included in the body of that Task Order’s PWSs.

Exceptions to the stated minimum qualifications will be considered on a case-by-case basis.

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. In the event that Government-unique training is necessary, training may be charged directly to a respective CLIN provided that PCO approval is obtained prior to the training.

4.3.1. The Contractor shall recruit and hire personnel who are qualified IAW Section J Attachment 4, Labor Categories and Qualifications, and any Task Order-specific requirements.

4.3.2. Any experience/education qualifications shall be related to the functional area.

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

4.3.4. The Contractor shall ensure personnel are fully trained and possess any required specialized skills/knowledge prior to beginning work for the Government.

4.3.5. Contracted employees shall demonstrate progressive experience within the minimum qualification determination years. “Progressive” is defined as moving forward and proceeding in a career course.

4.3.6. The Contractor shall ensure personnel maintain proficiency and keep up to date on new and evolving concepts, technologies, processes, etc. related to their labor categories/specialties.

4.4. Labor Quantity Workbook (LQW) (Section J Attachment 3)

The LQW in Section J Attachment 3 states the Government requirement for quantities (in man-years) of each labor category for the first five (5) Task Orders, along with location and security clearance requirements for each. At contract award, the master LQW will be split and the applicable tabs will become attachments to the appropriate Task Order PWS. Future Task Order PWSs will each have an LQW stating the Government’s manning requirement for that Task Order. All labor quantity requirements are contingent upon availability of Government funds.

4.4.1. The Contractor shall provide the number of Full-Time Equivalents (FTEs) and Contractor Manpower Equivalents (CMEs) required by each Task Order, contingent upon Government funds availability.

For purposes of this contract, “FTE” and “CME” are defined as follows:

• “FTE” is defined as a Contractor employee dedicated to a specific labor category position and assigned to a specific effort (non-interchangeable). FTEs are based on 1880 hours annually.

• “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.

4.4.2. The work to be performed under this contract shall be performed at “Government-site”, “Contractor-site-on-base”, and “Contractor-site-off-base”, as required in the LQW for each Task Order.

4.4.2.1. Contractor-site-off-base shall be within the local vicinity. “Local vicinity” is defined as within ten (10) minutes travel time from the work location to a Hill AFB entry gate.

The Government reserves the right to adjust Contractor location requirements as needed during the contract PoP. This will be accomplished through bilateral modifications, using the established rates.

4.4.3. The Contractor shall ensure personnel have the required security clearance/ trustworthiness determination prior to beginning work for the Government.

4.5. Contractor Behavior

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

ICBM Organization, the United States Air Force (AF), the DoD, and the Federal Government, IAW governing laws and regulations.

4.5.2. Contractor behavior shall be professional and reflect positively on the Government.

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

4.5.4. The Contractor shall foster and maintain good working relationships with internal and external stakeholders.

4.5.5. The Contractor shall collaborate with internal and external stakeholders as needed to accomplish requirements and tasks.

4.6. Workforce Adaptability

4.6.1. Contractor personnel shall work alongside Government personnel as part of a team and may be required to act on behalf of the Government (see paragraph 4.8 below for restrictions).

4.6.2. The Contractor shall ensure consistent, quality support throughout any priority or program transitions.

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

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

4.6.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.

4.7. Workforce Stability

4.7.1. The Contractor shall provide uninterrupted, quality support and continuity of capability.

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

4.7.3. The Contractor shall ensure continuation of services during temporary 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.

4.7.4. The Contractor shall provide a qualified, long-term replacement within 45 calendar days from the date of any vacancy.

4.7.4.1. If a replacement cannot be provided within 45 calendar days from the date of vacancy, the Contractor shall notify the PCO and provide a corrective plan as soon as the issue becomes known. (CDRL A012) The PCO may issue a Corrective Action Report (CAR) as defined in paragraph 6.4 of this document.

4.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. (CDRL A059-3) The PCO will evaluate the rationale and make a determination.

4.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 PCO.

4.7.5.1. The Contractor shall ensure continuation of services with existing staff and provide a qualified replacement within 45 calendar days, at no additional cost to the Government.

4.8. 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 defined in FAR 7.503 and Office of Federal Procurement Policy (OFPP) Policy Letter 11–01, Performance of Inherently Governmental and Critical 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.

4.8.1. The Contractor shall NOT perform Inherently Governmental Functions as defined in FAR 7.503 and OFPP Policy Letter 11–01.

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

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

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

4.9. Non-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.

4.9.1. The Contractor shall manage its own employees and guard against any actions that constitute or resemble personal services (see FAR 37.104).

4.9.2. The Contractor shall notify the PCO 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.

4.9.3. Required tasks/work will be tasked through a Contractor Tasking Point (CTP).

4.9.3.1. The Contractor shall designate all FTE positions as CTPs.

4.9.3.2. The CTP shall be responsible for seeing that Government-assigned tasks are appropriately recorded and tracked in the designated task tracking system and IAW the task tracking process.

4.9.3.3. The designated task tracking system and process shall be negotiated and finalized during the transition period from ISC 1.0 to ISC 2.0.

4.9.3.4. CME positions are not required to be designated as CTPs. As such, CME positions will receive taskings through the task tracking system and IAW the task tracking process.

Note: The establishment of a task tracking process/system will be a task that counts towards the Award Fee for the first Award Fee period. The number of open tasks needing transition will be taken into account in the first Award Fee period.

4.10. Other Contracted Support

The ICBM Organization manages many contract actions to facilitate mission execution.

Prime contracts for acquisition programs are responsible for design, development, production, etc. of solutions to meet the requirements of the program.

MMIII Subsystem Support Contracts (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 contracted support includes Federally Funded Research and Development Centers (FFRDCs), University Affiliated Research Centers (UARCs), software Independent Validation and Verification (IV&V), program-specific support contracts, etc.

4.10.1. The Contractor shall foster and maintain good working relationships with other contracted personnel supporting the ICBM SPOs.

4.10.2. The Contractor shall coordinate and collaborate with other contractors as needed to accomplish requirements and tasks.

4.10.3. The Contractor shall assist the Government in integrating and incorporating (if applicable) inputs/information/deliverables received from other contractors.

4.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 ICBM Organization. NDAs are required to facilitate this open communication and appropriately protect information. Violation of an NDA is considered a major security violation.

4.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.

4.11.2. The Contractor shall provide a copy of each NDA to the PCO. (CDRL A115)

4.12. Associate Contractor Agreements (ACAs)

4.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.

4.12.2. All costs associated with ACAs shall be included in the negotiated cost of this contract.

4.12.3. A copy of any such agreements shall be provided to the PCO for review before execution by the cooperating contractors. (CDRL A059-118)

4.12.4. ACAs may be amended as required by the Government during the performance of this contract.

4.12.5. ACAs shall ensure the greatest degree of cooperation to meet the terms of the contract.

4.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 Government contracts and the ACA, including agreements on protection of proprietary data and employee restrictions

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

4.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.

4.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 (SSI) (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 the objectiveness of all ISC Contractor recommendations to the Government and create a cooperative relationship for the integration of SSC and other contract efforts.

ISC support work required by the Government for the SMIC, limited to sustainment of specialized test equipment, is excluded from these restrictions. (New capabilities for specialized test equipment are the responsibilities of the SSC Contractors.)

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

4.13.2. The Contractor shall promptly submit a plan to the PCO to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be accepted solely at the discretion of the Government PCO. In the event the PCO unilaterally determines that an OCI cannot be satisfactorily avoided or mitigated, the PCO may affect other remedies as deemed necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI. (CDRL A008-1)

4.13.3. OCI restrictions apply to all team members (Primes, Subcontractors, Joint Venture Members, etc.).

4.14. Contractor Manpower Reporting

4.14.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 (MSRs), expenditure reports, invoices, proposals, limitation of…