DRAFT AWBS PWS 21 Jul 2021.pdf

PERFORMANCE WORK STATEMENT (PWS)

For

Automatic Weight and Balance System (AWBS)/Automated Form F Generator (AFF)

Prepared by:

Pamela Christensen A-10 Division

Ogden Air Logistics Center Hill AFB, Utah 84056

PR # FD2020-21-XXXXX

21 July 2021

REVISION RECORD

Revision Date Description Pages

ACRONYM LIST

ACO - Administrative Contracting Officer AFF – Automated Form F AFLCMC/WAA – Air Force Life Cycle Management Center/A-10 Division AWBS - Automated Weight and Balance CDRL - Contract Data Requirements Lists CTM - Contract Technical Monitor COR- Contracting Officer Representative DoD - Department of Defense DFARS - Defense Federal Acquisition Regulation Supplement DID - Data Item Description ETIMS - Enhanced Technical Information Management System GFE - Government Furnished Equipment GFI - Government Furnished Information CG - Center of Gravity IAW - In Accordance With IPT - Integrated Product Team JTR - Joint Travel Regulations MDS - Model Design Series OSHA - Occupational Safety and Health Administration OSS&E - Operational, Safety, Suitability and Effectiveness PCO – Procurement Contracting Officer PM - Program Manager SPO - System Program Office PWS – Performance Work Statement TO - Technical Orders TIM - Technical Interchange Meeting

Table of Contents

1.0 INTRODUCTION

1.1 Purpose

1.2 Background

2.0 APPLICABLE DOCUMENTS

2.1 Compliance Documents

DoD Documents

2.2 Other Documents

2.3 Government Furnished Equipment

2.4 Government Furnished Information

3.0 CONTRACTOR REQUIREMENTS

3.1 General Requirements

3.2 Program Management

3.2.1 Technical Interchange Meetings (TIMs)

3.3 Data Format Requirements

3.3.1 A-10 Model Design Series (MDS) Requirements

3.3.2 A-10 Design & Upgrade

3.3.3 A-10 Integration and Test

3.3.4 A-10 Software Distribution

3.3.5 A-10 On-line Help

3.4 Program Summary

4.0 PERIOD OF PERFORMANCE AND DELIVERABLES

4.1 Period of Performance

4.2 Deliverables Contractor Data Requirements List (CDRL)

4.3 Government Inspection and Acceptance of Deliverables

5.0 ADMINISTRATIVE

5.1 Contract Management

5.2 Travel Requirements

5.4.1 Release/Removal of Documentation

6.0 SERVICES SUMMARY

6.1 Services Summary Table

6.2.1 One-Hundred Percent Inspection

6.2.2 Periodic Surveillance/Inspection

6.3 Government Quality Assurance Surveillance

6.4 Contractor Quality Assurance Requirements

1.0 INTRODUCTION

1.1 Purpose

The purpose of this Performance Work Statement (PWS) establishes the contractor activities necessary to identify system deficiencies and update the A-10C AFF software that incorporates changes and revisions to relevant Technical Orders (TO).

1.2 Background

Lockheed Martin is the original owner and designer of the AWBS software since 1999, and owns 100% of the data rights. Over the years Lockheed Martin has implemented specific AFF software not only on the A-10, but on ten other USAF platforms as well as multiple Army/Navy aircraft. The initial A-10 AFF contract was awarded to Lockheed Martin in the 2000 timeframe due to their history and success of their AWBS program. The AFF software was designed to incorporate the A-10’s unique flight profile in combat and addresses all of the flight stores that are defined in TO 1A-10C-1, 1-1B-50, and 1A-10C-5. The Department of Defense (DoD) utilizes a Microsoft (MS) window-based software tool, the Automated Form F (AFF), to automate weight and balance calculations for Fighter/Attack Aircraft. The AFF uses data from weight and balance technical orders to automate the generation of flight clearance Form Fs. AFF uses aircraft effectivity data to determine the aircraft Mission Design Series (MDS) type to calculate the forward and aft limits and determine fuel tank capacities. It calculates all Center of Gravity (CG) limits, in-flight limits, and fuel weights and moments. The AFF also calculates most forward and most aft conditions. Weight and Balance Technicians face the complex task of generating Form Fs for Fighter/Attack aircraft. Over time, the limiting weight and balance factors have become more complex. Many errors in interpreting the weight and center of gravity results have occurred. Increases in the number of weight limits, in-flight limits, and fuel capacities have compounded the problem. Multiple limits make identifying unsafe aircraft even more critical. The AFF calculates the worst case scenarios including combat configurations of the specific MDS. AFF also includes ground handling calculations for taxi, towing, jacking, and hoisting. AWBS software significantly reduces the chances of error in calculations and helps determine the aircraft will stay within safety limits throughout duration of flight and any ground operations.

2.0 APPLICABLE DOCUMENTS

2.1 Compliance Documents

DoD Documents Document No. Date Title TO 1-1B-50 *1 AUG 2019 Basic TO for USAF Aircraft Weight and Balance

TO-1A-10C-5 *10 JAN 2021

Weight and Balance Loading Data for the A-10C Aircraft *Change 1 / 22 Apr 2021

1A-10C-1 *10 FEB 2021

A-10 Flight Manual *Change 1 / 22 Apr 2021

1A-10C-2-4JG-1 *1APR 2007

Job Guide – Ground Handling *Change 33 / 22 Apr 2021

* Software updates should be based on most recent TO release

2.2 Other Documents

None.

2.3 Government Furnished Equipment

None.

2.4 Government Furnished Information

The government will provide draft electronic copies of the listed TO with RFP. The contractor shall access the published TO defined in Section 2.1 through ETIMS or other electronic means.

3.0 CONTRACTOR REQUIREMENTS

3.1 General Requirements

The executable software program generated from the tasks listed below shall be developed for the A-10C. The government will maintain government purpose rights and unlimited usage of the A-10C AFF executable program.

3.2 Program Management

The contractor shall perform administrative, technical, and financial management functions during the course of this effort and shall maintain a status of their effort towards achieving the objectives, including all technical activities and efforts, problems/deficiencies, notional schedule for Technical Interchange Meetings (TIM) and Model Design Series (MDS) report, impacts, and recommended solutions. (CDRL A002)

3.2.1 Technical Interchange Meetings (TIMs)

The contractor shall conduct technical interchange meetings as necessary in the performance of this task. The TIM with the contractor shall be scheduled when there is need for technical interchange between the government and the contractor. The proposed agenda will be provided via monthly status reports. The content of the meeting can include the discussion of any information that has impact upon the task activities, including documentation contents or format. (CDRL A002)

3.3 Data Format Requirements

Automated Form Fs shall operate with the latest Microsoft Windows operating system being used by USAF. The contractor shall upgrade the Graphical User Interface to use the latest version of AWBS common standard interfaces. A primary working interface will consist of either a Form F properties dialog and/or a tabbed view that allows the user to modify the Form F and display CG Graph (where applicable) in the view window.

The AFF shall operate with the following minimum computer configuration:

1) CPU: 1.6 GHz or faster

2) OS: Windows 10

3) RAM: 8 GB

4) PERIPHERALS:

a) Mouse and Keyboard

b) VGA or better (1920 X 1200 minimum)

c) Printer

3.3.1 A-10 Model Design Series (MDS) Requirements

The contractor shall research the latest TO and develop a requirements specification document that will include A-10C aircraft configurations and any new software/hardware technologies to increase effectiveness and performance of the software for the A-10 AFF (CDRL A001). The proposed technical approach shall be summarized at a TIM for Integrated Product Team (IPT) approval.

3.3.2 A-10 Design & Upgrade

The contractor shall upgrade the A-10 AFF based on the requirements developed under paragraph 3.3.1. The requirements shall include but are not limited to:

1) Capability for the A-10 AFF to integrate with new AWBS releases

2) Convert AFF to the most current AWBS architecture and integration

3) Software updates from current drawings and technical orders

4) Update fuel loading capabilities where applicable

5) Taxi and in-flight limits per the -5 manual (A-10 Weight and Balance TO)

6) Taxi, towing, jacking, and hoisting calculations

7) Back up loadings to Central Server

3.3.3 A-10 Integration and Test

The contractor shall develop internal test procedures for verifying system performance. The contractor shall conduct a test program to ensure the AFF meets the requirements defined herein. This test program shall consist of:

1) In-house Testing

2) Field Testing

3) User Acceptance Test, coordinated with the A-10C SPO engineering authority

3.3.4 A-10 Software Distribution

The contractor shall distribute the AFF executable program for the A-10C via the AWBS website with any necessary installation instructions. CD/DVDs will be produced upon Government request IAW (CDRL A003).

3.3.5 A-10 On-line Help

The contractor shall establish AFF On-line HELP to be compatible with the latest version of AWBS. The contractor shall provide the most current information to assist with the latest upgrades to the AFF and weight and balance concepts. All help information shall be provided to the users on the AWBS website through the A-10 AFF client application.

(CDRL A003).

3.4 Program Summary

The contractor shall summarize all work accomplished, including significant technical accomplishments, problems encountered, solutions implemented, recommendations for improvement, and a comparison of planned schedules and costs with final performance. The final report will be delivered with the last monthly status report (CDRL A002).

4.0 PERIOD OF PERFORMANCE AND DELIVERABLES

4.1 Period of Performance

Contract Period of Performance is 10 years with one 5 year option, executed with annual Orders.

For each 12-month TaskOrder, the contractor will deliver thesoftware NLT 11 months ARO of the basic PoP. Additionally, the last month will be used for the government to perform the final review of their submittals and provide a response to allow the contractor to correct any deficiencies. Essentially, each Task Order has an overall 12-month period of performance with an 11 month delivery for the software.

The contractor will be required to deliver the software no later than 11 months after Contract modification to execute each Task Order.

4.2 Deliverables Contractor Data Requirements List (CDRL)

The Contractor shall prepare and deliver data in accordance with references in earlier sections.

All Data Item Descriptions (DID) in the CDRL, as contained in the following table, shall be used as guides in upgrading the data. All CDRL items will be logged into and maintained in the Contractor's electronic library, and a cover letter paper submittal will be provided to the Government's contracting officer identifying the data item and its configuration identification (date and revision level). In the event of a conflict between the CDRL and the PWS, the PWS shall take precedence. Late submittals shall be coordinated through the Government PM and Procurement Contracting Officer (PCO).

Dist.

Stmt

Item Description Data Item

Description First

Submission

Frequency of

Submissions

Government Approval/ Info

Only

Data Rights

PWS

Paragraph Reference

D A001

A-10 AFF

Requirements Specification

Report

DI-IPSC-

81433A

10 Days Prior to TIM As Required 15 After TIM Unlimited 3.3.1

D A002 Status Reports DI-MGMT- 80368A 90 Days ARO Quarterly Info Only Unlimited 3.2, 3.2.1, 3.4

D A003

AFF

Executable Program

DI-MCCR-

80700

11 Months ARO As Required 10 Days after submission None* 3.3.4, 3.3.5

*Government will have access to Executable program only, source code will not be delivered

4.3 Government Inspection and Acceptance of Deliverables

The Government has 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 Government COR/PCO of the specific reasons why the deliverable was rejected.

The Government shall have the right to require that the Contractor make changes to any technical submissions as a result of technical or program reviews, until the final CDRL submissions have been accepted.

5.0 ADMINISTRATIVE

5.1 Contract Management

AFLCMC/WAAP will provide the Government Program Manager for this Task Order. The Government Program Manager will provide the Contractor access to available technical data required to perform approved tasking. The Air Force PCO shall be responsible for contract management. Only the PCO can make changes affecting this delivery order (contract). Any instances where implied or explicit direction, received from any government representative and perceived by the contractor to affect delivery under this contract, or to have a material impact on costs incurred in association with this contract, shall be brought to the immediate attention of the PCO for disposition and instructions before proceeding with any work thus affected. Only the Government Program Manager has authority to review and approve contract deliverables which shall be routed through government contracting. Only the PCO may approve any deliverable affecting the terms and conditions of the contract. Although forecasted travel is part of typical monthly status reports, all travel must be coordinated and approved separately per paragraph 5.2.

5.2 Travel Requirements

All travel must be pre-authorized via coordination with the assigned Program Manager and approved by the PCO in writing prior to commencement of travel. All travel will be accomplished IAW FAR 31.205-46)

The contractor is required to travel on a limited basis to accomplish this requirement. With the exception of the Travel requirement listed below, Telecoms shall be the primary means for conducting all meetings. The contractor shall forecast all travel. In the event of emergency travel, travel may be verbally authorized with the PCO contacted by both the vendor and the government POC by 1200 hours of the next duty day. Travel may be verbally authorized ONLY by the PCO. E-mail is acceptable as “written” notification. The projected travel requirements are as listed below:

a. Technical Interchange Meeting, date and location of the TIM shall be determined based on completion of MDS specification report and base access/aircraft availability (5 day meeting, 2 days travel, 2 people).

5.3 General Safety Requirements

The Contractor shall comply with all safety provisions, e.g., technical specifications, technical publications, Federal Occupational Safety and Health Standards (Title 29 CFR. Part 1910). If there is no applicable Occupational Safety and Health Administration (OSHA) standard, use other applicable nationally recognized sources of safety, health, and fire prevention standards referenced in the work requirements of this contract.

5.4 Security

This is a new contract and the effort does not require the contractor to access classified information; a DD Form 254 is not required.

5.4.1 Release/Removal of Documentation

The contractor shall not release, remove, or alter documentation, data, or reports generated by or through use of any government systems. All requests for information shall be forwarded to the Government PCO.

5.4.2 Controlled Unclassified Information (CUI)

The Contractor shall comply with DoDI 5200.48, Controlled Unclassified Information, AFI 16-1404 Air Force Information Security Program, Air Force Guidance Memorandum 2020-16-01, Air Force Guidance Memorandum for CUI, 23 July 2020, and DoDM 5400.07-Air Force Manual 33-302, DoD Freedom of Information Act (FOIA) Program. The Contractor shall monitor CUI aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information. The Contractor shall distribute controlled unclassified information IAW DoD Instruction 3200.14, Principles and Operational Parameters of the DoD Scientific and Technical Information Program, and DoD Instruction 2040.02, International Transfer of Technology, Articles, and Services. The Contractor shall properly mark all such documents IAW DoD Instruction 5230.24, Distribution Statements on Technical Documents. Technical documents not subject to distribution are defined in DoD Instruction 5230.24, DoD Directive 5230.25, and DoD Manual 5010.12-M, Procedures for the Acquisition and Management of Technical Data.

Protection of Information Controlled Unclassified Information (CUI):

Controlled Unclassified Information is any information that law, regulation, or Government-wide policy requires to have safeguarding or disseminating controls, excluding information that is classified under Executive Order 13526, Classified National Security Information, December 29, 2009, or any predecessor or successor order, or the Atomic Energy Act of 1954, as amended.

The National Archives and Records Administration (NARA) CUI Registry (http://www.archives.gov/cui/registry/category-list.html) identifies approved CUI categories and subcategories, provides general descriptions for each, identifies the basis for controls, and sets out procedures for the use of CUI.

http://www.archives.gov/cui/registry/category-list.html

The Contractor shall comply with DoDI 5200.48, Controlled Unclassified Information, AFI 16-1404 Air Force Information Security Program, and Air Force Guidance Memorandum 2020-16-01, Air Force Guidance Memorandum for CUI, 23 July 2020. The Contractor will consult the applicable Security Classification Guide to monitor CUI aggregation for potentially generating classified information by compilation.

The Contractor shall comply with DoDM 5400.07/Air Force Manual 33-302, DoD Freedom of Information Act (FOIA) Program requirements.

Protection of CUI and unclassified DoD information not approved for public release on non-DoD Information Systems will be protected IAW DoDI 8582.01, Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information. Unless specific categories of CUI require more stringent controls, non-DoD Information Systems must be protected using the guidelines set forth in NIST Special Publication 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations.

Covered Defense Information: The Contractor shall comply with DFARS 252.204-7012 Safeguard Covered Defense Information and Cyber Incident Reporting (Dec 2019). This subpart applies to contracts and subcontracts requiring Contractors and Subcontractors to safeguard covered defense information that resides in or transits through covered contractor information systems by applying specified network security controls. It also requires reporting of cyber incidents. The subpart does not abrogate any existing Contractor physical, personnel, or general administrative security operations governing the protection of unclassified DoD information, nor does it impact requirements of the National Industrial Security Program.

6.0 SERVICES SUMMARY

6.1 Services Summary Table

Performance Objective PWS Para. Performance Threshold Method of Surveillance

Software Delivery (AFF software)

4.1 The contractor shall deliver the

updated software no later than 11 months ARO of the basic delivery ordering period.

100% Inspection

Quality of Data Products:

Contractor must submit complete and accurate data

4.2 Data products must meet

contract requirements upon initial submission 90% of the time.

Periodic (Quarterly) products in accordance with the applicable CDRLs.

No more than 3% of data products shall be submitted late.

No more than 3% of data products shall have to be reworked more than once for acceptability.

6.2.1 One-Hundred Percent Inspection

This method implies inspecting every time the requirement occurs. Use of this technique may be appropriate when performance has an especially critical impact on mission accomplishment or safety, occurs infrequently or contains stringent requirements.

6.2.2 Periodic Surveillance/Inspection

Periodic surveillance/inspection is the type of surveillance that is based upon selecting samples for evaluation on other than 100% inspection or on a statistically random basis.

Periodic surveillance can be accomplished periodically using a checklist method.

Surveillance will be accomplished monthly through a written status report and program management reviews (via teleconference or in person per the PWS).

6.3 Government Quality Assurance Surveillance

The role of the Government quality assurance is to ensure that the contract standards are achieved.

In this contract, the quality control program is the driver for service quality. The COR will review comments from functional and technical experts and the contract negotiator. Contractor will be notified of comments/corrections as required. For all tasks, the Contractor shall perform systems engineering and quality assurance processes to ensure thoroughness, accuracy, and completeness during the development, analyses, and Val-Ver sections in this PWS and to ensure the delivery of error free technical data.

6.4 Contractor Quality Assurance Requirements

The Contractor shall create, implement and maintain comprehensive quality control and systems engineering processes throughout this effort.