RFP Corrections
77 KB Posted
- Attached to
- PEOPLESOFT HCM EXPERTISE FOR ENTERPRISE HUMAN RESOURCES AND PAYROLL (EHRP) APPLICATION SUPPORT SERVICES
- Solicitation number
- (SOL)HHSP2332010EAD
About this file
RFP CORRECTIONS
Text of this file
(SOL)HHSP2332010EAD
AMENDMENT NUMBER TWO
Corrections to Enterprise HR Application Support Services Program: PeopleSoft HCM Expertise for EHRP Application Support Services RFP
| Page |
| Section |
| Old Language |
| New Language |
| 2 |
| B. |
| PSC will award the initial task order for EHRP application support to vendors awarded an IDIQ contract in the PeopleSoft area of expertise as defined in this RFP. |
| PSC will award the initial task order for EHRP application support to one of the vendors awarded an IDIQ contract in the PeopleSoft area of expertise as defined in this RFP. |
| 8 |
| C.2.3 |
| For example, EAD enhanced EHRP to support Title 38 and Title 45 employees and to support market pay, converted the in-house payroll system to DFAS, upgraded from HCM 8.0 to 8.9, and upgraded from Oracle 8 to 9. |
| For example, EAD enhanced EHRP to support Title 38 and Title 42 employees and to support market pay, converted the in-house payroll system to DFAS, upgraded from HCM 8.0 to 8.9, and upgraded from Oracle 8 to 9. |
| 31 |
| C.6.1 |
| Offerors eligible to be awarded an IDIQ contract to provide enterprise HR application support services for this expertise area must demonstrate experience with PeopleSoft HCM federal application version 8.9 or higher to be considered and should demonstrate experience in a large-scale federal, multi-vendor environment |
| Offerors eligible to be awarded an IDIQ contract to provide enterprise HR application support services for this expertise area must demonstrate experience with PeopleSoft HCM U.S. Federal Government version 8.9 or higher to be considered and should demonstrate experience in a large-scale federal, multi-vendor environment |
| 33 |
| Table 4, Requirement Area 1.1 |
Contractor role
| Transition EHRP application operations, maintenance, and infrastructure services from the incumbent. |
| Transition EHRP application support requirements 2.0 (Application Operations), 3.1 (Application development) and 3.4 (Quality assurance testing) from the incumbent. |
| 33 |
| Table 4, Requirement Area 1.2 |
Contractor role
| Transition Objective 1 EHRP application operations, maintenance, and infrastructure services to the incoming contractor. |
| Transition Objective 1 EHRP application support services (Requirement areas 2.0 to 8.0) to the incoming contractor as requested by EAD. |
| 34 |
| Table 4, Requirement Area 2.2 |
Contractor role
| Supplement EAD Level 1 and Level 2 support staff as volume dictates. |
| Supplement EAD Level 1 support staff as volume dictates. |
| 34 |
| Table 4, Requirement Area 2.2 |
Contractor role
| Not Applicable. |
| Added bullet: |
Provide Level 2 functional support to respond to and resolve Level 2 EHRP issues as assigned by EAD
| 38 |
| Table 4, 8.0 Project management services |
Requirement area
| Not applicable. |
| Added: |
8.1 – 8.5
| 38 |
| C.6.2 |
| EAD also seeks limited support to supplement federal resources at Levels 1 and 2, either when federal staff members are on leave or during peak times of support such as after a major release. |
| In additional to Level 3 help desk support, EAD also seeks Level 2 functional support to respond to and resolve Level 2 help desk issues as assigned by EAD. EAD requires limited support to supplement federal resources at Level 1, either when federal staff members are on leave or during peak times of support such as after a major release. |
| 81 |
| Table 7 |
| Old Table 7 page limits |
| See new Table 7 page limits (further below). |
| 83 |
| L.1.1.3.2 Volume 1, Section 2.2: Past Performance |
| If a subcontractor or teaming partner is proposed and will perform a major or critical aspect of the requirement, the offeror should submit related experience for the subcontractor or teaming partner. |
| If a subcontractor or teaming partner is proposed, the offeror should submit related experience for the subcontractor or teaming partner. |
| 83 |
| L.1.1.3.2 Volume 1, Section 2.2: Past Performance |
| For the sole offeror, or for the team lead and each major subcontractor or teaming partner, offerors must submit no more than five related experience of current or completed contracts for each service capability area (related experience can include federal, state, and local government and private entities) during the past 3 years. |
| Offerors must submit no more than five related experience of current or completed contracts (related experience can include federal, state, and local government and private entities) during the past 3 years for the sole offeror, or for the team lead, and no more than three for each subcontractor or teaming partner. |
| 84 |
| Past Performance template |
| Experience working in a multivendor, large-scale and complex fee-for-service O&M environment (describe the context, your role, challenges and outcomes). Describe an incident where you. Describe your approach and how the issues were resolved: |
| Experience working in a multivendor, large-scale and complex fee-for-service O&M environment (describe the context, your role, challenges and outcomes). Describe your approach and how the issues were resolved: |
| 86 |
| L.1.1.4 Volume 1, Section 3 |
Second business scenario
| Refer to section C.6.2 for more details on the strategic analysis portion of this task |
| Refer to section C.6.3 for more details on the strategic analysis portion of this task |
| 88 |
| L.1.2.1.1 Volume 2, Section 1.1: Objective 1 Technical Approach |
| Method for supporting the EAD program in the face of the following government business scenario: |
HHS has identified the need to upgrade the UFMS system to Oracle Federal Financials version 12. This application interfaces directly with EHRP and could also impact the AFPS interface. This development and implementation effort has been assigned to you. You will be responsible for conducting the necessary analytical activities required to assess the implementation impact of this new development effort.
The offeror should describe its approach to analyzing, assessing the impact of, and implementing the EHRP interface and should clearly state any assumptions. The approach should specify the activities required, their dependencies, the specific actions taken, and the parties involved, including handling and frequency of communication, the recipients of the communication, and the communication type for the scenario. The offeror should note if and when its approach results in artifacts or deliverables. The offeror should summarize the approximate timeline of activities, staffing requirements, and any other information deemed pertinent to this scenario including assumptions.
Delete entire bullet.
| 90 |
| L.1.2.1.3 Volume 2, Section 1.3: Performance Management Plan |
| The offeror should provide a completed performance management plan using the template in Table 5, which contains sample data. |
| The offeror should provide a completed performance management plan using the template in Table 8, which contains sample data. |
| 91 |
| L.1.2.1.4 Volume 2, Section 1.4 |
| The offeror should define how the services associated with the PSC enterprise O&M core services task order will be in compliance with the established EIT accessibility standards. |
| The offeror should define how the services associated with the PSC Objective 1 task order will be in compliance with the established EIT accessibility standards. |
| 93 |
| L.1.4 |
| Sections: L.1.4, L.1.4.1, L.1.4.2 |
| Sections: L.1.3, L.1.3.1, L.1.3.2 |
| 93 |
| L.1.3.1 Volume 3, Section 1 |
| If not, offerors should provide other substantiating documentation. |
| If not, offerors should provide other substantiating documentation. In lieu of pre-negotiated Schedule rates, the Offeror shall propose fixed loaded hourly labor rates for each labor category proposed. For each fixed loaded hourly rate, the Offeror shall identify the unloaded rate, fringe benefit rate, overhead rate, G&A rate and the amount of profit applied to each labor category. Unloaded rates shall be supported by leave and earnings statements and/or salary rate schedules. The Offeror shall indicate how category averages (if applicable), indirect costs and profit have been computed and applied. A copy of the Offeror’s current indirect rate agreement with its cognizant audit agency must be included, if available. |
The Offeror shall indicate whether current employee hourly rates or escalated rates are used. If escalation is included, state the percent and methodology (e.g., annual flat rate applied to the base rate as of a specific date or a midpoint rate for the period of performance). Salary increases that are anticipated during the performance of the resultant contract must be figured into our fixed loaded hourly rate. The date of hire and anniversary dates for employees must also be included in your proposal. In addition, your proposal must state whether any additional direct labor (new hires) will be required during the period of performance. If so, indicate the number of positions to be filled and the anticipated date of hire. The Offeror must also indicate the number of hours per year on which hourly rates are based.
The Offer shall also list commitments relating to the specified work or services which may interfere with the completion of the work or services contemplated under this proposal or which may be impacted by performance of this work. The Offeror shall also indicate if it has the necessary financial capacity, working capital, and other resources to perform without assistance form any outside sources. (If not, indicate the amount required and the anticipated source.)
| A-1 |
| Attachment A |
| During the transition period, EAD anticipates approximately five mission-critical incumbent contractor resources who will be available to support transition to the incoming contractor from contract award through July 15, 2010. |
| During the transition period, EAD anticipates approximately five mission-critical incumbent contractor resources who will be available to support transition to the incoming contractor from contract award through August 15, 2010. Incumbent resources will support transition activities under Requirement area 2.0, 3.1 and 3.4, which includes documentation of release notes. |
| B-1 |
| Attachment B |
| See Microsoft Excel file named “Attach_B_PriceTemplate.XLS |
| See Microsoft Excel file named “Attach_B_PriceTemplate_corrected.XLS |
See Updated Table 7 on next page:
Table 7. Page Limits for RFP Submission
| Volume |
| Section |
| Page |
limit
| 1: Program Technical Proposal |
| Transmittal/Cover Letter |
| 2 |
Section 1:
Executive Summary
Section 2:
Corporate Capability and Past Performance
Capability Area and Related Experience
Capability Area and Related Experience Appendix
Past Performance
NA
—a
Section 3:
Program Technical Approach
2: Objective 1 Technical Proposal Section 1:
Objective 1 Technical Approach and Understanding of the Problemb Objective 1 Technical Approach
Transition Management Plan
Performance Management Plan
Section 508 Compliance
Section 2:
Objective 1 Project Staffing
Personnel Capability Appendix
Price Template—Technical Version
Resume Appendix Commitment Letters
NA
NA
NA
NA
| 3: Price Proposal |
| Section 1: |
Proposed Rate Schedule
NA
Section 2:
Objective 1 Price Proposal
NA
a See RFP Section L.1.1.3.2 for instructions on page limits for Past Performance.
b The page limit for Volume 2, Section 1 in its entirety is 36 pages.
PAGE
Other files
| File | Type | Posted |
|---|---|---|
| AttachmentB_Price Template_corrected.xls | XLS spreadsheet | |
| SF30AMENDMENTTWO.doc | DOC document | |
| PeopleSoft IDIQ_RFP Q A_Final v 10.doc | DOC document | |
| AttachmentB_Price Template_corrected.xlsx | XLSX spreadsheet | |
| AttachmentF_Contractor Guide.pdf | ||
| AttachmentB_Price Template.xlsx | XLSX spreadsheet | |
| Attachment G_PSCForm82.pdf | ||
| EAD_IDIQ_Final_v7.doc | DOC document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
File details come from the government source that posted it. Updated .