Draft PWS - Corporate Intake and Solutioning Support.pdf

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology (OIT) Software Product Management (SPM)

Corporate (CORP) Service Line

Corporate Intake and Solutioning Support

Date: April 30, 2024

VA-24-00072386

PWS Version Number: 1.0 https://btt.dva.va.gov/ppsServlet/spring/listing/processListing?templateId=50&filter_planningUID=VA-24-00072386&noCache=noCache

CORP Intake and Solutioning Support

Contents

1.0 BACKGROUND

2.0 APPLICABLE DOCUMENTS

3.0 SCOPE OF WORK

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

4.2 PLACE OF PERFORMANCE

4.3 TRAVEL

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

5.1.2 REPORTING REQUIREMENTS

5.1.3 TECHNICAL KICKOFF MEETING

5.1.4 REQUIRED TRAINING ................................ Error! Bookmark not defined.

5.1.5 ADMINISTRATIVE SUPPORT

5.1.6 PROCESS IMPROVEMENT

5.2 INTAKE PROCESS MANAGEMENT

5.3 REQUIREMENTS DEVELOPMENT

5.4 ANALYSIS SUPPORT

5.5 INFORMATION EXCHANGE SUPPORT

5.6 COST ESTIMATION (CE) SUPPORT

5.7 REQUIREMENTS DEVELOPMENT SUPPORT PACKAGES (OPTIONAL

TASK 1)

5.8 TA PACKAGES (OPTIONAL TASK 2)

5.9 DSD PACKAGES (OPTIONAL TASK 3)

5.10 AoA PACKAGES (OPTIONAL TASK 4)

5.11 PHASE-OUT TRANSITION PLAN (OPTIONAL TASK 5)

6.0 GENERAL REQUIREMENTS

6.1 ENTERPRISE AND IT FRAMEWORK

6.1.1 VA TECHNICAL REFERENCE MODEL

6.1.2 FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT

(FICAM)

6.1.3 INTERNET PROTOCOL VERSION 6 (IPV6)

6.1.4 TRUSTED INTERNET CONNECTION (TIC)

6.1.5 STANDARD COMPUTER CONFIGURATION

6.1.6 VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT

LINE MANAGEMENT (PLM)

6.1.7 PROCESS ASSET LIBRARY (PAL)

6.1.8 AUTHORITATIVE DATA SOURCES

6.1.9 SOCIAL SECURITY NUMBER (SSN) REDUCTION

6.2 SECURITY AND PRIVACY REQUIREMENTS

6.2.1 POSITION/TASK RISK DESIGNATION LEVEL(S)

6.2.2 CONTRACTOR PERSONNEL SECURITY REQUIREMENTS

6.3 METHOD AND DISTRIBUTION OF DELIVERABLES

6.4 PERFORMANCE METRICS

6.5 FACILITY/RESOURCE PROVISIONS

6.6 GOVERNMENT FURNISHED PROPERTY

6.7 SHIPMENT OF HARDWARE OR EQUIPMENT

ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED

ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM

SECURITY/PRIVACY LANGUAGE

1.0 BACKGROUND

The Department of Veterans Affairs (VA), Office of Information & Technology (OIT), Software Product Management (SPM) strives to provide high quality, effective, and efficient Information Technology (IT) services to those responsible for providing care to the Veterans at the point-of-care as well as throughout all the points of the Veterans’ health care in an effective, timely and compassionate manner. VA depends on Information Management/Information Technology (IM/IT) systems to meet mission goals.

The VA OIT SPM, Corporate (CORP) Service Line (SL) delivers world-class, Veteran-centric capabilities that provide secure, seamless delivery of IT systems to VA corporate offices so these offices may efficiently and effectively provide benefits and services to Veterans and their families. CORP manages a variety of products, programs, and projects that require oversight in the key areas of IT development, operations, and sustainment. CORP includes the following four Product Lines (PLs):

1. Acquisition and Property Management - IT products for conducting acquisition and performance management activities, including acquisition planning, sourcing, contracting, purchasing, equipment and inventory management and facility operations.

2. Financial Management - IT products for conducting financial management activities including budget formulation and execution, account management, payment processing and financial performance reporting.

3. Human Capital Management - IT products for conducting human capital management, including talent acquisition and development, employee performance and compensation management and employee separation and retirement management.

4. Sec VA/Congressional/Legal Affairs - IT products for supporting the activities of Office of the Secretary of VA, Office of General Counsel and Congressional Liaison operations. It also includes products for enabling regulatory activities such as matter intake and tracking under the VA accountability and whistleblower's protection program.

CORP is currently responsible for approximately 170 products assigned within four PLs.

These products are routinely re-assigned within OIT, and so the number of products and their assigned PL are subject to change, both internally and to other SLs within OIT.

The number of PLs within the SL is also subject to change as it is anticipated that new PLs will be added to CORP throughout the life of this Task Order (TO).

The core mission of the Corporate Intake and Solutioning (CIS) Division is to manage and analyze IT capability requests through the Intake Process, focusing on enterprise alignment with VA solution standards and strategic priorities, cost estimation (CE), and planning requirements, in preparation for project initiation.

2.0 APPLICABLE DOCUMENTS

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

1. 44 U.S.C. § 3541-3549, “Federal Information Security Management Act (FISMA) of 2002”

2. “Federal Information Security Modernization Act of 2014”

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

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

5. FIPS Pub 200, “Minimum Security Requirements for Federal Information and

Information Systems,” March 2006

6. FIPS Pub 201-2, “Personal Identity Verification of Federal Employees and

Contractors,” August 2013

7. 10 U.S.C. § 2224, "Defense Information Assurance Program"

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

9. Public Law 109-461, Veterans Benefits, Health Care, and Information

Technology Act of 2006, Title IX, Information Security Matters

10. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”

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

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

13. VA Directive and Handbook 6102, “Internet/Intranet Services,” August 5,

14. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” January 18, 2017

15. Office of Management and Budget (OMB) Circular A-130, “Managing Federal

Information as a Strategic Resource,” July 28, 2016

16. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed

Services (CHAMPUS)”

17. NIST SP 800-66 Rev. 1, “An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule,” October 2008

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

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

20. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021

21. VA Handbook 6500, “Risk Management Framework for VA Information

Systems VA Information Security Program,” February 24, 2021

22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive

Personal Information (SPI),” March 12, 2019

23. VA Handbook 6500.5, “Incorporating Security and Privacy into the System

Development Lifecycle,” March 22, 2010

24. VA Handbook 6500.6, “Contract Security,” March 12, 2010 https://www.va.gov/vapubs/index.cfm https://www.va.gov/vapubs/index.cfm http://www.va.gov/vapubs http://www.va.gov/vapubs

25. VA Handbook 6500.8, “Information System Contingency Planning,” April 6,

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

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

28. OIT Process Asset Library (PAL), https://www.va.gov/process/ . Reference

Process Maps at https://www.va.gov/process/maps.asp and Artifact templates at https://www.va.gov/process/artifacts.asp

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

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

31. VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy Impact Assessment,” July 30, 2015

32. VA Handbook 6510, “VA Identity and Access Management,” January 15,

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

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

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

36. 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

37. 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)

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

39. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-

12) Program,” March 24, 2014

40. 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

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

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

43. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011, (NOTE: Part A of the FICAM Roadmap and Implementation Guidance, v2.0, was replaced in 2015 with an updated Architecture (https://arch.idmanagement.gov/#what-is-the-ficam-architecture)

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

45. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, “Digital Identity Guidelines,” updated March 02, 2020 https://www.va.gov/process/ https://www.va.gov/process/maps.asp https://www.va.gov/process/artifacts.asp https://www.va.gov/trm/TRMHomePage.aspx https://arch.idmanagement.gov/#what-is-the-ficam-architecture https://arch.idmanagement.gov/#what-is-the-ficam-architecture

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

47. NIST SP 800-164, “Guidelines on Hardware-Rooted Security in Mobile

Devices (Draft),” October 2012

48. Draft National Institute of Standards and Technology Interagency Report

(NISTIR) 7981, “Mobile, PIV, and Authentication,” March 2014

49. 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)

50. 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)

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

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

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

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

55. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public Law 110–140), December 19, 2007

56. Section 104 of the Energy Policy Act of 2005, (Public Law 109–58), August 8, 2005

57. Executive Order 13834, “Efficient Federal Operations,” dated May 17, 2018

58. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August

2, 2001

59. VA Directive 0058, “VA Green Purchasing Program,” July 19, 2013

60. VA Handbook 0058, “VA Green Purchasing Program,” July 19, 2013

61. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote

Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

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

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

64. VA Memorandum “Proper Use of Email and Other Messaging Services,”

January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

65. “DevSecOps Product Line Management Playbook” version 2.0, May 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

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

67. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol

Version 6 (IPv6),” November 19, 2020

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

69. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896 https://www.cisa.gov/publication/tic-30-core-guidance-documents https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

70. Attachment 1 – SPM CIS Process

71. Attachment 2 – Analysis of Alternatives (AoA) Template

72. Attachment 3 – Technical Assessment (TA) Template

73. Attachment 4 – Detailed Solutioning Document (DSD) Template

74. Attachment 5 – Integrated Meeting Minutes (IMM) Template

75. Attachment 6 – Rough Order of Magnitude (ROM) Template

76. Attachment 7 – Cost Estimate (CE) Worksheet Template

77. Attachment 8 - Product Line Acceptance (PLA) Template

3.0 SCOPE OF WORK

The Contractor shall provide technical support for the SPM Corporate Portfolio Office’s CIS Division. Major work areas include process management, requirements management, IT capability request management and analysis, solutioning recommendations, administrative support, architecture support, integration analysis, and cost estimation support.

The support and deliverables provided under this PWS are primarily strategic pre-project level analysis and will lead directly to a work statement for the acquisition of a future system or services. Moreover, the support and deliverables provided under this PWS are not at the project level, but through Discovery and Analysis provide project managers enough detail to effectively initiate the request as a project. More granular, project-level support is provided by the product lines themselves. Project or acquisition-level support is outside the scope of this PWS.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The Period of Performance (PoP) shall be 12 months from date of award with three 12-month Option Periods, which may be exercised at the discretion of the Government. All tasks are applicable for the Base Period, as well as each Option Period, if exercised.

There are five Optional Tasks (OT) that may be exercised in the Base and Option Periods.

There are eleven (11) Federal holidays set by law (USC Title 5 Section 6103) that VA follows. Under current definitions, four 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

4.2 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.

4.3 TRAVEL

The Government anticipates 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. Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government.

The total estimated number of trips in support of the program related meetings for this effort is one (1) trip in per year for four travelers per trip. Anticipated locations include the following, estimated at four (4) days in duration:

1. Washington, D.C.

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

The 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 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 PM approved CPMP throughout the PoP.

Deliverable:

A. Contractor Project Management Plan (CPMP)

5.1.2 REPORTING REQUIREMENTS

The Contractor shall provide the COR with Monthly Progress Reports in electronic form in Microsoft Word and Project formats. 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 Month.

The Monthly 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 problems that arose and a description of how the problems were resolved. 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. 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. Monthly Progress Report

5.1.3 TECHNICAL KICKOFF MEETING

A technical kickoff meeting shall be held within 10 business days after TO 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 Program Manager, as the Co-Chairperson, the Contract Specialist (CS), and the COR. The Contractor shall provide a draft agenda to the CO and VA Program Manager at least five calendar days prior to the meeting. Upon Government approval of a 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 product schedule for each effort via a PowerPoint presentation. At the conclusion of the meeting, the Contractor shall update the presentation with a final slide entitled “Summary Report” which shall include notes on any major issues, agreements, or disagreements discussed during the kickoff meeting and the following statement, “As the Post-Award Conference Chairperson, I have reviewed the entirety of this presentation and assert that it is an accurate representation and summary of the discussions held during the Technical Kickoff Meeting for the “CORP Intake and Solutioning Support.” The Contractor shall submit the final updated presentation to the CO for review and signature within three calendar days after the meeting. The Contractor shall also work with the CS, the Government’s designated note taker, to prepare and distribute the meeting minutes of the kickoff meeting to the CO, COR, and all attendees within 3 business 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.

5.1.4 ADMINISTRATIVE SUPPORT

The Contractor shall provide administrative support to include:

1. Scheduling CIS related meetings with internal and external stakeholders.

2. Providing ad-hoc responses, presentation, and reporting materials.

3. Generating and tracking action items.

4. Managing dashboards and repositories, including documents and artifacts following proper naming conventions.

5. Providing CIS operations tasks such as routing Demand (DMND) requests and managing the Demand Tracking Tool.

6. Creating Integrated Meeting Minutes (IMM) (See Attachment 5 template) for each

DMND within the Demand Tracking Tool. IMMs include historical minutes for all meetings related to the DMND and are to be uploaded into Demand Tracking Tool. The estimated quantity of DMND requests per PoP is 93.

Deliverable:

A. Integrated Meeting Minutes (IMM)

5.1.5 PROCESS IMPROVEMENT

The Contractor shall support continuous CIS process improvement and innovation throughout the lifecycle of this TO and update the Intake Work Product Templates accordingly. The Contractor shall research and implement automated and intelligent workflows using advanced technologies to streamline routine tasks, diminish reliance on manual labor, mitigate errors, and accelerate project completion timelines.

A. Intake Work Product Templates

5.2 INTAKE PROCESS MANAGEMENT

The Contractor shall provide the following support:

1. Updating the Intake Process Models (see Attachment 1 template) to include only the new CIS phases of the Intake Process. Coordinate with the Process Asset Library (PAL) team to update changes made to CIS processes in the PAL system.

2. Creating and updating Intake Process Guides and Intake Job Aids.

3. Performing analysis of existing processes to identify gaps in the process and sub-process steps and document with an Intake Process Gap Analysis. Gap analysis will be under the direction of Government staff to validate that processes are documented accurately.

Deliverables:

A. Intake Process Models B. Intake Process Guides

C. Intake Job Aides D. Intake Process Gap Analysis

5.3 REQUIREMENTS DEVELOPMENT

The Contractor shall work with business customers to develop functional and non-functional IT requirements and use cases. The level of detail shall vary depending on the type of implementation of the DMND. At minimum, high-level capabilities and a clear scope of the request shall be required for each DMND. This is a new role being established within CIS and will require the development of templates and processes.

The Contractor shall provide the following support:

1. Maintaining best practices of business analysis as set forth by the International Institute of Business Analysis TM (IIBA) - https://www.iiba.org

2. Assisting the Business Customer to identify and understand business needs, gaps (IT and non-IT) to enhance the business process, accomplish business goals, and prepare needs for initial analysis.

3. Defining and validating work effort scope, structure, and schedule, while identifying and coordinating stakeholders, reviewing existing documentation and facilitation of work effort kick-off meeting with stakeholders.

4. Facilitating stakeholder meetings to elicit, document and validate business requirements for each work effort approved for Requirements Analysis.

5. Maintaining documents as part of the DMND Tracker Tool to capture all information obtained through stakeholder engagement, as well as IMMs.

6. The elicitation process includes identification of detailed business needs, business requirements written in user story format, acceptance criteria, business rules, and non-functional requirements. Additionally, work efforts may include business architectural process models in Business Process Model Notation (BPMN) for ‘As-Is’ and ‘To-Be’ processes models for related requirements.

7. As requirements are identified, the Contractor shall generate a Requirements Analysis Support Package, refine requirements, and obtain stakeholder concurrence. The estimated quantity of Requirements Analysis Support Packages per PoP is 60.

Deliverable:

A. Requirements Analysis Support Packages

5.4 ANALYSIS SUPPORT

The Contractor shall provide the following support:

1. Identifying and understanding technical needs, Key Performance Indicators (KPIs), risks, key dependencies, Service Level Agreements (SLAs), Operation Level Agreements (OLAs), identifying opportunities to leverage Enterprise Shared Services (ESS’), and reusing/leveraging existing capabilities.

https://www.iiba.org/

2. Analyzing DMND requests and recommending what work product and/or service will provide the most value to business stakeholders and inform VA decision-making.

3. Facilitating and conducting Play Decision meetings with business stakeholders and the CORP Integrated Intake Team (CIIT) to determine one or more of the VA defined Play Decisions.

4. Creating Technical Assessments (TAs) (see Attachment 3 template) to provide a high-level overview of the DMND request and the recommended Play Decision for the CIIT. The TA includes an executive summary, scope, PL alignment, current and future architecture, play decision, known risks and dependencies, points of contact (POCs), and an initial rough order of magnitude (ROM) (see Attachment 6 template). Most but not all DMND’s require a TA. The estimated quantity of TAs per PoP is 60.

5. Producing Detailed Solutioning Documents (DSDs) (see Attachment 4 template) to provide a detailed analysis overview of DMND request and CORP SL’s assessment of OIT’s next step in future system planning. The estimated quantity of DSDs per PoP is 15.

An emphasis is placed on the system architecture as identified below:

• Alignment to OneVA Enterprise Architecture (EA) and SL/segment level architecture, enterprise shared services architecture, and business requirements.

• Use of best practices to facilitate seamless integration with other products and systems.

• Compliance of a selected solution and aligning the architecture, solution, or product against the EA perspective.

• Configuration management of review artifacts and publishing them to a VA designated repository.

• VA’s current and potential future IT environments and maximization of implementing standard solution designs.

6. Developing Analysis of Alternatives (AoAs) (templates Attachment 2 template) for comparison between multiple solutions to satisfy business requirements. The Contractor shall perform the analysis, develop recommendations, and prepare and present those recommendations and justifications to VA. The estimated quantity of AoAs per PoP is 18.

NOTE: There are situations where market research is done as a high-level desktop review of solution alternatives with possible product demonstrations.

These reviews do not require scoring and are not considered AoA products and shall be included within the scope of TAs.

7. Working with business owners to review and recommend options to identify and evaluate current and proposed future architectures, including the current and future architecture breadth, requirements, usability, and other factors, as well as identification of potential re-use of ESS capabilities for each TA, DSD, or AoA.

8. Grooming of the Intake backlog to prioritize Intake workload. The Contractor shall prepare a Backlog Queue Prioritization Report that provides a listing of requests in the queue with priority ranking provided by Business Integration and Outcome Services (BIOS).

9. Supporting the transition of work products from CIS to CORP PLs or OIT Service Providers. The Contractor shall support, development, and deliver the Product Line Acceptance (PLA) document (see Attachment 8 template) and execution of the Transition process.

10. Maintaining statuses in a VA DMND tracking tool for all Cross-Portfolio DMNDs and CORP DMNDs.

Deliverables:

A. Technical Assessments (TAs) B. Detailed Solutioning Documents (DSDs) C. Analysis of Alternatives (AoAs) D. Backlog Queue Prioritization Report E. Product Line Acceptance (PLA) document

5.5 INFORMATION EXCHANGE SUPPORT

As part of the development of TAs, DSDs, AoAs, and architecture support, the Contractor shall utilize information in VA Systems Inventory (VASI). The Contractor shall feed relevant metadata back into VASI, such as, business capabilities, Business Reference Model (BRM), business processes, and information exchange details. The Contractor shall produce the VASI Update Report that captures the metadata updated in VASI.

A. VASI Update Report

5.6 COST ESTIMATION (CE) SUPPORT

The Contractor shall engage and communicate with OIT and business customers to develop, validate, and use CE processes and tools to determine the total cost of the IT products incorporating expenditures of activities, such as, planning, management, systems engineering, design, development, and sustainment. The Contractor shall work with VA cost estimators, and it is expected that the Contractor shall have a background in IT in order to understand the business needs and IT solutions to extrapolate the costs associated with the demands.

The Contractor shall provide the following support:

1. Developing CE Worksheets (see Attachment 7 template) utilizing standardized CIS CE processes, tools, and outputs. The CE Worksheet shall be inclusive of all applicable cost factors, be accurate, and document assumptions and risks. The Contractor shall be able to complete the CE Worksheet independently within the established procedures, business rules, and timelines.

2. Providing baseline two-year ROMs or eight-year CE Worksheets with development and sustainment dollars broken down for every year. The Contractor shall analyze the DMND work effort’s level of effort (LOE) to include all major cost drivers, such as, management and technical labor categories, development, sustainment, operations and maintenance, and other direct costs (ODCs) to include software, hardware, infrastructure, networking, and cloud technologies.

3. Reviewing, analyzing, and interpreting IT planning and development documents from a combination of resources, including but not limited to the system’s operating environment, software acquisition plans, architecture diagrams, cloud analysis, feasibility studies, market analyses, business plans, and analyses of competing products and domain.

4. Briefing and obtaining approval from Government cost estimators as part of a quality assurance (QA) process for validation prior to the final product(s) CE Worksheet release(s).

5. Updating the SharePoint-hosted SPM DMND CE Tracker with statuses of all new, in-progress, and completed DMNDs.

6. Performing continuous market research to identify industry changes and better business practices in all cost drivers, such as, ODCs, government full-time equivalent (FTE cost), dependent system interface costs, development, operations and maintenance, and sustainment costs to support cost estimates.

A. Rough Order of Magnitude (ROM) Worksheet B. CE Worksheet

5.7 REQUIREMENTS DEVELOPMENT SUPPORT PACKAGES (OPTIONAL

TASK 1)

If exercised, the Contractor shall provide additional Requirement Analysis Support Packages (Section 5.3). This optional task can be exercised up to six (6) times in the base period and up to six (6) times in each option period, in quantities of five (5), ten (10), or twenty (20) packages.

1. Five (5) Requirements Analysis Support Packages (separately priced)

2. Ten (10) Requirements Analysis Support Packages (separately priced)

3. Twenty (20) Requirements Analysis Support Packages (separately priced)

5.8 TA PACKAGES (OPTIONAL TASK 2)

If exercised, the Contractor shall provide additional TA Packages, which consists of TAs (Sections 5.4.1, 5.4.2, 5.4.3, 5.4.4, 5.4.8, 5.4.9, and 5.4.10) to include corresponding

ROMs (Section 5.6) and IMMs (Section 5.1.5). This optional task can be exercised up to six (6) times in the base period and up to six (6) times in each option period, in quantities of five (5), ten (10), or twenty (20) packages during base and option periods.

1. Five (5) TA Packages (separately priced)

2. Ten (10) TA Packages (separately priced)

3. Twenty (20) TA Packages (separately priced)

5.9 DSD PACKAGES (OPTIONAL TASK 3)

If exercised, the Contractor shall provide additional DSD Packages, which consists of DSDs (Section 5.4.1, 5.4.2, 5.4.3, 5.4.5, 5.4.7, 5.4.8, 5.4.9 and 5.4.10) to include corresponding CE Worksheets (Section 5.6) and IMMs (Section 5.1.5). This optional task can be exercised up to six (6) times in the base period and up to six (6) times in each option period, in quantities of five (5), ten (10), or twenty (20) packages during base and option periods.

1. Five (5) DSD Packages (separately priced)

2. Ten (10) DSD Packages (separately priced)

3. Twenty (20) DSD Packages (separately priced)

5.10 AOA PACKAGES (OPTIONAL TASK 4)

If exercised, the Contractor shall provide additional AoA Packages, which consists of AoAs (Section 5.4.1, 5.4.2, 5.4.3, 5.4.5, 5.4.7, 5.4.8, 5.4.9 and 5.4.10) to include corresponding CE Worksheets (Section 5.6) and IMMs (Section 5.1.5). This optional task can be exercised up to six (6) times in the base period and up to six (6) times in each option period in quantities of five (5), ten (10), or twenty (20) packages during base and option periods.

1. Five (5) AoA Packages (separately priced)

2. Ten (10) AoA Packages (separately priced)

3. Twenty (20) AoA Packages (separately priced)

5.11 PHASE-OUT TRANSITION PLAN (OPTIONAL TASK 5)

If exercised by VA, the Contractor shall develop and deliver a Phase-Out Transition Plan if all or part of the tasks are terminated or completely transitioned to the Government or a new Contractor at the end of the PoP. The Contractor shall submit details for the Phase-Out portion of the Transition Plan and execute the Phase-Out Transition Plan upon Government approval. The Contractor shall provide subject matter expertise support to affect the requisite knowledge transfer in accordance with the resulting Transition Plan. The transition period shall not exceed 60 days.

The Contractor shall work collaboratively with other support contractors and/or Government personnel. As part of collaboration, the Contractor shall convey all information, as it pertains to CIS effort. This support shall also consist of providing advice, clarification, or explanation to facilitate the understanding of the information presented. The Transition Plan shall detail both the assumption of responsibilities and the transfer of responsibilities to follow on parties at the conclusion of the PoP. This Transition Plan shall, at a minimum, include the following:

1. Coordination with Government representatives,

2. Review, evaluation, and transition of current support services,

3. Assist in the transition of historic data to new Contractor system,

4. Government-approved training and certification process,

5. Transfer of all necessary business and/or technical documentation,

6. Orientation phase and program to introduce Government personnel, programs, and users to the Contractor's team, tools, methodologies, and business processes,

7. Knowledge transfer demonstration.

A. Transition Plan

6.0 GENERAL REQUIREMENTS

6.1 ENTERPRISE AND IT FRAMEWORK

6.1.1 VA TECHNICAL REFERENCE MODEL

The Contractor shall support the VA enterprise management framework. In association with the framework, the Contractor shall comply with OIT Technical Reference Model (VA TRM). The VA TRM is one component within the overall Enterprise Architecture (EA) that establishes a common vocabulary and structure for describing the information technology used to develop, operate, and maintain enterprise applications. Moreover, the VA TRM, which includes the Standards Profile and Product List, serves as a technology roadmap and tool for supporting OIT. Architecture & Engineering Services (AES) has overall responsibility for the VA TRM.

6.1.2 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 Technical Architecture (ETA), https://www.ea.oit.va.gov/EAOIT/VA_EA/Enterprise_Technical_Architecture.asp, and VA Identity and Access Management (IAM) approved enterprise design and integration patterns, https://www.oit.va.gov/library/recurring/edp/index.cfm. 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 VA Handbook 6510 VA Identity and Access Management, VA Handbook 0735 Homeland Security Presidential Directive 12 (HSPD-12) Program, and align with the Federal Identity, Credential, and Access Management Roadmap and Implementation Guidance v2.0.

https://www.ea.oit.va.gov/EAOIT/VA_EA/Enterprise_Technical_Architecture.asp https://www.oit.va.gov/library/recurring/edp/index.cfm

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-3, VA Handbook 6500 Appendix F, “VA System Security Controls”, and VA IAM enterprise requirements for direct, assertion-based authentication, and/or trust based authentication, as determined by the design and integration patterns. 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, and NIST Federal Information Processing Standard (FIPS) 201-2. OMB Memoranda M-05-24 and M-19-17 can be found at:

https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2005/m05- 24.pdf, and https://www.whitehouse.gov/wp-content/uploads/2019/05/M-19-17.pdf respectively. Contractor delivered applications and systems shall be on the FIPS 201-2 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 design pattern as outlined in VA Enterprise Design Patterns.

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-3 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.

https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2005/m05-24.pdf https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2005/m05-24.pdf https://www.whitehouse.gov/wp-content/uploads/2019/05/M-19-17.pdf 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.

6.1.3 INTERNET PROTOCOL VERSION 6 (IPV6)

The Contractor solution shall support Internet Protocol Version 6 (IPv6) 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). IPv6 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 shall support native IPv6 and 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 and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall communicate using native IPv6 and dual stack (IPv6 / IPv4) operations.

6.1.4 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). Any deviations must be approved by the VA TIC 3.0 Working Group at vaoisesatic30team@va.gov.

6.1.5 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, currently Windows 10 (64bit), Edge (Chromium based), and 365 Apps for enterprise. Applications delivered to VA and intended to be deployed to Windows 10 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 United States https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf file://R04.med.va.gov/V03/EAS/Users/vhaeasWymbsk/TEMPLATES--NEW%20TAC%20PROCESS/PWS%20TEMPLATE%20(DO%20NOT%20TOUCH)%20-%20In%20Process%20Revisions/DO%20NOT%20TOUCH%20(next%20version/IPv6/(https:/www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1 file://R04.med.va.gov/V03/EAS/Users/vhaeasWymbsk/TEMPLATES--NEW%20TAC%20PROCESS/PWS%20TEMPLATE%20(DO%20NOT%20TOUCH)%20-%20In%20Process%20Revisions/DO%20NOT%20TOUCH%20(next%20version/IPv6/(https:/www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1 https://doi.org/10.6028/NIST.SP.500-267Br1 https://doi.org/10.6028/NIST.SP.800-119 https://www.whitehouse.gov/wp-content/uploads/2019/09/M-19-26.pdf https://www.cisa.gov/publication/tic-30-core-guidance-documents mailto:vaoisesatic30team@va.gov

Government Configuration Baseline (USGCB) and Defense Information Systems Agency (DISA) Secure Technical Implementation Guide (STIG) specific to the particular client operating system being used.

6.1.6 VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT LINE

MANAGEMENT (PLM)

The Contractor shall support VA efforts IAW the updated VIP and PLM. The major focus of the new VIP is on Governance and Reporting and is less prescriptive, with a focus on outcomes and continuous delivery of value. 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 Playbook and can be found at: https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 and the PLM Playbook can be found at https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946. The PLM Playbook pivots from project-centric to product-centric delivery and contains descriptive practices that focuses on outcomes. The PLM Playbook contains a set of “plays” that implement Development, Security, and Operations (DevSecOps) principles and processes such as automated development, continuous integration/continuous delivery, and release on demand. The PLM Playbook details how PLs implement Lean-Agile principles, methods, practices, and techniques through levels of maturity. VIP and PLM are the authoritative processes that IT projects must follow to ensure development and delivery of IT products.

6.1.7 PROCESS ASSET LIBRARY (PAL)

The Contractor shall perform their duties consistent with the processes defined in the OIT Process Asset Library (PAL). The PAL scope includes the full spectrum of OIT functions and activities, such as VIP 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. The Contractor shall follow the 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 https://www.va.gov/PROCESS/artifacts/maps/process_CONB_ext.pdf.

The main PAL can be accessed at www.va.gov/process.

6.1.8 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 & https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946 https://www.va.gov/PROCESS/artifacts/maps/process_CONB_ext.pdf http://www.va.gov/process

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 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 Vet360 to access personal contact information, if the solution relies on VA Veteran personal contact information data. Vet360 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.

6.1.9 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.