APPROVED AMENDMENT 002.docx

M0026320Q1018

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 31-Aug-2020 11:00 AM to 02-Sep-2020 11:00 AM.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

DESCRIPTIONS AND SPECIFICATION

1. Background

This contract is in support of the Marine Corps Recruiting Command’s (MCRC) prospect messaging for each of the six Marine Corps Districts (MCD), which are located throughout the United States and its territories. Prospect messaging will allow recruiters to engage with their target market through short message service (SMS) text messaging. MCRC requires access to an information system platform that enables SMS text messaging with perspective applicants and poolees and will comply with current policies and directives applicable to the safeguarding of Personally Identifiable Information (PII).

2. Objectives

The objective of this contract is to provide an information system with the capability of engaging a recruiter’s target market, through a commercial off-the-shelf application that allows the user to customize and automate content and communication. This information system will comply with current policies and directives applicable to safeguarding PII.

3. Scope

MCRC identified a need for a firm-fixed price contract for the capability to leverage mobile device management capabilities, such as SMS text messaging, for data collection and lead generation. The guidance and specification for the prospect messaging is based on the guidelines and specifications cited in Sections 4 through Section 6.

4. Requirements Points of Contact

4.1. Government Technical Point of Contact (POC): The MCRC Government POC will be identified upon contract award.

4.2. Recruiting District Representatives: The marketing and communication officer and chiefs (MACO/C) at each district will serve as a Recruiting District Representative and the technical point of contact (POC) for each MCD.

4.3. Contractor POC: The contractor shall establish a single management focal POC to accomplish the administrative, managerial, warranty, and financial aspects of this contract, and this person will serve as the primary interface with the Government Technical Point of Contact and the MACO/C, and the contracting office.

5. Platform Requirements

The tasks for this requirement shall include the following. For any referenced document or publication, the contractor must comply with the most recent edition, or in the case of any document or publication that is superseded, the newest edition of the document or publication that supersedes the one mentioned below. Also, any databases are to be made available to specific United States Government (USG) personnel on direction of the Contracting Officer. When the contractor makes such records available, the USG point of contact will be given access to records to be able to search, print, and download specific records or groups of records. The contractor is not to monitor our system or make backup copies of text messages.

Vendor will maintain all records of data generated by or on its platform in performance of or related to this contract, to include histories of numbers to whom Recruiters send messages or from which Recruiters receive messages, and records of the content of and attachments to messages sent and received. All databases are USG property and the USG will maintain all rights to the databases; the contractor’s system will comply with the Privacy Act and implementing regulations. The vendor may not make any use of the databases other than to perform this contract, and is not to allow access to such records by any individual who is not an employee of the vendor who needs such access for the vendor to perform this contract. At the end of the contract the contractor will turn over all such records to USG.

The contractor must maintain intellectual property as required by the contract and submit an Intellectual Property Release when appropriate. All data, regardless of format, created, generated, produced or provided under, or as a result of, this contract is and shall remain the property of the U.S. Government/Marine Corps. This data includes, but is not limited to, reports, materials, data, information, and all electronic/digital files. It also includes all training and training-related materials which consists of all evaluations and evaluation criteria, computer software/applications and hardware, source code, interfaces, tools, works, and other related items. The items described herein, and any other items, are hereinafter referred to individually or collectively as the Work or Works. The U.S. Government/Marine Corps shall be the owner of all of these Works and all intellectual property rights in or to these Works. Therefore, any restricted data rights, information, software, materials and/or other items, including the contractor’s or a third-party’s proprietary data, information, software, materials and/or items must not be used under this contract without the specific written approval by the KO prior to the start of any work.

The contractor shall assign or by this contract has assigned all intellectual property rights in or to the Works and other items required under this contract.

The contractor will maintain records of all messages sent, including the sender(s) and receiver(s) of all messages, the content of all messages, and any attachments to any messages, in accordance with policies in SECNAV M-5210.1, and will retain records for at least three years or the end of the contract, whichever is sooner. The contractor will notify the Government point of contact at least fifteen (15) business days before any such deletion of data. The contractor will provide a copy of any data to the Government point of contact, and receive conformation from the Government point of contact that the Government has received the records, before deleting any data.

The Contactor must operate all access, collection, and storage of all electronic and hardcopy data in compliance with the DoD Risk Management Framework (RMF). The Contractor must comply with all provisions relating to accessing, collection, storage, sharing, use, and disposition of data in any form stated in all applicable instructions, regulations, and guidance, including that listed below. The Contractor shall perform all necessary upgrades and updates to comply with emerging security requirements.

The contractor is prohibited from selling, sharing, reusing, or in any way profiting from the data obtained in the performance of tasks associated with this contract without first obtaining the written approval of the KO.

In the event of a cyber incident (e.g., unplanned interruption of service), suspected or actual compromise, breach, denial of service of network resources, or actual or suspected loss, spillage, or compromise of personally identifiable information, the contractor shall notify the Contracting Officer as soon as practicable but not later than 72 hours after discovery of the incident.The Contracting Officer may modify the contract after award to add additional points of contact, which the contractor will also be responsible for notifying.

All IT resources and services required under this Contract shall comply with the following information assurance policies and guidance, as well as any subsequent version or superseding guidance published, and those listed elsewhere in this section 5 and elsewhere in the contract:

Chiefs of Staff Instruction Defense Information Systems Network Responsibilities

Chiefs of Staff Manual Cyber Incident Handling Program

and Electronic Messaging

Internet-Based Capabilities

Standards and Technology Assessing Security and Privacy Controls in Federal Information Systems and Organizations

*The most-recent versions of these references apply.

The controls and standards incorporated in the data security framework mentioned above are evolving. The Contractor must adhere to and implement changes in accordance with the then current regulations and policies.

5.1. Accommodates the information system on the categorization of FedRAMP Information Impact Level 4 (Controlled Unclassified Information – Privacy Information). The messaging platform will facilitate full support of any features native to the SMS text message format, to include text, image, gif, and web link support. The requirement, specifically Information Impact Level 4, is categorized in the DoD Cloud Computing Security Requirements Guide v1r3. Privacy Information refers to personal information or, in some cases, PII as defined in OMB M-07-16 or means of identification as defined in 18 USC 1028(d)(7). Level 4 is found in the DoD Cloud Computing Security Requirements Guide v1r3 starting on page 26.

5.1.1. Ability and capability to meet the OMB, Office of E-Government and Information Technology, 25 Point Implementation Plan to Reform Federal Information Technology Management that requires U.S. Federal Agencies to use cloud-based solutions whenever a secure, reliable, cost-effective cloud option exits.

5.1.2. Ability and capability to meet the OMB FedRAMP Policy Memo; Security Authorization of Information Systems in Cloud Computing Environments. This FedRAMP Policy Memo requires that all Federal Agencies meet the FedRAMP requirements for all Agency use of cloud services within two years of FedRAMP declared operational. FedRAMP began its initial operational capability on 04 June 2012.

5.1.3. Ability and capability to meet the NIST SPs 500-320, 800-53, 800-61, 800-92, 800-182, and 1800-19 requirements.

5.2. Ability and capability to provide communication from a single management user interface across SMS text messaging. The user will have the ability to upload lists for specific campaigns (i.e., “Graduate Reserve Prospects”). The system will also provide notification to the user if a particular phone number was already uploaded to the system for another campaign, regardless of geographic or account used to initially upload it (to prevent multiple campaigns targeting a single individual unless intended).

5.3. Ability and capability to leverage automation with Natural Language Processing Artificial Intelligence across SMS text messaging to produce higher lead-production rates and to increase recruiter productivity. The results will readily display the total number of outgoing messages sent, those responded to, and whether or not the response was positive or negative (such as a desire to be removed from that particular campaign or messaging list or an interest in more information).

5.4. Ability and capability to allow drip campaigns which is the automatic sending of a timed series of SMS text messages to individuals or group of contacts.

5.5. Ability and capability to create, produce, and update data as a single source of record to include the entire communication history.

5.6. Ability and capability to operate on the MCRC’s June 2020 End User Device (EUD) baseline as follows:

5.6.1. Microsoft Windows 10, Version 1809 (OS Build 17763.1217) or latest.

5.6.2. Google Chrome, Version 83.0.4103.97 (Official Build) (32-bit) or latest.

5.6.3. Microsoft Edge, Version 44.17763.831.0 or latest.

5.6.4. Microsoft Internet Explorer 11, Version 11.1217.17763.0, Update Version 11.0.190 (KB4456798) or latest.

5.6.5. Google Chrome 83.0.4103.101, Operating System Android 7.0.0; SM-G930V Vuild/NRD90M or latest.

5.6.6. The contracted Information System utilizes a Certificate Authority trusted by the Department of Defense Information Network (DODIN).

5.7. Ability and capability to tag, manage, track, and filter multiple SMS text messaging "campaigns" to personalize the message narrative to fit a specific market or message or both. This includes the ability to “Text to Apply,” where the message will be routed based “campaigns” and other defined criteria.

5.8. Ability and capability to use a "wildcard" in the SMS text message to allows the user to send individual messages in bulk using the (first) name, (last) name, or both names of the individual to provide a customized message to each recipient (i.e., Hello Sam, or Hello Mr. Jones, vice simply hello) without requiring the user to enter the name(s) for each specific intended recipient.

5.9. Ability and capability to provide an administrator level dashboard for program oversight, reporting, and analysis of return on investment. This dashboard will include the ability to monitor all conversations happening in near real time and allow for filtering of results based off of SMS text "campaign" or user.

5.10. Ability and capability to provide a generic phone number from which SMS text messages originate that is not a phone number in use by an individual (i.e., all text messages received by recipients appear to come from a generic number not belonging to an actual phone line in use). The tool will allow for the ability to call forward to a phone number, defined by the user, any calls to that number (in the event a recipient chooses to call vice text a response). This will ensure that the flow and continuity of conversations and messages remain between the recipient and the user’s web and app interface and only departs from that chain of conversation when a voice conversation is initiated.

5.11. In the event that the user does not enter a call-forwarding number, the tool will provide for the ability to setup a voicemail inbox for the SMS text number with the ability for a user to check and clear those messages through either the web interface or mobile app.

5.12. Vendor is subject to government security assessments, security control evaluations, and penetration tests.

5.13. Vender will provide a help desk capability with on-call training for individual, and groups of, users.

6. Period of Performance

6.1. Commencement. The contractor shall commence performance of the work on the contract immediately upon receipt of the first Delivery Order issued under the Indefinitely Delivery, Indefinite Quantity (IDIQ) Contract.

6.2. This IDIQ contract establishes a five (5) year ordering period during which platform licenses may be purchased at a fixed-unit price via Delivery Orders up to the maximum amount established in the contract. Each license purchased under a Delivery Order shall have a license period of one (1) year from the date of Order issuance.

The Government is required to purchase the minimum amount established in the contract (the minimum amount is established as a dollar value). The Government may purchase additional license quantities on an as-needed basis (via subsequent Delivery Orders) up to the maximum not-to-exceed (NTE) amount established in the IDIQ contract.

SECTION I - CONTRACT CLAUSES

The following have been added by reference:

(End of Summary of Changes) image1.wmf