36C10B18R2839-0001001.pdf

36C10B18Q2839 0001

5. PROJECT NUMBER (if applicable)

CODE 7. ADMINISTERED BY

2. AMENDMENT/MODIFICATION NUMBER

CODE

6. ISSUED BY

8. NAME AND ADDRESS OF CONTRACTOR

4. REQUISITION/PURCHASE REQ. NUMBER 3. EFFECTIVE DATE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED

PAGE OF PAGES

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED

BPA NO. 1. CONTRACT ID CODE

FACILITY CODE CODE

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

E. IMPORTANT:

is extended,

(a) By completing Items 8 and 15, and returning __________ copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR

ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY is not extended.

12. ACCOUNTING AND APPROPRIATION DATA

(REV. 11/2016)

is required to sign this document and return ___________ copies to the issuing office. is not, A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

15C. DATE SIGNED

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES

SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER

BY

Contractor

16C. DATE SIGNED

14. DESCRIPTION OF AMENDMENT/MODIFICATION

16B. UNITED STATES OF AMERICA

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER 16A. NAME AND TITLE OF CONTRACTING OFFICER

15B. CONTRACTOR/OFFEROR

STANDARD FORM 30 PREVIOUS EDITION NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.243

(Type or print) (Type or print)

(Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

(Number, street, county, State and ZIP Code)

(If other than Item 6)

(Specify type of modification and authority)

(such as changes in paying office, appropriation date, etc.)

(If required)

(SEE ITEM 11)

(SEE ITEM 13)

(X)

CHECK

ONE

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

(Signature of person authorized to sign) (Signature of Contracting Officer)

1 25

TAC-18-50333

Department of Veterans Affairs

Technology Acquisition Center

23 Christopher Way

Eatontown NJ 07724

Department of Veterans Affairs

Technology Acquisition Center

23 Christopher Way

Eatontown NJ 07724

To all Offerors/Bidders

36C10B18R2839

X

X

CONTINUATION PAGE

The purpose of this Amendment A0001, to Request for Quote(RFQ) 36C10B18Q2839 titled

“Whole Health Mobile Application,” is as detailed below. All changes to RFP 36C10B18Q2839 have been captured in track changes.

1. Section B.5, Performance Work Statement (PWS), Paragraph 5.4.2, Performance

Management:

a. Task for user help desk to respond to inquiries through telephone and email responses regarding download process and applications performance is hereby incorporated at PWS Paragraph 5.4.2(1).

b. Task 5.4.2(4) to isolate performance issues to application is hereby deleted.

2. Section B.5, PWS Paragraph 6.1.4, Veterans Focused Integration Process (VIP) and PWS

Paragraph 6.1.5, Process Asset library (PAL) are hereby deleted.

3. The Quote Due Date of August 29, 2018 at 3PM EST remains.

Except as provided herein, all other terms and conditions of RFP 36C10B18Q2839 remain unchanged and in full force and effect.

B.5 PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Veterans Health Administration

Office of Patient Centered Care & Cultural Transformation

Whole Health Mobile Application

Date: July 3, 2018

TAC-18-50333

PWS Version Number: 1.0

1.0 BACKGROUND

The Department of Veterans Affairs (VA), Veterans Health Administration (VHA) Office of

Patient Centered Care & Cultural Transformation (OPCC&CT) has defined a clear vision and roadmap to proactively empower and equip users in better engaging in and managing their health and well-being known as Whole Health. The Whole Health approach is a reorientation of the user’s relationship with VA and combines state-of-the-art conventional medicine with personalized health planning, complementary and integrative health (CIH) approaches, and innovative self-care approaches. Through the Whole Health approach, users have access to health coaches, health and well-being information, education on managing their health and a host of resources that support the user’s achievement of their personal health goals. The OPCC&CT has established a Whole Health Pathway where OPCC&CT is training Whole Health Partners to facilitate users through a self-exploration process looking at their own health and well-being, starting with their Personal Health Inventory and finishing with the beginning of their Personal

Health Plan (PHP).

OPCC&CT seeks a mobile solution to enable all users (regardless of whether care is received within VA or commercially) to navigate the comprehensive array of currently available VA tools, resources and capabilities that support the Whole Health System. The OPCC&CT is seeking a mobile application (app) that is iOS and Android compatible and accessible via the

Internet.

See Attachment 1 for an overview of the Whole Health program and Attachment 2 for additional

Whole Health references.

2.0 APPLICABLE DOCUMENTS

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

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

2002”

2. “Federal Information Security Modernization Act of 2014”

3. Federal Information Processing Standards (FIPS) Publication 140-2, “Security

Requirements For Cryptographic Modules”

4. FIPS Pub 199. Standards for Security Categorization of Federal Information and

Information Systems, February 2004

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

Information Systems, March 2016

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

Contractors,” August 2013

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

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

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

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

Act of 2006, Title IX, Information Security Matters

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

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

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

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

15. 36 C.F.R. Part 1194 “Electronic and Information Technology Accessibility

Standards,” July 1, 2003

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

Information as a Strategic Resource,” July 28, 2016

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

Services (CHAMPUS)”

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

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

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

21. VA Directive 6500, “Managing Information Security Risk: VA Information Security

Program,” September 20, 2012

22. VA Handbook 6500, “Risk Management Framework for VA Information Systems –

Tier 3: VA Information Security Program,” March 10, 2015

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

24. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal

Information (SPI)”, July 28, 2016

25. VA Handbook 6500.3, “Assessment, Authorization, And Continuous Monitoring Of

VA Information Systems,” February 3, 2014

26. VA Handbook 6500.5, “Incorporating Security and Privacy in System Development

Lifecycle”, March 22, 2010

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

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

29. OI&T Process Asset Library (PAL), https://www.va.gov/process/ . Reference

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

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

31. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy

Impact Assessment,” October 15, 2014

32. VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy

Impact Assessment,” July 30, 2015

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

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

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

36. NIST SP 800-37, Guide for Applying the Risk Management Framework to Federal

Information Systems: a Security Life Cycle Approach, June 10, 2014

37. NIST SP 800-53 Rev. 4, Security and Privacy Controls for Federal Information

Systems and Organizations, January 22, 2015

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

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

Program, October 26, 2015

40. VA Handbook 0735, Homeland Security Presidential Directive 12 (HSPD-12)

Program, March 24, 2014 http://www.va.gov/vapubs http://www.va.gov/vapubs https://www.va.gov/process/ https://www.va.gov/process/maps.asp https://www.va.gov/process/artifacts.asp https://www.va.gov/trm/TRMHomePage.aspx

41. OMB Memorandum M-06-18, Acquisition of Products and Services for

Implementation of HSPD-12, June 30, 2006

42. OMB Memorandum 04-04, E-Authentication Guidance for Federal Agencies, December 16, 2003

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

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

45. OMB Memorandum, Guidance for Homeland Security Presidential Directive

(HSPD) 12 Implementation, May 23, 2008

46. Federal Identity, Credential, and Access Management (FICAM) Roadmap and

Implementation Guidance, December 2, 2011

47. NIST SP 800-116, A Recommendation for the Use of Personal Identity Verification

(PIV) Credentials in Physical Access Control Systems, November 20, 2008

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

49. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, Digital Identity Guidelines, June

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

51. NIST SP 800-164, Guidelines on Hardware-Rooted Security in Mobile Devices

(Draft), October 2012

52. Draft National Institute of Standards and Technology Interagency Report (NISTIR)

7981 Mobile, PIV, and Authentication, March 2014

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

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

55. VA Memorandum “Mandate to meet PIV Requirements for New and Existing

Systems” (VAIQ# 7712300), June 30, 2015, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4846

56. Trusted Internet Connections (TIC) Reference Architecture Document, Version 2.0, Federal Interagency Technical Reference Architectures, Department of Homeland

Security, October 1, 2013, https://s3.amazonaws.com/sitesusa/wp-content/uploads/sites/482/2015/04/TIC_Ref_Arch_v2-0_2013.pdf

57. OMB Memorandum M-08-05, “Implementation of Trusted Internet Connections

(TIC), November 20, 2007

58. OMB Memorandum M-08-23, Securing the Federal Government’s Domain Name

System Infrastructure, August 22, 2008

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

60. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public

Law 110–140), December 19, 2007

61. Section 104 of the Energy Policy Act of 2005, (Public Law 109–58), August 8, 2005 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4846 https://s3.amazonaws.com/sitesusa/wp-content/uploads/sites/482/2015/04/TIC_Ref_Arch_v2-0_2013.pdf https://s3.amazonaws.com/sitesusa/wp-content/uploads/sites/482/2015/04/TIC_Ref_Arch_v2-0_2013.pdf https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552

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

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

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

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

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

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

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

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

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

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

71. “Veteran Focused Integration Process (VIP) Guide 2.0”, May 2017, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

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

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

74. VA Memorandum “Use of Personal Email (VAIQ #7581492)”, April 24, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

75. VA Memorandum “Updated VA Information Security Rules of Behavior (VAIQ

#7823189)”, September, 15, 2017, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

3.0 SCOPE OF WORK

The Contractor shall provide a Whole Health mobile app that is iOS and Android compatible and accessible via the Internet. The scope of work includes Whole Health Mobile app development, implementation and configuration, and maintenance. Maintenance includes such things as bug fixes, operating system updates and new phone layouts (like the iPhone X).

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The period of performance (PoP) shall be a 12-month base period to include six months for development, implementation, configuration, deployment and six months for maintenance with two 12-month option periods to provide annual software updates, enhancements and maintenance.

An optional task is included for additional sprint cycles for development of additional functionality or enhancements. This optional task includes six one-month sprint cycles for a total of six months.

https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4411 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4412

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:

New Year's Day January 1

Independence Day July 4

Veterans Day November 11

Christmas Day December 25

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

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

Martin Luther King's Birthday Third Monday in January

Washington's Birthday Third Monday in February

Memorial Day Last Monday in May

Labor Day First Monday in September

Columbus Day Second Monday in October

Thanksgiving Fourth Thursday in November

4.2 PLACE OF PERFORMANCE

Access to VA facilities will be permitted when required. Tasks under this PWS shall be performed at Contractor facilities. The Contractor shall identify the Contractor’s place of performance in their Task Execution Plan submission.

4.3 TRAVEL

The Government anticipates travel under this effort to perform the tasks associated with the effort, as well as to provide management briefings or other consultations as necessary. Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government.

The total estimated number of trips in support of management briefings and other consultations for this effort is as follows:

1. One face to face kickoff meeting

2. One face to face meeting for each sprint

All meetings locations are expected to be in Washington, DC.

5.0 SPECIFIC TASKS AND DELIVERABLES

The contractor shall perform the following:

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the

Contractor’s approach, timeline and tools to be used in execution of the contract. The CPMP should take the form of both a narrative and graphic format that displays the schedule, milestones, risks and resource support. The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the PWS. The initial baseline CPMP shall be concurred upon and updated in accordance with Section B of the contract. The Contractor shall update and maintain the VA PM approved CPMP throughout the period of performance.

Deliverable:

A. Contractor Project Management Plan

5.1.2 REPORTING REQUIREMENTS

The Contractor shall provide the COR with Progress Reports in electronic form in Microsoft

Word and Project formats. The report shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding period. During the initial development phases through deployment phase, the reports shall be provided weekly. During the maintenance phase, the reports shall be monthly.

The Progress Reports shall cover all work completed during the reporting period, decision made, and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The report shall also include an itemized list of all Electronic and Information Technology (EIT) deliverables and their current Section 508 conformance status. The Contractor shall monitor performance against the CPMP and report any deviations.

It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

A. Weekly Progress Report

B. Monthly Progress Reports

5.1.3 TECHNICAL KICKOFF MEETING

The Contractor shall hold a technical kickoff meeting within 10 days after TO award. The

Contractor shall present, for review and approval by the Government, the details of the intended approach, work plan, and project schedule for each effort. The Contractor shall specify dates, locations, agenda (shall be provided to all attendees at least five calendar days prior to the meeting), and meeting minutes (shall be provided to all attendees within three calendar days after the meeting). The Contractor shall invite the Contracting Officer (CO), Contract Specialist (CS), COR, and the VA PM.

5.2 AGILE SPRINT DELIVERABLES

The Contractor shall provide cross-functional Contractor Scrum Teams to support the development of the Whole Health Application. Development of the Whole Health Application shall take place in iterative month-long sprints. The Government estimates that each Contractor

Scrum Team shall be comprised of five to seven staff. The Contractor may invoice at the end of each sprint upon Government acceptance of the Sprint Certification Package and Artifacts.

1. At the beginning of each monthly sprint, each Contractor Scrum Team shall initiate, coordinate, and participate in a Sprint Planning Meeting and develop a Sprint Plan with the VA Project Team, including the VA PM, COR, designated VA Product Owner and additional stakeholders, to plan the work to be accomplished for the sprint. Additionally, the team shall determine the acceptance criteria for the sprint and populate the Sprint

Backlog. The Contractor, in collaboration with the VA Project Team, shall define the relative complexity of each task and determine the amount of work that can be accomplished. All activity scheduled in each sprint and backlog shall be captured and have status showing all work items, changes, impediments, and retrospectives. The

Contractor shall update the Sprint Plan at the conclusion of sprint planning. Once the

Sprint Plan is accepted by the VA PM/COR and the VA Product Team, the sprint backlog may change throughout the duration of the sprint, however, the effort of work will remain constant.

2. The Contractor shall provide Sprint Demonstration that confirms all functionality developed in the sprint is operational. At the Sprint Demonstration, the Contractor

Scrum Team shall submit a Sprint Certification Package to the VA PM/COR for review and approval.

3. The Sprint Certification Package shall include a summary of the planned, accomplished, and unaccomplished work for the month-long sprint to include issues encountered and corrective actions taken as well as all artifacts produced, including any and all code

(submitted to VA source code repository), during the sprint. This package, certification that all work is completed, and a demonstration that all work planned for the sprint has been fully implemented, are necessary for sprint acceptance by the Government. The

Contractor must complete all work planned for each sprint and receive VA PM/COR approval of the Sprint Certification Package for the prior month-long sprint before beginning a new sprint.

4. The below task contains the basic requirements for the development of the Whole Health

Application. Once the Whole Health Application has been delivered by the Contractor, the maintenance phase shall maintain and sustain the Whole Health Application as well as perform app bug fixes, updates and issue mitigation through the period of performance of this contract.

The Contractor shall review, elaborate, and prioritize the project backlog at Attachment 003

Whole Health Application Backlog, during the agile development process in conference with the

OPCC&CT SME’s. This backlog grooming will occur continuously throughout the build to ensure the customer’s highest priorities are being met. The Contractor shall continuously support an iterative build and development methodology to complete all functionality described in the backlog. The Contractor shall continuously maintain the Project Backlog for each build, in every release and throughout the life of the period of performance.

Deliverables:

A. Sprint Plan

B. Sprint Certification Package and Artifacts

5.3 WHOLE HEALTH MOBILE APP REQUIREMENTS

This contract is to provide a mobile application for unlimited users, to enable and support a personalized Whole Health journey. To accomplish this, the resources developed by VA must be readily and easily accessible anytime, anywhere for each user. This contract shall bring together those resources in an easy to navigate app that is mobile and user friendly.

The Contractor shall provide a mobile app with a user-friendly interface to content accessible on mobile devices and desktop devices that will engage users as they navigate through the app and encourage the users to take advantage of and benefit from participation in the Whole Health

System. The app shall be designed to guide and actively involve the user in full and complete participation in the Whole Health approach. All of the user-generated information shall be stored locally on the user’s device. External content referenced by the app are publicly available outside of VA firewalls.

The Contractor shall define leading / branching questions used to identify the user preferences and interest in the Whole Health Pathways. These questions will guide the users through the app as part of the user experience to create the branching/decision making capability. The Contractor shall provide an algorithm to guide the path through the software based on user preferences and responses to the questions asked. The software shall link to resources, and provide construct for the entry of a smart goal by suggestion options for each field that is not free text, i.e. identify timeframe, free text goal, identify options for measuring etc.

It is expected that the Contractor will include OPCC&CT subject matter experts in all sprint meetings and recurring meetings where appropriate.

The capabilities of the Whole Health Application shall mirror the Whole Health journey as depicted in the diagram below:

The Whole Health Application shall utilize automated process flows that are triggered based upon data provided by the user. The functionality and output of the app shall synthesize information and assist the user in their journey with intelligent, customized recommendations and guidance. The app shall have the flexibility to adapt to the needs and preferences of the user to create the most personalized experience based on the branching questions. The data from the experience shall be available for printing if the user desires. The user experience shall be engaging, where appropriate to incentivize progression through the Whole Health journey, and provide the necessary capability to proactively engage the user with reminders, prompts, recognition and feedback and adaptive response to user data and input.

It is expected that this app will be stand-alone without the capability to interface with Electronic

Health Record (EHR) but will be built in such a way to allow future integration with the EHR

(Veterans Health Information Systems and Technology Architecture (VistA)/ Computerized

Patient Record System (CPRS)) for data exchange and for data triggers received from CPRS that serve to launch appropriate workflows, prescriptions and pathways for the user. In addition to the EHR, future work will include integration into myHealtheVet providing users a single access point for this resource along with many other resources available through that portal.

In order to be an Approved VA Mobile Application, the Contractor shall comply with steps and requirements identified on the Mobile App Development site:

https://mobile.va.gov/content/developing-va-apps. The Whole Health mobile application shall be required to undergo the VA App Compliance Reviews to include: Code Review, Section 508

Compliance Review, VA Branding Compliance Review, Enterprise Security Compliance

Review (refer to the Mobile App Development site for the full list of reviews) and shall comply with VA Handbook 6500 and NIST 800-53 requirements for certification and accreditation. A number of services are already available utilizing the VA mobile program’s Application

Programming Interface (API) gateway. Fast Healthcare Interoperability Resources (FHIR) is a standard for data transmission and subsequent storage.

5.4 MOBILE APP MAINTENANCE

The Contractor shall develop an Operations and Maintenance (O&M) Plan that will detail the planned approach to maintaining the Whole Health Application, how issues, bug fixed and routine upgrades shall be addressed. The updated O&M Plan shall include the Contractor’s concepts, methods and resources that shall be utilized to provide the required O&M support for

Whole Health Application as described in the tasks below.

The Contractor shall:

a) Create an O&M Plan.

b) Perform Whole Health Application O&M activities identified below in accordance with the approved O&M Plan.

c) Provide a summary of monthly O&M activities from each subtask below and key operating statistics as part of the Monthly Progress Report.

A. O&M Plan

5.4.1 APPLICATION ADMINISTRATION

The Contractor shall ensure that Whole Health Application renewals, version upgrades, and

Commercial Off-The-Shelf (COTS) patches/upgrades are implemented as required. The

Contractor shall renew the maintenance agreements annually on behalf of VA. Additionally, the

Contractor shall present version upgrades with an assessment of implementation risk to the COR to determine if upgrade contents are applicable to VA and can be installed without issue. The https://mobile.va.gov/content/developing-va-apps

Contractor shall estimate the impact of upgrades to customized code to ensure the scope of the upgrade implementation on Whole Health Application is fully defined. The Contractor shall implement version updates upon COR approval.

The Contractor shall provide ongoing application administration support including:

1. Establish Backup Schedules

2. Establish Monitoring Requirements and Parameters

3. Implement Software Upgrades

4. Configure and Install Software patches / version updates, Scripts and Parameter Settings

5. Tune Whole Health Application to resolve application performance issues

6. Monitor Application Logs

7. Application Versioning Retention – the Contractor shall ensure that Whole Health

Application versioning is retained, accessible and editable throughout the period of performance of the contract.

5.4.2 PERFORMANCE MANAGEMENT

The Contractor shall provide ongoing performance management support by ensuring that the uptime requirements of the system are met, monitoring services, and proactively responding to projected system demands. The Contractor shall:

1. Provide a user help desk to respond to inquiries through telephone and email responses regarding download process and applications performance. Email responses shall be made within 24 hours. Phone response shall be provided standard business hours of 8am

– 8pm EST. Content questions will be directed to VA staff.

1.2.Develop and maintain Whole Health Application Performance Management Plan

2.3.Collect system statistics and monitor system availability to ensure Whole Health

Application meets availability requirements of 95 percent.

3.4.Collect Help Desk Metrics – Calls answered, issue or problem resolved and compliance with contract requirements.

4. Isolate performance issues to the application and/or the hosting environment

a. Develop and implement availability and performance improvements to meet performance requirements.

b. Monitor Application Software Performance

c. Monitor Database Server Performance

d. Monitor Hardware Performance

e. Monitor Hosting Network Performance

f. Monitor Operating System Performance

A. Performance Management Plan

5.4.3 INCIDENT MANAGEMENT

The Contractor shall coordinate appropriate resources to address incidents (e.g. functional errors, availability/uptime, accessibility and security incidents) and communicate incident related information for situational awareness within twenty-four hours of the incident to the COR and

VA PM. The Contractor shall:

1. Document Incident Escalation Procedures

2. Escalate Incidents/Requests

3. Issue Incident Response Messages (IRMM) and/or Activity Not Responding (ANR)

Messages for Critical Maintenance

4. Log and Track Incidents/Requests

5. Notify COR of Incident

6. Perform Triage for Incidents/Requests

7. Provide Incident Reporting and Distribution

8. Respond to Incidents/Requests

9. Identify hosting or application changes required to ensure similar incidents will not occur.

10. Implement hosting or application changes upon approval of the COR.

5.4.4 NETWORK ADMINISTRATION

The Contractor shall implement and maintain the communications infrastructure utilized by

Whole Health Application. Network administration responsibilities include the hosting environment network and network communications. The Contractor shall:

1. Manage network connectivity.

2. Monitor network and identify issues as they occur.

3. Process updates as required for network changes and connectivity issues.

5.4.5 SECURITY MANAGEMENT

The Contractor shall comply with the security requirements identified on the Mobile Application

Development site https://mobile.va.gov/content/data-security and https://wiki.mobilehealth.va.gov/display/OISSWA where it applies to a stand-alone app described in these requirements.

5.4.6 APPLICATION ADMINISTRATION

The Contractor shall perform the processes related to hardware and operating systems, particularly changes to configuration that are released to the environment. The Contractor shall:

1. Update Application Guides with changes as required

2. Create User Authorizations and Profiles

3. Notify the COR of scheduled system outages/scheduled updates

4. Monitor and maintain system logs

5. Process backups

5.5 ADDITIONAL AGILE SPRINTS (OPTIONAL TASK)

If this Optional Task is exercised by VA, the Contractor shall provide up to 18 one-month sprints for development of functionality in accordance with Section 5.2 Agile Sprint Deliverables and

Section 5.3, Whole Health Mobile App Requirements.

5.6 OPTION PERIOD ONE

If Option Period One is exercised by VA, all tasks in the following sections and their sub-sections shall apply: 5.1 Project Management (excluding 5.1.3 Technical Kickoff Meeting) and 5.4 Mobile

App Maintenance.

5.7 OPTION PERIOD TWO

If Option Period Two is exercised by VA, all tasks in the following sections and their sub-sections shall apply: 5.1 Project Management (excluding 5.1.3 Technical Kickoff Meeting) and 5.4 Mobile

App Maintenance.

https://mobile.va.gov/content/data-security https://wiki.mobilehealth.va.gov/display/OISSWA

6.0 GENERAL REQUIREMENTS

6.1 ENTERPRISE AND IT FRAMEWORK

6.1.1 ONE-VA TECHNICAL REFERENCE MODEL

The Contractor shall support the VA enterprise management framework. In association with the framework, the Contractor shall comply with OI&T Technical Reference Model (One-VA

TRM). One-VA TRM is one component within the overall Enterprise Architecture (EA) that establishes a common vocabulary and structure for describing the information technology used to develop, operate, and maintain enterprise applications. One-VA TRM includes the Standards

Profile and Product List that collectively serves as a VA technology roadmap. Architecture, Strategy, and Design (ASD) has overall responsibility for the One-VA TRM.

6.1.2 FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT

(FICAM)

The Contractor shall support the latest Internet Protocol Version 6 (IPv6) based upon the directives issued by the Office of Management and Budget (OMB) on August 2, 2005

(https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m

05-22.pdf) and September 28, 2010 (https://cio.gov/wp-content/uploads/downloads/2012/09/Transition-to-IPv6.pdf). IPv6 technology, in accordance with the USGv6 Profile, NIST Special Publication (SP) 500-267

(https://www.nist.gov/programs-projects/usgv6-technical-basis-next-generation-internet), the

Technical Infrastructure for USGv6 Adoption (http://www-x.antd.nist.gov/usgv6/index.html), and the NIST SP 800 series applicable compliance

(http://csrc.nist.gov/publications/PubsSPs.html) shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices shall support native IPv6 and/or dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g. web, email, DNS, ISP services, etc.) shall support native IPv6 and/or dual stack (IPv6/ IPv4) users and all internal infrastructure and applications shall communicate using native IPv6 and/or dual stack (IPv6/ IPv4) operations.

Guidance and support of improved methodologies which ensure interoperability with legacy protocol and services in dual stack solutions, in addition to OMB/VA memoranda, can be found at: https://www.voa.va.gov/documentlistpublic.aspx?NodeID=282.

6.1.3 TRUSTED INTERNET CONNECTION (TIC)

The Contractor solution shall meet the requirements outlined in Office of Management and

Budget Memorandum M08-05 mandating Trusted Internet Connections (TIC)

(https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2008/m

08-05.pdf), M08-23 mandating Domain Name System Security (NSSEC)

(https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2008/m

08-23.pdf), and shall comply with the Trusted Internet Connections (TIC) Reference

Architecture Document, Version 2.0 https://s3.amazonaws.com/sitesusa/wp-content/uploads/sites/482/2015/04/TIC_Ref_Arch_v2-0_2013.pdf.

https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m05-22.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m05-22.pdf https://cio.gov/wp-content/uploads/downloads/2012/09/Transition-to-IPv6.pdf https://cio.gov/wp-content/uploads/downloads/2012/09/Transition-to-IPv6.pdf https://www.nist.gov/programs-projects/usgv6-technical-basis-next-generation-internet http://www-x.antd.nist.gov/usgv6/index.html http://csrc.nist.gov/publications/PubsSPs.html https://www.voa.va.gov/documentlistpublic.aspx?NodeID=282 https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2008/m08-05.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2008/m08-05.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2008/m08-23.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2008/m08-23.pdf

6.1.4 VETERAN FOCUSED INTEGRATION PROCESS (VIP)

The Contractor shall support VA efforts IAW the Veteran Focused Integration Process (VIP).

VIP is a Lean-Agile framework that services the interest of Veterans through the efficient streamlining of activities that occur within the enterprise. The VIP Guide can be found at https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371. The VIP framework creates an environment delivering more frequent releases through a deeper application of Agile practices. In parallel with a single integrated release process, VIP will increase cross-organizational and business stakeholder engagement, provide greater visibility into projects, increase Agile adoption and institute a predictive delivery cadence. VIP is now the single authoritative process that IT projects must follow to ensure development and delivery of IT products.

6.1.5 PROCESS ASSET LIBRARY (PAL)

The Contractor shall utilize PAL, the OI&T-wide process management tool that assists in the execution of an IT project (including adherence to VIP standards). PAL serves as an authoritative and informative repository of searchable processes, activities or tasks, roles, artifacts, tools and applicable standards or guides to assist project teams in facilitating their VIP compliant work.

6.2 SECURITY AND PRIVACY REQUIREMENTS

6.2.1 POSITION/TASK RISK DESIGNATION LEVEL(S)

In accordance with VA Handbook 0710, Personnel Security and Suitability Program, the position sensitivity and the level of background investigation commensurate with the required level of access for the following tasks within the PWS are:

Position Sensitivity and Background Investigation Requirements by Task

Task Number Tier1 / Low Risk Tier 2 / Moderate

Risk

Tier 4 / High Risk

5.1

5.2

5.3

5.4

5.5

The Tasks identified above and the resulting Position Sensitivity and Background Investigation requirements identify, in effect, the Background Investigation requirements for Contractor individuals, based upon the tasks the particular Contractor individual will be working. The submitted Contractor Staff Roster must indicate the required Background Investigation Level for each Contractor individual based upon the tasks the Contractor individual will be working, in accordance with their submitted proposal.

6.2.2 CONTRACTOR PERSONNEL SECURITY REQUIREMENTS

Contractor Responsibilities:

a. The Contractor shall prescreen all personnel requiring access to the computer systems to ensure they maintain the appropriate Background Investigation, and are able to read, write, speak and understand the English language.

b. Within 3 business days after award, the Contractor shall provide a roster of

Contractor and Subcontractor employees to the COR to begin their background investigations in accordance with the PAL template artifact. The Contractor Staff

Roster shall contain the Contractor’s Full Name, Date of Birth, Place of Birth, individual background investigation level requirement (based upon Section 6.2

Tasks), etc. The Contractor shall submit full Social Security Numbers either within the Contractor Staff Roster or under separate cover to the COR. The Contractor Staff

Roster shall be updated and provided to VA within 1 day of any changes in employee status, training certification completion status, Background Investigation level status, additions/removal of employees, etc. throughout the Period of Performance. The

Contractor Staff Roster shall remain a historical document indicating all past information and the Contractor shall indicate in the Comment field, employees no longer supporting this contract. The preferred method to send the Contractor Staff

Roster or Social Security Number is by encrypted e-mail. If unable to send encrypted e-mail, other methods which comply with FIPS 140-2 are to encrypt the file, use a secure fax, or use a traceable mail service.

c. The Contractor should coordinate with the location of the nearest VA fingerprinting office through the COR. Only electronic fingerprints are authorized. The Contractor shall bring their completed Security and Investigations Center (SIC) Fingerprint request form with them (see paragraph d.4. below) when getting fingerprints taken.

d. The Contractor shall ensure the following required forms are submitted to the COR within 5 days after contract award:

1) Optional Form 306

2) Self-Certification of Continuous Service

3) VA Form 0710

4) Completed SIC Fingerprint Request Form

e. The Contractor personnel shall submit all required information related to their background investigations (completion of the investigation documents (SF85, SF85P, or SF 86) utilizing the Office of Personnel Management’s (OPM) Electronic

Questionnaire for Investigations Processing (e-QIP) after receiving an email notification from the Security and Investigation Center (SIC).

f. The Contractor employee shall certify and release the e-QIP document, print and sign the signature pages, and send them encrypted to the COR for electronic submission to the SIC. These documents shall be submitted to the COR within 3 business days of receipt of the e-QIP notification email. (Note: OPM is moving towards a “click to sign” process. If click to sign is used, the Contractor employee should notify the

COR within 3 business days that documents were signed via e-QIP).

g. The Contractor shall be responsible for the actions of all personnel provided to work for VA under this contract. In the event that damages arise from work performed by

Contractor provided personnel, under the auspices of this contract, the Contractor shall be responsible for all resources necessary to remedy the incident.

h. A Contractor may be granted unescorted access to VA facilities and/or access to VA

Information Technology resources (network and/or protected data) with a favorably adjudicated Special Agreement Check (SAC), completed training delineated in VA

Handbook 6500.6 (Appendix C, Section 9), signed “Contractor Rules of Behavior”, and with a valid, operational PIV credential for PIV-only logical access to VA’s network. A PIV card credential can be issued once your SAC has been favorably adjudicated and your background investigation has been scheduled by OPM.

However, the Contractor will be responsible for the actions of the Contractor personnel they provide to perform work for VA. The investigative history for

Contractor personnel working under this contract must be maintained in the database of OPM.

i. The Contractor, when notified of an unfavorably adjudicated background investigation on a Contractor employee as determined by the Government, shall withdraw the employee from consideration in working under the contract.

j. Failure to comply with the Contractor personnel security investigative requirements may result in loss of physical and/or logical access to VA facilities and systems by

Contractor and Subcontractor employees and/or termination of the contract for default.

k. Identity Credential Holders must follow all HSPD-12 policies and procedures as well as use and protect their assigned identity credentials in accordance with VA policies and procedures, displaying their badges at all times, and returning the identity credentials upon termination of their relationship with VA.

A. Contractor Staff Roster

6.3 METHOD AND DISTRIBUTION OF DELIVERABLES

The Contractor shall deliver documentation in electronic format, unless otherwise directed in

Section B of the solicitation/contract. Acceptable electronic media include: MS Word

2000/2003/2007/2010, MS Excel 2000/2003/2007/2010, MS PowerPoint 2000/2003/2007/2010, MS Project 2000/2003/2007/2010, MS Access 2000/2003/2007/2010, MS Visio

2000/2002/2003/2007/2010, AutoCAD 2002/2004/2007/2010, and Adobe Postscript Data

Format (PDF).

6.4 PERFORMANCE METRICS

The table below defines the Performance Standards and Acceptable Levels of Performance associated with this effort.

Performance Objective Performance Standard Acceptable Levels of

Performance

A. Technical /

Quality of

Product or

Service

1. Demonstrates understanding of requirements

2. Efficient and effective in meeting requirements

3. Meets technical needs and mission requirements

4. Provides quality services/products

Satisfactory or higher

B. Project

Milestones and

Schedule

1. Established milestones and project dates are met

2. Products completed, reviewed, delivered in accordance with the established schedule

3. Notifies customer in advance of potential problems

Satisfactory or higher

C. Cost & Staffing 1. Currency of expertise and staffing levels appropriate

2. Personnel possess necessary knowledge, skills and abilities to perform tasks

Satisfactory or higher

D. Management 1. Integration and coordination of all activities to execute effort

Satisfactory or higher

The COR will utilize a Quality Assurance Surveillance Plan (QASP) throughout the life of the contract to ensure that the Contractor is performing the services required by this PWS in an acceptable level of performance. The Government reserves the right to alter or change the surveillance methods in the QASP at its own discretion. A Performance Based Service

Assessment will be used by the COR in accordance with the QASP to assess Contractor performance.

ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED

A1.0 Cyber and Information Security Requirements for VA IT Services

The Contractor shall ensure adequate LAN/Internet, data, information, and system security in accordance with VA standard operating procedures and standard PWS language, conditions, laws, and regulations. The Contractor’s firewall and web server shall meet or exceed VA minimum requirements for security. All VA data shall be protected behind an approved firewall. Any security violations or attempted violations shall be reported to the VA Program

Manager and VA Information Security Officer as soon as possible. The Contractor shall follow all applicable VA policies and procedures governing information security, especially those that pertain to certification and accreditation.

Contractor supplied equipment, PCs of all types, equipment with hard drives, etc. for contract services must meet all security requirements that apply to Government Furnished Equipment

(GFE) and Government Owned Equipment (GOE). Security Requirements include: a) VA

Approved…