PWS - FSC OM FY26 - Draft .docx

FSC Operations and Maintenance Support

VA-XX-XXXXX

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Financial Service Center (FSC) Operations and Maintenance Support

Date: December 17, 2025 TAC Number: VA-XX-XXXXX PWS Version Number: 0.4

Contents

BACKGROUND

The Department of Veterans Affairs (VA), Financial Services Center (FSC) is authorized by the Government Management Reform Act of 1994 (Public Law 103-356) to provide common administrative support services on a reimbursable basis to VA and Other Government Agencies (OGA’s), as a Franchise Fund. The goals of the Franchise Fund organizations include:

· Lowering overhead costs

· Improving the quality and delivery of services

· Creating economies of scale

· Eliminating redundant services

· Being auditable

VA-FSC requires operations and maintenance (O&M) support and related support to operate, maintain, and implement upgrades/enhancements for the VA Enterprise Resource Planning (ERP) system. This system is used to accounting, financial, acquisitions, reporting, and related transactions. As a franchise organization, the FSC has existing and potential customers that can be migrated into the system.

VA-FSC selected Momentum® ERP, a commercial-off-the-shelf system rebranded as Integrated Financial and Acquisition Management System (iFAMS). Currently the following VA offices have migrated to iFAMS: National Cemetery Administration (NCA), VA Staff Offices, Veterans Benefits Administration (VBA) General Operating Expense funds, VBA Loan Guaranty business line, and Veterans Health Administration (VHA) station 134. VA plans to migrate the remaining VA stations and processes to iFAMS.VA plans to move all financial and acquisitions work from legacy systems to iFAMS.

APPLICABLE DOCUMENTS

In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:

1. “Federal Information Security Modernization Act of 2014”

2. Federal Information Processing Standards (FIPS) Publication 140-3, “Security Requirements for Cryptographic Modules”, March 22, 2019

3. FIPS Pub 199. “Standards for Security Categorization of Federal Information and Information Systems,” February 2004

4. FIPS Pub 200, “Minimum Security Requirements for Federal Information and Information Systems,” March 2006

5. FIPS Pub 201-3, “Personal Identity Verification of Federal Employees and Contractors,” January 2022

6. 10 U.S.C. § 2224, "Defense Information Assurance Program", as amended

7. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”

8. Public Law 109-461 (P.L. 109-461), Veterans Benefits, Health Care, and Information Technology Act of 2006, as amended, Title IX, Information Security Matters

9. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”, as amended

10. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, https://www.va.gov/vapubs/index.cfm

11. VA Handbook 0710, “Personnel Security and Suitability Program,” May 2, 2016, https://www.va.gov/vapubs/index.cfm

12. VA Directive 6102, “Internet/Intranet Services,” August 5, 2019

13. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” as amended

14. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016

15. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”, as amended

16. NIST SP 800-66 Rev. 2, “Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule: A Cybersecurity Resource Guide,” February 2024

17. 45 C.F.R Parts 160 and 164, Subparts A and E, the Standards for Privacy of Individually Identifiable Health Information (“Privacy Rule”); and 45 C.F.R. Parts 160 and 164, Subparts A and C, the Security Standard (“Security Rule”); as amended

18. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended

19. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004

20. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021 (see VA NOTICE 24-18, dated September 27, 2024, “Update to VA Directive 6500 Cybersecurity Program”, and VA Notice 25-07, dated 3/18/25, “Amending VA Directive 6500 to incorporate M-24-15”)

21. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021 (see VA Notice 25-01, dated October 15, 2024, “Update to VA Handbook 6500 Risk Management Framework for VA Information Systems VA Information Security Program”, and VA Notice 25-06, dated 3/18/25, “Amending VA Directive 6500 to incorporate M-24-15”)

22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” June 30, 2023

23. VA Handbook 6500.6, “Contract Security,” March 12, 2010 (see VA Notice 24-12, dated April 22, 2024, “Update to VA Handbook 6500.6, Contract Security, Appendix C VA Information and Information System Security/Privacy Language For Inclusion Into Contracts, As Appropriate”)

24. VA Handbook 6500.8, “Information System Contingency Planning,” March 25, 2025

25. VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018

26. VA Handbook 6500.11, “VA Firewall Configuration,” August 22, 2017

27. OIT Process Asset Library (PAL), OIT Process Asset Library

28. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)

29. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014

30. VA Directive 6510, “VA Identity, Credential and Access Management,” September 3, 2024

31. VA Handbook 6510, “VA Identity, Credential and Access Management,” September 27, 2024

32. VA Directive and Handbook 6513, “Secure External Connections,” October 12, 2017

33. VA Directive 6300, “Records and Information Management,” September 21, 2018

34. VA Handbook, 6300.1, “Records Management Procedures,“ March 24, 2010

35. NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018

36. NIST SP 800-53 Rev. 5, “Security and Privacy Controls for Federal Information Systems and Organizations,” September 23, 2020 (includes updates as of 12/10/2020)

37. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” October 26, 2015

38. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” March 24, 2014

39. OMB Memorandum 05-24, “Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors,” August 5, 2005

40. OMB Memorandum M-19-17, “Enabling Mission Delivery Through Improved Identity, Credential, and Access Management,” May 21, 2019

41. OMB Memorandum, “Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation,” May 23, 2008

42. Federal Identity, Credential, and Access Management (FICAM) Architecture, June 30, 2023 (FICAM Architecture (idmanagement.gov))

43. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,“ June 2018

44. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, “Digital Identity Guidelines,” updated March 02, 2020

45. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014

46. VA Memorandum, VAIQ #7100147, “Continued Implementation of Homeland Security Presidential Directive 12 (HSPD-12),” April 29, 2011 (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

47. IAM Identity Management Business Requirements Guidance document, May 2013, (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

48. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

49. Trusted Internet Connections (TIC) 3.0 Core Guidance Documents, https://www.cisa.gov/publication/tic-30-core-guidance-documents

50. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019

51. OMB Memorandum M-08-23, “Securing the Federal Government’s Domain Name System Infrastructure,” August 22, 2008

52. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (P.L. 110–140), December 19, 2007

53. Section 104 of the Energy Policy Act of 2005, (P.L. 109–58), August 8, 2005

54. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001

55. VA Directive 0057, “VA Environmental Management Program,” October 25, 2022

56. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

57. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103

58. “Veteran Focused Integration Process (VIP) Guide 4.0,” March 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

59. VA Memorandum “Proper Use of Email and Other Messaging Services,” January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

60. “Product Line Management Transformation Playbook” version 3.1, August 2023, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

61. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020

62. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),” November 19, 2020

63. Social Security Number (SSN) Fraud Prevention Act of 2017

64. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018

65. C.F.R Title 15 Part 7, “Securing the Information and Communications Technology and Services (ICTS) Supply Chain”, as amended

66. Executive Order 14028, “Executive Order on Improving the Nation's Cybersecurity,” May 12, 2021,

67. OMB Memorandum M-22-09, “Moving the U.S. Government Toward Zero Trust Cybersecurity Principles”, January 26, 2022, https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf.

68. NIST SP 800-52 Revision 2, “Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations

69. OMB M-22-18, “Enhancing the Security of the Software Supply Chain through Secure Software Development Practices,” September 14, 2022

70. OMB M-23-16, “Update to Memorandum M-22-18,” June 9, 2023

71. OMB M-21-31, “Improving the Federal Government’s Investigative and Remediation Capabilities Related to Cybersecurity Incidents,” August 27, 2021

72. NIST SP 800-88 Revision 1 “Guidelines for Media Sanitization,” December 2014

73. CISA Binding Operational Directive (BOD) 19-02: “Vulnerability Remediation Requirements of Internet-Accessible Systems,” April 29, 2019, BOD 19-02: Vulnerability Remediation Requirements for Internet-Accessible Systems | CISA

74. CISA BOD 22-01: “Reducing the Significant Risk of Known Exploited Vulnerabilities,” November 3, 2021, BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities | CISA

75. CISA BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks.” Cybersecurity & Infrastructure Security Agency (CISA), BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks | CISA

76. VA Directive 6550, Pre-Procurement Assessment and Implementation of Medical Devices/Systems, June 03, 2019

77. VA Memorandum, “VA Security Controls,” January 17, 2025, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010

SCOPE OF WORK

The Contractor shall provide operations and maintenance (O&M) support for iFAMS and support to support all iFAMS releases including enhancements, upgrades, etc. O&M support includes defect resolution, technical support, and installing software patches/upgrades, and associated testing, training, and organizational change management. Change requests include business rule changes, code changes, and integration with new VA interfaces. Activities included in this support include configuration, implementation, integration, testing, deployment of software, training, annual close, accounting, reconciliation, systems assurance, audit, reporting, user provisioning, communication, organizational change management, maintenance, and technical support in accordance with paragraph 5 of this PWS and its sub-paragraphs.

PERFORMANCE DETAILS

PERFORMANCE PERIOD

The Base Period of Performance (PoP) shall be 12 months from date of award, with up to two (2) 12-month option periods.

Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO). If required, the CO may designate the Contractor to work during holidays and weekends.

There are eleven (11) Federal holidays set by law (USC Title 5 Section 6103) that VA follows:

Under current definitions, five are set by date:

If any of the above falls on a Saturday, then Friday shall be observed as a holiday. Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.

The other six are set by a day of the week and month:

PLACE OF PERFORMANCE

Tasks under this PWS shall be performed at both Government and Contractor facilities and work may be performed at remote locations with prior approval of the Contracting Officer’s Representative (COR).

It is anticipated that the majority of work under this PWS shall be performed at Contractor facilities. The Contractor facilities in Washington DC Metropolitan Area shall be Metro accessible and shall be used for collaboration, meetings, and training. The Contractor principals and key personnel shall be located within local commuting area of VA facilities in Washington DC or Austin, Texas, since face-to-face meetings with Government decision makers will be required.

VA anticipates face-to-face meetings in Washington DC and Austin, Texas. VA may provide a limited number of seats in support of the work performed in this contract at the Government facility in Austin, Texas. Temporary Duty (TDY) to a government facility within the effort does not change the Place of Performance to the Government Site.

TRAVEL

The Government anticipates travel under this effort to support the breadth of program management activities relating to FSC O&M planning, initiation, deployment, and sustainment, as well as to attend program-related meetings through the PoP.

Travel is on a cost reimbursable, no fee basis and shall be in accordance with the Federal Travel Regulations (FTR) and requires advance concurrence by the Contracting Officer Representative (COR). The Contractor shall provide cost estimates with each travel request to the COR. Each Contractor invoice must include copies of all requested, applicable, and required receipts (FTR §301-11.25: required for lodging, regardless of amount, and a receipt for every authorized expense over $75) that support the travel costs claimed in the invoice.

Contractor travel within the local commuting area of 50-miles will not be reimbursed. Travel performed for personal convenience and daily travel to and from work at the Contractor’s facility will not be reimbursed. Contractor travel within the local commuting area will not be reimbursed.

SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

PROJECT MANAGEMENT

The Contractor shall plan, govern, coordinate, execute, and report on all tasks and activities performed under this TO. The Contractor shall provide management, ensure compliance, measure performance, and report on all activities through to delivery.

The Contractor shall use product line management methodologies and toolsets approved by the FSC PMO Manager so that all contract-driven activities are identified, documented, and tracked so that the contract shall continuously be evaluated and monitored for timely and quality service. The Contractor shall notify the Government PMO Manager and COR of any technical, financial, personnel, or general managerial problems encountered throughout the PoP. The Contractor shall migrate to new or revised methodologies and toolsets as they are approved by the Government. Contractor shall propose tailoring of methodologies and toolsets to improve operational efficiency.

Project Management activities for Base and Optional Tasks should be tracked and billed against that particular activity so that optional task project management is only included when and if an optional task is exercised.

Requirements contained within this Task Order requires coordination with several different resources which may be Government personnel or other Contractors. Duties will be performed through collaboration with all parties. Proper chain of command and roles and responsibilities shall be established, documented, and maintained to work effectively in this type of environment.

Coordination shall take place in writing through formal processes such as team working agreements, status reports and participation in project meetings and informal processes while working side by side. The Contractor shall work effectively with all contractors supporting FSC.

Any configuration decisions that affect the Enterprise Configuration discussed in informal processes (examples include working side by side, or in office hours meeting) will be documented and presented in formal change control process for approval.

CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor Project Management Plan (CPMP) task involves the management and oversight of all activities performed by Contractor personnel, including sub-Contractors, to satisfy the requirements identified in this PWS. The Contractor shall identify a Program Manager (PM) by name, who shall provide management, direction, administration, quality assurance, and leadership of the execution of this contract. The VA shall retain overall Program Management Responsibility. The Contractor shall operate and coordinate within the FSC and coordinate with other VA offices, under FSC supervision, as needed to complete the tasks in this project work statement. The Contractor’s Program and Project Managers shall coordinate their efforts with VA Program and Project Managers.

The Contractor shall deliver a CPMP that lays out the Contractor’s approach, timeline, and tools to be used in execution of the contract. The CPMP should take the form of both a narrative and graphic format that displays the schedule, costs, milestones, risks, and resource support. The CPMP shall contain at minimum the following sections: Cost Management Plan and baseline budget, Schedule Management Plan, Resource Management Plan, Risk Management Plan, and Quality Management Plan. The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the PWS.

The Contractor shall describe in the CPMP the organizational resources and management controls the Contractor shall employ to meet the support, schedule, quality, and performance requirements defined in this PWS. The Government will use this CPMP to manage, track, and evaluate the Contractor’s performance. The VA PM will approve the Contractor’s baseline CPMP prior to execution. The VA PM will approve any updates to the CPMP that the Contractor prepares.

The initial baseline CPMP shall be concurred upon and updated in accordance with Section B of the contract. The Contractor shall update and maintain the VA PM approved CPMP throughout the PoP.

Deliverable:

A. Contractor Project Management Plan

KICKOFF MEETING

The Contractor shall conduct a Kickoff meeting within five (5) calendar days after award to introduce the Government team, including but not limited to the COR and CO, to the Contractor’s Project Leadership Team and present the Contractor’s overall operating plans and approach for this effort. At the meeting, the Contractor shall present a Staffing and Quality plan, overall CPMP, and a high-level schedule for the task order. . Two (2) days prior to the Kick-off Meeting, the Contractor shall submit to the government an agenda, location, and virtual option of the meeting for COR approval. The Contractor’s Staffing Plan and milestones shall address all aspects of onboarding personnel required to access VA information or networks. The Contractor shall provide the meeting minutes two (2) days after the Kick-off Meeting.

During the kickoff-meeting, the Contractor shall present the following for review and approval by the Government :

a. Identification of key personnel

b. Plan to onboard staff including any risks or known issues

c. Approach managing schedule and task assignments based on SAFe Agile principals

d. Risk management approach

e. Review of all assumptions and any constraints

f. Organization and administrative structure

g. Key milestones for the first 90 days of the POP

Deliverable:

A. Kickoff Meeting Agenda B. Kickoff Meeting Minutes C. Kickoff Presentation D. Staffing plan E. Quality Plan

REPORTING REQUIREMENTS

Bi-Weekly Status Report The Contractor shall provide the COR and PM with Biweekly (every two weeks) Status Reports in electronic form per Government approved format and media. These reports shall provide accurate, timely, and complete project information supporting FSC Reporting Requirements and reflect data as of the last day of the preceding Biweekly report.

The Biweekly Status Report shall include the following data elements for each work effort supported:

a. TO Name

b. Overall high-level assessment of TO progress

c. Summary of all production releases planned within the next 30 days

d. Total number of stories and combined story points completed for the current sprint

e. Total number of stories and combined story points in progress for the current sprint

f. All stories that were transferred between sprints and reason for transfer

g. Identification of any TO related risks/issues uncovered during the reporting period and especially highlight those areas with a high probability of impacting schedule, cost or performance goals and their likely impact on schedule, cost, or performance goals

h. Explanations for any unresolved issues, including workable solutions and any actions required of the Government and/or Contractor to resolve or mitigate any identified issue, including a plan and timeframe for resolution

i. Status on previously identified issues, actions taken to mitigate the situation and/or progress made in rectifying the situation

j. Work planned for the subsequent five (5) reporting periods, when applicable. Current TO schedule overlaid on original TO schedule showing any delays or advancement in schedule

k. Workforce staffing data showing all Contractor personnel performing on the effort during the current reporting period by team. After the initial labor baseline is provided and approved, each report shall identify any changes in staffing identifying each person who was added to the TO or removed from the TO. The report shall include the replacement personnel’s resumes that include education level and other information as to replacement personnel’s qualification in general.

l. Training Certificates, after initial and updated certificates are provided, each report shall identify any changes for all Contractor personnel including the dates of expiration and the due date for the next time due

m. A Government Furnished Equipment (GFE) Report for all equipment issued to Contractor personnel performing on the effort during the current reporting period including a record of transfer of any GFE. The report shall include up-to-date information on the physical location of the GFE and to whom the GFE is assigned.

n. Original schedule of deliverables and the corresponding deliverables made during the current reporting period.

Deliverable:

A. Bi-Weekly Progress Status Report

Staffing/Resource Plan The Contractor shall deliver a Staffing/Resource Plan to the Government for approval. The Staffing/Resource Plan shall include an analysis of current and projected resource needs to meet the system requirements for performance, product quality, and security. The Contractor shall identify any known technology resource requirements. The Contractor shall propose for government approval the correct levels of staff, with optimal skill sets, that are required to support the complete iFAMS ecosystem. This includes Momentum, the iFAMS enterprise service bus (ESB), iFAMS-EZ, and business intelligence and reporting platform and content. The Staffing/Resource Plan shall include an analysis of current and projected resource needs to meet the system requirements for performance, product quality, and security. The contractor shall identify resources within 30 days of government approval.

The contractor shall alert the government if a resource is to be removed from the task order for any reason. When a resource leaves the task order, the contractor shall schedule knowledge transfer activities, designate the resource that will cover all outstanding tasks, and if the individual will be replaced or if the position is to be eliminated.

Deliverable:

A. Staffing/Resource Plan

Weekly and Monthly Status Meetings Weekly status meetings shall be scheduled by the Contractor to address progress, planned activities, risks, or conflicts that may impact the schedule, scope, or cost and any change management impacts for Operations and Maintenance efforts.

The Government and the Contractor PM shall jointly chair weekly status meetings, and these will be attended by the Contractor and Government team leads. Tasks and sub- tasks will be discussed at this meeting, with agreed upon delivery dates. The meetings shall schedule and present risks, risk status, and risk mitigation strategies.

The first weekly status meeting of the month will become a monthly status meeting where the Contractor shall discuss major schedule and accomplishments during the prior month, Performance metrics, and risk mitigation strategies and efforts.

The Contractor shall attend and support Change Control Board (CCB) meetings on a weekly basis. The Contractor shall present the status of the tasks closed during the prior week, tasks scheduled to be worked on during the current week, and the following week, impediments.

In addition, ad-hoc meetings, executive briefings, and demonstrations may be requested by the Government on an as-needed basis.

The Contractor shall produce agendas at least twenty-four (24) hours before scheduled meetings and meeting minutes no later than two (2) business days following the meeting.

In conjunction with the weekly status meetings, the Contractor shall prepare and distribute a weekly Status Report that documents the activities and achievements in the prior week and the planned activities, milestones, deliverables due, and meetings for the following week.

Deliverable:

A. Weekly Status Report

Monthly Program Management Review The Contractor shall prepare a Monthly Program Management Review (PMR), to be distributed on the first weekly status meeting of the month that documents the activities and achievements in the prior month and the planned activities, milestones, and deliverables due for the following month. The PMR report shall document any problems or unresolved issues that may impact the triple constraint (scope, schedule, and cost).

The Contractor shall prepare and deliver a PMR Report in VA format provided in Attachment A. The PMR Report shall outline primary activities conducted by the Contractor for each reporting period. The PMR Report shall measure the Contractor's cost and schedule performance using either the Government-approved WBS or a separate arrangement as mutually agreed upon by the Government and the Contractor. It shall also include but not be limited to the following:

a. Activities completed in reporting period

b. Identified risks and mitigation of risks

c. Any Government action needed

d. Monthly Performance Metrics

e. iFAMS System Availability

f. Performance Baseline

g. Planned versus actual cost per reporting period with explanations for variances

h. Planned versus actual schedule variances

i. GFE inventory implemented

j. Projected GFE requirements

k. Lessons learned

l. Current licenses: Licenses used for development and testing shall be annotated separately from those used in Production

m. Itemized list of all section 508 deliverables and current conformance status

n. Tier 2 and Tier 3 metrics

The Contractor shall require all sub-contractors to provide input to the PMR Report where there are critical or significant tasks related to the prime contract, if applicable. The Government will update the PMR template based on business needs and reporting requirements. All changes to the PMR templates will be communicated by the Government to the contractor one reporting period prior to the change.

Deliverable:

A. Monthly PMR Report

Monthly Task Order Report The Contractor shall provide to the Government’s designated personnel a Monthly FSC Task Order report in accordance with the format specified by the government. The Monthly Task Order Report shall include a list of Contractor personnel supporting each Time and Material (T&M) task and the supporting activities for each Contractor personnel, as well as the impact to the T&M budget. The Monthly Task Order Report shall comply with Activity Based Costing Labor Tracking methodology per PWS section 5.1.7. The contractor shall include ABC tracking reports, the Monthly Task Order Reports, with each submitted invoice.

Deliverable:

A. Monthly Task Order Report

KEY PERSONNEL

FSC uses Agile approach for the operations of the program. Agile principles and scrum practices will be applied to complete work where appropriate.

Program Manager:

The Contractor Program Manager shall be responsible for managing the overall performance, quality, schedule, and cost of the contract. Among other responsibilities, the Program Manager shall support the FSC in executing the systems integration activities. The Program Manager shall have successful experience in supporting a large complex Enterprise Resource Planning (ERP) system with financial and acquisition management cloud-based solution. The Program Manager shall have extensive experience with agile and traditional project management methodologies. The Program Manager shall have experience including finance, acquisitions, and technology. The Program Manager shall hold current agile certification and project management professional certifications. The Program Manager should have at minimum:

a. Active project management certification

b. Demonstrable Capability to support a large ERP product supporting 100s to 1000s of users with a target of up to 100,000

c. Minimum of 15 years’ experience in areas related to finance, acquisition, and technology.

Deputy Program Manager:

The Contractor Deputy Program Manager shall be responsible for supporting the Program Manager in managing the overall performance, quality, schedule, and cost for the contract. Among other responsibilities, the Deputy Program Manager shall support the FSC in executing their program management activities, support the Department’s transition to the iFAMS solution, preparing for governance process reviews, and assisting with communications across the capabilities of the iFAMS solution. The Deputy Program Manager shall have successful experience in supporting a large complex financial and acquisition management cloud-based solution for a Cabinet Level Agency. The Deputy Program Manager shall have extensive experience with agile and traditional project management methodologies. The Deputy Program Manager shall have experience including finance, acquisitions, and technology. The Deputy Program Manager shall hold current agile certification and project management professional certifications. The Deputy Program Manager should have a minimum:

a. Active project management certification

b. Demonstrable Capability to support a large ERP product supporting 100s to 1000s of users with a target of up to 100,000

c. Minimum of 15 years’ experience in areas related to finance, acquisition, and technology.

The Contractor key personnel for Program Manager and Deputy Program Manager shall have prior experience in large-scale financial management business transformation, shared service implementation including customer and provider side implementation, and large-scale program integration. The Contractor shall provide the titles, and a description of the duties of key personnel to be assigned to these tasks. The Contractor shall submit a resume for each key person. Each resume shall provide information with respect to:

a. Subject matter expertise and knowledge of financial management and acquisition business transformations.

b. Demonstrated project management expertise on similar complex Federal Department-wide financial and acquisition system implementations.

c. Demonstrated experience and expertise, including certification when applicable for all FSC tools in support of the Knowledge Management efforts (reference Section 5.2.2.3).

d. Subject matter expertise in Momentum is required.

Momentum Technical SMEs:

The Contractor shall provide Momentum Technical Subject Matter Experts as key personnel. The Contractor SMEs resume shall include:

a. Experience supporting a financial and acquisition management system for a Cabinet Level Agency.

b. Experience providing technical direction and guidance in the performance of analysis, requirements development, and support of Momentum.

c. Experience making recommendations on system improvements in the following specialties as they pertain to Momentum: information systems architecture, networking, automation, security, communications, software life-cycle management, modeling and simulation.

d. Experience providing technical, managerial, or administrative direction for functional domains related to IT systems and projects.

Federal Accounting SMEs The Contractor shall provide Federal Accounting Subject Matter Experts as key personnel. The Contractor SMEs resume shall include:

a. Demonstrated subject matter expertise of federal financial accounting standards including USSGL,Treasury and OMB guidance.

b. Demonstrated experience applying accounting theories, concepts, principles and standards to the financial activities of a cabinet-level government agency.

c. Experience designing, developing, and operating Momentum at a cabinet- level government agency.

d. Demonstrated experience applying professional accounting knowledge to develop innovative solutions to improve financial operations and resolve accounting, reporting and system issues.

e. Subject matter expertise in Momentum is required.

The Contractor shall provide resumes for any Key Personnel positions identified above. All submitted resumes are to be redacted to prevent disclosure of personally identifiable information (PII). Examples of PII include but are not limited to names, addresses, phone numbers, social security numbers, and birthdays/dates. For those individuals proposed as Key Personnel who are not current employees of your company, a signed a Letter of Intent will be required. The Key Personnel positions and redacted resumes of individuals who shall fill the Key Personnel positions shall be included as an attachment to the contract/order in Section D upon award.

Letters of Commitment: The Offeror shall provide written Letters of Commitment signed by the individuals concerned that are included in the Offeror’s proposal as Key Personnel. The Letters of Commitment shall indicate, at a minimum, that each individual proposed as Key Personnel was contacted after the issue date of the solicitation, that each proposed individual has consented to the submission of their Letter of Commitment by the Offeror with its proposal, and that each individual has confirmed that he/she is available for order performance. Offerors are advised that in the event it may become necessary to replace any of the proposed Key Personnel prior to and/or during the course of contract performance, the Offeror must, prior to conducting the replacement, provide the cognizant Contracting Officer with assurances that the agency will receive replacements with equal or better qualifications as compared to those Key Personnel being replaced.

During the first 90 calendar days of performance, the Contractor shall not replace or substitute Key Personnel who the Contractor proposed pre-award unless the replacement is necessitated by illness, death, or termination of employment. The Contractor shall notify the Contracting Officer within 15 calendar days after the occurrence of any of these events and provide a detailed explanation of the circumstances necessitating the proposed substitution and shall demonstrate that the proposed replacement personnel are of at least substantially equal ability and qualifications as the individual originally proposed for that position. The proposed replacement personnel shall be approved by the CO or COR prior to final determination.

After the initial 90 calendar days, any personnel the Contractor offers as substitutes for the above identified key personnel positions shall have the ability and qualifications equal to or better than the key personnel which are being replaced and shall meet or exceed the qualifications designated for that Key Personnel position. If any change to a key personnel position becomes necessary, the Contractor shall immediately notify the VA PM and COR in writing, but whenever possible Contractor shall notify the VA PM of substitutions in personnel in writing 30 calendar days prior to making any change in key personnel, and provide a detailed explanation of the circumstances necessitating the proposed substitution and shall demonstrate that the proposed replacement personnel are of at least substantially equal ability and qualifications as the individual originally proposed for that position and that the proposed replacement meets or exceeds the qualifications designated for that Key Personnel position.

The Contractor agrees that it has a contractual obligation to mitigate the consequences of the loss of Key Personnel and shall promptly secure any necessary replacements in accordance with (IAW) this PWS section. Failure to replace a Key Personnel pursuant to this clause and without a break in performance of the labor category at issue shall be considered a condition endangering contract performance and may provide grounds for default termination.

QUALITY ASSURANCE AND QUALITY CONTROL

The Contractor shall deliver an update to the Quality Assurance and Quality Control (QA/QC) Plan to the Government for approval and implement a QA/QC program which establishes, implements, and maintains QA/QC as it relates to technical quality for deliverables, work products, and services performed under this task order.

The QA/QC Plan shall document the Contractor’s QA/QC process, which will meet and comply with quality standards established in this PWS and are compliant with ISO 9001/IEC 90003 and include a monitoring and controls process.

The QA/QC Program shall address all requirements within the PWS and incorporate all processes required to develop, document, monitor, review, analyze, and conduct the Contractor's execution of the PWS It shall ensure that all developed application software and associated materials meet accepted industry standards, best practices for quality, and Federal Financial Management System requirements as detailed in OMB Circular A-127, Financial Management Systems. It shall ensure adherence to the performance measures specified in the Performance Requirements Summary (PRS) defined in the task order a Quality Assurance and Surveillance Plan (QASP). The Government will use this QASP to measure Contractor performance against the metrics defined in this PWS.

Consistent with QA/QC plan, the QA/QC program shall include management and technical reviews and audits to validate the quality of the work performed by the Contractor's personnel and of the work performed by its sub-contractors. Management and technical reviews and audits will be performed by personnel/sub-contractors not directly responsible for the work performed.

The Contractor shall maintain records documenting all corrective actions and process improvements undertaken during contract performance. The records shall validate the Contractor's compliance with the processes contained in the QA/QC plan. The Contractor shall make the records available to the Government during contract performance.

The Government has the right to perform periodic surveillance of the Contractor to assure that the Contractor's work products and QA processes are in compliance with the contract requirements, including performing root cause analysis on specific problems and/or issues.

Deliverable:

A. QA/QC Plan B. Monthly Updates to QA/QC Plan

PRIVACY AND HIPAA TRAINING

The Contractor shall submit status of VA Privacy and Information Security Awareness training for all individuals engaged on the task. The status reporting shall identify; a single Contractor Security Point of Contract, the names of all personnel engaged on the task, their initial training date for VA Privacy and Information Security training, and their next required training date. This information shall be submitted as part of the Bi-Weekly Progress Status Report.

The Contractor shall submit Talent Management System (TMS) training certificates of completion for VA Privacy and Information Security Awareness training. The Contractor shall also provide VA Privacy and Information Security Awareness Signed Rules of Behavior, and VA Health Insurance Portability and Accountability Act (HIPAA) Certificate of Completion in accordance with Section 9, Training, from Appendix C of the VA Handbook 6500.6, “Contract Security”.

Deliverable:

A. TMS Training Certificates of Completion for VA Privacy and Information Security Awareness Training B. Privacy and Information Security Awareness Signed Rules of Behavior C. VA HIPAA Certificate of Completion

ACTIVITY BASED COSTING

The Contractor shall comply with Labor Tracking Time Entry (LTTE). LTTE supports activity-based costing processes among other uses. The quantities from LTTE contribute to activity cost visibility throughout the organization, incentivize cost reduction, increase precision of overhead allocation, and enable informed pricing decisions.

For LTTE purposes, Financial Services Center (FSC) users are required to input their work hours by activity and other categories into the FSC’s LTTE each Government Pay Period. Users have up to the Wednesday following the end of the Pay Period to enter their time in LTTE. Pay Periods close automatically midnight on Wednesday’s.

If work hours are not entered prior to the close of the Government’s Pay Period, LTTE will no longer allow the user to enter time. In this case, users must submit the hours to their Government PM/COR (and then must be provided to the Cost Accounting Section) or directly to the Cost Accounting Section for entry into LTTE. Courtesy email reminders are sent out reminding everyone to enter their work hours before the Government’s Pay Period closes. In addition, Compliance Enforcement reports are sent as a follow-up to the individuals who still need to enter their hours before the pay period closes. Non-compliance must be rectified.

SCALED AGILE FRAMWORK

The Contractor shall use the existing FSC Scaled Agile Framework and make recommendations for improvement/updates based on lessons learned to the Government for approval. The objective of the Scaled Agile Framework is to provide a governing set of Agile best practices critical to the successful implementation of iFAMS in alignment with the Department of Veterans Affairs Digital Transformation Strategy. These key practices have been defined, at a high level, to enable the FSC to satisfy GAO and OIG audit requirements.

iFAMS Agile teams are expected to adhere to FMBT Scaled Agile Framework practices and work with the Government Agile Council for advice, strategy, and feedback to improve agile practices and backlog management.

Contractor will also be responsible for:

a. Manage agile release trains following FMBT SAFe principles and practices

b. Utilize approved toolset and standards to manage business and technical requirements. .

c. Facilitate the prioritization of backlog items by designated product owners and plan work tasks in accordance with prioritization decisions. Prioritization of outstanding work shall be reviewed at least once a quarter to ensure alignment with current needs.

d. Refine items within backlog and update information within designated government tracking tool as details become known.

e. Report on emergent work that must be completed on an immediate basis due to operational impact including impact upon other tasks that were previously committed for completion.

f. Propose for government approval metrics for determining the health of the backlog that can be continuously monitored.

g. Coordinate with designated scheduling resources to track agile epics and features in the Integrated Project Schedule

h. Supporting and participating in A quarterly PI Planning, program retrospectives, lessons learned, and continuous process improvement efforts.

Deliverable:

A. Backlog B. Backlog Health Metrics and Data Integrity Checks

FINANCIAL MANAGEMENT QUALITY SERVICE MANAGEMENT OFFICE (FM QSMO) REPORT

The Contractor shall be responsible for meeting the Provider Service Measure requirements, as established by the Financial Management Capability Framework as part of the General Services Administration (GSA) Multiple Award Schedule (MAS) Special Item Number (SIN) 518210FM - Financial Management Quality Service Management Office (FM QSMO) Core Financial Management (FM) Solutions and Information Technology (IT) Professional Services as part of…