DI-TMSS-81760A

Operational Test Program Instruction/Test Program Instruction (OTPI/TPI)

Specifies the format and content requirements for an Operational Test Program Instruction/Test Program Instruction (OTPI/TPI), which provides connection instructions and data used to troubleshoot elements of an Operational Test Program Set (OTPS).

Approval DateMay 2, 2025

AMSC NumberN10560

Preparing ActivitySA

Project NumberTMSS-2025-012

OPR—

DTIC Applicable—

GIDEP Applicable—

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

DI-TMSS-81760

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

An Operational Test Program Set (OTPS) is a collection of hardware, software and data to test Avionics items (all from the same Aircraft or Weapons System) of similar characteristics and functions. By grouping these Avionics items, the hardware, software and data needed by Automatic Test System operators is minimized.

The OTPI is a collection of TPIs that share this hardware, software and data. The TPIs provide connection instructions and data used to trouble-shoot the individual elements of the OTPS.

This DID supersedes DI-TMSS-81760.

Preparation Instructions

1Reference documentThe applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.

2GeneralThe Operational Test Program Instruction/Test Program Instruction (OTPI/TPI) specified herein shall be in a digital form.

3FormatThe OTPI/TPI shall conform to the general guidelines for planning and preparation of the Work Package (WP) concept defined in NAVAIR 00-25-700 as applied to the TPI contents contained herein.

3.1Page layoutThe OTPI/TPI shall consist of all text pages including tabular data and illustrations in a form suitable for display on a computer screen. Text shall be single column single spaced, with a left justified margin. Text shall be double spaced between paragraphs, procedural steps, and before and after warnings, cautions, and notes.

3.1.1Margins(see figure 1.) All page margins, including title/cover pages must have a left margin of one inch and a right margin of one-half inch. Top and bottom margins shall be one-half inch.

3.1.2Page size(see figure 1.) Page sizes shall be limited to two sizes:

a8 1/2 inches (width) by 11 inches (length)

b17 inches (width) by 11 inches (length)

3.1.3Text image area

aPage size 8 1/2 x 11 inchesThe text and illustration image area is 7 inches wide and 10 inches high.

bPage size 17 x 11 inchesThe text and illustration image area in 15 1/4 inches wide and 10 inches in length.

3.1.4Type SizeThe text type size for all OTPIs/TPIs shall have a minimum typeface of 8 points and a maximum of 12 points.

3.1.5IndentationIndentation shall be consistent with paragraph 3.2.5.

3.2Numbering

3.2.1OTPI NumberEach OTPI number shall be assigned a permanent number in accordance with the contract.

3.2.2TPI numberEach TPI number shall be assigned a permanent number in accordance with the contract.

3.2.3Work package numberEach TPI work package (WP) number shall be assigned as specified herein (see 3.5 below).

3.2.4Page numbersPages shall be numbered consecutively within each WP using Arabic numerals beginning with the number one. On WP title pages, the page number and count shall be placed below the WP number in 10- to 12-point bold type right justified with the WP number; for example, "Page 1 of 20." On second and subsequent WP pages, only the page number shall appear.

3.2.5Paragraph numbersTPI paragraphs shall be numbered as follows:

aParagraph and subparagraph divisionsParagraph and subparagraph divisions shall be numbered consecutively for every field of information. Paragraphs within a WP having subparagraphs shall be numbered consecutively by a decimal numbering system as follows: 1. PRIMARY PARAGRAPH 1.1 SECONDARY SUBPARAGRAPH 1.1.1 Tertiary Subparagraph 1.1.1.1 Quaternary subparagraph

bIntroductory matter and technical content textIntroductory matter and technical content text shall contain one or more main paragraphs which may be divided into subordinate paragraphs. Major paragraphs shall have a brief underlined heading describing the content or action portrayed.

cFor clarity, paragraph numbering should be limitedFor clarity, paragraph numbering should be limited to three sub-levels unless additional sub-levels are unavoidable.

3.2.6Illustrations and table numbersIllustrations and tables within a WP shall be numbered consecutively in Arabic numerals beginning with the number one.

3.2.6.1IllustrationsEach sheet of a multi-sheet illustration shall be identified by a sheet number following the figure number and title below the illustration. Each sheet shall include the total number of sheets that make up the figure; for example, "Figure 2. Inertial Sensor Element Assembly Test Diagram (Sheet 1 of 5)." Remaining sheets shall be numbered in consecutive order, Sheet 2 of 5, Sheet 3 of 5, and so forth.

3.2.6.2TablesEach table shall be identified by a table number and an underlined title above the table. Each sheet of a multi-sheet table shall include the total number of sheets that make up the table; for example, "Table 2. Command message data content. (Sheet 1 of 5)". Remaining sheets shall be numbered in consecutive order, Sheet 2 of 5, Sheet 3 of 5, and so forth.

3.2.7Blank page numbersA Blank page shall be assigned a number, but it shall appear on the preceding page; e.g., if page 10 is blank, page 9 shall bear the number "9/ (10 blank)." Alternatively, the numbered page is annotated "This page intentionally left blank."

3.3Warnings, cautions, and notesWarnings, cautions, and notes shall be used to introduce items of information which are parenthetical (cannot logically be included in the text) and which the writer feels must be emphasized. A warning or caution shall immediately precede the text to which it refers.

3.3.1Use of symbolsThe symbols should be used sparingly, consistent with real need. Titles are identified by the following labeling:

aWarningThe warning title shall be capitalized with a 1-point rule above and below the title.

bCautionThe caution title shall be capitalized with a 1-point rule below the title.

cNoteThe note title shall be capitalized.

3.3.2Headings and textWarning, caution and note headings shall precede the text to which they apply. The text shall not contain procedural steps, direct maintenance actions, or be numbered. Warnings and cautions may be worded positively or negatively and shall state the hazard and result or reason for the instruction or the consequences if not heeded, unless obvious.

3.3.3PlacementThe title shall be in the horizontal center of the page. None of the three are ever plural (i.e., "NOTES" is not acceptable). The text of a warning, caution, or note is centered horizontally under its title. If several distinct items of information are to be covered at the same time and all are of the same type (i.e., more than one warning, caution, or note), include all under the single appropriate heading, number each item and double space between items. Avoid having cautions, warning or notes follow each other consecutively without intervening text. The text of warnings, cautions, or notes shall not be divided at the end of a page.

3.3.4Use of warnings, cautions, and notes

3.3.4.1WarningUse a warning for information which, if not regarded might result in injury to personnel.

3.3.4.2CautionUse a caution for information which, if not regarded, might result in damage to equipment.

3.3.4.3NoteUse a note for information which is too bulky to be included internally within parentheses. In most instances, a note should immediately follow the text to which it refers, but it may precede if the context demands. For example, in text procedures, it may be desirable to tell the reader that if certain conditions are met, then certain succeeding steps can be omitted. A figure note has an initial capital and is not underscored.

3.4Use of abbreviations, acronyms, and termsIndividual words and word combinations can only be abbreviated when their meaning is unquestionably clear. When in doubt, the word(s) must be spelled out.

3.5Work package numbering systemEach WP shall be assigned a permanent number in accordance with 5. below.

3.5.1Work package number assignmentEach WP number shall have a five digit number, beginning with the number WP 001 00. There shall be one blank space between the third and fourth numerals.

3.5.2Assignment of the last two digits of the work package numberThe last two digits of any WP number may be assigned by the developer/contractor in the basic issue and by the cognizant activity in any change cycle following distribution of the basic issue.

4OTPIThe OTPI consists of front matter and, if applicable, common technical WPs.

4.1OTPI Front MatterFront Matter consists of the following (see figure 9): OTPI Title Page OTPI Master Index of TPIs (normally page 2) OTPI Record of Revisions/Changes (normally page 3)

4.1.1OTPI Title page(see figure 2.) A title page shall serve as the cover for the OTPI. The title page shall provide sufficient information to correlate the OTPI to the Operational Test program Set (OTPS) and include the following:

aThe OTPI number shall be placed in the upper left cornerThe OTPI number shall be placed in the upper left corner of the page. Each manual or volume shall have a separate number assigned. The OTPI number shall be in 18- to 20-point bold type.

bA 1-point rule shall be placed 1 1/2 inches from the topA 1-point rule shall be placed 1 1/2 inches from the top of the page below the OTPI number.

cThe title "OPERATIONAL TEST PROGRAM INSTRUCTION" shall be centeredThe title "OPERATIONAL TEST PROGRAM INSTRUCTION" shall be centered on the page below the 1-point rule, in 16- to 18-point type.

dThe words "FOR TESTING." shall be centered below the titleThe words "FOR TESTING." in 12- to 14-point type, shall be centered below the words "OPERATIONAL TEST PROGRAM INSTRUCTION" with the aircraft type/model/series centered below, both in 14- to 16-point bold type.

eThe aircraft system nomenclature being tested and model numberThe aircraft system nomenclature being tested and model number; for example, 'STANDARD ATTITUDE READING REFERENCE SYSTEM (SAHRS) AN/USN-2(V)' shall be centered below the aircraft type, in 16- to 18-point bold type.

fThe word 'USING' shall be centered below the aircraft system/model numberThe word 'USING' in 12- to 14-point type, shall be centered below the aircraft system/model number with the "AN" identification of the Automatic Test Equipment (ATE) test system, name and acronym (if any) of the test system, in 14- to 16-point type.

gCentered below the test system shall be the developing activity and contract numberCentered below the test system shall be the developing activity and contract number, in 10- to 12-point type.

hThe contract-specified distribution statement and warning statementThe contract-specified distribution statement and warning statement, as identified in the Contract Data Requirements List (CDRL), shall be left-justified below the developing activity and contract number in 10 pt. type. The words "DISTRIBUTION STATEMENT X." (where "X" is the contract-specified distribution statement letter) shall start the distribution statement and shall be bold and underlined. The word "WARNING - " shall start the warning notice and shall be bold and underlined.

jThe contract-specified destruction noticeThe contract-specified destruction notice, as identified in the Contract Data Requirements List (CDRL), shall be left-justified below the distribution and warning statements in 10 pt. type. The words "DESTRUCTION NOTICE - " shall start the destruction notice and shall be bold and underlined.

kA 1-point rule shall be placed 1 1/2 inches above the bottom of the page

lThe OTPI date shall be placed in the lower right cornerThe OTPI date shall be placed in the lower right corner, above the 1-point ruler in 10- to 12-point type.

mThe change number shall be placed above the OTPI dateThe change number shall be placed above the OTPI date, in 10- to 12-point type.

4.1.2OTPI Master Index(see figure 3.) The OTPI Master Index shall contain an index of TPIs for the entire manual. The index pages shall immediately follow the title page and always start on page two of the OTPI and include the following:

aThe OTPI publication number shall be placed in the upper left cornerThe OTPI publication number shall be placed in the upper left corner of the page, in 14- to 16-point bold type.

bThe page identification shall be placed in the upper right cornerThe page identification (Page 2, Page 3, etc.) shall be placed in the upper right corner of the page, in 10- to 12-point bold type.

cThe title "MASTER INDEX OF TEST PROGRAM INSTRUCTIONS" shall be centeredThe title "MASTER INDEX OF TEST PROGRAM INSTRUCTIONS" shall be centered, in 12- to 14-point bold type.

dColumn heads shall be placed below the titleColumn heads "TPI Number," "Title," "Volume Number" (if applicable), and "Change Number" shall be placed below the title. A 1-point rule shall be placed above and below the column heads.

eA linked and/or hyperlinked numerical listing of TPIsA linked and/or hyperlinked numerical listing of TPIs and common WPs assigned to the manual and the numbers, titles, volumes numbers (if applicable), and change number shall be placed below the applicable column heads.

4.1.3OTPI Record of revisions and changes (REVCHG)(see figure 4.) A list of revisions/changes incorporated shall be specified for all manuals. This page shall begin with the original issue of the OTPI coinciding with the delivery of the OTPS and subsequently maintained by the cognizant activity to list all subsequent revisions and changes. The REVCHG page(s) shall follow the index page and include the following:

aThe OTPI publication number shall be placed in the upper left cornerThe OTPI publication number shall be placed in the upper left corner of the page, in 16 point bold type.

bThe page identification shall be placed in the upper right cornerThe page identification (Page 3, Page 4, etc.) shall be placed in the upper right corner of the page on the same line as the OTPI publication number in 16 pt bold type.

cThe OTPI date or revision date shall be in the upper left cornerThe OTPI date or revision date shall be in the upper left corner below the publication number in 10- to 12-point type.

dThe title "OPERATIONAL TEST PROGRAM INSTRUCTION, RECORD OF REVISIONS/CHANGES" shall be centeredThe title "OPERATIONAL TEST PROGRAM INSTRUCTION, RECORD OF REVISIONS/CHANGES" shall be centered on the page below the publication number, in 12- to 14-point type, split into 2 lines at the comma.

eThe original issue date must be includedThe original issue date must be included and labeled "ORIGINAL ISSUE" with an appropriate date below title, in 10- to 12-point type.

fThe page shall be in column formatThe page shall be in column format with column heads TPI No,." REVCHG No.." "DATE," and "REASON FOR CHANGE." A 1-point rule shall be placed above and below the column heads.

4.2OTPI Common Technical WPsA technical content WP is considered common if it is applicable to more than one TPI in an OTPI. A common technical WP shall take the publication number of the OTPI. Common technical WPs are generally self-contained PDF files and include: WP 002 02 System Wiring Diagram and, if applicable: WP 003 02 Common Test Program Source Listing, and WP 003 04 Common Digital Test Program Source Listing. These files are accessed via hyperlinks from OTPI and TPI indexes.

4.2.1OTPI WP 002 02 System Wiring Diagram (SWD)The SWD is a diagram that shows all wiring and hardware devices between the Unit Under Test (UUT) and the ATE. The diagram shall show the "as-built", not the electrical equivalence of the wiring and hardware devices. See paragraph 5.2.1.4 for a detailed SWD description.

4.2.2OTPI WP 003 02 Common Source ListingConsists of formatted WP data per 5.2.1 immediately followed by a hyperlinked list of Source Code filenames (*.LU, *.AS and any others as appropriate) and procedure names. Each filename hyperlink shall connect to the beginning of the referenced file listing. Each procedure name hyperlink shall link to the particular common Source Code procedure.

4.2.3OTPI WP 003 04 Common Digital Source ListingConsists of formatted WP data per 5.2.1 immediately followed by a hyperlinked list of common Digital Source filenames (*.PMP, *.SYM and any others as appropriate) and procedure names. Each filename hyperlink shall connect to the beginning of the referenced file listing. Each procedure name hyperlink shall link to the particular Digital Source routine.

4.3OTPI/TPI security classificationThe classification of the OTPI/TPI shall be as defined in the Contract Data Requirements List (CDRL).

5TPIThe TPI consists of front matter and technical content WPs. (see figure 9): Front Matter Title Page TPI Numerical Index of Work Packages (normally Page 2), Revisions/Changes (normally page 3), and if applicable, List of peculiar Abbreviations/Acronyms used. Technical Content WPs WP 001 00 Supplemental Testing Data Optional: contains messages and/or graphics that are too complex for display by the TPS. WP 002 00 Test Diagnostic Information WP 002 01 Test Oriented Wire List (TOWL). hyperlink to OTPI WP 002 02 System Wiring Diagram. WP 003 00 Program source code information WP 003 01 Program source code. (hyperlink to OTPI WP 003 02 Common source listing.) WP 003 03 Digital Test program source listing. (hyperlink to OTPI WP 003 04 Common digital source listing.) WP 003 05+ Additional sub-WPs to accommodate other TPS source modules as applicable.

5.1TPI front matter

5.1.1TPI title page(see figure 5.) The TPI title page shall include the following:

aThe title page shall indicate the TPI publication numberThe title page shall indicate the TPI publication number in the upper left corner of the page, in 16- to 18-point bold type.

bA 1-point rule shall be placed 1 1/2 inches from the topA 1-point rule shall be placed 1 1/2 inches from the top of the page below the TPI number.

cThe title "TEST PROGRAM INSTRUCTION" shall be centeredThe title "TEST PROGRAM INSTRUCTION" shall be centered on the page below the 1-point rule, in 14- to 16-point bold type.

dThe words "FOR TESTING," shall be centered below the titleThe words "FOR TESTING," in 12- to 14-point type, shall be centered below the words "TEST PROGRAM INSTRUCTION" with the UUT nomenclature and part number centered below, both in 16- to 18-point bold type.

eThe word "USING" shall be centered below the UUT nomenclatureThe word "USING" shall be centered below the UUT nomenclature with the "AN" identification of the ATE test system, name and acronym (if any) of the test system, in 10- to 12-point type.

fThe words "PART OF" shall be placed in the lower left cornerThe words "PART OF" shall be placed in the lower left corner above the 1-point rule with the OTPI publication number and date identified, in 10- to 12-point type.

gA 1-point rule shall be placed 1 1/2 inches above the bottom of the page

hThe TPI change no. and date shall be placed in the lower right cornerThe TPI change no. and date shall be placed in the lower right corner, above the 1-point rule, in 10- to 12-point type.

5.1.2TPI numerical index of work packages(see figure 6.) The TPI numerical index of Work Packages shall contain a hyperlinked index of WPs for the TPI. The index page shall immediately follow the title page and normally begin on page 2 of the TPI and include the following:

aThe TPI publication number shall be placed in the upper left cornerThe TPI publication number shall be placed in the upper left corner of the page, in 14- to 16-point bold type.

bThe page identification shall be placed in the upper right cornerThe page identification (normally, Page 2) shall be placed in the upper right corner of the page on the same line as the publication number, in 16 pt. bold type.

cThe title "TEST PROGRAM INSTRUCTION" shall be enteredThe title "TEST PROGRAM INSTRUCTION" shall be entered in 14- to 16-point bold type.

dThe title "NUMERICAL INDEX OF WORK PACKAGES" shall be centeredThe title "NUMERICAL INDEX OF WORK PACKAGES" shall be centered, in 12- to 14-point type.

eCentered below the title shall be the words "WORK PACKAGE INDEX"Centered below the title shall be the words "WORK PACKAGE INDEX" with column heads "WP NO., "TITLE," and "CHANGE NO." below. A 1-point rule shall be placed above and below the column headings.

fA numerical listing of WPs assigned to the manualA numerical listing of WPs assigned to the manual and their titles shall be placed below the applicable column heads.

gThe TPI change date shall be placed below the titleThe TPI change date shall be placed below the title in 10- to 12-point type.

5.1.3Revisions/changes(see figure 7.) A list of revisions/changes incorporated shall be specified for all manuals. This page shall begin with the original issue of the OTPI/TPI coinciding with the delivery of the OTPS and subsequently maintained by the cognizant activity to list all subsequent revisions and changes. The WP REVCHG page shall follow the WP index page and include the following:

aThe TPI publication number shall be placed in the upper left cornerThe TPI publication number shall be placed in the upper left corner of the page, in 14- to 16-point bold type.

bThe TPI date or revision date shall be in the upper left cornerThe TPI date or revision date shall be in the upper left corner below the publication number in 10- to 12-point type.

cThe page identification shall be placed in the upper right cornerThe page identification (Page 3, Page 4, etc.) shall be placed in the upper right corner, on the same line and in the same font as the publication number right justified.

dThe title "TEST PROGRAM INSTRUCTION RECORD OF REVISIONS/CHANGES" shall be centeredThe title "TEST PROGRAM INSTRUCTION RECORD OF REVISIONS/CHANGES" shall be centered on the page below the publication number, in 12- to 14-point type.

eThe page shall be in column formatThe page shall be in column format with column heads "REVCHG NO.," "DATE," "REASON FOR CHANGE," and "TPI/WP AFFECTED (PARA., TABLE, FIGURE, etc.)," in 12-point type. A 1-point rule shall be placed above and below the column heads.

fA list of current changes assigned to the manualA list of current changes assigned to the manual shall be placed below the applicable column heads.

5.2Technical-content work packageAll WPs numbered WP 001 00 and above shall be considered technical content WPs.

5.2.1Technical content package title page(see figure 8.) The title page shall include the following:

aThe OTPI or TPI publication number shall be placedThe OTPI or TPI (as applicable) publication number shall be placed in the upper left corner of the page in 14- to 16-point bold type.

bThe work package number shall be placed in the upper right hand cornerThe work package number shall be placed in the upper right hand corner on the same line as the publication number, in 14- to 16-point bold type.

cThe WP change number and date shall be placed below the publication numberThe WP change number and date shall be placed below the publication number in 12 pt. type. The page number and number of pages shall be placed below the WP number in 12 to 14 point type.

dA 1-point rule shall be placed 1 1/2 inches from the topA 1-point rule shall be placed 1 1/2 inches from the top of the page below the TPI number.

eThe words "OPERATIONAL TEST PROGRAM INSTRUCTION" or "TEST PROGRAM INSTRUCTION"The words "OPERATIONAL TEST PROGRAM INSTRUCTION" or "TEST PROGRAM INSTRUCTION", as applicable, followed by the technical contents (i.e. title) of the WP shall be centered on the page in 12 to 14 point. bold type.

fThe words "FOR TESTING" shall be centered below the contents titleFor TPI WPs, the following apply: The words "FOR TESTING" in 12, to 14-point type shall be centered below the contents title with the UUT nomenclature an number centered below, both in 14- to 16-point bold type.

gA 1-point rule shall be placed below the technical contents title

5.2.1.1TPI WP 001 00 Supplemental Testing DataWork Package 001 00 will convey to the TPS operator any required data to successfully run the UUT or self-test TPS that is not available in any other TPS documentation including TPS output messages, MTPSI, and Technical Manuals for the UUT and/or Operational Test Program Hardware (OTPH). If included, WP 001 00 shall contain:

aFormat WP data per 5.2.1 above

bWP 001 00 may include the following paragraphsWP 001 00 may include the following paragraphs, or any others deemed applicable within the constraints of this WP. 1. UNTESTED HARDWARE 2. SELECT AT TEST PROCEDURE 3. OTHER MESSAGES (Any other messages too wordy or complex to be put in the TPS program) If no supplemental testing data is required, the TPI will contain a WP 001 00. The first page of the formatted WP shall state "This Work Package Intentionally Omitted"

5.2.1.2TPI WP 002 00 Test Diagnostic Information (TDI)The TDI consists of two parts. Part 1 is a Test Oriented Wire List (TOWL) of active wire segments used during a particular test. Part 2 is a System Wiring Diagram (SWD) of the entire OTPH. WP 002 00 will contain a description of the use of the TOWL in conjunction with the SWD and links to TPI WP 002 01 TOWL and OTPI WP 002 02 SWD. NOTE: TOWL and SWD samples can be found at both web sites listed below: https://pma260.navair.navy.mil or http://www.acq.osd.mil.

5.2.1.3TPI WP 002 01 Test Oriented Wire ListThe TOWL is a list of the point-to-point connections of wire segments within the OTPH. Each wire segment is prefaced with an abbreviation to indicate its whereabouts within the ATE, the OTPH or the UUT (e.g. GPI:P9-11B to ID:TB0610-F indicates the wire of interest has one end at the GPI panel and the other inside the OTPH on TB0610). For complex OTPH that has an interface device that contains terminal blocks, as well as a test fixture with terminal blocks then TF:TB0610-F would indicate that the terminal block is in the test fixture, not the interface device. The first page of WP 002 01 will contain an index for all test numbers with links to the TOWL point-to-point wire segment connections for each test. The TOWL shall be prepared in a tabular format with five column headings as follows ASSET Identifies the asset (ATE, GPETE, ancillary, etc.) providing the measurement/stimulus FROM Identifies the connector/pin reference for the signal path segment TO Identifies the ending connector/pin reference for the signal path segment FROM SHEET Identifies the SWD sheet where the connector reference can be located TO SHEET Identifies the SWD sheet where the "to" connector reference can be located Bold green text shall be used to identify previously unchecked paths. Regular green text shall identify checked paths. An asterisk "*" shall be placed next to the wire path in the TOWL to indicate a daisy chained path. The "FROM" and "TO" path shall be linked to allow direct opening of the corresponding schematic PDF that is part of the System Wiring Diagram. Wire paths in the TOWL that have not been checked by a previous test shall be identified by bold red text. Wire paths in the TOWL that have been checked by previous tests shall be identified by regular underlined blue text. An exclamation point "!" shall be placed next to the wire path in the TOWL to indicate a path that is not directly used by this test but is connected to the test path. The listing shall follow an orderly flow that matches the flow of the SWD. A wire segment in the SWD may begin on one sheet and end on another. The TOWL shall include sheet numbers for both the "from" and "to" pins. When a listed pin is part of ATE, the asset name (from CASS .RTT, for instance) is included on that line. When a listed pin is part of the UUT, then "UUT" is added to that line. The Source Code header commentary for each test shall be included as part of the TOWL to provide the operator insight into the test functionality. See figure 10 for a presentation example.

5.2.1.4OTPI WP 002 02 System Wiring Diagram (SWD)SWD shall be prepared in accordance with ASME Y14.24-1999, paragraph 10.3. Symbolic representation of all OTPH electrical components shall be in accordance with ASME Y14.24-1999, Paragraph 10.3.3. A wire list shall NOT be substituted for any portion of the SWD. The SWD shall provide an explicit illustration between the ATE, OTPH and UUT. The SWD shall be developed to print on 11" X 17" paper size (B size drawings). All font sizes shall be a minimum of 8 point. When more than one sheet is required to describe a SWD, the SWD shall be clearly identified with appropriate notation on all associated SWD sheets as to the total number of sheets (i.e. sheet 1 of 38). The SWD shall show all hardware elements of the OTPH containing circuitry/wiring (i.e. Splice Points, Terminal Blocks, mother boards, CCA schematic etc.) including all repairable and non-repairable assemblies etc. as well as the ATE (CASS) assets used (i.e. instruments, station relays). The following information is provided to ensure standardization:

aThe front page of the SWD shall have all terms and definitionsThe front page of the SWD shall have all terms and definitions used in the SWD identified.

bFor OTPH designed for use on CASS ATEFor OTPH designed for use on CASS ATE: CASS assets are identified with the GPI: label. Instruments are further identified with their RTT labels.

cAll ATE asset blocks are drawn with bold linesAll ATE asset blocks are drawn with bold lines to differentiate the OTPH hardware from the ATE hardware.

dThe SWD shall include all ATE assets used by the TPSThe SWD shall include all ATE assets used by the TPS including RF, EO and ancillary assets such as the ADTS, MPSRD, VPG, ULAS, BTI, EO Cart, etc.

eAll labels used in the SWD and TOWL shall matchAll labels used in the SWD and TOWL shall match. Examples of labeling are: GPI:P9, ID:TB3_11, and MB:J10.

fRelays shall show all NO/NC designationsRelays shall show all NO/NC designations. ATE relay identification numbers are not required.

gUnused pins that are identified on the SWDUnused pins that are identified on the SWD shall be annotated with NC (no connection). Alternatively, unused pins may have an "X" placed at the open termination.

hWire connections such as splice pointsWire connections such as splice points shall be identified with a standard tie point or "dot".

iThe SWD portion of the TDI is a point-to-point representationThe SWD portion of the TDI is a point-to-point representation of the OTPH as built. That is, wire segments are clearly delineated. Refer to Example 1. In View 1, pins A and D each hold one wire, while pins B and C each hold two. In View 2, pins A and B each hold one wire, while pins C and D each hold two. In View 3, pins A, B, C and D each hold one wire and all of the other ends are terminated in a splice. All three views are electrically identical, but quite different for the technician trying to trace wires through an OTPH. The point of the SWD is to provide an accurate tracing of wire segments through an OTPH.

jSplice points shall be referred to as SPSplice points shall be referred to as "SP".

5.2.1.5TPI WP 003 00 Source Code Test Information and IndexConsists of formatted WP data 5.2.1 above and the following two paragraphs:

aParagraph 1, SOURCE CODE TEST INFORMATIONParagraph 1, SOURCE CODE TEST INFORMATION, is a description of the content of each sub-WP.

bParagraph 1.1, SOURCE CODE TEST INDEXParagraph 1.1, SOURCE CODE TEST INDEX, is hyperlinked listing of the sub-WP numbers and titles. The index shall list and provide links and/or hyperlinks to all applicable Source Code modules including OTPI WPs 003 02 and/or 003 04, if applicable.

5.2.1.6TPI WP 003 01 Test Program Source ListingConsists of formatted WP data per 5.2.1 above, immediately followed by a hyperlinked list of Source Code filenames (*.LU, *.AS and any others as appropriate) and Source Code test numbers. Each filename hyperlink shall connect to the beginning of the referenced file listing. Each test number hyperlink shall connect to the program source code for that test number.

5.2.1.7OTPI WP 003 02 Common Source ListingSource code that is common to multiple TPSs within the OTPS shall be provided in OTPI WP 003 02, see 4.5 above.

5.2.1.8TPI WP 003 03 Digital Program Source ListingIf applicable, consists of formatted WP data per 5.2.1 immediately followed by a hyperlinked list of TPS-specific digital filenames (*.PMP, *.SYM and any others as appropriate) and procedure names. Each filename hyperlink shall connect to the beginning of the referenced file listing. Each procedure name hyperlink shall link to the particular Digital Source routine.

5.2.1.9OTPI WP 003 04 Common Digital Source ListingDigital Source code that is common to multiple TPSs within the OTPS shall be provided in OTPI WP 003 04, see 4.6 above.

5.2.1.10TPI WP 003 05+ Additional TPS Source ListingsAdditional TPS source module listings, if required.