S02 - 36C10B20R0009_3.docx

36C10B20R0009

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

36C10B20R0009 8-24-2020

KEIAHNA BREWER, CONTRACT SPECIALIST

732-440-9686 8-31-2020

3PM EST

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

X

541519 $30 Million

N/A

See Delivery Schedule

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

Please see Section B.1 Contract Administration Data

Commercial Off-The-Shelf (COTS) Software as a Service (SaaS) Facilities Management Solution Software.

Period of Performance – one, 9-month base period with four, 12-month

12-month option periods.

Points of Contact:

Contract Specialist

Keiahna Brewer/ Keiahna.Brewer@va.gov/ 732-440-9686 Contracting Officer

Peter Lewandowski/ Peter.Lewandowski@va.gov/ 732-440-9640

ARM #: TBD PO #: TBD SPI #: TBD

Peter Lewandowski 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:

a. CONTRACTOR: TBD

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:

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.

Please see Section B.1 Contract Administration Data 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 optimizing software, as well as remedying defects. It shall include all new fixes, patches, releases, updates, versions and upgrades, as further defined below.

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

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

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

(2). Software License.

a) Unless otherwise stated in the Schedule of Supplies/Services, the Performance Work Statement or Product Description, the software license provided to the Government is a perpetual, nonexclusive license to use the software.

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

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

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

(3). Software Maintenance and Technical Support.

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

b) The Contractor shall provide software support services, which includes periodic updates, enhancements and corrections to the software, and reasonable technical support, all of which are customarily provided by the Contractor to its commercial customers 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 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).

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

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

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

B.4 PRICE SCHEDULE

BASE PERIOD – 9 months

This CLIN includes all services and reports required for the successful completion of the services detailed in Paragraphs 5.1 and all subsequent subparagraphs in the Performance Work Statement (PWS).

Contractor shall perform project management IAW PWS Section 5.1 and all subsequent subparagraphs.

The cost of this CLIN shall be amortized across all priced CLINS.

The Contractor shall provide a CPMP IAW PWS Paragraph 5.1.1.

Due 30 Days After Contract Award (DAC) and updated monthly thereafter.

The cost of this SLIN shall be amortized across all priced CLINS.

Electronic submission to: VA Project Manager (PM), Contracting Officer Representative (COR), Contracting Officer (CO), Contract Specialist (CS) Inspection: destination Acceptance: destination

The Contractor shall provide Monthly Progress Report IAW PWS Paragraph 5.1.2.

Due the fifth day of each month throughout the Period Of Performance (PoP).

The cost of this SLIN shall be amortized across all priced CLINS.

Electronic submission to: VA PM, COR, CO, CS Inspection: destination Acceptance: destination

Contractor shall install, configure, test and attain FedRAMP and Authority to Operate (ATO) approval.

In Accordance With (IAW) PD paragraph 5.5 and all applicable sub-paragraphs.

Delivery/Due: Shall be delivered No Later Than (NLT) 6 months after receipt of award.

· 30 days after award: Completed FedRAMP System Security Plan (SSP) and supporting documentation (10% of base period contract value billable upon receipt)

· 75 days after award: 3PAO Security Assessment Plan (SAP) (10% of base period contract value billable upon receipt)

· 90 days after award: 3PAO Security Assessment Report (SAR) (10% of base period contract value billable upon receipt)

The remaining 70% will be billable when all ATO work is complete.

Electronic submission to: VA PM, COR, CO, CS Inspection: destination Acceptance: destination

The cost of this Subcontract Line Item Number (SLIN) shall be included under Contract Line Item Number (CLIN) 0002.

Electronic submission to: VA PM, COR, CO, CS.

Inspection: destination Acceptance: destination

The cost of this SLIN shall be included under CLIN 0002.

Electronic submission to: VA PM, COR, CO.

Inspection: destination Acceptance: destination

The cost of this SLIN shall be included under CLIN 0002.

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

This CLIN includes all services and reports required for the successful completion of the services detailed in Paragraphs 5.1 and all subsequent subparagraphs in the

PWS.

Contractor shall perform project management IAW PWS Section 5.1 and all subsequent subparagraphs.

The cost of this CLIN shall be included under CLIN 1003

The Contractor shall provide a CPMP IAW PWS Paragraph 5.1.1.

Due 30 Days After Option Exercise and updated monthly thereafter.

The cost of this CLIN shall be included under CLIN 1003

Electronic submission to: VA PM, COR, CO, CS Inspection: destination Acceptance: destination

The Contractor shall provide Monthly Progress Report IAW PWS Paragraph 5.1.2.

Due the fifth day of each month throughout the PoP.

The cost of this CLIN shall be included under CLIN 1003

Electronic submission to: VA PM, COR, CO, CS Inspection: destination Acceptance: destination

Contractor shall provide COTS SaaS FMS IAW PWS paragraph 5.2

Number of licenses - 1500

Contractor shall provide facilities management solution integration support IAW PWS Paragraph 5.3 and all subsequent subparagraphs.

Contractor shall provide Project Plan IAW PWS Paragraph 5.3.1.

Due 15 Days after option exercised updated monthly thereafter.

Electronic submission to: VA PM, COR, CO, CS.

Inspection: destination Acceptance: destination

Cost of this SLIN shall be under CLIN 1003

Contractor shall provide Data Migration Templates IAW PWS Paragraph 5.3.1.

Due 15 days after option exercise and updated monthly thereafter.

Electronic submission to: VA PM, COR, CO, CS.

Inspection: destination Acceptance: destination

Cost of this SLIN shall be under CLIN 1003.

Contractor shall provide UAT Report IAW PWS Paragraph 5.3.9.

Due 15 days after option exercise and updated throughout the PoP.

Electronic submission to: VA PM, COR, CO.

Inspection: destination Acceptance: destination

Cost of this SLIN shall be under CLIN 1003.

Contractor shall provide UAT Defect and Resolution Report IAW PWS Paragraph 5.3.9.

Due 15 DAC award and updated throughout the PoP.

Cost of this SLIN shall be under CLIN 1003.

Contractor shall provide production technical support IAW PWS Paragraph 5.3.10.

The Contactor shall provide personnel-based training sessions to VA users and administrators IAW PWS Paragraph 5.3.11.

Contractor shall provide training manuals IAW PWS Paragraph 5.3.11.

The cost of this SLIN shall be included under SLIN 1003AN.

Contractor shall provide FMS Solution Post-Production Customer Support IAW PWS Paragraph 5.4.

Contractor shall provide Contractor Staff Roster IAW PWS Paragraph 6.2.

Electronic submission to: VA PM, COR, CO.

Inspection: destination Acceptance: destination

The cost of this CLIN shall be amortized across all priced CLINS.

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

Contractor shall provide COTS SaaS FMS IAW PWS paragraph 5.2.

Number of licenses - 1500

Contractor shall provide FMS Solution Post-Production Customer Support IAW PWS Paragraph 5.4.

CONTRACTOR STAFF ROSTER

Contractor shall provide Contractor Staff Roster IAW PWS Paragraph 6.2.

Electronic submission to: VA PM, COR, CO.

Inspection: destination Acceptance: destination

The cost of this CLIN shall be amortized across all priced CLINS.

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

Contractor shall provide COTS SaaS FMS IAW PWS paragraph 5.2.

Number of licenses - 1500

Contractor shall provide FMS Solution Post-Production Customer Support IAW PWS Paragraph 5.4.

CONTRACTOR STAFF ROSTER

Contractor shall provide Contractor Staff Roster IAW PWS Paragraph 6.2.

Electronic submission to: VA PM, COR, CO.

Inspection: destination Acceptance: destination

The cost of this CLIN shall be amortized across all priced CLINS.

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

Contractor shall provide COTS SaaS FMS IAW PWS paragraph 5.2.

Number of licenses - 1500

Contractor shall provide FMS Solution Post-Production Customer Support IAW PWS Paragraph 5.4.

CONTRACTOR STAFF ROSTER

Contractor shall provide Contractor Staff Roster IAW PWS Paragraph 6.2.

Electronic submission to: VA PM, COR, CO.

Inspection: destination Acceptance: destination

The cost of this CLIN shall be amortized across all priced CLINS.

B.5 PERFORMANCE WORK STATEMENT

Page 1 of Page 1 of

1.0 BACKGROUND

The Department of Veterans Affairs (VA), Office of Management, Financial Services Center (FSC) is an organization in VA. Under the authority of "The Government Management Reform Act of 1994" and "The Military Quality of Life and Veterans Affairs Appropriations Act, 2006, Public Law 109-114", FSC offers a wide range of financial, accounting, and facility management products and services to both VA and Other Government Agencies (OGA).

Full life-cycle facilities asset management can no longer be properly achieved using old, legacy technologies. The growing strategic role along with the cost and visibility of facilities demands a modern, cloud-based alternative to legacy solutions.

VA FSC is now modernizing their Facilities Management Solution (FMS) in order to optimize processes for facilities, operating technologies and employees in order to efficiently manage employee locations, office moves, relocations, and consolidation of office space. The Contractor shall serve as the single point of contact for all elements of the solution to include installation, necessary computing platforms, integration services, and software support as required.

The Federal Chief Information Officer (CIO) has confirmed that for Software as a Service (SaaS), agencies have the option of: (1) leveraging a Provisional Authority to Operate (ATO) completed by the Joint Authorization Board (JAB); (2) leveraging an ATO completed by another agency, or (3) conducting their own ATO. However, if either the Joint Authorization Board or another agency has already gone through the Risk Management Framework process with the cloud service provider then we encourage the agency to leverage the work already done. This is less burdensome for both the agencies and the service providers.

Regardless of the approach, VA will be using the Federal Risk and Authorization Management Program (FedRAMP) baselines as a starting point, since they are specifically tailored for cloud services.

2.0 APPLICABLE DOCUMENTS

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

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

2. “Federal Information Security Modernization Act of 2014”

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

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

5. FIPS Pub 200, Minimum Security Requirements for Federal Information and Information Systems, March 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, https://www.va.gov/vapubs/index.cfm

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

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

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

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. NIST SP 800-66 Rev. 1, 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, “VA Cybersecurity Program,” January 24, 2019

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

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

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

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

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

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

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

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 and Handbook 6513, “Secure External Connections”, October 12, 2017

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

3.0 SCOPE OF WORK

The Contractor shall provide a Commercial off-the-Shelf (COTS) SaaS FMS that will optimize processes for facilities, operating technologies and employees in order to efficiently manage employee locations, office moves, relocations, and consolidation of office space. The Contractor shall also provide FMS integration support, to include program initiation tasks, FMS setup and design, data migration, asset management, work order management, portal management, floor mapping, space and planned move management, user acceptance testing, production technical support, and training. Additionally, the Contractor shall provide FMS solution post-production customer support and assessment, authorization and continuous monitoring. This maintenance, support and equipment and the Contractor shall serve as the single point of contact for all elements of the solution to include installation, necessary computing platforms, integration services, and software support as required.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The Period of Performance (PoP) shall be one, nine-month base period to complete ATO with four, 12-month option periods, if exercised by the Government.

Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO). (If required, the CO may designate the Contractor to work during holidays and weekends)

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

Under current definitions, four 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:

4.2 PLACE OF PERFORMANCE

Efforts under this contract shall be performed at Contractor Facilities. The Contractor shall identify the Contractor’s place of performance in their proposal.

4.3 TRAVEL

The Government does anticipate travel to perform the tasks associated with the effort, as well as to attend program-related meetings throughout the PoP. Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government.

The total estimated number of trips in support of the program related meetings for this effort is four. Anticipated locations include the following, estimated at two days in duration:

1. 7600 Metropolis Drive Austin, Texas (TX) 78744.

Travel to Austin, Texas would typically involve program-related meetings, and travel to VA Facilities would typically involve program-related meetings and/or training sessions. Meetings should be held virtually whenever possible

4.4 GOVERNMENT FURNISHED PROPERTY

The Government will provide complete information and documents on a timely basis which are reasonably requested by the Contractor for the proper performance of this contract. VA will provide the following information, documents, and server access:

· VA will provide data in a conforming format (excel, csv, or xml)

· VA will review and sign-off on all user stories prior to the start of each sprint

· VA will provide DXF files

· VA will provide access to a server for DXF file ingestion and/or any requested integrations

5.0 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall perform the following:

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN

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

Deliverable:

A. Contractor Project Management Plan

5.1.2 REPORTING REQUIREMENTS

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

The Monthly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The report shall also include an itemized list of all Information and Communication Technology (ICT) deliverables and their current Section 508 conformance status. The Contractor shall monitor performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues.

Deliverable:

A. Monthly Progress Report

5.2 FACILITIES MANAGEMENT SOLUTION SAAS SOLUTION

The Contractor shall provide a COTS FedRAMP - Low Impact Level approved SaaS FMS that will optimize processes for facilities, operating technologies and employees in order to efficiently manage employee locations, office moves, relocations, and consolidation of office space.

SaaS is an application delivery model in which the application is hosted on a cloud infrastructure outside the security boundary of VA and is provided to the Cloud Service Customer (CSC) over the internet (Software hosted in VA Enterprise Cloud does not meet this definition of SaaS). The CSC uses the SaaS offering via a thin-client interface, such as a web-browser or a program interface. The CSC subscribes to the SaaS offering and is only responsible for limited application configuration settings. The Cloud Service Provider (CSP) offering the application is responsible for management of the application, safeguarding of data stored or processed by the application, and all elements of the underlying infrastructure.

In order to qualify as SaaS for use at VA, and to align with FedRAMP requirements, the hosting for the offering must conform to the NIST 800-145 definition of Cloud Computing and thus contain following key characteristics:

· On-Demand Self-Service: The CSP fully automates the provisioning of both the customer interface and the underlying cloud components of the SaaS offering. In some cases, the CSP may provision internal resources manually, while providing the CSC an automated interface to request and track the service.

· Broad Network Access: The SaaS capabilities are available over the internet or over a network that is available from all access points the CSC requires. The SaaS offering is accessible through common platforms (e.g., mobile phones, tablets, laptops, and workstations).

· Resource Pooling: The computing infrastructure supporting the SaaS offering is shared among more than one CSC using a multi-tenant model, and resources are dynamically assigned depending on customer demand.

· Rapid Elasticity: Computing capabilities are automatically provisioned and released in a manner that scales with customer demand. In some cases, the scaling of resources may not be fully automated, but it should be fast enough to support the needs of the CSC, which the CSC would have to define.

· Measured Service: Resource usage, such as storage, processing, bandwidth, and user activity are measured and reported on in a manner that is relevant to the SaaS offering.

The SaaS offering must be hosted within the United States and data stored/processed/transmitted within the offering must remain within the United States.

The FMS SaaS Solution shall:

· Run on a cloud infrastructure and shall be accessible from various client devices through either a thin client interface, such as a web browser (e.g., web-based email) or a program interface.

· Not require download of software to VA computers.

· Support 5 Facility Managers (Administrators).

· Support up to 1,500 users, up to 800 simultaneous users.

The VA shall not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or individual application capabilities.

The system shall be vendor or third-party hosted and require no servers within VA. There is no interface required to be developed or customization to the vendor hosted solution being requested. All proprietary data processed by SaaS provider shall be owned by SaaS provider/user. The contractor shall have the right to use any Government furnished information throughout the life of the contract for the purpose of performing this specific Contract.

The following details the required FMS SaaS solution functionality that shall be implemented:

· Space Management

· Asset Management

· Strategic Planning

· Facility Maintenance

· Move Management

· Employee Emergency Contact Information Management

· Vehicle information

· Parking Pass Management

· Room and Seat Scheduling and Reservation

· Facility Requests

· Work Requests

· Supply Requests

· On-boarding and Exiting Employee Requests.

· Ability to access and analyze facilities, real estate and maintenance information in real time.

Software must be a SaaS solution that is FedRAMP - Low Impact Level compliant at the time of award.

5.3 FACILITIES MANAGEMENT SOLUTION INTEGRATION SUPPORT

The Contractor shall provide integration support to ensure that the COTS FedRAMP approved SaaS FMS is tailored to the FSC’s specific organizational needs. The Contractor shall integrate the solution through an agile software development methodology. This will include short development cycles, known as sprints, that involve close coordination with customer stakeholders to provide constant feedback.

The following details the specific tasks required to integrate the FMS solution functionality into the FSC organization:

5.3.1 PROGRAM INITIATION TASKS:

The Contractor shall perform the following program initiation tasks after contract award and submit findings in a VA approved Project Plan:

· Schedule remote project kickoff meeting for introductions

· Provide templates to VA for FMS data migration

· Review FMS project roles and responsibilities

· Review of internal VA organizational or cultural issues or constraints

· Review of VA project approval processes to avoid unnecessary delays

· Develop sprint cycle and project sequence of requirements with VA

· Understand VA security requirements and approvals

· Review escalation processes

· Review VA FMS business requirements

· Refine FMS project plan with task dates

· Define FMS scrum call schedule

· Determine Subject Matter Experts from VA

Deliverables:

A. Project Plan B. Data Migration Templates

5.3.2 FMS SETUP AND DESIGN

The Contractor shall install the most recent version of the FMS onto the VA platform. Then the Contactor shall complete the following tasks for the setup and design of the FMS:

· Upload logo, configure banner text and configure welcome page content for login page

· Deactivate modules out of scope for the Engagement

· Assist with the loading of group, location and department data

· Configure list layouts, landing page, style sheets, and navigation

· Configure system roles and security groups

· Configure the system default date format, time format and time zone

· Configure groups to contain specified roles and associate users to inherit such roles

· Confirm POP3-SMTP e-mail is operational and set e-mail override properties for development

· Configure e-mail catch-box for non-production instance

· Set up admin access for project and engagement managers

· Identify key user and metadata to be brought into the application

5.3.3 DATA MIGRATION

The Contractor shall complete the following tasks in support of data migration:

· Ensure conforming format (excel, csv, or xml)

· Ensure VA data conforms to FMS Data Dictionary

· Import all active assets including; Space management information and floor plans, employee information, facility maintenance information including (1) year of work order data, move management information including (1) year of move order data, system admin information.

5.3.4 ASSET MANAGEMENT

The Contractor shall complete the following tasks in support of asset management:

· Create required new asset classes

· Define or extend attributes

· Modify rules

· Update configuration item fields

· Update assets

· Create new assets

· Configure pre-allocated and fixed assets

· Set asset states and sub-states

· Retire related assets rules

· Configure asset life cycle workflow

· Creation of asset onboarding workflow

· Creation of preventative maintenance scheduling workflow

· Creation of asset retirement workflow

5.3.5 WORK ORDER MANAGEMENT

The Contractor shall complete the following activities and tasks in support of work order management:

· Enable out-of-the-box asset states and sub-states

· Configure work order types

· Complete work order assignment groups, security groups and group hierarchy

· Enable work order routing rules

· Operationalize outbound notifications and inbound creation configuration

· Enable out-of-the-box escalations and state workflow

· Enable properly assigned work order to groups and users within Customer’s structure

· Transfer and configure work order checklists from work instructions in current application(s)

· Configure Checklist assignment rules by Asset Model, Asset ID and Work Order Type

· Enable out-of-the-box Service Level Agreements (SLA) and inactivity rules

· Define SLA start, stop and pause conditions

· Define the following SLA stages:

· In progress

· Achieved

· Breached

· Cancelled

· Paused

· Completed

· Define SLA automation criteria

· Configure SLA time stamps by work order stage

· Enable e-mail notifications to the appropriate assignment group and assignees at specific stages of the work order workflow and to end users

5.3.6 PORTAL MANAGEMENT

The Contractor shall complete the following tasks in support of the portal management:

· Enable the out-of-the-box portal and landing page functionality

· Create top level reporting dashboard

· Update the portal with appropriate VA branding

· Logo

· Color Scheme

· Enable request catalog

· Configure persona-based dashboard

· Configure navigation links

· Create up to five (5) configured reports with VA using the reporting engine

5.3.7 FLOOR MAPPING

The Contractor shall complete the following tasks in support of floor mapping:

· Gather and load DXF files only

· Analyze DXF files to determine and configure space profile

· Migrate up to fifteen (15) DXF files into the module

· Configure rules for DXF file import on a regular basis

· Configure one (1) move management workflow to align with organization process and approvals

· Configure user and asset data relationships

· Configure all business rules, UI policies and client scripts

· Complete location hierarchy

· Unit test interactive floor maps with all personas

· Executive

· Manager

· Technician

5.3.8 SPACE AND PLANNED MOVE MANAGEMENT

The Contractor shall complete the following tasks in support of space and planned move management:

· Setup and configure Departments to meet customer needs

· Setup and configure Regions to meet customer needs

· Setup and configure Campuses to meet customer needs

· Setup and configure Sites to meet customer needs

· Setup and configure Floors to…