SoN_Encl_A_GCSS-Army_Disconnected_CONOPS_v1-1_2021_04_12.pdf

GCSS-Army Disconnected Operations Solution (DISCOPS) CONOPS Solicitation Version 1.1, 12 April 2021

DISCONNECTED OPERATIONS SOLUTION (DISCOPS)

CONCEPT OF OPERATIONS

(CONOPS)

SUMMARY

UNITED STATES ARMY

COMBINED ARMS SUPPORT COMMAND

FORT LEE, VA

ENTERPRISE SYSTEMS DIRECTORATE

(USA CASCOM ESD)

SOLICITATION VERSION 1.1, 12 APRIL 2021

V 1.1 Changes Highlighted in YELLOW (on page 3)

Distribution A. Approved for public release: distribution unlimited.

GCSS-Army DISCOPS CONOPS

Distribution A. Approved for public release:

distribution unlimited.

1.0 Background: The U.S. Army must have the capability to perform its mission-critical functions in support of Multi-Domain Operations. In the future operational environment of the Multi-Domain Operations1, the U.S. Army will operate in smaller, more dispersed units far away from well-established military posts that offer critical infrastructure comforts and essentials like connectivity, fuel, water, ammunition, and energy.

1.1 Army Sustainment Operations2 rely on effective enterprise resource planning systems (ERPs), which require access to the DOD Information Network. ERPs typically communicate over the network using the Combat Service Support Automated Information System Interface (CAISI) over Combat Service Support Very Small Aperture Terminals (VSAT).

1.1.1 Army units performing Army Sustainment Operations3 must be ready, as “adversaries will attempt to disrupt, degrade, or curtail our communications and access to sustainment enterprise systems.” Therefore, Army sustainment units and soldiers must be equipped and prepared to continue to operate and perform mission-critical functions in disconnected, intermittent, and limited bandwidth (DIL) operational environments.

1.2 Current State: The Army is crafting a strategy to reduce the logistics tails for units expected to operate at the tactical edge and empower elements to support forward under degraded, disrupted, and even denied communications. This Concept of Operations (CONOPs) focuses on the Logistics element of the U.S. Army’s Sustainment Warfighting Functions, emphasizing the mission-critical functions performed for Maintenance Operations, Warehouse Management, Property Accountability, Unit Supply, and key supporting business functions.

1.2.1 Key Logistics Enabler: The Global Combat Support System-Army (GCSS-Army) provides the Warfighter with an integrated solution for maintenance, unit supply, property management, warehouse management, and includes the supporting finance and Human Resources (HR) (see Figure 1: GCSS-Army Sustainment Logistics Enabler). It is the principal Warfighting system for logisticians to achieve readiness and support operations across multiple domains. GCSS-Army provides a consolidated, integrated database for logistics functions and gives both sustainers and supported commander’s up-to-date visibility of the resources available to a commander. GCSS-Army has been fully fielded and continues to add improved functionality to the baseline.

1.2.2 GCSS-Army currently does not include a capability to operate disconnected. This capability gap requires the GCSS-Army users to implement paper-based processes in their place during times of system outages (see Figure 2: GCSS-Army High-Level Operational View (OV-1)). The Army validates this gap in the GCSS-Army Capability Production Document (CPD) approved by the Joint Requirements Oversight Council (JROC) in June 2011. This document updates that gap with detailed requirements for the Disconnected Concept of Operations.

1 See Training and Doctrine Command (TRADOC) Pamphlet 525-3-1, dated 30 November 2018:

https://www.tradoc.army.mil/Portals/14/Documents/MDO/TP525-3-1_30Nov2018.pdf 2 See Field Manual (FM) 4 – 0 Sustainment Operations, dated July 2019, page 2-70, paragraph 2-305:

https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN19602_FM%204-0%20FINAL%20WEB%20v2.pdf 3 Ibid, page 2-70, paragraph 2-304.

https://www.tradoc.army.mil/Portals/14/Documents/MDO/TP525-3-1_30Nov2018.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN19602_FM%204-0%20FINAL%20WEB%20v2.pdf

Figure 1: GCSS-Army-Sustainment Logistics Enabler

Figure 2: GCSS-Army High-Level Operational View (OV-1)

2.0 Future State: To meet Multi-Domain Operations challenges, the Warfighter requires the capability to execute selected Mission Critical Functions (MCF) in DIL environments. Units must be ready to operate in a degraded/disconnected mode for up to seven (7) continuous days. The GCSS-Army Disconnected Operations Solution (DISCOPS) must have the capability to perform Army designated MCF with sufficient supporting Data, Supply Chain, Asset Management, Inspection, Status Reporting, and Administration functions to support the end-to-end business process(es). The following sections will detail the requirements and provide the context for an envisioned disconnected solution that will be assessed as part of the prototype efforts. Figure 3 below shows the tactical operational view for the solution.

Figure 3: GCSS-Army Enterprise Tactical Operational View (Non-Aviation)

2.1 Functional Capabilities: Users [Military, Government Civilians, and Contractors] need to be able to perform the identified Mission Critical Functions from the GCSS-Army baseline capabilities (Plant Maintenance, Unit Supply, Property Accountability, Warehouse, and applicable administrative Human Resource & Security capabilities) when communications are lost and disconnected from GCSS-Army. Conditions include, but are not limited to:

a) Planned Store & Forward capabilities at all levels.

b) Unplanned disconnected capabilities.

c) Operate up to seven (7) continuous days (168 hours) while disconnected in a multi-domain environment.

d) Solution must be able to interface and synchronize to current and future SAP ERPs

[text deleted] for Army Ground, Missile, Watercraft, and Aviation platforms.

e) Solution must also be able to connect to non-SAP systems.

2.1.1 GCSS-Army Users: GCSS-Army Target Audience includes the following categories and characteristics:

a) Tactical Army Users operating at home station and while deployed.

b) DoD Civilian and Support Contractor Personnel.

c) Personal characteristics: Broad spectrum of ages, levels of education, and skills.

d) Professional/Technical characteristics: Broad spectrum of experience in using the

GCSS-Army fielded systems or other field tablets/scanners/computer workstations and applications.

2.1.2 GCSS-Army Primary Military Users: GCSS-Army provides for position-based access.

The system roles providing access to functional transactions, reports, and necessary workflow processes are aligned to the organizational duty positions. The system Users are assigned to those positions and can execute all assigned functions required for their duty responsibilities.

The Primary User positions for the disconnected solution include, but not limited to, the following military occupational specialties and positions:

a) Maintenance Managers/Supervisors – 91 Series.

b) Automated Logistic Specialists/Clerks – 92 Series (92A) (Includes the local designations of “Equipment Record Parts Specialist (ERPS) Clerk”, the term used in this document).

c) Unit Supply Specialists – 92 Series (92Y).

d) Master Drivers – 88 Series (88M).

e) Staff Officers, Warrant Officers, Non-commissioned Officers, Soldiers and in some units Support Contractors assigned to a Division Sustainment Support Battalion (DSSB) and/or a Combat Sustainment Support Battalion (CSSB) Staff.

f) Sustainment Automation Support Management Office (SASMO) (See Army Doctrine and Training References available on-line at: https://armypubs.army.mil/ ; and see Army Techniques Publications ATP 4-93, ATP 4-93.1 and ATP 4-0.6 at https://armypubs.army.mil/ProductMaps/PubForm/ATP.aspx ).

2.2 User Interface / User Experience: The disconnected solution must have an intuitive User Interface (UI) capability that will provide Users with an effective and efficient User Experience (UX) that optimizes productivity and simplifies meeting the required mission-critical functions.

2.2.1 User Experience (UX): Design should minimize steps and processes users must perform.

2.2.2 User Interface (UI):

a) Design should optimize the intuitive and interactive features of the interface.

b) Builds from the UX design to the user interface.

c) Must be hardware and software agnostic useable on Army Gold Master (AGM) GCSS-Army devices and should be extendable to other industry standard operating systems.

2.3 Follow-on Initiatives: The Army will continue with necessary process improvements to their current Enterprise Business Systems (EBS) portfolio to maintain the Warfighters’ capabilities’ operational effectiveness. That is the principal reason for pursuing this disconnected solution. However, the Army is also prudently begun to plan and develop the next generation of business systems that will optimize the end-to-end process and converge functional capabilities from national to tactical. With that in mind, the disconnected solution’s https://armypubs.army.mil/ https://armypubs.army.mil/ProductMaps/PubForm/ATP.aspx design and technical architecture should be based on common industry standards that may be extensible to the planned future Army converged solution with minimal rework. Be extensible to the planned future Army converged ERP with minimal rework.

3.0 Prototype Solution to Meet the Gap: The Army intends to pursue a prototyping strategy among qualified vendors to identify solutions that can address the GCSS-Army disconnected capability requirement gap. While the disconnected capability is essential for battlefield operations, there may be situations requiring Users at home station or in non-deployed status to operate on occasion in a DIL environment. Policies and procedures will be developed for operating in an off-line mode.

Figure 4: GCSS-Army Disconnected Operations Prototype (Non-Aviation)

3.1 For this Disconnected Operations Solution CONOPs, the focus is from Brigade Support Battalion (BSB)4 perspective and limited to non-aviation maintenance operations, warehouse management, unit supply, property accountability, and the supporting business processes. The capabilities required for aviation disconnected operations are currently being satisfied with the GCSS-Army Aircraft Notebook (ACN) solution.

4 See Army Technical Publication, ATP 4-90, dated 19 June 2020

3.2 Prototype Solution must be able to demonstrate the following summarized capabilities on Government Furnished Equipment (representative of fielded Tablets and Laptops) designated as Disconnected-Enabled Devices (DEDs).

Figure 5: GCSS-Army Disconnected Enabled Devices (DEDs)

4.0 Disconnected Prototype Capabilities: During Prototype demonstration, requirements described in the Performance Work Statement [To Be Published] include those Mission Critical Functions for Supply Support, Property Book, Unit Supply Activities (including the associated Human Resource functions) shall demonstrate on Government Furnished Equipment device(s).

4.1 The following Disconnected Operations Scenarios will be used to demonstrate the capabilities:

a) User Set Up and Initial Synchronization

b) Execute Standard GCSS-Army Maintenance Activities

c) Record Equipment Dispatch

d) Provide Dashboard Data

e) Execute Warehouse Management Activities

f) Execute Unit Supply Management Activities

g) Execute Property Book Management Activities

h) Execute Access Administrator Activities.

4.1.1 User Set Up and Initial Synchronization:

a) Conduct End-user training to operate the Disconnected-Enabled Device (DED)

b) Load/activate Unit Organization data on the DED (at HQ – Sustainment Tech)

c) Assign user roles & authorizations on DED (At Unit – Access Administrator)

d) Load/activate Mission Critical Functions and Unit Platform/Weapon Configurations on DED (at HQ – Sustainment Tech)

e) Load/activate Mission Critical Master Data on DED (at HQ – Sustainment Tech)

f) Define relevant Unit DED Mission Essential Equipment List (MEEL) (at Unit – Commander/Property Book Office (PBO)/Maintenance Supervisor roles)

g) Provision Headquarters local server(s) to communicate with the DEDs (at Unit – Sustainment Automation Support Management Office (SASMO))

h) Establish a connection with the Combat Service Support Automated Information Systems Interface (CAISI) Very Small Aperture Terminal (VSAT) (at Unit – SASMO)

i) Perform initial connection Synchronization to a GCSS-Army ECC Server

j) Capture work-in-progress and enter in (DED) – (At Unit – ERPS Clerk)

k) Synchronize and Check Error Log– (at Unit - SASMO/Maintenance role)

l) Fix any local errors– (at Unit)

m) Release DED for normal disconnected operation of Mission Critical Functions (At Unit – Commander /Maintenance Supervisor roles)

n) Verify Synchronized data at the GCSS-Army ECC Server and resolve any errors (at HQ – Sustainment Tech role).

4.1.2 Execute Standard GCSS-Army Maintenance Activities:

a) Mechanic conducts manual Inspection for fault or planned maintenance (manual / paper process)

b) Mechanic complete paper documentation and delivers to ERPS Clerk with DED

c) ERPS Clerk creates Notification assigned to mechanic

d) Maintenance Supervisor verifies and sets equipment status

e) ERPS clerk either closes Notification or Converts it to a Work Order and creates or copies a task list

f) ERP clerk/Maintenance Supervisor assigns work and schedules, or if required, documents the transfer (evacuation) of the system or components to higher level maintenance

g) ERPS Clerk requisitions necessary part(s) from Shop Stock (SS) or Supply support Activity (SSA) if not in SSA

h) SSA or SS issue parts, decrement inventory, or backorder from higher supply chain node

i) Special tools required are identified and reserved

j) Mechanic notified and executes task list; additional faults identified can be added

k) Mechanic Task List Operations capture time, serial numbers/Item Unique Item Identification (IUIDs) Codes for installed and dismantled parts, and completion confirmation manually documented and returned to clerk

l) Supervisor and Clerk verify work and technically complete work order with costs captured

m) Supervisor or Clerk:

i) Update equipment status and documents the return of un-repairable /carcasses for recoverable parts to the Supply SSA

ii) Update equipment configuration (internal on DED and with sync)

iii) Update the Property Book (internal on DED and with sync)

iv) Connect to the GCSS-Army ECC Server with CAISI VSAT or other method to conduct sync and validate that all transactions, including Cost data transfer with sync.

4.1.3 Record Equipment Dispatch:

a) Identify available mission capable equipment

b) Verify Operator/Driver data

c) Assign Equipment by Serial Number and/or Bumper Number

d) Issue to Individual

e) Capture Measurements (e.g. Miles/Hours/Vibrations as defined by platform)

f) Dispatcher reports platform faults to Mechanic.

4.1.4 Provide Dashboard Data:

a) Readiness Status

b) Maintenance Schedule and Plans

c) Authorized-Actual Reports (Property Book impacts)

d) Inventory Reports (Supply Status).

4.1.5 Execute Warehouse Management Activities – Supply Support Activities (SSA):

a) Establish required lock out for selected SSA deployed inventory to prevent material movements to facilitate stock management while deployed disconnected status

b) SSA Clerk and Manager will continue to perform Inventory Management (IM) functions, but not automated Warehouse Management (WM) functions, while disconnected

c) SSA Managers, access dashboards that populate disconnected information on inbound deliveries, stock requirements list for SSA management and planning, to include view of material master records transactions/movement, Stock Requirements List and parts order information:

i) Current stock overview requirements and availability by material, equipment, Serial Number or batch added while disconnected

ii) Stock overview requirements and availability of material, equipment, Serial Number or batch added while disconnected

iii) Stock overview requirements an availability of material, equipment, Serial Number, or batch changed while disconnected

d) SSA Clerks create inspection lots, record inspections and make usage decisions while disconnected

e) Manage returns of accountable N/S parts categorize as Red (Overdue) Yellow (almost due) and Green (already returned)

f) SSA Clerks create Purchase Requisitions in preparation for re-established back end connection and processing, but limited to only display of Purchase Orders

g) SSA Clerks continuer to initiate the creation/updates/deletions of shipments from SSA to SSA / SSA to National that will be executed when connectivity is re-established.

4.1.6 Execute Unit Supply Activities:

a) Unit Supply Clerks/Managers, access dashboards that populate disconnected information on Unit Supply and Property and have ability to display the following:

i) Current stock overview requirements and availability by material, equipment, Serial Number or batch added while disconnected

ii) Stock overview requirements and availability of material, equipment, Serial Number or batch added while disconnected

iii) Stock overview requirements an availability of material, equipment, Serial Number or batch changed while disconnected.

b) Unit Supply Clerk will manage property accountability – display and track current Hand-Receipts/loans and create/update Hand-Receipt/loans issue/returns of Unity property

c) Unit Supply Clerk will create and execute Property Inventory

d) Unit Supply clerk prepares new Purchase Requisitions that will be processed on connectivity is re-established

e) Unit Supply clerk continues to manage requisitions received by creating Goods Receipts but only display Inbound Deliveries

f) Unit Supply clerk/supervisor create inspection lots, record inspections and make usage decisions while disconnected.

4.1.7 Execute Property Accountability Activities – Property Book Office (PBO):

a) PBO Officer maintains accountability for all assigned property during deployment operations and while disconnected, including during planned blackout periods

b) PBO will manage current property status and track hand-receipts between units/users

c) PBO conducts equipment transfers of equipment laterally within their units (e.g.

goods movement within same Brigade Force Element)

d) PBO creates/trigger limited inventory counts from unit(s) while disconnected, including personal materials and equipment (e.g. "sub-sub Hand Receipt"=Personal functional Equipment):

i) Create limited inventory counts from unit while disconnected

ii) Prepare/create updates based on inventory counts to be process once connectivity is re-established.

4.1.8 Execute Access Administrator Activities:

a) GCSS-Army decentralized/Unit Access Administrators will manage system access through position assignments. Positions based assigned provide Users with Role/Attribute-based access controls that been created for the User groups.

b) Access Administrator should be able to assigned/transfer existing personnel to a role position.

4.2. Disconnected Operations Solution Technical and Security Requirements

4.2.1. A modern web-based intuitive user interface based on Human-Centered Design methodology that enables access and/or launches access through all modern Army approved browser and devices (desktop, laptop). The interface will allow users to perform their assigned roles in established and limited user-configurable: displays, workflows, tools, and data sets:

4.2.1.1. The solution must build upon an intuitive User Experience view having all the screens in a common industry standard format, such as User Interface (UI) 5 format.

4.2.1.2 Solution should provide the ability to connect to supported embedded training and other training products and have a UI with the extensible capability to connect to the non-SAP applications.

4.2.1.3 Ability to achieve an Authority to Operate on Non-Classified Internet Protocol Router Network (NIPRNet).

4.2.1.4 Operate in a Disconnected Mode for up to seven (7) continuous days (168 hours) and connect over a CAISI / VSAT Network to complete the synchronization of transactions and data with designated GCSS-Army ECC Server(s).

4.2.1.5 The ability to deploy with device-agnostic software employable on Government Furnished Equipment.

4.2.1.6 Demonstrate a low-code/no-code Module Open Systems Architecture (MOSA) that the Army can sustain and carry forward into the future planned ERP system convergence.

4.2.2 ECC Synchronization and Trap Errors tracking: The Disconnected Solution must have the ability to perform frequent automatic synchronization to the GCSS-Army ECC (enterprise system) while connected to ensure the device software has the most current data available before connectivity disruptions. Synchronization status must be clearly tracked along with errors and a remediation process that is intuitive and handle at the lowest level possible.

4.2.2.1 Reprocess or fix DED (internal records) errors.

4.2.2.2 Reprocess or fix any sync errors with the GCSS-Army ECC Server(s).

4.2.3 To meet technical compliance requirements for cybersecurity in accordance with DoD RMF the Solution must meet and the following:

4.2.3.1 Provide a Multi-Factor (Two-Factor) Authentication (e.g., enterprise LDAP, X.509 PKI, Active Directory, Etc.) as well as Single Sign-On (SSO) capabilities using the Army’s Identity and Access Management (IdAM) capability, Enterprise Access Management Service – Army

(EAMS-A).

4.2.3.2 Protect data at rest and in transit using Federal Information Processing Standards (FIPS) 140-2 approved and validated algorithms for encryption, hashing, and signing (e.g., full disk encryption, Kerberos).

4.2.3.3 The ability to achieve and maintain an Interim Authority to Test (IATT) on DoD NIPRNet for the prototype effort duration.

4.2.3.4 The ability to meet the DOD RMF accreditation requirements for an Authorization to Operate (ATO) on DoD NIPRNet and with a DoD approved Cloud at Impact Level (IL) 4/5.

4.2.4 Other Non-Technical Requirements

4.2.4.1 The Solution User Interface must be intuitive enough to eliminate formal classroom training and minimize standard over-the-shoulder training requirements.

4.2.2.2 The Solution must be affordable for the deployment to the Sustainment Enterprise consisting of over ~70,000+ total active system users (estimated at this time).