36C10B21R0025_2.docx

36C10B21R0025

PAGE 1 OF

1. REQUISITION NO.

2. CONTRACT NO.

3. AWARD/EFFECTIVE DATE

4. ORDER NO.

5. SOLICITATION NUMBER

6. SOLICITATION ISSUE DATE

a. NAME

b. TELEPHONE NO. (No Collect Calls)

8. OFFER DUE DATE/LOCAL

TIME

9. ISSUED BY

CODE

10. THIS ACQUISITION IS

UNRESTRICTED OR

SET ASIDE:

% FOR:

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

RFQ

IFB

RFP

15. DELIVER TO

CODE

16. ADMINISTERED BY

CODE

17a. CONTRACTOR/OFFEROR

CODE

FACILITY CODE

18a. PAYMENT WILL BE MADE BY

CODE

TELEPHONE NO.

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

36C10B21R0025 William Waterhouse 848-377-5097

EDT

Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724 X 541519 $30 Million N/A X See Delivery Schedule Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724

65TR8

PAR EXCELLENCE SYSTEMS, INC.

11500 NORTHLAKE DR STE 135

CINCINNATI, OH 45249-1655

513-289-8342 824657944 Department of Veterans Affairs Technology Acquisition Center Financial Services Center PO Box 149971 Austin TX 78714-8971 See CONTINUATION Page TITLE: Point of Use (POU) Integration – PAR Excellence (ParEX) See Section B Contracting Officer: Kendra Casebolt, Kendra.Casebolt@va.gov Type of Contract: Firm-Fixed-Price Brand Name:

PAR Excellence (ParEX) X Kendra M. Casebolt Contracting Officer

Table of Contents

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:

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

3. INVOICES: Invoices shall be submitted in arrears:

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

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

B.2 GOVERNING LAW CLAUSE

Federal law and regulations, including the Federal Acquisition Regulations (FAR), shall govern this Contract/Order. Commercial license agreements may be made a part of this Contract/Order but only if both parties expressly make them an addendum hereto, as permitted by FAR 12.212. If the commercial license agreement is not made an addendum, it shall not apply, govern, be a part of or have any effect whatsoever on the Contract/Order; this includes, but is not limited to, any agreement embedded in the computer software (clickwrap), any agreement that is otherwise delivered with or provided to the Government with the commercial computer software or documentation (shrinkwrap), or any other license agreement otherwise referred to in any document. If a commercial license agreement is made an addendum, only those provisions addressing data rights regarding the Government’s use, duplication and disclosure of data (e.g., restricted computer software) are included and made a part of this Contract/Order, and only to the extent that those provisions are not duplicative or inconsistent with Federal law, Federal regulation, the incorporated FAR clauses and the provisions of this Contract/Order; those provisions in the commercial license agreement that do not address data rights regarding the Government’s use, duplication and disclosure of data shall not be included or made a part of the Contract/Order. Federal law and regulation including, without limitation, the Contract Disputes Act (41 U.S.C. § 7101 et seq.), the Anti-Deficiency Act (31 U.S.C. § 1341 et seq.), the Competition in Contracting Act (41 U.S.C. § 3301 et seq.), the Prompt Payment Act (31 U.S.C. § 3901 et seq.), Contracts for Data Processing or Maintenance (38 USC § 5725), and FAR clauses 52.212-4, 52.227-14, 52.227-19 shall supersede, control, and render ineffective any inconsistent, conflicting, or duplicative provision in any commercial license agreement. In the event of conflict between this clause and any provision in the Contract/Order or the commercial license agreement or elsewhere, the terms of this clause shall prevail. The Contractor shall deliver to the Government all data first produced under this Contract/Order with unlimited rights as defined by FAR 52.227-14. Claims of patent or copyright infringement brought against the Government as a party shall be defended by the U.S. Department of Justice (DOJ) in accordance with 28 U.S.C. § 516; at the discretion of DOJ, the Contractor may be allowed reasonable participation in the defense of the litigation. Any additional changes to the Contract/Order must be made by modification (Standard Form 30) and shall only be made by a warranted Contracting Officer. Nothing in this Contract/Order or any commercial license agreement shall be construed as a waiver of sovereign immunity.

B.3 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT

1. Definitions

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

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

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

d) Maintenance. The term “maintenance” is the process of enhancing and

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

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

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

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

1. Software License

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

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

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

1. d) All limitations of software usage are expressly stated in the Schedule of Supplies/Services and the Performance Work Statement/Product Description.

1. Software Maintenance and Technical Support.

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

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

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

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

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

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

1. 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.4 PRICE SCHEDULE

NOTE: ParEX shall complete Section B.4 and submit with their proposal. ParEX is cautioned that alterations to the line items as specified below may render their proposal unacceptable. For each priced line item ensure the “Unit Price” column multiplied by the “Qty” column equals the “Total Price” (there should be no rounding). Also provide backup cost and pricing data and to substantiate proposed pricing for use in the Government’s determination of a fair and reasonable price. This shall include but is not limited to, a crosswalk to published commercial catalog pricing. Direct all questions to William Waterhouse, Contract Specialist, at William.Waterhouse@va.gov and Kendra M. Casebolt, Contracting Officer, at Kendra.Casebolt@va.gov prior to the closing date and time specified in Block 8 on page 1 of the SF 1449.

Inspection and Acceptance: Destination

All Contract Line Items Numbers (CLINs) are firm-fixed-price, except where noted.

BASE PERIOD

Period of Performance shall be 12 months from date of award

(Cost Reimbursable)

Not-To-Exceed (NTE) $18,279.92

NTE

BASE PERIOD OPTIONAL TASKS

These OPTIONAL TASKS may be exercised multiple times up to the amount listed, at the Government’s discretion, at any time during the BASE PERIOD IAW FAR 52.217-7, Option for Increased Quantity-Separately Priced Line Item (MAR 1989). Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer.

(OPTIONAL TASK #1)

IAW paragraph 5.2 of the PWS located at Section B.5.

(OPTIONAL TASK #1)

Functional DMLSS/LogiCole Interface IAW paragraph 5.2 of the PWS located at Section B.5.

(OPTIONAL TASK #2)

IAW paragraph 5.3 of the PWS located at Section B.5 – Lift & Shift

(OPTIONAL TASK #2)

IAW paragraph 5.3 of the PWS located at Section B.5 – DB Merger

(OPTIONAL TASK #3)

IAW paragraph 5.4 of the PWS located at Section B.5.

(OPTIONAL TASK #3)

Installation Acceptance Form IAW paragraph 5.4 of the PWS located at Section B.5

(OPTIONAL TASK #3)

Equipment Inventory List IAW paragraph 5.4 of the PWS located at Section B.5

(OPTIONAL TASK #3)

Functional DMLSS/LogiCole Interface IAW paragraph 5.4 of the PWS located at Section B.5.

OPTION PERIOD 1

Period of Performance shall be 12 months

This 12-month option period may be exercised in accordance with FAR 52.217-9 Option to Extend the Term of the Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. If exercised, this option period shall commence immediately after expiration of the BASE PERIOD.

(Cost Reimbursable)

NTE

$18,700.36

NTE

OPTION PERIOD 1 OPTIONAL TASKS

These OPTIONAL TASKS may be exercised multiple times up to the amount listed, at the Government’s discretion, at any time during OPTION PERIOD 1 IAW FAR 52.217-7, Option for Increased Quantity-Separately Priced Line Item (MAR 1989). Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer.

(OPTIONAL TASK #1)

IAW paragraph 5.2 of the PWS located at Section B.5.

(OPTIONAL TASK #1)

Functional DMLSS/LogiCole Interface IAW paragraph 5.2 of the PWS located at Section B.5.

(OPTIONAL TASK #2)

IAW paragraph 5.3 of the PWS located at Section B.5 – Lift & Shift

(OPTIONAL TASK #2)

IAW paragraph 5.3 of the PWS located at Section B.5 – DB Merger

(OPTIONAL TASK #3)

IAW paragraph 5.4 of the PWS located at Section B.5.

(OPTIONAL TASK #3)

Installation Acceptance Form IAW paragraph 5.4 of the PWS located at Section B.5

(OPTIONAL TASK #3)

Equipment Inventory List IAW paragraph 5.4 of the PWS located at Section B.5

(OPTIONAL TASK #3)

Functional DMLSS/LogiCole Interface IAW paragraph 5.4 of the PWS located at Section B.5.

OPTION PERIOD 2

Period of Performance shall be 12 months

This 12-month option period may be exercised in accordance with FAR 52.217-9 Option to Extend the Term of the Contract (MAR 2000). Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer. If exercised, this option period shall commence immediately after expiration of OPTION PERIOD 1.

(Cost Reimbursable)

NTE

$19,130.47

NTE

OPTION PERIOD 2 OPTIONAL TASKS

These OPTIONAL TASKS may be exercised multiple times up to the amount listed, at the Government’s discretion, at any time during OPTION PERIOD 2 IAW FAR 52.217-7, Option for Increased Quantity-Separately Priced Line Item (MAR 1989). Work shall not commence until, and unless, a formal modification is issued by the Contracting Officer.

(OPTIONAL TASK #1)

IAW paragraph 5.2 of the PWS located at Section B.5.

(OPTIONAL TASK #1)

Functional DMLSS/LogiCole Interface IAW paragraph 5.2 of the PWS located at Section B.5.

(OPTIONAL TASK #2)

IAW paragraph 5.3 of the PWS located at Section B.5 – Lift & Shift

(OPTIONAL TASK #2)

IAW paragraph 5.3 of the PWS located at Section B.5 – DB Merger

(OPTIONAL TASK #3)

IAW paragraph 5.4 of the PWS located at Section B.5.

(OPTIONAL TASK #3)

Installation Acceptance Form IAW paragraph 5.4 of the PWS located at Section B.5

(OPTIONAL TASK #3)

Equipment Inventory List IAW paragraph 5.4 of the PWS located at Section B.5

(OPTIONAL TASK #3)

Functional DMLSS/LogiCole Interface IAW paragraph 5.4 of the PWS located at Section B.5.

B.5 PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology Enterprise Program Management Office

Point of Use (POU) Integration – PAR Excellence (ParEX)

Date: September 16, 2021

VA-21-00070898

PWS Version Number: 1.0

1. BACKGROUND

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

The VA’s Supply Chain delivers clinical care to Veterans by managing the flow of supplies and equipment. Both the Point of Use Family of Systems (POU-FOS) and Defense Medical Logistics Standard Support (DMLSS/LogiCole) System are part of the Supply Chain Management Product Line (SCM PL). POU standardization and modernization is a SCM PL initiative that will increase the efficiency of on-hand inventory and management of consumable supplies, enhance logistics support to clinicians, provide on-time availability of medical supplies, improve healthcare to the Veteran and streamline POU solutions to achieve cost and maintenance savings.

The SCM PL is currently comprised of a set of antiquated legacy and Commercial of the Shelf (COTS)/ Government off the Shelf (GOTS) Systems with disjointed capabilities. Integration of POUs with DMLSS/LogiCole supports the SCM PL modernization initiative of implementing a fully integrated supply chain solution that provides the full spectrum of medical logistics. The DMLSS/LogiCole Project is an inter-agency project between the VA and the Department of Defense (DoD) to implement one supply chain system at VA. DMLSS/LogiCole is a Government Off the Shelf (GOTS) product that provides material management capabilities to include supply chain management, medical/surgical supplies and pharmaceuticals, inventory management, procurement support, equipment accountability and maintenance, and facilities management.

DMLSS/LogiCole is software that is owned, delivered, and managed remotely by the Defense Health Agency (DHA) Government integration Joint Medical Logistics Functional Development Center (JMLFDC), under the DHA, Solution Deliver Division (SDD), Chief Information Office/Deputy Assistant Director, Information Operations (DAD IO/J-6). DMLSS/LogiCole implementation will develop interfaces between DMLSS and VA systems through a Health Connect (HC) to Defense Automated Addressing System (DAAS) interface to include: The Financial Management System (FMS), the Credit Card System (CCS) and Integrated Funds Distribution Control Point Activity, Accounting and Procurement (IFCAP), Electronic Contracting Management System (eCMS), Federal/Non-Federal Receiving Reports (IFRR and INRR, respectively), and POUs.

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”

1. “Federal Information Security Modernization Act of 2014”

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

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

1. FIPS Pub 200, Minimum Security Requirements for Federal Information and Information Systems, March 2016

1. FIPS Pub 201-2, “Personal Identity Verification of Federal Employees and Contractors,” August 2013

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

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

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

1. Public Law 109-461, Veterans Benefits, Health Care, and Information Technology Act of 2006, Title IX, Information Security Matters

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

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

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

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

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

1. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016

1. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”

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

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

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

1. VA Directive 6500, “VA Cybersecurity Program,” January 24, 2019

1. VA Handbook 6500, “Risk Management Framework for VA Information Systems – Tier 3: VA Information Security Program,” March 10, 2015

1. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI)”, July 28, 2016

1. VA Handbook 6500.3, “Assessment, Authorization, And Continuous Monitoring Of VA Information Systems,” February 3, 2014

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

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

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

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

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

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

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

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

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

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

1. VA Directive 6300, Records and Information Management, September 21, 2018

1. VA Handbook, 6300.1, Records Management Procedures, March 24, 2010

1. NIST SP 800-37 Rev 1, Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy, December 2018

1. NIST SP 800-53 Rev. 4, Security and Privacy Controls for Federal Information Systems and Organizations, January 22, 2015

1. OMB Memorandum, “Transition to IPv6”, September 28, 2010

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

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

1. OMB Memorandum M-06-18, Acquisition of Products and Services for Implementation of HSPD-12, June 30, 2006

1. OMB Memorandum 04-04, E-Authentication Guidance for Federal Agencies, December 16, 2003

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

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

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

1. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011

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

1. OMB Memorandum M-07-16, Safeguarding Against and Responding to the Breach of Personally Identifiable Information, May 22, 2007

1. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, Digital Identity Guidelines, December 2017

1. NIST SP 800-157, Guidelines for Derived PIV Credentials, December 2014

1. NIST SP 800-164, Guidelines on Hardware-Rooted Security in Mobile Devices (Draft), October 2012

1. Draft National Institute of Standards and Technology Interagency Report (NISTIR) 7981 Mobile, PIV, and Authentication, March 2014

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

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

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

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

1. OMB Memorandum M-08-05, “Implementation of Trusted Internet Connections (TIC), November 20, 2007

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

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

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

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

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

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

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

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

1. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access”, January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28

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

1. “Veteran Focused Integration Process (VIP) Guide 3.2”, December 2018, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

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

1. DMLSS Legacy – Point of Care Inventory Management System (POC-IMS) Interface Specification

1. DMLSS Legacy –Point of Care Inventory Management System (POC-IMS) Interface Data Map

3.0 SCOPE OF WORK

The Contractor shall provide technical services in support of ParEx Supply POU installation at VA SimLearn Centers, to include hardware and software required at the sites. This includes configuring the ParEx system to communicate with the VA’s material management system to send data to DMLSS/LogiCole using the new Point of Care (POC) interface according to the DMLSS Legacy POU Smart Shelf System Interface Specification and Data Map documents listed in Section 2 (Documents 71 and 72). The Contractor shall provide installation, testing, and troubleshooting technical support. The exchange of inventory information between the ParEx system and DMLSS/LogiCole via the DMLSS Point of Care Interface falls into the following categories:

Required:

· Order Request (ORD) from POU to DMLSS/LogiCole containing resupply requests.

· Item Master Update (IMU) from DMLSS/LogiCole to POU containing inventory tracking requirements, to synchronize catalog information in both DMLSS and ParEx system.

· Advance Shipping Notice (ASN) from DMLSS/LogiCole to POU containing resupply delivery lists, confirming items that will be restocked in the ParEx cabinets.

Optional:

· Order Status for Status of an entire order.

· Order Line Status for Status on a specific line of an order.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The Period of Performance (PoP) shall consist of a base period of 12 months from date of award, with two (2) 12-month option periods, if exercised. There are also three (3) Optional Tasks, each of which may be exercised at any time during the base period and each of the option periods. Depending upon the date exercised, the PoP for each Optional Task may be up to, but shall not exceed, twelve (12) months in duration. The overall PoP shall not exceed 36 months.

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

Under current definitions, five (5) are set by date:

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:

Tasks under this PWS shall be performed at Contractor facilities. The Contractor shall identify the Contractor’s place of performance in their proposal submission.

4.3 TRAVEL (COST REIMBURSABLE)

The Government anticipates travel under this effort for Section 5.1 and Optional Task 3 under Section 5.4 when virtual vendor support is not sufficient.

The total estimated number of trips in support of equipment installation for this effort is eight (8) trips per exercise over the life of the TO. Anticipated locations are at VA Simulation Centers as listed in the link below. https://www.simlearn.va.gov/SIMLEARN/Certified_Simulation_Centers_SimLEARN.asp

Travel shall be in accordance with the Federal Travel Regulations (FTR) and requires advanced concurrence by the COR. The Contractor shall provide cost estimates with each travel request. Each Contractor invoice shall include copies of all receipts that support the travel costs claimed in the invoice. Contractor travel within the local commuting area will not be reimbursed. Also, not reimbursable are travel performed for personal convenience or daily travel to and from work at the Contractor’s facility.

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PAR EXCELLENCE SUPPLY POU HARDWARE AND SOFTWARE INSTALLATION

The Contractor shall provide technical services in support of ParEx Supply POU installation at VA SimLearn Centers to include hardware and software required at the site. The Contractor shall equip one (1) supply distribution point at each SimLearn Center to support VA Supply Chain initiatives. One (1) site in the Base Period and one (1) site in each of the Option Periods (three (3) sites in total for the entire contract PoP) shall receive the technical services, to include hardware and software required at the site, as stated above.

After completion of the installation, the Contractor shall deliver an Installation Acceptance Form signed by the designated site facility manager to verify installation completion and Equipment Inventory List.

The contractor shall also perform the following tasks to integrate the ParEx Supply System with the DMLSS/LogiCole material management system at the facility:

The Contractor shall conduct the following test/validation events:

The Contractor shall provide a Test Plan (TP) and Test Scripts to support integration testing efforts. The Test Plan should describe the test strategy, objectives, schedule, estimation, deliverables, and resources required to perform integration testing. The Test Scripts should include but not be limited to the test id, description, module name, pass/fail, tester information, and re-test.

Deliverables:

5.2 PAREX INTEGRATION (OPTIONAL TASK#1)

If exercised, the Contractor shall provide technical support needed to integrate ParEx Supply POU systems with DMLSS/LogiCole at sites where the ParEx System is implemented, and the DMLSS/LogiCole materiel management system will be deployed. This optional task may be exercised at any time during the period of performance for one (1) or more additional sites, up to a maximum of 87 sites during the base and option periods.

The contractor shall perform the following tasks:

1. Assist and provide input to the site-specific project plans to reconfigure the POC interface. DMLSS/LogiCole integration planning will begin at least three months prior to site DMLSS/LogiCole deployments. Integrations will be dependent on the DMLSS/LogiCole deployment schedule.

1. Provide status updates during a weekly working group call and input to the DMLSS/ParEx integration activities on the VA’s DMLSS/LogiCole Integrated Master Schedule.

1. Provide gap analysis on related POU business requirements.

1. Reconfigure, install, and test ORD, ASN, and IMU interfaces in the test environment.

1. Upon Government approval, reconfigure, install, and validate ORD, ASN, and IMU interfaces in the production environments.

1. Collaborate with the VA’s Cybersecurity Team in completing security packages and security assessments needed to process the ParEx supply system through the Office of Information Security (OIS) Risk Management Framework (RMF) and obtain an Authority to Operate (ATO) on the VA network.

1. Provide troubleshooting support during site’s cutover from GIP to DMLSS/LogiCole because of reconfiguring the interface to connect with DMLSS.

The Contractor shall conduct the following test/validation events:

1. Connectivity testing between POC interface (for ParEx), HealthConnect, and DMLSS/LogiCole at each site.

1. End-to-end validation of ORD, ASN, IMU interfaces with production data at each site.

Deliverables:

1. Functional DMLSS/LogiCole Interface

5.3 PAREX CLOUD MIGRATION (OPTIONAL TASK #2)

If exercised, the Contractor shall provide technical support to migrate the existing ParEx on-premises solution to the VA Enterprise Cloud. This migration would involve reconfiguring the ParEx application and database servers to support connections from multiple sites within a single VISN. The Contractor shall provide technical support needed to manage the ParEx solution in the VA Enterprise Cloud. This optional task may be exercised at any time during the period of performance for one (1) or more sites up to a maximum of 88 sites during the base and option periods.

5.4 PAR EXCELLENCE SUPPLY POU HARDWARE AND SOFTWARE INSTALLATION (OPTIONAL TASK #3)

The Contractor shall provide technical services in support of ParEx Supply POU installation at VA SimLearn Centers to include hardware and software required at the site. The Contractor shall equip one (1) supply distribution point at each SimLearn Center to support VA Supply Chain initiatives. This optional task may be exercised up to a total of six (6) times during the base and/or option periods.

After completion of the installation, the Contractor shall deliver an Installation Acceptance form and Equipment Inventory List. Once installation is complete, the Contractor shall gain approval from the Government COR and facility manager to verify installation completion.

The contractor shall also perform the following tasks to integrate the ParEx Supply System with the DMLSS/LogiCole material management system at the facility:

The Contractor shall conduct the following test/validation events:

Deliverables:

· Installation Acceptance

· Equipment Inventory List

· Functional DMLSS/LogiCole Interface

5.5 OPTION PERIODS

If Option Periods One (1) through Two (2) are exercised by the Government, all the tasks and deliverables in Section 5.1 shall apply. The Government has the discretion to exercise Optional Task One (Section 5. 2), Optional Task Two (Section 5.3), and/or Optional Task Three (Section 5.4) during the base and option periods.

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, https://www.oit.va.gov/library/recurring/edp/index.cfm. The Contractor shall ensure all Contractor delivered applications and systems comply with the VA Identity, Credential, and Access Management policies and guidelines set forth in 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.

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

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

1. Multiple authenticators for a given identity and authenticators at every Authenticator Assurance Level (AAL) appropriate for the solution.

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

1. Federation for each Federation…