CANCELLED PEO MLB ERP+ RFI and DRAFT CSO

UPDATE FOR INDUSTRY 7/8/2024 - DRAFT
CSO - Anticipate first call will be a
Demonstration Lab / Sandbox environment
for ERP+ in an impact level 4 environment
that will enable configuration of company
codes in SAP S4.

Update 7/9/2024 - removed statement that
potential OCI vendors cannot respond to
the RFI. All vendors are eligible to respond
to this RFI.

Update 7/11/2024 - Posting Q&A to date.
Revised RFI and Draft CSO. Please review
both documents before responding.

update 7/12/2024 - Questions regarding the
RFI and Draft CSO closed today at Noon
EST. Final Q&A is posted.

UPDATE FOR INDUSTRY 7/8/2024 - DRAFT
CSO - Anticipate first call will be a
Demonstration Lab / Sandbox environment
for ERP+ in an impact level 4 environment
that will enable configuration of company
codes in SAP S4.

Update 7/9/2024 - removed statement that
potential OCI vendors cannot respond to
the RFI. All vendors are eligible to respond
to this RFI.

Update 7/11/2024 - Posting Q&A to date.
Revised RFI and Draft CSO. Please review
both documents before responding.

THIS IS A REQUEST FOR INFORMATION
(RFI) ONLY. NAVWAR PEO MLB is
performing market surveillance on the
viability of using a Commercial Solutions
Opening (CSO) and Competitive Prototyping
for elements of Enterprise Resource
Planning (ERP) solutions, to include
acquisition strategies. No solicitation exists.
This is not a request for a quote, request for
proposal, request for a prototype solution,
or an invitation to bid. This is not to be
construed as a commitment by the US
Government to form a binding contract or
agreement. The Government will not
reimburse or pay for information submitted
in response to this RFI.

This RFI is open to all business types. The
anticipated North American Industry
Classification System (NAICS) code will be
determined per CSO Call as scopes will
vary. The CSO will be unrestricted.

SECTION 1: PROGRAM OVERVIEW

The Program Executive Office for Mission,
Logistics, and Business Solutions (PEO MLB)
is responsible for managing the Department
of the Navy’s (DON) financial system
program of record, Enterprise Resource
Planning (ERP). ERP is a software portfolio
of finance, acquisition, supply, workforce
management, and grants management
modules that are components System
Applications and Products (SAP). To date
ERP has deployed to per 87,000 users
(96,000 users expected by Oct 2025) and
facilitates $145B in financial transactions
per year.

As an Enterprise Information Management
System, Navy ERP is the single General
Ledger, Accountable Property System of
Record and Enterprise Supply System for
the Navy. PMW 220 consolidated and
integrated Navy ERP’s financial, supply
chain, acquisition, and workforce
management functions into a single,
auditable system. Financial Management
functionality includes both appropriated
General Fund (GF) and Working Capital
Fund (WCF), Procurement, Workforce
Management including Time and
Attendance, Program/Project Management,
Grants Management, and additional
capabilities. For supply, Navy ERP is the
backbone of the Navy’s enterprise business
requiring critical data from material
inception through maintenance to issuance
to the fleet in order to have full auditability,
total cost of ownership and asset visibility.
Navy ERP has over 75 system interface
partners and over 900 system data
exchanges across the DON’s business
mission area enterprise.

Background: In the late 1990’s four Navy
user communities initiated pilot efforts for
enterprise resource planning. All four pilots
used SAP interface as a baseline. In 2003,
the Navy began consolidating and evolving
its ERP solution, maintaining the SAP
interface with various database approaches.
Navy ERP attained full operational capability
in December 2013. Most recently, the Navy
completed a technical refresh of the ERP
database in 2019 to SAP’s cloud-based high-
speed analytic appliance (HANA) while also
migrating to a cloud-hosting environment.
The Navy has invested over $2B in its
current SAP-based ERP, with $300M
invested in the HANA migration.

Today: Navy ERP is a Business Category I
(BCAT I) Defense Business System (DBS)
operating on the DBS Acquisition Pathway in
accordance with DoD Information 5000.75.
The acquisition strategy for new capabilities
is still under development.

SECTION 2: PROBLEM

The Navy’s current ERP is a SAP-based
solution, using ERP Central Component
(ECC) middleware over a HANA database.
The current Navy ERP system captures over
a decade of legacy data, history,
transactions, and patches. SAP’s ECC will
reach end of life in 2027, with support
available through 2030 for an additional
cost. To address ECC obsolescence, the
Navy needs a fully functional and
operational ERP solution fully deployed no
later than 2030 with 96,000+ users.

The Navy is also considering improving its
Navy ERP user experience by adding over
30 new capabilities to its ERP, resulting in a
program called Navy ERP+. The Navy ERP+
solution must modernize the current system
design and its business processes to better
leverage out-of-the-box (OOTB) capabilities,
reduce customization & technical debt,
improve flexibility and responsiveness, and
lower long-term operating and sustainment
costs in an impact level-4 (IL4) cloud
environment.

During prototyping the Navy must test the
hypothesis that it will be able to establish
and adopt standardized enterprise business
processes based on delivered OOTB
capability. If this hypothesis test fails, then
the Navy ERP+ effort can be re-planned
early to address the organizational and
cultural change management challenges.

Commercial solution offerings including
industry ‘best of breed’ solution enablers
that complement S/4HANA systems are
needed to accelerate Navy ERP+
deployment while reducing both deployment
and sustainment costs.

SECTION 3: OBJECTIVE

The objective of this market research RFI is
to (1) refine the acquisition strategy for
Navy ERP+ to include use of a CSO and or
an OTA, (2) determine that traditional and
non-traditional government contractors are
interested in and capable of performing the
work, and (3) secure feedback from the
marketplace on these approaches.

Commercial Solutions Opening (CSO) as
defined in DFARS 212.70 and 10 USC 3458
-Potential Areas of Interest:
a.Technical
a.Low Code/no Code tools
b.Sandbox Environment
c.Artificial Intelligence Tools
d.Software Development Lifecycle Tools
e.Data Migration/Conversion Tools
f.User Interface / User Experience
(UI/UX)
g.GIT Repository and Alternatives
h.Reporting Tools
i.Automated Testing Tools
j.Job Scheduling Tools
k.Middleware platform
l.End-User Printing from SAP
b.Business Processes
a.Business Process Re-
Engineering/Modeling
b.Training
c.Studies and Analysis
d.Modeling and Simulations of Process &
Policy Change Scenarios
e.Finding Efficiencies in Cost, Schedule,
and Performance of Navy ERP+
f.Cost Estimating Tools

Competitive Prototype Project(s) (FAR or
non-FAR instruments such as an Other
Transaction Authority (OTA) agreement) 10
USC 4022
-The Navy intends to utilize a
competitive multi-phased down-select
approach to identify the Navy ERP+
Developer/Integrator.
-CSO will include options to award
commercial contractors or OTAs.

SECTION 4: NAVY ERP+ ASSUMPTIONS

The Government welcomes feedback,
comments, challenges, or data to support or
refute any of the following assumptions:

-CSO enables risk reduction that can be
achieved through use of innovative
commercial solutions to address the areas
of interest.



SECTION 5: QUESTIONS WE HAVE

The following questions we need your help
to answer.
1.Can the Government expect to receive
innovation commercial solutions in response
to calls posted on a CSO for Navy ERP+?
2.Does the vendor base for these
technology and business areas include non-
traditional defense contractors as defined in
10 USC 4022 (d)?
3.Do traditional defense contractors
have cost share ideas to satisfy the
requirements of 10 USC 4022?
4.Does your firm currently have ERP
capabilities?
5.Does your firm have an innovative
commercial solution and is the solution
Federal Risk and Authorization Management
Program (FEDRAMP) and IL4 compliant?
6.How can small business participation
in a CSO be improved?
7.How can PEO MLB and the Navy ERP
Financial IT Services Program Office reach
and attract non-traditional defense
contractors?
8.Please recommend additional areas of
interest for a Navy ERP+ CSO.

SECTION 6: RESPONSE FORMAT AND
DELIVERY
1.Cover Letter (not to exceed two (2)
pages) with the following:
a.Name of firm, Commercial and
Government Entity (CAGE) Code, Business
size for NAICS 541512, Traditional or Non-
Traditional Defense contractor
b.Affiliation to include parent or
subsidiary corporation information, joint
venture partners, potential teaming
partners, or potential role in a future
contract or acquisition for Navy ERP+.
c.Point of contract for business
development, technical expertise, and
contract execution
d.Current ERP related work performed
or use cases of you innovative commercial
solution in public or private entities
2.Responses should not exceed five (5)
pages, 8”x11” 11 pt font.
3.Submissions due by noon EDT 23 July
2024.

Any questions regarding this RFI or Navy
ERP shall be directed to
pmw220_ERP_plus@us.navy.mil no later
than Noon EDT 12 July 2024. The
Government will make every effort to
answer questions and post responses daily
but cannot guarantee that all questions will
be answered before the RFI response
submission deadline.

SECTION 7: CONFLICT OF INTEREST AND
SUPPORT CONTRACTORS

See FAR 9.505 - Current contractor support
services (CSS) supporting PEO MLB are not
eligible for award of
any possible resulting contracts. NAVWAR
uses contracted support services in the
review and evaluation of RFI Responses.
The contractors have executed Non-
Disclosure Agreements (NDA) with the
Navy. If you require an NDA executed
directly with the vendor to accommodate
your response, please contact the
contracting officer at
robyn.l.kedrow.civ@us.navy.mil .

Support contractors utilized by PEO MLB
and stakeholders include the following:
Boston Consulting Group, Booz Allen
Hamilton, Bowhead, Government Solutions,
and Falconwood, OliverWyman (SeaTech),
Kupono, Deloitte, and Tecolote.

SECTION 8: INDUSTRY COLLABORATIONS

The Government reserves the right to
conduct one-on-one meetings in person or
virtually with respondents to this RFI or ERP
system integration experts. The
Government may or may not choose to
interact with select respondents in order to
perform market research. Such exchanges,
should they occur, would be solely for the
purpose of obtaining further clarification of
industry’s potential capabilities,
experiences, and perspectives and for the
purpose of conducting product
demonstrations at the Government’s
discretion. Additional RFI’s may be released.

UPDATE FOR INDUSTRY 7/8/2024 - DRAFT
CSO - Anticipate first call will be a
Demonstration Lab / Sandbox environment
for ERP+ in an impact level 4 environment
that will enable configuration of company
codes in SAP S4.

Update 7/9/2024 - removed statement that potential
OCI vendors cannot respond to the RFI. All vendors
are eligible to respond to this RFI.

THIS IS A REQUEST FOR INFORMATION
(RFI) ONLY. NAVWAR PEO MLB is
performing market surveillance on the
viability of using a Commercial Solutions
Opening (CSO) and Competitive Prototyping
for elements of Enterprise Resource
Planning (ERP) solutions, to include
acquisition strategies. No solicitation exists.
This is not a request for a quote, request for
proposal, request for a prototype solution,
or an invitation to bid. This is not to be
construed as a commitment by the US
Government to form a binding contract or
agreement. The Government will not
reimburse or pay for information submitted
in response to this RFI.

This RFI is open to all business types. The
anticipated North American Industry
Classification System (NAICS) code will be
determined per CSO Call as scopes will
vary. The CSO will be unrestricted.

SECTION 1: PROGRAM OVERVIEW

The Program Executive Office for Mission,
Logistics, and Business Solutions (PEO MLB)
is responsible for managing the Department
of the Navy’s (DON) financial system
program of record, Enterprise Resource
Planning (ERP). ERP is a software portfolio
of finance, acquisition, supply, workforce
management, and grants management
modules that are components System
Applications and Products (SAP). To date
ERP has deployed to per 87,000 users
(96,000 users expected by Oct 2025) and
facilitates $145B in financial transactions
per year.

As an Enterprise Information Management
System, Navy ERP is the single General
Ledger, Accountable Property System of
Record and Enterprise Supply System for
the Navy. PMW 220 consolidated and
integrated Navy ERP’s financial, supply
chain, acquisition, and workforce
management functions into a single,
auditable system. Financial Management
functionality includes both appropriated
General Fund (GF) and Working Capital
Fund (WCF), Procurement, Workforce
Management including Time and
Attendance, Program/Project Management,
Grants Management, and additional
capabilities. For supply, Navy ERP is the
backbone of the Navy’s enterprise business
requiring critical data from material
inception through maintenance to issuance
to the fleet in order to have full auditability,
total cost of ownership and asset visibility.
Navy ERP has over 75 system interface
partners and over 900 system data
exchanges across the DON’s business
mission area enterprise.

Background: In the late 1990’s four Navy
user communities initiated pilot efforts for
enterprise resource planning. All four pilots
used SAP interface as a baseline. In 2003,
the Navy began consolidating and evolving
its ERP solution, maintaining the SAP
interface with various database approaches.
Navy ERP attained full operational capability
in December 2013. Most recently, the Navy
completed a technical refresh of the ERP
database in 2019 to SAP’s cloud-based high-
speed analytic appliance (HANA) while also
migrating to a cloud-hosting environment.
The Navy has invested over $2B in its
current SAP-based ERP, with $300M
invested in the HANA migration.

Today: Navy ERP is a Business Category I
(BCAT I) Defense Business System (DBS)
operating on the DBS Acquisition Pathway in
accordance with DoD Information 5000.75.
The acquisition strategy for new capabilities
is still under development.

SECTION 2: PROBLEM

The Navy’s current ERP is a SAP-based
solution, using ERP Central Component
(ECC) middleware over a HANA database.
The current Navy ERP system captures over
a decade of legacy data, history,
transactions, and patches. SAP’s ECC will
reach end of life in 2027, with support
available through 2030 for an additional
cost. To address ECC obsolescence, the
Navy needs a fully functional and
operational ERP solution fully deployed no
later than 2030 with 96,000+ users.

The Navy is also considering improving its
Navy ERP user experience by adding over
30 new capabilities to its ERP, resulting in a
program called Navy ERP+. The Navy ERP+
solution must modernize the current system
design and its business processes to better
leverage out-of-the-box (OOTB) capabilities,
reduce customization & technical debt,
improve flexibility and responsiveness, and
lower long-term operating and sustainment
costs in an impact level-4 (IL4) cloud
environment.

During prototyping the Navy must test the
hypothesis that it will be able to establish
and adopt standardized enterprise business
processes based on delivered OOTB
capability. If this hypothesis test fails, then
the Navy ERP+ effort can be re-planned
early to address the organizational and
cultural change management challenges.

Commercial solution offerings including
industry ‘best of breed’ solution enablers
that complement S/4HANA systems are
needed to accelerate Navy ERP+
deployment while reducing both deployment
and sustainment costs.

SECTION 3: OBJECTIVE

The objective of this market research RFI is
to (1) refine the acquisition strategy for
Navy ERP+ to include use of a CSO and or
an OTA, (2) determine that traditional and
non-traditional government contractors are
interested in and capable of performing the
work, and (3) secure feedback from the
marketplace on these approaches.

Commercial Solutions Opening (CSO) as
defined in DFARS 212.70 and 10 USC 3458
-Potential Areas of Interest:
a.Technical
a.Low Code/no Code tools
b.Sandbox Environment
c.Artificial Intelligence Tools
d.Software Development Lifecycle Tools
e.Data Migration/Conversion Tools
f.User Interface / User Experience
(UI/UX)
g.GIT Repository and Alternatives
h.Reporting Tools
i.Automated Testing Tools
j.Job Scheduling Tools
k.Middleware platform
l.End-User Printing from SAP
b.Business Processes
a.Business Process Re-
Engineering/Modeling
b.Training
c.Studies and Analysis
d.Modeling and Simulations of Process &
Policy Change Scenarios
e.Finding Efficiencies in Cost, Schedule,
and Performance of Navy ERP+
f.Cost Estimating Tools

Competitive Prototype Project(s) (FAR or
non-FAR instruments such as an Other
Transaction Authority (OTA) agreement) 10
USC 4022
-The Navy intends to utilize a
competitive multi-phased down-select
approach to identify the Navy ERP+
Developer/Integrator.
-CSO will include options to award
commercial contractors or OTAs.

SECTION 4: NAVY ERP+ ASSUMPTIONS

The Government welcomes feedback,
comments, challenges, or data to support or
refute any of the following assumptions:

-CSO enables risk reduction that can be
achieved through use of innovative
commercial solutions to address the areas
of interest.



SECTION 5: QUESTIONS WE HAVE

The following questions we need your help
to answer.
1.Can the Government expect to receive
innovation commercial solutions in response
to calls posted on a CSO for Navy ERP+?
2.Does the vendor base for these
technology and business areas include non-
traditional defense contractors as defined in
10 USC 4022 (d)?
3.Do traditional defense contractors
have cost share ideas to satisfy the
requirements of 10 USC 4022?
4.Does your firm currently have ERP
capabilities?
5.Does your firm have an innovative
commercial solution and is the solution
Federal Risk and Authorization Management
Program (FEDRAMP) and IL4 compliant?
6.How can small business participation
in a CSO be improved?
7.How can PEO MLB and the Navy ERP
Financial IT Services Program Office reach
and attract non-traditional defense
contractors?
8.Please recommend additional areas of
interest for a Navy ERP+ CSO.

SECTION 6: RESPONSE FORMAT AND
DELIVERY
1.Cover Letter (not to exceed two (2)
pages) with the following:
a.Name of firm, Commercial and
Government Entity (CAGE) Code, Business
size for NAICS 541512, Traditional or Non-
Traditional Defense contractor
b.Affiliation to include parent or
subsidiary corporation information, joint
venture partners, potential teaming
partners, or potential role in a future
contract or acquisition for Navy ERP+.
c.Point of contract for business
development, technical expertise, and
contract execution
d.Current ERP related work performed
or use cases of you innovative commercial
solution in public or private entities
2.Responses should not exceed five (5)
pages, 8”x11” 11 pt font.
3.Submissions due by noon EDT 23 July
2024.

Any questions regarding this RFI or Navy
ERP shall be directed to
pmw220_ERP_plus@us.navy.mil no later
than Noon EDT 12 July 2024. The
Government will make every effort to
answer questions and post responses daily
but cannot guarantee that all questions will
be answered before the RFI response
submission deadline.

SECTION 7: CONFLICT OF INTEREST AND
SUPPORT CONTRACTORS

See FAR 9.505 - Current contractor support
services (CSS) supporting PEO MLB are not
eligible to respond to this RFI or award of
any possible resulting contracts. NAVWAR
uses contracted support services in the
review and evaluation of RFI Responses.
The contractors have executed Non-
Disclosure Agreements (NDA) with the
Navy. If you require an NDA executed
directly with the vendor to accommodate
your response, please contact the
contracting officer at
robyn.l.kedrow.civ@us.navy.mil .

Support contractors utilized by PEO MLB
and stakeholders include the following:
Boston Consulting Group, Booz Allen
Hamilton, Bowhead, Government Solutions,
and Falconwood, OliverWyman (SeaTech),
Kupono, Deloitte, and Tecolote.

SECTION 8: INDUSTRY COLLABORATIONS

The Government reserves the right to
conduct one-on-one meetings in person or
virtually with respondents to this RFI or ERP
system integration experts. The
Government may or may not choose to
interact with select respondents in order to
perform market research. Such exchanges,
should they occur, would be solely for the
purpose of obtaining further clarification of
industry’s potential capabilities,
experiences, and perspectives and for the
purpose of conducting product
demonstrations at the Government’s
discretion. Additional RFI’s may be released.

UPDATE FOR INDUSTRY 7/8/2024 - DRAFT
CSO - Anticipate first call will be a
Demonstration Lab / Sandbox environment
for ERP+ in an impact level 4 environment
that will enable configuration of company
codes in SAP S4.

THIS IS A REQUEST FOR INFORMATION
(RFI) ONLY. NAVWAR PEO MLB is
performing market surveillance on the
viability of using a Commercial Solutions
Opening (CSO) and Competitive Prototyping
for elements of Enterprise Resource
Planning (ERP) solutions, to include
acquisition strategies. No solicitation exists.
This is not a request for a quote, request for
proposal, request for a prototype solution,
or an invitation to bid. This is not to be
construed as a commitment by the US
Government to form a binding contract or
agreement. The Government will not
reimburse or pay for information submitted
in response to this RFI.

This RFI is open to all business types. The
anticipated North American Industry
Classification System (NAICS) code will be
determined per CSO Call as scopes will
vary. The CSO will be unrestricted.

SECTION 1: PROGRAM OVERVIEW

The Program Executive Office for Mission,
Logistics, and Business Solutions (PEO MLB)
is responsible for managing the Department
of the Navy’s (DON) financial system
program of record, Enterprise Resource
Planning (ERP). ERP is a software portfolio
of finance, acquisition, supply, workforce
management, and grants management
modules that are components System
Applications and Products (SAP). To date
ERP has deployed to per 87,000 users
(96,000 users expected by Oct 2025) and
facilitates $145B in financial transactions
per year.

As an Enterprise Information Management
System, Navy ERP is the single General
Ledger, Accountable Property System of
Record and Enterprise Supply System for
the Navy. PMW 220 consolidated and
integrated Navy ERP’s financial, supply
chain, acquisition, and workforce
management functions into a single,
auditable system. Financial Management
functionality includes both appropriated
General Fund (GF) and Working Capital
Fund (WCF), Procurement, Workforce
Management including Time and
Attendance, Program/Project Management,
Grants Management, and additional
capabilities. For supply, Navy ERP is the
backbone of the Navy’s enterprise business
requiring critical data from material
inception through maintenance to issuance
to the fleet in order to have full auditability,
total cost of ownership and asset visibility.
Navy ERP has over 75 system interface
partners and over 900 system data
exchanges across the DON’s business
mission area enterprise.

Background: In the late 1990’s four Navy
user communities initiated pilot efforts for
enterprise resource planning. All four pilots
used SAP interface as a baseline. In 2003,
the Navy began consolidating and evolving
its ERP solution, maintaining the SAP
interface with various database approaches.
Navy ERP attained full operational capability
in December 2013. Most recently, the Navy
completed a technical refresh of the ERP
database in 2019 to SAP’s cloud-based high-
speed analytic appliance (HANA) while also
migrating to a cloud-hosting environment.
The Navy has invested over $2B in its
current SAP-based ERP, with $300M
invested in the HANA migration.

Today: Navy ERP is a Business Category I
(BCAT I) Defense Business System (DBS)
operating on the DBS Acquisition Pathway in
accordance with DoD Information 5000.75.
The acquisition strategy for new capabilities
is still under development.

SECTION 2: PROBLEM

The Navy’s current ERP is a SAP-based
solution, using ERP Central Component
(ECC) middleware over a HANA database.
The current Navy ERP system captures over
a decade of legacy data, history,
transactions, and patches. SAP’s ECC will
reach end of life in 2027, with support
available through 2030 for an additional
cost. To address ECC obsolescence, the
Navy needs a fully functional and
operational ERP solution fully deployed no
later than 2030 with 96,000+ users.

The Navy is also considering improving its
Navy ERP user experience by adding over
30 new capabilities to its ERP, resulting in a
program called Navy ERP+. The Navy ERP+
solution must modernize the current system
design and its business processes to better
leverage out-of-the-box (OOTB) capabilities,
reduce customization & technical debt,
improve flexibility and responsiveness, and
lower long-term operating and sustainment
costs in an impact level-4 (IL4) cloud
environment.

During prototyping the Navy must test the
hypothesis that it will be able to establish
and adopt standardized enterprise business
processes based on delivered OOTB
capability. If this hypothesis test fails, then
the Navy ERP+ effort can be re-planned
early to address the organizational and
cultural change management challenges.

Commercial solution offerings including
industry ‘best of breed’ solution enablers
that complement S/4HANA systems are
needed to accelerate Navy ERP+
deployment while reducing both deployment
and sustainment costs.

SECTION 3: OBJECTIVE

The objective of this market research RFI is
to (1) refine the acquisition strategy for
Navy ERP+ to include use of a CSO and or
an OTA, (2) determine that traditional and
non-traditional government contractors are
interested in and capable of performing the
work, and (3) secure feedback from the
marketplace on these approaches.

Commercial Solutions Opening (CSO) as
defined in DFARS 212.70 and 10 USC 3458
-Potential Areas of Interest:
a.Technical
a.Low Code/no Code tools
b.Sandbox Environment
c.Artificial Intelligence Tools
d.Software Development Lifecycle Tools
e.Data Migration/Conversion Tools
f.User Interface / User Experience
(UI/UX)
g.GIT Repository and Alternatives
h.Reporting Tools
i.Automated Testing Tools
j.Job Scheduling Tools
k.Middleware platform
l.End-User Printing from SAP
b.Business Processes
a.Business Process Re-
Engineering/Modeling
b.Training
c.Studies and Analysis
d.Modeling and Simulations of Process &
Policy Change Scenarios
e.Finding Efficiencies in Cost, Schedule,
and Performance of Navy ERP+
f.Cost Estimating Tools

Competitive Prototype Project(s) (FAR or
non-FAR instruments such as an Other
Transaction Authority (OTA) agreement) 10
USC 4022
-The Navy intends to utilize a
competitive multi-phased down-select
approach to identify the Navy ERP+
Developer/Integrator.
-CSO will include options to award
commercial contractors or OTAs.

SECTION 4: NAVY ERP+ ASSUMPTIONS

The Government welcomes feedback,
comments, challenges, or data to support or
refute any of the following assumptions:

-CSO enables risk reduction that can be
achieved through use of innovative
commercial solutions to address the areas
of interest.



SECTION 5: QUESTIONS WE HAVE

The following questions we need your help
to answer.
1.Can the Government expect to receive
innovation commercial solutions in response
to calls posted on a CSO for Navy ERP+?
2.Does the vendor base for these
technology and business areas include non-
traditional defense contractors as defined in
10 USC 4022 (d)?
3.Do traditional defense contractors
have cost share ideas to satisfy the
requirements of 10 USC 4022?
4.Does your firm currently have ERP
capabilities?
5.Does your firm have an innovative
commercial solution and is the solution
Federal Risk and Authorization Management
Program (FEDRAMP) and IL4 compliant?
6.How can small business participation
in a CSO be improved?
7.How can PEO MLB and the Navy ERP
Financial IT Services Program Office reach
and attract non-traditional defense
contractors?
8.Please recommend additional areas of
interest for a Navy ERP+ CSO.

SECTION 6: RESPONSE FORMAT AND
DELIVERY
1.Cover Letter (not to exceed two (2)
pages) with the following:
a.Name of firm, Commercial and
Government Entity (CAGE) Code, Business
size for NAICS 541512, Traditional or Non-
Traditional Defense contractor
b.Affiliation to include parent or
subsidiary corporation information, joint
venture partners, potential teaming
partners, or potential role in a future
contract or acquisition for Navy ERP+.
c.Point of contract for business
development, technical expertise, and
contract execution
d.Current ERP related work performed
or use cases of you innovative commercial
solution in public or private entities
2.Responses should not exceed five (5)
pages, 8”x11” 11 pt font.
3.Submissions due by noon EDT 23 July
2024.

Any questions regarding this RFI or Navy
ERP shall be directed to
pmw220_ERP_plus@us.navy.mil no later
than Noon EDT 12 July 2024. The
Government will make every effort to
answer questions and post responses daily
but cannot guarantee that all questions will
be answered before the RFI response
submission deadline.

SECTION 7: CONFLICT OF INTEREST AND
SUPPORT CONTRACTORS

See FAR 9.505 - Current contractor support
services (CSS) supporting PEO MLB are not
eligible to respond to this RFI or award of
any possible resulting contracts. NAVWAR
uses contracted support services in the
review and evaluation of RFI Responses.
The contractors have executed Non-
Disclosure Agreements (NDA) with the
Navy. If you require an NDA executed
directly with the vendor to accommodate
your response, please contact the
contracting officer at
robyn.l.kedrow.civ@us.navy.mil .

Support contractors utilized by PEO MLB
and stakeholders include the following:
Boston Consulting Group, Booz Allen
Hamilton, Bowhead, Government Solutions,
and Falconwood, OliverWyman (SeaTech),
Kupono, Deloitte, and Tecolote.

SECTION 8: INDUSTRY COLLABORATIONS

The Government reserves the right to
conduct one-on-one meetings in person or
virtually with respondents to this RFI or ERP
system integration experts. The
Government may or may not choose to
interact with select respondents in order to
perform market research. Such exchanges,
should they occur, would be solely for the
purpose of obtaining further clarification of
industry’s potential capabilities,
experiences, and perspectives and for the
purpose of conducting product
demonstrations at the Government’s
discretion. Additional RFI’s may be released.