WSSA_PWS_7_April_14.pdf

PERFORMANCE WORK STATEMENT (PWS)

For

Weapon System Support & Analysis

7 April 2014

Prepared by:

A-10 Division Ogden Air Logistics Center

Hill AFB, Utah 84056 PR Number: FD2020-14-50544

REVISION RECORD

Revision Date Description Pages

LIST OF TABLES

Table 1 Support Equipment Roadmap Section Titles, Numbers, Content, and Schedule …………… 17 Table 2 CDRL with PWS Para references………………………….……………………………………… 30 Table 3 Projected Travel Requirements………………..………………...……………… Table 4 Services Summary…..……………………………………...………………………………………. 35

LIST OF APPENDICES

Appx Document Name Document Number

PWS

Reference Paragraph(s)

A AVSAP Project 3.1.2, 3.3.1

B Requirements Management Plan (RMP) 10-A10DOC-002 3.3.2

C System Engineering Plan (SEP) 09-A10DOC-006 3.3.2

D Architecture Management Plan (AMP) 10-A10DOC-001 3.3.2

E Modernization Sustainment Implementation Plan (MSIP) Presentation 3.1.2, 3.3.2

F OSS&E Baseline Document (OBD) 09-A10DOC-006APP 3 3.3.2

G Sustaining Engineering Program Technical Reference Handbook (SEPTR)

08-A10DOC-1074 3.3.2

H Engineering Handbook A-10 Engineering Handbook

3.3.2

I Software Drawing Matrix (SDM) 160D904000 3.3.2, 3.7.5

J Integrated Configuration Management Plan (ICMP) 08-A10DOC-010 3.3.2

K Reliability Maintainability Sustainability &Supportability

OI (RMS&S)

OI 21-11 3.3.2

L CM Technical Deficiency Correction Plan Spreadsheet 3.7.1, 3.7.2, 3.7.3, 3.7.6

M AWSME Interface Description Document (AIDD) 242A806 3.6.8

N Trigger Based Management (TBM) Power Point Briefing 3.6.5

O A-10 Support Equipment Roadmap (SER) 1 OCT 2013 3.5

P Electrical Loads Analysis (ELA) Database 3.6.10

Q Reserved

R Reserved

S Safety Requirements March 22,2012 5.8.1

T Travel Request Form TDY worksheet 5.7

U Requirements for Architecture System Engineering Tool PDF Doc 3.1.2

V De-Confliction Matrix OCT 2013 3.1.1

ACRONYM LIST

ACA Associate Contractor Agreement ACC Aircraft Combat Command ACO Administrative Contracting Officer AEDS A-10 Date Exchange Specification AFB Air Force Base AFI Air Force Instruction AFMC Air Force Material Command AHP Analytical Hierarchy Process AIS Automated Information System AMP Architecture Management Plan APOP A-10 Platform Obsolescence Plan ASRRC A-10 Aircraft System Requirements Review Conference AVCOM Advanced Component Obsolescence Management AVSAP Avionics System Architecture Plan AVSATA Avionics System Architecture Trade Analysis AVSIP Avionics System Integrity Program AWSME A-10 Weapon System Management Environment CAC Common Access Card CAF Combat Air Force CAS Common Allowance Standard CDRL Contract Data Requirements Lists CFR Code of Federal Regulations CM Configuration Management ICMP Integrated Configuration Management Plan CORE System Engineering and Architecture Development Tool COTR Contracting Officer Technical Representative DAL Data Accession List DFARS Defense Federal Acquisition Regulation Supplement DID Data Item Description DMS Diminishing Manufacturing Sources DMSMS Diminishing Manufacturing Sources and Materiel Shortages DoD Department of Defense DODAF Department of Defense Architecture Framework DODI Department of Defense Instruction DOORS Dynamic Object-Oriented Requirements System ELA Electrical Loads Analysis EMD Engineering and Manufacturing Design ERP/APS Enterprise Resource Planning/ Advanced Planning & Scheduling EWS Electronic Warfare System FTP File Transfer Protocol GEIA Government Electronics & Information Technology Association GFI Government Furnished Information GFM Government Furnished Material GFS Government Furnished Software IAW In Accordance With ICD Interface Control Document; Initial Capabilities Document IMP Integrated Master Plan IMS Integrated Master Schedule IPT Integrated Product Team IT Information Technology JCIDS Joint Capabilities Integration and Development System

J-RAMS Joint Reliability Availability Management System LCSE Life Cycle Systems Engineering LCSP Life Cycle Sustainment Plan LRU Line Replaceable Unit MECSIP Mechanical Equipment and Subsystems Integrity Program MICAP Mission Impaired Capability Awaiting Parts MRO Maintenance, Repair and Overhaul MSD Material Support Division MSR Monthly Status Report No. Number NSN National Stock Number OA Operational Assessment OBD OSS&E Baseline Document OSHA Occupational Safety and Health Administration OSS&E Operational Safety, Suitability and Effectiveness OUE Operational Utility Evaluation PC Personal Computer PCO Procuring Contracting Officer PEM Program Element Monitor PLM Product Life Cycle Management PLMi PLM Initiative PM Program Manager; Program Management PMR Program Management Review POM Program Objective Memorandum PWS Performance Work Statement QASP Quality Assurance Surveillance Plan REMIS Reliability & Maintainability Information System RMP Requirements Management Plan RMS & S Reliability, Maintainability, Sustainability, and Supportability SE Support Equipment SEGP Support Equipment Generation Plan SEP Systems Engineering Plan SEPTR Sustaining Engineering Program Technical Reference SER Support Equipment Roadmap SIPRNET Secret Internet Protocol Router Network SPO System Program Office SS Services Summary TBM Trigger Based Management TCTO Time Compliance Technical Order TIM Technical Interchange Meeting TLPS Thunderbolt Life-cycle Program Support TO Technical Order WEPTAC Weapons and Tactics Conference WSMT Weapon System Management Tool WRP Wing Replacement Program

Table of Contents

1.0 INTRODUCTION …………………………………………………………………………………. 5

1.1 Purpose ……………………………………………………………………………………………. 5

1.2 Background ……………………………………………………………………………………….. 5

1.3 Scope ……………………………………………………………………………………………… 5

2.0 APPLICABLE DOCUMENTS ………………………………………………………………… .. 6

2.1 DoD Document …………………………………………………………………………………… 6

2.2 USAF Publications ……………………………………………………………………………….. 6

2.3 Other ………………………………………………………………………………………………. 7

3.0 CONTRACTOR TASKING/REQUIREMENTS ………………………………………………. 8

3.1 Systems Engineering Based Integrated Management……………………………………… 8

3.2 Requirements Management Software Licensing and Installation…………………………… 13

3.3 Engineering Baseline Maintenance ……………………………………………………………..13

3.4 A-10 Platform Obsolescence Plan ………………………………………………………………15

3.5 Support Equipment Roadmap …………………………………………………………………..16

3.6 Weapon System Management Environment Engineering Services Requirements ……... 20

3.7 Aircraft Configuration Technical Support ….………………………………………………… 23

3.8 Program and Engineering Management Support …………………………………………… 25

3.9 Data ……………………………………………………………………………………………... 26

3.10 Operational Utility Evaluations …………………………………………………………………27

4.0 DELIVERABLES (CONTRACTOR DATA REQUIREMENTS LIST) ……………………. 30

4.1 Government Inspection and Acceptance of Deliverables …………………………………. 31

5.0 ADMINISTRATIVE ……………………………………………………………………………. 31

5.1 Subcontract Management……………………………………………………………………… 31

5.2 Associate Contractor Agreements…………………………………………….………………. 31

5.3 Contractor Manpower Requirements …………………………………………………………. 32

5.4 Classified Material and Gov't Computer Access ………………………………………………33

5.5 Security…………………………………………….……………………………………………….33

5.6 Government Furnished Information, Equipment, Materials and Software…………………. 34

5.7 Travel Requirements………………………………………………………………………………34

5.8 Safety Requirments………………………………………………………………………………..35

5.9 Computer System Compatability Requirements………………………………………………..35

5.10 Ozone Depleting Compounds……………………………………………………………………35

6.0 SERVICES SUMMARY (SS) …………………………………………………………………….35

6.1 Service Summary Table…………………………………………………………………………. 35

6.2 Government Quality Assurance Surveillance ………………………………………………… 37

6.3 Contractor Quality Assurance Requirements ………………………………………………… 37

6.4 Methods of Surveillance ………………………………………………………………………… 37

7.0 STATEMENT OF MISSION ESSENTIAL SERVICES ……………………………………

1.0 INTRODUCTION

1.1 Purpose

The purpose of this effort is to obtain task based systems engineering services that include analysis, engineering and management processes and tools to facilitate the role of the A-10 System Program

Office (SPO) to perform system integration. The A-10 SPO requires Contractor provided analysis and tools to accurately assess, track and prioritize modernization and sustainment requirements, devise and implement integration strategies to achieve the highest attainable level of congruity between all A-

10 aircraft programs. This requires performing dedicated analytical and systems engineering tasks to identify and resolve technical deficiencies, program conflicts, duplicative efforts and inefficiencies to insure that the most efficient weapon system performance and integrated platform configuration management are accomplished to support the A-10 Weapon System.

1.2 Background

The current and anticipated dynamic battlefield environments drive many modernization and sustainment changes to the A-10 legacy aircraft and creates unique requirements to maintain the A-10 as an effective and viable weapon system throughout its life cycle. Modifications affecting all A-10 functional areas and interfaces to include mechanical, structural, electrical, avionics, weapons, support equipment and operational flight programs (OFP), continue to evolve at an unprecedented pace.

Employing experienced, effective and efficient systems engineering and integration practices is crucial to successfully identify and adjudicate the many conflicts associated with executing numerous simultaneous modification and sustainment programs. The systems engineering and integration tasks, defined herein, are critical in supporting the A-10 weapon system and in facilitating the role of the A-10

SPO as a highly successful prime integrator. They will insure that the A-10 fleet remains a viable part of the cohesive, ready, and agile fighting forces that the Air Force, the Joint Force Commander, and the

Nation require.

The goal of the new A-10 SPO Process, System Design and Implementation Support services is twofold:

a. Refine/Develop, map and document standard logistics/engineering processes and procedures and their information technology interfaces for the sustainment of the A-10 in the AF inventory.

b. Further develop standard engineering processes and policy (tools, templates and training) for efficient future acquisition and sustainment of the A-10 aircraft.

1.3 Scope

The efforts described in this PWS establish the systems engineering tasks required to support the A-10

SPO in meeting the needs of the war fighter in a timely and cost effective manor. The objectives and requirements for subject engineering tasks are to facilitate technical analysis required for the A-10 SPO to accomplish efficient integrated systems engineering. Integrated systems engineering is defined as the overarching disciplined and systematic engineering practices that maximize the effectiveness of modernization and sustainment funding to increase weapon system capabilities, reliability, and availability. The over all goal of integrated systems engineering is to most cost effectively keep the A-

10 a viable platform in executing its missions over its lifecycle. To facilitate integrated systems engineering and the A-10 SPO’s role as the system/prime integrator, the tasks in this PWS include identifying new and developing technologies that can support the accomplishment of A-10 missions and either eliminate or minimize operational and/or sustainability gaps. These efforts will help the A-10

SPO meet Air Force goals to deter and defeat adversaries with a credible first look, first shot, first kill capability and to modernize the capabilities of the A-10 fleet to reduce operating costs while attaining desired effects with greater persistence, survivability, longer range, and more versatile payloads.

2.0 APPLICABLE DOCUMENTS

These documents form a part of the proposed work only to the extent they are referenced in the main body of the PWS. In the event that a contradiction between the following documents and this PWS occurs, the order of precedence will be this PWS and then the referenced documents.

2.1 DoD Documents

a. Chairman of the Joint Chiefs of Staff Manual, CJCSM 3500.02A, 17 May 2011

b. Chairman of the Joint Chiefs of Staff Manual, CJCSM 3500.04F, 1 June 2011

c. CJCSI 5705.01 Series, “Standardization of Military and Associated Terminology”

d. DoD 8570.1-M, Information Assurance Workforce Improvement Program

e. DoD Architecture Framework (DODAF) 2.0, 28 May 2009

f. Joint Capabilities Areas, JCA 2010 Refinement Doc. 8 April 2011

g. Joint Capabilities Areas, JCA, Taxonomy Spread Sheet

h. METLS, JETLS A-10 Requirements Summary Spread sheet

i. DOD Instruction 5025.12, 14 Aug 2009, “Standardization of Military and Associated Terminology”

j. Joint Publication 1-02, 17 October 2007 (amended 30 September 2010), “Department of Defense

Dictionary of Military and Associated Terms”

k. OSS&E and LCSE, MIL_HDBK-514

l. Defense Standardization Program Office, publication SD-22 “Diminishing Manufacturing Sources and Material Shortages”, September 2010 or later

m. DoD DMSMS Guidebook 4-7-05

n. MIL-STD-3018 “Parts Management”

o. Government Electronics & Information Technology Association (GEIA) STD-0016, the new DoD standard for all DMSMS programs.

2.2 USAF Documents

a. AFDD 3-01 Couterair Operations, 1 Nov 2011

b. AFDD 3-03 Counterland Operations, 28 Jul 2011

c. AFDD 3-04 Countersea Operations, 26 Oct 2010

d. AFDD 3-05 Special Operations, 28 Jul 2011

e. AFDD 3-50 Personnel Recovery Operations, 1 Nov 2011

f. AFI 63-101, Integrated Life Cycle Management, 7 Mar 2013

g. Reserved

h. AFI63-131, Modification Program Management, 6 Nov 2009

i. AFMCI 23-103 Diminishing Manufacturing Sources and Materiel Shortages (DMSMS), 13 Oct 2000

j. AFMCI 63-1201, Implementing OSS&E and LCSE, 14 Oct 2009

k. AFPAM 63-128, Guide to Acquisition and Sustainment Life Cycle Management, 5 Oct 2009

l. AFPD 10-9, Lead Command Designations and Responsibilities for Weapon Systems, 8 Mar 2007

m. AFPD 33-4 Enterprise Architecting, 6 July 2010

2.3 Other Reference Documents

a. 508 ASW OI 62-03, Mechanical Equipment and Subsystems Integrity Program MECSIP), A-10

MECSIP Master Plan, NG-0212-A10-00030007-11-PLN-a, latest version

b. 508 ASWMOI 63-21, Engineering Requirements Management Plan, 16-ct-2007

c. A-10 Avionics System Architecture Roadmap Doc. No.08-A10DOC-1084

d. A-10 DODAF 2.0 Architecture

e. A-10 Drawing Practices document, 08-A10DOC-001, Latest Rev.

f. 08-A10DOC-010, A-10 Integrated Configuration Management Plan, Latest Rev.

g. A-10 OI 63-21, 1067 Process Management

h. A-10 Selected missions requirements from METL, etc. Spreadsheet

i. Architecture Management Plan (AMP), 10-A10DOC-001, (W9133-A004-0001A), Oct 2012

j. Architecture Status Final Report, W9133-A004-0010A, Oct 2012

k. ASC Guide to Technical Reviews/Audit for Aeronautical Weapon System Acquisition

l. ASW 21-01, ASW System Engineering Management

m. Baseline Architecture Final Report, W9133-A008-0008, 6-Nov-2012

n. Functional Architecture Description Document, W9133-A008-0004B, OCT 2012

o. ICD, Draft, W9133-A004-0007A, NOV-2012

p. Physical Architecture Description Document, W9133-A008-0005B, OCT 2012

q. Requirements Leveling, W9133-A007-0005A, SEPT 2012

r. Requirements Management Plan (RMP), 10-A10DOC-002, (W9133-A004-0006A), OCT 2012

s. Technology Insertion Final Report, W9133-A008-0007A, NOV-2012

t. A-10C Operational Viability and Sustainment Gap Analysis Report

u. A-10 Electronic Warfare System Capabilities Description Document

v. Planned OUEs

w. Background Paper ON A-10 Weapon Systems Diminishing Manufacturing Sources and Material

Shortages (DMSMS) Program

x. 12-A10DOC-010, A-10 TeamCenter Implementation Strategy Plan, Latest Rev

y. A-10 3D Modeling Specification 11-A10DOC-004

z. MECSIP ASW OI 62-03

aa. A-10 NX Drafting Specification 11-A10DOC-005 (for CAD generated drawings/sheets)

bb. A-10 Avionics System Segment Specification (AS3) Draft, 4 Jun 2013

cc. A-10 Suite 7B reference documents including the A-10 Weapon System Specification (WSS), the

A-10 Prime Item Development Specification (PIDS), both Rev. E, and the other 7B related System

Segment Specifications, etc. provided as GFI

dd. OBOGS Modification Drawings and Documents provided as GFI

ee. A-10 Product Lifecycle Management (PLM) Data Exchange Specification 12-A10DOC-002

ff. A-10 3D Model Validation Specification 12-A10DOC-009

gg. System Engineering Plan (SEP) 09-A10DOC-006

hh. 08-A10DOC-001 Drawing Practices

ii. A-10 Engineering Handbook, 22 Jul 10

jj. SEPTR Sustaining Engineering Program Technical REF Handbook

kk. A10 2D Drawing to 3D Model Migration Specification 13-A10DOC-001

ll. 11-A10DOC-004 A-10 3-D Modeling Specification

mm. PLM Data Exchange Specification 12-A10DOC-002 C

nn. AvSATA ll HARS Replacement OA Final Presentation

oo. AvSATA ll HARS Replacement OA Final Report

3.0 CONTRACTOR TASKING/REQUIREMENTS

The Contractor shall audit, analyze, correct and update products to include A-10 Architecture, A-10

Weapon System Management Environment (AWSME) Products and Views; as well as all documents called out in sections 3.1- 3.7 to include the following as applicable to the individual product, architecture view or document to include:

a. The most current description of ongoing A-10 programs

b. The most current organizational charts, office symbols, locations, personnel names, and phone numbers

c. The most current valid versions of all specifications, directives, Operational Instructions (OIs), policy and guidance document references

d. The most current versions of all delegation authority letters, Memorandum of Agreements (MOA) and Service Level Agreements (SLA)

e. All links and pointers are current and functioning properly from Government computers

f. Formatting is consistent within documents, products and views

g. Internal cross references in each document to the other corresponding documents are correct

h. Common and correct terminology is used in all products, architecture views and documents throughout all deliverables

3.0.1 Delivery Requirements

All non-classified 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.

3.0.2 2D Drawing and 3D CAD Modeling Requirements

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 “A-10 2D Drawing to 3D Model Migration

Specification” 13-A10DOC-001. For each task the Contractor shall identify the specific methodology to be used along with any and all other requirements pertenant to the task. For updating, creating, and/or migrating

2D drawings into 3D models, one or more of the specifications listed below will be required by each methodology to ensure a complete and accurate engineering TDP.

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

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

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

A-10 Drawing Practice 08-A10DOC-001

3.1 Systems Engineering Based Integrated Management

Historically, the A-10 community has discussed, defined, and prioritized capability gaps, requirements and sustainment deficiencies annually at the A-10 Aircraft System Requirements Review Conference

(ASRRC), the combined Air National Guard (ANG) and Air Force Reserve Command (AFRC) Weapons and Tactics Conference (WEPTAC) and the Combat Air Forces Weapons and Tactics Conference

(CAF WEPTAC). Due to organizational changes and other considerations the names of these meetings may change over the next five years. Regardless of the names, the goals of these equivalent meetings are the same. This PWS uses the current names with the understanding that the names may be different over the period of performance of this contractual effort, but the intent and requirements in this PWS remain the same. The Contractor shall perform a comprehensive integrated risk analysis for all current and any anticipated programs by performing the tasks in this section.

3.1.1 De-confliction Matrix Analysis

The Contractor shall:

Gather programs information, format, then populate, update, validate, and analyze the A-10 de-confliction matrix for all A-10 System Program Office (SPO) programs. The matrix shall be used to show the potential conflicts between all on-going efforts, as well as proposed solutions. Conlficts are defined but not limited to, the use of indentical wiring harnesses, circuit breakers, installation areas for all devices including paths for harnnesses, Ethernet addresses and switch ports, 1553 buss addresses and couplers, and RF bandwidths, etc.

Automate the process to automatically note and identify conflicts. This would include such things as writing simple macros to compare each field (d.-p. below) for duplicate (conflicts) entries.

Analyze and compare all of the items in a- p below to determine conflicts, duplicate efforts, or impacts to or with the same support equipment, T.O.s, and other items in the list. The matrix shall be based on the current A-10 de-confliction matrix and include as a minimum, the ability to determine confliction of the following items (CDRL A004):

a. Prime Contractor

b. Status of Modification

c. Description of Modification – provide a brief summary

d. Panel/Bay # - identify panel and bay impacted by mod

e. Weight and CG Impact – identify net weight increase/decrease and CG resulting from mod

f. Structural – air frame, panels, skins, mounting brackets, etc.

g. Mechanical – hydraulic, landing gear, actuators, life support, etc.

h. LRU – names and type added, modified and removed

i. Avionics – processor throughput, bus bandwidth, memory, EMI/EMC, etc.

j. Power – delta power usage of equipment removed and/or equipment installed; positive number indicates a net power increase, negative number indicates a power increase

k. Firmware – identify changed, modified or new firmware

l. Software – identify/describe changes to OFP and test equipment

m. Wiring Harness – identify new and modified harnesses

n. Bulkhead/Inline Disconnects – identify by name/# or state none

o. Circuit beaker used

p. Ethernet addresses and switch ports

3.1.2 Avionics System Architecture Integration, Updates and Support

A significant portion of the A-10 allocated baseline is the applicable A-10 DODAF 2.0 architecture compatible views and related information. The views make up the architecture which is a system engineering tool used to track and trace A-10 requirements, identify and track requirement gaps and technical deficiencies as well as to perform systems engineering tasks. One of the most important applications of the requirements gap tracking is to unequivocally tie requirement gaps to mission requirements in order to clearly justify obtaining funding for sustainment and modernization. Several gaps and deficiencies remain to be corrected in the architecture in order to fully apply it as a systems engineering and integration tool.

The A-10 SPO previously used and evaluated Rhapsody and System Architect as potential systems engineering and architecture tools for the A-10. Neither tool was deemed optimal for managing A-10 requirements. As a result, the architectures built in those tools were transferred to another system engineering and architecture development tool called CORE. The A-10 architecture built with and in

CORE consists of an operational, a functional and a physical architecture. All of these architectures require regular updates and corrections to stay viable systems engineering tools. This includes, but is not limited to, identifying and correcting missing or incomplete sections, gaps and deficiencies in all three under lying architectures within the A-10 architecture itself. The tasks in this paragraph focus on identifying, tracking and eliminating gaps and deficiencies both within these architectures themselves and more importantly, within the A-10 weapon system. The intended use of these architectures is as system engineering tools to facilitate the role of the A-10 SPO as prime integrator.

This task involves correcting known gaps and deficiencies in the architecture identified below as well as identifying unknown technical and operational gaps and deficiencies. The Contractor shall review current architecture and requirements products and:

3.1.2.1 Genesys Architecture Database Tool Analysis:

a. Using the Requirements for Architecture System Engineering Tool in Appendix U and the requirements in the following paragraph, accomplish an in-depth analysis as described in 1 – 5 below of the latest available version of the Genesys architecture database tool capabilities.

1. Compare the Genesys architecture database tool capabilities and constraints with

CORE version 8.0 or later with respect to current architecture content, functionality, relationships.

2. Show that the current A-10C architecture information and structure, references and links from lower levels currently also shown in higher levels are automatically maintained when transferring architecture data from CORE to Genesys.

3. Determine feasibility, time, and cost for transferring the A-10 CORE V9.0 or later version of the A-10 architecture into Genesys to include all of its current functionality and future needs of the A-10 architecture and systems engineering requirements.

4. Determine and demonstrate Genesys’ ability to provide readable block diagrams as documented in paragraph 3.1.2.2a below.

5. Clearly demonstrate and compare functionality, uses and constraints using both tools with the A-10 operational, functional, and physical architectures. (CDRL A004, A008)

b. If a determination is made to migrate to Genesys (upon Government approval) based on the results of paragraph 3.1.2.1a, the requirements identified in paragraph 3.1.2.3 a-k below shall be performed in the Genesys architecture database tool.

3.1.2.2 Alternate Database Tool Determination:

a. If it is determined that the current or the next release of Genesys cannot cost effectively meet the architectural and systems engineering requirements of the A-10 weapon system per paragraph

3.1.2.1, and upon approval by the Government, analyze other current commercially available

DODAF 2.0 or later compliant architecture tools (excluding Rhapsody and System Architect).

b. If a determination is made to migrate to an alternative architecture database tool (upon

Government approval), the requirements identified in paragraph 3.1.2.3 a-k below shall be performed in the selected architecture tool.

3.1.2.3 Architecture Updates, Integration and Support: The requirements identified in a-k below shall be performed utilizing CORE V9.0 or later.

a. Update and publish all the currently used views with block diagrams with the improvements made in CORE V9.0 or later. (CDRL A004, A007) Block diagrams views include the ability to:

1. Select which blocks will be displayed in a particular view for all diagram views.

2. Select the color of individual blocks or groups of blocks, or otherwise improve the readability of the graphics generated in the architecture views provided to the users.

3. Select which connections or paths are displayed in a particular view.

4. Combine multiple connections into one nameable connection.

5. Edit the paths of specific connections so that they do not run on top of each other.

b. Evaluate the weapons requirements in the A-10 SV-8 and SV-9 and all other sources as required to determine all related requirement gaps and the need to update the A-10 Electronic Warfare

System (EWS) CDD or A-10 SPO approved equivalent. If required, update the A-10 EWS CDD or current A-10 SPO approved equivalent. This will require maintaining two separate baseline architectures, one that can be accessed without a security clearance and one that can only be accessed with a security clearance. The architecture that includes the EWS is classified and must be stored accordingly and separately from the non-classified baseline architecture that does not include the classified portions of the EWS. (CDRLs A004, A008)

c. Identify technical and operational gaps and deficiencies, recommend and implement solutions that support full requirement gaps and deficiencies traceability from A-10 architecture products through to the Avionics System Segment Specifications (AS3), A-10 end item specifications, interface documents, and design and development documents. This will require the improvement of the process and writing additional scripts within the architecture database tool to detect, clearly identify, and organize requirements gaps. (CDRLs A004, A008)

d. Analyze, identify, improve or create new views, implement and demonstrate specific views requirements among the A-10 stakeholders to ensure that the architecture supports the stakeholders’ needs and requirements. (CDRL A004, A007) The stakeholders, listed below, are:

1. MAJCOM requirements views for requirements traceability to support and justify funding requests.

2. Program Management programmatic views for hardware modification milestone and related views.

3. A-10 SPO and 309th systems engineering for OA and OUE for temporary hardware modifications related views.

e. Identify new requirements gaps and technical deficiencies from both of the annual WEPTACs and

ASRRC prioritized requirements, and ensure the definitions are clearly defined, accurate, complete, compatible and easily found and accessed within the architecture baseline data contained in the database tool architecture databases, the associated views, and their DOORS and HTML outputs. (CDRLs A007, A008)

f. Generate the Suites 8, 9, and 10 architecture views including importing or generating the required data from and/or to the respective AS3, Hardware System Segment Specifications (HS3) and

Electrical Interface Control Documents (EICD) information in compliance with DoD Architecture

Framework (DODAF) 2.0. (CDRL A008)

g. Identify and generate architecture baseline content for planned OAs and OUEs in conjunction with the 309th Software Maintenance Group and/or the applicable Contractor. “Consumer” architecture content is defined as those views and products (and the underlying architectural data) that are required to facilitate the most efficient development and implementation of hardware and software

OA and OUE candidate solutions as part of the OA, OUE or similar efforts by the 309th Software

Maintenance Group and/or Contractor. These views will be subsets of the views needed to facilitate the Joint Capabilities Integration and Development System (JCIDS) process as part of the permanent modification process. (CDRL A008)

h. Evaluate A-10 mission applicable emerging commercial technology at the Air Force Research

Laboratory (AFRL), Defense Advanced Research Project Agency (DARPA) and with Aerospace defense industry projects and consortiums. Analyze the A-10 avionics system and the Avionics

Roadmap for limitations, technical deficiencies and gaps that could be corrected with the insertion of the applicable emerging technologies. (CDRLs A004, A008)

i. Develop reports recommending plans to correct existing (A-10C Operational Viability and

Sustainment Gap Analysis Report 2013 or most recent analysis accomplished during the POP of this contract) and newly identified (WEPTAC, ASRRC, any UNRs or UONs and any sustainment issues identified during the Period of Performance (POP) of this contract effort) requirement gaps and technical deficiencies based on specific new or existing technologies to improve the reliability, maintainability, and sustainability of the avionics system and provide for continued viable operational capabilities. These reports and plans shall detail available solution sets and provide recommended solutions, taking into account A-10 architectural requirements and AVSAP goals and include expanded and updated SV-8 Systems Evolution Description (Roadmap) and SV-9

Systems Technology and Skills Forecast views from the current and recommended A-10

Architecture. The reports shall also include white paper explanations, program planning materials, etc., that support the required market research, sustainment planning, requirements refinement, and Rough Order of Magnitude (ROM) estimates for budget planning to accomplish the recommended activities. (CDRL A004, A008)

j. Analyze and strategize modifications in the SV-8 developed paragraph i. above and identify the potential combination of multiple programs into a single release cycle including affected OFPs, flight tests, etc. The analysis and the recommended combination of modifications shall be based on cost reduction and other criteria to be provided by the A-10 SPO. (CDRL A004)

k. Accomplish a systems engineering review across all deliverables to include a final report summarizing all efforts with an Architecture Status report and a common acronym list, to insure accuracy, completeness, common use of terminology, common use of versions of all referenced views and content, A-10 missions, etc., for and throughout every deliverable. For example, the

SV-8 and SV-9 must align with the MSIP, etc. All common efforts and programs mentioned in any report, view, etc., must use common names, terminology, and references. Also analyze and recommend what, if any, reports can be effectively combined to minimize duplication of effort and reduce the overall number of reports. (CDRL A004)

3.2 Requirements Management Software Licensing and Installation A-10 SPO engineering uses database tools for systems and sustaining engineering. These tools include, but are not limited to, DOORS and CORE. It is anticipated that the A-10 SPO will begin using a new database systems engineering tool called Genesys over the next few years. The Contractor shall purchase the licenses to these database tools for their own use in order to perform all tasks in this

PWS. The Contractor shall also purchase the licenses to these database tools and install them on identified Government computers (maximum of 2). The A-10 WSSA program manger will identify the

Government computers to the Contractor. The Contractor shall ensure the Government can check and use architecture deliverables per the following:

a. Update and support proper function of one Government owned DOORS database licensed application once annually to the most current version available during the first 8 months of each year of the contract. Contractor shall purchase one DOORS license for their own use in order to perform all tasks in this PWS.

b. Update and support proper function of one Government owned CORE licensed data based application once annually to the most current version available during the first 10 months of each year of the contract. Contractor shall purchase one CORE license for their own use in order to perform all tasks in this PWS.

c. Ensure all software is running properly on the selected Government computer(s) (maximum of 2) and that the computers have access to the latest and correct version of the A-10 requirements

DOORS database, the CORE and if approved by the Government Genesys or other new tool based A-10 System Architectures. Contractor shall purchase the one Genysys (or new tool) license for their own use in order to perform all tasks in this PWS.

d. Coordinate these installs with the Government base IT for assistance and approval. (CDRL A007)

3.3 Engineering Baseline Maintenance

3.3.1. Avionics System Architecture Baseline Maintenance

The Contractor shall analyze, maintain, and ensure the accuracy, completeness, consistency, interoperability, common terminology usage within and between each deliverable listed below and facilitate the signature process. In addition, the Contractor shall ensure the availability of the most current versions of the A-10 Avionics Roadmap, Avionics System Architecture Program (AVSAP), see

Appendix A, and A-10 architectural products to the A-10 community in AWSME and as requested by the Government.

The Contractor shall:

a. Validate the completeness and accuracy of the A-10 System Architecture, to include the operational, functional and physical architectures applicable views and products for Suite 8, 9, and 10 software and hardware changes to match WSS Rev E/PIDS Rev E/ or latest versions in compliance with DoD Architecture Framework (DODAF) 2.0. (CDRLs A004, A008)

b. Analyze the A-10 Architecture products and views, identify and correct technical deficiencies to ensure the correct flow down and traceability of requirements from the latest versions of

METLS, JETLS, Chairman of the Joint Chiefs of Staff Manual, CJCSM 3500 series, the A-10 related taskson the AF Task list, documents referenced in paragraph 2.1 b. – g. and 2.2 a. – e., to the current A-10 operational JCIDS and ACC/A8A10 to program level, and from program level to technical requirements in the physical architecture. All source documents called out in this paragraph shall be accessible from the external documents section of the HTML version of the architecture. (CDRLs A004, A008)

3.3.2. Baseline Documents Updates

The Contractor shall review, analyze, update, maintain and ensure accuracy, completeness consistency, interoperability, common terminology usage and integration within, between and throughout each deliverable in the following Systems Engineering documents per the A-10 Integrated

Configuration Management Plan and A-10 SPO engineering processes:

a. A-10 Modernization and Sustainment Investment Plan (MSIP)

The Contractor shall update the A-10 MSIP to capture current and future requirements gaps to ensure the continued operational viability of the A-10 weapon system. Using the results of the latest A-10 Capabilities Based Assessment (CBA) and Gap Analysis or results of ASRRC requirements analysis, the Contractor shall develop and provide an updated Analytical Hierarchy

Process (AHP) framework for evaluating and prioritizing hardware and software requirements.

This task includes coordination with ACC, the SPO, associated Contractors, and the appropriate test agencies on the candidates/initiatives to be rated at the annual ASRRC, and then facilitate the voting session at the ASRRC using decision support tools, compile results and conduct a sensitivity analysis of those results for hardware, software, and support equipment candidates as requested. At the conclusion of the ASRRC, provide a Deficiency Mitigation and Fiscally

Unconstrained Candidate Prioritization that will include prioritized lists of hardware, software and support equipment candidates that are fiscally unconstrained (ranked irrespective of cost) for both

Maintenance and Operations working groups. (CDRL A004).

b. Post ASRRC, update and provide a Deficiency Mitigation and Fiscally Constrained Candidate

Prioritization. The Contractor will coordinate with the Program Office and ACC to gather programmatic data (cost, risk, dependencies, exclusions, etc.) of the hardware candidates rated at the ASRRC. The Contractor shall perform optimization to faciliate a fiscally constrained priority listing of candidates. (CDRL A004).

c. Provide Program Objective Memorandum (POM) Presentation Support - The Contractor shall update and prepare presentation materials that summarize the results and provide “what if” scenarios for the ACC Requirements Officer’s POM presentation over the POP of the contract.

The presentation will delineate A-10 requirements and the basis for funding support needed to implement the developed investment strategy. (CDRL A004)

d. A-10 Systems Engineering Plan (SEP)

The Contractor shall accomplish a review/update of the A-10 SEP or similar document for coordination, approval and signatures by the A-10 Chief Engineer, System Program Manager

(SPM) and AFLCMC Fighter/Bomber PEO. Updates to the SEP shall be in accordance with (IAW)

AFI 63-101, 7 Mar 13.

e. A-10 Sustaining Engineering Program Technical Reference (SEPTR), 08-A10DOC-1074, Rev. 4.0 or latest version

f. A-10 Thunderbolt II (Warthog) Engineering Handbook, 8 Jul 10

g. A-10 Top Level Software Drawing Matrix (SDM) or A-10 SPO approved equivalent 160D904000, Rev. B

h. A-10 Integrated Configuration Management Plan (ICMP) 08-A10DOC-010

i. A-10 Architecture Management Plan (AMP), 10-A10DOC-0001, 27 Jan 2012 or later

j. A-10 Requirements Management Plan (RMP) 10-A10DOC-0002, 18 May 2011 or later

k. A-10 Reliability, Maintainability, Sustainability, and Supportability (RMS&S) Operating Instruction

(OI) (to include format requirements for APOP data)

l. A-10 Platform Obsolescence Plan (APOP)

The Contractor shall accomplish a review/update of the APOP developed in paragraph 3.4.1 for coordination, approval and signatures by the A-10 Chief Engineer, System Program Manager

(SPM) and AFLCMC Fighter/Bomber PEO. Updates to the APOP shall be IAW AFMC Instruction

23-103.

m. A-10 Life Cycle Sustainment Plan (LCSP), Draft 1.0 February 2014

n. A-10 Connectivity CDD Increment I (evaluate the need, content and develop for Increments II and III or A-10 SPO approved equivalent.

o. Update and demonstrate to the A-10 SPO an A-10 Architecture HTML Users Guide to aid users in navigating and using the full content of everything that CORE publishes from the architecture into HTML to facilitate a clear understanding and optimal use of the architecture for systems engineering and integration of A-10 programs. (CDRL A004, A007

p. OSS&E Baseline Document (09-A10DOC-006, APP 3)

q. Electrical Interface Control Document (EICD), Mar 2014

r. Initial Capabilities Document (ICD), Draft, Nov 2012

3.4 A-10 Platform Obsolescence Plan (APOP)

3.4.1. The Contractor shall develop an A-10 Platform Obsolescence Plan (APOP) and facilitate it’s execution which assists, prioritizes, and tracks the support from Air Logistics Complex (ALC) item managers and their teams in supporting, reporting and resolution of the obsolescence issues on the A-

10 commodities for which they are responsible. The APOP must meet the intent of AFMC Instruction

23-103, Diminishing Manufacturing Sources and Materiel Shortages (DMSMS) Program and

Guidebook, and the Defense Standardization Program Office, publication SD-22 “Diminishing

Manufacturing Sources and Material Shortages”, a Guidebook of Best Practices and Tools for

Implementing a Proactive DMSMS Management Program. Other applicable guidance is the MIL-STD-

3018 “Parts Management” and the new DoD standard for all DMSMS programs, GEIA STD-0016. The presentation of the data from the plan shall be modeled after the A-10 Support Equipment Roadmap

(SER), see Appendix O, to organize and present data in a simple but complete fashion from which resolution of obsolescence decisions can be made by A-10 SPO leadership. (CDRL A004)

3.4.2. The Contractor shall analyze and compare the list of A-10 commodities contained in the list of

AVCOM loaded commodities in the “Background Paper on A-10 Weapon Systems Diminishing Sources and Material Shortages (DMSMS) Program” against all known A-10 avionics commodities and determine which A-10 avionics commodities have not been loaded into the AVCOM database.

3.4.3 Work with the A-10 Logistics Branch, AFLCMC/ WWAW in the A-10 SPO, AFMC 429 SCMS/GUBC, and A-10 commodities program managers and item managers to ensure commodities that are currently planned are loaded into the DMSMS tracking database (AVCOM).

3.4.4. Obtain access to and load all A-10 avionics commodities into AVCOM Tier 4 that are not already loaded or planned to be loaded. The Contractor will likely have to have a teaming arrangement with BAE, the current Contractor managing AVCOM, in order to accomplish the AVCOM related tasks.

If the Contractor managing AVCOM changes during the PoP of this contract another teaming arrangement will have to be made. If required, assistance for contacting the current Contractor can be obtained through the Procuring Contracting Officer (PCO).

3.4.5 Develop a Government approved prioritization method to identify the top 20 commodities with obsolescence (DMSMS) issues having the highest impact to fleet mission capability. (CDRL A004)

3.4.6 Using AVCOM, provide the Government a prioritized listing of all A-10 avionics commodities with

DMSMS issues and the plans for the resolution of these issues at the component level for the top 20 commodities. These support efforts shall include an A-10 DMSMS Support Summit or equivalent meeting where the top 20 commodities with DMSMS issues are presented and include the plan for implementation of the prioritized obsolescence reports, briefs, etc. into ASWME for common A-10 community access. Generate the updated list of the top 20 commodities with DMSMS issues annually.

(CDRL A004)

3.4.7 Compare and analyze the avionics commodities with the roadmap, SV-8 and SV-9 and planned modification efforts to determine if there are cost effective ways to replace some or all of the top 20 commodities functions with software using FACE based procecessor or its equivalent or by combining their function with other commodities into one. (CDRL A004)

3.5 Support Equipment Roadmap

The Contractor shall perform the tasks in section 3.5 IAW the annual process defined in the A-10

SE Roadmap (SER) facilitating the role of Support Equipment Analyst and A-10 SE Integration.

The Contractor shall deliver sections of the A-10 SE Roadmap periodically as specified in Table 1

Support Equipment Roadmap (SER) Section Titles, Numbers, Content, and Schedule (See specific

CDRLs for each section below).

SER

Section

No.

Section Title Contents of Section Annual Delivery

Schedule1

1 Program Summary Summary of all SER work performed. 15 days before contract end date

2 A-10 Support

Equipment

Baseline

Baseline data collected against

1. AS333 National Stock Number

(NSNs) for Organizational (O) and

Intermediate (I) level equipment.

2. A-10 items with Source of Repair

(SOR) at the Air Logistics Complex for Depot (D-) level equipment.

3. Field and depot allowance standards

10 days after A-10 Data

Gathering and Entry

Task

3 A-10 Support

Equipment Strategy

Development

Analyses, Market Research and Trade

Studies performed, leading to strategy/forward plan recommendations.

10 days after SE

Analysis Task, and 10 days after Strategy

Development Task

4 A-10 Support

Equipment

Generation Plan

(SEGP)

Planning Document authorized by the SE

Council; provides the POM data required to enact the SE Strategies developed in

Section 3.

10 days after Support

Equipment Generation

Plan Task

5 A-10 Support

Equipment

Management Plan

(SEMP)

Policies, responsibilities, and processes required to maintain the SER. Includes a

Support Equipment (SE) Working Group

Charter, a Memorandum of Agreement, a

Tutorial, and the data/algorithms used to calculate SE deficiency rankings.

15 days before contract end date

Table 1 Support Equipment Roadmap (SER) Section Titles, Numbers, Content, and Schedule

3.5.1 A-10C Data Gathering and Entry Task

The Contractor shall perform data gathering and entries per SER Section 5, paragraph 6 to include an updated Tier list of A-10C SE based on the ACC/A4A8 Common Allowance Standard (CAS) for the

Combat Air Force (CAF) (AS333). The Contractor shall perform an equipment usage survey focusing on the O-level, and intermediate level for currently fielded unique and common support equipment for the A-10C. The Contractor shall continue to identify current SE in use in the field, and map SE to A-

10C commodity by referencing Technical Orders (TOs). The SE surveys shall be conducted per SER

Section 5, Para 6 utilizing applicable templates and processes via electronic means or through on-site interviews when required. Completed Surveys will be captured as an attachment to SER Section 2, and integrated into the A-10 SEGP spreadsheet and applicable databases including AWSME and

TeamCenter. Site locations are stated below but not limited to:

Day count is based on the US Government business calendar

a. ACC Air Force Bases

b. Air National Guard Bases

c. Air Force Reserve Command Bases

The types of data to be collected by the Contractor during the surveys for the SE shall include, but is not limited to, Data Identifiers per attachment B of SER Section 5.

The Contractor shall gather and analyze Reliability & Maintainability Management Information System

(REMIS) failure data or other Government databases for the SE identified for analysis by the SE

Integrated Product Team (IPT). Data shall be collected by the Contractor from the following, but not limited to Government Repositories:

a. G099, Reliability and Maintainability Information System (REMIS)

b. G021,Quality Deficiency Reports or equivalent

c. D041, Recoverable Consumption Items Requirements System

d. D002A, Standard Base Supply System

e. D200, Recoverable Consumption Item Requirements System

f. C001, Air Force Equipment Management System (AFEMS)

g. D200C, Equipment Item Process

h. G105,Integrated Maintenance Data System

i. G081,Malfunction Detection Analysis and Recording System

j. A400,Joint Reliability Availability Management System (J-RAMS)

k. Q310, Global Combat Support System Data System (GCSS)

l. D043A,Master Item Identification Database

m. D035,Stock Control System

n. Q302, Air Force material Command (AFMC) Data Depot

o. G019C, Management of Items Subject to Repair (MISTR) Requirements Scheduling and Analysis

System

p. Execution and Prioritization of Repair Support System (EXPRESS)

q. H103, Central Procurement Accounting System (CPAS)

r. Reliability, Availability, Maintainability for Pods & Integrated Systems (RAMPOD)

s. Lean Depot Management System (LDMS)

t. Tool Accountability Data System (TADS)

u. Test Equipment Database (TED)

v. Precision Measurement Equipment Laboratory (PMEL) Automated Management System (PAMS)

The Contractor shall support quarterly teleconferences to collect status updates on the SEGP projects and action items. The Contractor shall integrate the data received from the A-10 SE Technical

Interchange Meetings (TIM)/reviews discussion item forms into the A-10 SEGP spreadsheet. The results of the usage survey and logistic data collection shall be captured by the Contractor in the SER

Analysis report. Results shall include a list of SE items which are impacting A-10 support and are recommended for Tier Level prioritization for improvement, replacement, or other solutions (additional quantity more…