ATSSI_PWS_Final_11.2.16.pdf

1 | P a g e

PERFORMANCE WORK STATEMENT (PWS)

FOR

AUTOMATED TEST SYSTEM SUSTAINMENT INITIATIVE (ATSSI)

INTEGRATED COMPUTER SYSTEM SOLUTIONS

Supportive of OO-ALC 309th EMXG

2 November 2016

2 | P a g e

INTRODUCTION

PURPOSE

SCOPE

BACKGROUND

REFERENCE DOCUMENTS

BASIC SERVICES

ATSSI INITIATIVE

3.1.1 DEVELOP EMXG ATSSI INTEGRATED MASTER PLAN (IMP)

3.1.1.1 REQUIREMENTS BASELINE AND PRELIMINARY ATSSI DESIGN

3.1.1.2 DESIGN AND DEVELOPMENT

3.1.1.3 PROGRAM MANAGEMENT PLAN

3.1.1.3.1 Program Management Support

3.1.1.4 QUALITY SYSTEM

3.1.2 ATSSI IMPLEMENTATION

3.1.2.1 Task Orders

3.1.2.2 System Engineering – Design/ Build/Test

3.1.2.3 System Engineering – Formal Qualification Testing (FQT)

3.1.2.4 Technical Reports

3.1.2.5 Engineering Trade Studies

3.1.3 PROCESS AND CONTROLS

3.1.4 IT-BASED SUPPORT EQUIPMENT RECOMMENDATION DATA (SERD) DEVELOPMENT

3.1.4.1 Support Equipment Recommendation Data (SERD)

INFRASTRUCTURE SUPPORT SERVICES

3.2.1 Task Orders

3.2.2 Infrastructure Support Services

LOGISTICS GUIDANCE CONFERENCES AND REVIEWS

SYSTEM DOCUMENTATION

3.4.1 Direction for System Documentation

3.4.2 Technical Documentation

3.4.3 Government Approval

3.4.4 Structured Generalized Markup Language (SGML)

3.4.5 Monthly Status Report

3.4.6 Engineering Drawings

DATA

3 | P a g e

3.5.1 Contract Data Requirement List (CDRL)

3.5.2 ATE/TPS Technical Data

Diminishing Manufacturing Sources and Material Shortages (DMSMS)

SERVICES SUMMARY

PERIOD OF PERFORMANCE

SERVICE SUMMARY

GENERAL INFORMATION

GOVERNMENT FURNISHED PROPERTY

5.1.1 Government Furnished Information (GFI)

5.1.2 Government Furnished Equipment (GFE)

Data Rights

Data Management

Disclosure of Information

Government Inspection and Acceptance of Deliverables

Access to Facilities and Property

Security

5.7.1 Clearances

5.7.2 Computer Network

5.7.3 Common Access Cards

5.7.4 Classifications

HOURS OF OPERATION

CONSERVATION OF UTILITIES

GOVERNMENT PROGRAM AND CONTRACT MANAGEMENT

5.10.1 Government Representative (GR) Program Management

5.10.2 Government Contract Management

5.10.3 Potential Contract Changes

5.10.4 Contract Review

TRAVEL REQUIREMENTS (Cost Reimbursable)

QUALITY CONTROL

QUALITY ASSURANCE

SAFETY PROGRAM

ENVIRONMENTAL CONTROLS

MANPOWER REPORTING

CONTINUATION OF ESSENTIAL SERVICES DURING CRISIS

4 | P a g e

INSTALLATION SAFETY AND HEATLH STANDARDS

5.18.1 Voluntary Protection Program

Utilization of Small Business

5.19.1 Small Business Participation Requirements

Transition Support

5.20.1 Phase-In Transition Plan

5.20.2 Phase-Out Transition Plan

APPENDICES

APPENDIX A - List of Acronyms

APPENDIX B - Summary of Deliverables

APPENDIX C

5 | P a g e

INTRODUCTION

PURPOSE

The purpose of this effort is to develop and implement an Information Technology (IT) infrastructure supportive of the OO-ALC mission to perform critical test functions important to the ongoing operational safety, suitability, and effectiveness of multiple Air Force weapon systems/subsystems. The resulting IT infrastructure shall be referred to as the Automated Test System Sustainment Initiative (ATSSI). The ATSSI infrastructure solution will provide for the integration, update, and consolidation of computer-based test stations (i.e., ATS), test fixtures, Test

Program Sets (TPSs), database repositories, analytical software tools, and associated network communication functions. Additionally, the EMXG ATSSI will resolve current system obsolescence and performance issues while providing significant efficiency and cost improvements.

SCOPE

The scope of this PWS includes the development and implementation of a Government approved Sustainment

Initiative (SI) providing an IT based infrastructure comprised of computer-based test stations, test fixtures, TPSs, database repositories, analytical software tools, and network communications. There are no Advisory and

Assistance Services (A&AS) associated with this effort. Specific aspects of the scope of work include:

Development of the EMXG ATSSI Integrated Master Plan (IMP), specifically documenting: 1) ATSSI

Requirements, 2) “The Existing SI Model”, 3) “The Planned SI Model”, and 4) An Integrated Master

Schedule (IMS). (CDRL A/B017 or contractor format)

EMXG ATSSI Implementation (i.e., IT infrastructure design, build, and test)

Infrastructure Support Services necessary to sustain existing and planned IT infrastructures during the period of EMXG ATSSI implementation

System Documentation necessary to ensure ATSSI sustainability

BACKGROUND

Each individual piece of test equipment located in EMXG can support end items from several different vendors

(sometimes dozens of vendors), incorporates ancillary equipment from various vendors in its build/design, and requires coordination with multiple vendors when such systems are modified or replaced. Computer-based test stations are generally referred to by EMXG as Automated Test Systems (ATS).

309 EMXG is facing operation, maintenance, performance, and infrastructure support issues for a growing number of computer-based test stations. Many of these systems are obsolete, stove-piped (i.e., not properly interfaced for efficiency purposes), duplicative, require unique/costly repair solutions, and/or require specialized sustainment in order to remain operable. 309 EMXG has established the ATSSI to integrate, update, and consolidate ATS, test fixtures, TPS, database repositories, analytical software tools, and network infrastructures.

The planned objective being to implement an integrated Sustainment Initiative (SI) based on common

Commercial-off-the-Shelf (COTS) and/or Government-off-the-Shelf (GOTS) solutions, whenever possible. 309

EMXG does not have the organic personnel resources necessary to design, develop, and implement ATSSI.

REFERENCE DOCUMENTS

Documents and electronic files will be made available to the Contractor as needed, based on distribution statements. The Contractor will have access to Government offices, computer-based test stations, database repositories, analytical software tools, networks, and facilities in accordance with Sections 5.0 of this PWS.

Consequently, all required reference documentation will be readily available for use during the performance of assigned tasks.

6 | P a g e

BASIC SERVICES

The Contractor shall develop, implement, and maintain a critical IT infrastructure necessary to support computer-based test stations supportive of OO-ALC 309th EMXG requirements as specified in Task Orders. The resulting

IT infrastructure shall be referred to as the “EMXG ATSSI” (or “ATSSI”). The Support Equipment (SE) and TPS identification process in support of this work statement for obtaining common or peculiar support equipment or modifications to existing support equipment shall be IAW GEIA-STD-0007. New ATE, if developed in support of this effort shall meet the requirements of MIL-PRF-28800F, which will be tailored and provided at a task order level.

Kick-Off Meeting Unless otherwise instructed by the Contracting Officer (CO) or Contracting Officer Representative

(COR) the contractor shall participate in a Government-scheduled, Kick-Off Meeting after contract award. Key prime contractor personnel shall participate in the Kick-Off Meeting. The purpose of the Kick-Off Meeting is to:

1. Aid both the Government and contractor personnel in achieving a clear and mutual understanding of all requirements, and

2. Identify and resolve potential problems.

The contractor shall be prepared to discuss any Task requirements requiring clarification. The Government, with mutual input from the contractor, will schedule the Kick-Off Meeting to be conducted within forty-five (45) days after contract award.

The contractor shall prepare a tentative agenda for the Kick-Off Meeting and submit this agenda to the Government

Representative (GR), CO, and COR within thirty (30) days of contract award. (CDRL A/B002)

ATSSI INITIATIVE

3.1.1 DEVELOP EMXG ATSSI INTEGRATED MASTER PLAN (IMP)

The Contractor shall develop an Integrated Master Plan (IMP) specifically documenting: 1) ATSSI Requirements,

2) “The Existing SI Model”, 3) “The Planned SI Model”, and 4) An Integrated Master Schedule (IMS). The

Integrated Program Management Report (IMPR) shall be submitted to the GR thirty (30) working days after Kick-

Off Meeting (Section 3.0) and updates thirty (30) working days after new task award (CDRL A/B014, A/B017 or contractor format).

ATSSI Requirements:

a) ATSSI requirements shall be coordinated with EMXG and weapon system stakeholders.

b) Documented Requirements shall provide the basis from which the EMXG ATSSI is designed and developed (ref para 3.1.2).

c) Requirements shall be drafted in such a manner that they can be later used in support of Formal

Qualification Testing (FQT) of ATSSI systems/subsystems (ref para 3.1.2).

d) Trade-offs and analyses shall be performed by the Contractor to determine the technical feasibility, cost, and benefit of various ATSSI design alternatives. The results of Trade-offs and Analyses shall be documented within the Monthly Status Report (MSR) (CDRL A/B001).

e) Documented System Requirements shall include, but not be limited to:

i. Standardization, consolidation, and integration of computer hardware, software, database repositories, analytical software, and network solutions to minimize the cost of system implementation and long-term sustainment.

ii. Significant system flexibility and scalability to meet dynamic ATSSI requirements over a period of 10 years or more.

7 | P a g e

iii. Stakeholder access to computer-based test data via database repository and network solutions;

providing analytical software tools as appropriate (CDRL A/B020, A/B021, A/B022 and

A/B023)

f) System Engineering – The Contractor shall follow a system engineering process defined and documented, at a minimum, by an ISO 9001, or equivalent, compliant process. This process shall adhere to the technical processes identified in the DoDI 5000.02, Enclosure 3 (System Engineering).

These processes are designed for much larger scale projects, so it must be tailored to fit smaller efforts, such as TPS developments and projects similar to the Air Data Computer Task Order (ADCTO) identified for this proposal. The contractor’s process, as applicable to TPS development which will be utilized by the contractor for this effort, shall be submitted in detail and evaluated in conjunction with the ADCTO. (CDRL A/B014)

The Integrated Master Schedule (IMS) shall be developed through coordination with 309 EMXG and shall represent the schedule and resources necessary to transition from “The Existing SI Model” to “The Planned SI

Model” in a step-wise and logical manner. (CDRL A/B017 or contractor format)

3.1.1.1 REQUIREMENTS BASELINE AND PRELIMINARY ATSSI DESIGN

Completion of the Government approved IMP will represent the formal Requirements Baseline and the

Preliminary ATSSI Design. Consequently, the Contractor shall place the IMP under formal configuration management and shall require Government Stakeholder coordination and approval prior to any future document modifications. IMP updates will be necessary as requirements and design concepts are iteratively assessed throughout contract performance. (CDRL A/B017 or contractor format)

3.1.1.2 DESIGN AND DEVELOPMENT

The contractor shall design and develop all ATE/TPS to meet the performance requirements of MIL-PRF-32070 and MIL-PRF-49503. The software design/development process, as a minimum, shall meet the requirements of the Software Engineering Institute (SEI) Capability Maturity Model Integration (CMMI) Level 2 or an equivalent software design/development process. As noted in Section 3.1.1, (part f) this TPS development process shall be submitted and evaluated as part of the ADCTO. The contractor shall deliver all software in accordance with the

Automated Computer Program Identification Number System (ACPINS) Technical Order (T.O.) 00-5-16. (CDRL

A/B012, A/B016)

3.1.1.3 PROGRAM MANAGEMENT PLAN

The contractor shall develop a Program Management Plan (PMP) in accordance with the documented procedures in their established quality system that details the activities to be performed under this contract. The PMP shall include, but is not limited to, plan purpose, scope, schedule, budget, performance plan, quality plan, risk plan, and any additional support plans required to complete the requirements of this contract. The contractor shall process all changes to the established plan following their documented quality procedures. The contractor shall develop the

PMP within thirty (30) days of contract award and document completion in the appropriate monthly status report.

(CDRL A/B018)

3.1.1.3.1 Program Management Support

The Contractor shall provide Program Management Support for all tasks and task orders associated with this contract. This support shall include, but not be limited to:

Monthly Status Reports (ref para 3.1.1 and para 3.4.5)

Program Management Plan updates (ref para 3.1.1.3)

Project Status Reviews/Technical Interchange Meetings (ref para 3.2.2.g)

8 | P a g e

3.1.1.4 QUALITY SYSTEM

The contractor shall establish, document, and maintain a quality system equivalent to International

Organization for Standardization (ISO) 9001:2008 as a means of ensuring that the requisite quality assurance oversight is exercised in fulfilling the requirements of this contract. The contractor shall ensure that this requirement is levied on any subcontractors used in satisfying the requirements of this contract.

3.1.2 ATSSI IMPLEMENTATION

3.1.2.1 Task Orders

The Contractor will be specifically directed via “Task Order (TO)” regarding each segment of the Integrated

Master Plan (IMP) that is to be implemented and tested. The Contractor shall provide a FFP proposal for each requested segment implementation. (CDRL A/B017 or contractor format)

3.1.2.2 System Engineering – Design/ Build/Test

The Contractor shall prototype areas of technical risk and update IMP design concepts to support an ATSSI Critical

Design Review (CDR). Following Government approval of CDR, the Contractor shall build/implement the approved design. The Contractor shall utilize COTS/GOTS hardware and software solutions to the greatest extent possible. Contractor efforts shall include: system/subsystem development, modification, integration, consolidation, and validation/verification. Affected systems/subsystems include: computer-based test systems (i.e., ATS), Test Program Sets (TPS), database repositories, analysis software, and network infrastructures. (CDRL

A/B009 or contractor format)

3.1.2.3 System Engineering – Formal Qualification Testing (FQT)

The Contractor shall perform Formal Qualification Testing (FQT) for all implemented segments of the IMP. The

Contractor shall develop FQT Test Plans/Test Procedures demonstrating full compliance with ATSSI

Requirements specifically listed within the IMP (ref para 3.1.1.a). The Test Plan/Test Procedures shall be submitted to the GR within five (5) working days prior to government review listed within the IMP. (CDRL

A/B019)

3.1.2.4 Technical Reports

Technical reports required, as stated within Paragraph 3.1.2, shall be submitted to GR and COR within ten (10) working days prior to government review date listed within the IMP. (CDRL A/B014)

3.1.2.5 Engineering Trade Studies

The contractor shall perform engineering trade studies (ref para 3.1.1.d) supporting the following:

• Technology Assessment/Qualification

• Feasibility Analysis

• Alternatives Analysis (including build, buy, upgrade, etc.)

• Cost/Benefit Analysis

• Hardware/Software Consolidation and/or Integration

• Operational Software

• Support Equipment

• Transportation and Material Handling Equipment

• Data Systems and Automated Tools

• Automated Test Equipment (ATE); including Test Sets Test Stations

• Trade Study Reports as required by task order (CDRL A/B014)

9 | P a g e

3.1.3 PROCESS AND CONTROLS

The Contractor shall adhere to industry standards, controlling processes and controls, such as ISO 9001 and

Capability Maturity Model Integration (CMMI) certification, Level 2 or equivalent at a minimum. Configuration control shall also be dictated by industry standard processes and documented in accordance with an ISO 9001 process (or equivalent) which shall be available for review by the GR.

3.1.4 IT-BASED SUPPORT EQUIPMENT RECOMMENDATION DATA (SERD) DEVELOPMENT

The contractor shall develop either a material or non-material test capability for use at 309 EMXG maintenance facilities for the Line Replaceable Unit (LRU) and Shop Replaceable Unit (SRU) identified in each Task Order

(TO). The resultant capability must be compatible with the IT-based ATE and ancillary Support Equipment (SE) currently possessed by that activity. The maximum number of simultaneous test operations is identified in each

TO. The contractor shall, to the maximum extent possible, leverage existing material and non-material solutions to minimize the costs associated during the test capability development. If a material solution is selected, the contractor shall procure or develop, integrate, test and deliver all contractor-provided equipment to enable testing of the LRUs and SRUs identified in the TO. Integration activities shall include, but not be limited to, qualification of parts to correct obsolescence conditions; TPS integration support activities for existing and newly developed members of the IT-based ATE – series of testers, e.g. CBATS; update and delivery of SE technical documentation as required; and update of SERD documentation as required. IAW GEIA-STD-0007 (CDRL A/B026) and (CDRL

A/B008, A/B009 or contractor format).

The contractor shall fabricate the SERD equipment in accordance with best commercial practices and, if desired, is authorized to substitute functionally equivalent commercial parts for military standard and military specification parts identified in the engineering technical data packages. Products shall be provided IAW GEIA-STD-0007

(CDRL A/B026).

3.1.4.1 Support Equipment Recommendation Data (SERD)

Support Equipment SERDs – The Contractor shall prepare and submit SERDs for all recommended Support

Equipment (SE) end items. These SE end items shall include common support equipment, calibration equipment, and special handling gear required for equipment maintenance. The Contractor shall identify all SE end items that require early approval (i.e. prior to acceptance of the maintenance plan) using the Contractor's progress, status and management report. SERD preparation shall be IAW GEIA-STD-0007 (CDRL A/B026).

Support Equipment Selection Criteria – The Contractor shall use the following order of priority in preparing

SE recommendations to promote standardization and nonproliferation of SE.

1. Identify the weapons system’s support/test requirements,

2. Define the various support/test alternatives,

3. Analyze the alternatives, and

4. Select the appropriate ATS support alternative (see below for ATS selection process).

a) Service’s Designated ATS Family

b) DoD Designated ATS Family

c) Commercial tester

d) Current weapon system/Service ATS

e) Other DoD inventory ATS

f) New development AT

5. If existing items are selected, they may not be “free” to the contractor. The contractor might have to procure sufficient quantities to support their TPS design approach.

6. There must be a current data package available to procure the items.

7. The current status of logistics support is a consideration.

10 | P a g e

8. Coordinate these considerations with the government.

ATS Selection Process – In order to avoid any Organizational Conflict of Interest (OCI), the ATS support alternative evaluation and selection will be performed according to the documented process found in DoD ATS

Selection Process Guide (2009), located on the Office of the Under Secretary of Defense for Acquisition, Technology and Logistics web page (http://www.acq.osd.mil/ats/). The Contractor will follow this process utilizing information from the IMP to determine the appropriate ATS Selection and shall submit it to the

Government for approval. Once the Government approves the selection, the Contractor shall then proceed to development (or Subcontracting) of that chosen ATS support alternative.

INFRASTRUCTURE SUPPORT SERVICES

3.2.1 Task Orders

The Contractor will be specifically directed via “Task Order” to provide services needed to support: 1) The

“Existing SI Model” and/or 2) The partially implemented “Planned SI Model”; both of which are documented within the IMP. The Contractor shall provide an FFP proposal for support services specified by individual Task

Order. (CDRL A/B017 or contractor format)

3.2.1.1 Task Order Procedures

Individual Task Order proposals shall follow instructions in each Task Order RFP. The Contractor shall submit the proposal within the time identified in the Task Order RFP, typically 14 calendar days from receipt of Task

Order RFP. However, Task Order RFP response dates may vary depending upon the complexity of the Task

Order, urgency, and end of fiscal year requirements.

3.2.1.1.1 Submission of TO RFP

The contractors shall be requested to submit the Task Order proposal to the issuing office within the period stated in the Task Order RFP which may consist of:

a. Technical Proposal may consist of proposed technical approach/solution, list of required work elements, management approach, key personnel and/or subcontractors, and/or other material submittals.

b. Price Proposal. The price proposal for the Task Order cost.

3.2.2 Infrastructure Support Services

The Contractor shall provide Infrastructure Support Services necessary to sustain “The Existing SI Model” during

EMXG ATSSI Implementation (i.e. para 3.1.2 performance). Additionally, the Contractor shall maintain completed segments of “The Planned SI Model” and assist in the transition of these segments to Government control. Related services shall include:

a) IT infrastructure sustainment services, including the sustainment of computer-based test stations, TPS, database repositories, analytical software tools, and appropriate network systems/subsystems

b) On-the-Job (OJT) training of Government personnel charged with long-term sustainment of associated systems

c) Configuration Management and support of the EMXG ATSSI Configuration Control

d) Systems Management: Including system/subsystem location and status tracking, software license management, maintenance/repair/calibration, remote systems control/monitoring, planned enhancements, service updates, issue tracking and resolution, and appropriate support

e) Development, implementation, and management of security controls required to protect classified or sensitive data resident within ATS, associated database repositories, and/or analytical software systems

11 | P a g e

f) Strategic Planning focused on the achievement of EMXG mission requirements in an environment of dynamic change and limited resources

g) Customer Relationship Management (CRM) supporting the review of alternative technologies, Technical Interchange Meetings (TIMs), In-Progress Reviews (IPRs), and Project Status Reviews

(PSRs) associated with EMXG and other Air Force organizations having similar functions; adapting lessons learned and best practices.

h) To ensure real time status updates for various stakeholders, the Contractor shall utilize a Program

Management Software solution to provide relevant information in a customer friendly format. Such real time information shall include draft and released document delivery, project status, action item status, and project schedule. This software solution shall be provided via a secure website that is accessible to Government stakeholders.

LOGISTICS GUIDANCE CONFERENCES AND REVIEWS.

The Contractor shall participate in Program Reviews and In Process Reviews (IPRs) jointly with the Government to manage the logistics element efforts addressed in this PWS. Program Reviews shall be held informally and at a minimum of one (1) time per quarter to ensure availability of supporting data and personnel. In Process Reviews

(IPRs) of the technical manual shall include engineering to verify procedures, and to the greatest practical extent, schedule logistics meetings to align to program related meetings, such as TRR / PDR / CDR. The contractor shall provide the GR, the Meeting Agenda thirty (30) working days prior to the review/meeting. The contractor shall provide the GR, meeting minutes within ten (10) working days following the review/meeting. The Contractor shall ensure that engineering data used in data development is available. (CDRL A/B002, A/B003)

SYSTEM DOCUMENTATION.

3.4.1 Direction for System Documentation

The Contractor will be specifically directed via “Task Order” to provide required System Documentation. The

Contractor shall provide an FFP proposal for support services specified by individual Task Order.

3.4.2 Technical Documentation

The Contractor shall provide support for the development, update, and management of technical documentation necessary to ensure system sustainability. System documentation shall include specifications, Technical Orders

(T.O.s), Manuals, and/or other documentation as specified by Government Stakeholders. (CDRL A/B010, A/B012, A/B020, A/B021, A/B022 and A/B023)

Reference documents for proper documentation include (but are not limited to):

MIL-DTL-38807D

MIL-DTL-87829

Technical Order (T.O.) 00-5-1

T.O. 00-5-3

T.O. 00-5-16

T.O. 00-5-17

3.4.3 Government Approval

The Contractor shall work with several independent Government agencies to facilitate approval of test solutions to the Air Force, to include documentation approval, calibration process approval, adherence to configuration standards set forth by applicable organizations (to include the Automated Test Standardization Group), and any specific equipment/end item cognizant organizations. Calibration/Measurements Requirements Summary

(CMRS)

12 | P a g e

The Contractor shall provide a Calibration/Measurements Requirements Summary (CMRS), or update to existing

CMRS, where appropriate and as identified in each Task Order. (CDRL A/B013).

3.4.4 Structured Generalized Markup Language (SGML)

Where required by individual organization, the Contractor shall provide the capability to generate documentation in Structured Generalized Markup Language (SGML) format. Where SGML is not required, the Contractor shall deliver documentation in contractor format, according to MIL-PRF-28001/MIL-HDBK-28001. (CDRL A012)

3.4.5 Monthly Status Report

Progress towards the achievement of the above contractual requirements shall be documented and coordinated within the Monthly Status Report (MSR) (CDRL A/B001)

3.4.6 Engineering Drawings

The contractor shall submit prepared engineering drawings and/or associated lists in the designated appropriate format to support systems/subsystems problem resolution when required by 309 EMXG. All engineering drawings generated shall adhere to best commercial practices and shall, at a minimum, follow ASME Y14 standards.

Engineering drawings generated shall be prepared for incorporation in JEDMICS repositories. Products shall be provided IAW (CDRL A/B015) and/or (CDRL A/B006) as applicable.

DATA

3.5.1 Contract Data Requirement List (CDRL)

The contractor shall prepare and submit the documents listed in Appendix B, and media in support of this work effort, and all associated Task Orders in accordance with the CDRL Exhibits cited within the Appendix.

3.5.2 ATE/TPS Technical Data

The contractor shall modify ATE/TPS technical data in accordance with the contractor’s engineering directives, internal drawings and procedures, acceptance test procedures, and other procedures as agreed upon by the contractor and the Government. (CDRL A/B004, A/B005, A/B007, A/B008, A/B009, A/B010, A/B011 and

A/B016)

DIMINISHING MANUFACTURING SOURCES AND MATERIAL SHORTAGES (DMSMS)

The contractor shall provide personnel as needed to support Diminishing Manufacturing Sources and Material

Shortages (DMSMS) resolution of IT-based hardware used to test 309 EMXG managed weapon system components. The contractor shall ensure that personnel assigned to this task are fully knowledgeable of legacy avionics intermediate and depot maintenance level IT- based test equipment and its related support infrastructure requirements. The contractor shall have provided this type of engineering support to the Government within the last

60 months.

The contractor shall research and analyze component provider capabilities to ensure that production of legacy

IT-based test capability equipment can be continued. In the event required component resources cannot be sourced to meet IT-based test capability production requirements, the contractor shall take all actions required to mitigate the production shortfalls. This support shall include, but not be limited to:

Research, identify, analyze, test, and qualify replacement components for use in the production and sustainment of legacy IT-based test capability equipment

Update technical documentation to ensure all replacement components are fully documented

Develop, fabricate, test, and qualify replacement end-items of IT-based test capability equipment if component part mitigation techniques are not viable in ensuring out-year support for the legacy equipment

13 | P a g e

SERVICES SUMMARY

PERIOD OF PERFORMANCE

The Period of Performance will be IAW Section B of the contract.

14 | P a g e

SERVICE SUMMARY

Performance Objective

PWS

Para.

Performance Threshold

Integrated Master Plan (IMP)

3.1.1, 3.1.2 and 3.2

Completed on time and updated to reflect planning changes as they occur

100% of the time (CDRL A/B017 or contractor format)

Monthly Status Report 3.1.1, 3.1.1.3

The report is to be submitted to the GR and COR monthly. 10 working days after the first calendar month after receipt of the delivery order and monthly thereafter (CDRL A/B001).

Test Plan/Procedures 3.1.2.3 5 working days prior to Government Review date listed within the IMP

(CDRL A/B019)

Meeting Agenda 3.3

3.4.6 3 working days prior to conference/ review/meeting (CDRL A/B002)

Meeting Minutes (Minutes and Action Items)

3.3 ASREQ - 10 working days following the event (CDRL A/B003)

Technical Report –

Study/Services (System

Documentation)

3.1.2.4 10 working days after completion of Study/Service (CDRL A/B014)

Calibration and

Measurements Requirements

Summary (CMRS)

3.4.4 15 working days after completion of verification testing (CDRL A/B013)

Product Drawings/Models and Associated Lists

3.4.7 15 working days prior to formal review event (CDRL A/B015)

Program Management Plan 3.1.1.3 30 working days after contract award (CDRL A/B018)

Utilization of Small Business 5.19

Contractor is to show best effort in conducting market research and seeking qualified small business sources as detailed in Para 5.19 to perform at least 10% of the total subcontract value. (CDRL A/B031)

15 | P a g e

GENERAL INFORMATION

GOVERNMENT FURNISHED PROPERTY

Government Furnished Property (GFP), Government Furnished Equipment (GFE), Materials, Government

Furnished Information (GFI), and Software will include full access to existing OO-ALC 309 EMXG ATS, TPS, database repositories, and analytical software as necessary to accomplish contract requirements. All GFP, GFE, Materials, GFI, and Software will be accounted for at the individual task order level. Access will be provided at

Government facilities and will require written authorization prior to removal to the Contractor’s facility.

5.1.1 Government Furnished Information (GFI).

The Contractor shall investigate and identify the need for GFI, to include Technical Orders (T.O.), Test

Requirements Documents (TRD), legacy source code, etc. and shall request such information a minimum of thirty

(30) days prior to need date. The ability of the Government to provide GFI will be dependent on availability of such GFI as well as ability for the Government to release such data. In the instances where the Government cannot release or provide the data to the Contractor, the Contractor shall provide the Government with impacts to the program and mitigation plans for dealing with such lack of data issues.

5.1.2 Government Furnished Equipment (GFE).

The Contractor shall investigate and determine GFE needs and request such GFE a minimum of sixty (60) days prior to need date. The ability of the Government to provide GFE will be dependent on availability of assets and ability of the Government to provide those assets to the Contractor. In the instances where the Government cannot provide or release the GFE to the Contractor, the Contractor shall provide the Government with impacts to the program and mitigation plans for dealing with such lack of GFE.

DATA RIGHTS

The contractor shall provide the government with unlimited purpose rights to all documents, material, engineering and software data produced under this contract. The Government may use, modify, release, reproduce, perform, display or disclose the data pertaining to such items, components, or processes within the Government without restriction but may release or disclose the data outside the Government only for government purposes. All documents and materials, to include the source code of any software produced under this contract shall be government owned and are the property of the government with all rights and privileges of ownership/copyright belonging exclusively to the government. In the event that data rights exceptions my occur during the course of the contract, the Contractor may request restrictions to data rights in accordance with DFARS 252.227 – 7013.

These exceptions will be addressed on a case by case basis and at the task order level.

DATA MANAGEMENT

Contractor personnel shall not release or remove system documentation, data, or reports generated by or through use of Government systems. All requests for information shall be forwarded to the GR.

DISCLOSURE OF INFORMATION

The contractor shall not divulge any information regarding files, data, processing activities/functions, user ID's, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all Government rules, procedures, and standard of conduct.

Contractors requiring access to Government AIS shall have background investigations and security awareness training completed prior to the start of contract performance. When the period of performance is complete and /or contractor personnel leave work on this project they will have 5 days to terminate all their network user accounts and to return all access cards and base identification badges.

16 | P a g e

IAW DFARS 211.106, “Service contracts shall require contractor employees to identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, contracts shall require contractor personnel to appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.”

Non-Disclosure Agreements (NDA) will be required.

GOVERNMENT INSPECTION AND ACCEPTANCE OF DELIVERABLES

The assigned GR will have the right to reject or require correction of any deficiencies found in deliverables. In the event of rejection of any deliverable, the Contractor will be notified in writing by the GR of the specific reasons why the deliverable was rejected. The Contractor shall have thirty (30) working days to correct the rejected deliverable and resubmit to the GR for re-inspection. If no comments are provided within thirty (30) working days of deliverable receipt, the deliverable will be deemed to have been accepted by the Government.

ACCESS TO FACILITIES AND PROPERTY

Access to Government facilities is limited. Therefore, the contractor shall coordinate required access/usage times and dates through the GR at least fifteen (15) days prior to the need date. Control of the facilities shall remain with the Government. The GR will assist contractor in processing the necessary DoD forms to obtain base or area badges for access to government facilities.

The contractor shall comply with all clearance and access requirements throughout the period of performance.

Contractor personnel shall comply with the Air Force facility requirements for personnel identification badges before being allowed access to facilities to accomplish this contract.

To obtain a controlled/restricted area badge, the contracting officer or security manager initiates an AF Form 2586, Unescorted Authorized Entry Certificate, stating what areas are needed. The form is signed by the contracting officer or security manager and designated personnel authorized to sign for specific areas. An original and one copy of the AF Form 2586 are brought to Pass & Registration for badge issuance.

SECURITY

5.7.1 Clearances

A security clearance of SECRET will be required for all personnel having access to classified data. The contractor shall comply with all clearance and access requirements throughout the period of performance. The contractor shall comply with all requirements of the DD Form 254, Department of Defense Contract Security Classification

Specification, attached to this contract.

The DD Form 254 will be required for each individual TO if applicable.

5.7.2 Computer Network

Access to the Hill AFB computer network shall be required to accomplish the requirements of this PWS.

Contractor personnel shall abide by all Government rules, procedures, and standard of conduct. Contractors requiring access to Government Automated Information Systems (AIS) shall have background investigations and security awareness training completed, after task order award but prior to AIS access.

5.7.3 Common Access Cards

In the event a Common Access Card (CAC) is required in support of this effort and the Security Clearance level is expected to be UNCLASSIFIED, the following instructions shall apply. It should be no ted that this process may take a minimum of four (4) weeks to complete; so it is critical that Contractors consider

17 | P a g e these instructions before award and prior to changing contractor personnel after award. The CAC requirements shall be accomplished in accordance with AFFARS clause 5352.242-9001 and Hill AFB

Instruction 36-812.

5.7.4 Classifications

The contractor shall require access to “For Official Use Only (FOUO)” information, access to Program and

Security Classification Guides and have Operations Security (OPSEC) requirements. The Contractor is responsible for subcontractor implementation of the OPSEC requirements for this contract. (CDRL A/B027)

HOURS OF OPERATION

Unless otherwise required by the Government, the contractor shall have access to perform services during the following MST hours: 6:00 AM to 5:00 PM dayshift, Monday through Friday up to Force Protection Condition

(FPCON) Charlie.

Unless otherwise required by the government, the contractor shall not have access to government facilities to work on the following federal holidays: New Year’s Day, Martin Luther King’s Birthday, President’s Day, Memorial

Day, Independence Day, Labor Day, Columbus Day, Veterans’ Day, Thanksgiving Day, and Christmas Day.

If the holiday falls on Sunday, it is observed on Monday. If the holiday falls on Saturday, it is observed on Friday.

CONSERVATION OF UTILITIES

The contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions, which prevent the waste of utilities, which includes the use of Government telephones shall be used only for official government business.

GOVERNMENT PROGRAM AND CONTRACT MANAGEMENT

5.10.1 Government Representative (GR) Program Management

The GR for this effort is defined as the EMXG Lead Process Engineer or alternate. The GR will be assigned to this contract. The assigned GR will provide the contractor access to all technical data required to perform approved tasking. Only the GR has authority to review and approve contract deliverables.

5.10.2 Government Contract Management

Responsibility for contracting activities rests solely with the Government Contracting Officer. No conversation, recommendations, or direction, whether given directly by, or implied by Government personnel, that will affect the contract’s scope, schedule, or price shall be acted upon by the contractor unless specifically approved by the

Government Contracting Officer.

5.10.3 Potential Contract Changes

Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the

Contracting Officer (CO), not to the COR(s).

5.10.4 Contract Review

Services performed by the contractor during the period of this contract are at all times and places subject to review by the CO or authorized representative(s). The GR will evaluate the contractor’s performance through inspections and receipt of complaints from base personnel. The GR may inspect each task as completed or increase the number of quality control inspections if deemed appropriate because of repeated failures discovered during quality control inspections or because of repeated customer complaints

18 | P a g e

TRAVEL REQUIREMENTS (COST REIMBURSABLE)

The contractor may be required to travel to support the objectives of this PWS. In the event travel is required, the contractor shall obtain prior approval from the CO or the COR. Any travel required shall be performed IAW the

Federal Travel Regulations and FAR 31.205-46, Travel Costs. The contractor shall be responsible for making all necessary arrangements for their personnel, including air travel, car rental, lodging and subsistence.

As a minimum, travel shall include, but not be limited to:

Travel as necessary to subcontractor/vendor facilities to perform quality assurance oversight activities and subcontract management.

Travel as necessary to accomplish check-out and/or integration for IT-based equipment and software.

Travel as necessary to attend meetings with Government program management and technical personnel to discuss programmatic and technical issues/status.

QUALITY CONTROL

The contractor shall establish a complete Quality Control Program (QCP) via a Quality Control Plan to ensure the requirements of this contract are provided as specified. The contractor's quality management program shall comply with the minimum quality management systems elements specified in the American National Standards Institute

(ANSI), American Standards Organization (ASO), and International Standard Organization (ISO) family of standards. Quality Control Plan will be in Contractor format. (CDRL A/B024)

QUALITY ASSURANCE

The Contracting Officer Representative is the authorized government representative(s) who will perform assessments of the contractor’s performance. Subsequent to contract award, the identity of the COR(s), with a letter defining duties and authority will be promptly furnished to the contractor

The COR(s) or alternate(s) will inform the task manager in person when discrepancies occur and will request corrective action. The COR(s) or alternate(s) will make a notation of the discrepancy on the assessment checklist with the date and time the discrepancy was noted and will request the task manager (or authorized representative) to initial the entry on the checklist.

Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the

CO.

The services to be performed by the contractor during the period of this contract are at all times and places subject to review by the CO or authorized representative(s).

The Government will periodically evaluate the contractor’s performance by appointing a representative(s) to monitor performance to ensure services are received. The Government representative will evaluate the contractor’s performance through inspections and receipt of complaints from base personnel.

The Government may inspect each task as completed or increase the number of quality control inspections if deemed appropriate because of repeated failures discovered during quality control inspections or because of repeated customer complaints.

SAFETY PROGRAM

The contractor shall implement a safety program that ensures protection of Government personnel and property.

(See Appendix C)

19 | P a g e

As part of the Safety Program the contractor shall establish a Safety Plan and checklist IAW Appendix C of this

PWS, which may be tailored (with Government approval) to meet contractor’s current safety plan. The contractor shall submit the Safety Plan at Contract Award. (CDRL A/B025)

In the event of an accident/mishap, the contractor shall take reasonable and prudent action to establish control of the accident/mishap scene, prevent further damage to persons or property, and preserve evidence. A written or email copy of the accident / incident notification shall be sent within three calendar days to the COR, who will forward it to 309 MXW safety. (CDRL A/B028)

ENVIRONMENTAL CONTROLS

The contractor shall ensure their employees are made aware of the performances of these services will occur in industrial areas. The industrial complex at the ALC has the potential to expose workers to hazardous materials which may include, but is not limited to: hexavalent chrome and others. While the contractor will not perform duties in a regulated area (where exposures are expected to exceed the permissible exposure limits set by 29

CFR11910.10xx), there may be contact hazards with these materials. The contractor shall ensure proper protective measures and training are taken to ensure contracted employees are protected from these hazards.

MANPOWER REPORTING

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for Systems Engineering and Technical Services via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year

(FY), which ruins 1 October through 30 September. While inputs may be recorded anytime during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the

CMRA help desk.

Uses and Safeguarding Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with direct labor hours and direct labor dollars.

At no time will any data be released to the public with the contractor name and contract number associated with the data.

User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link. However, user manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.

CONTINUATION OF ESSENTIAL SERVICES DURING CRISIS

IAW DODI 1100.22 this requirement is not considered mission essential.

INSTALLATION SAFETY AND HEATLH STANDARDS

5.18.1 Voluntary Protection Program

Hill AFB, along with the entire Air Force, has adopted the Voluntary Protection Program (VPP) as recognized by

Occupation Safety Health Association (OSHA). Consequently, VPP impacts all “applicable contractors” operating on Air Force Installations. It is the contractor’s responsibility to ensure its employees and managers have a comprehensive understanding of VPP as well as full compliance with OSHA requirements. Detailed information on VPP is available on the OSHA website (http://www.osha.gov/dcsp/vpp/index.html). Contractors, whether regularly involved in routine site operations or engaged in temporary projects such as construction or repair, must follow the safety and health rules of the installation or VPP site.

VPP requirements apply to contractors whose employees work more than 1,000 hours per quarter. The contractor shall flow down these requirements to all subcontractors who qualify as applicable contractors under this contract.

http://www.ecmra.mil/ http://www.ecmra.mil/ http://www.osha.gov/dcsp/vpp/index.html

20 | P a g e

Contractors are required to provide from their OSHA 300 information the Total Case Incident Rate/Days Away

Restricted or Transferred (TCIR/DART) rate by 15 January of each year to the COR for submission as part of the installation’s annual OSHA VPP self-evaluation report. (CDRL A/B029)

UTILIZATION OF SMALL BUSINESS

The contractor shall be required to make a best effort to meet small business subcontracting goals to include Small

Businesses (SB), Veteran-Owned Small Business (VOSB), Service Disabled Veteran-Owned Small Business

(SDVOSB), HUBZone Small Business (HUBZone), Small Disadvantaged Business (SDB), and with Women

Owned Small Business (WOSB). The contractor shall submit a Small Business Utilization Report to the CO, bi-annually. (CDRL A/B031)

5.19.1 Small Business Participation Requirements

The Government has set a minimum small business subcontracting goal for this effort of 10% of the total subcontracted amount.

Small Disadvantaged Business (SDB) - 5% of total subcontracted amount above

Woman-Owned Small Business - 5% of total subcontracted amount above

Hub-zone - 3% of total subcontracted amount above

Service-Disabled Veteran-Owned Small Business - 3% of total subcontracted amount above

A Small Business Subcontracting Plan will be required in accordance with (IAW) Federal Acquisition Regulation

(FAR) 52-219-9, Small Business Subcontracting Plan.

TRANSITION SUPPORT

The contractor shall develop and execute a Phase-In Transition Plan and a Phase-Out Transition Plan to ensure a smooth and orderly project transition between the contractor and the Government. Transition ensures the incoming prime contractor is afforded the opportunity to develop a thorough understanding of the existing system life-cycle management processes and system requirements; define, implement and receive government concurrence of any new or changed management processes based on the contractor's proposal.

5.20.1 Phase-In Transition Plan

The contractor shall develop a Phase-In Transition Plan that shall facilitate the accomplishment of a seamless transition from the incumbent to an incoming contractor. Phase-In Transition services shall occur after award, starting thirty (30) days prior to responsibility period of performance start.