- Attached to
- R702--WORKFORCE ASSESSMENT (VA-27-00016203)
- Solicitation number
- 36C10B27Q0127
About this file
This is a Performance Work Statement (PWS) for the Department of Veterans Affairs Financial Services Center (FSC) Workforce Assessment Services under contract number VA-27-00016203, issued November 16, 2026.
The PWS outlines a 12-month base period with two optional 12-month extension periods (total contract duration not to exceed 36 months) requiring a comprehensive enterprise-wide and service-line level workforce assessment for VA's FSC, which currently operates with over 1,400 employees across 106 product and sub-product line services. The contractor must conduct data collection and validation, perform gap analysis comparing current workforce capabilities against future requirements, assess workforce planning maturity, conduct benchmarking against government and industry standards, and develop recommendations across staffing levels, workload volume, roles, skills, and competencies. Key deliverables include a Data Collection Report, Workforce Gap Analysis Report, Current Workforce Maturity Report, Current State SWOT Assessment Report, Industry Benchmark Analysis Report, Skill Gap Analysis Report, Succession Plan, Leadership Development Plan, Strategic Plan, Metric Tracking List, Implementation Plans and Roadmaps, Change Management Strategies and Communication Plan, and two workforce modeling tools (Future and Historical) built using existing customer technology such as Power BI with associated training videos and requirements documentation.
The contractor must comply with extensive federal and VA security, privacy, and technology requirements including VA Technical Reference Model, Zero Trust security controls, FICAM/PIV authentication standards, IPv6 support, TIC 3.0 compliance, Section 508 accessibility standards, and AI/LLM governance requirements including compliance with Unbiased AI Principles and Trustworthy AI Framework. Work shall be performed at contractor facilities with no travel anticipated. The contractor must maintain a current project management plan, provide weekly progress reports, and ensure all contractor personnel undergo appropriate background investigations commensurate with task risk designations. All deliverables must be provided in electronic format using Microsoft 365 suite, PDF, or other specified formats. Performance will be evaluated based on technical quality, project milestones and schedule adherence, cost and staffing appropriateness, and management effectiveness using a Quality Assurance Surveillance Plan.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 36C10B27Q0127.docx | DOCX document |
On GovTribe
Work with this file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Workforce Assessment
VA-27-00016203
PERFORMANCE WORK STATEMENT (PWS)
DEPARTMENT OF VETERANS AFFAIRS
Office of Information & Technology (OIT) Financial Services Center
Workforce Assessment Services
Date: November 16, 2026
VA-27-00016203
PWS Version Number: 1.0
Contents
| 1.0 | BACKGROUND | 5 |
| 2.0 | APPLICABLE DOCUMENTS | 5 |
| 3.0 | SCOPE OF WORK | 9 |
| 4.0 | PERFORMANCE DETAILS | 10 |
| 4.1 | PERFORMANCE PERIOD | 10 |
| 4.2 | PLACE OF PERFORMANCE | 10 |
| 4.3 | TRAVEL | 10 |
| 5.0 | SPECIFIC TASKS AND DELIVERABLES | 11 |
| 5.1 | PROJECT MANAGEMENT | 11 |
| 5.1.1 | TECHNICAL KICKOFF MEETING | 11 |
| 5.1.2 | CONTRACTOR PROJECT MANAGEMENT PLAN | 11 |
| 5.1.3 | REPORTING REQUIREMENTS | 12 |
| 5.2 | FSC ENTERPRISE-WIDE WORKFORCE ASSESSMENT | 12 |
| 5.2.1 | DATA COLLECTION AND VALIDATION | 12 |
| 5.2.2 | GAP ANALYSIS | 13 |
| 5.2.3 | WORKFORCE RECOMMENDATIONS, METRICS, AND KEY PERFORMANCE INDICATORS (KPI) | 15 |
| 5.2.4 | IMPLEMENTATION ROADMAP | 15 |
| 5.2.5 | FUTURE WORKFORCE MODELING TOOL | 16 |
| 5.2.6 | HISTORIAL WORKFORCE MODELING TOOL | 17 |
| OPTION PERIOD 1-2 | 18 | |
| 5.3 | EXECUTION OF IMPLEMENTATION ROADMAP (OPTIONAL TASK 1) | 18 |
| 6.0 | GENERAL REQUIREMENTS | 19 |
| 6.1 | ENTERPRISE AND IT FRAMEWORK | 19 |
| 6.1.1 | VA TECHNICAL REFERENCE MODEL | 19 |
| 6.1.2 | ZERO TRUST – VA CRITICAL SECURITY CONTROLS | 19 |
| 6.1.3 | FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT (FICAM) | 19 |
| 6.1.4 | INTERNET PROTOCOL VERSION 6 (IPv6) | 21 |
| 6.1.5 | TRUSTED INTERNET CONNECTION (TIC) | 22 |
| 6.1.6 | STANDARD COMPUTER CONFIGURATION | 22 |
| 6.1.7 | VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT LINE MANAGEMENT (PLM) | 22 |
| 6.1.8 | PROCESS ASSET LIBRARY (PAL) | 23 |
| 6.1.9 | AUTHORITATIVE DATA SOURCES | 23 |
| 6.1.10 | SOCIAL SECURITY NUMBER (SSN) REDUCTION | 24 |
| 6.1.11 | SOFTWARE AND LICENSING REQUIREMENTS | 25 |
| 6.1.12 | GENERATIVE ARTIFICIAL INTELLIGENCE REQUIREMENTS | 25 |
| 6.1.12.1 | AI SYSTEM/LLM DEVELOPMENT AND OPERATION DOCUMENTATION REQUIREMENTS | 27 |
| 6.1.12.2 | MONITORING, REPORTING, AND CORRECTIVE ACTION | 29 |
| 6.1.12.3 | AI MODEL UPDATES AND CHANGE DISCLOSURES | 29 |
| 6.1.13 | SOURCE CODE HARMONIZATION AND REUSE IN INFORMATION TECHNOLOGY (SHARE IT Act) | 30 |
| 6.2 | SECURITY AND PRIVACY REQUIREMENTS | 30 |
| 6.2.1 | POSITION/TASK RISK DESIGNATION LEVEL(S) | 30 |
| 6.2.2 | CONTRACTOR PERSONNEL SECURITY REQUIREMENTS | 31 |
| 6.3 | METHOD AND DISTRIBUTION OF DELIVERABLES | 33 |
| 6.4 | PERFORMANCE METRICS | 33 |
| 6.5 | FACILITY/RESOURCE PROVISIONS | 35 |
| 6.6 | GOVERNMENT FURNISHED PROPERTY | 36 |
| 6.7 | SHIPMENT OF HARDWARE OR EQUIPMENT | 37 |
| ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED | 41 | |
| ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM SECURITY/ PRIVACY LANGUAGE | 48 |
BACKGROUND
The Department of Veterans Affairs Financial Services Center (FSC) serves as VA’s centralized financial operations hub, delivering enterprise-wide financial management services that support the Department’s mission to provide care, benefits, and services to millions of Veterans. FSC executes high-volume, transaction-intensive operations across core financial functions, and plays a foundational role in maintaining financial integrity, supporting audit readiness, and enabling compliance with federal financial regulations.
As VA continues to advance enterprise modernization initiatives, FSC must adapt its workforce to support new technologies, evolving internal controls, automation initiatives, the Integrated Financial and Acquisition Management System (iFAMS), and increasing performance expectations. At the same time, FSC is facing increasing workforce pressures and increasing demand for data-driven performance transparency. Modernization initiatives, robotic process automation (RPA), an emerging AI workforce, and digital workflow tools present opportunities for productivity gains, but they also require new skills, updated role definitions, and deliberate workforce planning to avoid operational risk during transition periods.
The FSC currently has a workforce totaling over 1,400 employees across 106 product and sub-product line services. As FSC pursues operational excellence within a dynamic financial environment while balancing budget constraints, hiring timelines, and service level expectations, there is a clear need for a structured, data-driven workforce analysis to inform strategic workforce decisions, mitigate operational risk, and ensure sustained mission performance.
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 Vetting Program,” September 8, 2025, https://www.va.gov/vapubs/index.cfm
11. VA Handbook 0710, “Personnel Vetting Program,” September 8, 2025, 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”, VA Notice 25-16, dated September 15, 2025, “Amending VA Handbook 6500 to Replace Enterprise Mission Assurance Support Services Tool With Office of Information Technology Governance Risk Compliance Tool, and VA Notice 25-17, dated September 22, 2025, “Rescission Of Office Of Information Security (OIS) Deputy Assistant Secretary (DAS) Memorandum – Requirements of Proper Plan of Action and Milestones (POA&M) Completion)
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 (see VA NOTICE 25-10, dated June 9, 2025, “Use of Personally Owned Mobile Devices Policy Amendment of Department of Veterans Affairs Handbook 6500.10”, and VA Notice 25-15, dated August 22, 2025, “Update to VA Handbook 6500.10 Mobile Device Security Policy”)
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 Rev 4, 800-63A-4, 800-63B-4, 800-63C-4, “Digital Identity Guidelines,” August 1, 2025
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. Executive Order 14148, “Initial Rescissions of Harmful Executive Orders and Actions,” dated January 20, 2025
56. VA Directive 0057, “VA Environmental Management Program,” October 25, 2022
57. OIS VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28
58. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103
59. “Veteran Focused Integration Process (VIP) Guide 4.0,” March 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371
60. VA Memorandum “Proper Use of Email and Other Messaging Services,” January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28
61. “Product Line Management Transformation Playbook” version 3.1, August 2023, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946
62. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020
63. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),” November 19, 2020
64. Social Security Number (SSN) Fraud Prevention Act of 2017
65. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018
66. C.F.R Title 15 Part 7, “Securing the Information and Communications Technology and Services (ICTS) Supply Chain”, as amended
67. Executive Order 14028, “Executive Order on Improving the Nation's Cybersecurity,” May 12, 2021, https://bidenwhitehouse.archives.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/
68. 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.
69. NIST SP 800-52 Revision 2, “Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations
70. OMB M-26-05, “Adopting a Risk-based Approach to Software and Hardware Security,” January 23, 2026
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
78. E.O. 13960, “Promoting the Use of Trustworthy Artificial Intelligence in the Federal Government,” December 3, 2020
79. E.O. 14319, “Preventing Woke AI in the Federal Government,” July 23, 2025
80. OMB Memorandum M-25-21, “Accelerating Federal Use of AI through Innovation, Governance, and Public Trust,” April 3, 2025
81. OMB Memorandum M-25-22, “Driving Efficient Acquisition of Artificial Intelligence in Government,” April 3, 2025
82. OMB Memorandum M-26-04, “Increasing Public Trust in Artificial Intelligence (AI) Through Unbiased AI Principles,” December 11, 2025
83. P.L. 118-187, Source Code Harmonization and Reuse in Information Technology (SHARE IT) Act, December 23, 2024
SCOPE OF WORK
The Contractor shall provide Project Management support and conduct a comprehensive FSC Enterprise-wide and service-line level workforce assessment. The Contractor shall provide services to ensure VA FSC meet both current service demands and anticipated future workload shifts.
The Contractor shall also perform an optional task for execution of Implementation Plan and Roadmap to ensure successful project engagement and adoption of new strategies, processes, and/or technologies
PERFORMANCE DETAILS
PERFORMANCE PERIOD
The PoP shall be 12 months from date of award, with two 12-month option period(s). The overall Period of Performance shall not exceed 36 months
Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO).
There are 11 Federal holidays set by law (USC Title 5 Section 6103) that VA follows:
Under current definitions, five are set by date:
| New Year's Day | January 1 | |
| Juneteenth | June 19 | |
| Independence Day | July 4 | |
| Veterans Day | November 11 | |
| Christmas Day | December 25 |
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:
| Martin Luther King's Birthday | Third Monday in January |
| Washington's Birthday | Third Monday in February |
| Memorial Day | Last Monday in May |
| Labor Day | First Monday in September |
| Columbus Day | Second Monday in October |
| Thanksgiving | Fourth Thursday in November |
PLACE OF PERFORMANCE
Tasks under this PWS shall be performed at Contractor facilities. The Contractor shall identify the Contractor’s place of performance in their proposal submission.
TRAVEL
The Government does not anticipate travel under this effort to perform the tasks associated with the effort, as well as to attend program-related meetings or conferences throughout the PoP.
SPECIFIC TASKS AND DELIVERABLES
The Contractor shall perform the following:
PROJECT MANAGEMENT
0. TECHNICAL KICKOFF MEETING
A technical kickoff meeting shall be held within five days after contract award. The Contractor shall coordinate the date, time, and location (can be virtual) with the Contracting Officer (CO), as the Post-Award Conference Chairperson, the VA PM, as the Co-Chairperson, the Contract Specialist (CS), and the COR. The Contractor shall provide a draft agenda to the CO and VA PM at least three calendar days prior to the meeting. Upon Government approval of the final agenda, the Contractor shall distribute to all meeting attendees. During the kickoff-meeting, the Contractor shall present, for review and approval by the Government, the details of the intended approach, work plan, and project schedule for each effort via a Microsoft Office PowerPoint presentation. This meeting shall be recorded and transcribed to include notes on any major issues, agreements, or disagreements discussed during the kickoff meeting and any follow-up items to be addressed. The Contractor shall prepare and distribute the meeting minutes of the kickoff meeting to the CO, COR and all attendees within three calendar days after the meeting. The Contractor shall obtain concurrence from the CS on the content of the meeting minutes prior to distribution of the document.
CONTRACTOR PROJECT MANAGEMENT PLAN
Contractor shall deliver a Contractor Project Management Plan (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, milestones, risks, and resource support. The CPMP shall include Change Management & Communications Plan that outlining strategies for managing change and communications, including objective key stakeholder groups, channels, frequency and timing for communications. 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 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 Program Manager (PM) approved CPMP throughout the PoP.
Deliverable:
A. Contractor Project Management Plan
REPORTING REQUIREMENTS
The Contractor shall provide the COR with Weekly Progress Reports in electronic form in Microsoft Word. The report shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding week.
The Weekly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any risk and problems that arose and a description of how the problems were resolved, and risks shall be managed. If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The report shall also include an itemized list of all Information and Communication Technology (ICT) deliverables and their current Section 508 conformance status. The Contractor shall monitor performance against the CPMP and report any deviations. The report shall also identify any anticipated periods during which the Contractor staffs will be unavailable and provide the name and contact information of a designated alternate point of contact who will be available to address any questions or concerns the VA may have during the Contractor staff’s absence. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.
Deliverable:
A. Weekly Progress Report
FSC ENTERPRISE-WIDE WORKFORCE ASSESSMENT
The Contractor shall conduct an enterprise-wide and service line level workforce assessment to evaluate FCS current workforce capabilities, workforce planning maturity, and future needs.
The Contractor shall perform the following:
DATA COLLECTION AND VALIDATION
The Contractor shall assess FCS’s current workforce capabilities, by the gathering of relevant organizational documents, policies, previous assessments that will be vital to data collection. This could be with a variety of data collections, such as surveys, interviews or questionnaires.
The Contractor shall use existing organizational and workforce data and supplement available data through stakeholder engagement and other data collection methods to assess FSC’s current workforce capabilities.
The Contractor shall:
1. Collect and assess workforce and organizational data. Review available FSC workforce and organizational data to establish a current-state baseline. Supplement available data, as needed, through document reviews, surveys, and stakeholder interviews. The assessment shall include, as applicable, organizational structure, positions, staffing, workload, skills and competencies, performance, succession, attrition, retention, and organizational climate.
2. Assess current and future workforce requirements. Review FSC strategic plans, service scopes, organizational documentation, external trends, and applicable regulatory requirements. Based on this review, identify current and future workload and workforce requirements, including required roles, skills, competencies, and capabilities.
3. Assess workforce planning maturity. Evaluate FSC’s current workforce planning practices and processes to determine their level of maturity and effectiveness. Assess how workforce planning aligns with talent management activities, including recruitment, onboarding, employee development, retention, and succession planning.
4. Conduct enterprise-wide benchmarking. Compare FSC workforce practices and performance measures against relevant Government, industry, and leading practices. Assess how FSC compares areas related to workforce effectiveness and productivity.
5. The Contractor shall provide Data Collection Report that includes list of what data was collected, why it was collected, how it was collected, and what the results show. The report shall be organized so that readers can understand the data collection process, evaluate the quality of the data, and use the findings to make informed decisions.
6. The Contractor shall validate all information gathered against workforce management system data.
Deliverable:
A. Data Collection Report
GAP ANALYSIS
The Contractor shall use the information gather under Data Collection and Validation to develop an assessment of the current state FSC at an enterprise-wide and service level.
The Contractor shall perform the following:
1. Conduct workforce gap analysis by comparing current workforce data and capabilities against anticipated future-state workforce requirements to identify and quantify workforce staffing and performance gaps in the following areas:
a. Staffing levels and workforce capacity;
b. Workload volume and performance requirements;
c. Roles and position requirements;
d. Skills and competencies; and
e. Other critical workforce capabilities identified through the analysis.
2. Conduct Gap Analysis and documenting a Workforce Gap Analysis Report. The Workforce Gap Analysis Report shall reference:
a. Current and Future-state workforce staffing requirements
b. Define current and future-state staffing positions, competencies, and associated proficiency or skill levels necessary to meet anticipated business and workload requirements.
c. Current and future-state project and performance requirements
3. Conduct Current-state workforce maturity assessment enterprise-wide and service line level in the following areas:
a. Leadership engagement
b. Analytical capabilities
c. Data availability
d. Process formalization
e. Cross functional integrations
4. The Contractor shall provide a Current Workforce Maturity Report to identify the current maturity level including the following:
a. Planning capability
b. Identify lagging capability
c. Recommend capability needed for future strategy (e.g. how to get to the next or higher maturity levels)
d. Prioritize the recommendation of capabilities being addressed
5. Conduct Strengths, Weaknesses, Opportunities, and Threats (SWOT) analysis. Assess FSC’s workforce strengths, weaknesses, opportunities, and threats. Use findings from the data collection, workforce maturity assessment, supply and demand analysis, and benchmarking to identify workforce capability gaps. The Contractor shall deliver a Current State SWOT Assessment Report documenting the results of the enterprise-wide assessment. The Current State SWOT Assessment Report shall include current workforce capabilities and supply, current and future workforce demand and key demand drivers, workforce planning and talent management maturity, benchmarking and performance measure findings, enterprise-wide SWOT findings, and key workforce risks and capability gaps requiring further analysis.
6. The Contractor conduct analysis to compare FSC’s current workforce benchmark to the industry benchmark and develop an Industry Benchmark Analysis Report. The report shall provide a comprehensive comparison of FSC’s current performance per service line against relevant industry performance benchmarks, identify workforce gaps and opportunities for improvement, and provide actionable recommendations to support workforce planning and optimization.
7. The Contractor shall assess the current workforce skill and competencies and those required to meet mission requirements. The Contract shall develop a Skill Gap Analysis Report to identify critical skill gaps, assess their operational impacts, and recommend strategies to close those gaps through training, recruitment, workforce development, and resource realignment.
Deliverables:
A. Workforce Gap Analysis Report B. Current Workforce Maturity Report C. Current State SWOT Assessment Report D. Industry Benchmark Analysis Report E. Skill Gap Analysis Report
WORKFORCE RECOMMENDATIONS, METRICS, AND KEY PERFORMANCE INDICATORS (KPI)
The Contractor shall use the findings from Data Collection and Validation and Gap Analysis to prepare recommendations. The Contractor shall develop and deliver a Succession Plan that identifies organization operational key roles and information to ensure continuity if the position becomes vacated. The Contractor shall deliver a Leadership Development Plan that identifies competencies, career path, training and education required for the leadership role. The Contractor shall update current FSC Strategic Plan to reflect current strategic priorities which include recommendations for strategies recruitment, retention, upskilling, and training. Based on current workforce assessment, design metrics and KPIs for ongoing tracking using existing resources, the Contractor shall provide a Metric Tracking List that recommend and prioritize what metric should be tracked. The Contractor shall ensure that metrics and KPIs recommendations can be used for short-term and long-term assessments (e.g., turnover rates, time-to-fill, competency scores).
Deliverables:
A. Succession Plan.
B. Leadership Development Plan C. Strategic Plan D. Metric Tracking List
IMPLEMENTATION ROADMAP
The Contractor shall
1. Utilizing data from collected information to develop strategies on how to implement the identified recommendations using existing resources, tools, and constraints.
2. Develop Implementation Plans and Roadmaps including timeline, resources needed, and anticipated impact and results of implementing each recommendation. The roadmap shall ensure implementation is successful, minimizing operational interruptions.
3. Provide Change Management Strategies and Communication Plan to transition staff to the new recommendation. The plan shall outline how an organization will prepare, engage, support, and communicate with employees and stakeholders during significant organizational changes for each of the recommendations.
Deliverables:
A. Implementation Plans & Roadmaps B. Change Management Strategies and Communication Plan
FUTURE WORKFORCE MODELING TOOL
The Contractor shall develop a Future Workforce Modeling Tool to simulate various organizational changes and provide Scenario-based planning. The tool shall have capability to adjust parameters that include growth, contraction, mission shift, and benchmarking using organizational input and workforce data.
This tool shall be built using existing customer technology (e.g. Power BI), user friendly and will ultimately be maintained by the FSC.
The Contractor shall develop the Future Workforce Modeling Tool with the following:
1. Workforce planning processes and workflows;
2. Data collection instruments to address identified data gaps;
3. Scenario-based workforce planning;
4. Workforce planning templates support consistent workforce analysis and planning.
5. Criteria and methods for identifying critical roles recommendations, risks, and strengths
6. Present point in time status of workforce health. The tool shall utilize source data, generate recommendations, highlight risks, and validate strengths based on adjustable management operational thresholds.
7. Capability to display status indicators (e.g. red, amber, green)
The Contractor provides a recorded virtual Future Workforce Modeling Tool Training Video that demonstrates the feature of the tool and how end users utilize the Future Workforce Modeling Tool.
The Contractor shall provide a Future Workforce Modeling Tool Requirements and Design Document that defines how the Future Workforce Modeling Tool is developed, how users will interact with the tool and its functionalities.
Deliverables:
A. Future Workforce Modeling Tool B. Future Workforce Modeling Tool Training Video C. Future Workforce Modeling Tool Requirements and Design Document
HISTORIAL WORKFORCE MODELING TOOL
The Contractor shall develop a Historical Workforce Modeling Tool containing historical data, trends and anticipatory gap maps.
The Contractor shall develop the Historical Workforce Modeling Tool with the following:
1. User-friendly with customizable views that contain data visualization (historical data, trends, and anticipatory gap maps) with secure integration with existing HR systems. Utilize reporting and visualization platform (e.g. Power BI)
2. Shall have filtering, reporting and workforce analytics capabilities to support ongoing reporting, analysis, and decision-making.
3. Workforce performance measure reporting;
4. Workforce supply and demand analysis;
5. Workforce gap and risk monitoring;
6. Workforce trends and performance analysis Hiring data, staffing data, retirements and departure data, time and leave data
The Contractor provides a recorded virtual Historical Workforce Modeling Tool Training Video that demonstrates the feature of the tool and how end users utilize the Future Workforce Modeling Tool.
The Contractor shall provide a Historical Workforce Modeling Tool Requirements and Design Document that defines how the Historical Workforce Modeling Tool is developed, how users will interact with the tool and its functionalities.
Deliverables:
A. Historical Workforce Modeling Tool B. Historical Workforce Modeling Tool Training Video C. Historical Workforce Modeling Tool Requirements and Design Document
OPTION PERIOD 1-2
The Contractor shall continue to perform tasks and provide deliverables indicated in section 5.1 and 5.2.
EXECUTION OF IMPLEMENTATION ROADMAP (OPTIONAL TASK 1)
The Contractor shall execute VA approved Implementation Plans & Roadmaps. The Contractor shall perform the following:
1. Prioritize the Implementation Plans & Roadmaps order as designated by VA leadership’s direction.
2. Implementation the Change Management strategies and Communications Plan
3. Facilitate ongoing FSC stakeholder engagement and monitor change management
4. Measure effectiveness of implementation and provide update to the Implementation Plans & Roadmap,
a. Provide quantifiable actual results of what was implemented.
5. Develop and maintain Standard Operating Procedures that include Job Aids, Desk Guides to align with current operation after implementation
a. The Standard Operating Procedures shall be reviewed by FSC Risk and Audit services to ensure audit readiness and address and incorporate feedback from review
6. Review and adjust the Future Workforce Modeling Tool after implementing roadmap to ensure tool remains current.
This Optional Task may be exercised at the Government’s discretion at any time during base and option periods. This optional task shall have PoP of six months, can be exercised four times.
Deliverable:
A. Standard Operating Procedures
GENERAL REQUIREMENTS
ENTERPRISE AND IT FRAMEWORK
VA TECHNICAL REFERENCE MODEL
The Contractor shall comply with the VA OIT Technical Reference Model (VA TRM). Compliance with the VA TRM is achieved by using only technologies and standards that are listed as approved for use in the VA TRM. The Contractor shall provide all necessary information requested by VA to ensure TRM approval is obtained prior to use on VA’s network.
ZERO TRUST – VA CRITICAL SECURITY CONTROLS
VA has established minimum mandatory security requirements and requires that any network connected software system or service must meet the VA Critical Security Controls as outlined in the VA Memorandum, “VA Security Controls”, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010. VA Critical Security Controls identify the minimum mandatory requirements that must be implemented across all VA enterprise infrastructure, cloud computing environments, information systems, networks, and specialized devices (medical devices/systems, special-purpose systems, and research scientific computing devices) that process, store, and/or transmit VA data. Effective July 1, 2025, the Contractor shall implement these VA Critical Security Controls, within any network connected software system or service prior to being authorized for use in the VA. This functional requirement is not negotiable, and Plan of Action & Milestones (POAM) will not be accepted in the event these controls cannot be implemented for new systems. Critical Security Controls are intended to increase VA’s security posture and provide security and privacy risk visibility into the VA network and is not a new requirement. The Contractor’s failure to maintain these VA Critical Controls after implementation will result in VA discontinuing the use of the system.
FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT (FICAM)
The Contractor shall ensure Commercial Off-The-Shelf (COTS) product(s), software configuration and customization, and/or new software are Personal Identity Verification (PIV) card-enabled by accepting HSPD-12 PIV credentials using VA Enterprise Architecture (EA), and VA Identity and Access Management (IAM) approved Enterprise Technology Guidelines (ETG). The Contractor shall ensure all Contractor delivered applications and systems comply with the VA Identity, Credential, and Access Management policies and guidelines set forth in Executive Order 14028, VA Handbook 6510 VA Identity and Access Management, VA Handbook 0735 Homeland Security Presidential Directive 12 (HSPD-12) Program, CISA Binding Operational Directive 23-01, and align with the Federal Identity, Credential, and Access Management Roadmap and Implementation Guidance v2.0.
The Contractor shall ensure all Contractor delivered applications and systems provide user authentication services compliant with the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-63-4, VA Handbook 6500, and VA IAM enterprise requirements for direct, assertion based authentication, and/or trust based authentication, as determined by the ETGs. Direct authentication at a minimum must include Public Key Infrastructure (PKI) based authentication supportive of PIV card and/or Common Access Card (CAC), as determined by the business need.
The Contractor shall ensure all Contractor delivered applications and systems conform to the specific Identity and Access Management PIV requirements set forth in the Office of Management and Budget (OMB) Memoranda M-05-24, M-19-17, M-22-09, and NIST Federal Information Processing Standard (FIPS) 201-3. Contractor delivered applications and systems shall be on the FIPS 201 Approved Product List (APL). If the Contractor delivered application and system is not on the APL, the Contractor shall be responsible for taking the application and system through the FIPS 201 Evaluation Program.
The Contractor shall ensure all Contractor delivered applications and systems support:
1. Automated provisioning and are able to use enterprise provisioning service.
2. Interfacing with VA’s Master Person Index (MPI) to provision identity attributes, if the solution relies on VA user identities. MPI is the authoritative source for VA user identity data.
3. The VA defined unique identity (Secure Identifier [SEC ID] / Integrated Control Number [ICN]).
4. Multiple authenticators for a given identity and authenticators at every Authenticator Assurance Level (AAL) appropriate for the solution.
5. Identity proofing for each Identity Assurance Level (IAL) appropriate for the solution.
6. Federation for each Federation Assurance Level (FAL) appropriate for the solution, if applicable.
7. Two-factor authentication (2FA) through an applicable Technology Guideline as outlined in VA ETG.
8. A Security Assertion Markup Language (SAML) implementation if the solution relies on assertion-based authentication. Additional assertion implementations, besides the required SAML assertion, may be provided as long as they are compliant with NIST SP 800-63-4 guidelines.
9. Authentication/account binding based on trusted Hypertext Transfer Protocol (HTTP) headers if the solution relies on Trust based authentication.
10. Role Based Access Control.
11. Auditing and reporting capabilities.
12. Compliance with VIEWS 00155984, PIV Logical Access Policy Clarification https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896.
The required Assurance Levels for this specific effort are Identity Assurance Level 3, Authenticator Assurance Level 3, and Federation Assurance Level 3.
INTERNET PROTOCOL VERSION 6 (IPv6)
The Contractor solution shall support IPv6-Only based upon the memo issued by the Office of Management and Budget (OMB) on November 19, 2020 (https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). Which defines IPv6-only as the state of an operational system or service when IPv4 protocol functions (addressing, packet forwarding) are not in use. The NIST USGv6 profile defines technical requirements for a product to be capable of operating in IPv6-Only environments. IPv6-Only technology, in accordance with the USGv6 Program (https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1), NIST Special Publication (SP) 500-267B Revision 1 “USGv6 Profile” (https://doi.org/10.6028/NIST.SP.500-267Br1), and NIST SP 800-119 “Guidelines for the Secure Deployment of IPv6” (https://doi.org/10.6028/NIST.SP.800-119), compliance shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices, applications, and systems shall support all applicable functionality on native IPv6-Only as well as dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g., web, email, DNS, ISP services, etc.) shall support native IPv6-Only and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall support using native IPv6-Only and dual stack (IPv6 / IPv4) for all functionality and operations.
TRUSTED INTERNET CONNECTION (TIC)
The Contractor solution shall meet the requirements outlined in Office of Management and Budget Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative“ (https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf), VA Directive 6513 “Secure External Connections”, and shall comply with the TIC 3.0 Core Guidance Documents, including all Volumes and TIC Use Cases, found at the Cybersecurity & Infrastructure Security Agency (CISA) (https://www.cisa.gov/publication/tic-30-core-guidance-documents).
STANDARD COMPUTER CONFIGURATION
The Contractor IT end user solution that is developed for use on standard VA computers shall be compatible with and be supported on the standard VA operating system, Windows 11, Edge (Chromium based), and 365 Apps for enterprise. Applications delivered to VA and intended to be deployed to Windows 11 workstations shall be delivered as a signed .msi package with switches for silent and unattended installation and updates shall be delivered in signed .msp file formats for easy deployment using Microsoft Endpoint Configuration Manager (CM) VA’s current desktop application deployment tool. Signing of the software code shall be through a vendor provided certificate that is trusted by VA using a code signing authority such as Verizon/Cybertrust or Symantec/VeriSign. The Contractor shall also ensure and certify that their solution functions as expected when used from a standard VA computer, with non-admin, standard user rights that have been configured using the Defense Information Systems Agency (DISA) Secure Technical Implementation Guide (STIG) specific to the particular client operating system being used.
VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT LINE MANAGEMENT (PLM)
The Contractor shall support VA efforts IAW the Veteran-Focused Integration Process (VIP) Guide and Product Line Management (PLM) Playbook. The major focus of VIP is on Enterprise Oversight, Governance, reporting, and establishing practices that focus on outcomes and continuously delivering sustainable IT capabilities to benefit the Veteran. PLM is a framework that focuses on delivering functional products that provide the highest priority work to customers while delivering simplified, reliable, and practical solutions to the business, medical staff, and our Veterans. The VIP Guide is a companion guide to the PLM Transformation Playbook and can be found at: https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 and the PLM Transformation Playbook can be found at https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946. VIP and PLM are the authoritative processes that IT projects must follow to ensure development and delivery of IT products.
The VIP Guide provides guidance for transitioning from project-centric to product-centric delivery. The VIP guide applies to all OIT Office of Management and Budget (OMB) reportable products that are required to collect and report costs, schedules, risks, and other valuable information in VA PARS (whether products are procured or developed by VA) and any VA Information Technology project effort in Software Product Management (SPM) and Infrastructure Operations (IO), or their successors, that touch the VA network regardless of IT organizational alignment (whether it spends government funding from VA's Congressional IT Appropriation or any other appropriation).
The PLM Transformation Playbook details how OIT leadership expects Product Lines (PLs) to implement PLM, DevOps, and Lean-Agile principles, methods, practices, and techniques through levels of maturity. The PLM Transformation Playbook applies to all Information Technology (IT) products aligned to PLs in the Software Product Management, Infrastructure Operations and Product Engineering organizations within the OIT organization.
Others outside the referenced groups or organizations may use the VIP Guide and PLM Transformation Playbook for situational awareness as needed.
PROCESS ASSET LIBRARY (PAL)
The Contractor shall perform their duties consistent with the processes defined in the OIT Process Asset Library (PAL). The PAL includes a spectrum of OIT functions and activities, such as project management, operations, service delivery, communications, acquisition, and resource management. PAL serves as an authoritative and informative repository of searchable processes, activities or tasks, roles, artifacts, tools and applicable standards and guides to assist the OIT workforce, Government and Contractor personnel. OIT utilizes PAL processes to ensure compliance with policies and regulations and to meet VA quality standards. The PAL includes the contractor onboarding process consistent with Section 6.2.2 and can be found at process_CONB_ext.docx (live.com). The main PAL can be accessed at www.va.gov/process.
AUTHORITATIVE DATA SOURCES
The VA Enterprise Architecture Repository (VEAR) is one component within the overall EA that establishes the common framework for data taxonomy for describing the data architecture used to develop, operate, and maintain enterprise applications. The Contractor shall comply with the department’s Authoritative Data Source (ADS) requirement that VA systems, services, and processes throughout the enterprise shall access VA data solely through official VA ADSs where applicable, see below. The Information Classes which compose each ADS are located in the VEAR, in the Data & Information domain. The Contractor shall ensure that all delivered applications and system solutions support:
1. Interfacing with VA’s Master Person Index (MPI) (formerly the Master Veteran Index (MVI)) to provision identity attributes, if the solution relies on VA user identities. MPI is the authoritative source for VA user identity data.
2. Interfacing with Capital Asset Inventory (CAI) to conduct real property record management actions, if the solution relies on real property records data. CAI is the authoritative source for VA real property record management data.
3. Interfacing with electronic Contract Management System (eCMS) for access to contract, contract line item, purchase requisition, offering vendor, and solicitation information above the micro-purchase threshold, if the solution relies on procurement data. ECMS is the authoritative source for VA procurement actions data.
4. Interfacing with HRSmart Human Resources Information System to conduct personnel action processing, on-boarding, benefits management, and compensation management, if the solution relies on personnel data. HRSmart is the authoritative source for VA personnel information data.
5. Interfacing with VA Profile to access personal contact information, if the solution relies on VA Veteran personal contact information data. VA Profile is the authoritative source for VA Veteran Personal Contact Data.
6. Interfacing with VA/Department of Defense (DoD) Identity Repository (VADIR) for determining eligibility for VA benefits under Title 38, if the solution relies on qualifying active duty military service data. VADIR is the authoritative source for qualifying active duty military service in VA.
7. Interfacing with VA Systems Inventory (VASI) to access VA systems information, if the solution relies on VA system information. VASI is the authoritative source for VA Information Technology systems.
8. Interfacing with Enterprise Mission Assurance Support Service (eMASS) to access the historical Authority to Operate (ATO) status of all VA Information Systems prior to migrating to ServiceNow Continuous Authorization and Monitoring (SNowCAM) until it is determined the migration is completed and eMASS is sunset. eMASS contains the historical Authority to Operate (ATO) status of all VA Information Systems prior to September 30, 2025, with all status provided through SNowCAM once migration is completed.
SOCIAL SECURITY NUMBER (SSN) REDUCTION
The Contractor solution shall support the Social Security Number (SSN) Fraud Prevention Act (FPA) of 2017 which prohibits the inclusion of SSNs on any document sent by mail. The Contractor support shall also be performed in accordance with Section 240 of the Consolidated Appropriations Act (CAA) 2018, enacted March 23, 2018, which mandates VA to discontinue using SSNs to identify individuals in all VA information systems as the Primary Identifier. The Contractor shall ensure that any new IT solution discontinues the use of SSN as the Primary Identifier to replace the SSN with the ICN in all VA information systems for all individuals. The Contractor shall ensure that all Contractor delivered applications and systems integrate with the VA MPI for identity traits to include the use of the ICN as the Primary Identifier. The Contractor solution may only use a Social Security Number to identify an individual in an information system if and only if the use of such number is required to obtain information VA requires from an information system that is not under the jurisdiction of VA.
SOFTWARE AND LICENSING REQUIREMENTS
The…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .