RFP 378136 - Peoplesoft Professional Support - Addendum 004 - QA.xlsx

XLSX spreadsheet 13 KB Posted

Attached to
REQUEST FOR PROPOSAL; HMIS RFP# 378136 REV. 04
Solicitation number
378136
Issued by

About this file

This document is an Addendum 004 Q&A for RFP 378136 concerning a PeopleSoft Enterprise Resource Planning (ERP) implementation for Hanford Mission Integration Solutions, LLC (HMIS). The Q&A covers detailed technical requirements across Financials & Supply Chain (FSCM 9.2), Human Capital Management (HCM 9.2), Project Costing, Payroll, and Succession Planning modules. Key aspects include implementing a new financial system with multiple business units, configuring journal approval processes, enabling project costing, and integrating various financial and HR functionalities.

The solicitation is for professional services supporting the Hanford Mission Essential Services Contract with the U.S. Department of Energy, Richland Office. Critical dates include: Intent to Bid due June 18, 2025, Preproposal Conference on June 23, 2025, Questions due June 26, 2025, and Proposals due July 3, 2025. The period of performance covers a base year and one option year (2025-2027), with project presentations scheduled between July 21-30, 2025. The implementation will focus on modernizing financial systems, project costing, payroll, and HR processes, with an emphasis on DOE best practices and potential workflow improvements.

View the file

Other files

File Type Posted
RFP 378136 - Addendum 004.pdf PDF
RFP 378136 - Peoplesoft Professional Support - Addendum 003 - QA.xlsx XLSX spreadsheet
RFP 378136 - Addendum 003.pdf PDF
RFP 378136 - Addendum 002.pdf PDF
RFP 378136-Q and A (includes pre-proposal Q and A) - Addendum 001.xlsx XLSX spreadsheet
RFP 378136 - Addendum 001.pdf PDF
Attachment 1-PWS-Req. 378136 Rev. 0 - Peoplesoft Professional Support.pdf PDF
Exhibit 2_Subcontract Release (Example).pdf PDF
Exhibit 1_ Proposal Structure Guidelines.pdf PDF
Exhibit 3_FFP (Comp Sch - Example).xls XLS spreadsheet
Attachment 7-Intellectual Property Agreement (C-7000-010).pdf PDF
Attachment 4_Special Provisions (SP_5)-On_Site Rev 2 2023-12-4.pdf PDF
Attachment 3_Special Provisions_Software Rev. 1 2020-12-09.pdf PDF
Appendix C-PeopleSoft Time and Labor Requirements.xlsx XLSX spreadsheet
Attachment 1-PWS-Req. 378136 Rev. 0 - Peoplesoft Professional Support.pdf PDF
Appendix A-PeopleSoft Enterprise Resource Planning Finance Requirements.xlsx XLSX spreadsheet
Attachment 5_SCA Wage Determination 2015_5527 Rev 24_ 2024-12-23.pdf PDF
Attachment 2_HMIS General Provisions_Commercial Provisions Rev 8 2023-12-04.pdf PDF
Appendix B-PeopleSoft Human Capital Management Requirements.xlsx XLSX spreadsheet
Attachment 6_Non_Disclosure Agreement (NDA).pdf PDF
Request For Proposal (RFP) 378136.pdf PDF
Show all 21

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Addendum 004 - Q&A

RFP 378136 - Peoplesoft Professional Support - Addendum 004
LineQuestionHMIS Response
1Financials & Supply Chain (FSCM 9.2) - General Finance & Chart of Accounts:

A. Key pain points in current Financial and Project-Costing processes the new solution must address.

B. Which workflow/approval processes (e.g., voucher, journal) are critical and must be configured at go-live?

C. List significant customizations in current Financial and Project-Costing systems that HMIS deems essential to replicate or replace.

D. Has HMIS licensed Customer Contracts and, if so, should it be included in scope?

E. Is a Chart-of-Accounts redesign in scope?

F. Do source systems migrating to PeopleSoft already share the same COA values, or will mapping be required?

G. Current state of the Vendor Master—will data-cleansing be required?

H. How many external banks and bank accounts must be configured for AR, AP, and Cash Management?

I. May eBill Payment be deferred to a later phase?\

J. Largest challenges HMIS faces in contract billing (e.g., FAR, DCAA) that must be solved.

K. How many punch-out catalogues must be integrated, and do any require real-time pricing calls? A. Please post financial pain points file.

B. Journal approval process is the only critical at this time, all others are TBD

C. TBD

D. Not at this time, but is in consideration but not currently in scope. Please address as an option.

E. Currently a shared GL then broken down by Company/BU, TBD as a split by Company

F. Share same COA

G. Yes

H. AR: 5; AP: TBD; Cash Management: 5

I. TBD

J. Currently it is a manual process

K. None 2 Financials & Supply Chain (FSCM 9.2) - General Ledger:

A. Does HMIS already populate the “Project” ChartField in GL, and will historical journals need conversion to align with Project Costing?

B. Will multiple business units remain post-go-live, or is consolidation planned?

C. Are new variance-pricing analytics required for budget-vs-actual labor-cost comparisons? A. "Project" Charfield in GL is used as Charge Code (CACN) at this time. Will need to look at how CACN in GL reconcile to Projects in GL. Purge of Journals year to year so conversion may not need to be done.

B. Will require multiple business units

C. Yes 3 Financials & Supply Chain (FSCM 9.2) - Project Costing & Commitment Control:

A. Is this a first-time Project Costing implementation requiring significant data conversion, or is PC already in use?

B. Will Commitment Control be enabled, and at which budget levels (project, activity, resource)?

C. Should variance-pricing be enabled to recharge higher/lower internal rates across DOE programs?

D. Is an early conversion prototype needed to prove historical-cost integrity?

E. Will HMIS adopt the Image 53 Rush Requisition flag for critical buys?

F. How many punch-out catalogues must be integrated, and do any require real-time pricing calls? A. PC is already in use

B. TBD

C. Yes

D. Yes

E. Not during this Phase

F. Not during this Phase 4 Human-Capital Pillar (HCM 9.2) - Payroll (North American / Federal):

A. Will Payroll post labor distribution directly to Project Costing / GL, and what combo-code structure must be validated?

B. Are there bespoke garnishment or retro-calc rules unique to DOE/Hanford that must be retained?

C. How many parallel pay runs will HMIS require before cut-over (cycles and sample size)? A. Yes; TBD on combo-code structure at this time

B. Not unique standard

C. Please refer to RFP and pre-proposal conference/meeting info.

5 Human-Capital Pillar (HCM 9.2) - Succession & Career Planning:

A. Which key roles need succession plans, and what readiness scale (e.g., 9-box) should be used?

B. Will Talent Profile competencies be loaded from spreadsheets or external systems?

C. Should Talent Reviews route through AWE approvals or rely on delivered meeting-workspace pages?

D. KPIs required for bench-strength and readiness and whether they feed DOE HR scorecards.

E. Is a link to the LMS required for development-plan tracking? A. All management level positions and SME roles grade 18 and higher (essential personnel)

B. Not currently in Peoplesoft looking to modernize with this implementation

C. Will route through AWE approvals with further configuration

D. Looking to implement best practices

E. No

6Are there any DOE-wide ERP integration or data standards that HMIS must conform to (e.g., DOE OCIO mandates)Best practices
7Is HMIS DOE integrated lab or working as a subcontractor? If integrated lab, are you changing letter of credit provider in conjunction with the system changeWorking as Subcontractors
8

Finance:

A. What workflow structures are currently in place? Do they involve multi-level approvals?

B. How much historical data (in years or volume) is expected to be migrated into the new environment?

C. Since PO/Inventory functionality is not in scope and not currently in PeopleSoft, what external systems are used today and how do they integrate with PeopleSoft? What are your expectations for these integrations in the new environment?

D. What is the primary driver for Project Costing implementation?

E. Will Project Costing need to integrate with legacy procurement or external financial systems?

F. How many existing ChartField combinations are currently in use, and are there known cleanup efforts underway?

G. What percentage of current transactions utilize project details? What is the target percentage for future transactions?

H. Do you expect a full ChartField redesign or reconfiguration?

I. Do you currently follow a defined and documented month-end process?

J. Can you confirm whether data mapping and conversion ownership will be led by HMIS, with consulting support focused on tools and facilitation only?

K. How’s current budget check on spending is performed?

L. How many contracts do you currently have?

M. What is the maximum number of funding sources on individual contracts.

N. Please confirm whether a phased go-live by functional module (e.g., Financials and Project Costing by Sept 2026; HCM modules in FY27) is required. If so, are there any DOE-mandated sequence requirements for module go-lives? A. No current workflow structures in place but a great opportunity for improvements

B. For Finance back to January 2021; rest of finance is archived by FY in a datawarehouse

C. Multiple files and integrations uploads into Finance and Finance feeds out to multiple systems

D. It is a re-implementation (upgrade) as we use Project Costing today

E. Need to integrate with Asset Suites Procurement and no external financial systems

F. Very light usage of the combination rules, another opportunity for best practices

G. Need further information on this question

H. Do not anticipate a full but some changes

I. Yes

J. Previously answered

K. No current system budget check

L. Each Contractor has a Prime contract with multiple Task Order per company. There are also Contracts (Inter-company) ~700 for one company and the others have ~200 each

M. Per company/DOE Contract on average there is ~350 fund source lines tracked which can increase or decrease depending on "active".

N. Yes on Financials by FY26 and all others are to run in parallel

File details come from the government source that posted it. Updated .