Exhibit_J-1_Section_C_SOW.pdf

C-1

Exhibit J-1

STATEMENT OF WORK

FOR

T2S2 COLLECTION SYSTEMS

AND

ANNUAL FLEET SUPPORT, SERVICE, AND MAINTENANCE

TABLE OF CONTENTS

SUBSECTION C.A GENERAL

Subsection C.A.1 Background

Subsection C.A.2 Definition of T2S2 Collection Systems

Subsection C.A.3 Reference Documents

Subsection C.A.4 Scope of Work

Subsection C.A.5 Government Right to System Refreshment, Upgrade, and Expansion

SUBSECTION C.B GENERAL SYSTEM REQUIREMENTS, DESIGN,

CONFIGURATION, AND SCALABILITY

Subsection C.B.1 System Overview

Subsection C.B.2 System Security & Encryption

Subsection C.B.3 Database

Subsection C.B.4 Scalability & Configuration

Subsection C.B.5 Operating System

Subsection C.B.6 Third Party Software

Subsection C.B.7 Hardware Requirements

SUBSECTION C.C COLLECTION CAPABILITIES AND PERFORMANCE

Subsection C.C.1 Collection Capabilities and Types of Target Transmissions

Subsection C.C.2 Interface Hardware

Subsection C.C.3 Emerging Technologies

SUBSECTION C.D CRITICAL PRIMARY FUNCTIONS

Subsection C.D.1 Live Monitoring

Subsection C.D.2 Archiving

Subsection C.D.3 Minimization

Subsection C.D.4 Playback

SUBSECTION C.E SECONDARY FUNCTIONS

Subsection C.E.1 Analytical Tools

Subsection C.E.2 Reports

Subsection C.E.3 System Administration

Subsection C.E.4 Audit Capabilities

Subsection C.E.5 GPS/Cellular Telephone Tower Site Mapping

Subsection C.E.6 Electronic Storage Management

C-2

Subsection C.E.7 Disaster Recovery Platform (DRP)

Subsection C.E.8 System Core and Network Interoperability and Standardization Feature

(SCNISF)

SUBSECTION C.F NON-AUDITORY AND IP COMMUNICATIONS

Subsection C.F.1 General (Including Post-Collection Minimization)

Subsection C.F.2 SMS/Text Messaging

Subsection C.F.3 MMS/Photos/Video File Transmission

Subsection C.F.4 Facsimile (Fax) Transmissions

Subsection C.F.5 Post Cut through Dialed Digits (PCTDD)

Subsection C.F.6 Data and Internet Protocol (IP) Collection

SUBSECTION C.G ADDITIONAL EQUIPMENT

Subsection C.G.1 Transportable Systems

Subsection C.G.2 Mediation Devices

C.G.2.01 Mediation - General

C.G.2.02 Definition of a Lawful Interception Mediation System or

Management Server (LIMS)

C.G.2.03 LIMS Functional Requirements

C.G.2.04 LIMS Hardware Requirements

SUBSECTION C.H MISCELLANEOUS

Subsection C.H.1 Consensual Interceptions

Subsection C.H.2 Confidentiality/Security Issues

Subsection C.H.3 Procedures for Post-Award Actions

SUBSECTION C.I JUDICIAL PROCEDURE PRESENTATIONS OF ORIGINAL

EVIDENCE AND JUDICIAL CHALLENGES

SUBSECTION C.J WARRANTY AND SUPPORT

Subsection C.J.1 Warranty and Support Overview

Subsection C.J.2 Personnel Services

Subsection C.J.3 Training

Subsection C.J.4 Annual Fleet Service, Support and Maintenance CLIN Overview

Subsection C.J.5 Help Desk/Telephone Support

Subsection C.J.6 Preventive Maintenance

C.J.6.01 Preventive Maintenance – General

C.J.6.02 Locally Provided Preventive Maintenance (LPPM)

C.J.6.03 Contractor Provided Preventive Maintenance (CPPM)

Subsection C.J.7 Corrective Maintenance

C.J.7.01 Corrective Maintenance – General

C.J.7.02 Locally Resolved Corrective Maintenance (LRCM)

C.J.7.03 Emergency Call-Out Corrective Maintenance (ECOCM)

C.J.7.04 Contractor Facility Corrective Maintenance (CFCM)

Subsection C.J.8 Software Support

Subsection C.J.9 Hardware Support

C-3

Subsection C.J.10 Upgrade/Software/Patch Release or Hardware Configuration Change

Procedures

Subsection C.J.11 Program Management

C.J.11.01 Contractor Program Manager

C.J.11.02 Configuration/Baseline/Version Management

C.J.11.03 Regular Meetings

Subsection C.J.12 Reporting Requirements

C.J.12.01 Reporting Requirements – General

C.J.12.02 Program Reporting

C.J.12.03 Manuals/Guides

Subsection C.J.13 Miscellaneous Service, Support, and Maintenance Issues

C.J.13.01 System Performance Development Standards

C.J.13.02 Transportable Systems Support Issues

SUBSECTION C.K FOREIGN APPLICABILITY

Subsection C.K.1 Foreign Applicability – General

Subsection C.K.2 Foreign System Issues

Subsection C.K.3 Foreign Support Issues

GLOSSARY FOR SECTION C – STATEMENT OF WORK

SUBSECTION C.A GENERAL

SUBSECTION C.A.1 BACKGROUND

A. The mission of the Drug Enforcement Administration is to enforce the controlled substances laws and regulations of the United States and to bring to the criminal and civil justice systems those organizations and/or individuals involved in the growing, manufacture, or distribution of controlled substances appearing in or destined for illicit traffic in the United States and its territories.

B. This requirement is for the acquisition of T2S2 Collection Systems (also referred to throughout this Statement of Work as “systems,” or “the system”) and an associated

Annual Fleet Service, Support and Maintenance CLIN (AFSSMC), as well as associated supportive and interrelated equipment.

C. The equipment acquired will be used for the court ordered, or otherwise legally authorized, interception of electronic communications content. The T2S2 Collection

Systems will be tasked with collecting and producing evidence-quality recordings and logs of activity of intercepted transmissions and/or data made or received by telephones, mobile telephones, computers, other handheld electronic devices, VoIP/packet data based audio and other forms of IP communications, SMS/Text messaging, fax machines, etc., as utilized by targets of criminal investigations. (Maintaining current collection requirements often requires extensive software engineering in the case of digital communications.)

C-4

D. This Statement of Work further defines the responsibilities, scope, services to be rendered, and other applicable parameters of a comprehensive engineering support, development, and maintenance program (or otherwise referred to as Annual Fleet

Service, Support and Maintenance), providing a wide range of services, which will cover the DEA’s anticipated routine and customary needs for its entire T2S2 Collection Fleet as provided by any particular contractor. Its purpose is to ensure a high level of T2S2

Collection System availability at all DEA sites utilizing the contractor’s product.

SUBSECTION C.A.2 DEFINITION OF T2S2 COLLECTION SYSTEMS

A. A T2S2 (Transcription and Translation Support System) Collection System is a computer system operating over a network and utilized by law enforcement agencies to perform court-ordered, or otherwise legally authorized, interception of content transmitted via electronic communications, which provide the “back-end” monitoring platform functionality. The electronic communications content collected generally falls into one of three categories: Auditory Communications (such as the audio from telephone conversations), Non-Auditory Communications (such as text messaging or the content of faxed transmissions, etc.), and Internet Protocol (IP) Communications (such as e-mail or internet browsing, etc.). T2S2 Collection Systems are also referred to as T2S2, T2S2

Systems, Title III Collection Systems (referring to 18 USC Section 2518 (3), the federal law allowing federal agencies to conduct such interceptions), “Wiretap” Systems, Audio

Communications Collection Equipment, and Communications Content Collection

Equipment.

B. At a minimum, T2S2 Collection Systems provide the following four Critical Primary

Functions:

1. The ability to intercept and perform live monitoring (i.e., listening to and recording of live telephone sessions, etc.);

2. The ability to properly minimize, or where applicable, post-minimize, an intercepted communication (i.e., discontinue monitoring and collection when communication is irrelevant to criminal activities or when determined to consist of privileged communications);

3. The ability to archive all intercepted communications to media suitable for evidence and retrieve that evidence for processing, sealing, or presentation to the court; and

4. The ability to call up on demand, transcribe, translate, and review within a reasonable time frame playback of intercepted communication.

C. In addition to the minimum functions listed above, T2S2 Collection Systems also provide numerous advanced analytical and automated features to enhance investigative efforts as specified in other sections of this Statement of Work.

D. Also, T2S2 Collection Systems demonstrate compliance with the statutes, law enforcement policies and procedures, and judicial requirements governing judicially authorized interceptions established in the particular jurisdictions in which the system is utilized. Over time, changes in these governing statutes, policies, procedures, and

C-5 requirements can mandate changes in the functions and features of the T2S2 Collection

Systems, with which the Contractor shall update and adapt their product within a reasonable time frame dependent on the specific issue addressed.

E. Finally, T2S2 Collection Systems provide all the above elements in a manner that is secure, verifiable, and withstands judicial review.

SUBSECTION C.A.3 REFERENCE DOCUMENTS

A. All T2S2 Collection Systems and software shall comply with all applicable system security policies, guidelines and procedures as directed by Department of Justice Order

2640.2(series), Information Technology Security Standards. All T2S2 Collection Systems shall be compatible with all hardware/software solutions developed by industry to comply with the Communications Assistance to Law Enforcement Act (CALEA), including, but not limited to landline telephone communications, J-STD-025-A, J-STD-

025-B, Packet Cable 1.5/2.0, (iDEN) Digital Dispatch, Q-Chat, ATIS T1.IAS, ANSI

T1.724, and ANSI T1.678 and any other applicable ANSI standards. All T2S2 Collection

Systems shall comply with the CALEA Broadband Coverage Order issued by the FCC on

September 23, 2005, or superseding orders. These documents apply to capabilities needed by law enforcement and messaging formats by which information will be delivered. References in this solicitation to Department of Justice Order 2640.2(series), indicates the approved contemporaneous version of this document which is currently

Department of Justice Order 2640.2F, Information Technology Security, dated November

26, 2008 as of the writing of this solicitation.

B. All T2S2 Collection System wiring shall comply with TIA/EIA-568 specifications.

SUBSECTION C.A.4 SCOPE OF WORK

A. The Contractor shall provide the Drug Enforcement Administration with fully installed

T2S2 Collection Systems as defined and specified in this Statement of Work, including, but not limited to, supporting hardware, software, certain additional equipment and other accessories, warranties, associated system fleet support, service, and maintenance, training, upgrades, enhancements, periodic hardware and software refreshments, and engineering services (laboratory development and onsite support for all installations, upgrades, or equipment failures) throughout the life of the agreement.

B. The Contractor shall keep pace with technological advances and changes in standards in the telecommunications industry (“state of the art”) throughout the life of the agreement.

The Contractor shall continue development of the functions and features of their product throughout the life of the agreement so as to ensure their product is in compliance with the statutes, law enforcement policies and procedures, and judicial requirements governing judicially authorized interceptions established in the particular jurisdictions in which the system is utilized by the government, and provide delivery of such required product changes within reasonable timeframes.

C-6

C. The Contractor shall ensure their product is compatible and able to fully function over the government’s Wide Area Network (WAN) and shall develop and implement any customized changes to their product in order to continually achieve that end.

D. The Contractor shall provide services to the government in the areas of installation, removal and troubleshooting for any or all of the equipment and software provided or supported under the agreement.

E. T2S2 Collection Systems represent major financial investments on the part of the government which are utilized to perform crucial law enforcement functions.

Furthermore, the environment in which these systems function is dynamic, constantly evolving, and subject to changes in technological advances, standards of the telecommunications industry, and legal requirements. Thus, it might be in the government’s interest to purchase an Annual Fleet Service, Support and Maintenance

CLIN (AFSSMC) from the Contractor providing for the following fleet services:

1. Preventive maintenance.

2. Corrective maintenance and troubleshooting by Contractor experts.

3. User/Helpline Support.

4. Training.

5. Upgrades and enhancements.

6. Development of software and hardware based options.

7. Engineering response to equipment failures.

8. General engineering services.

9. Adjustment of the existing system to changes in technology, industry standards, or legal requirements.

10. Periodic Program Reporting to the Contracting Officer and the COR.

11. Program management.

(The Contractor is directed to take note of the Annual Fleet Service, Support and Maintenance

CLIN specified in Section B.)

F. Unless otherwise specified, all services and responsibilities provided for and to the government by the Contractor under this Statement of Work shall be included in the price of the agreement. This shall include all import/export fees, shipping and transport costs associated with the system and its sub-components prior to final acceptance of any system or sub-component by the government, as well as any import/export fees, shipping and transport costs assigned to the Contractor under the terms of the Annual Fleet

Service, Support and Maintenance CLIN (AFSSMC).

G. The first year of the Annual Fleet Service, Support and Maintenance CLIN (AFSSMC) for new/additional software licenses and/or new/additional hardware in an initial purchase or subsequently added to an existing system shall be provided to the government by the Contractor without additional charge (beyond costs incorporated into

C-7 the price for the software licenses and hardware themselves) commencing immediately after satisfactory completion of installation and acceptance by the government.

H. The contractor shall provide to the government the option to renew the Annual Fleet

Service, Support and Maintenance CLIN (AFSSMC) each following subsequent year throughout the life of the agreement according to pricing schedules mutually agreed upon between the contractor and the government under this agreement.

I. The Contractor shall meet the Acceptable Level of Compliance with the Statement of

Work upon installation of any of their systems or component hardware or software. The

Acceptable Level of Compliance is defined as the conglomeration of those requirement elements, identified through application of the word “shall,” which must immediately be available to the government from the Contractor upon delivery of equipment or service.

J. All contractor personnel utilized onsite at government facilities to perform training, installation, support and maintenance, or any other onsite function, shall either be (1)

U.S. citizens capable of obtaining appropriate security clearances, or (2) foreign nationals who possess appropriate, current NATO security clearances reciprocated by the U.S.

Department of Defense. The Contractor shall be responsible for providing all requested security clearance information to the government in a timely manner upon request by the

COR. The Contractor shall be responsible for ensuring availability of sufficient personnel necessary to the fulfillment of all the responsibilities and obligations of the

Contractor under this agreement, even in the event particular contractor personnel fail to obtain their required security clearances.

K. The Contractor shall be responsible for the development of all software and/or hardware solutions necessary to the fulfillment of its obligations under this agreement. This responsibility shall extend to the generation, provisioning, and collection of test target samples, or other interactions with any particular telecommunication and/or Internet

Protocol format or service provider necessary to the Contractor in the development of functionality for their system. Under the terms of this agreement, the government is not responsible for furnishing any test data, content or other samples, equipment, expert advice or consultation from the government’s personnel, or any tangible aid in any development of the Contractor’s product other than that specifically provided for under this SOW, although the government may choose to do so solely at its discretion if it so determines that to do so is in the government’s interest. Denial of any such requests on the part of the government does not in any way change, remove, or lessen any of the

Contractor’s responsibilities or obligations under this agreement.

L. The Contractor shall be responsible for ensuring the full functionality and operability of their products prior to delivery, or where onsite Contractor installation is applicable, before departure of their personnel upon the completion of any installation, upgrade, expansion or refreshment.

C-8

SUBSECTION C.A.5 GOVERNMENT RIGHT TO SYSTEM REFRESHMENT,

UPGRADE, AND EXPANSION

A. New replacements are the complete and total replacement of all hardware and software components, to include proprietary Contractor software licensing, of a system previously installed at a site. New installations are the placement of a system where none has previously been installed. New replacements and new installations are not included and are separate procurements from the refreshments, upgrades, and expansions described below.

B. The Contractor shall acknowledge and accept on all applicable occasions the government’s unilateral right when in the government’s interest to place delivery orders with another contractor currently imbedded at a particular government site without competition when performing hardware and software refreshments of components of existing systems already installed at that site. Refreshments are the replacement of a hardware or software component or group of such components with new components when either the existing components have reached or extended beyond their normal service life, or the existing components have otherwise in some way reached a state of obsolescence or antiquation, although the existing proprietary Contractor software licensing will remain in place on the system.

C. The Contractor shall acknowledge and accept on all applicable occasions the with another contractor currently imbedded at a particular government site without competition when the government seeks to upgrade the hardware or software capabilities of any and all components of existing systems already installed at that site. Upgrades are hardware or software based changes which result in improvements in features, functions, or performance to the benefit of the system users or the government, although the existing proprietary Contractor software licensing will remain in place on the system.

D. The Contractor shall acknowledge and accept on all applicable occasions the with another contractor currently imbedded at a particular government site without competition when the government seeks the expansion of any and all components of existing systems already installed at that site. Expansions are the increasing of the number of hardware or software components in a particular system. When applicable, expansion includes the increasing of system functions, equipment and/or connectivity to a previously unconnected or nonexistent remote site under a particular core site, although the existing proprietary Contractor software licensing will remain in place on the system.

E. The Contractor shall acknowledge and accept on all applicable occasions the government’s unilateral right to exercise the above specified rights in combination.

SUBSECTION C.B GENERAL SYSTEM REQUIREMENTS, DESIGN,

CONFIGURATION, AND SCALABILITY

C-9

SUBSECTION C.B.1 SYSTEM OVERVIEW

A. Systems shall meet the definition of and the functional requirements of a T2S2 Collection

System as set forth in Subsection C.A.2 Definition of T2S2 Collection Systems. The

Contractor shall equip their systems to meet the listed specifications and be responsible for their systems fully functioning within the provided parameters defined within this

SOW or as specified in any particular Delivery Order.

B. All physical components and materials shall be comprised of new, previously unused equipment with no recycled, refurbished, or otherwise re-used equipment being resident on a system or sub-component at the time of delivery by the Contractor to the government.

C. Systems shall be designed to continuously function without interruption 24 hours a day, 365 days a year. Systems shall be constructed flexibly, with enough reliability and redundancy to remain in a functional mode at all times over the life of the agreement or the warranty period, whichever period is longer, despite the failure of a particular sub-component. In the event of unusual or special circumstances resulting in an outage, total accumulated system outages per year shall not exceed 0.6%, or 52.56 hours per year per major core, calculated consecutively in real time without interruption by or with consideration for “non-business hours” once any particular outage commences.

D. Systems shall function with high levels of confidentiality, system integrity, and availability.

E. For each purchase made under this agreement, the Contractor shall provide the government with clearly defined and specific operating guidelines and requirements which comprehensively address all infrastructure issues impacting the normal functioning of the system and its various subcomponents. These operating guidelines and requirements shall include but not be limited to:

1) Network bandwidth requirements.

2) Electrical power requirements.

3) Environmental operating ranges for temperature and humidity.

4) Physical space requirements.

5) System component BTU generation and its associated cooling requirements.

F. Systems shall be able to function over the government’s Wide-Area Network (WAN).

G. Systems shall be configured around a centralized core at which all evidence shall be collected, stored and produced. All data, content, and work product collected or produced throughout the network shall ultimately be stored and available at the centralized core.

C-10

H. Main core sites for each system purchased shall reside at a designated government field site. The main computer core shall be configured and organized in wheeled computer server rack(s) so as to promote efficient use of floor space.

I. Systems shall be capable of connecting, exchanging information and communicating

(passing of data/audio) with other core systems from the same contractor upon establishment of connectivity by the government.

J. Systems shall be designed to maximize bandwidth efficiency between the centralized core and remote field sites through the use of remote caching. Remote servers shall be used at larger remote field sites (as defined by the number of audio workstations to be a remote site hosting four or more workstations) to achieve maximum efficiency. All implementation of remote caching shall include the following features:

1. Local file copies shall be maintained at the remote site for each target initially monitored at that remote site.

2. Local file copies should be maintained at the remote site for any files comprising content or work product subsequently reviewed at that remote site even if the target was not initially monitored at that remote site.

3. After initial session creation (or subsequent duplication due to local review), the local file copies shall provide primary access to the information contained therein for any system users accessing the system at the remote site. Accessing of file information over the WAN shall provide secondary access to the information when information is not available in the local file copies for any system users accessing the system at the remote site.

4. File copies maintained on the remote caching device shall include all files which comprise the Evidence Copy media, including in particular the content of the target communications, and should include all other files which comprise the Working/Duplicate Copy media (see, Archiving

Subsection, below).

5. The remotely cached local file copies which are normally subject to periodic change or update (as, for example, in the case of synopses or transcriptions and translations) shall be updated upon user changes so as to maintain concurrence with the primary files located on the core.

6. Users at the remote site shall have access to the local file copies from any workstation located at the remote site at any time.

7. Remote servers shall act as the local domain controller so as to facilitate quicker log on processing for local users and to reduce bandwidth utilization during log on and off processing.

8. Remote servers and other caching equipment shall be provided adequate housing appropriate to the caching method utilized at the particular remote site, for example, a server rack in the case of a server.

K. Live monitoring, minimization, playback, transcription, translation, report generation, cellsite mapping and case analysis shall be performed at network audio workstations, a portion of which may be located in different cities or work sites of considerable distance

C-11 from the centralized core. All functionality of each of these separate capabilities shall be fully executable for any target from anywhere on the network at any time, independent of where on the network monitoring was conducted for a particular target up until that time.

L. All systems’ characteristics (Operating System, Intercept Software, Word Processing

Software, etc.) shall fully comply with all Department of Justice regulations regarding

Certification and Accreditation (DOJ Order 2640.2(series), Telecommunications and

Automated Information Systems Security). The Contractor shall be responsible at all times for this compliance with the most current regulation at no additional cost to the

M. The Contractor shall provide the Government with T2S2 Collection Systems which are capable of monitoring telephone activity and packet activity information in accordance with Title III requirements, to include but not be limited to both traditional landline and wireless collection of telephone communications.

N. The T2S2 Collection Systems shall collect, decode, and reassemble audio and other transmissions to include voice conversations, text messaging/SMS, MMS/video, MMS/text messaging, MMS document, photo, and other files, IP data files, modem, facsimile and signaling information.

O. The T2S2 Collection Systems shall provide automated, permanent recording of any monitored intercepted audio or other transmissions consisting of content.

P. The T2S2 Collection Systems shall be capable of accepting both analog and digital inputs from the telephone, VoIP, or Internet service providers.

Q. The T2S2 Collection Systems shall be capable of handling Communication Identification

Information (CII) and session content in such a way that:

1) where the communications provider is able to separate CII and session content and the court-ordered interception only provides for collection of CII, the monitor shall only be provided with CII;

2) where the communications provider discloses CII and/or data or audio content beyond that for which the court-ordered interception provides, but the communications provider is otherwise able to separate CII and session content, the monitor shall only be provided with information conforming to the breadth of information permissibly collected under the court order; and

3) where the communications provider is unable to separate CII and session content, the

T2S2 Systems shall provide for the minimization of information impermissible for collection under the court order.

R. The T2S2 Systems shall be capable of collecting, decoding, analyzing, and otherwise handling any audio or non-audio transmissions capable of transmitting over a telephone, mobile telephone, or other mobile communications device. The systems shall provide to the government capability of collecting, decoding, analyzing, and otherwise handling standard protocols for audio or non-audio transmissions from a computing device.

C-12

S. The systems shall provide and demonstrate adequate redundancy and automated backup ability for each critical component towards a goal of preventing or minimizing down time due to failures. For example: the database shall have a minimum redundancy of RAID 5 with a hot spare for data and product drives and have an automatic backup done frequently with several restore points. Archiving shall be redundant with multiple controllers and media handlers. Audio and data shall reside in multiple, redundant locations before archiving and until purged from the system after completion of the investigation. Transcripts, reports, and other user data shall be automatically backed up with multiple recovery locations. The systems shall be equipped with critical redundant components such as redundant power backups, redundant power supplies, spare network servers, etc.

T. The systems shall recover from failures within 24 hours or a reasonable time period

(which could be less or more than 24 hours) as determined by the COR.

U. The systems shall be equipped with an appropriate number of UPSs which are sufficient to support the systems for a minimum period of 30 minutes.

V. All data shall be backed up frequently to an external storage device, such as a NAS, removable serial hard drives, etc.

W. The systems shall possess sufficient safeguards to protect collected data, audio, and work product from loss during cataclysmic events such as power outages.

X. The systems shall ensure that in the case of Title III audio interceptions, no user/monitor is capable of listening to (through either Live Monitoring mode or Playback mode) any interception or any portion of an interception which is not recorded and archived by the systems, or conversely, that no Title III audio interception or any portion of a Title III interception is recorded or archived by the systems if it was not live monitored by a user/monitor with the availability of full minimization functionality.

Y. The systems shall be electrically engineered according to the standards of the United

States National Electrical Code (NEC) (also known as National Fire Protection

Association (NFPA) 70, current edition as of this writing being the 2011 Edition, and all associated and related editions, for example NFPA 70E, Standard for Electrical Safety in the Workplace, etc.) and the current applicable standards set and adopted by the (United

States) National Electrical Manufacturers Association (NEMA). Core rack components shall receive power inputs of 120V 30AMP through NEMA L5-30p connectors. All other components shall receive power inputs of 120V 15AMP through NEMA 5-15p connectors.

SUBSECTION C.B.2 SYSTEM SECURITY & ENCRYPTION

C-13

A. The systems shall have sufficient features which serve to protect and preserve the integrity of the evidence and work product collected and prepared on the system.

B. The systems shall be equipped with sufficient security safeguards to limit access to the systems by legitimate or authorized users and to protect the systems and its evidence from attack by outside malicious entities.

C. All users of the systems regardless of role (i.e., monitors, case agents, intelligence analysts, supervisors, system administrators, etc.) shall only be able to access the network through a valid, unique user account and associated password that is set by the user to prevent any unauthorized access to the network. User accounts shall have a minimum password length configurable as dictated by the federal agency policy. The systems shall require the user to change passwords in intervals as dictated by the federal agency policy, without affecting the collection process. The systems shall comply with all Department of Justice regulations regarding Certification and Accreditation (DOJ Order 2640.2

(series), Information and Technology Security). The systems’ application software should not require a separate log-in from the operating system for a single user, i.e. the operating system should pass the user’s authorization through to the system application utilizing a single log-in.

D. The systems shall provide extensive selections for each User Account so as to precisely define the abilities, granted access, permissions, and allowable use of the systems by each system user. The systems shall by default refuse access or permissions to system areas, content, sub-systems, intelligence, and data for any user unless their account is granted the appropriate prerequisite permissions.

E. If encryption authorization codes, including proprietary encryption algorithms, are required to operate any function within the system, the Contractor shall make them open and accessible to government agency personnel, providing all codes and keys to the government agency.

F. The system shall implement the configuration of the security parameters to be applied to each server and workstation centrally from the core.

SUBSECTION C.B.3 DATABASE

A. The systems shall have a large, accessible, scalable database capable of storing not only the data and content collected from the interceptions conducted on it, but also digital information gathered from other sources in an investigation. The systems shall be equipped with a database, or series of databases, sufficiently robust to handle a minimum of 50 million records and expandable to handle a minimum of 100 million records. The database shall perform at least 200 transactions per second at 75% processor utilization.

The database’s end-to-end execution time shall ensure at least 90% of transactions respond within two seconds.

C-14

B. The systems should provide a means through an Application Programming Interface

(API) for querying, updating, and inserting data stored in the database by another application for functions such as data export, data import, and collection provisioning/configuration.

C. This database shall contain fields describing the archived original evidence and working copy media names.

D. This database shall be structured as to not be considered “original evidence.”

E. The systems shall possess the ability to import data into the database which was accumulated from other databases or sources. This importable data shall include, but not be limited to, existing subscriber databases, digital video and pictures taken in the course of investigations, audio collected from other sources, etc., in unprotected, generally accepted formats.

F. The system database shall come equipped with a Subscriber Database. The Subscriber

Database shall be utilized by the system to automatically populate the associated information into the appropriate session fields for purposes of report generation and other analysis. The Subscriber Database shall be utilized by the system to avoid the necessity of repetitive entry of redundant or duplicate information onto the system. The Subscriber

Database shall provide Import/Export linkage with common database formats.

G. The Subscriber Database shall be simple in construction, including the following named field types or similar field types:

Telephone number (should accommodate IP addresses or e-mail addresses if applicable)

Servicing Telephone Company (or Internet Service Provider if applicable)

Account Number

Subscriber Name

Assigned user

Billing Address Line 1

Billing Address Line 2

Billing City

Billing State

Billing Zip Code

Alternate Address Line 1

Alternate Address Line 2

Alternate City; Alternate State

Alternate Zip Code

Additional Telephone Numbers

Actual User 1

Actual User 2

Actual User 3

Type of communications device:

C-15 o Landline o VoIP o Fax machine o Pager o Cell phone o Computer o Other

Origin of Device:

o Mobile o Residential o Business o Public o IP Address o Other

H. The Subscriber Database shall allow for time sensitive multiple listing of telephone numbers, i.e. Information for Subscriber A who possessed telephone number from

01/03/2010 to 03/30/2010, information for Subscriber B who possessed the same telephone number from 04/15/2010 to 06/30/2010, and Subscriber C who possessed the same telephone number from 07/05/2010 to the present.

I. The following fields or like fields from the Subscriber Database shall appear at live monitor and playback: Telephone number and Subscriber Name.

J. The system database shall come equipped with a Session Database. The Session

Database shall include the following named field types or similar field types, populated automatically by the system or manually by the system users as appropriate for each field:

• Language spoken/used during the session.

• Session participants.

• Session number.

• Date of session.

• Start time of session.

• Dialed digits.

• Session connect time (based on off hook or ringing or CALEA).

• Session disconnect or end time.

• Session duration (or calculated by the system).

• Hook flash (time stamp and new sequential session number).

• Audio (time and condition when audio is turned on, off, or changed).

• Target number (expandable for new or different numbering plans).

• Session progress tones (Post-cut-through Dialed Digits).

• Caller ID information or calling number identification (CNI).

• Identify session direction as either “Incoming” or “Outgoing.”

• GPS or cell site location information.

• Classification of sessions as Pertinent, Non-Pertinent, or Privileged.

• CALEA Events.

C-16

• Monitor ID.

• Session Content.

K. The database should possess system administrator configurable fields for case or site specific information. The fields should be fully searchable and definable.

L. The internal database of the system should be structured so that the naming protocols and network pathways of content (or audio) files, work product files (such as transcriptions and translations), session data files, etc., follow a logic which increases the ease with which they can be located, and if necessary exported or copied, by the system administrator (i.e., G:\Casename\Target\Audio Files\Target Evidence Session

Number.wav). File names should be configurable, should consist of at least three elements formed from either database fields or system administrator defined fields, and should allow the elements of government agency case number (or DEA Case Number in the instance of DEA), the target (or line) number, and the session number. For example, file names for transcriptions should be configurable to be

DEACaseNumber_Target_SessionNumber.wpd or

DEACaseNumber_Line_SessionNumber.doc.

SUBSECTION C.B.4 SCALABILITY & CONFIGURATION

A. The systems shall be sufficiently robust and scalable to support up to a minimum of three hundred (300) target lines in an off-hook condition simultaneously.

B. The system shall be sufficiently robust and scalable to support up to a minimum of two hundred (200) workstations connected simultaneously with up to fifty (50) remote offices under a single centralized core.

SUBSECTION C.B.5 OPERATING SYSTEM

A. The T2S2 Collection System shall be built upon an underlying Commercial-off-the-Shelf

(COTS) operating system that is still supported by the manufacturer.

B. The Contractor shall assume full responsibility for the compatibility, functionality, performance, and updating of the operating system software incorporated by them into their system.

SUBSECTION C.B.6 THIRD PARTY SOFTWARE

A. The Contractor shall assume full responsibility for the compatibility, functionality, performance, and updating of any third party software incorporated by them into their system.

B. The systems shall be compatible with a wide variety of commercially available versions of anti-virus enterprise software (McAfee, Symantec, Kaspersky Labs, Trend Micro, etc.). The government will specify the anti-virus software to be utilized selectable on

C-17 each major core purchase. The Contractor shall throughout the life of the agreement accommodate upon a system the change of anti-virus software within 30 calendar days of receipt of notification by the government.

C. The Contractor shall provide the option to the government, selectable on each major core throughout the life of the agreement, of either (1) purchasing anti-virus software through the Contractor or (2) utilizing anti-virus software available to the government through the government’s existing enterprise licensing. When the government so chooses to utilize the government’s existing anti-virus enterprise licensing, the Contractor shall provide full engineering support of the installation and performance of the software upon the system.

D. The systems shall be compatible with a wide variety of commercially available versions of remote administration software (such as Net-Op Remote Control, or other remote administration software of similar or equal quality). The government will specify the remote administration software to be utilized selectable on each major core purchase.

The Contractor shall throughout the life of the agreement accommodate upon a system the change of remote administration software within 30 calendar days of receipt of notification by the government.

E. The Contractor shall provide the option to the government, selectable on each major core throughout the life of the agreement, of either (1) purchasing remote administration software through the Contractor or (2) utilizing remote administration software available to the government through the government’s existing enterprise licensing. When the government so chooses to utilize the government’s existing remote administration enterprise licensing, the Contractor shall provide full engineering support of the installation and performance of the software upon the system.

SUBSECTION C.B.7 HARDWARE REQUIREMENTS

A. All servers shall be current (as of the time of the issuance of the particular delivery order or award) enterprise-class servers manufactured either by Dell, Hewlett-Packard, IBM, NetApp, or other servers of similar, equal or higher quality, equipped with a minimum of twice the recommended RAM for the most RAM intensive software component on the system as recommended by the original software developer or as requested by the COR.

B. Individual workstations and/or laptop computers (utilized in transportable systems) shall be a current (as of the time of award) Business-class workstation manufactured either by

Dell, Hewlett-Packard, or other workstations of similar, equal or higher quality, equipped with a minimum of twice the recommended RAM for the most RAM intensive software component on the system as recommended by the original software developer, or a minimum of twice the recommended RAM for the operating system, or a minimum of 8

GB of RAM, whichever is the highest amount of RAM, or as otherwise requested by the government. The individual workstation shall consist of the following components: a

CPU, integrated dual flat screen display monitors, full standard keyboard with numeric pad, computer mouse, foot pedal control, stereo desktop speakers, stereo headphones, and workstation power surge protection and power backup providing a minimum backup

C-18 period of 20 minutes. For each workstation purchase, the Contractor should provide the government with an option to replace the standard keyboard with numeric pad for an ergonomic keyboard with numeric pad if requested for the particular purchase.

C. Network Printers shall be a current (as of the time of the issuance of the particular delivery order or award) high speed laser-jet Office-class printers manufactured by Dell, Hewlett-Packard, or other network printers of similar, equal or higher quality.

D. Display Monitors shall be 19” flat panel LCD monitors with VGA and DVI connections manufactured either by Dell, Sony, NEC, or other monitors of similar, equal or higher quality. For each Display Monitor purchase, the Contractor should provide the government with an option to replace the 19” Display Monitor for a larger screen if requested for the particular purchase.

E. Network Switches shall be 1000-baseT on all ports manufactured either by Dell, Cisco, Hewlett-Packard, or other network switches of similar, equal or higher quality. The connection between switches shall be at least 10,000-baseT. For each Network Switch purchase, the Contractor should provide the government with an option for higher speeds if requested for the particular purchase.

F. Throughout the life of the agreement, the Contractor shall adjust their hardware component offerings to comply with additional or changed hardware requirements for the preceding hardware categories within 30 days of receipt of notifications by the

G. The Contractor shall be responsible for ensuring that all hardware incorporated into their products performs sufficiently to provide for the full functionality and operability of their products.

SUBSECTION C.C COLLECTION CAPABILITIES AND PERFORMANCE

SUBSECTION C.C.1 COLLECTION CAPABILITIES AND TYPES OF TARGET

TRANSMISSIONS

A. The systems shall provide for reception of all forms of telephonic and/or electronic communication including, but not limited to, cellular/wireless/mobile telephones, other handheld electronic devices, computers, packet cable (including Packet Cable 1.5/2.0), VoIP, IP communications, SMS/Text messaging, fax machines, all CALEA mandated formats and standards, all variations of J-STD, (iDEN) Digital Dispatch, Q-Chat, ATIS T1.IAS, ANSI

T1.724, ANSI T1.678, all other applicable ANSI standards, CDMA, GSM and analog landline/voltage threshold, etc.

B. The systems shall provide for reception of all forms of telephonic and/or electronic communication delivery formats including, but not limited to, analog, ISDN PRI, ISDN BRI, and modem. The systems shall also provide for reception from direct audio inputs including, but not limited to, analog room probes and radio transmissions.

C-19

C. The systems should provide for automated reception/import via monitored folders of preprocessed third party data files delivered in a standardized xml format (or other standard accepted by the system such as rfc822 and later rfcs) which accurately represent internet data communications including email messages (including rfc822 and later rfcs), text messages, chat, video, audio, VOIP, images, web pages, and other internet based communications.

D. The system shall minimally provide for the collection of the following data field types when received by the system:

Date

Start Time

Dialed Digits

Direction of Session (Incoming/Outgoing)

Caller ID Information (CNI)

End (or release) Time

Cell Site/GPS Location Information

Target Telephone Number

Session completion/answered.

SUBSECTION C.C.2 INTERFACE HARDWARE

A. Telephonic Interface for data packet/audio delivery shall possess the capability of customizing to all possible standards, including but not limited to, PRI interface cards, BRI interface cards, and analog.

SUBSECTION C.C.3 EMERGING TECHNOLOGIES

A. The Contractor shall continually update their product throughout the life of the agreement to maintain compatibility with any new technologies, innovations, or forms of communications emerging in the realm of telecommunications.

SUBSECTION C.D CRITICAL PRIMARY FUNCTIONS

SUBSECTION C.D.1 LIVE MONITORING

A. Live Monitoring (the intercepting, reviewing, controlling for minimization protocols, and recording of communications content in real time) shall be performed by a single monitor located at an individual workstation connected by either LAN or WAN to the T2S2

System, depending on the physical location of the workstation and its proximity to the central core.

B. Terminal services shall be available to achieve remote location monitoring (for example, to facilitate later system expansion to smaller offices).

C. Individual workstations shall be re-configurable for location assignment at any time, general system parameters allowing. (For example, the number of workstations assigned

C-20 to a main core site shall be reducible, with the workstations re-assigned to a remote office.)

D. The system shall possess the ability to utilize the integrated dual flat screen monitors so as to “un-dock” and transfer selected display functions from one monitor screen to another while preserving full functionality. For example, the user shall be able to move any cell site mapping display, or synopsis or summary field, etc., from one monitor to the other.

E. The system shall afford operators the selectable ability to choose to utilize headphones or speakers for the monitoring of target lines at any particular time of use.

F. Live Monitoring and the associated interception/collection of communications shall take precedence over all other activities performed on the system. If a monitor happens to be in the process of producing a written word product, performing case analysis, generating reports, or otherwise utilizing secondary functions of the system and a live session is initiated or received by the target, the program shall automatically save all the work and the system shall immediately switch the monitor’s focus to the live session. The controlling monitor shall be barred from performing functions unrelated to the Live

Monitoring mode while responsible for the live monitoring of any particular session, thereby focusing the monitor’s attention upon the new live session. After the live session is complete, if the new live session interrupted work in another Playback session, the system should give the monitor the option of returning to the prior session at the location where the monitor was when the live session began.

G. The Live Monitoring mode shall possess an easily identifiable, unique onscreen appearance which differentiates itself to the user from the Playback mode, thus alerting the monitor to a new session which is being intercepted live.

H. Only one monitor shall have control of an interception occurring in Live Monitor mode at any time. Multiple listeners shall be allowed, but only the monitor possessing control shall be able to type in the…