S06 - 36C10A25R0002 0003 Amended RFP.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

TAC

36C10A25R0002 06-26-2025

Anthony Browner 512-981-4449 10-31-2025

14:00 CST

Department of Veterans Affairs Technology Acquisition Center - Div G

23 Christopher Way Eatontown NJ 07724

X 100

X

Y

541519

150 Employees

N/A

X

See Schedule

Department of Veterans Affairs Technology Acquisition Center - Div G

23 Christopher Way Eatontown NJ 07724

Department of Veteran Affairs Financial Services Center P.O. Box 149971

Austin TX 78714-8971

(877) 353-9791

See CONTINUATION Page

MODERNIZED MESSAGING SOFTWARE AS A SERVICE

See CONTINUATION Page

X X

36C10A25R0002

Table of Contents

SECTION A

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

AND COMMERCIAL SERVICES

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 SCHEDULE OF SUPPLIES AND SERVICES

B.2 GOVERNING LAW (continuation of Schedule of Supplies and Services above):

B.3 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT:

B.4 PERFORMANCE WORK STATEMENT

B.4.1. BACKGROUND

B.4.2. APPLICABLE DOCUMENTS

B.4.3. SCOPE OF WORK

B.4.4. PERFORMANCE DETAILS

B.5 CONTRACT ADMINISTRATION DATA

B.6 ACCOUNTING AND APPROPRIATION DATA

SECTION C - CONTRACT CLAUSES

C.1 FAR 52.212-4 CONTRACT TERMS AND CONDITIONS—COMMERCIAL

PRODUCTS AND COMMERCIAL SERVICES (NOV 2023)

C.1.1 ADDENDUM to FAR 52.212-4 CONTRACT TERMS AND CONDITIONS—

COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

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

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

LINE ITEM (MAR 1989)

C.1.4 FAR 52.217-8 OPTION TO EXTEND SERVICES (NOV 1999)

C.1.5 FAR 52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR

2000)

C.1.6 FAR 52.227-16 ADDITIONAL DATA REQUIREMENTS (JUN 1987)

C.1.7 VAAR 852.201-70 CONTRACTING OFFICER’S REPRESENTATIVE (DEC 2022)

C.1.8 VAAR 852.239-70 SECURITY REQUIREMENTS FOR INFORMATION

TECHNOLOGY RESOURCES (FEB 2023)

C.1.9 VAAR 852.239-72 INFORMATION SYSTEM DESIGN AND DEVELOPMENT

(FEB 2023)

C.1.10 VAAR 852.239-73 INFORMATION SYSTEM HOSTING, OPERATION,

MAINTENANCE, OR USE (FEB 2023)

C.1.11 VAAR 852.219-73 VA NOTICE OF TOTAL SET-ASIDE FOR CERTIFIED

SERVICE-DISABLED VETERAN-OWNED SMALL BUSINESSES (JAN 2023)

(DEVIATION)

C.1.12 VAAR 852.219-75 VA NOTICE OF LIMITATIONS ON SUBCONTRACTING —

CERTIFICATE OF COMPLIANCE FOR SERVICES AND CONSTRUCTION (JAN 2023)

(DEVIATION)

C.1.13 VAAR 852.232-72 ELECTRONIC SUBMISSION OF PAYMENT REQUESTS

(NOV 2018)

C.1.14 VAAR 852.237-75 KEY PERSONNEL (OCT 2019)

C.1.15 VAAR 852.242-71 ADMINISTRATIVE CONTRACTING OFFICER

C.1.16 MANDATORY WRITTEN DISCLOSURES

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

STATUTES OR EXECUTIVE ORDERS—COMMERCIAL PRODUCTS AND

COMMERCIAL SERVICES (JAN 2025) (DEVIATION JUL 2025)

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION E - SOLICITATION PROVISIONS

E.1 FAR 52.212-1 INSTRUCTIONS TO OFFERORS—COMMERCIAL PRODUCTS

AND COMMERCIAL SERVICES (SEP 2023)

E.1.1 ADDENDUM to FAR 52.212-1 INSTRUCTIONS TO OFFERORS—COMMERCIAL

PRODUCTS AND COMMERCIAL SERVICES

E.1.2 FAR 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE

(FEB 1998)

E.1.3 FAR 52.204-24 REPRESENTATION REGARDING CERTAIN

TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT

(NOV 2021)

E.1.4 FAR 52.204-29 FEDERAL ACQUISITION SUPPLY CHAIN SECURITY ACT

ORDERS—REPRESENTATION AND DISCLOSURES (DEC 2023)

E.1.5 FAR 52.209-7 INFORMATION REGARDING RESPONSIBILITY MATTERS (OCT

2018)

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

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

E.1.8 VAAR 852.233-71 ALTERNATE PROTEST PROCEDURE (OCT 2018)

E.2 FAR 52.212-2 EVALUATION—COMMERCIAL PRODUCTS AND COMMERCIAL

SERVICES (NOV 2021)

B. FACTORS TO BE EVALUATED

C. EVALUATION APPROACH

E.12 FAR 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—

COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (MAY 2024) (DEVIATION

FEB 2025)

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 SCHEDULE OF SUPPLIES AND SERVICES

CLIN DESCRIPTION QTY UNIT of

ISSUE UNIT PRICE TOTAL

All products/services shall be in accordance with the Product Description, Modernized Messaging Software Application.

ARM: 182833

Inspection/Acceptance: Destination Delivery Address/Point of Contact: See Product Description Product Service Code (PSC): DA10 Type: Firm Fixed Price (FFP)

Base Year: POP 12 months from date of award

Messaging Software Application (Not to Exceed (NTE) 20,000 licenses)

20,000

NTE EA $________ $________

0002 Project Management IAW PWS Section B.4.5.1

1 LT $________ $________

0002AA

Deliverable IAW PWS Section B.4.5.3.1 Project Kickoff Meeting Agenda

1 EA NSP NSP

0002AB

Deliverable IAW PWS Section B.4.5.3.2 Project Kickoff Meeting Minutes

1 EA NSP NSP

0002AC

Deliverable IAW PWS Section B.4.5.5.1 Go-Live Artifacts

10 EA NSP NSP

0002AD

Deliverable IAW PWS Section B.4.5.7.1 Contractor Management Plan

(CMP)

1 EA NSP NSP

0002AE

Deliverable IAW PWS Section B.4.5.7.2 Implementation Plan with Transition Plan

1 EA NSP NSP

CLIN DESCRIPTION QTY UNIT of

ISSUE UNIT PRICE TOTAL

0002F Deliverable IAW PWS Section B.4.5.9.1 Weekly Progress Report

52 EA NSP NSP

0002AG

Deliverable IAW PWS Section B.4.5.9.2 Quarterly Usage Report

4 EA NSP NSP

0003 SaaS FedRAMP Requirements IAW PWS Section B.4.5.10

1 EA NSP NSP

0003AA

Deliverable IAW PWS Section B.4.5.10.2.1 SaaS FedRAMP Requirements Artifacts and Documentation

1 EA NSP NSP

0004 Authority to Operate (ATO) IAW PWS Section B.4.6

1 LT $________ $________

0004AA

Deliverable IAW PWS Section B.4.6.5.1 ATO Package Document

1 EA NSP NSP

0005 Messaging Software Application Solution IAW PWS Section B.4.8

1 LT $________ $________

0005AA

Deliverable IAW PWS Section B.4.8.5.1 Web-based Portal Interface

1 EA NSP NSP

0005AB

Deliverable IAW PWS Section B.4.8.5.2 Maintain issuance and renewal of software licenses

1 EA NSP NSP

0005AC

Deliverable IAW PWS Section B.4.8.5.3 Breakdown of management level of effort

1 EA NSP NSP

0005AD

Deliverable IAW PWS Section B.4.12.1 Message Software Application Training Plan

1 EA NSP NSP

CLIN DESCRIPTION QTY UNIT of

ISSUE UNIT PRICE TOTAL

0005AE

Deliverable IAW PWS Section B.4.14.7.1 Capabilities and Effectiveness Report

1 EA NSP NSP

Messaging Software SaaS Cloud Infrastructure for up to 20,000 licenses IAW PWS Section B.4.15

1 LT $________ $________

Messaging Solution Operations, Maintenance, Sustainment, and Engineering (OMS&E) and Technical Support for up to 103-site implementation IAW PWS B.4.16

1 LT $________ $________

0007AA

Deliverable IAW PWS Section B.4.16.5.1 Application Monitoring Plan

1 EA NSP NSP

Base Year Optional Task Items Optional CLINs IAW FAR 52.217-7, OPTION FOR INCREASED QUANTITY- Separately Priced

Line Items. Optional CLINs may be exercised multiple times, but total amounts exercised shall not exceed the quantities listed below.

Optional CLINs 0008 through 0009 may only be exercised from during the base period. CLIN 0010 may be exercised anytime from during the life of the contract

The Contractor shall provide Messaging Software Application (up to 100,000 licenses)

Up to

100,000 EA $________ $________

Messaging Software SaaS Cloud Infrastructure for up to 100,000 licenses IAW PWS B.4.15

1 LT $________ $________

Messaging Solution Operations, Maintenance, Sustainment, and Engineering (OMS&E) for expanding the current system capacity to an additional 72 sites increasing total site coverage up to 175-site implementation IAW PWS Section B.4.16

1 LT $________ $________

BASE YEAR TOTAL $________

CLIN DESCRIPTION QTY UNIT of

ISSUE UNIT PRICE TOTAL

BASE YEAR: OPTIONAL TASK TOTAL $________

IAW FAR 52.217-9, OPTION TO EXTEND THE TERM OF THE CONTRACT

Option Year One: POP 12-months from the end of the base period.

Messaging Software Application (Not to Exceed (NTE) 20,000 licenses)

20,000

NTE EA $________ $________

1002 Project Management IAW PWS Section B.4.5.1

1 LT $________ $________

1003 Authority to Operate IAW PWS B.4.6.5.1

1 LT $________ $________

Messaging Software SaaS Cloud Infrastructure Renewal for up to 20,000 licenses IAW PWS B.4.15

1 LT $________ $________

Messaging Solution Operation, Maintenance, and Sustainment (OMS) Renewal for up to 103-sites IAW PWS B.4.16

1 LT $________ $________

Option Period One: Optional Task Items Optional CLINs IAW FAR 52.217-7, OPTION FOR INCREASED QUANTITY- Separately Priced Line Items. Optional CLINs may be exercised multiple times, but total amounts exercised shall not exceed the quantities listed below.

Optional CLINs 1006 through 1008 may only be exercised during the period of performance for Option Period One.

The Contractor shall provide Messaging Software Application (up to 100,000 licenses)

100,000

NTE EA $________ $________

Messaging Software SaaS Cloud Infrastructure for up to 100,000 licenses IAW PWS B.4.15

1 LT $________ $________

Messaging Solution Operation, Maintenance, and Sustainment (OMS) for expanding the current system capacity to 72 sites increasing total site coverage up to 175-sites IAW PWS B.4.16

YEAR ONE OPTION TOTAL $________

CLIN DESCRIPTION QTY UNIT of

ISSUE UNIT PRICE TOTAL

YEAR ONE OPTION: OPTIONAL TASK TOTAL $________

IAW FAR 52.217-9, OPTION TO EXTEND THE TERM OF THE CONTRACT

Option Year Two: POP 12-months from the end of Option Period One

Messaging Software Application (Not to Exceed (NTE) 20,000 licenses)

20,000

NTE EA $________ $________

2002 Project Management IAW PWS Section B.4.5.1

1 LT $________ $________

2003 Authority to Operate IAW PWS B.4.6.5.1

1 LT $________ $________

Messaging Software SaaS Cloud Infrastructure Renewal for up to 20,000 licenses IAW PWS B.4.15

1 LT $________ $________

Messaging Solution Operation, Maintenance, and Sustainment (OMS) Renewal for up to 103-sites IAW PWS B.4.16

1 LT $________ $________

Option Year Two: Optional Task Items Optional CLINs IAW FAR 52.217-7, OPTION FOR INCREASED QUANTITY- Separately Priced Line Items. Optional CLINs may be exercised multiple times, but total amounts exercised shall not exceed the quantities listed below.

Optional CLINs 2006 and 2008 may only be exercised during the period of performance for Option Period Two

The Contractor shall provide Messaging Software Application (up to 100,000 licenses)

100,000

NTE EA $________ $________

Messaging Software SaaS Cloud Infrastructure for up to 100,000 licenses IAW PWS B.4.15

1 LT $________ $________

Messaging Solution Operation, Maintenance, and Sustainment (OMS) for expanding the current system capacity to 72 sites increasing total site coverage up to 175-sites IAW PWS B.4.16

CLIN DESCRIPTION QTY UNIT of

ISSUE UNIT PRICE TOTAL

YEAR TWO OPTION TOTAL $________

YEAR TWO OPTION: OPTIONAL TASK TOTAL $________

IAW FAR 52.217-9, OPTION TO EXTEND THE TERM OF THE CONTRACT

Option Year Three: POP 12-months from the end of Option Period Two

Messaging Software Application (Not to Exceed (NTE) 20,000 licenses)

20,000

NTE EA $________ $________

3002 Project Management IAW PWS Section B.4.5.1

1 LT $________ $________

3003 Authority to Operate IAW PWS B.4.6.5.1

1 LT $________ $________

Messaging Software SaaS Cloud Infrastructure Renewal for up to 20,000 licenses IAW PWS B.4.15

1 LT $________ $________

Messaging Solution Operation, Maintenance, and Sustainment (OMS) Renewal for up to 103-sites IAW PWS B.4.16

1 LT $________ $________

Option Year Three: Optional Task Items Optional CLINs IAW FAR 52.217-7, OPTION FOR INCREASED QUANTITY- Separately Priced Line Items. Optional CLINs may be exercised multiple times, but total amounts exercised shall not exceed the quantities listed below.

Optional CLINs 3006 and 3008 may only be exercised during the period of performance for Option Period Three

The Contractor shall provide Messaging Software Application (up to 100,000 licenses)

100,000

NTE EA $________ $________

Messaging Software SaaS Cloud Infrastructure for up to 100,000 licenses IAW PWS B.4.15

1 LT $________ $________

Messaging Solution Operation, Maintenance, and Sustainment (OMS) for expanding the current system capacity to 72 sites increasing total site coverage up to 175-sites IAW PWS B.4.16

YEAR THREE OPTION TOTAL $________

CLIN DESCRIPTION QTY UNIT of

ISSUE UNIT PRICE TOTAL

YEAR THREE OPTION: OPTIONAL TASK TOTAL $________

IAW FAR 52.217-9, OPTION TO EXTEND THE TERM OF THE CONTRACT

Option Year Four: POP 12-months from the end of Option Period Three

Messaging Software Application (Not to Exceed (NTE) 20,000 licenses)

20,000

NTE EA $________ $________

4002 Project Management IAW PWS Section B.4.5.1

1 LT $________ $________

4003 Authority to Operate IAW PWS B.4.6.5.1

1 LT $________ $________

Messaging Software SaaS Cloud Infrastructure Renewal for up to 20,000 licenses IAW PWS B.4.15

1 LT $________ $________

Messaging Solution Operation, Maintenance, and Sustainment (OMS) Renewal for up to 103-sites IAW PWS B.4.16

1 LT $________ $________

Option Year Four: Optional Task Items Optional CLINs IAW FAR 52.217-7, OPTION FOR INCREASED QUANTITY- Separately Priced Line Items. Optional CLINs may be exercised multiple times, but total amounts exercised shall not exceed the quantities listed below.

Optional CLINs 4006 and 4008 may only be exercised during the period of performance for Option Period Four

The Contractor shall provide Messaging Software Application (up to 100,000 licenses)

100,000

NTE EA $________ $________

Messaging Software SaaS Cloud Infrastructure for up to 100,000 licenses IAW PWS B.4.15

1 LT $________ $________

Messaging Solution Operation, Maintenance, and Sustainment (OMS) for expanding the current system capacity to 72 sites increasing total site coverage up to 175-sites IAW PWS B.4.16

1 LT $________ $________

YEAR FOUR OPTION TOTAL $________

YEAR FOUR OPTION: OPTIONAL TASK TOTAL $________

CLIN DESCRIPTION QTY UNIT of

ISSUE UNIT PRICE TOTAL

IAW FAR 52.217-8, OPTION TO EXTEND SERVICES – Not to exceed six-months

Line # Description QTY UNIT UNIT PRICE TOTAL

Messaging Software Application Subscription Renewal (up to 20,000 licenses)

20,000

NTE EACH $________ $________

5002 Project Management IAW PWS Section B.4.5.1

1 LT $________ $________

5003 Authority to Operate IAW PWS B.4.6.5.1

1 LT $________ $________

Messaging Software SaaS Cloud Infrastructure Renewal for up to 20,000 licenses IAW PWS B.4.15

1 LT $________ $________

Messaging Solution Operation, Maintenance, and Sustainment (OMS) Renewal for up to 103-sites IAW PWS B.4.16

1 LT $________ $________

Optional Task Items Optional CLINs IAW FAR 52.217-7, OPTION FOR INCREASED QUANTITY- Separately Priced Line Items. Optional CLINs may be exercised multiple times, but total amounts exercised shall not exceed the quantities listed below.

Optional CLINs 5006 and 5008 may only be exercised for the duration of when FAR 52.217-8 is exercised

The Contractor shall provide Messaging Software Application (up to 100,000 licenses)

100,000

NTE EA $________ $________

Messaging Software SaaS Cloud Infrastructure for up to 100,000 licenses IAW PWS B.4.15

1 LT $________ $________

Messaging Solution Operation, Maintenance, and Sustainment (OMS) for expanding the current system capacity to 72 sites increasing total site coverage up to 175-sites IAW PWS B.4.16

1 LT $________ $________

OPTION TO EXTEND SERVICES TOTAL $________

OPTION TO EXTEND SERVICES: OPTIONAL TASK TOTAL $________

CLIN DESCRIPTION QTY UNIT of

ISSUE UNIT PRICE TOTAL

Base and all Option Years (excludes Optional Tasks)

GRANDTOTAL $________

Base and all Option Years including Optional Tasks

GRAND TOTAL $________

B.2 GOVERNING LAW (continuation of Schedule of Supplies and Services above):

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 contract/order 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.3 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 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 so as to cause the software to perform according to its specifications, documentation or demonstrated claims.

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

d) The Contractor shall provide all maintenance services in a timely manner in accordance with the Contractor’s customary practice or as defined in the Performance Work Statement or Product Description. However, prolonged delay (exceeding 2 business days) in resolving software problems will be noted in the Government’s various past performance records on the Contractor (e.g., www.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.

http://www.cpars.gov/

B.4 PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS (VA)

Office of Information & Technology (OIT)

End User Services (EUS)

Modernized Messaging

Date: September 26, 2025

VA-25-0034169

PWS Version Number: 3.0

B.4.1. BACKGROUND

The VA Office of Information and Technology (OIT), End User Services (EUS), strives to provide high quality, effective, and efficient Information Technology (IT) services to those responsible for providing care to the Veterans at the point-of-care as well as throughout all the points of the Veterans’ health care in an effective, timely and compassionate manner. VA depends on Information Management/Information Technology (IM/IT) systems to meet mission goals.

OIT EUS is leading the effort to modernize alpha-numeric and numeric text messaging communication technology from mobile physical pagers, that utilize a combination of satellite and terrestrial radio networks, to a non-physical pager, non-life safety packet switching and Transmission Control Protocol (TCP)/Internet Protocol (IP) protocols mobile device software application text messaging communication solution architecture. The solution’s mission critical principal strategic requirement shall be secure, encrypted, and Health Insurance Portability and Accountability Act (HIPAA)-compliant text messages. Additionally, bedrock privacy, security, and performance characteristics of the solution shall include:

• Security and privacy of Veteran data and information is built into the solution

• Veteran Protected Health Information (PHI), Personally Identifiable Information (PII), Sensitive Personal Information (SPI) are protected (No unauthorized access and use)

• Text messaging transmission is security enabled (All text messages encrypted)

• No government data or information exists on device (No VA information or data exists, stored, or saved on device)

• 100% separation of government/corporate and personal device data and information (Preserves end-user privacy)

• 100% privacy of personal data (Reduces security risks with no data at rest and no data in transit)

B.4.2. APPLICABLE DOCUMENTS

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

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

B.4.2.2. Federal Information Security Modernization Act of 2014 B.4.2.3. Federal Information Processing Standards (FIPS) Publication 140-2, “Security

Requirements for Cryptographic Modules” B.4.2.4. FIPS Pub 199. “Standards for Security Categorization of Federal Information and

Information Systems,” February 2004 B.4.2.5. FIPS Pub 200, “Minimum Security Requirements for Federal Information and

Information Systems,” March 2006 B.4.2.6. FIPS Pub 201-2, “Personal Identity Verification of Federal Employees and

Contractors,” August 2013 B.4.2.7. 10 U.S.C. § 2224, "Defense Information Assurance Program" B.4.2.8. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974” B.4.2.9. Public Law 109-461, Veterans Benefits, Health Care, and Information Technology

Act of 2006, Title IX, Information Security Matters B.4.2.10. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964” B.4.2.11. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, https://www.va.gov/vapubs/index.cfm B.4.2.12. VA Handbook 0710, “Personnel Security and Suitability Program,” May 2, 2016, https://www.va.gov/vapubs/index.cfm B.4.2.13. VA Directive and Handbook 6102, “Internet/Intranet Services,” August 5, 2019 B.4.2.14. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and

Guidelines,” January 18, 2017 B.4.2.15. Office of Management and Budget (OMB) Circular A-130, “Managing Federal

Information as a Strategic Resource,” July 28, 2016 B.4.2.16. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services

(CHAMPUS)”

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

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

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

B.4.2.19. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004 B.4.2.20. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021 B.4.2.21. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA

Information Security Program,” February 24, 2021 B.4.2.22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal

Information (SPI),” March 12, 2019 B.4.2.23. VA Handbook 6500.5, “Incorporating Security and Privacy into the System

Development Lifecycle,” March 22, 2010 B.4.2.24. VA Handbook 6500.6, “Contract Security,” March 12, 2010 B.4.2.25. VA Handbook 6500.8, “Information System Contingency Planning,” April 6, 2011 B.4.2.26. VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018 https://www.va.gov/vapubs/index.cfm https://www.va.gov/vapubs/index.cfm http://www.va.gov/vapubs http://www.va.gov/vapubs

B.4.2.27. VA Handbook 6500.11, “VA Firewall Configuration,” August 22, 2017 B.4.2.28. 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

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

B.4.2.30. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014

B.4.2.31. VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy Impact Assessment,” July 30, 2015

B.4.2.32. VA Handbook 6510, “VA Identity and Access Management,” January 15, 2016 B.4.2.33. VA Directive and Handbook 6513, “Secure External Connections,” October 12, B.4.2.34. VA Directive 6300, “Records and Information Management,” September 21, 2018 B.4.2.35. VA Handbook, 6300.1, “Records Management Procedures, “March 24, 2010 B.4.2.36. NIST SP 800-37 Rev 2, “Risk Management Framework for Information Systems and

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

B.4.2.37. 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)

B.4.2.38. VA Directive 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” October 26, 2015

B.4.2.39. VA Handbook 0735, “Homeland Security Presidential Directive 12 (HSPD-12) Program,” March 24, 2014

B.4.2.40. 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

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

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

B.4.2.43. 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)

B.4.2.44. NIST SP 800-116 Rev 1, “Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access,“ June 2018

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

B.4.2.46. NIST SP 800-157, “Guidelines for Derived PIV Credentials,” December 2014 B.4.2.47. NIST SP 800-164, “Guidelines on Hardware-Rooted Security in Mobile Devices

(Draft),” October 2012 B.4.2.48. Draft National Institute of Standards and Technology Interagency Report (NISTIR)

7981, “Mobile, PIV, and Authentication,” March 2014 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 https://arch.idmanagement.gov/#what-is-the-ficam-architecture https://arch.idmanagement.gov/#what-is-the-ficam-architecture

B.4.2.49. 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)

B.4.2.50. 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)

B.4.2.51. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896

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

B.4.2.53. OMB Memorandum M-19-26, “Update to the Trusted Internet Connections (TIC) Initiative,” September 12, 2019

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

B.4.2.55. OMB M-06-16 “Protection of Sensitive Agency Information,” B.4.2.56. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public Law 110–140), December 19, 2007 B.4.2.57. Section 104 of the Energy Policy Act of 2005, (Public Law 109–58), August 8, 2005 B.4.2.58. Executive Order 13834, “Efficient Federal Operations,” dated May 17, 2018 B.4.2.59. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001 B.4.2.60. VA Directive 0058, “VA Green Purchasing Program,” July 19, 2013 B.4.2.61. VA Handbook 0058, “VA Green Purchasing Program,” July 19, 2013 B.4.2.62. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote

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

B.4.2.63. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103 B.4.2.64. “Veteran Focused Integration Process (VIP) Guide 4.0,” January 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 B.4.2.65. VA Memorandum “Proper Use of Email and Other Messaging Services,” January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 B.4.2.66. “DevSecOps Product Line Management Playbook” version 2.0, May 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946 B.4.2.67. NIST SP 500-267B Revision 1, “USGv6 Profile,” November 2020 B.4.2.68. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol

Version 6 (IPv6),” November 19, 2020 B.4.2.69. Social Security Number (SSN) Fraud Prevention Act of 2017 B.4.2.70. Section 240 of the Consolidated Appropriations Act (CAA) 2018, March 23, 2018 B.4.2.71. Committee on National Security Systems Instruction No. 1253 (CNSSI 1253) B.4.2.72. Health Information Technology for Economic and Clinical Health (HITECH) Act B.4.2.73. National Institute of Standards and Technologies (NIST) Cybersecurity Framework

(CSF) - Core Identify Function B.4.2.74. NIST SP 800-18, Guide for Developing Security Plans for Federal Information

Systems B.4.2.75. NIST SP 800-60 Volume 1 Revision 1: Guide for Mapping Types of Information and

Information Systems to Security Categories (The SP 800-60 information types and security impact levels are based on the OMB Federal Enterprise 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 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

Program Management Office’s October 2007 FEA Consolidated Reference Model Document, Version 2.3 inputs from participants in NIST SP 800-60 workshops, and

FIPS 199).

B.4.2.76. NIST SP 800-60 Volume 2 Revision 1: Guide for Mapping Types of Information and Information Systems to Security Categories: Appendices

B.4.2.77. The Privacy Act of 1974 B.4.2.78. VA Directive 0900, VA Enterprise Data Management (VADM) B.4.2.79. VA Handbook 6517, Risk Management Framework for Cloud Computing Services B.4.2.80. NIST Special Publication (SP) 800-60 may be used by organizations in conjunction with a family of security-related publications including: NIST SP 800-30, Risk Management Guide for Information Technology Systems.

B.4.2.81. NIST Draft SP 800-39, Managing Risk from Information Systems: An Organizational Perspective.

B.4.2.82. NIST SP 800-59, Guideline for Identifying an Information System as a National Security System.

B.4.2.83. NIST SP 800-145: The NIST Definition of Cloud Computing B.4.2.84. NIST SP 800-122 “Guide to Protecting the Confidentiality of Personally Identifiable

Information (PII),” B.4.2.85. NIST SP 800-171 “Protecting Controlled Unclassified Information in the Nonfederal

Information Systems and Organizations,” B.4.2.86. NIST SP 500-322 Evaluation of Cloud Computing Services based on NIST SP 800-

B.4.2.87. VA Directive 6517, Cloud Computing Services B.4.2.88. VA Directive 6066, Protected Health Information (PHI) and Business Associate

Agreements Management

B.4.3. SCOPE OF WORK

The Contractor shall provide text messaging software application in a Software as a Service (SaaS) Federal Risk and Authorization Management Program (FedRAMP) Moderate, and encrypted alpha, numeric and graphic communications cloud environment with Federal Information Processing Standards (FIPS)-199 Security Characterization Moderate. The Contractor shall provide program management to accomplish the requirements as described in this PWS; complete the process to obtain a VA Authority to Operate (ATO) and maintain the ATO throughout the life of the contract; and provide implementation, and operations, maintenance, sustainment and engineering (OMS&E) support. The Contractor shall also provide Optional Tasks for additional SaaS licenses and Optional support periods.

B.4.4. PERFORMANCE DETAILS

B.4.4.1. PERFORMANCE PERIOD

The PoP shall be 12 months from date of award, with four 12-month option period(s). The overall Period of Performance shall not exceed 60 months.

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

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

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

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 Tuesday in November

B.4.4.3. PLACE OF PERFORMANCE

Tasks under this PWS shall be implemented and supported in VA facilities located in VA Medical Centers (VAMCs), Community Based Outpatient Clinics (CBOCs), field and program offices and other remote users that are geographically dispersed throughout the United States (US), Guam, Saipan, American Samoa, Philippines, and Puerto Rico.

B.4.4.4. TRAVEL

The Government does not anticipate any travel under this effort.

B.4.5. SPECIFIC TASKS AND DELIVERABLES

The Contractor shall provide a non-physical pager, non-life safety text messaging software application solution that delivers Federal Risk and Authorization Management Program FedRAMP) Moderate, and encrypted alpha-numeric, and numeric communications. The Contractor shall demonstrate/document current FedRAMP Moderate Authorization.

Additionally, the CSP offering the mobile application solution shall be responsible for management of the application, safeguarding of data stored or processed by the application, and all elements of the underlying infrastructure. The mobile messaging software application vendor shall be responsible for demonstrating current Federal Information Processing Standards (FIPS)-199 Security Characterization Moderate.

The Contractor shall provide a non-physical pager, non-life safety messaging software application solution which shall not store or save any Government data on Government Furnished Equipment (GFE) mobile smartphones and tablets or Bring Your Own Device (BYOD) mobile smartphones and tablets. The Contractor shall enable the full capability and functionality of the solution with Government Furnished Equipment (GFE) smartphones and tablets as well as end user Bring Your Own Device (BYOD) non-GFE smartphones and tablets.

The Contractor shall ensure the proposed messaging solution is designed to protect the confidentiality and integrity of all electronic Protected Health Information (PHI), Personally Identifiable information (PII), Sensitive Personal Information (SPI), and VA sensitive information, created, transmitted, received, and maintained/stored as alpha-numeric text messages. All messages shall be encrypted according to the Federal and Agency standards for all data at rest, in use and in transit to include compliance with the Federal Information Security Management

Act (FISMA) and Federal Information Processing Standards (FIPS). The Contractor shall ensure no VA data, of any nature, is stored on the device. The Contractor shall ensure 100% separation of government/corporate and personal device data and information.

The Contractor shall be responsible for the management of network, servers, operating systems, storage, and application capabilities infrastructures, apart from limited Government user-specific applications configuration settings. The messaging software application solution shall have on-demand self-service, broad network access, resource pooling, handle varying workloads, scalable resource that shall be able to add computing power, storage, or network capacity. The messaging software application solution shall be hosted within the continental United States (CONUS) to include data storing and transmission exclusively in CONUS. The Contractor shall complete the process to obtain a VA Authority to Operate (ATO) and maintain the ATO throughout the life of the contract. The Contractor shall provide the plan of approach and Implementation plan that will deliver the solution.

The Contractor shall describe their Modernized Messaging solution’s execution (delivery, transition, installation, provisioning, Day 1 readiness for production deployment), enterprise deployment, implementation, operations, maintenance, sustainment, and engineering (OMS&E) plan with notional schedule portrayed across the enterprise. The Contractor shall provide all required hardware, software, and licensing for the operations, maintenance, sustainment, and engineering (OMS&E) of the solution.

B.4.5.1. PROJECT MANAGEMENT

The Contractor shall accomplish the administrative, managerial, logistical, technical, quality assurance, reporting, and security requirements as described in this PWS. The Contractor shall identify an individual as the primary Point of Contact (POC) for all project matters. Intellectual property owned by the VA shall be provided to the Contractor in an electronic format and transmitted by a secure communication methodology for use under this PWS.

B.4.5.2. PROJECT KICKOFF MEETING

A kickoff meeting shall be held virtually within seven calendar days after contract award. The Contractor shall coordinate the date and time of the virtual meeting with the Contracting Officer (CO), the VA contract Project Manager (PM), the Contract Specialist (CS), the Contracting Officers Representative (COR), the Delivery Date Coordinator, the Implementation Manager and/or VA-designee. The Contractor shall provide a draft agenda to the CO and VA contract PM at least three calendar days prior to the meeting. Upon Government approval of the final agenda, the Contractor shall distribute to all meeting attendees. During the kickoff-meeting, the Contractor shall present, for review and approval by the Government, the details of the intended approach, work plan, and project schedule for each effort via a Microsoft Office PowerPoint presentation. This shall include a plan to discuss delivery schedule requirements. At the conclusion of the meeting, the Contractor shall update the presentation with a final slide entitled “Summary Report” which shall include notes on any major issues, agreements, or disagreements discussed during the kickoff meeting. The Contractor shall submit the final updated presentation to the CO for review within three calendar days after the meeting. The Contractor shall also work with the CS, the Government’s designated note taker, to prepare and distribute the meeting minutes of the kickoff meeting to the CO, COR, and all attendees within three calendar days after the meeting. The Contractor shall obtain concurrence from the CS on the content of the meeting minutes prior to distribution of the document.

For the option periods, a kick-off meeting is only needed if requested by the VA contract PM.

B.4.5.3. Deliverables:

B.4.5.3.1. Project Kickoff Meeting Agenda

B.4.5.3.2. Project Kickoff Meeting Minutes

B.4.5.4. GO-LIVE TASKS

B.4.5.4.1. The Contractor shall provide the following activities and artifacts to achieve readiness for go-live and beyond:

B.4.5.4.2. Develop and provide introductory and ongoing Go-Live communications, Bulletins, Notices as applicable.

B.4.5.4.3. Prepare (author), update, provide, publish, and revise Knowledge Documents / yourIT Knowledge Base, your IT Service Portal, yourIT Technical Services Catalogue; end-user application provisioning and installation instructions; Instructions;

How-Tos; frequently asked questions; end-user guides.

B.4.5.4.4. Include details about transitioning/migrating to solution, provisioning, initial setup and installation, user training and instruction, end user technical support throughout the life of the contract, and post-implementation operations, maintenance, sustainment, and engineering (OMS&E).

B.4.5.4.5. Document, coordinate, and resolve Troubleshooting, Incident, and Problem Ticket Reporting and Escalation.

B.4.5.4.6. Coordinate mobile applications VA compliance approval (Privacy, Security, Section 508, Technical Reference Model (TRM), security updates, operating system updates, application version updates, etc).

B.4.5.4.7. Provide checklist or guidance for Day 1 readiness for Production Go- Live/Deployment (Technical Checklist & Other Checklists necessary for go-live).

B.4.5.4.8. Identify and track the countdown of activities and milestones to provide leadership with assessment of Day 1 Production Go-Live readiness and beyond.

B.4.5.4.9. Scale up Contractor operations and activities to achieve Go-Live implementation, operations, maintenance, sustainment, and engineering (OMS&E) at more than one facility at the same time across the enterprise.

B.4.5.4.10. The Contractor shall lead ongoing operations, maintenance, sustainment, and engineering (OMS&E) activities to achieve all facility’s readiness for go-live and beyond.

B.4.5.4.11. 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.4.5.5. Deliverable:

B.4.5.5.1. Go-Live Artifacts

B.4.5.6. CONTRACTOR MANAGEMENT PLAN (CMP)

The Contractor shall develop, maintain, and execute an implementation Plan, that defines the implementation approach, processes, and activities (prior to, during, and after), test strategy, setup, and configuration procedure, inventory of IT assets, implementation checklist, risk assessment, key dependencies, and schedule. The Contractor shall recommend the compatible Software as a Service (SaaS) Cloud Service Provider (CSP).