70RDAD20R00000019-0001 Attachment 1 - CLINs and SOW.pdf

70RDAD20R00000019 Attachment 1 - SCHEDULE OF CLINS AND STATEMENT OF WORK

CONTRACT LINE ITEM NUMBER (CLIN) 0001

Base Period

Period of Performance: Twelve (12) Months

SUPPLIES/SERVICES CLIN TYPE UNIT QUANTITY UNIT PRICE TOTAL PRICE

Named User License FIRM FIXED

PRICE

EA 12

Concurrent User License FIRM FIXED

PRICE

EA 12

User Training FIRM FIXED

PRICE

EA 24

Upgrade to Private VPC FIRM FIXED

PRICE

LO 1

CONTRACT LINE ITEM NUMBER (CLIN) 1001

Option Period One Period of Performance: Twelve (12) Months

SUPPLIES/SERVICES CLIN TYPE UNIT QUANTITY UNIT PRICE TOTAL PRICE

Named User License FIRM FIXED

PRICE

EA 12

Concurrent User License FIRM FIXED

PRICE

EA 12

User Training FIRM FIXED

PRICE

EA 24

Annual Private VPC FIRM FIXED

CONTRACT LINE ITEM NUMBER (CLIN) 2001

Option Period Two Period of Performance: Twelve (12) Months

SUPPLIES/SERVICES CLIN TYPE UNIT QUANTITY UNIT PRICE TOTAL PRICE

Named User License FIRM FIXED

PRICE

EA 12

Concurrent User License FIRM FIXED

PRICE

EA 12

User Training FIRM FIXED

PRICE

EA 24

Annual Private VPC FIRM FIXED

CONTRACT LINE ITEM NUMBER (CLIN) 3001

Option Period Three

Period of Performance: Twelve (12) Months

SUPPLIES/SERVICES CLIN TYPE UNIT QUANTITY UNIT PRICE TOTAL PRICE

Named User License FIRM FIXED

PRICE

EA 12

Concurrent User License FIRM FIXED

PRICE

EA 12

User Training FIRM FIXED

PRICE

EA 24

Annual Private VPC FIRM FIXED

CONTRACT LINE ITEM NUMBER (CLIN) 4001

Option Period Four Period of Performance: Twelve (12) Months

SUPPLIES/SERVICES CLIN TYPE UNIT QUANTITY UNIT PRICE TOTAL PRICE

Named User License FIRM FIXED

PRICE

EA 12

Concurrent User License FIRM FIXED

PRICE

EA 12

User Training FIRM FIXED

PRICE

EA 24

Annual Private VPC FIRM FIXED

Open Source Collection Operations Tool Interface Requirements Statement of Work (SOW)

1.0 BACKGROUND INFORMATION

1.1 The Department of Homeland Security (DHS) Office of Intelligence and Analysis (I&A) mission is to equip the Homeland Security Enterprise with timely intelligence and information it needs to keep the homeland safe, secure, and resilient.

1.2 To meet the operational needs of our Homeland partners, DHS I&A has transitioned to a Mission Center concept that increases integration between intelligence and operations across the Department. These Mission Centers are responsible for integrating intelligence and information to drive threat mitigation and decision making across the Current Intelligence, Counterterrorism, Transnational Organized Crime, Cyber, Economic Security and Trade, and Counterintelligence areas.

1.3 To support the intelligence and operational mission center needs of the Current and Emerging Threats Center (CETC), DHS I&A Open Source Collection Operations (OSCO) serves as the primary DHS collector of homeland security open source intelligence and information.

OSCO conducts open source collection exploitation operations and produces open source intelligence reports for dissemination to a variety of customers supporting the protection of national, international, and homeland security missions.

2.0 SPECIFIC REQUIREMENTS/TASKS

2.1 To procure a software interface tool to assist the Government in DHS collection of publicly available information in response to analytic and customer needs through automated assistance, reducing the amount of time a collector spends collecting data on an independent DHS collection system. The software interface shall be compatible with the existing DHS collection systems and must be immediately deployable. The vendor must be able to automate the loading and configuration of the interface on a LYNX platform for multiple users. The system should be implemented on premise as a subscription SaaS model over a private cloud base service.

Specifically, the vendor must have the capability for deployment to the Amazon Virtual Private Cloud (VPC) us-east-2. The interface from the users browser to the all vendor interfaces shall support private to private AWS network connection via VPC peering. The vendor must have the ability to integrate on an DHS agreed upon network address subnet assignments prior to deployment. The vendor must have Domain Name Service (DNS) and Transport Layer Security (TLS) to support the VPC peering. The vendor must have the ability to provide a tool extension from an app store and not rely on manual installation. The vendor must have a mechanism to configure the extension via automation for anonymized browsing as well bridging to “The Onion Router” (TOR) network and integrating with the investigation platform to stored captured insights.

2.1.1 The software interface shall be a cloud-based web live platform to analyze in real-time endless web sources by keywords, locations, users and groups, from anywhere in the world, with single clicks.

2.1.2 The software interface shall utilize DHS owned and managed Application Programing Interface (API) for access to social media sites using direct content access.

2.1.3 The software interface shall provide direct translation capability for multiple foreign languages to include but not limited to Arabic, Spanish, Russian and French.

2.1.4 The software interface shall utilize algorithms that automatically generate intelligence insights based on user directed targeted collection to provide real-time translation of live web content directly on the user interface and not through a third party API or access.

2.1.5 The software interface shall utilize algorithms and AI capability to identify social circles and connections in real time, with live web connections accessible through the interface to content retrieved via the algorithms or AI which can be further manipulated by the end user independent of the vendor

2.1.6 The software interface shall provide the ability to perform audit functions of related to the users online activities.

2.1.7 The software interface shall provide the capability to integrate avatar management of accounts fully within the DHS managed attribution system.

2.1.8 The software interface shall enable multiple users to connect concurrently and to share their critical information. It shall be implemented as a subscription SaaS model over cloud base service.

2.1.9 The software interface shall assist the DHS with reducing the collection time and improve the capability to access social media applications at the request of DHS without restrictions or third party API.

2.1.10 The software interface shall provide Artificial Intelligence (AI) technology that extracts targeted intelligence from user-directed terms meeting the requirement for unique user-tailored collection on web content on the Deep, Dark and Surface web.

2.1.11 The software interface shall provide automated tips and leads DHS may have missed by collecting manually stored user-defined key word searches which can be updated, and controlled and maintained at the user level.

2.1.12 The software interface shall be able to add new platforms at the request of DHS without additional cost.

2.1.13 The software interface shall enable locating web connections of deleted material, to include associations of users not visible directly on accounts.

2.1.14 The software interface shall have algorithms used to identify linked content of users and known or suspected associations to the target.

2.1.15 The software interface shall serve as a data aggregator for keyword searches on all Social Media (not limited to a specific service) platforms on surface, dark, and deep websites.

2.1.16 The software interface shall send immediate notifications to inquiries.

2.1.17 The software interface shall capture the metadata from deleted or suspended accounts.

2.1.18 The software interface shall have a built-in geolocation feature without additional cost for use of the feature.

2.1.19 The software interface shall provide Graph analysis and cross Analysis.

2.1.20 The software interface shall have a function to capture large video, images, or numerous screenshots.

2.1.21 The software interface shall have a near-real-time response with live web content when returning results for keywords, hashtags, etc.

2.1.22 The software interface shall have a feature to filter results by specific time or date and the ability to search historical information.

2.1.23 The software interface must have the capability to conduct deep target identification via keyword search with social link analysis for both direct entities and associates to generate a risk assessment indication based on customized user driven dictionaries and severity levels.

2.1.24 The software interface must have the capability to provide continuous situational awareness- of specific keyword driven items – hashtags, specific accounts, groups, pages, and websites.

2.1.25 The software interface must have fully integrated deep analysis capabilities on accounts, posts, hashtags, locations and generate automatically entities and perform SNA for topic, persons, transactions and visualize present relevant data over map for location data.

2.1.26 The software interface must have the capability to conduct block chain analysis for Bitcoin wallet address transactional direction and amounts.

2.1.27 The software interface must have platform provider independency with the ability to search content independently without third party API.

2.1.28 The software interface must have the ability to integrate user content across all assigned users within the unit to ensure investigate leads and search criteria are shared within the same platform, to include but not limited to phone (International identification numbers must should be supported), email addresses, names, locations, social media handles, and URLs.

2.1.29 The software interface must have fully integrated multi-layer deep web investigation capability with continuous keyword specific web searches that are managed, updated and maintained at the user level with the ability to change without third party intervention and with unlimited frequency.

2.1 Program Management

2.1.1 The vendor shall designate a POC for any technical issues or problems

2.1.2 The vendor shall provide program management and help desk support 24/7 365 days.

2.1.3 The vendor shall provide 24/7 technical support for staff if needed.

2.1.4 The vendor shall have a method to load the configuration options (proxy, ports, etc.) via config file.

2.1.5 The vendor shall provide DHS the capability to create and assign user names and temporary passwords to users.

2.1.6 The vendor shall provide on-boarding and refresher training for users.

2.2 Standard Warranty

2.2.1 The vendor shall provide one year standard warranty for its tool based on the industry standards and an additional warranty period for each option year.

2.3 Maintenance

2.3.1 The vendor shall provide monthly maintenance for the software to include any updates to the operating system and patches needed for security.

2.3.2 The vendor shall provide recommendations, software updates and assist CETC with software related questions.

2.3.3 The vendor shall provide a routine maintenance tasks as some bug discovered by some user or it may be a large event in itself based on maintenance size or nature.

2.3.4 Corrective Maintenance - This includes modifications and updates done in order to correct or fix problems, which are either discovered by user or concluded by user error reports.

2.3.5 Adaptive Maintenance - This includes modifications and updates applied to keep the software product up-to date and tuned to the everchanging world of technology and business environment.

2.3.6 Perfective Maintenance - This includes modifications and updates done in order to keep the software usable over long period of time. It includes new features, new user requirements for refining the software and improve its reliability and performance.

2.3.7 Preventive Maintenance - This includes modifications and updates to prevent future problems of the software, which are not significant at this moment but may cause serious issues in the future.

2.4 Major modifications

2.4.1 Given the evolving nature of open source collection, new platforms and collections functions are constantly being developed. CETC will need to work closely with the software company to identify any upgrade or modifications that may be a need to the software in order to stay current on collection operations.

3.0 CONTRACT MANAGEMENT

The Contractor shall prepare and deliver monthly progress reports to the Contracting Officer and the Contracting Officer’s Representative no later than the 5th working day of the month. The progress report shall cover the previous month to include the following information:

• A summary of the work performed, including an explanation of changes to the work planned in the previous month

• Key issues or problems which may affect performance or schedule, along with the proposed resolution of those issues

• Financial status report reflecting contract expenditure costs for the reporting period and the cumulative total contract cost to date

The Contractor shall meet with the Contracting Officer’s Representative on a monthly basis to present deliverables, discuss progress, exchange information, and resolve emerging problems and issues such as cost and schedule variances.

The Contractor shall submit a meeting report recording the key discussions, decisions, and subsequent action items no later than five working days after the meeting.

The Contractor shall submit one electronic copy of each program management progress report and progress monthly summary to the Contracting Officer’s Representative. As requested by the Contracting Officer or the Contracting Officer’s Representative, the Contractor shall provide one hard copy of any of the deliverables listed above The Contracting Officer Representative may identify in writing other federal individuals in the Office of Intelligence and Analysis (I&A) that can directly receive the deliverable. The Contractor shall submit one electronic copy of each deliverable via e mail unless otherwise directed by the Contracting Officer, Contracting Officer’s Representative, or other federal I&A individuals assigned by the Contracting Officer’s Representative.

3.1 QUALIFIED PERSONNEL

The Contractor shall provide qualified personnel to perform all requirements specified in this SOW. It is the responsibility of the Contractor to propose immediately qualified contractor personnel to perform all requirements specified in this SOW, including any pre-cleared personnel identified as requiring security clearances to effectively provide the necessary services.

3.3 PROJECT MANAGER (non-billable)

The Contractor shall provide a Project Manager who shall be responsible for all Contractor work performed under this SOW. The Project Manager shall be a single point of contact for the Contracting Officer and the COR. The name of the Project Manager, and the name(s) of any alternate(s) who shall act for the Contractor in the absence of the Project Manager, shall be provided to the Government as part of the Post Award Conference. During any absence of the Project Manager, only one alternate shall have full authority to act for the Contractor on all matters relating to work performed under this contract. The Project Manager and all designated alternates shall be able to read, write, speak and understand English.

3.3.1 The Project Manager shall be available to the COR via telephone between the hours of 0800 and 1600 EST, Monday through Friday, and shall respond to a request for discussion or resolution of technical problems within 4 hours of notification.

4.0 OTHER APPLICABLE CONDITIONS

4.1 SECURITY

The maximum level of classification is Unclassified//FOUO. The majority of necessary information to support the required analysis will be commercially or publically available “open source” information. Contractor access to unclassified, but Security Sensitive Information may be required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination.

4.2 PERIOD OF PERFORMANCE

The contract period of performance shall be for one (1), 12-month Base Period followed by four (4), 12-month Option Periods, as follows;

Base Period 12 Months from Date of Award Option Period One 12 Months following Base Period Option Period Two 12 Months following Option Period One Option Period Three 12 Months following Option Period Two Option Period Four 12 Months following Option Period Three

4.3 PLACE OF PERFORMANCE

The primary place of performance will be the Contractor’s facilities.

4.4 TRAVEL

Travel is not required.

4.5 POST AWARD CONFERENCE

The Contractor shall attend a Post-Award Conference with the Contracting Officer and the Contracting Officer’s Representative (COR) no later than ten (10) business days after the date of award. The purpose of the Post-Award Conference, which will be chaired by the Contracting Office is to discuss contracting requirements. The Post-Award Conference will be held at DHS Nebraska Avenue Complex at 3801 Nebraska Avenue NW, Washington DC, St. Elizabeth’s Campus, or via teleconference.

4.6 KICK-OFF MEETING

The Contractor shall attend a Kick-Off Meeting with the COR no later than ten (10) business days after the date of award or by the date of the Kick-Off meeting, whichever is sooner. The purpose of the Kick-Off meeting, which will be chaired by the COR, is to discuss technical objectives of this contract. The Kick-Off meeting will be held at one of DHS’s facilities in the Washington, D.C., metropolitan area or via teleconference.

4.7 PROJECT PLAN

The Contractor shall provide a draft Project Plan at the Post Award Conference for Government review and comment. The Contractor shall provide a final Project Plan to the COR not later than 30 calendar days after the Post Award Conference.

4.8 PROGRESS REPORTS

The Project Manager shall provide a monthly progress report to the Contracting Officer and COR via electronic mail. This report shall include a summary of all Contractor work performed, including a breakdown tasks performed, an assessment of technical progress, schedule status, and any Contractor concerns or recommendations for the previous reporting period.

4.9 PROGRESS MEETINGS

The Project Manager shall be available to meet with the COR upon request to present deliverables, discuss progress, exchange information and resolve emergent technical problems and issues.

These meetings shall take place at the DHS Nebraska Avenue Complex, St. Elizabeth’s Campus, or via teleconference, at the discretion of the COR.

4.10 PROTECTION OF INFORMATION

Contractor access to information protected under the Privacy Act is required under this SOW.

Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with the law and Government policy and regulation.

Contractor access to proprietary information is required under this SOW. Contractor employees shall safeguard this information against unauthorized disclosure or dissemination in accordance with DHS MD 11042.1, Safeguarding Sensitive But Unclassified (For Official Use Only) Information. The Contractor shall ensure that all Contractor personnel having access to business or procurement sensitive information sign a non-disclosure agreement (DHS Form 11000-6).

4.11 SECTION 508 COMPLIANCE

Pursuant to Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) as amended by P.L.

105-220 under Title IV (Rehabilitation Act Amendments of 1998) all Electronic and Information Technology (EIT) developed, procured, maintained and/or used under this contract shall be in compliance with the “Electronic and Information Technology Accessibility Standards” set forth by the Architectural and Transportation Barriers Compliance Board (also referred to as the “Access Board”) in 36 CFR Part 1194. The complete text of Section 508 Standards can be accessed at http://www.access-board.gov/ or at http://www.section508.gov.

5.0 GOVERNMENT FURNISHED RESOURCES

N/A

6.0 CONTRACTOR FURNISHED PROPERTY

The Contractor shall furnish all facilities, materials, equipment and services necessary to fulfill the requirements of this contract.

http://www.access-board.gov/ http://www.section508.gov/

7.0 GOVERNMENT ACCEPTANCE PERIOD

The COR will review deliverables prior to acceptance and provide the contractor with an e-mail that provides documented reasons for non-acceptance. If the deliverable is acceptable, the COR will send an e-mail to the Contractor notifying it that the deliverable has been accepted.

7.1 The COR will have the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained in the Contractor’s accepted proposal.

In the event of a rejected deliverable, the Contractor will be notified in writing by the COR of the specific reasons for rejection. The Contractor may have an opportunity to correct the rejected deliverable and return it per delivery instructions.

7.2 The COR will have 5 business days to review deliverables and make comments. The Contractor shall have 3 business days to make corrections and redeliver.

7.3 All other review times and schedules for deliverables shall be agreed upon by the parties based on the final approved Project Plan. The Contractor shall be responsible for timely delivery to Government personnel in the agreed upon review chain, at each stage of the review. The Contractor shall work with personnel reviewing the deliverables to assure that the established schedule is maintained.

8.0 DELIVERABLES

The Contractor shall consider items in BOLD as having mandatory due dates. Items in italics are deliverables or events that must be reviewed and/or approved by the COR prior to proceeding to next deliverable or event in this SOW.

ITEM SOW

REFERENCE DELIVERABLE / EVENT DUE BY DISTRIBUTION

1 4.5 Post Award Conference 10 Business Days after Award

N/A

2 4.6 Kick Off Meeting 10 Business Days after Award N/A

3 4.7 Project Plan 30 calendar days after

Post Award Conference

COR, Contracting

Officer

4 4.8 Progress Reports Monthly; NLT 5th COR, Contracting Officer

5 2.0 Access to Technology Platform/Tools

Upon Award NLT 15 days after Award COR, Tech POC