FBMS_Support_Services_IDIQ_Attachment_1_-_FBMS_Support_Services_IDIQ_PWS.pdf

U.S. Department of the Interior Solicitation No. 140D0418R0001 – Attachment 1

Solicitation No. 140D0418R0001 Page 1 of 33

Financial and Business Management System (FBMS) Support Services Indefinite Delivery, Indefinite Quantity (IDIQ)

Performance Work Statement (PWS) October 30, 2017January 31, 2018

Table of Contents 1 Background and Objective

2 FBMS Overview

FBMS Deployment History

FBMS Accomplishments Post-DOI Deployment

2.2.1 Cloud Migration

2.2.2 In-Memory Computing

2.2.3 Reporting Improvements

2.2.4 Usability Improvements

2.2.5 Production Operations Support

2.2.6 Improved the FBMS Security Environment

FBMS Governance Structure

FBMS User Support Scope

2.4.1 Business Processes Support by FBMS

2.4.2 FBMS User Count

2.4.3 Incident Count

FBMS Functional Scope

FBMS Technical Environment Background

2.6.1 FBMS System Interfaces

2.6.2 Current Hosting Environment and Architecture

2.6.3 Current and Projected Processing Statistics

2.6.4 FBMS Software Upgrades

FBMS Support Tools

FBMS Documentation

FBMS Future Activities

2.9.1 System Security

2.9.2 Reporting Improvements

2.9.3 System Performance and Usability Improvements

2.9.4 Expanded Business Support

2.9.5 Migration to In-Memory Database Management System

Attachment 1 – FBMS Support Services IDIQ PWS

Solicitation No. 140D0418R0001 Page 2 of 33

IDIQ Scope

2.10.1 FBMS Support

2.10.2 Labor Categories

3 Requirements

Task Orders Requirements

Transition In and Out

Performance Measures

Staffing Requirements

Deliverables

4 General Information

Notice Regarding Late Delivery/Delayed Performance

Section 508

Contractor Interfaces

Warranty Against Dual Compensation

Authority to Obligate the Government

Data Use, Disclosure of Information and Handling of Sensitive Information

Place of Performance

Hours of Operation

Period of Performance

Other Direct Cost (ODCs)

Travel

Points of Contact

Non-Personal Services

Government Furnished Equipment

Contractor Personnel

4.15.1 Employee Termination

4.15.2 Additional Hours

4.15.3 Contractor Staff Training

Contractor Personnel Security and Suitability Requirements

Reference Documents

5 Acronyms and Abbreviations

6 Attachments

List of Figures

Solicitation No. 140D0418R0001 Page 3 of 33

Figure 1: FBMS Deployments

Figure 2: FBMS Functional Scope

Figure 3: FBMS Technical Landscapes

List of Tables

Table 1: FBMS Users by Bureau and Office

Table 2: Actual and Projected Incident Count

Table 3: Cloud Services Virtual Machine Processing Capability

Table 4: Cloud Services Allocated Storage Projections by Environment (Non-HANA)

Table 5: Database Allocated Storage Projections by Environment

Table 6: Existing Cloud Services FBMS Virtual Machines and Appliances (October 2016)

Table 7: Projected Counts for Cloud Services Virtual Machine and HANA Appliances

Table 8: HANA Migration and Improvement Phases

Solicitation No. 140D0418R0001 Page 4 of 33

1 Background and Objective

This Performance Work Statement (PWS) specifies critical support services required by the U.S.

Department of the Interior (DOI) to manage DOI’s Financial and Business Management System (FBMS).

Task orders issued under this Indefinite Delivery, Indefinite Quantity (IDIQ) contract will be relevant to FBMS support for bureau or Departmental offices.

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. 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. FBMS is based on commercial off-the-shelf (COTS) software applications that include a variety of SAP solutions (ECC, BI, BOBJ, BPC, PI, GRC, Enterprise Portal, SLD, Solution Manager, MDG), Compusearch PRISM contract and grants writing applications, Tableau Server, and OpenText’s document management application. See Attachment 1A, FBMS SAP Modules, for a complete list of SAP modules utilized by FBMS. DOI strives for the least amount of customization and promotes business process standardization across bureaus. Still, all system implementations require some amount of configuration and customization. The FBMS custom development objects are listed in Attachment 1B, FBMS Development Objects. This integrated system has led to the decommissioning of over 80 DOI and bureau-specific systems and enabled the alignment of a business management system with the DOI’s strategy of modernization, integration, accountability, and customer value. The full implementation of FBMS allows the DOI to realize the benefits of common 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 Deployment 8 (D8) go-live in November 2013.

As noted above, task orders issued under this IDIQ contract will be relevant to FBMS support. It is expected that the first task order issued through this IDIQ will be by the Business Integration Office (BIO). 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, Performance and Acquisition (DAS-BFPA) within the Office of Policy, Management and Budget (PMB). PMB is an office located within DOI’s Office of the Secretary (OS).

Additional task orders for FBMS support may be issued by individual DOI bureaus or Departmental offices. FBMS 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.

2 FBMS Overview

FBMS is an Enterprise Resource Planning (ERP) system that replaced the DOI’s many administrative systems to provide a modernized, fully integrated, enterprise-wide solution. FBMS supports the administrative systems requirements of all DOI bureaus for acquisition, budget execution, core finance, financial reporting, fleet management, financial assistance, personal property, real property, business decision reporting and travel management.

Solicitation No. 140D0418R0001 Page 5 of 33

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 an independent auditor;

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

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. As of August 29, 2016, FBMS has 11,849 users across these 10 organizations. The figure below illustrates the FBMS Deployments though November 2013.

Figure 1: FBMS Deployments

Solicitation No. 140D0418R0001 Page 6 of 33

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:

2.2.1 Cloud Migration

DOI completed the migration of all FBMS environments to the cloud in Fiscal Year 2015. This modernized, secure hosting arrangement not only increased the speed, reliability, and flexibility of the FBMS infrastructure, but also established a base for inclusion of future technical improvements, including in-memory computing.

2.2.2 In-Memory Computing

As noted earlier, FBMS is based on COTS software applications that include a variety of SAP solutions. In Fiscal Year 2016, DOI began the multi-phase effort to migrate to SAP HANA, which is SAP’s next generation of in-memory computing technology. In-memory computing will enable FBMS users to have quicker, more complete data analysis to support decision making. The first phase, which included the implementation of SAP HANA Accelerator, was completed in Calendar Year 2016. SAP HANA Accelerator

Solicitation No. 140D0418R0001 Page 7 of 33 provides a transformational improvement for a select number of real-time operational reports and transactions, greatly increasing the speed and utility of both.

2.2.3 Reporting Improvements

Along with the real-time reporting improvements provided by the first phase of the in-memory technology, DOI also greatly increased its ability to make business decisions by implementing a new FBMS tool to publish data visualizations through the implementation of Tableau Server. Data visualizations increase decision making by highlighting information, showing trends and outliers. This new module enables secure sharing of this information in an intuitive manner.

2.2.4 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.

2.2.5 Production Operations Support

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

2.2.6 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.

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

2.4.1 Business Processes Support by FBMS

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

Solicitation No. 140D0418R0001 Page 8 of 33

Acquisitions o Fiscal Year 2015: Over 71K awards and modifications for over $4.1B

Financial Assistance o Fiscal Year 2015: Over 14K awards and modifications for over $5.2B

Charge Card o Over $623M in Fiscal Year 2015

Invoices o Nearly 680,000 for over $27B in Fiscal Year 2015

Vehicles and equipment (Fiscal Year 2015) o Over 41,000 vehicles and equipment o 648,000 utilization measurements, such as miles traveled, days used, number of trips o 681,000 fuel transactions o 58,000 work orders managed

Assets o 785,000 of in-service assets o $40 billion gross fixed investment value o $17 billion accumulated depreciation o $22 billion net book value o $2 billion assets under construction

Energy o In Fiscal Year 2015, $55 million in energy costs captured o 130 metered and unmetered energy services/types

Real Property o 40,000 tenants in/out of housing o 4,000 leases and space contracts o Over 46,000 buildings, over 92,000 structures, and over 152,000 land records

Batch operations o FBMS executes approximately 39,000 batch jobs per month

2.4.2 FBMS User Count

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

Table 1: FBMS Users by Bureau and Office

Bureau / Office User

Count % of Total

FBMS Users

BLM – Bureau of Land Management 1,881 16%

BOEM – Bureau of Ocean Energy Management 258 2%

BOR – Bureau of Reclamation 1,151 10%

BSEE – Bureau of Safety and Environmental Enforcement 244 2%

DO – Department of the Interior Offices 1,222 10%

FWS – U.S. Fish and Wildlife Service 1,627 14%

IA – Bureau of Indian Affairs 1,349 11%

Solicitation No. 140D0418R0001 Page 9 of 33

Bureau / Office User

Count % of Total

FBMS Users

NPS – National Park Service 3,051 26%

OSMRE – Office of Surface Mining Reclamation and Enforcement 145 1%

USGS – U.S. Geological Survey 912 8%

Total 11,840

2.4.3 Incident Count

The following table provides our current ticket counts for the past three years and our projection for the next three (Fiscal Years 2017, 2018, and 2019). 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 2017 are based on trending in place in FY 2016. The calculations for the projections for the remaining two out years are noted in the below tables. User count data will be presented in the section that follows this one. The incident data presented includes actual data for FY14 through FY16 along with projections for the three out-years (FY17 through FY19). Incidents submitted for Travel Concur Government Expense (CGE) and Master Data Management (MDM) have been excluded. 96% of the Travel CGE tickets are resolved by the Customer Support Center (CSC) Tier 1 support or the Bureau Tier 2 support. Incidents submitted for MDM are normally resolved at the Interior Business Center (IBC) Financial Management Division (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 Incident Count

Actual Projected

Fiscal Year 2014 2015 2016 2017 2018 2019

Application Management 31,848 34,380 30,489 30,123 29,1788 30,562

Operations 23,169 27,403 24,622 24,617 25,1087 27,6203

Grand Total 55,017 61,783 55,111 54,740 54,2865 58,182

FBMS Functional Scope

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

Figure 2: FBMS Functional Scope

Solicitation No. 140D0418R0001 Page 10 of 33

FBMS Technical Environment Background

This section provides information describing the current FBMS Technical environment and also the projected future environment where feasible. This work is primarily accomplished by resources from the Applications Management and Architecture and Security Management Divisions, and based upon direction from the Production Management and Project Management Division. Technical support is provided to both those working on production support and those working on development work. DOI has begun a multi-phase effort to migrate FBMS’s SAP application databases to SAP HANA.

2.6.1 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., JPMorgan Chase’s charge card billing system).

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

2.6.2 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 closely involved with the execution of this hosting

Solicitation No. 140D0418R0001 Page 11 of 33 contract. The BIO is responsible for all application and database level system administration. 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.

A visual depiction of the relationship of FBMS software products is shown in Attachment 1E, FBMS Architecture Diagram.

Attachment 1F, FBMS Software Matrix per Release, contains a chart which depicts primary FBMS software products with their current and planned versions over the next 3 years.

The FBMS infrastructure follows the standard N+1 SAP Landscape methodology utilizing the SAP 2-tier architecture in the Development landscapes and SAP 3-tier architecture in all other landscapes. FBMS is supported by the standard 5-box landscape for operations support and deployment (production, two development, and two test environments). In addition FBMS has training, R&D (sandbox), production copy (PRODCOPY), and disaster recovery (DR) environments. Annual disaster recovery exercises are typically addressed during one weekend in the summer. DOI’s OCIO, BIO, and Hosting Provider participate to meet the defined Service Level Agreements (SLA). FBMS is currently running in a virtualized, clustered, and highly available in the Federal Cloud.

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

Figure 3: FBMS Technical Landscapes

Solicitation No. 140D0418R0001 Page 12 of 33

TRN

Environment

Release Changes

Release Changes

As needed per Training

Requirements and schedule

Replication

DR Failover

ProdCopy

Environment1

(aka Sandbox)

Production Support Landscape

Deployment Support Landscape

As Needed

D1 Ext Portal

DEV1

Environment1,2

D1 Data Exchange

Q1 Ext Portal

QAS1

Environment1,2

Q1 Data Exchange

PROD Ext Portal

PROD

Environment1,2

PROD Data

Exchange

DEV3

Environment

R&D Landscape

DEV2

Environment1

D2 Data Exchange

QAS2

Environment1

Q2 Data

Exchange

Sync PROD changes to DSL

Virtustream

Hosted Vienna

OCIO Hosted DDC

OCIO Hosted ESC

Virtustream DR

San Francisco

DR Ext Portal

PROD

Environment1,2

DR Data Exchange

Legend

Note 1 - Environment has HANA RDS

Note 2 - Environment has Tableau

Server

Note 3 – PRODCopy will be hosted from San Francisco starting

Dce 2016

2.6.3 Current and Projected Processing Statistics

The figures to follow are the projected system capacity and memory requirements of FBMS over the next few years. These estimates were produced using the most current methods and models with input from SAP, Oracle, the DOI’s CSC, and the BIO (System Architect), and were validated by objective third-party review.

Table 3: Cloud Services Virtual Machine Processing Capability

The below table reflects virtual resources. Projected reductions reflect BW on HANA implementation.

Projections for Total Allocated vCPU and Memory (GB)

Environment Oct-16 Oct-17 Oct-18 Oct-19 Oct-20 vCPU RAM vCPU RAM vCPU RAM vCPU RAM vCPU RAM

PROD 1,163 6,476 1,269 7,282 1,219 7,036 1,311 7,739 1,415 8,510

PROD Copy 258 1,278 294 1,446 291 1,372 314 1,509 340 1,659

QAS1 492 1,630 313 1,151 308 1,162 329 1,280 352 1,406

QAS2 462 1,590 466 1,700 504 1,877 542 2,068 584 2,271

DEV1 153 690 177 787 172 724 184 795 197 873

Solicitation No. 140D0418R0001 Page 13 of 33

Projections for Total Allocated vCPU and Memory (GB)

Environment Oct-16 Oct-17 Oct-18 Oct-19 Oct-20 vCPU RAM vCPU RAM vCPU RAM vCPU RAM vCPU RAM

DEV2 101 492 122 511 132 564 142 620 153 681

R&D 69 300 61 221 65 245 69 269 73 295

TRN 92 332 88 330 92 363 96 396 104 437

ITSSO 15 64 15 72 15 80 15 88 15 96

CSP 13 40 13 44 13 48 13 52 13 56

Total 2,818 12,892 2,818 13,544 2,811 13,471 3,015 14,816 3,246 16,284

Table 4: Cloud Services Allocated Storage Projections by Environment (Non-HANA)

Storage numbers in the below table reflect allocated storage for data maintained outside of HANA appliances. Projected reductions reflect BW on HANA implementation.

Allocated Storage (GB)

Environment Oct-16 Oct-17 Oct-18 Oct-19 Oct-20

PROD 102,102 112,941 61,131 68,296 75,461

ProdCopy 58,681 79,441 38,478 43,315 48,153

QAS1 73,719 78,327 39,533 44,362 49,193

QAS2 57,854 36,677 41,487 46,296 51,106

DEV1 82,012 81,680 42,072 46,916 51,760

DEV2 48,147 34,551 39,360 44,170 48,980

R&D 61,154 34,233 39,081 43,930 48,778

TRN 28,512 28,512 28,512 28,512 28,512

ITSSO 635 635 635 635 635

CSP 222 222 222 222 222

NFS Share 35,023 38,525 42,378 46,615 51,277

Grand Total 548,061 525,745 372,890 413,270 454,077

Table 5: Database Allocated Storage Projections by Environment

Storage numbers in the below table reflect allocated storage for data maintained outside of HANA appliances. Projected reductions reflect BW on HANA implementation.

Database Allocated Storage (GB)

PROD 88,141 96,308 44,018 48,888 53,759

Prod Copy 53,316 73,843 35,521 40,359 45,196

QAS1 68,478 74,043 35,712 40,541 45,371

QAS2 52,266 30,697 35,506 40,316 45,126

DEV1 77,187 76,682 37,538 42,358 47,178

DEV2 44,390 32,004 36,813 41,623 46,433

Solicitation No. 140D0418R0001 Page 14 of 33

Database Allocated Storage (GB)

Environment Oct-16 Oct-17 Oct-18 Oct-19 Oct-20

R&D 60,038 33,216 38,064 42,913 47,762

TRN 26,674 26,674 26,674 26,674 26,674

Grand Total 470,490 443,467 289,847 323,671 357,498

Table 6: Existing Cloud Services FBMS Virtual Machines and Appliances (October 2016)

The following table represents the FBMS virtual machines and HANA appliances that the BIO staff needs to monitor to keep the applications up and running.

OS VM Type PROD Prod Copy

TRN QAS1 DEV1 QAS2 DEV2 R&D TOTAL

RHEL Application 78 21 9 31 5 31 5 6 186

Central Services 18 4 14 14 50

Database 22 7 8 18 16 18 9 9 107

Rhel Total 118 32 17 63 21 63 14 15 343

Windows Application 16 1 2 4 3 4 1 1 32

Database 1 2 1 4

Windows Total 17 1 2 4 5 4 2 1 36

VM Total 135 33 19 67 26 67 16 16 379

OS HANA Appliance Type

PROD Prod Copy

TRN QAS1 DEV1 QAS2 DEV2 R&D TOTAL

SUSE Accelerator (Scale-Up)

1 1 1 1 1 5

BWoH (Scale-Out) 5 5

Appliance Total 1 0 0 1 1 1 1 5 10

Total VMs & Appliances 136 33 19 68 27 68 17 21 389

Table 7: Projected Counts for Cloud Services Virtual Machine and HANA Appliances

Note: Projected counts reflect HANA Accelerator and BW on HANA implementation.

Projected Virtual Machine Count

PROD 134 135 133 133 133

PRODCopy 32 33 32 32 32

QAS1 67 44 43 43 43

QAS2 64 64 64 64 64

DEV1 25 25 24 24 24

DEV2 14 15 15 15 15

R&D 11 10 10 10 10

Solicitation No. 140D0418R0001 Page 15 of 33

Projected Virtual Machine Count

Environment Oct-16 Oct-17 Oct-18 Oct-19 Oct-20

TRN 18 17 17 17 17

ITSSO 9 9 9 9 9

CSP 5 5 5 5 5

Total VMs 379 357 352 352 352

Accelerator Appliance Projections BWoH Appliance Projections

Environment Oct-16 Oct-17 Oct-18 Oct-19 Oct-20 Oct-16 Oct-17 Oct-18 Oct-19 Oct-20

PROD 1 1 1 1 1 5 6 7 8

PRODCopy 1 1 1 1 4 5 6 7

QAS1 1 1 1 1 1 4 4 5 5

QAS2 1 1 1 1 1 3 3 4 4

DEV1 1 1 1 1 1 2 2 3 3

DEV2 1 1 1 1 1 4 4 5 5

R&D 5

TRN

Total Appliances

5 6 6 6 6 5 22 24 30 32

2.6.4 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.

Ancile uPerform (SAP Productivity Pak): Supports the development of Work Step Instructions, development of CBT, simulation development, and end user training materials. This software is limited to training team members.

BMC Remedy: Remedy is a web-based incident tracking tool managed by the DOI Customer Support Center (CSC). Remedy supports the tracking and reporting of FBMS production and BIO support issues. FBMS users from all over DOI enter help desk tickets into Remedy to request support.

Google Software (Drive, Docs, Sheets, Slides, Mail). Google Drive is a file storage and synchronization service created by Google. It allows users to store files in the cloud, synchronize

Solicitation No. 140D0418R0001 Page 16 of 33 files across devices, and share files. Google Drive encompasses Google Docs, Sheets and Slides, an office suite that permits collaborative editing of documents, spreadsheets, presentations, drawings, forms, and more.

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.

o 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.

o 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.

o 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.

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

VersionOne: VersionOne is Enterprise Agile Platform’s agile lifecycle management (ALM), DevOps, and integration solutions that provide insight and traceability from strategy through development and delivery. VersionOne provides the ability for the BIO teams to manage and prioritize FBMS work through a single, centralized system. BIO teams use VersionOne 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:

o Manage Agile backlogs, Sprint tracking and reporting o Project level workload and task status o Other work: VersionOne is also used to track and monitor Data Quality item backlog, Situation Reports, White Papers and DOI policy work

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.

The BIO has invested time and resources to develop the Worksoft Certify automated testing solution. The BIO has committed to continued development and use of the solution in FY16 and beyond. Automation will be utilized where possible, however 100% automation will not be possible.

Solicitation No. 140D0418R0001 Page 17 of 33

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 training document that provides a step-by-step procedure for executing a specific transaction in FBMS. These documents are very detailed and contain screenshots of exactly what the user should see at each step. These documents are used for online help and training instruction.

Solicitation No. 140D0418R0001 Page 18 of 33

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:

2.9.1 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. Optimized and redesigned security roles as part of the migration to Suite on HANA and

S/4HANA;

4. Redesign 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;

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

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

7. Security tasks associated with enhanced analytics functionality like SAP BW on HANA, Tableau Server, and other reporting requirements;

8. Security tasks for implementing new systems like SAP Master Data Governance (MDG) and future acquired systems;

9. Security tasks for implementing new functionality in FBMS as it is deployed, for example revenue management; and

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

2.9.2 Reporting Improvements

The BIO will continue to improve the FBMS reporting environment through the implementation of an in-memory solution in two phases. The first phase consists of a migration of the business warehouse data from an Oracle database to a SAP HANA database that resides in-memory. The second phase of the in-memory migration effort will optimize the FBMS-wide data warehouse, greatly increasing the ability to better leverage the FBMS data across the core functional areas, as well as greatly increasing the reporting performance. The BIO is also 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.

2.9.3 System Performance and 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

Solicitation No. 140D0418R0001 Page 19 of 33 identify opportunities to improve DOI operations through improved business processes or system configurations. The BIO will continue to move forward with its plans to implement in-memory computing, including beginning the move of the FBMS data warehouse to this improved platform in Fiscal Year 2017. In-memory adoption is a multi-year effort that will improve business transaction processing and reporting, and also sets the stage for larger usability improvements.

2.9.4 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.

2.9.5 Migration to In-Memory Database Management System

FBMS currently utilizes an Oracle database management system. Over the next several years, the SAP portion of FBMS will be migrating to an in-memory database management system to continue enhancing the usability and response time of FBMS for increased customer satisfaction. FBMS will migrate to SAP HANA through a phased implementation that will take several years. Through this phased approach, continued improvements for FBMS will also be implemented during these timeframes. The table below outlines the phases and projected timeframes.

Table 8: HANA Migration and Improvement Phases

Phase Focus and Benefit Projected Accomplishments Projected Timeframe

Accelerate Select Real-time Transactions, Reports and Period-end Close

1. Implement SAP HANA Accelerator

Complete Calendar Year 2016

Accelerate and Simplify Analytical Reporting

2. Perform a technical clean-up of current business warehouse in preparation for the migration

3. Complete a BW on HANA pilot

4. Migrate to BW on HANA

5. Enhance BW on HANA to support simpler, more integrated reporting

6. Implement tiered data storage to allow for fast access to key

FY 2016 – FY 2018

Solicitation No. 140D0418R0001 Page 20 of 33

Phase Focus and Benefit Projected Accomplishments Projected Timeframe data while controlling overall costs

Simplify and Speed Up Day-to-Day Operations & Improve User Experience

7. Invite opportunities to re-examine and simplify business processes

8. Migrate to Suite on HANA

9. Migrate to SAP S/4 HANA

10. Enhance user experience through implementation of SAP Fiori

11. Implement tiered data storage to allow for fast access to key data while controlling overall costs

FY 2019 – FY 2020

with an expected go-live of early FY 2021

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.

2.10.1 FBMS 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, Tableau 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.

Solicitation No. 140D0418R0001 Page 21 of 33

2.10.2 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.

3 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.

4 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

Solicitation No. 140D0418R0001 Page 22 of 33 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 Classes and Materials, and FBMS training materials must adhere to Section 508 guidelines. Additional specific 508 deliverables will be specified within individual task orders.

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.

Solicitation No. 140D0418R0001 Page 23 of 33

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 10 a.m. to 2 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.

Solicitation No. 140D0418R0001 Page 24 of 33

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, 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:

Base Period: Month Day, 2018 – Month Day, 2019 Option Period 1: Month Day, 2019 – Month Day, 2020 Option Period 2: Month Day, 2020 – Month Day, 2021 Option Period 3: Month Day, 2021 – Month Day, 2022 Option Period 4: Month Day, 2022 – Month Day, 2023

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

Prior approved 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…