36C10B21R0036.pdf

PAGE 1 OF 96 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

36C10B21R0036 08-23-2021

Lauren Sankar 08-31-2021

9AM EDT

36C10B

Department of Veterans Affairs

Technology Acquisition Center

23 Christopher Way

Eatontown NJ 07724

X

541512

$30 Million

N/A

X

See Delivery Schedule

36C10B

Technology Acquisition Center

Eatontown NJ 07724

30C10A

Technology Acquisition Center

Financial Services Center

PO Box 149971

Austin TX 78714-8971

Mobile Application Testing and Content Writing

See Section B

POCs:

Contract Specialist Lauren Sankar Lauren.Sankar@va.gov

Contracting Officer Den-el Opuszynski Den-el.Opuszynski@va.gov

ARM: 137387

x

Den-el Opuszynski

Contracting Officer mailto:Lauren.Sankar@va.gov mailto:Den-el.Opuszynski@va.gov

36C10B21R0036

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 GOVERNING LAW

B.2 CONTRACT ADMINISTRATION DATA

B.3 PRICE SCHEDULE

B.4 PERFORMANCE WORK STATEMENT

SECTION C - CONTRACT CLAUSES

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

C.2 52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR INFORMATION

SYSTEMS (JUN 2016)

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

STATUTES OR EXECUTIVE ORDERS—COMMERCIAL ITEMS (JAN 2021) (JUL 2020)

(DEVIATION)

(End of Clause) ................................................................... Error! Bookmark not defined.

C.4 FAR 52.217-7 OPTION FOR INCREASED QUANTITY- SEPARATELY PRICED LINE

ITEM (MAR 1989)

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

C. 6 852.212-70 PROVISIONS AND CLAUSES APPLICABLE TO VA ACQUISITION OF

COMMERCIAL ITEMS (APR 2020)

C.7 VAAR 852.219-76 SUBCONTRACTING PLANS MONITORING AND COMPLIANCE

(JUL 2018)

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.204-24 REPRESENTATION REGARDING CERTAIN TELECOMMUNICATIONS

AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT (OCT 2020)

E.3 52.204-26 COVERED TELECOMMUNICATIONS EQUIPMENT OR SERVICES-

REPRESENTATION (OCT 2020)

E.4 52.209-7 INFORMATION REGARDING RESPONSIBILITY MATTERS (OCT 2018)

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

ITEMS (FEB 2021)

E.6 52.216-1 TYPE OF CONTRACT (APR 1984)

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

E.8 BASIS FOR AWARD

E.9 EVALUATION APPROACH

E.10 PROPOSAL SUBMISSION

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, as permitted by FAR 12.212.

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 USC § 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. The Contractor shall deliver to the Government all data first produced under this Contract/Order with unlimited rights as defined by FAR 52.227-14. Claims of patent or copyright infringement brought against the Government as a party shall be defended by the U.S. Department of Justice (DOJ) in accordance with 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 modification (Standard Form 30) and shall only be made 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 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) Den-el Opuszynski

Den-el.opuszynski@va.gov

Department of Veterans Affairs

Technology Acquisition Center

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

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly [ ]

b. Semi-Annually [ ]

c. Other [X] In accordance with the Price Schedule in Section B.

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 Offeror acknowledges receipt of amendments to the Solicitation numbered and dated as follows:

AMENDMENT NO DATE

mailto:Den-el.opuszynski@va.gov

B.4 PRICE SCHEDULE

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

NOTE: In accordance with Federal Acquisition Regulation (FAR) 25.401(a)(1), the subject procurement is exempt from the requirements of the Trade Agreements Act (TAA). Accordingly, Non-TAA compliant items may be quoted for this procurement, and ultimately delivered under any resulting order.

BASE PERIOD

The period of performance: 12 Months

Contract Line

Item Number

(CLIN)

Description Qty Unit Unit Price Total Price

0001 Project Management In Accordance

With (IAW) PWS Sections 5.1 and all of its subparagraphs.

This Firm Fixed Price (FFP) CLIN includes all tasks required for the successful completion of services detailed in PWS section 5.1 and all of its subparagraphs.

12 MO $ $

0001AA Contractor Project Management Plan IAW PWS Section 5.1.1

Due 30 days after contract (DAC) award and updated monthly thereafter.

Electronic submission to: VA PM, COR, CO.

Inspection: destination

Acceptance: destination

1 LO

Not Separately Priced

(NSP)

NSP

0001AB Monthly Progress Reports IAW PWS Section 5.1.2

Due the fifth day of each month throughout the period of performance (PoP).

Electronic submission to: VA

PM, COR, CO.

Inspection: destination Acceptance: destination

1 LO NSP NSP

0001AC Staff Roster IAW PWS Section 6.2.2.

Due one week after contract award

Electronic submission to: VA

PM, COR, CO

Inspection: destination Acceptance: destination

1 LO NSP NSP

0001AD Signed Contractor Rules of Behavior IAW PWS Section

6.2.2.

Due one week after contract award

PM, COR, CO

Inspection: destination

Acceptance: destination

1 LO NSP NSP

0002 Mobile Application software testing and content writing IAW PWS

Sections 5.2 and all of its subparagraphs.

This FFP CLIN includes all tasks required for the successful

12 MO $ $

completion of services detailed in

PWS section 5.2 and all of its subparagraphs.

0002AA Testing Documentation and

Reports IAW PWS Section 5.2.1.

Due one week after testing occurs.

Inspection: destination Acceptance: destination

1 LO NSP NSP

0002AB Weekly Testing Report IAW

PWS Section 5.2.1.

Due on a weekly basis throughout the PoP.

Inspection: destination

Acceptance: destination

1 LO NSP NSP

0002AC Weekly Content Report IAW

PWS Section 5.2.3.

Inspection: destination

Acceptance: destination

1 LO NSP NSP

TOTAL BASE PERIOD $

OPTION PERIOD 1

This option may be exercised by the Government IAW FAR 52.217-9 Option to Extend the Term of the

Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the

Contracting Officer. 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 PWS

Sections 5.1 and all of its completion of services detailed in

PWS section 5.1 and all of its

1001AA Contractor Project Management Plan IAW PWS Section 5.1.1

Due 30 days after option commencement of option period and updated monthly thereafter.

Inspection: destination Acceptance: destination

1 LO NSP NSP

1001AB Monthly Progress Reports IAW

Electronic submission to: VA

PM, COR, CO.

1001AC Staff Roster IAW PWS Section 6.2.2.

Due one week after commencement of option period.

Electronic submission to: VA

PM, COR, CO

Inspection: destination Acceptance: destination

1 LO NSP NSP

1001AD Signed Contractor Rules of Behavior IAW PWS Section

Due one week after commencement of option period.

Electronic submission to: VA

PM, COR, CO

Inspection: destination Acceptance: destination

1 LO NSP NSP

1002 Mobile Application software testing and content writing IAW PWS

PWS section 5.2 and all of its subparagraphs.

1002AA Testing Documentation and

Electronic submission to: VA

PM, COR, CO

Inspection: destination Acceptance: destination

1 LO NSP NSP

1002AB Weekly Testing Report IAW PWS Section 5.2.1.

Inspection: destination Acceptance: destination

1 LO NSP NSP

1002AC Weekly Content Report IAW PWS Section 5.2.3.

Inspection: destination Acceptance: destination

1 LO NSP NSP

TOTAL OPTION PERIOD 1 $

OPTION PERIOD 2

This option may be exercised by the Government IAW FAR 52.217-9 Option to Extend the Term of the

Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the

Contracting Officer. If exercised this option shall commence immediately after expiration of option period 1.

2001 Project Management IAW PWS completion of services detailed in

PWS section 5.1 and all of its

2001AA Contractor Project Management Plan IAW PWS Section 5.1.1

Due 30 days after commencement of option period and updated monthly thereafter.

Inspection: destination

Acceptance: destination

1 LO NSP NSP

2001AB Monthly Progress Reports IAW

PWS Section 5.1.2

2001AC Staff Roster IAW PWS Section

Inspection: destination Acceptance: destination

1 LO NSP NSP

2001AD Signed Contractor Rules of Behavior IAW PWS Section

6.2.2.

Inspection: destination

Acceptance: destination

1 LO NSP NSP

2002 Mobile Application software testing and content writing IAW PWS completion of services detailed in PWS section 5.2 and all of its subparagraphs.

2002AA Testing Documentation and

Electronic submission to: VA

PM, COR, CO

Inspection: destination Acceptance: destination

1 LO NSP NSP

2002AB Weekly Testing Report IAW PWS Section 5.2.1.

Electronic submission to: VA

PM, COR, CO

Inspection: destination Acceptance: destination

1 LO NSP NSP

2002AC Weekly Content Report IAW

Inspection: destination Acceptance: destination

1 LO NSP NSP

TOTAL OPTION PERIOD 2 $

OPTION PERIOD 3

This option may be exercised by the Government IAW FAR 52.217-9 Option to Extend the Term of the

Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the

Contracting Officer. If exercised this option shall commence immediately after expiration of option period 2.

3001 Project Management IAW PWS

3001AA Contractor Project Management

Plan IAW PWS Section 5.1.1

Due 30 days after commencement

Inspection: destination

Acceptance: destination

1 LO NSP NSP

3001AB Monthly Progress Reports IAW

3001AC Staff Roster IAW PWS Section

Electronic submission to: VA

PM, COR, CO

Inspection: destination Acceptance: destination

1 LO NSP NSP

3001AD Signed Contractor Rules of

Inspection: destination Acceptance: destination

1 LO NSP NSP

3002 Mobile Application software testing and content writing IAW PWS

Sections 5.2 and all of its completion of services detailed in

PWS section 5.2 and all of its subparagraphs.

3002AA Testing Documentation and

Reports IAW PWS Section 5.2.1.

Due one week after testing occurs.

Electronic submission to: VA

PM, COR, CO

Inspection: destination Acceptance: destination

1 LO NSP NSP

3002AB Weekly Testing Report IAW PWS Section 5.2.1.

Due on a weekly basis throughout the PoP.

Electronic submission to: VA

PM, COR, CO

Inspection: destination Acceptance: destination

1 LO NSP NSP

3002AC Weekly Content Report IAW

Electronic submission to: VA

PM, COR, CO

Inspection: destination Acceptance: destination

1 LO NSP NSP

TOTAL OPTION PERIOD 3 $

OPTION PERIOD 4

This option may be exercised by the Government IAW FAR 52.217-9 Option to Extend the Term of the

Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the

Contracting Officer. If exercised this option shall commence immediately after expiration of option period 3.

4001 Project Management IAW PWS subparagraphs.

4001AA Contractor Project Management

Plan IAW PWS Section 5.1.1

Due 30 days after commencement

Inspection: destination Acceptance: destination

1 LO NSP NSP

4001AB Monthly Progress Reports IAW

4001AC Staff Roster IAW PWS Section 6.2.2.

Due one week after commencement of option period.

Electronic submission to: VA

PM, COR, CO

Inspection: destination Acceptance: destination

1 LO NSP NSP

4001AD Signed Contractor Rules of

Inspection: destination Acceptance: destination

1 LO NSP NSP

4002 Mobile Application software testing and content writing IAW PWS completion of services detailed in

PWS section 5.2 and all of its subparagraphs.

4002AA Testing Documentation and

Inspection: destination Acceptance: destination

1 LO NSP NSP

4002AB Weekly Testing Report IAW

PWS Section 5.2.1.

Inspection: destination

Acceptance: destination

1 LO NSP NSP

4002AC Weekly Content Report IAW

PWS Section 5.2.3.

Inspection: destination

Acceptance: destination

1 LO NSP NSP

TOTAL OPTION PERIOD 4 $

Optional Task 1

This Optional Task may be exercised IAW FAR 52.217-7 “Option for Increased Quantity- Separately Priced Line Items”

(MAR 1989) and may be exercised multiple times, at any time, and from time to time at the Government’s discretion at any time during the Base Period and/or Option Periods not to exceed the maximum quantity of 100 times and not to exceed the overall Period of Performance of 60 months.

Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer.

Contract Line Item

Number (CLIN) Description QTY Unit Unit Cost Total Price

0005 Additional Mobile Application Testing

IAW PWS Sections 5.3.1

100 EA $ $

This FFP CLIN includes all tasks required for the successful completion of services detailed in PWS section 5.3.1.

The PoP for this Optional Task is one month from optional task commencement.

This Optional Task may be exercised multiple times, at any time, and from time to time at the Government’s discretion at any time during the Base Period and/or

Option Periods up to the not to exceed maximum quantity of 100 times and not to exceed the overall Period of Performance of 60 months.

0005AA Testing Documentation and Reports IAW PWS Section 5.3.1.

Due one week after testing occurs.

COR, CO

Inspection: destination Acceptance: destination

1 LO NSP NSP

0005AB Weekly Testing Report IAW PWS Section 5.3.1.

Due on a weekly basis throughout the PoP.

Electronic submission to: VA PM, COR, CO

Inspection: destination Acceptance: destination

1 LO NSP NSP

Total Optional Task 1 $

Optional Task 2

This Optional Task may be exercised IAW FAR 52.217-7 “Option for Increased Quantity- Separately Priced Line Items”

(MAR 1989) and may be exercised multiple times, at any time, and from time to time at the Government’s discretion at any time during the Base Period and/or Option Periods not to exceed the maximum quantity of 100 times and not to exceed the overall Period of Performance of 60 months.

Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer.

Contract Line Item Number (CLIN)

Description QTY Unit Unit Cost Total Price

0006 Additional Mobile Application User

Experience Testing IAW PWS Sections 5.3.2

100 EA $ $

detailed in PWS section 5.3.2.

The PoP for this Optional Task is one month from commencement of optional task.

to time at the Government’s discretion at any time during the Base Period and/or

Option Periods not to exceed maximum quantity of 100 times and not to exceed the overall Period of Performance of 60 months.

Total Optional Task 2 $

Optional Task 3

This Optional Task may be exercised IAW FAR 52.217-7 “Option for Increased Quantity- Separately Priced Line Items”

(MAR 1989and may be exercised multiple times, at any time, and from time to time at the Government’s discretion at any time during the Base Period and/or Option Periods not to exceed the maximum quantity of 100 times and not to exceed the overall Period of Performance of 60 months.

Contract Line Item

Number (CLIN) Description QTY Unit Unit Cost Total Price

0007 Additional Content for Mobile Applications

IAW PWS Sections 5.3.3.

detailed in PWS section 5.3.3.

The pop for this Optional Task is one month from commencement of optional task.

to time at the Government’s discretion at any time during the Base Period and/or

Option Periods not to exceed maximum quantity of 100 times and not to exceed the overall Period of Performance of 60 months

100 EA $ $

0007AA Weekly content report IAW PWS Section

5.3.3.

Due on a weekly basis throughout the

PoP.

Electronic submission to: VA PM, COR, CO.

Total Optional Task 3 $

Total Base, Option Periods 1-4 and Optional Tasks 1-3 $

B.5 PERFORMANCE WORK STATEMENT

1.0 BACKGROUND

The National Center for Posttraumatic Stress Disorder (NCPTSD), Dissemination and Training Division, part of the U.S. Department of Veterans Affairs (VA), is responsible for creating training and educational products to support evidence-based care of Veterans with Posttraumatic Stress Disorder (PTSD) and related problems. PTSD is very common among Veterans and has a significant impact on Veterans’ quality of life. Most Veterans with PTSD do not access evidence-based treatments for PTSD, and many

Veterans are either unable or choose not to access available mental health services of any kind. Lack of available services, distance from clinics, and stigma associated with mental health care are just a few of the barriers to providing care for Veterans and those living with a Veteran with PTSD. NCPTSD has developed mobile phone applications to overcome these and other barriers to care. The apps are designed to assist Veterans and their family members with understanding PTSD and related problems, tracking their improvement over time, obtaining support and resources, and managing symptoms using a variety of brief tools.

NCPTSD has developed a variety of mobile applications in the past nine years, including, most notably, the multi-award winning PTSD Coach (Winner of the Advancements in Accessibility Award from the

Federal Communications Commission 2011 and Winner of the President’s Innovation Award from the

American Telemedicine Association 2012). NCPTSD currently maintains a portfolio of 33 native, publicly available apps (e.g., PTSD Coach, CBT-i Coach, Mindfulness Coach, PE Coach, Stay Quit

Coach), that have been downloaded from the App Store and Play Store by over three million Veterans and others. The portfolio currently consists of 20 native (i.e. Swift and Objective-C) iOS apps and 13 native

(i.e. Java) Android apps. Each mobile app aims to address specific implementation challenges faced by

Veterans and their family members in receiving education, training, and treatment.

The Dissemination and Training Division of NCPTSD has also been charged with 1) ensuring that

NCPTSD mobile apps are capable of supporting scientific research and 2) capable of responding to the needs of Veterans, VA providers, and other stakeholders. To meet this charge, NCPTSD has a multi-phase coordinated research program to study the usability, efficacy, and implementation of these applications and works directly with Mental Health Services in VA’s Central Office to ensure that products are aligned with the mission to enhance and optimize mental health care for Veterans.

This contract action is part of a set of activities designed to maintain, redesign, test, and upgrade existing mobile apps previously built for NCPTSD, in order to provide reliable, high-quality mental health service to Veterans, their families, health care providers, and others. The specific work assignments will be determined throughout the period of performance, as Apple’s successive updates to iOS and Google’s successive updates to Android introduce new bugs and performance problems to the apps over the year, and as NCPTSD staff consider and develop possible new features.

2.0 APPLICABLE DOCUMENTS

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

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

2. “Federal Information Security Modernization Act of 2014”

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

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

Information Systems,” February 2004

5. FIPS Pub 200, “Minimum Security Requirements for Federal Information and Information Systems,” March 2006

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

August 2013

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

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

9. Public Law 109-461, Veterans Benefits, Health Care, and Information Technology Act of 2006, Title IX, Information Security Matters

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

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

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

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

14. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and

Guidelines,” January 18, 2017

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

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

(CHAMPUS)”

17. NIST SP 800-66 Rev. 1, “An Introductory Resource Guide for Implementing the Health

Insurance Portability and Accountability Act (HIPAA) Security Rule,” October 2008

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

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

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

VA Handbook 6500, “Risk Management Framework for VA Information Systems VA

Information Security Program,” February 24, 2021

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

(SPI),” March 12, 2019

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

Lifecycle,” March 22, 2010

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

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

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

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

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

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

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

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

Assessment,” October 15, 2014

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

Assessment,” July 30, 2015 https://www.va.gov/vapubs/index.cfm https://www.va.gov/vapubs/index.cfm 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

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

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

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

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

35. NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and

Organizations: A System Life Cycle Approach for Security and Privacy,” December 2018

36. NIST SP 800-53 Rev. 5, “Security and Privacy Controls for Federal Information Systems and Organizations,” September 23, 2020 (includes updates as of 12/10/2020)

37. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,”

October 26, 2015

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

March 24, 2014

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

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

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

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

Implementation Guidance, December 2, 2011, (NOTE: Part A of the FICAM Roadmap and

Implementation Guidance, v2.0, was replaced in 2015 with an updated Architecture

(https://arch.idmanagement.gov/#what-is-the-ficam-architecture)

43. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV)

Credentials in Facility Access,“ June 2018

44. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, “Digital Identity Guidelines,” updated March 02, 2020

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

46. NIST SP 800-164, “Guidelines on Hardware-Rooted Security in Mobile Devices (Draft),”

October 2012

47. Draft National Institute of Standards and Technology Interagency Report (NISTIR) 7981, “Mobile, PIV, and Authentication,” March 2014

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

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

50. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy

Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

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

52. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC)

Initiative,” September 12, 2019

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

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

110–140), December 19, 2007

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

56. Executive Order 13834, “Efficient Federal Operations,” dated May 17, 2018 https://arch.idmanagement.gov/#what-is-the-ficam-architecture https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896 https://www.cisa.gov/publication/tic-30-core-guidance-documents

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

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

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

60. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access,”

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

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

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

63. VA Memorandum “Proper Use of Email and Other Messaging Services,” January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

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

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

66. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),” November 19, 2020

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

68. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018

3.0 SCOPE OF WORK

The Contractor shall provide native mobile app (iOS and Android) testing and content writing for mobile apps and public health education materials to support NCPTSD mobile apps for PTSD. This includes include functional testing, user experience testing, and ensuring the apps are clinically sound and current.

The Contractor shall also generate clinical content for the mobile apps.

Contractor personnel directly involved with application testing and clinical content services shall have completed a doctoral degree in clinical psychology from an American Psychological Association -accredited program, have clinical experience in working with Veterans with PTSD, conducting behavioral research, have expertise in science and evidence-based recommendations for the treatment of PTSD, and clinical experience in delivering mobile interventions to Veterans with PTSD.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The PoP shall be 12 months from date of award, with four 12-month option periods and three optional tasks.

Work at the Government site shall not take place on Federal holidays or weekends unless directed by the

Contracting Officer (CO). If required, the CO may designate the Contractor to work during holidays and weekends.

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

Under current definitions, four are set by date:

New Year's Day January 1

Juneteenth June 19

Independence Day July 4

Veterans Day November 11

Christmas Day December 25 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

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

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

Martin Luther King's Birthday Third Monday in January

Washington's Birthday Third Monday in February Memorial Day Last Monday in May

Labor Day First Monday in September

Columbus Day Second Monday in October

Thanksgiving Fourth Thursday in November

4.2 PLACE OF PERFORMANCE

Tasks under this PWS shall be performed at Contractor facilities. The Contractor shall identify the

Contractor’s place of performance in their proposal submission.

4.3 TRAVEL

The Government anticipates travel under this effort to perform the tasks associated with the effort, as well as to attend program-related meetings or conferences throughout the period of performance. Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government. The Contractor shall be required to attend meetings in-person quarterly, in San

Francisco, CA. The total estimated number of trips in support of the program related meetings for this effort is four per year. Anticipated location is San Francisco, CA, estimated at one day in duration for one person.

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

Deliverable:

A. Contractor Project Management Plan

5.1.2 REPORTING REQUIREMENTS

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

Word and Project formats. The report shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding Month.

The Monthly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the

Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The report shall also include an itemized list of all Information and Communication Technology (ICT) deliverables and their current Section 508 conformance status. The Contractor shall monitor performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

The Contractor shall attend weekly meetings to brief VA on the status of each task and deliverable defined within this PWS and to review ongoing needs across the mobile app’s portfolio. The Contractor briefing shall include a detailed review of the current work breakdown structure and Gantt chart; the projected schedule; risk mitigation status; and the Contractor’s planned actions for recovering from any schedule slippage.

A. Monthly Progress Report

5.1.3 TECHNICAL KICKOFF MEETING

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

Contractor shall present, for review and approval by the Government, the details of the intended approach, work plan, and overall project management approach. The Contractor shall specify dates, locations (can be virtual), 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), Contractor

Officer’s Representative (COR), and VA PM.

5.2 MOBILE APPLICATION SOFTWARE TESTING AND CONTENT

WRITING

The Contractor shall provide native mobile app testing, user experience testing, and content writing for mobile apps and public health education materials to support NCPTSD mobile apps for PTSD.

5.2.1 MOBILE APPLICATION TESTING

The Contractor shall provide testing of NCPTSD mobile apps for PTSD to improve user experience and provide clinical judgement to ensure safety, suggest additional content to improve the apps and keep the content up to date. The testing will be performed on a per-project basis at NCPTSD’s discretion, with testing ranging from focused testing of a specific app section or feature to comprehensive user experience testing or complete testing of a mobile app. NCPTSD anticipates the Contractor shall test one mobile app at a given time, but may be required to test up to two apps concurrently during a 30 day period.

The Contractor shall coordinate with NCPTSD for testing timelines for the mobile applications. The

Contractor shall report on all active and planned mobile app testing projects in the Monthly Progress Report and during weekly mobile app briefings.

Quality control of delivered mobile app testing shall be led and performed by the Contractor. All readily available specifications and documentation will be provided to the Contractor for use in testing, but the

Contractor should be able to implement these tasks without any further documentation. The Contractor shall download required mobile apps to be tested from VA’s repository, currently Vertical. An issue tracking system administered by NCPTSD, currently GitHub, shall be used to track quality control issues and monitor progress. The Contractor shall test NCPTSD native mobile apps for PTSD.

Testing shall include:

1. Testing of mobile apps on multiple Android and iOS devices to ensure the app works as intended and displays correctly on the device screen. For device testing, the Contractor shall test the mobile apps using actual devices (i.e., not simulators), particularly devices that are most widely used in the general population, that include multiple Android screen sizes (both phones and tablets) and multiple iOS screen sizes (both phones and tablets). At a minimum, the Contractor shall test using two Android phone devices that have different screen sizes and one Android tablet device and two iOS phone devices that have different screen sizes and one iOS tablet device.

2. Ensuring mobile app content and features match NCPTSD technical specifications. The

Contractor shall be responsible for comparing technical specifications against their implementation in a mobile app, ensuring that a) all content matches between the specifications and the app and b) the app is resilient to complex user interactions without crashing, stalling, or losing data.

3. Reviewing material for consistency with current evidence-based PTSD treatment guidelines (i.e., https://www.healthquality.va.gov/guidelines/MH/ptsd/) and the most up-to-date scientific literature on PTSD education, treatment, and clinical care.

4. Ensuring clinical safety (i.e., appropriateness to the clinical care of Veterans with PTSD) and confidentiality.

5. Ensuring consistency with Apple iOS human interface guidelines, Android design guidelines, and recently released NCPTSD mobile apps.

6. Optimizing user experience, which at a minimum shall include reviewing wireframes and app sequences to identify potential dead-ends (i.e., views that cannot be easily navigated out of, user-entered information that cannot be changed or edited, etc.) or ways of interacting with the apps that are likely to be confusing for different types of Veterans using the app, but particularly for

PTSD-related challenges; offering suggestions for simplifying user interaction elements and alternative flows to improve usability among Veterans with PTSD; identifying additional evidence-informed clinical content that could assist Veterans in making better use of the apps.

7. Testing for Section 508 accessibility compliance.

8. Conducting comprehensive testing of research versions of apps to be consistent with best practices in the scientific PTSD literature, by visiting and recording all screens within the app and checking that data transmitted from research versions of apps (i.e., timestamps, buttons tapped, user-entered data) match testing records (i.e., data transmitted in JavaScript Object Notation (JSON) format should match testing records of which app screens were visited, dates and times for when each screen was visited, and any data entered by the tester while testing the app).

9. Veteran-focused user experience testing. Testing shall include focused (i.e., testing one section or feature of an app) and general (i.e., testing every feature and section of the app) testing of mobile apps using specific user personas (e.g., repeat survey-taker, skeptical user, long-term user, etc.). The Contractor shall also conduct user experience interviews with Veterans with PTSD, employing established user experience (UX) research principles and consistent with evidence-based interviewing guidelines for working with clinical populations. The Contractor shall incorporate results of user experience interviews into recommendations for cost-effective design changes that could improve users’ experiences with the app.

For device testing, the contractor shall use actual devices that include multiple Android screen sizes and tablets and multiple iOS screen sizes and tablets. The contractor shall be responsible for comparing technical specifications against their implementation in a mobile app, ensuring that all content matches between the specifications and the app and the app is resilient to complex user interactions without crashing, stalling, or losing data. The contractor shall compare JSON generated from research-enabled versions of mobile apps with expected values (e.g., screen names, test scores, etc.). The amount and type of testing will vary widely on a per-project basis at NCPTSD’s discretion, with testing ranging from focused testing of a specific app section or feature to comprehensive user experience testing or complete testing of a mobile app. The contractor shall also be responsible for developing a timeline for testing across apps and coordinating all testing timelines with NCPTSD.

The Contractor shall provide a Weekly Testing Report that summarizes the testing performed during the week and the progress made on the issues reported in the issue tracking system. In addition, any recommended user experience improvements and suggested clinical content shall be included in the

Weekly Testing Report.

Final deliverables of each testing project shall include the delivery of all testing documentation and reports as described above.

A. Testing Documentation and Reports

B. Weekly Testing Report

5.2.2 MOBILE APPLICATION USER EXPERIENCE TESTING

The Contractor shall perform Mobile Applications testing to include focused and general testing of mobile apps using specific user personas (e.g., repeat survey-taker, skeptical user, long-term user, etc.).

The contractor shall also conduct user experience interviews with target users, employing established UX research principles. The contractor shall incorporate results of user experience interviews into recommendations for cost-effective design changes that could improve users’ experiences with the app.

The testing will be performed on a per-project basis at NCPTSD’s discretion and anticipates the

Contractor shall test one mobile app at a given time but may be required to test up to two apps concurrently during a 30-day period.

5.2.3 CONTENT FOR MOBILE APPLICATIONS

The Contractor shall provide content writing support services for mobile apps and public health education materials to support NCPTSD mobile apps for PTSD, based on the best available scientific evidence, current VA norms and standards for the clinical care of Veterans with PTSD, expert knowledge of VA care for PTSD, current clinical guidelines for the treatment of PTSD, and familiarity with common terms and expressions used by Veterans. NCPTSD mobile apps for PTSD need to be kept up to date with, for example, the newest treatment, educational materials, and available clinical science. The Contractor shall be responsible for writing up-to date content to be used in publicly released mobile apps for mental health and supporting handouts and patient education materials.

The contractor shall write public health education materials capable of being included in NCPTSD mobile apps, such as brief psychoeducational topics specific to PTSD treatment and recovery (see PTSD Coach, PTSD Family Coach apps for examples). The contractor shall provide written outlines and wireframes for detailed tools and other app features requested by NCPTSD. The contractor shall create flyers and other web-based promotional materials to support appropriate implementation of VA mobile apps across

VA treatment settings. The contractor shall be required to demonstrate familiarity with the best available scientific evidence for treatment of PTSD while also writing content that can be quickly and easily read and is optimized for delivery on a mobile device or tablet. The contractor shall be able to write content that is accessible to the widest possible range of reading levels, with brief content that is accessible to reading levels of sixth grade and below and more detailed content accessible to those with slightly higher reading levels. The contractor shall be responsible for writing content to be used in publicly released mobile applications for mental health and supporting handouts and patient education materials.

Quality control of delivered mobile app testing shall be led and performed by the Contractor. All readily available specifications and documentation will be provided to the Contractor for use in testing, but the

Contractor should be able to implement these deliverables without any further documentation. An issue tracking system administered by NCPTSD shall be used to track quality control issues and monitor progress. Use of NCPTSD GitHub is required for source code and audio/visual asset delivery and issue tracking.

The content will be created on a per-project basis at NCPTSD’s discretion and anticipates the Contractor shall create 20-40 brief topics ranging from 100-250 words each during a 30-day period. This task is anticipated to take approximately 960 hours in the base year and approximately 960 hours in each option period. The Contractor shall report on all active and planned mobile app testing projects in the Monthly Progress Report and during weekly mobile app briefings.

A. Weekly Content Report

5.3 OPTIONAL TASKS

5.3.1 ADDITIONAL MOBILE APPLICATION TESTING (OPTIONAL TASK 1)

VA may exercise this optional task for additional mobile application testing with a performance period of up to one month. This optional task may be exercised multiple times, at any time, and from time to time at the Government’s discretion at any time during the Base Period and/or Option Periods not to exceed the maximum quantity of 100 times and not to exceed the overall Period of Performance of 60 months.

The Contractor shall provide testing of NCPTSD mobile apps for PTSD to improve user experience and provide clinical judgement to ensure safety, suggest additional content to improve the apps and keep the content up to date. The testing will be performed on a per-project basis at NCPTSD’s discretion, with testing ranging from focused testing of a specific app section or feature to comprehensive user experience testing or complete testing of a mobile app. NCPTSD anticipates the Contractor shall test one mobile app at a given time, but may be required to test up to two apps concurrently during a 30 day period.

The Contractor shall coordinate with NCPTSD for testing timelines for the mobile applications. The

Contractor shall…