36C10B20Q0067-001.docx
DOCX document Posted
- Solicitation number
- 36C10B20Q0067
About this file
36C10B20Q0067 36C10B20Q0067_1.docx
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 36C10B20Q0067-002.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
36C10B20Q0067 Contract Opportunity Combined Synopsis/Solicitation Notice
CLASSIFICATION CODE
SUBJECT
CONTRACTING OFFICE'S
ZIP-CODE
SOLICITATION NUMBER
RESPONSE DATE (MM-DD-YYYY)
ARCHIVE
DAYS AFTER THE RESPONSE DATE
RECOVERY ACT FUNDS
SET-ASIDE
NAICS CODE
CONTRACTING OFFICE
ADDRESS
POINT OF CONTACT
(POC Information Automatically Filled from User Profile Unless Entered)
DESCRIPTION
See Attachment
AGENCY'S URL
URL DESCRIPTION
AGENCY CONTACT'S EMAIL
ADDRESS
EMAIL DESCRIPTION
ADDRESS
POSTAL CODE
COUNTRY
ADDITIONAL INFORMATION
GENERAL INFORMATION
PLACE OF PERFORMANCE
* = Required Field Contract Opportunity Combined Synopsis/Solicitation Notice TAC-20-57831 Upgrade Building Automation System - Puerto Rico 07724 36C10B20Q0067 12-17-2019 N 334512 Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724 Charles Hutchins charles.hutchins1@va.gov 732-795-1101 See attached RFQ charles.hutchins1@va.gov charles.hutchins1@va.gov This is a Combined Synopsis for Commercial services in accordance with Federal Acquisition Regulations (FAR) subpart 12.6 and subpart 5.207. This notice does not in itself represent the issuance of a formal request for proposal/quote and is not intended to be taken as such.
The Department of Veterans Affairs (VA), Office of Procurement, Acquisition and Logistics (OPAL), Technology Acquisition Center (TAC), located at 23 Christopher Way, Eatontown, NJ 07724 intends to award a firm-fixed-price contract, issued on a sole source basis, to Upgrade the existing Trane Summit BAS software with the Trane Tracer Ensemble software, at the VA Caribbean Healthcare System in San Juan, Puerto Rico.
The period of performance shall be 120 days from the date of award. The Statutory Authority for this effort falls under Federal Acquisition Regulation (FAR) Part 13.501 entitled, “Special Documentation Requirements.” The North American Industrial Classification System (NAICS) code for this effort is 334512 which have a small business size standard of 500 employees. This notification shall close on December 17, 2019. The anticipated award date is December 20, 2019. The Solicitation Number for this RFQ is 36C10B20Q0067.
Questions/responses shall be submitted via e-mail to Contract Specialist Charles Hutchins, charles.hutchins1@va.gov with the subject line as the RFQ number 36C10B20Q0067. The Point of Contacts for this action are Charles Hutchins, charles.hutchins1@va.gov and Contracting Officer Debra G. Clayton, debra.clayton2@va.gov.
PAGE 1 OF
1. REQUISITION NO.
2. CONTRACT NO.
3. AWARD/EFFECTIVE DATE
4. ORDER NO.
5. SOLICITATION NUMBER
6. SOLICITATION ISSUE DATE
a. NAME
b. TELEPHONE NO. (No Collect Calls)
8. OFFER DUE DATE/LOCAL
TIME
9. ISSUED BY
CODE
10. THIS ACQUISITION IS
UNRESTRICTED OR
SET ASIDE:
% FOR: PM
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.
DUNS:
DUNS+4:
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. 2/2012)
PREVIOUS EDITION IS NOT USABLE
Prescribed by GSA - FAR (48 CFR) 53.212
7. FOR SOLICITATION
INFORMATION CALL:
STANDARD FORM 1449
OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30
SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS
672-20-1-510-0170 36C10B20Q0067 CS Charles Hutchins
(732) 795-1101
12/16/19 11:59 PM
Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724 X 334512 Employees N/A X See Delivery Schedule See Delivery Schedule See Delivery Schedule Eatontown NJ 07724 Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724
Department of Veterans Affairs Technology Acquisition Center Financial Services Center PO Box 149971 Austin TX 78714-8971 See CONTINUATION Page Title: Upgrade of Trane Brand Name Building Automation System, VACHS POCs:
CO: Debra G. Clayton, 732-795795-1015 debra.clayton2@va.gov CS: Charles Hutchins, 732-795795-1101 charles.hutchins1@va.gov Purchase Order No.: TBD Period of Performance: 120 Days From Date of Award (See Continuation Page) 672-3600162-510-855100-2580 010050100 X Debra G. Clayton Contracting Officer
Page 1 of
Page 1 of
Table of Contents
| SECTION B - CONTINUATION OF SF 1449 BLOCKS | 6 | |
| B.1 CONTRACT ADMINISTRATION DATA | 6 | |
| B.2 GOVERNING LAW | 7 | |
| B.3 PRICE/COST SCHEDULE | 10 | |
| B.4 PERFORMANCE WORK SCHEDULE | 14 | |
| 2.0 | APPLICABLE DOCUMENTS | 15 |
| 3.0 | SCOPE OF WORK | 18 |
| 4.0 | PERFORMANCE DETAILS | 18 |
| 4.1 | PERFORMANCE PERIOD | 18 |
| 4.2 | PLACE OF PERFORMANCE | 18 |
| 4.3 | TRAVEL | 18 |
| 5.0 | SPECIFIC TASKS AND DELIVERABLES | 18 |
| 5.1 | PROJECT MANAGEMENT | 19 |
| 5.1.1 | DETAILED PROJECT SCHEDULE | 19 |
| 5.2 | CAMPUS UPGRADE | 19 |
| 5.3 | SOUTH BED TOWER CONTROLS INTEGRATION | 20 |
| 5.4 | TESTING/ACCEPTANCE | 20 |
| 5.5 | TRAINING | 21 |
| 5.6 | SERVICE MAINTENANCE PLAN | 21 |
| 6.0 | GENERAL REQUIREMENTS | 21 |
| 6.1 | ENTERPRISE AND IT FRAMEWORK | 21 |
| 6.1.1 | VA TECHNICAL REFERENCE MODEL | 21 |
| 6.1.2 | FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT (FICAM) | 21 |
| 6.1.3 | INTERNET PROTOCOL VERSION 6 (IPV6) | 22 |
| 6.1.4 | TRUSTED INTERNET CONNECTION (TIC) | 23 |
| 6.1.5 | STANDARD COMPUTER CONFIGURATION | 23 |
| 6.1.6 | VETERAN FOCUSED INTEGRATION PROCESS (VIP) | 24 |
| 6.1.7 | PROCESS ASSETT LIBRARY (PAL) | 24 |
| 6.1.8 | AUTHORITATIVE DATA SOURCES | 24 |
| 6.2 | SECURITY AND PRIVACY REQUIREMENTS | 25 |
| 6.2.1 | POSITION/TASK RISK DESIGNATION LEVEL(S) | 25 |
| 6.2.2 | CONTRACTOR PERSONNEL SECURITY REQUIREMENTS | 25 |
| 6.3 | METHOD AND DISTRIBUTION OF DELIVERABLES | 27 |
| 6.4 | PERFORMANCE METRICS | 27 |
| 6.5 | FACILITY/RESOURCE PROVISIONS | 28 |
| 6.6 | GOVERNMENT FURNISHED PROPERTY | 29 |
| ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED | 30 | |
| ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY LANGUAGE | 36 | |
| SECTION C - CONTRACT CLAUSES | 42 | |
| C.3 52.212-5 Contract Terms and Conditions Required to Implement Statutes or Executive Orders-Commercial Items (OCT 2019) | 43 | |
| C.4 852.232-72 ELECTRONIC SUBMISSION OF PAYMENT REQUESTS (NOV 2018) | 51 | |
| C.5 852.270-1 REPRESENTATIVES OF CONTRACTING OFFICERS (JAN 2008) | 53 | |
| SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENTS | 54 | |
| SECTION E - SOLICITATION PROVISIONS | 55 | |
| E.1 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998) | 55 | |
| E.2 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—COMMERCIAL ITEMS (OCT 2018) | 56 | |
| E.3 52.216-1 TYPE OF CONTRACT (APR 1984) | 72 | |
| E.4 52.225-18 PLACE OF MANUFACTURE (AUG 2018) | 73 | |
| E.5 52.233-2 SERVICE OF PROTEST (SEP 2006) | 74 | |
| E.8 RESPONSE TO INSTRUCTIONS | 70 | |
| E.9 BASIS FOR AWARD | 70 |
SECTION B - CONTINUATION OF SF 1449 BLOCKS
B.1 CONTRACT ADMINISTRATION DATA
1. Contract Administration: All contract administration matters will be handled by the following individuals:
a. CONTRACTOR:
Trane US Inc.
3600 Pammel Creek Road La Crosse, Wisconsin 54601-7511
b. GOVERNMENT: Contracting Officer 36C10B Department of Veterans Affairs Technology Acquisition Center 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 |
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.
Department of Veterans Affairs Technology Acquisition Center Financial Services Center PO Box 149971 Austin TX 78714-8971 ACKNOWLEDGMENT OF AMENDMENTS: The offeror acknowledges receipt of amendments to the Solicitation numbered and dated as follows:
| AMENDMENT NO |
| DATE |
B.2 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. 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 U.S.C. § 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. Claims of patent or copyright infringement brought against the Government as a party shall be defended by the U.S. Department of Justice (DOJ). 28 U.S.C. § 516. At the discretion of DOJ, the Contractor may be allowed reasonable participation in the defense of the litigation. Any additional changes to the Contract/Order must be made by contract/order modification (Standard Form 30) and shall only be affected 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, 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 licensor ownership rights to deliver license, software maintenance and support of the computer software being acquired. The term “contractor” is the party identified in Block17a on the SF1449. If the contractor is a reseller and not the Licensor, the contractor remains responsible for performance under this 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 are vision 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 Version5.4 to 6).
(2) Software License (a)Unless otherwise stated in the Schedule of Supplies/Services, the Performance Work Statement or Product Description, the software license provided to the Government is a perpetual, nonexclusive license to use the software
(b) The Government may use the software in a networked environment.
(c)Any dispute regarding the license grant or usage limitations shall be resolved in accordance with the Disputes Clause incorporated in FAR 52.212-4(d).
(d)All limitations of software usage are expressly stated in the Schedule of Supplies/Services and the Performance Work Statement/Product Description.
(3) Software Maintenance and Technical Support (a)If the Government desires to continue software maintenance and support beyond the period of performance identified in this contract or order, the Government will issue a separate contract or order for maintenance and support. Conversely, if a contract or order for continuing software maintenance and technical support is not received the contractor is neither authorized nor permitted to renew any of the previously furnished services.
(b)The contractor shall provide software support services, which includes periodic updates, enhancements and corrections to the software, and reasonable technical support, all of which are customarily provided by the contractor to its commercial customers so as to cause the software to perform according to its specifications, documentation or demonstrated claims.
(c) Any telephone support provided by contractor shall be at no additional cost.
(d) The contractor shall provide all maintenance services in a timely manner in accordance with the contractor’s customary practice or as defined in the Performance Work Statement/Product Description. However, prolonged delay (exceeding 2 business days) in resolving software problems will be noted in the Government’s various past performance records on the contractor (e.g., www.ppirs.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 or order at no cost.
B.3 PRICE/COST SCHEDULE
The Period of Performance Shall Be 120 Days From Date of Award
| CLIN # |
| DESCRIPTION |
| QTY |
| UNIT |
| UNIT PRICE |
| TOTAL |
| 0001 |
| Project Management in accordance with PWS paragraph 5.1 |
This Firm-Fixed Price (FFP) Contract Line Item Number (CLIN) includes all labor, materials, travel, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.1 inclusive of all of its subparagraphs.
Inspection: destination Acceptance: destination
| 1 |
| LT |
| $ |
| $ |
| 0001AA |
| Detailed Project Schedule in accordance with PWS paragraph 5.1.1 |
Due 7 days after contract award
Electronic submission to: VA PM, COR.
Inspection: destination Acceptance: destination
| 1 |
| EA |
| NSP |
| NSP |
| 0002 |
| Campus Upgrade in accordance with PWS paragraph 5.2 |
Due 10 days after contract award
Electronic submission to: VA PM, COR.
Inspection: destination Acceptance: destination
| 1 |
| LT |
| NSP |
| NSP |
| 0002AA |
| Display Monitor Manuals in accordance with PWS paragraph 5.2 |
Due 14 days after contract award
Electronic submission to: VA PM, COR.
Inspection: destination Acceptance: destination
| 1 |
| LT |
| NSP |
| NSP |
| 0003 |
| South Bed Tower Controls Integration in accordance with PWS paragraph 5.3 |
This Firm-Fixed Price (FFP) Contract Line Item Number (CLIN) includes all labor, materials, travel, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.3 inclusive of all of its subparagraphs
Inspection: destination Acceptance: destination
| 1 |
| LT |
| $ |
| $ |
| 0004 |
| Testing/Acceptance in accordance with PWS paragraph 5.4 |
This Firm-Fixed Price (FFP) Contract Line Item Number (CLIN) includes all labor, materials, travel, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.1 inclusive of all of its subparagraphs
Inspection: destination Acceptance: destination
| 1 |
| LT |
| $ |
| $ |
| 0004AA |
| Final Commissioning Report in accordance with PWS paragraph 5.4 |
Due 120 days after contract award
Electronic submission to: VA PM, COR.
Inspection: destination Acceptance: destination
| 1 |
| EA |
| NSP |
| NSP |
| 0005 |
| Training in accordance with PWS paragraph 5.5 |
This Firm-Fixed Price (FFP) Contract Line Item Number (CLIN) includes all labor, materials, travel, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.5 inclusive of all of its subparagraphs
Inspection: destination Acceptance: destination
| 1 |
| LT |
| $ |
| $ |
| 0005AA |
| Training Materials in accordance with PWS paragraph 5.5 |
Due 14 days after contract award
Electronic submission to: VA PM, COR.
Inspection: destination Acceptance: destination
| 1 |
| LT |
| NSP |
| NSP |
| 0006 |
| Service Maintenance Plan in accordance with PWS paragraph 5.6 |
This Firm-Fixed Price (FFP) Contract Line Item Number (CLIN) includes all labor, materials, travel, and deliverables required for the successful completion of the services detailed in PWS paragraph 5.6 inclusive of all of its subparagraphs
Acceptance: destination
| 1 |
| LT |
| $ |
| $ |
| 0007 |
| Building Management System Upgrade & South Bed Tower Controls Integration Projects Materials . |
See below
See below
| 0007AA |
| Trane Tracer Ensemble Platform in accordance with PWS paragraph 5.3. |
| 1 |
| EA |
| $ |
| $ |
| 0007AB |
| Trane Tracer SC+ Main Controllers in accordance with PWS paragraph 5.3. |
| 5 |
| EA |
| $ |
| $ |
| 0007AC |
| Operator graphics for equipment navigation in accordance with PWS paragraph 5.3. |
| 60 |
| EA |
| NSP |
| NSP |
| 0008 |
| Dell EMC PowerEdge brand name or equal R340 Server |
| 1 |
| EA |
| $ |
| $ |
| 0009 |
| Commercial Displays – Sharp PN-R496 brand name or equal |
| 4 |
| EA |
| $ |
| $ |
| Total Price |
| $ |
B.4 PERFORMANCE WORK SCHEDULE
PERFORMANCE WORK STATEMENT (PWS)
DEPARTMENT OF VETERANS AFFAIRS
VETERANS HEALTH ADMINISTRATION (VHA)
VA Caribbean Health Care System (San Juan)
Upgrade of Building Automation System
Date: December 3, 2019
TAC-20-57931
PWS Version Number: 1.0
1.0 BACKGROUND
The mission of the Department of Veterans Affairs (VA), Veterans Health Administration (VHA), is to provide benefits and services to Veterans of the United States. In meeting these goals, VHA strives to provide high quality, effective, and efficient 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.
To support its mission and achieve these goals the VA Caribbean Healthcare System (VACHS) in San Juan, Puerto Rico, has a requirement to upgrade the existing Building Automation System (BAS). Several years ago, as part of a Non-Recurring Maintenance (NRM) construction and renovation program the VHA began modernization and standardization at VACHS in Puerto Rico. The Non-Recurring Maintenance Program was established pursuant to VHA Directive 1002.1. This modernization included installation of systems that permitted centralized monitoring and controlling of all aspects of the hospital environment and building management systems. The core of this modernization and standardization is the Trane Tracer Ensemble which centralizes the monitoring and management of the VA facilities systems. This acquisition is an extension of that VA NRM construction and renovation program. The Sole Source nature of this acquisition is consistent with the standardization aspect of the NRM.
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 2016
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. Carnegie Mellon Software Engineering Institute, Capability Maturity Model® Integration for Development (CMMI-DEV), Version 1.3 November 2010; and Carnegie Mellon Software Engineering Institute, Capability Maturity Model® Integration for Acquisition (CMMI-ACQ), Version 1.3 November 2010
9. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”
10. Public Law 109-461, Veterans Benefits, Health Care, and Information Technology Act of 2006, Title IX, Information Security Matters
11. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”
12. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, http://www.va.gov/vapubs/
13. VA Handbook 0710, Personnel Security and Suitability Security Program, May 2, 2016, http://www.va.gov/vapubs
14. VA Directive and Handbook 6102, “Internet/Intranet Services,” July 15, 2008
15. 36 C.F.R. Part 1194 “Electronic and Information Technology Accessibility Standards,” July 1, 2003
16. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016
17. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”
18. An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule, October 2008
19. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended, January 18, 2017
20. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004
21. VA Directive 6500, “Managing Information Security Risk: VA Information Security Program,” September 20, 2012
22. VA Handbook 6500, “Risk Management Framework for VA Information Systems – Tier 3: VA Information Security Program,” March 10, 2015
23. VA Handbook 6500.1, “Electronic Media Sanitization,” November 03, 2008
24. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI)”, July 28, 2016
25. VA Handbook 6500.3, “Assessment, Authorization, And Continuous Monitoring Of VA Information Systems,” February 3, 2014
26. VA Handbook 6500.5, “Incorporating Security and Privacy in System Development Lifecycle”, March 22, 2010
27. VA Handbook 6500.6, “Contract Security,” March 12, 2010
28. VA Handbook 6500.8, “Information System Contingency Planning”, April 6, 2011
29. OI&T 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
30. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)
31. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014
32. VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy Impact Assessment,” July 30, 2015
33. VA Handbook 6510, “VA Identity and Access Management”, January 15, 2016
34. VA Directive 6300, Records and Information Management, February 26, 2009
35. VA Handbook, 6300.1, Records Management Procedures, March 24, 2010
36. NIST SP 800-37 Rev 1, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach, June 5, 2014
37. NIST SP 800-53 Rev. 4, Security and Privacy Controls for Federal Information Systems and Organizations, January 22, 2015
38. OMB Memorandum, “Transition to IPv6”, September 28, 2010
39. VA Directive 0735, Homeland Security Presidential Directive 12 (HSPD-12) Program, October 26, 2015
40. VA Handbook 0735, Homeland Security Presidential Directive 12 (HSPD-12) Program, March 24, 2014
41. OMB Memorandum M-06-18, Acquisition of Products and Services for Implementation of HSPD-12, June 30, 2006
42. OMB Memorandum 04-04, E-Authentication Guidance for Federal Agencies, December 16, 2003
43. 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
44. OMB memorandum M-11-11, “Continued Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors, February 3, 2011
45. OMB Memorandum, Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation, May 23, 2008
46. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011
47. NIST SP 800-116 Rev 1, Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access, June 2018
48. OMB Memorandum M-07-16, Safeguarding Against and Responding to the Breach of Personally Identifiable Information, May 22, 2007
49. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, Digital Identity Guidelines, June 2017
50. NIST SP 800-157, Guidelines for Derived PIV Credentials, December 2014
51. NIST SP 800-164, Guidelines on Hardware-Rooted Security in Mobile Devices (Draft), October 2012
52. Draft National Institute of Standards and Technology Interagency Report (NISTIR) 7981 Mobile, PIV, and Authentication, March 2014
53. 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)
54. 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)
55. VA Memorandum “Mandate to meet PIV Requirements for New and Existing Systems” (VAIQ# 7712300), June 30, 2015, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4846
56. Trusted Internet Connections (TIC) Reference Architecture Document, Version 2.2, Federal Interagency Technical Reference Architectures, Department of Homeland Security, June 19, 2017, https://www.dhs.gov/sites/default/files/publications/TIC_Ref_Arch_v2.2_2017.pdf
57. OMB Memorandum M-08-05, “Implementation of Trusted Internet Connections (TIC), November 20, 2007
58. OMB Memorandum M-08-23, Securing the Federal Government’s Domain Name System Infrastructure, August 22, 2008
59. VA Memorandum, VAIQ #7497987, Compliance – Electronic Product Environmental Assessment Tool (EPEAT) – IT Electronic Equipment, August 11, 2014 (reference Document Libraries, EPEAT/Green Purchasing Section, https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552)
60. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public Law 110–140), December 19, 2007
61. Section 104 of the Energy Policy Act of 2005, (Public Law 109–58), August 8, 2005
62. Executive Order 13834, “Efficient Federal Operations”, dated May 17, 2018
63. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001
64. VA Directive 0058, “VA Green Purchasing Program”, July 19, 2013
65. VA Handbook 0058, “VA Green Purchasing Program”, July 19, 2013
66. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access”, January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28
67. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103
68. VA Memorandum, “Implementation of Federal Personal Identity Verification (PIV) Credentials for Federal and Contractor Access to VA IT Systems”, (VAIQ# 7614373) July 9, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28
69. VA Memorandum “Mandatory Use of PIV Multifactor Authentication to VA Information System” (VAIQ# 7613595), June 30, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28
70. VA Memorandum “Mandatory Use of PIV Multifactor Authentication for Users with Elevated Privileges” (VAIQ# 7613597), June 30, 2015; https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28
71. “Veteran Focused Integration Process (VIP) Guide 3.2”, December 2018, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371
72. “VIP Release Process Guide”, Version 1.4, May 2016, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4411
73. “POLARIS User Guide”, Version 1.9, March 2017, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4412
74. VA Memorandum “Use of Personal Email (VAIQ #7581492)”, April 24, 2015, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28
3.0 SCOPE OF WORK
The Contractor shall upgrade the existing Trane Building Automation System (BAS) software and provide controls integration of the South Bed Tower for the VA Caribbean Health Care System - San Juan campus. The Contractor shall provide Project Management, technology refresh, software and equipment installation/configuration/ programming, export and edit existing graphics, create and upload new graphic to server, re-arrange navigation tree, programming existing schedules, trending, sequencing, and reports, LAN/wireless networking, Dell EMC brand name or equal R340 server installation and programming, four Sharp brand name or equal PN-R4496 commercial displays/monitors, data migration, graphical user interface, engineering and technical documentation, commissioning/testing/validation and training services.
4.0 PERFORMANCE DETAILS
4.1 PERFORMANCE PERIOD
The Period of Performance (PoP) shall be 120 days from date of award.
The Contractor may have access to the VA facility 24x7 to complete the BAS upgrade.
4.2 PLACE OF PERFORMANCE
Tasks under this PWS shall be performed in VA facilities located at VA Caribbean Healthcare System, 10 Casia Street, San Juan, Puerto Rico. Work may be performed at remote locations with prior concurrence from the Contracting Officer’s Representative (COR).
4.3 TRAVEL
The Government does not anticipate 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:
5.1 PROJECT MANAGEMENT
Contractor shall be responsible for the project management of this contract including but not limited to; scheduling, site preparation, equipment procurement, equipment/ materials delivery, equipment installation, tests, and final inspection.
5.1.1 DETAILED PROJECT SCHEDULE
The Contractor shall provide a detailed project schedule to include phasing and written narrative, indicating specific dates for each step of the upgrade process. Tasks 5.2 and 5.3 shall be performed simultaneously.
Deliverable Detailed Project Schedule
5.2 CAMPUS UPGRADE
The Contractor shall upgrade the existing Building Automation System (BAS). The Contractor shall supply, install, integrated and configure the latest Tracer Ensemble software version, at time of award, server and all equipment’s, mains controllers, unit controllers and licenses. This installation shall include but is not limited to a new server and pertaining accoutrements. The operator interface graphics and menus shall be improved and upgrade to reflect the new and existing campus configurations.
The Contractor shall install four (4) new monitors in the Operations Control Center that operates continuous-duty with DVI to HDMI or DVI to display port interface. The Contractor shall deliver manuals for the Display Monitors.
The system upgrade shall be done by paralleling the new system with the existing. The existing equipment/software shall not be taken off-line until the entire new system is completed and tested. All data migration, programming, etc. shall be done in parallel.
The upgraded Trane Ensemble BAS shall include the following features:
1. Accessibility to BAS functions through any Web browser from PCs, tablets and smartphones.
2. Capability to integrate with existing Tracer Summit systems (BMTX, BMTW, V16 or higher), new Tracer System (SC, UC600, UC400, Air™ Wireless Technology), as well as Johnson Control systems.
3. If the current BAS data is incompatible with the upgraded BAS, the Contractor shall perform data migration and/or conversion to ensure current BAS data is compatible with the upgraded BAS.
4. IP network communication to allow easy connection of multiple systems across VA Caribbean Healthcare System.
5. Provide capability to update any or all Tracer Ensemble workstations from a centralized point within the VA firewall. Data collection, analysis, and reporting of all BAS data. Users shall be able to retrieve historical data; this data provides invaluable information for optimal system operation. It can be used for a variety of purposes, from reporting monthly energy usage to troubleshooting equipment problems.
6. Provide Dashboard functionality and graphics to monitor all existing measuring systems such as:
a. Steam flow metering
b. Medical Oxygen System
c. Isolation Room Monitoring
d. Fire pump and cistern monitoring
e. Chiller Plant
f. Energy metering
g. HVAC System Control and Monitoring
h. Domestic Water Distribution
i. Fuel Storage Tanks
j. Potable Water Storage
k. Secondary Chlorination System for Potable Water
l. Medical Gases alarm panels
m. Medical Vacuum Pump system
n. Medical Air Compressor system
o. Domestic Hot Water System The Contractor shall provide all required monitor accoutrements (cables, power supply, etc).
Deliverable: Display Monitor Manuals
5.3 SOUTH BED TOWER CONTROLS INTEGRATION
The Contractor shall replace (but not remove) the existing (5) Johnson Controls NAE main controllers with (5) Trane Tracer SC+ main controllers with licenses. The Contractor shall integrate the following existing components: Chillers, Cooling Towers, Air Handling Units, Variable Air Volume (VAVs) Boxes, Heat Exchanger System, Fan Coils, Supply Fans, Exhaust Fans Variable Frequency Drives and monitoring points, as they were prior to the new upgrade installation of Tracer Ensemble Platform.
The Contractor shall program all (5) Tracer SC+ main controller to allow control from the prior installed Tracer Summit to the new upgrade installation of Tracer Ensemble Platform. The new Trane control components shall provide, at a minimum, the same upgraded features and capabilities identified in 5.2
The system upgrade shall be done by paralleling the new system with the existing. The existing equipment/software shall not be taken off-line until the entire new system is completed and tested. All data migration, programming, etc. shall be done in parallel.
The Contractor shall supply new operator graphics for equipment navigation (approximate 60 graphics) and upgrade any outdated graphics that currently depict the VACHS campus with current/upgraded graphics.
5.4 TESTING/ACCEPTANCE
Commissioning and testing shall be conducted for the entire system for proper operation of all the equipment components to be integrated (e.g. air handling units, VAVs, etc.). The Contractor system validation shall include demonstrating all monitoring and control set points are as they were prior to the new upgrade installation of Tracer Ensemble Platform. The Contractor shall deliver a Final Commissioning Report detailing the testing conducted with test results and the system validation demonstration.
Deliverable C: Final Commissioning Report
5.5 TRAINING
The Contractor shall provide on-site training for up to 10 system operators and users. The training material covered shall include all new functionalities, enhancements and operations from the current Tracer Summit to the new Tracer Ensemble including familiarization of dashboard features, data collection and reporting usage, and system operations. The Contractor shall provide training materials covered in the training to each training participants. Training shall not commence before VA acceptance of the system upgrade. The Contractor shall coordinate the training dates with the COR.
Deliverable D: Training Materials
5.6 SERVICE MAINTENANCE PLAN
The Tracer ES and Tracer Ensemble site license files contains a software maintenance plan (SMP) in place in order to access new versions of software. Contractor shall include a 3-year software maintenance plan which provide access to new versions of software during the active period of the SMP. The SMP shall include labor for the upgrades, training on new features, modifications to graphics, etc. Upgrades to SMP shall not exceed current approved TRM version. SMP upgrades shall not be performed until approval from OI&T has been granted.
6.0 GENERAL REQUIREMENTS
6.1 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 OI&T 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 OI&T. 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, http://www.techstrategies.oit.va.gov/enterprise_dp.asp. 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 the VA Handbook 6510 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-04-04, M-05-24, M-11-11, and NIST Federal Information Processing Standard (FIPS) 201-2. OMB Memoranda M-04-04, M-05-24, and M-11-11 can be found at: https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy04/m04-04.pdf, https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m05-24.pdf, and https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2011/m11-11.pdf respectively. Contractor 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 Veteran Index (MVI) to provision identity attributes, if the solution relies on VA user identities. MVI 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 VAIQ# 7712300 Mandate to meet PIV requirements for new and existing systems. https://www.voa.va.gov/DocumentView.aspx?DocumentID=4846
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 the latest Internet Protocol Version 6 (IPv6) based upon the directives issued by the Office of Management and Budget (OMB) on August 2, 2005 (https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m05-22.pdf) and September 28, 2010 (https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/egov_docs/transition-to-ipv6.pdf). IPv6 technology, in accordance with the USGv6 Profile, NIST Special Publication (SP) 500-267 (https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication500-267.pdf), the Technical Infrastructure for USGv6 Adoption (https://www.nist.gov/programs-projects/usgv6-program), and the NIST SP 800 series applicable compliance (https://csrc.nist.gov/publications/sp) 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/or 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/or dual stack (IPv6/ IPv4) users and all internal infrastructure and applications shall communicate using native IPv6 and/or dual stack (IPv6/ IPv4) operations. Guidance and support of improved methodologies which ensure interoperability with legacy protocol and services in dual stack solutions, in addition to OMB/VA memoranda, can be found at: https://www.voa.va.gov/documentlistpublic.aspx?NodeID=282.
6.1.4 TRUSTED INTERNET CONNECTION (TIC)
The Contractor solution shall meet the requirements outlined in Office of Management and Budget Memorandum M08-05 mandating Trusted Internet Connections (TIC) (https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2008/m08-05.pdf), M08-23 mandating Domain Name System Security (NSSEC) (https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2008/m08-23.pdf), and shall comply with the Trusted Internet Connections (TIC) Reference Architecture Document, Version 2.0 https://www.dhs.gov/sites/default/files/publications/TIC_Ref_Arch_v2.2_2017.pdf.
6.1.5 STANDARD COMPUTER CONFIGURATION
The Contractor IT end user solution that is developed for use on standard VA computers shall be compatible with and be supported on the standard VA operating system, currently Windows 7 (64bit), Internet Explorer 11 and Office 365 ProPlus. In preparation for the future VA standard configuration update, end user solutions shall also be compatible with Windows 10. However, Windows 10 is not the VA standard yet and is currently approved for limited use during its rollout. We are in-process of this rollout and making Windows 10 the standard for OI&T. Upon the release approval of Windows 10 as the VA standard, Windows 10 will supersede Windows 7 respectively. Applications delivered to the VA and intended to be deployed to Windows 7 workstations shall be delivered as a signed .msi package with switches for silent and unattended installation and updates shall be delivered in signed .msp file formats for easy deployment using System Center Configuration Manager (SCCM) VA’s current desktop application deployment tool. Signing of the software code shall be through a vendor provided certificate that is trusted by the VA using a code signing authority such as Verizon/Cybertrust or Symantec/VeriSign. The Contractor shall also ensure and certify that their solution functions as expected when used from a standard VA computer, with non-admin, standard user rights that have been configured using the United States Government Configuration Baseline (USGCB) and Defense Information Systems Agency (DISA) Secure Technical Implementation Guide (STIG) specific to the particular client operating system being used.
6.1.6 VETERAN FOCUSED INTEGRATION PROCESS (VIP)
The Contractor shall support VA efforts IAW the Veteran Focused Integration Process (VIP). VIP is a Lean-Agile framework that services the interest of Veterans through the efficient streamlining of activities that occur within the enterprise. The VIP Guide can be found at https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371. The VIP framework creates an environment delivering more frequent releases through a deeper application of Agile practices. In parallel with a single integrated release process, VIP will increase cross-organizational and business stakeholder engagement, provide greater visibility into projects, increase Agile adoption and institute a predictive delivery cadence. VIP is now the single authoritative process that IT projects must follow to ensure development and delivery of IT products
6.1.7 PROCESS ASSETT LIBRARY (PAL)
The Contractor shall perform their duties consistent with the processes defined in the OIT Process Asset Library (PAL). The PAL scope includes the full spectrum of OIT functions and activities, such as VIP project management, operations, service delivery, communications, acquisition, and resource management. PAL serves as an authoritative and informative repository of searchable processes, activities or tasks, roles, artifacts, tools and applicable standards and guides to assist the OIT workforce, Government and Contractor personnel. The Contractor shall follow the PAL processes to ensure compliance with policies and regulations and to meet VA quality standards. The PAL includes the contractor onboarding process consistent with Section 6.2.2 and can be found at https://www.va.gov/PROCESS/artifacts/maps/process_CONB_ext.pdf. The main PAL can be accessed at www.va.gov/process.
6.1.8 AUTHORITATIVE DATA SOURCES
The VA Enterprise Architecture Repository (VEAR) is one…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .