MRMSS Solicitation_Final.pdf

U.S. DEPARTMENT OF INTERIOR

OFFICE OF NATURAL RESOURCES REVENUE

INDEFINITE DELIVERY, INDEFINITE QUANTITY (IDIQ)

SOLICITATION

For

MINERALS REVENUE MANAGEMENT SUPPORT SYSTEM

(MRMSS)

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 4 of 84

TABLE OF CONTENTS

SECTION A – SOLICITATION/CONTRACT FORM

SECTION B – SUPPLIES/SERVICES AND PRICES/COSTS

B.1. GENERAL

B.2. CONRACT TYPE

B.3. SERVICES AND SUPPLIES

B.4. PRICING SCHEDULE

B.5. CONTRACT LINE ITEM NUMBERS (CLIN)

B.6. MINIMUM AND MAXIMUM THRESHOLDS

B.7. EXTENT OF OBLIGATION

B.8. ORDERING

B.9. NORTH AMERICAN INDUSTRICAL CLASSISIFICATION CODE (NAICS)

B.10. OTHER DIRECT COSTS (ODCs)

B.11. IDIQ LABOR CATEGORIES

SECTION C – STATEMENT OF OBJECTIVES

C.1. BACKGROUND

C.2. OBJECTIVES

C.3. CONTRACT LINE ITEMS NUMBERS (CLIN):

C.4. TECHNICAL EXHIBITS

C.5. PLACE OF PERFORMANCE

C.6. MANAGEMENT REQUIREMENTS

C.7. QUALITY AND PERFORMANCE DELIVERY

C.8. CONTRACTOR PERSONNEL

C.9. HOURS OF OPERATION

C.10. REPORTS & MEETINGS

C.11. QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

C.12. OPERATIONS AND MAINTENANCE GUIDELINES

C.13. DIRECTIVES, LAWS AND REGULATIONS

C.14. IT SECURITY AND PRIVACY COMPLIANCE REQUIREMENTS

C.15. INFORMATION PROTECTION

C.16. NON-DISCLOSURE

C.17. ORGANIZATIONAL CONFLICT OF INTEREST

C.18. LIMITED USE OF DATA

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 5 of 84

SECTION D – PACKAGING AND MARKING

D.1. PACKAGING

D.2. MARKING

SECTION E – INSPECTION AND ACCEPTANCE

E.1. 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

E.2. INSPECTION AND ACCEPTANCE OF SERVICES/DELIVERABLES

E.3. SCOPE OF INSPECTION

E.4. GENERAL ACCEPTANCE CRITERIA

E.5. QUALITY ASSURANCE

SECTION F – DELIVERABLES OR PERFORMANCE

F.1. 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

F.2. TERM OF THE CONTRACT

F.3. PLACE OF PERFORMANCE

F.4. MEETINGS, REPORTS AND OTHER DELIVERABLES

SECTION G – CONTRACT ADMINISTRATION DATA

G.1 CONTRACT MANAGEMENT

G.2. POST-AWARD MEETING

G.3. CONTRACT AUTHORITY

G.4. PAYMENT

G.5. ADDITIONAL INVOICING INSTRUCTIONS

G.6. METHOD OF PAYMENT

G.7. PAYMENT FOR UNAUTHORIZED WORK

G.8. IN-PROGRESS REVIEW (IPR)

SECTION I – CONTRACT CLAUSES

I.1. CONTRACT CLAUSES

I.2. CONTACT CLAUSES (AAAP)

I.3. CONTRACT CLAUSES (DIAR)

SECTION H – SPECIAL CLAUSES

SECTION J – ATTATCHMENTS AND EXHIBITS

SECTION K – REPRESENTATIONS, CERTIFICATIONS, AND OTHER STATEMENTS OF

OFFEROR

SECTION L – INSTURCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

SECTION M – EVALUATION CRITERIA

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 6 of 84

SECTION A – SOLICITATION/CONTRACT FORM

Request for Proposal (RFP) 140D0420R0005 begins with the SF-1449.

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 7 of 84

SECTION B – SUPPLIES/SERVICES AND PRICES/C OSTS

B.1. GENERAL

The United States, Department of the Interior (DOI), Interior Business Center (IBC), Acquisition Services Directorate (AQD) on behalf of the Office of Natural Resources Revenue (ONRR) anticipates awarding a single Indefinite Delivery/Indefinite Quantity (IDIQ) contract to provide Operations and Maintenance (O&M) support services for the Minerals Revenue Management Support System (MRMSS). The contract resulting from this solicitation shall provide ONRR with an industry partner to provide the following activities in daily support of the MRMSS:

O&M, new developments, enhancements, and upgrades (major/minor). These activities support ONRR’s mission to ensure the MRMSS’ accounting, auditing, compliance, and analysis are accurate and complete in the collection and distribution of the mineral royalties.

This competitive RFP is issued in accordance with FAR Part 12 - “Acquisition of Commercial Items,” follows the procedures of FAR Part 15 - “Contracting by Negotiation,” and in conjunction with FAR Part 16 - “Types of Contracts.”

If interested in this acquisition, please participate in accordance with the Section J, Attachment 8

- Instructions to Offerors (Section L) and Section J, Attachment 9 - Evaluation Criteria (Section M). Offerors will not be reimbursed for any costs incurred in developing their submission in response to this RFP.

B.2. CONRACT TYPE

The anticipated contract resulting from this RFP is for a single-award IDIQ contract. Task Orders issued under this IDIQ contract will consist of Firm-Fixed-Price (FFP), as well as Time and Materials (T&M) elements. The majority of Task Orders to be issued are anticipated to be

FFP.

B.3. SERVICES AND SUPPLIES

The required non-personal services shall be provided in accordance with the IDIQ contract Statement of Objectives (SOO) incorporated in Section C; the O&M Performance Work Statement (PWS) located at Section J, Attachment 1; and the Transition SOO located at Section J, Attachment 2.

Specific tasks, above those already identified within the general categories currently specified in Section B - Supplies/Services and Prices/Costs; Section C - IDIQ contract SOO; the O&M PWS at Section J, Attachment 1; and Transition SOO at Section J, Attachment 2 may be considered within scope of this IDIQ contract and may be performed under separate Task Orders, as appropriate. For example, if a Task Order requires support services and designates a labor resource not available in the IDIQ contract, the requirement would allow the contractor to propose, and the Government to negotiate, the inclusion of the labor category. This could also pertain to an offering that is considered within the general scope of MRMSS support, but not explicitly identified within the pricing.

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 8 of 84

For Task Orders issued against this IDIQ contract, the Task Order request will originate from the ordering activity Contracting Officer and will identify the scope of work required and any additional instructions regarding proposal submission. All Task Orders shall use the prices established herein.

The contractor shall furnish all personnel, facilities, equipment, materials, supplies, and/or services in performing the work described in Section C - IDIQ contract SOO; Section J, Attachment 1 - O&M PWS; Section J, Attachment 2 - Transition SOO; and any subsequent Task Orders issued under this IDIQ contract, unless otherwise stated herein. Task Orders will be issued as FFP, unless otherwise agreed upon in the individual Task Orders.

B.4. PRICING SCHEDULE

Offerors shall respond to the Instructions to Offerors (Section L), as articulated in Section J, Attachment 8 of this RFP. Offerors shall propose pricing for each of the ordering periods as detailed in Section J, Attachment 10 - Pricing Model. Prices and labor rates quoted by the successful offeror, as submitted in accordance with the Instructions to Offers (Section L) at Section J, Attachment 8 of this RFP, will be included in and made a part of Section B – Supplies/Services and Prices/Costs, of the final IDIQ contract award.

Future Task Order pricing will be specified at the Task Order level. Specific Task Order pricing shall be consistent (i.e. equal to or less than) the established IDIQ contract pricing.

B.5. CONTRACT LINE ITEM NUMBERS (CLIN)

Performance CLINs CLIN 0010 – Labor CLIN 0020 – Other Direct Costs (ODC) CLIN 0030 – ODC - Travel (T&M) CLIN 0040 – Transition

B.6. MINIMUM AND MAXIMUM THRESHOLDS

During the life of this IDIQ contract, the Government is not obligated to purchase services above the guaranteed minimum for the entire period of performance for this IDIQ contract, which is $100,000.00.

The contract ceiling for the entire period of performance for this IDIQ contract (inclusive of all option periods) shall not exceed $250,000,000.00.

B.7. EXTENT OF OBLIGATION

This IDIQ contract does not obligate any funds. The Government shall only obligate funds through the issuance of authorized Task Orders placed under this IDIQ contract. The guaranteed minimum order associated with this IDIQ contract is $100,000.00. The Offeror shall incur costs under the IDIQ contract only in the performance of Task Orders issued in accordance with the ordering procedures and period of performance contained herein. No other costs are authorized without express written consent of the ordering activity Contracting Officer.

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 9 of 84

B.8. ORDERING

All services under this IDIQ contract are to be performed in accordance with the IDIQ contract terms and conditions, and Task Orders issued by the ordering activity Contracting Officer. The following will apply to all Task Orders under this IDIQ contract.

a. An RFP will be issued by the Government for each new Task Order requirement. The offeror must have sufficient procedures and personnel in place to provide a proposal and/or quote within fifteen (15) business days of issuance of the RFP. The Government will, to the maximum extent practicable, provide the offeror with a longer response time.

b. Task Orders shall be placed by electronic commerce. Additionally, only a DOI warranted Contracting Officer is authorized to issue a Task Order RFP or Task Order Request for Quotation (RFQ).

c. The terms and conditions of the IDIQ contract take precedence over Task Order terms and conditions.

d. Task Orders shall not imply authorization to exceed or change the terms and conditions of the IDIQ contract.

e. Individual Task Orders may be awarded through the last day of the IDIQ contract period of performance. Furthermore, no Task Orders or options on Task Orders, may extend more than one (1) year after the expiration of the basic IDIQ contract.

f. Task Orders shall include CLINs and description of the work; quantities; funded amounts; ceiling value; period of performance; deliverables; performance work standards; performance schedule; contract administration information, including government points of contact and associated contracting office information; and other data, as appropriate. The contractor will be requested to provide a price and technical solution for each Task Order.

g. Performance under a Task Order shall not begin prior to the period of performance start-date as stated in the Task Order.

B.9. NORTH AMERICAN INDUSTRICAL CLASSISIFICATION CODE (NAICS)

The following North American Industry Classification System (NAICS) code is the primary code applicable to this acquisition: 541519 – “Other Computer Related Services”.

B.10. OTHER DIRECT COSTS (ODCs) ODCs, not identified herein, shall be Task Order dependent. The price(s) charged to the Government for such item(s) and/or service(s) shall be an amount not greater than the [then] current commercial list price and procured, in accordance with all required laws and regulations.

The contractor shall seek competitive bids for all items and services acquired under the IDIQ contract, which exceeds the micro-purchase threshold, as identified in the Federal Acquisition Regulation (FAR) 2.1 – “Definitions,” and provide them to the Government as backup documentation to support price reasonableness. As an alternative to seeking competitive bids, the

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 10 of 84 contractor may show that the proposed pricing is at or below the General Services Administration (GSA) Federal Supply Schedule (FSS) contract price for the same type of item/service.

B.11. IDIQ LABOR CATEGORIES

Anticipated labor categories and loaded rates are listed below. Each labor category is a projected requirement for this IDIQ contract. The list, as stated, is not limited to the labor categories identified. Specific Task Orders may require additional skills and/or expertise that are not listed.

The Government retains the right to negotiate with the contractor via a bilateral modification to incorporate additional skills/labor categories and rates when necessary, within scope of the IDIQ contract.

Note: At the time of IDIQ contract award, the rates proposed via Section J, Attachment 10 - Pricing Model, will be incorporated into Section B - Supplies/Services and Prices/Costs.

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 11 of 84

SECTION C – STATEMENT OF OBJECTIVES

C.1. BACKGROUND

The DOI, ONRR, Information and Digital Services (IDS) manages the end to end contract and oversight of the MRMSS that services the mission of ONRR: “For the benefit of all Americans, ONRR collects, accounts for, and verifies natural resources and energy revenue due to the states, American Indians, and the U.S. Treasury.” MRMSS primarily interfaces and shares and receives information with the Bureau of Land Management (BLM), Bureau of Safety and Environment Enforcement (BSEE), the Bureau of Ocean Energy Management (BOEM), Bureau of Indian Affairs (BIA), the State and Tribal Royalty Audit Committee (STRAC), and the Office of Special Trust (OST).

1.1. ONRR BACKGROUND

ONRR is an office under the Assistant Secretary for Policy, Management and Budget within DOI. Organized in 2010, ONRR is comprised of all the functions performed previously by the Minerals Management Service (MMS), Minerals Revenue Management (MRM) organization. ONRR is responsible for the efficient, timely, and accurate collection and disbursement of all royalty payments, rentals, bonuses, fines, penalties, assessments, and other revenue due the Federal Government, Indian Tribes and allottees, States and the American people from the leasing and production of natural resources from Federal and Indian lands onshore as well as the Outer Continental Shelf. This effort is one of the Federal Government’s greatest sources of non-tax revenues.

ONRR collects, accounts for, and disburses more than $10 billion in revenues annually from Federal offshore mineral leases and from onshore mineral leases on Federal and Native American lands. Principle responsibilities of ONRR are highly technical and rely heavily on Information Technology (IT) systems. These responsibilities include the collection and distribution of mineral royalties from all Federal onshore and offshore leases and Native American leases, together with compliance and auditing functions. Federal statutes require ONRR to ensure that fair and proper value of oil, gas, and other minerals produced from Federal and Indian leased lands is received. ONRR conducts comprehensive audits reviewing source documentation and conducts more streamlined compliance reviews to identify discrepancies through analysis of data. ONRR also places high priority on fulfilling its Indian Trust responsibilities. Through the performance of this highly visible mission, ONRR has significant and continuous interaction with various Federal and State government offices and energy companies.

ONRR is headquartered in Washington, DC but is operationally based near Denver, Colorado. ONRR’s workforce totals about 600 people who work at Program Headquarters in Washington, DC and Denver, CO, with regional offices in Dallas, TX; Houston, TX; Tulsa, OK; Oklahoma City, OK; and Farmington, NM.

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 12 of 84

Another key aspect of ONRR’s mission is the sharing of information between other government entities such as BLM, BIA, OST, BOEM, BSEE, and STRAC.

Entirely separate from the scope of this contract, ONRR is conducting a Modernization Project that is a multi-year, multi-phased effort to explore, identify, develop and implement new processes and technologies that enhance ONRR’s ability to perform revenue collection and distribution, disbursement, production and royalty reporting, verification and compliance, and workload management of applicable cases. The scope of this requirement does not include the long-term modernization efforts. Furthermore, ONRR completed an analysis of alternatives study which evaluated different solutions and is working on a business process re-engineering initiative that will modernize and streamline ONRR’s business processes. These new processes will potential generate requirements that will be used in the potential development of a new ONRR IT system. If necessary, a new modernization contract – separate from this contract – will be initiated by the work from ONRR’s business process re-engineering effort and will establish business requirements that are not specific to ONRR’s current hardware or current web interface for reporting functions.

As ONRR transitions to a new system, components of the current MRMSS (i.e. the scope of this contract) may be decommissioned which may include certain contract descope activities.

1.2. OFFICE AND PROGRAM BACKGROUND

Historically, most oil and gas royalties have been collected as a cash payment or in value known as Royalty In-Value (RIV). Under RIV, companies are required to file monthly royalty and production documents with ONRR at the lease/agreement level and when required at the well and mine level. The ONRR-2014 details the amount of production and revenue received from each lease and the amount of royalty owed for that month. The companies are required to pay the total amount owed on their royalty report monthly.

Royalties from Federal and Indian properties are reported and paid separately.

• Well operators are required to submit production documents Oil and Gas Operation Report (OGOR), and Production Allocation Schedule Report (PASR) each month that are used by ONRR to ensure all production sold and removed pays its requisite royalties.

• OGOR and PASR information is shared with BLM, BOEM, and BSEE for their mission activities, which includes ensuring the production is accurately reported.

• Form ONRR-4430 Solids Minerals Production and Royalty (P&R) Report is required to report monthly production, sales, royalty owed, and other obligations such as rent, advance royalty, etc., for leases associated with a solid minerals mine.

ONRR’s financial business functions uses primarily PeopleSoft software to support the financial processes for the management of incoming documents, accounts receivable, accounts payable, and general ledger. The process for royalties can be compared to the Internal Revenue Service (IRS) approach where the royalties are received subject to audit.

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 13 of 84

ONRR’s Audit Management (AM) and Compliance Management (CM) Divisions perform audit and compliance activities using the compliance components. Additionally, the Program Coordination, Enforcement, Valuation and Appeals Office provides regulatory and enforcement support to the mission areas, and the IDS office is the focal point for coordinating all IT activities with contractors and ONRR.

1.3. MRMSS BACKGROUND

The MRMSS is a computerized information system that automates many of the business and regulatory functions supporting ONRR and mission areas within BLM, BSEE, BOEM, OST, and BIA. The support of MRMSS is entirely outsourced end to end with ONRR oversight.

MRMSS uses relational database technology to bring diverse onshore and offshore information into transactional data from the financial database which is shareplexed nightly with new transactions. In order for the other DOI missions of BLM, BSEE, BOEM, OST, and BIA to perform their missions, the Government must provide solutions to automate information exchange while reducing errors and maintaining data quality. Currently there are prototypes, occurring between agencies to support this information sharing, utilizing the current technology that the Bureaus have in common.

MRMSS is a critical mission support system for the business functions of ONRR in the collection, verification, and disbursement of revenues timely to the stakeholder’s which include, States, Counties, Parishes, Other Federal Agencies, and Native Americans. MRMSS is a major investment and is tracked by the Capital Planning and Investment Control (CPIC) process in the Federal Government.

MRMSS consists of multiple applications using several different technologies, currently housed in two (2) separate contractor-owned private facility FedRAMP data center locations.

The production data center site is located in Raleigh, NC and the non-production and disaster recovery data center site is located in Boulder, CO. Technical Exhibit 02 – “MRMSS System Decomposition and System Description” provides additional detail on the components of MRMSS as generally discussed below in subsection 1.3.1.

The current number of users within the MRMSS Community is estimated at:

• ONRR and other government users – 1,000

• Industry users – 3,000

1.3.1. The MRMSS is comprised of three (3) major mission components (see attachment J_TE01) with sub-components including:

1.3.1.1. Component 1: MRMSS Financial (MRMSS-Financial)

• General Ledger

• Accounts Payable

• Accounts Receivable

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 14 of 84

• Debt Collection

• Royalty Reporting and Error Correction

• Production Reporting and Error Correct

• Reference data management and maintenance

• Electronic reporting of production, royalty, and solid minerals information (eCommerce and Solids Production and Royalty (P&R))

• Financial Reports

• Upload/Download

• Online Rental Payment Systems (ORPS)

1.3.1.2. Component 2: MRMSS Compliance (MRMSS-Compliance)

• Indian Pricing Tool (IPT)

• Supplemental Data Capture (SDC)

• Compliance Program Tools (CPT)

• Office Workload Management System (OWMS)

• Operations Management Tool (OMT) o Work Management o Case Management o Electronic Work Papers

• Document Repository

• Tracking Tools

• Compliance Information Management (CIM)

• Solids Compliance Program Tools (SCPT)

1.3.1.3. Component 3: MRMSS Business Automation/Data Warehouse (MRMSS-

BA/DW)

• Data Mining/Query Tools

• Business Intelligence reports and dashboards

• Industry Reports and Queries

• Internal and External portal – WebCenter Portal and Hyperion

Portal o Financial Reports

• eStatement of Accounts (eSOA)

• Lease Account Balance (eLab)

1.3.1.4. Underlying Infrastructure for all Components

• PeopleSoft & PeopleTools

• WebCenter Portal

• Hyperion Portal

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 15 of 84

• .NET Framework

• Oracle Business Intelligence (OBIEE) o Oracle Business Intelligence Publisher (BIP)

• Oracle Business Rules (OBR)

• Oracle Business Process Management SOA Suite

• Universal Content Manager (UCM) also, known as WebCenter

Server (WCS)

• Identity and Access Management (I&AM) Suite

• Oracle Databases

1.3.2. MRMSS Component Details

The primary operational site for MRMSS is located in a FedRAMP certified hosting contractor-owned private facility in Raleigh, NC. The disaster recovery/non production environments housed in a FedRAMP contractor-owned private facility in Boulder, CO.

1.3.2.1. MRMSS-Financial

The strategic goal of the MRMSS-Financial function is to collect, account for, and disburse Federal and Native American mineral lease revenues to the proper recipients in a timely and accurate manner per applicable laws, regulations, and lease terms, approximately $10 billion in annual revenues are processed through the MRMSS-Financial.

MRMSS-Financial accounts for all Federal and most Native American minerals rents, royalties, bonuses and their distribution/disbursement to the U.S. Treasury, counties, States (states generally receive 50% of the revenues collected in their state), and Native Americans (Native Americans receive 100% of their revenues).

The MRMSS-Financial also issues bills for late payment or non-payment of royalties and other lease term obligations. Most of the input data for MRMSS- Financial consists of royalty reports and production reports received from industry via an electronic reporting contractor.

MRMSS-Financial relies on major customizations of PeopleSoft®, and Oracle’s Business Process Management SOA Suite (BPM SOA) utilizing Oracle Business Rule (OBR) engine. MRMSS-Financials PeopleSoft® financials is composed of several modules including: Production, Reference, Royalty, Accounts Receivable, Accounts Payable, Billing, Lease Account Balance, Appeals Tracking System (ATS), General Ledger, Distribution & Disbursement, and Exception Processing.

1.3.2.2. MRMSS-Compliance

The compliance function consists of custom-built tools aimed at assuring that ONRR has collected every dollar due and all required reporting. These tools

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 16 of 84 include basic case management tools (tracking assignments and progress by employee and property), targeting tools, electronic work papers, and other specialized tools for analyzing variances between reported and expected values, and documentation. Compliance activities result in coverage of a significant portion of the royalty revenues paid each year. Many of the components are customized utilizing .Net framework.

1.3.2.3. MRMSS BA/DW

The MRMSS BA/DW provides a repository of historical financial and production information used by ONRR users, BLM, BOEM, BSEE, other Federal agencies, State and Tribal entities, and Industry. The MRMSS-BA/DW also provides data-mining tools for ONRR, States and Tribes, other government agencies and industry to run queries, reports and download the results of their royalty and production data and revenues received and disbursed.

MRMSS account management utilizes Oracle’s Identity and Access Management (IAM) Suite.

1.3.3. History of ONRR Financial Systems

Throughout the 1990’s, the financial and compliance processes operated on a mainframe environment. Financial and compliance software had been customized over the years and was complex, inefficient, difficult to change, and expensive to maintain. The various compliance processes and the organizational structure were very compartmentalized with “stove-pipe” business processes and associated personnel. In addition, high operating costs of the mainframe, the desire to utilize COTS software, web-based technology and implementation of the re-engineered Audit and Compliance Management (ACM) and the Asset Management Programs caused ONRR to re-compete the mainframe IT contract.

ONRR, formerly MRM, wanted to utilize COTS accounting systems to manage collection receipts, processing, distribution and disbursement; maintenance of receivables and payables balances; support of electronic data interchange and electronic commerce;

and production of required accounting and financial reports. The system had to comply with Treasury financial system per the OMB Circular A-127, A-130, and the Joint Financial Management Improvement Program (JFMIP).

ONRR selected the current contractor to convert the financial system to the PeopleSoft® financial system and to develop the re-engineered audit and compliance business processes. The new systems became operational in November 2001.

Since then, ONRR has further customized the PeopleSoft® financial system. The ACM systems have gone through an evolution from a structured analytical business process to a more flexible, user driven work management and analytical tool set that supports changing workloads and priorities.

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 17 of 84

The data warehouse and associated data mining tools have been updated with Oracle’s Business Intelligence Enterprise Edition over the last four (4) years.

ONRR’s portal functionality has been updated utilizing Oracle’s WebCenter Portal which is the access to all MRMSS applications both for internal and external users. Access control to MRMSS applications and WebCenter Portal are integrated with Oracle’s Identity and Access Management Suite.

C.2. OBJECTIVES

The primary objective of this IDIQ contract is to provision support for the O&M of MRMSS to include minimal development and enhancement. Following are the desired objectives from this IDIQ contract:

• Maintain the operations and maintenance of the MRMSS and meeting the desired service level agreements (SLA)

• Increase agility, throughput, and reliability in delivering mission IT needs

• Reduce IT operational costs

• Maintain high availability and high performance for all MRMSS components

• Maintain physical and logical data security

• Mitigate risks of end-of-life/end-of-support hardware and software

C.3. CONTRACT LINE ITEMS NUMBERS (CLIN):

All work performed under this IDIQ contract will be specifically identified by the issuance of Task Orders IAW B.8. Ordering.

3.1. CLIN 0010 – Labor & Program Applications

The contractor shall provide the necessary management, supervision, personnel, and information security for the continued daily operations and maintenance of the MRMSS, as well as, for enhancements and upgrades, as necessary, to the MRMSS. Support for MRMSS includes, but is not limited to:

3.1.1. MRMSS Operations and Maintenance

• Facilities Management and Physical Security

• MRMSS Network Administration

• Network Engineering, Installation, Maintenance, Repairs, and Upgrades

• MRMSS Firewall Management and Maintenance

• Server Administration

• Server Installation, Maintenance, Repairs, and Upgrades

• System Back-ups and Restorations

• Application System Administration

• System and Subsystem Testing for MRMSS

• MRMSS System and Network Administration

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 18 of 84

• Operating System (OS) Administration

• Oracle Exa Data Administration

• Oracle Exalogic Administration

• Oracle Exalytics Administrations

• Oracle Times Ten Administration

• Database Administration

• Citrix Administration

• Microsoft .NET and SQL Server Administration

• Asset Management

• Capacity Management

• Change Management (for Software)

• Configuration Management (for Hardware)

• Data Management

• Documentation Management

• Incident Management

• Systems Monitoring and Support

• Systems Performance Monitoring and Support

• Virtualization Management

• Government Audit Support Activities

3.1.2. Emergency Preparedness and Management

3.1.3. Business Continuity Management

3.1.4. Inventory Control/Government Furnished Property and Equipment

3.1.5. Software License and Maintenance Agreement Support

3.1.6. Client Application Management

3.1.7. Security Services

• Security Resources

• Security Planning

• Security Risk Management

• Security Audit Support

• Security Findings Resolution

• Security Incident Management

• Patch Management/Implementation

• Security Auditing and Operations

3.1.8. Quality Assurance for Operations and Maintenance, Modifications, Enhancements and Development

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 19 of 84

• Performance Management Approach

• Performance Strategy

• Quality Assurance Plan

3.1.9. Continuity of Operations Plan

3.1.10. MRMSS Network Connectivity

3.1.11. MRMSS Internal/External Audit Support

3.1.12. MRMSS - New Development, Upgrades and Enhancements

The contractor shall provide the necessary management, supervision, personnel, information security, materials, and supplies necessary to design, implement, and execute development or enhancements in support of the MRMSS. Due to the rapidly changing nature of information technology, the Government anticipates a need for additional IT development, upgrades, and enhancements in support of MRMSS during the life of this IDIQ contract. For example, some development, may be required in relation to technology refreshment and enhancements to the existing environment. This type of development typically includes updates and enhancements to compliance, security, financial, and data warehouse components. There are also routine updates and changes required to this environment generated by new guidelines and requirements mandated by internal and external entities, such as, the General Accounting Office (GAO), Inspector General (IG), Department of Justice (DOJ), Congress, or other Government agencies.

Upgrades are anticipated throughout the life cycle of this program. Development work can range from a simple upgrade to major system changes required by internal and external entities. Depending on the level of understanding and complexity of the requirement, a Task Order may be issued as FFP or T&M.

3.1.13. Decommissioning Components due to Potential Modernization

ONRR is currently conducting a Modernization Project that is a multi-year, multi-phased effort to explore, identify, develop and implement new processes and technologies that enhance ONRR’s ability to perform. These efforts are expected to result in the development of modernized components of the MRMSS and necessitate the decommissioning of existing components, which are supported by this contract. The Government shall require, potentially under separate Task Orders or modification of an existing Task Order, the O&M contractor to support the decommissioning of an existing component and switch-over to the new, modernized component. The contractor agrees, upon written notification by the Contracting Officer (CO), to provide services in collaboration with ONRR and other entities that ONRR designates, to decommission legacy MRMSS components as new modernized components are deemed operational.

3.2. CLIN 0020 – Other Direct Costs

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 20 of 84

The contractor shall provide the necessary materials, and supplies, for the continued daily operations and maintenance of the MRMSS system, as well as, for enhancements and upgrades, as necessary, to the MRMSS system as detailed in Section 3.1.

Software Vendor CSI / Reference Number (if applicable)

PeopleSoft License Maintenance Oracle CSI No: 14487438 Hyperion/Brio – OLAP, Portal and Quickview License Maintenance

Oracle CSI No: 15529649

MicroFocus COBOL Oracle CSI No: 14769092 SAS - Data Mining License Maintenance SAS Reference No: 430478 STAT Quest Reference No: 1449496 Other licenses: (to include software for batch maintenance, change request tracking, and Web Inspect/Security) Current software used for batch maintenance: AutoSys For Change Request Tracking: HP ALM For Security: Fortify/Web Inspect

TBD

3.3. CLIN 0030 – ODC Travel – T&M

The contractor shall provide the necessary travel for the continued daily operations and maintenance of the MRMSS system, as well as, for enhancements and upgrades, as necessary, to the MRMSS system as detailed in Section 3.1.

3.4. CLIN 0040 – Transition

3.4.1. Transition Plan

The Contractor shall submit a Draft Transition Plan with its technical proposal in accordance with the solicitation. The Draft Transition Plan shall focus on the Phase-In activities, which shall begin at Task Order award and last for no more than six (6) months. At a minimum, the Contractor’s Draft Transition Plan shall incorporate the following:

• Transition approach, process, and schedule.

• Approach to risk management and mitigation to ensure disruptions are minimized.

• Knowledge transfer and training methodology.

• Handling of personnel security adjudication, as it can take 30 to 90 days to comply with the personnel security requirements of this solicitation.

• Approach to coordination with the outgoing contractor.

• Approach for completing an application, module inventory, and a source code baseline that captures a relationship of the current release and the source code in production, as well as any source code in development or testing.

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 21 of 84

After Task Order award, the contractor shall update its Transition Plan and deliver a copy to ONRR for review and comment. Upon resolution of ONRR’s comments, the contractor shall deliver the plan for final approval by the Government.

3.4.2. Transition-In

The contractor shall complete phase-in efforts in accordance with the approved transition plan (to include the Government’s validation of the Transition Plan, which shall contain critical events, schedules, and approach). The contractor shall be prepared to begin full performance six (6) months after award of the first Task Order. The contractor shall submit a weekly status report during the phase-in period, to include the operational activities to the Contracting Officer’s Representative (COR); these reports shall begin immediately following award. The status report shall address those items identified as key to the success of the transition.

3.4.3. Execute Transition-In

During the transition-in, the contractor shall ensure that there will be minimum service disruption to ONRR’s MRMSS application availability; there will be no service interruptions vital to government business; and there will be no service degradation during and after transition. The transition activities shall be completed no later than six

(6) months from Task Order award; individual systems and applications may be transitioned using a staged approach. The contractor shall perform an Operational Readiness Review (ORR), which outlines the contractor’s preparedness to assume operation of Task Order duties for each application sub-system. The contractor shall assume full application operations, on an individual application sub-system basis, only upon written government approval. The contractor shall provide an updated transition-in plan that is based on the contractor’s draft plan. After O&M Task Order award, the contractor shall update the transition plan with its transition-out approach. During transition-in execution the Government will help ensure, to the maximum extent possible, the cooperation of the outgoing contractor.

The contractor shall provide a weekly transition status report. On an application level, this report shall detail:

• The application transition phase, as identified in the contractor’s transition-in plan.

• Performance against the contractor’s application transition schedule.

• Status of any in-flight or in-progress projects.

• The contractor’s staffing status, to include security processing.

• The contractor’s applications acceptance plan, checklist, schedule, and process.

• Transition risk management and mitigation.

• Coordination and activities with the previous contractor.

3.4.4. Transition Out

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 22 of 84

The contractor recognizes that the services provided by this contract are vital to the Government’s overall effort, that the continuity thereof must be maintained in a consistently high level without interruption, that upon expiration of this contract, a successor—either the Government or another contractor—may continue these services.

That the successor, be it the Government or another contractor, will need phase-in training by the outgoing contractor, and that the outgoing contractor shall provide for an orderly and efficient transition to a successor by providing full cooperation in the transition.

Final phase out activities at the end of the current contract will begin at the point a new contract is awarded beginning as early as 180 calendar days prior to expiration the current contract expires. The contactor’s transition out plan shall design a training program and specify a date for shifting the responsibility to the successor for each task of work set forth in the plan, and shall be subject to the approval of the CO. The contractor shall provide sufficient experienced personnel during the PIPO period to ensure that the services called for by this contract are maintained at a high level of proficiency. A Task Order will be issued to cover the contractor’s PIPO services.

The contractor agrees to cooperate with the successor, whether it is the Government or another contractor, in allowing as many personnel as practicable to remain on the job in order to enhance the continuity and consistency of the services called for by this contract.

Toward that end, the contractor agrees to disclose necessary personnel records and to allow its successor to conduct onsite interviews with its employees (see FAR 52.222-17).

C.4. TECHNICAL EXHIBITS

Technical Exhibits (TE) are provided as attachments to the solicitation and SOO. These exhibits provide additional requirements and details to guide the development of proposals as well as the execution of work under the IDIQ contract that results from this solicitation. The TEs are located in Section J, Technical Exhibits (TE) of this solicitation.

C.5. PLACE OF PERFORMANCE

Primary support will be performed at the Government’s facility on the Denver Federal Center located in Lakewood, Colorado. The Government anticipates that the contractor shall attend meetings at ONRR’s facility on the Denver Federal Center in Lakewood, CO and/or participate via conference call. While remote access to the MRMSS is available via VPN, any remote access must originate within the continental United States, and must adhere to the DOI Information Technology Security Policy Handbook (https://www.doi.gov/ocio/policy-mgmt-support/info-assurance) remote network access guidance.

C.6. MANAGEMENT REQUIREMENTS

6.1. Program Management

The Contractor shall provide program management support for all Task Orders issued under this IDIQ contract. Planning and program management support is critical to the successful https://www.doi.gov/ocio/policy-mgmt-support/info-assurance https://www.doi.gov/ocio/policy-mgmt-support/info-assurance

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 23 of 84 and timely completion of IT services and deliverables. The Contractor shall provide all necessary program management oversight to ensure that this contract is performed efficiently, accurately, on-time, within scope and budget, and in compliance with all applicable laws, regulations, policies, procedures, and requirements of the contract. Project maintenance and schedule management support involves the creation, maintenance, and reporting on Microsoft-Project schedules. Multiple project plans will be developed to manage the cost and schedule of ongoing and future projects.

6.2. Post-Award Meeting for IDIQ Contract

A Post-Award meeting is required per C.10.1 and G.2.

6.3. Project Kick Offs for Task Orders

The Contractor shall schedule and coordinate task orders and project kickoff meetings at a location approved by the Government. The meeting will provide an introduction between the Contractor personnel and Government personnel who will be involved with the task order and/or projects. At a minimum, the attendees shall include key Contractor personnel and relevant Government personnel. At the meeting, the Contractor shall provide a project kickoff agenda that includes, at a minimum, the following topics/deliverables:

• POCs for the parties

• Staffing plan and status

• Security discussion

6.4. Develop Project Management Plan (PMP)

The Contractor shall submit a Draft Project Management Plan (PMP) with its technical proposal. This Draft PMP should be developed in accordance with the latest version of the Project Management Institute’s (PMI) Project Management Book of Knowledge (PMBoK).

Two (2) weeks after award of the Transition-In (Phase-In) (Reference Section 3.4.2) Task Order, the Contractor shall provide an updated PMP to ONRR for review and comment.

Following resolution of ONRR’s comments, the Contractor shall deliver an interim PMP for ONRR approval. After the full transition has been completed, the Contractor shall further update its PMP to include any lessons learned through the transition period. The updated PMP shall be submitted as a deliverable under the Operations and Maintenance (O&M) Task Order two (2) weeks after the final transition activities. ONRR will review and comment on the updated PMP and the Contractor shall resolve ONRR’s comments and deliver a final PMP for ONRR approval.

The Contractor’s PMP, at a minimum, shall address the following key managerial elements:

• Scope Management

• Risk Management

• Schedule Management

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 24 of 84

• Cost Management

• Quality Management

• Communications Management

• Task Order Management

The PMP should be straightforward and easy to follow. The PMP will be updated as changes in the program occur. The Contractor shall conform to the latest Government-approved version of the PMP.

The Contractor is hereby notified that Project-specific PMPs shall be required for Task Orders, including O&M, associated with MRMSS. ONRR will notify the Contractor when Project-specific PMPs are required.

C.7. QUALITY AND PERFORMANCE DELIVERY

The contractor is responsible for the quality of all work performed. ONRR is responsible for the monitoring of the performance and delivery of services from the contractor. Refer to J_TE11 for the MRMSS Quality Assurance Surveillance Plan and Approach.

C.8. CONTRACTOR PERSONNEL

8.1. In general, the Contractor shall:

• Provide effective and qualified management and leadership empowered to make timely decisions, engage resources, and resolve issues.

• Provide effective management of subcontractors to ensure customer and mission support is responsive, efficient, and transparent to bureau users.

• Ensure coordination and interfaces with relevant Government and Contractor support teams across the internal and external stakeholder organizations.

• Analyze bureau IT goals, objectives, and evolutions in technology to assure alignment of initiatives.

• Provide effective and proactive communication and coordination with other IT contractor(s) to ensure clear performance accountability and successful mission accomplishment.

• Keep the Government proactively informed of significant issues and concerns.

• Ensure names and resumes for assigned Key Personnel (see below) are provided to the CO and COR.

8.2. Personnel Security Requirements

All contractor personnel performing work under this SOO must be eligible to undergo a successful National Agency Check (NAC) and obtain a DOI Public Trust designation and maintain the level of security required while performing tasks under this SOO.

8.3. Identification/Building Pass

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 25 of 84

This requirement will be fully adhered to until vendor personnel are cleared and processed for non-escort badges.

8.3.1. The Contractor must sign-in and out each work day at the Government site and secure a temporary badge from the security office or security desk.

8.3.2. The Contractor is responsible for ensuring that each of his/her employees performing work under this task order display their temporary badges at all times that they are present and on-duty in the building. Refusal or repeated neglect to display the identification may result in an unsuitability determination.

8.3.3. Upon termination, resignation or other event leading to a task order employee leaving duty under this task order, the Contractor is responsible for returning all Government badges (temporary), building passes, keys, and other Government property issued to that employee – if applicable. Failure on the part of the Contractor may result in the Contractor's liability for all costs associated with correcting the resultant breech in building security. The Contractor must notify the COR when the employee badges or other equipment or information are lost. It will be the responsibility of the Contractor to pay for replacement of all items lost at the current replacement cost of the item(s).

8.3.4. If applicable, the requirements of this clause are applicable to and must be flow down to all subcontractors who will work at the Government facilities.

8.4. Key Personnel

Certain skilled experienced professional and/or technical personnel are essential for accomplishing the work to be performed. These individuals are defined as “Key Personnel” and are those persons whose resumes were submitted and marked by the vendor as “Key Personnel”. No substitutions shall be made of accepted key personnel except for sudden illness or death, or termination of employment or promotion. Substitutions shall only be accepted if in compliance with “Substitution of Key Personnel” provision stated in the solicitation.

8.4.1. Key Personnel Designation

For the purpose of the overall performance of this contract, the below personnel shall be designated as key personnel as they are considered to be essential to work performance.

• Program Manager

• Operations Manager

• Functional Lead(s)

• Senior Business Intelligence Analyst

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 26 of 84

• Certified Information System Security Manager

• Senior System Administrator(s) (Exa and Identity and Access Management

(IAM) Engineers

The following subsections define the key personnel and associated skills sets required for this contract.

8.4.2. Program Manager

The Program Manager (PM) will work closely with the COR and the CO to ensure that supervision of Contractor employees is provided by the Contractor. The Contractor shall provide a PM who shall be responsible for executing the following duties:

• Overseeing and supervising the work distribution to Contractor employees.

• Managing the performance of the work for Contractor tasks and associated deliverables.

• Developing contract status reports and providing write-ups on tasks that are late or other issues/risks identified in the status update.

• Providing answers in writing to project management questions/issues raised during the execution of Tasks.

• Providing suggestions to improve Government software development methodologies.

• Possessing full authority to act for their respective company on contract matters relating to daily operation of this IDIQ; and

• Remaining available during normal duty hours to meet with COR/MRMSSPM to discuss any problem areas.

The PM must possess experience in managing an Operations and Maintenance (O&M), application development, enhancement, operations, and program management similar in size, scope, and complexity to this SOO. Desired skills and/or credentials for the PM are as follows:

• A minimum of 5 years of experience

• PMP® or PgMP® Certification: The Government prefers the candidate to have a current PMP® or PgMP certification from the Project Management Institute (PMI).

• Technical Background: The Government prefers the candidate to possess a deep technical background in IT programs that contain multiple subsystems; special focus must be given to the integration management processes and the release and build management processes to be used. throughout the project’s lifecycle.

• Delivery Background: The Government prefers the candidate to have experience with delivery of products that meet the functional and non-functional requirements that are professional delivered.

Continuation Sheets 140D0420R0005 MRMSS Solicitation Page 27 of 84

• Communications Skills: The Government prefers the candidate to possess excellent written…