36C10B22R0118 AMD 0004.docx

36C10B22R0118

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

06-13-2022 Kyle Maccia 848-377-5249 076-0627-2022

2:00PM

EDT

Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

X

517312 1500 Employees

N/A

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

See CONTINUATION Page Title: Enterprise Mobile Devices and Services 2.0

Contract Specialist: kyle.maccia@va.gov, 848-377-5249

Contracting Officer: debra.clayton2@va.gov, 848-377-5174

Debra Clayton Contracting Officer

Table of Contents

SECTION B - CONTINUATION OF SF 1449 BLOCKS

B.1 CONTRACT ADMINISTRATION DATA

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

a. CONTRACTOR: TBD

b. GOVERNMENT:

Contracting Officer 36C10B Department of Veterans Affairs Technology Acquisition Center 23 Christopher Way Eatontown NJ 07724

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

3. INVOICES: Invoices shall be submitted in arrears:

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

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

B.1 GOVERNING LAW CLAUSE

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

B.2 SOFTWARE LICENSE, SOFTWARE MAINTENANCE AND SOFTWARE 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/or 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 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 two business days) in resolving software problems will be noted in the Government’s various past performance records on the Contractor (e.g., www.cpars.gov).

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

(4). Disabling Software Code.

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

(5). Manuals and Publications.

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

B.3 PRICE SCHEDULE

The Offeror is required to complete and submit the Government provided Price Schedule found at Attachment B – Price Schedule EMDS 2.0 - 36C10B22R0118 to the Solicitation. Instructions for the Spreadsheet can be found in the Worksheet entitled “Instructions.” This sheet will form the basis of the Price Schedule which will be incorporated into any subsequently awarded contract.

B.4 PERFORMANCE WORK STATEMENT

Page 1 of Page 1 of

PERFORMANCE WORK STATEMENT (PWS)

DEPARTMENT OF VETERANS AFFAIRS

Office of Information & Technology Telecommunications Provisioning Office

Enterprise Mobile Devices and Services (EMDS) 2.0

Date: January 18, 2022

VA-22-00000147

PWS Version Number: 1.0

1.0 BACKGROUND

The Department of Veterans Affairs (VA), Office of Information & Technology (OIT), Development, Security, and Operations (DevSecOps), Solution Delivery (SD) strives to provide high quality, effective, and efficient mobile device services to VA Medical Centers (VAMCs), Community Based Outpatient Clinics (CBOC)s, field and program offices and other remote users that are geographically dispersed throughout the 50 United States (US), District of Columbia, Guam, Saipan, American Samoa, Philippines, and Puerto Rico. These services include the availability of continuous wireless telecommunications services to include data (email), telephone/voice (including voicemail) and/or wireless internet to designated VA staff within the geographic areas identified herein.

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 – Tier 3: 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 Handbood 6500.10, “Mobile Device Security Policy, February 15, 2018

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

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

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, December 2018

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

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

This is an acquisition for cellular and wireless services and devices for VA for providing mobile device and related wireless services to VAMCs, CBOCs, field and program offices and other remote users throughout the 50 United States, District of Columbia, Puerto Rico, Guam, American Samoa, Saipan, and Philippines to include the VA facilities listed in Attachment A - VA Facilities EMDS 2.0 - 36C10B22R0118, as well as outside the United States on a temporary basis. Attachment A will be updated as needed as VA adds and removes locations based on mission needs. Wireless services include voice and text only services (voice phone devices); voice, text, and data services (smartphone devices); and data services (mobile broadband cards, and tablets). The Contractor shall provide all labor, management, tools, materials, and equipment to perform all requirements described herein. The scope of this work shall include the incorporation of emerging technologies over the life of the contract. Currently, the VA Enterprise consists of approximately 120,000 activated mobile devices with the opportunity for future growth. The forecasted rate of growth is 15% per year. Additionally, a high-speed nationwide wireless broadband network dedicated to public safety will be required for emergencies and disaster recovery situations. The scope of this work shall also include ebonding to interface with the VA Electronic Telecom Expense Management System when needed.

4.0 PERFORMANCE DETAILS

4.1 PERFORMANCE PERIOD

The period of performance (PoP) shall consist of a six-month base period followed by eight 12-month option periods and one 6-month option period as well as options for increased quantities. The overall PoP shall not exceed 108 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 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 PLACE OF PERFORMANCE

Services shall be provided to the VA facilities listed in Attachment A - VA Facilities EMDS 2.0 - 36C10B22R0118.

4.3 TRAVEL

The Government anticipates minimal 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. . These costs will not be directly reimbursed by the Government.

5.0 SPECIFIC DELIVERABLES AND TASKS

5.1 PROJECT MANAGEMENT

The Contractor shall provide a dedicated account support team to include an account manager, program manager, 24/7/365 vendor network support.

5.1.1 KICKOFF MEETING

A technical kickoff meeting shall be held within 10 days after contract award. The Contractor shall coordinate the date, time, and location (can be virtual) with the Contracting Officer (CO), as the Post-Award Conference Chairperson, the VA PM, as the Co-Chairperson, the Contract Specialist (CS), and the Contracting Officer’s Representative (COR). The Contractor shall provide a draft agenda to the CO and VA PM at least 5 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 EMDS 2.0 requirement.” The Contractor shall submit the final updated presentation to the CO for review and signature within 3 calendar days after the meeting. The Contractor shall also work with the CS, the Government’s designated note taker, to prepare and distribute the meeting minutes of the kickoff meeting to the CO, COR, and all attendees within 3 calendar days after the meeting. The Contractor shall obtain concurrence from the CS on the content of the meeting minutes prior to distribution of the document.

Deliverable:

A. Kickoff Agenda B. Kickoff Presentation C. Kickoff Meeting Minutes

5.1.2 TRANSITION REQUIREMENTS

If the incumbent Contractor does not secure this contract award, the new Contractor shall have until October 31, 2022, to transition to the new contract. The Contractor shall provide transition support to each site identified. The Contractor shall provide the level of support described below:

1. Should the Contractor be the incumbent provider for the facility, transition may consist only of moving the existing devices and numbers to the new contract account numbers, and no new equipment for devices in service shall be received as part of the transition. Any new devices as part of this contract will be ordered accordingly. Throughout the performance period of the contract, equipment refresh as outlined in these requirements will be coordinated with the individual sites as time and staffing permits, and during equipment refresh, transitions of smartphone operating system (OS) may or may not occur, but will remain within the contracted parameters of the Contractor, all of which will be coordinated with the local VA Telecommunications Provisioning Office (TPO).

2. Should the Contractor not be the incumbent provider for the facility, in order to ensure continuity of services and minimal impact to end users, the Contractor shall provide support services to ensure that transition be fully complete by October 31, 2022. The service delivery points to be awarded on a contract, referenced in Attachment A - VA Facilities, will be identified by the COR after award. The Contractor shall provide a Transition Plan which outlines its approach to transition and should include a phased plan for device replacement, if necessary. The transition shall be coordinated with the primary COR.

Deliverable:

A. Transition Plan

5.1.3 CONTRACTOR PROJECT MANAGEMENT PLAN

The Contractor shall deliver a Contractor Project Management Plan (CPMP) that details 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 Contractor shall deliver the CPMP to VA 90 days after contract award. The Contractor shall update and maintain the VA PM approved CPMP throughout the PoP.

Deliverable:

A. Contractor Project Management Plan

5.1.4 REPORTING REQUIREMENTS

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

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

The Contractor shall provide Monthly Invoice Reports/Bill Review and meetings to review the current billing cycle, which shall occur prior to submission of Monthly Invoices into the VA electronic payment system.

The Contractor shall provide Ad hoc reports for the purpose of responding to such as inquiries as VA leadership requests, Congressional inquiries, etc.

The Contractor shall provide a weekly device count showing number of active devices.

The Contractor shall provide a zero usage report on a quarterly basis showing any device which has not been used in the preceding 90 days.

The Contractor shall provide a zero usage report on a quarterly basis showing any device which has not been used in the preceding 180 days.

The Contractor shall provide a device upgrade list showing all devices that are eligible for upgrade on a monthly basis.

The Contractor shall provide reporting on the number of EPEAT-registered products purchased or leased under this contract, together with the total number of unregistered products purchased. For each piece of equipment sold/leased, EPEAT Registration Status (i.e., Bronze, Silver, Gold or Unregistered) shall be provided by the Contractor on a yearly basis.

Deliverables:

A. Ad hoc reporting B. Monthly Invoice Report- Bill Review (PowerPoint) C. Weekly Device Counts - Active Devices D. 90- Day zero usage report (Receive monthly) E. 180 -Day zero usage report (Receive monthly) F. Device Upgrades List (Receive Monthly) G. Electronic Product Environmental Assessment Tool (EPEAT) reporting and compliance (Quarterly).

5.1.5 PROGRAM PROGRESS REVIEWS

The Contractor shall conduct Program Progress Reviews (PPR) for Government personnel at a mutually agreeable facility (can be virtual). The CO, or the COR, will schedule the initial PPR. The first PPR shall occur in Option Period One. Thereafter, PPRs shall occur annually, for the life of the contract. During each PPR, the Contractor shall present provide a PPR presentation that addresses the current status of the Contractor’s projects and any outstanding complaints or services.

The Contractor shall provide an PPR Agenda three days prior to the PPR and PPR presentation and meeting minutes three days after the PPR.

Deliverables:

A. PPR Presentation B. PPR Agenda C. PPR Minutes

5.1.6 ADDITIONAL REPORTING

5.1.6.1 EMERGING TECHNOLOGY REPORTS

The Contractor shall supply a Monthly Internet of Things (IoT) Technologies Report on any new IoT technologies that come to market for potential VA use related to VA’s technology integration, that VA might integrate into the VA network. The IoT Technologies Report shall include New and Emerging Technology the Contractor additions to include anything that may have a positive impact on improving the VA’s network connectivity using mobile networks.

Deliverable:

A. Emerging Technology Report

5.2 GENERAL REQUIREMENTS

The Contractor shall provide one to three options for devices at no additional cost , one generation behind current market offering, that meet the requirements of the RFP. Devices shall be offered with select service plans and shown on the Contractor-provided Management Portal.

5.2.1 VOICE PLANS OVERVIEW

The Contractor shall provide voice plan(s) that shall include Smartphones and Basic Phones with the service plan which shall include the following features:

1. Caller ID display

2. Call waiting

3. Three-way calling

4. Voice and texting capability

5. A minimum standard of 4G or higher to be standard for all devices (Smart phones, basic phones, mobile WiFi (MiFi)

6. Hands free compatible

7. Support WiFi calling

8. Push-to-talk

9. Commercially available ruggedized device

5.2.2 TEMPORARY INTERNATIONAL COVERAGE

In rare instances, VA personnel require use of their devices while overseas. This task (which will be priced separately) is to provide temporary international coverage to identified devices. When requested by the CO or COR, the Contractor shall provide services that include the following at a minimum:

1. Data usage

2. Roaming or long distance charges

3. Voice mail with message waiting indicator

4. Caller ID

5. Call waiting

6. Three-way calling

7. Call forwarding

8. Text messaging

5.3 VOICE PLAN REQUIREMENTS FOR SMARTPHONES AND BASIC PHONES

The Contractor shall provide voice plans that include the following, for all Smartphones and Basic Phones:

1. Descriptions of the Plans

a. Unlimited Voice and Text

i. The Contractor shall NOT throttle, or reprioritize, the data for designated essential field staff

ii. The Contractor shall always maintain optimal data speeds for the cellular user.

b. Group Texting with QWERTY keyboard

c. Smart Phone

d. Basic Phone

e. QWERTY Device

f. Out of Warranty Device

5.3.1 FEATURES FOR BASIC PHONE PLANS ONLY

The Contractor shall include, in the voice plans for all Basic Phones only, the following features:

1. International service shall be blocked on all devices provided. International service shall only be activated on devices upon written request by the COR.

2. Devices shall be eligible for “buddy” upgrades based on upgrade eligibility of other devices on the contract.

3. Devices shall block all toll calls not included in the unlimited minutes plan, including directory assist (e.g., 411), premium rate numbers (e.g., 900 numbers) unless specifically requested in writing from the COR.

4. Devices shall block all International Toll/Long Distance calls from US, unless specifically requested in writing from the COR.

5.4 DATA PLANS OVERVIEW

Data devices include smartphones, data cards, mobile hotspot, and tablet computing devices. The Contractor shall provide devices used for data that include the following features:

1. All devices provided under this effort shall be on VA’s approved devices list, including current market offering devices. VA will provide this list, which will evolve over time as new devices are tested and approved.

2. As applicable, all data devices shall be managed by VA’s Mobile Device Management (MDM).

3. The Contractor shall load the latest version of VA’s MDM application and any other device standard commercial applications (prior to shipment).

4. All Apple and Android devices shall be enrolled in the Apple and Android Device Enrollment Program (DEP) by the Contractor unless designated by the COR as a test device.

5. International service shall be blocked on all devices provided. International service shall only be activated on devices upon written request by the COR.

6. Visual Voicemail on smartphones shall always be enabled and active.

7. Vibrate alert shall be available for emails and text messages.

8. Ring alert shall be available for emails and text messages.

9. Ability to disable audio recording, video recording, and all recording functionality.

10. Ability to transmit and receive data (e.g., surf the Internet) while conducting a voice session.

11. Devices shall be compatible with email services that employ Advanced Encryption Standard (AES) encryption that is FIPS validated 140-2.

12. Devices shall be retained by VA, except those that are recycled through VA approved recycling program.

13. Ability to install private / internal applications onto the device.

14. Ability to side load applications (i.e., push to VA’s device catalog) as needed for iOS or Android.

15. Devices should have full hardware / software support from manufacturer for at least 24 months from date of VA receiving the device including the ability to get the latest software patches from the OS vendor, not necessarily the Contractor or reseller.

5.4.1 DATA PLAN REQUIREMENTS FOR SMARTPHONES, MIFI, AND TABLETS

The Contractor shall include data plans the following features for the smartphones, smartphone hotspot, tablets, and MiFi:

1. Data shall include emails, Internet access, video, Short Message Service (SMS), Multimedia Messaging Service (MMS), Rich Communication Services (RCS), and other data.

2. A data service plan added to a voice service plan. This is defined as a data add-on service plan.

3. Fourth Generation (4G) or higher data rates. Higher means that, when the best available data rates offered to customers in the area of service are higher than 4G, the higher network technology rate shall be provided (5G, 6G, etc.).

4. Custom 5G Data Only - 15GB (Broadband & Hotspots & Tablets).

5. Two to five unlocked device types shall be provided at no additional cost, meeting the requirements defined herein, shall be offered per plan, and shown on the Contractor-provided VA Government website. One device shall be iOS VA Security Technical Implementation Guide (STIG) Approved and one device will be Android VA STIG Approved.

6. The Contractor shall provide 2 devices that are compliant with Section 508, 1194.31 of the Rehabilitation Act.

7. The Contractor shall provide devices that are for inclusion on VA’s approved devices list must be submitted to VA for testing at least 45 days prior to the refresh date. At least 30 days prior to submitting devices for testing the Contractor shall notify the CO and COR in writing of the impending device change. Notification shall include at a minimum the specific manufacturer, make and model number of the current device on contract and those of the refresh device. The price of the device(s) added to VA’s approved devices list, including support services, shall be equal to or lower than the current contract pricing for the same product.

8. The Contractor shall provide an emergency responder or network priority plans for designated sites and staff.

5.4.2 DATA PLAN FOR MACHINE TO MACHINE (M2M) ONLY

The Contractor shall provide Machine to Machine (M2M) data plans with the following features for the M2M devices:

1. 25GB, 50GB, 100GB, 500GB, and up to 1TBUnlimited Data plans shall be included for M2M devices.

2. M2M plans shall be at a minimum of 4G. If better network technology is available in a service delivery point (SDP) market, the Contractor shall provide the latest technology available.

3. No prioritization, throttling or decrease in speeds at any usage level. Network speeds must remain at the fastest commercial rate possible.

4. Pooling - All M2M data ordered shall be pooled at the contract level.

5. Software updates to devices shall be made over the wireless network.

6. The Contractor shall provide an emergency responder or network priority plans for designated sites and staff.

5.4.3 MIFI HOTSPOT DEVICE REQUIREMENTS

The Contractor shall provide MiFi Hotspot data plans that include MiFi Hotspot Devices with the service plan which shall include the following features:

1. Capable of providing support to five devices at once.

2. Battery power availability of at least 3.5 hours.

3. At least protocol 802.11n based router. If a greater network technology exists, the Contractor will provide the updated equipment.

4. Plans shall be at a minimum of 4G. If better network technology is available in a SDP market, the Contractor shall offer the latest technology available.

5. Existing telephone number portability when transferring to a new device.

6. The Contractor shall provide an emergency responder or network priority plans for designated sites and staff.

5.5 SEED STOCK

Seed stock is identified as new, non-refurbished, non-activated smartphones.

The Contractor shall ensure new devices from seed stock shall be available upon request at a minimum of 5% of the total contract device count. Seed stock devices shall meet the device requirements set forth at PWS paragraph 5.2, General Requirements.

The seed stock pool shall refresh to the full 5% at the beginning of each PoP option period, at no cost to VA, until the devices are activated. (No seed stock to be provided for iPads and M2M devices, basic phones, and MiFi’s.)

5.6 TEXT MESSAGE ARCHIVING – OPTIONAL TASK

The Contractor shall provide a text message archiving solution. This solution shall contain a Federal Risk and Authorization Management Program (FedRamp) Approved rating of High along with an approved Authority to Operate and shall be a cloud-hosted, Software-as-a-Solution capability. The solution shall have a minimum of seven years retention time with contractor hosted storage and shall provide the following:

1. FedRamp Authorized search and retention capabilities.

2. External archiving capabilities.

3. Advance administration based on roles.

4. Export capabilities directly from the Contractor.

5. All devices must be compliant with text message archiving if this option is exercised in order to meet the eDiscovery requirements as defined by National Archives and Records Administration.

5.7 STANDARD ACCESSORIES

The Contractor shall provide standard accessories for each provided voice phone device and/or smartphone device. All devices shall include wall charger, charging cable and any other receptacle needed to power the device. The standard accessory package shall also include any wired or wireless headsets or earbuds and shall be included in the price of the service plans.

5.7.1 OTHER ACCESSORIES

The Contractor shall provide such items as screen protectors, durable protective cases, car chargers, Phone Cases, Front Clear Cover, Tablet Cases, Belt Clip Cases, USB Cable. Each item will be separately priced and other accessories may be ordered within scope modification.

5.8 VOICE AND DATA COVERAGE

VA business practices and patient care are reliant upon adequate cellular coverage both inside and outside of the designated locations.

The Contractor shall provide voice and data coverage for a 50 mile radius around all VA facilities in Attachment A - VA Facilities, as well as within the facilities themselves. These locations are in the 50 United States, District of Columbia, Puerto Rico, Guam, American Samoa, Saipan, and Philippines. The Contractor shall rapidly react to and resolve coverage issues that may arise due to dynamically changing usage within a covered area. The Contractor shall provide reliable cellular communications inside all the facilities of Attachment A - VA Facilities.

Where the Contractor does not have adequate signal to penetrate the buildings, the Contractor shall take measures to enhance the signal or make arrangements with other contractors to provide the required service. The Contractor shall provide Reliable Service Coverage in and around the required coverage areas. Reliable Cellular Communications Service Coverage shall be defined as signal strength, reported in decibel-milliwatts (dBm), of not less than -100 dBm in all exterior locations on the property and not less than -90 dBm in interior locations. Signal strength measurements shall be in terms of Reference Signal Received Power (RSRP), Received Signal Code Power (RSCP) or other equivalent, technology-specific measurement (measured or converted to dBm). The Contractor shall ensure this Reliable Service Coverage level to at least 90% of the SDP coverage areas identified in Attachment A – VA Facilities.

Additionally, the Contractor shall respond to coverage issues identified by the COR. The Contractor shall, upon written notification from the COR, propose a coverage resolution plan for the affected area(s) within 15 business days.