![](/uploads/1/2/5/6/125615593/742536137.jpg)
The Battle Command Sustainment Support System BCS3 is the logistics Battle Command system that provides command and control to logistics commanders.
Army Digitization Master Plan '965. ARMY BATTLE COMMAND SYSTEM (ABCS)ABCS is the integration of command and control systems found at all echelons: from theground force component commander at the theater or joint task force level to theindividual soldier or weapons platform; in an Army force deployed for land combat orconducting peace operations, humanitarian assistance, or operations in aid of civilauthorities. ABCS is the integration of battlespace automation systems and communicationswhich functionally link strategic and tactical headquarters. It can also employ a mix offixed and semi-fixed installations and mobile networks. It is interoperable with joint andmultinational command and control systems at upper echelons across the full range ofcommand and control functionality, and is vertically and horizontally integrated at thetactical and operational levels.ABCS has three major components:. Army Global Command and Control System (AGCCS). Army Tactical Command and Control System (ATCCS).
Force XXI Battle Command, Brigade-and-Below (FBCB2) system.5.1 Army Global Command and Control System (AGCCS)AGCCS is the Army component of the joint GCCS. It is being built from applicationprograms developed by the Army WWMCCS Information System (AWIS), the Strategic TheaterCommand and Control System (STCCS), and the Echelons Above Corps (EAC) portion of theCombat Service Support Control System (CSSCS). The primary scope of this effort is toevolve these stand alone systems into a suite of modular applications (e.g., logistics,medical, personnel, Theater Army Special Operations Support, mobilization, deployment,Army Status of Readiness and Training, and Transportation Asset Management) that operatewithin the DII COE. AGCCS modules will interface with common applications and other sharedcomponents of the ABCS and with the joint C2 mission applications provided by GCCS.5.1.1 Army WWMCCS Information System (AWIS)When the Army is currently called upon to rapidly deploy its forces, AWIS provides thesupport for the entire operation: from mobilization and deployment through employment andsustainment. AWIS fulfills the Army's strategic C2 requirements for software, hardware,and databases for the implementation of the Joint Operations Planning and Execution System(JOPES) and other Joint Service systems that support the Unified Commands and the JointStaff.
Page/Link:Page URL:HTML link:The Free Library. Retrieved Apr 14 2020 fromSince its inception, the Battle Command Sustainment Support System(BCS3) has had to overcome several obstacles on its way to becoming thelogistics component of the Army Battle Command System (ABCS). Despitethe millions of dollars spent on research and development, fielding,training, service, and support for BCS3, most units still use it only ona limited basis. Recent updates to BCS3 software can help curb negativeattitudes toward the system and go a long way toward increasing its useacross the logistics community.Issues Causing Low BCS3 UseAlthough BCS3 offers tremendous capability for logisticians at alllevels of war, including in the joint environment, numerous issues havecaused its low usage by units in the field.
![Battle Command Sustainment Support System Battle Command Sustainment Support System](/uploads/1/2/5/6/125615593/649012742.jpg)
Part of the problem is thatBCS3 was a product of the Joint Deployment Logistics Model.Incorporating BCS3 with 'live' data created data integrityissues because information from numerous sources was stored in twoseparate unsynchronized databases.Before the recent updates, the look and feel of BCS3 software wasquite possibly the biggest issue causing low usage of the system. Theuser interface was not intuitive or user friendly and had clutteredmenus. The biggest drawback was that BCS3 did most tasks in anon-Windows environment.
Even the simplest tasks, such as creating basicfilters, were complicated in BCS3. The use of nonstandard terms in placeof standard Army terminology created confusion.
Starting BCS3 was alengthy and slow process, and it took several minutes to transitionthrough various screens. BCS3 TrainingBecause the BCS3 software was not user friendly, its use requiredextensive training on a skill that would soon become obsolete.Initially, the Army fielded BCS3 to units just before they deployed,which precluded adequate training opportunities. Today, BCS3 fieldingand new equipment training occur early in the predeployment process,potentially causing the opposite dilemma. If Soldiers are trained tooearly, their BCS3 skills could atrophy before they have the opportunityto use them at a capstone training exercise.Operators and managers must continue to be exposed to BCS3 to avoidskill erosion. The many predeployment tasks for midgrade officers andsenior noncommissioned officers (NCOs) compete with their availabilityto attend BCS3 training.System DistributionAnother problem in BCS3's development is the battle commandpolicy of 'software blocking' for ABCS. Software blocking isthe process of delivering updated versions of all of the different ABCSsoftware simultaneously to ensure compatibility, limit the amount ofABCS software testing, and most importantly, decrease turbulence tousers in the field.Although these are all valid reasons for the use of softwareblocking, the policy creates a major shortfall by dramatically delayingupdates to the field. If the software for most of the subsystems isready for an update, waiting for the remaining subsystems to reachmaturity causes a delay.
Delays continue until all of the subsystemsoftware passes compatibility testing. Consequently, major softwareupdates normally take years to field.The basis of issue plan determines the number of BCS3 systemsauthorized for the different types of units. The authorized quantity onthe modified table of organization and equipment (MTOE) comes from thebasis of issue plan. Many factors, such as unit type, echelon, and dutyposition, determine the number of authorized BCS3 systems. The BCS3basis of issue plan disproportionately authorizes more BCS3 systems atthe operational level than the tactical level. A more even distributionof the systems would benefit overall BCS3 effectiveness.Logistics Reporting ToolThe most recent version of the BCS3 software offers a logisticsreporting tool (LRT), which provides an automated means of reportinglogistics status (LOG-STAT). As a single point of data entryapplication, LRT provides 'bottom up' reporting for allclasses of supply.
Key commodities without a tactical Standard ArmyManagement Information System (STAMIS), such as class I (subsistence),class III (petroleum, oils, and lubricants), and water, benefit the mostfrom the LRT capability. Designed in a spreadsheet format, LRT is veryuser friendly and therefore requires minimal user training. Managers ofcommodities without a dedicated tactical STAMIS will find LRTparticularly useful.
Historically, units have managed commodities such as fuel and waterby emailing multiple Microsoft Excel spreadsheets. Normally, a higherheadquarters creates the spreadsheets and pushes them down tosubordinate units. Lower-level activities submit appropriatespreadsheets to their next higher command.Typically, quality checks at each level result in units volleyingspreadsheets until they are correct. Likewise, each command levelconsolidates data from like activities and forwards them to the nexthigher command, and so forth.
Because of the numerous manual dataentries at every level and the long trail of email traffic, this processis inefficient, lengthy, and prone to human error.As a single source of data entry, LRT is efficient, fast, andaccurate. For example, a supply point clerk submits a report and theinformation is immediately available for all LRT account holders. LRTeliminates manual spreadsheets and the associated errors, reduces emailtraffic, and most importantly, provides logistics planners andcommanders at all levels accurate real-time commodity information.An additional benefit of LRT is that it is stand-alone software.LRT software is loaded on all of the BCS3 MTOE systems and is alsoeasily downloaded to any computer. Since most supply points and supplysupport activities do not have BCS3 systems readily available to them,the ability to download LRT to any computer gives them a simple, quick,and automated application to report LOGSTAT data.In addition to having the stand-alone capability of LRT, many BCS3capabilities are Internet accessible via the BCS3 local access portal(LAP).
Commanders, support operations officers (SPOs), commoditymanagers, and S-4s can access all LOGSTAT and STAMIS reports quickly andconveniently. Including LRT and LAP can easily increase the amount ofpersonnel in a unit exposed to data in BCS3.Ways to Increase the Use of BCS3Despite improvements, the current version of BCS3 still onlyreceives limited use in the field. In fact, most units employ only asmall portion of their MTOE-authorized BCS3 systems. The most importantfactors to increase BCS3 use are support by senior leaders and increasedtraining for mid-level managers.In the field, a commander has the discretion to use or not to useany of the numerous tools available. No matter how much the Army investsin a system, many senior leaders do not mandate the use of specificsystems such as BCS3. Although a commander should have this prerogative,not encouraging the use of a system influences the users'perceptions of it If the commander does not support BCS3, it is notlikely to be used by the staff.
If a higher command does not use orenforce the use of BCS3, the subordinate units do not even considerusing itOn the other hand, if a commander encourages or mandates the use ofBCS3, the staff will, at the very minimum, attempt to learn and use thesystem. Commanders, field-grade officers, and senior NCOs mustparticipate in BCS3 implementation plans to foster its integration intothe unit and ensure that the system meets its full potential.To increase the effectiveness of BCS3, one major change to thecurrent training format is needed: training should familiarize studentswith BCS3 and focus on system management rather than only operatortraining.
Is approach would have significant effects. Officers andsenior NCOs could concentrate on analyzing and managing informationinstead of creating or harvesting data.
This training could beincorporated into the SPO course, or a course could be developed by theArmy Logistics University as a complement to the SPO course.BCS3 has improved and continues to improve its capabilities and itsease of use for logisticians. System changes that consolidated BCS3 intoone database have nearly eliminated data integrity issues. Updates tothe software to increase the ease of use have begun, and additionalimprovements are on the horizon. Commanders, senior staff officers, andoperators must approach BCS3 with an open mind and experience firsthandthe power that BCS3 brings to logistics mission control, reporting, andsituational awareness.MAJOR DONALD C. SANTILLO IS THE BRIGADE S-4 FOR THE 10THSUSTAINMENT BRIGADE AT FORT DRUM, NEW YORK. HE PREVIOUSLY SERVED AT THESUSTAINMENT CENTER OF EXCELLENCE AT FORT LEE, VIRGINIA, AS A COMBATDEVELOPMENT STAFF OFFICER FOR THE ARMY TRAINING AND DOCTRINE COMMANDCAPABILITIES MANAGER, BCS3.
HE HOLDS A B.S. DEGREE FROM NIAGARAUNIVERSITY AND A MASTER OF MILITARY ARTS AND SCIENCES DEGREE FROM THEARMY COMMAND AND GENERAL STAFF COLLEGE. HE IS A GRADUATE OF THE ORDNANCEOFFICER BASIC COURSE, COMBINED LOGISTICS CAPTAINS CAREER COURSE, ANDINTERMEDIATE LEVEL EDUCATION.
![](/uploads/1/2/5/6/125615593/742536137.jpg)