P01-DRAFT BA IDIQ PWS - Health Architecture Serv V2.docx

BA Health Architecture Services and Standardization

IDIQ PWS

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS (VA)

VETERANS HEALTH ADMINISTRATION (VHA)

STRATEGIC INVESTMENT MANAGEMENT (SIM)

BUSINESS ARCHITECTURE SERVICES (BA)

HEALTH ARCHITECTURE SERVICES AND STANDARDIZATION

Date: TBD PWS Version Number: x.x

Table of Contents

BACKGROUND

Business Architecture (BA) is part of the Strategic Investment Management (SIM) Office within the Department of Veterans Affairs (VA), Veterans Health Administration (VHA). Other services within SIM are Investment Governance Services (IGS), and Requirements Development and Management (RDM). SIM was established to support the business’ health information technology (IT) needs by providing the information that leaders need to make sound decisions. SIM supports the vision of informing the transformation of VHA health care through the timely provision of structured information that enables leadership to make knowledgeable decisions on health and health IT investments. SIM’s mission is to facilitate sound decision making for the development, acquisition, and maintenance of health-focused IT investments by providing leadership with a comprehensive understanding of needed VHA business capabilities including business requirements, processes, information needs, IT strategy and priorities, and investment analysis. The focus of this Performance Work Statement (PWS) is on business architecture, work that is foundational to the IT acquisition process.

Business Architecture (BA) is an integral part of SIM. As its name suggests, BA develops and manages the VHA’s business architecture which structures and communicates VHA's healthcare business, including descriptions of business behaviors, functionality, processes, and the flow of information that is required to achieve VHA’s mission. The VHA business architecture supports and integrates with VA and other federal enterprise architectures. Key functional component areas of BA that are relevant to this PWS are as follows:

1. Director’s Office

2. Data Analytics and Design

3. Tooling Operations and Quality Assurance

4. Referential Architecture

5. Process Architecture

6. Information Architecture

SIM provides leadership and staff resources for several integrated governance bodies of which BA plays a key role. Likewise, BA staff support SIM with analyses of IT requests, to inform the Capability Management Boards (CMBs) who prioritize business cases submitted by program offices for IT solutions. SIM’s overarching mission is executed through functional services focused on functional requirements, business architecture, and investment management provided to the Information Technology Committee (ITC), which is charged with providing IT investment priorities and strategic considerations for VHA decision-making.

As VHA moves forward with its mission to honor America’s Veterans by providing exceptional health care that improves their health and well-being, it is imperative that Business Architecture obtains the support services, skill sets, and subject matter expertise available to ensure continuity of already established business architecture efforts.

Applicable Documents In the performance of the tasks associated with this PWS, the Contractor shall comply with the following:

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

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

3. FIPS Pub 201-2, “Personal Identity Verification of Federal Employees and Contractors,” August 2013

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

5. Carnegie Mellon Software Engineering Institute, Capability Maturity Model® Integration for Development (CMMI-DEV), Version 1.3 November 2010; and Carnegie Mellon Software Engineering Institute, Capability Maturity Model® Integration for Acquisition (CMMI-ACQ), Version 1.3 November 2010

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

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

8. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, http://www.va.gov/vapubs/

9. VA Handbook 0710, Personnel Security and Suitability Security Program, May 2, 2016, http://www.va.gov/vapubs

10. VA Directive and Handbook 6102, “Internet/Intranet Services,” July 15, 2008

11. 36 C.F.R. Part 1194 “Electronic and Information Technology Accessibility Standards,” July 1, 2003

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

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

14. An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule, October 2008

15. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended by the Workforce Investment Act of 1998 (P.L. 105-220), August 7, 1998

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

17. VA Directive 6500, “Managing Information Security Risk: VA Information Security Program,” September 20, 2012

18. VA Handbook 6500, “Risk Management Framework for VA Information Systems – Tier 3: VA Information Security Program,” March 10, 2015

19. VA Handbook 6500.1, “Electronic Media Sanitization,” November 03, 2008

20. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI)”, July 28, 2016 (http://www1.va.gov/vapubs/)

21. VA Handbook 6500.3, “Assessment, Authorization, And Continuous Monitoring of VA Information Systems,” February 3, 2014

22. VA Handbook 6500.5, “Incorporating Security and Privacy in System Development Lifecycle”, March 22, 2010

23. VA Handbook 6500.6, “Contract Security,” March 12, 2010

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

25. Office of Information and Technology (OI&T) ProPath Process Methodology (Transitioning to Process Asset Library (PAL) (reference process maps at http://www.va.gov/PROPATH/Maps.asp and templates at http://www.va.gov/PROPATH/Templates.asp). NOTE: In the event of a conflict, OI&T ProPath (PAL) takes precedence over other processes or methodologies.

26. One-VA Technical Reference Model (TRM) (reference at http://www.va.gov/trm/TRMHomePage.asp)

27. National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53, “Recommended Security Controls for Federal Information Systems and Organizations” (http://csrc.nist.gov/publications/PubsSPs.html)

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

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

30. VA Directive 6300, Records and Information Management, February 26, 2009

31. VA Handbook, 6300.1, Records Management Procedures, March 24, 2010

32. OMB Memorandum, “Transition to IPv6”, September 28, 2010

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

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

35. OMB Memorandum M-06-18, Acquisition of Products and Services for Implementation of HSPD-12, June 30, 2006

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

37. OMB memorandum M-11-11, “Continued Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors, February 3, 2011

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

39. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011

40. NIST SP 800-116, A Recommendation for the Use of Personal Identity Verification (PIV) Credentials in Physical Access Control Systems, November 20, 2008

41. OMB Memorandum M-07-16, Safeguarding Against and Responding to the Breach of Personally Identifiable Information, May 22, 2007

42. NIST SP 800-63-2, Electronic Authentication Guideline, August 2013

43. NIST SP 800-157, Guidelines for Derived PIV Credentials, December 2014

44. NIST SP 800-164, Guidelines on Hardware-Rooted Security in Mobile Devices (Draft), October 2012

45. Draft National Institute of Standards and Technology Interagency Report (NISTIR) 7981 Mobile, PIV, and Authentication, March 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. VA Memorandum, VAIQ # 7011145, VA Identity Management Policy, June 28, 2010 (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)

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

49. Trusted Internet Connections (TIC) Reference Architecture Document, Version 2.0, Federal Interagency Technical Reference Architectures, Department of Homeland Security, October 1, 2013, https://www.fedramp.gov/files/2015/04/TIC_Ref_Arch_v2-0_2013.pdf

50. OMB Memorandum M-08-05, “Implementation of Trusted Internet Connections (TIC), November 20, 2007

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

52. VA Memorandum, VAIQ #7497987, Compliance – Electronic Product Environmental Assessment Tool (EPEAT) – IT Electronic Equipment, August 11, 2014 (reference Document Libraries, EPEAT/Green Purchasing Section, https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552)

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

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

55. Executive Order 13693, “Planning for Federal Sustainability in the Next Decade”, dated March 19, 2015

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

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

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

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

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

61. VA Memorandum, “Implementation of Federal Personal Identity Verification (PIV) Credentials for Federal and Contractor Access to VA IT Systems”, (VAIQ# 7614373) July 9, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

62. VA Memorandum “Mandatory Use of PIV Multifactor Authentication to VA Information System” (VAIQ# 7613595), June 30, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

63. VA Memorandum “Mandatory Use of PIV Multifactor Authentication for Users with Elevated Privileges” (VAIQ# 7613597), June 30, 2015; https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

64. “Veteran Focused Integration Process (VIP) Guide 1.0”, December, 2015, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

65. “VIP Release Process Guide”, Version 1.4, May 2016, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4411

66. “POLARIS User Guide”, Version 1.2, February 2016, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4412

SCOPE OF WORK

The functional component areas the contractor shall support in this PWS are: Director’s Office, Data Analytics and Design, Operations and Quality Assurance, Integration and Reference Architecture, Process and Value Architecture, and Information and Knowledge Architecture. This includes both professional and technical architecture services in support of BA and VA/VHA program offices. The types of services represented under this PWS are:

1. Data Analytics and Design services,

1. Business process modeling and process architecture services,

1. Business information modeling and Information architecture services,

1. Integration and Reference architecture services,

1. Internal and external information exchange (e.g., analysis, issues, updates, trends),

1. Subject matter expert advice for all functional component areas,

1. Decision support services for collaboration efforts,

1. Participation on working groups or teams,

1. Architecture services which assist in planning, initiating, managing, executing, and closing out various architecture themed engagements,

1. Interoperability advisory services (e.g., Electronic Health Record Modernization (EHRM), Financial Management Business Transformation (FMBT), Supply Chain/VALOR, Defense Health Agency (DHA)/VHA collaboration work, VA/VHA Modernization, and other VA/DoD interoperability work efforts)

1. Health Care operational analysis and design,

1. Strategic requirements analysis and alignment,

1. Assessments of current and emerging architecture industry or federal architecture standards,

1. Independent assessments of VHA and VA architecture products and services for gaps or deficiencies, and recommendations for improvements and/or maturation

1. Development and delivery of executive architecture briefings and presentations to senior management on VHA emerging health technology change management, strategy, and other architectural artifacts

1. Internal and external collaboration planning

1. Architecture tooling configuration management and quality assurance activities

1. Database/data management and Business Intelligence Analytics and Reporting to include Artificial Intelligence (AI) use and integration where appropriate

1. Support for coordination of BA Communications including publications and outreach, and

1. All necessary services in support of the architecture continuum for VHA’s Health Architecture.

Additionally, not intended to be an exhaustive or static list, the following architecture domain areas shall be supported by this PWS and are categorized and depicted in the following list and figures:

1. Care Delivery Capabilities

· Clinical Care Capabilities

· Extended Care

· Radiology & Imaging

· Laboratory / Pathology

· Internal Medicine

· Mental Health

· Primary Care

· Women’s Health

· Primary Care General

· Primary Care Other

· Physical Med. & Rehabilitation

· Specialty

· Integrated Care Programs

· Surgery

· Social Programs / Services

· Emergency & Urgent Care

· Other Clinical Care

· Clinical Enabling Capabilities

· Health Administration

· Capacity Management

· Billing & Coding

· In Patient (incl ADT)

· Medical Records

· Privacy

· Other Health Admin

· Health Delivery Support

· Pharmacy

· Library

· Research

· Voluntary

· Education

· Patient Transportation

· Prosthetics

· Bio surveillance

· Other Health Del. Support

· Quality Systems

· Utilization Management

· Cred. & Privileging

· Patient Safety

· Other Quality Systems

· Operational Support

· Fiscal (excl. claims & billing)

· (Facility) Engineering

· Environ. Mgmt

· Supply Chain, Logistics, & Procurement

· Police

· Canteen Services

· Human Resources

· Other Op. Support

2. Care Coverage Capabilities

· Eligibility & Enrollment

· Disability Evaluation

· (Care) Approvals

· Claims Processing

· Provider Net. Mgmt

· Appeals

· Other Care Coverage

3. Patient Management Capabilities

· Patient Registration

· Patient Education

· Patient Preferences

· Patient Advocacy

· Patient Experience

· Other Patient Mgmt

4. Health Business Services

· Common Health Care Workflows

· Scheduling

· Consults & Referrals Management

· Orders

· Care Guidelines/Educational Materials

· Adverse Reactions

· Patient Reminders

· Care Coordination

· Medication Administration

· Care Plan Management

· Observations

· Diagnosis Management

· ADT

· Patient Assessments

· Immunizations

· Medication Review & Reconciliation

· Patient Check-in

· Gen. Virtual Health

· Other HC Workflows

5. Health Technology Services

· Common Health Care Services

· Clinical Context Management

· Medical Reference Library

· Patient Location

· Clinical Decision Support

· Registries

· Positive Identification

· Consents

· Population Health Analytics

· Other HC Services

· Virtual Veteran Record

· Documents & Images

· Documentation

· Terminology

· Patient Identity

· External Interoperability

· Patient Entered Data Integration / Management

· Record Access Control

· Radiology Images

· Demographics

· Benefits Data Access

· Other VVrs

· Health Care Infrastructure

· Single Sign On

· Core GUI

· Medical Device Integration

· Other HC Infrastructure

· Enterprise IT Infrastructure

· Data Analytics

· Inventory

· Workflow Engine

· Secure Messaging

· Security Services

· Reporting System

· Finance / Accounting System

· Barcoding & RFID technology

· Other Infrastructure Services

VHA Capability and Service Architecture

Figure 1: VHA Capability and Service Architecture In order to strengthen and improve VHA, SIM and BA’s ability to deliver quality health enterprise architecture information and services for leadership, clinicians and other health care professionals, the contractor shall employ VHA’s Capability and Service Architecture constructs and principles, and shall meet and/or conform to best business and industry practices, e.g., Federal Enterprise Architecture (FEA), federal segment architecture methodologies, DoD Architecture Framework (DoDAF), Health Level 7 (HL7), Services-Aware Interoperability Framework (SAIF), Office of National Coordinator (ONC), Federal Health Architecture (FHA), Malcolm Baldrige, Capability Maturity Model Implementation (CMMI), IT Infrastructure Library (ITIL), Project Management Institute’s (PMI™) Project Management Body of Knowledge (PMBOK), and International Institute of Business Analysis (IIBA) Business Analysis Body of Knowledge (BABOK) Guide.

Please Note: The VA has ownership of data first produced in the performance of this contract; Form, fit, and function data delivered under this contract; Data delivered under this contract (except for restricted computer software) that constitute manuals or instructional and training material for installation, operation, or routine maintenance and repair of items, components, or processes delivered or furnished for use under this contract; and All other data delivered under this contract unless provided otherwise for limited rights data or restricted computer software in accordance with FAR 52.227-14, Rights in Data.

Figure 2: VHA Transition Management Framework (Conceptual)

The following bulleted information describes the intent and a key business architecture concept as depicted in Figure 2:

· National Standard Baseline models exist, leveraging legacy IT and best practices in industry and across VHA

· Sites migrate from their disparate processes, as much as possible, to standard baseline

· National Standard Future State models exist informed by Oracle Workflows, field experience and actual practices using Oracle

· As Oracle rolls out transition it is from a more uniform starting point (the baseline) leading to more repeatable, predictable, results and outcomes

· Models are a part of the Change Management Framework that informs and enables standardized:

· Roles

· Software/Systems Used

· Activity Sequencing

· Applicable Policies/SOPs/Directives and Regulations

· Medical Equipment/Devices

· Applicable Fed EHR Workflows

· Associated Training and Education Materials

CHANGES TO THE PWS

Any changes to this PWS or any related Task Order PWS shall be authorized and approved only through written correspondence from the Contracting Officer (CO). A copy of each change shall be kept in a project folder along with all other products of the project. Costs incurred by the Contractor through the actions or authorizations of parties other than the CO shall be borne by the Contractor.

PERFORMANCE DETAILS

The following describes the performance details associated with this PWS.

PERFORMANCE PERIOD

This PWS is being issued under an IDIQ. The ordering period of this IDIQ is a five (5) year base period.

Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO).

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

Under current definitions, five (5) are set by date:

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

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

PLACE OF PERFORMANCE

Most of the work performed under this PWS shall take place at the Contractor’s site, with occasional meetings held at a Government facility. However, some TOs may require that the Contractor perform the work on-site at a government facility. No work at any Government site shall take place on Federal holidays or weekends, unless directed by the CO. Place of performance shall be determined at the TO level.

Below is an example of where performance may be required; however, the Government reserves the right to alter these locations.

1. VA Central Office 810 Vermont Ave. NW Washington, DC 20420

TRAVEL

The Government will reimburse the cost of travel required in conjunction with performance of orders issued under this contract. Reimbursement for travel is limited to that required in the performance of the order. Specific Government direction to attend meetings or gather information shall be reimbursed on a cost-reimbursable basis only. Local travel or the relocation of PWS holder personnel from other geographic areas for the purpose of staffing an order are not subject to reimbursement. The Government will not pay travel charges for travel to and from the PWS holder employee's home and (Government Office) or to and from one company building to another (either within a company or to and from a prime to a sub company). Travel costs subject to reimbursement are limited to travel occurring at the direction of the Government, performed in conjunction with a specific requirement for a trip authorized in the order. Any administrative/clerical support travel costs shall be considered and approved by the CO on a case-by-case basis.

Occasional travel may be required on individual TOs issued against the PWS. The Government will identify travel requirements on a TO basis. Travel shall be reflected on the TO as a separate, cost-reimbursable line item with a Not-to-Exceed (NTE) total expenditure.

Reimbursement of travel expenses are allowable only to the extent specifically authorized on the individual TO. Additionally, the VA Program Manager (PM) and CO’s Representative (COR) shall approve all travel requirements/requests before travel begins. Travel that occurs without pre-approval by the VA PM and COR will NOT be reimbursed. The Contractor shall submit a Travel Request Form (see Attachment “B”) no later than five (5) business days prior to the commencement of travel. Travel and per diem expenses will be reimbursed on an actual expenditures’ basis in accordance with FTR and FAR 31.205-46. In order to be reimbursed for travel, the Contractor shall submit supporting documentation as required by FTR with invoices. FTR requires receipts for travel expenditures of $75.00 or more. Expenses for subsistence and lodging will be reimbursed to the Contractor only to the extent where an overnight stay is necessary and authorized by FTR in effect at the time of the stay for the specific location. Additional information can be found at:

http://www.gsa.gov/Portal/gsa/ep/contentView.do?contentType=GSA_OVERVIEW&contentId=14161

NON-DISCLOSURE AGREEMENTS AND CONFLICTS OF INTEREST

Due to the procurement-sensitive nature of the deliverables produced by this effort, Contractors (both at the prime and sub-contractor level at all tiers) shall be required to execute Non-disclosure/Conflict of Interest Agreements.

Pursuant to Veterans Affairs Acquisition Regulation (VAAR) 852.209-70, Organizational Conflicts of Interest, the Contractor shall also provide an additional statement with its offer(s) which describes, in a concise manner, all relevant facts concerning any past, present, or currently planned interest (financial, contractual, organizational, or otherwise) or actual or potential organizational conflicts of interest relating to the services to be provided under this solicitation and any subsequent TOs issued under this PWS. The Contractor shall also provide statements with its offer(s) containing the same information for any consultants and sub-contractors identified in its proposal and which shall provide services under the solicitation.

The Contractor may also provide the CO relevant facts which show how the Contractor’s organizational and/or management system or other actions would avoid or mitigate any actual or potential organizational conflicts of interest. The presentation of any such information intended to reflect the Contractor’s attempts and/or plans to mitigate any actual or potential organizational conflicts of interest does not in and of itself, however, guarantee that the CO shall approve any such mitigation attempts/plans.

Nondisclosure or misrepresentation of actual or potential organizational conflicts of interest at the time of the offer or arising as a result of a modification to the contract, may result in the termination of the contract at no expense to the Government.

TASK ORDER PROCEDURES

Orders against the established term PWS contract shall be placed by issuance of task orders against the term contract (estimated 2-3 task orders over a 5-year period). Each TO issued under this PWS shall specify its own period of performance, not to exceed the duration of the PWS term contract. Prior to each task order, an in-scope determination shall be conducted to ensure we have not reached the ceiling/max of the contract.

SPECIFIC TASKS AND DELIVERABLE REQUIREMENTS

The Contractor shall perform the following:

This PWS provides general requirements (i.e., additional required deliverables) and specific requirements (deliverables). Functional component areas are described in Section 5.1. This section encompasses the work to be completed throughout the contract and provides both general and specific deliverables associated within each functional component area. Other deliverables may be added within the functional component areas if they are determined to be within scope of this PWS. Requirements shall fall within the areas described in Sections 5.0 and 6.0. Furthermore, as the general requirements become further defined, they may be incorporated into this contract on an as needed basis to facilitate future ordering, provided such requirements are deemed to be within the scope of this PWS.

Individual TOs may encompass one or more functional component focus areas listed below. Further functional area details are described to provide greater insight into the complexity and uniqueness of some potential TO requirements covered by this PWS. Functional component area requirements are not mutually exclusive and may apply across multiple functional areas.

The Functional Component Areas are:

1. Director’s Office

2. Data Analytics and Design

3. Tooling Operations and Quality Assurance

4. Reference Architecture

5. Process Architecture

6. Information Architecture

Deliverables The deliverables associated with the tasks described below as predefined are specific in nature. Individual TOs may encompass more than one specific requirement listed below. Tasks identified as predefined in this section shall be ordered by simply applying the quantity the Government requires to the predetermined, firm-fixed-prices outlined in the PWS price schedule (not-to-exceed travel costs shall be included at the individual task order level as deemed necessary).

Additional Required Deliverables The deliverables associated with the tasks described below as not specific and are general in nature (i.e., not yet fully defined). Individual TOs may encompass more than one general requirement listed below. The details provided for the general requirements are described to provide greater insight into the complexity and uniqueness of potential future TO task requirements covered by this PWS. General requirements are not mutually exclusive and may apply across multiple requirements. To facilitate the award of TOs under this section, the Government shall issue a Request for Proposal (RFP) that shall include a detailed PWS with specific tasks and deliverables. The RFP shall require the contractor to provide the appropriate labor categories from the PWS contract and the corresponding level of effort. The result shall be a firm-fixed-price TO award.

Additional deliverables which are determined to be within the Scope of Work may also be identified at the individual TO level.

VENDOR MANAGEMENT OF CONTRACTOR ACTIVITIES AND DIRECTORS OFFICE SUPPORT

The Vendor shall apply Project Management Institute (PMI) - https://www.pmi.org , best practices to all project tasks in a manner such that activities are traceable against contract requirements and meet each objective. Likewise, the Vendor shall provide proactive and interactive engagement across all functional component areas of architecture support, to include innovative and creative analysis and recommendations, and preemptive actions to ensure timeliness for all engagements and continued architecture maturity.

The contractor shall provide for comprehensive knowledge management and knowledge transfer to VA personnel and partners for all contract requirements. The contractor shall employ methods such as presentations, papers, meetings, and virtual workspace content management. The scope descriptions below provide further articulation of key focus areas for contractor support responsibility:

0. Enterprise Health Architecture Consolidated Monthly Accomplishment Report:

The contractor shall produce and submit a consolidated monthly report describing progress and activities. This report shall include any written meeting agenda, list of attendees/absentees, minutes/notes captured, any task work adjustments or change requests, program office issues and risk assessments, deliverables completion and any architecture recommendations founded upon program-level architecture support, special projects and reviews of BA office level architecture maturity in support of VHA. (Monthly - 12 consolidated reports)

0. Enterprise Health Architecture Quarterly Accomplishment Updates:

The contractor shall develop updates to the BA Management Plan for this functional component area. The following components shall be included as areas of responsibility (Quarterly - 4 comprehensive presentations):

· Communication and Risk Management updates

· Quality Management and Control updates

· Staffing Management updates (including reach-back capabilities) to include no less than: change requests, staff rosters, status of staff background investigations and access requirements and summary notations of any outstanding training requirements

· Integrated Master Schedule (IMS) to include a Work Breakdown Structure (WBS), tasks and milestone tracking, issue tracking, and schedule status for all BA engagements (past/present/future).

· Organizational Knowledge Retention and Knowledge Transfer Strategy/Approach and updates

· Directors Office Insights related to special projects, engagements, and conceptual/tactical architecture plans which may influence the wholistic future of the Health Architecture and its utility.

5.1.3 Enterprise Architecture Leadership Meetings and Director’s Office Support:

The contractor shall provide senior architecture support for the development of reports and briefs, as well as facilitate BA weekly leadership and unit lead engagements for the purpose of establishing a consistent level of knowledge of the status and progress of team work effort assignments and ongoing activities. Regular reports and briefings to government leadership and leads ensure a high level of awareness regarding team engagements with customers and help to identify situations that require government knowledge and decisional management of specific activities. Contracting staff will strive to ensure customer engagements provide maximum value and are highly productive.

The Contractor shall assist DO in its development of the agenda for the annual BA Strategic Planning meeting, document minutes and action items during execution of the meeting, facilitate recurring review and analysis of BA goals and objectives and revise as necessary to ensure alignment to VA/VHA goals and objectives, assist BA in its solicitation of new tasks from each unit in support of BA goals, consolidating that information into the Integrated Master Schedule (IMS), and reporting status on progress toward meeting those tasks as requested, and during monthly BA All Staff calls throughout the period of performance of this contract.

The Contractor shall assist in the updating of BA communications and marketing materials as warranted (e.g., blogs, fact sheets and presentations) and in determining marketing strategies to enhance customer awareness and BA’s image with stakeholders.

(Monthly - 12 comprehensive packages)

DATA ANALYTICS AND DESIGN (DAD) SUPPORT

Data Analytics and Design unit serves as primary customer support for guidance concerning Health Architecture (HA) data analytics and architecture content. DAD coordinates the integration of business architecture data and services and defines architecture design requirements used in governance and alignments across the enterprise. The Contractor shall provide support services for architecture content analysis and meta-model strategic design to support Health Architecture design and implementation. This work will include proactive customer engagement support, quarterly and annual review/governance documentation and briefing support and general maintenance of standards, guidance and procedures. Likewise, the vendor will create and implement innovative graphical design materials and provide stewardship of improvements to existing reports and tooling. The scope descriptions below provide further articulation of key focus areas for contractor support responsibility:

Architecture Content Analysis. Ad-hoc and routine architecture content analysis, health architecture meta-model strategic design, assist BA leadership with determining the meaning and value of an architecture-alignment

Design Implementation and Support. Health Architecture design and implementation support (to include emergent conceptual, logical and physical model design implementation and strategic considerations)

Customer Engagement and Stakeholder Support. Proactive support for both internal and external customers and stakeholder support for enablement and utilization of Business Architecture products and services across BA/SIM/VHA

Governance Review and Support. Annual and quarterly review and governance of existing and emergent activities to include associated documentation for concurrence/accuracy

Development and Maintenance of Architecture Standards, Guidance and Procedures. Maintenance and generation of architecture standards, guidance and procedures, including web-based and document-based content creation and control, SharePoint hosting and site maintenance, syndication, governance and change management.

Graphic Design Implementation. Creation, implementation and maintenance of innovative graphical design materials and standards that accurately convey the value of Business Architecture products, services, protocols and procedures to assist BA with effective and concise communication of the meaning and value of an architecture alignment and associated key products and services.

Consolidated Data Analytics and Design Accomplishment Report:

The contractor shall produce and submit a consolidated monthly report describing progress and activities. This report shall include a summary of meetings attended, minutes/notes captured, monthly IMS updates, work plan updates, and any other data analytics and design updates. (12 consolidated monthly reports) Quarterly Data Analytics and Design Leadership Progress Briefing and Accomplishment Updates:

The contractor shall develop updates to the status brief for the DAD functional component area. This includes review of current documentation with appropriate updates made, and environmental scanning impacts. These quarterly PowerPoint presentations shall inform the completed and upcoming work efforts of the DAD unit with BA team and stakeholders. (Quarterly - 4 comprehensive presentations) Health Architecture Logical Information Model Publication:

This report shall include updates and publications of the VHA Capability and Service Architecture reference model and publication of VHA wide logical information model, to include outcomes/impacts related to the Physical Health Architecture Meta-Model. All key architecture concepts and relationships shall be addressed. This documentation is uploaded into and maintained within VA-approved tooling (SQL Server, Visio, Cameo and other tooling – as appropriate). All documentation shall be in a format that is consumable by business customers using Microsoft Office, as well as published and integrated in the BA tooling repositories in order to be consumable by stakeholders. (Semi-Annual – 2 Model Publications)

TOOLING OPERATIONS AND QUALITY ASSURANCE (OQA) SUPPORT

OQA provides operational tooling support across BA, to include architecture databases, SharePoint, and Business Intelligence (BI) decision support. OQA performs the research, analysis of alternatives, selection, and operational implementation of tools to meet BA’s requirements. OQA’s role ensures the quality, consistency, accuracy, and accessibility of data content across the various tools and environments in use. OQA shares industry and VA best practices in enterprise architecture, business architecture, business requirement, business process and information architecture, and Health Information Technology (HIT), with the goal of attaining proper alignment among these areas. The Contractor shall provide OQA support services for healthcare clinical and administrative areas that include Tooling Management and Production, Physical Meta-Model Design and Publications, Integrated Testing and Quality Assurance, Data and User Interfaces, and Configuration Management as it relates to continuous design and maturity in support of Dashboarding, BI and BA Tooling Utilization. The scope descriptions below provide further articulation of key focus areas for contractor support responsibility:

Tooling Management and Production: The Contractor shall support tooling management and production activities through working with other BA units and stakeholders such as Requirements Development and Management (RDM), Investment Governance Services (IGS), and VA Architecture and Engineering Service (AES) to help BA foster and establish a collaborative environment that meets BA tooling requirements. Support efforts include identification and tracking associated with analysis, design, initiation, execution, implementation, and reporting related to BA architecture tooling solutions. Current tooling includes Microsoft Visio, Microsoft Power Platform, and Microsoft SQL Server. The Contractor shall be expected to be an expert in these tools to include configuration support and be familiar with other common industry tooling in the architecture discipline.

Health Architecture (HA) Physical Meta-model: The Contractor shall review and assess the HA physical meta-model to determine if changes are required and shall assist in making appropriate changes to same. This work shall be done in collaboration with the Data Analytics and Design (DAD) unit, which has responsibility for the HA Logical Meta-Model and integrating content by leveraging tools such as Microsoft SQL Server Management Studio, Microsoft Visual Studio, and other VA-approved tools. Changes to BA tooling encyclopedia content shall result in physical meta-model changes. These changes to the physical meta-model shall be implemented throughout the BA tooling environments. This includes support for continued analysis and maturation of a physical meta-model in support of BA product integration and tooling configuration.

Integrated Testing and Quality Assurance: The Contractor shall support integrated testing of BA tools and ensure quality assurance of tooling products and underlying database designs that meet HA requirements. This may include working with various BA stakeholders such as RDM, IGS, AES, and EHRMIO. The Contractor shall perform tooling integration and testing support, to include assistance for all BA units to develop and test custom BI reporting in support of auditing, reporting, analytics, governance and investment prioritization.

Data and User Interfaces: The Contractor shall support the identification, design, testing, and implementation of data interfaces within BA, across SIM, and with available VA application programming interfaces (API). This work will include the implementation of user interfaces to facilitate the extraction, transformation, and loading of data, the correction of data quality issues, and user interaction with the data.

Configuration Management (Architecture and Tooling Configuration): The Contractor shall support OQA with the management of the addition/inclusion of new architecture concepts, and the archival of any deprecated concepts, thereby ensuring consistent management of all architecture concepts. Architecture Concepts are items such as Process Roles, Enterprise Data Object Tables (EDOT) and Business Capabilities typically conveyed via Conceptual and Logical Information Models (the Health Architecture CIM and LIM). These concepts are normally designed, developed and introduced via other core BA organizational units. Likewise, the Contractor shall utilize the VA-approved tooling environment to develop, produce and publish Business Intelligence analytics, reports, and dashboard views with the input of appropriate BA units. As necessary, the Contractor shall work with BA tooling owners to ensure the VA-approved tool can be configured to customize products needed by BA. This may also require working with various tooling environments to acquire access to products that shall meet HA requirements.

Consolidated Tooling Management Monthly Accomplishment Report:

The contractor shall produce and submit a consolidated monthly report describing progress and activities. This report shall include written meeting minutes, summarizing meetings attended and minutes/notes captured, tooling system status reports, integrated testing and quality assurance updates, and any other operations and quality assurance updates. Likewise, the contractor shall include a BA Tooling Support and Quality Assurance Plan which shall encompass monthly updates that provide identification and tracking associated with analysis, design, configuration, initiation, execution, implementation and testing of HA architecture tooling solutions, to include quality data integrity validations. The BA Tooling Support and Quality Assurance Plan shall provide support for continued validation and maturation of physical meta-models in support of BA product integration, reporting and tooling configuration. (Monthly - 12 consolidated reports) Quarterly Tooling Management Leadership Progress Briefing and Accomplishment Updates:

The contractor shall develop the following Quarterly Updates and Briefings: physical Health Architecture (HA) meta-model updates and change log; HA database maintenance and configuration updates; a status brief for the OQA functional component area; and HA database data dictionary updates and change log. (Quarterly - 4 comprehensive presentations)

· Physical Health Architecture meta-model updates - The physical HA meta-model updates shall include a review of the HA Conceptual and Logical Information Models to identify any changes needed to the physical meta-model, execution of appropriate updates to the physical meta-model, and documentation of changes executed.

· Health Architecture database maintenance and configuration updates - The HA database maintenance and configuration updates shall include a review of the current database environment, data interfaces and documentation of any appropriate maintenance or configuration management activities.

· Tooling Management Status Brief - The status brief shall be a separate quarterly PowerPoint presentation which will provide updates on the completed and upcoming work efforts of the OQA unit to inform the BA team and stakeholders.

· Health Architecture Data Dictionary - The HA database data dictionary shall track HA data concepts and their mappings, data concept owner, source of record, data format, concept steward, repository steward, versioning, update method and frequency, and update status.

INTEGRATION AND REFERENCE ARCHITECTURE SUPPORT

The Integration and Reference (IR) team coordinates the integration of business architecture concepts and depicts the components of VHA’s business and their relationships to one another. IR develops and maintains multiple architectural perspectives, including the relationships among VHA functions, capabilities, services, and other relevant architectural concepts. IR also supports the categorization and planning of underlying process and information elements used to deliver healthcare and this work helps ensure that VHA standardization and optimization plans can be analyzed and assessed across the enterprise. Additionally, IR maintains the VHA Health Architecture Repository (HAR), which houses business/health architecture content and their associations. The Contractor shall provide integration and reference architecture support services for healthcare clinical and administrative areas. This includes assisting BA with architecturally defining VHA referential frameworks and performing research, mapping and association activities, planning, scope coordination and management, and reporting. The contractor shall also support ad hoc reference architecture analysis and the continued maturation of all integration and reference architecture concepts. The Contractor shall execute work efforts and assignments involving diverse internal and external stakeholder engagements, including interactions with end users and subject matter experts, resulting in a common understanding of referential alignments and reporting requirements. Healthcare related work efforts shall support VA Secretary and Under Secretary for Health identified and prioritized initiatives. Examples include efforts related to Electronic Health Record Modernization (EHRM), Financial Management Business Transformation (FMBT), Supply Chain/VA Logistics Refresh (VALOR), and Defense Health Agency (DHA)/VHA collaboration activities. The scope descriptions below provide additional detail on key contractor support responsibility:

Analyze and Inform VHA Information Technology Needs - This includes identifying and understanding business needs, assessing gaps, overlaps, and redundancies (both IT and non-IT), and enhancing business understanding to support the achievement of business goals. The Contractor shall prepare identified needs for VHA Governance review when and where appropriate. This work is based on multi-year planning and prioritization activities organized and led by the Architecture Requirements and Investment Working Group (ARIWG).

Planning and Scope Coordination - In conjunction with government leadership, assist architecture customers with defining and validating work effort scope, structure, and schedule. This includes identifying and coordinating stakeholders—such as Subject Matter Experts (SMEs), Business Owners, and other supporting staff—supporting the establishment of roles and responsibilities,…