Medical Logistics - Army Logistics University - U.S. Army
Medical Logistics - Army Logistics University - U.S. Army
Medical Logistics - Army Logistics University - U.S. Army
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
information within a commander’s area of interest tailored<br />
to the user’s requirements and based on common<br />
data and information shared by more than one command.”<br />
Similarly, an LCOP is a single and identical<br />
accounting of the logistics capabilities, requirements,<br />
and shortfalls in an area of operations shared between the<br />
supporting and supported elements. The LCOP allows<br />
the supporting elements to determine unit capabilities,<br />
forecast logistics requirements, synchronize logistics<br />
movements, and publish information that improves situational<br />
awareness at multiple echelons of support.<br />
6<br />
Many <strong>Army</strong> terms formerly reserved<br />
solely for the tactical field<br />
now have logistics equivalents.<br />
Supply convoys are now potential<br />
combat convoys because modern<br />
logisticians cannot expect to operate<br />
in the rear battlespace<br />
and deliver supplies forward<br />
as their predecessors did.<br />
Contemporary logistics operations require that use<br />
of the LCOP be integrated into and support the COP.<br />
The tiered areas of interest (meaning combat zones, or<br />
“hotspots”) on the multilinear battlefield in the Middle<br />
East have led to greater emphasis on increasing the<br />
combat skills of sustainment Soldiers. Many <strong>Army</strong><br />
terms formerly reserved solely for the tactical field<br />
now have logistics equivalents. Supply convoys are<br />
now potential combat convoys because modern logisticians<br />
cannot expect to operate in the rear battlespace<br />
and deliver supplies forward as their predecessors did.<br />
Modern logisticians consider every combat support<br />
mission in Iraq and Afghanistan a deliberate tactical<br />
movement through unforgiving, hostile territory.<br />
Correspondingly, logisticians realize the increased<br />
need to incorporate tactical considerations into their<br />
planning process through the development of their<br />
own COP, the LCOP. This means that the operation<br />
of the BSB tactical operations center (TOC) must be<br />
aligned in a manner that “fuses” the key information<br />
and planning cells. This TOC fusion cell must<br />
be efficient, effective, and simple enough to function<br />
throughout continuous operations. The BSB SPO, S–2,<br />
and S–3 officers, along with the BCT S–4, assemble in<br />
a directed logistics targeting meeting to address current<br />
and future mission capabilities, shortfalls, and requirements.<br />
The logistics targeting meeting synchronizes the<br />
brigade’s logistics effort with its tactical mission and<br />
includes the brigade-level maintenance meeting.<br />
The Daily LOGSTAT<br />
Observer-controllers at NTC have noted a trend<br />
toward low frequency of submission of LOGSTAT<br />
or forward operating base logistics (FOBLOG) status<br />
reports by brigades training at NTC. Many reasons<br />
are behind this trend, ranging from conflicting<br />
mission requirements and communications network<br />
issues to sheer noncompliance by BSB-supported<br />
units. Noncompliance with the established battle<br />
rhythm is often directly related to the supported units’<br />
lack of confidence in, or inexperience with, their supporting<br />
BSB or a general lack of trust in the supply<br />
system. [“Battle rhythm” refers to a deliberate daily<br />
cycle of command, staff, and unit activities intended<br />
to synchronize current and future operations.]<br />
However, just as Department of the <strong>Army</strong> Form<br />
5988–E, Equipment Inspection Maintenance Worksheet,<br />
is the starting point of the entire maintenance<br />
support process, the LOGSTAT report is the feeder<br />
for the visibility, forecasting, and execution of the sustainment<br />
mission. It is not just a logistician’s tool but<br />
also a friendly force information requirement (FFIR),<br />
which is “information the commander and staff need to<br />
understand the status of friendly force and supporting<br />
capabilities,” as defined in FM 3–0.<br />
Before logistics planning can begin, the organic and<br />
nonorganic units supported by the BSB must submit<br />
accurate information on the status of commodities.<br />
Consequently, the LOGSTAT report must be detailed<br />
enough to be an effective tool but also easy enough for<br />
everyone to use and understand. The LOGSTAT report<br />
should be standardized across the using units and should<br />
follow a format that allows its transmission through a<br />
system that does not require line-of-sight communications.<br />
To ensure that multiple transmission methods are<br />
available to prevent the disruption of the information<br />
flow, units should develop a primary, alternate, contingency,<br />
and emergency communication plan.<br />
Once the LOGSTAT format is determined, a good<br />
data-transfer battle rhythm must be established to develop<br />
a good LCOP. A thorough communications exercise<br />
(COMMEX) should be conducted before the information<br />
management systems are actually used; this will<br />
allow the command to identify and resolve issues while<br />
building user confidence in the stability of the signal<br />
officer’s communication plan. Coupling the COMMEX<br />
with a good data-transfer rehearsal helps to establish the<br />
brigade standard with each participating unit.<br />
A good data-transfer battle rhythm facilitates the<br />
collection of accurate and timely information from<br />
supported units by maintaining the principles of<br />
flexibility, sustainability, and ease of use. A flexible<br />
battle rhythm responds to changing mission effects<br />
and new logistics requirements. A sustainable battle<br />
rhythm is synchronized with the scheduled logistics<br />
NOVEMBER–DECEMBER 2008