Asys_AAS_PWS_2025_Aug_7.pdf

UNCLASSIFIED CONTROLLED INFORMATION (CUI)

PERFORMANCE WORK STATEMENT (PWS)

ENGINEERING AND ANALYSIS ACTIVITIES

IN LANDING GEAR:

ANALYSIS ENGINEERING SUPPORT

AIR FORCE MATERIEL COMMAND (AFMC)

AIR FORCE SUSTAINMENT CENTER (AFSC)

417 SCMS/GUEA LANDING SYSTEM ENGINEERING

HILL AFB, UT

DATE: 7 August 2025

1.0 GENERAL INFORMATION

1.1 Introduction / Purpose / Background

The intent of this Performance Work Statement (PWS) is to obtain Assistance and Advisory Service (A&AS) in support of the 417th Supply Chain Management Squadron (SCMS) design and analysis requirements for landing gear structures. This contract provides comprehensive engineering support to the Landing Gear Squadron, encompassing logistics, engineering, equipment management, item management, and production management for various aircraft, including the A-10, B-1,B-2, B-52, C-5, C-130, F-15, F-16, KC-46, KC-135 and T-38.

2.0 REFERENCE DOCUMENTS

2.1 Government / Other Documents

MIL-STD-882E

Documents as required by the individual engineering task

3.0 SCOPE / CONTRACTOR TASKING / REQUIREMENTS

3.1 Engineering Design and Analysis Support

All tasks outlined in this contract are considered severable. The Contractor shall provide the following engineering design and analysis support for landing gear structures.

3.1.1 Analysis Method Development

Develop and execute analysis methods related to landing gear loading, reactions, stress, and crack nucleation.

3.1.2 Advanced Structural Analysis

Utilize state-of-the-art structural analysis tools, including, but not limited to, MATLAB, ANSYS, HBM nCode Design Life, and Solidworks. This may require the development of new engineering methods.

3.1.3 Solid Modeling and Analysis

Develop 3D solid models from 2D drawings and perform static strength analysis under ultimate load conditions. Conduct fatigue crack nucleation analyses.

3.1.4 Crack Growth Evaluation

Evaluate crack growth in landing gear, considering factors such as corrosion, pre-existing repairs, stress corrosion cracking, manufacturing processes, and residual stresses.

3.1.5 Design and Analysis of Modifications

Design and analyze structural modifications, repairs, and component redesigns based on requirements identified by field units, depots, or other relevant stakeholders. Evaluate new manufacturing and maintenance processes for their applicability to sustainment efforts. Support the qualification of new processes as considered by depot or field organizations.

3.1.6 Landing Gear Risk Assessment and Analysis Support

Utilize field data, depot maintenance data, and flight data to develop, refine and support landing gear risk assessments and analysis. Contractor shall possess a thorough understanding of MIL- STD-882E and provide expertise in state-of-the-art risk assessment methodologies. Specific responsibilities shall include, but not limited to:

Risk Assessment Development and Presentation

Develop comprehensive risk assessments for landing gear systems.

Summarize and present risk assessment findings to decision-makers

Sensitivity Analysis and Documentation

Conduct sensitivity studies to determine the impact of current maintenance practices.

Analyze and document the effects of improvements made to maintenance and support procedures.

Author formal system safety evaluations to document all risk assessments.

Failure Assessment and Process Improvement

Conduct failure assessments to evaluate fleet or depot findings related to corrosion, fatigue, process deficiencies, and other relevant factors.

Develop and refine processes to support part production and maintenance activities.

Evaluate the effectiveness of thermal spray methods, corrosion-preventative plating, and material additive technologies.

Quality Assurance and Process Control

Implement robust quality processes, including the development and review of metrics for repair and production processes.

Develop, qualify, and implement quality control measures for repair and production activities.

Collaboration and Knowledge Transfer

Participate in working groups and mentoring initiatives outside 417 SCMS.

3.1.7 Aircraft Airworthiness Certification and Recertification Support

Support aircraft airworthiness certification and recertification efforts. This support will directly impact aircraft sustainment by informing decision makers regarding the repair and replacement of landing gear components. Contractor shall possess a thorough understanding of Federal Aviation Administration (FAA) airworthiness certification requirements and their application to USAF independent airworthiness processes as outlined in AFPD 62-6 and AFI 62-601. Specific responsibilities shall include, but not limited to:

Analyze and influence repair and replacement decisions for landing gear parts in both repair and new production scenarios.

Consider and address process qualification requirements for new and innovative maintenance actions, including but not limited to paint stripping, spare part production, and high-strength steel forging.

3.1.8 Technical Inquiry Response

Summarize and present findings from complex engineering analyses, both formally and informally, to facilitate informed sustainment decision-making.

Support the translation of field-identified requirements into well-defined project and redesign program work statements.

3.1.9 Cross-Platform ASIP/MECSIP Facilitation

Facilitate synergistic Aircraft Structural Integrity Program (ASIP) and Mechanical Equipment, Components, and Systems Integrity Program (MECSIP) efforts for all systems supported by the 417th SCMS/GUEA, ensuring compliance with MIL-STD-1530C.

3.1.10 Engineering Test Support

Support the following material, component, and full-scale tests:

Engineering review of full-scale fatigue testing of Air Force landing gear as well as military derivatives of commercial aircraft and their landing gear.

Design of full-scale fatigue test fixturing for military and commercial landing gear testing, instrumentation and control system operational requirements for full-scale fatigue testing.

Design of sub-component and coupon tests to support and substantiate the results of analysis related to modifications, repairs, production and rework methods, and the development of new analysis tools or repair concepts.

Design of process evaluation test coupons and the necessary test machine requirements for testing.

Detailed knowledge of servo-hydraulic test machines, selection of instrumentation, validation testing through applicable ASTM test standards.

Specific knowledge related to the factors that influence specimen performance related to specimen preparation through test fixturing is expected.

3.1.11 Engineering Data Hardware/Software/Procurement Requirement

As required and approved by the Government PM, store and transport engineering data between information systems, store large analysis datasets, gather engineering information, and or process data with hardware/computer codes not currently owned or in use by the Government.

Examples of this include, but are not limited to, delivering analysis data to the Government on a hard drive, acquiring a software license not currently in use, or procuring engineering data not currently owned by the government. The exact requirement will be determined by the nature of the specific analysis work. This requirement will be cost reimbursable - no fee. Any hardware and/or software procured under this requirement shall become the property of the Government.

3.1.12 Contractor Supplied Hardware and Software

The Contractor shall provide and maintain all necessary computer hardware, Solidworks, software licenses, ANSYS software licenses, and nCode software licenses necessary to support the tasks of this PWS when Government-furnished equipment and software are not available.

The Contractor shall implement and maintain contingency plans for hardware/software failures and data recovery procedures. Example, if Adobe license expires on Government computer, the expectation is the contractor would be able to operate without that Government provided software.

All contractor supplied hardware must meet or exceed minimum USAF current operational versions and specifications required for running current versions of the specified software suites and must be capable of processing and storing large engineering datasets. The Contractor is responsible for all contractor supplied hardware maintenance, software patches updates, license renewal and replacements needed to maintain operational capability. The Contractor shall maintain proper documentation of compliance and approval status for all hardware and software implementations. Regular security audits and assessments must be conducted and documented in accordance with DoD cybersecurity requirements and applicable security classifications.

Notification of any system failures or security incidents shall be provided to the Government.

3.1.13 Transition of Workload

In the event a follow-on contract is awarded to other than the incumbent Contractor or if the operation reverts to in-house, the incumbent Contractor shall provide all reasonable support to the Government and/or the successful offeror to ensure an orderly transition and minimize any impact on the entire operation.

3.1.14 Post Award Conference

A post-award conference shall be conducted IAW FAR 42.503.

3.2 Documentation / Data / Reporting Requirements

3.2.1 Data Rights

Documentation provided by the Government in support of this contract, in any media, shall remain the sole property of the U.S. Government with unlimited rights belonging to the U.S. Air Force in accordance with DFARS 252.227-7013.

Documentation generated by the Contractor in support of this contract, in any media, shall remain the sole property of the U.S. Government with unlimited rights belonging to the U.S. Air Force in accordance with DFARS 252.227-7013.

Documentation generated using Contractor-owned equipment and software licenses shall remain the sole property of the U.S. Government with unlimited rights belonging to the U.S. Air Force in accordance with DFARS 252.227-7013.

3.2.2 Documentation Management

Documentation shall be maintained, inventoried, and disposed of in accordance with the applicable records management regulations AFI 33-322, AFMAN 33-363, and AFI 33-364 (in their entirety) and written coordination with the Government COR. The Contractor shall ensure proper marking and handling of all technical data and maintain secure backup systems with appropriate data protection measures in accordance with DoD standards. The Contractor shall not use or disclose any documentation for any purpose or in any manner not specifically authorized or required by this PWS.

All documentation returned to the Government COR during contract performance, at contract completion or termination shall be in the English language, readable, and in a readily retrievable format, which requires no additional software or tools to read and to retrieve beyond those already installed on the affected U.S. Government computers.

3.2.3 Documentation Inspection / Acceptance

The Government has the inherent right to disapprove any data deliverables. Therefore, the Government Program Manager will have the right to reject or require correction of any deficiencies found in deliverables. In the event of rejection of any deliverable, the Government Program Manager, with coordination with the COR. will notify the Contractor in writing of the specific reasons why the deliverable was rejected. The Contractor shall have 10 calendar days, or unless designated otherwise through a PCO letter or contract modification, to correct the rejected deliverable and resubmit to the Government Program Manager for re-inspection. The Government must approve final versions of data deliverables.

3.2.4 Documentation Deliverables

Reporting and data requirements shall be provided in the DD Form 1423-1 Contract Data Requirements List (CDRL) A/B/C004. Documentation shall include but not limited: analysis results, engineering products, design files, simulation data, test results, documentation, and reports, data, records, files, documents, work papers, logs, materials, products, and services.

Documentation also includes requirements information from customers, design specifications, notes, end-user manuals, flowcharts, diagrams, and prototypes. Products and services include those that are innovations, or were learned as part of normal operational processes, or those not listed as a requirement but the Contractor saw and filled a need based on Government CO approval at no additional cost to the Government. CDRL A/B/0004

This list shall not be considered as all-inclusive and may change after award. The Government retains the right to request and/or modify the current format at no additional cost to the Government. The following CDRLS shall be provided electronically to the Government:

CDRL DID TITLE

A/B/C001 DI-MGMT 80227/T Contractor’s Progress. Status, & Management Report A/B/C002 DI-ADMN 81373/T Presentation Material A/B/C003 DI- QCIC 81722/T Quality Program Plan (QPP) A/B/C004 DI-MISC-81920 List of All Deliverables, Subtitle: Continuity Book A/B/C005 DI-MISC-80508B/T Technical Report-Study/Services A/B/C006 DI-SAFT-81563/T Accident/Incident Report, Subtitle: Mishap Report A/B/C007 DI- QCIC 81722/T Property Management Plan (PMP) A/B/C008 DI-SAFT-81626 System Safety Program Pan (SSPP)

3.2.4.1 Deliverables with Proposal

The following shall be submitted with the Contractor’s proposal in response to the solicitation and approved by the CO before the start of the performance period.

System Safety Program Plan (SSPP) (CDRL A/B/C008)

IAW Appendix C, and updated as changes occur and resubmitted for government approval.

Quality Program Plan (QQP) (CDRL A/B/C003)

Describes the inspection system to ensure services are provided IAW the PWS. Procedures to identify, prevent, and ensure non-recurrence of defective services. Key performance parameters shall be used to monitor work performance, measure results, ensure delivery of contracted product deliverables and solutions, support management and decision-making and facilitate communications. Identify risks, resolve problems and verify effectiveness of corrective actions. Institute and maintain a process that ensures problems and action items are tracked through resolution and shall provide timely status reporting. Results of actions taken to improve performance shall be tracked and lessons learned incorporated into applicable processes. Establish and maintain a documented set of disciplined, mature and continuously improving processes for administering all contract efforts with an emphasis on schedule, performance, responsiveness and consistently high-quality delivery. Plan shall be updated as changes occur and resubmitted for government approval.

Property Management Plan (PMP) (CDRL A/B/C007)

Describes the voluntary consensus standards (VCSs) or industry-leading practices (ILPs) Contractor shall follow regarding Government Furnished Property (GFP) FAR 45.201(c)(4).

Upon approval, PMP will be incorporated into the resulting contract upon award.

3.2.4.2 Contractor’s Progress. Status, & Management Report (CDRL A/B/C001)

The contractor shall provide a written monthly status report detailing projects in-work due by the 10th calendar day of the following month. The contractor shall attend quarterly Program Management Reviews (PMRs) and End of Performance Project Review meetings if requested and scheduled by the COR. The purpose of these meetings is to discuss progress and achievements made during the performance period, as well as any outstanding issues requiring the attention of the AF. The Contractor shall identify any outstanding issues requiring AF attention and/or any areas where process improvement efficiencies can be gained and are recommended in the Monthly Status Report.

Develop and maintain contingency plans for situations that might impact either on-site or alternate work location capabilities, including but not limited to: network outages, facility access issues, weather-related disruptions, or other force majeure events. The plan shall be updated as changes occur and resubmitted for government approval.

The Contractor shall also maintain detailed records of work location patterns, hours worked, and task completion metrics to ensure transparency and accountability. Shall be updated as changes occur and resubmitted for government approval.

Post travel report shall also be included in the progress report. See section 5.5 of this PWS

3.2.4.3 Technical Report-Study/Services (CDRL A/B/C005)

All engineering support shall be fully documented in technical reports as defined by Data Item Description (DID) DI-MISC-80508B with attachments to include memos, drawings, engineering orders, computer generated analysis models/data, source data, computer scripts, and research papers. Due to the custom nature of each technical report, the final data product will be delineated by the specific and discrete effort. All engineering data referenced and generated shall be government-owned with appropriate distribution control statements. The Contractor shall certify compliance with distribution control requirements at the completion of each engineering task.

3.2.4.4 Contractor Full-Time Equivalent Reporting (eCRMA)

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the 417 SCMS via a secure data collection site. The contractor shall register this contract an input all required information into eCMRA: https://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the Contractor Manpower Reporting Application (CMRA) help desk.

Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the 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 requires 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

3.2.4.5 Accident / Incident Report - Voluntary Protection Program (VPP) (CDRL A/B/C006)

The Contractor shall provide from its OSHA 300 information the Total Case Incident Rate/Days Away Restricted or Transferred (TCIR/DART) rates to the CO and COR that administer the basic contract for submission as part of the installation’s annual OSHA VPP self-evaluation report. See Safety section of this PWS for reference.

4.0 GENERAL REQUIREMENTS

4.1 Mission Essential Services

This requirement is NOT considered essential per DFARS 237.7602.

4.2 Performance- Based Services

This requirement is considered performance-based services, not personal services; therefore, the PWS describes the work to be performed – not specific labor categories or number of contractor personnel.

4.3 Non-Personal Services

The selection, assignment, reassignment, transfer, supervision, management, and control of Contractor employees in performance of this PWS shall be the responsibility and prerogative of the Contractor. The Government will neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual Contractor employees. It shall be the responsibility of the Contractor to manage its employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the Contractor feels that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor's responsibility to notify the COR immediately. These services shall not be used to perform work of a policy/decision making or management nature, i.e., inherently Governmental functions. All decisions relative to programs supported by the Contractor shall be the sole responsibility of the Government.

The Contractor shall ensure all employees, including Subcontractors, receive and read a copy of this PWS prior to commencing work. The Contractor shall provide written confirmation to the PM, COR and CO that this has occurred prior to starting performance.

4.4 Period of Performance and Option Year Periods

The period of performance shall be IAW Section B, The Schedule, of the contract (i.e.

individual CLINs of the Contract). The base period of performance is one (1) year, with two (2) optional one-year extensions, for a maximum performance period of three (3) years.

These options may be exercised through a modification to the contract (i.e. written direction of the Government Contracting Officer) in the event additional funding is made available. The contractor SHALL NOT start work until receipt of a contract modification that exercises the option period and obligates additional funding. It is anticipated option years may be exercised within the previous performance period (i.e. option year 1 may be exercised within the basic period). Refer to FAR clause 52.217-9, Option to Extend the Term of the Contract, of the task order for information regarding when the Government gives the contractor preliminary written notice of its intent to exercise these optional years.

4.5 Contractor Personnel Qualification

4.5.1 Qualification

The following skill set establishes the minimum core competency required to perform the tasks required by this PWS. The Contractor shall ensure all employees possess required training, qualifications, proficiency, security clearances and satisfy all other access requirements.

Training necessary to meet minimum requirements will not be paid for by the Government.

Engineering master’s degree from a ABET accredited engineering school and experience targeted toward the development of structural integrity methods, engineering method development, and structural qualification.

Familiarity with the structural layout of various military airframes including, but not limited to, the A-10, B-1, B-2, B-52, C-5, C-130, E-3, F-5, F-15, F-16, KC-135, and T-38. A thorough understanding of the principles of aerospace structural analysis (including safe-life management, fatigue failure, failure mechanisms), the tools used for structural analysis (including finite element methods, Miner’s fatigue method, strain based fatigue initiation, fracture mechanics), verification and validation methods for analysis, the mechanical behavior and properties of materials used in aerospace structures, and the demonstrated ability to synthesize these skills and transition them to Government engineers through formal and informal mentoring sessions.

8 years systems engineering experience.

2 years experience with material testing and allowable development for military and commercial aircraft.

2 years experience with Air Force ASIP, structures, engineering, sustainment, and program management experience associated with DoD logistic support and supply chain management.

2 years experience with loads and usage spectrum development, data collection methods, and aircraft usage coordination.

2 years experience supporting safety probabilistic studies to include risk and economic analyses.

5 years experience in aerospace materials characterization, failure assessment, fatigue nucleation, fracture mechanics, and corrosion of metallic aircraft structures.

2 years experience solid modeling experience with Dassault Systems SolidWorks and knowledge of other industry modeling formats.

2 years experience with finite element analysis, specific to aerospace structures. Experience time requirement shall be with ANSYS Workbench and ANSYS APDL.

2 years experience evaluating fatigue life and durability utilizing strain-life based methods.

1 year experience with aerospace landing gear systems to include, landing system layout, shock absorber design, tires, aircraft steering systems, brakes, wheels, airfield design, and landing gear kinematic concepts.

4.5.2 Professional Certifications and/or Licenses Required for Contractor Personnel

The following Professional Certifications and/or Licenses shall be required in support of the performance of this PWS.

No certification required outside of a ABET accredited engineering school is anticipated

4.5.3 General Training Requirements

Below is a list of general training requirements that may be required in support of this PWS.

This list is for informational purposes only and is not considered to be all inclusive.

TABLE 4.5.3 GENERAL TRAINING REQUIREMENTS

COURSE NAME GOVT

PROVIDED

CONTRACTOR

PROVIDED

NOTES

New Hire Training- Hill AFB Contractors X Contractor New Hire Training

Controlled and Restricted Area Training X All contractor personnel requiring access to controlled areas.

Generating and Distributing Scientific and Technical Information (STINFO)

X

DoD Directive 8570.1. - Information Assurance Training, Certification and Workforce Management

X All contractor personnel shall comply with all computer and network access requirements and instructions

4.5.4 Other Government Provided Training

The contractor’s employees may participate in other Government provided training, on a non-discriminatory basis as among contractors, under the following circumstances:

Employees’ participation is on a space-available basis.

Employees’ participation does not negatively impact performance of this contract.

Government incurs no additional cost in providing the training due to the contractor employees’ participation.

4.5.5 Software Program Languages

Below is a list of software program languages that may be required in support of this PWS. This list is for informational purposes only and is not considered to be all inclusive.

Table 4.5.5 Software Program Languages

Software Program Languages

ANSYS

MATLAB

4.5.6 System Access

Below is a list of systems that may be required and/or utilized in support of this PWS. This list is for informational purposes only and is not considered to be all inclusive.

Table 4.5.6 System Access

System Access Enhanced Technical Information Management System (ETIMS) All-purpose Tool for Engineering, Analytics, and Management (A-TEAM )

4.5.6.1 ETIMS

ETIMS access is required to establish and manage TODO accounts, prospective TODO the contractor must first obtain a Common Access Card (CAC) or an External Certificate Authority (ECA) with a minimum of a favorable NAC to establish Air Force Portal access needed for ETIMS. Procedures for contractors to obtain an ECA certificate are found at:

http://iase.disa.mil/pki/eca/certificate.html. The USAF portal ID of the prospective, primary TODO POC is entered into block 6 of the AFTO Form 43. The designated Contracting Officer representative must confirm an approved DD Form 2345; Militarily Critical Technical Data

Agreement (AFI 61-204, Disseminating Scientific and Technical Information) is on file prior to approving the AFTO Form 43. The approved AFTO Form 43 is then submitted to the OC- ALC/EZGTP using the following email address: aflcmc.ezgtp.afto43@us.af.mil. If Government support contractors maintain a separate company-owned TO library, the company shall process a separate AFTO Form 43 to establish the contractor owned and operated TODO.

NOTE: Once contractor TODO accounts are established, the contractor TODO uses ETIMS to directly order and receive the TOs required under the contract. Upon receipt of the approved AFTO Form 43, the primary TODO should access and use the ETIMS account associated with the Joint Computer-Aided Acquisition and Logistics Support (JCALS) TM account number on the AFTO Form 43 to establish and manage their unit’s TO / ETO requirements.

4.5.6.2 A-TEAM

The contractor shall be responsible for gaining access to A-TEAM to obtain required technical drawings. Use the link (https://usaf.dps.mil/sites/LZP/JARVIS) and click the white button under PDSS System Account Requests. Fill out the form and submit an e2875 per the site instructions.

Once access has been granted, login to A-TEAM with the link https://a-team.us.af.mil/login/

4.5.7 Organizational Conflict of Interest (OCI)

Contractor Personnel

The Contractor shall not employ any person who is an employee of the United States (US) Government if the employment of that person would create a conflict of interest.

The Contractor shall not employ any person who is an employee of the Department of the Air Force (AF), either military or civilian, unless such person seeks and receives approval according to the Department of Defense (DoD) 5500.7-R Joint Ethics Regulations (JER) and the policies contained in Air Force Instruction (AFI) 64-106, AF Industrial Labor Relations Activities.

The Contractor shall be prohibited from employing off-duty CORs who are surveying any contracts or subcontracts awarded to the Contractor.

Future Acquisitions

The Contractor may be required to perform the following services under this PWS, which are more likely to result in an actual or potential OCI, as defined in FAR Subpart 9.5.

Determining specifications Identifying and resolving interface problems Developing test requirements Evaluating test data, and supervising design.

Developing work statements Determining parameters Resolving technical controversies Access to proprietary information

The Contractor shall notify the PM and CO immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the CO to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the CO and in the event the CO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the CO may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

5.0 PLACE OF PERFORMANCE

5.1 Primary Place of Performance

Contractor personnel shall work as part of an integrated team alongside government personnel within the primary places of performance identified in the table below. While the preferred place of performance is a government installation an alternate place of performance may be used IAW section 5.4 when the alternate workplace is beneficial to the effort being accomplished .

Table 5.1 Primary Place of Performance

Supported Organization Location 417 SCMS 417th SCMS/GUEA, Bldg. 1216, Hill AFB, Utah

5.1.1 Insurance – Work on a Government Installation

Before commencing work under this contract, the Contractor shall notify the Contracting Officer in writing that the required insurance in accordance with (IAW) FAR clause 52.228-5, Insurance-Work on a Government Installation, of the basic contract has been obtained.

5.2 Days and Hours of Operation (work to be performed at Government location)

Contractor is responsible for providing continuous support between the normal core working hours 8:00 am to 3:00 PM Mountain Time, five (5) days per week Monday thru Friday (except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings). Core working hours don’t necessarily represent the working schedule, but represent availability for supporting Government requirements.

5.3 Contract Holidays (work to be performed at Government location)

The prices/costs in Section B, The Schedule, of the contract shall include holiday observations;

accordingly, the Government will not be billed for such holidays, except when services are required by the Government and are actually performed on a holiday. Holidays falling on a Saturday will be observed on the preceding Friday. Holidays falling on a Sunday will be observed on the following Monday. The following days are considered contract holidays per the U.S. Office of Personnel Management holiday schedule. In addition, the Contractor may be required to observe energy days and/or other down days as directed by OO-ALC Center Commander, AFSC Center Commander and/or AFMC.

New Year’s Day 1 January

Martin Luther King’s Birthday Third Monday in January President’s Day Third Monday in February Memorial Day Last Monday in May Juneteenth 19 June Independence Day 4 July Labor Day First Monday in September Columbus Day Second Monday in October Veteran’s Day 11 November Thanksgiving Day Fourth Thursday in November Christmas Day 25 December

5.4 Alternate Place of Performance

Any requests to change the designated work location (telework or contractor facility) must be submitted for approval to the Government PM, COR and CO at least 30 calendar days in advance of the proposed change.

The CO shall notify the contractor whether the request was approved or not. Alternate locations shall not be used prior to Government approval. In the event a request is approved, the following shall apply (list is not considered all inclusive):

Result in no additional cost to the Government. For example, Contractor shall be responsible for any travel costs to the primary place of performance when contractor personnel is needed to perform PWS tasks.

Approval is on a case-by-case basis and must be in the best interests of the Government.

Approval may be revoked at any time by the CO.

Employees performing off-site and requiring access to Government systems/networks shall only use Government provided computers (desktop or laptop).

Maintain full connectivity and accessibility during standard business hours, including video conferencing capability, telephone accessibility, and real-time collaboration tools as specified by the Government.

Technical infrastructure to support required duties, including necessary bandwidth, hardware, and software capabilities.

Meet all applicable security requirements, including appropriate network connectivity, secure communication capabilities, and compliance with DoD cybersecurity standards.

5.5 Travel

5.5.1 Travel Pre-Approval

It is anticipated that contractor personnel may be required to travel within the Continental United States (CONUS) on an “as needed basis” in support of the work to be performed under this PWS. Each travel request shall be reviewed by the Contracting Officer Representative (COR) prior to submitting to the Government Program Manager and Contracting Officer for approval prior to traveling. The Contractor shall obtain written approval from the Government prior to making travel arrangements.

5.5.2 Travel Expenses

The Contractor shall be responsible for any and all travel expenses incurred within a 50 mile radius of Hill AFB in performance of this PWS or when an alternate place of performance is required regardless of the distance from Hill AFB. Contractor travel policies and procedures must be best business practices IAW FAR 31.205-46. Contractor must use FAR 31.205-46 and the DoD Joint Travel Regulation (JTR) as a guide regarding air fares, per diem, allowances and reimbursement of travel expenses. First class air travel is not authorized. Costs incurred must be in accordance with FAR 31.205-46. The Government reserves the right to disallow unreasonable travel costs. Travel must be billed as a separate line item on all invoices.

5.5.3 Post Travel Report

The contractor shall submit a travel report to the COR within 10 business days after travel is complete, (CDRL A/B/C001).

5.6 Government Services Plan (work to be performed at Government location)

When work is to be performed at the Government’s location, the Government will prioritize service requirements based on operating requirements. The Government will provide the Contractor’s Technical Lead a generalized projected service plan that may be reviewed or revised by the Government Program Manger as necessary. The purpose of the plan is to prioritize Government service requirements and provide the contractor with the information the contractor needs to effectively manage their contractor personnel.

The Contractor shall provide total task management and supervise contractor personnel. The Government’s relationship in this non-personal services contract is with the Contractor and not with individuals employed by the Contractor. At all times, it must be clear that the Contractor, not the Government, manages its employees. The Contractor’s Technical Lead shall serve as the primary point of contact for all technical aspects of the required work. This person shall also be a prime provider of the required technical services. No personal services shall be performed.

AFI63-138, Chapter 6, Section 6.4, Initial Contract Performance Review, states “The initial evaluation of contractor performance is a joint determination by the multi-functional team (MFT) that the contractor has successfully started performance, completed transition, is fully operational, and is within the estimated cost, schedule, and performance parameters of the contract. The initial performance review criteria shall be included in the QASP or similar documentation. The Services Designated Official (SDO) may waive the initial evaluation for contractors that have continued performance under a successor contract award (prior incumbent), or for contractors that have otherwise demonstrated full compliance with contract start-up. Separate initial contract performance reviews are not required when they would duplicate existing reviews.”

AFI63-138, Chapter 6, Section 6.4.1, Scheduling, states “The review shall take place within 30 days after the contractor assumes full performance responsibility (i.e. after completion of transition/mobilization).”

In order to help the contractor start performance, complete transition/mobilization and become fully operational when work is to be performed at the Government location, the following initial performance review criteria is provided below. These criteria shall be used for the “Initial Contract Performance Review” that shall take place 30 days after receipt of contract (DAROC)

(i.e. contract award) and shall also be considered as the initial generalized projected service plan. This list shall not be considered to be all inclusive and may be reviewed or revised by the Government Program Manger as necessary after award.

Below is an example of a Government Provided Service Plan. It should be noted that this is only an example and may be subject to change per the requirements of the PWS.

Initial Performance Review Criteria / Government Provided Service Plan

DAROTO

(Business Days) Performance / Objective Element

No later than 30 days prior to starting work or entering secure areas.

IAW DAFFARS clause 5352.204-9000, Notification of Government Security Activity, the Contractor Security Officer shall ensure that the Security Agreement is completed and signed, and a copy is on file with 448th Security Officer no later than 30 days prior to starting work or entering secure areas.

1 Contractor shall provide a notice of who their designated “Technical Lead” is for this contract to the PM, CO and COR.

Contractor shall provide a listing of personnel who require Base or Area Badges and Access to Facilities and a CAC to the CO, PM, COR and Security Manager.

1 - 5 Contractor personnel shall coordinate receipt/assignment of Base Support

- Government Provided Office Space with the PM and COR.

Contractor’s Technical Lead shall notify the PM and COR when the Contractor has obtained the Government documents referenced in the

PWS.

12 Contractor personnel in place at Government location and ready to begin performance of PWS tasks.

6.0 SPECIAL CONSIDERATIONS

6.1 Security

6.1.1 General Information / Standards of Conduct

Contractor employees shall identify/represent themselves as contractor personnel by displaying distinguishing badges or other visible identification. Identify themselves as contractor employees in telephone, conversations and formal/informal written correspondence. Contractor signature blocks on E-mail messages shall identify their status. Identify themselves as contractor employees on any attendance sheet or any coordination documents they may review. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, contractor/subcontractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Where practicable, contractor occupying collocated space with their Government program customer should identify their work space area with their name and company affiliation.

All Contractor employees shall conduct themselves in a professional, courteous manner. The Contractor shall not employ persons on this contract if such employee is identified to the Contractor as a potential threat to the health, safety, security, or general well-being or operational mission of the installation and its population. The Contractor understands that any Contractor employee may be summarily and immediately removed from or denied access to any government property, facility, and installation at the sole discretion of competent government authority if that authority determines such action is necessary to protect or preserve government property, safety and security, or to maintain good order and discipline. It is the responsibility of the Contractor to replace, at no additional cost to the Government, any of its employees that are removed pursuant to the section where replacement is necessary to ensure full, timely, and complete contract performance.

6.1.2 Release/Removal of Documentation

The Contractor shall not release or remove system documentation, data, or reports generated by or through use of any government systems. The Contractor shall not divulge any information regarding files, data, processing activities/functions, user ID's, passwords, or other knowledge they may have gained, to anyone who is not authorized to have access to such information.

Contractor personnel shall abide by all government rules, policies, procedures, and standards of conduct. All requests for information shall be forwarded to the Contracting Officer who will request approval from the Government Program Office.

6.1.3 Automated Information Systems (AIS) Security

Contractors requiring access to Government AIS shall have background investigations, security awareness training, and derivative classifier training completed prior to the start of contract performance. The Government Program Office will be responsible to verify the appropriate background investigations are performed. When the period of performance is complete or contractor personnel leave work on this project, the contractor personnel shall terminate all their network user accounts and return all access cards and base identification within 5 working days, unless authorized to retain them.

6.1.4 Safeguarding Covered Defense Information and Cyber Incident Reporting

The contractor shall control information IAW the following clauses, other sections of this PWS and terms and conditions of the contract.

252.204-7008 Compliance with Safeguarding Covered Defense Information Controls 252.204-7009 Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting 252.239-7009, Representation of Use of Cloud Computing 252.239-7010, Cloud Computing Services 5352.204-9000, Notification of Government Security Activity and Visitor Group Security Agreement

6.1.5 Universal Serial Bus (USB) Devices

All Contractor employees shall comply with the following Universal Serial Bus (USB) Device policy while performing work utilizing Government computers:

USB flash memory devices are not allowed to be plugged into a Government computer at any time, including when the network cable is unplugged. USB flash memory devices include cell phones, memory sticks, cameras, iPods, and mp3 players. A violation of this policy will result in removal of network access.

6.1.6 Access to Confidential, Proprietary and/or Sensitive Information

Contractor personnel may be required to access Confidential, Proprietary and/or Sensitive Information held by the USAF relating to the tasks to be performed under the individual Task Orders. This information may belong to other contractors, other third parties, or the USAF.

Contractor personnel, direct and indirect, shall provide a completed copy of the Nondisclosure Agreement (NDA) provided below to the Government PM, CO, and COR prior to performing work that involves Confidential, Proprietary and/or Sensitive Information held by the AF.

It should be noted that Confidential, Proprietary and/or Sensitive Information shall not include information that the Contractor personnel or the Contractor can demonstrate:

(A) was known by the Contractor personnel or the Contractor without restriction as to further disclosure when received or was developed independently by the Contractor by individuals who had no direct or indirect access to such information,

(B) was obtained from a source other than the USAF, its employees, agents, or contractors through no breach of confidence,

(C) was in the public domain when received or thereafter enters the public domain through no breach of confidence by Contractor or Contractor personnel, or

(D) was used or disclosed with the prior written approval of the USAF.

It should be noted that this is only an example of an NDA and may be subject to change per the requirements of the PWS.

CONTRACTOR

NONDISCLOSURE AGREEMENT (NDA)

Contractor / Contract #: ____________________________________

I, ____________________________, an employee of ___________________________________, (Contractor) in order to support the United States Air Force (USAF) and in consideration of the USAF granting me access to Confidential, Proprietary and/or Sensitive Information held by the USAF relating to the tasks to be performed under the Task Order, intending to be legally bound, hereby agree to the following terms and conditions:

1. I understand that my assignment to support the Contractor in its contractual duties under the Task Order (the “Effort”) will involve access to Confidential, Proprietary and/or Sensitive Information belonging to other contractors, other third parties, or the USAF. The sharing of Confidential, Proprietary and/or Sensitive Information is necessary to effectively perform the mission of the USAF.

2. Except as expressly authorized in writing by the USAF, I agree to hold Confidential, Proprietary and/or Sensitive Information in trust and confidence and agree that it shall be used only for my performance of duties in support of the Contractor’s performance of the Effort, shall not be used for any other purpose, or disclosed to any third party outside the USAF. I agree that I shall not, except as expressly authorized in writing by the USAF, at any time during or after my performance of duties in support of the Contractor’s performance of the Effort, directly or indirectly, disclose, publish or disseminate, to any other person or entity, any Confidential, Proprietary and/or Sensitive Information I have access to by reason of my performance of duties in support of the Contractor’s performance of the Effort, nor shall I use any such Confidential, Proprietary and/or Sensitive Information for my personal use or advantage, or make it available to others not cleared for access to Confidential, Proprietary and/or Sensitive Information by the USAF or lacking a need-to-know for performance of the Effort. I will hold all Confidential, Proprietary and/or Sensitive Information I have access to by reason of my performance of duties in support of the Contractor’s performance of the Effort in confidence and use it solely for the benefit of the USAF and the performance of Effort. I shall not retain any Confidential, Proprietary and/or Sensitive Information, including written notes, photographs, sketches, models, memoranda or any tangible representation of the Confidential, Proprietary and/or Sensitive Information except as required in my performance of duties in support of the Contractor’s performance of the Effort. Without limiting the generality of the foregoing statements, I agree that Confidential, Proprietary and/or Sensitive Information shall not be released to the media, press, competing firms, individuals, or government officials outside the USAF for any purpose. I further understand and agree that all Confidential, Proprietary and/or Sensitive Information shall be retained, disseminated, released, and destroyed in accordance with the requirements of law and applicable Department of Defense or USAF directives, regulations, instructions, policies and guidance.

3. All information that I receive or obtain in performance of my duties in support of the Contractor’s performance of the Effort shall be deemed to be Confidential, Proprietary and/or Sensitive Information, including, without limitation, visual, verbal and written information, in whatever form or medium, including, but not limited to, personal, business or financial information, or intellectual property, or technical information in the form of discussions, communications, designs, concepts, requirements, specifications, software, interfaces, components, processes, or similar things. I understand and agree that any work product related to the Effort, including, but not limited to, final documents and products, drafts, feeder documents, briefings, notes, and any other related oral or written communication shall constitute Confidential, Proprietary and/or Sensitive Information for purposes of this Agreement.