45N_CDRL_A009.doc

CONTRACT DATA REQUIREMENTS LIST

FORM APPROVED

OMB No.0704-0188

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instruction, searching existing data sources, gathering and maintaining the data needed and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to, Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contract Office for the Contract/PR No. listed in Block E.

1. DATA ITEM NO.

A009

2. TITLE OF DATA ITEM

System Technical Manual

3. SUBTITLE

Test Site Support Documentation

4. AUTHORITY (DATA ACQUISITION DOCUMENT NO.)

DI-TMSS-81677B (See BLK 16)

5. CONTRACT REFERENCE

SOW Para 3.3.2

6. REQUIRING OFFICE

AD4.5.14

7. DD 250 REQ

LT

9. DIST STATEMENT REQUIRED

10. FREQUENCY

ONE/R

12 DATE OF FIRST

See BLK 16

14. DISTRIBUTION

b. COPIES

8. APP CODE

A

13. DATE OF SUBSEQUENT See BLK 16

Reg Repro

16. REMARKS

BLOCK 4: Contractor format acceptable. The contractor shall refer to MIL-DTL-

24784 (Technical Content Development Requirements for Combat System

Technical Operations Manuals (CSTOMS); Hull, Mechanical, and Electrical (HM&E)

System and Equipment Manuals; Electronic [Including Service Test Electronic, Experimental Electronic and Interior Communication (IC)] System and Equipment

Manuals; and Weapon Systems and Weapon Equipment Manuals) for guidance.

BLOCK 8 and 13: The Government has 45 working days for review and acceptance or rejection. Contractor has 30 days for re-submittal if accepted with comments or rejected.

BLOCK 9: DISTRIBUTION STATEMENT D, Department of Defense and U.S. DoD contractors only (Critical Technology) (Date). Other requests shall be referred to (Cognizant Program Office assigned at time of award).

BLOCK 12: Report to be submitted NLT 45 days after completing studies, research, development, test and evaluation.

BLOCK 14: One (1) soft copy (Reg). Soft copy shall be delivered in the original and modifiable application (e.g., Microsoft Office, AutoCAD, etc.) to:

Building 2185 1130 - B2

22347 Cedar Point Road

Patuxent River, MD 20670

DESTRUCTION NOTICE: Follow the procedures in DoD 5220.22-M, NISPOM, Section 5-705.

4.5.14 (See Block 16)

15.TOTAL

G. PREPARED BY

H. DATE

18 September 2018

I. APPROVED BY

J. DATE

DD FORM 1423, JUN 90 Previous editions are obsolete Page of Pages

Double click to view full contents of this DID.

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

_1598780945.pdf

Comments, suggestions, or questions on this document should be addressed to: Commander, Naval Sea Systems Command, ATTN: SEA 05M3, 1333 Isaac Hull Avenue, SE, Stop 5160, Washington Navy Yard DC 20376-5160 or emailed to CommandStandards@navy.mil, with the subject line “Document Comment”. Since contact information can change, you may want to verify the currency of this address information using the ASSIST Online database at http://assist.daps.dla.mil.

AMSC N/A AREA TMSS

INCH-POUND

MIL-DTL-24784/22(NAVY)

3 November 2007

SUPERSEDING

(See 6.3)

DETAIL SPECIFICATION SHEET

TECHNICAL CONTENT DEVELOPMENT REQUIREMENTS FOR

COMBAT SYSTEM TECHNICAL OPERATIONS MANUALS (CSTOMS);

HULL, MECHANICAL, AND ELECTRICAL (HM&E) SYSTEM AND EQUIPMENT MANUALS;

ELECTRONIC [INCLUDING SERVICE TEST ELECTRONIC, EXPERIMENTAL ELECTRONIC AND

INTERIOR COMMUNICATION (IC)] SYSTEM AND EQUIPMENT MANUALS; AND

WEAPON SYSTEMS AND WEAPON EQUIPMENT MANUALS

This specification is approved for use by the Department of the Navy, and is available for use by all Departments and Agencies of the Department of Defense.

The requirements for acquiring the product specified herein shall consist of this specification sheet and

MIL-DTL-24784.

1. SCOPE

1.1 Scope. This specification sets forth content requirements for the preparation of technical manuals (TMs) covering description, operation, maintenance, installation, and parts support for Combat System Technical Operations Manuals (CSTOMs); Hull, Mechanical, and Electrical (HM&E) Systems and Equipment Manuals;

Electronic [including Service Test Electronic, Experimental Electronic, and Interior Communications (IC)] System and Equipment Manuals; and Weapon Systems and Weapon Equipment Manuals. The requirements are applicable for the output of paper or for the display of page-oriented, linear, and non-linear TMs on an Electronic Display System (EDS).

2. APPLICABLE DOCUMENTS

2.1 General. The documents listed in this section are specified in sections 3, 4, or 5 of this specification. This section does not include documents cited in other sections of this specification or recommended for additional information or as examples. While every effort has been made to ensure the completeness of this list, document users are cautioned that they must meet all specified requirements of documents cited in sections 3, 4, or 5 of this specification, whether or not they are listed.

2.2 Government documents.

2.2.1 Specifications, standards, and handbooks. The following specifications, standards, and handbooks form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

Source: https://assist.dla.mil -- Downloaded: 2018-09-18T16:57Z Check the source to verify that this is the current version before use.

DEPARTMENT OF DEFENSE SPECIFICATIONS

MIL-DTL-24784 - Manuals, Technical: General Acquisition and Development Requirements, General Specification for

(Copies of this document are available online at http://assist.daps.dla.mil/quicksearch/ or http://assist.daps.dla.mil or from the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia, PA 19111-5094.)

2.2.2 Other Government documents, drawings, and publications. The following other Government documents, drawings, and publications form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

DEPARTMENT OF THE NAVY DOCUMENTS

OPNAVINST 4790.4 - Ships’ Maintenance Material Management (3-M) System Policy

(Copies of this document are available from the Department of the Navy Issuances, SECNAV/OPNAV Directives Control Office (DNS-5), Bldg. 36, 720 Kennon Street, SE, Rm 203, Washington Navy Yard, DC 20374- 5074 or online at http://doni.daps.dla.mil/default.aspx.)

NAVAL SEA SYSTEMS COMMAND (NAVSEA) PUBLICATIONS

NAVSEA OP 1700 - Standard Fire Control Symbols

N0002400003 - Navy Installation and Maintenance Book

NAVSEA ST000-AB-GYD-010 - Portable Electrical/Electronic Test Equipment (PEETE); Stowage Guide

(Copies of these documents are available from the Naval Logistics Library, 5450 Carlisle Pike, Mechanicsburg, PA 17055 or online at https://nll1.ahf.nmci.navy.mil.)

NAVAL WARFARE DEVELOPMENT COMMAND (NWDC)

Fleet Exercise Publication FXP2 - Air and AAW Exercises

Fleet Exercise Publication FXP3 - Ship Exercises

(Copies of these documents are available by emailing fleetpubs@nwdc.navy.mil or calling (401)841-1856.)

NAVAL SURFACE WARFARE CENTER (NSWC) CORONA DIVISION

NAVSEA Test, Measurement, and Diagnostic Equipment (TMDE) Index

(Copies of this document are available from NSWC Corona Division, Detachment Seal Beach, Strategic Systems Evaluation Division (MS50), Test Systems Support Branch MS532, Bldg 112, 800 Seal Beach Blvd., Seal Beach, CA 90740-5000; by calling (562)626-7959 or (DSN)873-7959; or by FAX (562)626-7831; or contact the Navy Distance Support Anchordesk at Help@AnchorDesk.Navy.Mil; by calling 1-877-418-6824; or at http://www.anchordesk.navy.mil.)

2.3 Non-Government publications. The following documents form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those cited in the solicitation or contract.

INSTITUTE OF ELECTRICAL AND ELECTRONIC ENGINEERS, INC. (IEEE)

IEEE 991 - Standard for Logic Circuit Diagrams (DoD adopted)

(Copies of this document are available from the Institute of Electrical and Electronics Engineers, Inc., 445 Hoes Lane, PO Box 1331, Piscataway, NJ 08855-1331 or online at www.ieee.org.)

http://assist.daps.dla.mil/quicksearch/ http://assist.daps.dla.mil/ http://doni.daps.dla.mil/default.aspx https://nll1.ahf.nmci.navy.mil/ mailto:fleetpubs@nwdc.navy.mil mailto:Help@AnchorDesk.Navy.Mil http://www.anchordesk.navy.mil/ http://www.ieee.org/

2.4 Order of precedence. In the event of a conflict between the text of this document and the references cited herein, (except for related specification sheets), the text of this document takes precedence. Nothing in this specification, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

3. REQUIREMENTS

3.1 Development. This specification provides the technical content data requirements necessary for the development of NAVSEA TMs described in 1.1 (see 6.2). This specification contains some technical content requirements that may not be applicable to all of the TMs described in 1.1. Selective application and tailoring of requirements shall be accomplished as necessary. The applicability of some requirements is also designated by one of the following statements: unless otherwise specified by the acquiring activity; or as/when specified by the acquiring activity.

3.2 Development products. Development of TM products shall be in accordance with MIL-DTL-24784 (see 6.2).

3.3 Security classification, distribution statement, and destruction notice. Security classification, distribution statement, and destruction notice shall be in accordance with MIL-DTL-24784.

3.4 Format and development instructions. The requirements for front matter, style and format, safety, tabular material, and graphics shall be in accordance with MIL-DTL-24784.

3.5 Maintenance coverage. Unless otherwise specified by the acquiring activity, each type of TM shall contain, in detail, the maintenance coverage prescribed for the applicable maintenance level(s) based on the maintenance concept or approved maintenance plan (see 6.2).

3.6 Technical content requirements. Technical content is organized into “containers” called information modules (IMs) that are grouped according to the type of information being documented. IMs consist of one or more individual information packages (IPs) that contain the actual technical content for the associated IM.

3.6.1 Information modules (IMs). IMs identify specific categories of technical content requirements grouped as follows:

a. Descriptive information (see 3.7) consists of the following IMs:

(1) General IM (see 3.7.1).

(2) Supporting IM (see 3.7.2).

(3) Descriptive IM (see 3.7.3).

(4) Functional description IMs (consisting of HM&E systems functional description IM, HM&E equipment functional description IM, weapon system functional description IM, weapon equipment functional description IM, electronic systems functional description IM and electronic equipment functional description IM) (see 3.7.4).

b. Procedural information (see 3.8) consists of the following IMs:

(1) Operation IM (see 3.8.1).

(2) Maintenance IM (see 3.8.2).

(3) System/equipment installation IM (see 3.8.3).

(4) Operational checkout and troubleshooting IM (see 3.8.4).

c. Illustrated parts breakdown (IPB) IM (see 3.9).

d. CSTOM information (see 3.10) consists of the following IMs:

(1) Combat system introduction and description IM (see 3.10.1).

(2) Combat system description IM (see 3.10.2).

(3) Combat system operational description IM (see 3.10.3).

(4) Combat system readiness assessment IM (see 3.10.4).

(5) Fault detection and impact evaluation IM (see 3.10.5).

(6) Fault isolation IM (see 3.10.6).

3.6.2 Information packages (IPs). IMs consist of one or more individual IPs. The IP contains the actual technical content for the associated IM.

3.6.2.1 IP general content requirements. As applicable, each IP developed shall begin with all reference publications, special tools and test equipment, materials, and field and factory changes that apply to the technical content being developed (see 3.7.2.2 through 3.7.2.7). The following additional information about the contents of the IP shall be included as applicable:

a. Maintenance level.

b. Effectivity.

c. Personnel required.

d. Required conditions.

e. Special environmental conditions.

f. General safety instruction.

3.7 Descriptive information. Descriptive information consists of the following IMs, each of which consists of one or more IPs.

a. General IM (see 3.7.1).

b. Supporting IM (see 3.7.2).

c. Descriptive IM (see 3.7.3).

d. Functional description IM (see 3.7.4).

3.7.1 General IM <GeneralIM>. As applicable, the general IM shall contain the following IPs:

a. General Introduction IP (see 3.7.1.1).

b. Model differences IP (see 3.7.1.2).

The information developed shall be so that command level, supervisory personnel, and other users having a general interest in the equipment can easily and rapidly determine the purpose, physical and functional characteristics, interface requirements, and the operational capabilities of the system/equipment.

3.7.1.1 General Introduction IP <GeneralIntroIP>. An introduction shall be developed for all TMs. The primary purpose of the introduction is to provide information necessary to use the data provided in the TM and respective IPs as effectively as possible. The introduction IP shall include the following information:

a. Purpose and scope. The purpose and scope of the manual, including the subject matter being covered and any superseding data, if applicable.

b. Description and designated nomenclature. The designated nomenclature and a brief description of the end item. The introduction may include an illustration (frontispiece) (see 3.7.8.2.1 of MIL-DTL-24784) of the equipment. Applicability (including ship and shore) of the TM, including capabilities, subsystem or equipment mission, subsystem or equipment interface description, models, serial numbers, and configuration covered shall also be included. As applicable, a consolidated list of the ship hull numbers (by ship class, if applicable), model numbers, serial numbers and part numbers, covered by the TM shall be included and identified as the configuration identification list <ConfigurationIDList>.

c. Effectivities. If applicable, an explanation of the effectivities used throughout the TM.

d. Multi-volume TMs. The first volume of a multi-volume TM shall contain general information and reporting requirements regarding all volumes and specific information applicable to Volume 1, as required.

e. Technical manual deficiency/evaluation report (TMDER). The following submittal and routing instructions for TM improvement reports shall be included:

“Ships, training activities, supply points, depots, Naval Shipyards and Supervisors of Shipbuilding are requested to arrange for the maximum practical use and evaluation of NAVSEA technical manuals (TMs). All errors, omissions, discrepancies, and suggestions for improvement to NAVSEA TMs shall be submitted as a Technical Manual Deficiency/Evaluation Report (TMDER). All feedback comments shall be thoroughly investigated and originators will be advised of action resulting there from.

(Use this statement for printed hard copy TMs) Three copies of the NAVSEA/SPAWAR Technical Manual Deficiency/Evaluation Report form, NAVSEA

4160/1 are included at the end of each separately bound hardcopy TM.

(Use this statement for a TM on CD-ROM) The NAVSEA/SPAWAR Technical Manual Deficiency/Evaluation Report form, NAVSEA 4160/1 is included as the last page of the TM.

(Include this statement for all TMs) Copies of form NAVSEA 4160/1 may also be downloaded from:

https://nsdsa2.phdnswc.navy.mil/tmmp/forms/TMDER_BLANK_REV_7-2003.doc.

The following methods are available for generation and submission of TMDERs:

• The most expedient and preferred method of TMDER generation and submission is via the Technical Data Management Information System (TDMIS) website at: https://mercury.tdmis.navy.mil. TDMIS accounts can be requested at https://nsdsa2.phdnswc.navy.mil/.

• Generate and submit TMDER via the Naval Systems Data Support Activity (NSDSA) website at:

https://nsdsa2.phdnswc.navy.mil/tmder/tmder-generate.asp?lvl=1.

• When internet access is not available, submit TMDER via hardcopy to:

COMMANDER

CODE 310 TMDERs

NAVSURFWARCENDIV NSDSA

4363 MISSILE WAY, BLDG 1388

PORT HUENEME, CA 93043-4307

• TMDERs against classified TMs must be submitted using the hardcopy method cited above.

• Urgent priority TM deficiencies shall be reported by Naval message with transmission to Port Hueneme

Division, Naval Surface Warfare Center (Code 310), Port Hueneme, CA. Local message handling procedures shall be used. The message shall identify each TM deficiency by TM identification number and title. This method shall be used in those instances where a TM deficiency constitutes an urgent problem, (i.e., involves a condition, which if not corrected, could result in injury to personnel, damage to the equipment or, jeopardy to the safety or success of the mission).

Complete instructions for TMDER generation and submission are detailed on the NSDSA website at:

https://nsdsa2.phdnswc.navy.mil/tmder/tmder.asp?lvl=1.”

f. Distance support information. Provide current information on contacting Navy Distance Support (Anchor Desk) via the web (http://www.anchordesk.navy.mil/) and via the toll free number (1-877-4-1-TOUCH [86824]).

g. Warranty information. As applicable, warranty and guarantee information shall be included as stated in the contract and shall be in accordance with the Federal Acquisition Regulations (FAR), including hardware modifications (such as ship alterations, engineering change proposals, machinery alterations, ordnance alterations, field changes, and so forth) (see 6.2).

h. Other specific introductory information. Additional introductory information related to a specific type of TM shall be included, such as the interface relationship of the TM to other referenced publications and the relationship of the equipment to referenced systems or other equipment.

https://nsdsa2.phdnswc.navy.mil/tmmp/forms/TMDER_BLANK_REV_7-2003.doc https://mercury.tdmis.navy.mil/ https://nsdsa2.phdnswc.navy.mil/ https://nsdsa2.phdnswc.navy.mil/tmder/tmder-generate.asp?lvl=1 https://nsdsa2.phdnswc.navy.mil/tmder/tmder.asp?lvl=1 http://www.anchordesk.navy.mil/

3.7.1.2 Model differences IP <ModelDiffIP>. When applicable, the differences between models of the equipment shall be briefly delineated in this IP. Descriptions of major physical differences shall be supported by reference to appropriate illustrations. These major differences shall also be reflected in the operating instructions, maintenance instructions, and parts list. Multiple model differences that involve a number of equipment sections or subsections shall be presented in tabular form. The method for handling differences between models in other portions of the TM shall be defined here.

3.7.2 Supporting IM <SupportingIM>. The supporting IM shall contain the following IPs, as applicable:

a. Safety precaution IP (see 3.7.2.1).

b. Reference publications IP (see 3.7.2.2).

c. Special tools and test equipment IP (see 3.7.2.3).

d. Materials required IP (see 3.7.2.4).

e. Equipment modification IP (see 3.7.2.5).

f. Equipment, accessories, and documents supplied IP (see 3.7.2.6).

g. Equipment, accessories, and documents not supplied IP (see 3.7.2.7).

3.7.2.1 Safety precaution IP <SafetyPrecautionIP>. All TMs containing dangers, warnings, or cautions shall have a safety precaution IP. See 3.7.5 of MIL-DTL-24784 for safety and health requirements. General safety precautions and the complete warnings applicable to hazardous materials and related information shall be contained in the safety precaution IP in accordance with 3.7.5.10 of MIL-DTL-24784. Hazardous material warnings used throughout the TM shall be referenced to the safety precaution IP to provide the user with the applicable hazardous material icons and the complete warning text. This IP shall describe all safety precautions necessary for the protection of personnel and the ship including the hazards associated with system operation and maintenance. This IP shall include the following information, as applicable.

3.7.2.1.1 Introduction <intro>. This description shall orient system supervisory personnel, and shall include the following:

a. Purpose, scope, and organization of the system safety instructions.

b. Basic safety concepts.

c. Basic responsibilities for safety.

3.7.2.1.2 Electromagnetic radiation hazards and precautions <RadiationHazard>. If applicable, describe the radiation hazards to topside personnel and the precautions to be taken. The description shall include discussions of the following:

a. Locations of topside and in-board radiation hazardous areas.

b. Minimum safe distances on the axis of beam radiation.

c. Precautions to be taken when entering areas of radiation hazard (such as the wearing of copper-screen goggles).

d. The effect of radiation on flammable or explosive material such as induction of RF currents in metals, sparking, and the consequent possibility of igniting flammables or detonating explosives. The text shall be supported by one or more illustrations identifying the areas of radiation hazards and the location of antennas, and so forth.

3.7.2.1.3 Hazards to divers <DiverHazard>. When applicable, the description of hazards to divers shall include but shall not necessarily be limited to the following:

a. The nature and intensity of sound energy in water as related to divers.

b. Precautions to be taken when working near operating equipment.

c. Illustrations identifying the hazardous areas and locations of sonar domes.

3.7.2.1.4 System hazards and precautions <SystemHazard>. Descriptions of system hazards and precautions shall be included, addressed to system personnel and referenced to particular system equipment. The descriptions shall be organized to be consistent with the operation of the system. The descriptions shall supplement and extend equipment safety instructions to the system level, by warning of potential hazards that can be caused during operation or maintenance.

3.7.2.1.5 Operational safety summary <OperationalHazard>. A summary shall be included which emphasizes the proper use of equipment controls, describes the hazards to operators, or as applicable, the hazards to persons in areas remote from the operation, and recommend precautions.

3.7.2.1.6 Maintenance safety summary <SafetySummary>. A maintenance safety summary shall emphasize the proper use of controls, describe the hazards to maintenance personnel, potential damage to the equipment, and recommend precautions.

3.7.2.1.7 Hazardous components <HazardComp>. Identify and briefly describe the hazardous components including radioactive devices and elements used with the system and summarize the general handling precautions for such components. The description of a hazardous component shall include brief statements as to the purpose, manner of functioning, nature of built-in safety devices, and nature of the hazardous element; it shall also indicate the relative sensitivity of the component to mechanical shock, vibration, electromagnetic and radioactive radiation, and electrostatic charges.

3.7.2.2 Reference publications IP <RefPubIP>. A list of the manuals that pertain to system and subsystem equipment, and other documents of interest or use to operating or maintenance personnel, such as basic training manuals, special directives, NAVSEA OP 1700, and manuals for associated systems equipment shall be included in this IP. The list of publications shall include the title and publication number of the referenced publications.

3.7.2.3 Special tools and test equipment IP <StteIP>. All special tools, tool kits, test equipment, miscellaneous parts, and Government-furnished items that form a part of, or are supplied (or not supplied) with, the system or equipment shall be included in this IP. Items included in the table (<SpecialToolsList>) shall be listed alphabetically by their official name or nomenclature. Notes explaining the use of the tables and stock code numbering system shall precede the first table for which a particular note is applicable. For each listed item, the table shall include:

a. Item name consisting of the official name or nomenclature of the listed item.

b. If applicable, a description of its general use and a reference to the illustration contained in the IPB.

c. Quantity of the items required for maintenance of the equipment.

d. Manufacturer’s part number consisting of the manufacturer’s or the contracting activity’s assigned part number as it appears on the item.

e. The Commercial and Government Entity (CAGE) code consisting of the assigned CAGE code of the manufacturer or contracting activity of the listed item.

f. The stock code number consisting of an assigned number which indicates the procurement status of the listed item as follows:

(1) Item is supplied with the equipment.

(2) Item is supplied by the manufacturer.

(3) Item is available from the manufacturer.

3.7.2.3.1 Equipment and publications required but not supplied IP (electronic systems and equipment only). A tabular listing of all test equipment and publications required but not supplied with the equipment or system shall be included in this IP. The NAVSEA Test, Measurement, and Diagnostic Equipment (TMDE) Index shall be used as a guide for the selection and application of test equipment required for shipboard use. If a measurement requirement is established which cannot be satisfied by the subcategory (SCAT) codes listed in this guide, or alternate test procedures cannot be developed utilizing the listed SCAT request for assistance should be directed to:

Commander Naval Sea Systems Command

ATTN: SEA 05M3

1333 Isaac Hull Avenue, SE Stop 5160 Washington Navy Yard DC 20376-5160

The listing shall contain:

a. SCAT code. When applicable, this column shall contain the four digit group of numbers, which is included in the NAVSEA TMDE Index, used to identify a measurement requirement.

b. Test equipment category. This column shall contain the item name of each item of equipment required.

c. Representative test equipment model number. This column shall contain the model number of the standard or substitute standard general purpose electronic test equipment, listed in the NAVSEA TMDE Index, as applicable, which can be used to satisfy the measurement parameters.

d. Equipment test parameters. This column shall specify the range of test parameters, which shall be satisfied by this test equipment item (it shall not define the ranges of the test equipment model).

e. Application. This column shall indicate the intended use of the test equipment (for example, troubleshooting, maintenance, or installation).

f. Publication number and title. This column shall specify the publication by number and title.

3.7.2.4 Materials required IP <MatReqIP>. When applicable, this IP shall provide a list of all materials (consumable materials and/or expendable items) required to perform maintenance type procedures. Items shall be listed in alphabetical sequence by noun nomenclature. The materials required list (<MaterialsList>) shall be prepared in accordance with the following guidelines:

a. Each material entry in the list shall be identified by “Nomenclature <Nomenclature>,” and “Specification <SpecNumber>, Part Number <PartNumber>, or Not Specified <NotSpecified>” as applicable. If the materials are authorized for use at only certain maintenance level(s), the restriction shall be indicated by the use of an O, I, and/or D.

b. Unless alternate identification is approved by the acquiring activity, materials shall be listed by Government specification in parentheses following the item nomenclature.

c. When more than one of the same item is required, the quantity shall follow the nomenclature in parentheses.

d. Parts that require mandatory replacement in the procedure, such as preformed packing, shall be listed.

3.7.2.5 Equipment modification IP <EquipModIP>. An IP shall be developed to include all equipment modification change data (<EquipModTable>) for the system/equipment covered by the TM. Field changes, factory changes, engineering changes or notices, modifications, and so forth (<FieldFactoryChangeList>) shall be identified and included as follows:

a. Change number <ChangeNumber>. This column shall list the change number for each field and factory change considered and included in the preparation of the TM.

b. Nomenclature <Nomenclature>. This column shall list the equipment nomenclature and Government serial numbers of equipment affected by the change.

c. Description <desc>. This column shall contain a brief statement identifying the change and its purpose.

3.7.2.6 Equipment, accessories and documents supplied IP <EquipDocSuppIP>. As applicable, an IP containing a tabular listing of all equipment, accessories, and other documents supplied (<EquipDocSuppTable>) shall be provided. List the equipment (other than test equipment), its units, and its accessories. The table shall include the following:

a. Quantity <Quantity>. This column shall contain the quantity of each unit and accessories supplied with the equipment.

b. Item name or nomenclature <name>. This column shall contain the official name (for example, pump, winch) or nomenclature (name and designation) of each component, unit or accessory. For documents, list the document title.

c. PIN number <PINNumber>, RIC number <RICNumber>, or unit number <UnitNumber>. This column shall contain the part identification number (PIN) or component identification number (CID), repairable identification code (RIC), or unit number of each equipment unit or accessory. For documents, list the document identification number.

d. Overall dimensions <Dimensions>. This column shall contain the crated (if available) and uncrated height, width, and depth in inches (or inches and centimeters) of each unit, accessory, or document.

e. Weight and volume <WeightVolume>. This column shall contain the crated (if available) and uncrated weight and volume in cubic feet of each unit, accessory, and document.

3.7.2.7 Equipment, accessories, and documents not supplied IP <EquipDocNotSuppIP>. As applicable, an IP shall be provided describing equipment and accessories (such as controls, foundations mounts, couplings, and accessories) and related publications, which are not furnished with the basic equipment covered by the TM, but which attach or relate importantly to the basic equipment. The data shall be in sufficient detail to establish the correlation of the equipment with respect to physical and functional interfaces. If applicable, a reference should be made to the shipbuilder’s power plant technical manual if it contains additional applicable information.

3.7.3 Descriptive IM <DescriptiveIM>. Descriptive IMs shall be developed and be divided into IPs as described in 3.7.3.1 through 3.7.3.4, as applicable.

3.7.3.1 Physical arrangement IP (HM&E systems, weapon systems, and electronic systems and equipment only) <PhysicalArrangeIP>. For systems, all system areas and compartments shall be described and the system equipment and units contained in the areas shall be listed in this IP. The physical arrangement description shall be supported by the following illustrations:

a. An inboard profile drawing of the ship or stations showing compartment locations and identifying topside equipment and equipment units comprising the system (see figure 1).

b. Separate illustrations of each compartment and area, identifying the listed system equipment (see figure 2).

Other equipment, which is installed in the subject system compartments and areas, need not be listed in the text or called out in the illustrations if they do not directly affect the operation or maintenance of the subject system.

3.7.3.2 System description IP <SystemDescriptionIP>. System description IPs shall describe the system and its relationship to associated systems, subsystems, and equipment. For other than weapon systems and subsystems or weapon equipment, the descriptions shall combine the physical and general aspects of the system and associated systems contained therein and their interdependencies and interactions. Each of the equipment comprising the system shall be identified and described. Descriptions of operator-attended equipment shall include general statements as to the nature and purpose of units and indicators. The text shall be supported by illustrations. All equipment shall be shown, whenever possible, in relative-scale proportion. Equipment may be separately illustrated with significant features called out, if such details are necessary for proper support of the text. When required, descriptions and illustrations of associated system equipment shall be limited to the major units thereof. The descriptions of associated system equipment shall be more condensed than those of the subject system equipment;

otherwise, the same requirements are applicable. In the descriptions, emphasis shall be placed on those associated system equipment that constitute operational or functional interfaces with the subject system and shall be included in the illustrations.

a. For weapon systems and subsystems, the general description shall identify each subsystem group of weapon system equipment and each unit equipment in a group by composite illustrations of the subsystem group of the first ship of the class, for example, the fire control subsystem. The text shall only describe significant features of a particular component of an equipment in a group. Significant features would comprise such items as console panels, sub-panels, and control and indicator groups. Each component of an equipment in a group shall be called out as shown in figure 3. Associated systems equipment shall be shown in separate group operational and functional interfaces with the weapon system. Examples of such components include search radar distribution switchboard and radar order switches that control the availability of weapon system planned-position indicator (PPI) displays, and units of the naval tactical data system that control the transmission of target data to and from the weapon system.

b. For weapon equipment, if the equipment operates as part of a system, a system description shall be included. This shall be a non-technical orientation of the subject equipment with other equipment in the system. The system description shall discuss only those components of the system necessary to introduce the subject equipment’s system-contributing capabilities. An illustration shall be used to clarify the relationships. Figure 4 is a typical equipment/system integration illustration.

3.7.3.2.1 Equipment and component description. The IPs shall identify and describe the equipment and components. The description shall include the intended use (why, where, when, how, and with what), capabilities, and limitations of the equipment. Descriptions of operator-attended equipment shall include general statements as to the nature and purpose of units and indicators. The text shall be supported by illustrations. Text covering physical description or structural arrangement shall be brief, with special attention given to avoiding unnecessary or repetitious details that are easily illustrated. All equipment shall be shown, whenever possible, in relative-scale proportion. Equipment may be separately illustrated with significant features called out, if such details are necessary for proper support of the text. Assembly and detail drawings as appropriate may be referenced. If the TM covers more than one equipment configuration, a table defining the differences shall be included.

3.7.3.3 Software description IP <SoftwareDescriptionIP>. This IP shall be developed to provide descriptive information for programming software used for systems, equipment, and test equipment, when applicable. Block diagrams, test setup diagrams, and pictorials of display readouts shall be included when necessary to support the descriptive text.

3.7.3.4 System/equipment characteristics/capabilities IP <SystemCharIP>. When required, an IP shall be prepared containing the leading particulars or technical characteristics (reference data) to present the physical, mechanical and electrical characteristics of the system, subsystem, equipment, or major functional components. The following shall be included:

a. Official nameplate designations and nomenclature of all equipment [manufacturer, type, model, and component identification number (CID)] or, for HM&E equipment a part number, repairable identification code (RIC), and allowance parts list (APL), joint electronics type designation (when applicable) major units, and support equipment. This list shall include common names and quantities required per unit, if available.

b. Detailed operating characteristics, and significant equipment capabilities and limitations such as: pounds of thrust, knots, turning radius, minimum and maximum ranges, degree of coverage, resolution, accuracy, wattages, voltages, horsepower, gallons per minute, input and output signals, load limits, frequency, testable items, resolution, memory capacity, reaction time, transfers per hour, boom capacity, data handling capability, and number of channels.

c. Power input requirements and other externally supplied inputs (such as data and control signals, pressurized air, and coolant water) shall be listed, along with identity of the source of each, such as: ships supply, specific associated equipment, gyrocompass, power requirements, horsepower, pressure, capacity, modes of operation, power output, frequency, pulse characteristics, sensitivity, selectivity, including tolerances, where applicable.

d. Environmental characteristics, such as: ambient temperatures, heat dissipation per unit, humidity limits, coolants (airflow, water or oil flow rate, chilled and demineralized seawater). Measurements provided shall match the installed equipment.

e. In addition, for weapon systems, a description of the system capabilities and how these enable the ship to perform the primary mission. Subsystem and equipment capabilities shall be described only to the extent necessary to describe system capabilities. Capabilities of associated systems shall be described as applicable. Data such as search radar detection ranges, fire control radar acquisition and tracking ranges, number of targets that can be simultaneously evaluated, number of targets that can be simultaneously engaged, and minimum and maximum effective ranges of missiles and guns shall be included. Envelope drawing(s) shall be developed to illustrate system capabilities (see figure 5). Such drawing(s) shall meet the requirements for training documents and shall be technically accurate for use as a guide for system evaluation training exercises.

3.7.4 Functional description IMs. Functional description IMs shall be developed and divided into IPs as described in 3.7.4.1 through 3.7.4.6, as applicable.

3.7.4.1 HM&E systems functional description IM <HMESysFunctionalDescIM>. Functional description for HM&E systems shall describe how the components or equipment comprising the system jointly perform major operations and functions, and how associated systems contribute to the performance of these major functions. The description of the entire system shall be supported by a basic block diagram of the system (see figure 6). Each major function shall then be discussed separately at progressively increasing levels of detail supported with overall and functional block diagrams. Where information can be better presented pictorially than by text, additional diagrams and other illustrations shall be used. Reference may be made to diagrams provided for troubleshooting.

Equipment or associated system interfaces shall be described only as necessary to identify the sources or destinations of system inputs and outputs. Functional description data may be divided into as many IPs as necessary to facilitate usability of the information.

3.7.4.1.1 Introduction IP <IntroductionIP>. This IP shall describe the general approach that is used in the functional description. The introduction shall also describe briefly the interrelationship between the system and associated systems.

3.7.4.1.2 System function directory IP <SysFuncDirIP>. This IP shall include a system function directory tabulating the operation control functions and the signal data described in the detailed level of functional description (see 3.7.4.1.4). The tabulation shall include the following information, as applicable:

a. Official name of the function, common name, and symbol.

b. Type of control or signal (alternating current frequency and voltage, direct current polarity and voltage, hydraulic pressure, mechanical motion, synchro, and so forth).

c. The origin and termination of the control or signal.

d. Identify equipment (relay transmitters, coordinate converters, distribution boxes, switches, and the like) between the origin and termination of the output control or signal.

e. A reference to supporting illustrations.

3.7.4.1.3 Simplified functional description IPs <SimplFuncDescIP>. The IPs shall be developed for system simplified functional descriptions. The simplified functional description shall be confined to data such as origin of the major functions at an equipment control or sensor; transmission of the signal via intermediate equipment such as switchboards, relay transmitters, coordinate converters, and distribution boxes; and presentation of the function at terminal equipment. Control functions essential to the development of a signal shall be introduced and briefly described in their relationship to the signal. The description shall be supported by electronic, electrical, and mechanical system type block diagrams, as applicable (see MIL-DTL-24784 for examples of block diagrams).

Functions involving computations may be explained in mathematical terms, but at a level no higher than high school mathematics; that is, algebra, plane geometry, and trigonometry (through sine, cosine, and tangent).

3.7.4.1.4 Detailed functional description IPs <DetlFuncDescIP>. The IPs shall be developed for system detailed functional descriptions. The detailed-level description shall explain the system major functions in terms directly related to the diagrams provided for troubleshooting. Data and control functions shall be described down to the level of an equipment or an equipment group.

3.7.4.2 HM&E equipment functional description IM <HMEEquipFunctionalDescIM>. Functional description IPs for HM&E equipment describing how the equipment operates shall be provided. Major assemblies of the equipment and interaction on major subassemblies shall be described. Detailed mechanical and electrical functional description, including descriptions of power distribution, power supplies, and regulators, shall be provided. Simplified electrical and electronic schematic diagrams, piping diagrams, mechanical schematic diagrams, as applicable shall support the text. The functional description of digital equipment shall be similar to that for conventional equipment. However, the functional and hardware makeup of digital equipment requires a variation in the method of presentation and descriptive requirements. An overall description of the functional relationship of the logic sections, units, and assemblies comprising the equipment shall be provided. The functional description IPs shall be presented in successive levels of increasing detail as described in 3.7.4.2.2 through 3.7.4.2.4.

3.7.4.2.1 Introduction IP <IntroductionIP>. This IP shall describe the general approach that is used in the functional description. The introduction shall also describe briefly the interrelationship between the equipment and associated components.

3.7.4.2.2 Simplified functional description IP <SimplFuncDescIP>. This IP shall provide narrative text that supports and refers to the overall functional block diagram. All major functions such as transmit, receive, control, display, power distribution, cooling, and so forth shall be described at this level.

3.7.4.2.3 Detailed functional description IP <DetlFuncDescIP>. This IP shall describe the development of each major function at the level of detail shown on its related signal flow diagram, logic diagram, or other diagram provided in troubleshooting. The text shall support and refer directly to the diagrams. The following shall be included, as applicable.

a. An introduction to, and description of, the signal characteristics:

(1) Signal levels or bi-stable states utilized by the equipment; that is, true (1) and false (0), and their relative voltage levels.

(2) Interpretation of the word-code bit structure; that is, address, instruction, or data bit codes.

(3) Signals, identified by their operational accomplishment.

b. Overall and functional block diagrams (FBDs), and associated descriptions.

c. Logic principles shall be described beginning with an introduction to the basic digital logic symbology used in the manual. Each logic function shall be described and supported by Boolean equations, truth tables, simplified logic diagrams, and timing diagrams.

d. Functional description of power distribution, power supplies, and regulators.

3.7.4.2.4 Integrated circuits and micro-miniature capsules IP <IntegratedCircuitIP>. This IP shall provide a brief description of the overall functional operation for circuits within different types of non-repairable integrated circuits and micro-miniature capsules. Non-repairable circuits are not required for functional understandings of theory of operation. Simplified schematics in accordance with SE000-01-IMB-010 or logic diagrams showing input and output connections, truth tables, and waveforms as applicable shall support the text.

3.7.4.3 Weapon systems functional description IM <WeaponSysFunctionalDescIM>. Major weapon system functions shall be identified and described in functional description IPs. The highest threat level shall be considered the primary mode of weapon system operation. Other modes shall be treated as secondary and, insofar as feasible, as modifications of the primary mode. Thus, functions that are common to all modes shall be described under the primary mode and referred to under the secondary mode, with such modifications as may be necessary. Each function shall be analyzed by describing the origin of the function and by stating how each pertinent equipment contributes to the purpose of the overall system function. Functions shall be covered in terms directly related to the system troubleshooting procedures and diagrams. Each functional analysis shall be presented in two levels, simplified and detailed, so that personnel training based on this approach can adequately support the concept.

Descriptions shall be supported by illustrations, which may include block diagrams, geometrical diagrams, and functional block diagrams.

3.7.4.3.1 Introduction IP <IntroductionIP>. This IP shall briefly describe the system interfaces and explain interrelationships between the subject system and associated systems and equipment. The major system functions shall be introduced briefly, and the general approach used in the description and analysis of the major function shall be explained. The introduction shall introduce all major system functions and physical interfaces. Subsequent IPs shall contain a description and analysis of major system functions. The introduction shall inform the reader that each major function is separately analyzed in two levels: simplified and detailed.

3.7.4.3.2 Weapon system interfaces IP <WeaponSysInterIP>. This IP shall include descriptions of weapon system interface relationships to associated systems and equipment and shall be supported by interface functional block diagrams that illustrate system integration (see figure 7).

3.7.4.3.3 Major system functions IPs <SysFuncDescIP>. All major system functions shall be listed and defined and included in individual IPs. Major functions shall reflect the operational phases or events of the primary mode of system operation. Secondary system modes, integration with associated systems, multiple-radar synchronizing systems, evaluation instrumentation systems, and other such miscellaneous but primary subjects, shall be treated separately as related functions. Each major function shall be thoroughly analyzed from generation to output on the basis of concurrent or sequential sub-functions such as data and control functions. The analytic levels in order of increasing complexity are from simplified to detailed. The detailed level shall be an expansion of, and correlate to, concepts introduced at the simplified level. Each level shall be complete within itself. The selected levels of presentation shall be adequate to indoctrinate the reader in weapon system technology.

a. Simplified. The objective of the simplified level shall be to describe the major functions in terms understandable by a person possessing fundamental technical knowledge, and thus provide this person with a basis for better understanding of the detailed analysis. The simplified functional analysis shall explain the generation, transformation, interrelation, and use of the data and control functions that constitute the major function.