C03 - NNG15SD27B 36C10B26F0302 both parties signed.pdf

PAGE 1 OF1. 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.19.

ITEM NO.

20.

SCHEDULE OF SUPPLIES/SERVICES

21.

QUANTITY

22.

UNIT

23.

UNIT PRICE

24.

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

F367478-26-0000189

NNG15SD27B

36C10B26F0302

AWARDED:

EFFECTIVE:

See Block 16C 36C10B26Q0610

Jennifer McCloud/Jennifer.McCloud@va.gov 915-564-6100 ext 2086 08-05-2026

11:59 PM EDTEDT

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

X 100

X

541519

150 Employees

N/A

See Delivery Schedule

Eatontown NJ 07724

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

4Y8H0 1

V3GATE, LLC

V

555 MIDDLE CREEK PKWY UNIT 120

PHONE: FAX:COLORADO SPRINGS CO 80921

EPHONE NO :UEIUEI J4KHM5JY79E3

Department of Veterans Affairs Technology Acquisition Center Financial Services Center PO Box 149971 Austin TX 78714-8971

ES/SERVICES QU

See CONTINUATION Page

Puppet Enterprise Software

See Continuation Pages

$85,810.00VACO-2026—4539XRDB-S1991000-S18760010—INFTECSERVS----233102-

FFACTIVITIES---787442301-00-FRNCHFND

X X

X ___________ 1 ________________________________ARD OF CONTRACT

SET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

Edgar Alonso-BernalEdgar Alonso Bernal

EDGAR ALONSO-BERNAL

2026.08.13 14:42:54 -05'00'

Christopher Hagerman, COO 8/13/2026

NASA SEWP: NNG15SD27B

Order Number: 36C10B26F0302

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 SCHEDULE OF SUPPLIES AND SERVICES

1. This is a Puppet Enterprise software Brand Name requirement. All requirements shall be in accordance with the Performance Work Statement (PWS) provided in Section D titled Puppet Enterprise software.

2. Period of Performance: August 14, 2026 – August 13, 2027 Option Period 1: August 14, 2027 – August 13, 2028 Option Period 2: August 14, 2028 – August 13, 2029 Option Period 3: August 14, 2029 – August 13, 2030

3. ARM Number: 200980

4. IFAM PO#: 36C10B26F0302

5. Inspection/Acceptance/FOB: Destination

Item No. Description of Supplies Qty Unit Unit Price Amount 0001 Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription;

Part No.: PECD1499S

PSC: DA10

500 EA $171.62 $85,810.00

0002 Description: Puppet Ent./Cont.

Delivery Jumpstart: Basic impl.

Pkg. incl. up to 80 hrs.;

Part No.: CD4PE_JSBasic

PSC: DA10

1 EA NA NA

0003 The Contractor shall fill in blocks 15-31. The Contractor shall provide Original Equipment Manufacturer (OEM) confirmation that all software support or licenses have been purchased. The Contractor shall provide service call instructions to include all information required to obtain

NSP NSP NSP NSP

maintenance, support or licenses.

BASE PERIOD OPTIONAL

CLIN IAW 52.217-7 Option for Increased Quantity-Separately Priced Line Item

0004 Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription; Part No.:

PECD1499S

200 EA $171.62 $34,324.00

Base Year Total $120,134.00 Option Year 1: IAW FAR 52.217-9 OPTION TO EXTEND THE TERM OF THE

CONTRACT

1001 Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription.

Part No.: PECD1499S

PSC: DA10

500 EA $180.78 $90,390.00

1002 The Contractor shall provide Original Equipment Manufacturer (OEM) confirmation that all software support or licenses have been purchased. The Contractor shall provide service call instructions to include all information required to obtain maintenance, support or licenses.

NSP NSP NSP NSP

OY1 OPTIONAL CLIN IAW

52.217-7 Option for Increased Quantity-Separately Priced Line Item

1003 Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription; Part No.:

PECD1499S

200 EA $180.78 $35,156.00

Option Year 1 Total $126,546.00 Option Year 2: IAW FAR 52.217-9 OPTION TO EXTEND THE TERM OF THE

CONTRACT

2001 Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription.

Part No.: PECD1499S

PSC: DA10

500 EA $189.93 $94,965.00

2002 The Contractor shall provide Original Equipment Manufacturer (OEM) confirmation that all software support or licenses have been purchased. The Contractor shall provide service call instructions to include all information required to obtain maintenance, support or licenses.

NSP NSP NSP NSP

OY2 OPTIONAL CLIN IAW

52.217-7 Option for Increased Quantity-Separately Priced Line Item

2003 Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription; Part No.:

PECD1499S

200 EA $189.94 $37,988.00

Option Year 2 Total $132,953.00 Option Year 3: IAW FAR 52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (Mar 2000) 3001 Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription.

Part No.: PECD1499S

PSC: DA10

500 EA $199.09 $99,545.00

3002 The Contractor shall provide Original Equipment Manufacturer (OEM) confirmation that all software support or licenses have been purchased. The Contractor shall provide service call instructions to include all information required to obtain maintenance, support or licenses.

NSP NSP NSP NSP

OY3 OPTIONAL CLIN IAW

52.217-7 Option for Increased Quantity-Separately Priced Line Item

3003 Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription; Part No.:

PECD1499S

200 EA $199.09 $39,818.00

Option Year 3 Total $139,363.00 Total Contract Value $518,996.00

Governing Law Clause

Federal law and regulations, including the Revolutionary Federal Acquisition Regulation (FAR) Overhaul (RFO), 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. 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 RFO 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), Source Code Harmonization and Reuse in Information Technology Act “SHARE IT Act” (P.L. 118-187), and RFO clauses 52.212-4, 52.227- 14 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 RFO 52.227-14, this includes any custom code developed for the purpose of performing under this contract. 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.

SOFTWARE LICENSE, SOFTWARE MAINTENANCE AND SOFTWARE 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) All limitations of software usage are expressly stated in the Schedule of Supplies/Services and the Performance Work Statement/Product Description.

d) The commercial computer software delivered under this contract may not be used, reproduced, or disclosed by the Government except as provided below or as expressly stated otherwise in this contract. The commercial computer software may be-

i. Used or copied for use with the computer(s) for which it was acquired, including use at any Government installation or agency to which the computer(s) may be transferred;

ii. Used or copied for use with a backup computer if any computer for which it was acquired is inoperative;

iii. Reproduced for safekeeping (archives) or backup purposes;

iv. Modified, adapted, or combined with other computer software;

v. Disclosed to and reproduced for use by support service Contractors or their subcontractors, subject to the same restrictions set forth in this contract; and

vi. Used or copied for use with a replacement computer.

e) Unauthorized Obligations.

i. Except as stated in paragraph (ii), when any supply or service acquired under this contract is subject to any commercial supplier agreement (as defined in 502.101) that includes any language, provision, or clause requiring the Government to pay any future fees, penalties, interest, legal costs or to indemnify the Contractor or any person or entity for damages, costs, fees, or any other loss or liability that would create an Anti-Deficiency Act violation ( 31 U.S.C.

1341), the following shall govern:

1) Any such language, provision, or clause is unenforceable against the Government.

2) Neither the Government nor any Government authorized end user shall be deemed to have agreed to such clause by virtue of it appearing in the commercial supplier agreement. If the commercial supplier agreement is invoked through an “I agree” click box or other comparable mechanism (e.g., “click-wrap” or “browse-wrap” agreements), execution does not bind the Government or any Government authorized end user to such clause.

3) Any such language, provision, or clause is deemed to be stricken from the commercial supplier agreement.

ii. Paragraph (u)(1) of this clause does not apply to indemnification or any other payment by the Government that is expressly authorized by statute and specifically authorized under applicable agency regulations and procedures.

f) Commercial supplier agreements unenforceable clauses.

i. This agreement is a part of a contract between the commercial supplier and the U.S. Government for the acquisition of the supply or service that necessitates a license or other similar legal instrument (including all contracts, task orders, and delivery orders under RFO 12).

ii. End user. This agreement shall bind the ordering activity as end user but shall not operate to bind a Government employee or person acting on behalf of the Government in his or her personal capacity.

iii. Law and disputes. This agreement is governed by Federal law. Any language purporting to subject the U.S.

Government to the laws of a U.S. state, U.S. territory, district, or municipality, or a foreign nation, except where Federal law expressly provides for the application of such laws, is hereby deleted.

1) Any language requiring dispute resolution in a specific forum or venue that is different from that prescribed by applicable Federal law is hereby deleted. Any dispute regarding the license grant or usage limitations shall be resolved in accordance with the Disputes Clause incorporated in RFO 52.212-4(e).

2) Any language prescribing a different time period for bringing an action than that prescribed by applicable Federal law in relation to a dispute is hereby deleted.

3) Continued performance. The supplier or licensor shall not unilaterally revoke, terminate or suspend any rights granted to the Government except as allowed by this contract. If the supplier or licensor believes the ordering activity to be in breach of the agreement, it shall pursue its rights under the Contract Disputes Act or other applicable Federal statute while continuing.

4) Arbitration; equitable or injunctive relief. In the event of a claim or dispute arising under or relating to this agreement, a binding arbitration shall not be used unless specifically authorized by agency guidance, and equitable or injunctive relief, including the award of attorney fees, costs or interest, may be awarded against the U.S. Government only when explicitly provided by statute (e.g., Prompt Payment Act or Equal Access to Justice Act).

iv. Updating terms. After award, the contractor may unilaterally revise commercial supplier agreement terms if they are not material. A material change is defined as:

1) Terms that change Government rights or obligations;

2) Terms that increase Government prices;

3) Terms that decrease overall level of service; or

4) Terms that limit any other Government right addressed elsewhere in this contract.

5) For revisions that will materially change the terms of the contract, the revised commercial supplier agreement must be incorporated into the contract using a bilateral modification.

6) Any agreement license terms or conditions unilaterally revised subsequent to award that are inconsistent with any material term or provision of this contract shall not be enforceable against the Government, and the Government shall not be deemed to have consented to them.

v. No automatic renewals. If any license or service tied to periodic payment is provided under this agreement (e.g., annual software maintenance or annual lease term), such license or service shall not renew automatically upon expiration of its current term without prior express consent by an authorized Government representative.

vi. Indemnification. Any clause of this agreement requiring the commercial supplier or licensor to defend or indemnify the end user is hereby amended to provide that the U.S.

Department of Justice has the sole right to represent the United States in any such action, in accordance with 28 U.S.C. 516.

vii. Audits. Any clause of this agreement permitting the commercial supplier or licensor to audit the end user's compliance with this agreement is hereby amended as follows:

1) Discrepancies found in an audit may result in a charge by the commercial supplier or licensor to the ordering activity. Any resulting invoice must comply with the proper invoicing requirements specified in the underlying Government contract or order.

2) This charge, if disputed by the ordering activity, will be resolved in accordance with RFO 52.212-4(e); no payment obligation shall arise on the part of the ordering activity until the conclusion of the dispute process.

3) Any audit requested by the contractor will be performed at the contractor's expense, without reimbursement by the Government.

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

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

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

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

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

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

(4). Disabling Software Code.

The Government requires delivery of computer software that does not contain any code that will, upon the occurrence or the nonoccurrence of any event, disable the software. Such code includes but is not limited to a computer virus, restrictive key, node lock, time-out, or other function, whether implemented by electronic, mechanical, or other means, which limits or hinders the use or access to any computer software based on residency on a specific hardware configuration, frequency of duration of use, or other limiting criteria. If any such disabling code is present, the Contractor agrees to indemnify the Government for all damages suffered as a result of a disabling caused by such code, and the contractor agrees to remove such code upon the Government’s request at no extra cost to the Government. Inability of the Contractor to remove the disabling software code will be considered an inexcusable delay and a material breach of contract, and the Government may exercise its right to terminate for cause. In addition, the Government is permitted to remove the code as it deems appropriate and charge the Contractor for consideration for the time and effort expended in removing the code.

(5). Manuals and Publications.

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

B.2 CONTRACT ADMINISTRATION DATA

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

a. CONTRACTOR: See Block 17a

b. GOVERNMENT: Contracting Officer - See Block 31b Department of Veterans Affairs Technology Acquisition Center-Austin 23 Christopher Way Eatontown, NJ 07724

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

[X] 52.232-33, Payment by Electronic Funds Transfer—System for Award Management, or

[] 52.232-36, Payment by Third Party

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly []

b. Semi-Annually []

c. Other [X – Upon acceptance]

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.

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

B.3 ACCOUNTING AND APPROPRIATION DATA

Funds in the amount of $85,810 are obligated on Purchase Order (PO) Number 36C10B26F0302 to pay for products/services on Contract Line-Item Numbers (CLIN) 0001-0003. The Contractor shall reference PO Number 36C10B26F0302 and CLIN on all invoices submitted for CLIN 0001-0003.

B.4 Performance Work Statement

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology Financial Services Center

Puppet Enterprise Platform Software

Date: June 1, 2026

VA-26-00062749

PWS Version Number: 4.0

1.0 BACKGROUND

The Department of Veterans Affairs (VA) Financial Services Center (FSC)/Financial Technology Service (FTS) has a requirement for brand name Puppet Enterprise Platform software. The acquired solution will have both infrastructure automation and configuration management tool solutions that will allow the FSC to combine both model-based and task-based capabilities that will enable the organization to scale its multi-cloud and on-premises infrastructure as its automation footprint continues to grow. The product has both agent-based and agentless capabilities to give the organization the flexibility to automate when, where and how it wants. With the overall end result of reducing time spent on manual tasks and scripting efforts that will save money and increase overall infrastructure standardization and security using this VA approved tool.

The period of performance shall be one 12-month base period, with three 12-month option periods, if exercised.

2.0 APPLICABLE DOCUMENTS

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

1. “Federal Information Security Modernization Act of 2014”

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

Requirements for Cryptographic Modules”, March 22, 2019

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

Information Systems,” February 2004

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

Information Systems,” March 2006

5. 10 U.S.C. § 2224, "Defense Information Assurance Program", as amended

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

7. Public Law 109-461 (P.L. 109-461), Veterans Benefits, Health Care, and

Information Technology Act of 2006, as amended, Title IX, Information Security Matters

8. VA Directive 6102, “Internet/Intranet Services,” August 5, 2019

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

Guidelines,” as amended

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

Services (CHAMPUS)”, as amended

11. 45 C.F.R Parts 160 and 164, Subparts A and E, the Standards for Privacy of

Individually Identifiable Health Information (“Privacy Rule”); and 45 C.F.R. Parts 160 and 164, Subparts A and C, the Security Standard (“Security Rule”); as amended

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

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

14. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021 (see VA

NOTICE 24-18, dated September 27, 2024, “Update to VA Directive 6500 Cybersecurity Program”, and VA Notice 25-07, dated 3/18/25, “Amending VA Directive 6500 to incorporate M-24-15”)

15. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021 (see VA Notice 25-01, dated October 15, 2024, “Update to VA Handbook 6500 Risk Management Framework for VA Information Systems VA Information Security Program”, and VA Notice 25-06, dated 3/18/25, “Amending VA Directive 6500 to incorporate M- 24-15”, VA Notice 25-16, dated September 15, 2025, “Amending VA Handbook 6500 to Replace Enterprise Mission Assurance Support Services Tool With Office of Information Technology Governance Risk Compliance Tool, and VA Notice 25- 17, dated September 22, 2025, “Rescission Of Office Of Information Security (OIS) Deputy Assistant Secretary (DAS) Memorandum – Requirements of Proper Plan of Action and Milestones (POA&M) Completion)

16. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” June 30, 2023

17. VA Handbook 6500.6, “Contract Security,” March 12, 2010 (see VA Notice 24-12, dated April 22, 2024, “Update to VA Handbook 6500.6, Contract Security, Appendix C VA Information and Information System Security/Privacy Language For Inclusion Into Contracts, As Appropriate”)

18. VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018 (see VA NOTICE 25-10, dated June 9, 2025, “Use of Personally Owned Mobile Devices Policy Amendment of Department of Veterans Affairs Handbook 6500.10”, and VA Notice 25-15, dated August 22, 2025, “Update to VA Handbook

6500.10 Mobile Device Security Policy”)

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

20. OIT Process Asset Library (PAL), OIT Process Asset Library.

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

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

Impact Assessment,” October 15, 2014

23. VA Directive 6510, “VA Identity, Credential and Access Management,” September

3, 2024

24. VA Handbook 6510, “VA Identity, Credential and Access Management,”

September 27, 2024

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

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

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

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

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

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

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

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

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

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

35. Federal Identity, Credential, and Access Management (FICAM) Architecture, June 30, 2023 (FICAM Architecture (idmanagement.gov))

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

37. NIST SP 800-63 Rev 4, 800-63A-4, 800-63B-4, 800-63C-4, “Digital Identity Guidelines,” August 1, 2025

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

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

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

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

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

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

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

45. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (P.L.

110–140), December 19, 2007

46. Section 104 of the Energy Policy Act of 2005, (P.L. 109–58), August 8, 2005

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

48. VA Directive 0057, “VA Environmental Management Program,” October 25, 2022

49. OIS VAIQ #7424808 Memorandum, “Remote Access,” January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

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

51. “

52. VA Memorandum “Proper Use of Email and Other Messaging Services,” January

2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

53. “Product Line Management Transformation Playbook” version 3.1, August 2023, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

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

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

Version 6 (IPv6),” November 19, 2020

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

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

58. C.F.R Title 15 Part 7, “Securing the Information and Communications Technology and Services (ICTS) Supply Chain”, as amended

59. Executive Order 14028, “Executive Order on Improving the Nation's

Cybersecurity,” May 12, 2021, https://bidenwhitehouse.archives.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/

60. OMB Memorandum M-22-09, “Moving the U.S. Government Toward Zero Trust Cybersecurity Principles”, January 26, 2022, https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf.

61. NIST SP 800-52 Revision 2, “Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations

62. OMB M-26-05, “Adopting a Risk-based Approach to Software and Hardware Security,” January 23, 2026

63. OMB M-21-31, “Improving the Federal Government’s Investigative and Remediation Capabilities Related to Cybersecurity Incidents,” August 27, 2021

64. NIST SP 800-88 Revision 1 “Guidelines for Media Sanitization,” December 2014

65. CISA Binding Operational Directive (BOD) 19-02: “Vulnerability Remediation

Requirements of Internet-Accessible Systems,” April 29, 2019, BOD 19-02:

Vulnerability Remediation Requirements for Internet-Accessible Systems | CISA

66. CISA BOD 22-01: “Reducing the Significant Risk of Known Exploited Vulnerabilities,” November 3, 2021, BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities | CISA

67. CISA BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks.” Cybersecurity & Infrastructure Security Agency (CISA), BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks

| CISA

68. VA Memorandum, “VA Security Controls,” January 17, 2025, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010

69. E.O. 13960, “Promoting the Use of Trustworthy Artificial Intelligence in the Federal Government,” December 3, 2020

70. E.O. 14319, “Preventing Woke AI in the Federal Government,” July 23, 2025

71. OMB Memorandum M-25-21, “Accelerating Federal Use of AI through Innovation, Governance, and Public Trust,” April 3, 2025

72. OMB Memorandum M-25-22, “Driving Efficient Acquisition of Artificial Intelligence in Government,” April 3, 2025

73. OMB Memorandum M-26-04, “Increasing Public Trust in Artificial Intelligence (AI)

Through Unbiased AI Principles,” December 11, 2025

74. CISA BOD 22-01: “Reducing the Significant Risk of Known Exploited

Vulnerabilities,” November 3, 2021, BOD 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities | CISA

75. CISA BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks.” Cybersecurity & Infrastructure Security Agency (CISA), BOD 23-01: Improving Asset Visibility and Vulnerability Detection on Federal Networks

| CISA

76. VA Directive 6550, Pre-Procurement Assessment and Implementation of Medical Devices/Systems, June 03, 2019

77. VA Memorandum, “VA Security Controls,” January 17, 2025, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010

78. E.O. 13960, “Promoting the Use of Trustworthy Artificial Intelligence in the Federal Government,” December 3, 2020

79. E.O. 14319, “Preventing Woke AI in the Federal Government,” July 23, 2025

80. OMB Memorandum M-25-21, “Accelerating Federal Use of AI through Innovation, Governance, and Public Trust,” April 3, 2025

81. OMB Memorandum M-25-22, “Driving Efficient Acquisition of Artificial Intelligence in Government,” April 3, 2025

82. OMB Memorandum M-26-04, “Increasing Public Trust in Artificial Intelligence (AI) Through Unbiased AI Principles,” December 11, 2025

3.0 SCOPE OF WORK

The Contractor shall provide Puppet Enterprise Software licenses and maintenance support. Services in accordance with (IAW) this PWS establish an Infrastructure as Code (IaC) and configuration management tool. This streamlines Development and Operations (DevOps) by automating server management, eliminating the need for constant shell script updates across evolving system configurations. The tool uses custom declarative language to describe system configuration. It is then distributed using the client-server paradigm to realize the configuration. The resource abstraction layer enables administrators to describe the configuration in high-level terms, such as users, services and packages. The Puppet software will then ensure the server's state matches the description.

CLIN Base YEAR Quantity Unit

Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription; Part No.: PECD1499S

500 Each

Description: Puppet Ent./Cont. Delivery Jumpstart:

Basic impl. Pkg. incl. up to 80 hrs.; Part No.:

CD4PE_JSBasic

1 Each

The Contractor shall provide Original Equipment Manufacturer (OEM) confirmation that all software support or licenses have been purchased. The Contractor shall provide service call instructions to include all information required to obtain maintenance, support or licenses. Payment of invoices will not be made without proper distribution and installation.

NSP NSP

BASE PERIOD OPTIONAL CLIN

Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription; Part No.: PECD1499S

NTE

CLIN Option YEAR 1 Quantity Unit

Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription; Part

500 Each

The Contractor shall provide Original Equipment Manufacturer (OEM) confirmation that all software support or licenses have been purchased. The Contractor shall provide service call instructions to include all information required to obtain maintenance, support or licenses. Payment of invoices will not be made without proper distribution and installation.

NSP NSP

OY1 OPTIONAL CLIN

Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription; Part

NTE 200

CLIN Option YEAR 2 Quantity Unit

Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription; Part No.: PECD1499S

500 Each

The Contractor shall provide Original Equipment Manufacturer (OEM) confirmation that all software support or licenses have been purchased. The Contractor shall provide service call instructions to include all information required to obtain maintenance, support or licenses. Payment of invoices will not be made without proper distribution and installation.

NSP NSP

OY2 OPTIONAL CLIN

Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription; Part

NTE 200

CLIN Option YEAR 3 Quantity Unit

Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription; Part

500 Each

The Contractor shall provide Original Equipment Manufacturer (OEM) confirmation that all software support or licenses have been purchased. The Contractor shall provide service call instructions to include all information required to obtain maintenance, support or licenses. Payment of invoices will not be made without proper distribution and installation.

NSP NSP

OY3 OPTIONAL CLIN

Description: Puppet Enterprise w/Continuous Delivery 1-499 Nodes Std Annual Subscription; Part

NTE

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The PoP shall be 12 months from date of award, with three 12 month option period(s) and one Optional Tasks each performance year. The overall period of performance shall not exceed 4 months

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

4.2 PLACE OF PERFORMANCE

Software shall be uploaded to VA Information Technology (IT) equipment. Tasks under this PWS shall be performed in VA facilities located at 8000 Metropolis Drive, Building B, Austin TX 78744.

4.3 TRAVEL

The Government does not anticipate travel under this effort to perform the tasks associated with the effort.

If travel is required – 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.

5.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall deliver 500 each of the Puppet software licenses and Proof of Entitlement within 5 days of receipt of award. The Puppet software should provide the following salient characteristics:

-A declarative configuration management and infrastructure automation designed to manage and automate the configuration of servers and other IT systems.

-Treat infrastructure configuration as a code (IaC), enabling version control, testing and reproductablity.

-works like a cross-platform support should work on Unix-like systems and Microsoft

Windows Use custom declarative language to define the desires state of systems, not step-by-step instructions.

-Be model-driven, requiring minimal programming knowledge to use, making it accessible to administrators without deep coding skills -Shall run on managed systems and applies configurations fetched from the server _will be open source (Apache License since v2.7.0) -Function as a modular ecosystem using modules to automate common tasks, from software deployment to security compliance -Provide Automaton capabilities, automates provisioning, configuration, software deployment, security settings, and maintenance tasks, reducing manual work and human error

-, Ensures consistency across all systems adhere to the same configuration rules -Provide efficiency by reducing repetitive administrative tasks and speeds up deployment A. Deliver 500 each Puppet License Keys within 5 days of receipt of award B. Contractor shall submit a complete Proof of Entitlement (PoE) form for maintenance support. The Contractor shall provide Original Equipment Manufacturer (OEM) confirmation that all software support or licenses have been purchased. The Contractor shall provide service call instructions to include all information required to obtain maintenance, support or licenses. Payment of invoices will not be made without proper distribution and installation.

ADDITIONAL TASK(S)

C. The Contractor shall submit a complete Proof of Entitlement (PoE) form for maintenance support. The Contractor shall provide Original Equipment Manufacturer (OEM) confirmation that all software support or licenses have been purchased. The Contractor shall provide service call instructions to include all information required to obtain maintenance, support or licenses. Payment of invoices will not be made without proper distribution and installation.

Deliver Optional Licenses, when exercised, within 5 days of award - Provide Statement of Attestation within 5 days of receipt of award

6.0 GENERAL REQUIREMENTS

6.1 ENTERPRISE AND IT FRAMEWORK

6.1.1 VA TECHNICAL REFERENCE MODEL

The Contractor shall comply with the VA OIT Technical Reference Model (VA TRM).

Compliance with the VA TRM is achieved by using only technologies and standards that are listed as approved for use in the VA TRM. The Contractor shall provide all necessary information requested by VA to ensure TRM approval is obtained prior to use on VA’s network.

6.1.2 ZERO TRUST – VA CRITICAL SECURITY CONTROLS

VA has established minimum mandatory security requirements and requires that any network connected software system or service must meet the VA Critical Security Controls as outlined in the VA Memorandum, “VA Security Controls”, https://www.voa.va.gov/DocumentView.aspx?DocumentID=5010. VA Critical Security Controls identify the minimum mandatory requirements that must be implemented across all VA enterprise infrastructure, cloud computing environments, information systems, networks, and specialized devices (medical devices/systems, special-purpose systems, and research scientific computing devices) that process, store, and/or transmit VA data. Effective July 1, 2025, the Contractor shall implement these VA Critical Security Controls, within any network connected software system or service prior to being authorized for use in the VA. This functional requirement is not negotiable, and Plan of Action & Milestones (POAM) will not be accepted in the event these controls cannot be implemented for new systems. Critical Security Controls are intended to increase VA’s security posture and provide security and privacy risk visibility into the VA network and is not a new requirement. The Contractor’s failure to maintain these VA Critical Controls after implementation will result in VA discontinuing the use of the system.

6.1.3 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 Architecture (EA), and VA Identity and Access Management (IAM) approved Enterprise Technology Guidelines (ETG). 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 Executive Order 14028, VA Handbook 6510 VA Identity and Access Management, VA Handbook 0735 Homeland Security Presidential Directive 12 (HSPD-12) Program, CISA Binding Operational Directive 23- 01, 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, and VA IAM enterprise requirements for direct, assertion based authentication, and/or trust based authentication, as determined by the ETGs. 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, M-22-09, and NIST Federal Information Processing Standard (FIPS) 201-3. Contractor delivered applications and systems shall be on the FIPS 201 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 Technology Guideline as outlined in VA ETG.

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.4 INTERNET PROTOCOL VERSION 6 (IPv6)

The Contractor solution shall support IPv6-Only 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). Which defines IPv6-only as the state of an operational system or service when IPv4 protocol functions (addressing, packet forwarding) are not in use. The NIST USGv6 profile defines technical requirements for a product to be capable of operating in IPv6-Only environments.