CALL title banner
Handbook 10-55
August 2010

Chapter 4

Research and Development for the Warfighter

Articles:

Section 1: Achieving Army-Marine Corps Logistic Interoperability   Dale E. Houck

Section 2: Precision Cargo Air Drop - Coming to Your Servicing Theater   Albin R. Majewski and CPT Arthur A. Pack


Section 1: Achieving Army-Marine Corps Logistic Interoperability

Dale E. Houck

Reprinted with permission from the November-December 2009 issue of Science AT&L Magazine.

An Army Stryker battalion is attached to a Marine expeditionary brigade's regimental combat team, which is being supported by the brigade's logistics forces ashore and at sea. On the fifth day of operations ashore, a Stryker health management system identifies a maintenance problem and automatically initiates a call-for-support message. The Stryker crew uses the platform's embedded interactive electronic technical manual to verify the turbocharger has failed and must be replaced. The platform commander submits the call-for-support message for maintenance, providing necessary information to the Stryker battalion supply and logistics officer by means of Force XXI Battle Command, Brigade-and-Below/Joint Capabilities Release (FBCB2/JCR), an automated information system that facilitates enhanced tactical command and control (C2) and situational awareness through the incorporation of interoperable data standards and messaging methods. The supply and logistics officer analyzes the situation and determines he has neither the parts (meaning the turbocharger) nor qualified maintenance personnel (meaning limited forward maintenance team support attached to the Stryker battalion) to support this problem. He forwards the call-for-support message to the Marine Corps' direct support combat logistics battalion operations officer. At the same time, information is extracted from the variable-message-format call-for-support message to automatically open a service request for maintenance in the Marine Corps' logistics business system, the Global Combat Support System-Marine Corps. The direct support combat logistics battalion operations officer uses GCSS-MC to determine that qualified maintenance personnel are available, but the required part is not. The direct support combat logistics battalion operations officer (located ashore) initiates a requisition for the turbocharger in GCSS-MC and forwards it to the general support combat logistics battalion operations officer (located at sea). The general support operations officer cannot satisfy the requirement and forwards the requisition via GCSS-MC to the sea-base, where the turbocharger is sourced. The reinforced combat logistics regiment manages the distribution of the turbocharger to the direct support combat logistics battalion operations officer, who then ensures the turbocharger and a maintenance contact team are sent to fix the Stryker.

While that scenario is hypothetical, it is typical of the circumstances faced by soldiers and Marines in joint operations. In the scenario, the request for support, initiated as an FBCB2/JCR variable-message-format message, is automatically and seamlessly integrated into the business processes and systems of the supporting service without requiring either service to change its unique processes or systems, demonstrating true joint logistics interoperability. The scenario illustrates how network-enabled technologies could enhance future Army and Marine Corps logistics interoperability and readiness during joint combat operations. Inter-Service obstacles to seamless communications are overcome, and common logistics support is delivered to the operational commander on the battlefield.

Operations Desert Storm, Iraqi Freedom, and Enduring Freedom revealed that joint and Service logistics systems that could not communicate with each other resulted in order fulfillment lag times, redundant ordering, choked supply pipelines, and uncertainty for the warfighter. It was readily apparent that deployable, integrated technology was necessary to provide responsive, agile, and flexible logistics support to the warfighter. As a result, the Army and Marine Corps have been collaborating to leverage and integrate their logistics capabilities to accomplish missions at the tactical level.


Future Imperatives

Two imperatives needed to ensure operational logistics adaptability are reduced logistics demand and intelligent supply chains, with both enabled by data fusion and science and technology. Operational logistics adaptability translates to decision making in the face of complexity and the ability to share information across the joint force unhindered by distance, terrain, weather, or hostile activity; and intelligent supply chains of the future will require radically advanced data collection, transmission, analysis, and discovery of relationships normally hidden in vast quantities of data scattered throughout multiple global data bases. Reduced logistics demand and intelligent supply chains will require integrated and interoperable logistics systems and processes, providing a near-real-time logistics common operating picture and adhering to common net-centric standards and protocols-necessary for success within a common logistics operating environment.

The future land component will be, by necessity, net-centric and interoperable within the full range of military operations including interagency and coalition partners. The Joint Logistics White Paper (draft version 0.6, June 2009) describes a concept for providing logistics support to a future joint operating force in the 2016-2028 timeframe. It describes three well-documented issues that must be overcome:

  • Insufficiently integrated logistics organizations and processes
  • Execution issues
  • Insufficiently interoperable/integrated C2, logistics management, and financial systems.

The Army-Marine Corps Logistics Interoperability Demonstration (AMLID) is a significant step in addressing several of those issues as it works toward improved Army-Marine logistics capabilities.


A Joint Effort for Interoperability

AMLID project is a joint effort between the Army and Marine Corps, with project management provided by the U.S. Army Logistics Innovation Agency, a field operating agency of the Office of the Deputy Chief of Staff of the Army, G-4. The project's goal is to enable Army-Marine Corps logistics interoperability and joint interdependence by creating the capability to exchange actionable information across Service boundaries needed for joint task force employment. Interoperability-the basic tenet of AMLID-provides a compelling case for obtaining required support for a tactical unit from an attached sister Service, as far forward as possible, to eliminate the requirement to conduct reachback logistics support via stovepiped Service systems.

AMLID will perform information exchanges of platform-generated data between logistics and C2 systems. That will result in a cross-Service fulfillment of a logistics support request; and the sharing of common situational awareness across the joint logistics operating environment, building on both Services' logistics operational architectures. AMLID will provide a useful, near-term practical application of logistics C2 convergence through advanced technology insertion. It will allow Services to operate using their business systems and practices, but still operate jointly. AMLID seeks to provide rapid inter-Service fulfillment of a common sustainment requirement in time-sensitive situations (i.e., when it is more efficient or effective as a result of one or more factors related to mission, enemy, terrain and weather, troops and support available, or time available). While AMLID will demonstrate information exchanges from the platform level via FBCB2/JCR to another Service's logistics system, its metadata dictionary and data translation standards, defined during development of the initial system interfaces, could support further development of a broader spectrum of system interface software and more extensive net-centric logistics capabilities.


Creating Logistics Synergy

AMLID, a four-phased project, will facilitate direct communication between Army and Marine Corps logistics systems, thereby reducing the logistics demand on C2 systems. The AMLID team will develop the seamless integration of variable-message-format data between tactical C2 and logistics systems from each Service as well as the automated extraction of variable-message- format data from the tactical C2 systems and insertion directly into each Service's logistics systems to automatically open service requests, work orders, and supply requisitions. The team has developed a software interface tool known as the Marine-Army Joint Interoperability Component using a service-oriented architecture approach to bridge the gap between systems and networks. A service-oriented architecture approach provides a framework for organizing and orchestrating application functions/services across system boundaries. Within this framework, MAJIC acts as the translator to enable FBCB2/JCR variable-message-format combat service support messages to be exchanged and accurately interpreted among supporting and supported units.

The AMLID use-case scenarios address likely threat scenarios. The use-case technique is used to capture a system's behavioral requirements generated from requests that are based on scenario-driven threads. Completed in March 2009, AMLID Phase I was a laboratory-based demonstration of interoperable network architecture that tested prototype system interfaces and information exchanges. Scenarios were focused at the tactical echelon and included mission threads for resupply of petroleum, oil, and lubricants; ammunition; logistics situational awareness; and maintenance support. The intent was to simulate logistics calls for support by passing Joint Capabilities Release initiated information to GCSS-MC through an enterprise service bus and to a standard Army management information system (STAMIS). FBCB2/JCR version 1.0 was used to send variable-message-format logistics messages from the Marine Corps to the Army and included situation reports, logistics status reports, and call-for-support messages.

Phase I

The Phase I demonstration, conducted at the Marine Corps GCSS-MC System Integration Lab at Pennsylvania State University's Applied Research Laboratory, successfully demonstrated interoperability between Army and Marine Corps information transmissions via FBCB2/JCR, each Service's logistics systems, and MAJIC. Four different use-cases were evaluated, resulting in a 97-percent success rate for the message transfer/translation process. Phase I-and MAJIC in particular-demonstrated that Army and Marine Corps tactical units can transmit requests for emergency logistics requirements between logistics systems using interpretive software (middleware) to translate the raw data inherent in the variable-message-format requests between the Services.

Phase II

AMLID Phase II is currently under way. It includes a senior leadership live platform demonstration that showcases a network architecture expanded to include C2 and logistics systems and processes up to and including the operational echelon. The demonstration consists of two scenarios-forced-entry operations and decisive land operations-with each scenario incorporating situational awareness threads integrated with related C2 monitoring systems. The forced entry operations scenario will include a use-case and thread for petroleum, oil, and lubricants; ammunition; distribution; and logistics situational awareness, while the decisive land operations scenario will focus on repair parts, maintenance, distribution, and logistics situational awareness. The ability to seamlessly communicate requests for service, feedback, and status information between GCSS-MC and the Army STAMIS/GCSS-Army system is a primary objective. A successful demonstration will provide a valuable assessment on the potential to eventually extend the same capability to Global Combat Support System-Joint.

Phase II-which is designed to successfully pass logistics information between Service logistics systems-will significantly advance the utility of interoperability, resulting in platform-level data aggregated in C2 systems and joint logistics situational awareness. Information will flow between operating combat platforms, a Marine Corps light armored vehicle, and an Army Stryker using FBCB2/JCR-through MAJIC-allowing information to go from one Service to another. Upon completion, AMLID will have developed consolidated mission threads for petroleum, oil, and lubricants; ammunition; and repair parts; as well as distribution in-transit visibility and logistics situational awareness. DoD's Battle Command Sustainment and Support System will be integrated into the overall network architecture in order to manage logistics situational awareness through the various logistics supporting establishments to the theater sustainment command and Joint Task Force component commander.

Successful completion of Phase II will serve as a foundation for prospective follow-on Phases III and IV. AMLID team stakeholders envision Phase III to be the development of a fielding plan for the logistics interoperability functionality that was developed, blueprinted, and demonstrated during Phases I and II. The project would culminate in Phase IV, providing for the advanced integration of AMLID technology into other closely related logistics modernization programs, such as the Marine Corps' Autonomic Logistics effort and the Army's Conditions-Based Maintenance Plus project. While not yet officially sanctioned by Service proponents, those follow-on efforts could potentially support the objectives of the Services' combat service support and sustainment missions and the visions outlined in their higher-level logistics architectures.


Logistics Architectures

AMLID is a major initiative of the Army's Common Logistics Operating Environment Program and is aligned with objectives of the Marine Corps' Logistics Modernization program and Joint Forces Command's Joint Interoperability and Data Dissemination Strategy. The Common Logistics Operating Environment is the Army's capstone initiative to synchronize diverse logistics modernization efforts into a cohesive, net-centric logistics domain. The effort integrates data across the full spectrum of logistics and includes equipment platforms, logistics information systems (including GCSS-Army), and C2 systems-all functioning within a common architectural framework described in detail by the Army's Training and Doctrine Command-validated Army Integrated Logistics Architecture. That architecture spans from the tactical through strategic echelons; supports a joint, integrated environment; and assists the Army logistics community in achieving integration and interoperability in the logistics domain.

The Marines' Logistics Modernization Program will produce a more effective and efficient logistics chain management process, with modernized, integrated, and streamlined supply, maintenance, and distribution processes that conform to the Marine Corps' Logistics Operational Architecture. The architecture supports the implementation of enterprise-wide processes for logistics and will be supported by a thoroughly modernized enterprise resource planning system, GCSS-MC.

Both the Army and the Marine Corps architectures provide the framework to clearly define logistics processes and to implement net-centric warfare principles in the logistics domain. Additionally, they provide the foundation to move beyond the unsynchronized use of a handful of common C2 systems and help realize a unity of effort within the logistics joint capability area.

Architecturally, AMLID supports both the Army's and the Marine Corps' logistics architectures and seeks to provide a flexible support construct that integrates various logistics systems across Service boundaries. It is accelerating the technology maturation process for logistics automation in a joint operational environment. The Phase II demonstration will provide an early opportunity to perform focused testing on the latest version of GCSS-MC's Release 1.1 software and evaluate its prospective future interoperability with the Army's STAMIS. Ultimately, DoD Architecture Framework products developed for AMLID will be fed back to the Marine Corps' Logistics Operational Architecture and the Army Integrated Logistics Architecture to assist in the further development of common data standards and associated architectures that will facilitate logistics net-centricity and fully integrated Army and Marine Corps operations.


A Significant Step

The Army and Marine Corps continue to reduce gaps in logistics interoperability related toorganizational and system interface differences and non-standard architecture. AMLID identifies gaps in process or system interoperability where additional work may be necessary in order to support the development of a composite architecture (the Marine Corps' Logistics Operational Architecture and the Army Integrated Logistics Architecture) necessary for joint interoperability. AMLID's service-oriented architecture allows different applications to exchange data, and tools such as MAJIC will make it possible to securely exchange information between Service enterprise resource planning systems and legacy systems.

AMLID does not purport to be a final solution in resolving interoperability issues between the Army and Marine Corps or other DoD services and supporting government agencies; however, it is the focused application of technology solutions to improve the efficiency of Army-Marine Corps operations as part of a joint force. AMLID is a significant step in achieving:

  • More effective and efficient joint logistics
  • The coordinated use, synchronization, and sharing of two or more military departments' logistic resources to support the joint force
  • A foundation for future programs, such as GCSS-Joint.

As AMLID evolves to support remaining classes of supply, it will integrate disparate Service information systems and data to provide enhanced visibility of resources and requirements; and it will provide Army brigade combat teams and Marine Corps regimental combat team commanders, and ultimately all of DoD, an effective means to achieve mission objectives.



Section 2: Precision Cargo Air Drop - Coming to Your Servicing Theater

Albin R. Majewski and CPT Arthur A. Pack

Reprinted with permission from the Winter 2004 issue of Quartermaster Professional Bulletin.

Just a few years ago if you had spoken to personnel from units outside the Airborne and Light Infantry communities about precision air drop resupply, you would have received some mighty strange looks. Today, because of highly dispersed operations, the length of ground lines of communication (GLOC), the enemy's continuous attacks on convoys and increased use of improvised explosive devices (IEDs) in Southwest Asia, the expanded use of cargo air drop resupply doesn't seem so far-fetched. The operational environment has caused the Army to rethink the way to sustain the warfighter and to accelerate delivery of a precision air drop capability, in support of Operation Iraqi Freedom.


Urgent Operational Need

Off-the-shelf technology called the Sherpa 900 system was the immediate answer to an urgent request from Multi-National Force-Iraq for extra-light air drops to Marines in forward operating bases. The Sherpa 900 gets its name not because of its 1,200-pound load weight, but because of its 900-square-foot RAM air parachute canopy that can be steered - unlike the standard round canopy. The Sherpa drops since last August typically have been Meals, Ready to Eat and bottled water delivered within 100 meters of the predetermined impact point in remote locations.

The Directorate of Combat Developments for Quartermaster (DCD-QM), US Army Combined Arms Support Command, has been playing an active role in securing advanced technology for precision air drop since approval of a mission needs statement in 1997. However, the initiative gained visibility in October 2002 when the Deputy Commanding General, US Army Quartermaster Center and School, decided for DCD-QM to pursue precision air drop as an official Advanced Concept Technology Demonstration (ACTD). At the same time, the Army Natick Soldier Center was developing a linkage between the Air Force's Precision Air Drop System (PADS) and the Army's Precision Extended Glide Airdrop System (PEGASYS). Together, the Army and Air Force pursued an ACTD for their linked programs, named the Joint Precision Air Drop System (JPADS). The go-ahead for the JPADS ACTD came in August 2003.

What is an ACTD and why is it so important? ACTDs emphasize technology assessment and integration rather than technology development to solve important military problems. The ACTD's goals are to provide warfighters a prototype of a capability and to support the Soldiers evaluating that prototype. Warfighters evaluate technologies in real military exercises. Also, a key ACTDs objective is to provide an operational capability to the warfighter as an interim solution before procurement of a successful prototype.

The assessment of the Sherpa 900 system for extra-light precision air drop in Iraq became an interim solution while the JPADS ACTD's process worked toward the demonstration of a 10,000-pound total rigged weight capability and a 2,200-pound total rigged weight capability. The Sherpa 900 system's 1,200-pound load weight met a more immediate need for combat operations.

In May 2004, the Army G3 (Operations) approved an Urgent Operational Needs Statement initiated by Multi-National Force-Iraq, requesting an extra-light precision air drop capability in the theater of operations during FY04. The system's users would be Marines - in particular the riggers from 1st Air Delivery Platoon that is part of Combat Service Support Battalion 7, 1st Force Service Support Group delivering supplies to Marine units throughout the vast western portion of Iraq's Al Anbar Province. After completing coordination, Marines from the Marine detachment in theater and from their home base at Camp Pendleton, CA, completed Sherpa 900 training at Yuma Proving Ground, AZ.

The Sherpa 900 system consists of a mission planner, central processing unit (CPU), parachute control unit (PCU) with built-in Global Positioning System (GPS) guidance unit, and the 900-square-foot canopy. By contrast, the Army/Air Force JPADS with a 10,000-pound total rigged weight is considered the light version in the JPADS family of systems under development. The extra-light version of JPADS has a total rigged capability of 2,200 pounds. The Sherpa 900 is considered a 60 percent solution to what is to come. The final solution will be incorporated with the Air Force's PADS capability and then boosted to a total rigged weight of 2,200 pounds.


Battle Hand-Off During Operation Iraqi Freedom

After the Marines completed training in Arizona, two Sherpa 900 systems were packed and shipped into theater in Iraq. The two systems were accompanied by two Army officers, a combined team consisting of the materiel developer and the combat developer, who ensured a proper battle hand-off to the unit. While in theater, the team witnessed the first operational use of the Sherpa 900 system in support of Operation Enduring Freedom on 9 Aug 04. Both Sherpa 900s were dropped for a Marine forward operating base (FOB) called Camp Korean Village.

By late autumn 2004, 9 of 11 air drops with Sherpa 900 systems had been successful. Drop number six failed after the GPS did not receive satellite lock before exiting the aircraft. This resulted in an unguided flight to the ground. A problem on drop 11 caused the main canopy not to deploy. The cause of this canopy problem has not yet been determined, but the system has since been replaced. After completion of the required 10 extra-light air drops, DCD-QM anticipates that Multi-National Force-Iraq will request that Army G3 provide 18 more systems to complete its original Urgent Operational Needs Statement.


Modernizing Theater Distribution

Both the Army and the Air Force had been independently working their respective pieces of the JPADS program, but that came to a halt last August when the Air Staff directed incorporation of Air Force analysis and requirements into the Army documentation. On 28-29 Sep 04, DCD-QM hosted a Joint Requirements Working Group that brought all military services up to speed on both the JPADS program and documentation required the JPADS Extra Light and Light versions. Ultimately, the intent is to submit the 2,200-pound Extra Light requirement in 2d Quarter, FY05, followed by the 10,000-pound JPADS Light requirement as soon as its ACTD results are known.

The Air Force plays an important role on two fronts. First, the Air Force provides most JPADS aircraft delivery platforms, Secondly and most importantly, the Air Force brings its PADS capability that will provide near real-time wind information, further improving airdrop accuracy. The PADS today is a single, portable package of three major components on the PADS laptop computer. PADS will provide greater accuracy to ballistic high-altitude air drops and precision-guided, high-altitude air drop systems through algorithms and high- fidelity wind data.

Cargo air drop, and JPADS in particular, directly lead the way in supporting Modernization of Theater Distribution: one of the Army G4 (Logistics) four focus areas. Based upon the asymmetric battlefield, with long GLOCs and widely dispersed units, cargo air drop with a precision air drop capability is just what the combatant commander ordered. As one logistics operations officer with Multi-National Force-Iraq stated: "The Army is attempting to modernize its supply distribution process throughout Iraq and aerial delivery is certainly part of that. If we can use aerial deliver to keep Soldiers and Marines off the road, then that's a winner for everybody."



 

 
          |   Privacy and Security Notice   |     |   Accessibility Help   |   External Link Disclaimer   |   No Fear Act   |
 
|   U.S. Army   |   Tradoc   TRADOC   |   iSALUTE   | Ft. Leavenworth   |   Site Map   |   FOIA   |   USA.GOV   |   This is an official U.S. Army Site   |