24 May 95
23 Sep 96
From: Commanding General, Marine Corps Combat Development
Command, 3300 Russell Road, Quantico, Virginia
22134-5021 (C 442)
Subj: OPERATIONAL REQUIREMENTS DOCUMENT (ORD) FOR THE
INTELLIGENCE ANALYSIS SYSTEM (IAS) (NO. INT 250.1);
Ref: (a) DoD Regulation 5000.2-R
1. Purpose. To transmit pen changes to the basic Operational Requirements Document (ORD). Per the reference, the following changes to the ORD for the Intelligence Analysis System (IAS) (NO. INT 250.1) are approved.
a. Replace paragraph 4c(2)(b)1 with the following: "The MEF IAS system will be employed in two shelters mounted on two High Mobility Multi-Wheeled Vehicles (HMMWV). An additional HMMWV and two HMMWV trailers are required for transporting ancilliary MEF IAS equipment. The maximum MEF IAS cargo weight for each HMMWV, including the shelter, will be no more than 1859 kilograms (Kg) (4,098 lb). The total maximum MEF IAS cargo weight includes 272 Kg (600 lb) for driver and passenger. The maximum cargo weight for each trailer shall be no more than 680 Kg (1,500 lb). The total weight of MEF IAS shall not exceed 5,623 Kg (12,396 lb)."
b. Replace paragraph 8a(1) with the following: "MEF IAS: 1st Qtr, FY98."
c. Replace paragraph 8h(1) and 8h(1)(a) with the following:
"1. Threshold Time for IOC
(a) MEF IAS: 3rd Qtr, FY98."
3. Filing Instructions. 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, Computers, and Intelligence Sponsor (C 442), Requirements Division, MCCDC, DSN 278-6196.
R. J. ANTONICH
Distribution: See attached
OPERATIONAL REQUIREMENTS DOCUMENT (ORD)
INTELLIGENCE ANALYSIS SYSTEM (NO. INT 250.1)
1. General Description
a. Mission Area. The AN/MYQ-7, Intelligence Analysis System (IAS) falls under Mission Areas 12 (Intelligence). It addresses the deficiencies caused by the inability to adequately direct, manage, process, and disseminate combat information and intelligence to the Marine Air Ground Task Force (MAGTF).
b. System Type. The IAS is a segment of the Marine Air-Ground Intelligence System (MAGIS). The IAS will provide
semi-automation of intelligence functions and all-source
intelligence to each section and unit in the Fleet Marine Force and throughout the MAGTF. The extent of support functions provided by the IAS and the size, capability and mobility of the equipment will correspond to the unit at which the system is employed and mission requirements.
c. Operational Concept. 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 and Fleet Marine Force Manual 3-21.
IAS will be used by all intelligence sections in the MAGTF and its subordinate elements, down to the battalion and squadron level, and by specialized intelligence units. It may also be used to support the Commander, Joint Task Force (CJTF) or Marine Component Commander, if the Marine Expeditionary Force (MEF) Commanding General is assigned those roles.
(1) The IAS consists of three tiers: MEF IAS, IAS Suites, and the IAS Workstation. Each IAS tier includes computer workstation(s), peripherals, data storage devices, software applications, cables, and communications interface hardware and software. The IAS will be expeditionary and deploy with the unit to which assigned. All equipment will be employed by intelligence sections throughout the world in garrison, field, and shipboard operations and exercises, to support the MAGTF.
(2) Composition and size of each tier varies. The MEF headquarters requires a mobile, shelter contained system with communications interface capabilities. The MEF IAS will fulfill this role. The headquarters of Marine Forces (MarFor), the Marine Expeditionary Force (MEF), Marine Divisions, Marine Air Wings (MAW), Force Service Support Groups (FSSG), Regiments, Marine Aircraft Groups (MAG), and Marine Expeditionary Units (MEU), require a transportable system with communications
interface capabilities. The IAS Suite will fulfill this role. Marine battalions and squadrons, and selected units, require a
portable system, with communications interface. The IAS Workstation will fulfill this role.
(3) Garrison, shipboard, and battlefield missions
include formulation of the commander's Essential Elements of Information and Other Intelligence Requirements, contingency planning, management of MAGTF collection assets, all-source intelligence analysis, briefing support, intelligence product fusion, production, reporting, dissemination, and training.
(4) The IAS will accomplish its missions through performance of the following major functions.
(a) Provide for rapid receipt, storage and retrieval of all-source intelligence data.
(b) Facilitate display, processing, reporting, and dissemination of intelligence products and information throughout the MAGTF.
(c) Provide collection management applications to
task and monitor MAGTF, theater, and national assets.
(d) Provide word processing, mapping, and graphics software applications, in accordance with applicable Marine Corps standards, to prepare intelligence products for the MAGTF.
(5) All tiers of IAS will deploy for use in field environments for the period of time necessary to accomplish the mission (see paragraphs 4b(2) and 4c(1)(c)). The IAS will be employed in the unit's command and control facility (e.g., Combat Operations Center, Combat Intelligence Center). In garrison, the system will support the intelligence planning cycle and provide contingency planning, exercise support, and training.
d. Support Concept. Logistic support will be provided for IAS hardware through the IAS Integrated Logistic Support (ILS) administered by Marine Corps Systems Command. IAS unique equipment will be supported under the current Intelligence Analysis Center Critical Low Density Support Concept.
e. Mission Need Statement (MNS) Summary. The requirement for the IAS was validated by the Required Operational Capability (INT 250.1) published 29 May 1990.
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.
a. Threat To Be Countered. The IAS is an intelligence information management system, to facilitate intelligence fusion, rapid reporting, and product integration. It is not designed to overcome a distinct specific threat.
b. Present and Projected Threat Against the System. Potential enemy threats confronting the FMF in the near-to-long range periods are outlined in the Marine Corps Master Plan 1994-2004 (MCMP). The primary threat to the IAS 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 provides adversaries with greater standoff ranges and accuracy to successfully engage rear area command and control facilities. Threats also exist from nuclear and non-nuclear electromagnetic pulse weapons and Radio Frequency (RF) weapons designed to produce physical damage to internal electronic components. These threats are well documented in various Defense Intelligence Agency classified technical publications and studies, such as: DST-1740S-385-YR, DST-2700S-497-YR-VOL 1, -VOL 2, and -VOL 2-SUP 1, DST-1730H-077-YR, and DST-1730H-077-YR. Marine Corps Intelligence Activity letter 3880 MCIA12, dated 4 November 1993, also addresses current and future threats which may be encountered by the IAS.
3. Shortcomings of Existing Systems. FMF intelligence
collection capabilities have increased dramatically during recent years. There has also been a parallel increase in other service and national collection capabilities. Intelligence units and organizations without semi-automated capabilities are unable to rapidly analyze, produce, and disseminate all-source intelligence. The Marine Corps capability to rapidly process, analyze, and disseminate information has not kept pace with these developments. Current technology will allow MAGTF intelligence sections to reduce processing times and produce detailed, timely, and accurate fused all-source intelligence for the commander.
The IAS is a mission essential capability required to provide timely handling of large quantities of intelligence data.
4. Capabilities Required
a. Subsystems. The major subsystems of the IAS consist of the MEF IAS, the IAS Suites, and the IAS Workstation. The
following tables demonstrate the threshold and objective numbers of computer workstation(s) and peripherals for each IAS tier.
IAS COMPUTER WORKSTATIONS
IAS PERIPHERALS BY TIER
b. System Performance
(a) General. IAS is the center-point of MAGIS and must be capable of communication and data exchange at both the GENSER and SCI levels via MAGTF communications. The IAS shall be an integrated data system which provides support to the MAGTF through production of timely intelligence. Composition and size will vary with each mission, but the IAS essentially consists of data storage device(s), workstations, and input/output devices.
(b) Parameters. The following parameters must be provided unless otherwise indicated.
1 The computer workstations of all IAS tiers will be capable of running all IAS software applications.
2 The loss of any client workstation will not cause loss of the system.
3 All workstations will support:
a Keyboard input.
b Transfer and storage of electronic data.
c Information display.
d Display of classified information.
4 Send, receive, store, and retrieve messages.
5 Send, receive, store, retrieve information.
6 Provide an opportunity to automatically update files/data bases without keyboard input.
7 Produce and display graphics.
8 Display and print military symbols.
9 Display images of maps and overlays.
10 Display imagery data.
11 Provide a semi-automated collection management software application for tasking, control, and management of MAGTF collection assets, and for integration and tasking of joint, combined, theater, national networks, and collection efforts.
12 Display softcopy images, produce hard copy images, and provide imagery enhancement capabilities through incorporation of a Secondary Imagery Dissemination System (SIDS) capability which will allow the IAS to host a MAGTF SIDS network. The intra-MAGTF SIDS will utilize the National Imagery Transmission Format Standard (NITFS) for transmission.
13 Store intelligence information interoperable with the Military Intelligence Integrated Data System/Integrated Data Base (MIIDS/IDB).
14 Allow multiple, simultaneous access to all software applications by all workstations in use.
15 System set up and tear down time is based on all tasks needed to prepare the IAS for operations, relocation, movement, and/or termination of operations. Set up includes provision of power, environmental control, cable hook-up, equipment turn-on, and any routine 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. Set up and tear down is also dependent on crew size and availability. Parameters are illustrated below.
16 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.
(c) IAS Workstation. The workstation will be used primarily to disseminate intelligence information and products.
The following pertains only to the IAS Workstation.
1 Consists of a single workstation with associated printer, cables and associated peripherals.
2 The workstation requires no Special Compartmented Information (SCI) level functions.
3 The workstation requires no collection management functions.
(d) Modifications. This document will be periodically reviewed to ensure currency with the requirements of the FMF. New or modified changes, needs, and requirements may be identified from time to time and are encouraged. The system software applications may evolve prior to and after Full Operational Capability (FOC) to meet requirements identified by the FMF and maintain state of the art capabilities. A continuing evolutionary acquisition strategy through IAS MOD shall be pursued to preserve leading edge technology.
(2) Mission Scenarios. The system will operate consistently in peacetime, garrison, field, training or wartime (non-battle-field) scenarios. The system will operate in all combat and environmental conditions including: smoke, dust, rain, fog, arctic, and desert environs (see paragraph 4d(3)(a)). There may be variations in shipboard and battlefield operations.
(a) The following mission profiles apply to all tiers of the IAS.
Mission Mode General Shipboard Battlefield
Operations Operations Operations
Contingency Planning 65% 30% 5%
Intelligence Briefing 25% 60% 30%
Intelligence Fusion -- -- 60%
Training 10% 10% 5%
Storage and retrieval 20% 25% 50%
of intelligence and
Dissemination and 30% 25% 25%
display of intelligence
Collection management 15% 25% 15%
Preparation of 35% 25% 10%
Storage and retrieval 15% 25% 25%
of intelligence and
Dissemination and 50% 35% 50%
display of intelligence
Mission Mode General Shipboard Battlefield
Operations Operations Operations
Preparation of 35% 30% 25%
Collection Management -- 10% --
Storage and retrieval 20% 40% 40%
of intelligence and
Dissemination and 30% 25% 25%
Collection management 20% 30% 25%
Preparation of 30% -- 10%
Transmission/receipt -- -- 60%
Storage and retrieval -- -- 5%
of intelligence and
Dissemination and -- -- 15%
display of intelligence
Collection management -- -- 5%
Word Processing -- -- 15%
(3) System Support. The system may be required to
provide support to the MAGTF on a 24 hour basis, dependent upon the tactical situation and mission.
(4) Future Capabilities. The following are objective requirement capabilities, identified for enhancements and
(a) Display three dimensional terrain profiles from digitized map and/or imagery data.
(b) On screen rotation of three dimensional terrain profiles from digitized map and/or imagery data.
(c) Receive input from digital sources to include: optical storage, magnetic storage, and Optical Character Reader (OCR) devices.
(d) Incorporate a Multi-Level Security (MLS) system for all echelons of classified data handling and storage.
(e) Allow removal of MEF IAS components to locations remoted up to 500 meters from the shelters, using fiber optic cable or wire lines.
(f) Achieve full interoperability with the Defense Message System (DMS).
(g) Parse incoming message traffic. Parse is the capability to automatically extract specific fields of information from incoming messages and update data files.
c. Logistics and Readiness. The following measures apply for wartime and peacetime.
(1) Measures. Peacetime and wartime are identical. The reliability of IAS depend on the Mission Duration (MD) and Mean Time Between Operational Mission Failure (MTBOMF).
(a) Mission Duration (MD). The MD is 48 hours (two days) for all tiers of IAS.
(b) Mean Time Between Operational Mission Failure (MTBOMF). The MTBOMF threshold is 300 hours; objective-500 hours. An operational mission failure occurs when the system cannot perform any mission essential functions.
(c) 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 the transport vehicles of the MEF IAS. (See paragraph 5).
(d) Maintenance and Repair. The IAS will be maintained by the using unit. Second echelon and higher repairs
will be conducted by maintenance personnel in the communications-electronics elements of the Division, Wing, and FSSG.
1 The Mean Time To Repair (MTTR) is one hour for unscheduled maintenance at the organizational level. Unscheduled Intermediate Level Maintenance (ILM) MTTR is two hours.
2 The threshold Maximum Time to Repair (MaxTTR) Organizational Level Maintenance (OLM) unscheduled maintenance is one hour at 90 percentile; and the MaxTTR for unscheduled ILM is two hours at 90 percentile.
(f) Built-in Test (BIT)/System Diagnostics. BIT will be provided to detect 90% of malfunctions, within each tier of IAS. Each indication of malfunction shall have at least a 90% level of confidence that a malfunction has occurred.
(g) Storage Availability. The IAS may be stored for transport or staging prior to transport for lengthy periods of time. The IAS must operate with 90 percent availability, after 180 days of storage at temperatures no greater than plus 35 degrees celsius (90 degrees farenheit) or lower than 0 degrees celsius (32 degrees farenheit). After a period of non-operation, transportation, or storage, the system will require a 30 minute warm-up period, after which the system shall meet full performance specifications.
(2) Combat Support Requirements
(a) Battle Damage Repair Capability. None required.
(b) Mobility Requirements. The mobility and portability requirements of the IAS vary by tier. The system should be as lightweight and compact as technology will allow.
1 The MEF IAS equipment shall be placed in two shelters mounted on two High Mobility Multi-Wheeled Vehicles (HMMWV) and include two HMMWV trailers, for transport of all equipment. The maximum MEF IAS cargo weight for each HMMWV, including the shelter, shall be no more than 1859 kilograms (Kg) (4098 pounds). The total maximum MEF IAS cargo weight includes 272 Kg (600 pounds) for a driver and passenger. The maximum cargo weight for each trailer shall be no more than 680 Kg (1500 pounds). The total weight of the MEF IAS shall not exceed 5623 Kg (12396 pounds).
2 The IAS Suite is a team transportable system which requires no more than two Marines to transport each module or component from the transport vehicle to the operation site.
The IAS Suite shall weigh no more than 275 kg (606 pounds).
3 The IAS Workstation is a portable system designed for transport by a single Marine. Each component shall weigh no more than 15 Kg (33 pounds).
(c) Expected Maintenance Manpower and Skill Levels.
The IAS will cause an increase to the skill levels and numbers of maintenance hours needed within the Marine Corps to perform necessary maintenance. Formal training for IAS maintainers will be established and conducted at the Marine Corps Communications and Electronics School (MCCES), 29 Palms, California. Training for the computer workstation will be conducted in conjunction with the courses for the Marine Common Hardware Suite (MCHS).
(d) Surge/Mobilization Objectives and Capabilities. The system will not be planned or programmed for surge, mobilization, or reconstitution.
(e) Maintenance Tool Requirement. 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) and supplied through IIP.
d. Critical System Characteristics
(1) Shielding. Shielding from the effects of RF and high power microwave effects and weapons, directed energy weapons and high energy electromagnetic pulse is an objective.
(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 IAS must be capable of undergoing the standard NBC decontamination process, when contained within transit cases, or, for the MEF IAS, within its shelter(s).
(b) Wartime Reserve Modes. Not applicable.
(3) Natural Environmental Factors
(a) Climatic. The IAS must be capable of operations in all climatic conditions and geographic locations in which a MAGTF can be expected to operate, and during times of limited visibility, including rain, smoke, fog, darkness. The MEF IAS will require an environmental control capability within the shelters, whenever used. The system must be protected from rain, sand, salt, and wind by tentage or other appropriate cover.
(b) Terrain. The system will operate in all terrain types in which a MAGTF can be expected to operate.
(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.
(b) Frequency Spectrum Assignment. The primary means of communications between MAGIS systems and IAS systems at different echelons/units within the MAGTF is electronic digital data communication via the MAGTF C4I architecture. As a threshold, the IAS shall be capable of connection with voice or data communications within the HF/VHF/UHF frequency spectrum used within the MAGTF C4I architecture. Voice and/or data communications within the super high (SHF) and extra high (EHF) frequency spectrum is an objective.
1 When part of an amphibious task force, IAS connectivity to joint, theater, and national intelligence organizations will be via doctrinal ship to shore radio nets.
2 Alternative means of information transfer consist of delivery of magnetic media via couriers and/or voice communications.
(5) Safety Parameters. The system shall be safe and comply with best commercial safety guidelines for commuications and electronic equipment. Integrity for electromagnetic interference, grounding and bonding, and electrostatic discharge will be maintained in the shelterized MEF IAS. Design and operation must not create any situations where physical injury could occur.
(6) 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. The system must be certified for
handling SCI (see paragraph 4b(1)c2).
(c) Physical and Operational. The IAS will possess a security system to prevent unauthorized disclosure of classified information. Moreover, the MEF IAS will possess the means to physically destroy and/or disable all COMSEC equipment and purge all systems of classified information within 30 minutes.
(7) Power Source. The IAS must 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 controlled shutdown of the system.
(a) The MEF IAS primary power source will be externally provided USMC MEP generators and/or standard,
commercial power (110 VAC, 60Hz, single phase), plus or
minus 10% tolerance.
(b) The primary power source for IAS Suites and Workstations shall be provided USMC MEP generators or standard, commercial power (110 VAC, 60Hz, single phase), plus or minus 10% tolerance, and/or 24/28 volt direct current from vehicles, plus or minus 10% tolerance (see paragraph 4d(7)).
(c) When operating independently, all workstations will have power backup to prevent loss of data in the event of
unplanned power outages.
5. Integrated Logistics Support (ILS). The MEF IAS will be
designated as Critical Low Density (CLD). The IAS Suite and IAS workstations shall conform with systems available from the MCHS listing of computers to ensure compatibility and supportability.
a. Maintenance Planning. The IAS should not change organizational, intermediate, or depot maintenance concepts.
Initial Issue Provisioning (IIP) of maintenance items shall be accomplished through the Total Package Fielding concept.
All initial maintenance items shall be included as part of the IAS initial fielding effort. Maintenance sustainment support may be augmented through contractor supplied parts, if needed, at the intermediate or depot levels.
b. Planning Approach for Contract Versus Organic Repair.
Depot level maintenance may require contractor support. Contract maintenance is not desirable, but may be identified as part of a warranty agreement when support equipment will not adapt to the tactical situation or when combat readiness is below established levels. Maintenance and operator manuals for any off-the-shelf equipments will be written to "best commercial practice". Commercial manuals will be supplemented as required to ensure acceptability.
c. Support Equipment
(1) Organizational Support Objective. Organizational maintenance consists of inspecting, removing, and replacing
faulty parts through the use of BIT and trouble-shooting flow charts. Preventive and corrective maintenance, cleaning, servicing, lubricating, and adjusting are functions of organizational maintenance. The organizational level support objective is replacement of parts by the operator/system administrator using spares and BIT, without the use of separate test equipment, for system start-up.
(2) Intermediate Support Objective. Intermediate maintenance is performed both by BIT and through diagnostics in a unit work center or shop and consists of repairing or replacing damaged or unserviceable parts and components, fault isolation,
Shop Replaceable Units, removal/replacement of faulty assemblies, subassemblies, and verifying proper equipment operation.
(3) Depot Support Objective. Depot maintenance is defined as that which needs complete rebuild or overhaul or else that maintenance which cannot be performed at the intermediate level. Depot level repair may require contractor support.
d. Human Systems Integration. The system must be
user-friendly, easy to set-up, operate, use, tear-down, and maintain. Initial training for operators and maintainers will be provided prior to delivery and acceptance at the using units. After acceptance, training will be conducted via a combination of formal school and OJT training further supported through use of manuals and training aids.
(1) Operational and Maintenance Training Concept
1 Operator Training. Formal Military Occupational Specialty (MOS) training for Occupation Field
(OF) 02 IAS operators will take place at the United States Navy/Marine Intelligence Training Center (NMITC), Dam Neck, Virginia. Training will include all steps needed to operate
the IAS. Operators will be taught system description, design characteristics and capabilities, operating features, hardware configurations, set-up, tear-down, trouble shooting, and techniques for malfunction isolation.
2 System Administration. At least one IAS operator per using unit will receive additional training as a System Administrator (SA). Training will include control and management of the operating system, on-line data bases, system performance, network set-up, security management, and system and network troubleshooting. Additionally, SA will be trained to install, maintain, and manage various application programs.
3 Maintenance Training. Routine training provided to microcomputer maintenance technicians within OF 28 for other inventory Automated Data Processing (ADP) and MCHS equipment will support maintenance of the IAS workstations.
The repair process may require additional personnel and formal training other than that currently provided at the MCCES.
(b) Training Devices. None required during IOC. Electronic equipment may be required at a later date, if requested by the MEF electronic maintenance support elements.
(c) Embedded Training. None required, but is an objective.
(d) Interactive Courseware. None required, but is
(a) Manpower. No additional personnel are required.
(b) Personnel. Marines assigned to FMF intelligence sections will employ all IAS equipment.
(c) Training. OF 02 Marines currently receive initial, primary MOS, skills training at the NMITC, Dam Neck, Virginia. Formal training for operators of IAS may increase after IOC of the MEF IAS or IAS Suites. If so, the training will be added to the course curriculum. Skill level training shall conform to the Individual Training Standards (ITS) for MOS 02 and 28 for both formal and OJT.
(3) Manpower and Training Methodologies. To provide
in-depth and well trained operators and analysts, formal training will be augmented through utilization of computer aided instruction, help menus, and hands on training.
(4) Human Engineering. The system must be easy to
set-up, operate, use, tear-down, and maintain.
(a) All components must be easy to install, operate, trouble-shoot, erect, and de-install. Cables must be labeled and easy to connect and disconnect.
(b) Controls and displays shall be easy to locate
and visible under all light conditions, with adjustable light intensity. Screen and control lighting shall not interfere
with use of night vision goggles.
(c) No components of any subsystem should
restrict operator activity or present an unsafe situation.
e. Computer Resources
(a) Language. The system shall conform to applicable standards to ensure interoperability with appropriate government agencies and other services. The software must be developed in the ADA language IAW MIL-STD-1815A, unless exempted by waiver, via appropriate service and DoD directives. If exempted, software may integrate Non-Developmental Items (NDIs), Government Furnished Information, and Commercial Off-The-Shelf (COTS) software applications and operating systems not written in ADA programming language.
(b) Computer. The computer workstations shall conform with systems available from the MCHS to ensure interoperability, compatibility, and supportability with the MAGTF C4I architecture and its systems.
(c) Data Storage. The following table provides the
minimum computer memory and storage capacity for IAS.
64 MB 32 MB
(d) Architecture. The system architecture must allow future capabilities, improvements and system growth to provide continued interoperability with emerging and planned systems.
(e) Interoperability. IAS 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.
1 The IAS may be employed aboard ship, within
the Joint Intelligence Center, or other locales, as appropriate. The MEF IAS and IAS Suites shall host Joint Defense Intelligence Support System (JDISS) communications interface software, to allow access to DODIIS DSNET 3, Joint Worldwide Intelligence Communications System (JWICS) for receipt of intelligence information from national and theater level systems.
2 IAS shall provide intelligence updates for mission planning devices to include: the Tactical Aircraft Mission Planning System (TAMPS), Map Operation Maintenance Station (MOMS), and Tactical EA-6B Mission Planning System (TEAMS). IAS shall interface with the Navy Tactical Command System-Afloat (NTCS-A).
3 IAS will be capable of exchanging information,
through passing files and information with the following MAGTF C4I systems, via the method indicated. Files and information are defined as USMTF, data base, graphics, map overlays, and word processing files. IAS will be capable of exchanging information with the following C4I systems:
a All other IAS systems, via data link.
b AN/TSQ-130(V), Technical Control and Analysis Center (TCAC) via data link.
c AN/TSQ-90D,Tactical Electronic Reconnaissance Processing and Evaluation System (TERPES), via data link.
d AN/TYQ-1A, Tactical Air Command Central (TACC), via data link.
e Tactical Command Operations (TCO), via data link.
f The National Intelligence Support Team (NIST) Critical Source Facility (CSF) via LAN/WAN.
4 As an objective, IAS will operate with:
a Joint Services Imagery Processing System (JSIPS), via data link.
b AN/TYQ-51, Advanced Tactical Air Command and Control (ATACC), via data link.
c AN/PSQ-9, Team Portable Communications Intelligence System (TPCS), via data link.
d AN/MLQ-36, Mobile Electronic Warfare Support System (MEWSS), via data link.
e The U.S. Army All Source Analysis System (ASAS) through Marine Corps communications systems, to the maximum extent possible, via data link.
f AN/GSQ-261, Tactical Remote Sensor System (TRSS), via data link.
g Naval Intelligence Processing System (NIPS), via data link.
h The U.S. Air Force Combat Information System
i Tactical Rreconnaissance Intelligence Exchange System (TRIXS) via the Commander's Tactical Terminal (CTT), or equivalent transceiver.
j Tactical Information Broadcast Service (TIBS)
via the Multi-mission Advanced Tactical Terminal (MATT), or equivalent transceiver.
k Tactical and Related Applications (TRAP)/
Tactical Data Information Exchange Service (TADIXS-B) broadcasts via the Tactical Receive Equipment (TRE) or equivalent transceiver.
5 All tiers of the IAS shall be capable of passing SIDS files, via data link, to all other IAS tiers.
A SIDS file is that data necessary to provide a photo image.
(2) Mission Critical Resources
(a) Post Deployment Software Support (PDSS) will be provided for the service life of the system. The Marine Corps Tactical Systems Support Activity (MCTSSA) will function as the Marine Corps Post Deployment Software Support Activity (PDSSA).
All source code will be documented.
(b) Compact Disc - Read Only Memory (CD-ROM) and digital audio recording/playback technology are objectives.
(c) Computer hardware shall not be required to meet full ruggedized standards.
(3) Support Resources. No special support resources are
necessary or acceptable.
(4) Automated Test Equipment. Paragraphs 5c and 4c(1)(f) apply.
(5) Capabilities Desired for Integrated Support.
No special capabilities are desired or required.
(6) Unique User Interface Requirements. None.
(7) Documentation Needs. No special documentation needs are required or desired.
f. Other Logistics Considerations
(1) Provisioning Strategy. The IAS shall not create any need for new or different provisioning procedures.
(2) Unique Requirements. None.
(3) Special Considerations
(a) Packing. No special packaging requirements are necessary or acceptable.
(b) Handling. The IAS shall not require new or unique handling, calibration, facilities, or storage.
(c) Transportation. The IAS shall be capable of transport by fixed wing cargo aircraft, internal or external lift by heavy helicopters, rail and sealift. The MEF IAS HMMWVs shall be capable of self-loading onto all modes of transport. The IAS Suite and Workstation will be transportable by individual Marines and capable of loading onto the transport mode without additional or special lift requirements.
(4) Unique Data Requirements. None.
6. Infrastructure Support and Interoperability
a. There is one companion Operational Requirements Document (ORD)-SIDS (ORD No. CCC 1.50). SIDS allows the IAS to host implementation of an intra-MAGTF SIDS network to provide imagery across the battlefield and to the MAGTF. Specific IAS requirements to support SIDS are contained in the SIDS ORD. A synopsis of SIDS capabilities and IAS related requirements follow.
(1) SIDS will provide the capability to electronically receive, process, reproduce, and disseminate near-real-time imagery throughout the MAGTF. This capability will be hosted on the IAS and serve as the means to manage imagery products. The SIDS consists of three components:
(a) SIDS External (SIDS-E). The SIDS-E module will be a hardware and software enhancement included on the TAC DODIIS IAS tier, located at the MAGTF Command Element. SIDS-E provides
connectivity between the MAGTF and external sources; theater, national, and other service(s)).
(b) SIDS Internal (SIDS-I). The SIDS-I module is
a hardware and software enhancement installed on the IAS intermediate suites and workstations. SIDS-I provides internal connectivity to conduct imagery dissemination of imagery.
(c) SIDS Manpack. The manpack SIDS configuration consists of two devices; a man portable device which provides reconnaissance and surveillance units the capability to electronically disseminate imagery to the MAGTF in near-real-time via tactical communications, and a base station module to receive imagery and enter it into the IAS hosted SIDS network.
(2) SIDS Performance Capabilities and Characteristics
(a) Rapid transmission time, not to exceed two minutes per image on the IAS-hosted (SIDS-I/E) or 10 seconds on the SIDS manpack configuration.
(b) For all components, a 0.5 maximum allowable National Imagery Interpretation Rating Scale (NIIRS) loss from transmission.
(c) Contain a data storage capability on the IAS
hosted SIDS (SIDS-E/SIDS-I) configurations and manpack SIDS.
The volume of data storage will vary with the IAS equipment configuration. All storage units will have a compression capability and will store images on removable diskettes.
(d) SIDS-I/E will have a reproduction capability of approximately nine inches by nine inches hard copy product within one minute containing 126 shades of gray, collocated with IAS, but not installed on the IAS.
(e) The IAS-hosted configurations (SIDS-I/E) can be in operation 22 hours a day. The average processing time per image shall be five minutes, including receipt, manipulation, and annotation of each image. The IAS-hosted SIDS configurations may operate on the same power source as the IAS host machines.
(3) Physical Characteristics
(a) The IAS-hosted configurations (SIDS-I/E) will consist of modular equipment, with software, installed and attached as hardware and software enhancements to IAS equipment.
(b) The IAS-hosted configurations (SIDS-I/E) will display soft copy imagery on the screen of the IAS host
workstation(s). The SIDS will be capable of rotating, limited mensurating, and annotating the displayed soft copy imagery.
(4) User Information Characteristics
(a) The IAS-hosted configurations (SIDS-I/E) will be capable of displaying latitude-longitude or Universal Transverse Mercator (UTM) grid location, north arrow, date/time of imagery, and classification. Soft copy imagery processing will be accomplished on the IAS host by interfacing SIDS software with IAS hardware. Therefore, no controls other than the IAS host controls will be required, except for a on/off switch for the imagery reproduction system.
(b) The SIDS manpack configuration shall receive imagery product from a hand held NDI "filmless" camera, display the image on a screen not smaller than 12.7 centimeters (CM) by 12.7 CM, and transmit the image beyond line of sight over secure single channel radio. The SIDS manpack is not required to manipulate the imagery, but must display it.
(5) Power Source and Mounting. The IAS-hosted SIDS E/I hardware and software enhancements will operate on the same power sources as IAS. The manpack SIDS will use batteries common to Marine Corps tactical communications equipment.
(6) Training to operate the IAS-hosted configurations (SIDS-I/E) will be a part of the training required for IAS.
IAS operators will be taught system description, design characteristics, operating features, hardware configuration, set-up/tear-down procedures, isolation of malfunctions, and software applications of the SIDS. The training objective for manpack SIDS is to train Marines in reconnaissance and surveillance units to successfully utilize the manpack to receive, annotate, and disseminate imagery collected by hand held camera equipment and
the training objectives for the SIDS I/E.
b. The U.S. Army, Navy, and Air Force have similar requirements and all have indicated Joint Interest. The following architectures and programs are related to the IAS.
(1) USMC: JSIPS, SIDS, TCAC, TCO, TERPES.
MCCTA and MAGTF C4I architecture.
(2) U.S. Army: ASAS.
(3) U.S. Navy: COPERNICUS, JMCIS.
(4) U.S. Air Force: Combat Information System (CIS).
(5) DoD/Joint: DoDIIS, MIIDS/IDB, JDISS,
JWICS, Joint Interoperability
with National and Tactical
Command and Control Systems
c. Command, Control, Communications, and Intelligence
(1) System Integration. The system will be fully compatible with and capable of interoperability with U.S. Marine Corps C4I architecture equipment. The IAS will be capable of connectivity to the AN/MSC-63A, Communications Central for AUTODIN and SCI communications. These capabilities will provide connectivity within the MAGTF and with Commander, Amphibious Task Force, joint, theater, and national intelligence organizations.
(2) Data Requirements
(a) Data. Threshold - 1200 Bits Per Second (BPS).
Objective - 19400 BPS.
(b) Voice. Threshold - single channel voice, within
Objective - single channel voice external
(c) Video. Threshold - None required.
Objective - Video data link capable
of JWICS data transmission.
(3) Computer Network. IAS must be capable of connection in local and wide area networks (LAN/WAN) within the MAGTF and establishing a LAN within the MEF IAS and IAS Suite. The IAS will have the capability to exchange data via LAN and/or WAN.
IAS will use standard protocols in the DOD TRM for Information Management, Volume 2 of the TAFIM, and the DODIIS Profile.
(4) Anti-jam Requirements. None required.
d. Transportation and Basing. There are no special transportation or basing requirements for IAS.
(1) Lift Constraints. None. The IAS shall be transportable by fixed wing transport aircraft, heavy helicopters, rail and sealift.
(2) Training Locations. See paragraph 5d(1).
(3) Basing. The IAS is transportable and based with
the units to which assigned.
e. Standardization, Interoperability, and Commonality
(1) NATO Cross-Servicing. There is no requirement for
interoperability or integration with NATO, or other allies.
(2) Interoperability with Other Service, Joint Service, and Allied Systems. The system must be certified per DODI 4630.8 and capable of interoperability with Joint protocols and standards through data and secure voice communications, compatible with existing and planned doctrinal tactical communications paths.
(3) Energy Standardization and Efficiency Needs. No special fuels or electrical power needs are desired.
(a) Fuels. No special vehicular fuels will be used.
(b) Electric power. See paragraph 4d(7).
(4) Data Protocols and Standards. The IAS shall provide connectivity to all required applicable data communications networks. At a minimum, IAS shall conform to all data communications protocols and data standards supported by the Marine Corps Tactical Data Network (TDN) program. (See TDN ORD CCC 11.16 and annexes thereto).
f. Mapping, Charting, and Geodesy Support. The system shall support the use of standard Defense Mapping Agency products and the Navy Maritime mapping tool kit.
g. Environmental Support. No special site preparation shall be required for operations. The IAS shall operate without the need for special weather, oceanographic, or astro-geophysical forecasting support beyond that which is normally available.
7. Force Structure
a. Spares. Normal provisioning through Marine Corps supply system, augmented by contractor support.
b. Training Units. See paragraph 5d(1).
c. Platforms to Employ Systems/Subsystems. There are no requirements for employment of the IAS by other Services, government agencies, or NATO.
d. Requirement Numbers
(1) MEF IAS
I MEF 2
II MEF 2
III MEF 2
SPT ESTAB 2
NAL MEB 0
REQUIREMENT NUMBER: 9
(2) IAS Suite
I MEF 19
II MEF 16
III MEF 11
SPT ESTAB 8
NAL MEB 0
REQUIREMENT NUMBER: 70
1 - Numbers of the IAS Suite needed for sustainment may be
published at a future revision to this document.
(3) IAS Workstation
I MEF 57
II MEF 57
III MEF 27
SPT ESTAB 3
NAL MEB 0
REQUIREMENT NUMBER: 227
8. Schedule Considerations
a. Initial Operational Capability (IOC)
(1) MEF IAS: FY95.
(2) IAS Suite: FY94.
(3) IAS Workstation: FY96.
b. Actions Constituting IOC
(1) MEF IAS: One system fielded at one MEF.
(2) IAS Suite: One system fielded at each MEU, Division,
Wing, and FSSG.
(3) IAS Workstation: 15 systems fielded within each MEF.
c. Operational Capability Necessary to Declare IOC. Same as above, for all tiers.
d. Level of Performance Necessary to Declare IOC. Acceptance by the Force Commander.
e. Number of Operational Systems for IOC
(1) MEF IAS: One.
(2) IAS Suite: 18.
(3) IAS Workstation: 45.
f. Number of Operational and Support Personnel for IOC.
g. Number of Facilities and Support Elements for IOC. Not applicable.
h. Time Frame
(1) Objective Time for IOC
(a) MEF IAS: FY96.
(b) IAS Suite: FY95.
(c) IAS Workstation: FY97.
(2) Impact if Objective Not Met. Any delay will
cause a serious, negative impact on the Marine Corps ability
to provide collection management, product fusion, intelligence reporting and dissemination to the MAGTF.
(3) Window of Acceptability. All tiers: FY96-00.
9. Full Operational Capability (FOC)
a. Actions Constituting FOC. FOC objective is two years after IOC with a threshold no later than three years after IOC.
b. Operational Capability Necessary to Declare FOC.
Fielding of entire Acquisition Objective (AO) of all tiers, with all repair parts, and acceptance by the Force Commander.
c. Level of Performance Necessary to Declare FOC. Acceptance by the Force Commander.
d. Number of Operational Systems for FOC
(1) MEF IAS: 8.
(2) IAS Suite: 70.
(3) IAS Workstation: 161.
e. Number of Operational and Support Personnel for FOC.
f. Number of Facilities and Support Elements for FOC. Not applicable.
g. Time Frame
(1) Objective Time for FOC. FY98.
(2) Impact if Objective Not Met. Failure to achieve FOC will cause a negative impact on the Marine Corps ability to provide collection management, product fusion, intelligence reporting and dissemination to all elements of the MAGTF within all MEFs and contingency deployments.
(3) Window of Acceptability. FY98-00.