text: Chapter 9
  projected requirements; to synchronize movement and materiel management; and to maintain integrated
  visibility of transportation and supplies. The Joint Capabilities Release (known as JCR), Joint Capabilities
  Release-Logistics (known as JCR-Log) Joint Battle Command-Platform, Joint Battle Command-Platform
  Logistics, Global Combat Support System-Army (GCSS-Army), Command Post of the Future (known as
  CPOF or its replacement Command Post Computing Environment [known as CPCE]), Medical
  Communications for Combat CasualtyCare (known as MC4) are some of the fielded systems the BSB uses
  to ensure effective situational understanding and logistics support. These systems enable sustainment
  commanders and staffs to exercise command and control, anticipate support requirements, and maximize
  battlefield distribution.
  Reports
  9-59. The LOGSTAT is an internal status report that identifies logistics requirements, provides visibility on
  critical shortages, allows commanders and staff to project mission capability, and informs the COP. Accurate
  reporting of the logistics and AHS support status is essential for keeping units combat ready. Brigade SOPs
  establish report formats, reporting times, redundancy requirements, and radio voice brevity codes to keep
  logistic nets manageable.
  9-60. LOGSTAT reporting begins at the lowest level. The company first sergeant or XO compiles reports
  from subordinate elements and completes the unit’s LOGSTAT report. Once completed, units forward
  reports to its higher headquarters and its supporting logistics headquarters, to include the FSC and the BSB.
  Normally LOGSTATs flow through S-4 channels. The BSB and its subordinate units report on-hand supply
  and supply point on-hand quantities.
  Note.(See FM 4-0 for an example LOGSTAT format that BCT units may adapt based on type of
  unit, on-hand equipment, type or phase of an operation, mission requirements, and commanders’
  requirements.) The format is an example spreadsheet for the report. It is nota prescribed format.
  Commanders can modify the format and tailor the report to their unit or mission.
  9-61. The frequency of a LOGSTAT varies and is dependent on the operational tempo of the BCT or
  subordinate units. Typically, units complete a LOGSTAT report twice daily, but during periods of increased
  intensity, the commander may require status updates more frequently. As long as automation is available,
  LOGSTAT relayed via near-real time automation provides the commander with the most up-to-date
  information, ultimately improving the supporting unit’s ability to anticipate requirements.
  9-62. Units can complete the LOGSTAT reporting through any means of communication to include written
  reports, radio, email, JCR, or CPOF/CPCE. AHS status is typically reported through the MC4 system. The
  JCR system helps lower level commanders automate the sustainment data-gathering process. The system
  does this through logistics situation reports, personnel situation reports, logistics call for support, logistics
  task order messaging, situational understanding, and task management. This functionality affects the
  synchronization of all logistics support in the area of operations between the supported and the supporter.
  9-63. Sustainment leaders utilize the GCSS-Army to track supplies, spare parts, and the operational readiness
  of organizational equipment. GCSS-Army is the tactical logistics and financial system of the U.S. Army.
  Within the BCT, supply rooms, motor pools, and the SSA platoon all use GCSS-Army to order supplies and
  repair parts,track maintenance status, and manage SSA operations.
  9-64. The sustainment staff must proactively identify and solve sustainment issues. This includes—
  (cid:122) Using CPOF/CPCE, JCR, JCR-Log, GCSS-Army, and other Army command and control systems
  to maintain sustainmentsituational understanding.
  (cid:122) Working closely with higher headquarters staff to resolve sustainment problems.
  (cid:122) Recommending sustainment priorities that conform to mission requirements.
  (cid:122) Recommending sustainment-related commander’s critical information requirements (CCIRs).
  (cid:122) Ensuring the staff keeps the commander aware of critical sustainment issues.
  (cid:122) Coordinating as required with key automated system operators and managers to assure focus and
  continuity of support.