RFP AITC PACS 36C10B25R0006_FINAL.pdf

PAGE 1 OF 89 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, &

12/12/2024

36C10B25R0006

Christian Brown christian.brown5@va.gov 848-377-5181 12-19-2024

2:00 PM EST

Department of Veterans Affairs

Technology Acquisition Center

23 Christopher Way

Eatontown, NJ 07724

X

561621

$25 Million

N/A

See Delivery Schedule

Financial Services Center

PO BOX 149971

Austin, TX 78714-8971

This Request for Proposal (RFP) is issued for Austin Information

Technology Center (AITC) Physical Access Control System (PACS)

Maintenance and Support.

See Section B.4 Price Schedule and B.5 for Performance Work

Statement

The Period of Performance shall be one 12-month base period, with four 12-month option periods.

Points of Contact:

Christian Brown, Contract Specialist christian.brown5@va.gov

Jason King, Contracting Officer jason.king6@va.gov

Period for Questions will close on 12/16/2024, 2:00PM EST. Answers will be posted via Addendum.

Jason King

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 GOVERNING LAW

B.2 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT

B.3 CONTRACT ADMINISTRATION DATA

B.4 PRICE SCHEDULE

B.5 PERFORMANCE WORK STATEMENT

SECTION C - CONTRACT CLAUSES

C.1 FEDERAL ACQUISITION REGULATION (FAR) 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 FAR 52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT

STATUES OR EXECUTIVE ORDERS—COMMERCIAL PRODUCTS AND COMMERCIAL

SERVICES (NOV 2024)

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

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

C.6 VAAR 852.239-70 SECURITY REQUIREMENTS FOR INFORMATION TECHNOLOGY

RESOURCES (FEB 2023)

C.7 VAAR 852.239-71 INFORMATION SYSTEM SECURITY PLAN AND

ACCREDITATION (FEB 2023)

C.8 VAAR 852.239-76 INFORMATION AND COMMUNICATION TECHNOLOGY

ACCESSIBILITY (FEB 2023)

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS

SECTION E - SOLICITATION PROVISIONS

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

1998)

E.2 FAR 52.204-20 PREDECESSOR OF OFFEROR (AUG 2020)

E.3 FAR 52.204-24 REPRESENTATION REGARDING CERTAIN

TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT

(NOV 2021)

E.4 FAR 52.204-26 COVERED TELECOMMUNICATIONS EQUIPMENT OR SERVICES-

REPRESENTATION (OCT 2020)

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

E.6 FAR 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS –

COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES (MAY 2024)

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

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

E.9 VAAR 852.233-70 PROTEST CONTENT/ALTERNATIVE DISPUTE RESOLUTION (SEP

2018)

E.10 VAAR 852.233-71 ALTERNATE PROTEST PROCEDURE (SEP 2018)

E.11 VAAR 852.239-75 INFORMATION AND COMMUNICATION TECHNOLOGY

ACCESSIBILITY NOTICE (FEB 2023)

E.12 BASIS FOR AWARD

E.13 PROPOSAL SUBMISSION INSTRUCTIONS

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 GOVERNING LAW

Federal law and regulations, including the Federal Acquisition Regulations (FAR), shall govern this Contract/Order. Commercial license agreements may be made a part of this Contract/Order but only if both parties expressly make them an addendum hereto, as permitted by FAR 12.212.

If the commercial license agreement is not made an addendum, it shall not apply, govern, be a part of or have any effect whatsoever on the Contract/Order; this includes, but is not limited to, any agreement embedded in the computer software (clickwrap), any agreement that is otherwise delivered with or provided to the Government with the commercial computer software or documentation (shrinkwrap), or any other license agreement otherwise referred to in any document. If a commercial license agreement is made an addendum, only those provisions addressing data rights regarding the Government’s use, duplication and disclosure of data (e.g., restricted computer software) are included and made a part of this Contract/Order, and only to the extent that those provisions are not duplicative or inconsistent with Federal law, Federal regulation, the incorporated FAR clauses and the provisions of this Contract/Order; those provisions in the commercial license agreement that do not address data rights regarding the

Government’s use, duplication and disclosure of data shall not be included or made a part of the

Contract/Order. Federal law and regulation including, without limitation, the Contract Disputes

Act (41 U.S.C. § 7101 et seq.), the Anti-Deficiency Act (31 U.S.C. § 1341 et seq.), the

Competition in Contracting Act (41 U.S.C. § 3301 et seq.), the Prompt Payment Act (31 U.S.C. §

3901 et seq.), Contracts for Data Processing or Maintenance (38 USC § 5725), and FAR clauses

52.212-4, 52.227-14, 52.227-19 shall supersede, control, and render ineffective any inconsistent, conflicting, or duplicative provision in any commercial license agreement. In the event of conflict between this clause and any provision in the Contract/Order or the commercial license agreement or elsewhere, the terms of this clause shall prevail. The Contractor shall deliver to the

Government all data first produced under this Contract/Order with unlimited rights as defined by

FAR 52.227-14. Claims of patent or copyright infringement brought against the Government as a party shall be defended by the U.S. Department of Justice (DOJ) in accordance with 28 U.S.C. §

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

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

B.2 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT

(1). Definitions.

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

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

b) Licensor. The term “licensor” shall mean the Contractor having the necessary license or ownership rights to deliver license, software maintenance and support of the computer software being acquired. The term “Contractor” is the party identified in Block 17a on the SF1449. If the Contractor is a reseller and not the Licensor, the Contractor remains responsible for performance under this Contract/Order.

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

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

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

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

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

(2). Software License.

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

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

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

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

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

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

(3). Software Maintenance and/or Technical Support.

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

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

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

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

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

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

(4). Disabling Software Code.

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

Contractor agrees to indemnify the Government for all damages suffered as a result of a disabling caused by such code, and the contractor agrees to remove such code upon the

Government’s request at no extra cost to the Government. Inability of the Contractor to remove the disabling software code will be considered an inexcusable delay and a material breach of contract, and the Government may exercise its right to terminate for cause. In addition, the

Government is permitted to remove the code as it deems appropriate and charge the Contractor for consideration for the time and effort expended in removing the code.

(5). Manuals and Publications.

Upon Government request, the Contractor shall furnish the most current version of the user manual and publications for all products/services provided under this Contract/Order at no cost.

http://www.cpars.gov/

B.3 CONTRACT ADMINISTRATION DATA

(Continuation from Standard Form 1449, block 18A)

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

a. CONTRACTOR:

Name of Company:

Address:

Point of Contact:

Phone Number:

Email Address:

Company Business Size & Status:

Unique Entity Identifier (UEI):

b. GOVERNMENT: Contracting Officer 36C10B, Jason King

Technology Acquisition Center

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

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly ☐

b. Semi-Annually ☐

c. Other ☒ Upon Government acceptance of deliverables in accordance with B.4, Price Schedule and in accordance with Section

B.5, Performance Work Statement

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

Payment Requests.

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

AMENDMENT NO DATE

6. Purchase Order for Billing Purposes: TBD

☒ 52.232-33, Payment by Electronic Funds Transfer—System for Award Management, or

B.4 PRICE SCHEDULE

Vendors are instructed to complete Section B.4: Price Schedule and submit with their quote.

Vendors are cautioned that alterations to the line items as specified below may render quotes unacceptable. All questions shall be directed to the Contract Specialist, Christian Brown, christian.brown5@va.gov, and Contracting Officer, Jason King, jason.king@va.gov prior to the closing date and time specified in the Request for Proposal (RFP).

Any resulting contract will be awarded on a firm-fixed-price basis as defined by Federal

Acquisition Regulation Subpart 16.202. Accordingly, the Contractor shall ensure that any and all costs associated with the Contractor’s proposed application(s), software products, software solution, and/or system, shall be included in the Contractor’s proposed firm-fixed price, and shall serve as the Contractor’s firm-fixed price for the life of any resulting contract. No additional costs or fees relative to the Contractor’s proposed application(s), software products, software solution, and/or system including, but not limited to, licensing costs and any associated licensing maintenance required for the development, delivery, integration, operation, and/or maintenance of the Contractor’s proposed solution will be allowed, accepted, and/or paid by the Government.

All deliverables will be destination inspection, acceptance, and F.O.B.

Days used below refer to calendar days unless otherwise stated. Deliverables with due dates falling on a weekend or holiday shall be submitted the following Government workday after the weekend or holiday.

Electronic submission to: VA Project Manager, Contracting Officer, and Contracting Officer’s

Representative

Product Service Code for the following CLINs/SLINs is J063: Maintenance, Repair, and

Rebuilding of Equipment- Alarm, Signal, and Security Detection Systems

Base Period

The period of performance for this effort shall be 12 months from date of award.

CLIN Description Qty Unit Unit Price Extended Price

Project Management In

Accordance with (IAW) AITC

PACS Performance Work

Statement (PWS) paragraph

5.1 and all subparagraphs.

This Firm Fixed Price (FFP)

Contract Line Item Number

(CLIN) includes all Labor, Materials, Project

Management and Deliverables required for successful completion of the services detailed in PWS paragraphs

12 MO $ $

mailto:christian.brown5@va.gov mailto:jason.king@va.gov

5.1 inclusive of all subparagraphs.

Period of Performance (PoP):

12 months from date of award

0001AA

Contractor Project Management

Plan IAW PWS paragraph 5.1.1.

Due 30 days after award and updated monthly thereafter

1 LO NSP NSP

0001AB

Monthly Progress and Time-of-

Service Log IAW PWS paragraph 5.1.2.

Due the fifth day of each month throughout the PoP.

1 LO NSP NSP

0001AC

Contractor Staff Roster IAW

PWS paragraph 6.2.2.

Due 3 days after contract award and updated as required throughout the PoP.

1 LO NSP NSP

Maintenance, Support and

Repair IAW AITC PACS

PWS paragraph 5.2.

This FFP CLIN includes all

Labor, Materials, Project

Management and Deliverables required for successful completion of the services detailed in PWS paragraph

5.2.

PoP: 12 months from date of award

12 MO $ $

0002AA

Site Visit Report IAW AITC

PACS PWS paragraph 5.2.

Due quarterly throughout the

PoP.

1 LO NSP NSP

Software House Software

Support IAW PWS paragraph

1 LO $ $

EverRun Software Support IAW

PWS paragraph 5.2

1 LO $ $

award.

Base Period Total $

Option Period One

This 12-month option period may be exercised in accordance with FAR 52.217-9, Option to Extend the

Term of the Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. If exercised, this option shall commence immediately after expiration of the Base Period.

CLIN Description Qty Unit Unit Price Extended Price

Project Management In

Accordance with (IAW)

Performance Work Statement

(PWS) paragraph 5.1 and all

(CLIN) includes all Labor, Materials, Project Management and Deliverables required for successful completion of the services detailed in PWS paragraphs 5.1 inclusive of all

PoP: 12 months after expiration of the base period

12 MO $ $

1001AA

Due 30 days after exercise of

Option Period One and updated monthly thereafter

1 LO NSP NSP

1001AB

Monthly Progress and Time-of-

Service Log IAW PWS paragraph 5.1.2.

Due the fifth day of each month throughout the PoP.

1 LO NSP NSP

1001AC

Updated as required.

1 LO NSP NSP

Maintenance, Support and

Repair IAW PWS paragraph

This FFP CLIN includes all

Labor, Materials, Project

Management and Deliverables required for successful

12 MO $ $

completion of the services detailed in PWS paragraph 5.2.

expiration of base period

1002AA

Due quarterly throughout the

PoP.

1 LO NSP NSP

Software House Software

1 LO $ $

EverRun Software Support IAW

Option Period One Total $

Option Period Two

This 12-month option period may be exercised in accordance with FAR 52.217-9, Option to Extend the

Term of the Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. If exercised, this option shall commence immediately after expiration of Option Period One.

CLIN Description Qty Unit Unit Price Extended Price

Project Management In

Accordance with (IAW) AITC

PACS Performance Work

(CLIN) includes all Labor, Materials, Project Management and Deliverables required for successful completion of the services detailed in PWS

12 MO $ $

PoP: 12 months after expiration of Option Period

One

2001AA

Option Period Two and updated monthly thereafter

1 LO NSP NSP

2001AB

Monthly Progress and Time-of-

Service Log IAW PWS paragraph 5.1.2.

Due the fifth day of each month throughout the PoP.

1 LO NSP NSP

2001AC

Maintenance, Support and

Repair IAW AITC PACS PWS paragraph 5.2.

expiration of Option Period

One

12 MO $ $

2002AA

Due quarterly throughout the PoP.

Software House Software

1 LO $ $

Option Period Two Total $

Option Period Three

Term of the Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. If exercised, this option shall commence immediately after expiration of Option Period Two.

CLIN Description Qty Unit Unit Price Extended Price

Project Management In

Accordance with (IAW) AITC

PACS Performance Work

(CLIN) includes all Labor, Materials, Project Management and Deliverables required for successful completion of the services detailed in PWS

Two

12 MO $ $

3001AA

Option Period Three and updated monthly thereafter

1 LO NSP NSP

3001AB

Monthly Progress and Time-of-

Service Log IAW PWS paragraph 5.1.2.

Due the fifth day of each month throughout the PoP.

1 LO NSP NSP

3001AC

Maintenance, Support and

Repair IAW AITC PACS PWS paragraph 5.2.

Two

12 MO $ $

3002AA

Software House Software

1 LO $ $

Option Period Three Total $

Option Period Four

Term of the Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. If exercised, this option shall commence immediately after expiration of Option Period Three.

CLIN Description Qty Unit Unit Price Extended Price

Project Management In

Accordance with (IAW) AITC

PACS Performance Work

(CLIN) includes all Labor, Materials, Project

Management and Deliverables required for successful completion of the services detailed in PWS paragraphs

5.1 inclusive of all

Three

12 MO $ $

4001AA

Option Period Four and updated monthly thereafter

4001AB

Monthly Progress and Time-of-

Service Log IAW PWS paragraph 5.1.2.

Due the fifth day of each month throughout the PoP.

1 LO NSP NSP

4001AC

Maintenance, Support and

Repair IAW AITC PACS

PWS paragraph 5.2.

Three

12 MO $ $

4002AA

Software House Software

1 LO $ $

1 LO $ $

Option Period Four Total $

Total Contract Price $

B.5 PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology

Austin Information Technology Center

AITC Physical Access Control System (PACS)

Maintenance Contract

Date: 3/26/2024

TAC- 24-00008651

PWS Version Number: 1.1

1.0 BACKGROUND

The mission of the Department of Veterans Affairs (VA), Office of Information & Technology

(OI&T), Austin Information Technology Center (VA-AITC) is to provide benefits and services to Veterans of the United States. In meeting these goals, OI&T 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.

This contract is for a VA-AITC PACS 24/7 maintenance contract to respond to Security Devices maintenance and repairs.

2.0 APPLICABLE DOCUMENTS

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

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

2002”

2. “Federal Information Security Modernization Act of 2014”

3. Federal Information Processing Standards (FIPS) Publication 140-2, “Security

Requirements for Cryptographic Modules”

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

Information Systems,” February 2004

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

Information Systems,” March 2006

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

Contractors,” August 2013

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

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

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

Act of 2006, Title IX, Information Security Matters

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

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

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

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

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

Guidelines,” January 18, 2017

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

Information as a Strategic Resource,” July 28, 2016

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

Services (CHAMPUS)”

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

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

October 2008

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

19. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004 https://www.va.gov/vapubs/index.cfm https://www.va.gov/vapubs/index.cfm http://www.va.gov/vapubs http://www.va.gov/vapubs

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, 2011

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, 2016

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

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

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

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

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

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

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, 2018 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

3.0 SCOPE OF WORK

The Contractor shall provide 24/7 support and maintain the existing Physical Access Control

Systems (PACS) and Closed-Circuit Television Video (CCTV) systems installed at the AITC, including providing brand name Software House C-Cure 9000 and EverRun Software support license agreements. The Contractor shall manage a service request response system for PACS and CCTV maintenance requests. The Contractor shall employ maintenance personnel which are trained and certified in the use and operation of all PACS and CCTV equipment located within the facility and listed Attachment 001 - Equipment List herein, prior to conducting any work at the AITC.

The Contractor shall provide maintenance repairs and support for the AITC PACS and CCTV located at 1615 Woodward Street, Austin, Texas. The Contractor shall provide all resources necessary to maintain and repair the existing PACS and CCTV systems, furnish all labor, supervision, equipment, tools, materials, supplies, travel and transportation necessary to provide

PACS and CCTV systems maintenance and repairs. Repair and replacement parts shall be included at no additional cost to the Government. Systems functionality shall be achieved upon completion of the first service call. Functionality is defined as a working system as designed but may be accomplished with any part available to the Technician at the time of service. Only in an even where repair is not possible during service, a loaner (or equal) part may be used to regain system functionality.

The Contractor must be Enterprise Software House Dealer/Distributor and master technician certified and Avigilon Camera/computer server certified. Documentation of each must be provided. Due to requirement of 24/7 support Contractor must have local representatives that can satisfy required the response time for repairs, as defined in paragraph 5 below.

4.0 PERFORMANCE DETAILS

PERFORMANCE PERIOD

The Period of Performance (PoP) shall be one 12-month base period, with four (4) 12-month

Option Periods.

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

There are 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 Thursday in November

PLACE OF PERFORMANCE

When an issue related to the duties of this contract under this PWS arises, tasks shall be performed at 1615 Woodward Street, Austin, TX 78772.

TRAVEL

The Government anticipates local travel under this effort to perform the tasks associated with the effort. Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government.

5.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the

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

Deliverable:

A. Contractor Project Management Plan

5.1.2 REPORTING REQUIREMENTS

The Contractor shall provide the Contracting Officer’s Representative (COR) with Monthly

Progress Reports in electronic form in Microsoft Word and Project formats. The Monthly

Progress Report shall include the following: a description of services calls completed; open issues or concerns; record of equipment that has been replaced; and a summation of weekly reports. The Monthly Progress 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 Week.

The Contractor shall keep detailed comprehensive records of all maintenance and repair.

Records shall include all equipment that has been replaced. The Contractor shall include this information within the Monthly Progress Report as a separate document which is to be entitled

“Time-of-Service Log”.

The Monthly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The report shall also include an itemized list of all

Information and Communication Technology (ICT) deliverables and their current Section 508 conformance status. The Contractor shall monitor performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

The Monthly Progress Report shall also include a Time-of-Service log that includes the following:

• What type of work (Inspection, Service, Repair)

• What was serviced (Door number or Camera Number, serial number of part)

• When the work was started

• When the work was completed

• Status of the work (completed, still in progress, waiting on parts)

• What technician performed the work

Deliverables:

A. Time-of-Service Log

B. Monthly Progress Report

PACS MAINTENANCE AND SUPPORT

The Contractor shall obtain all necessary equipment, parts, manufacturer's specifications, and drawings to manage the current PACS and provide CCTV maintenance and repair as required by this PWS; See equipment list in Section D, Attachment 001 – VA Equipment List. The

Contractor shall maintain an on-site inventory mix of appropriate replacement parts necessary for the security equipment. Replacement parts shall be included at no additional cost to the

Government. The Contractor shall provide non-repairable items to the COR for turn in and accountability. All replaced equipment shall be property of the VA.

The Contractor shall repair or replace any PACS and/or CCTV equipment at Attachment 001, as necessary to keep equipment fully functional and operating in accordance with manufacturer’s specifications. The Contractor shall ensure that all PACS and CCTV equipment is properly configured and setup to achieve internet connectivity for all AITC servers connected to the

PACS and CCTV system.

The Contractor shall provide the Government COR with the Contractor’s technical support number and one Point of Contact (POC) for service and account representation. POC shall provide customer service to VA for all questions or concerns related to this requirement.

The Contractor shall provide a maintenance “return to service” level of response with a technician on-site to resolve all failures within eight hours after the VA representative calls the

Contractor’s technical support number. The Contractor shall provide technical support Monday through Friday, from 8:00 A.M. through 5:00 P.M. Central Standard Time (CST). PACS and/or

CCTV operating systems must be fully functional upon completion of service call.

The Contractor shall perform maintenance services Monday through Friday during normal business hours, 8:00 A.M. through 5:00 P.M. CST, and the Contractor shall start no later than

1:00 P.M. CST. For outdoor surveillance camera repair and/or replacement, a boom lift will be required to access the cameras after business hours. Outdoor surveillance cameras are an estimated 20-25 feet high on light poles in the parking lot.

After business hours repair or services may be required by the Government.

This shall be effective during non-business hours. Emergency response time shall be within four hours. Service will generally be requested by a service ticket signed by the COR; however, the

CO or COR may designate in writing other Government employees and/or contractors authorized to request services and sign service tickets. The CO, COR, or other designated Government representative may direct the Contractor to perform the work during Holidays and outside of normal, 8:00 A.M. through 5:00 P.M. CST, business hours.

The Contractor shall advise the COR of potential delays in completion of any aspects of the repair and provide recommendations on actions necessary for keeping the task on schedule.

The Contractor shall perform quarterly preventive maintenance on the PACS and CCTV systems during the contract maintenance period. This shall include the manual inspecting and testing of all PACS and CCTV components with inspection/testing reports on a regular basis in accordance with manufacturer recommendations. Also, the maintenance shall include site visits required to modify or replace any component of the PACS and/or CCTV system. The Contractor shall provide to the VA Security Officer or COR, a site visit report listing all updates and corrective actions performed during site visit. The Contractor shall verify the operation of the systems with

VA Security or COR upon completion of work.

The Contractor shall maintain a current license and/or license agreement with Software House.

The Contractor shall be C-Cure 9000 and Avigilon Camera/computer server certified.

The Contractor shall be an Enterprise Software House Dealer/Distributor and provide EverRun software support.

The Contractor shall have a Software House Certified/trained, Master Enterprise technician on staff for this contract at all times.

A. Site Visit Report

OPTION PERIOD ONE

The Contractor shall provide all the tasks and services identified in Sections 5.1 and 5.2 throughout Option Period One.

OPTION PERIOD TWO

The Contractor shall provide all the tasks and services identified in Sections 5.1 and 5.2 throughout Option Period Two.

5.5 OPTION PERIOD THREE

The Contractor shall provide all the tasks and services identified in Sections 5.1 and 5.2 throughout Option Period Three.

5.6 OPTION PERIOD FOUR

The Contractor shall provide all the tasks and services identified in Sections 5.1 and 5.2 throughout Option Period Four.

6.0 GENERAL REQUIREMENTS

ENTERPRISE AND IT FRAMEWORK

6.1.1 VA TECHNICAL REFERENCE MODEL

The Contractor shall support the VA enterprise management framework. In association with the framework, the Contractor shall comply with OIT Technical Reference Model (VA TRM). The

VA TRM is one component within the overall Enterprise Architecture (EA) that establishes a common vocabulary and structure for describing the information technology used to develop, operate, and maintain enterprise applications. Moreover, the VA TRM, which includes the

Standards Profile and Product List, serves as a technology roadmap and tool for supporting OIT.

Architecture & Engineering Services (AES) has overall responsibility for the VA TRM.

6.1.2 FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT

(FICAM)

The Contractor shall ensure Commercial Off-The-Shelf (COTS) product(s), software configuration and customization, and/or new software are Personal Identity Verification (PIV) card-enabled by accepting HSPD-12 PIV credentials using VA Enterprise Technical Architecture

(ETA), https://www.ea.oit.va.gov/EAOIT/VA_EA/Enterprise_Technical_Architecture.asp, and

VA Identity and Access Management (IAM) approved enterprise design and integration patterns, https://www.oit.va.gov/library/recurring/edp/index.cfm. The Contractor shall ensure all

Contractor delivered applications and systems comply with the VA Identity, Credential, and

Access Management policies and guidelines set forth in VA Handbook 6510 VA Identity and

Access Management, VA Handbook 0735 Homeland Security Presidential Directive 12 (HSPD-

12) Program, and align with the Federal Identity, Credential, and Access Management Roadmap and Implementation Guidance v2.0.

The Contractor shall ensure all Contractor delivered applications and systems provide user authentication services compliant with the National Institute of Standards and Technology

(NIST) Special Publication (SP) 800-63-3, VA Handbook 6500 Appendix F, “VA System

Security Controls”, and VA IAM enterprise requirements for direct, assertion based authentication, and/or trust based authentication, as determined by the design and integration patterns. Direct authentication at a minimum must include Public Key Infrastructure (PKI) based authentication supportive of PIV card and/or Common Access Card (CAC), as determined by the business need.

The Contractor shall ensure all Contractor delivered applications and systems conform to the specific Identity and Access Management PIV requirements set forth in the Office of

Management and Budget (OMB) Memoranda M-05-24, M-19-17, and NIST Federal Information

Processing Standard (FIPS) 201-2. OMB Memoranda M-05-24 and M-19-17 can be found at:

https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2005/m05-24.pdf, and https://www.whitehouse.gov/wp-content/uploads/2019/05/M-19-17.pdf respectively. Contractor https://www.ea.oit.va.gov/EAOIT/VA_EA/Enterprise_Technical_Architecture.asp https://www.oit.va.gov/library/recurring/edp/index.cfm https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2005/m05-24.pdf https://www.whitehouse.gov/wp-content/uploads/2019/05/M-19-17.pdf delivered applications and systems shall be on the FIPS 201-2 Approved Product List (APL). If the Contractor delivered application and system is not on the APL, the Contractor shall be responsible for taking the application and system through the FIPS 201 Evaluation Program.

The Contractor shall ensure all Contractor delivered applications and systems support:

1. Automated provisioning and are able to use enterprise provisioning service.

2. Interfacing with VA’s Master Person Index (MPI) to provision identity attributes, if the solution relies on VA user identities. MPI is the authoritative source for VA user identity data.

3. The VA defined unique identity (Secure Identifier [SEC ID] / Integrated Control Number

[ICN]).

4. Multiple authenticators for a given identity and authenticators at every Authenticator

Assurance Level (AAL) appropriate for the solution.

5. Identity proofing for each Identity Assurance Level (IAL) appropriate for the solution.

6. Federation for each Federation Assurance Level (FAL) appropriate for the solution, if applicable.

7. Two-factor authentication (2FA) through an applicable design pattern as outlined in VA

Enterprise Design Patterns.

8. A Security Assertion Markup Language (SAML) implementation if the solution relies on assertion-based authentication. Additional assertion implementations, besides the required SAML assertion, may be provided as long as they are compliant with NIST SP

800-63-3 guidelines.

9. Authentication/account binding based on trusted Hypertext Transfer Protocol (HTTP) headers if the solution relies on Trust based authentication.

10. Role Based Access Control.

11. Auditing and reporting capabilities.

12. Compliance with VIEWS 00155984, PIV Logical Access Policy Clarification https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896.

The required Assurance Levels for this specific effort are Identity Assurance Level 3, Authenticator Assurance Level 3, and Federation Assurance Level 3.

6.1.3 INTERNET PROTOCOL VERSION 6 (IPV6)

The Contractor solution shall support Internet Protocol Version 6 (IPv6) based upon the memo issued by the Office of Management and Budget (OMB) on November 19, 2020

(https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf). IPv6 technology, in accordance with the USGv6 Program (https://www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1), NIST Special Publication (SP) 500-267B Revision 1 “USGv6

Profile” (https://doi.org/10.6028/NIST.SP.500-267Br1), and NIST SP 800-119 “Guidelines for the Secure Deployment of IPv6” (https://doi.org/10.6028/NIST.SP.800-119), compliance shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. In addition to the above requirements, all devices shall support native IPv6 and dual stack (IPv6 / IPv4) connectivity without additional memory or other resources being provided by the Government, so that they can function in a mixed environment. All public/external facing servers and services (e.g. web, email, DNS, ISP services, etc.) shall support native IPv6 and dual stack (IPv6 / IPv4) users and all internal infrastructure and applications shall communicate using native IPv6 and dual stack (IPv6 / IPv4) operations.

https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896 https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf file://///R04.med.va.gov/V03/EAS/Users/vhaeasWymbsk/TEMPLATES--NEW%20TAC%20PROCESS/PWS%20TEMPLATE%20(DO%20NOT%20TOUCH)%20-%20In%20Process%20Revisions/DO%20NOT%20TOUCH%20(next%20version/IPv6/(https:/www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1 file://///R04.med.va.gov/V03/EAS/Users/vhaeasWymbsk/TEMPLATES--NEW%20TAC%20PROCESS/PWS%20TEMPLATE%20(DO%20NOT%20TOUCH)%20-%20In%20Process%20Revisions/DO%20NOT%20TOUCH%20(next%20version/IPv6/(https:/www.nist.gov/programs-projects/usgv6-program/usgv6-revision-1 https://doi.org/10.6028/NIST.SP.500-267Br1 https://doi.org/10.6028/NIST.SP.800-119

6.1.4 TRUSTED…