Legacy_VII_Base PWS 11-8-2019.docx

PERFORMANCE WORK STATEMENT

A-10 Aircraft Structural Integrity Program (ASIP) Legacy VII

November 2019

AIR FORCE LIFE CYCLE MANAGEMENT CENTER ENGINEERING BRANCH

STRUCTURAL INTEGRITY AND ANALYSIS SECTION HILL AIR FORCE BASE, UTAH 84056

TABLE OF CONTENTS

Page Contents

PERFORMANCE WORK STATEMENT

Page

LIST OF TABLES

RECORD OF REVISIONS

ACRONYMS AND ABBREVIATIONS

AFGROW – Air Force Growth (crack life prediction software) AFI – Air Force Instruction AIS – Automated Information System ASIP – Aircraft Structural Integrity Program CAD – Computer Aided Design CDRL – Contract Data Requirements List CLIN – Contract Line Item CMRA – Contract Manpower Reporting Application COR – Contracting Officer’s Representative CP – Control Point DFARS – Defense Federal Acquisition Regulation Supplement DR – Design Review DTA – Damage Tolerance Analysis DTR – Damage Tolerance Rating ECR – Engineering Change Request FAR – Federal Acquisition Regulation FEM – Finite Element Model FSMP – Force Structural Maintenance Program FY – Fiscal Year GFI – Government Furnished Information GFM – Government Furnished Materials GFP – Government Furnished Property GFS – Government Furnished Software IAW – In Accordance With JEDMICS - Joint Engineering Data Management Information and Control System MAJCOMs – Major Commands MIL-STD – Military Standard MOD – Modification NDI – Nondestructive Inspection OEM – Original Equipment Manufacturer OSS&E – Operational Safety, Suitability and Effectiveness PCO – Procurement Contracting Officer PLM – Product Lifecycle Management PM – Program Manager PMR – Program Management Review PWS – Performance Work Statement RPDS – Reconfigured Post Desert Storm SE – Systems Engineering SLEP – Service Life Extension Program SOLR – Shutoff Overload Ratio SPO – System Program Office TCTO – Time Compliance Technical Order TDP – Technical Data Package TM – Technical Manual TO – Technical Order

1 Description of Services:

1.0 Purpose

The following Performance Work Statement (PWS) provides a general description of the required contractor services in support of the A-10 weapon system. The A-10 weapon system is managed by the Fighter Bomber (FB), A-10 System Program Office (SPO). This PWS defines A-10 Aircraft Structural Integrity (ASIP) legacy types of tasks required to keep the A-10 weapon system viable through 2030 and beyond.

1.1 Background

In January 2003, the A-10 System Program Office (SPO) ASIP engineering staff began a process to obtain a diverse engineering support team through strategic contracting and organic Air Force staff. This was initially accomplished with independent contracts leveraging expertise from two different contractors allowing for both on-site and traditional off-site support. These independent contracts were initially consolidated under the A-10 Prime and later Bridge contract vehicles. More recently, they were consolidated under the A-10 Thunderbolt Life-cycle Program Support (TLPS), which ended June 2019.

Since inception, this contractor/government team has evolved into a balanced technical force that captures the sustainment, legacy, and modernization aspects of A-10 weapon system support. Organic Air Force engineering is the sustainment leg of this arrangement and provides direction to contractors to address legacy and modernization needs.

Contractors provide the legacy and modernization support. This has proven to be efficient and flexible by allowing the organic Air Force team to support the depot activities and operating communities while contractors perform some of the longer term legacy and modernization ASIP engineering efforts. Further clarification of ASIP sustainment, legacy, and modernization definition and tasking efforts follow.

1.2 ASIP Sustainment Definition

ASIP sustainment is performed by organic Air Force engineering (the A-10 Chief Engineer, AFLCMC/WWAE and the Aging Aircraft Analysis Group within AFLCMC/WWAEJ). These tasks are specifically focused on Depot and Major Command (MAJCOM) support activities and providing vision for future ASIP requirements for the A-10. For the purposes of this document, ASIP SUSTAINMENT involves those activities necessary to ensure continued Operational Safety, Suitability and Effectiveness (OSS&E) per AFI 63-101/20-101 and the requirements of ASIP as outlined in MIL-STD-1530D. At minimum, the following responsibilities are associated with the ASIP sustainment function:

a) Providing leadership and vision to the ASIP team by balancing operational requirements with engineering assessments.

b) Integrating the findings from testing, teardowns, and analysis into requirements documented in MIL-STD-1530D and weapon system specific technical data.

c) Interacting with A-10 SPO leadership to secure the necessary resources to implement an effective ASIP.

1.3 ASIP Legacy Definition

ASIP legacy tasks will be performed by contract and will require legacy data and expertise. For the purposes of this document, ASIP LEGACY is defined as something resulting from, associated with, related to, and/or left behind by, the original development program for the A-10 aircraft. These tasks include but are not limited to A-10 engineering services that result in data deliverables and prototype deliverables associated with engineering services tasks within the scope of this PWS. At minimum, ASIP legacy tasks are generalized as follows:

d) Provide technical advisors as required to investigate and evaluate the background and circumstances concerning accidents/incidents of the A-10 weapon system.

e) Provide evaluations, and/or analysis, and/or repair designs, and/or testing, and/or prototype to support the requirements for ASIP and maintenance of OSS&E.

f) Attend and participate in meetings and conferences when unique A-10 specific engineering data and/or support are required.

g) Maintain and update the A-10 engineering database, including engineering drawings, processes, integrity documents, and source data.

h) Provide prototype with Technical Data Package (TDP) associated with engineering services within the scope of the PWS.

1.4 Scope

The scope of this PWS includes support for sustainment of weapon system operational safety, suitability, and effectiveness. This PWS allows the SPO to continue to contact the Original Equipment Manufacturer (OEM) by phone or email, cite the specific task order and task number, and receive rapid input from the OEM. This approach would maximize the A-10 SPO’s ability to ensure that the A-10 fleet meets availability, cost, and capability benchmarks required to satisfy its Air Force mission and remain viable to the end of the programmed life cycle. The tasks to be performed under this contract require LEGACY data and expertise where Legacy is defined in 1.1.2. These tasks include but are not limited to the following:

· Usage Survey/Assessment

· Loads Analysis

· Stress and Thermal Analysis

· Critical Area Analysis

· Spectra Development

· Fatigue Crack Nucleation and Durability and Damage Tolerance Analysis

· Durability and Damage Tolerance Testing

· Materials Testing

· Metallurgical and Failure Analysis

· Teardown Inspection

· Failure Analysis

· Test and Evaluation

· Individual Aircraft/Engine/Mechanical System Tracking

· Force Structure Management

· Software Application and Database Update and Development

· Probabilistic Analysis and Risk Assessment

· Structural Repair Support

· Flutter/Aeroservoelastic Analysis

· Structural Dynamics Analysis

· Engineering Test Support

· Non Destructive Inspection Development and Support

· Configuration Management

· Legacy and Modernization Data Retrieval

· New Wing Program Engineering Support

· Depot Support

· Technical Data Development and Validation

· Drawings and Processes

· Materials, Prototype and TDP Delivery

For tasks that require the contractor to provide written technical procedures, follow the instructions provided in Technical Manual Contract Requirements (TMCR) TM-86-01Q and applicable CDRL on the task order.

3 Government Furnished Property

3.0 Reports Provided:

The government will provide the contractor with all the necessary Technical Orders (TOs), Time Compliance Technical Orders (TCTOs), and any reports, required to accomplish the tasks as detailed in this PWS.

4 Security and Access to Government Facilities and Equipment

4.0 Security Clearance:

The efforts required for this task are UNCLASSIFIED and will not require contractor personnel to obtain a security clearance. Contractor personnel shall abide by all Air Force rules, procedures, and standard of conduct. Contractors requiring access to Air Force Automated Information Systems (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 the contractor personnel leave work on this project, they will return all access cards and base identification badges within five days.

4.1 Access to Government Facilities

Access to government facilities is limited. Therefore, the contractor shall coordinate the need, time, and personnel requiring access to government facilities with the PM, at least one week prior to need. The government PM or designated representative will coordinate between the contractor and base personnel as required.

4.2 Obtaining and Retrieving Base Identification

Contractors requiring access to government installations shall obtain the appropriate base identification for all contractor personnel who make frequent visits to or perform work at government sites. Contractor personnel are required to wear or prominently display installation identification badges or contractor-furnished identification badges while visiting or performing work on the installation(s). During performance of the contract, the contractor shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials for any employee who no longer requires access to the work site(s). Upon completion or termination of the contract or expiration of base identification, the contractor shall ensure that all base identification passes issued to contractor employees are returned to the appropriate issuing office.

4.3 Entry Procedures to Controlled or Restricted Areas

Contractor employees shall comply with local base procedures for entry into government controlled and restricted areas. If contractor employees require unescorted entry to controlled or restricted areas, the contractor shall comply with the Federal Installations Command Physical Security Plan and DoD Personnel Security Program, DoD 5200.2-R.

4.4 Procedures and Controls

The contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified information and to control distribution of controlled unclassified information IAW DoD 5220.22-M, National Industrial Security Program Operating Manual. All contractor facilities shall provide appropriate means of storage for controlled unclassified information and materials. All controlled unclassified information shall be appropriately identified and marked as For Official Use Only IAW DoD 5200.01, DoD Information Security Program: Controlled Unclassified Information Volume 4 (enclosure 3) and DoD 5400.7-R Freedom of Information Act Regulation Chapter 3. The contractor shall not store or transmit controlled unclassified information on personal information technology systems or via personal e-mail.

4.5 Cybersecurity

Cybersecurity (CS) is the discipline that protects and defends information and information systems by ensuring their availability, integrity, authentication, confidentiality, and non-repudiation. These measures include providing for restoration of information systems by incorporating protection, detection, and reaction capabilities. DoD Instruction 8500.01 establishes a DoD cybersecurity program to protect and defend DoD information and information technology. The contractor shall implement DoDI 8500.01 guidance for development of a cybersecurity strategy as defined below.

4.6 Network Security

The contractor shall take means (defense-in-depth measures) necessary to protect the availability, integrity, and confidentiality of government Controlled Unclassified Information (CUI) in the same manner as the contractor would protect its own unclassified company proprietary information IAW DoD Instruction 8582.01. The contractor shall safeguard CUI stored on non-DoD information systems to prevent the loss, misuse, and unauthorized access to or modification of this information. The contractor shall ensure that contractor-owned and operated unclassified information technology (IT) network assets (including assets used for contractor teleworkers) used to process sensitive government CUI are managed and maintained IAW commercial best practices, vendor-specific, or other nationally or internationally-recognized IT configuration and management standards.

4.7 Operational Security (OPSEC)

OPSEC requirements are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the contract. A critical information list will be provided by the government.

5 General Information

5.0 General Requirements

The A-10 aircraft is currently being managed with the benefit of both the experience and historical analyses available from the Northrop Grumman Corporation (NGC), the OEM. The goal of this effort is to provide vital and timely OEM support to the A-10 Aircraft Structural Integrity Program (ASIP). Scope of ASIP will include support for sustainment of weapon system operational safety, suitability, and effectiveness. OSS&E will benefit from the A-10 weapon system integrity analysis and support which is dependent upon multiple integrity disciplines to ensure weapon systems viability for the future. This PWS allows the government to contact the OEM by phone or e-mail, cite the specific task order, and receive rapid input from the OEM. General requirements for sustainment engineering are given in MIL-HDBK-514, “Operational Safety, Suitability, and Effectiveness for the Aeronautical Enterprise,” (Ref. 4, Attachment One). In addition, other key guiding documents that cover the integrity programs are JSSG-2006, MILSTD-1530D, MIL-STD-1798B, MIL-HDBK-515, and MIL-HDBK-87244 (Ref. Appendix One).

5.1 Specific Requirements

The contractor shall provide the appropriate engineering, program management, and technical services as required for this PWS. It is an objective of this program that the contract defines, as a minimum, the contractor’s support of the following United States Air Force (USAF) aircraft engineering activities:

5.1.1 Aircraft Structural Integrity Program (ASIP)

General guidance for the ASIP are given in JSSG-2006; more specific requirements are found in MIL-STD-1530D (Ref. 1 and 2, Attachment One). Engineering services for ASIP can include, but are not limited to: damage tolerance analyses (DTA), finite element modeling (FEM) and analyses, stress analyses, failure analyses, life predictions, risk assessment, environmental impact assessments (e.g., corrosion study), weight and balance assessments, flight loads data recorder (FLDR) programs, individual aircraft tracking programs (IATP), force structure maintenance and planning (FSMP) documentation, loads analyses, and general consultations. For establishing a baseline for ASIP and structures technical activities, some of the more recent (and core) documents are included at the end of this PWS (Ref. 7-12).

5.1.2 Structures

General requirements for structures are given in JSSG-2006 (Ref. 1, Attachment One).

Engineering services can include, but are not limited to: structural design, repair evaluations, classic stress analyses, FEM and analyses, failure analyses, special reviews/studies (e.g., bonded honeycomb evaluation, weight reduction study), part improvements (e.g., wing, horizontal tail), and general consultations.

5.1.3 Nondestructive Inspection (NDI)

Engineering services can include, but are not limited to: NDI improvement studies, methods developments, teardown analysis support, and general consultations.

5.1.4 Systems and Sustainment Engineering

General requirements for systems and sustainment engineering are given in MIL-HDBK-514 and MIL-HDBK-515 (Ref. 4 and 5, Attachment One). Engineering services can include, but are not limited to: systems analyses, fault tree analyses, single-point failure analyses, Functional System Integrity Program (FSIP) studies (i.e., maintenance related), and general consultations.

5.1.5 Failure and Metallurgical Analysis

Engineering services can include, but are not limited to: structural teardowns (e.g., wing, empennage, and horizontal stabilizer), scanning electron microscopy (SEM) evaluation, low-power microscope assessments, failure analysis support, and general consultations.

5.1.6 Material Properties Testing

Engineering services can include, but are not limited to: static testing, fatigue testing, crack growth testing, fracture toughness testing, and general consultations.

5.1.7 Component Testing

Engineering services can include, but are not limited to: wing testing, empennage testing, fuselage testing, built-up coupon testing, and general consultations.

5.1.8 Prototype and Technical Data Package Deliveries

The need for materials, manufacturing processes and prototype development may arise during Legacy VII order performance. This can include design, material procurement, development, manufacturing and fabrication processes, and producing and delivering a prototype of specified components. Validating the manufactured prototype and any revisions to the prototype or process deliverables shall be incorporated.

5.2 Delivery Requirements

All data deliverables in this PWS shall be formatted for import into the A-10 TeamCenter environment using the “A-10 Data Exchange Specification” 12-A10DOC-002. In addition, drawing deliverables shall also be formatted for import into the Joint Engineering Data Management Information and Control System (JEDMICS) using the Ogden Air Logistics Complex, Engineering, “Digital Delivery Requirements and Metadata Instructions”. Data delivery schedule/frequency requirements are found in the Contract Data Requirements List (CDRL) for each specific task. The Government will use an alpha prefix of “A” for CDRLs in the base period of the contract. The alpha prefix of “B” will be used for the CDRLs in the option period of the contract.

5.3 Digital Data, 2D Drawing and 3D CAD Modeling Requirements:

The contractor shall:

Meet the minimum requirements specified below in regards to digital data, 2D drawings and 3D CAD modeling deliveries and creation/updating.

All digital data deliverables in this PWS shall be formatted for import into the A-10 TeamCenter environment using the “A-10 Data Exchange Specification” 12-A10DOC-002. In addition, drawing deliverables shall also be formatted for import into JEDMICS using the Ogden Air Logistics Complex, Engineering, “Digital Delivery Requirements and Metadata Instructions”. Data delivery schedule/frequency requirements are found in the CDRL for each specific task.

All tasks requiring the updating or creating of 2D drawings with or without 3D CAD models shall be accomplished using one of the methodologies listed in the current revision of the “A-10 2D Drawing to 3D Model Migration Specification” 13-A10DOC-001. Each task shall identify the specific methodology to be used along with any other requirements pertinent to the task. For updating, creating, and/or migrating 2D drawings into 3D models, one or more of the current revision specifications listed below will be required by each methodology to ensure a complete and accurate engineering TDP.

a) 11-A10DOC-004- A-10 3-D Modeling Specification

b) 12-A10DOC-009 A-10 3D Model Validation Specification

c) 11-A10DOC-005-NX Drafting Specification (for CAD generated drawings/sheets)

d) A-10 Drawing Practice 08-A10DOC-001

The contractor shall include the AF in their internal TeamCenter electronic workflow process for all revised and/or created drawings and models. The contractor shall submit all drawings and models to the AF prior to release using their workflow process.

5.4 Support Requirements and Data Rights

5.4.1 Computer System Compatibility

All contractor work shall be fully compatible and usable when loaded onto A-10 assets.

The contractor shall maintain computer system compatibility with government computer systems operated in the AFLCMC/WWA. It should be noted that software is continually being upgraded, so any specific listing herein are given as examples:

a) PC platform

b) Microsoft Office Professional Edition

c) Excel

d) Word

e) PowerPoint

f) MSC.NASTRAN 2010

g) MSC.PATRAN 2010

h) JEDMICS

i) Air Force Growth (AFGROW)

j) Adobe Acrobat Professional

k) Adobe Acrobat Reader

l) Stress Check

m) Mathcad

n) CAD-Siemens

o) Product Lifecycle Management (PLM)-Siemens Team Center

p) Kestral

The contractor shall maintain compatibility with any other systems not listed above, but required for successful completion.

The government will provide contractor licenses and any other fees for the use of AFGROW during the period of performance of this contract.

5.4.2 Data Rights

All data generated under this PWS shall be developed for the A-10 with unlimited rights. All existing vendor proprietary data used in the execution of these tasks, such as trade studies, shall be marked with the appropriate distribution statement. The Government shall have unlimited rights to all intellectual property, material solutions or concepts, including all items, systems, processes, software and technical data developed by the Contractor and/or its subcontractors. The Contractor shall identify and receive written approval from the PCO prior to committing to the use of any privately developed items, components, processes, computer software and technical data which the Contractor intends to deliver with limited rights, Government purpose rights, or restricted rights. The government will receive unlimited/unrestricted rights to all data developed under this contract as defined in DFARS 227.7103-5 and DFARS 252.227-7013(a)(15). And despite DFARS 252.227-7013(f) all such documents shall be marked “unlimited rights’ as follows:

UNLIMITED RIGHTS

Contract No.

Contractor Name Contractor Address

The Government’s rights to use, modify, reproduce, release, perform, display, or disclose these technical data are unlimited No restrictions apply.

5.4.3 Configuration Management

The Contractor shall implement configuration management practices throughout the life of this effort which meet the requirements of the current A-10C Integrated Configuration Management Plan Doc No. 08-A10DOC-010 (Rev E or later). Comment by MICHELLE WARMOTH: Rich will look into this document

5.5 Contract Management

The Air Force Procurement Contracting Officer (PCO) shall be responsible for contract management. Only the PCO can make changes affecting this contract. Any instances where implied or explicit direction, received from any government representative and perceived by the contractor to affect performance of tasks 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. AFLCMC/WWA will provide the Government PM for this contract. The Government PM will provide the Contractor access to available technical data required to perform approved tasking. Only the PCO may approve any deliverable affecting the terms and conditions of the contract.

5.6 Program Updates and Meetings

The following types of program updates and meetings are to be supported by the contractor:

5.6.1 Kick-Off Meeting

A kick-off meeting shall be held within 30 days of task order award each year to discuss upcoming task order requirements and discuss the anticipated challenges with the tasks. The contractor shall provide a MSFT PowerPoint document as well as present minutes of the meeting in the most appropriate quarterly report.

5.6.2 Status Updates

Depending on the needs of a specific task order, monthly or quarterly status updates and information exchanges between the government and the contractor will be conducted. These interchanges can be accomplished via teleconferencing or by a face-to-face meeting. Unless otherwise arranged, minutes will be maintained by the contractor. For each task order, performance and cost reporting must be submitted monthly. The performance and cost reports shall provide current status and projected requirements of funds, man-hours, and work completion.

5.6.3 Program Reviews

The Contractor shall hold yearly PMRs, which can be included in the yearly task order kick-off meeting. The contractor shall present program status, parts status, technical and programmatic issues at PMRs.

5.7 Travel

Travel is required and estimated travel will be detailed in the task order. No authorization by the USG is required for travel, but all upcoming travel shall be discussed during the regular program status meetings. PCO can unilaterally add USG approval of travel at any time if deemed necessary.

5.8 Administration

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Department of the Air Force 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 PoP 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.

Reporting Period: Contractors are required to input data by 31 October of each year.

User Manuals: User manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.

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.

6 Integrated Management Support

6.0 Contractor Program Manager

For all tasks required by this PWS, the contractor shall identify and maintain a program manager. The contractor PM shall have a defined and direct line of authority and responsibility over all aspects of the work effort. The contractor’s work progress, status and any corrective action shall be documented (CDRL A001-A012).

6.0.1 Continuation of Essential DoD Contractor Services During Crisis:

In accordance with DODI 1100.22 (Dated 12 April 2010), this requirement is not considered mission essential.

6.1 Contracting Officer Representative (COR)

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

6.1.2 Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the Contracting Officer and not to the COR.

6.1.3 Management Objectives

The management objective is to allow the contractor the maximum flexibility to innovatively manage the program schedule, performance, risks, warranties, subcontracts, and data to produce engineering services that satisfy the USAF performance requirements. Another objective is to maintain clear government visibility into the program schedule, performance, and risk.

7 Appendices

7.0 Applicable Documents

7.0.1 Document Availability and Delivery

If the A-10 SPO/PM deems appropriate, the contractor may use other applicable documents. Also, the contractor shall request necessary documents from the A-10 PM, as required. In turn, the government shall supply all required TOs and TCTOs for the contractor to perform the tasks of this PWS.

7.1 Contractor Reporting

The contractor shall submit reports in accordance with the DIDs specified in DD form 1423 (CDRLs A001-A00C) with the following stipulations. Tables, figures, drawings, etc. shall be placed immediately following their reference in the main body of the text (i.e. same page if possible or on the next page).

APPENDIX ONE: LIST OF APPLICABLE DOCUMENTS

Department of Defense (DoD) Specifications

1) JSSG-2006, “Aircraft Structures,” 30 October 1998.

Department of Defense Standards

Other Publications

1) 06-A10DOC-6260 FSMP 2009 Rev B, Force Structural Maintenance Plan: Reconfigured Post Desert Storm Severe Spectrum.

2) SA220R0207 Rev D, Damage Tolerance Re-Assessment: Reconfigured Post Desert Storm Severe Spectrum.

3) A3G-2012-184383, DTA SOLR Determination Ground Rules.

4) TO 00-5-3, Air Force Technical Manual Acquisition Procedures.

5) TO 00-5-1, Air Force Technical Order System.

6) TO Process Plan. TM-86-01Q.

7) 220P09D409E, A-10 ASIP Master Plan

8) SA220R9401J, A-10 ASIP Report

9) CM220R0005, Teamcenter Linking Plan (Acquired at end of Legacy III – to be used as reference only.)

10) CM220R0006, Teamcenter Implementation Plan (Acquired at end of Legacy III – to be used as reference only.)

11) CM220R0007, A-10 SPO ASIP Gap Analysis (Acquired at end of Legacy III)

12) SA220R0474D, Summary of CP Stress Equations and RPDS Severe Spectrum Maximum Stresses

13) SA220R0501, Identification of Critical CPs and DTR Methodology Based on Cumulative Spectra.

14) A-10 PLM Data Exchange Specification (ADES) # 12-A10DOC-002.

15) A-10 2D Drawing to 3D Model Migration Specification # 13-A10DOC-001

16) A-10 NX Drafting Standard #11-A10DOC-005.

17) A-10 Drawing Practice #08-A10DOC-001.

18) A-10 No Strength Impact Allowance #13-A10DOC-002

19) A-10 3D Modeling Specification #11-A10DOC-004.

20) A-10 3D Model Validation Specification # 12-A10DOC-009.

Note: If the A-10 SPO/PM deems appropriate, the contractor may use other applicable documents.

image1.png