36C10B25Q0041 Final.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. UEI: EFT:

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. NOV 2021)

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

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

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

36C10B25Q0041 12-17-2024

Dominic Tanglao 848-353-377-5213 1-03-2025

15:00 EST

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

X

541511

N/A

X

See Delivery Schedule

Financial Services Center PO Box 149971 Austin TX 78714-8971

See CONTINUATION Page

This procurement is sole source w/VLogic Systems Inc.

The period of performance shall consist of:

1/07/2025-01/06/2026 w/4 12-month option periods

Points of Contacts:

CO: Matthew Newell at matthew.newell@va.gov CS: Dominic Tanglao at dominic.tanglao@va.gov

See CONTINUATION Page

Contracting Officer

Matthew Newell

36C10B25Q0041

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 GOVERNING LAW

B.2 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT

SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT:

B.3 CONTRACT ADMINISTRATION DATA

B.4 PRICE SCHEDULE

1.0 BACKGROUND

2.0 APPLICABLE DOCUMENTS

3.0 SCOPE OF WORK

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

4.2 PLACE OF PERFORMANCE

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

5.1.2 REPORTING REQUIREMENTS

5.1.3 TECHNICAL KICKOFF MEETING

5.2 DEVELOPMENT

5.2.1 AboutFace Engagement Intervention DEVELOPMENT

5.2.2 Automated Assessment

5.2.3 USER ACCEPTANCE TESTING

5.2.4 SYSTEM HOSTING

5.3 VA CERTIFIED PEER SUPPORT SPECIALISTS

5.3.1 Training peer support specialists to support participants with the AboutFace Engagement Intervention

5.4 PILOT STUDY

5.5 FINAL REPORT

5.6 OPTION PERIOD ONE

5.7 OPTION PERIOD TWO

5.8 OPTION PERIOD THREE

5.9 OPTION PERIOD FOUR

5.10 OPTIONAL CLIN

6.0 GENERAL REQUIREMENTS

6.1 SECURITY AND PRIVACY REQUIREMENTS

6.1.1 POSITION/TASK RISK DESIGNATION LEVEL(S)

6.2 METHOD AND DISTRIBUTION OF DELIVERABLES

6.3 PERFORMANCE METRICS

6.4 FACILITY/RESOURCE PROVISIONS

6.5 GOVERNMENT FURNISHED PROPERTY

36C10B25Q0041

6.6 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL

INFORMATION AND COMMUNICATION TECHNOLOGY (ICT) PROCUREMENTS

(SECTION 508)

6.6.1 SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

STANDARDS

6.6.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY

6.6.3 ACCEPTANCE AND ACCEPTANCE TESTING

6.7 INFORMATION SECURITY CONSIDERATIONS:

6.8 RECORDS MANAGEMENT

6.8.1 RECORDS MANAGEMENT OBLIGATIONS

7.0 POINTS OF CONTACT

ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED

ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY

LANGUAGE

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 (AUG 2020)

C.4 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

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

OF COMMERCIAL ITEMS. ............................................. Error! Bookmark not defined.

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-26 COVERED TELECOMMUNICATIONS EQUIPMENT OR SERVICES

REORESENTATION (DEC 2019)

E.3 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—

COMMERCIAL ITEMS (JUN 2020)

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

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

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

RESOLUTION (OCT 2018)

36C10B25Q0041-Building Records File Management

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 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT

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 Contract/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/or Technical Support.

a) If the Government desires to continue software maintenance and support beyond the period of performance identified in this Contract/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 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 or Product Description. However, prolonged delay (exceeding two business days) in resolving software problems will be noted in the Government’s various past performance records on the Contractor (e.g., www.cpars.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/Order at no cost.

B.3 CONTRACT ADMINISTRATION DATA

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

a. CONTRACTOR: VLogic Systems, Inc.

150 Baker Avenue Extension – Suite 110 Concord, MA 01742 USA

(M) +1 (617) 823-7121 www.vlogicsystems.com

b. GOVERNMENT: Contracting Officer

Technology Acquisition Center

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 IAW B.4 Price Schedule]

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.

B.4 PRICE SCHEDULE

Inspection: Destination Acceptance: Destination

Free on Board (FOB): Destination

Option Period One

This 12-month option period may be exercised in accordance with 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 at the end of the base period. The Period of Performance is January 7, 2026–January 6, 2027 unless otherwise noted in the Description block in the table below.

Item No.

Product Description QTY Unit Unit Price Item No.

Base Period

The period of performance for this effort shall be 12 months in accordance with (IAW) the Product Description (PD). The Period of Performance (PoP) is January 7, 2025–January 6, 2026

Item No.

Product Description QTY Unit Unit Price Total

Price

Maintenance of Space Database and Architectural Drawings

Provide 24/7 Technical Support

Update Drawings and Database

(See Product Description)

1 YR $ $

Provide FedRAMP authorized software as-a-service for Space Management Modules: As-builts, CAI, Space, and System Administration

1 YR $ $

Provide on-line training-Unlimited number of attendees

Base Period Total $

Provide 24/7 Technical Support

Update Drawings and Database

(See Product Description)

1 YR $ $

Provide FedRAMP authorized software as-a-service for Space Management Modules: As-

Provide on-line training-Unlimited number of attendees

Option Period One Total $

Option Period Two

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 at the end of the previous option period. The Period of Performance is January 7, 2027–January 6, 2028 unless otherwise noted in the Description block in the table below.

Product Description QTY Unit Unit Price Item No.

Provide 24/7 Technical Support

Update Drawings and Database

(See Product Description)

Provide FedRAMP authorized software as-a-service for Space Management Modules: As-

Provide on-line training-Unlimited number of attendees

Option Period Two Total $

Option Period Three

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 at the end of the previous option period. The Period of Performance is January 7, 2028–January 6, 2029 unless otherwise noted

Provide 24/7 Technical Support

Update Drawings and Database

(See Product Description)

1 YR $ $

Provide FedRAMP authorized software as-a-service for Space Management Modules: As-

Provide on-line training-Unlimited number of attendees

Option Period Three Total $

Option Period Four

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 at the end of the previous option period. The Period of Performance is January 7, 2029–January 6, 2030 unless otherwise noted

Provide 24/7 Technical Support

Update Drawings and Database

(See Product Description)

1 YR $ $

Provide FedRAMP authorized software as-a-service for Space Management Modules: As-builts, CAI, Space, and System Administration.

1 YR $ $

Provide on-line training-Unlimited number of attendees

1 YR $ $

Option Period Four Total $

Base and Options Total $

B.5 PRODUCT DESCRIPTION

DEPARTMENT OF VETERANS AFFAIRS

Veterans’ Health Administration

PRODUCT DESCRIPTION (PD) TEMPLATE

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology

STL OI&T

Building Records & File Management

Date: 20241108

VA-25-00009618

1.0 PRODUCT REQUIREMENTS

VASTLHCS has a requirement for Building Records and Files Management to maintain accuracy of current building records/files and make the records/files available to staff through a web portal. VASTLHCS requires a Contractor to provide a full range of professional and software services to:

Archive of all current and past records, files, and related data Field verify and maintain 2D AutoCAD record files of all buildings Field verify and maintain Revit 3D models of all buildings Provide drafting assistance Field verify, provide drafting assistance, and coordinate building space assignments Maintain detailed records of building space assignments responsive to the

VA’s Capital Assets Inventory (CAI) process and leases Provide access to record files through a web-based server Assess current state and create CAD/BIM Guidelines utilizing the VA TIL as a guide.

Attain and maintain proper FedRAMP certification levels and any required

Authority to Operate

2.0 APPLICABLE DOCUMENTS

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

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

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

Standards,” July 1, 2003

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

Security Program,” September 20, 2012

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

5. VA Handbook 6500.2, “Management of Breaches Involving Sensitive

Personal Information (SPI)”, July 28, 2016

6. VA Handbook 6500.6, “Contract Security,” March 12, 2300010

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

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

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

Privacy Impact Assessment,” October 15, 2014

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

Privacy Impact Assessment,” July 30, 2015

11. VA Directive 6300, Records and Information Management, February 26,

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

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

Information Systems and Organizations, January 22, 2015

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

15. OMB Memorandum M-07-16, Safeguarding Against and Responding to the

Breach of Personally Identifiable Information, May 22, 2007

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

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

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

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

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

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

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

22. 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 all supervision, coordination, staffing, software, licenses, website access, training, redundancy and other related services as necessary to provide and maintain vastlhcs building records and files and make them readily accessible to va staff through the contractor’s website. the contractor shall perform all these services as defined by this sow and by the cor or other co designated representative. the services shall be provided to support all divisions, va clinics and administrative facilities..

4.0 GENERAL REQUIREMENTS

4.1 VA TECHNICAL REFERENCE MODEL

The Contractor shall support the VA enterprise management framework. In association with the framework, the Contractor shall comply with OIT Technical Reference Model (VA TRM). The VA TRM is one component within the overall Enterprise Architecture (EA) that establishes a common vocabulary and structure for describing the information technology used to develop, operate, and maintain enterprise applications. Moreover, the VA TRM, which includes the Standards Profile and Product List, serves as a technology roadmap and tool for supporting OIT. Architecture & Engineering Services (AES) has overall responsibility for the VA TRM.

4.2 INTERNET PROTOCOL VERSION 6 (IPV6)

The Contractor solution shall support Internet Protocol Version 6 (IPv6) based upon the memo issued by the Office of Management and Budget (OMB) on November 19, 2020 (https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). IPv6 technology, in accordance with the USGv6 Program (https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1), NIST Special Publication (SP) 500-267B Revision 1 “USGv6 Profile” (https://doi.org/10.6028/NIST.SP.500-267Br1), and NIST SP 800-119 “Guidelines for the Secure Deployment of IPv6” (https://doi.org/10.6028/NIST.SP.800-119), compliance shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices shall support native IPv6 and dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g.

web, email, DNS, ISP services, etc.) shall support native IPv6 and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall communicate using native IPv6 and dual stack (IPv6 / IPv4) operations.

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 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 Contractor shall monitor performance against the CPMP and report any deviations and communicate with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

Deliverable:

A. Contractor Project Management Plan

5.1.2 REPORTING REQUIREMENTS

The Contractor shall attend weekly project meetings and provide verbal reports on progress. The Contractor shall also provide brief weekly status updates via a written Weekly Status Report that indicates the status of the project, including the work breakdown structure; the projected schedule; and the Contractor’s recommendations for recovering from any schedule slippage. Upon deployment of the software solutions to the Contractor-hosted production environment, the Weekly Status Report shall include the recruitment and enrollment numbers once the pilot study begins.

A. Weekly 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 project schedule. The Contractor shall specify dates, set up the call, develop the agenda, and meeting minutes. The Contractor shall invite the Contracting Officer (CO), Contract Specialist (CS), COR, and the VA PM.

Deliverable:

A. Kickoff Agenda B. Kickoff Meeting Minutes

5.2 DEVELOPMENT

5.2.1 AboutFace Engagement Intervention DEVELOPMENT

The Contractor shall develop a web based AboutFace Engagement Intervention using videos from AboutFace and text provided by the National Center for PTSD which includes 6-8 modules, the outline to be included as Appendix A. Each module will address a specific topic (e.g., symptoms, effects on family, stigma, barriers to care, treatment, recovery) and will include some brief text followed by 2 videos.

The Contractor shall provide input on technical and information security aspects of the platform so that the NCPTSD can prepare the Institutional Review Board (IRB) application in support of the AboutFace pilot study. The Contractor shall provide all technical information needed for the IRB application within one month after contract award.

The Contractor shall conduct requirements analysis, configuration management, software design, development, testing and deployment of the software needed. The

Contractor shall work directly with NCPTSD to refine the requirements and develop solutions that meet the requirements in this PWS.

The Contractor shall plan, schedule, and conduct requirement review meetings with VA stakeholders to analyze, refine, and translate the requirements specified in this PWS into a user storyboard including screen mockups depicting every representative screen requested by NCPTSD, and acceptance criteria. The Contractor shall be responsible for documenting and maintaining the user storyboard and acceptance criteria. The Contractor shall ensure that the VA PM has access to the most current version of the user story and acceptance criteria.

The Contractor shall host and maintain a User Acceptance Testing (UAT) environment with the latest code for VA to test and demonstrate the functionality between versions.

This environment shall remain operational throughout the software development phase.

The final Contractor tested software code shall not have any known defects. The Contractor shall deliver a Final Test Report summarizing the testing that was performed, including both functional and scalability testing.

The Contractor shall host the final tested AboutFace Engagement Intervention.

Deliverables:

A. AboutFace Engagement Intervention, 508 compliant, Software Build

5.2.2 Automated Assessment

The Contractor shall create a 508 compliant platform for the assessment questionnaires on the same platform as the AboutFace intervention. The contractor will automate the questionnaires that are provided. Assessment questionnaires are required for recruiting and screening, as well as to determine outcomes. A list of assessment measures is included as Appendix B. Tracking of conversations with peer support specialists and of whether participants sought out additional resources that were provided (i.e. clicked links for more information) are also required.

1. Security

a. The Contractor’s solution shall meet all VA system security requirements identified within this PWS. The studies will collect and store Veterans’ Personally Identifiable Information (PII) and Protected Health Information (PHI) outside of the VA network. VA will not share any PII or PHI with the contractor. The contractor will make available on a secure server participant names and contact information. A business associate agreement will be utilized.

b. Collected PHI shall be stored within a Health Insurance Portability and Accountability Act (HIPAA) and Health Information Trust Alliance compliant server that can only be accessed by select staff members with limited and controlled access.

c. The clinical data collected as part of the research study (to be reviewed by the IRB) shall be connected to a non-identifiable unique participant username/ID only, which is assigned by the awardee.

A. AboutFace Assessment build on 508 compliant platform, Software Build

5.2.3 USER ACCEPTANCE TESTING

The Contractor shall facilitate VA UAT. Upon successful implementation and Contractor testing of the requirements specified in Appendix A, the Contractor shall deploy the completed software solutions to a Contractor-hosted UAT environment. The Contractor shall develop test scenarios, test cases, and test scripts necessary to test the functional requirements as specified within this PWS. The Contractor shall provide and input any sample data required by the systems in order to complete the testing of the functional requirements. The Contractor shall track, resolve, and retest all defects found during UAT and provide updated Software Source Code, Compiled Code, and Software Builds for the Pilot AboutFace Study.

Deliverable:

A. UAT Test Scenarios, Test Cases, and Test Scripts B. Updates to Pilot Study Software Build

5.2.4 SYSTEM HOSTING

Upon completion of VA UAT, the Contractor shall deploy the software solutions to the Contractor-hosted production environment so that the assessment questionnaires and AboutFace Engagement Intervention is available to users of the website who enroll in the study.

The system shall be operational 24 hours a day, seven days a week. The system shall be available at least 99 percent of the scheduled operational time, excluding scheduled maintenance outages. The Contractor shall schedule system maintenance outages between 2 a.m. and 5 a.m. Eastern Standard Time (EST). Scheduled outages shall not occur more than once per week and shall be set up at least seven days in advance for maintenance and/or system upgrades to the greatest extent practical unless deemed emergent due to system compromise or imminent failure. The Contractor shall inform the VA PM and COR of any downtimes for planned or unplanned maintenance to include technical refreshes, upgrades, patches, or security updates.

The Contractor shall deliver a monthly System Hosting Report. The report shall summarize any planned or unplanned outages that occurred during the reporting period and any planned outages scheduled for the following reporting period. An explanation shall be provided for any unplanned outage that occurred during the reporting period, indicating the root cause of the outage and the steps that were or are being taken to correct the problem and prevent its reoccurrence.

5.2.4.1 Text Edits

Based on feedback from study participants, it may become necessary to make edits to the written content in the intervention. If exercised, the contractor shall replace up to 50% of the text in the intervention. NCPTSD will supply the revised text.

5.2.4.2 Programming Changes

Based on feedback from study participants, there may need to be substantive changes to the intervention to improve user experience. If exercised, the contractor shall implement programming changes to revise the intervention structure by up to 25% by, for example, changing the order of the modules.

5.2.4.3 Video Replacement

Based on feedback from study participants it may become necessary to replace selected videos in the intervention. If exercised, the contractor shall remove videos from the intervention, replacing them with a different video. NCPTSD will decide on which videos will be removed and will supply the new video.

A. System Hosting Report

5.2.5 SOFTWARE MAINTENANCE

The Contractor shall resolve and retest any defects found while the software applications are in production. The Contractor shall document and track all defects to closure. The Contractor shall provide a Monthly Defect Report describing all defects, their status, and final resolution.

The Contractor shall host Updated Software Build for the Pilot Study, and deploy bug fixes to the production environment in accordance with Task 5.2.4 System Hosting.

Deliverables:

A. Monthly Defect Report B. Updates to Software for the Pilot Study

5.3 VA CERTIFIED PEER SUPPORT SPECIALISTS

5.3.1 Training peer support specialists to support participants with the AboutFace Engagement Intervention

The contractor will provide VA certified peer support specialists to assist participants with using the AboutFace Engagement Intervention. The number required should be sufficient so that participants can get connected with a peer specialist within 2 days (preferably same day) of enrolling in the study and so that they are able to respond within 24 hours to any inquiries that come in while the participants are using the intervention. Peer support specialists will receive a specific training in the intervention and how to support participants in its use.

A. VA certified peer support specialists B. Tracking of peer support contacts (e.g., nature of contact, when contact occurred, number of total contacts, etc.)

5.4 PILOT STUDY

The Contractor shall conduct a pilot study of the AboutFace Engagement Intervention with up to 50 veterans. Goals are to 1) to determine the feasibility, rate of recruitment, and study retention, 2) assess the acceptability of the Intervention, and 3) describe pre/post data on readiness, stigma, attitudes toward seeking mental health treatment and behavioral action steps.

The Contractor shall: recruit enough Veterans to ensure that a minimum of 50 Veterans enroll in the pilot study following screening. Eligible participants are Veterans who screen positive on the PC-PTSD-5 (e.g. 3 or more endorsed) and who have not received PTSD treatment in the last 6 months. The pilot study shall run until all 50 participants have been enrolled and all those who have not withdrawn have completed post-assessments (approximately 3 months).

The Contractor shall collect system usage and behavioral health outcomes data to evaluate the impacts of the Veterans’ use of the platform and their interaction patterns with peer support mentors using the measures and time points specified by NCPTSD.

The Contractor shall provide a structured dataset containing de-identified data on participant usage of the intervention, clinical variables, and peer support contacts to NCPTSD for analysis and interpretation.

The Contractor shall collect self-report measures of clinical variables at study enrollment, post intervention, and at three-month follow up. Automated reminders should be sent to participants with log-in information that takes them to the online surveys. The contractor will also provide summary data of peer support contacts (e.g., nature of contact, when contact occurred, number of total contacts, etc.)

The Contractor shall provide NCPTSD with Preliminary Study Datasets after collection of the first 10 participants for quality and process checks. The Contractor shall provide a Final Pilot Study Dataset after meeting recruitment goals and after completing data collection. The datasets shall consist of system usage and peer support services interaction data summarized at the individual user level. System usage includes variables such as frequency and duration of time spent on system, completion of current intervention modules, frequency and duration of peer support specialist interactions per peer support specialist and in total, frequency of use of peer chat function, and any indicator variables for safety-related actions taken (e.g., required peer support contact and/or transfer to Veterans Crisis Line). The dataset also shall include the raw item-level scores for each clinical measure from each assessment point. To obtain de-identified data, dates of assessment points and other time-based information shall be provided as days since day of enrollment. A unique person-specific study identification variable shall be included as a numeric (integer) variable that does not include any personally identifying information.

Deliverables:

A. Preliminary Pilot Study Dataset B. Final Pilot Study Dataset

5.5 FINAL REPORT

1. Final Report

a. There shall be a research report on the pilot study.

b. The dashboards shall display data on:

i. Participant enrollment (e.g., number consented, random assignment condition if applicable, progress through programs, completion status).

ii. Program usage (e.g., mean and mode of time spent completing various study components, such as module review, video time, etc.).

iii. Progress on completing various study modules (e.g., time since last log on, number of components completed, research peer support identification, tools accessed if applicable, research questionnaires completed and by time point, overall completion status, etc.).

iv. At agreed upon timepoints (e.g., after first ten users, at completion of study, upon need for preliminary analyses), NCPTSD staff shall have access to all relevant data collected via a data download option.

v. All VA and Contractor staff who are involved in these research protocols and programs and/or access these data shall have completed Collaborative Institutional Training Initiative training (i.e., training in responsible conduct of research).

Deliverables:

A. AboutFace Pilot Study Final Report

5.6 OPTION PERIOD ONE

If Option Period One is exercised by VA, all tasks in the following sections and their sub-sections shall apply:

5.2.4 System Hosting

5.7 OPTION PERIOD TWO

If Option Period Two is exercised by VA, all tasks in the following sections and their sub-sections shall apply:

5.2.4 System Hosting

5.8 OPTION PERIOD THREE

If Option Period Three is exercised by VA, all tasks in the following sections and their sub-sections shall apply:

5.2.4 System Hosting

5.9 OPTION PERIOD FOUR

If Option Period Four is exercised by VA, all tasks in the following sections and their sub-sections shall apply:

5.2.4 System Hosting

At any point in the contract (base or option years) the following CLINs can be exercised.

5.10 OPTIONAL CLIN

400 completed Veterans through the study design using 5.2.4, 5.2.5, 5.3, 5.4, and 5.5 as a guide.

5.10.1 Four hundred completed Veterans through the study design

5.10.2 Report including details on the 400 completed Veterans

6.0 GENERAL REQUIREMENTS

6.1 SECURITY AND PRIVACY REQUIREMENTS

6.1.1 POSITION/TASK RISK DESIGNATION LEVEL(S)

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

Position Sensitivity and Background Investigation Requirements by Task Task Number Tier1 / Low Risk Tier 2 / Moderate

Risk Tier 4 / High Risk

5.1 5.2 5.3 5.4 5.5

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

A. Contractor Staff Roster

6.2 METHOD AND DISTRIBUTION OF DELIVERABLES

The Contractor shall deliver documentation in electronic format, unless otherwise directed in Section B of the solicitation/contract. Acceptable electronic media include:

MS Word 2000/2003/2007/2010, MS Excel 2000/2003/2007/2010, MS PowerPoint 2000/2003/2007/2010, MS Project 2000/2003/2007/2010, MS Access 2000/2003/2007/2010, MS Visio 2000/2002/2003/2007/2010, AutoCAD 2002/2004/2007/2010, and Adobe Postscript Data Format (PDF).

6.3 PERFORMANCE METRICS

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

Performance Objective

Performance Standard Acceptable Levels of Performance

A. Technical / Quality of Product or Service

1. Demonstrates understanding of requirements

2. Efficient and effective in meeting requirements

3. Meets technical needs and mission requirements

4. Provides quality services/products

Satisfactory or higher

B. Project Milestones and Schedule

1. Established milestones and project dates are met

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

3. Notifies customer in advance of potential problems

Satisfactory or higher

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

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

Satisfactory or higher

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

Satisfactory or higher

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

6.4 FACILITY/RESOURCE PROVISIONS

All procedural guides, reference materials, and program documentation for the project and other Government applications will be provided on an as-needed basis.

The Contractor shall request other Government documentation deemed pertinent to the work accomplishment directly from the Government officials with whom the Contractor has contact. The Contractor shall consider the COR as the final source for needed Government documentation when the Contractor fails to secure the documents by other means. The Contractor is expected to use common knowledge and resourcefulness in securing all other reference materials, standard industry publications, and related materials that are pertinent to the work.

The Contractor shall ensure all work is performed in countries deemed not to pose a significant security risk. For detailed Security and Privacy Requirements (additional requirements of the contract consolidated into an addendum for easy reference) refer to ADDENDUM a – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED and

ADDENDUM B - VA INFORMATION AND INFORMATION SYSTEM

SECURITY/PRIVACY LANGUAGE.

6.5 GOVERNMENT FURNISHED PROPERTY

No Government furnished property or information will be issued.

6.6 NOTICE OF THE FEDERAL ACCESSIBILITY LAW AFFECTING ALL

INFORMATION AND COMMUNICATION TECHNOLOGY (ICT)

PROCUREMENTS (SECTION 508)

On January 18, 2017, the Architectural and Transportation Barriers Compliance Board (Access Board) revised and updated, in a single rulemaking, standards for electronic and information technology developed, procured, maintained, or used by Federal agencies covered by Section 508 of the Rehabilitation Act of 1973, as well as our guidelines for telecommunications equipment and customer premises equipment covered by Section 255 of the Communications Act of 1934. The revisions and updates to the Section 508-based standards and Section 255-based guidelines are intended to ensure that information and communication technology (ICT) covered by the respective statutes is accessible to and usable by individuals with disabilities.

6.6.1 SECTION 508 – INFORMATION AND COMMUNICATION TECHNOLOGY

(ICT) STANDARDS

On January 18, 2017, the Architectural and Transportation Barriers Compliance Board (Access Board) revised and updated, in a single rulemaking, standards for electronic and information technology developed, procured, maintained, or used by Federal agencies covered by Section 508 of the Rehabilitation Act of 1973, as well as our guidelines for telecommunications equipment and customer premises equipment covered by Section 255 of the Communications Act of 1934. The revisions and updates to the Section 508-based standards and Section 255-based guidelines are intended to ensure that information and communication technology (ICT) covered by the respective statutes is accessible to and usable by individuals with disabilities.

The following Section 508 Requirements supersede Addendum A, Section A3 from the T4NG Basic PWS. The Section 508 standards established by the Access Board are incorporated into, and made part of all VA orders, solicitations and purchase orders developed to procure ICT. These standards are found in their entirety at:

https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines. A printed copy of the standards will be supplied upon request.

Federal agencies must comply with the updated Section 508 Standards beginning on January 18, 2018. The Final Rule as published in the Federal Register is available from the Access Board: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule.

The Contractor shall comply with “508 Chapter 2: Scoping Requirements” for all electronic ICT and content delivered under this contract. Specifically, as appropriate for the technology and its functionality, the Contractor shall comply with the technical standards marked here:

E205 Electronic Content – (Accessibility Standard -WCAG 2.0 Level A and AA Guidelines)

E204 Functional Performance Criteria E206 Hardware Requirements E207 Software Requirements E208 Support Services and Documentation Requirements

6.6.2 COMPATABILITY WITH ASSISTIVE TECHNOLOGY

The standards do not require installation of specific accessibility-related software or attachment of an assistive technology device. Section 508 requires that ICT be compatible with such software and devices so that ICT can be accessible to and usable by individuals using assistive technology, including but not limited to screen readers, screen magnifiers, and speech recognition software.

6.6.3 ACCEPTANCE AND ACCEPTANCE TESTING

Deliverables resulting from this solicitation will be accepted based in part on satisfaction of the Section 508 Chapter 2: Scoping Requirements standards identified above.

The Government reserves the right to test for Section 508 Compliance before delivery.

The Contractor shall be able to demonstrate Section 508 Compliance upon Deliverables resulting from this solicitation will be accepted based in part on satisfaction of the Section 508 Chapter 2: Scoping Requirements standards identified above.

The Government reserves the right to test for Section 508 Compliance before delivery.

The Contractor shall be able to demonstrate Section 508 Compliance upon delivery.

6.7 INFORMATION SECURITY CONSIDERATIONS:

The Assessment and Authorization (A&A) requirements do not apply and a Security Accreditation Package is not required.

All VA sensitive information shall be protected at all times in accordance with local security field office System Security Plans (SSP’s) and Authority to Operate (ATO)’s for all systems/LAN’s accessed while performing the tasks detailed in this Product Description.

a. A prohibition on unauthorized disclosure: “Information made available to the Contractor or Subcontractor by VA for the performance or administration of this contract or information developed by the Contractor/Subcontractor in performance or administration of the contract shall be used only for those purposes and shall not be used in any other way without the prior written agreement of the VA.” This clause expressly limits the Contractor/Subcontractor’s rights to use data as described in Rights in Data – General, FAR 52.227-14(d).(1).

b. A requirement for data breach notification: Upon discovery of any known or suspected security/privacy incidents, or any unauthorized disclosure of sensitive information, including that contained in system(s) to which the Contractor/Subcontractor has access, the Contractor/Subcontractor shall immediately notify the COR and simultaneously, the designated ISO, and Privacy Officer for the contract.