36C10B25Q0349 Soliciation 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

36C10B25Q0349 08-05-2025

Dennis Simms 848-377-5132 08-07-2025

9:00 AM EDT

Department of Veterans Affairs

Technology Acquisition Center

Office of Procurement, Acquisitions and Logistics

23 Christopher Way

Eatontown NJ 07724

811210

$34 Million

N/A

X

See Delivery Schedule

Technology Acquisition Center

TBD

Financial Services Center

PO Box 149971

Austin TX 78714-8971

See website at: http://www.fsc.va.gov/einvoice.asp.

(877) 353-9791

See CONTINUATION Page

Points of Contact:

Michael.Weckesser@va.gov, Contracting Officer

Dennis.Simms@va.gov, Contract Specialist

This sole-source action will result in Firm-fixed-priced contract.

See Solicitation for details.

Period of Performance shall be a 3-month Base Period from date of award with three (3) 1-month Option Periods if exercised.

Total performance shall not extend beyond 6 months.

x X

MICHAEL WECKESSER

CONTRACTING OFFICER

Office of Procurement, Acquisitions and Logistics

36C10B25Q0349

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B1. GOVERNING LAW CLAUSE

B2. SOFTWARE LICENSE, SOFTWARE MAINTENANCE AND SOFTWARE

TECHNICAL SUPPORT:

B.3 CONTRACT ADMINISTRATION DATA

B.4 PRICE SCHEDULE

B.5 PERFORMANCE WORK STATEMENT (PWS)

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

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

STATUTES OR EXECUTIVE ORDERS—COMMERCIAL PRODUCTS AND

COMMERCIAL SERVICES (JAN 2025) (DEVIATION FEB 2025)

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

C.5 52.227-19 COMMERCIAL COMPUTER SOFTWARE LICENSE (DEC 2007)

C.6 VAAR 852.201-70 CONTRACTING OFFICER'S REPRESENTATIVE (DEC 2022)67

C.7 VAAR 852.203-70 COMMERCIAL ADVERTISING (MAY 2018)

C.8 VAAR 852.204-70 PERSONAL IDENTITY VERIFICATION OF

CONTRACTORRSONNEL (MAY 2020)

C.9 VAAR 852.204-71 INFORMATION AND INFORMATION SYSTEMS

SECURITY (FEB 2023)

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

2018)

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION E - SOLICITATION PROVISIONS

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

1998)

E.2 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—

COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (MAY 2024)

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B1. GOVERNING LAW CLAUSE

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.

B2. SOFTWARE LICENSE, SOFTWARE MAINTENANCE AND SOFTWARE

TECHNICAL SUPPORT:

(1). Definitions.

1. Licensee. The term “licensee” shall mean the U.S. Department of Veterans Affairs (“VA”) and is synonymous with “Government.”

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

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

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

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

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

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

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

2. The Government may use the software in a networked environment.

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

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

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

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

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

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

5. 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.3 CONTRACT ADMINISTRATION DATA

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

a. CONTRACTOR: TBD

b. GOVERNMENT: Contracting Officer 36C10B Michael Weckesser

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] As noted in Section 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.

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

AMENDMENT NO DATE

B.4 PRICE SCHEDULE

All days referenced below shall be considered calendar days, unless otherwise noted.

All items are Inspection/Acceptance/FOB Destination.

Base Period

The Period of Performance shall be three months from date of award

CLIN Description QTY/Unit of Issue

Unit Price Price

Project Management support in accordance with (IAW) Performance Work Statement Paragraph 5.1 and its sub-paragraphs found at Section B.5.

PSC Code: 7D20

This is a Firm-fixed-priced Contract Line-Item Number (CLIN). All costs associated with this CLIN and its underlying Sub-Line Item Numbers (SLINs) shall be wrapped into the costs noted for CLIN 0003.

3 Lots

(LO)

Not Separately

Priced (NSP)

NSP

0001AA

Weekly Progress Reports IAW PWS Paragraph 5.1.1.

To be delivered the Monday of each preceding week.

1 LO NSP NSP

Hardware Replacement IAW PWS Paragraph 5.2.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

3 LO NSP NSP

WIFI System Service Requirements IAW PWS Paragraph 5.3.

3 LO $_______ $_________

PSC Code: DB02

VGIA Support IAW PWS Paragraph 5.4.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

0004AA

VGIA Quarterly Utilization Report

Technical Support IAW PWS Paragraph 5.5.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

Maintenance Support IAW PWS Paragraph 5.6.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

Total Option Period $

Option Period 1

This option may be exercised by the Government IAW Federal Acquisition Regulation (FAR) 52.217-9 Option to Extend the Term of Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the VA Contracting Officer. If exercised this option shall commence immediately after expiration of the base period

CLIN Description QTY/Unit of Issue

Unit Price Price

Project Management support in accordance with (IAW) Performance Work Statement Paragraph 5.1 and its sub-paragraphs found at Section B.5.

PSC Code: 7D20

This is a Firm-fixed-priced Contract Line-Item Number (CLIN). All costs associated with this CLIN and its underlying Sub-Line Item Numbers (SLINs) shall be for CLIN 1003.

1001AA

Weekly Progress Reports IAW PWS Paragraph 5.1.1.

Hardware Replacement IAW PWS Paragraph 5.2.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

WIFI System Service Requirements IAW PWS

1 LO $_______ $_________

VGIA Support IAW PWS Paragraph 5.4.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

1004AA

VGIA Quarterly Utilization Report IAW PWS Paragraph 5.4.

To be delivered by end of Option PoP if the subsequent Option is not exercised.

Technical Support IAW PWS Paragraph 5.5.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

Maintenance Support IAW PWS Paragraph 5.6.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

Total Option Period 1 Value $

Option Period 2

This option may be exercised by the Government IAW Federal Acquisition Regulation (FAR) 52.217-9 Option to Extend the Term of Contract (MAR 2000). Work shall not commence until, and unless, a Formal modification is issued by the Contracting Officer. If exercised this option shall commence Immediately after expiration of the Option Period 1.

CLIN Description QTY/Unit of Issue

Unit Price Total Price

Project Management support in accordance with (IAW) Performance Work Statement Paragraph 5.1 and its sub-paragraphs found at Section B.5.

PSC Code: 7D20

This is a Firm-fixed-priced Contract Line-Item Number (CLIN). All costs associated with this CLIN and its underlying Sub-Line Item Numbers (SLINs) shall be wrapped into the costs noted for CLIN 2003.

2001AA

IAW PWS Paragraph 5.1.1.

Hardware Replacement IAW PWS Paragraph 5.2.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

WIFI System Service Requirements IAW PWS

VGIA Support IAW PWS Paragraph 5.4.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

2004AA

VGIA Quarterly Utilization Report IAW PWS Paragraph 5.4.

To be delivered by end of Option PoP if the subsequent Option is not exercised.

Technical Support IAW PWS Paragraph 5.5.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

Maintenance Support IAW PWS Paragraph 5.6.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be noted for CLIN 0003.

Total Option Period 2 Value $

Option Period 3

This option may be exercised by the Government IAW Federal Acquisition Regulation (FAR) 52.217-9 Option to Extend the Term of Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the VA Contracting Officer. If exercised this option shall commence immediately after expiration of Option Period 2.

CLIN Description QTY/Unit of Issue

Unit Price Total Price

Project Management support in accordance with (IAW) Performance Work Statement Paragraph 5.1 and its sub-paragraphs found at Section B.5.

PSC Code: 7D20

This is a Firm-fixed-priced Contract Line-Item Number (CLIN). All costs associated with this CLIN and its underlying Sub-Line Item Numbers (SLINs) shall be noted for CLIN 3003.

3001AA

IAW PWS Paragraph 5.1.1.

Hardware Replacement IAW PWS Paragraph 5.2.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

WIFI System Service Requirements IAW PWS

VGIA Support IAW PWS Paragraph 5.4.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

3004AA

VGIA Quarterly Utilization Report IAW PWS Paragraph 5.4.

To be delivered electronically to the VA COR on quarterly basis at the cadence set in the base period.

Technical Support IAW PWS Paragraph 5.5.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be

Maintenance Support IAW PWS Paragraph 5.6.

This is a Firm-fixed-priced CLIN. All costs associated with this CLIN and any underlying SLINs shall be noted for CLIN 0003.

Total Option 3 Period Value $

Total Base and Option Periods Value: $

B.5 PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology

VISN 17, Doris Miller VA, Waco

Patient WIFI Maintenance and Support

Date: 07/2/2025

VA-25-00083764

PWS Version Number: 1.1

1.0 BACKGROUND

The Department of Veterans Affairs (VA), Office of Information & Technology (OIT), VIS17, Doris Miller, VA Waco and Olin E. Teague, VA Temple 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.

Waco VA, Temple VA and Cedar Park OPC campuses are in need of a contractor that can provide materials, installation and maintenance service to the existing patient WIFI system at each campus. The current contract has expired, and service are being provided under a good faith services.

2.0 APPLICABLE DOCUMENTS

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

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

2. “Federal Information Security Modernization Act of 2014”

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

4. FIPS Pub 199. “Standards for Security Categorization of Federal Information and Information Systems,” February 2004

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

Information Systems,” March 2006

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

Contractors,” August 2013

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

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

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

Technology Act of 2006, Title IX, Information Security Matters

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

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

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

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

14. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” January 18, 2017

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

Information as a Strategic Resource,” July 28, 2016

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

Services (CHAMPUS)” https://www.va.gov/vapubs/index.cfm https://www.va.gov/vapubs/index.cfm http://www.va.gov/vapubs http://www.va.gov/vapubs

17. NIST SP 800-66 Rev. 1, “An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule,” October 2008

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

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

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

21. VA Handbook 6500, “Risk Management Framework for VA Information

Systems VA Information Security Program,” February 24, 2021

22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” March 12, 2019

23. VA Handbook 6500.5, “Incorporating Security and Privacy into the System Development Lifecycle,” March 22, 2010

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

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

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

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

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

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

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

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

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

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

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

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

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 2018

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)

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

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

12) Program,” March 24, 2014

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 https://www.va.gov/process/ https://www.va.gov/process/maps.asp https://www.va.gov/process/artifacts.asp https://www.va.gov/trm/TRMHomePage.aspx

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

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

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)

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

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

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

47. NIST SP 800-164, “Guidelines on Hardware-Rooted Security in Mobile

Devices (Draft),” October 2012

48. Draft National Institute of Standards and Technology Interagency Report

(NISTIR) 7981, “Mobile, PIV, and Authentication,” March 2014

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)

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)

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

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

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

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

55. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public Law 110–140), December 19, 2007

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

57. Executive Order 13834, “Efficient Federal Operations,” dated May 17, 2018

58. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August

2, 2001

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

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

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

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

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

63. “Veteran Focused Integration Process (VIP) Guide 4.0,” January 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 https://arch.idmanagement.gov/#what-is-the-ficam-architecture https://arch.idmanagement.gov/#what-is-the-ficam-architecture https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896 https://www.cisa.gov/publication/tic-30-core-guidance-documents https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

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

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

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

67. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol

Version 6 (IPv6),” November 19, 2020

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

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

3.0 SCOPE OF WORK

The Contractor shall maintain and sustain the existing WIFI service network and infrastructure (hardware and components) in accordance with the site specifications for Waco, Temple, and Cedar Park OPC. This includes product licensing, maintenance, support, programming, and testing for the existing patient WIFI in Waco, Temple VAMC and Cedar Park OPC VA Facilities.

The contractor shall provide both on site and remote support and repair to current existing hardware, software, and firewalls through the entire contract period for Waco, Temple, and Cedar Park VA facilities. The Contractor shall monitor and maintain the guest WIFI network and tune network performance to meet the requirements of this PWS. The contractor shall respond to On-Site and remote to repairs/work (Critical and/or Normal) in accordance with established service level standards noted in subsequent sections

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The Period of Performance (PoP) shall be a 3-month Base Period from Notice to Proceed (NTP), with three subsequent 1-month Option Periods, if exercised.

Work under this agreement shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO). As this contract requires on call and emergency service related to WIFI outages this work restriction may be waved as required to maintain integrity of service.

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

Under current definitions, four are set by date:

New Year's Day January 1 Juneteenth June 19 Independence Day July 4 Veterans Day November 11 https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

Christmas Day December 25

If any of the above falls on a Saturday, then Friday shall be observed as a holiday.

Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.

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

Martin Luther King's Birthday Third Monday in January Washington's Birthday Third Monday in February Memorial Day Last Monday in May Labor Day First Monday in September Columbus Day Second Monday in October Thanksgiving Fourth Thursday in November

4.2 PLACE OF PERFORMANCE

Tasks under this PWS shall be primarily performed at the Contractors facility/remote locations based upon concurrence and approval from the VA Contracting Officer's Representative. All on-site work shall be performed at the following locations:

Name Address City State Zip

Doris Miller VA Campus 4800 Memorial Drive Waco Tx 76711

Olin E. Teague Campus 1901 Veterans Memorial Drive Temple Tx 76504

Cedar Park Outpatient Clinic 1401 Medical Parkway Building C Suites 200/400 Cedar Park Tx 78613

Offsite Tasks such as network monitoring, trouble shooting, and software upgrades under this PWS shall be performed at Contractor facilities. The Contractor shall identify the Contractor’s place of performance in their proposal submission.

4.3 TRAVEL

Travel shall be in accordance with the Federal Travel Regulations (FTR) and requires advanced concurrence by the COR. Contractor travel within the local commuting area will not be reimbursed.

Travel requires advanced concurrence by the COR. Contractor travel will not be reimbursed.

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the Contractor’s approach, timeline, and tools to be used in execution of the contract. The CPMP should take the form of both a narrative and graphic format that displays the schedule, milestones, risks, and resource support detailing each site for the lifecycle of the project. The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the PWS. The initial baseline CPMP shall be concurred upon and updated in accordance with Section B or price schedule of the contract. The Contractor shall update and maintain the VA PM approved CPMP throughout the PoP.

Deliverable:

A. Contractor Project Management Plan

5.12 TECHNICAL KICKOFF MEETING

A technical kickoff meeting shall be held within 10 days after TO award. The Contractor shall coordinate the date, time, and location (can be virtual) with the Contracting Officer (CO), as the Post-Award Conference Chairperson, the VA PM, as the Co-Chairperson, the Contract Specialist (CS), and the COR. The Contractor shall provide a draft agenda to the CO and VA PM at least five (5) calendar days prior to the meeting. Upon Government approval of a 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. 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 and the following statement “As the Post-Award Conference Chairperson, I have reviewed the entirety of this presentation and assert that it is an accurate representation and summary of the discussions held during the Technical Kickoff Meeting for the Guest WIFI Services – Waco/Temple/Cedar Park VAMC.” The Contractor shall submit the final updated presentation to the CO for review and signature within three (3) 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 (3) 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.

5.1.3 REPORTING REQUIREMENTS

The Contractor shall provide the COR with reports in electronic form in Microsoft Word and Project formats. The report shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding.

The Weekly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The report shall also include an itemized list of all Information and Communication Technology (ICT) deliverables and their current Section 508 conformance status. The Contractor shall monitor performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues. The weekly progress report also contains a weekly incident section to detail the WIFI network, and any issues (to include oversight and monitoring of the installed wireless network(s) and trouble tickets received and resolution) encountered during the reporting period or adverse events, including unauthorized access attempts, security vulnerabilities, and performance problems.

Deliverables:

A. Weekly Progress Reports

5.2 HARDWARE REPLACEMENT

The Contractor shall provide and replace failed hardware components to restore WIFI services and meet uptime requirements

5.3 WIFI SYSTEM SERVICE REQUIREMENTS

The contractor shall furnish all personnel, equipment, tools, materials, transportation, management supervision, and other items and services necessary to perform all WIFI installation tasks and functions. The contractor must perform to the standards identified in the performance work statement.

The contractor shall provide ongoing support to the existing solution which includes, but is not limited to:

1. Maintain existing annual software licenses for (3) firewall appliances/hardware.

2. Maintain existing annual licensing and support renewal for FortiGate 60E for

(3) locations.

3. Provide annual support and maintain licensing for Ruckus equipment for 167 access points, 40ISX switches, SCI, and SmartZones 100 at Waco/Temple.

This number may increase based on exercise of any optional task during the life of this effort.

The contractor shall be responsible for connecting existing and new/replacement WIFI components to the existing 1G internet service provided by others. The Contractor shall not be responsible for providing the underlying internet connectivity from the source. In the event of an outage, the Contractor shall notify the site Point of Contact.

The Contractor shall also perform the following services as part of this effort:

1. The Cable Distribution System will be maintained to satisfy the digital data and voice requirements of the Department of Veterans Affairs, Veteran Integrated Service Network (VISN) 10.

2. AP (Wireless Access Point) and Cable Installation: Install at minimum Cat 6A cabling and APs in accordance with work orders, location drawings, and specifications.

3. Horizontal cabling shall be at minimum Category 6A (Cat6A) American National Standards Institute (ANSI) Telecommunications Industry Association (TIA) - 1179 Healthcare Facility Telecommunications Infrastructure.

4. Installation shall be compliant with the Building Industry Consulting Service International (BICSI) standards ANSI/NECA(National Educational Consultancy Association)/BICSI 568, Standard for Installing Commercial Building Telecommunications Cabling and ANSI/TIA -1179-A Healthcare Facility Telecommunications Infrastructure for new installations.

5. New cable installations additionally shall be compliant with TIA 568.2-D, TIA Technical Service Bulletin (TSB)-184-A, and National Fire Protection Association (NFPA) -70 Section 725.144 to prevent Power over Ethernet (PoE) heat accumulation. Provide certification reports to the COR.

6. Alternatively, new Unshielded Twisted Pair (UTP) cabling shall carry a UL listed Limited Power (LP) rating.

7. Cat6A cable shall be terminated to identified RJ-45 patch panel in IT closet and CAT6A RJ-45 jack at wall plate and labeled at both ends.

8. Use a cable analyzer to determine cable length (max cable length 90M/295 linear feet) and certify that cable meets or exceeds TIA-EIA-568-C.2.

9. Cables shall be installed in continuous lengths from origin to destination, no splices with a one-foot service loop.

10. Use existing raceways as much as possible. Cable shall be installed in accordance with manufacturer’s recommendations and best industry practices.

Existing raceways shall not be filled greater than the National Electric Code (NEC) maximum fill for the raceway type. Cables shall be supported with J hooks or cable bags every four (4) to five (5) feet whenever there is an absence of a cable tray. Any areas requiring the use of fire sealing material will conform to the ANSI/NFPA-70 FIRE SEALING / SAFETY standard. The VA, upon written request, will authorize the contractor to provide a quote to increase number or size of pathways only in the event the total pathways provided to any given area are inadequate.

11. Label patch panels in accordance with specifications and VAMC standard. Patch panel labels shall include outlet number, jack number. All label printing shall be machine generated

12. Confirm locations, including installation height, with COR.

13. Patch and finish disturbed surfaces to match existing.

14. All material, installed by the contractor, shall be new, tested, and certified.

15. Attach all AP units to ceiling grid or other prior approved location using manufacturer recommended hardware.

16. Contractor shall be proficient of the following:

• Ruckus Brand Server or compatible licenses or components, switches, and AP’s.

• Forti Gate or compatible Firewall.

• Contractor shall notify COR and IT subject matter expert of any periodic manufacture updates prior to installation throughout the life of the contract.

5.3.1 SOFTWARE AND LICENSING REQUIREMENTS

The Contractor shall be responsible for the identification of, and as required and approved by VA, the provision of any software licenses and any associated licensing maintenance required for any development, delivery, integration, operation, and/or maintenance associated with its proposed application(s), software products, software solution, and/or system including, but not limited to, any and all application(s), software and/or software products that comprise, are a part of, or integrate with the Contractor’s proposed application(s), software products, software solution, and/or system for the life of any resulting contract.

5.3.2 WEB CONTENT FILTERING

The Contractor shall implement and maintain Web content filtering so that VA can deny guest WIFI to unacceptable and inappropriate Internet content, and to best maintain performance of the network. Web content filtering shall include VA administrator-configurable options and a capability to review and modify filtering. The Contractor shall update the web content filter at the request of patient and guest users and/or VA personnel, only after approval by the VA COR. These web content filtering database updates shall be based on industry standards. The Contractor shall vet any website access requests to determine the level of risk to allowing users access to the site and advise the COR accordingly.

VA is responsible for providing a filter list to the Contractor that defines websites to be blocked. The Contractor shall update the filtering service upon receipt of the new filter list. In the event a web page is blocked, the Web Content Filtering will allow notification to the user that the web page was blocked due to VA customer web policy. This service also provides mitigation for common internet malware. The Contractor shall provide a

Web Content Filtering Report detailing the findings and any service performed. All efforts associated with this activity shall be reported to the COR in the Quarterly

Utilization Report.

5.3.3 GUEST WIFI LANDING PAGE

The Contractor shall provide an introduction page with usage agreements for acknowledgement at the time of login with information on the program, rules and restrictions and usage agreements. If no agreement acknowledgement is received from the user, access shall be denied. [Users of guest WIFI must acknowledge that they are aware of the risk of using a public network]. The Contractor shall provide a homepage at login displaying information security warning, public access information, VA non-liability disclaimer. VA will provide, to the Contractor, the information for the homepage that will be displayed upon login.

The Contractor shall design and implement a landing page for guest login (also known as a welcome, home, introduction page) that includes usage agreements and terms and conditions for acknowledgement at the time of login:

1. Rules and restrictions

2. Information security warning

3. Public network access risk information

4. VA non-liability disclaimer

The landing page operation shall require guest acceptance of guest WIFI terms and conditions before allowing guest internet access. VA will provide the Contractor all content and information to be displayed, including legal language, when a guest accesses the landing page. The Contractor shall provide other recommendations for landing page content. Final landing page content shall be determined by VA consideration of recommendations provided by the Contractor.

The Contractor shall update the guest WIFI Landing Page Software Code to keep the code current with VA security standards, which are outlined in “Attachment D Security

Information for guest WIFI Access”. The Contractor shall update the guest WIFI Landing

Page to reflect any VA-approved or VA-authorized changes to it.

The following is an example of a landing page for the Doris Miller VA Campus VAMC. A similar page will be required for the Olin E. Teague facility:

“Welcome to the Doris Miller VA Campus VAMC Guest Wireless Network A Service

VENDORCo”

To use this service, you agree to the following:

1 VENDORCo monitors the use of this system for purposes related to security management, system maintenance and system troubleshooting.

2 During monitoring, information may be examined, recorded, copied, and used for authorized purposes. If the monitoring reveals possible evidence of criminal activity, VENDORCo can provide records to law enforcement.

3 There is NO EXPECTATION OF PRIVACY in the use of the VA Guest Network as all information, including personal information, placed or sent over this network may be monitored.

4 You agree to abide by the VA Guest Network Acceptable Use Policy (Listed below).

5 Violation of the VA Guest Network Acceptable Use Policy may result in revocation of access, civil or criminal proceedings.

6 Access to this network may be disabled at any time. Your bandwidth may be limited by based on your usage and the usage of others.

The VA is not responsible for issues regarding access. Technical issues should be directed to VENDER Co help desk at 1-800-999-0000.

VA Guest Network Acceptable Use Policy

1. Attempting to access or accessing another's account, private files, or e-mail without the owner's permission; or misrepresenting oneself as another individual in electronic communication is prohibited.

2. Using the VA Guest Network to engage in conduct that interferes with others' use of guest network and/or the activities of other users is prohibited.

3. Using the VA Guest Network for commercial or profit-making purposes is prohibited.

Prohibited activity includes soliciting alms or contributions, vending, or debt collecting.

4. Using the VA Guest Network for illegal activities is prohibited. Criminal and illegal use includes but is not limited to obscenity, child pornography, threats, harassment, copyright infringement, defamation, theft, and unauthorized access.

5. Peer-to-Peer software such as KaZaa, Bearshare, or Gnutella that can be used to share files such as music, movies, or software in violation of copyright laws is prohibited on all computers connected to the VA network (including the Guest Network). The

Medical Center does not support the download or distribution of these copyrighted files and any violation of this policy will result in revocation of guest network access.

6. Use of the VA Guest Network to access gambling sites is prohibited.

7. Use of the VA Guest Network which results in a disturbance to the VA facility or impedes or disrupts the performance of official duties by government employees is prohibited.

To agree to the above and gain access to the Internet please click the ACCEPT button below.”

5.4 VGIA OPERATION

The Contractor shall provide service availability with an expected 99.8% of VGIA uptime for the areas listed in PWS Scope 3.0.

The Contractor shall be responsible for the operation of the solution ensuring that the

VGIA always meets all requirements of Section 5.4.

The Contractor shall monitor the network to verify the wireless physical requirements such as spectrum support and user density (bandwidth), antenna diversity (signal quality), and availability requirements within coverage areas are within limits specified in the solution requirements of 5.4.

The Contractor shall perform ongoing monitoring of the Radio Frequency (RF) environment, not only for potential IEEE 802.11 wireless interference, but also for all interference sources in the Industrial, Scientific, and Medical (ISM bands). Monitoring shall include Bluetooth, Zig Bee 802.15,4 and other device radio frequencies.

The Contractor shall provide and operate VGIA with no interference with other VA wireless networks. If there is conflict for wireless spectrum or physical space, the needs of VA official-use networks shall take precedence over VGIA access.

The Contractor shall monitor the typical usage of Wireless Application Protocol (WAPs).

Where…