Rqmnt_Statement_of_Need_GCSS-Army_DISCOPS_2021_03_23.pdf

Statement of Need (SoN): GCSS-Army Disconnected Operations Solution (DISCOPS) Solicitation Version 1.0, 23 March 2021

Statement of Need (SoN):

Global Combat Support System – Army (GCSS-Army) Disconnected Operations Solution (DISCOPS)

Prototype Project

Solicitation Number: W15QKN-21-R-0G91

Distribution Statement A. Approved for public release: distribution unlimited.

SoN: GCSS-Army (DISCOPS) Prototype i Distribution A. Approved for public release:

distribution unlimited.

Table of Contents

SECTION 1 – EXECUTIVE SUMMARY

1.1. Purpose & Authority

1.2. Background

SECTION 2 – DESCRIPTION OF THE REQUIREMENT

2.1. The Requirement

2.2. The “as is” Environment

2.3. The “to-be” Environment

SECTION 3 – PROTOTYPE CAPABILITY REQUIREMENTS

3.1. The Overarching Prototype Project Objectives

3.2. Disconnected Operations Solution Scenarios

3.3. Disconnected Operations Solution Phases

3.4. Follow-on Production

SECTION 4 – ENCLOSURES and REFERENCES

4.1. Enclosures

4.2. References:

SECTION 5 – DEFINITION of Commercially Available

SoN: GCSS-Army DISCOPS Prototype

Page 1 Distribution A. Approved for public release:

SECTION 1 – EXECUTIVE SUMMARY

1.1. Purpose & Authority1

The purpose of this Statement of Need is to communicate to Industry the requirement to be pursued under one (1) or multiple Other Transaction Authority (OTA) Agreements under the authority of 10 U.S.C. § 2371b, with each Awardee implementing an approach using a commercially available solution(s) to demonstrate a Global Combat Support System – Army (GCSS-Army) Disconnected Operations Solution (DISCOPS) Prototype capability. [See Section 5 for the definition of “commercially available”]

1.1.1 The U.S. Army is seeking prototype(s) of commercially available software solution(s), including low-code/no-code solution(s). This solution must be able to operate in a co-located environment with the Enterprise Resource Planning (ERP) Central Component (ECC) with the integrated application(s) that provide the Army Users with maximum configurability and minimal customization. Any Cloud-based Disconnected Operations Solution would be expected to integrate with the GCSS-Army ECC. Proposed solution(s) should provide an architecture that will allow the Army to transition this solution into the future Enterprise Business System - Convergence Platform.

1.2. Background

1.2.1 GCSS-Army is the U.S. Army’s SAP™ Enterprise Resource Planning (ERP) solution for automating and streamlining its tactical and non-tactical logistics activities in support of Active Army, National Guard, and the U.S. Army Reserve Components. It provides timely and accurate visibility and accountability of materiel across the Army Logistics Enterprise.

GCSS-Army integrates tactical logistics enterprise information for leaders and decision-makers to provide a single maneuver sustainment picture to manage combat power by tracking supplies, spare parts, organizational equipment, unit maintenance, the total cost of ownership, and other financial transactions related to logistics for all Army units.

1.2.2 GCSS-Army is the largest implementation of SAP’s Defense Forces Public Security (DFPS) module in the world that allows for military force structure and task force organization.

The system utilizes web-based capabilities to provide personnel data management, user access (using Common Access Card (CAC) credentials) to role-based information and exchange operational data related to tactical maintenance, materiel management, property accountability, tactical financials, and other related sustainment functional areas. GCSS- Army is critical for an Army in motion. To improve our Soldiers’ warfighting superiority in supply chain functions, the program must extend key functions to users with limited to no network connectivity efficiently and effectively. The main focus for this effort will be to provide a Disconnected Operations Solution addressing maintenance of all Army equipment other than that currently supported by the Aviation solution.

1 For additional information on Other Transactions, please refer to the Department of Defense (DoD), Other Transactions Guide, Version 1.0, dated November 2018 https://www.dau.edu/guidebooks/Shared%20Documents/Other%20Transactions%20(OT)%20Guide.pdf https://www.dau.edu/guidebooks/Shared%20Documents/Other%20Transactions%20(OT)%20Guide.pdf

Page 2 Distribution A. Approved for public release:

SECTION 2 – DESCRIPTION OF THE REQUIREMENT

2.1. The Requirement

The Army is seeking a commercially available software solution(s), including low-code/no-code solutions, which allows GCSS-Army users to perform mission-critical functions in a disconnected, intermittent, and limited bandwidth (DIL) operational environment with an effective, efficient, and modern user experience that is intuitive and interactive in nature.

2.2. The “as is” Environment

GCSS-Army (non-Aviation) currently does not include a capability to operate disconnected, and therefore, Soldiers implement manual processes during times of system outages. See the current GCSS-Army Enterprise Tactical Operational View in Figure 1.

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

GCSS-Army is currently moving incrementally to an improved User Experience (UX) based on the SAP™ User Interface 5 (UI5) standard applications in conjunction with its current Enterprise Resource Planning (ERP) system.

Page 3 Distribution A. Approved for public release:

2.3. The “to-be” Environment

GCSS-Army users require an ability to process transactions (end state) across all business areas and selected Mission Critical Functions (MCF) that are needed to operate up to seven

(7) continuous days on the battlefield while in a disconnected mode.

2.3.1 Overarching Objectives:

The U.S. Army is seeking a prototype(s) of commercially available software solution(s), with minimal customization requirements, which will enable the currently fielded hardware to conduct mission-critical logistics functions in off-line mode while disconnected from the GCSS-Army ERP ECC Server for up to seven (7) continuous days. The solution must transmit the results of transactions recorded while disconnected to synchronize to the GCSS- Army ECC landscape when connectivity is restored. The transactional data includes the necessary financial triggers the GCSS-Army ECC Server needs to financially close out some transactions. Similarly, GCSS- Army ECC Server master data, documents, and transactions relative to a disconnected organization must be kept synchronized when connectivity is restored. Authorized sustainment personnel must be able to operate and sustain proposed client software. Disconnected Operations Solution requires all the screens to be in a common industry standard, such as UI5 format.

2.3.1.1 The GCSS-Army DISCOPS Prototype Solution Software will demonstrate a select number of Army designated Maintenance-related processes, with sufficient supporting functions (Property Accountability, Data Management, Unit Supply, Equipment Management, DFPS Organizational Structure and associated Human Resources and Roles & Authorizations Management, and Status Reporting) to support the end-to-end business process(es). The following are the requirements and provide the context for an envisioned disconnected solution that will be assessed as part of the prototype efforts. See Figure 2:

GCSS-Army Disconnected Operations OTA Phase 1 End-to-End Prototype.

2.3.2 Functional Capabilities: Users [Military, Government Civilians and Contractors] need to be able to perform the identified MCFs (Enc. B) 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) Planned and unplanned disconnected capabilities.

c) Operate up to seven (7) continuous days (168 hours) while disconnected in a Multi-

Domain Operations environment.

d) Solution must be able to interface and synchronize to current and future SAP ERPs utilizing, but not limited to: SAP Work Manager™ framework SAP Mobilink™, NetWeaver Gateway™, for Army Ground, Missile, Watercraft, and Aviation platforms.

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

2.3.3 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-

Page 4 Distribution A. Approved for public release:

critical functions. (See Enclosure B – GCSS-Army DISCOPS Requirements Traceability Matrix)

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

2.3.3.2 During the Prototype Phase 1 and Phase 2 demonstration evaluations and the Phase 3 integration assessment, the solutions will be assessed for simplicity of design, intuitiveness, and usability.

2.3.3.3 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 imaged devices and should be extendable to other industry standard operating systems.

Figure 2: GCSS-Army Disconnected Operations OTA Phase 1 End-to-End Prototype

Page 5 Distribution A. Approved for public release:

2.3.4 Follow-on Initiatives: The Army will continue with necessary process improvements to their current Enterprise Business Systems (EBS) portfolio to maintain the operational effectiveness of the Warfighters’ capabilities. That is the principal reason for pursuing this disconnected solution. However, the Army has 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 GCSS-Army DISCOPS Prototype Software solution’s design and technical architecture should be based on common industry standards that should be extensible to the planned future Army converged solution with minimal rework. The future requirements are still being defined under the Army’s Enterprise Business Systems – Convergence (EBS-C) Product Lead, within the Program Executive Office Enterprise Information Systems (PEO EIS). The EBS-C effort is challenged to deliver a converged, single enterprise resource planning (ERP) system that manages acquisition, human resources, logistics, financial, environmental, and training and readiness enterprises. Information on the Army converged solution can be located here:

https://www.eis.army.mil/newsroom/news/data/army-hosts-industry-day-talk-enterprise-business-systems-convergence.

SECTION 3 – PROTOTYPE CAPABILITY REQUIREMENTS

3.1. The Overarching Prototype Project Objectives

In addition to the described objectives in para. 2.3.1, the GCSS-Army DISCOPS Prototype Software must demonstrate the following summarized capabilities on Government Furnished Equipment (representative of fielded Tablets and Laptops) designated as “Disconnected- Enabled Devices” (DEDs).

3.2. Disconnected Operations Solution Scenarios

3.2.1 The GCSS-Army DISCOPS Prototype Software initially must be able to demonstrate the Disconnected Software Solution on stand-alone or on a closed Network, (not on an Army Network), employed on Government Furnished Equipment device(s) to meet the following Maintenance Disconnected Operations Scenarios (see Enclosure A for more details):

f) User Set Up and Initial Synchronization

g) Execute Standard GCSS-Army Maintenance Activities

h) Record Equipment Dispatch

i) Provide Dashboard Data

j) Execute Warehouse Management Activities

k) Execute Unit Supply Management Activities

l) Execute Property Book Management Activities

m) Execute Access Administrator Activities.

3.3. Disconnected Operations Solution Prototype Phases

There are Six Steps in this Disconnected Operations Solution Prototype Project that permit industry to demonstrate technology (software) solutions that mature over time.

3.3.1 Step 1 – Offerors respond to the Prototype Project Opportunity Notice (PPON):

https://www.eis.army.mil/newsroom/news/data/army-hosts-industry-day-talk-enterprise-business-systems-convergence https://www.eis.army.mil/newsroom/news/data/army-hosts-industry-day-talk-enterprise-business-systems-convergence

Page 6 Distribution A. Approved for public release:

Conduct an Oral Presentation and Technology Demonstration #1 using Corporate and or Public Data. Upward Invitation #1 to Step 2 will include an updated PPON and the Performance Work Statement (PWS). The Government will provide written notice of Upward Invitation or Non-Selection at the conclusion of each Step.

3.3.2 Step 2 – Offerors respond to Upward Invite #1: Submit a Written Proposal in response to the PWS.

3.3.3 Step 3 – Agreement Awards for Phase 1 Prototype Development: made to one or multiple Prime Offeror(s).

3.3.4 Step 4 – Phase 1 Prototype Development and conduct Technology Demonstration #2, with an estimated Period of Performance not to exceed seven months.

3.3.5 Step 5 – Phase 2 Prototype Development and conduct Technology Demonstration #3, with an estimated Period of Performance not to exceed nine months.

3.3.6 Step 6 – Phase 3 Prototype Integration Assessment with a Period of Performance not to exceed two months.

3.4. Follow-on Production

In accordance with 10 U.S.C. § 2371b(f), this competitively awarded Agreement may lead to follow-on production activities if the Key Technical Goals and the Success Metrics, as defined in the Performance Work Statement (PWS), [The Government reserves the right to update the PWS published with Upward Invite #1] are met; or if a particularly favorable, or unexpected result is accomplished that justifies transition to production. The Government will determine if this award will be a follow-on Production OT Agreement or a Federal Acquisition Regulation (FAR) Contract to support approximately 70,000 users.

SECTION 4 – ENCLOSURES and REFERENCES

4.1. Enclosures

The following enclosures to this Statement of Need are provided by the Government to define the requirement:

A – GCSS-Army Disconnected Concept of Operations (CONOPs) B – GCSS-Army DISCOPS Requirements Traceability Matrix C – GCSS-Army Hardware Specification for Tactical Enterprise Logistics Systems (TELS) Program D – Operational View 6 Diagrams E - – Instructions for Government Furnished Equipment (GFE) & Applied Research Lab (ARL), marked as CUI (required DD Form 2345 to access).

4.2. References:

The below cited references include a summary statement for the document’s application to

Page 7 Distribution A. Approved for public release:

this Statement of Need. The links provided are publicly accessible.

4.2.1 DoD Instruction 8500.01, Cybersecurity, dated 14 March 2014, Incorporating Change 1, 7 October 2019. This DoD Instruction establishes a DoD cybersecurity program to protect and defend DoD information and information technology (IT). Available at:

https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/850001_2014.pdf?ver=20 19-10-07-112048-860

4.2.2 DoD Instruction 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), dated 12 March 2014, Incorporating Change 2, 28 July 2017. This DoD Instruction reissues and renames DoD Instruction (DoDI) 8510.01, Implements References by establishing the RMF (Risk Management Framework) for DoD IT (Information Technology) establishes associated cybersecurity policy, and assigns responsibilities for executing and maintaining the RMF. Available at:

https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/851001p.pdf?ver=2019- 02-26-101520-300

4.2.3 DoD Cloud Computing Security Requirements Guide, Version 1, Release 3, dated 6 March 2017. This DoD Guide outlines the security model by which DoD will leverage cloud computing along with the security controls and requirements necessary for using cloud-based solutions. It defines the Impact Levels 2, 4, 5, and 6. It applies to DoD provided cloud services and those provided by a contractor on behalf of the Department.

Available at:

https://dl.dod.cyber.mil/wp-content/uploads/cloud/pdf/Cloud_Computing_SRG_v1r3.pdf

4.2.4 Army Regulation 700-127 Integrated Product Support, dated 22 October 2018.

Provides DA policy for implementing performance-based life cycle product support, including performance-based logistics, through the Army’s Integrated Product Support (IPS) Program.

IPS process uses 12 IPS elements to facilitate development and integration of the key product support activities required to acquire, test, field, and support Army materiel and software. Available at:

https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN7460_R700_127_FINAL.pdf

4.2.5 Army Regulation 750-1 Army Materiel Maintenance Policy, dated 28 October 2019. This Army Regulation provides the Department of the Army policy for general maintenance operations; commodity-oriented maintenance operations; maintenance management systems; and more. It applies to the Regular Army, the Army National Guard/Army National Guard of the United States, and the U.S. Army Reserve. Available at:

https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN13933_AR750-1_FINAL.pdf

4.2.6 Field Manual 4-0 Sustainment Operations, dated 31 July 2019. This Field Manual provides the context for the variety of Operational Environments (OE) where Army Logistic Units must be able to perform sustainment functions. Available at:

https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN19602_FM%204- 0%20FINAL%20WEB%20v2.pdf https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/850001_2014.pdf?ver=2019-10-07-112048-860 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/850001_2014.pdf?ver=2019-10-07-112048-860 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/851001p.pdf?ver=2019-02-26-101520-300 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/851001p.pdf?ver=2019-02-26-101520-300 https://dl.dod.cyber.mil/wp-content/uploads/cloud/pdf/Cloud_Computing_SRG_v1r3.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN7460_R700_127_FINAL.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN13933_AR750-1_FINAL.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN19602_FM%204-0%20FINAL%20WEB%20v2.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN19602_FM%204-0%20FINAL%20WEB%20v2.pdf

Page 8 Distribution A. Approved for public release:

4.2.7 Department of the Army Pamphlet 750-8 The Army Maintenance Management System (TAMMS) Users Manual, dated 22 August 2005. This DA Pamphlet provides the processes, preparation, and management of forms, records, and data required to manage maintenance, control use, report deficiencies, document warranty actions, document equipment modifications; report equipment improvement recommendations; and report quality deficiency reports. It includes the DA Form 2400 Series and others. Available at:

https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/p750_8.pdf

4.2.8 Army Techniques Publication No. 4-0.6 (ATP 4-0.6) Techniques for Sustainment Information Systems Support, dated 5 April 2013. This document provides comprehensive information on all aspects of sustainment information systems support from the strategic to the tactical level. Support organizations, sustainment systems overview, system maintenance, support personnel training and security procedures are outlined. It introduces the Sustainment Automation Support Management Office (SASMO).

Available at:

https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN3697_ATP%204- 93x1%20FINAL%20WEB.pdf

4.2.9 Army Techniques Publication No. 4-93 (ATP 4-93) Sustainment Brigade, dated 19 April 2016. This document provides doctrine describing the capabilities, organization, and operations of the sustainment brigade and its subordinate units, to include the SASMO.

Available at:

https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ATP%204- 93%20FINAL%20WEB.pdf

4.2.10 Army Techniques Publication No. 4-93.1 (ATP 4-93.1) Combat Sustainment Battalion, dated 19 June 2017. This document provides doctrine describing the capabilities, organization, and operations of the combat sustainment support battalion headquarters and its subordinate units, to include the SASMO. Available at:

https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN3697_ATP%204- 93x1%20FINAL%20WEB.pdf

4.2.11 How the Army Runs – A Senior Leader Reference Handbook, 2019-2020, dated 29 January 2020, available on-line 4 May 2020. This 560 page Handbook published periodically by the US Army War College. Chapter 22 “Emerging Initiative: Global Force Information Management” introduces and provides the context for the terms “Army at Rest” and “Army in Motion” where an Army in Motion means an operationally committed Army element down to the individual billet (Soldier) level. Available at:

https://ssl.armywarcollege.edu/DCLM/pubs/HTAR.pdf

SECTION 5 – DEFINITION of Commercially Available

5.1. The solution must be capable of achieving Federal Cybersecurity compliance https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/p750_8.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN3697_ATP%204-93x1%20FINAL%20WEB.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN3697_ATP%204-93x1%20FINAL%20WEB.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ATP%204-93%20FINAL%20WEB.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ATP%204-93%20FINAL%20WEB.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN3697_ATP%204-93x1%20FINAL%20WEB.pdf https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN3697_ATP%204-93x1%20FINAL%20WEB.pdf https://ssl.armywarcollege.edu/DCLM/pubs/HTAR.pdf

Page 9 Distribution A. Approved for public release:

standards. The product(s) within the solution shall be commercially available, demonstrable and take into consideration existing Army commercial software license investments to the greatest extent possible.

5.2. For the GCSS-Army DISCOPS Prototype Project, the term "commercially available" is a compilation of three definitions listed here:

"Commercial component'' means any component that is a commercial item.

"Commercial computer software" means any computer software that is a commercial item.

"Commercial item” means –

(1) any item, other than real property, that is of a type customarily used by the general public or by non-governmental entities for purposes other than governmental purposes, and-

(i) Has been sold, leased, or licensed to the general public; or

(ii) Has been offered for sale, lease, or license to the general public.

(2) Any item that evolved from an item described in paragraph (1) of this definition through advances in technology or performance and that is not yet available in the commercial marketplace but will be available in the commercial marketplace in time to satisfy the delivery requirements under a Government solicitation.

(3) Any item that would satisfy a criterion expressed in paragraphs (1) or (2) of this definition, but for-

(i) Modifications of a type customarily available in the commercial marketplace; or

(ii) Minor modifications of a type not customarily available in the commercial marketplace made to meet Federal Government requirements. Minor modifications mean modifications that do not significantly alter the nongovernmental function or essential physical characteristics of an item or component or change the purpose of a process. Factors to be considered in determining whether a modification is minor include the value and size of the modification and the comparative value and size of the final product. Dollar values and percentages may be used as guideposts but are not conclusive evidence that a modification is minor.

(4) Any combination of items meeting the requirements of paragraphs (1), (2), (3), or

(5) of this definition that are of a type customarily combined and sold in combination to the general public.

(5) A non-developmental item, if the procuring agency determines the item was developed exclusively at private expense and sold in substantial quantities, on a competitive basis, to multiple State and Local governments.

(6) Services are neither considered included or excluded for this definition, any interpretation including Services must be presented by the Offeror with supporting rationale.

*** END OF STATEMENT OF NEED: GCSS-Army DISCOPS Prototype ***

SECTION 5 – DEFINITION of Commercially Available