DRAFT Statement of Objectives (SOO).pdf
PDF 1 MB Posted
- Attached to
- Common Armament Tester for Fighter (CAT-F)
- Solicitation number
- FA8533-25-R-0002
About this file
This is a draft Statement of Objectives (SOO) for the Common Armament Tester for Fighter (CAT-F) program, issued by the Air Force Materiel Command Lifecycle Management Center at Robins AFB. The primary objective is to develop, manufacture, deploy, and sustain a common armament tester for both flightline (O-Level) and backshop (I-Level) maintenance requirements for the U.S. Air Force fighter fleets. The CAT-F will execute preload, clean wing, and fault isolation armament requirements and replace or augment legacy testers for the A-10, F-15, and F-16 aircraft.
The CAT-F system will consist of four main components: an O-Level handheld tester, aircraft-specific O-Level cable and adapter kits, I-Level functional and fault isolation tester, and aircraft-specific I-Level cable and adapter kits. Key requirements include cyber security, nuclear certification, and use of a Modular Open System Architecture approach. The program specifies detailed estimated quantities for each fighter platform, with the F-16 requiring the largest allocation (304 O-Level and 143 I-Level sets), followed by F-15 (172 O-Level and 80 I-Level sets) and A-10 (68 O-Level and 42 I-Level sets). The contract will be structured as an Indefinite Delivery, Indefinite Quantity (IDIQ) with a one-year base period and four one-year options.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| DRAFT Techincal Manual Contract Requirements (TMCR).docx | DOCX document | |
| Industry Questions with Answers_16 May 2025.xlsx | XLSX spreadsheet | |
| Industry Questions with Answers_29 Apr 2025.xlsx | XLSX spreadsheet | |
| DRAFT Sections L and M_ v3.1_01 Apr 2025.pdf | ||
| DD Form 2345.pdf | ||
| Draft CLIN Structure_FA853325R0002_01 Apr 2025.rtf | RTF text file | |
| Questions for Industry_01 Apr 2025.docx | DOCX document | |
| Industry Questions with Answers_01 Apr 2025.xlsx | XLSX spreadsheet | |
| DRAFT STATEMENT OF OBJECTIVES - CAT-F_01 Apr 2025.pdf | ||
| Draft RFP Attachment 6 Excel Cost Model v4_01 Apr 2025.xlsx | XLSX spreadsheet | |
| Industry Questions with Answers_05 Mar 2025.xlsx | XLSX spreadsheet | |
| Industry Questions with Answers.xlsx | XLSX spreadsheet | |
| DRAFT Sections L and M_Pricing Cost language included.pdf | ||
| DRAFT RFP Attachment XX Excel Cost Model.xlsx | XLSX spreadsheet | |
| Questions for Industry.pdf | ||
| DRAFT Sections L and M.pdf |
Show all 16
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Statement of Objectives – Common Armament Tester for Fighter (CAT-F)
Common Armament Tester for Fighter (CAT-F)
DRAFT STATEMENT OF OBJECTIVES (SOO)
Prepared by:
AFMC AFLCMC/ROA ATS Program Office Robins AFB, Georgia
Purpose The Government requires a common armament tester to execute both flightline and backshop requirements for United States Air Force (USAF) fighter fleets. The Government’s primary objective is development, manufacture, deployment, and sustainment of a Common Armament Tester for Fighter (CAT-F). The CAT-F will be used at both Organizational (O-LVL) and Intermediate (I-LVL) Level maintenance. The tester shall be able to execute preload, clean wing, and fault isolation armament requirements and replace, or augment, legacy testers for the A-10, F-15, F-16. The CAT- F shall be cyber secure, nuclear certified and use a Modular Open System Architecture approach. The program will require industry to utilize a CAT-F specific Government Reference Architecture (GRA). The CAT-F acquisition will also be a solution for Diminishing Manufacturing Sources and Materiel Shortages (DMSMS) and Obsolescence Issues across several legacy testers.
The Government is providing industry with the overall solicitation objectives which allow flexibility for each offeror to propose an innovative development approach to achieve the Government’s CAT-F requirements. Offerors shall use the Statement of Objectives (SOO) and attachments with the Request for Proposal (RFP) as a basis for preparing their proposal. Proposals shall include a contractor Statement of Work (SOW) and expected Contract Data Requirements Lists (CDRLs). Proposals shall also include an Integrated Master Schedule (IMS) that indicates their schedule to design, manufacture, and deliver a CAT-F solution for the F-16, F-15, and A-10 platforms.
CAT-F Scope The “CAT-F System” is defined as an O-Level (Flightline) an I-Level (Backshop) tester.
The CAT-F System will be comprised of components with each component requiring kitting designed for safe storage and rapid deployment.
The required components are: • O-Level Handheld tester
• Aircraft Specific O-Level Cable and Adapter Kit
• I-Level Functional and Fault Isolation tester
• Aircraft Specific I-Level Cable and Adapter Kit
O-Level Handheld Tester The CAT-F O-Level Handheld tester must be able to execute legacy O-Level Maintenance (Flightline) Pre-load and Clean Wing requirements for the F-16, F-15, and A-10 fighter aircraft. The Handheld Tester must work independently to execute O-Level test requirements and store testing results. The test shall be compatible with I-Level Functional and Fault Isolation Tester.
Aircraft Specific O-Level Cable and Adapter Kit The Cable/Adapter TPS Kit is expected to be aircraft specific and contain all-appropriate cables and adapters needed to execute pre-load and clean wing testing required at O- Level Maintenance.
I-Level Functional and Fault Isolation Tester The CAT-F I-Level Functional and Fault Isolation Tester must be able to execute legacy I-Level (Backshop) requirements for the F-16, F-15, and A-10 fighter aircraft and shall incorporate the O-Level Handheld tester in its design.
Aircraft Specific I-Level Cable and Adapter Kit The Cable/Adapter TPS Kit is expected to be aircraft specific and contain the appropriate cables and adapters needed to execute Fault Isolation requirements at I-Level Maintenance.
CAT-F Component Quantities The expected component quantities listed are based on current fleet status and may be adjusted to meet future Force Structure Changes. This will be an Indefinite Delivery, Indefinite Quantity contract (IDIQ). Table 1.0 indicates the Governments estimated component quantities.
Table 1.0 CAT-F Estimated Component Quantities
CAT-F Component F-16 with Spares
F-15 with Spares
A-10 with Spares
O-Level Handheld Testers 304 172 68 O-Level Cable and Adapter Kits 304 172 68 I-Level Functional/Fault Isolation Testers 143 80 42 I-Level Cable and Adapter Kits 143 80 42
Product Support / Logistics Considerations
• Solution considers COTS and equipment that will expedites development, production, and fielding
• Solution that reduces legacy equipment footprint and able to deploy worldwide
• Provide equipment solutions that deliver a reliable option and minimizes the potential for DMSMS
• Describe the MOSA approach to deliver CAT-F capability
• IP considerations and technical data package.
Period of Performance (PoP) The period of performance will be a one (1) year Basic with four (4) one-year Options.
Contractor Statement of Work (SOW) Offeror shall develop a SOW using the SOW template (SOO Attachment 5). The SOW must clearly indicate the work to complete the CAT-F with detailed tasks, technical requirements, evaluation and exit criteria, and recommended program deliverables. The SOW may be incorporated into the resulting award and should not include any proprietary or sensitive company information.
Integrated Master Schedule (IMS) The offerors are expected to develop and provide a time-based Integrated Master Schedule (IMS) detailing the tasks, key milestones, and delivery dates necessary to ensure successful program/contract execution. The IMS should be traceable to the offer’s developed Contractor SOW. The Offeror’s submitted IMS shall address all 5 contract years.
STATEMENT OF OBJECTIVES (SOO) Attachments:
Attachment 1: SYSTEM REQUIREMENT DOCUMENT (SRD) Attachment 2: F-16/F-15/A-10 ALTERNATE MISSION EQUIPMENT (AME) Attachment 3: CAT-F AME MAINTENANCE LEVEL REQUIREMENTS Attachment 4: CAPABILITY DEVELOPMENT DOCUMENT (CDD) SUMMARY Attachment 5: PREPARATION OF STATEMENT OF WORK (SOW)
ATTACHMENT 1:
Common Armament Tester for Fighter (CAT-F)
DRAFT SYSTEM REQUIREMENT DOCUMENT (SRD)
Prepared by:
ATS Engineering Office
AFMC AFLCMC/WNA ATS Program Office Robins AFB, Georgia
15 July 2024
The Common Armament Tester for Fighter (CAT-F) System Requirement Document (SRD) defines the system-level functional and performance requirements for a common armament tester for multiple fighter Aircraft. The SRD is derived from the CAT-F Capability Development Document (CDD) and Concept of Operations (CONOPS), system-level performance metrics.
Attachment 1: SYSTEM REQUIREMENT DOCUMENT (SRD)
GRA Ref. Name Text/Description Verification
SRD_1.0
CAT-F System Requirements (New Development)
SRD_1.1
Required States and Modes
The Testers non-operational and operational modes are defined below:
a. Non-Operational modes including the tester’s system storage and system transportation, if applicable.
b. Operational modes including Tester Maintenance and UUT/DUT Testing. The Tester maintenance modes consists of System Administration activities supporting software updates and approved user access, Tester Self-Test and Tester Calibration.
Demonstration
SRD_1.1.1
Tester Self-Test/Built- In Test
The Tester Self-Test/Built in Test (BIT) shall be designed in accordance with MIL-PRF-32070. If faults are discovered, the core tester’s functional status shall be displayed to the user and shall not require the use of external technical manuals to determine functional status.
Analysis
SRD_1.1.1.1
Power-On Confidence Test
The Tester shall provide a Power-On Confidence Test to ensure proper operation prior to initiation/stimulation of UUT test. The Power-On Confidence Test shall be automatically performed upon system power-up and shall include running the malware detection defined in 3.8.1.6 of this specification. Power-On Confidence test shall be completed in 10 minutes or less (T) with an objective of 2 minutes (O).
Analysis Demonstration
SRD_1.1.1.2 Self-Test
The Tester shall have an integrated Self-Test capability for failure detection and fault isolation of all system components, and shall provide indications of out of range conditions of the tester. The Self- Test shall ensure that stimulus and measurement devices are operating within tolerance. Self-Test shall run upon system start up and when manually commanded by the user. Self-Test during TPS execution shall not be enabled.
Demonstration
SRD_1.1.1.2.1 Self-Test Data
The Tester on-board fault and Self-Test data shall be collected, stored, and provided IAW IEEE 1636, IEEE 1636.1, and IEEE 1636.2 compatible formats to maintenance personnel during and after maintenance operations.
Demonstration
SRD_1.1.1.2.2 Self-Test Execution Time
The Tester Self-Test execution time shall be no longer than 10 minutes
(T) with an objective of 1 minute (O). Demonstration
SRD_1.1.1.2.3
Self-Test Fault Detection
The Tester Self-Test shall detect 100 percent of detectable faults. A detectable fault is a failure of a Tester Replaceable Unit (TRU) that is exhibited at the interface of the TRU and is outside the defined performance parameter or threshold for that particular function.
Demonstration
SRD_1.1.1.2.4
Self-Test Fault Isolation Rate – 1 Component
The Tester Self-Test shall isolate at least 90% of detected faults to a single system component (e.g.: tester unit, interface unit, cable number/connector number/pin number, software, etc.)
Demonstration
SRD_1.1.1.2.5
Self-Test Fault Isolation Rate – 2 Components
The Tester Self-Test shall isolate at least 95% of detected faults to two system components (e.g.: tester unit, interface unit, cable number/connector number/pin number, software, etc.)
Demonstration
SRD_1.1.1.2.6
Self-Test Fault Isolation Rate – 3 Components
The Tester Self-Test shall isolate 100% of detected faults to three or less system components (e.g.: tester unit, interface unit, cable number/connector number/pin number, software, etc.).
Demonstration
SRD_1.1.2
Test Program Set Requirements
All armament UUT TPSs developed for use by the Tester shall be designed IAW MIL-PRF-32070.
Analysis
SRD_1.1.2.1
Unit Under Test Data Log and Documentation
The Tester software shall collect, store, and provide upon command, the following data in compliance with IEEE-STD-1636.1 for future export:
General Information UUT Serial Number
a. Installed LRU serial numbers if applicable (A UUT for test purposes may contain other subassemblies which are themselves UUTs and separately serial numbered)
b. Tester serial number
c. Operator and date
d. Computer Program Identification Number (CPIN)
e. Checksum/Signature of CPIN to indicate Software unaltered
f. Tester Self-Test Status
g. Total Test Time
h. Overall UUT status (Pass/Fail) For each test sequence in the TPS
i. Upper tolerance value
j. Measured value
k. Lower tolerance value
l. Expected digital data
m. Received digital data word, in both actual state and in “layman’s terms”
n. Power Quality Information in accordance with paragraph 3.3.3.7.
o. Time Stamp
p. Indictments (or callouts) determined through fault isolation to include Failed Connector and Pin and input Connector/Pin(s).
Information shall be traceable to the test program.
q. Number of times an individual test sequence was run The Tester shall retain the UUT test data log after an incomplete test or test termination.
Analysis
SRD_1.1.2.2
Real Time Display of Test Results and Status
The Tester shall provide real-time test status to the operator:
a. UUT Serial Number
b. CPIN Number
c. Test Number being executed
d. Upper tolerance value
e. Measured value
f. Lower tolerance value
g. 1553 status
h. External Elapsed Time Indicator
i. Expected digital data
j. Received digital data in both actual state and in “layman’s terms”
k. Recommended Failure Modes e.g. call out most common LRU, Cable etc. Failed Connector and Pin and input Connector/Pin(s)
l. Measurement values for loop back tests and adjustments
Analysis
SRD_1.1.2.3 End of Test Report At the conclusion of TPS execution, the Tester shall display and log a test report for indicating the pass/fail status and certifying the functionality of the UUT.
Analysis
SRD_1.1.2.4 Safe-To-Turn-On Test The UUT TPSs shall perform safe-to-turn-on tests prior to executing the TPS IAW MIL-PRF-32070A. Analysis
SRD_1.1.2.5 Test Sequencing
The UUT TPSs shall automatically sequence through all test steps pausing only when operator input is required, when operator manually aborts test sequence, when a failure is detected, or until all test steps are successfully completed. Upon failure of a test step or the operator manually aborting the test sequence, the Tester shall display the fault data and allow the operator to retest the failed step, continue testing, or discontinue testing.
Analysis
SRD_1.1.2.6 Test Termination The UUT TPSs shall provide a termination feature to perform an orderly termination of a test in progress (i.e., terminate external interfaces) leaving both the Tester and UUT in a safe state.
Analysis
SRD_1.1.2.7 Test Entry Points
The Tester shall allow the operator to select and run test sequences from operator selectable entry points. At a minimum, entry points shall provide autonomous groups of tests based on UUT functionality.
Test Entry Points shall provide the capability for the operator to select and execute testing of specific functional areas of the UUT individually and separate from other functional areas, as well as complete end-to-end testing. UUT certification shall require an end-to-end go chain.
Analysis
SRD_1.1.2.8 Manual Test Sequencing
Manual test sequencing shall perform one test step in the sequence and pause for the operator to initiate the next step. Analysis
SRD_1.1.2.9 Test Control Selection Selection between automatic and manual test control shall be available, except when prohibited due to sequencing and/or timing requirements for tests.
Analysis
SRD_1.1.2.10 Test Data Transfer The Tester shall provide a cyber-secure compliant capability to transfer test data to an approved external device through an existing secure data port when commanded by the administrator.
SRD_1.1.2.11 Clearing Test Data The Tester shall have the capability to clear non-volatile memory and test data when commanded by an administrator. Analysis
SRD_1.1.2.12
Pre-Test External Cable Identification Cable and Cable Testing
The Tester shall verify the external cable configuration/hook-up prior to the start of any test. The Tester shall notify operator of any incorrect cable configurations prior to the start of any test. The Tester shall prevent test initiation when cables are incorrectly configured.
The Tester shall test all Test Program Hardware to include Interface Test Adapters (ITA) and ITA cables as part of the UUT TPS IAW MIL-PRF-32070A paragraph 3.3.6.
Analysis
SRD_1.1.2.13 Stray Voltage Test The Tester shall be capable of detecting stray voltage, as required prior to munitions load. Analysis
SRD_1.1.2.14
Unit Under Test Fault Detection
The Tester shall detect 100 percent of detectable faults of system LRU failures, based on the available data offered by on-aircraft or off-aircraft equipment. A detectable fault is a failure of the UUT that is exhibited at the interface of the UUT and is outside the defined performance parameter or threshold for that particular function.
Analysis
SRD_1.1.2.15 Unit Under Test Cooling
The Tester shall provide a means to interface with UUT cooling carts when required. Analysis
SRD_1.1.2.16 Interface Test Adapters
TPS ITAs shall not utilize active circuit components without prior Government approval. Analysis
SRD_1.1.2.17
Functional and Parametric Test Data
Functional and Parametric data for both instruments and test stations should be formatted IAW ATML standards specified in IEEE 1671.2, IEEE 1871.1, as well as IEEE 1671.6 and 1871.2 respectively.
Analysis
SRD_1.1.2.18
Master Conformance Index
The Master Conformance Index present within the Tester shall be developed IAW IEEE 1671.4 ATML Test Configuration.
Analysis
SRD_1.1.2.19
Receiver Adapter Interface
The Receiver Adapter Interface present within the Tester shall be developed IAW IEEE 1641 Annex K.
Analysis
SRD_1.1.2.20
UUT Test Requirements and Product Design Data
UUT Test Requirements and Product Design Data shall be defined and designed respectively IAW IEEE 1671.1 ATML Test Description, as well as ANSI/EIA 682, Electronic Design Interchange Format (EDIF), and IEEE
1671.3 ATML UUT Description.
Analysis
SRD_1.1.2.21
Digital Test Interchange Format
Interchangeable data present within the Tester shall be formatted IAW IEEE 1445 Digital Test Interchange Format (DTIF).
Analysis
SRD_1.1.2.22
Test Program Documentation
All documentation referring to the Test Programs shall be developed
IAW
IEEE P1671.1 ATML Test Description, and IEEE 1671 Annex C.2 ATML Wire list Schema.
Analysis
SRD_1.1.2.23 Design for Testability
Designs for Testability will be created IAW IEEE 1149.1 Test Access Port and Boundary-Scan Architecture, IEEE 1149.4 Mixed Signal Test Bus, and IEEE 1149.6 Boundary-Scan Testing of Advanced Digital Networks.
SRD_1.1.2.24
Adapter Functional and Parametric Data
Adapter Functional and Parametric Data shall be IEEE 1671.5 ATML Test Adapter, and IEEE 1871.2 Recommended Practice for Intrinsic Signal Path Information.
Analysis
SRD_1.1.2.25 Test Duration
(U) Total test time using the Common Handheld Tester and the Preload TPS/Kit (O-level MDS specific) shall be less than the current duration of all comparable operational and/or functional testing. The O-LVL 180-day testing time will not exceed 6 Hours and all testing at I- LVL will be under 1 hour per AME.
Test
SRD_1.1.2.26
Software Developer’s Guide
The contractor shall develop the TPS style guide IAW ATS standard Inspection
SRD_1.2 Legacy Testing
(U) The CAT-F will be capable of performing all current legacy armament system tests and meet required nuclear certification. The CAT-F will replace multiple current USAF fighter Aircraft armament testers and shall execute all legacy inspection and troubleshooting requirements. The tester will be required to conduct armament preload and fault isolation testing on active model versions of the F-16 and F-15 fleets. This tester should be considered as a replacement armament tester for the A-10 fleet and be a future consideration for newer generation fighters. To verify the requirement, the CAT-F will be tested in all operationally representative environments and on all appropriate fighter Aircraft. The results will be compared to the appropriate legacy tester.
Test
SRD_1.2.1 A-10 AME The tester shall be able to execute all A-10 AME requirements I.A.W.
the specific MDS Technical Orders. Demonstration
SRD_1.2.1.1
Stations 1 and 11 Pylon (with MAU-50 installed)
The tester shall be able to execute all Stations 1 and 11 Pylon (with MAU-50 installed) requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.1.2
Stations 2 and 10 Pylon (with MAU-50 installed)
The tester shall be able to execute all Stations 2 and 10 Pylon (with MAU-50 installed) requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.1.3
Stations 3 & 9 Pylon (with MAU-40 installed
The tester shall be able to execute all Stations 3 & 9 Pylon (with MAU- 40 installed requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.1.4
Stations 4 & 8 Pylon (with MAU-40 installed)
The tester shall be able to execute all Stations 4 & 8 Pylon (with MAU- 40 installed) requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.1.5
Station 5 Pylon (with MAU-40 installed)
The tester shall be able to execute all Station 5 Pylon (with MAU-40 installed) requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.1.6
Station 6 Pylon (with MAU-40 installed)
The tester shall be able to execute all Station 6 Pylon (with MAU-40 installed) requirements I.A.W. the specific MDS Technical Orders.
SRD_1.2.1.7
Station 7 Pylon (with MAU-40 installed)
The tester shall be able to execute all Station 7 Pylon (with MAU-40 installed) requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.1.8
TER-9/A or Variant installed
The tester shall be able to execute all TER-9/A or Variant installed requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.1.9
Dual Rail Adaptor (DRA) with LAU-105s and LAU-128 installed
The tester shall be able to execute all Dual Rail Adaptor (DRA) with LAU-105s and GMIU installed requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.1.10 LAU-131 The tester shall be able to execute all LAU-131 requirements I.A.W.
the specific MDS Technical Orders. Demonstration
SRD_1.2.1.11 Chaff Flair The tester shall be able to execute all Chaff Flair requirements I.A.W.
the specific MDS Technical Orders. Demonstration
SRD_1.2.1.12 LAU-117 The tester shall be able to execute all LAU-117 requirements I.A.W.
the specific MDS Technical Orders. Demonstration
SRD_1.2.1.13 BRU-61 The tester shall be able to execute all BRU-61 requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.1.14 LAU-88 The tester shall be able to execute all LAU-88 requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.1.15 Gun Control Unit The tester shall be able to execute all Gun Control Unit requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.1.16 Pylon 5CU-A/SCU-8 The tester shall be able to execute all Pylon 5CU-A/SCU-8 requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.1.17 AN/ALE-47 CMDS The tester shall be able to execute all AN/ALE-47 CMDS requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.1.18 LAU-128 The tester shall be able to execute all LAU-128 requirements I.A.W.
the specific MDS Technical Orders. Demonstration
SRD_1.2.2 F-15 AME The tester shall be able to execute all F-15 AME requirements I.A.W.
the specific MDS Technical Orders. Demonstration
SRD_1.2.2.1 PYLON The tester shall be able to execute all PYLON requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.2.2 BRU-46/47 The tester shall be able to execute all BRU-46/47 requirements I.A.W.
the specific MDS Technical Orders. Demonstration
SRD_1.2.2.3 BRU-61 The tester shall be able to execute all BRU-61 requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.2.4
CBU-103105,107,118
System Check
The tester shall be able to execute all CBU-103105,107,118 System Check requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.2.5 GBU-31 (JDAM)
System Check
The tester shall be able to execute all GBU-31 (JDAM) System Check requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.2.6 GUB-31B UAi System Check
The tester shall be able to execute all GUB-31B UAi System Check requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.2.7 M-61A1 The tester shall be able to execute all M-61A1 requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.2.8 AIm-9M Missile System
The tester shall be able to execute all AIm-9M Missile System requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.2.9
GBU-38 UAI/GBU-54
UAI System Check
The tester shall be able to execute all GBU-38 UAI/GBU-54 UAI System Check requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.2.10 AGM-158 UAI System Check
The tester shall be able to execute all AGM-158 UAI System Check requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.2.11
AIM-9X/X-2 Missile System
The tester shall be able to execute all AIM-9X/X-2 Missile System requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.2.12
AIM-120 LAU-106
Missile Systems
The tester shall be able to execute all AIM-120 LAU-106 Missile Systems requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.2.13
AIM-120 LAU-128
Missile System
The tester shall be able to execute all AIM-120 LAU-128 Missile System requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.2.14
Jettison Checks Without Fuel Tanks
The tester shall be able to execute all Jettison Checks Without Fuel Tanks requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.2.15
Jettison Checks with Fuel Tanks
The tester shall be able to execute all Jettison Checks with Fuel Tanks requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.2.16
BRU-46/47 Single Carriage (Pylon)
The tester shall be able to execute all BRU-46/47 Single Carriage (Pylon) requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.2.17 BRU-47 The tester shall be able to execute all BRU-47 requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.2.18 SUU-20 The tester shall be able to execute all SUU-20 requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.2.19 MAU-12 The tester shall be able to execute all MAU-12 requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.2.20 LAU-128 (AIM-9L/M) The tester shall be able to execute all LAU-128 (AIM-9L/M) requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.2.21 LAU-128 (AIM-120) The tester shall be able to execute all LAU-128 (AIM-120) requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.2.22 LAU-120 (AIM-120) The tester shall be able to execute all LAU-120 (AIM-120) requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.2.23 GBU-39 UAI System Check
The tester shall be able to execute all GBU-39 UAI System Check requirements I.A.W. the specific MDS Technical orders. Demonstration
SRD_1.2.2.24 GBU-53 UAI System Check
The tester shall be able to execute all GBU-53 UAI System Check requirements I.A.W. the specific MDS Technical orders. Demonstration
SRD_1.2.2.25
Multipurpose Booster (MPB) UAI System Check
The tester shall be able to execute all MPB UAI System Check requirements I.A.W. the specific MDS Technical orders.
Demonstration
SRD_1.2.2.26 ALE-58A System Check The tester shall be able to execute all ALE-58A System Check requirements I.A.W. the specific MDS Technical orders. Demonstration
SRD_1.2.2.27 SUU-60B/A The tester shall be able to execute all SUU-60B/A requirements I.A.W. the specific MDS Technical orders. Demonstration
SRD_1.2.2.28 SUU-59B/A The tester shall be able to execute all SUU-59B/A requirements I.A.W. the specific MDS Technical orders. Demonstration
SRD_1.2.2.29 SUU-59C/A The tester shall be able to execute all SUU-59C/A requirements I.A.W. the specific MDS Technical orders. Demonstration
SRD_1.2.2.30 SUU-73/A The tester shall be able to execute all SUU-73/A System Check requirements I.A.W. the specific MDS Technical orders. Demonstration
SRD_1.2.2.31
Missile Launcher Auxiliary Relay Panel Check
The tester shall be able to execute all Missile Launcher Auxiliary Relay Panel Check requirements I.A.W. the specific MDS Technical orders.
Demonstration
SRD_1.2.2.32 IRST Pod System Check The tester shall be able to execute all IRST Pod System Check requirements I.A.W. the specific MDS Technical orders. Demonstration
SRD_1.2.2.33 B61 UAI System Check The tester shall be able to execute all B-61 UAI System Check requirements I.A.W. the specific MDS Technical orders. Demonstration
SRD_1.2.3 F-16 AMU The tester shall be able to execute all F-16 AME requirements I.A.W.
the specific MDS Technical Orders. Demonstration
SRD_1.2.8.1
Preload Functional Checks, 7560 Replacement Tess, Pre- Block Aircraft
The tester shall be able to execute all Preload Functional Checks, 7560 Replacement Tess, Pre-Block Aircraft requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.1.1
MAU--12 on Aircraft The tester shall be able to execute all MAU--12 on Aircraft requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.1.2
External Fuel Tank Pylon on Aircraft
The tester shall be able to execute all External Fuel Tank Pylon on Aircraft requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.1.3
AIM 9 Missile Launcher on Aircraft
The tester shall be able to execute all AIM 9 Missile Launcher on Aircraft requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.1.4
LAU-129 Missile Launcher on Aircraft
The tester shall be able to execute all LAU-129 Missile Launcher on Aircraft requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.1.5 TER-9A on Aircraft The tester shall be able to execute all TER-9A on Aircraft requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.8.1.6
On Aircraft Launcher Umbilical Only
The tester shall be able to execute all On Aircraft Launcher Umbilical Only requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.1.7 SUU-20 on Aircraft The tester shall be able to execute all SUU-20 on Aircraft requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.8.1.8
M61A1 20MM Gun System Control Circuits / Gun Control Unit
(GCU)
The tester shall be able to execute all M61A1 20MM Gun System Control Circuits / Gun Control Unit (GCU) requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.1.9
On Aircraft WWP 1760 Umbilical Only
The tester shall be able to execute all On Aircraft WWP 1760 Umbilical Only requirements I.A.W. the specific MDS Technical Orders.
SRD_1.2.8.1.10 SCRIU Equipped WWP The tester shall be able to execute all SCRIU Equipped WWP requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.8.1.11 BRU-57 on Aircraft The tester shall be able to execute all BRU-57 on Aircraft requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.8.2
Preload Functional Checks-75060 Replacement Tests, Post-Block Aircraft
The tester shall be able to execute all Preload Functional Checks- 75060 Replacement Tests, Post-Block Aircraft requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.2.1 MAU-12 on Aircraft The tester shall be able to execute all MAU-12 on Aircraft requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.8.2.2
External Fuel Tank Pylon on Aircraft
The tester shall be able to execute all External Fuel Tank Pylon on Aircraft requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.2.3 TER-9A on Aircraft The tester shall be able to execute all TER-9A on Aircraft requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.8.2.4
AIM-9 Missile Launcher on Aircraft
The tester shall be able to execute all AIM-9 Missile Launcher on Aircraft requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.2.5
LAU-129 Missile Launcher on Aircraft
The tester shall be able to execute all LAU-129 Missile Launcher on Aircraft requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.2.6
LAU-118 Missile Launcher on Aircraft
The tester shall be able to execute all LAU-118 Missile Launcher on Aircraft requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.2.7 On Aircraft Launcher Umbilical Only LAU- 117
The tester shall be able to execute all On Aircraft Launcher Umbilical Only LAU-117 requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.2.8
On Aircraft Launcher Umbilical only LAU 118 Launcher
The tester shall be able to execute all On Aircraft Launcher Umbilical only LAU 118 Launcher requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.2.9
On Aircraft Rocket Launcher Umbilical only
The tester shall be able to execute all On Aircraft Rocket Launcher Umbilical only requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.2.10 SUU-20 on Aircraft The tester shall be able to execute all SUU-20 on Aircraft requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.8.2.11
M61A1 20MM Gun System Control Circuits / Gun Control Unit (GCU)
The tester shall be able to execute all M61A1 20MM Gun System Control Circuits / Gun Control Unit (GCU) requirements I.A.W. the specific MDS Technical Orders.
SRD_1.2.8.2.12
On Aircraft WWP, 1760 Umbilical Only
The tester shall be able to execute all On Aircraft WWP, 1760 Umbilical Only requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.2.13 BRU-57 on Aircraft The tester shall be able to execute all BRU-57 on Aircraft requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.8.2.14 Under Wing Adapter The tester shall be able to execute all Under Wing Adapter requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.8.2.15 ALE-50 Pylon on Aircraft
The tester shall be able to execute all ALE-50 Pylon on Aircraft requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.8.2.16 BRU-46 on Aircraft The tester shall be able to execute all BRU-46 on Aircraft requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.8.2.17 Left Hardpoint Interface
The tester shall be able to execute all Left Hardpoint Interface requirements I.A.W. the specific MDS Technical Orders. Demonstration
SRD_1.2.8.2.18
Right Hardpoint Interface
The tester shall be able to execute all Right Hardpoint Interface on Aircraft requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.3
O Level Stores System Tester (SST) - Replacement Tests
The tester shall be able to execute all O Level Stores System Tester (SST) - Replacement Tests requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.3.1
Aircraft station 1, 2, 3 a, 8 and 9 interface connection circuits
The tester shall be able to execute all Aircraft station 1, 2, 3a, 8 and 9 interface connection circuits requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.3.2
Aircraft station 3, 4, 6 and 7 interface connection circuits
The tester shall be able to execute all Aircraft station 3, 4, 6 and 7 interface connection circuits requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.3.3
Aircraft station 5 (centerline station) interface connection circuits Pre ASQ-236 Modifications
The tester shall be able to execute all Aircraft station 5 (centerline station) interface connection circuits Pre ASQ-236 Modifications requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.3.4
Aircraft station 5 (centerline station) interface connection circuits Post ASQ-236 Modifications
The tester shall be able to execute all Aircraft station 5 (centerline station) interface connection circuits Post ASQ-236 Modifications requirements I.A.W. the specific MDS Technical Orders.
SRD_1.2.8.3.5
ASQ-236 Centerline Pylon on Aircraft, station 5
The tester shall be able to execute all ASQ-236 Centerline Pylon on Aircraft, station 5 requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.3.6
Centerline Pylon on Aircraft, station 5
The tester shall be able to execute all Centerline Pylon on Aircraft, station 5 requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.3.7
AIM - 9 Launcher on Aircraft, on stations 1, 2,3A, 7A, 8, 9
The tester shall be able to execute all AIM - 9 Launcher on Aircraft, on stations 1, 2,3A, 7A, 8, 9 requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.3.8
LAU-129 Launcher on Aircraft, on stations 1, 2, 3A, 7A, 8, 9
The tester shall be able to execute all LAU-129 Launcher on Aircraft, on stations 1, 2, 3A, 7A, 8, 9 requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.3.9
1760 or non-1760 Wing Weapon Pylon Equipped with Special Carry Remote Interface Unit (SCRIU) on Aircraft, stations 3 and 4
The tester shall be able to execute all 1760 or non-1760 Wing Weapon Pylon Equipped with Special Carry Remote Interface Unit (SCRIU) on Aircraft, stations 3 and 4 requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.3.10
Non - 1760 equipped Wing Weapon Pylon on Aircraft, stations 3, 4, 6, 7 (MIL - STD-
1760) W20 Check
The tester shall be able to execute all Non - 1760 equipped Wing Weapon Pylon on Aircraft, stations 3, 4, 6, 7 (MIL - STD-1760) W20 Check requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.3.11
1760 equipped Wing Weapon Pylon on Aircraft stations 3, 4, 6, 7 (MIL - STD-1760}
(W20 Long Check)
The tester shall be able to execute all 1760 equipped Wing Weapon Pylon on Aircraft stations 3, 4, 6, 7 (MIL - STD-1760} (W20 Long Check) requirements I.A.W. the specific MDS Technical Orders.
SRD_1.2.8.3.12
1760 equipped Wing Weapon Plon on Aircraft, stations 3, 4, 6, 7 (MIL-STD-1760)
(W20 Short Check, 1760 only)
The tester shall be able to execute all 1760 equipped Wing Weapon Plon on Aircraft, stations 3, 4, 6, 7 (MIL-STD-1760) (W20 Short Check, 1760 only) requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.3.13
Aircraft station 5B interface connection circuits ( Right Hardpoint Interface Checkout 5R)
The tester shall be able to execute all Aircraft station 5B interface connection circuits ( Right Hardpoint Interface Checkout 5R) requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.3.14
Aircraft station 5L interface connection circuits (Left Hardpoint interface Checkout 5L)
The tester shall be able to execute all Aircraft station 5L interface connection circuits (Left Hardpoint interface Checkout 5L) requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.4
Troubleshooting (94FI) Checks - 75060 ACPTS and SST
The tester shall be able to execute all Troubleshooting (94FI) Checks - 75060 ACPTS and SST requirements I.A.W. the specific MDS Technical Orders.
Demonstration
SRD_1.2.8.4.1 Gun System Analysis
SRD_1.2.8.4.2
Multiple Release - Procedures
SRD_1.2.4 Cables/Adapters
Cables/Adapters will be MDS specific. All Cables and Adapter required to execute testing will be provided in MDS specific kits. Each MDS platform will require cable and adapter kits for the O-Level pre-load, O- Level Fault Isolation, and I-level Fault Isolation testing requirements.
Demonstration
SRD_1.3
Future Armament Testing Requirements
(U) The CAT-F design will include the capability to upgrade by using the Computer Program Identification Number (CPIN) management process to sustain tester upgrades and modification during the tester’s life cycle. The developed CAT-F will be built using an open system software architecture that allows for future upgrades and modifications. In addition to software upgrades, the CAT-F shall utilize as much as possible Modular Open Systems Approach (MOSA) design for tester hardware and sustainment. Vendor will be required to submit all requested data to gain government engineering acceptance/approval for the MOSA standard and upgrade capability for software and hardware.
SRD_1.4
Nuclear Certification
Nuclear certification for the Tester and applicable nuclear platform TPSs shall be in accordance with AFI 63-125 (Nuclear Certification Program), AFI 91-103, AFI 91-107, AFMAN 91-118, AFMAN 91-119, and
MIL-STD-1822.
SRD_1.4.1
System Safety
System safety for the Tester shall be conducted IAW the requirements of MIL-STD-882E. The Tester design shall be compliant with requirements defined by AFMAN91-118 and AFMAN91-119.
SRD_1.4.1.1
Single Failures
The Tester shall be designed such that no single component failure, common mode failure, human error, or a design feature shall cause a mishap of catastrophic or critical mishap severity categories as defined in MIL-STD-882E.
SRD_1.4.1.2
Dual Failures
The Tester shall be designed such that no dual independent component failures, dual independent human errors, or a combination of a component failure and a human error involving safety critical command and control functions, shall cause a mishap of catastrophic or critical mishap severity categories.
SRD_1.4.1.3
Design Safety – Critical Functions
The Tester design shall prevent faults in the test equipment or test circuits that could operate critical functions or apply unintended power to the Tester interface.
SRD_1.4.1.4
Design Safety – Internal Faults
The Tester design shall prevent internal faults within the tester that could degrade the nuclear or conventional safety of the equipment to be tested.
SRD_1.4.1.5
Unintended Signals
The Tester design shall prevent the introduction of signals, voltages, or currents into the Tester system that could degrade nuclear or conventional safety of the equipment to be tested.
SRD_1.4.1.6
Unintended Firing
The Tester shall prevent operation or firing of an item under test, except when specifically designed for that purpose.
SRD_1.4.1.7
Test Safety – End of Test
The Tester shall ensure any devices, which has been operated during testing, is in the safe or inactivated position when the test ends. A positive indication verifies the safe position of such components.
SRD_1.4.1.8
Test Safety – System Failures
The Tester failures or shutdowns shall leave the components under test in a safe or inactivated condition. The Tester shall provide a clear indication of UUT failure status.
SRD_1.4.1.9
Electromagnetic Environmental Effects Requirements
The Tester shall be compatible with ordnance classified as Hazards of Electromagnetic Radiation to Ordnance (HERO) SAFE ORDNANCE IAW the requirements of MIL-STD-464C, section 5.9.3, Table 9, as well as
MIL-STD-461.
SRD_1.5
Systems external interface requirements
The Tester shall accommodate the Unit Under Test (UUT), ancillary equipment, and site interfaces defined below and by reference.
TBD
SRD_1.5.1
Unit Under Test (UUT) external interface description
The UUT interface shall be used to provide AC power, DC power, analog and digital stimuli to the UUTs and measure AC power, DC power, analog and digital signals from the UUTs through the Tester UUT interface.
SRD_1.5.1.1
UUT communication busses
Specify the communication buses the tester shall provide The following communication interfaces shall be provided by the Tester.
TBD
SRD_1.5.1.1.1 MIL-STD-1553
The MIL-STD-1553 bus interface shall operate as specified in MIL-STD-1553A/B and shall provide an interface for both direct and transformer coupled buses. The following modes of operation shall be supported: Bus controller (BC), Remote terminal (RT), and Bus monitor
(BM).
Demonstration
SRD_1.5.1.1.2 MIL-STD-1760 Pull information from AME interface
SRD_1.5.1.2 UUT Discrete Interfaces
SRD_1.5.2 Power
SRD_1.5.2.1 Operating Power
List associated voltages (including phases, type of current, and voltage ratings.
The Tester shall be capable of operating from 28 VDC and 120/240 VRMS 50 Hz, 60 Hz, and 400 Hz AC (single and multi-phase). Operating power shall comply with the requirements listed in MIL-PRF-28800, MIL-STD-704 and MIL-STD-1332. Automatic and operator initiated shutdown shall provide an orderly, sequential system shutdown to preclude damage to the Automatic Test Equipment (ATE) or UUT and shall not degrade the ATE hardware or software.
Operating power for the Tester computer/controller shall have the capability of being isolated from the test power being used to power the UUTs.
Analysis
SRD_1.5.2.1.1
Handheld Tester Power
(U) The CAT-F Handheld Tester will be powered by common design batteries which are non- proprietary, non-rechargeable and replaceable in minimal amount of time. Preload testing will utilize battery power for all go/no-go preload and stray voltage testing. In addition to having the required battery power, user should have the option to use aircraft or Aerospace Ground Equipment (AGE) power for preload testing. Power adapter cables must be provided for all user power options. Verification of handheld preload testing can be accomplished without the use of external power (AGE, Aircraft, building etc.). Verification team will ensure the handheld tester internal batteries can be replaced in under 2 minutes. If required, the verification team will ensure preload testing can easily utilize AGE, Aircraft, and backshop building power to execute requirements.
Demonstration
SRD_1.5.2.1.2
Fault Isolation Tester Power
(U) This equipment shall utilize electric power in accordance with MIL- STD-704 and shall be in accordance with the utilization equipment requirements of MIL-STD-704. As a minimum the primary power source shall operate at 100-240V@400 Hz and 28VDC IAW MIL- STD-704 and include adapters to utilize both aircraft, AGE, and backshop power.
SRD_1.5.2.2 Unit Under Test Power
The Intermediate Tester shall be capable of switching external power as required by the UUT. The Tester shall control on/off switching of power to the UUT as required by the UUT TPS.
Operating power for the Tester computer/controller shall have the capability of being isolated from the test power being used to power the UUTs.
Demonstration
SRD_1.5.2.3 Circuit Protection
(U) The CAT-F tester will be developed with built in Circuit protection.
The design will ensure the users, CAT-F, and Unit Under Test (UUT) are protected from improper voltage or amperage. Circuit Protection can be obtained by using a traditional fuse designed to ‘blow’ when a circuit is overloaded and easily replaced or by incorporating a circuit breaker that features a switch designed to trip by improper conditions. The switch then can simply be flip back into the ‘on’ position to restore power to the tester, providing no additional repairs are required. Verification of KPP2 will be accomplished by applying enough input power to blow fuse or trip circuit breaker in the designed tester, followed by replacing blown fuse or resetting breaker and verify the tester circuits were not damaged. The appropriate sections of MIL-STD-704 (Aircraft Electrical Power Characteristics) will be identified to ensure power requirements for circuit protection are followed.
Test
SRD_1.5.2.4 Power Monitoring
The Intermediate Tester shall measure input power, VRMS for each phase, phase sequence, and frequency information as follows:
a. As part of the power-up sequence.
b. At the start of all test sequences.
c. During each step while the test load is still connected. Report as part of the data for each failure, or for each step if in manual mode.
The Tester shall detect and respond to the presence of more than 6 VRMS between the Neutral and Chassis Ground as follows:
i. If during power-up, notify the operator of a power fault and prevent the Tester power-up sequence.
ii. If during operation, notify the operator and perform an orderly shutdown.
Test
SRD_1.5.2.5
Handheld Power Monitoring
Handheld Tester shall display handheld battery status
Tester shall display battery status warning at designated percentages that would impact test execution
TBD
SRD_1.5.3 Grounding
SRD_1.5.3.1
Controlled Grounding Concept
A controlled grounding concept shall be used so that grounding will not adversely impact the functional testing/operation of the UUT. This concept shall provide for a single point ATE signal ground as well as a single point safety ground IAW the guidelines of MIL-HDBK-419.
SRD_1.5.3.2
Shock Protection
The grounding scheme for the Tester shall provide protection of personnel and equipment from electrical shock hazards during normal operations and under ground fault conditions.
SRD_1.5.3.3
Ground Loop Prevention
The Tester shall be designed to eliminate ground loops and minimize common ground impedance which can degrade system noise margins.
SRD_1.5.3.4 External Safety Ground
The Intermediate Tester shall provide an external safety ground stud or bar. Demonstration
SRD_1.5.4 Graphical Display
SRD_1.5.4.1
Graphical Display Size
The display shall be adequately sized to clearly show at a minimum all applicable information as defined in specification paragraph 3.1.2.2 (e.g., status, menus, test data, fault codes, messages, etc.) in a manner that is easily readable by the user. The display shall meet the requirements of MIL-STD-1472, Section 5.2.
SRD_1.5.4.2
Graphical Display Readability
The display shall be readable in all lighting conditions, including full daylight ambient conditions; direct sunlight; and night time IAW MIL-STD-1472G, Section 5.2. The brightness setting shall not allow the display to "black-out".
SRD_1.5.4.3
Graphical User Interface
The Intermediate Tester graphical user interface functions shall enable the operator to interact with the test system, to include but not be limited to, enabling TPS diagnostic advancement and/or referral to alternate test instructions, explanations and/or troubleshooting trees;
authentication; test instruction initiation and/or termination; and test result save commands as necessary to achieve UUT test requirements.
SRD_1.5.4.4
User Navigation
The Tester shall provide controls to allow the operator to move between pages of display information, between selection options, and selection of a menu item/option.
SRD_1.5.4.5
Handheld
(U) Common Handheld Tester Display Size shall depend on final tester dimensions. Screen should follow current military standards with sunlight readable graphic display with resolution at least 128 X 64 pixels or better, and different screen background. The handheld tester display will be at a minimum 1.5 inches by 2.5 inches in Viewable Area.
SRD_1.6
Modular Open System Architecture Design
SRD_1.6.1
Modular Design
b. Modular, Open Design – The contractor shall develop an architecture that is layered and modular and uses standards-based hardware interfaces, operating systems, and middleware that all utilize either non-proprietary or non-vendor-unique key module or component interfaces. The contractor’s design approach shall be applied to all subsystems and components.
SRD_1.6.1.1 Module Cohesion
ii. Module Cohesion – The contractor’s design shall result in modules that are characterized by the singular assignment of identifiable and discrete functionality (high cohesion). The purpose is to ensure that any changes to system behavioral requirements can be accomplished by changing a minimum number of modules within the system.
Analysis
SRD_1.6.1.2 Module Coupling
i. Module Coupling – The contractor’s design approach shall result in modules that have minimal dependencies on other modules (loose coupling), as evidenced by simple, well-defined interfaces and by the absence of implicit data sharing. The purpose is to ensure that any changes to one module will not necessitate extensive changes to other modules, and hence facilitate module replacement and system enhancement.
Analysis
SRD_1.6.2 Open Architecture
a. Open Architecture – The contractor shall develop and maintain an architecture that incorporates appropriate considerations for re-configurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability.
Analysis
SRD_1.6.3
Requirements…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .