Approval Date:

13 Mar 97

Document:


3900
C 44
                                                          13 Mar 97

From:  Commanding General, Marine Corps Combat Development Command,
       3300 Russell Road, Quantico, Virginia 22134-5021 (C 442)

Subj:  OPERATIONAL REQUIREMENTS DOCUMENT (ORD) FOR THE AN/TSQ-90D TACTICAL        ELECTRONIC RECONNAISSANCE PROCESSING AND EVALUATION SYSTEM (TERPES) UPGRADE (NO.    INT 255.2.2A); CHANGE 1

Ref:   (a) DoD Regulation 5000.2-R
       (b) Operational Requirements Document (ORD) for the AN/TSQ-90D Tactical      Electronic Reconnaissance Processing and Evaluation System (TERPES) Upgrade
           (NO. INT 255.2.2A)

1.  Purpose.  Per reference (a), the following pen changes to reference (b), the basic Operational Requirements Document (ORD) for the AN/TSQ-90D Tactical Electronic Reconnaissance Processing and Evaluation System (TERPES) Upgrade (NO. INT 255.2.2A) are approved.

2.  Action

    a.  Replace the third sentence in paragraph 4.a. with the following:  "The TPU shall be capable of removal from the shelter and operated aboard ship, in the Advanced Tactical Air Command Center (ATACC) and/or in a field environment in the ATACC."

    b.  Replace the first sentence in paragraph 4.c.(4) with the following:  "This ORD shall be reviewed to ensure currency with the requirements of the Marine Force (MARFOR)."

    c.  Replace the first sentence in paragraph 4.d.(1)(f) with the following:  "The system shall be maintained by the using unit in accordance with critical low density equipment."  Delete the second sentence.  
 
    d.  Replace the last sentence in paragraph 4.e.(2)(a) with the following two sentences:  "The TERPES Upgrade must be capable of undergoing standard NBC decontamination process, when contained within shelter and/or transit cases.  No internal equipment will be,  subject to a decontamination process due to COTS nature."

    e.  Delete the words "and MAW" in paragraph 5.a.(1).

    f.  Replace paragraph 6.b.(4)(a)1 with the following:  "Intelligence Analysis System, via wireline and/or LAN."

    g.  Replace paragraph 6.b.(4)(b)4 with the following:  "Joint Services Imagery Processing System (JSIPS), via LAN."

    h.  Add the following new subparagraph "4.b.(4)(b)15.  The Tactical Aircraft Mission Planning system (TAMPS), via LAN and/or digital tape."

    i.  Delete the following words from paragraph 6.b.(4)(c)5:   "via wireline, and/or".

    j.  Replace paragraph 6.b.(4)(d)2 with the following:  "TAMPS via LAN and/or digital tape."

    k.  Add the following sentence to the end of paragraph 6.c.(1):  "The TPU shall be transported in accordance with established procedures for  computer and electronic equipment."

    l.  Replace the acronym FMF with "MARFOR" in paragraph 7.b.
       
3.  Filing Instruction.  This change transmittal will be filed immediately following the signature page of the basic ORD.

4.  The Marine Corps point of contact for this requirement is the Command, Control, Communications, Computers, and Intelligence (C 442), Requirements Division, MCCDC, DSN 278-3322 or commercial 703-784-3322.



R. J. ANTONICH
By direction  


OPERATIONAL REQUIREMENTS DOCUMENT
FOR THE
AN/TSQ-90D TACTICAL ELECTRONIC RECONNAISSANCE PROCESSING

        AND EVALUATION SYSTEM (TERPES) UPGRADE (No. INT 255.2.2A)

    
1.  General Description of Operational Capability

    a.  Mission Area.  The Tactical Electronic Reconnaissance Processing and Evaluation System (TERPES) Upgrade capability falls under Mission Areas 12 (Intelligence) and 36 (Electronic Warfare).  It supports actions in the Marine Corps Master Plan, (MCMP) 1994-2004, dated 21 July 1993.

    b.  System Type.  The requirement exists for a capability to
process Signals Intelligence (SIGINT) and Electronic Warfare (EW) information collected from the EA-6B aircraft mission, correlate it with other sources of Electronic Intelligence (ELINT), Electronic Warfare Support Measures (ES), and Order of Battle (OOB) information to provide support to the Marine Air-Ground Task Forces (MAGTF) during operations afloat and at Forward Operating Bases (FOB).  The requirement exists for a smaller system, downsized from the current two shelter configuration to one shelter; and a team portable capability, which can be carried aboard ship as well as into field environments at FOB.  This capability is necessary for all types of MAGTF operations; to complement national, theater, fleet, MAGTF SIGINT/EW operations, support to aviation operations, and MAGTF afloat operations in support of the Tactical Marine Electronic Warfare Squadrons (VMAQ) and their respective mission.
            
    c.  Operational Concept  

        (1) The mission is currently conducted by the
AN/TSQ-90D(V), which is a Command and Control Warfare (C2W)/EW system which processes signals information collected by the EA-6B aircraft, and combines the information with other intelligence and C2W/EW information.  Additionally, the system shall disseminate the information to intelligence sections for further analysis and dissemination throughout the MAGTF.  Finally, the system shall provide reports for air mission planning and operations to the VMAQ squadrons.

        (2) The TERPES Upgrade shall perform the same functions and be employed as the equipment it will replace; in accordance with the doctrine, procedures, and techniques prescribed in Fleet Marine Force Manuals 3-23, and 7-12, and applicable United States Signals Intelligence Directives (USSID).  It shall be employed with the VMAQ, to best support the Air Combat Element(ACE).  In
garrison, the system will support training, intelligence sections, and provide ELINT support to contingency planning.

         (3) TERPES Upgrade shall accomplish its missions through performance of the following major functions:

             (a) Process, evaluate, and analyze collected EW information from EA-6B missions.
 
             (b) Provide enemy Electronic Order of Battle (EOB), C2W capabilities, ELINT information, and reports to the MAGTF.
 
             (c) Provide C2W mission planning support information to assist Marine tactical aviation elements.

             (d) Provide C2W information and Indications and Warning (I&W) to the MAGTF.

    d.  Support Concept.  The TERPES Upgrade shall consist of critical low-density equipment with similar logistic support requirements as the equipment it replaces.  It is not expected to change VMAQ logistic support requirements or procedures.

    e.  Mission Need Statement (MNS) Summary.  MNS number CCC 11.21, dated 13 December 1993, for Command and Control Warfare (C2W), Cryptologic, and Signals Intelligence (SIGINT) validated the requirement for the upgrade.

2.  Threat.  The Marine Tactical Command and Control System (MTACCS) (now MAGTF Command, Control, Communications, Computers, and Intelligence, C4I) (1992-2010) System Threat Assessment Report of 16 December 1992 details specific threat information.  Foreign Command, Control, Communications, Computers, and Intelligence (C4I) systems (the threat TERPES Upgrade is designed to exploit and defeat) and C2W capabilities (the threat to TERPES Upgrade communications) are documented in Defense Intelligence Agency (DIA) documents.  

    a.  Threat to be Countered.  The TERPES Upgrade targets are contained in DIA's equipment and country series handbooks (e.g., Command, Control, and Communications Handbook, Telecommunications Equipment Handbook, and Radar Handbook); the Joint-Service Tactical Exploitation of National Systems Manual (J-TENS), Tabs 4B and 4C, 27 September 1991; Headquarters, U.S. Marine Corps, Marine Corps SIGINT/EW Plan, of August 1992; and the Marine Corps Combat Development Command, SIGINT Technologies Survey (1998- 2005), 31 January 1994.  The TERPES Upgrade is not designed to overcome, destroy, or attack any specific threat, but to support the VMAQ squadrons, which do perform such actions.

    b.  Projected Threat Environment.  TERPES Upgrade could be subjected to two major types of threats:  C2W and electronic interference.  

       (1) The primary threat is enemy C2W, which includes computer viruses and the pote ntial of physical destruction.  TERPES Upgrade shall also be vulnerable to all forms of intentional and unintentional forms of interference, common to electronic equipment and are described in the following Defense Intelligence Agency and Service approved documents:  Worldwide EW Threat (DST-1730H-018 and DST-1730H-077), and the System Threat Assessment for the Marine Tactical Command and Control System (MTACCS) (1992-2010), 16 December 1992.

         (2) The threat to TERPES Upgrade communications is presented in various DIA C2W publications, such as:  ESM/ECM Capabilities - ECC, Free World Electronic Warfare Capabilities, and Rest-of-the-World Electronic Warfare Index.  These and other representative threats to MAGTF C4I systems are contained in the DIA reviewed Marine Corps Intelligence Activity's System Threat Assessments Report for the Marine Tactical Command and Control System (MTACCS) (1992-2010), 16 December 1992.

         (3) The TERPES Upgrade is susceptible to physical attack and other enemy action when deployed at FOB.

    c.  Present and Projected Threat Against the System.  Potential enemy threats confronting the Marine Force (MARFOR)
in the current to long range are outlined in the MCMP.  The primary threat includes standoff weapons such as missiles and artillery, air delivered ordnance, biological and chemical munitions, and direct action from unconventional units.  Improvements in reconnaissance, surveillance, target acquisition, surface-to-surface missiles, artillery ranges, and air delivered ordnance, has provided potential adversaries greater standoff ranges and accuracy to engage rear area Command and Control (C2) facilities.  Threats also exist from nuclear weapons, non-nuclear electromagnetic weapons, and Radio Frequency (RF) weapons which produce physical damage to electronic components.  

3.  Shortcomings of Existing Systems.  The existing TERPES Phase III is too large for deployment afloat, cannot be used aboard amphibious shipping, and in many instances, cannot deploy to FOB due to lift constraints, space limitations and size.

4.  Capabilities Required  

    a.  General.  TERPES Upgrade will extend the service life, maintain compatibility with the EA-6B, and improve the deployment capability of the existing system.  The TERPES Upgrade shall be capable of operating either while housed in one 8' x 8' x 20' shelter, transportable via the Logistics Vehicle System (LVS)or as a Terpes Portable Unit (TPU) which can be removed from the shelter to provide a highly transportable option for deployment.  The TPU s hall be capable of removal from the shelter and operated aboard ship, in the Tactical Air Command Center (TACC) and/or in a field environment in the TACC.  The TPU shall provide a dynamic configuration capability to include only the equipment from the shelter that is required to support a particular mission.

    b.  Sub-systems.  TERPES Upgrade consists of central processing units, data storage device(s), workstations, and input/output devices.  The major subsystems consist of:

        (1) Data Processing.

        (2) Communications.
            
        (3) Auxiliary Support.

    c.  System Performance.  TERPES Upgrade is the singular evaluation point for analysis and dissemination of EA-6B collected C2W/EW information within the MAGTF.  It shall be capable of communication and data exchange within the MAGTF C4I architecture.  

        (1) Parameters.  The following parameters shall be provided within the TERPES Upgrade:

            (a) Identify and provide location information on enemy non-communications emitters from data collected by the
EA-6B aircraft.

            (b) Provide EW mission planning support information to assist Marine tactical aviation elements.

            (c) Provide ELINT reporting to national data bases.

            (d) Update OOB data bases.

            (e) Alert operators to equipment failure and pre- designated high interest events.

            (f) Send, receive, store messages and information.

            (g) Provide the capability to semi-automatically
update files/data bases.

            (h) Display images of maps and overlays.

            (i) Display imagery.

            (j) Store and maintain Military Intelligence Integrated Data System/Integrated Data Base (MIIDS/IDB) data.
       
            (k) Allow simultaneous access to all software applications by all workstations in use.

            (l) Workstations:
       
                1 Keyboard input.

                2 Transfer and store of electronic data.
           
                3 Display of classified information.

                4 Provide word processing, mapping, and graphics software applications.
           
            (m) System set-up and tear down time is based on all tasks needed for operations, relocation, movement, and/or termination of operations.  Set-up includes provision of power, environmental control, cable hook-up, equipment turn-on, and start-up testing.  All system components must be assembled, operational, and communications ready.  Tear down includes all actions necessary for disassembly, disconnection, packing, storage, and preparation for transport; or the reverse of set-up.  Crew size is no more than four Marines (threshold) or two Marines (objective) and integral to both set-up and tear down times.  The time parameters (in hours) are listed in the following table.

           Set-up, installation and deinstallation times
                       with a crew of four  

     Parameter

     Shelter
Threshold Objective

       TPU
Threshold Objective

 Set-up at FOB
     and/or
 Field Environment

  
    5         2

    4        2

 Remove from shelter

    -         -    

    5        2

 Set-up aboard ship

    -         -

    5        2

        (2) Wartime Mission Scenarios

            (a) Mission Duration (MD).  The TERPES Upgrade MD is 12 hours.  It is applicable to all types of operations and exercises.  

            (b) Mission Profiles.  The following table demonstrates the mission profiles in percentages of MD.  

                 TERPES Upgrade Mission Profile

    Mission Mode        Garrison      Shipboard    Battlefield
                        Operations    Operations   Operations

 Contingency Planning   Mission Planning
 Mission Support
 Intelligence Support

 
   35%
   35%
   30%

    50%
    25%
    25%

    50%
    25%
    25%

 Mission Support 
 Data Analysis
 Reporting              Briefing      

   50%
   25%
   25%

    50%
    25%
    25%

    50%
    25%
    25%   

   Communications
 Intelligence Support   Reporting              Briefing         

   25%
   50%
   25%

    50%
    25%
    25%

    50%
    25%
    25%



             TERPES Upgrade Mission Profile (Cont.) 

    Mission Mode        Garrison      Shipboard    Battlefield
                        Operations    Operations   Operations

      Training
 Contingency Planning
 Mission Support
 Mission Planning
 Data Analysis
 Intelligence Support   Reporting       
 Communications

   15%
   15%
   10%
   25%
   15%
   15%
    5%

    --

    --

        (3) System Support.  The system may be required to provide support to the MAGTF on a round the clock basis, dependent upon the tactical situation and mission.

        (4) Modifications.  This ORD shall be reviewed to ensure currency with the requirements of the FMF.  Modifications,
changes, and requirements may be identified from time to time and are encouraged.  A continuing evolutionary acquisition strategy shall be p ursued to preserve leading edge technology.

        (5) Future Capabilities.  The following objective capabilities are identified for future enhancements:

            (a) Interoperate during airborne missions with the EA-6B, via secure voice and/or data link.

            (b) Process near-real-time data link information from the EA-6B aircraft.

            (c) Operate with a tactical positioning system.

            (d) Use the Tactical Automated Sanitization (TAS) multi-level security device or procedure, if available.

            (e) Process Sensitive Compartmented Information.

            (f) Communicate within the Super High Frequency (SHF) and Extra High Frequency (EHF) spectrum.  

        (6) Employment Tactics.  The system will be employed in accordance with the doctrine, procedures and techniques prescribed in Joint Pub 2-0, Joint Doctrine for Intelligence Support to Operations, CJCS MOP 6, Electronic Warfare, Fleet Marine Force Manual (FMFM) 3-21, Intelligence, FMFM 3-27, Aviation Intelligence; FMFM 5-10, Air Reconnaissance; and FMFM 7-12, Electronic Warfare.  The system shall deploy for use in field environments for the period of time necessary to accomplish the mission.  In garrison, the system will support the mission planning, contingency operations, exercise support, and training.  It may be used to support the Commander, Joint Task Force (CJTF) or Marine Component Commander, if the MEF Commanding General is assigned those roles.  

        (7) Environmental Conditions.  TERPES Upgrade shall operate without degradation in all climates and environments that Marines from the tactical electronic warfare squadrons (VMAQ) may encounter.  The system will operate in all combat and environmental conditions; including: smoke, dust, rain, fog, arctic, and desert environs.  There may be variations in shipboard and battlefield operations.  When the TPU operates outside of its shelter it shall be operated in an environment protected from the elements.  The system must be protected from rain, sand, salt, and wind by tentage or other appropriate cover.

     d.  Logistics and Readiness

         (1) Measures.  Peacetime and wartime are identical.

             (a) Mean Time Between Operational Mission Failure (MTBOMF).  The reliability of the TERPES Upgrade depends on the MD and MTBOMF.  The MTBOMF threshold is 114 hours; objective - 994 hours.  An operational mission failure occurs if the system cannot perform any mission essential functions.  

   (b) Operational Availability (Ao).  The Ao is:  threshold - .80; objective - .85 or greater.

             (c) Achieved Availability (Aa).  An Aa of 0.993 is the threshold for the system; objective - 0.994 or greater.

             (d) Reliability:  .90 Threshold; .988 Objective.

             (e) Preventive Maintenance.  Preventive maintenance of the system shall consist of not more than six hours per week of routine operator maintenance common to electronics and computer equipment.  These hours are additional to maintenance for any dedicated transport vehicle.

             (f) Maintenance and Repair.  The system shall be maintained by the using unit.  Second echelon and higher repairs will be conducted by maintenance personnel in the communications-electronics elements of the MAW.  
    
                 1 Mean Time to Repair (MTTR).  The MTTR shall be 60 minutes (threshold) or less (objective) for Organizational Level Maintenance (OLM), two hours or less for Intermediate Level Maintenance (ILM), and one month or less for Depot Level Maintenance (DLM).  90% of all OLM, 85% of all ILM, and 75% of all DLM repairs shall not exceed these limits.

                 2 Maximum Time to Repair (MaxTTR).  The MaxTTR shall be one hour or less for OLM, six hours or less for ILM, and one month or less for DLM.

             (g) Built-in Test (BIT)/System Diagnostics.  BIT shall detect 90% of malfunctions, within each variant.  Each malfunction shall have at least a 90% level of confidence that a malfunction has occurred.  BIT system diagnostics shall be used to isolate and identify internal faults.  The BIT reliability is: Threshold - 90%; Objective - 95%.  The BIT accuracy rate is: Threshold - 90%; Objective - 95%.

             (h) Dormant Reliability.  The TERPES Upgrade may be stored for transport or staging prior to transport for lengthy periods of time.  All equipment must operate with 90 percent availability, after 180 days of storage at temperatures no greater than plus 30 degrees celsius or lower than 0 degrees celsius.  After a period of non-operation, transportation, or storage, the system shall require a 30 minute warm-up period, after which the system shall be fully capable for operation.

         (2) Combat Support Requirements 

             (a) Battle Damage Repair Capability.  None required.

             (b) Mobility Requirements  

                 1 The Upgrade shall be contained in no more than one shelter, no larger than 2.44 X 2.44 X 6.1 meters (M), (approximately 8  X 8 X 20 feet).

                 2 The TPU shall be capable of transport in tactical vehicles, aboard all types of airlift aircraft and aboard ship.

                 3 Each TPU component shall be capable of transport to and from tactical vehicles, all types of airlift aircraft and aboard ship by no more than four Marines (threshold) or two Marines (objective).


            (c) Weight.  The following weight requirements apply.

       TERPES Upgrade Weight Parameters in Kilos (Kg)

    Component

     Threshold

    Objective

      Shelter

      5700 Kg

     4550 Kg

    Complete TPU

      1100 Kg

      700 Kg

   Individual TPU
    components

        90 Kg

       65 Kg

      
            (d) Expected Maintenance Manpower and Skill Levels.
Manpower and skill level requirements shall not change.

            (e) Surge and Mobilization Objectives and Capabilities.  TERPES Upgrade does not require planning or programming for surge, mobilization or reconstitution.

    e.  Critical System Characteristics 

        (1) Shielding.  Shielding from the effects of RF and high power microwave effects and small arms weapons, directed energy weapons and high energy electromagnetic pulse is an objective.

        (2) Survivability  
     
            (a) Nuclear, Biological, and Chemical (NBC) Contamination.  The equipment must survive in an NBC environment to the same extent as operators wearing Mission Oriented
Protective Posture (MOPP) and/or cold weather clothing.  The TERPES Upgrade must be capable of undergoing standard NBC decontamination process, when contained within shelter and/or transit cases.

            (b) Electronic Protection (EP) Features.  No special EP features are required.

            (c) Wartime Reserve Modes.  None required.

        (3) Natural Environmental Factors.  TERPES Upgrade shall
operate in all climates and environments that MAW units may encounter, to include operations from forward operating bases.  TERPES must handle the dirt/dust/sand, humidity, precipitation, temperature, and wind handled by the AN/TSQ-90D.  When the TPU is removed from the shelter, it will be operated in an environment protected from the natural elements.  There is no need for oceanographic support.

        (4) Electromagnetic Spectrum

            (a) Electromagnetic Compatibility.  The system shall operate in the electromagnetic environment without causing or experiencing degradation of communications and equipment due to electromagnetic interference to or from other friendly electronic equipment.  MIL-STD-461C is applicable.  

            (b) Frequency Spectrum Assignment.  The system
shall be capable of connectivity for communications in the frequency spectrum authorized for the MAW.  

                1 The primary means of communications is digital data communication via the MAGTF C4I architecture.  

                2 TERPES Upgrade shall be capable of connection
with voice and/or data communications within the MAGTF.

                3 Exchange data via Local Area Network (LAN)
and/or Wide Area Network (WAN), in accordance with the MAGTF C4I and the Joint Maritime Command and Control Information System (JMCIS) network protocols and standards when aboard ship.  

                4 When part of an amphibious task force and deployed aboard ship, connectivity to joint, theater, and national intelligence organizations shall be via doctrinal ship to shore radio nets.   

                5 Alternative means of information transfer consist of delivery of magnetic media via couriers and/or voice communications.

        (5) Expected Mission Capability in Various Environments

            (a) Full.  Afloat, garrison, and conventional operational and training environments.

            (b) Degraded.  Nuclear environments.
     
        (6) Safety Parameters.  TERPES Upgrade shall meet safety standards for communications, computer and electronics equipment.
Grounding and bonding requirements will be in accordance with MIL-STD-188-124.  Integrity for electromagnetic interference, grounding and bonding, and electrostatic discharge will be maintained in the TERPES Upgrade shelter.  Design and operation must not create any unsafe or dangerous situations.

            (a) System.  The system shall be safe.  Operation must permit grounding of equipment and protect personnel from:

                1 Accidental contact with dangerous electrical components, to include servicing the equipment and protecting personnel from hazardous voltages.

                2 Radio frequency emissions.

                3 Physical injury resulting from heavy loads.

            (b) Flight.  TERPES must not interfere with the safe
operation of aircraft.

        (7) Security Needs

            (a) Communications.  When provided, voice and data communications capabilities must incorporate standard Communications Security (COMSEC) devices.  This ensures secure transmission of tasking, direction, reporting, and dissemination
of intelligence information throughout the MAGTF.

            (b) Information.  No security equipment is necessary beyond standard cryptographic devices and software protection.

            (c) Physical and Operational.  TERPES Upgrade shall possess a security system to prevent unauthorized disclosure of classified information and the means to physically destroy and/or purge all classified information within a 30 minute period.

        (8) Power Source.  TERPES Upgrade shall be capable of operation from standard U.S. Marine Corps Mobile Electric Power (MEP) generators, shipboard electrical power converted from Delta connected to Wye connected 120/208 VAC, 4-wire, 3 phase, 60Hz power, plus or minus 10% tolerance, or from standard, commercial power when provided as 120/208 VAC, 4-wire, 3 phase, 60 Hz, Wye connected power, plus or minus 10% tolerance.  Power surge protection and an uninterruptible power source are required for shutdown of the system, to provide a memory save for all workstations within five minutes from any power loss.

5.  Integrated Logistics Support (ILS)

    a.  Maintenance Planning 

        (1) Maintenance Tasks.  Preventive and scheduled maintenance will be performed by VMAQ and MAW personnel using the same procedures currently extant for the TERPES Phase III.

        (2) Planning Approach for Contract Versus Organic Repair.
Approach to repair remain as with the TERPES Phase III.

    b.  Support Equipment.  The TERPES Upgrade shall not generate any need for new support equipment.

    c.  Human Systems Integration 

        (1) The system must be easy to install, erect, and
set up.  Cables must be labeled and easy to connect and disconnect.

        (2) Component design, especially cables, connectors, and controls, shall not restrict operator activity or present a security or safety hazard.

        (3) It shall allow operators to continue using
the TERPES Upgrade (all mission essential functions) while wearing all levels of NBC protective clothing. (See 4c(2)(a)).

        (4) Controls and displays shall be easy to locate,
and visible under all light conditions.  Light intensity shall be adjustable and programmable.  

    d.  Operational and Maintenance Training Concept

        (1) Pipeline.  No TERPES upgrade will generate any need for additional manpower; however, it may create the need for operators, maintainers, and system administrators to attend new or modified formal schools and unit training.

            (a) Operators.  The established formal course is conducted at the Navy and Marine Corps Intelligence Training Center (NMITC). Operators will be taught system operation; to include:  assembly/disassembly, component and system description, design characteristics, operating features, hardware configuration, installation, isolation of malfunctions, preventive maintenance, use of power, EA-6B aircraft mission planning, and mission processing and analysis in accordance with the MCCDC-approved TERPES Operator Course.  Operators will be taught cryptologic skills through courses offered by the Cryptologic Training System, per MCO 1540.33A.

            (b) Maintainers.  The established formal course is conducted at the NMITC.  Maintainers will be taught TERPES maintenance procedures and maintenance support skills to perform corrective maintenance to the lowest replaceable unit in accordance with the MCCDC-approved TERPES Maintenance Course.

            (c) System Administrators.  This course may be established as an adjunct to existing courses conducted at NMITC.
System Administrators will be taught system administration including the UNIX operating system, system installation procedures, SYBASE database administration, administration of TERPES applications, and system security procedures.

        (2) Training Devices.  A TERPES Upgrade system (less shelter) shall be held at the NMITC for use by the students.

        (3) Embedded Training/Onboard Training.  HELP Files, Expanded HELP Files and Embedded training shall be required.

        (4) Interactive Courseware.  None required.

    e.  Constraints

        (1) Manpower.  Existing manpower structure must not increase.

        (2) Personnel.  TERPES must not create the need for
additional Military Occupational Specialties (MOS).

        (3) Training.  The TERPES Upgrade must not create the need for more or new training; however, modification and updating of existing courses are expected and acceptable.  All training must conform to the  Individual Training Standards for MOS 2602, 2631, and 2821.

        (4) Manpower and Training Methodologies.  Formal
school training courses shall be used in conjunction with On the Job Training (OJT) for the TERPES Upgrade system.

    f.  Computer Resources 

        (1) Constraints

            (a) Language.  The operational software may be integrated from Non-Developmental Items (NDIs), Government Furnished Information, Government Furnished Equipment (GFE) and Commercial Off-The-Shelf (COTS) applications.  All operational software applications are designated mission-critical software.  If software is not developed in Ada, in accordance with
MIL-STD-1815A, a waiver must be obtained.

            (b) Computer.  The computer workstations shall conform with systems available from the Marine Common Hardware System (MCHS) to ensure interoperability, compatibility, and supportability with the MAGTF C4I architecture and its systems.  Non-FMF/Marine Corps standard computers are not desired, but  acceptable if supportable and a waiver is provided by Headquarters, U.S. Marine Corps (Code CSB).  The following tables demonstrate the threshold and objective numbers of computer workstations and peripherals.

TERPES Upgrade Major Peripherals

PeripheralUpgrade
(threshold/objective)TPU
(threshold/objective)

Workstations 3          31         3

Printer  1          10         1

Plotter 1          10         1

         (2) Data Storage.  The following table provides the
minimum computer memory and storage capacity.

 TERPES Upgrade     

   Minimum Memory
  in Megabytes (MB)

  Minimum Storage
      Capacity

   Workstation

      84 MB   

   760 MEGABYTES

   File Server

     320 MB        

     4 GIGABYTES     

         (3) Architecture.  The system architecture must allow future capabilities, improvements and system growth to provide continued interoperability with emerging and planned systems.
TERPES is part of the MAGTF Command Control Communications Computer and Intelligence (C4I) Architecture.

         (4) Interoperability.  TERPES Upgrade must meet compatibility and interoperability standards as set forth in Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 6212.01, Department of Defense Directive (DoDD) 4630.5, and DoD Instruction (DoDI) 4630.8, DoD Technical Reference Model (TRM) for Information Management, Volume 2 of the Technical Architecture Framework for Information Management (TAFIM), and the Department of Defense Intelligence Information System (DODIIS) Profile.  Annex A contains specific protocol standards.

         (5) Support Resources.  No special support resources are
necessary or acceptable.

         (6) Capabilities Desired for Integrated Support.  No special capabilities are required.

         (7) Documentation Needs.  No special documentation needs exist.

    g.  Other Logistics Considerations 

        (1) Provisioning Strategy.  The TERPES Upgrade shall not use any new logistics procedures and shall be supported using the Contractor Logistics Support (CLS) procedures currently in place for the AN/TSQ-90D(V).  The VMAQ will use the same procedures currently used for provisioning the AN/TSQ-90D.  Following completion of the provisioning effort, MARCORLOGBASES Albany will assume support of the system, with CLS providing further support as required.  Some procedures currently in use include:  contractor provided spare blocks, on-site support, and the revision of technical manuals.

        (2) Unique Requirements

            (a) Facility.  None.

            (b) Shelter.  None.
        (3) Special Considerations.  No special packing, handling, or transportation requirements are acceptable.

        (4) Unique Data Requirements.  None.  

        (5) Maintenance Tools.  To the maximum extent possible, General Purpose Test Equipment (GPTE) and common Tools resident in the Marine Corps inventory will be used to perform all corrective and preventive maintenance at all authorized levels of maintenance.  Tools and test equipment required but not resident in the Marine Corps inventory will be identified as Special Tools and Special Purpose Test Equipment (SPTE), respectively, at all authorized levels of maintenance.

6.  Infrastructure Support and Interoperability.  There are no
companion Operational Requirements Documents (ORDs).  

    a.  All other Services have similar requirements:  

        (1) U.S. Army - Joint Interest:  Interim Tactical ELINT                Processor (ITEP) Electronics Processing and                        Dissemination System (EPDS).

        (2) U.S. Air Force - Joint Interest:

            (a) Tactical Electronic Reconnaissance Exploitation
                Center (TEREC).

            (b) Emitter Location System (ELS).

        (3) U.S. Navy - Joint:  VP/VQ reconnaissance aircraft
            ELINT suites and equipment.

    b.  Command, Control, Communications, and Intelligence  

        (1) System Integration.  TERPES Upgrade shall be completely integrated into the MAGTF C4I architecture and shall
possess software applications which are compatible with the Tactical Aircraft Mission Planning System (TAMPS), Tactical EA-6B Mission Support System (TEAMS), and the Joint Maritime Command Information System (JMCIS).  

        (2) Data Requirements  

            (a) Data.  Threshold - 1200 Bits Per Second (BPS);

                       Objective - 9600 BPS.

            (b) Voice. Threshold - single channel voice, within
                                   the MAGTF;

                       Objective - single channel voice external
                                   to MAGTF;
            (c) Video. None required.

        (3) Computer Network Support and Data Protocols and Standards.  The system shall provide connectivity to all required applicable data communications networks within the MAGTF C4I Architecture.  At a minimum, it shall conform to all data communications protocols and data standards supported by the Tactical Data Network (TDN) (See TDN ORD CCC 11.16).

        (4) Unique Intelligence Information Requirements

            (a) Threshold Intelligence Interfaces.  The TERPES shall be capable of exchanging information, through passing files and reports.  Files are defined as United States Message Text Format (USMTF), data base, graphics, map overlays, and word processing.  The system will interface with the following MAGTF C4I systems, via the method indicated, as a threshold:

                1 Intelligence Analysis System, via data link
                  and/or wireline.

                2 Tactical and Related Applications (TRAP)/
                  Tactical Data Information Exchange Service
                  (TADIXS-B) broadcasts via the Tactical Receive
                  Equipment (TRE) or equivalent transceiver.
                3 Tactical Digital Information Link (TADIL) -A,
                  via HF radio.

                4 TADIL-B, via wireline.

                5 EA-6B aircraft via UHF radio and digital tape.

            (b) Objective Intelligence Interfaces.  The system shall interface with the following intelligence related systems, via the meth od indicated, as an objective:

                1 AN/TSQ-130(V), Technical Control and                               Analysis Center (TCAC) via data link.   

                2 EA-6B aircraft via binary data link.

                3 Joint Maritime Command Information
                  System (JMCIS), via LAN.

                4 Joint Services Imagery Processing System
                  (JSIPS), via data link.

                5 The U.S. Air Force Combat Information
                  System (CIS), via LAN.

                6 The U.S. Army All Source Analysis System
                  (ASAS) through MAGTF C4I systems, via LAN.

                7 AN/PSQ-9, Team Portable Communications
                  Intelligence System (TPCS), via LAN.

                8 AN/MLQ-36, Mobile Electronic Warfare Support
                  System (MEWSS), via LAN.

                9 AN/GSQ-261, Tactical Remote Sensor System
                  (TRSS), via LAN.

                10 Tactical Reconnaissance Intelligence Exchange
                   System (TRIXS) via the Commander's Tactical
                   Terminal (CTT), or equivalent transceiver.

                11 Tactical Information Broadcast Service (TIBS)
                   via the Multi-mission Advanced Tactical
                   Terminal (MATT), or equivalent transceiver.
     
                12 Intelligence Broadcast Receivers, if deployed.

                13 TADIL-J.

                14 Tactical Combat Operations (TCO), via LAN.

            (c) Communications/Air Command and Control.  TERPES Upgrade shall be interoperable with the following MAGTF C4I systems as a threshold, via the method indicated:

                1 AN/MSC-63A TCC via wireline.

                2 STU-III via wireline.

                3 AN/TYQ-1A, Tactical Air Command Center (TACC),
                  via TADIL-A and/or TADIL-B, and/or IAS.

                4 AN/TYQ-51, Advanced Tactical Air Command                     Central (ATACC) via TADIL-A and/or TADIL-B,
                  and/or IAS.

                5 AN/TYQ-23, Tactical Air Operations
                  Module (TAOM) via wireline, and/or
                  via TADIL-A, and/or wireline.

            (d) Mission Planning Support Systems.  TERPES Upgrade shall be interoperable with the following MAGTF C4I systems as a threshold, via the method indicated:

                1 TEAMS via digital tape.

                2 TAMPS via LAN.
 
            (e) Data Base Support.  The Software Support Activity
(SSA) is the Naval Air Warfare Center, Weapons Division (NAWCWPNS), Point Mugu, California.
  
    c.  Transportation and Basing

        (1) Movement.  The system shall be capable of transport by fixed wing cargo aircraft, internal or external lift by heavy helicopters, rail and sealift.  The TPU will be transportable by individual Marines and capable of loading aboard all types of airlift aircraft including:  C-141, C-130, and CH-53, standard tactical vehicles and sealift.  The TPU will not create additional or special lift requirements.
    
        (2) Training Locations.  One TERPES Upgrade (less shelter) shall be at NMITC for use by TERPES students.

        (3) Main and Forward Operating Bases.  TERPES shall
deploy to and operate at expeditionary airfields and FOB.

    d.  Standardization, Interoperability, and Commonality

        (1) Joint Use.  The EA-6B aircraft are available for joint operations and employment.  Consequently, TERPES must be certified per DoDI 4630.8 and CJCSI 6212.01.

        (2) NATO Cross-servicing.  There is no requirement for
interoperability or integration with NATO, or other allies.

        (3) Interoperability with Other Service, Joint Service, and Allied Systems.  TERPES shall adhere to DoDD 4630.5, DoDI 4630.8, CJCSI 6212.01, DoD Intelligence Information Reference
Model, adhere to applicable USSID's on ELINT processing and reporting, and provide compatibility with the developing Global Command and Control System (GCCS).

        (4) Data/Government Open System Interconnection Profile (GOSIP).  TERPES shall conform to all data protocols and standards supported by the Tactical Data Network program and Technical Architecture Framework for Information Management (TAFIM).  Interfaces shall use the applicable technical and procedural standards, including GOSIP, as applic able.

        (5) Energy Standardization and Efficiency Needs.  Special
electrical power and fuel needs are not desired nor acceptable.

    e.  Mapping, Charting, and Geodesy Support.  The system shall use Defense Mapping Agency (DMA) standard products to support mission accomplishment.

    f.  Environmental Support.  No astrogeophysical, oceano-
graphic, or weather support is necessary.

7.  Force Structure.  Distribution of the TERPES Upgrade will be on a one-for-one basis for each AN/TSQ-90D in each VMAQ.  


    a.  The requirement for the TERPES Upgrade is five systems.

         (1) I  MEF:   0

         (2) II MEF:   4

         (3) III MEF:  O

         (4) Others:   1 (supporting establishment for training)

    b.  FMF.  Distribution and quantities of the TERPES Upgrade
shall be on a one-for-one replacement for each existing system.

    c.  Supporting Establishment.  One TERPES Upgrade system without shelter will be provided to the NMITC.

    d.  Spares.  No spare systems are necessary.  

8.  Schedule Considerations.  This requirement is designed as an evolutionary requirement.  This ORD forms the baseline to maintain TERPES from FY96 through FY10, to keep pace with the
EA-6B, threat, and technology.

    a.  IOC

        (1) Actions Constituting IOC.  Delivery of one TERPES
to a VMAQ and to the NMITC.

        (2) Operational Capability Necessary to Declare IOC.  
Same as above.

        (3) Level of Performance Necessary to Declare IOC.  
Acceptance by COMMARFORLANT or COMMARFORPAC.

        (4) Number of Operational Systems for IOC.  One.

        (5) Number of Operational and Support Personnel for IOC.
Not applicable.

        (6) Number of Facilities for IOC.  Not applicable.

        (7) Number of Support Elements for IOC.  Not applicable.

        (8) Time Frame

            (a) Objective Time for IOC.  FY98.

            (b) Impact if Objective Not Met.  The VMAQ will not be capable of fulfilling its mission.  TERPES Upgrade will not be able to adequately support ACE mission planning, EA-6B technical tasks, nor MAGTF ELINT information requirements.


            (c) Window of Acceptability  

    b.  FOC

        (1) Actions Constituting FOC.  Delivery of all TERPES
to VMAQ.

        (2) Operational Capability Necessary to Declare FOC.
Same as above.

        (3) Level of Performance Necessary to Declare FOC.  Same
as IOC.

        (4) Number of Operational Systems for FOC.  Five.

        (5) Number of Operational and Support Personnel for FOC.
Not applicable.

        (6) Number of Facilities for FOC.  Not applicable.

        (7) Number of Support Elements for FOC.  Not applicable.

        (8) Time Frame

            (a) Objective Time for FOC.  18 months after IOC.  

            (b) Impact if Objective Not Met.  VMAQ will not be
mission capable.

            (c) Window of Acceptability.  Same as for IOC.


                                                    Annex A


Table 1  Information Technology Standards.

                 Information Standards

  Joint Pub 6-04 United States Message Text Formatting (USMTF)

    Final Draft MIL-STD-2525 Common Warfighting Symbology

Table 2  AUTODIN and Related Protocols.

    TITLE

      REFERENCE

  PURPOSE/CONNECTION

  JANAP 128

JANAP 128 "AUTODIN Operating Procedures"

Provides message format, addressing and routing instructions for AUTODIN messages

  Mode I

MIL-STD-188-166-1, "Interoperability Standards for Information and Record Traffic Exchange -
Mode I"

Provides synchronous simultaneous data transfer for AUTODIN

  Mode II

MIL-STD-188-172, "Interoperability Standards for Information and Record Traffic Exchange -
Mode II"

Provides asynchronous simultaneous data transfer for AUTODIN

  Mode VI

MIL-STD-174, "Interoperability Standards for Information and Record Traffic Exchange -
Mode VI"

Provides Mode I over satellite links

Table 3  Interim Data Communications Protocol Standards.

    TITLE

    REFERENCE

 PURPOSE/CONNECTION

VINES

Banyan Documentation

Provides data communications protocols and network management for the Banyan LAN

StreetTalk

Banyan Documentation

Provides directory assistance for addressing and naming on the Banyan LAN

Defense  Message System   (DMS)

MIL-STD-2045-17502 ACP 123

Provides individual and organizational messaging support

Message  Security Protocol (MSP)

Draft MIL-STD-2045-48500

Provides security support for DMS and other messaging systems.  This is part of the Secure Data Network System (SDNS)

Simple Network  Management  
Protocol (SNMP)
RFCs 1155, 1156, 1157

Draft MIL-STD-2045-17507

Provides network management support to the DoD protocols

Directory  
Services
CCITT X.500

CCITT X.500
ISO/IEC 9594

Provides naming and addressing support

Domain Name
System (DNS)
RFC 1034, 1035

Draft MIL-STD-2045-17507

Provides addressing and naming for DoD protocols

Banyan Mail

Banyan Documentation

Provides the E-mail application protocol for the Banyan system
 

 Table 3 - Cont.  Interim Data Communications Protocol Standards.

    TITLE

  REFERENCE

     PURPOSE/CONNECTION

 Tactical
 Message
 Handler

MAGTF C4I TIDP Volume V

Message protocol for Marine Corps Tactical Systems

Simple Mail
Transfer Protocol (SMTP) RFCs 821, 822

Draft MIL-STD-2045-17503 Message

Provides protoocol for DoD Internet protocols

File Transfer Protocol (FTP)
RFC 959

Draft MIL-STD-2045-17504

File transfer protocol for DoD Internet protocols

Telnet
RFCs 854, 855

Draft MIL-STD-2045-17506

Provides a remote login protocol for DoD Internet protocols

User Datagram Protocol (UDP) RFC 768

Draft MIL-STD-2045-14502 Part 1

Provides a connectionless transport layer protocol for DoD Internet protocols.  Used primarily with DNS.

TP-TCP
RFC 1006

ISO Transport Service on Top of the TCP Ver.3

Provides for DMS operation over the TCP/IP network

Transmission Control Protocol (TCP) RFC 793

Draft MIL-STD-2045-14502 Part 1

Provides a connection-oriented transport layer protocol

Border Gateway Protocol 3 (BGP-3)

RFC 1267
RFC 1268

Provides routing protocol support between autonomous networks

 










 Table 3 - Cont.  Interim Data Communications Protocol Standards.

    TITLE

    REFERENCE

 PURPOSE/CONNECTION

Internet Protocol (IP)
RFCs 791, 792, 919, 922, 950

Draft MIL-STD-2045-14502 Part 1

Provides a connectionless network protocol

MAGTF C4I (Switched) Protocol

MAGTF C4I TIDP, Vol V

Provides packet (network) layer connection to the switched backbone

MAGTF C4I High-level Data Link Control (HDLC)

MAGTF C4I TIDP, Vol V

Provides the data link layer for the MAGTF C4I switched protocol

X.25 Wide Area Network
CCITT X.25

Draft MIL-STD-2045-14502 Part 3

Provides link and packet (network) layer connections to the switched backbone

Logical Link Control (LLC)
ISO 8802-2

Draft MIL-STD-2045- 14502 Part 4

Provides the logical link control for the LAN protocols

CSMA/CD
ISO 8802-3

Draft MIL-STD-2045- 14502 Part 5

Provides CSMA/CD LAN protocols

Point-to-Point link

Draft MIL-STD-2045-14502 Part 2

Provides point-to-point link layer protocol

Point to Point Protocol (PPP)
RFCs 1331, 1332

Draft MIL-STD-2045-13500

Provides a router with
point to point protocol for use with IP

SCR Broadcast Radio

MIL-STD-188-220

Provides a broadcast radio protocol for digital message transfer devices




Table 4   Data Communications GOSIP Protocol Standards.

    TITLE

   REFERENCE

     PURPOSE/CONNECTION

Directory Services CCITT X.500

CCITT X.500
ISO/IEC 9594

Provides naming and addressing support to the GOSIP protocols

Message Security Protocol (MSP)

Draft MIL-STD-2045-48500

Provides security support to DMS and other messaging systems.  This is part of the Secure Data Network System (SDNS).  The complete security system for GOSIP is still being developed

Common Management Information Protocol (CMIP)

ISO 9596
FIPS Pub 179

Provides network management support

Defense Message System (DMS)

MIL-STD-2045-17502
ACP 123

Provides individual and organizational messaging support

File Transfer, Access, and Management (FTAM)
(ISO 8571-4)

FIPS 146-1

Provides file transfer support

Virtual Terminal (VT)
(ISO 9041)

FIPS 146-1

Provides interactive terminal support

Tactical Message Handler

TBD

To replace MAGTF C4I application protocols for tactical systems

Table 4 - Cont.  Data Communications GOSIP Protocol Standards.

     TITLE

  REFERENCE

     PURPOSE/CONNECTION

Association Control Service Element/Remote
Operations Service Element/Reliable Transfer Service Element (ACSE/ROSE/RTSE) ISO 8650/ISO 9072/ISO 9066

MIL-STD-2045-17501
FIPS 146-1

Provide common application support for DMS and other application services

Connection-Oriented Presentation Protocol (COPP) ISO 8823

FIPS 146-1

Provides presentation service support to connection oriented GOSIP protocols

Connection-Oriented Session Protocol (COSP) ISO 8327

FIPS 146-1

Provides session services to support connection-oriented GOSIP protocols

Connection-Oriented Transport Protocol Class 4 (COTP)
ISO 8073

FIPS 146-1

Provides transport services to support connection-oriented GOSIP protocols

Connectionless Transport Protocol (CLTP)
ISO 8473

FIPS 146-1

Provides connectionless transport service to GOSIP protocols. There is no specified application for this protocol at this time

Connectionless Network Protocol (CLNP)
ISO 8473

FIPS 146-1

Provides connectionless network services.  Provides the internet capability across different systems.

Table 4 - Cont. Data Communications GOSIP Protocol Standards.

    TITLE

   REFERENCE

     PURPOSE/CONNECTION

End System-Intermediate System (ES-IS)
ISO 9542

FIPS 146-1

Provides limited routing services to CLNP.

Subnetwork Dependent Convergent Protocol (SNDCP) ISO 8878

FIPS 146-1

Converges the CLNP services with the X.25 (1980) services

X.25 Packet Level Protocol (PLP)

FIPS 146-1

Provides X.25 packet switched support

Link Access Procedures Balanced (LAPB) ISO 7776

FIPS 146-1

Provides data link protocol support to X.25 PLP

Logical Link Control (LLC)
ISO 8802-2

FIPS 146-1

Provides link control from the media access control (MAC) protocols, (CSMA/CD and token ring), to the network layer

Carrier Sense Multiple Access with Collision Detection (CSMA/CD)
ISO 8802-3

FIPS 146-1

Provides CSMA/CD LAN support

Token Ring Protocol
ISO 8802-5

FIPS 146-1

Provides token ring LAN support

Table 5.  Tactical Digital Information Link Description

     TITLE

    REFERENCE

  PURPOSE/CONNECTION

 TADIL A

MIL-STD-188-203-1
Joint Pub 3-56.23
Joint Pub 6-01.1

Provides a means for exchanging real-time control and air defense digital data between Services/Agencies Tactical Data Systems.

 TADIL B

MIL-STD-188-212
Joint Pub 3-56.23
Joint Pub 6-01.1

Provides a means for exchanging real-time air control and air defense digital data between Services/Agencies Tactical Data systems.

 TADIL J

JTIDS Class II System Specs; JTIDS TIDP-TE

Provides a means for the exchange of real-time digital data among airborne, surface, and ground JTIDS equipped platforms.

Table 6.  Acronym List.

ACP Allied Communications Publication
ACSE Association Control Service Element
AUTODIN Automated digital Network

BGP-3 Border Gateway Protocol-3

C4I Command, Control, Communications, Computers,
               and Intelligence
CCITT Consultative Committee on International Telephone
               and Telegraph
CD Collision Detection
CLNP Connectionless Network Protocol
CLTP Connectionless Transport Protocol
CMIP Common Management Information Protocol
COPP Connection-Oriented Presentation Protocol
COSP Connection-Oriented Session Protocol
COTP Connection-Oriented Transport Protocol
CSMA Carrier Sense Multiple Access

DMS Defense Message System
DNS Domain Name System
DoD            Department of Defense

ES End System

FIPS Federal Information Processing System
FTAM File Transfer, Access, and Management
FTP File Transfer Protocol

GOSIP Government Open Systems Interconnection Profile

HDLC High-Level Data Link Control

IP Internet Protocol
IS Intermediate System
ISO International Standards Organization

JANAP Joint Army/Navy/Air Force Publication


Table 6. - Cont.  Acronym List.

LAN Local Area Network
LAPB Link Access Procedures Balanced
LLC Logical Link Control

MAGTF Marine Air-Ground Task Force
MAC Media Access Control
MIL Military
MSP Message Security Protocol

ORD Operational Requirements Document

PLP Packet Level Protocol
PPP Point-To-Point Protocol

PUB Publication

RFC Request for Comments
ROSE Remote Operations Service Element
RTSE Reliable Transfer Service Element

SCR Single Channel Radio
SDNS Secure Data Network System
SMTP Simple Mail Transfer Protocol
SNDCP Subnetwork Dependent Convergence Protocol
SNMP Simple Network Management protocol
STD Standard

TADIL Tactical Digital Information Link
TCP Transmission Control Protocol
TIDP Technical Interface Design Plan
TP Transport protocol

UDP User Datagram Protocol
USMTF United States Message Test Formatting

VT Virtual Terminal