36C10B26Q0011_Sunrise DSS_Final.docx

36C10B26Q0011

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.

UEI:

EFT:

PHONE:

FAX:

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN OFFER 18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS CHECKED

SEE ADDENDUM

19.

20.

21.

22.

23.

24.

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. NOV 2021)

PREVIOUS EDITION IS NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

VA-26-00000374

Nov 13. 2025 Amanda Anderson, Contract Specialist 848-377-5329 11-20-2025 10:00 am

EDT

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

513210 $47.0 Million

N/A X

See Delivery Schedule

Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way

Eatontown NJ 07724

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

Sunrise Decision Support System (Sunrise DSS) Software Maintenance and Support

This is a sole source action.

See Section B.4 for Price Schedule.

Points of Contact:

Amanda Anderson/Amanda.anderson12@va.gov

Contract Specialist

Kathryn Pantages/Kathryn.pantages@va.gov Contracting Officer

Kathryn Pantages Contracting Officer

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 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, 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.2 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.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/Order at no cost.

B.3 CONTRACT ADMINISTRATION DATA

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

a. CONTRACTOR: Strata Decision Technology, LLC.

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

3. INVOICES: Invoices shall be submitted:

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:

Page 1 of

B.4. PRICE SCHEDULE

NOTE: All days are calendar unless otherwise noted.

Inspection/Acceptance/FOB: Destination All deliverables shall be electronically submitted to: VA Program Manager and Contracting Officer’s Representative Base Period Period of Performance shall be 12 months from date of award.

This Firm Fixed Price (FFP) Contract Line Item Number (CLIN) includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.1, inclusive of all subparagraphs.

The cost of Project Management CLIN 0001 shall be included in and allocated to CLINs 0003 through 0005.

Period of Performance: 12 months

Due 30 days after award and updated as needed

Due within 3 days following the Kickoff Meeting.

Due within 3 days following the Kickoff Meeting

Due on Friday every 2 weeks.

Due within 3 business days after award and updated as needed

This FFP CLIN includes all includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.2.

Period of Performance: 12 months

Due within 10 business days of upcoming release.

Documentation IAW PWS 5.2

Due within 10 business days of its release.

Due no later than 90 days after the Government informs the Contractor to implement the software release.

5.2

Due no later than 10 days after the Government informs the Contractor that the release has passed User Acceptance Testing

This FFP CLIN includes all includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.3, inclusive of all subparagraphs.

Period of Performance: 12 months

This FFP CLIN includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.4, inclusive of all subparagraphs.

Period of Performance: 12 months

Releases and Versions IAW PWS 5.4

Due within 10 business days of upcoming release.

Due within 10 business days of upcoming release.

This FFP CLIN includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.5.

Period of Performance: 12 months

Option Period One

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

Period of Performance shall be 12 months.

This Firm Fixed Price (FFP) Contract Line Item Number (CLIN) includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.1, inclusive of all subparagraphs.

The cost of Project Management CLIN 0001 shall be included in and allocated to CLINs 0003 through 0005.

Period of Performance: 12 months

Updated as needed

Due on Friday every 2 weeks.

Updated as needed

This FFP CLIN includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.2.

Period of Performance: 12 months

Due within 10 business days of upcoming release.

Documentation IAW PWS 5.2

Due within 10 business days of its release.

Due no later than 90 days after the Government informs the Contractor to implement the software release.

5.2

Due no later than 10 days after the Government informs the Contractor that the release has passed User Acceptance Testing

This FFP CLIN includes all includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.3, inclusive of all subparagraphs.

Period of Performance: 12 months

This FFP CLIN includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.4, inclusive of all subparagraphs.

Period of Performance: 12 months

Releases and Versions IAW PWS 5.4

Due within 10 business days of upcoming release.

Due within 10 business days of its release.

This FFP CLIN includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.5.

Period of Performance: 12 months

Option Period Two

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

Period of Performance shall be 12 months.

This Firm Fixed Price (FFP) Contract Line Item Number (CLIN) includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.1, inclusive of all subparagraphs.

The cost of Project Management CLIN 0001 shall be included in and allocated to CLINs 0003 through 0005.

Period of Performance: 12 months

Due 30 days after award and updated as needed

Due on Friday every 2 weeks.

Due within 3 business days after award and updated as needed

This FFP CLIN includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.2.

Period of Performance: 12 months

Due within 10 business days of upcoming release.

Documentation IAW PWS 5.2

Due within 10 business days of its release.

Due no later than 90 days after the Government informs the Contractor to implement the software release.

5.2

Due no later than 10 days after the Government informs the Contractor that the release has passed User Acceptance Testing

This FFP CLIN includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.3, inclusive of all subparagraphs.

Period of Performance: 12 months

This FFP CLIN includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.4, inclusive of all subparagraphs.

Period of Performance: 12 months

Releases and Versions IAW PWS 5.4

Due within 10 business days of upcoming release.

Due within 10 business days of its release.

This FFP CLIN includes all labor, materials, project management, travel and deliverables required for the successful completion of the services detailed in PWS 5.5.

Period of Performance: 12 months

B.5 PRODUCT DESCRIPTION

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology Managerial Cost Accounting Office (MCAO) Office of Finance, Veterans Health Administration

Sunrise Decision Support System (Sunrise DSS) Software Maintenance and Support Date: March 17, 2025

VA-26-00000374

PWS Version Number: 1.0

1.0 BACKGROUND

The mission of the Department of Veterans Affairs (VA) Office of Information and Technology (OI&T) and Veterans Health Administration (VHA) is to provide benefits and services to Veterans of the United States. In meeting these goals, OI&T strives to provide high quality, effective and efficient Information Technology (IT) services to those responsible for providing care to the Veterans at the point-of-care as well as throughout all the points of Veterans’ healthcare in an effective, timely and compassionate manner. VA depends on Information Management/Information Technology systems to meet mission goals. Managerial Cost Accounting Office (MCAO) is a component of the VHA Office of Finance and serves as the Program Office for all Activity-Based Cost Accounting activities at VA and provides its leadership with a complete roster of cost information services. Managerial Cost Accounting (MCA) is a shared service accountable for all cost accounting responsibilities for the VHA, Veterans Benefits Administration (VBA) and National Cemetery Administration (NCA). MCAO serves as the Business Sponsor for VA’s IT-based cost accounting system, Sunrise Decision Support System (Sunrise DSS).

MCA information services are used for process improvement in the field and at headquarters:

· VHA Senior Executives and Clinical Program Office Staff - Types and patterns of healthcare, groups of patients and patient care trends, including:

· Patterns and cost of care

· Comparative case costs

· Productivity analysis by case or department

· Financial Managers – Full product costs, including National and Veteran Integrated Service Network (VISN) overhead, and is used for such activities as budget execution and forecasting. Costs provided by type (i.e., fixed, variable, direct and indirect) and viewed at various levels of detail, including:

· Enables VERA’s equitable distribution of General-Purpose funds to each VISN.

· Production units

· Intermediate products (e.g., lab tests, medications, and clinic time)

· Inpatient and outpatient encounters (SSN specific)

· Facility and Executive Management – VISN and Veterans Affairs Medical Center (VAMC) Leadership use MCA information to formulate strategies for budget distribution, performance management and quality assurance. MCA information provides internal benchmarking to improve cost management across stations, VISNs, and program offices. And, enables comparing cost of VA care provided in-house versus care outsourced to community providers.

· Inspectors General – VISN Inspectors General regularly audit and assess for cost comparisons critical for financial oversight and identifying potential fraud, waste, and abuse.

MCAO utilizes Sunrise DSS by Strata to provide MCA information, as required by the Chief Financial Officers Act of 1990 (Public Law 101–576), Federal Financial Management Improvement Act of 1996 (104-208), and 2010 Government Performance and Results Modernization Act (PL 111-352) for VA. Sunrise DSS provides integrated analytics for resourcing, productivity reporting, product costing, budgeting, funding allocation, and knowledge-based decision support that brings together all the major components of financial and workload management. The software also allows for the reporting of patient-level utilization data for forecasting and variance reporting.

VHA, Office of Finance, MCAO has a requirement for this ongoing annual maintenance and support of Sunrise DSS which is currently used by VA as its designated MCA system.

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 2006

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. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”

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

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

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

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

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

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

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

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

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

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

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

20. VA Directive 6500, “VA Cybersecurity Program,” February 24, 2021

21. VA Handbook 6500, “Risk Management Framework for VA Information Systems VA Information Security Program,” February 24, 2021

22. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI),” March 12, 2019

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

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

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

26. VA Handbook 6500.10, “Mobile Device Security Policy,” February 15, 2018

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

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

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

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

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

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

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

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

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

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

37. NIST SP 800-53 Rev. 5, “Security and Privacy Controls for Federal Information Systems and Organizations,” September 23, 2020 (includes updates as of 12/10/2020)

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

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

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

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

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

43. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011, (NOTE: Part A of the FICAM Roadmap and Implementation Guidance, v2.0, was replaced in 2015 with an updated Architecture (https://arch.idmanagement.gov/#what-is-the-ficam-architecture)

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

45. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, “Digital Identity Guidelines,” updated March 02, 2020

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

63. “Veteran Focused Integration Process (VIP) Guide 4.0,” January 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371

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

65. “DevSecOps Product Line Management Playbook” version 2.0, May 2021, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4946

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

67. OMB Memorandum M-21-07, “Completing the Transition to Internet Protocol Version 6 (IPv6),” November 19, 2020

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

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

3.0 SCOPE OF WORK

The Contractor shall provide all periodic and recommended maintenance releases, updates, versions, and upgrade services, and VA-requested modifications for Sunrise Decision Support from Strata Decision Technology and its Database Management System (DBMS), Rocket Software’s Model 204 (M204).

Maintenance Service and Support

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The Period of Performance (PoP) shall be a 12 month base period with two (2), 12-month option periods. The overall period of performance shall not exceed 36 months.

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 eleven (11) Federal holidays set by law (USC Title 5 Section 6103) that VA follows:

Under current definitions, five 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 CONTRACT TYPE

The effort shall be proposed on a Firm Fixed Price (FFP) basis, including optional tasks with travel inclusive.

4.3 PLACE OF PERFORMANCE

Tasks under this PWS shall be performed at Contractor facilities. The Contractor shall identify the Contractor’s place of performance in their proposal submission. Work may be performed at remote locations with prior concurrence from the Contracting Officer’s Representative (COR).

4.4 TRAVEL

The Government anticipates travel under this effort to perform the tasks associated with the effort, as well as to attend program-related meetings or conferences 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 one (1) per period. The Contractor shall ensure that the right mix and quantity of qualified personnel attend as necessary (i.e., Strata Decision Technology programmer(s), managerial staff, etc.) for one three-day programmer meeting held at the VA Austin Information Technology Center, Austin, Texas to conduct annual face-to-face planning to support changing VA business needs and/or to improve usability of the software:

Base Period:

Option Period One:

Option Period Two:

Travel shall be In Accordance With (IAW) the Federal Travel Regulations and requires advanced concurrence by the COR. Contractor travel within the local commuting area will not be reimbursed.

5.0 SPECIFIC TASKS AND DELIVERABLES

5.1 PROJECT MANAGEMENT

5.1.1 CONTRACTOR PROJECT MANAGEMENT PLAN (CPMP)

The Contractor shall deliver a 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 IAW 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

5.1.2.1 KICK OFF MEETING

Contracting Officer (CO), as the Post-Award Conference Chairperson, the VA Program Manager (PM), as the Co-Chairperson, the Contract Specialist (CS), and the COR. The Contractor shall provide a draft agenda to the CO and VA PM at least five calendar days prior to the meeting. Upon Government approval of a final agenda, the Contractor shall distribute to all meeting attendees. During the kickoff-meeting, the Contractor shall present, for review and approval by the Government, the details of the intended approach, work plan, and project schedule for each effort via a Microsoft Office PowerPoint presentation. At the conclusion of the meeting, the Contractor shall update the presentation with a final slide entitled “Summary Report” which shall include notes on any major issues, agreements, or disagreements discussed during the kickoff meeting. and the following statement “As the Post-Award Conference Chairperson, I have reviewed the entirety of this presentation and assert that it is an accurate representation and summary of the discussions held during the Technical Kickoff Meeting for the Decision Support System (DSS) Software Maintenance and Support.”

The Contractor shall submit the final updated presentation to the CO for review and signature within three calendar days after the meeting. The Contractor shall obtain concurrence from the Government on the content of the meeting minutes prior to distribution of the document and prepare and distribute the meeting minutes of the kickoff meeting to all attendees within three calendar days after the meeting.

Deliverables:

5.1.2.2 BI-WEEKLY PROGRESS REPORT

The Contractor shall provide a Progress Report every two weeks (i.e., Bi-Weekly) that shall identify all software work items (e.g., Program Temporary Fixes (PTF), software patches, upgrades, testing results, technical documentation, etc.) tracking information, and information relative to Government-receipt of the software/code. In addition, the Progress Report shall identify any problems and provide a description of how the problems were resolved/addressed. If problems have not been completely resolved, the Contractor shall provide an explanation and status of resolution. Progress Reports shall be submitted in Microsoft Word/PDF format and shall clearly identify each software release/patch.

Deliverables:

A. Bi-Weekly Progress Report

5.2 SOFTWARE MAINTENANCE

The Contractor shall maintain the system, including software applications and VA specific code (i.e., Software Enhancements), in a production-ready state so that MCA data can be processed in an uninterrupted manner. The Contractor shall provide appropriate software modifications when the software malfunctions. This shall also apply to all code malfunctions, which reside in the specific code generated for VA by the Contractor. The Contractor shall make appropriate expertise available to attend conference calls and face-to-face meetings in order to maintain the DSS operational application during the term of this contract. Any alterations shall not void the warranty VA currently has with Strata Decision Technology software.

The Contractor shall inform VA regarding the timetable of upcoming Sunrise Decision Support Maintenance releases, updates, versions, and upgrades. The Contractor shall also provide written notice within 10 business days of Strata Decision Technology’s upcoming releases and the timeframe within which these will be made available to VA. These maintenance releases, updates, versions, and upgrades shall be provided along with Sunrise Decision Support Release and Update Technical Documentation that describes the release, update, version or upgrade, and updates, as well as instructions to install the release, update, version, or upgrade on the mainframe at the Austin Information Technology Center (AITC). The Government will decide, in consultation with the Contractor, if/when an update to code is to be implemented. When directed to implement updated code, the Contractor shall test any and all changes to existing code in a VA supplied dedicated test region(s) prior to releasing the code to the staff at the MCAO for User Acceptance Testing (UAT). The Contractor shall provide its successful Software Quality Assurance Test Results to the Government as part of the package for the hand-over to Government’s UAT. After the Government provides its documented passing of UAT, the Contractor shall provide Certification for Release to the Government for its scheduled deployment to production. The Contractor shall provide technical advice to the testing staff at MCAO and the AITC in establishing test region(s), test procedures, and in testing the software in both the test region (Alpha Testing) and in a subset of medical centers’ production regions (Beta Testing) before general release. Software diagnostic and repair services and application and database support at the AITC shall be provided during the testing. Software Maintenance Releases shall be available at a time mutually agreed to by the COR and the Contractor.

Deliverables:

a. Sunrise Decision Support Software Maintenance Releases

b. Release and Update Technical Documentation

c. Test Results

d. Certification for Release

5.2.1 RIGHTS IN COMPUTER SOFTWARE

The Contractor is required to deliver technical data, configurations, documentation, or other information, including source code data, during contract performance. The Government shall receive Unlimited Rights in that intellectual property which is first produced and delivered in the performance of this contract IAW Federal Acquisition Regulation (FAR) 52.227-14, Rights In Data-General (DEC 2007). This includes all rights to source code data and any and all documentation created in support thereof.

License rights in any Commercial Computer Software shall be governed by FAR 52.227-19, Commercial Computer Software License (DEC 2007). NOTE: All technical data, configurations, documentation, or other information, including source code data previously delivered pursuant to other VA contracts and/or order shall continue to be governed by the applicable data rights clauses in those contracts or orders.

5.3 SOFTWARE ENHANCEMENTS

The Contractor shall maintain the existing software functionality and support efficiency and effectiveness enhancements to VA’s DSS operating system, existing Strata Decision Technology software code, and VA custom code to accommodate changing requirements, management initiatives, and reporting needs within and across software regions. The Contractor shall coordinate and obtain concurrence from the COR prior to commencing any software code alterations in this section.

1. Incorporate into the processing cycle new source extracts (inputs to the system) or national data extracts (outputs from the systems) or modifications to both types of existing extracts when requested.

1. Repair global errors when the data being processed with current code results in inaccurate patient utilization or encounter data due to the condition of the source data.

1. Support the annual fiscal year conversion.

1. Support ongoing efficiency and effectiveness endeavors that modify either the operating system or Eclipsys software code or VA custom code.

5.4 SUPPORT OF DBMS AND OPERATING SYSTEM

The Contractor shall support the software operating system and DBMS on the AITC mainframe by providing troubleshooting services including support for AITC’s periodic upgrades to the IBM Operating System; providing Rocket Software’s Model 204 DBMS software maintenance releases with installation instructions, technical documentation, and other documentation provided by Rocket Software; providing new Rocket Model 204 DBMS Versions with installation instructions, technical documentation, and other documentation provided by Rocket Software; coordinating with Rocket Software to provide timely releases of Model 204 fixes to VA as such fixes are made available by Rocket Software. The Government will decide, in consultation with the Contractor, if/when an update to the code is to be implemented.

The Contractor shall inform VA when support for a particular release will end. The Contractor shall also inform VA regarding the timetable of upcoming new Model 204 Releases to facilitate VA planning and testing of the release. The Contractor shall also provide written notice, within 10 business days of Rocket’s notification regarding upcoming major Releases, Early Warnings, and service packs, of the timeframe within which these will be made available to VA. The Contractor shall support VA testing and implementation of the system changes on Model 204.

Deliverables:

A. Rocket Model 204 Software Releases and Versions B. Rocket Model 204 Software Release Installation Instructions and Technical Documentation

5.5 HELP DESK SUPPORT

The Contractor shall, via telephone and email, troubleshoot and resolve issues presented by the VA MCA Help Desk. Help Desk issues are referred to the Contractor on an almost daily basis. The Contractor shall also respond to any issue deemed urgent by the Help Desk within one hour during normal business hours from 8:00 a.m. to 5:00 p.m. Eastern Time.

6.0 NOTICE OF THE FEDERAL ACCESSIBILITY 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 OIT 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 OIT. 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…