Attachment_2H_-_2025_Notional_Scope_Descriptions_1.pdf

2025 Notional Scope Descriptions

Business Integration Office 2/11/2025

FY 2025 Scope and Initiatives

Title Description

G-Invoicing (Phase 2/Post Go-live Work)

G-Invoicing phase 2 encompasses post go-live user support and defect resolution, process and system stabilization. In addition, scope will analyze functionality included in the initial delivery of the G-Invoicing product, and not included at go-live of FBMS S4HANA. Lastly, BIO will migrate to SAP S4HANA 2023. Known scope includes but is not limited to:

• year end processes

• additional functionality

• seller facilitated orders

• constructive order acceptance

• 7600 EZ

• processes across DOI not included in the initial go-live

Phase 2 will also include continued collaboration with SAP, Treasury, other SAP agencies, DOI Policy Offices, and Bureaus on directives impacting functionality.

Title Description

ETSNext Implementation The current electronic travel system (ETS) contract, ETS2, expires on June 3, 2027.

With the upcoming iteration of the contract, ETSNext, GSA is enforcing standard data elements and processes across government agencies which are part of the Federal Integrated Business Framework (FIBF) and are endorsed by the Senior Travel Official Council (STOC) and Office of Management and Budget (OMB). These standards will impact DOI business processes and integrations between FBMS and the travel system.

Evaluate the standard data elements and interface requirements to identify technical, business process, and policy gaps and opportunities for improvement. Develop business process solutions to accommodate the standards and improve overall risk and reporting. In partnership with PFM, participate in contract and task order feedback and vendor evaluations to ensure Department requirements are accounted for where possible. Develop technical and reporting solutions to accommodate the new or changed travel system and processes. Facilitate bureau testing, including test script development, coordination of testing event(s), evaluation of defects, and coordination of resolution with the vendor. Provide change management support.

Develop training strategy, training materials, and support end user training. Develop a solution for storing and making ETS2 legacy data available.

Title Description

SFFAS 54 - Lease Accounting SFFAS (Statement of Federal Financial Accounting Standards) 54 revises the financial reporting standards for federal lease accounting.

Move to the newest lease accounting standards to recognize federal lease activities in the reporting entity’s general purpose federal financial reports and includes appropriate disclosures.

Title Description

BTP (Phases 1 and 2) SAP Business Technology Platform (SAP BTP) is the technological foundation for all SAP applications and the Intelligent Enterprise. SAP’s stated replacement for the Enterprise Portal is built upon BTP services and a cloud product called SAP Build Work Zone, advanced edition. The replacement for PI is also built upon BTP services and a product called the Integration Suite.

BTP provides not just a replacement for these components but a modern infrastructure with more features and opportunities for FBMS. SAP BTP brings together application development, data analytics, integration, and AI capabilities into one unified environment optimized for SAP applications.

BTP will be the core platform for several intiatives that the BIO is considering: Portal & PI Replacement, UX improvements, DevOps (automation & integration improvements), Engagement Layer (low code/no code, automation), Clean Core and Analytics.

Phase 1 is project prep and exploration. Phase 2 is implementation.

Title Description

Cyber ZTA Data Masking Cyber Zero Trust Architecture (ZTA) - Pathlock Data Masking (Data) deployment and configuration of the Pathlock Dynamic Access Controls software solution for FBMS.

This tool introduces the concept of Attribute Based Access Controls in conjunction with data masking. With S4 there are limitations with our ability to restrict access to certain PII data using standard role based access control. This tool will add an additional layer of granularity and will allow us to restrict access to PII (thru masking) to only those FBMS users who need it. In addition to the installation/deployment of the tool, we will undertake our first use case for masking PII data as part off this project.

Use Case #1 - Develop a masking policy for use with the BPI transactions and apps to further restrict visibility to customer/vendor/employee SSNs and Banking details.

Use Case #2 - Develop a masking policy associated with Charge Card data.

Additional use cases may be explored depending on complexity and need.

Title Description

ECC Data Retention Solution Scope includes a solution to archive and view the ECC data and associated attachments. The new solution will archive ALL the data in SAP ECC allowing the data and associated attachments to be readily accessible via an archive viewer front end tool. Upon successful completion of this solution DOI will decommission the SAP ECC SoH system.

PRISM Upgrade System upgrade to the DOI contract writing solution. The upgrade would entail development, configuration, testing, and training.

Tableau Upgrade System upgrade to the Tableau reporting tool. The upgrade would entail development, configuration, testing, and training.

Title Description

S4HANA 2023 Upgrade Upgrade to SAP S4HANA 2023 which supports the DOI financial management system: FBMS and G-Invoicing functionality. The upgrade would entail development, configuration, testing, and training.

Technical Upgrades and Maintenance

Backend system upgrades to newer versions and/or patches. This bucket of work is critical to maintain our technical currency in support of FBMS and help DOI maintain pace with current vendor releases allowing for latest functionality and security.

UI Path Cloud Migration & Hypercare UiPath achieved FEDRAMP certification in 2024 and they no longer supporting non-cloud capabilities and providing new capabilities only through their cloud platform.

This migration is mandatory to align with the vendor solution.