Draft_BIO_and_FBMS_Support_Services_IDIQ_PWS_2.docx

U.S. Department of the Interior Solicitation No. X – Attachment 1 DRAFT U.S. Department of the Interior Attachment 1 – BIO and FBMS Support Services IDIQ PWS DRAFT DRAFT: BIO and FBMS SUPPORT SERVICES IDIQ PWS Business Integration Office (BIO) and Financial and Business Management System (FBMS) Support Services Indefinite Delivery, Indefinite Quantity (IDIQ) Performance Work Statement (PWS) March 7, 2025

Table of Contents

List of Tables

Background and Objective

This Performance Work Statement (PWS) specifies critical support services required by the U.S. Department of the Interior (DOI) to support the Business Integration Office (BIO) and the management of DOI’s Financial and Business Management System (FBMS). Task orders issued under this Indefinite Delivery, Indefinite Quantity (IDIQ) contract will be relevant to the BIO in supporting the bureau or Departmental offices.

The BIO is responsible for the management, continued development, and operations and maintenance of FBMS and the support of the business community utilizing the system across all of DOI. The BIO is an office under the Deputy Assistant Secretary for Budget, Finance, Grants and Acquisition (DAS-BFGA) within the Office of Policy, Management and Budget (PMB). PMB is an office located within DOI’s Office of the Secretary (OS).

FBMS is the cornerstone of a fully integrated business management system, supporting DOI as a world-class organization acknowledged for management excellence and effective mission delivery. As a High Value Asset (HVA) it is critical to the DOI’s financial management modernization strategy and to meeting future business needs. FBMS is designed to incorporate the majority of DOI’s financial and business management functions into one system. The financials area of FBMS is based on commercial off-the-shelf (COTS) software applications that include a variety of SAP solutions (S4HANA, BI, BOBJ, BPC, BTP, GRC, Enterprise Portal, Fiori, SLD, Solution Manager, MDG). Other systems that make up the FBMS landscape include Unison PRISM for acquisitions, GrantSolutions to manage the financial assistance lifecycle, IBM’s ETSNext solution for government travel, Tableau Server, and OpenText’s document management application. See Figure 4 below, FBMS Application Landscape, for a visual list of systems included under the FBMS umbrella.

DOI strives for the least amount of customization and promotes business process standardization across bureaus. Still, many of our system implementations require some amount of configuration and enhancement or customization. The FBMS custom development objects are listed in Attachment 1B, FBMS Development Objects. This integrated system has led to the decommissioning of 87 DOI and bureau-specific systems and enabled the alignment of a business management system with the DOI’s strategy of modernization, integration, efficiency, accountability, and customer value. The full implementation of FBMS allowed the DOI to realize the benefits of common business processes, a common technology platform, integrated real time data, and improved operational decision making. FBMS achieved the goal of having all of DOI on one system with the last deployment occurring in November 2013 and was recently migrated to the S4HANA platform (version 2022) in October 2024.

The first task order under this IDIQ will be issued by the BIO. Additional task orders for support may be issued by individual DOI bureaus or Departmental Offices. Support for DOI bureaus and offices may include bureau/Department-specific business process documentation, additional guidance, supplemental Work Step Instructions, quick reference guides, reporting and analysis of FBMS data as well as overall user support.

FBMS Overview

FBMS is the administrative backbone for the Department and supports the system requirements of all DOI bureaus for acquisition, budget execution, core finance, financial reporting, fleet management, financial assistance, personal property, real property, as well as business decision reporting and travel management.

The standardization and integration delivered by FBMS facilitates a common approach to financial and business management. As a result, the DOI is positioned to deliver programs and services in a more efficient and effective manner, with greatly improved internal controls. Benefits gained from implementing this suite of applications include:

· Enhanced access to, and sharing of, real-time business information that supports effective business decisions for mission delivery across the DOI, bureaus, and in the field

· More timely business reports that facilitate analysis of core financial, acquisition, financial assistance, and property data

· Retirement of outdated legacy systems that do not comply with current mandates and are no longer supported by their software vendors

· An improved internal control environment with separation of duties and standardized business practices to support the internal controls

· Support for the consolidated financial DOI-wide audit with centrally produced information that can be used by the DOI, the Office of Inspector General, and independent auditor

· Shared expertise across the DOI and the bureaus so knowledge can be leveraged across the entire enterprise

· Development and adoption of shared approaches improving reporting and data management, management of tracking and reporting of administrative efficiencies, and value management

The implementation of FBMS across DOI has allowed the DOI to not only realize the benefits of a fully integrated, secure, modernized, business management system, but to also strengthen the integration and communication across the business management policy communities.

FBMS Deployment History

The DOI’s endeavor to migrate all of its bureaus to a single, integrated business management system and community was an effort that spanned several years. FBMS was incrementally developed, tested and deployed to the DOI user community through a series of eight deployments. The deployment of FBMS to the DOI’s final bureau was completed in November 2013. Nine bureaus and the Departmental Offices are included in FBMS production since November 2013.

The FBMS bureau deployments followed a cyclical development process with each deployment increasing functional scope while transitioning additional bureaus into FBMS. The figure below illustrates the FBMS Deployments though November 2013.

Figure 1: FBMS Deployments

FBMS Accomplishments Post-DOI Deployment

Since the deployment of DOI’s final bureau to FBMS, DOI continues to operate, maintain, optimize, and leverage FBMS under the direction of the BIO. FBMS accomplishments since the final bureau deployment include:

Cloud Migration DOI completed the migration of all FBMS environments to the cloud in Fiscal Year 2015 and then completed another migration of the entire FBMS environments to a more modernized cloud hosting provider in Fiscal Year 2023. This latest migration better enables DOI to leverage the scalability, flexibility, and cost-effectiveness of cloud technology, allowing for improved data accessibility and collaboration across the DOI. By moving to the cloud, FBMS facilitates real-time data processing and analytics, significantly reducing operational silos and promoting a more integrated approach to resource management.

The migration supports compliance with federal cybersecurity standards, ensuring that sensitive information remains protected while benefiting from the innovative capabilities of modern cloud solutions. Overall, the FBMS cloud migration represents a transformative step towards a more efficient and responsive FBMS system and infrastructure.

In-Memory Computing - HANA Over the last 9 years DOI has taken an iterative approach in leveraging In-memory computing with SAP HANA. The first phase, which included the implementation of SAP HANA Accelerator, was completed in Fiscal Year 2016. SAP HANA Accelerator provided a transformational improvement for a select number of real-time operational reports and transactions, greatly increasing the speed and utility of both. The second iteration involved the migration of our Business Warehouse (BW) to HANA which was completed in Fiscal Year 2017. This migration provided yet another transformational improvement for our reports that contain the transactional data by increasing the performance times for the queried data and allowed DOI to work with much larger data sets. The third iteration involved the migration of our ECC transactional system to HANA which was completed in Fiscal Year 2019. This migration significantly improved the performance of the transactional system allowing DOI to close months faster and conduct a year end close in days rather than weeks. The above iterations set the stage for the final steps to fully modernize to the next generation SAP ERP software for FBMS, B4HANA and S4HANA. B4HANA was completed in Fiscal Year 2022 while S4HANA was completed in the first two months of Fiscal Year 2025.

Figure 2: HANA In Memory Platform

Modernization of ECC to Next Gen Platform (B4HANA & S4HANA) As a part of a 9 year iterative approach, FBMS S4HANA, DOI planned and executed a series of projects around the next-generation enterprise resource planning (ERP) suite built on SAP's in-memory database technology. Leveraging the real-time processing capabilities of the HANA platform, FBMS S4HANA provides DOI with fast real-time data processing, improved data analytics, streamlined workflows, and intelligent automation, ultimately leading to better decision-making and resource management. FBMS B4HANA is a next generation data warehousing solution built on SAP’s in-memory database technology. It provides DOI with real-time analytics that offer insights and enable faster decision-making.

Reporting Improvements The iterative in-memory technology improvements detailed above have resulted in reporting improvements and increased user satisfaction across all FBMS reporting areas. This includes real-time reporting improvements, faster processing, and increased efficiency, allowing FBMS users to do more with the data stored in B4HANA. DOI has also implemented the FBMS Tableau Server, giving users visual analysis options and increased ability to integrate non-FBMS programmatic data sources with FBMS data. The Tableau Server also includes customizable functionality for the secure sharing of information within the department. The BIO has also deployed some of S4HANA’s Embedded Analytics options with the S4HANA go-live and will continue to implement them over time to meet user needs.

Usability Improvements In Fiscal Year 2016, the DOI implemented over 200 system improvement items utilizing a modular, agile deployment approach to deliver value to the user community at a more rapid pace. DOI also focused on key reporting improvement initiatives (e.g., budget execution reporting, financial assistance award reporting) and other high priority improvements such as tracking procurement action lead time and improving workflows.

Production Operations Support DOI continues to provide continuous, quality production support (e.g., system operations and maintenance, helpdesk support, issue resolution) for ~ 16,000 FBMS users.

Improved the FBMS Security Environment The BIO implemented updates to align FBMS with DOI’s Office of the Chief Information Officer (OCIO) Authentication Standard (SAML) in Fiscal Year 2016. This improved FBMS security and the user experience by leveraging network identification, which allows users to log into FBMS automatically through single sign-on capabilities. In calendar year 2024, the BIO implemented multifactor authentication (MFA) across the FBMS security boundary as directed by the OCIO to meet associated cybersecurity mandates.

FBMS Governance Structure

There are several entities involved in the governance of FBMS. The BIO is primarily responsible for sustaining, optimizing and leveraging FBMS, under the governance of FBMS’s system sponsor, and alon with the system owners and Executive Steering Committee (ESC). Additional end-user guidance is provided by the FBMS Software Advocacy Leadership Team (FSALT) and its collection of Special Interest Groups (SIGs). Daily FBMS production operations are coordinated through the Bureau Production Support Leads (BPSLs) and Bureau Incident Managers (IMs).

See Attachment 1C, FBMS Governance Structure, for further information about the FBMS governance structure.

FBMS User Support Scope

Business Processes Support by FBMS

The following information provides a snapshot of Fiscal Year 2024 transactions to provide a summary of DOI business processes that are supported by FBMS. Over 26 million transactions were processed through FBMS in Fiscal Year 2024.

· Acquisitions

· Over 48K awards and modifications for over $8.1B

· Financial Assistance

· Over 29.9K awards and modifications for over $12.4B

· Charge Card

· Over $818M processed

· Invoices

· Over 657K processed for 22.6B

· Vehicles and Equipment

· Over 187K Vehicles and Equipment

· Over 772K utilization measurements, such as miles traveled, days used, number of trips

· Over 1M fuel transactions

· Over 56K work orders opened

FBMS User Count

The table below shows the individual bureaus and office user count as of February 26, 2025. The user base is expected to be similar in future years.

Table 1: FBMS Users by Bureau and Office

Incident Count

The following table provides our current ticket counts for the past three years and our projection for the next three (Fiscal Years 2025, 2026, and 2027). Incident activity is primarily driven by user count, frequency of use, and new software features. Because all bureaus have been deployed and user base has stabilized, the projections for FY 2025 are based on trending in place in FY24 and a brief spike based on a three-month hypercare period post S4HANA go-live. The calculations for the projections for the remaining two out years are based on incident counts from FY22 through FY24User count data will be presented in the section that follows this one. The incident data presented includes actual data for FY22 through FY24 along with projections for the three out-years (FY25 through FY27). Incident counts for FY26 and FY27 include projected increases to ticket volumes to support G-Invoicing and a projected go-live for ETSNext impacting AR, AP, SD and Travel ticket counts. Incidents submitted for Travel CGE and MDM have been excluded. 96% of the Travel CGE tickets are resolved by the CSC Tier 1 support or the Bureau Tier 2 support. Incidents submitted for MDM are normally resolved at the IBC FMD Incident count data is presented in two broad groups: Application Management, which are more functionally related issues; and Operations, which are more technically related issues. The further breakdown provided by detailed topic areas in tables later in this section, can be directly related to teams provided in the organization chart as to who primarily works on these incidents.

Table 2: Actual and Projected BIO Support Incident Count

FBMS Functional Scope

The following figure provides an overview of FBMS’s functional scope.

Figure 3: FBMS Functional Scope

FBMS Technical Environment Background

This section provides information describing the current FBMS Technical environment. This work is primarily accomplished by resources from the Applications Management Division. The work is managed by the Application Management Division which includes Architecture, System Admin and Development branches. Technical support is provided to both those working on production support (O&M) and those working on development work (DME).

Current Hosting Environment and Architecture

FBMS is hosted in a secure commercially provided cloud. This separate cloud hosting contract describes the NIST service model as Infrastructure-as-a-Service (IaaS), and the Deployment Model as a Federal Government Only Community Cloud. The BIO is responsible for the execution of this hosting contract. The BIO is responsible for all application and database level system administration. BIO engaged a Managed Service Provider (MSP) to provide support for OS level, Network layout/support, infrastructure support including VM builds and storage setup/configuration. The BIO also works closely with the DOI Office of the Chief Information Officer (OCIO) to ensure this external data center is securely incorporated into the DOI infrastructure.

FBMS is supported by the standard 3-box production support landscape (PSL) for operations support. In addition, FBMS has training, R&D (sandbox), production copy (PRODCOPY), and disaster recovery (DR) environments. FBMS is currently running in a virtualized, clustered, and highly available in the FEDRAMP moderate public cloud. Annual disaster recovery exercises are typically addressed over one weekend in the second quarter of the fiscal year. DOI’s OCIO, BIO, and Hosting Provider participate to meet the defined Service Level Agreements (SLA).

The diagram below provides a picture of the FBMS production (PSL) and development (DSL) landscapes, and where the actual current hardware is located.

Figure 2: FBMS Technical Landscape

A visual depiction below shows the relationship of FBMS software products is shown in Figure 4 FBMS Application Landscape.

Figure 4: FBMS Application Landscape

FBMS Environment Applications/Databases/Virtual Machines/Appliances The tables below describe the FBMS current technical environment detailing the Applications and Databases as well as the number of Virtual Machines/Appliances.

Table 3: Applications and Database Versions

Table 4: Operating Systems All BIO FBMS supported applications operate on the following four operating systems: SUSE, Red Hat Enterprise Linux (RHEL), Windows, and Ubuntu. The distribution of virtual machines (VMs) across these operating systems is provided in the following table.

Total VMs

Table 5: Databases All major BIO FBMS supported applications run on the following three databases: Oracle, SAP HANA and MS SQL. The distribution of database instances across these databases is provided in the following table.

Table 6: Applications and Database Sizes The following table details the current database sizes for the major production applications in FBMS. Development, test, sandbox, and prodcopy environments maintain similar database sizes. Training environments utilize smaller databases containing data specifically created for user training purposes

FBMS System Interfaces Attachment 1D, FBMS Interfaces Overview, is an architectural diagram that depicts all of the FBMS interfaces, both internal and external. There are internal interfaces within FBMS modules (e.g., PRISM to SAP), external interfaces with DOI bureau systems (e.g., FBMS to USGS IBIS); external interfaces with other Federal entities (e.g., Treasury’s Internet Payment Platform (IPP) which DOI uses for electronic invoicing); and external interfaces with non-Federal systems (e.g., Citibank’s charge card billing system).

External systems (e.g., Treasury, IPP, etc.) are not typically supported by the BIO, however, integration issues and operational issues related to the external interfaces to FBMS, or any interface changes typically involve BIO staff research and issue resolution.

FBMS Software Upgrades

Attachment 1F, FBMS Software Matrix per Release, provides the current and projected software upgrade schedule for FBMS. Projected versions are planned but are not finalized until the Fiscal Year’s budget is approved.

FBMS Support Tools In support of FBMS, a number of different project tools are utilized by bureau and Departmental offices. Below are a list of known support tools; others may be identified in a task order. Several bureaus and Departmental offices use web versions of the tools to minimize setup time and maximize portability.

· Adobe Captivate: Supports the development of Computer Based Training (CBT) modules for FBMS End User Training. This software is limited to training team members and is being phased out as the team shifts to using ANCILE uPerform software instead

· ANCILIE uPerform: Supports and contributes to the creation of Work Step Instructions, CBT modules, simulation development, video development, and end-user training materials. This software is currently available to training team members

· Bison Support System (BSS): BSS is a web-based incident tracking tool managed by the DOI Customer Support Center (CSC). BSS supports the tracking and reporting of FBMS production and BIO support issues. FBMS users across DOI enter helpdesk tickets into BSS to request end-user FBMS support

· BMC Control-M: Control-M is our current batch scheduling and monitoring tool. It manages financial transactions and SAP jobs in FBMS. It operates on a client/server architecture. This provides access to four main domains: Planning, Monitoring, History, and Forecast, along with various additional tools

· Hewlett Packard Enterprise (HPE) LoadRunner: LoadRunner supports FBMS’s network and server stress and volume testing in a production environment. This tool is limited to the BIO’s Stress and Volume team members that support FBMS

· Microsoft SharePoint: SharePoint is a web-based application that integrates with Microsoft Office. SharePoint may be used as a secure place to store, organize, share, and access information

· SAP Solution Manager tool suite: Solution Manager (SolMan) is an SAP platform that provides the integrated content and tools required to implement, support, operate, and monitor enterprise-wide SAP Projects in a multi-component environment (e.g., SAP ECC, Business Intelligence, and Enterprise Portal). Solution Manager provides a centralized platform for managing an SAP implementation, including end-to-end functionality for solution design tracking and ongoing continuous improvement

· ChaRM: Change Request Management (ChaRM) is a tool in the Solution Manager suite used to manage changes and defects through the deployment and maintenance life cycle

· Solution Documentation: Solution Documentation is comprised of (1) the Business Process Repository which contains the mapping of the FBMS solution to transactions, configuration items, and development objects and (2) links to and version control for the solution documentation repository; for example, FDS, TDS, BPD

· Business Process Change Analyzer (BPCA): BPCA assists in the execution of a change impact analysis and allows for risk-based test planning and execution. With BPCA, it can be determined which transactions are impacted by a change so that testing can be targeted in the correct areas

· Test Suite: The Test Suite group in the SolMan launchpad is the central access to all functions for preparing, creating, managing, and evaluating test plans, test scripts, test configurations etc.

· Tableau: BIO staff use Tableau to visualize release, resource and project data providing support for analysis and management decisions

· Agilitydigital.ai (Agility): AgilityAgility is Enterprise Agile Platform’s agile lifecycle management (ALM), DevOps, and integration solutions that provide insight and traceability from strategy through development and delivery. AgilityAgility provides the ability for the BIO teams to manage and prioritize FBMS work through a single, centralized system. Used for the population of stakeholder release notes. BIO teams use AgilityAgility to coordinate and collaborate on software plans, priorities, and track progress. It is a browser-based software the BIO uses to manage our work backlog. It is used for the following types of work:

· Manage Agile backlogs, Sprint tracking and reporting

· Project level workload and task status

· Other work: Agility is also used to track and monitor Data Quality item backlog, Situation Reports, White Papers and DOI policy work

· UIPath: UIPath is used by the Robotics Process Automation (RPA) team to create process automations (Bots) that automate manual processes within DOI. This enables significantly improved processing time, freeing up DOI personnel to work on other tasks

· Worksoft Certify and Worksoft Capture: Worksoft Certify is an automated software testing tool used by the BIO. Worksoft Certify allows users to validate the behavior, capacity and user response time for FBMS.

· Microsoft Teams: Used to collaborate, communicate, and manage document resources and approvals for various projects and internal work management processes

FBMS Documentation

FBMS is a well-documented system. The below documentation provides necessary support for all users of FBMS, consumers of FBMS information and technical support for FBMS. Following are examples of key system documentation work products that will be supported under this contract:

· Business Process Definition (BPD): The BPD is used to document each of the identified business processes within the FBMS scope. These are high level documents that use workflows and are an output of the Blueprint phase of system development. Functional Design Specification

· Configuration Element (COE): The COE form details the configuration completed to support DOI business processes. The COE form is used for documenting configuration, tracking the status of configuration, and providing a base for an audit trail of changes.

· Decision Record: These records serve to capture and document decisions (e.g. Standardization decisions, process decision, etc.) that result from workshops, action Items, or any meeting where decisions are made and should be documented.

· Enhancement Design Specification (EDS): The EDS document includes both the functional and technical requirements for a custom development object.

· Functional Design Specification (FDS): The FDS is a document that describes the requested behavior of a specific development object. The FDS describes what is needed by the system user, as well as requested properties of inputs and outputs, and related error checks and handling.

· Situation Report (SITREP): The SITREP is used by the BIO to define an issue for which bureau agreement cannot be reached and that requires a System Owner's' concurrence to a recommendation in order to resolve the issue.

· Technical Design Specification (TDS): The TDS is a document that details the essential technical requirements for developing the custom object, including the procedures by which it can be determined that the requirements have been met. The TDS helps avoid duplication and inconsistencies, allows for accurate estimates of necessary work and resources, and acts as a reference document for engineering changes.

· Unit Testing Plan (UTP): The UTP is the plan on how a development object will be tested by the programmer after development is completed and before it is turned over to the Business Process team for Integration Testing.

· Unit Testing Plan Execution (UTPx): The UTPx is a document where the results of Unit Testing is recorded and signed off on.

· Work Step Instructions (WSI): The WSI is a comprehensive training document detailing step-by-step procedures for executing specific transactions in FBMS. These documents are meticulously detailed, featuring screenshots that illustrate exactly what users should see at each step. WSIs are utilized for both online help and training instruction.

· Release Notes: The Release Notes are used by the BIO to communicate high level details of changes made to FBMS across the BIO and the Bureau communities.

· Other pertinent documentation driven by specific project needs.

FBMS Future Activities

To continue optimization of FBMS for its users, the following activities are planned to be executed throughout the period of this IDIQ:

System Security For continued optimization of FBMS, security improvements will be executed throughout the period of this IDIQ. System security activities are expected to include:

1. System-wide updates to FBMS-related software to reduce security and operational risks

2. Enhancements to the GRC suite of tools to include new integration for access control features, new workflows, and updates to the GRC software suite

3. Development of application security roles to keep pace with SAP and PRISM application changes such as SAP Fiori, SAP Personas, and other user interface and application security enhancements

4. Continuing enhancements to authentication methods including Security Assertion Markup Language (SAML) and Single Sign-On (SSO);

5. Security tasks associated with integration with third party applications and internal interfacing systems

6. Security tasks associated with enhanced analytics functionality like SAP BW , Tableau Server, and other reporting requirements

7. Security tasks for implementing new systems like SAP Business Technology Platform (BTP) and future acquired systems

8. Security tasks for deploying and utilizing new security tools like Pathlock Dynamic Access Control

9. Continuing to respond to future assessments and audits to further improve and optimize the security of FBMS

Application Development and System Administration/Architecture For continued optimization of FBMS, technical improvements will be executed throughout the period of this IDIQ. Attachment 1B – FBMS Development Objects shows the RICE-F objects developed for FBMS. Activities are expected to include:

1. Alignment with a Zero Trust Architecture

2. Enhanced Monitoring functionality for SAP and non-SAP systems

3. Future investment in automation developers

4. Identification and implantation of Artificial Intelligence Use Cases

5. Migration of Application Development practices to use the SAP Clean Core Extensibility Model

6. Continuous improvement and optimization of the overall system architecture for FBMS.

7. Continuous improvement of the software delivery practices with Agile that focuses on the creation of Continuous Improvement/Continuous Delivery development pipelines

8. Migration to the Business Technology Platform (BTP) with an initial emphasis on implementation of WorkZone and Integration Suite (Portal and PI will be sunset no later than December 31, 2027)

9. Preparation of a long term BTP roadmap that incorporates a Clean Core approach with emphasis on SAP Build Apps and Artificial Intelligence

10. Leverage SAP Analytics Cloud as a replacement for Business Intelligence

11. Determine the replacement of Solution Manager (Sunset date December 31, 2027)

12. Design and development of an S4HANA Archiving Solution

Reporting Improvements Recent reporting improvements include an optimized FBMS-wide data warehouse that greatly increased the ability to better leverage the FBMS data across the core function areas, as well as increasing reporting performance. The BIO is further leveraging FBMS to increase the data quality and reduce the burden on the bureaus by centralizing several Department-wide reporting requirements. This centralization will enable DOI to provide one, cohesive submission for real property, fleet and energy reporting, as an example. The BIO will also implement a data quality program that will analyze the data within FBMS to identify opportunities to increase the efficiency of DOI operations and business decision making. The BIO may also implement reporting and analytics improvements to potentially include AI integration and additional new reporting tools.

Usability Improvements The BIO will continue to implement user community prioritized system enhancements through the Agile Methodology. Additionally, the BIO has implemented a new business process analysis program that will identify opportunities to improve DOI operations through improved business processes or system configurations.

Intelligent Automated Technologies The BIO will continue to implement new IAT ideas using Robotic Process Automation, Natural Language Processing, Optical Character Recognition, Artificial Intelligence, and other intelligent technologies. The BIO continues to receive an abundance of IAT requests from across the Department and internal to the BIO.

Expanded Business Support It is expected that in future out-years, the BIO will continue to look for opportunities to provide expanded business support for its users. This may include expanding the FBMS functional footprint to cover new areas of business or may provide new functionality within existing areas of business. Examples of areas of expanded business support may include:

1. Revenue Management

2. Point of Sale

3. Barcoding/Radio Frequency Identification (RFID)

4. Geospatial

5. Mobility

Any approved scope related to this work would be planned in accordance with available capacity of all BIO Federal and Contractor staffing levels. The Government will work closely with the Contractor on any fluctuating, additional or fewer, Contractor staff needs based on approved fiscal year scope.

IDIQ Scope

The scope of task orders issued under this IDIQ are expected to include specific requirements related to the operations, maintenance, new development, reporting and training of FBMS by bureau and Departmental offices. Specific task order requirements will be detailed in the task order’s PWS.

BIO Support FBMS support identified in task orders may include:

· Perform FBMS operations and maintenance (O&M) including Tier 2 Help Desk support and managing software upgrades;

· Manage overall system and application level security;

· Provide functional and technical support of FBMS modules and components;

· Perform Business Intelligence reporting development and support;

· Manage and deliver training in support of system operations and process standardization;

· Optimize the FBMS solution, including mobile and light applications (where effective) and in support of legislative and regulatory compliance;

· Lead application leverage efforts, based on the direction of FBMS governance;

· Provide expert guidance related to a leadership position in the U.S. Federal workspace for FBMS software products such as SAP ERP Central Component (ECC), SAP BusinessObjects and Compusearch PRISM;

· Support business process revisions and additions for bureau guidance;

· Develop supplemental or bureau/Department-specific Work Step Instructions and quick reference guides;

· Support bureau or Department initiatives through reporting and analysis of FBMS data.

· Provide project management and development support using both Waterfall and Agile methodologies. MS Project is used widely across project teams.

· Manage SAP Customer Messages as appropriate for the SME’s scope purview.

· Provide Intelligent Automated Technologies (IAT) development, implementation, and support, including Robotic Process Automation, Natural Language Processing, Optical Character Recognition, Artificial Intelligence, and other intelligent technologies.

Labor Categories Based on past and current Contractor support for FBMS, see Attachment 1G, FBMS Support Labor Categories, which provides a description of labor categories expected to be identified in task orders assigned to this IDIQ.

Requirements

Task Orders Requirements

Requirements for FBMS support will be specified at the task order level.

Transition In and Out

The contractor shall provide a seamless transition with no interruption of services. Specific transition requirements shall be specified at the task order level.

Performance Measures

Performance Measures shall be specified at the task order level.

Staffing Requirements

Staffing requirements shall be specified at the task order level.

Deliverables

All deliverables shall be specified at the task order level.

General Information

Notice Regarding Late Delivery/Delayed Performance

The contractor will immediately notify the Contracting Officer (CO) in writing in the event the contractor encounters difficulty in performance by giving pertinent details, including the date by which it expects to complete performance or make delivery. However, the notification will be informal only in character and will not be construed as a waiver by the Government of any contractual delivery schedule or date, or any rights or remedies provided by law or under this effort.

Section 508

Section 508 of the Rehabilitation Act of 1973 (found at 29 USC 794d) requires access use of information by individuals with disabilities. A deliverable such as electronic reports (ex., PDF files) to be placed on the web (either on the agency’s web server or the company’s), video footage, or other electronic data such as CD-ROMs to be distributed, are subject to Section 508 guidelines. Simplified, this means that PDF files need to be formatted so that they are “readable” by assistive technology devices such as screen readers. Video footage must be closed captioned. CD-ROMs that contain HTML, PDF or word processor files must assessable.

Deliverables such as FBMS Release Notes, Computer-Based Training (CBT) classes and materials, as well as FBMS training resources, must comply with Section 508 accessibility guidelines. Each task order will outline any additional Section 508 deliverables required.

Contractor Interfaces

The contractor and/or their subcontractors may be required to work with other contractors supporting the Government. The contractor and/or their subcontractors will not direct the work of other contractors.

The Government will establish initial contact between the contractor and other contractors and will participate in any initial meeting at which the conventions for the scheduling and conduct of future meetings/contacts will be established. Any Contracting Officer’s Representatives (CORs), of other efforts, will be included in any establishment of conventions.

Warranty Against Dual Compensation

The contractor warrants that if a person is involved in two or more projects, at least one of which is supported by Federal funds, this person will not be compensated for more than 100% of their time during any part of the period of dual involvement.

Authority to Obligate the Government

The CO is the only individual who can legally commit or obligate the Government to the expenditure of public funds. No costs chargeable to this effort can be incurred before receipt of a fully executed task order and/or specific authorization from the CO.

Data Use, Disclosure of Information and Handling of Sensitive Information

Performance of this effort may require the contractor to access and use data and information proprietary to a Government agency or Government contractor that is of such a nature that its dissemination or use, other than in performance of this effort, would be adverse to the interests of the Government and/or others.

The contractor will maintain, transmit, retain in strictest confidence, and prevent the unauthorized duplication, use, and disclosure of personnel information. The contractor will provide personnel information only to employees, contractors, and subcontractors having a need to know such information in the performance of their duties for this project.

Information made available to the contractor by the Government for the performance or administration of this effort will be used only for those purposes and will not be used in any other way without the written agreement of the CO.

The contractor agrees to assume responsibility for protecting the confidentiality of Government records that are not public information. Each offeror or employee of the contractor to whom information may be made available or disclosed will be notified in writing by the contractor that such information may be disclosed only for a purpose and to the extent authorized herein.

Contractor personnel will not divulge or release data or information developed or obtained in performance of this effort, until made public by the Government, except to authorize Government personnel or upon written approval of the CO. The contractor will not use, disclose, or reproduce proprietary data that bears a restrictive legend, other than as required in the performance of this effort. Nothing herein will preclude the use of any data independently acquired by the contractor without such limitations or prohibit an agreement at no cost to the Government between the contractor and the data owner that provides for greater rights to the contractor.

All non-proprietary data received, processed, evaluated, loaded, and/or created as a result of this delivery order will remain the sole property of the Government unless specific exception is granted by the CO.

Place of Performance

The BIO is located primarily in two cities: Reston, VA and Lakewood, CO. Current DOI project staff is split approximately 50/50 between Reston and Lakewood. In Reston, the BIO is located at the USGS campus at 12201 Sunrise Valley Drive. The Lakewood space is at the Denver Federal Center, Building 810. It is expected that the contractor staff be physically located at these two locations. Exceptions may be made on an individual basis.

The requirement for Bureau FBMS support may require work to be performed outside the Denver and Reston locations, at the Bureau location to be determined at the point of order.

Hours of Operation

Normal office working hours are 8 a.m. to 5 p.m., Monday through Friday local time. Core hours are 9:30 a.m. to 2:30 p.m. local time. Team working hours may vary, depending on support activities. After hours, including weekend support, may be required which is dependent on the division and/or organization being supported and time of year (e.g., fiscal year-end may require after hours work). Frequently, technical support is required after normal published hours for system maintenance or upgrade work. For certain functions, 24x7 support is required. In these cases, standard business hours may be adjusted accordingly.

BIO facilities are normally closed on Federal holidays and during times of inclement weather. During these times, Contractors will not be permitted to work at those facilities unless specifically authorized by the Government.

The Contractor shall not charge the Government for performance of work on Government Holidays or for any other kind of administrative leave authorized for acts of God (i.e. hurricanes, snow storms, tornadoes, etc.), Presidential funerals, or any other unexpected Government closures, with the exception of work authorized as ad hoc telework, after hours, or weekend support.

The Contractor should refer to the U.S. Office of Personnel Management website to obtain a list of designated Federal holidays. The following Government Holidays are normally observed by Government personnel: New Year’s Day, Martin Luther King, Jr.’s Birthday, Presidential Inauguration Day (DC metropolitan area (including Herndon, Reston, and DOI’s Main Interior building (MIB)/headquarters location in downtown Washington, DC only)), President’s Day, Memorial Day, Juneteenth Day, Independence Day, Labor Day, Columbus Day, Veteran’s Day, Thanksgiving Day, Christmas Day and any other day designated by Federal Statute, Executive Order and/or Presidential Proclamation.

Period of Performance

The base period of performance is one year from the date of award with four 1 year option periods. Estimated dates are:

Exercising any of the option periods in this section is contingent upon the Government having a continuing need, established funding, as well as the contractor meeting or exceeding performance requirements.

Other Direct Cost (ODCs)

ODCs and materials in support of the work required under the task order are not anticipated, but may be required. The contractor should include Other Direct Charges in their cost/price proposal to cover any costs associated with other direct costs (ODCs). After award, all ODCs shall receive Government CO approval prior to funds being expended. In addition, at the time of requesting approval, the contractor shall provide current quotes from three vendors or other proof of cost reasonableness to the Contracting Officer.

Travel

Travel will be reimbursed in accordance with travel will be reimbursed in accordance with FAR 31.205-46. Travel may be required in the performance of this task order. General and Administrative (G&A) costs will not be authorized on travel. Travel by the contractor in support of the task order will be reimbursed by the DOI provided:

(a) The COR will only authorize travel if there is a funded travel CLIN on each task order. If there is not a funded travel CLIN then only the CO can approve travel. The format and process for receiving travel authorizations will be communicated at the contract kickoff meeting. The Government COR or CO must pre-approve all travel. The contractor shall provide the COR adequate time to review and approve travel plans. A COR/CO approved/signed & dated copy shall be sent to the contracting officer to be placed in the file for invoice verification and approval by the contracting officer. Note that no travel expenses will be reimbursed without prior written approval by the COR.

(b) All travel costs and per diem costs must conform to Federal Travel Regulations (FTR) in effect at the time of travel authorization, including but not limited to daily per diem and lodging rates in effect for the area at the time of the travel. Expenses not in conformity with the FTR will not be reimbursed and should not be submitted.

(c) Receipts and other written evidence to support submitted travel expenses over $25.00 will be retained by the contractor for the duration of the contract plus one year, and made available to the CO or COR on request. Travel not supported by receipts or other evidence will not be reimbursed and should not be submitted.

(d) An approved Travel Authorization Form and travel receipts must be submitted upon invoicing. Receipts should include:

· Common carrier transportation;

· Lodging, including any associated taxes or fees;

· Rental car;

· Taxi receipts to/from airport;

· Airport parking receipts;

· Meals reimbursed under the Actual Expense method;

· Itemized receipt for every authorized expense of $75.00 or more, excluding…