36C10B19Q0193-001.pdf

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 76

36C10B19Q0193 2-14-2019

Jessica Adamitis - Contract Specialist 732-440-9704 2-21-2019

12:00PM EST

Department of Veterans Affairs

Technology Acquisition Center

23 Christopher Way

Eatontown NJ 07724

X 100

X

Y

541512

$27.5 Million

N/A

See Delivery Schedule

Financial Services Center

PO Box 149971

Austin TX 78714-8971

See CONTINUATION Page

VA Integrated Master Schedule (IMS) Support

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

Work Statement.

This Request for Proposal (RFP) will result in a

Firm-Fixed-Price (FFP) contract.

Offerors will be evaluated in accordance with Section E.

This is a Service-Disabled Veteran-Owned Small Business

(SDVOSB) set-aside in accordance with VAAR 852.219-10

VA Notice of Total Service-Disabled Veteran-Owned Small ness

Business set-aside.

See CONTINUATION Page

X X

36C10B19Q0193

Table of Contents

SECTION A

A.1 SF 1449 SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATIVE DATA

B.2 GOVERNING LAW

B.3 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT

B.4 PRICE SCHEDULE

B.5 PERFORMANCE WORK STATEMENT

SECTION C - CONTRACT CLAUSES

C.1 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

C.2 52.204-21 BASIC SAFEGUARDING OF COVERED CONTRACTOR INFORMATION

SYSTEMS (JUL 2016)

C.3 52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT

STATUTES OR EXECUTIVE ORDERS—COMMERCIAL ITEMS (JAN 2019)

C.4 52.217-7 OPTION FOR INCREASED QUANTITY—SEPARATELY PRICED LINE ITEM

(MAR 1989)

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

C.6 VAAR 852.203-70 COMMERCIAL ADVERTISING (MAY 2018)

C.8 VAAR 852.219-10 VA NOTICE OF TOTAL SERVICE-DISABLED VETERAN-OWNED

SMALL BUSINESS SET-ASIDE (JUL 2016) (DEVIATION)

C.9 VAAR 852.232-72 ELECTRONIC SUBMISSION OF PAYMENT REQUESTS (NOV

2018)

C.10 VAAR 852.237-70 CONTRACTOR RESPONSIBILITIES (APR 1984)

C.11 VAAR 852.270-1 REPRESENTATIVES OF CONTRACTING OFFICERS (JAN 2008) . 55

SECTION D - CONTRACT DOCUMENTS, EXHIBITS, OR ATTACHMENT

SECTION E - SOLICITATION PROVISIONS

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

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

E.3 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—COMMERCIAL

ITEMS (OCT 2018)

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

E.6 VAAR 852.233-70 PROTEST CONTENT/ALTERNATIVE DISPUTE RESOLUTION

(JAN 2008)

E.7 VAAR 852.233-71 ALTERNATE PROTEST PROCEDURE (MAY 2010)

E.8 BASIS FOR AWARD

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATIVE DATA

(continuation from Standard Form 1449, block 18A.)

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

a. CONTRACTOR: TBD

b. GOVERNMENT: Contracting Officer 36C10B

Technology Acquisition Center

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

3. INVOICES: Invoices shall be submitted in arrears:

a. Quarterly []

b. Semi-Annually []

c. Other [X] Upon Government Acceptance of services and associated

Deliverables in Section B.4

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

Payment Requests.

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

AMENDMENT NO DATE

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.

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

Inspection/Acceptance//F.O.B: Destination.

All deliverables must be submitted electronically to the VA Program Manager (PM), Contracting

Officer’s Representative (COR), and Contracting Officer unless otherwise specified in the line item. Please be advised that in accordance with Federal Acquisition Regulation (FAR) Part

2.101, a “day” means, unless otherwise specified, a CALENDAR day. Additionally, deliverables with due dates falling on a weekend or holiday shall be submitted the following Government work day after the weekend or holiday.

The Price Schedule contains contract line items identified as not separately priced (NSP). This means the price for the line item is included in the price of another, related line item. The

Contractor shall not invoice the Government for any portion of the contract line item which contains an NSP until the Contractor has delivered the total quantity of all related contract line items and the Government has accepted them.

NOTE: Vendors are instructed to see solicitation Section E for quote submission instructions inclusive of the price proposal. Vendors are cautioned that alterations to the line items as specified below may render quote unacceptable. All questions shall be directed to the Contract

Specialist, Jessica Adamitis, Jessica.Adamitis@va.gov and Contracting Officer, Juan Quinones, Juan.Quinones@va.gov prior to the closing date and time specified in the Request for Quote

(RFQ).

BASE PERIOD

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

Contract

Line

Item

Number

(CLIN)

Description Qty Unit Unit Price Total Price

0001 Project Management in accordance with

(IAW) Performance Work Statement

(PWS) Task 5.1 and its subtasks.

Period of Performance (PoP) shall be for 12 months from award.

This CLIN includes all tasks, labor, and travel required for the successful completion of the services details in PWS Section 5.1 and its subtasks.

The price of project management tasks and deliverables shall be allocated to CLINs 0002 through 0005.

12 Month

(MO)

NSP NSP

0001AA Contractor Project Management Plan IAW

PWS Task 5.1.1.

Due 30 days after contract (DAC) and

12 MO NSP NSP

mailto:Jessica.Adamitis@va.gov mailto:Juan.Quinones@va.gov updated monthly thereafter.

0001AB Monthly Progress Report IAW PWS Task

5.1.2.

Due 30 DAC and updated monthly thereafter

0001AC VA Privacy and Information Security

Awareness and Rules of Behavior Training

Certificate IAW PWS Task 5.1.3.

Due five DAC and updated annually as required for all Contractor employees.

1 Lot

(LO)

NSP NSP

0001AD Signed Contractor Rules of Behavior IAW

PWS Task 5.1.3.

1 LO NSP NSP

0001AE VA HIPAA Certificate of Completion IAW

1 LO NSP NSP

0001AF Contractor Staff Roster IAW PWS 6.2.2.

Due three DAC and updated within one day of any changes.

1 LO NSP NSP

0002 Integrated Master Schedule (IMS)

Analysis IAW PWS Task 5.2.

1 LO NSP NSP

0002AA Schedule Government Document IAW PWS

Task 5.2.

Due within 60 days DAC.

1 LO $ $

0002AB IMS Strategy Briefing IAW PWS Task 5.2.

Due within 60 DAC.

The price for this CLIN is included in CLIN

0002AA.

0003 IMS Dashboard IAW PWS Task 5.3.

The price of this CLIN shall include all services associated with initial delivery of the

IMS Dashboard.

The Contractor shall provide the IMS

Dashboard within 20 days after Government

Acceptance of the Schedule Government

Document at CLIN 0002AA.

0003AA IMS Dashboard Maintenance IAW PWS

Task 5.3.

The price of this CLIN shall include all services associated with dashboard maintenance

PoP shall begin upon Government

Acceptance of the IMS Dashboard at CLIN

0003. Not to Exceed (NTE) 12 months.

NTE

MO $ NTE $

0004 IMS Support IAW PWS Task 5.4.

PoP shall begin upon Contractor completed onboarding and approval of Government

Furnished Equipment (GFE). NTE 12 months.

services details in PWS Section 5.4 and its subtasks.

NTE

MO $ NTE $

0005 Transition Out Planning IAW PWS Task

5.5.

Due 90 days prior to the end of the base period.

services details in PWS Section 5.5 and its subtasks.

1 LO $ $

0005AA Transition Plan IAW PWS Task 5.5. 1 LO NSP NSP

0005AB Asset List IAW PWS Task 5.5. 1 LO NSP NSP

TOTAL BASE PERIOD $

OPTION PERIOD 1

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

Period of Performance shall be for 12 months from expiration of the base period.

CLIN Description Qty Unit Unit Price Total Price

1001 Project Management in accordance with

(IAW) Performance Work Statement (PWS)

Task 5.1 and its subtasks.

PoP shall be for 12 months from option exercise.

This CLIN includes all tasks, labor, and travel required for the successful completion of the deliverables shall be allocated to CLINs 1002 through 1005.

1001AA Contractor Project Management Plan IAW

Shall be updated monthly.

1001AB Monthly Progress Report IAW PWS Task

Shall be updated monthly.

1001AC VA Privacy and Information Security

Updated annually as required for all Contractor employees.

1 LO NSP NSP

1001AD Signed Contractor Rules of Behavior IAW

1 LO NSP NSP

1001AE VA HIPAA Certificate of Completion IAW

1001AF Contractor Staff Roster IAW PWS 6.2.2.

Due three DAC and updated within one day of any changes.

1002 IMS Analysis IAW PWS Task 5.2.

Updated as needed throughout the PoP.

The price of services and deliverables shall be allocated to CLIN 1004.

1 LO NSP NSP

1002AA Schedule Government Document IAW PWS

1003 IMS Dashboard Maintenance IAW PWS

The price of this CLIN shall include all services associated with dashboard maintenance

PoP shall be for 12 months.

12 MO $ $

1004 IMS Support IAW PWS Task 5.4.

PoP shall be 12 months from option exercise.

services details in PWS Section 5.4 and its subtasks.

12 MO $ $

1005 Transition Out Planning IAW PWS Task

Due 90 days prior to the end of the option services details in PWS Section 5.5 and its subtasks.

1 LO $ $

1005AA Transition Plan IAW PWS Task 5.5. 1 LO NSP NSP

1005AB Asset List IAW PWS Task 5.5. 1 LO NSP NSP

TOTAL OPTION PERIOD 1 $

OPTION PERIOD 2

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

Period of Performance shall be for 12 months from expiration of the option period 1.

CLIN Description Qty Unit Unit Price Total Price

2001 Project Management in accordance with

(IAW) Performance Work Statement (PWS)

Task 5.1 and its subtasks.

PoP shall be for 12 months from option.

deliverables shall be allocated to CLINs 2002 through 2005.

2001AA Contractor Project Management Plan IAW

Shall be updated monthly thereafter.

2001AB Monthly Progress Report IAW PWS Task

Shall be updated monthly thereafter.

2001AC VA Privacy and Information Security

1 LO NSP NSP

2001AD Signed Contractor Rules of Behavior IAW

1 LO NSP NSP

2001AE VA HIPAA Certificate of Completion IAW

2001AF Contractor Staff Roster IAW PWS 6.2.2.

Due three DAC and updated within one day of any changes.

2002 IMS Analysis IAW PWS Task 5.2.

The price of services and deliverables shall be allocated to CLIN 2004.

1 LO NSP NSP

2002AA Schedule Government Document IAW PWS

2003 IMS Dashboard Maintenance IAW PWS

The price of this CLIN shall include all services associated with dashboard maintenance

PoP shall be for 12 months.

12 MO $ $

2004 IMS Support IAW PWS Task 5.4.

PoP shall be 12 months from option exercise.

services details in PWS Section 5.4 and its subtasks.

12 MO $ $

2005 Transition Out Planning IAW PWS Task

Due 90 days prior to the end of the option services details in PWS Section 5.5 and its subtasks.

1 LO $ $

2005AA Transition Plan IAW PWS Task 5.5. 1 LO NSP NSP

2005AB Asset List IAW PWS Task 5.5. 1 LO NSP NSP

TOTAL OPTION PERIOD 2 $

OPTIONAL TASK – TRANSITION SERVICES

This optional task may be exercised IAW FAR 52.217-7 Option for Increase Quantity – Separately Priced

Line Item (MAR 1989). Work shall not commence until, and unless, a formal modification is issued by the

Contracting Officer.

CLIN Description Qty Unit Unit Price Total Price

3001 Transition Services IAW PWS Task 5.8 and its subtasks.

Shall be completed within 30 days of option exercise.

services details in PWS Section 5.7 and its subtasks.

3001AA Closeout Certification IAW PWS Task 5.7.

Due upon completion of transition period.

TOTAL OPTIONAL TASK – TRANSITION SERVICES $

TOTAL CONTRACT $

B.5 PERFORMANCE WORK STATEMENT

Office of Information & Technology

Office of Technology Integration (OTI)

Integrated Master Schedule (IMS) Support

Date: February 5, 2019

TAC-19-54546

PWS Version Number: 1.0

1.0 BACKGROUND

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

(OIT), Office of Technology Integration (OTI) is to provide benefits and services to Veterans of the United States. In meeting these goals, OIT and OTI strive 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.

There is a need for an Integrated Master Schedule (IMS) to be developed and maintained for all ongoing and planned OIT specified programs. The primary purpose of the IMS is for use by the

Government to:

• Provide a day-to-day tool for executing the OIT Program with proper sequencing

• Identify and manage dependencies and predecessor tasks

• Track individual project work request and sprint/release schedules

• Analyze schedule status sufficiently to depict any significant risks and priority trade-offs, especially as these risks might relate to cross-system dependencies

• Strengthen effectiveness of Government communications across programs, to VA senior executive leadership, and oversight entities

• Provide early warning signs of issues and concerns regarding critical projects, sequencing and dependencies

• Share OIT IMS components with other major initiative IMS teams such as the new Office of Electronic Health Record Modernization that may have an impact on OIT project milestones and completion dates

2.0 APPLICABLE DOCUMENTS

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

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

2. 36 C.F.R. Part 1194 “Electronic and Information Technology Accessibility

Standards,” July 1, 2003

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

Information as a Strategic Resource,” July 28, 2016

4. OI&T ProPath Process Methodology (Transitioning to Process Asset Library (PAL)

(reference process maps at http://www.va.gov/PROPATH/Maps.asp and templates at http://www.va.gov/PROPATH/Templates.asp

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

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

7. “VIP Release Process Guide”, Version 1.4, May 2016, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4411

8. “POLARIS User Guide”, Version 1.2, February 2016, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4412 http://www.va.gov/PROPATH/Maps.asp http://www.va.gov/PROPATH/Templates.asp http://www.va.gov/trm/TRMHomePage.aspx https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4411 https://www.voa.va.gov/DocumentView.aspx?DocumentID=4412

3.0 SCOPE OF WORK

The Contractor shall provide technical, management, analysis, and support services to OIT OTI, to develop and maintain an IMS for all ongoing and planned OIT specified programs. The

Contractor shall also provide, configure and maintain an IMS reporting/dashboard system.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The Period of Performance (PoP) shall be one, 12-month base period with two, 12-month option periods, which may be exercised at the Government’s discretion. Optional Task 1, Transition

Support may be exercised once for a PoP of 30 days from option exercise.

Business hours are 8:00AM – 5:00PM (EST). Any work at the Government site shall not take place on Federal holidays or weekends unless directed by the Contracting Officer (CO). There are 10 Federal holidays set by law (USC Title 5 Section 6103) that VA follows:

Under current definitions, four are set by date:

New Year's Day January 1

Independence Day July 4

Veterans Day November 11

Christmas Day December 25

If any of the above falls on a Saturday, then Friday shall be observed as a holiday. Similarly, if one falls on a Sunday, then Monday shall be observed as a holiday.

The other six are set by a day of the week and month:

Martin Luther King's Birthday Third Monday in January

Washington's Birthday Third Monday in February

Memorial Day Last Monday in May

Labor Day First Monday in September

Columbus Day Second Monday in October

Thanksgiving Fourth Thursday in November

4.2 PLACE OF PERFORMANCE

Tasks under this PWS shall be performed at Contractor facilities. Contractors may be required to work in VACO (810/811 Vermont Ave, Washington, D.C 2001) on an as-needed basis and will be provided hoteling space as required.

4.3 TRAVEL

No travel is anticipated for this effort; however, in performance of PWS Task 5.2 and 5.4 the

Contractor shall be capable of meeting onsite with VA personnel within 8-hours of request.

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 and timeline 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 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 deliverables and their current 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.

A. Monthly Progress Report

5.1.3 PRIVACY TRAINING

The Contractor shall submit TMS training certificates of completion for VA Privacy and

Information Security Awareness and Rules of Behavior and Health Insurance Portability and

Accountability Act (HIPAA) training, and provide signed copies of the Contractor Rules of

Behavior in accordance with Section 9, Training, from Appendix C of the VA Handbook 6500.6, “Contract Security”.

Deliverables:

A. VA Privacy and Information Security Awareness and Rules of Behavior Training

Certificate

B. Signed Contractor Rules of Behavior

C. VA HIPAA certificate of completion

5.1.4 TECHNICAL KICK-OFF MEETING

The Contractor shall conduct a technical kickoff meeting within 10 days after contract award.

The Contractor shall present, for review and approval by the Government, the details of the intended approach to execute this contract. The Contractor shall discuss their project management processes for Schedule Management. The Contractor shall specify dates, locations

(can be virtual), agenda (shall be provided to all attendees at least five calendar days prior to the meeting), and a copy of the presentation. The Contractor shall invite the CO, Contract Specialist

(CS), COR, and the VA PM.

5.2 INTEGRATED MASTER SCHEDULE ANALYSIS

The Contractor shall perform overall general IMS analysis of standard VA IMS monitoring parameters to include but not limited to cost, schedule, performance, risk, and VA critical path parameters identify issues and items on the critical path and overall IMS that are at risk or have trigger dates, 30-60-90 days out. This analysis is anticipated to be required for approximately 25 projects in the base period.

Based on the analysis the Contractor shall develop an IMS strategy to conduct progress assessments, identification of problems, and a discussion of critical path activities and urgent priorities. The Contractor shall document the strategy in a Schedule Process Governance

Document detailing the mechanism to provide individual project data including milestones, dependencies, and risks to the IMS. The Contractor shall provide an initial IMS briefing of its strategy to OIT staff.

A. Schedule Process Governance Document

B. IMS Strategy Briefing

5.3 INTEGRATED MASTER SCHEDULE DASHBOARD

The Contractor shall provide, configure and maintain an IMS reporting/dashboard system with connectivity to source systems (primarily MS Project/Primavera) used by VA project and program managers. The dashboard system shall utilize approved VA software packages in accordance with VA Technical Reference Model including, but not restricted to MS SharePoint and MS Project. The dashboard shall also provide visual artifacts, pictorial views, and drill down/hyperlink capability to show schedule/milestones alignment, and dependencies for individual project activities within the portfolio and against other existing IMS.

The schedule system shall include capabilities such as resource loading and identification of project/work request/sprint/release dependencies to facilitate accuracy in reprioritization scenarios.

The system shall enable alternate categorization views that group projects/work requests/sprints/releases by:

• strategic portfolio

• department

• resources

• OIT IT portfolio structure

• OIT service structure

• OIT financial reporting structure (such as Technology Business Management)

• other structures, operational and IT management frameworks, functions, processes, and lifecycles

The Contractor shall provide dashboard maintenance by coordinating with other major initiative

IMS teams and/or Government teams for dashboard inputs to include adding projects to the dashboard and changing details within projects, and will be responsible for adjusting/updating the dashboard with limited user interface features that provide further data points and project details to manage the overall program more effectively and efficiently.

Deliverables:

A. IMS Dashboard and Updates

5.4 INTEGRATED MASTER SCHEDULE SUPPORT

The Contractor shall develop, and maintain the IMS for those projects/work requests/sprints/releases specified by the COR. The Contractor shall create and maintain the

IMS using a scheduling system that develops the IMS by extraction of schedule data from project level scheduling systems used by program and project managers, such as MS Project.

The Contractor shall perform overall general IMS review of standard VA IMS monitoring parameters to include but not limited to cost, schedule, performance, risk, and VA critical path parameters on a weekly basis to identify issues and items on the critical path and overall IMS that are at risk or have trigger dates, 30-60-90 days out.

The Contractor shall assist OIT program/project managers to identify and maintain status of dependencies across projects. The Contractor shall work closely with other major initiative IMS teams and/or other VA organizations who have OIT project dependencies related to the overall success of VA initiatives.

The Contractor shall provide continuous IMS briefings to OIT staff, including progress assessments, identification of problems, and a discussion of critical path activities and urgent priorities.

The Contractor shall update, manage, and analyze proposed schedule changes providing OIT leadership with an assessment of impacts to the IMS. The Contractor shall meet regularly with

OIT program/project managers to provide guidance and feedback on products necessary to maintain the OIT IMS including secure web access to the IMS for authorized users. The

Contractor shall advise the Government of suspense dates that need to be met by the Government and/or Government Contractors to ensure on-time execution such as, but not limited to, delivery dates for items purchased by the Government, and information that the Contractor needs from the Government to complete the requirements of this PWS. The Contractor is responsible for tracking these dates and keeping the parties informed.

5.5 TRANSITION OUT PLANNING

The Contractor shall provide a Transition Plan for 30 days of outgoing transition support for transitioning work from the current contract to a follow-on contract/order or Government entity.

This transition may be to a Government entity or to another Contractor or to the incumbent

Contractor under a new contract/order.

This Transition Plan shall include, but is not limited to:

1. Coordination with Government representatives.

2. Review, evaluation, and transition of current support services.

3. Transition of historic data in VA repository accounts.

4. Transition of system accounts.

5. Transfer of hardware and software warranties, maintenance agreements, and licenses.

6. Transfer of all necessary business and/or technical documentation.

7. Orientation phase and program to introduce Government and Contractor personnel, programs, and users to the Contractor's team, tools, methodologies, and business processes.

8. Disposition of Contractor purchased Government owned assets.

9. Transfer of Government Furnished Equipment (GFE) and Government Furnished

Information, and GFE inventory management assistance.

10. Turn-in of all Government keys, ID/access cards, and security codes.

The Contractor shall also produce a list of all assets associated with the project. This includes all software assets, specification of support environments, tools; hardware and software licenses, warranties, and maintenance agreements; documentation, and any other assets that must be maintained throughout the asset lifecycle.

A. Transition Plan

B. Asset List

5.6 OPTION PERIOD ONE

If Option Period One is exercised by VA, PWS Tasks 5.1 through 5.5 shall apply. Work is anticipated to increase of up to 35 projects for this option period. It is anticipated that on average two additional views may be needed for the IMS Dashboard.

5.7 OPTION PERIOD TWO

If Option Period Two is exercised by VA, PWS Tasks 5.1 through 5.5 shall apply. Work is anticipated to increase of up to 50 projects for this option period. It is anticipated that on average two additional views may be needed for the IMS Dashboard.

5.8 OPTIONAL TASK – TRANSITION SERVICES

The Contractor shall execute the transition of essential knowledge and work products to and from other contractors as directed by VA to ensure the continuity of operations, its related components, and work flows.

In accordance with the Government-approved Transition plan, the Contractor shall assist the

Government in implementing a complete transition from this contract to a new support provider or the Government. This shall include formal coordination with Government staff and successor staff and management. It shall also include delivery of copies of all artifacts delivered under this contract, as well as existing policies and procedures, and delivery of baseline metrics and statistics.

Successful transition is defined as 100 percent completion of all work defined in the

Government-approved Transition Plan.

Upon the completion of the transition period, the Contractor shall provide closeout certifications that include a statement that the contract is complete, all deliverables have been provided, all services are complete, and there are no outstanding contractual issues.

A. Closeout Certifications

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://www.ea.oit.va.gov/EAOIT/VA_EA/Enterprise_Technical_Architecture.asp http://www.techstrategies.oit.va.gov/enterprise_dp.asp 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/fy04/m04-04.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m0

5-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/m

05-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 / https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m05-24.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m05-24.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2011/m11-11.pdf https://www.voa.va.gov/DocumentView.aspx?DocumentID=4846 https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m05-22.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m05-22.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/egov_docs/transition-to-ipv6.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/egov_docs/transition-to-ipv6.pdf https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication500-267.pdf https://www.nist.gov/programs-projects/usgv6-program https://www.nist.gov/programs-projects/usgv6-program https://csrc.nist.gov/publications/sp

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

08-05.pdf), M08-23 mandating Domain Name System Security (NSSEC)

(https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2008/m

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