1、NON-FIEASUREIIENT sErxrrIvE I I I MIL-STD-l399C(NAVY) 2 February 1988 SIJPERSEDINC: - DOD-ST3-1393B(NAVY) 22 November 1977 (See 6.4) MILITARY STANDARD INTERFACE STANDARD FOR SHIPBOARD SYSTEMS . SCOPE. INTERFACE. AND APPLICABILITY . 1 General . 1 Scope . 1 Basic interface . 1 Tailoring . 1 REFERENCED
2、 DOCUfIENTS . 2 Government docunent . 2 Order of precedence . 2 DEFINITIONS 2 Interface . 2 Environmental interface . 2 Functional interface 2 Characteristics . 2 Constraints . 2 Equipment . 3 GENERAL REQUIREIIENTS . 3 Application . 3 Invoking this standard 3 Consideration of the interface 3 Interfa
3、ce areas not covered . 3 DETAILED REQUIREMENTS 3 Interface sections 3 Interface groupings . 3 Environmental interface group . 3 Support services 3 Controlled design characteristics . 3 Uncontrolled environmental characteristics 4 Operational characteristics . 4 Functional interface group 4 Electroni
4、c information Characteristics 4 Weapons control characteristics . 4 Electrical information characteristics 4 flechanical information characteristics 4 Supporting section scope 4 Relationship to the Expanded Ship Work Breakdown Structure (ESWBS) 6 NOTES 6 Deviations 6 Conditions 6 Procedure . 6 Subje
5、ct term (key word) listing . 6 Changes from previous issue . 7 iv a Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-L377C L7 W 7777711 O030726 3 -. % MIL-STD-l399C(NAVY) 2 February 1988 CONTENTS - Continued Page FICURES Figure 1. Interface .
6、1 process 8 2. Application of MIL-STD-1399 to the ship acquisition TABLES Table I. Shipboard interface section coverages . 5 i i I. v/vi Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-1- MIL-STD-L399C 17 W 7777911 0030727 5 MIL-STD-l399C(NAVY) 2 Feb
7、ruary 1988 1. GENERAL, SCOPE, INTERFACE, AND APPLICABILITY 1.1 General. This standard consists of a general basic document (MIL-STD-1399) and supporting sections. Each section addresses a specific interface area. When an individual interface area is under consideration, the section which addresses t
8、hat particular interface and MIL-STD-1399 shall be viewed as an integral single document. 1.2 Scope. This standard establishes interface requirements or ship- board equipment to ensure compatibility between such equipment and the ship- board environment in which they will be installed. 1.3 Basic int
9、erface. The basic interface, its characteristics and con- straints are shown on figure 1. This symbolical presentation is detailed in each of the supporting sections as it applies. BAS IC INTERFACE m p I SHIPBOARD Id,; SHIP INSTALLATION 1/ I 2/ - SYSTEMS; ENVIRONMENT 4 - e EQUIPMENT U YCHARACTERISTI
10、CS LCONSTRAINTS Engineering features of Equipment design controls the shipboard environnent (See 3.3) (See 3.2) FIGURE 1. Interface. 1.4 Tailoring. The criteria established in individual supporting sections apply to all Naval ships where that particular interface is of concern. Circum- stances may a
11、rise where incorporation of requirements and constraints is con- sidered impractical, or the expected shipboard environment will be less stringent than the postulated “worst case“. In such a situation, it may be desirable to tailor the section requirements to be cost-effective. Such tailoring shall
12、not be done unilaterally. In any such case, the procedures established in section 6 “Deviations“ of this standard shall be followed. 1 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,- MIL-STD-l399C( NAVY) 2 February 1988 2. REFERENCED DOCUMENTS 2.1 G
13、overnment document. The following document, of the issue in effect on date of invitation for bids or request for proposal, forms a part of this standard to the extent specified herein. PUBLICATION MILITARY NAVSEA S9040-AA-IDX-O10/SHBS 5D - Expanded Ship Work Breakdown Structure. (Copies of publicati
14、ons required by contractors in connection with specific acquisition functions should he obtained from the contracting activity or as directed by the contracting officer.) 2.2 Order of precedence. In the event of a conflict between the text of this standard and the reference cited herein, the text of
15、 this standard shall take precedence. 3. DEFINITIONS 3.1 Interface. An interface is a ship system component boundary through which flows functional information, or a physical action occurs, or a relation exists which causes such ships, systems, or system components to be unilaterally dependent or mu
16、tually responsive. 3.1.1 Environnental interface. An environmental interface is a boundary between the environment and a ship system component where the interface rela- tionship is essentially physical and which causes such ship system component to he dependent or responsive to the environment. It i
17、s primarily concerned with the surroundings on board ship in which the installed equipment must function and operate. 3.1.2 Functional interface. A functional interface is a boundary between ship system components through which flows functional information which causes such components to be dependen
18、t or responsive in operation. It is primarily concerned with the effective transmission of information and control signals through the interface boundary. 3.2 Characteristics. Characteristics are those engineering features of the shipboard environnent that are measurable at an interface (see, 5.1).
19、Interface characteristics are firmly established and are not subject to change except by use of the deviation procedure (see 6.2). 3.3 Constraints. Constraints are specified controls or limits placed on the design of equipment to ensure operational compatibility of such equipment with the characteri
20、stics at the shipboard interface. Internal design features of equipment which do not interface with the environment and which are not influenced by that environment are not included. 2 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-1377C 17
21、W 7777711 0030727 7 W MIL-STD-l399C(NAVY) 2 February 1988 3.4 Equipment. Equipnent, for the purpose of this standard, are hardware entities which can encompass an integral system grouping of associated and related units and components, or may only relate to a single “black box“. 4. GENERAL REQUIEGME
22、NTS 4.1 Application. This standard applies to all activities involved in ship and equipment design, production, and installation and requires that interfaces be given priority consideration by such activities. This standard shall be adhered to by SYSCOMs, Project managers, contractors, and all other
23、s engaged in any aspect of ship design including equipment design, production and instal- lation. Figure 2 is a graphical presentation of the various applications of this standard, depending on the nature of the particular interface involved and the circumstances existing at the time. 4.1.1 Invoking
24、 this standard. It is mandatory that Principal Development Activities (PDA) invoke this standard in Development Proposals, Ship Project Directives, Ship Design Manuals, and procurement specifications for equipment destined for shipboard installation. 4.1.2 Consideration of the interface. Interface r
25、equirements shall be carefully considered by all Naval activities and contractors involved in ship construction/modernization/conversion throughout the entire ship life cycle. 4.2 Interface areas not covered. Interested activities, in consonance with the objectives of this standard, shall establish
26、a dialogue in a timely manner which will bring into focus and resolve any interface and deviation problem which may require attention during the early design stage of shipboard equipment (see 6.1). 5. DETAILED REQUIREMENTS 5.1 Interface sections. 5.1.2 Interface groupings. Interfaces covered by this
27、 standard fall into two broad groupings: environmental interfaces and functional interfaces. Within these two groupings, interfaces are broken down into general areas and specific sub-areas which comprise the subject material for the individual supporting sections of this standard. 5.2 Environmental
28、 interface erouD. 5.2.1 Support services. Support services include interface inputs required by equipment to meet specified requirements. Examples are electric service for primary power, compressed gases, water, and waste disposal. 5.2.2 Controlled design characteristics. Controlled design character
29、istics are interfaces that are responsive to or dependent on ship design. Examples are ins3de temperature and humidity, size and weight allowances, space allotments, ventilation, and handling devices. 3 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,
30、-tIIL-STD-l399C(NAVY) 2 February 1988 5.2.3 Uncontrolled environmental characteristics. Uncontrolled environ- mental characteristics are interfaces that are indeDendent of ship design. Examples are wind, icing, weather temperature and hhdity , and sea staie. 5.2.4 Operational characteristics. Operat
31、ional characteristics are interfaces that are generally unpredictable in occurrence or magnitude. Examples are shock, blast, and electromagnetic radiation. 5.3 Functional interface group. 5.3.1 Electronic information characteristics. Electronic information characteristics are monitor and sensing sig
32、nals of a functional nature. Examples are signals associated with search radar, sonar, and communications. 5.3.2 Weapons control characteristics. Weapons control characteristics are monitor, sensing and control signals of a functional nature associated with weapons systems. Examples are signals asso
33、ciated with missile guidance, tracking, and gun orders. 5.3.3 Electrical information characteristics. Electrical information characteristics are electrical monitor, sensing and control signals of a functional nature at direct current and power frequencies. Examples are signals associated with synchr
34、o, servo, and scalar devices. 5.3.4 Mechanical informatfon characteristics. Mechanical information characteristics are mechanical transmissions or signals of a functional nature. Examples are transmissions or signals associated with shaft position or rota- tion, linear linkage, and fluid control or
35、sensing devices. 5.4 Supporting section scope. Individual supporting sections of this standard cover discrete, finite, and manageable interfaces which identify the characteristics and constraints associated with that particular interface. Interface areas of potential interest are identified in table
36、 I. Since coverage of each section is restricted to interface requirements, and the overall policies are not repeated in the individual section, each section and the basic document must be viewed as a single integral document. Internal design features of equipment which are independent of, and not i
37、nfluenced by, external interface characteristics are not included in the sections. Such internal interfaces are properly included in the individual equipment specifications. Where applicable, individual sections may provide for the acquisition of pertinent interface data through the preparation of a
38、 Contract Data Requirements List (DD Form 1423) for use with an acquisition contract or purchase order. 4 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TABLE I. Shipboard interface section coverages. T Functional Support services Compressed gases C
39、ooling water for electronics Dry air for electronics Electric power Fresh water Hydraulics Salt water Steam Waste disposal Etc. Electronic information (signals) Audio CW Digital Interface function parameters Teletype Video Etc. Controlled factors Air conditioning Cables and connectors Heating Mainte
40、nance access Shape Size Ventilation Weapons handling Weight Etc Uncontrolled environment Humidity Icing Ship motion/attitude Temperatur e Wave impact Wind Et c. Weapons control (signals) Acquisition Interface function parameters Missile guidance Tracking Weapon orders Weapon selection Etc. Electrica
41、l information (signals) Alarm Scalar Servo Status indication Synchro Etc. Operational factors Blast Electromagnetic fields Magnetic fields Noise (acoustic) Shock Vibration Etc. Mechanical information (signals) Counters Cut-out cams Limit switches Position indication stops Etc. 5 Provided by IHSNot f
42、or ResaleNo reproduction or networking permitted without license from IHS-,-,- HIL-STD-l399C(NAVY) 2 February 1988 5.5 Relationship to the Expanded Ship Work Breakdown Structure (ES.JBS). The ESCJBS has been promulgated as publication NAVSEA S9040-AA-IDX-OlO/SWBS 5D to provide a common denominator f
43、or the diverse areas of endeavor associated with shipbuilding and establish a single language to span the entire ship life cycle. The ESVBS consists of a structured 5-digit numeric system. Sections of MIL-STD-1399 are identified by the first 3 digits of the ESW3S number corresponding with the primar
44、y element influenced by the interface under consi- deration. In cast? of subject duplication, to distinguish between sections related to the same primary ESWBS element , they will be identified as SECTION XXX-PART 1, 2, etc. Where a section covers several ESlJBS elements such sections will be number
45、ed at the sub group or group level. The application of this numbering system to sections of MIL-STD-1399 will not be applied retroactively, (i.e.) older sections will have their numbers changed to comply with the ES?BS only when they are revised and reissued. 6. NOTES 6.1 Deviations. 6.1.1 Condition
46、s. In achieving the purpose of this standard it is recog- nized that some flexibility of application is required. During the early design stage of shipboard equipment, it may become apparent that significant advantages in the overall design or operation of such equipment can be achieved by deviating
47、 from one or more of the interface requirements. In such instance, a cost-benefit analysis of the proposed deviation shall be performed. When the analysis leads to a conclusion that a more cost-effective ship design will result from adoption of such deviation, the PDA must forward the analysis with
48、a report to the Naval Sea Systems Command (NAVSEA) justifying the deviation. The report must specifi- cally weigh the benefits of adoption of the deviation against the negative effects such as increases in supporting subsystem weight, space, current and life cycle costs, logistics or compromise in r
49、eliability, with conclusions based on system effectiveness. 6.2 Procedure. When requesting a deviation in accordance with 6.1, each section should be considered individually, and such request must be submitted as directed in the section involved. Should contractual actions be involved, the procedural requirements of the applicable contract must be adhered to. 6.3 Subject term (key word) listing. Electronic information chara
