The thrusters control orbital eccentricity of the satellite during its repositioning. The satellite had a mass of 6,kg at launch. AEHF also has substantially increased coverage area, providing connectivity across naval, air and land mission warfare. The AEHF system consists of satellites in space, user terminals and ground-mission control and associated communication network systems.
Mobile and fixed control stations make up the highly survivable mission control segment. It handles the satellites in orbit, monitors satellite health and provides monitoring and planning of operations.
The terminal segment is a network of both fixed and ground mobile, airborne, ship and submarine and other terminals of all the international partners. These three segments enable communications and transfer of data at specified rates ranging from 75bps to about 8Mbps.
It also controls signal processing, time and frequency for extremely high, medium and low data rates of operation. In-orbit processing and reconfigurable networks allow interoperability and dynamic command and control requirements. Antenna beams from the satellite are electronically steerable and mappings can be made from channel to beam to achieve the required transmission capacity.
Satellites can be crosslinked for enabling communications across the globe from different ground gateways. Advantages of the tactical communication system are small and mobile terminals, dynamic routing and low detection probability. Combat Net Radios CNRs are a family of radios that allow voice or data communications for mobile users. These radios provide a half-duplex broadcast transmission media with potentially high BERs.
Integrated Services Digital Network ISDN is an international standard used to support integrated voice and data over standard twisted-pair wire. These interfaces support both circuitand packet-switched services.
It should be noted that deployable systems might additionally be required to support other non-North American ISDN standards when accessing region-specific international infrastructure for ISDN services. The JTA recognizes that this is a critical area affecting interoperability but does not recommend specific solutions in this version.
For BRI physical layer, the following standards are mandated: l. ANSI T1. Asynchronous Transfer Mode ATM is a high-speed switched data transport technology that takes advantage of primarily low BER transmission media to accommodate intelligent multiplexing of voice, data, video, and composite inputs over high-speed trunks and dedicated user links.
The function of the AAL layer is to adapt any traffic video streams, data packets from upper-layer protocols into the ATM format of octet payload. It also receives the cells from the ATM layer and reassembles the protocol data units. The PNNI supports the distribution of topology information between switches and clusters of switches to allow paths to be computed through the network.
For Physical Layer, the following standards are mandated: l. ATM Forum, af-phy ATM Forum, af-uni ATM Forum, af-ilmi ATM Forum, af-vtoa ITU-T I. ATM Forum, af-pnni ATM Forum, af-lane Information for Testing Pixit pro forma are available to demonstrate interoperability between vendor products.
ATM Forum, af-aic ATM Forum, af-sig ATM Forum, af-sec Gigabit Ethernet extends the speed of the Ethernet specification to 1 Gbps. Gigabit Ethernet is used for campus networks and building backbones. Ethernet Mbps service over fiber or Category 5 copper cabling, the following physical layer and framing standard is mandated: l. The major issues that are being resolved include support for legacy cellular systems and mutually agreed upon cellular standards that permit global roaming.
No standards are mandated in this section. Transmission media is used to transmit information from one location to another location. This section addresses the following types of transmission media: military satellite communications, radio communications, and synchronous optical network transmission. The basic elements of satellite communications are a space segment, a control segment, and a terminal segment air, ship, ground, etc.
An implementation of a typical satellite link will require the use of satellite terminals, a user communications extension, and military or commercial satellite resources.
These relatively low frequency bands are used for supporting many long-haul tactical, contingency, and special military operations. This section includes the standards that define the interoperability and performance requirements for user terminals and access controllers that operate over the military UHF SATCOM system. The following standards are mandated:. For 5-kHz or kHz single-channel access service supporting the transmission of either voice or data, the following standard is mandated: l.
For 5-kHz only Demand-Assigned Multiple Access DAMA service, supporting the transmission of data at 75 to bps and messaging and multi-hop, the following standard is mandated: l. For data controllers operating over single-access 5-kHz and kHz UHF SATCOM channels a robust link protocol that can transfer error-free data efficiently and effectively over channels that have high error rates , the following standard is mandated: l.
The new standards will eliminate the functional duplicity of the present standards and will make them easier and less expensive to implement. This section includes the standards that define the interoperability and performance requirements for user terminals and access controllers that will operate over military and commercial SHF SATCOM system.
For the minimum mandatory requirements to ensure interoperability of SATCOM baseband equipment the following standard is mandated: l. MIL-STD contains information concerning SHF multiplexing and de-multiplexing and does not currently address all baseband pertinent information.
The following draft standards are emerging. For waveform, signal processing, and protocol requirements for acquisition, access control, and communications for Medium Data Rate MDR 4. Government efforts to improve satellite operations interoperability among U. Government agencies. The National Security Space Architects Satellite Operations Architecture Team recommended a common set of standards for low data rate satellite telemetry and commanding.
These standards will allow DoD to share health and status resources with other U. Government agencies and with allies to enhance satellite operations while limiting costs. The standards provide a baseline for low data rate communication of health and status information between a spacecraft and the ground. These standards are mandated for S-band communication, but may be applied more generally.
For establishing the physical layer to support satellite health and status communications in the S-band during launch, early orbit, severe anomaly and disposal operations: l. For processing data being sent into distinct, easily distinguishable messages that allow reconstruction of the data with low error probability: l.
For the data unit formats and functions implemented within the coding and physical layers of the satellite health and status communications: l. For procedures and data unit formats implemented within the segmentation and transfer layers of the telecommand data routing service: l. For detailed specification of the logic required to carry out command operation procedure-1 COP-1 of the transfer layer: l.
For the data unit formats and functions implemented within the application, system management, and packetization layers of the satellite command data management service: l.
Packet telemetry provides a mechanism for implementing common data transport structures and protocols to enhance the development and operation of space mission systems. For facilitating the transmission of space-acquired data from source to user in a standardized manner, the following standard is mandated: l. For transmission of telemetry, command, and control and status data over IP-based. The following services are required for the transmission and reception of radio signals.
Tactical data links consist of data elements, standard message formats, protocols for exchanging the messages, and the transmission waveform.
Link 16 provides for exchange of air, space, surface, subsurface, and ground. SONET is a telecommunications transmission standard for use over fiber-optic cable. Network and Systems Management NSM provides the capability to manage designated networks, systems, and information services.
This includes: controlling the networks topology; dynamically segmenting the network into multiple logical domains; maintaining network routing tables; monitoring the network load; and making routing adjustments to optimize throughput. NSM also provides the capability to review and publish addresses of network and system objects; monitor the status of objects; start, restart, reconfigure, or terminate network or system services; and detect loss of network or system objects in order to support automated fault recovery.
A management system has four essential elements: management stations; management agents; management information bases MIBs ; and management protocols, to which these standards apply. Data communications management stations and management agents in end-systems and networked elements shall support the Simple Network Management Protocol SNMP.
The following SNMP-related standard is mandated: l. To standardize the management scope and view of end-systems and networks, the following standards are mandated for MIB modules of the management information base: l. RFCs through Implementations of. Telecommunications management systems for telecommunications switches will implement the Telecommunications Management Network TMN framework to perform the exchange of information within a telecommunications network.
ITU-T M. This section of the Core specifies standards for information modeling activity, data, and object models and information exchange bit-oriented and character-based formatted messages.
This section specifies the minimum information modeling, metadata, and information exchange standards DoD will use to develop or upgrade integrated, interoperable systems. The Information Modeling section applies to activity models, data models, object models and data definitions used to define physical databases.
Information Exchange Standards refer to the exchange of information among mission-area applications within the same system or among different systems.
Information exchange standards include the Tactical Data Links TDLs , bit-oriented and character-based formatted messages. The goal of these formatted messages is to provide a timely, integrated, and coherent picture for joint commanders and their operational forces.
Within the Information System IS domain, there are three basic types of models frequently created: activity, data, and object. Activity Models are representations of mission-area applications, composed of one or more related activities.
The primary product of each activity model is the definition of a measurable set of products, services, and information required to support the mission-area function. Data Models define entities, their data elements, and illustrate the interrelationships among the entities. A data model identifies logical information requirements and metadata, applicable to persistently stored data, which form a basis for physical database schemata and standard data elements within a relational database.
Object Models define the combined information and process requirements within a domain needed to accomplish a particular capability or set of capabilities, for example, as defined by activity models. Such models form the basis of object-oriented system implementations.
They also model system interoperability by combining the metadata for shared data with the allowable interfaces for sharing that data. Object models show associations and dependencies between system interfaces and the essential business rules for exercising those relationships.
System developers use this repository as a primary source of data element standards. Efficient execution of information exchange requirements IERs is key to evolving DoD toward the goal of seamless information exchange. No single data link is applicable to every platform and weapon system. Tactical Digital Information Links TADILs , structured on bit-oriented message standards, evolved to meet critical real-time and near-real-time message requirements.
The United States Message Text Format USMTF , designed primarily for non-real-time exchange, is based on a character-oriented message format and is the standard for human-readable and machine-processable information exchange. This section addresses standards for three basic types of models frequently created: activity, data, and object. Prior to system development or major system update, an activity model is prepared to depict the mission-area function to a level of detail sufficient to identify each entity in the data model that is involved in an activity.
It is validated against the requirements and doctrine, and approved by the operational sponsor. Relational data models are used in software requirements analyses and design activities as a logical basis for physical data exchange and shared data structures that can benefit from a relational schema definition, including message formats and schema for shared databases. Object-oriented systems use data models to design relational data structures when there is a requirement to maintain persistent data storage for that system in a relational database.
IDEF1X is used to produce a graphical information model that represents the. Use of this standard permits the construction of semantic data models, which support the management of data as a resource, the integration of information systems, and the building of relational databases.
System engineering methodology internal to a system is unrestricted. The following standard for data modeling is mandated: l. The key-style is used to produce information models that represent the structure and semantics of data within an enterprise and is backward-compatible with the U.
The identity-style is a wholly new language that provides system designers and developers with a robust set of modeling capabilities covering all static and many dynamic aspects of the emerging object model. This identity-style can, with suitable automation support, be used to develop a model that is an executable prototype of the target object-oriented system. The identity-style can be used in conjunction with emerging dynamic modeling techniques to produce full object-oriented models.
The following data modeling standard is emerging:. Object-oriented modeling techniques are used in the specification and development of object-oriented systems and to model and design the interoperability requirements of distributed components. The UML includes specifications for modeling elements, notation and modeling guidelines. The UML is independent of particular programming languages and development processes.
The UML supports higher-level development concepts such as collaborations, frameworks, patterns, and components, as well as analysis and design. The following object modeling standards are emerging:. Implementation of the DDA will be interpreted to mean that it will serve as the logical reference model database schema defining the names, representations, and generalized relations of data within DoD systems.
System developers comply by using this reference model database schema as a guide to reusable data structures that can form the basis of their own physical database schemas. The shared or sharable data of a new or major system upgrade that are to be persistently stored in a relational or object-relational database will be documented within a data model based on the DDM. New information requirements for shared data are submitted by DoD Components and approved by functional data stewards in accordance with DoD This data will be used to extend the DDA, as appropriate.
The procedures for preparing and submitting data definitions and data models for standardization are covered in DoD System developers shall use this repository as a primary source of data element standards. The following DoD Data Definitions standards are mandated: l. The scope of information exchange standards follows: o. The exchange of information among applications using shared databases or formatted message structures shall be based on the logical data models developed from identifying information requirements through activity models, where appropriate.
The data model identifies the logical information requirements that shall be developed into physical database schemata and standard data elements. The standard data elements shall be exchanged using the data management, data interchange, and distributed computing services of application platforms.
Refer to Section 2 for further guidance on these services. The goal is to exchange information directly between information systems, subject to security classification considerations.
Information exchange between systems using object-oriented interface definitions can be based on object models depicting those interfaces and the functional dependency of those interfaces. With object models, standard data elements are typically associated with the atomic data attributes that represent shared data. XML is widely used for metadata definition, management, and exchanges. Integrating XML with middleware technologies, CORBA for example, and core database technologies will provide the capability to exchange DoD mission-area data among heterogeneous environments.
Refer to 2. Information Exchange standards help form the Common Operating Environment COE , ensuring the use of system or application formats that can share data. Key references include 2. In distributed databases, other types of data messaging may be used as long as they remain DDDS-compliant. This section addresses standards for the following types of tactical information exchange messages: o.
Bit-oriented fixed and variable formatted Tactical Data Link TDL standards which allow real or near real-time tactical digital information exchange among air, ground, and maritime components of U. Character based information standards, which provide common, human-readable, and media independent messages used for planning and execution in joint and combined operations among U. The following standards are mandated for bit-oriented formatted messages: l.
Variable Message Format VMF is the DoD mandated standard for fire support information digital entry device exchange over tactical broadcast communications systems. The use of VMF has been extended to all war fighting functional areas. VMF minimum implementation and data forwarding requirements are under development.
Utilizing J-series messages and data elements, Link 22 uses an improved high frequency HF and ultra-high frequency UHF multimedia transmission scheme. However, within the U. On the same date, the approved subsequent years release is provided to developers for system updates within one calendar year. A few standards with a larger scope define their own specialized binary floating-point format for use within the scope of that standard.
VMF , the following standard is mandated as the format for transferring though not processing binary floating-point data: l. The tags themselves are not predefined, but user-defined that enables flexibility in its usage. In other words, XML models structural information of data independent of tag names. This section is concerned with exchange involving XML data formats. Examples of such data formats include object meta-data, APIs for database, transaction request-receive, mathematical equations etc.
Refer to Section 2. The objective of Section 5 is to standardize user interface design and implementation options, thus enabling DoD applications within a given domain to appear and behave consistently. The standardization of HCI appearance and behavior within DoD is expected to result in higher productivity; shorter training time; and reduced development, operation, and support costs. Section 5 addresses standards for the presentation and dialogue of the Human-Computer Interface.
The objective of system design is to ensure system reliability and effectiveness. To achieve this objective, the human must be able to effectively interact with the system. Operators, administrators, and maintainers interact with software-based information systems using the systems HCI. The HCI includes the appearance and behavior of the interface, physical interaction devices, graphical interaction objects, and other human-computer interaction methods.
A good HCI is both easy to use and appropriate to the operational environment. It exhibits a combination of user-oriented characteristics such as intuitive operation, ease and retention of learning, facilitation of user task performance, and consistency with user expectations.
The need to learn the appearance and behavior of different HCIs used by different applications and systems increases both the training burden and the probability of operator error.
What is required are interfaces that exhibit a consistent appearance and behavior both within and across applications and systems. Although GUIs are the preferred user interface, some specialized devices may require use of character-based interfaces due to operational, technical, or physical constraints.
These specialized interfaces shall be defined by domain-level style guides and further detailed in system-level user interface specifications. In order to present a consistent user interface, applications shall not mix interface styles; for example, mixing character-based interfaces and GUIs or combining Windows and Motif style elements.
When developing DoD automated systems, the graphical user interface shall be based on one commercial user interface style guide consistent with 5. Hybrid GUIs that mix user interface styles e. A hybrid GUI is composed of toolkit components from more than one user interface style. An application delivers the user interface style that matches the host platform i. This style conforms to commercial standards, with consistency in style implementation regardless of the development environment used to render the user interface.
Applications that use JTA Version 5. See 2. Character-based interfaces, primarily textual, are sometimes required for specialized devices due to operational, technical, or physical constraints. For systems with an approved requirement for character-based interfaces, guidance. A style guide is a document that specifies design rules and guidelines for the look and behavior of the user interaction with a software application or a family of software applications.
The goal of a style guide is to improve human performance and reduce training requirements by ensuring consistent and usable design of the HCI across software modules, applications, and systems. The style guide represents what user interfaces should do in terms of appearance and behavior and can be used to derive HCI design specifications defining how the rules are implemented in the application code.
Figure illustrates the hierarchy of style guides that shall be followed to maintain consistency and good HCI design within DoD. This hierarchy provides a framework that supports iterative prototype-based HCI development. The process starts with top-level general guidance and uses prototyping activities to develop system-specific design rules. The interface developer shall use the selected commercial GUI style guide and the appropriate domain-level style guide for specific style decisions, along with input of human factors specialists to create the system-specific HCI.
The following paragraphs include specific guidance regarding the style guide hierarchy levels. A commercial GUI style shall be selected as the basis for user interface development. If an X-Windows-based environment is selected, the style guide corresponding to the selected version of Motif is mandated.
For Motif style guides, the following standards are mandated: l. M CDE 2. Windows provide the visual means by which the user can interact with an application program. The standard in this service defines the user interface in terms of appearance and behavior according to JTA Version 5.
For a Windows-based environment, the following standard is mandated: l. These styles, when developed, will reflect the consensus on HCI appearance and behavior for a particular domain within DoD. The domain-level style guide will be the compliance document and may be supplemented by a system-level style guide.
Domain-level style guides should be complementary and non-conflicting with applicable commercial standards. System-level style guides provide the special tailoring of commercial, DoD, and domain-level style guides. These documents include explicit design guidance and rules for the system, while maintaining the appearance and behavior provided in the domain-level style guide.
The process of developing effective system-level style guidance and specifications is dependent upon a proper process for human systems integration engineering, as shown in Figure ISO , Human-centered design processes for interactive systems , provides a flexible model for inclusion of critical human systems integration issues into the design process.
Use of this process leads to interactive systems that are easier to use, reduces training and support costs, as well as improving user satisfaction and productivity. The purpose of warfighting symbology is to convey information about objects in the warfighter battlespace. The display of warfighting symbology has evolved from a static, manual operation to include fully automated computer generation.
This evolution has resulted in the fielding of many system-specific symbology implementations by the Combatant Commands, Services, and Agencies to meet the mission requirements of the warfighter. The C4I for the Warrior concept, signed by the Chairman of the Joint Chiefs of Staff in June , brings together C4I functions to provide the warfighter with a seamless, real-time, true representation of the battlespace.
To achieve this capability, standardization of warfighting symbology is playing an integral role in achieving interoperability during joint service operations. Symbology has been determined to be a critical interoperability factor in today and tomorrows digital battlespace.
For the display of common warfighting symbology, the following standard is. This section provides the mandated and emerging information security standards necessary to implement an appropriate level of protection for DoD Information Systems. The standards mandated in this section apply to all DoD IT systems. Security issues are divided into the following categories: the local computing environment 6.
The category Evaluation Criteria 6. This section covers security related standards for the local computing environment as defined by the IATF. This includes end-user workstations both desktop and laptop and servers. Note that some individual computing environments also need some of the services of enclave boundaries, e.
This section is further divided into applications including Web browsing, e-mail, and operating system and cryptographic security services.
This section provides mandated and emerging standards for secure Web browsing. This service identifies the protocol used to provide communications privacy over a network. The protocol allows applications to communicate in a way designed to prevent eavesdropping, tampering, or message forgery in e-mail packages. World Wide Web services provide abilities for navigation and data transport across the internet. The protocol encapsulates various higher-level protocols and is application independent.
TLS is not supported. It is expected that SSL 3. The following standards are both mandated for securing the communications of web browsers and web servers: l. This service applies to the use of security implementations for the Defense Messaging System DMS , the access control capabilities for communications with Allied partners, and for e-mail.
ACP was developed to take advantage of X. This security label provides for access control based not only on hierarchical classification, but also for compartments, categories, and citizenship. For DoD message systems required to process both unclassified and classified organizational messages using DMS Release 3. To support the access control capabilities of ACP , the following security label standards are mandated: l.
For individual messages that use certificates issued by the DoD PKI to protect unclassified sensitive information or sensitive information on system high networks the following standards are mandated: l.
IETF RFC provides optional enhanced security services, which are signed receipts non-repudiationproof of receipt , security labels, secure mailing lists, and signing certificates. For enhanced security services, the following standard is mandated: l.
Access control is the process to limit access to the resources of a system only to authorized processes or other systems in a network.
The identification process enables recognition of an entity subject or object by a computer system generally by the use of unique machine-readable user names. Authentication establishes the validity of a claimed identity. If DCE 1. If DCE Version 1. IETF RFC , A One-Time Password System, February , provides authentication for system access login and other applications requiring authenticationthat is secure against passive attacks based on replaying captured reusable passwords.
The following standard is emerging for one-time password systems:. This section provides mandated and emerging standards for Authentication Servers. Authentication servers are servers designed using security measures to. This service addresses the identification of security labels to be used with data. The data to which this service applies is defined in Section 2. This service provides a secure remote login and other secure network services over a network that does not necessarily provide security services.
Secure Shell SSH is a protocol for secure remote login and other secure. The following standard is emerging for securing specific terminal and X-Windows sessions:. This service provides security requirements associated with the transfer of binary and text files between user systems. These extensions provide strong authentication, integrity, and confidentiality on both the control and data channels.
This service identifies the standards to be used when security is required in association with distributed computing. Distributed computing allows various tasks, operations, and information transfers to occur on multiple physically or logically dispersed computer platforms. The Common Object Request Broker Architecture CORBA Security Services define a software infrastructure that supports access control, authorization, authentication, auditing, delegation, non-repudiation, and security administration for distributed-object-based systems.
This infrastructure can be based on existing security environments and can be used with existing permission mechanisms and login facilities. The key security functionality is confined to a trusted core that enforces the essential security policy elements. Level 1 provides support for a default system security policy covering access control and auditing.
Level 1 is intended to support applications that do not have a default policy. Level 2 provides the capability for applications to control the security provided at object invocation and also for applications to control the administration of an application-specific security policy. Level 2 is intended to support multiple security policies and to provide the capability to select separate access control and audit policies.
This service defines the protection profile, and the levels of such protection profiles, to be applied to the operating system. A protection profile is defined in the Common Criteria see 6. For the application platform entity, the following protection profiles are.
For basic robustness:. To support interoperability using encrypted messages, products must share a common communications protocol. This protocol must include common cryptographic message syntax, common cryptographic algorithms and common modes of operation e. The mechanisms to provide the required security services are as follows. Encryption algorithms are a set of mathematical rules for rendering information unintelligible by effecting a series of transformation to be the normal representation of the information through the use of variable elements controlled by a key.
The following standard is mandated when the security policy or the program. For those systems required or desiring to use a cryptographic device to protect privacy act information and other unclassified information not covered by the Warner Amendment to Public Law , the following standard is mandated: l. The following standard is emerging for encryption of sensitive but unclassified. Key-Hashing for Message Authentication HMAC is a mechanism for message authentication using cryptographic hash functions, and can be used with any iterative hash function in combination with a shared secret key.
The cryptographic strength of HMAC depends on the properties of the underlying hash function. Note that HMAC prevents extension attacks that iterative hash functions do not prevent.
The following standard is mandated when the security policy or program security. For computing shared-secret key message authentication codes MAC , the following is mandated: l. A signature algorithm is an algorithm developed to assure message source authenticity and integrity. The intent of the signature is to provide a measure of assurance that the person signing the message sent the message that is signed, and that the contents of the message have not been changed.
Cryptographic tokens are portable, user controlled, physical devices used to store cryptographic information and possibly perform cryptographic functions. A cryptographic token is used to validate and end entity's identification and bind that identity to its public key. Cryptographic algorithms are the source code formats and procedures through which an application program accesses cryptographic hash algorithms, digital signature algorithms, and key management algorithms.
An example application is secure electronic mail in which data needs to be protected without any online connection with the intended recipient s of that data. Subsequent to being protected, the data unit can be transferred to the recipient s or to an archiveperhaps to be processed as unprotected days or years later. Cryptographic key algorithms are mathematical expressions that develop a sequence of symbols that controls the operation of encipherment and decipherment.
This section provides mandated standards for Cryptographic Modules. Also see the JTAs cryptologic subdomain. This section defines standards for devices to support effective control and monitoring of the data flows into and out of a physical or logical enclave. This provides boundary defenses for those components within the enclave that cannot defend themselves due to technical or configuration problems.
A firewall is a system or combination of systems that enforces a boundary between two or more networks. Pipeline maintenance training is in place to support the approved aircraft and systems maintenance plans. Where appropriate, maintenance training courses have been revised to provide the minimum training necessary for first enlistment personnel.
This is called initial training. Personnel who have received initial training and have been assigned to a second tour of duty in VQ-3 or VQ-4 will receive additional training which is designed to assist them in their assignment to billets of greater responsibility.
This is called career training. Aircrew training tracks listing the specific courses required for personnel assigned to the various aircrew billets have been developed and approved by CNO. Normally personnel assigned to fill aircrew billets are provided only that training required by the aircrew billet. TACAMO aircrews are also responsible for organizational level maintenance while the aircraft is deployed to remote locations away from the parent squadron.
This imposes an additional pipeline training requirement. The analysis includes a task and skills media selection to determine the most cost effective use of Computer Aided Instruction CAI , self paced Interactive Courseware, and hands-on use of existing training devices. A prototype CBT lesson will be developed upon completion of the analysis. Initial Training. Follow-on Training. Training Pipelines. Modify curriculum as appropriate to meet CAT I training requirements of fleet squadrons.
No additional time to train is authorized. Upon approval, submit curriculum to training contractor to effect changes to the syllabus. This is a 1-day course taught by the FAA. Note: 1. Upon approval, submit curriculum to training contractor so that the syllabus may be changed. Do not hold up FE training if student pilots are not available.
Action command: CNO. Restructure E-6 FE CAT I syllabus E for normal checklist procedures at beginning of course and put emergency procedures at the end of the course. Action command: CNET. Submit proper paperwork up admin chain of command so detailers will add appropriate P-text on orders. Change NEC Manual.
Extend course C to include how to maintain the reel system to include aircraft systems description, aircraft pubs, electrical and hyd power. Course not to exceed 60 P days. Change NEC manual. Action command. Add note to NEC Course length not to exceed 7. Repair Organizational Maintenance. Second tour aircrewmen require a Cat II course. Use CIN C if possible. No increase in course length authorized. Revise C to add borescope lab and remove slide valve information.
0コメント