36C77618R0091-002.docx

BA Health Enterprise Architecture

IDIQ PWS

PERFORMANCE WORK STATEMENT (PWS)

INDEFINITE DELIVERY INDEFINITE QUANTITY (IDIQ)

DEPARTMENT OF VETERANS AFFAIRS (VA)

VETERANS HEALTH ADMINISTRATION (VHA)

OFFICE OF HEALTH INFORMATICS (OHI)

STRATEGIC INVESTMENT MANAGEMENT (SIM)

BUSINESS ARCHITECTURE SERVICE (BA)

BA HEALTH ENTERPRISE ARCHITECTURE

Date: 08/14/18 PWS Version Number: 1.0

Table of Contents

BACKGROUND

Business Architecture (BA) Service is part of the Strategic Investment Management (SIM) division within the Department of Veterans Affairs (VA), Veterans Health Administration (VHA) Office of Health Informatics (OHI). Other services within SIM are Investment Governance Services (IGS), Requirements Development and Management (RDM), and Open Source Management. 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 organizational components of BA that are relevant to this PWS are as follows:

1. Director’s Office (includes Advisory)

2. Strategy and Planning

3. Operations and Quality Assurance

4. Integration and Reference Architecture

5. Process and Value Architecture

6. Information and Knowledge Architecture SIM provides leadership and staff resources for several integrated governance bodies of which BA plays a key role. Examples include: the Architecture and Requirements Investment Workgroup (ARIWG), and the Joint Technology Advisory Group (JTAG), a joint OIT and VHA body. Likewise, BA staff supports SIM with analyses of the benefits and risks associated with 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 open source solutions, functional requirements, business architecture, and investment management provided to the Information Technology Committee (ITC), which is charged with providing IT investment priorities and decisions for VHA.

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 Office of Health Informatics Strategic Investment Management Business Architecture obtain 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 task areas that shall be supported by this IDIQ are: Director’s Office (Advisory, Strategy, Planning, Operations, Tooling and Quality Assurance), Integration and Reference Architecture, Process and Value Architecture, Information and Knowledge Architecture, and Program/Project Management. This includes both professional and technical health information services in support of BA and VA/VHA program offices. The types of services represented under this IDIQ PWS are:

1. Business process modeling and Process and Value architecture services,

1. Business information modeling and Information and Knowledge 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 task areas,

1. Decision support services for collaboration efforts,

1. Participation on working groups or teams,

1. Architect, program and project management services to assist in planning, initiating, managing, executing, and closing out work efforts or projects,

1. Interoperability advisory services (e.g., Electronic Health Record Modernization (EHRM), Community Care, VA/VHA Modernization, VA/DoD interoperability work efforts/partnering)

1. Health Care Delivery analysis and design,

1. Health information strategic planning,

1. Strategic requirements analysis and alignment,

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

1. Independent assessments of VHA and VA business products and services for gaps or deficiencies,

1. Development and delivery of executive 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. Tooling configuration management and quality assurance activities

1. Coordination of BA Communications including publications and outreach, and

1. Services in support of VHA’s BA lifecycle.

Additionally, the architecture domain areas that will be supported by this IDIQ are categorized and depicted in the following list and diagrams:

The Capability Architecture domains are:

1. Clinical Care Capabilities – includes, Primary Care, Specialty Care, Dentistry, Geriatrics/Extended Care, Imaging, Laboratory/Pathology, Medicine Services, Mental Health, Radiation Oncology, Rehabilitation, Surgery

2. Clinical Enabling Capabilities – includes, Health Administration, Operational Support, Health Delivery Support, Quality Systems,

3. Care Coverage Capabilities – includes, Eligibility & Enrollment, Disability Evaluation, (Care) Approvals, Claims Processing, Provider Network Management, Other Care Coverage

4. Patient Management Capabilities – includes, Patient Education, Patient Registration, Patient Preferences, Other Patient Management The Service Perspective domains serve as a matrixed architectural layer to the capability domains, they are:

1. Common Healthcare Workflows – includes, Appointment Management, Consults & Referrals Management, Orders, Care Guidelines / Educational Materials, Adverse Reactions (incl. Drug Interactions), Patient Reminders, Care Co-ordination, Medication Administration, Care Plan Management, Observations, Diagnosis Management, ADT

2. Healthcare Specific Common Service Components – includes, Clinical Context Management, Medical Reference Library, Patient Location, Clinical Decisions Support (incl. Reminders), Registries, Positive Identification, Consents, Population Health Assessments

3. Virtual Veteran Record – includes, VPR, Documents & Images, Documentation, Terminology, Patient Identity, External Clinical Record Integration, Patient Entered Data Integration & Management, Record Access Control, Radiology Images, Demographics

4. Healthcare IT Infrastructure – includes, Single Sign On, Core GUI, Medical Device Integration

5. Enterprise IT Infrastructure VHA Capability Architecture

VHA Service Perspectives

Where appropriate, all services will employ VHA’s Capability Architecture and Services 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), International Institute of Business Analysis (IIBA) Business Analysis Body of Knowledge (BABOK) Guide in order to strengthen and improve OHI, SIM and BA’s ability to deliver quality health enterprise architecture information and services for leadership, clinicians and other health care professionals.

Please Note: The VA has ownership of all deliverables and work product involved in this effort.

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 will 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 IDIQ.

PERFORMANCE PERIOD

This PWS is being issued under an IDIQ. The duration of the single-award IDIQ shall not exceed five (5) years.

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

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

Under current definitions, four 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

The majority of the work performed under this IDIQ 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 will take place on Federal holidays or weekends, unless directed by the CO. Place of performance shall be determined at the TO level.

Below are samples of sites 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

1. Franklin Templeton 140 Fountain Parkway Suite 230 St. Petersburg, FL 33716

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 IDIQ 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 IDIQ 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 IDIQ. The Government will identify travel requirements on a TO basis. To the extent practicable, all travel shall be priced on a fixed-price basis. When it is not practicable to price travel on a fixed priced basis (i.e., travel is anticipated, but firm dates and/or locations are not known at the time the TO is awarded,), 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) must 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 “L”) 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 require 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 IDIQ. 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 will 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 will 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 base IDIQ contract will be placed by issuance of task orders against the base contract (estimated 1-3 task orders per year). The performance period will be specified in each Task Order (TO) Request whether in terms of an actual specified period or performance goals for performance-based orders. The performance period for each issued task order will be specified at the individual task order level. Each TO issued under this IDIQ shall specify its own period of performance, not to exceed the duration of the IDIQ base contract. Prior to each task order or exercised option year, an in-scope determination will be conducted to ensure we have not reached the ceiling/max of the contract.

SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

This PWS provides general requirements (i.e. additional required deliverables) and specific requirements (deliverables). Technical 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 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 as a result of future TO awards, 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 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 (includes Advisory)

2. Strategy and Planning

3. Operations and Quality Assurance

4. Integration and Reference Architecture

5. Process and Value Architecture

6. Information and Knowledge 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 will be ordered by simply applying the quantity the Government requires to the predetermined, firm-fixed-prices outlined in the price schedule of the basic contract (not-to-exceed travel costs will 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 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 will issue a Request for Proposal (RFP) that will include a detailed PWS with specific tasks and deliverables. The RFP will require the contractor to provide the appropriate labor categories from the basic contract and the corresponding level of effort. The result will be a firm-fixed-price TO award.

PROJECT MANAGEMENT OF CONTRACTOR ACTIVITIES

The contactor shall apply Project Management Institute (PMI) - http://www.pmi.org/, best practices to all project tasks in a fashion such that activities are traceable against contract requirements and meet each objective.

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 Contractor shall provide project management support, as detailed below, in compliance with VA management policies and guidelines such as Veteran-Focused Integrated Process (VIP). The Contractor shall identify to VA COR a Contractor Program Manager (PgM) that shall be the primary contact point for all contractor programmatic risks, issues, concerns, and status.

The Contractor shall deliver and maintain a Project Management Plan (PMP). The purpose of the PMP is to provide a tool to allow VA to effectively manage each TO. The PMP shall define the Contractor’s detailed approach, risks/issues, dependencies, assumptions, timeline, and tools to be used in the execution of the task order. The PMP shall describe the Contractor’s plans to support TO and includes an Integrated Master Schedule (IMS) in MS Project, detailing tasks, milestones, deliverables, resources, and dependencies. The PMP shall take the form of both a narrative and graphic format. The PMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection and reporting requirements as identified within the TO and as defined by VA PgM and Project Managers (PM) in support of specific areas defined in the PWS paragraph Section 5.0

0. Program Consolidated Monthly Report (PCMR):

The contractor shall produce and submit a consolidated monthly report describing progress and activities. This report will include written meeting minutes, summarizing meetings attended and minutes/notes captured, any task work adjustments or change requests, project issues and risk assessments, deliverables completion and schedule status, and summary notations of any background investigations and outstanding training requirements, to include the Project Management Plan (PMP). This report should also include a signed contractor rules of behavior and weekly contractor on-boarding/off-boarding status.

0. PM Quarterly Updates:

The contractor shall develop updates to the BA PMP for this functional task area. The following components will be included as areas of responsibility:

· Communication Management updates

· Quality Management and Control updates

· Staffing Management updates (including reach-back capabilities)

· Risk Management updates

· Schedule to include Work Breakdown Structure (WBS), tasks and milestone tracking, change requests, issue tracking, schedule statuses, staff rosters, status of staff background investigations and access requirements.

· Organizational Knowledge Retention and Knowledge Transfer Strategy/Approach

5.1.3 Meeting Facilitation, Reports and Briefs for Leadership:

The contractor shall develop 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 leadership and unit leads ensure that there is a high level awareness of the team engagements with BA customers and help to identify areas that require knowledge management activities for contracting staff to ensure their engagements are maximized and productive.

0. Conduct Kick-off Meeting (Not separately priced)

STRATEGY AND PLANNING SUPPORT SERVICES

The Contractor shall provide Strategy and Planning support services for healthcare clinical and administrative areas that include Health Information Technology (IT) Strategy; BA Planning, Tracking and Reporting; BA Communications and Marketing; Strategic Architecture Meta-model and Content, and SP Tooling Support.

Health IT Strategy. The Contractor shall support the National Leadership Council’s (NLC) Information Technology Committee’s (ITC) IT Strategy Sub-Committee (ITSSC) by facilitating monthly meetings and annual face-to-face meeting, development and publishing of the Health Information Strategic Plan (HISP), developing and obtaining endorsement from the IT Committee on the multi-year program (MYP) Prioritization Criteria each year, and participating in various specific-purpose work groups. The Contractor shall also support SIM Strategy and Planning activities including VHA IT Governance, assisting VHA with its development of the Stakeholder Engagement Strategy and Guiding Principles, provide consultative services with various stakeholders, and assist with the establishment of internal operations.

BA Planning, Tracking and Reporting. The Contractor shall assist BA in its development of the agenda for the annual BA Strategic Planning meeting, perform annual 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 BA Task List (BATL), and reporting status on progress toward meeting those tasks on the monthly BA All Hands call.

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

Strategic Architecture Meta-model and Content. The Contractor shall review, assess, and update the Strategic Architecture Meta-model and content annually.

SP Tooling Support. The Contractor shall maintain SP artifacts including VA Goals and Objectives, for example, and related mappings for inclusion in the Business Architecture Repository.

Consolidated Unit Monthly Report:

The contractor shall produce and submit a consolidated monthly report describing progress and activities. This report will include written meeting minutes, summarizing meetings attended and minutes/notes captured, monthly BATL updates, work plan updates, and any other strategy and planning architectural updates.

Quarterly Updates:

The contractor shall develop updates to the HISP and status brief for this functional task area. This includes review of current documentation with appropriate updates made, review of HISP change log and disposition of each item, and environmental scanning impacts.

OPERATIONS AND QUALITY ASSURANCE (OQA) SUPPORT SERVICES

OQA provides operational support across BA related to Tooling and Business Intelligence (BI) decision support. OQA’s role enables BA Units to operate and perform their work in an efficient manner by providing operational support and leveraging the best tools available while ensuring consistency, accuracy, and accessibility of BA data content across the various VA-approved tools in use. The Contractor shall provide OQA support services for healthcare clinical and administrative areas that include Tooling Management, Configuration Support, Production and Reporting, BA Physical Meta-model Design and Publications, Integrated Testing and Quality Assurance, and Configuration Management as it relates to continuous design and maturity in support of Dashboarding, BI and BA Tooling Utilization.

Tooling Management and Production. The Contractor shall support tooling management and production activities through working with other BA units and with stakeholders such as VA Office of Enterprise Architecture (OEA) to help BA foster and establish a collaborative environment exists 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 Unicom System Architect and the Rational Suite to include Software Architect and Tableau. The Contractor will be expected to be an expert in these tools to include configuration support, and familiar with common industry tooling in the architecture discipline.

BA Physical Meta-model. The Contractor shall review and assess the BA physical meta-model to determine if changes are required and will assist in making appropriate changes to same. This work will be done in collaboration with the Integration and Reference unit which has responsibility for the BA logical meta-model and integrating content leveraging tools such as Unicom System Architect (SA) and other VA-approved tools. Changes to BA tooling encyclopedia content will result in physical meta-model changes. These changes to the physical meta-model must 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 BA requirements. This may include working with various BA stakeholders such as OEA. 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 governance and investment prioritization.

Configuration Management (Dashboarding and Tooling Configuration). The Contractor shall utilize the VA-approved tooling environment to develop, produce and publish analytics 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 also may require working with various tooling environments to acquire access to products that will meet BA requirements.

Consolidated Unit Monthly Report:

The contractor shall produce and submit a consolidated monthly report describing progress and activities. This report will 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 will encompass monthly updates that provide identification and tracking associated with analysis, design, configuration, initiation, execution, implementation and testing of BA architecture tooling solutions, to include quality data integrity validations. The BA Tooling Support and Quality Assurance Plan will provide support for continued validation and maturation of physical meta-models in support of BA product integration, reporting and tooling configuration.

Quarterly Updates:

The contractor shall develop updates to the physical BA Meta-model, BA Configuration Management, and status brief for this functional task area. This includes review of current documentation with appropriate updates made, review of the BA meta-model and any changes needed, and any appropriate configuration management activities. The Quarterly Updates will include a quarterly BA Tooling Data Stewardship Management Plan that coincides with the BA Repository (BAR) quarterly publication accomplished by the Integration and Reference team. The Data Stewardship Management Plan shall track BA data objects and their mappings, data owner, source of record, data format, data steward, repository steward, versioning, update method and frequency, and update status. (4 quarterly updates which include physical BA Meta-model updates; Configuration Management updates; status brief updates; and BA Tooling Data Stewardship Management Plan updates)

INTEGRATION AND REFERENCE ARCHITECTURE SUPPORT SERVICES

The Contractor shall provide Integration and Reference support services for healthcare clinical and administrative areas that include assisting BA with defining and ranking VHA needs, planning, scope coordination and management, reporting, ad-hoc reference architecture analysis and continued maturity of all Integration and Reference architecture products and services. The Contractor shall support completion of work efforts, leveraging technical writer skills, which involve diverse internal and external stakeholder engagements including end users and subject matter experts, resulting in a common understanding of referential alignments and reporting. The healthcare related work efforts include VA Secretary and Under Secretary for Health identified and prioritized efforts. Examples of work effort focus areas include Greater Choice, Improve Timeliness, Suicide Prevention, Efficiency, and Modernize Systems.

For all tasks listed under this section, the contractor is not defining the scope of its own performance under this effort but rather shall be assisting VA with determining the level of effort needed for the Business Architecture Service to provide integration and reference architecture services to stakeholders.

Define and Prioritize VHA Information Technology Needs. The Contractor shall support the Business Customer in identifying and understanding the business needs, identifying gaps (IT and non-IT) to enhance the business understanding and accomplish business goals, and preparing the needs for VHA Governance (when/where appropriate). Work is based upon multi-year planning and prioritization activities organized and led by the ARIWG.

Planning and Scope Coordination. In conjunction with government leadership, the Contractor shall assist business customers with efforts to define and validate work effort scope, structure and schedule, identify and coordinate Stakeholders (Subject Matter Experts (SMEs), Business Owners and other supporting staff) including supporting the establishment of roles and responsibilities, review existing documentation (environmental scan and other relevant information), and facilitation of work effort kick-off meeting with identified Stakeholders to discuss all of the above.

VHA Integration Requirements and Reference Architecture. The Contractor shall assist in BA efforts to elicit, refine, and document integration and reference support activities associated with VHA’s Requirements repository to inform reporting, analysis, project planning and development. Support activities include modeling and architecture requirements elicitation utilizing Agile Methodologies, using VA approved Collaborative Lifecycle Management tools (currently primary tools are Rational Suite, Unicom System Architect and Tableau).

The level of effort of the Contractor will be limited to identified domains. Domains are understood through the VHA Capability Architecture and Service Perspective (see diagrams above). Capabilities offered by VHA form the architectural basis to help organize scope, requirements and architecture and are a perspective into the Business Architecture. Services are the mechanisms by which VHA achieves its Capabilities and form a Perspective into the Business Architecture.

Leveraging all relevant historical documentation as part of performing all tasks within this PWS, the Contractor shall provide support services that include Coordination of the delivery of Integration and Reference architecture work efforts, Delivery of Integration and Reference architecture support services, and Delivery of Integration and Reference architecture services to ensure appropriate operational and architectural integration and success.

Coordination of the delivery of Integration and Reference architecture work efforts. To include facilitation, business reference modeling (e.g., mappings/alignments) and re-engineering, architecture requirements capture, and approved scoping documentation and engagement strategies for healthcare clinical and administrative areas.

Delivery of Integration and Reference architecture support services. For the VHA healthcare clinical and administrative setting including business descriptive and definition modeling, analysis, mappings/alignments, matrices, functional decomposition, maturation of the business reference model, and maintenance of a comprehensive list and database of Integration and Reference artifacts/primitives and their alignments. Continue to improve database outliers and mapping updates.

Delivery of Integration and Reference architecture services to ensure successful integration. To ensure successful integration of architectural artifacts that yield business impact reports, using the current methodologies and industry best practices.

Domain/Work Effort Monthly Reports (DMR): This report shall include, as appropriate: models and matrices, summary updates, status/progress updates, Integrated Master Plan (IMP) and BA Task List (BATL) updates, and meeting minutes.

Reference Repository Packaging:

This report shall include final work effort packaging. Included in this report is the Business Architecture Repository (BAR) release documentation, updated/current VHA Capability Model, updated/current VHA Services Model and a complete inventory of all changes and updates with version control. All releases and documentation must 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. (quarterly) Integration Analysis Packaging:

This report will include updates and publications of the Business Function Framework (BFF) reference model and publication of VHA-BA wide logical relationship model, to include outcomes/impacts related to BA’s Physical Meta-Model. This documentation is uploaded into and maintained within VA-approved tooling (currently Unicom System Architect). All releases and documentation must 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-annually) Quarterly Work Activity Status Briefs:

These quarterly PowerPoint presentations will review the ongoing work efforts of the Integration and Reference architecture activities with BA team and stakeholders.

Consolidated Unit Monthly Report:

The contractor shall produce and submit a consolidated monthly report describing progress and activities. This report will include written meeting minutes, summarizing meetings attended and minutes/notes captured, tooling system status reports, integration activity updates, and any other operational updates relevant to integration and reference activities. Necessary updates to the BA Integration and Reference User Guide and Guiding Principles will be included.

PROCESS AND VALUE ARCHITECTURE SUPPORT SERVICES

The Contractor shall provide support services that shall include Coordination of the delivery of Process and Value architecture work efforts and Delivery of Process and Value support services.

For all tasks listed under this section, the contractor is not defining the scope of its own performance under this effort but rather shall be assisting VA with determining the level of effort needed for the Business Architecture Service to provide Process and Value Architecture support services to stakeholders.

Coordination of the delivery of Process and Value architecture work efforts. For healthcare clinical and administrative areas, to include work effort scoping and engagement strategies, modeling session facilitation, re-engineering of business process modeling utilizing Business Process Model and Notation (BPMN), architecture requirements capture and integration within the VA-approved tooling. Currently, Rational Tool Suite is the tool provided by the Government.

Delivery of Process and Value architecture support services.