36C10B23Q0025_2.docx
DOCX document 214 KB Posted
- Attached to
- R710--eCAMS Support Software (VA-23-00011367) Federal contract opportunity
- Solicitation number
- 36C10B23Q0025
About this file
This is a combined synopsis and solicitation notice for operations and maintenance support services and change request support services for an electronic claims adjudication system used by the Department of Veterans Affairs Financial Services Center. The solicitation is for a noncompetitive contract to be awarded to Client Network Services, LLC as the incumbent contractor. The base period of performance is one year with two optional one-year periods. Operations and maintenance support will be firm-fixed price while change request support will be time and materials with a not-to-exceed amount of $5 million per year. The contractor will provide help desk support, software updates, defect resolution and other services to support the claims processing system. Change requests will include implementing new business rules, system enhancements and integrating with other systems.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| JA 2.23.24 final redacted.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
36C10B23Q0025
| SUBJECT* |
| eCAMS Support Software (VA-23-00011367) |
GENERAL INFORMATION
| CONTRACTING OFFICE’S ZIP CODE* |
| 07724 |
| SOLICITATION NUMBER* |
| 36C10B23Q0025 |
| RESPONSE DATE/TIME/ZONE |
| 03-15-2023 17:00 EASTERN TIME, NEW YORK, USA |
| ARCHIVE |
| 30 DAYS AFTER THE RESPONSE DATE |
| RECOVERY ACT FUNDS |
| N |
SET-ASIDE
| PRODUCT SERVICE CODE* |
| R710 |
| NAICS CODE* |
| 541512 |
| CONTRACTING OFFICE ADDRESS |
| Department of Veterans Affairs |
Technology Acquisition Center
23 Christopher Way Eatontown NJ 07724
POINT OF CONTACT*
Contract Specialist Marleine Raisin Marleine.Raisin@va.gov 848-377-5093
PLACE OF PERFORMANCE
ADDRESS
POSTAL CODE
COUNTRY
ADDITIONAL INFORMATION
AGENCY’S URL
URL DESCRIPTION
AGENCY CONTACT’S EMAIL ADDRESS
EMAIL DESCRIPTION
Combined Synopsis/Solicitation Notice Combined Synopsis/Solicitation Notice
DESCRIPTION
| *= Required Field |
| Combined Synopsis/Solicitation Notice |
Combined Synopsis/Solicitation Notice
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-23-00011367
36C10B23Q0025 /2023 M arleine Raisin 848-377-5093 03/ /20
EDT
36C10B Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724 541512 N/A X See Delivery Schedule Eatontown NJ 07724 36C10B Department of Veterans Affairs Technology Acquisition Center
36C10A Department of Veterans Affairs Technology Acquisition Center Financial Services Center PO Box 149971 Austin TX 78714-8971 See CONTINUATION Page Title:
eCAMS Support Software Period of Performance: 12-month from date of award with two
12-month option periods This RFQ will result in a Firm-Fixed Priced Delivery order With a Time-in-Material for Change Order Request Contract Specialist: Marleine Raisin, Marleine.Raisin@va.gov Contracting Officer: Matthew Newell, Matthew.Newell@va.gov See CONTINUATION Page X X M atthew Newell Page 1 of Table of Contents
| SECTION A | 4 | |
| A.1 SF 1449 SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES | 4 | |
| B.1 SUBCONTRACTING PLAN--MONITORING AND COMPLIANCE | 7 | |
| B.2 INTELECTUAL PROPERTY RIGHTS | 7 | |
| 2.0 | APPLICABLE DOCUMENTS | 30 |
| 3.0 | SCOPE OF WORK | 34 |
| 4.0 | PERFORMANCE DETAILS | 34 |
| 4.1 | PERFORMANCE PERIOD | 34 |
| 4.2 | PLACE OF PERFORMANCE | 35 |
| 4.3 | TRAVEL | 35 |
| 5.0 | SPECIFIC TASKS AND DELIVERABLES | 35 |
| 5.1 | OPERATIONS AND MAINTENANCE (O&M) | 35 |
| 5.1.1 | SOFTWARE TECHNICAL SUPPORT | 35 |
| 5.1.2 | PATCHES FOR BUGS AND ISSUES | 36 |
| 5.1.3 | SOFTWARE UPDATES AND QUALITY IMPROVEMENT | 37 |
| 5.2 | CHANGE REQUESTS (CR) BASE AND ALL OPTION YEARS AS WELL AS OPTIONAL TASKS | 38 |
| 5.3 | ADDITIONAL TASKS | 39 |
| 5.3.1 | CODE RELEASES | 39 |
| 5.3.2 | SYSTEM FEATURES AND CAPABILITIES | 39 |
| 5.3.2.1 SOFTWARE LICENSE | 39 | |
| 5.3.2.2 MEMBER MANAGEMENT AND ELIGIBILITY | 39 | |
| 5.3.2.3 BENEFIT ADMINISTRATION | 40 | |
| 5.3.2.4 PROVIDER MANAGEMENT | 40 | |
| 5.3.2.5 FEE SCHEDULE AND CONTRACT MANAGEMENT | 40 | |
| 5.3.2.6 AUTHORIZATIONS AND REFERRALS | 41 | |
| 5.3.2.7 DATA INPUT, CLAIMS INTAKE, AND DATA ACCESSIBILITY | 42 | |
| 5.3.2.8 WORK ASSIGNMENTS AND WORKFLOW | 42 | |
| 5.3.2.9 CLAIMS ADJUDICATION | 42 | |
| 5.3.2.10 CUSTOMER MANAGEMENT | 43 | |
| 5.3.2.11 FINANCIALS AND ACCOUNTS PAYABLE | 43 | |
| 5.3.2.12 CORRESPONDENCE | 44 | |
| 5.3.2.13 DATA STORAGE AND DATA MANAGEMENT | 44 | |
| 5.3.2.14 REPORTING | 45 | |
| 5.3.2.15 SECURITY AND AUDIT TRAILS | 45 | |
| 5.3.2.16 | DATA EXCHANGE SERVICES, ELECTRONIC DATA INTERCHANGE, AND CAQH CORE | 46 |
| 5.3.2.17 CAPACITY AND SCALABILITY | 47 | |
| 5.3.2.18 FLEXIBILITY | 47 | |
| 5.3.2.19 LEVEL OF AUTOMATION | 48 | |
| 5.3.2.20 SYSTEM INTEGRATION AND INTEROPERABILITY | 48 | |
| 5.3.2.21 HIGH-AVAILABILITY | 48 | |
| 5.3.2.24 TECHNICAL REFERENCE MODEL (TRM) | 48 | |
| 5.3.2.23 TECHNOLOGY STACK | 48 | |
| 5.3.2.24 HISTORICAL DATA PURGING AND RE-LOADING | 49 | |
| 5.3.2.25 SYSTEM CONFIGURATION RETENTION AND MIGRATION | 49 | |
| 5.3.2.26 SYSTEM STATUS | 49 | |
| 5.3.2.27 WEB-BASED PROVIDER PORTAL | 49 | |
| 5.3.2.28 WEB-BASED AUTHORIZATIONS AND REFERRALS PORTAL | 49 | |
| 5.3.2.29 CLOUD ENVIROMENT | 50 | |
| 5.3.3 | SYSTEM CONFIGURATION AND IMPLEMENTATION | 50 |
| 5.3.4 | SYSTEM DOCUMENTATION | 50 |
| 5.3.5 | TRAINING AND USER DOCUMENTATION | 50 |
| 6.0 | GENERAL REQUIREMENTS | 51 |
| 6.1 | ENTERPRISE AND IT FRAMEWORK | 51 |
| 6.1.1 | VA TECHNICAL REFERENCE MODEL | 51 |
| 6.1.2 | FEDERAL IDENTITY, CREDENTIAL, AND ACCESS MANAGEMENT (FICAM) | 51 |
| 6.1.3 | INTERNET PROTOCOL VERSION 6 (IPV6) | 52 |
| 6.1.4 | TRUSTED INTERNET CONNECTION (TIC) | 53 |
| 6.1.5 | STANDARD COMPUTER CONFIGURATION | 53 |
| 6.1.6 | VETERAN FOCUSED INTEGRATION PROCESS (VIP) AND PRODUCT LINE MANGEMENT (PLM) | 53 |
| 6.1.7 | PROCESS ASSET LIBRARY (PAL) | 54 |
| 6.1.8 | AUTHORITATIVE DATA SOURCES | 54 |
| 6.2 | SECURITY AND PRIVACY REQUIREMENTS | 55 |
| 6.2.1 | POSITION/TASK RISK DESIGNATION LEVEL(S) | 55 |
| 6.2.2 | CONTRACTOR PERSONNEL SECURITY REQUIREMENTS | 56 |
| 6.3 | METHOD AND DISTRIBUTION OF DELIVERABLES | 58 |
| 6.4 | PERFORMANCE METRICS | 58 |
| 6.5 | FACILITY/RESOURCE PROVISIONS | 60 |
| 6.6 | GOVERNMENT FURNISHED PROPERTY | 63 |
| 6.7 | SHIPMENT OF HARDWARE OR EQUIPMENT | 64 |
| ADDENDUM A – ADDITIONAL VA REQUIREMENTS, CONSOLIDATED | 65 | |
| ADDENDUM B – VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY LANGUAGE | 71 | |
| 7.0 | Points of Contact | 81 |
SECTION B - CONTINUATION OF SF 1449 BLOCKS
B.1 SUBCONTRACTING PLAN--MONITORING AND COMPLIANCE
This solicitation includes FAR 52.219-9 – Alternate II, Small Business Subcontracting Plan, and VAAR 852.219-70, VA Small Business Subcontracting Plan Minimum Requirement. Accordingly, any contract resulting from this solicitation will include these clauses. The contractor is advised in performing contract administration functions, the Contracting Officer may use the services of a support contractor(s) to assist in assessing the contractor's compliance with the plan, including reviewing the contractor's accomplishments in achieving the subcontracting goals in the plan. To that end, the support contractor(s) may require access to the contractor's business records or other proprietary data to review such business records regarding the contractor's compliance with this requirement. All support contractors conducting this review on behalf of VA will be required to sign an “Information Protection and Non-Disclosure and Disclosure of Conflicts of Interest Agreement” to ensure the contractor's business records or other proprietary data reviewed or obtained in the course of assisting the Contracting Officer in assessing the contractor for compliance are protected to ensure information or data is not improperly disclosed or other impropriety occurs. Furthermore, if VA determines any services the support contractor(s) will perform in assessing compliance are advisory and assistance services as defined in FAR 2.101, Definitions, the support contractor(s) must also enter into an agreement with the contractor to protect proprietary information as required by FAR 9.505-4, obtaining access to proprietary information, paragraph (b). The contractor is required to cooperate fully and make available any records as may be required to enable the Contracting Officer to assess the contractor compliance with the subcontracting plan.
B.2 INTELECTUAL PROPERTY RIGHTS
It is agreed that:
1. VA Data is defined as the Healthcare Claims Adjudication Software schema (VA business rules, templates, and file formats that are provided by VA), and any Veteran Personally Identifiable Information (PII) and VA Sensitive Personal Information (SPI). VA Data is not considered Data as that term is defined by Federal Acquisition Regulation (FAR) 52.227-14, Rights in Data – General (a) (May 2014) of the contract.
2. VA Data shall not be modified, updated, revised or changed in any manner by the Contractor during performance of the contract. VA Data initially provided to the contractor to populate the VA Healthcare Claims Adjudication software shall remain the exclusive information and property of the VA and shall be returned to the Contracting Officer at the conclusion of the contract in order for the VA Data to be used, stored, and maintained by the Government. The parties further agree that because VA Data contains both PII and SPI, the disclosure thereof would violate the right of privacy or publicity of Veterans, their families, and the VA. Accordingly, the Contractor relinquishes its reservation of rights set forth in FAR 52.227-14 (b)
(2) for all VA Data.
3. Any Data as that term is defined by FAR 52.227-14 Rights in Data – General (May 2014) first produced and delivered by the Contractor during performance of the contract shall be delivered with Unlimited Rights in accordance with FAR 52.227- 14, Rights in Data – General (May 2014). Data includes all Technical Data, Computer Software, Computer Software Documentation, source code, all documentation created in support thereof, and any and all data elements first produced in the performance of the contract and generated included and contained in the Contractor’s data reports, Healthcare Claims Adjudication software, and any other data file(s) supporting this contract.
4. License rights in any Commercial Computer Software shall be governed by FAR 52.227-19, Commercial Computer Software License (DEC 2007).
5. The CO is the sole authorized official to release verbally or in writing, any VA Data, Data or any other written or printed materials pertaining to the Healthcare Claims Adjudication Software maintained and provided by Contractor pursuant to the requirements of the contract. The contractor will not release any such information
B.3 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 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) 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.4 SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT SOFTWARE LICENSE, MAINTENANCE AND TECHNICAL SUPPORT:
1. Definitions.
1. Licensee. The term “licensee” shall mean the U.S. Department of Veterans Affairs (“VA”) and is synonymous with “Government.”
1. 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.
1. Software. The term “software” shall mean the licensed computer software product(s) cited in the Schedule of Supplies/Services.
1. 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.
1. 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.
1. 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.
1. 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).
1. Software License
1. The Government may use the software in a networked environment.
1. Any dispute regarding the license grant or usage limitations shall be resolved in accordance with the Disputes Clause incorporated in FAR 52.212-4(d).
1. All limitations of software usage are expressly stated in the Schedule of Supplies/Services and the Performance Work Statement/Product Description.
1. Software Maintenance and Technical Support
| (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. |
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.
B.5 CONTRACT ADMINISTRATION DATA
1. Contract Administration: All contract administration matters will be handled by the following individuals:
a. CONTRACTOR: CLIENT NETWORK SERVICES, INC. (CNSI) 2277 Research Blvd.
Rockville, Maryland 20850-3224, United States
UEI: LD1DU6SKNP83
CAGE/NCAGE: 03VY8
b. GOVERNMENT: Contracting Officer Department of Veterans Affairs 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 |
| [] |
| 52.232-36, Payment by Third Party |
3. INVOICES: Invoices shall be submitted in arrears:
| a. Quarterly | [] |
| b. Semi-Annually | [] |
| c. Other | [X] Upon acceptance of Deliverables IAW B.4 Price Schedule] |
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.
36C10B23Q0025
Page 1 of Page 1 of Page 1 of Page 1 of
B.6 PRICE SCHEDULE
Inspection: Destination Acceptance: Destination Free on Board (FOB): Destination
Base period:
The period of performance for this effort shall be March 19, 2023, to March 18, 2024
| Contract Line-Item Number (CLIN) |
| Description |
| QTY |
| Unit |
| Unit Price |
| Total Price |
| 0001 |
| Operations and Maintenance (O&M) support in accordance with PWS Sections 5.1 and 5.3 inclusive of all sub-paragraphs. |
Contract Type: Firm-Fixed Price
Period of Performance: 12-months from award date
Purchase Order Number:
All cost of SLIN’s shall be included in this CLIN.
| 12 |
| MO |
| $ |
| $ |
| 0001AA |
| Software Technical Support Plan Technical Services Report and Technical Services Log in accordance with the requirements specified in the Performance Work Statement (PWS) paragraph 5.1.1 delivery shall be electronically to the VA-FSC COR no later than the fifth calendar day of every month throughout the POP. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 0001.
| 12 |
| EA |
| NSP |
| NSP |
| 0001AB |
| Migration/Upgrade Plan in accordance with the requirements specified in the PWS paragraph 5.1.3 delivery shall be within 30 days of contract award and updated as changes occur. |
All costs for successful completion of of this SLIN shall be included and allocated in CLIN 0001.
| 1 |
| LO |
| NSP |
| NSP |
| 0001AC |
| Release Notes in accordance with the requirements specified in the PWS paragraph 5.1.3 release notes shall include but not limited to Contractor’s release schedule to licensed customers, their software updates, including all related documentation for these software updates and release notes to all changes to the VA-FSC Program Manager or COR. Release notes are due 2 days prior to any release. |
All costs for successful completion of of this SLIN shall be included and allocated in CLIN 0001.
| 1 |
| LO |
| NSP |
| NSP |
| 0001AD |
| GFE status report in accordance with the requirements specified in the PWS paragraph 6.6 due two weeks after award or after any change in GFE status. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 0001.
| 1 |
| LO |
| NSP |
| NSP |
| 0001AE |
| Identification of Testing Methods and Tools used to Verify Compliance in accordance with the requirements specified in the PWS paragraph 5.3.2.18 due at the time of each code release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 0001.
| 1 |
| LO |
| NSP |
| NSP |
| 0001AF |
| Proof of Security Compliance in accordance with the requirements specified in the PWS paragraph 5.3.2.18 due at the time of each code release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 0001.
| 1 |
| LO |
| NSP |
| NSP |
| 0001AG |
| System Documentation and Software Configuration Users Guide in accordance with the requirements specified in the PWS paragraph 5.3.4 is required seven days after an upgrade or update. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 0001.
| 1 |
| LO |
| NSP |
| NSP |
| 0001AH |
| System Configuration and Implementation Final Configured Software shall be conducted throughout the life of the contract in accordance with the requirements specified in the PWS paragraph 5.3.3 |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 0001.
| 1 |
| LO |
| NSP |
| NSP |
| 0001AI |
| Software Training Manual and User Guide in accordance with the requirements specified in the PWS paragraph 5.3.5 due 14 days prior to scheduled deployment of configured software |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 0001.
| 1 |
| LO |
| NSP |
| NSP |
| 0001AJ |
| Contractor Staff Roster in accordance with the requirements specified in the PWS paragraph 6.2.2 due 3 days after award and updated as required. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 0001.
| 1 |
| LO |
| NSP |
| NSP |
| 0002 |
| Implementing Change Request Support defect resolution, technical support, installing software patches/upgrades, business rule changes, code changes, integration with new interfaces, and implementing new healthcare program offerings, in accordance with PWS Section 5.2. |
Contract Type: Time and Material
Prior to the contractor initiating any work under this CLIN, the contractor shall submit a request to the VA PM and COR detailing the estimated budget and schedule for the completion of work inclusive of major milestones. The contractor shall be responsible for adhering to all requirements of the PWS section in which work is performed and all deliverables of the associated section. No work shall be funded unless projected to provide a finished useable product.
This Time and Materials CLIN is IAW FAR 52.232-7 for invoicing or billing purposes.
Purchase Order Number:
| 1 |
| LO |
| $NTE |
$5,000,000
$NTE
$5,000,000
| 0002AA |
| Change Requests (CR) Proposed Response in accordance with the requirements specified in the PWS paragraph 5.2 developed and approved change request shall be implemented in accordance with paragraph 5.2 and its sub-paragraphs due one week after receipt of change request. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 0002.
| 1 |
| LO |
| NSP |
| NSP |
| 0002AB |
| Code Release (if needed) in accordance with the requirements specified in the PWS paragraph 5.2 shall be conducted monthly within the first week of every month throughout the POP. Additional task specified in the PWS sub-paragraph 5.3.1 due at the end of each release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 0002.
| 12 |
| EA |
| NSP |
| NSP |
| 0002AC |
| Implementation Documentation in accordance with the requirements specified in the PWS paragraph 5.2 due at the end of each release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 0002.
| 1 |
| LO |
| NSP |
| NSP |
| Base Period Total: |
| $ |
Option Period 1 The period of performance for this effort shall be March 19, 2024, to March 18, 2025. If this option is exercised, it shall be exercised via unilateral modification in accordance with FAR 52.217-9, Option to Extend the Term of the Contract (MAR 2000).
| Contract Line-Item Number (CLIN) |
| Description |
| QTY |
| Unit |
| Unit Price |
| Total Price |
| 1001 |
| Operations and Maintenance (O&M) support in accordance with PWS Sections 5.1 and 5.3 inclusive of all sub-paragraphs. |
Contract Type: Firm-Fixed Price
Period of Performance: 12-months from award date
Purchase Order Number:
| 12 |
| MO |
| $ |
| $ |
| 1001AA |
| Software Technical Support Plan Technical Services Report and Technical Services Log in accordance with the requirements specified in the Performance Work Statement (PWS) paragraph 5.1.1 delivery shall be electronically to the VA-FSC COR no later than the fifth calendar day of every month throughout the POP. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 1001.
| 12 |
| EA |
| NSP |
| NSP |
| 1001AB |
| Migration/Upgrade Plan in accordance with the requirements specified in the PWS paragraph 5.1.3 delivery shall be within 30 days of contract award and updated as changes occur. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 1001.
| 1 |
| LO |
| NSP |
| NSP |
| 1001AC |
| Release Notes in accordance with the requirements specified in the PWS paragraph 5.1.3 release notes shall include but not limited to Contractor’s release schedule to licensed customers, their software updates, including all related documentation for these software updates and release notes to all changes to the VA-FSC Program Manager or COR. Release notes are due 2 days prior to any release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 1001.
| 1 |
| LO |
| NSP |
| NSP |
| 1001AE |
| Identification of Testing Methods and Tools used to Verify Compliance in accordance with the requirements specified in the PWS paragraph 5.3.2.18 due at the time of each code release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 1001.
| 1 |
| LO |
| NSP |
| NSP |
| 1001AF |
| Proof of Security Compliance in accordance with the requirements specified in the PWS paragraph 5.3.2.18 due at the time of each code release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 1001.
| 1 |
| LO |
| NSP |
| NSP |
| 1001AG |
| System Documentation and Software Configuration Users Guide in accordance with the requirements specified in the PWS paragraph 5.3.4 is required seven days after an upgrade or update. |
| 1 |
| LO |
| NSP |
| NSP |
| 1001AH |
| System Configuration and Implementation Final Configured Software shall be conducted throughout the life of the contract in accordance with the requirements specified in the PWS paragraph 5.3.3 |
| 1 |
| LO |
| NSP |
| NSP |
| 1001AI |
| Software Training Manual and User Guide in accordance with the requirements specified in the PWS paragraph 5.3.5 due 14 days prior to scheduled deployment of configured software |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 1001.
| 1 |
| LO |
| NSP |
| NSP |
| 1001AJ |
| Contractor Staff Roster in accordance with the requirements specified in the PWS paragraph 6.2.2 due 3 days after award and updated as required. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 1001.
| 1 |
| LO |
| NSP |
| NSP |
| 1002 |
| Implementing Change Request Support defect resolution, technical support, installing software patches/upgrades, business rule changes, code changes, integration with new interfaces, and implementing new healthcare program offerings, in accordance with PWS Section 5.2 |
Contract Type: Time and Material
Prior to the contractor initiating any work under this CLIN, the contractor shall submit a request to the VA PM and COR detailing the estimated budget and schedule for the completion of work inclusive of major milestones. The contractor shall be responsible for adhering to all requirements of the PWS section in which work is performed and all deliverables of the associated section. No work shall be funded unless projected to provide a finished useable product.
This Time and Materials CLIN is IAW FAR 52.232-7 for invoicing or billing purposes.
Purchase Order Number:
| 1 |
| LO |
| $NTE |
$5,000,000
$NTE
$5,000,000
| 1002AA |
| Change Requests (CR) Proposed Response in accordance with the requirements specified in the PWS paragraph 5.2 developed and approved change request shall be implemented in accordance with paragraph 5.3 and its sub-paragraphs due one week after receipt of change request. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 1002.
| 1 |
| LO |
| NSP |
| NSP |
| 1002AB |
| Code Release (if needed) in accordance with the requirements specified in the PWS paragraph 5.2 shall be conducted monthly within the first week of every month throughout the POP. Additional task specified in the PWS sub-paragraph 5.3.1 due at the end of each release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 1002.
| 12 |
| EA |
| NSP |
| NSP |
| 1002AC |
| Implementation Documentation in accordance with the requirements specified in the PWS paragraph 5.2 due at the end of each release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 1002.
| 1 |
| LO |
| NSP |
| NSP |
| Option Period One Total: |
| $ |
Option Period 2:
The period of performance for this effort shall be March 19, 2025, to March 18, 2026 from the expiration of Option Period One. If this option is exercised, it shall be exercised via unilateral modification in accordance with FAR 52.217-9, Option to Extend the Term of the Contract (MAR 2000).
| Contract Line-Item Number (CLIN) |
| Description |
| QTY |
| Unit |
| Unit Cost |
| Total Price |
| 2001 |
| Operations and Maintenance (O&M) support in accordance with PWS Sections 5.1 and 5.3 inclusive of all sub-paragraphs. |
Contract Type: Firm-Fixed Price
Period of Performance: 12-months from award date
Purchase Order Number:
| 12 |
| MO |
| $ |
| $ |
| 2001AA |
| Software Technical Support Plan Technical Services Report and Technical Services Log in accordance with the requirements specified in the Performance Work Statement (PWS) paragraph 5.1.1 delivery shall be electronically to the VA-FSC COR no later than the fifth calendar day of every month throughout the POP. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 2001.
| 12 |
| EA |
| NSP |
| NSP |
| 2001AB |
| Migration/Upgrade Plan in accordance with the requirements specified in the PWS paragraph 5.1.3 delivery shall be within 30 days of contract award and updated as changes occur. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 2001.
| 1 |
| LO |
| NSP |
| NSP |
| 2001AC |
| Release Notes in accordance with the requirements specified in the PWS paragraph 5.1.3 release notes shall include but not limited to Contractor’s release schedule to licensed customers, their software updates, including all related documentation for these software updates and release notes to all changes to the VA-FSC Program Manager or COR. Release notes are due 2 days prior to any release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 2001.
| 1 |
| LO |
| NSP |
| NSP |
| 2001AE |
| Identification of Testing Methods and Tools used to Verify Compliance in accordance with the requirements specified in the PWS paragraph 5.3.2.18 due at the time of each code release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 2001.
| 1 |
| LO |
| NSP |
| NSP |
| 2001AF |
| Proof of Security Compliance in accordance with the requirements specified in the PWS paragraph 5.3.2.18 due at the time of each code release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 2001.
| 1 |
| LO |
| NSP |
| NSP |
| 2001AG |
| System Documentation and Software Configuration Users Guide in accordance with the requirements specified in the PWS paragraph 5.3.4 is required seven days after an upgrade or update. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 2001.
| 1 |
| LO |
| NSP |
| NSP |
| 2001AH |
| System Configuration and Implementation Final Configured Software shall be conducted throughout the life of the contract in accordance with the requirements specified in the PWS paragraph 5.3.3 |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 2001.
| 1 |
| LO |
| NSP |
| NSP |
| 2001AI |
| Software Training Manual and User Guide in accordance with the requirements specified in the PWS paragraph 5.3.5 due 14 days prior to scheduled deployment of configured software |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 2001.
| 1 |
| LO |
| NSP |
| NSP |
| 2001AJ |
| Contractor Staff Roster in accordance with the requirements specified in the PWS paragraph 6.2.2 due 3 days after award and updated as required. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 2001.
| 1 |
| LO |
| NSP |
| NSP |
| 2002 |
| Implementing Change Request Support defect resolution, technical support, installing software patches/upgrades, business rule changes, code changes, integration with new interfaces, and implementing new healthcare program offerings, in accordance with PWS Section 5.2 |
Contract Type: Time and Material
Prior to the contractor initiating any work under this CLIN, the contractor shall submit a request to the VA PM and COR detailing the estimated budget and schedule for the completion of work inclusive of major milestones. The contractor shall be responsible for adhering to all requirements of the PWS section in which work is performed and all deliverables of the associated section. No work shall be funded unless projected to provide a finished useable product.
This Time and Materials CLIN is IAW FAR 52.232-7 for invoicing or billing purposes.
Purchase Order Number:
| 1 |
| LO |
| $NTE |
$5,000,000
$NTE
$5,000,000
| 2002AA |
| Change Requests (CR) Proposed Response in accordance with the requirements specified in the PWS paragraph 5.2 developed and approved change request shall be implemented in accordance with paragraph 5.3 and its sub-paragraphs due one week after receipt of change request. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 2002.
| 1 |
| LO |
| NSP |
| NSP |
| 2002AB |
| Code Release (if needed) in accordance with the requirements specified in the PWS paragraph 5.2 shall be conducted monthly within the first week of every month throughout the POP. Additional task specified in the PWS sub-paragraph 5.3.1 due at the end of each release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 2002.
| 12 |
| EA |
| NSP |
| NSP |
| 2002AC |
| Implementation Documentation in accordance with the requirements specified in the PWS paragraph 5.2 due at the end of each release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 2002.
| 1 |
| LO |
| NSP |
| NSP |
| Option Period Two Total: |
| $ |
Optional Task This optional task may be exercised at any time and from time to time up to the total NTE Price in accordance with FAR 52.217-7, Option for Increase Quantity---Separately Priced Line Item Mar 1989. If exercised, no single period of performance in any exercise shall exceed 12-months.
| Contract Line-Item Number (CLIN) |
| Description |
| QTY |
| Unit |
| Unit Cost |
| Total Price |
| 3001 |
| Additional Change Request Support; defect resolution, technical support, installing software patches/upgrades, business rule changes, code changes, integration with new interfaces, and implementing new healthcare program offerings, in accordance with PWS Section 5.2 |
Contract Type: Time and Material
If exercised this option shall not exceed 12-months, this option shall not include routine change requests or maintenance tasks.
Prior to the contractor initiating any work under this CLIN, the contractor shall submit a request to the VA PM and COR detailing the estimated budget and schedule for the completion of work inclusive of major milestones. The contractor shall be responsible for adhering to all requirements of the PWS section in which work is performed and all deliverables of the associated section. No work shall be funded unless projected to provide a finished useable product.
This Time and Materials CLIN is IAW FAR 52.232-7 for invoicing or billing purposes.
Purchase Order Number:
| 1 |
| LO |
| NTE $20,000,000 |
| NTE |
$20,000,000
| 3002AA |
| Change Requests (CR) Proposed Response in accordance with the requirements specified in the PWS paragraph 5.2 developed and approved change request shall be implemented in accordance with paragraph 5.3 and its sub-paragraphs due three days after receipt of change request. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 3001.
| 1 |
| LO |
| NSP |
| NSP |
| 3002AB |
| Code Release (if needed) in accordance with the requirements specified in the PWS paragraph 5.2 shall be conducted monthly within the first week of every month throughout the POP. Additional task specified in the PWS sub-paragraph 5.3.1 due at the end of each release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 3001.
| 12 |
| EA |
| NSP |
| NSP |
| 3002AC |
| Implementation Documentation. in accordance with the requirements specified in the PWS paragraph 5.2 due at the end of each release. |
All costs for successful completion of this SLIN shall be included and allocated in CLIN 3001.
| 1 |
| LO |
| NSP |
| NSP |
| Optional Task Total: |
| $ |
| Contract Total: |
| $ |
PERFORMANCE WORK STATEMENT (PWS)
DEPARTMENT OF VETERANS AFFAIRS
Financial Services Center Financial Healthcare Service eCAMS Software Support
VA-23-00011367
March 1, 2023
1.0 BACKGROUND
The Department of Veterans Affairs (VA), Financial Services Center (FSC) is authorized by the Government Management Reform Act of 1994 (Public Law 103-356) to provide common administrative support services on a reimbursable basis to VA and Other Government Agencies (OGA’s), as a Franchise Fund. The goals of the Franchise Fund organizations include:
· Lowering overhead costs
· Improving the quality and delivery of services
· Creating economies of scale
· Eliminating redundant services
· Being auditable
VA-FSC requires operations and maintenance (O&M) support and support to implement change requests for their claims adjudication system. This system is used to adjudicate, process, and prepare for payment of healthcare claims submitted by healthcare providers. As a franchise organization, the FSC has existing and potential customers that can be migrated into the system.
FSC currently uses the Electronic Claims Adjudication System (eCAMS), provided by Client Network Services, LLC (CNSI), a commercial-off-the-shelf (COTS) claims adjudication system based on CNSI’s eCAMS HCE product line. The FSC uses eCAMS to adjudicate, process, and pay healthcare claims for four programs that support our healthcare processing product line: National Dialysis Services Contract (NDNC), ICE Healthcare Service Core and Other Government Agencies (OGA),(if contracted for), and Community Care Non-Network Claims (CCNNC). Our current programs use’s Medicare-based rules and pricing; however, as a Franchise Fund, we may expand our program offerings which may involve more complex rules (all necessary configuration and implementation of such complex rules, if introduced, would be performed by VA personnel).
The purpose of this procurement is to procure operations and maintenance (O&M) support for eCAMS and support to implement change requests within the eCAMS system. O&M support includes defect resolution, technical support, and installing software patches/upgrades from CNSI. Change requests include business rule changes, code changes, integration with new VA interfaces, and implementing new healthcare program offerings.
2.0 APPLICABLE DOCUMENTS
In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:
1. 44 U.S.C. § 3541-3549, “Federal Information Security Management Act (FISMA) of 2002”
2. “Federal Information Security Modernization Act of 2014”
3. Federal Information Processing Standards (FIPS) Publication 140-2, “Security Requirements for Cryptographic Modules”
4. FIPS Pub 199. Standards for Security Categorization of Federal Information and Information Systems, February 2004
5. FIPS Pub 200, Minimum Security Requirements for Federal Information and Information Systems, March 2016
6. FIPS Pub 201-2, “Personal Identity Verification of Federal Employees and Contractors,” August 2013
7. 10 U.S.C. § 2224, "Defense Information Assurance Program"
8. Carnegie Mellon Software Engineering Institute, Capability Maturity Model® Integration for Development (CMMI-DEV), Version 1.3 November 2010; and Carnegie Mellon Software Engineering Institute, Capability Maturity Model® Integration for Acquisition (CMMI-ACQ), Version 1.3 November 2010
9. 5 U.S.C. § 552a, as amended, “The Privacy Act of 1974”
10. Public Law 109-461, Veterans Benefits, Health Care, and Information Technology Act of 2006, Title IX, Information Security Matters
11. 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”
12. VA Directive 0710, “Personnel Security and Suitability Program,” June 4, 2010, https://www.va.gov/vapubs/index.cfm
13. VA Handbook 0710, Personnel Security and Suitability Program, May 2, 2016, https://www.va.gov/vapubs/index.cfm
14. VA Directive and Handbook 6102, “Internet/Intranet Services,” August 5, 2019
15. 36 C.F.R. Part 1194 “Information and Communication Technology Standards and Guidelines,” January 18, 2017
16. Office of Management and Budget (OMB) Circular A-130, “Managing Federal Information as a Strategic Resource,” July 28, 2016
17. 32 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”
18. NIST SP 800-66 Rev. 1, An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule, October 2008
19. Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended, January 18, 2017
20. Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004
21. VA Directive 6500, “VA Cybersecurity Program,” January 24, 2019
22. VA Handbook 6500, “Risk Management Framework for VA Information Systems – Tier 3: VA Information Security Program,” March 10, 2015
23. VA Handbook 6500.2, “Management of Breaches Involving Sensitive Personal Information (SPI)”, July 28, 2016
24. VA Handbook 6500.3, “Assessment, Authorization, And Continuous Monitoring Of VA Information Systems,” February 3, 2014
25. VA Handbook 6500.5, “Incorporating Security and Privacy into the System Development Lifecycle”, March 22, 2010
26. VA Handbook 6500.6, “Contract Security,” March 12, 2010
27. VA Handbook 6500.8, “Information System Contingency Planning”, April 6, 2011
28. VA Handbook 6500.11, “VA Firewall Configuration”, August 22, 2017
29. OI&T Process Asset Library (PAL), https://www.va.gov/process/ . Reference Process Maps at https://www.va.gov/process/maps.asp and Artifact templates at https://www.va.gov/process/artifacts.asp
30. One-VA Technical Reference Model (TRM) (reference at https://www.va.gov/trm/TRMHomePage.aspx)
31. VA Directive 6508, “Implementation of Privacy Threshold Analysis and Privacy Impact Assessment,” October 15, 2014
32. VA Handbook 6508.1, “Procedures for Privacy Threshold Analysis and Privacy Impact Assessment,” July 30, 2015
33. VA Handbook 6510, “VA Identity and Access Management”, January 15, 2016
34. VA Directive and Handbook 6513, “Secure External Connections”, October 12, 2017
35. VA Directive 6300, Records and Information Management, September 21, 2018
36. VA Handbook, 6300.1, Records Management Procedures, March 24, 2010
37. NIST SP 800-37 Rev 1, Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy, December 2018
38. NIST SP 800-53 Rev. 4, Security and Privacy Controls for Federal Information Systems and Organizations, January 22, 2015
39. OMB Memorandum, “Transition to IPv6”, September 28, 2010
40. VA Directive 0735, Homeland Security Presidential Directive 12 (HSPD-12) Program, October 26, 2015
41. VA Handbook 0735, Homeland Security Presidential Directive 12 (HSPD-12) Program, March 24, 2014
42. OMB Memorandum M-06-18, Acquisition of Products and Services for Implementation of HSPD-12, June 30, 2006
43. OMB Memorandum 04-04, E-Authentication Guidance for Federal Agencies, December 16, 2003
44. OMB Memorandum 05-24, Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors, August 5, 2005
45. OMB memorandum M-11-11, “Continued Implementation of Homeland Security Presidential Directive (HSPD) 12 – Policy for a Common Identification Standard for Federal Employees and Contractors, February 3, 2011
46. OMB Memorandum, Guidance for Homeland Security Presidential Directive (HSPD) 12 Implementation, May 23, 2008
47. Federal Identity, Credential, and Access Management (FICAM) Roadmap and Implementation Guidance, December 2, 2011
48. NIST SP 800-116 Rev 1, Guidelines for the Use of Personal Identity Verification (PIV) Credentials in Facility Access, June 2018
49. OMB Memorandum M-07-16, Safeguarding Against and Responding to the Breach of Personally Identifiable Information, May 22, 2007
50. NIST SP 800-63-3, 800-63A, 800-63B, 800-63C, Digital Identity Guidelines, December 2017
51. NIST SP 800-157, Guidelines for Derived PIV Credentials, December 2014
52. NIST SP 800-164, Guidelines on Hardware-Rooted Security in Mobile Devices (Draft), October 2012
53. Draft National Institute of Standards and Technology Interagency Report (NISTIR) 7981 Mobile, PIV, and Authentication, March 2014
54. VA Memorandum, VAIQ #7100147, Continued Implementation of Homeland Security Presidential Directive 12 (HSPD-12), April 29, 2011 (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)
55. IAM Identity Management Business Requirements Guidance document, May 2013, (reference Enterprise Architecture Section, PIV/IAM (reference https://www.voa.va.gov/documentlistpublic.aspx?NodeID=514)
56. VA Memorandum “Personal Identity Verification (PIV) Logical Access Policy Clarification,” July 17, 2019, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4896
57. Trusted Internet Connections (TIC) Reference Architecture Document, Version 2.2, Federal Interagency Technical Reference Architectures, Department of Homeland Security, June 19, 2017, https://www.dhs.gov/sites/default/files/publications/TIC_Ref_Arch_v2.2_2017.pdf
58. OMB Memorandum M-08-05, “Implementation of Trusted Internet Connections (TIC), November 20, 2007
59. OMB Memorandum M-08-23, Securing the Federal Government’s Domain Name System Infrastructure, August 22, 2008
60. VA Memorandum, VAIQ #7497987, Compliance – Electronic Product Environmental Assessment Tool (EPEAT) – IT Electronic Equipment, August 11, 2014 (reference Document Libraries, EPEAT/Green Purchasing Section, https://www.voa.va.gov/documentlistpublic.aspx?NodeID=552)
61. Sections 524 and 525 of the Energy Independence and Security Act of 2007, (Public Law 110–140), December 19, 2007
62. Section 104 of the Energy Policy Act of 2005, (Public Law 109–58), August 8, 2005
63. Executive Order 13834, “Efficient Federal Operations”, dated May 17, 2018
64. Executive Order 13221, “Energy-Efficient Standby Power Devices,” August 2, 2001
65. VA Directive 0058, “VA Green Purchasing Program”, July 19, 2013
66. VA Handbook 0058, “VA Green Purchasing Program”, July 19, 2013
67. Office of Information Security (OIS) VAIQ #7424808 Memorandum, “Remote Access”, January 15, 2014, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28
68. Clinger-Cohen Act of 1996, 40 U.S.C. §11101 and §11103
69. “Veteran Focused Integration Process (VIP) Guide 3.2”, December 2018, https://www.voa.va.gov/DocumentView.aspx?DocumentID=4371
70. VA Memorandum “Proper Use of Email and Other Messaging Services”, January 2, 2018, https://www.voa.va.gov/DocumentListPublic.aspx?NodeId=28
3.0 SCOPE OF WORK
The Contractor shall provide operations and maintenance (O&M) support for eCAMS and support to implement change requests within the eCAMS system. O&M support includes defect resolution, technical support, and installing software patches/upgrades from CNSI. Change requests include business rule changes, code changes, integration with new VA interfaces, and implementing new healthcare program offerings. Activities included in this support include: configuration, implementation, integration, testing, deployment of software, training, maintenance, and technical support in accordance with paragraph 5 of this PWS and its sub-paragraphs.
The O&M portion of this contract shall be a firm-fixed price contract. The change request portion of this contract shall be priced based on a time and materials (T&M) contract line item, not to exceed $5,000,000 for each period of performance.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .