FY24 516SWES F16 ATS Sustainment Organic Workload.pdf

FOR OFFICIAL USE ONLY

STATEMENT OF WORK

(SOW)

FOR

F-16 AUTOMATED TEST SYSTEM (ATS) SUSTAINMENT

WORKLOAD

1 Oct 2023– 30 Sep 2024

416th SUPPLY CHAIN MANAGEMENT SQUADRON

HILL AIR FORCE BASE, UTAH 84056-5609

OPR: 416 SCMS/GUMAA, Hill AFB, UT 84056

Project Directive A-24-2080, Rev001 Distribution as specified in the PD

Atch 1

INDEX

1. Scope and Purpose Page 3

2. References and Ground Rules Page 3

3. Tasks and Requirements for TPS Support, 416SCMS/GUMA Page 5

4. General Support for TPS Page 12

1. SCOPE AND PURPOSE:

1.1 SCOPE

This document sets forth all requirements to be performed by 516 SWES in support of Automated Test System (ATS) software for the F-16 weapon system. Included are Depot Deficiency Reports (DDRs), Material Improvement Project (MIP) investigations, Avionics Intermediate Shop (AIS), and field sites; associated Organic Change Proposals (OCPs), special projects, customer support, configuration management, and Software Control Center (SCC) services as requested and/or approved by 416 SCMS. Integral to this effort, 516 SWES shall aggressively pursue cost savings and efficiency while providing critical feedback to 416 SCMS on the value added to the mission.

1.2. PURPOSE

Purpose of this SOW is to describe requirements for ATS sustainment that will ensure system integrity, mission readiness, sustainability, reliability and maintainability and the criteria for acceptable performance of 516 SWES in accomplishing those requirements.

2. REFERENCES AND GROUND RULES

2.1. 516 SWES

2.1.1. 516 SWES policy, and the associated processes, plans, and procedures.

2.1.2. 516 SWES Squadron Engineering Processes (SEPs) for ATE Software Maintenance.

2.1.3. Government Performance Assessment Rating (GPAR) Memorandum of Agreement (MOA) (Dated 1 October 2023).

2.2. 416 SCMS

2.2.1. USAF Material Deficiency Reporting and Investigating System, TO 00-35D-54.

2.2.2. Air Force Time Compliance Technical Order System, TO 00-5-15.

2.2.3. Calibration and Measurement Summary for F-16 Weapon System, F-16 C/D Aircraft, TO 1F-16A-37.

2.2.4. Technical Agreement 13, Cost Sharing Plan for F-16 Organic Software Support.

2.4. IMPLEMENTATION.

516 SWES shall be responsible to implement a plan for the execution of this SOW.

2.5. DEFINITIONS.

2.5.1. AUTOMATED TEST SYSTEM (ATS) – A fully integrated, computer-controlled suite of electronic test equipment, hardware, software, documentation and ancillary items designed to verify the functionality of the Unit Under Test (UUT) assemblies.

2.5.1.1. Automatic Test Equipment (ATE) - An integrated assembly of stimulus, measurement, and switching components under computer control that is capable of processing software routines designed specifically to test a particular item or group of items.

2.5.1.2. Test Program Set (TPS) - ATE interface hardware, test program software, documentation and other ancillary equipment that connects ATE to the UUT.

2.5.1.3. Test Environment - A description of the ATS architecture, programming and test specification languages, compiler, development tools and provisions for capturing and using UUT design requirements and test strategy information in the generation and maintenance of TPS software.

2.5.2. MATERIAL IMPROVEMENT PROJECT (MIP) - For the purposes of this SOW, a MIP is defined as a deficiency report generated from the Joint Deficiency Reporting System (JDRS) to 516 SWEG indicating a problem which may be related to the ATS or Bad Actor program. MIPs can include but are not limited to Depot Deficiency Reports (DDRs), Material Deficiency Reports (MDRs), Software Deficiency Reports (SDRs), Quality Deficiency Reports (QDRs) or Tech Generated MIPs (TGMIPs).

2.5.3. BAD ACTOR - Avionics system or subsystem component that enters the repair cycle at a rate significantly higher than the total population of like systems or subsystem components.

2.5.4. ReTEST OK (RTOK) - A condition that results when an LRU or SRU has a verified malfunction at an intermediate level testing facility yet passes testing without failure at a Depot testing facility.

2.5.5. FUTURE WORK - DRs that are identified but not entered into JDRS until the ES and Engineering Organization agree to start the investigation.

2.5.6. ORGANIC CHANGE PROPOSAL (OCP) - OCPs are the activities required to produce the software changes to the ATS from MIP investigations.

2.5.6.1. OCP Overruns - The number of hours over the original bid provided at the Software Configuration Control Board (SCCB) that are required to complete an OCP. Request for an overrun should be made thru the 309th SWEG PD program manager to the 416 SCMS PD program manager. Hours may be charged with justification and approval by the program office. Overtime may not be charged unless determined at the SCCB and labor bid reflects this decision.

2.5.7. ORIGINAL EQUIPMENT MANUFACTURE (OEM) – OEMs are the software programs produced by external contractors. 516 SWES will perform tasks associated with the current process to review and deliver OEM software and documents.

2.5.8. SPECIAL PROJECTS (SP) – Special Projects shall be tasks that cannot be submitted thru JDRS and are requested by 416 SCMS as necessary to implement this SOW. This WBS element is intended to capture investigations/testing of a larger scope/unknown, research (prototyping), adding additional UUT part number requiring more than average hours that cannot be worked as a MIP or OCP according to the stated definitions in this document. It is not intended to negate the MIP process for projects that run longer than the average amount of hours for a DR.

2.5.9. PROJECT DIRECTIVE (PD) FUNDING. Implementation of this project directive will require the use of ATE managed by AFLCMC ATS PGM. Separate funding will be provided by that organization for management of test equipment and the related software. 416 SCMS will provide funding for TPS requirements utilizing the ATE. The following information is provided to define these differences.

2.5.9.1 TPS. Requirements for TPS support will be charged against the proper WBSs assigned for these tasking’s. Working Capital Funds (WCF) are provided thru the 416 SCMS PD Manager for these efforts.

2.5.9.2 ATE. Requirements for ATE support will be charged against the proper WBSs assigned for these tasking’s. Operations & Maintenance (O&M) funds are budgeted/requested by AFLCMC ATS PGM (Robins AFB). ATE requirements will be managed by the ATS PGM under separate agreement.

Due to O&M program realignment, certain ATE programs have been retained for management at Hill AFB. Funds are budgeted/requested by 416SCMS program office (Hill AFB). These ATE requirements at Hill AFB will be managed by the 416SCMS program office under this agreement.

3. TASKS AND REQUIREMENTS FOR TPS SUPPORT, 416SCMS/GUMA

3.1. MATERIAL IMPROVEMENT PROJECTS (MIPs)

3.1.1. Analysis/Investigation. Projects against this WBS shall be tracked separately to ensure proper funding. Only Budget Code 8 NSNs may be charged to USAF TPS funding. Other FMS related NSNs of the same nomenclature may be worked if cost shared. If the MIP is other than Budget Code 8, only FMS will be charged.

Budget Code A NSNs for Common Aircraft Ground Support Equipment will be charged to the appropriate ATE funding provided. WBSs are separate from TPS and in place.

516 SWES shall analyze MIPs to determine cause of user identified discrepancy, software anomaly or hardware failure, and provide a report of findings to 416 SCMS Equipment Specialist via Common Avionics Software Tracker (CAST). 516 SWES shall correct deficiencies found during investigation of MIPs via an internally controlled engineering change process. These deficiencies should be documented if anything beyond spelling errors.

3.1.1.1. Significant deficiencies shall be worked separately under new MIPs as approved by an

ES.

3.1.1.2. If a MIP requires investigation from both SRU and LRU engineers, the MIP must remain opened until completed. The MIP may not be closed and a new MIP opened for the same DR.

3.1.2. Hours/Schedule. The average number of hours and days are stated in the Government Performance Assessment Report (GPAR). The GPAR is an overall metric to be applied to all MIPs collectively. The actual hours and days expended per MIP can vary above and below the average, usually due to issues such as complexity or lack of available manpower. PD Managers and the ES should be contacted if a MIP deems to be above the average complexity to resolve.

This may not be immediately known until the investigation is started.

Examples of possible complexities but are not limited to:

a. Change of an existing TPS to adjust capability to the ATS for testing additional UUTs.

b. Program size due to a TPS correction or the Software Line of Code (SLOC) is expected to exceed 1000 lines.

c. Improve significant diagnostic capability to UUTs.

d. Change digital TPS device models for use in LASAR simulations and/or the MIL-STD-

1553 R/T data bus protocol.

Based on historical data, most DRs are considered to be of average complexity, approximately 75 MIP hours and closed within 94 GPAR days. If a MIP is deemed to be of above average complexity, the PD managers have the discretion to authorize GPAR exemption or work as a special project.

3.1.3. Tech generated MIPs. If SWEG engineer identifies a software deficiency, the TechGen MIP process shall be utilized with ES concurrence.

3.1.4. Priority of Workload. 516 SWES shall work MIPs based on the listed criteria. Lower priority MIPs can be expected to run significantly longer than GPAR metric standards when MICAPs and higher priorities prevent lower priority MIPs from being worked. Priorities are:

a. MICAP (Mission Capability)

b. Backorders (when no other platform/capability is available)

c. ES Priority

d. JDRS (Joint Deficiency Reporting System) oldest DR first

3.1.5. Bad Actors. 516 SWES shall investigate bad actors submitted through JDRS. Repairs shall be accomplished through existing repair channels, OO-ALC production depot or applicable contractor as required to prevent the exhibits from repeating as Bad Actors.

3.1.6. ReTEST OK (RTOK). 516 SWES shall investigate RTOK assets submitted thru the JDRS.

3.1.7. Exhibit Maintenance (LRU/SRU). 516 SWES shall accomplish any required maintenance to MIP exhibits to continue analysis or verify the fix of user identified discrepancies. 516 SWES shall process ATS related exhibits through existing channels, OO-ALC production depot, according to their recommended disposition, and include disposition recommendation in their final report. 516 SWES may not repair LRU mock-ups with Working Capital Funds (WCF) provided through the PD. 516 SWES shall ensure that a minimum number of exhibits are retained to support software correction verification process.

3.1.8. Software Sustainment Environment. 516 SWES shall maintain the proper sustainment environment necessary to support ATS including Security, Information Assurance and Safety.

3.1.9. Work Stop. PD Managers, in conjunction with TPM’s must insure proper manpower and staffing are available to comply with assigned workload(s). MIPs may not be work stopped due to lack of manpower. The only exceptions will be in cases of un-forecasted retirement or sudden transfer of personnel that is beyond the control of the 516 SWES. MIPS also may not be work stopped due to higher priority workload driven by other organizations supported by 516 SWES. The Equipment Specialist or ES’s Program Manager must be notified and agree to work stop a MIP. MIPs may be work stopped based on the following criteria:

a. Awaiting Parts (AWP), document number must be provided in Common Avionics Software Tracker (CAST) prior to stopping

b. Test Station Problems (repair, calibration, etc.)

c. Unavailability of Test Equipment

d. Awaiting Depot Repair

e. Baseline Not Available (tied to another pending s/w project, etc.)

f. Awaiting Receipt of Exhibit/Asset from Country

g. Other (determined on case by case basis with respective PD Managers)

In the event of extenuating circumstances, Work Stop options can be reviewed on a case-by-case basis with the Program Office. These circumstances will be pre-coordinated with the PD Manager and the Program Office prior to the formal work stop request being made in CAST.

3.1.10. Future Work. 516 SWES shall keep track of uncorrected deficiencies for future updates via the Future Workload database in the Common Avionics Software Tracker (CAST). The applicable Equipment Specialist is notified via e-mail/CAST and will be consulted prior to investigation/implementation.

3.2. GPAR EXEMPTION. Exemption may be granted for MIPs that are in work by a contractor and tracked thru CAST or for investigations requiring an FMS asset. Other exemptions may be granted at the discretion of the Program Office.

3.3. ORGANIC CHANGE PROPOSALS (OCPs). OCPs are the change activities required to produce the changes to the ATS from a MIP. Engineering functions shall include, but not be limited to, incorporating all proposed changes, integration, test, and delivery of those changes. 516 SWES Configuration Management shall control changes and releases for TPSs. OCP Preparation Procedures are identified in the F-16 PD Collaborative Lifecycle Management (CLM) Help file.

Emergency changes shall be accomplished via the Urgent OCP process as defined in the process also found in the CLM Help file.

Same activities and processes apply to ATE software for Common Aircraft Ground Support Equipment. Support will be charged to the appropriate ATE funding provided. WBSs are separate from TPS and in place.

3.3.1 Resolution Summary. OCP’s normally consist of one or more changes. These changes will be listed on a single document and attached to the applicable OCP project in CAST, under “File Attachments”. This document will contain all associated MIP(s) that pertain to the subject OCP.

Each MIP will contain MIP number, assigned engineer, and date of completion. Each associated MIP will have a detailed description of the problem and solution along with other modifications that were accomplished and any updated and/or new files. See page 16, fig. 1 for example.

3.3. 2 Work Stop. Authority to work stop OCPs resides with the Program Office. TPMs should provide justification via the project in CAST. The 416 SCMS PD Manager will contact the ES for concurrence. Acceptable justifications for work stop:

a. Waiting for sell-off at off-site location

b. Unavailability of test equipment

c. Waiting for additional MIP after OCP is boarded

d. Awaiting direction from ES

e. Awaiting receipt of exhibit/asset from country

f. Concurrent release with another program

g. S/W sent to country for V&V

h. Test equipment problems

i. Other (explanation required)

The nature of OCP’s are primarily “verification and clean-up”. The solutions have already been reviewed and verified in the MIP stage, these projects could be easily turned over to be worked by other assigned staff. Therefore, Work Stop for man power shortages are not authorized except in extreme conditions not covered above. These Work Stop requests will be pre-coordinated with the PD Manager & the Program Office prior to a formal request being made in

CAST.

3.4. SPECIAL PROJECTS. 416 SCMS shall initiate special projects on behalf of Equipment Specialists or as recommended by the 516 SWES, to include special investigations, research, work that is considered outside of MIP scope, or other unique support. Each special project approved by the 416 SCMS PD Manager will be tracked separately and reported as required.

Special Projects shall be managed per Special Projects Process as defined in the 516 SWES process. The requirements of each customer initiated special project shall be defined in writing by the customer to include any reports required, interval of status reports, test plans, and any deliverables necessary to close the projects. 516 SWES reserves the right to refuse special projects that are out of scope. Funding for special projects shall be provided prior to initiation.

3.5. CUSTOMER SUPPORT

3.5.1. Informal Technical Data Exchange (ITDE). ITDE is a process of sharing SPAR/ECP and MIP/OCP information as it relates to the ATS software between ATS and TPS contractors and 516 SWES. 516 SWES shall evaluate all exchanged data which may generate the following actions:

3.5.1.1. Ensuring SPARs are entered into the Future Work Database.

3.5.1.2. Coordinate and report changes in OEMs including outstanding Software Program Anomaly Reports (SPARs), technical content, schedule, or baseline of existing or planned OCPs.

3.5.1.3. Participation in ITDE teleconferences.

3.5.1.4. TDY/participation in Program Management Reviews (PMRs).

3.5.1.5. Assist contractors with CPIN assignments as requested.

3.5.2. Tech Generated MIPs. If 516 SWES engineer identifies a software deficiency, the TechGen MIP process shall be utilized with the ES concurrence.

3.5.3. 309 EMXG Support. 516 SWES shall provide customer support to 309 EMXG to assist in preliminary investigation of Depot Deficiency Reports (DDRs) to determine if there is a requirement to write a Software Deficiency Report (SDR). Test Station maintenance shall not be accomplished on behalf of the 309 EMXG and charged to the Project Directive. 309 EMXG is responsible for providing funding for test station maintenance efforts.

3.5.4. Depot Deficiency Reports (DDRs). Depot DRs are to be utilized by 309 EMXG to identify problems requiring investigation. DDRs may be submitted directly from Depot personnel thru CAST without a preliminary investigation. The Equipment Specialist will be contacted and with concurrence, a MIP will be opened. A DRIU number will be provided to the shop and the asset or exhibit will be marked “Q” condition and turned in. 516 SWES will request the necessary asset or exhibit from Supply to perform an investigation. If a deficiency is identified by 516 SWES, the TechGen MIP process will be utilized with the ES concurrence.

3.5.5. 416 SCMS Support. 516 SWES shall provide customer support to 416 SCMS as required.

This shall include attendance at conferences, meetings, reviews and other special activities as requested by the customer.

3.5.5.1. 516 SWES shall document assistance to 416 SCMS by recording the problem under the Customer Support WBS to include the requestor and the action taken for each instance of support provided.

3.6. STATION/EQUIPMENT MAINTENANCE. 516 SWES shall provide technical support for DATS, FATSS, FACT, LM STAR, MDTS, and RTTS located in building 100 and maintenance for the AIS ATE located in building 1515. The AIS equipment is essential for use in the sustainment of ATS software. This equipment shall be maintained in a serviceable condition and calibrated as required IAW TO 1F-16A-37 and AIS/IAIS/RIAIS technical manuals.

3.6.1. AIS ATE. Per agreements with the AFLCMC ATS PGM (Robins AFB), and with 416SCMS (Hill AFB) for those locally managed programs, equipment may be removed from its calibrated state as needed to perform engineering functions. Parts support shall be maintained to keep the ATE in operation. AIS test stations, TPS and ancillary equipment (AIS, IAIS, VXI-IAIS, and R- IAIS) maintenance actions will be documented in the Defense Repair Information Logistics System (DRILS). The DRILS documentation will include those actions taken to troubleshoot failures in Calibration, Confidence, Alignment, Diagnostics, and hardware failures impacting TPSs and ITAs. DRILS documentation will include at a minimum: the station serial number, station Standard Reporting Designator (SRD) failing Test Number, Upper Limit (UL) and Lower Limit (LL) parameters, and the actual measured value, part numbers and serial numbers of any components removed and replaced to resolve station failures; and a narrative to describe the action that was taken to troubleshoot and repair the anomaly. Additionally, TCTO compliance reporting will be documented, however Periodic Maintenance documentation is optional.

3.7. SUPPORT RELATED FUNCTIONS:

3.7.1. Project Tracking System Administration and Support. 516 SWES shall support all project-tracking metrics and accounting data for the DRs, MIPs, OCPs, and Special Projects of the F-16 workload as outlined in this SOW. Changes to the project tracking system shall be coordinated with 416 SCMS as it is interfaces with CAST. Changes to CAST, including maintenance and enhancements shall be approved via Configuration Control Board (CCB) with all appropriate stakeholders and the 416 SCMS. In the event these changes can’t be supported by the CAST maintenance team in a timely fashion, these items will be prioritized. This prioritized list will have input and final approval from the 416SCMS. 516 SWES shall notify 416 SCMS of updates to the Configuration Management Tool, Collaborative Lifecycle Management (CLM) Tool, Reviews (Defect) Database, and future development of databases that are required to provide accurate reporting to the 416 SCMS organization. Project Management Tools that are not driven by, approved, or of benefit to the 416 SCMS will not be funded.

3.7.2. Planning and Scheduling. 516 SWES shall provide the overhead support function to maintain an accurate cost and schedule accounting system that tracks costs of this SOW. This data shall be made available to 416 SCMS as specified in paragraph 4 below.

3.7.3. Equipment Custodian. 516 SWES shall provide equipment custodian services for equipment account 516AV. This shall include but not be limited to maintenance of an accountability matrix, inventory control, turn-in and issue of obsolete and new equipment, and other duties as required.

3.7.4. Network Support. 516 SWES shall maintain a computer network system to enable a smooth flow of information and data between individuals, groups and organizations and to provide access to government and contractor data systems including but not limited to: G004L, G042A, JDRS, EDDR, EDCS, LM Aero LISS, PUB LOG FLIS (FED LOG), HayStack, CAST, LIMS-EV, ETIMS/SATODS, SMART, etc. as required to accomplish the objectives of this SOW.

3.7.5. TDY: 516 SWES shall utilize TDY as needed and necessary to perform the tasks and requirements of this SOW or as directed by customer. Requesting customer or country shall approve and provide funding prior to all TDYs. Trip reports shall be provided to F16PD Program Office.

Per AFSCI21-101, para 5.12.19: “the Requirements Generator (RG) cannot fund TDY(s) from project funding. Government travel in support of validated TPS maintenance projects are funded separately under the appropriate EEIC 409. Government travel may not be funded under TPS EEICs 56001 (contract), 54001 (organic) or 54002 (DMISA).”

3.7.6. Configuration Management (CM). 309 SWEG/MXDXC1 & MXDXC4 shall maintain accurate configuration management of the products supported with this SOW. MXDXC1 & 4 shall coordinate, schedule, and conduct an independent kit proof and/or Validation & Verification (V&V), IAW TO 00-5-15, for each approved OCP. This task includes preparing a complete and final kit proof/V&V package for OCP sell-off. Required participants include the ATS Equipment Specialist, a representative from the user community, engineering and MXDXC1 or 4 configuration manager. Final approval for release of all OCPs involving TPSs shall reside with 416 SCMS.

3.7.7. Software Control Center (SCC). 309 SWEG/MXDXC3 shall prepare and distribute software and documentation masters and copies to all authorized users and storage facilities.

The following list includes, but does not limit, the various areas that may receive distribution:

Field/User Software Libraries Robins AFB / WR-ALC Tinker AFB / OC-ALC ATS Program Manager Lockheed Martin Aeronautics (LM Aero)

British Aerospace Electronics (BAE) Systems Tech Order & Engineering Data Pkg Repositories

The SCC shall maintain a repository for all ATS software required by the customer. Customer shall provide logistics support in acquiring vendor or contractor software not currently in the library on an as needed basis.

3.7.8. Security. 309 SWEG/MXDSSB shall maintain a secure environment to provide for control of classified software and documentation.

3.7.9. Communications Security (COMSEC) Account Maintenance. 516 SWES shall create, update, and maintain a COMSEC account per established Operating Instructions. These tasks shall include required inspections, safeguarding and disposition of COMSEC materials in support of the F-16 PD.

4.0. GENERAL SUPPORT FOR TPS

4.1. PROJECT MANAGEMENT. 309 SWEG/MXDX shall provide process controls, tracking, and project management services in direct support of the requirements of this SOW. This shall include but not be limited to management of work assignments, participation on change control boards, oversight of process improvement processes, and technical lead engineering services in support of ATS systems, etc.

4.1.1 CAST Support. As CAST is the central project management tool for projects contained within this PD, its upkeep and smooth operation is essential to project success. Configuration Control Board (CCB) meetings will be held at least once a quarter, or more often as necessary to provide progress status on open requests. Support provided for the CAST database will be, at a minimum, the projected and agreed upon bid hours for the yearly budget. Support that cannot be provided as projected will be coordinated with the F16 Program Office. Any deviations not approved by the Program Office are not authorized.

4.2. PROJECT DIRECTIVE TECHNICAL PROGRAM MANAGER (PD TPM). Duties include coordinating with customer on budgetary prospects, facilitating the gathering of historical budget data, meeting with and coordinating with Flight Directors and Project Managers (PMs) on their budgetary needs, finalizing negotiated budget with the customer, assisting in obtaining signatures from all squadron directors involved in the PD budget, and tracking PD budget spending.

4.3. PROJECT MANAGERS (PMs). The PM's duties include work control, risk analysis, funding tracking, status accounting, and process improvement. Also assists the Flight Director/PD TPM in assembling and analyzing the data needed to make an informed bid, assisting in making the bid, and assisting in monitoring PD financial execution.

4.4. SUBJECT MATTER EXPERTS (SMEs). 516 SWES SME’s support for MIPs, OCPs, and Special Projects shall be charged directly to those projects.

4.5. PROCESS IMPROVEMENT. 309th SWEG shall continually seek to reduce cost, schedule, and improve the overall DR program.

4.6. REPORTING. Measurement of performance criteria shall be accomplished utilizing an agreed upon GPAR (Ref: GPAR MOA Dated 01 Oct 2022) as coordinated between 516 SWES and

416 SCMS.

4.7. PROJECT TRACKING SYSTEM. Updates are necessary to provide the submitter/JDRS visibility into the status of their project. 516 SWES shall update the project tracking system as MIP investigations, OCPs, and special projects are completed and/or, at minimum of every 30 days; however, updates should be submitted sooner than 30 days when noteworthy, significant findings or events occur. Engineer/TPM comments should be informational and meaningful.

Vague and non-descriptive comments are not acceptable.

4.8. COST AND SCHEDULE. 516 SWES shall provide quarterly cost and schedule update briefings to 416 SCMS for all tasks and requirements in the SOW Section 3. The briefing charts will be provided electronically to 416 SCMS for review within 21 working days after the end of each quarter. A PMR briefing will be held within 30 days at the end of the second and fourth quarter. After the end of the first and third quarters, only the electronic briefing will be provided. 516 SWES format is acceptable. 516 SWES shall provide briefings to 416 SCMS that covers all aspects/issues of the program. Briefings shall be scheduled by 416 SCMS and briefed by 516 SWES. Quarterly reports on PD line items shall also be provided as directed by customer. Reports will include breakouts by Flights and End of Year Roll-up.

4.8.1 Quarterly PD Reporting: 516 SWES shall provide a breakdown separate from the PD briefing presented to 416 SCMS management consisting of budgeted hours and cost by funding type, i.e., TPS. Breakdown should reflect USAF actual hours and EPAF/FMS actual hours. For example:

Budgeted Hrs Per Quarter

USAF

Actual Hrs

EPAF/FMS

Actual Hrs

TPS Support Hrs TPS Production Hrs TPS Labor Cost $ $ $

MTT/ASSET Support Hrs

MTT/ASSET Production Hrs MTT/ASSET Labor Cost $ $ $

Exhibit Parts Cost $ $ $

4.8.1.1 TPS Support Hours. WBS correlates to SWEG Project Management in TAS EVM.

Detailed Report of Duties/Labor & Description. Detailed reporting will consist of the total cost (total number of hours) per PD Element and lists of descriptive comments supporting the work accomplished.

WBS 3.1.1 MIP Analysis & Investigation (USAF Only Requirement) WBS 3.1.2 MIP Analysis & Investigation (Cost Shared) WBS 3.3 Special Projects WBS 3.3.1 LRU/TPS Integration WBS 3.4.1 Technical Leads (SME)

WBS 3.5.1 ITDE

WBS 3.5.2 COMSEC/Software Assurance WBS 3.5.3 Shop Support WBS 3.5.4 416th Customer Support WBS 3.7.3 UUT Asset/Exhibit Custodian WBS 3.7.6.1 Support Related Functions Configuration Management WBS 3.7.6.2 CM UUT Support WBS 3.7.7.3 Distribution (UUT Support) WBS 3.9.4 Process Improvement WBS 3.10.1 MIP Analysis & Investigation (FACT)

4.8.1.2 TPS Production Hours. WBS correlates to SWEG Project Management in TAS EVM.

WBS 3.2.1 OCP TPS Support WBS 3.10.2 FACT OCPs

4.8.1.3 One-Time List of Duties Performed. Require an annual one-time list of duties performed.

WBS 3.9.1 PD Manager WBS 3.9.2 Project Management (PM) WBS 3.10.6 FACT Project Management (PM)

4.8.1.4 Program Manager Reviews. Reviews will be held as required by the Program Office.

WBS 3.7.1.1 CAST/TAS EVM/Process Tool Maintenance

4.8.1.5 MTT/ASSET Support Hours. Detailed Report of Duties/Labor & Description. Detailed reporting will consist of the total cost (total number of hours) per PD Element and lists of descriptive comments supporting the work accomplished.

WBS 4.1.2 MIPs WBS 4.5.3 Shop/Field Support WBS 4.5.4 Customer Supt - 416th ProgOfc WBS 4.7.6.1 Configuration Management WBS 4.7.7.3 Software Control Center

4.8.1.6 MTT/ASSET Production Hours. WBS correlates to SWEG Project Management in TAS

EVM.

WBS 4.2.1 OCP TPS Support

4.8.1.7 List of Duties Performed. Require an annual one-time list of duties performed.

WBS 4.9.2 Project Management (PM)

FIGURE 1

RESOLUTION SUMMARY EXAMPLE

MIP 18-XXXX Notes

Assigned Engineer Name 26 September 2019

Problem:

DDR-2018-0038 – Safe To Turn On (STTO) resistance tolerances need to be reevaluated on the grounds that different manufacturers of U1, U2, & U3, and U6 yield different measurements.

Regulated dropout test 229014 rarely passes first time but will pass eventually when repeated.

Analysis:

1. The STTO test limits were picked by the engineer when the TPS was rehosted to DATS. They are not a measurement set forth in the ATS. They are used to keep the asset safe before applying power. The ES said that it would be fine to change the limits as needed.

2. Found that test 2290 would pass all of the time on DATS9 and DATS10 but not pass on DATS20 across the street, where the workload is performed.

3. Test 2130 would fail on DATS20. Found that the first measurement was always incorrect but it was always correct every following measurement.

4. Tests 2090, 2100, and 2110 were failing on DATS20.

Solution:

1. Resistance measurement on test 1030 changed from 232kOhms to 230kOhms, test 1040 changed from 240kOhms to 200kOhms, test 1050 changed from 60kOhms to 15kOhms, and test 1070 changed from 8.5kOhms to 5kOhms. This change should allow for the varying input resistance on the suitable substitute U3 part.

2. Removed the loop on test 229000. Changed the TPS to use the oscilloscope to perform the measurement instead of the DMM. Tested on DATS20 and DATS2, which is the only 2-channel oscilloscope remaining.

3. Added a loop to test 2130 to perform the measurement twice and only count the second reading.

4. On DATS9 and DATS 10 tests 2090, 2100, and 2110 would always pass, but fail on DATS20.

The measurements on 9 & 10 were not even close to 20. I looked in the ATS and found that the requirements for test 2090 was +15 +/- 0.050 VDC, 2100 was -15 +/- 0.050 VDC, test 2110 was +5 +/- 0.3 VDC. The TPS values were test 2090 LL 11.5 UL 15 VDC, test 2100 LL -15 UL -12.5 VDC, test 2110 LL 3.6 UL 4.8 VDC. I changed the UL on test 2090 and 2110 to match the UL of the ATS. I changed the LL on 2100 to match the LL of the ATS. The rest of the TPS will need reviewing to see what other values do not meet the requirements set forth in the ATS.

Other Modifications:

1. CPIN updated from 81F-F16/14FBJ/SRUDS-U001-01A REV 001 to REV 002.

2. Changed Software development agency to 516SWES/MXDPD

Updated Files:

1. Databases: F16_14FBJ.mdb, F16_14FBJSFT.mdb

2. All files resulting from ATLAS code generation and compilation (not including self test files): *.SRC, *.emu, *.ITA, *.lst, *.trc, *.bin, *.MEP

3. TRD: 3002837.doc

4. Flowchart files: F16_14FBJ.txt, F16_14FBJ.acd

5. Quality Report.doc

New Files:

1. F16_14AAB_MIP_18-0336_UUT GOPATH.htm

2. F16_14AAB_MIP_18-0336_UUT GOPATH_results.htm

3. F16_14AAB_MIP_18-0336_ITA GOPATH.htm

4. F16_14AAB_MIP_18-0336_ITA GOPATH_results.htm

5. Engineering Notes: MIP 18-0336 notes.doc (this file)

6. 14FBJ_CD Label_A_SCC.doc

7. 14FBJ_CD Label_D_SCC.doc

MIP 18-XXXX Notes Assigned Engineer Name

26 September 2019

Problem:

DDR-2018-0038 – Safe To Turn On (STTO) resistance tolerances need to be reevaluated on the grounds that different manufacturers of U1, U2, & U3, and U6 yield different measurements.

Regulated dropout test 229014 rarely passes first time but will pass eventually when repeated.

Analysis:

1. The STTO test limits were picked by the engineer when the TPS was rehosted to DATS. They are not a measurement set forth in the ATS. They are used to keep the asset safe before applying power. The ES said that it would be fine to change the limits as needed.

2. Found that test 2290 would pass all of the time on DATS9 and DATS10 but not pass on DATS20 across the street, where the workload is performed.

3. Test 2130 would fail on DATS20. Found that the first measurement was always incorrect but it was always correct every following measurement.

4. Tests 2090, 2100, and 2110 were failing on DATS20.

Solution:

1. Resistance measurement on test 1030 changed from 232kOhms to 230kOhms, test 1040 changed from 240kOhms to 200kOhms, test 1050 changed from 60kOhms to 15kOhms, and test 1070 changed from 8.5kOhms to 5kOhms. This change should allow for the varying input resistance on the suitable substitute U3 part.

2. Removed the loop on test 229000. Changed the TPS to use the oscilloscope to perform the measurement instead of the DMM. Tested on DATS20 and DATS2, which is the only 2-channel oscilloscope remaining.

3. Added a loop to test 2130 to perform the measurement twice and only count the second reading.

4. On DATS9 and DATS 10 tests 2090, 2100, and 2110 would always pass, but fail on DATS20.

The measurements on 9 & 10 were not even close to 20. I looked in the ATS and found that the requirements for test 2090 was +15 +/- 0.050 VDC, 2100 was -15 +/- 0.050 VDC, test 2110 was +5 +/- 0.3 VDC. The TPS values were test 2090 LL 11.5 UL 15 VDC, test 2100 LL -15 UL -12.5 VDC, test 2110 LL 3.6 UL 4.8 VDC. I changed the UL on test 2090 and 2110 to match the UL of the ATS. I changed the LL on 2100 to match the LL of the ATS. The rest of the TPS will need reviewing to see what other values do not meet the requirements set forth in the ATS.

Other Modifications:

3. CPIN updated from 81F-F16/14FBJ/SRUDS-U001-01A REV 001 to REV 002.

4. Changed Software development agency to 516SWES/MXDPD

Updated Files:

6. Databases: F16_14FBJ.mdb, F16_14FBJSFT.mdb

7. All files resulting from ATLAS code generation and compilation (not including self test files): *.SRC, *.emu, *.ITA, *.lst, *.trc, *.bin, *.MEP

8. TRD: 3002837.doc

9. Flowchart files: F16_14FBJ.txt, F16_14FBJ.acd

10. Quality Report.doc

New Files:

8. F16_14AAB_MIP_18-0336_UUT GOPATH.htm

9. F16_14AAB_MIP_18-0336_UUT GOPATH_results.htm

10. F16_14AAB_MIP_18-0336_ITA GOPATH.htm

11. F16_14AAB_MIP_18-0336_ITA GOPATH_results.htm

12. Engineering Notes: MIP 18-0336 notes.doc (this file)

13. 14FBJ_CD Label_A_SCC.doc

14. 14FBJ_CD Label_D_SCC.doc