Defense Civilian Pay System (DCPS)

Performance Work Statement (PWS)

To provide comprehensive functional and technical support for the Defense Civilian Pay System (DCPS), ensuring its continued development, maintenance, and operation.

The contractor will provide full software lifecycle support for DCPS, including:

• Software and database design, development, and maintenance.
• System change request analysis, testing, and implementation.
• Configuration and release management.
• Systems interface support.
• Customer inquiries and production support.
• Performance measurements and audit readiness.
• Information assurance.

Quality Assurance Plan (QAP) required. Performance standards are detailed in the Performance Requirements Summary (PRS) at Technical Exhibit 1, covering areas like documentation, requirements analysis, technical design, programming, testing, systems support, and production control.

• Period of Performance: One (1) Base Period of 12 months and four (4) 12-month option periods.

• Place of Performance: DFAS Indianapolis Center or other agreed-upon locations. Travel within CONUS may be required.

• Security: U.S. Citizenship, Selective Service registration (males), favorable fitness review, and background investigation (Tier 3 or equivalent) are mandatory. Continuous vetting and specific DFAS/DoD security regulations must be followed. Personnel require a Common Access Card (CAC).

• Hours of Operation: Standard hours are 6:00 am to 6:00 pm, Monday-Friday, with 24/7 production support required. Extended/emergency hours may be necessary with advance notice.

• Training: Mandatory security and role-specific training (e.g., Cyber Awareness, Privacy Act, Insider Threat) must be completed by contractor personnel.

• Section 508 Compliance: All Information and Communication Technology (ICT) must comply with Section 508 of the Rehabilitation Act.

• Government Furnished Items: DFAS will provide workspace, office supplies, hardware, telecommunications, network access, software, and storage for on-site personnel. Remote personnel will receive logon IDs and VPN access.

• Knowledge Transfer: A phase-out plan for knowledge transfer to the new contractor or government staff is required.

• Organizational Conflict of Interest (OCI): Contractors must notify the CO of any potential OCI and submit a mitigation plan.

• Deliverables: Various reports (P&C, Status, Management), plans (SDP, SCMP), specifications (SRS, SSS), and documentation (Manuals, Descriptions) are required as detailed in the Deliverables Schedule (Technical Exhibit 2).

Questions & Answers / Clarifications

This document contains questions submitted by potential vendors and the Government's responses regarding the DCPS Labor Contract Support Recompete. It aims to clarify requirements and gather information on vendor capabilities related to the Performance Work Statement (PWS).

• Corporate Information: Vendors must provide Company Name, GSA Contract Number (if applicable), UEI Number, CAGE Code, company website, and a designated Point of Contact. Business size and socio-economic categories are also required.
• NAICS/PSC Codes: Vendors are asked to recommend appropriate NAICS and PSC codes for the described scope of work.
• Corporate Experience: Vendors must detail their capability to perform the PWS services, provide examples of similar large-scale legacy government financial or payroll system support (especially on IBM Mainframe/z/OS), and describe experience supporting multi-stakeholder systems with numerous interfaces.
• Audit Support: Vendors need to describe their experience supporting systems undergoing federal financial and system audits (e.g., GAO, DoD IG, RMF, FISCAM, SSAE18), including their role in producing artifacts, researching findings, and implementing resolutions.
• PWS Sufficiency: Vendors are asked if the PWS provides sufficient detail for RFQ response preparation and to identify any areas needing more information.
• Production Support: Vendors should provide examples and methodologies for 24/7 production support, including monitoring, issue resolution, and handling unplanned program terminations (ABENDs).
• Performance Metrics: Vendors are requested to suggest additional tools/processes for monitoring and reporting against performance thresholds, and to identify any metrics that should be removed and why.
• Deliverables: Vendors are asked to suggest additions or removals from the list of Software Development Lifecycle deliverables in the PWS.
• Knowledge Transfer: Vendors should assess the adequacy of the PWS knowledge transfer plan for a 90-day transition and identify any additional required details.
• Staffing: Vendors must confirm if they have staff available with the required multi-year experience for legacy (IDMS, COBOL, JCL) and modern systems, and identify any hiring challenges.
• Key Personnel: Vendors are asked to identify positions they would consider key personnel for a similar engagement.
• Subcontracting: Vendors should indicate the anticipated percentage of work to be subcontracted.
• Rough Order of Magnitude (ROM): Vendors are asked to provide a high-level ROM based on workload data or specify what additional information is needed.

This RFI seeks information to inform the final solicitation. Responses will help the Government refine requirements, understand industry capabilities, and potentially adjust the PWS, deliverables, and evaluation criteria. Vendors should use this RFI to assess their own capabilities and prepare for a potential future solicitation.