36C10B18R2839-008.pdf

PAGE 1 OF 1. REQUISITION NO.

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NO. 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

a. NAME b. TELEPHONE NO. (No Collect Calls) 8. OFFER DUE DATE/LOCAL

TIME

9. ISSUED BY CODE 10. THIS ACQUISITION IS UNRESTRICTED OR SET ASIDE: % FOR:

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

RFQ IFB RFP

15. DELIVER TO CODE 16. ADMINISTERED BY CODE

17a. CONTRACTOR/OFFEROR CODE FACILITY CODE 18a. PAYMENT WILL BE MADE BY CODE

TELEPHONE NO. DUNS: DUNS+4:

PHONE: FAX:

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS CHECKED

SEE ADDENDUM

19. 20. 21. 22. 23. 24.

ITEM NO. SCHEDULE OF SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Govt. Use Only)

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA ARE ARE NOT ATTACHED.

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN _______________ 29. AWARD OF CONTRACT: REF. ___________________________________ OFFER

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND DATED ________________________________. YOUR OFFER ON SOLICITATION

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY (BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED SET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

30b. NAME AND TITLE OF SIGNER (TYPE OR PRINT) 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER (TYPE OR PRINT) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION (REV. 2/2012)

PREVIOUS EDITION IS NOT USABLE Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS 74

36C10B18Q2839 08-15-2018

Mike Frank 7324409701 08-29-2018

3:00PM EST

Department of Veterans Affairs

Technology Acquisition Center

23 Christopher Way

Eatontown NJ 07724

X

X

541512

$27.5 Million

X

N/A

X

See Delivery Schedule Department of Veterans Affairs

Technology Acquisition Center

23 Christopher Way

Eatontown NJ 07724

Department of Veterans Affairs

Technology Acquisition Center

Financial Services Center

PO Box 149971

Austin TX 78714-8971

This Request for Quote (RFQ) is being issued for:

Whole Health Mobile Application

This RFQ will result in a Firm-Fixed-Price Contract

Period of Performance is 12 months from date of award to include 6 months for development, implementation, configuration, deployment and 6 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

Points of Contact:

Contract Specialist - Michael Frank, 732-440-9701

Michael.Frank@va.gov

Contracting Officer - Juan Quinones, 732-440-9714

Juan.Quinones@va.gov

X X

Juan Quinones

Contracting Officer

36C10B18Q2839

Table of Contents

SECTION A

A.1 SF 1449 SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 GOVERNING LAW

B.2 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT

B.3 CONTRACT ADMINISTRATION DATA

B.4 PRICE SCHEDULE

B.5 PERFORMANCE WORK STATEMENT

SECTION C - CONTRACT CLAUSES

C.1 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

C.2 52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT

STATUTES OR EXECUTIVE ORDERS—COMMERCIAL ITEMS (JUL 2018)

C.3 52.217-7 OPTION FOR INCREASED QUANTITY—SEPARATELY PRICED LINE

ITEM (MAR 1989)

C.4 52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR 2000)

C.5 VAAR 852.203-70 COMMERCIAL ADVERTISING (JAN 2008)

C.6 VAAR 852.219-10 VA NOTICE OF TOTAL SERVICE-DISABLED VETERAN-OWNED

SMALL BUSINESS SET-ASIDE (JUL 2016)(DEVIATION)

C.7 VAAR 852.232-72 ELECTRONIC SUBMISSION OF PAYMENT REQUESTS (NOV

2012)

C.8 VAAR 852.237-70 CONTRACTOR RESPONSIBILITIES (APR 1984)

C.9 VAAR 852.270-1 REPRESENTATIVES OF CONTRACTING OFFICERS (JAN 2008) . 48

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION E - SOLICITATION PROVISIONS

E.1 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB

1998)

E.2 52.209-7 INFORMATION REGARDING RESPONSIBILITY MATTERS (JUL 2013) ... 50

E.3 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—COMMERCIAL

ITEMS (NOV 2017)

E.4 52.227-15 REPRESENTATION OF LIMITED RIGHTS DATA AND RESTRICTED

COMPUTER SOFTWARE (DEC 2007)

E.5 52.233-2 SERVICE OF PROTEST (SEP 2006)

E.6 VAAR 852.233-70 PROTEST CONTENT/ALTERNATIVE DISPUTE RESOLUTION

(JAN 2008)

E.7 VAAR 852.233-71 ALTERNATE PROTEST PROCEDURE (JAN 1998)

E.8 BASIS FOR AWARD

E.9 QUOTE SUBMISSION INSTRUCTIONS

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 GOVERNING LAW

Federal law and regulations, including the Federal Acquisition Regulations (FAR), shall govern this Contract/Order. Commercial license agreements may be made a part of this Contract/Order but only if both parties expressly make them an addendum hereto. If the commercial license agreement is not made an addendum, it shall not apply, govern, be a part of or have any effect whatsoever on the Contract/Order; this includes, but is not limited to, any agreement embedded in the computer software (clickwrap), any agreement that is otherwise delivered with or provided to the Government with the commercial computer software or documentation (shrinkwrap), or any other license agreement otherwise referred to in any document. If a commercial license agreement is made an addendum, only those provisions addressing data rights regarding the

Government’s use, duplication and disclosure of data (e.g., restricted computer software) are included and made a part of this Contract/Order, and only to the extent that those provisions are not duplicative or inconsistent with Federal law, Federal regulation, the incorporated FAR clauses and the provisions of this Contract/Order; those provisions in the commercial license agreement that do not address data rights regarding the Government’s use, duplication and disclosure of data shall not be included or made a part of the Contract/Order. Federal law and regulation including, without limitation, the Contract Disputes Act (41 U.S.C. § 7101 et seq.), the Anti-Deficiency Act (31 U.S.C. § 1341 et seq.), the Competition in Contracting Act (41

U.S.C. § 3301 et seq.), the Prompt Payment Act (31 U.S.C. §3901 et seq.), Contracts for Data

Processing or Maintenance (38 U.S.C. § 5725), and FAR clauses 52.212-4, 52.227-14, 52.227-19 shall supersede, control, and render ineffective any inconsistent, conflicting, or duplicative provision in any commercial license agreement. In the event of conflict between this Clause and any provision in the Contract/Order or the commercial license agreement or elsewhere, the terms of this Clause shall prevail. Claims of patent or copyright infringement brought against the

Government as a party shall be defended by the U.S. Department of Justice (DOJ). 28 U.S.C. §

516. At the discretion of DOJ, the Contractor may be allowed reasonable participation in the defense of the litigation. Any additional changes to the Contract/Order must be made by contract/order modification (Standard Form 30) and shall only be effected by a warranted

Contracting Officer. Nothing in this Contract/Order or any commercial license agreement shall be construed as a waiver of sovereign immunity.

B.2 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT

(1) Definitions.

(a) Licensee. The term “licensee” shall mean the U.S. Department of Veterans Affairs

(“VA”) and is synonymous with “Government.”

(b) Licensor. The term “licensor” shall mean the contractor having the necessary license or ownership rights to deliver license, software maintenance and support of the computer software being acquired. The term “contractor” is the party identified in Block 17a on the

SF1449. If the contractor is a reseller and not the Licensor, the contractor remains responsible for performance under this order.

(c) Software. The term “software” shall mean the licensed computer software product(s) cited in the Schedule of Supplies/Services.

(d) Maintenance. The term “maintenance” is the process of enhancing and optimizing software, as well as remedying defects. It shall include all new fixes, patches, releases, updates, versions and upgrades, as further defined below.

(e) Technical Support. The term “technical support” refers to the range of services providing assistance for the software via the telephone, email, a website or otherwise.

(f) Release or Update. The term “release” or “update” are terms that refer to a revision of software that contains defect corrections, minor enhancements or improvements of the software’s functionality. This is usually designated by a change in the number to the right of the decimal point (e.g., from Version 5.3 to 5.4). An example of an update is the addition of new hardware.

(g) Version or Upgrade. The term “version” or “upgrade” are terms that refer to a revision of software that contains new or improved functionality. This is usually designated by a change in the number to the left of the decimal point (e.g., from Version 5.4 to 6).

(2) Software License

(a) Unless otherwise stated in the Schedule of Supplies/Services, the Performance Work

Statement or Product Description, the software license provided to the Government is a perpetual, nonexclusive license to use the software

(b) The Government may use the software in a networked environment.

(c) Any dispute regarding the license grant or usage limitations shall be resolved in accordance with the Disputes Clause incorporated in FAR 52.212-4(d).

(d) All limitations of software usage are expressly stated in the Schedule of

Supplies/Services and the Performance Work Statement/Product Description.

(3) Software Maintenance and Technical Support

(a) If the Government desires to continue software maintenance and support beyond the period of performance identified in this contract or order, the Government will issue a separate contract or order for maintenance and support. Conversely, if a contract or order for continuing software maintenance and technical support is not received the contractor is neither authorized nor permitted to renew any of the previously furnished services.

(b) The contractor shall provide software support services, which includes periodic updates, enhancements and corrections to the software, and reasonable technical support, all of which are customarily provided by the contractor to its commercial customers so as to cause the software to perform according to its specifications, documentation or demonstrated claims.

(c) Any telephone support provided by contractor shall be at no additional cost.

(d) The contractor shall provide all maintenance services in a timely manner in accordance with the contractor’s customary practice or as defined in the Performance Work

Statement/Product Description. However, prolonged delay (exceeding 2 business days) in resolving software problems will be noted in the Government’s various past performance records on the contractor (e.g., www.ppirs.gov).

(e) If the Government allows the maintenance and support to lapse and subsequently wishes to reinstate it, any reinstatement fee charged shall not exceed the amounts that would have been charged if the Government had not allowed the subscription to lapse.

(4) Disabling Software Code. The Government requires delivery of computer software that does not contain any code that will, upon the occurrence or the nonoccurrence of any event, disable the software. Such code includes but is not limited to a computer virus, restrictive key, node lock, time-out or other function, whether implemented by electronic, mechanical, or other means, which limits or hinders the use or access to any computer software based on residency on a specific hardware configuration, frequency of duration of use, or other limiting criteria. If any such disabling code is present, the contractor agrees to indemnify the

Government for all damages suffered as a result of a disabling caused by such code, and the contractor agrees to remove such code upon the Government’s request at no extra cost to the

Government. Inability of the contractor to remove the disabling software code will be considered an inexcusable delay and a material breach of contract, and the Government may exercise its right to terminate for cause. In addition, the Government is permitted to remove the code as it deems appropriate and charge the Contractor for consideration for the time and effort expended in removing the code.

(5) Manuals and Publications. Upon Government request, the contractor shall furnish the most current version of the user manual and publications for all products/services provided under this contract or order at no cost.

http://www.ppirs.gov/

B.3 CONTRACT ADMINISTRATION DATA

(continuation from Standard Form 1449, block 18A.)

1. Contract Administration: All contract administration matters will be handled by the following individuals:

a. CONTRACTOR: To Be Determined

b. GOVERNMENT: Contracting Officer (36C10B)

Department of Veterans Affairs

Technology Acquisition Center

23 Christopher Way

Eatontown, NJ 07724

2. CONTRACTOR REMITTANCE ADDRESS: All payments by the Government to the contractor will be made in accordance with:

[X] 52.232-33, Payment by Electronic Funds Transfer—System For Award

Management, or

[ ] 52.232-36, Payment by Third Party

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly [ ]

b. Semi-Annually [ ]

c. Other [X] Upon Acceptance of Deliverables in Section B.4

4. GOVERNMENT INVOICE ADDRESS: All Invoices from the contractor shall be submitted electronically in accordance with VAAR Clause 852.232-72 Electronic Submission of

Payment Requests.

5. ACKNOWLEDGMENT OF AMENDMENTS: The Quoter acknowledges receipt of amendments to the Solicitation numbered and dated as follows:

AMENDMENT NO DATE

B.4 PRICE SCHEDULE

Inspection/Acceptance//F.O.B: Destination.

All deliverables must be submitted electronically to the VA Program Manager (PM), Contracting

Officer’s Representative (COR), and Contracting Officer unless otherwise specified in the line item. Please be advised that in accordance with Federal Acquisition Regulation (FAR) Part

2.101, a “day” means, unless otherwise specified, a CALENDER day. Additionally, deliverables with due dates falling on a weekend or holiday shall be submitted the following Government work day after the weekend or holiday.

The Price Schedule contains contract line items identified as not separately priced (NSP). This means the price for the line item is included in the price of another, related line item. The

Contractor shall not invoice the Government for any portion of the contract line item which contains an NSP until the Contractor has delivered the total quantity of all related contract line items and the Government has accepted them.

Base Period

Period of Performance: 12 months from date of award

CLIN DESCRIPTION QTY UNIT UNIT PRICE TOTAL PRICE

0001 PROJECT MANAGEMENT

In accordance with (IAW) paragraphs 5.1 of the Performance Work Statement (PWS).

This Firm-Fixed-Price (FFP) Contract Line

Item Number (CLIN) includes all labor, materials, and deliverables required for the successful completion of the services detailed in PWS paragraphs 5.1 (inclusive of all of its subparagraphs).

The price of CLIN 0001 shall be included in and allocated to CLIN 0002 through CLIN

0003.

Period of performance shall be 12 months from date of award.

12 MO NSP NSP

0001AA Contractor Project Management Plan

IAW paragraph 5.1.1 of the PWS.

Due 30 days after contract and updated monthly thereafter.

1 LO NSP NSP

0001AB Weekly Progress Report

IAW paragraph 5.1.2 of the PWS.

Due weekly during initial development phases through deployment phase.

26 EA NSP NSP

0001AC Monthly Progress Report

6 EA NSP NSP

Due the fifth day of each month throughout the period of performance during the maintenance phase.

0002 COTS LICENSE

If proposing a COTS product, Quoters shall quote the price of the 6-month perpetual license to co-term with the expiration of the base period.

1 LO $ $

0003 WHOLE HEATLH MOBILE

DEVELOPMENT

IAW paragraphs 5.2 - 5.3 of the PWS.

This FFP CLIN includes all labor, material, and other costs required for the successful completion of the tasks IAW PWS paragraph

5.2 and its subparagraphs.

The Contractor shall only invoice upon completion of each one-month sprint and

COR acceptance of the sprint certification package and artifacts

6 EA $ $

0003AA Sprint Plan

IAW paragraph 5.2 of the PWS

Due upon completion of the Sprint.

6 EA $NSP $NSP

0003AB Sprint Certification Package and Artifacts

IAW paragraph 5.2 of the PWS

Due upon completion of the Sprint.

6 EA $NSP $NSP

0004 WHOLE HEALTH APPLICATION

MAINTENANCE

IAW paragraph 5.4 of the PWS.

This FFP CLIN includes all labor, material, travel, and other costs required for the successful completion of the tasks IAW PWS paragraph 5.4.

Period of performance shall be 6 months from completion of development.

6 MO $ $

0004AA O&M Plan

IAW paragraphs 5.4 of the PWS

Due Monthly

1 EA $NSP $NSP

0005 PERFORMANCE MANAGEMENT

PLAN

IAW paragraphs 5.4.2 of the PWS

1 EA $NSP $NSP

Due Monthly

0006 CONTRACTOR STAFF ROSTER

IAW paragraph 6.2.2 of the PWS.

Due three days after contract award and updated throughout the period of performance.

The price of this CLIN shall be allocated to

CLIN 0002 through CLIN 0003.

1 EA NSP NSP

0007 FINAL SECTION 508 COMPLIANCE

TEST RESULTS

IAW paragraph A3.4 of the PWS.

Due upon delivery of each deliverable.

The price of this CLIN shall be allocated to

CLIN 0002 through CLIN 0003.

1 EA NSP NSP

BASE PERIOD TOTAL $

Option Period 1

This 12-month option period may be exercised in the sole discretion of the Government IAW FAR 52.217-9

Option to Extend the Term of the Contract. If exercised, this option shall commence immediately after expiration of the Base Period.

CLIN DESCRIPTION QTY UNIT UNIT PRICE TOTAL PRICE

1001 PROJECT MANAGEMENT

IAW paragraphs 5.1 of the PWS.

This FFP CLIN includes all labor, materials, and deliverables required for the successful completion of the services detailed in PWS paragraphs 5.1 (inclusive of all of its subparagraphs, excluding 5.1.3).

The price of CLIN 1001 shall be included in and allocated to CLIN 1002 through CLIN

1003.

from commencement of Option Period 1.

12 MO NSP NSP

1001AA Contractor Project Management Plan

Due 30 days after contract option and updated monthly thereafter.

12 EA NSP NSP

1001AB Monthly Progress Report 12 EA NSP NSP

Due the fifth day of each month throughout the period of performance.

1002 COTS LICENSE

If proposing a COTS product, Quoters shall quote the price of the 12-month perpetual license to start upon the expiration of the base period.

1 LO $ $

1003 WHOLE HEALTH APPLICATION

MAINTENANCE

IAW paragraph 5.3 of the PWS.

This FFP CLIN includes all labor, material, travel, and other costs required for the successful completion of the tasks IAW PWS paragraph 5.3.

12 MO $ $

1003AA O&M Plan

IAW paragraphs 5.4 of the PWS

1004 PERFORMANCE MANAGEMENT

PLAN

OPTION PERIOD 1 TOTAL $

Option Period 2

This 12-month option period may be exercised in the sole discretion of the Government IAW FAR 52.217-9

Option to Extend the Term of the Contract. If exercised, this option shall commence immediately after expiration of the Option Period 1.

CLIN DESCRIPTION QTY UNIT UNIT PRICE TOTAL PRICE

2001 PROJECT MANAGEMENT

IAW paragraphs 5.1 of the PWS.

This FFP CLIN includes all labor, materials, and deliverables required for the successful completion of the services detailed in PWS paragraphs 5.1 (inclusive of all of its subparagraphs, excluding 5.1.3).

12 MO NSP NSP

The price of CLIN 1001 shall be included in and allocated to CLIN 1002 through CLIN

1003.

2001AA Contractor Project Management Plan

Due 30 days after contract option and updated monthly thereafter.

12 EA NSP NSP

2001AB Monthly Progress Report

Due the fifth day of each month throughout the period of performance.

12 EA NSP NSP

2002 COTS LICENSE

If proposing a COTS product, Quoters shall quote the price of the 12-month perpetual license to start upon the expiration of option period one.

1 LO $ $

2003 WHOLE HEALTH APPLICATION

MAINTENANCE

IAW paragraph 5.3 of the PWS.

travel, and other costs required for the successful completion of the tasks IAW PWS paragraph 5.3.

from commencement of Option Period 2.

12 MO $ $

2003AA O&M Plan IAW paragraphs 5.4 of the PWS

2004 PERFORMANCE MANAGEMENT

PLAN

OPTION PERIOD 2 TOTAL $

OPTIONAL TASK 1: Additional Sprint Cycles Additional Sprints Cycles for Application Enhancement

This is an optional task, FAR 52.217-7, Option for Increased Quantity – Separately priced Line

Item (MAR 1989). Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. This optional task can be exercised from time to time, multiple times not to exceed 18 one-month sprints in total. This option may be exercised in the Base Period and/or during Option Periods 1 and

2.

CLIN DESCRIPTION QTY UNIT UNIT PRICE TOTAL PRICE

3001 WHOLE HEATLH MOBILE

DEVELOPMENT ENHANCMENTS

IAW paragraphs 5.2.1 and 5.2 - 5.3 of the

PWS.

and other costs required for the successful completion of the tasks IAW PWS paragraph

5.2 and its subparagraphs.

The Contractor shall only invoice upon completion of each one-month sprint and

COR acceptance of the sprint certification package and artifacts

NTE 18 EA $ NTE$

OPTIONAL TASK 1 TOTAL $

CONTRACT TOTAL (INCLUSIVE OF ALL OPTIONS) $

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.

Deliverable:

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.

Deliverable:

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. Develop and maintain Whole Health Application Performance Management Plan

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

Application meets availability requirements of 95 percent.

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