ATTACHMENT A - STATEMENT OF WORK FOR STATEWIDE LAW ENFORCEMENT RADIO SYSTEM (SLERS) ITN NO: DMS-15/16-018 INVITATION TO NEGOTIATE THE STATE OF FLORIDA DEPARTMENT OF MANAGEMENT SERVICES

Table of Contents 1

STATEMENT OF WORK INTRODUCTION ........................................................................ 6

2

SLERS USERS ................................................................................................................... 6

3

COMMUNICATIONS SERVICE .......................................................................................... 6 OPERATIONAL OBJECTIVES .................................................................................... 6 Communications Capabilities Objectives .............................................................. 6 Service Capabilities Requirements ....................................................................... 9 Wide Area Communications.................................................................................. 9 Encryption and Authentication .............................................................................10 Service Design and Failure Modes ......................................................................11 Dispatch Operations ............................................................................................12 Computer Aided Dispatch Interface .....................................................................17 Location Services ................................................................................................18 Over the Air Programming (OTAP) ......................................................................18 Administration and Control ...................................................................................19 Interoperability .....................................................................................................22 Radio Equipment and Components .....................................................................26 Facilities...............................................................................................................26 SECURITY .................................................................................................................31 COVERAGE OBJECTIVES ........................................................................................32 Terrestrial and Maritime Service Coverage Objectives .........................................32 Aircraft Service Coverage Objectives ...................................................................33 CAPACITY OBJECTIVES ...........................................................................................34

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 1 | 91

Historical Service Traffic Data Description ...........................................................34 Service Capacity Objectives ................................................................................35 FREQUENCY PLANNING ..........................................................................................36 SUPPORT AND MAINTENANCE ...............................................................................36 Management ........................................................................................................36 Maintenance Capabilities .....................................................................................37 Network Management System .............................................................................37 SU Maintenance Service .....................................................................................38 Network Status Dashboard ..................................................................................38 Service Level Agreement Performance Monitoring Application ............................39 Network Operations Center..................................................................................40 Trouble Ticketing System.....................................................................................40 Infrastructure Trouble Response and Repair .......................................................41 Support Teams ....................................................................................................42 Technical Support ................................................................................................42 Subscriber Unit Diagnostics and Monitoring .........................................................43 Subscriber Unit Compatibility Testing ..................................................................44 SU Installation and Programming Service ............................................................45 Service Management Center (SMC) - Web-based Online Portal(s)......................45 SERVICE LICENSING ................................................................................................47 HARDWARE/SOFTWARE UPDATES ........................................................................48 MOBILE RADIO SYSTEM ..........................................................................................48 SYSTEM TESTING.....................................................................................................50

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 2 | 91

General ................................................................................................................50 Factory Staging and Acceptance Tests ................................................................50 Service Acceptance Test Plan .............................................................................51 Coverage Acceptance Testing .............................................................................54 4

SUBSCRIBER UNITS ........................................................................................................55 OPERATIONAL OBJECTIVES ...................................................................................55 Communications Capabilities Objectives .............................................................55 Service Capabilities Requirements ......................................................................56 Wide Area Communications.................................................................................57 Encryption and Authentication .............................................................................58 Failure Modes ......................................................................................................58 Location Services ................................................................................................59 Over the Air Programming ...................................................................................59 Administration and Control ...................................................................................60 SU Performance Specifications............................................................................61 SU Feature Specifications....................................................................................61 SU Programming .................................................................................................62 SU LICENSING ..........................................................................................................63

5

ROAMING WITH AUTOMATIC CHANGING OF SUBSCRIBER MODE ............................63 Roaming Method A .....................................................................................................63 Roaming Method B .....................................................................................................67 Enhanced Local Mode and Travel Mode .....................................................................70

6

TECHNOLOGY EVOLUTION ............................................................................................71

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 3 | 91

7

TRAINING..........................................................................................................................72 SERVICE TRAINING ..................................................................................................72 State User Training ..............................................................................................72 Technical Training ...............................................................................................73 SU TRAINING.............................................................................................................74 State User Training ..............................................................................................74 Technical Training ...............................................................................................74

8

PROJECT MANAGEMENT PLAN......................................................................................75 Staffing .......................................................................................................................75 DMS Role ...................................................................................................................75

9

TRANSITION PLAN ...........................................................................................................76

10

DISASTER RECOVERY PLAN ......................................................................................77

11

PERFORMANCE MEASURES .......................................................................................78 Performance Monitoring Baseline ...............................................................................81 Timely Credit Determination and the Application of Credits.........................................81

12

END OF CONTRACT PLAN ...........................................................................................81 Transition - Contract Completion.................................................................................81 Transition - Payment Strategy .....................................................................................82 Overlapping Contracts ................................................................................................82 Contract Terms, Conditions, and Rates ......................................................................82 Expeditious Efforts during the Transition .....................................................................82 Transition Assistance ..................................................................................................83

13

FINANCIAL CONSEQUENCES .....................................................................................84

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 4 | 91

Consequences for Non-Performance ..........................................................................84 14

OTHER ELIGIBLE SLERS PARTNERS .........................................................................84

15

MINIMUM SERVICES TECHNICAL REQUIREMENTS ..................................................85

16

INFORMATION REQUIRED FOR NEGOTIATIONS.......................................................85 Service Design............................................................................................................85 Coverage Prediction Maps ..........................................................................................86 Terrestrial and Maritime Service Coverage Prediction Maps ................................86 Aircraft Service Coverage Prediction Maps ..........................................................87 Capacity Plan..............................................................................................................89 Terrestrial and Maritime Service Capacity Plan ....................................................89 Aircraft Service Capacity Plan ..............................................................................89 Frequency Plan ...........................................................................................................89

17

BUSINESS OPERATIONS .............................................................................................89 Service Inventory ........................................................................................................89 New Service Requests ................................................................................................90 Invoicing Requirements ..............................................................................................90 Electronic Substantiating Detail File ............................................................................91 DMS Review of Contractor Invoices ............................................................................91

THIS SPACE INTENTIONALLY LEFT BLANK

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 5 | 91

1 STATEMENT OF WORK INTRODUCTION This Attachment A, Statement of Work (SOW), contains the objectives for the SLERS that will form the requirements for implementation and on-going support under any Contract resulting from this ITN. Pursuant to Section 2838, Chapter 2016-66, Laws of Florida, “[t]he procurement shall accomplish, but not be limited to: improved coverage, audio clarity, interoperability, and enhanced system features including GPS location service, text messaging, and central device management.” The deliverable is a SLERS. SLERS is made up of the communications service (Service) and subscriber units (SU) required to use the Service. Service Level Agreements (SLAs), in Attachment D, define the required minimum level of service to be performed (including criteria for evaluating successful service performance). When the SOW requires a response, an approximate word count in [brackets] is provided as guidance relative to the length of the expected response. This word count is neither a minimum nor maximum limit. The Department of Management Services (DMS) reserves the right to modify the requirements contained within the SOW during the ITN process in order for the State to achieve best value.

2 SLERS USERS See Attachment H, SLERS Users for a current listing.

3 COMMUNICATIONS SERVICE OPERATIONAL OBJECTIVES Communications Capabilities Objectives All service requirements are defined by and based upon TIA-102: Land Mobile Communications Standards (APCO/Project 25) suite of standards. Call Processing The Service should provide trunking functionality where radio channel resources are dynamically assigned to requests for communications. The processing of communications requests should be based upon priority levels such that, during periods in which there are insufficient channel resources available to accommodate all traffic, subscriber units with the highest priority are

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 6 | 91

granted access to the resource. The Service should support priority call, recent user priority, busy queuing and call back. The Service should provide continuous assignment updating where the Service continuously transmits talk group channel assignments on the control channel to allow SUs registering with the Service to being to receive in-progress calls. The Service should provide misdirected radio protection where the talk group ID or destination ID is included in the embedded traffic channel signaling to allow for SUs to verify the channel assignment is correct and revert to the control channel if not. The Service should support both P25 Phase 1 and Phase 2 calls. The Service should support P25 Phase 1 and Phase 2 operation on all working channels and should dynamically assign calls as either P25 Phase 1 or Phase 2 based upon the capability of the Subscriber Units (SU) participating in the call (i.e., P25 Phase 1 / Phase 2 Dynamic Dual Mode operation). Some models of existing SUs are capable of operating only in the 800 MHz band (i.e., no support for 700 MHz channels). For interoperability purposes, the Service should accommodate SUs capable of operating only on 800 MHz channels (i.e., SUs with no support for 700 MHz channels) in certain areas of the state as determined by the State.

1. Indicate whether the proposed Service will utilize transmission or message trunking for calls and describe any exceptions. [250 words] 2. Describe the Service’s methodology for providing for priority calls, recent user priority and busy queuing and call back. [250 words] 3. Describe any service limitations for transport of talking party identification (ID), continuous assignment updating and misdirected radio protection. [250 words] 4. Describe the Service’s methodology for providing P25 Phase 1 / Phase 2 Dynamic Dual Mode. [500 words] 5. Describe Service’s call grant times (the time period between the SU sending a call request and the system issuing a call grant over the control channel) for local and wide area calls. [150 words] 6. Describe how the Service can be designed to support 800 MHz-only SUs in certain service areas. [250 words] Communications Types The Service should provide for talk group calls, broadcast calls, emergency group calls and individual calls. If supported, Service should provide for announcement group calls and system calls.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 7 | 91

Describe, from a SU brand-agnostic perspective, the Service’s capability for and any limitations on the following types of calls: 1. 2. 3. 4. 5. 6.

Group calls Broadcast calls Emergency alerts and emergency group calls Individual calls Announcement group calls System calls. [250 words]

Describe, from a SU brand-agnostic perspective, how the Service processes emergency alerts and emergency group calls. [250 words] Messaging The Service will provide users with a means to transmit and receive messages from one SU to another. Messages may be free-form alphanumeric text messages, and pre-programmed short messages, status updates, and status requests. If supported, the Service should provide for call alert. Describe, from a SU brand-agnostic perspective, the Service's capability for and any limitations on the following types of messaging: 1. 2. 3. 4. 5.

Text messaging Short messages Status updates Status requests Call alert

[250 words] Scanning The Service should provide for the ability to identify certain talk groups as priority scan talk groups such that SUs, appropriately configured, are able to determine when the talk groups are active even when the SU is receiving transmissions on another talk group (i.e., not monitoring the control channel), thereby allowing the SU to switch to the priority scan talk group. Furthermore, the Service should provide for the ability of SUs to scan talk groups that have been patched together.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 8 | 91

The Service should be capable of forcing talk groups, designated by the State, to be available for scanning at all Radio Access Network (RAN) sites, regardless of whether a SU registered with the RAN site is affiliated with the talk group. Describe, from a SU brand-agnostic perspective, how the Service provides for SUs to perform priority scan, including the quantity of talk groups that can be configured as priority scan talk groups. [250 words] Describe, from a SU brand-agnostic perspective, how the Service provides for scanning of Patched Talk Groups. [250 words]

Service Capabilities Requirements The Service should support multisite and simulcast RAN site configurations. For simulcast RAN site configurations, the Service should utilize linear simulcast technology. The Service should support a P25 SU ID range of 1 to 15,000,000, or higher. The Service should support a minimum of 5,000 talk groups. Describe any compliance issues with the stated service capability requirements. [250 words]

Wide Area Communications Terrestrial and Maritime Service Roaming To provide wide area coverage, SUs should be allowed to roam between various RAN sites while the Service tracks the location of the SUs. The roaming process should be as automatic as possible and require very little or no action by the user of the SU. The Service should restrict the transmission of group calls to only RAN sites with registered SUs affiliated with the particular talk group. The Service should be configurable to allow certain talk groups to be service-wide to facilitate scanning. Describe, from an SU brand-agnostic perspective, how the Service tracks the locations of SUs and facilitates the roaming of SUs and scanning of talk groups. [250 words] Aircraft Service Roaming With the current service, when the aircraft are on the ground, the aircraft SUs are registered with the existing Terrestrial and Maritime Service RAN sites as they do not generally have coverage from the existing Aircraft Service RAN sites. When the aircraft reaches altitude, the users manually switch the SUs to the existing Aircraft Service. The SUs do not automatically roam

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 9 | 91

between existing Aircraft Service RAN sites. The Service should provide comparable roaming functionality as the current service. The Service should provide the option for the State to enable SUs to automatically roam between the Aircraft Service RAN sites and between Aircraft Service RAN sites and Terrestrial and Maritime Service RAN sites. Describe, from an SU brand-agnostic perspective, how the Service facilitates the roaming of SUs between Aircraft Service RAN sites and between Aircraft Service RAN sites and Terrestrial and Maritime Service RAN sites. [250 words]

Encryption and Authentication The Service should encrypt all communications calls as determined by the State. The encryption should be based upon Advanced Encryption Standard (AES) with 256-bit encryption keys (i.e., AES-256). The Service should also support Data Encryption Standard (DES) for interoperability purposes. The Service should support multiple encryption keys where individual talk groups or groups of talk groups are encrypted with unique encryption keys. If technically feasible, the Service should also provide end-to-end encryption to ensure the integrity of the communications. The Service should authenticate all SUs prior to allowing access to the Service. The authentication should be P25 standards-based Link Layer Authentication. If supported, the Service should participate in mutual authentication (Service to SU and SU to Service). The Service should provide a key management facility (KMF) to assist the State with maintaining control and integrity of the encryption and authentication keys. The KMF should have multiple layers of secure access and partitioning to allow for multiple agency use while protecting sensitive information. The KMF should utilize a FIPS 140-2 certified key generator. The KMF should support P25 standard KMF-KMF interface. The Service should also provide key fill devices to load and change encryption keys of SUs that cannot be keyed or rekeyed over the air. The key fill devices should be compliant with P25 standards for key fill devices for key loading. If supported, the key fill device should be FIPS 1402 certified. If technically feasible, the Service should provide the ability to remotely disable, add or remove rights from the key fill device. The Service should allow Multi-user / Multi-agency level access and restrictions to the KMF and key fill devices so that a user has the ability to key/rekey only the SUs for which they have the authority to do so. The Service should support P25 standards-based Over the Air Rekeying (OTAR) of encryption keys to provide the State a means to change the encryption keys without having to physically

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 10 | 91

touch a SU. The Service should also support Over the Ethernet Keying (OTEK) for Dispatch Consoles and logging recorders. Describe, from a SU brand-agnostic perspective, the methodology the proposed Service utilizes to provide the following: 1. Encryption of communications calls 2. OTAR 3. OTEK [250 words] Describe, from a SU brand-agnostic perspective, the communications chain from end device to end device (i.e., SU to SU, SU to Dispatch Console, Dispatch Console to SU) and how encryption is maintained or managed along the communications chain. [250 words] Describe, from a SU brand-agnostic perspective, the methodology of the proposed Service to authenticate SUs prior to allowing access to the Service. [250 words] Describe the proposed KMF and key fill devices including their compatibility with the proposed SUs and SUs of other manufacturers and their security and access controls. [500 words]

Service Design and Failure Modes In order to meet the SLA requirements, the State expects that the Service will be based upon a high availability/high reliability system providing resilience and tolerance to component and connectivity failures. It is the expectation of the State that to meet the SLA requirements, at a minimum, redundant connectivity to all sites will be part of the Service. Insofar as practical, the Service should maintain trunked and wide area operation and provide for a graceful degradation of trunking when a critical threshold of trunking and connectivity resources are lost. In the event of a loss of all connectivity to a multi-site RAN site, the Service should continue to provide localized trunking communications to SUs registered to the RAN site. The Service should provide an alternate means (above and beyond the system connectivity) for dispatchers to communicate with the RAN site if all system connectivity is lost. In the event of a loss of connectivity to a simulcast RAN site or a failure at the simulcast RAN site that prohibits the site from participating in the simulcast cluster without causing harmful interference, the Service should remove the RAN site from operating on simulcast frequencies. If supported, the Service should be configurable to allow the disconnected simulcast RAN site to operate, in a trunked mode, on a limited set of channels while the remaining simulcast RAN sites continue to operate normally (though without the channels allocated to the disconnected RAN site).

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 11 | 91

In the event of a loss of one or more P25 repeaters at a RAN site, the Service should continue to provide full communication services to SUs registered to the RAN site unless there are no resources available to function as a P25 control channel or there are no resources available to function as a P25 working channel. In the event of a loss of connectivity to a state dispatch center, Dispatch Consoles should operate from backup radio control stations. Describe the proposed Service’s design and tolerance to failures, including but not limited to: 1. 2. 3. 4. 5.

Hardware redundancy, including switchover times for all major components. Connectivity types and redundancy for dispatch centers, network core, RAN sites Trunking failure modes, including fall back to conventional operation if supported Compatibility of trunking failure modes with SUs from other manufacturers Dispatch failure modes and backup options, including ability to hand-off dispatch functionality to another dispatch center.

[20 pages]

Dispatch Operations The State currently has 10 locations with Dispatch Consoles. •

•

•

Regional Communications Centers (RCCs) o Fort Myers RCC – 15 Dispatch Consoles o Jacksonville RCC – 19 Dispatch Consoles o Lake Worth RCC – 19 Dispatch Consoles o Miami RCC – 17 Dispatch Consoles o Orlando RCC – 19 Dispatch Consoles o Tallahassee RCC – 19 Dispatch Consoles o Tampa RCC – 21 Dispatch Consoles Department of Corrections: o Jacksonville – 1 Dispatch Console o Tallahassee – 1 Dispatch Console Florida Department of Law Enforcement – Capitol Police o Tallahassee – 2 Dispatch Consoles

The Service should allow for additions and reductions to the quantity of dispatch centers during the term of the contract. The Service should furnish and install equal quantities of new Dispatch Consoles at each location as replacements for the existing Dispatch Consoles.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 12 | 91

Dispatch Consoles Dispatch Consoles should be designed for ease of use and should be customizable on an individual user level allowing users or agencies to configure the layout of the Dispatch Console as desired. Dispatch Consoles should be designed to enhance the dispatchers' capabilities in performing resource management tasks and to minimize the effort and concentration required for efficient use and control of the Service. This should, in part, be accomplished using high quality touch screen LCD monitors for selecting dedicated channel and talk group control windows representing all base stations, repeaters, talk groups, alert paging, and auxiliary functions at each Dispatch Console. Each function within each channel/talk group control representation, and all other functions controlled through the Dispatch Console should be color-coded with user definable color choices. Touch screen and keyboard/mouse operations should be used to select and use all dispatch functions. If supported, Dispatch Consoles should utilize touch screens and allow for control and input by use of voice commands. If supported, the Dispatch Console should provide the ability to interface a reduced version of the Dispatch Console screen (i.e., key functionality) onto the display of the computer aided dispatch (CAD) monitor or other monitor located at the dispatcher position. Dispatch Consoles should include instant recall recorders readily accessible from the dispatch application to play back recent audio transmissions. If supported, the recordings of an instant recall recorder should be able to be replayed by another instant recall recorder (if dispatcher 1 receives a call, then the instant recall converter should allow dispatcher 2 to be able to play back dispatcher 1 calls even if dispatcher 2 is not monitoring the same talk groups). Dispatch Consoles should have access to the archival logging recorder for playback of archived transmissions. If supported, the Dispatch Consoles, in comparison to large desktop and workstation computers, should occupy a smaller physical space and produce lower amounts of heat and noise. If supported, provide an option for software-based Dispatch Consoles that operate on laptop computers, perhaps with limitations, and connect to the Service through Virtual Private Network (VPN) connections. Software-based Dispatch Consoles might be used in mobile command vehicles and at locations on an as-needed basis. The Dispatch Consoles should have direct access to all interoperability resources that are part of the Service, including the ability to activate and deactivate repeaters.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 13 | 91

The Service should allow for the hand-off of dispatch responsibilities of one RCC to another RCC. Dispatch Consoles should support the following functions: 1. User Login Accounts: Dispatch Consoles should require a valid user login and security password to access the Dispatch Console. 2. Select/Unselect Audio: Dispatch Consoles should be capable of affiliating with multiple talk groups and channels and allowing the dispatcher to select one as the “selected” group with the remaining mixed together as the “unselected” groups. The Dispatch Consoles should route the selected group to a particular audio resource and the unselected audio to a different audio resource. 3. Speaker Volume Controls: Dispatch Consoles should provide volume controls for each individual speaker and headset. 4. Push-to-Talk: Dispatch Consoles should provide for push-to-talk capabilities activated by, at a minimum, mouse click, keyboard click, headset button and foot switch. 5. Clock: Dispatch Consoles should provide a clock display synchronized to the Service's master timing source. 6. Volume Display: Dispatch Consoles should visually indicate the ability to receive and transmit audio levels. 7. Channel Marker: Dispatch Consoles should provide the ability for periodic tone on a talk group or channel to indicate to new arrivals that the resource is in use. 8. Channel Monitor: Dispatch Consoles should provide the dispatcher the ability to disable the continuous tone controlled squelch system (CTCSS) of any selected conventional resource in order to permit monitoring of the communications channel prior to making a transmission. 9. Simultaneous Select: Dispatch Consoles should provide the dispatcher the ability to manually select any combination of talk groups and conventional resources for simultaneous transmissions. The Service should utilize a single trunked channel per RAN site when the simultaneous select involves multiple talk groups. 10. Multi-Auto Select: Dispatch Consoles should provide the means to create pre-configured "Simultaneous Selects" that is accessible via a single button. 11. Talk Group/Channel Busy Indicator: Dispatch Consoles should provide a visual indication that a talk group or channel resource is busy. 12. Patch: Dispatch Consoles should provide a means for a dispatcher to patch two or more talk groups, channel and/or telephone resources together such that all dispatchers and units affiliated with the resources can talk to and hear each other. 13. Talk Group Merge: The Service should utilize a single trunked channel per RAN site for transmissions when multiple talk groups are patched together. 14. Audio Cross Mute: The Dispatch Consoles should provide a programmable cross mute feature that precludes voice communication from a dispatcher's microphone from being repeated over loud speakers at other Dispatch Consoles in the dispatch center. 15. Intercom: Dispatch Consoles should provide intercom functionality with other Dispatch Consoles.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 14 | 91

16. Group Call: Dispatch Consoles should allow dispatchers to place and receive group calls. 17. Individual Call: Dispatch Consoles should allow dispatchers to place and receive individual calls. 18. Emergency Group Calls and Alerts: Dispatch Consoles should be capable of initiating, receiving, acknowledging, and terminating emergency group calls and alerts. If technically feasible, Dispatch Consoles should be configurable to increase the volume level on the transmissions from the SU that initiated the emergency group call. 19. Emergency Alert Mute: Dispatch Consoles should have the ability to be configured to mute the emergency alert tone, upon acknowledgement of an emergency alert, either only the local Dispatch Console emergency alert or all Dispatch Console emergency alerts. 20. Alert Tones: Dispatch Consoles should provide a minimum of three distinct over-the-air tones to be used for alerting purposes. Each alert tone should be immediately broadcasted on the selected talk group and channel resource when activated. At a minimum, the following tones should be available: a. Steady Alert Tone - 1000 Hz steady tone b. Warbling Tone - Alternate from low to high frequency c. Pulsed Alert Tone - Two second sequence of 1000 Hz tone pulses 21. Alias Display: Dispatch Consoles should be capable of displaying an alpha-numeric alias for the user identifications. The Service should support and provide for a centrally managed database that all Dispatch Consoles reference when converting a numeric user identifier to an alpha-numeric alias. 22. System Call: Dispatch Consoles should be capable of transmitting a broadcast message to all users affiliated with one or more specific RAN sites. 23. Remote Unit Monitoring: If technically feasible, Dispatch Consoles should be capable of remotely initiating a group call and/or individual call transmission from a SU without user pressing the push-to-talk button. 24. Call Alert: Dispatch Consoles should be capable of sending call alerts. 25. Discreet Listening: Dispatch Consoles, with appropriate authorization, should be capable of monitoring an active user's conversation without the user being aware of the activity. 26. Preprogrammed Single Button Paging: Dispatch Consoles should be capable of being configured with a series of pre-configured tones to be transmitted over a selected resource that can be activated by a dispatcher by pressing single buttons. 27. Supervisory Control: Supervisory Dispatch Consoles should be capable of taking over control to prevent other Dispatch Consoles from keying repeaters or base stations for each channel supported by parallel Dispatch Consoles. Supervisory Dispatch Consoles should be capable of overriding transmissions of other Dispatch Consoles and field units. 28. Repeat Disable: Supervisory Dispatch Consoles should be capable of disabling received audio from being repeated on conventional repeaters. 29. Headset and Jack: Dispatch Consoles should be equipped with two headset jacks per dispatch position. a. The jacks should be installed at locations convenient to the dispatcher. b. The jacks should support 4-wire and 6-wire headset configurations.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 15 | 91

c. When a headset is inserted into a jack, the dispatcher should have the capability of routing selected audio to the headset and/or the selected speaker. d. Audio from the unselected channels should remain routed to the unselected speaker output. e. The selected speaker audio should operate normally with the headset removed from its associated jack or when telephone audio is routed to the headset. f. Individual headset volume controls for radio and telephone audio should be provided and not affect the volume control setting of the selected speaker. g. Push-to-Talk (PTT) function should be incorporated into the headset jack. 30. Microphone: Dispatch Consoles should include a cardioid pattern gooseneck or swivel mount microphone having a uniform frequency response and a minimum front-to-back discrimination of 15 dB. The microphone should be resistant to interference from devices used in proximity of the Dispatch Console. 31. Footswitch: Dispatch Consoles should include a rugged dual footswitch. The footswitch should include one pedal for PTT and one pedal for monitor feature. 32. Instant Recall Recorder: Dispatch Consoles should include an instant recall recorder that is capable of replaying the recent transmissions. 33. Call History Window: Dispatch Consoles should provide a window that displays a list of recent calls received by the Dispatch Console. 34. Console Priority: Dispatch Consoles should have wireline priority over a field unit and should have the capability of preempting the field unit's repeated audio from the system. 35. Radio-telephone interface: Dispatch Consoles should have radio-telephone interfaces. When a headset is plugged in to the headset jack and no telephone line is selected, the selected speaker should be muted, selected audio routed to the headset, and transmit audio from the headset should be routed to the selected radio function. When a headset is plugged in to the headset jack and a telephone line is selected, the selected audio should be routed to the speaker, the telephone audio should be routed to the headset and the transmit audio from the headset should be routed to the telephone. In the latter configuration, when the Dispatch Console is placed in a transmit condition, headset microphone audio should be routed to the selected radio function and revert to the telephone after release of the transmit key. Describe the proposed Dispatch Consoles features, functionality, ease-of-use and operations. Indicate if any requested functions are not supported by the Dispatch Consoles. Indicate the maximum quantity of Dispatch Consoles the Service can support at any particular dispatch center. Describe any hardware/software upgrades necessary to increase the quantity of Dispatch Consoles at a particular dispatch center. [5 pages] Describe how backup RF control stations will be integrated with the Dispatch Consoles and how the Dispatch Consoles can access and control the backup RF control stations. [250 words]

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 16 | 91

Archival Logging Recorders The Service should include a dedicated archival logging recorder for state agency usage to store and retrieve radio transmissions. The logging recorder should record all calls on designated talk groups, including patched talk groups, and designated conventional channels. The logging recorder should record all text message transmissions from designated SUs. The logging recorder should record the transmission’s associated metadata consisting of time and date, duration, call type, talk group ID, talk group alias, SU ID, and SU alias. If technically feasible, the geographic location of an SU, when available, should also be recorded in the metadata. The logging recorder should be capable of recording a minimum of 128 simultaneous audio transmissions for each RCC. The logging recorder should retain recordings in accordance with the statutory provisions of Chapters 119, 257, Florida Statutes, and Section 9, Public Records of the Contract (Attachment B). The logging recorder should be redundant to ensure continued operation of the recorder in the event of a failure. The logging recorder interface should be centralized such that any authorized user can access, playback and export all state agency recordings without having to access multiple logging recorders. The interface should be designed for ease of use. The logging recorder should provide user accounts that allow for the restricting a user’s access to certain users and talk group recordings. Describe the proposed logging recorder’s features, functionality and operations and how the logging recorder meets the needs of the State. [750 words]

Computer Aided Dispatch Interface The Service should provide an interface to the State’s existing CAD system, SmartCAD by CTS America (SmartCOP, Inc.). If supported, the Service interface should provide SU ID and alias on PTT, SU site registration/deregistration notifications and talk group affiliation/de-affiliation notifications. If supported, the Service interface should allow for the CAD system to transmit status requests and receive status updates from SUs. If supported, the Service should also allow for geofencing of SUs such that the CAD system can initial talk group affiliation changes of SUs based upon their geographic location.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 17 | 91

Describe the Service’s capability to provide an interface to the State’s CAD system and the information that can be transmitted to and received from the State’s CAD system via the interface. Describe the Service’s support for geofencing of SUs. [500 words]

Location Services The Service should provide the means for SUs to transmit their geographic locations to other SUs and applications, such as the state’s existing CAD system. The Service’s location service should be in accordance with P25 standard for Tier 2 Location Services. The Service should support the configuration of location update triggers on SUs. The Service should support the following location update triggers: 1. 2. 3. 4. 5. 6. 7.

Push to Talk (PTT) Periodic Emergency Power On/Off Host Request User Request Distance Change

The Service should provide an interface to the State’s CAD systems located at each of the RCC’s to transport SU locations. The Service should provide a web-based interface for authorized users to view the location of SUs associated with the user’s permissions. The interface should allow users to configure the SUs triggers within limits based upon a user’s permission. For example, some users should be allowed to configure faster periodic trigger cadence than other users. The interface should provide the SU ID and alias of the SUs displayed on the map as well as a list of SUs that have not sent a location update for a configurable period of time. Describe, from a SU brand-agnostic perspective, the proposed Service’s location service capabilities. [500 words] Describe the CAD interface capability of the Service. [250 words] Describe the web-based mapping interface and how Multi-user / Multi-agency support is provided for this feature. [500 words]

Over the Air Programming (OTAP) The Service should provide an application and/or appliance to allow for over the air programming of their SUs. If technically feasible, the OTAP system should support Multi-user / Multi-agency

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 18 | 91

usage such that users can be restricted to reprogramming only SUs they are authorized to reprogram. The OTAP system should support programming security. The OTAP system should track successful and failed OTAP programming attempts and provide detail reporting on SU programming. Describe the OTAP solution, how SUs are reprogrammed and available connectivity options, how the solution supports Multi-user / Multi-agency and how programming complies with programming security requirements. [500 words]

Administration and Control User and Agency Accounts The Service should provide the State access to a service control system that allows authorized users to administer and manage their talk groups and SUs. The Service should provide secured remote access capabilities to the Service control system. Describe in detail how the Service provides for Multi-user / Multi-agency support for administration and control functions. [500 words] Subscriber Unit and Radio Access Network Site Registration Monitoring The Service should provide authorized users the ability to perform a radio check verify the availability of a SU on the network. The Service should provide authorized users the ability to determine to which RAN site a SU was last registered and to which talk group a SU was last affiliated. If technically feasible, the Service should provide authorized users the ability to perform a trace of a specific SU to determine in chronological order the SU’s RAN site and talk group affiliations. The Service should provide authorized users the ability to determine the SUs registered to a particular RAN site and the talk groups to which those SUs are affiliated. The access to the Service’s SU and RAN site registration monitoring should be through a web interface. If technically feasible, this access should be integrated with the Network Status Dashboard (see Section 3.6.4). Describe, from a SU brand-agnostic perspective, how the Service provides for monitoring of availability of SU and RAN site registrations and talk group affiliations and how Multi-user / Multi-agency support is provided for these functions. [500 words]

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 19 | 91

Alias Database Management The Service should support a centralized SU ID alias database for the entire Service. The Service should provide authorized users the ability to add, modify and delete SU ID alias entries in the database. If supported, alias updates should be able to be performed directly from Dispatch Console applications. If technically feasible, the alias updates should be able to be performed from a web-based interface. The Service should provide for real-time updates to the alias database. The Service should also allow for bulk updates of aliases from spreadsheets and/or other file formats. Describe how the Service provides SU ID alias database management and how Multi-user / Multi-agency support is provided. [500 words] Subscriber Unit Inhibit and Uninhibit The Service should provide authorized users the ability to inhibit a SU from operating on the system and to place the SU in a mode that appears to be powered off. The Service should provide authorized users the ability to uninhibit a SU. This function should be in accordance with P25 standards. Describe, from a SU brand-agnostic perspective, how the Service provides SU inhibit and uninhibit functionality and how Multi-user / Multi-agency support is provided. [250 words] Talk Group Control The Service should provide a means to restrict talk groups to certain RAN sites. The Service should provide a means to group permissions to facilitate applying and updating the same permissions to multiple talk groups in lieu of individually configuring each talk group. The Service should also provide a means to restrict the quantity of individual calls that are active on particular RAN sites. If technically feasible, the access to the Service’s talk group control functions should be through a web interface. Remote access should be supported. Describe, from a SU brand-agnostic perspective, the methodology the proposed Service utilizes to manage permissions of talk groups and other calls. Describe how Multi-user / Multiagency support is provided for these functions. [500 words] Regroup and Cancel Regroup The Service should provide a means for authorized users to dynamically change the talk group affiliation (a.k.a. regroup) of one or more SUs without requiring interaction by the users. The

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 20 | 91

Service should also provide a means for cancelling the regroup to return SUs to their originally affiliated talk group. If supported, the Service should provide the ability to perform regroup and cancel regroups directly from the Dispatch Console application. The Service should also provide a means for the configuration of preplanned regroup plans (a.k.a. storm plans) that can be readily activated by authorized users. If supported, a preplanned regroup plan should be able to be initiated directly from the Dispatch Console application. Describe, from a SU brand-agnostic perspective, the methodology the proposed Service utilizes to provide dynamic and preplanned regroup and cancel regroup functionality and how Multi-user / Multi-agency support is provided for these functions. [250 words] Subscriber Unit Access Control The Service should provide a means to restrict SUs to certain RAN sites and certain talk groups and types of calls. If technically feasible, this control should be a part of the Service rather than relying strictly upon the programming of a SU. The Service should provide a means to group permissions to facilitate applying and updating the same permissions to multiple SUs in lieu of individually configuring each SU. In the event a user attempts to perform an operation the SU is restricted from performing, the Service should instruct the SU to issue a talk prohibit tone to notify the user that the operation is not permitted by the system. If technically feasible, access to the Service’s SU access control functions should be through a web interface and remote access should be supported. Describe, from a SU brand-agnostic perspective, the methodology the proposed Service utilizes to manage permissions of SUs and how Multi-user / Multi-agency support is provided. [500 words] Agency / Talk Group Capacity Usage Control If technically feasible, the Service should provide for a means for authorized users to restrict an agency’s talk groups to a limited number of simultaneous talk paths on specific RAN sites. If technically feasible, when restrictions are in place, the restricted agency should have “virtual” elevated priority so that the restricted agency users should not experience contention with their restricted quantity of talk paths due to the activity of other users operating on the RAN site. If technically feasible, access to the Service’s capacity usage access control functions should be through a web interface and remote access should be supported.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 21 | 91

Describe, from a SU brand-agnostic perspective, the methodology the proposed Service utilizes to restrict agency talk groups to a limited quantity of simultaneous talk paths. [500 words] Traffic Data Monitoring, Analysis and Archival The Service should provide robust traffic data monitoring and archival functionality to facilitate management of the Service capacity. The Service should maintain a minimum of the last eight full years of data online for retrieval and analysis. The Service should archive data not available online for offline retrieval and analysis. The Service should provide authorized users the ability to generate preconfigured reports as well as the ability to generate and execute fully customizable SQL-like queries. Customized queries should be savable for repeat execution. The Service should provide, at a minimum, the following preconfigured reports on system-level, RCC regional level, and at RAN site-level bases: 1. 2. 3. 4. 5.

Busy hour calculation and traffic amount Talk group airtime usage Agency (group of SUs) airtime usage Specific SU / Dispatch Console / dispatch center airtime usage Queued calls and queuing wait times

The Service should also provide traffic data for patched talk groups, and if technically feasible, provide a breakdown of the traffic data by which talk group initiated the call. The access to the Service’s traffic data monitoring, analysis and archival functionality should be through a web interface. Remote access should be supported. Describe the traffic data monitoring, analysis and archival features and functionality of the proposed Service and how Multi-user / Multi-agency access is provided. [750 words]

Interoperability Beyond migrating to a standards-based service (i.e., P25), the State has three primary goals for improving interoperability: 1) Interoperability Overlay; 2) maintaining and sustaining the current analog mutual channels deployed throughout the state (i.e., SLERS Mutual Aid and the Mutual Aid Build-Out Project); and 3) the integration of the functionality of Florida Interoperability Network (FIN), along with enhancements, into the new Service.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 22 | 91

Interoperability Overlay Objectives One goal of this ITN is for the new Service to also function as an Interoperability Overlay that all eligible public safety users can utilize for mutual aid events (planned or incidents). For the purpose of this ITN, the State has indicated in the Terrestrial and Maritime Service capacity objectives (See Section 3.4.2) that the Service should provide for additional capacity to support two additional simultaneous talk paths when operating at P25 Phase 1 and four additional simultaneous talk paths when operating at P25 Phase 2. However, the mission critical operations of the state users should not be affected by the use of the new Service as an Interoperability Overlay. Therefore, the new Service should have a means of limiting the amount of capacity utilized by the Interoperability Overlay to the two specific additional channels. If technically feasible, this limitation should be able to be quickly removable by the State on a temporary basis and on a RAN site basis should additional capacity be required, as may occur with a large-scale multi-jurisdictional, multi-disciplinary event. The State has indicated that the Service should use P25 standards-based Link Layer Authentication and that programming of SUs should be locked such that only authorized personnel can program or change the programming of the Service in an SU. The State is interested in options, if technically feasible, to support interoperability with users with SUs that do not support P25 standards based Link Layer Authentication. Describe the capabilities of the proposed Service to manage traffic associated with using the new Service as an Interoperability Overlay and options available, if technically feasible, to allow users that have SUs that do not support P25 standards based Link Layer Authentication to have access to the Interoperability Overlay on an as-needed basis. [500 words] SLERS Mutual Aid, Mutual Aid Build-Out Project and the Florida Interoperability Network SLERS Mutual Aid The current service provides for 8CALL90/8TAC91 analog mutual aid conventional repeaters at each RAN site that was part of the initial service construction and at one of the state-funded enhancement sites. These repeaters are currently interfaced to the Integrated Multisite Controllers (IMC) of the current service and are therefore, able to be controlled directly from the Dispatch Consoles. Some local agencies have agreed to function as the Network Control Center (NCC) for monitoring and operating the mutual aid channels within their area. Therefore, some of the repeaters have audio bridges installed between the repeater and the IMC to allow for the agency functioning as NCC to monitor and control the mutual aid repeaters.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 23 | 91

Mutual Aid Build-Out Project The State has constructed additional mutual aid repeaters, in multiple frequency bands, to supplement the mutual resources that were part of the current SLERS service and mutual aid resources deployed by local agencies as part of their communications systems. The State has gone through a process to decommission some of the mutual aid build-out sites but has retained a significant portion of the original deployment. The mutual aid build-out channels are integrated into the FIN by means of a Radio Gateway Unit (RGU) for control and operating purposes. Mutual aid build-out is not part of the current SLERS service and are not directly available on the SLERS service Dispatch Consoles. Florida Interoperability Network The State implemented the Florida Interoperability Network (FIN) in 2005. The FIN project objectives were: 1. To enable First Responders and Emergency Services personnel using dissimilar radio systems and frequencies to communicate directly with each other; 2. To provide resources that will enable First Responders and Emergency Services personnel to communicate with each other when they are out of their local service area; 3. To use, when possible, existing radio systems rather than purchase/build new radio systems; 4. To provide tools that can be used in planned interagency and emergency response situations as well as normal daily operations; and 5. To have interoperability solutions that are always available, everywhere. FIN, as implemented, provides the following: 1. For network users, there are four primary functions available. a. Ability to patch any two or more radio talk groups/channels. The network can support 2048 patches simultaneously across the network. b. Ability to access radios at sites on the network. Dispatch positions can use remote radio resources across the network. c. Ability for each dispatch center to conference with up to seven other dispatch centers. d. Ability for each dispatch center to intercom other dispatch centers. 2. The Dispatcher Application also provides: a. All functions through pull-down menus and mouse usage (point-and-click) b. Call priorities (nine levels) c. Views of all active patches and conferences d. Network status (round trip delay per connection, CPU usage, packet loss rate) e. Information about remote radio sites (site name, radio type) f. Status information about remote radio sites (transmitting, receiving or idle)

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 24 | 91

g. Remote control head to operate selected remote radio sites (ability to turn on/off and change channels/talk groups) h. Audio replay up to sixty seconds i. Notifications/log display of all local actions FIN workstations are installed at 160 locations throughout the state. The FIN workstations are connected to the FIN service through a combination of MyFloridaNet and local-agency provided circuits. FIN is a separate service distinct from the current SLERS service, though the two are tied together such that SLERS talk groups are available for patching through the FIN service. However, to establish a FIN patch between a SLERS resource and a federal, state or local agency resource, it requires dispatchers for both systems to work together. For example, on the SLERS Dispatch Console, the state dispatcher first patches a SLERS talk group to a FIN resource. Similarly, on the local agency’s Dispatch Console, the local agency dispatcher patches a local resource to a different FIN resource. Then, on the FIN dispatcher application, one of the dispatcher patches the two FIN resources together. This process is performed in a similar manner when two local, state and/or federal agencies utilize FIN to patch their respective agency resources together. Service Interoperability Integration Objectives One goal of this ITN is that the Mutual Aid, Mutual Aid Build-Out Project and the Florida Interoperability Network be integrated into the new Service with the following objectives: 1. Maintain and sustain comparable coverage for all existing mutual aid and mutual aid buildout project resources. 2. Provide for direct access to all mutual aid resources directly from the new Service’s Dispatch Consoles. 3. Provide direct access to local, state and federal agency resources directly from the new Service’s Dispatch Consoles without requiring action of the local agency. As detailed in Section 3.1.11.2.3, to create a patch between a state interoperability talk group and a local agency resource, the local agency dispatcher must create a patch between the local agency resource and a FIN resource. If technically feasible, this step should be eliminated to allow state dispatchers operating on the Service to directly patch state interoperability/common talk groups to local, state and federal agency resources. If technically feasible, this capability should be reciprocal where local, state and federal agencies have access to approved state talk groups on the Service. 4. Maintain and sustain local, state and federal agency access to all mutual aid and other local, state and federal agency resources. 5. Provide local, state and federal agencies access to the new Service’s interoperability talk groups.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 25 | 91

Describe how the Service can meet the Service interoperability integration objectives of the State. Describe limitations as to the quantity of interoperability interfaces that may be supported by the Service. [5 pages]

Radio Equipment and Components All service radio equipment should be FCC type-accepted for its application. All radio equipment should meet the performance standards, specifications recommendations as specified in TIA-102.CAAB, TIA-102.CCAB and TIA-603E.

and

All radio equipment should meet the technical requirements of the Florida Law Enforcement Communications Plan for Option A equipment. All radio equipment should have passed the test cases listed in the appropriate Project 25 Compliance Assessment Bulletin for the equipment type and have a Supplier’s Declaration of Compliance and Summary Test Report on file with the U.S. Department of Homeland Security (DHS) and listed by DHS as eligible for grant procurement. All P25 repeaters should be 100 percent duty cycle at full rated transmitter power of 100 watts. Indicate if any service equipment does not meet the State’s requirements as indicated above. Describe any deviations from the requirements. [250 words] In an attachment, provide product data sheets, for all radio equipment and components proposed as part of the Service, including but not limited to: 1. 2. 3. 4. 5. 6. 7.

Servers, storage arrays and workstations Routers and switches Repeaters, base stations and control stations Antenna systems and associated components Timing and synchronization components Security components and appliances Monitoring and control equipment

Include copies of the Project 25 Compliance Assessment Program Supplier’s Declaration of Compliance and Summary Test Report for each relevant radio component proposed for the Service.

Facilities The facilities consist of towers, antenna systems, equipment shelters, emergency power systems, heating, ventilation and air-conditioning (HVAC) systems, physical security systems, site alarm

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 26 | 91

systems, and lightning and surge protection systems. The facilities should provide a highly reliable and highly available platform on which the Service is built. The facilities should, insofar as practicable, include no single point of failure. The state is subject to high wind speed events and lightning storms on an annual basis. The survivability and the effectiveness of the Service is dependent upon maintaining availability before, during and after such events. By ensuring that the antenna support structures are at current standards, well maintained and in good condition, and that the structures and associated equipment enclosures are properly grounded, the State can be assured that reasonable steps have been taken so that a catastrophic failure is unlikely except in the most extreme circumstances. The State expects the Offerors to propose structures, equipment enclosures and emergency power systems that are commensurate with mission critical communication systems. The Service should follow the recommendations for site hardening facilities in the National Public Safety Telecommunications Council (NPSTC) Public Safety Grade Task Group “Defining Public Safety Grade Systems and Facilities”, May 22, 2014. Antenna Support Structures Antenna support structures used by the Service should: 1. Have adequate space and loading capacity for the proposed antenna systems as well as the recommended distributed and concentrated design loads specified by the Florida Law Enforcement Communications Plan. 2. New antenna support structures and shall be designed by a Florida Registered Professional Engineer using ANSI/TIA-222 (latest edition) for the proposed loading and meet Florida Building Code (latest edition), and if applicable, the High Velocity Hurricane Zone (HVHZ) for antenna towers for Risk Category IV at the appropriate wind-speed and exposure for the location of the antenna support structure. 3. New antenna support structures shall, at a minimum, meet the operational limits per ANSI/TIA-222. 4. When required by the conditions of ANSI/TIA-222 (latest edition), existing antenna support structures and shall be analyzed by a Florida Registered Professional Engineer using ANSI/TIA-222 (latest edition) for the proposed loading and meet Florida Building Code (latest edition), and if applicable, the High Velocity Hurricane Zone (HVHZ) for antenna towers for Risk Category IV at the appropriate wind-speed and exposure for the location of the antenna support structure. 5. Achieve an electrical ground resistance of five ohms or less when tested using a threepoint fall-of-potential ground test performed by a Florida Registered Professional Engineer using calibrated test equipment. Electrical ground resistance should be retested every three years to verify that a resistance of five ohms or less is still being achieved.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 27 | 91

6. For new antenna support structures, be inspected and approved by a Florida Registered Professional Engineer upon completion of construction. 7. Be annually inspected following the recommendations of ANSI/TIA-222, including measuring the structure's deflection and rotation and guy wire tension, as applicable. All deficiencies identified in the inspection should be corrected within 30 days. 8. Be lighted and/or marked in accordance with the requirements of the FAA. 9. Tower lightning controllers should be installed with surge protection devices that protect all tower light lines, markers, strobes and beacons connected to the controller. It is the Offeror’s responsibility for determining if the State’s expectations are adequate to enable the Offeror to meet the SLA requirements. Describe how proposed antenna support structures will be designed to meet the expectations of the State, describe the Offeror’s own technical requirements and how such requirements will allow the Offeror to meet the SLA requirements. [750 words] Antenna Systems Land mobile radio antenna systems should be rated by the manufacturer for a minimum wind speed survivability of 120 mph. Microwave antenna system should be rated for a minimum wind speed survivability of 155 mph. Land mobile radio and microwave antenna systems should be, at a minimum, grounded at the top of the antenna support structure, the base of the antenna support structure and upon entrance into the equipment enclosure. Land mobile antenna radio antenna systems should have lightning protector(s) installed upon entrance into the equipment enclosures. Waveguide and transmission line hangers should be bolt-in type. Snap-in hangers should not be used. It is the Offeror’s responsibility for determining if the State’s expectations are adequate to enable the Offeror to meet the SLA requirements. Describe how the proposed land mobile and microwave antenna systems will be designed to meet the expectations of the State and describe the Offeror’s own technical requirements and how such requirements will allow the Offeror to meet the SLA requirements. [500 words] Equipment Enclosures Equipment enclosures should:

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 28 | 91

1. Have adequate space and capacity for the planned equipment. 2. Meet Florida Building Code (latest edition), and if applicable, the High Velocity Hurricane Zone (HVHZ) requirements for manufactured buildings for Risk Category IV at the appropriate wind-speed and exposure for the location of the building. 3. Achieve an electrical ground resistance of five ohms or less when tested using a threepoint fall-of-potential ground test performed by a Florida Registered Professional Engineer using calibrated test equipment. Electrical ground resistance should be retested every three years to verify that a resistance of five ohms or less is still being achieved. This test may be performed in conjunction with an antenna supporting structure ground test. 4. Be annually inspected structural issues, HVAC issues, safety compliance, and insect damage. An inspection report should be delivered to the State on an annual basis. 5. Have surge protection device(s) on commercial power and all metallic wireline telecommunications circuits. 6. Have redundant environmental control units (e.g., HVAC units) 7. Be physically secured by, at a minimum, the following means: a. Deadbolt door lock b. Anti-prying plate c. Bullet resistivity rating of UL-752 Level 4 for both the structure and the door. d. Signage e. 8-foot security fence around perimeter when located in unsecured area. 8. Have an appropriately sized emergency power system. 9. Meet all OSHA requirements for safety. Each equipment enclosure should be monitored by site alarm equipment. The following alarms should be monitored by the Service's 24/7 network operations center: 1. Building entry 2. Building smoke/fire 3. Fire suppression system discharge 4. Fire suppression system trouble fault 5. Air conditioner A failure 6. Air conditioner B failure 7. Commercial power failure 8. Emergency power generator transfer switch position 9. Main power surge protection device (SPD) failure 10. For each emergency generator system a. Generator running b. Generator control switch not set c. Generator low oil pressure alarm d. Generator high coolant temperature alarm e. Generator fuel level (analog measurement) f. Generator failure g. Generator battery charger alarm

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 29 | 91

11. For each emergency power supply a. Power supply on line b. Rectifier/battery charger low voltage c. Low voltage disconnects 12. For each air dielectric transmission line and waveguide pressurization manifold a. high pressure b. low pressure It is the Offeror’s responsibility for determining if the State’s expectations are adequate to enable the Offeror to meet the SLA requirements. Describe how the proposed equipment enclosures will be designed to meet the expectations of the State, describe the Offeror’s own technical requirements and how such requirements will allow the Offeror to meet the SLA requirements. [750 words] Dispatch Facilities The State will be responsible for providing state dispatch facilities and making the necessary improvements to the facilities to support the installation of the Offeror’s equipment. The Offeror is responsible for determining if the dispatch facilities are adequate to enable the Offeror to meet the SLA requirements. Describe the Offeror’s technical requirements for dispatch facilities, including industry standards and their own industry standards necessary for the Offeror to meet the SLA requirements. [750 words] Emergency Power Systems New and existing emergency power systems should consist of the combination of a long-term emergency power generator for use in the event of a loss of commercial power and a short-term emergency power supply, such as a UPS and/or DC power system, to maintain the electrical service to equipment during the startup of the emergency power generation system or failure of the emergency power generation system. Emergency power generators should: 1. Upon loss of commercial power, automatically start and provide power to the equipment enclosure. 2. Provide a minimum of 14 days of continuous runtime of all equipment enclosure loads based upon the fuel supply initially being at its fuel storage’s maximum fill level.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 30 | 91

3. Be sized for a minimum of ten percent excess continuous kilovolt-ampere (kVA) capacity over planned loads, including step load of emergency power supplies and start-up capacity for rotating equipment. 4. Have fuel supply maintained at a minimum of 50 percent of the maximum level and be refueled to the maximum level, at a minimum, between April 1 and June 1 of each year. 5. At a minimum, be annually inspected and maintained by manufacturer certified personnel. 6. Be weekly tested including transference of equipment enclosure loads. 7. Be fully load tested prior to being used for the new Service to confirm the emergency power generation system meets design specifications. Emergency power supplies should: 1. During period of no commercial and emergency generator power, automatically provide power to connected loads with no disruption. 2. Provide a minimum of 2.5 hours of continuous runtime of all loads associated with the RAN, lighting system (equipment enclosure and tower lighting), and safety equipment based upon the power supply storage initially being at its maximum level. 3. Provide a minimum of eight hours of continues runtime of all connectivity equipment and alarm equipment. 4. Be sized for a minimum of 25 percent expansion of load. 5. Be inspected on a monthly basis to ensure that all battery cells are within manufacturer specifications. The State expects that the emergency power supply that supports the connectivity and alarm equipment be a separate emergency power supply from the emergency power supply that supports the RF equipment. Describe how the proposed emergency power systems will be designed to meet the expectations of the State, describe the Offeror’s own technical requirements and how such requirements will allow the Offeror to meet the SLA requirements. [750 words]

SECURITY The Service, as well as its users, should consider communications security as of paramount importance. The Service should take a holistic approach by considering physical security, network security, communications security and administrative security. The State expects, at a minimum, that the Service’s network security will consist of the following: 1. Firewalls 2. Virtual Private Networks 3. Intrusion Detection

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 31 | 91

4. 5. 6. 7.

Antivirus Antimalware Access Control Tested Security Patches

The State expects the Contractor to regularly audit the Service for compliance with the Service’s security requirements. Describe their security plan for the Service including, but not limited to: 1. 2. 3. 4.

Physical security Network security Communications security Administrative security

Describe how compliance with the Service’s security requirements will be regularly and independently audited. The Offeror should consider the recommended guidelines for “sensitive-but-unclassified” security level of the Public Safety Wireless Network Digital Land Mobile Radio System Security Guidelines Recommendations, October 1998 and the requirements of Criminal Justice Information Services Security Policy, Version 5.4, October 6, 2015 in their response. [5 pages]

COVERAGE OBJECTIVES Terrestrial and Maritime Service Coverage Objectives A goal of this ITN is for the Service to provide mobile coverage and audio clarity such that 98 percent of the area 98 percent of the time will be validated as meeting or exceeding Delivered Audio Quality (DAQ) 3.4 to/from a mobile SU operating with a 3 dBd antenna mounted at 5.5 feet within the geographic land boundary of the state such that when tested, 98 percent of the test grids will meet or exceed the test criteria. A goal of this ITN is for the Service to provide portable outdoor coverage and audio clarity such that 95 percent of the area 95 percent of the time will be validated as meeting or exceeding DAQ 3.4 to/from a portable SU located on the hip within the geographic land boundary of the state such that when tested, 95 percent of the test grids will meet or exceed the test criteria. A goal of this ITN is for the Service to provide reliable DAQ 3.4 portable outdoor coverage at specific work locations, such as boat ramps, weigh stations and agriculture inspection stations.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 32 | 91

A goal of this ITN for Maritime operation is for the Service to provide mobile coverage and audio clarity such that 98 percent of the area 98 percent of the time will be validated as meeting or exceeding DAQ 3.4 to and from a mobile SU operating with a 3 dBd antenna mounted at 5.5 feet within 25-mile boundary of the coastline of the state such that when tested, 98 percent of the test grids will meet or exceed the test criteria. The areas of less-than-desired coverage should be due to the difficult environment factors (e.g., terrain, dense urban clutter, site access or environmental permitting issues restricting construction of new towers) rather than due to an Offeror’s attempt to meet a minimum coverage specification with the minimum number of sites. Insofar as practical, there should be no significant contiguous area of less than desired coverage or spotty coverage. The State intends to negotiate a mutually acceptable coverage acceptance test procedure such that the coverage goals of the State are met. The State expects an exhaustive and comprehensive coverage acceptance test will be performed. Describe how the proposed Terrestrial and Maritime Service design will be developed, what techniques will be used to optimize coverage, the technology advantages of the Service, and the compatibility of the technology with SUs from other manufacturers. [750 words] Describe the techniques that could be employed to improve the radio coverage level within buildings, particularly areas below ground level and deep interiors of buildings. [500 words] Describe the techniques that could be employed to improve indoor and outdoor radio coverage at specific locations where it is not cost-effective to deploy or provide adequate coverage from a full RAN site. Such techniques may consider providing limited capacity to be used primarily by the personnel stationed at those locations. [250 words] Provide the following RF coverage parameters that will be utilized in the Terrestrial and Maritime Service coverage analyses: 1. Receiver sensitivity specifications for all Service’s receivers 2. Bit Error Rate (BER) required for DAQ 3.4 3. The faded performance margin, CF/(I+N), utilized per TIA TSB-88 for the required Channel Performance Criterion (CPC) requirement for DAQ 3.4 4. The minimum received signal level for DAQ 3.4 for all Service’s receivers. [100 words]

Aircraft Service Coverage Objectives A goal of this ITN for aircraft operation is for the Service to provide Aircraft Service coverage and audio clarity such that 98 percent of the area 98 percent of the time will be validated as meeting or exceeding DAQ 3.4 to and from an aircraft SU (mobile SU limited to 10 watts output power) operating at 500 feet AGL within the area that extends 25 miles beyond the geographic land

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 33 | 91

boundary of the state such that when tested, 98 percent of the test grids will meet or exceed the test criteria. It is the expectation of the State that the Aircraft Service be a separate RAN from the Terrestrial and Maritime Service. All aircraft SUs are P25 capable and should be compatible with the new Service. State will be responsible for programming the SUs to operate on the new Service, however, the Contractor should provide assistance in troubleshooting compatibility issues should they arise. The State expects that the Offeror will provide detailed coverage prediction maps during negotiations. Describe how the proposed Aircraft Service design will be developed, what techniques will be used to optimize coverage, the technology advantages of the proposed Service, and the compatibility of the technology with SUs from other manufacturers. [750 words] Provide the following RF coverage parameters that will be utilized in the Aircraft Service coverage analyses: 1. Receiver sensitivity specifications for all Service’s receivers 2. BER required for DAQ 3.4 3. The faded performance margin, CF/(I+N), utilized per TIA TSB-88 for the required CPC requirement for DAQ 3.4 4. The minimum received signal level for DAQ 3.4 for all Service’s receivers. [100 words]

CAPACITY OBJECTIVES Historical Service Traffic Data Description The current service provides the State access to a data warehouse where historical traffic data can be retrieved. The State has retrieved busy hour reports for the existing Terrestrial and Maritime Service from the period of 11/9/2014 to 11/8/2015 in one week intervals. The traffic data is aggregated on a site basis with simulcast clusters being represented by a single entry. The State has converted the coverage prediction of the current system for mobile talk-out to a simplified shapefile and joined a summary of the traffic data to the shapefile coverage elements. For the existing Aircraft Service, the State has retrieved busy hour reports from the period of 11/9/2014 to 11/8/2015 in one week intervals. The current service utilizes transmission trunking and therefore the data provided is based does not include a hang time. The State has also collected basic site parameters to allow the Offeror perform its own coverage analyses of the Terrestrial and Maritime Service and Aircraft Service.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 34 | 91

This data will be provided to the Offeror during negotiations in accordance with Section 16.

Service Capacity Objectives The Service should provide capacity with a goal of achieving a Grade of Service of one percent (No more than 1 out of 100 calls queued) during the busy hour for each Terrestrial and Maritime Service RAN site (Note: the term RAN site in this context also refers to a group of RAN sites configured into a simulcast cluster.) Though it is expected that all state SUs operating on the Terrestrial and Maritime Service will be P25 Phase 2 capable, there is a need to support P25 Phase 1 only SUs for interoperability purposes. The Terrestrial and Maritime Service should provide additional capacity to allow for two simultaneous talk paths, operating at P25 Phase 1 at each RAN site to support usage of additional interoperability talk groups. This additional capacity should also support P25 Phase 1 / Phase 2 Dynamic Dual Mode operation in order to achieve up to four simultaneous talk paths. The Service will provide P25 Tier 2 location services (i.e., GPS). The Service should provide additional capacity to accommodate location reporting for 50 SUs with a 30 second cadence periodic location update per Terrestrial and Maritime Service RAN site. This expectation applies to individual RAN sites within a simulcast cluster such that the total quantity of users supported within a simulcast cluster equals the 50 times the number of simulcast cluster RAN sites. The Service should provide for capacity for state aircraft, which may be Phase 1 only SUs. The Service should provide comparable capacity level that exists today from the existing 10-sites each operating with four channels (three working channels) and an eleventh Aircraft Service RAN site that is scheduled for construction in Fiscal Year 16-17 operating with six channels (five working channels). If supported, the Service should provide P25 Tier 2 location services (i.e., GPS) for aircraft. If necessary, the Service should provide additional capacity to accommodate location reporting for two SUs with a 30 second cadence periodic location update per Aircraft Service RAN site. The State expects the Offeror will provide a detailed traffic usage during negotiations. Describe the technology that will be used by the Service to maximize capacity and minimize equipment costs. Describe how the Terrestrial and Maritime Service and Aircraft Service capacity designs will be developed upon receipt of the historical traffic data. Describe how the Terrestrial and Maritime Service and Aircraft Service capacity will be tuned based upon the actual traffic loads after the Service is operational. [750 words]

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 35 | 91

FREQUENCY PLANNING The State has collected a list of call signs that are part of the current service and a list of 700 MHz channels the State is authorized to utilize for the new Service per 47 Code of Federal Regulations § 90.531(b)(5) and the State’s 700 MHz Region 9 plan. The State has allocated a quantity of channels of 700 MHz state-use channels for the Terrestrial and Maritime Service usage. A portion of these channels are currently used to support the Regional Domestic Security Task Force Region 2 Public Safety Interoperable Communications (PSIC) grant Interoperability Overlay. Should the negotiated Service’s contract provide for an Interoperability Overlay providing comparable coverage to the Region 2 PSIC system, the State will allow the Service to utilize these state-use channels. The State has allocated, and the current Aircraft Service RAN sites are using, a quantity of stateuse channels for the Aircraft Service. This data will be provided to the Offerors during negotiations in accordance with Section 16. The State expects the Offeror to develop a frequency plan during negotiations. The State expects the Offeror to be responsible for all engineering studies and frequency coordination required, including coordination with neighboring states, to ensure that harmful interference will not be caused by or received by the new Service. The State may allocate additional 700 MHz channels for campus operations on a case-by-case basis. Campus operations should be limited to cover no more than a three-mile radius beyond their geographic boundary. Describe how a detailed frequency plan will be developed and any special considerations for use of 700 MHz and 800 MHz channels. [500 words]

SUPPORT AND MAINTENANCE Management The Service should provide a support manager functioning as a single point of contact (SPOC) for the management of all support and maintenance issues. The support manager should have responsible charge for all aspects of maintaining the operations of the Service and authority to direct Contractor’s staff and subcontractors to correct service-affecting issues. The SPOC should be available 24/7, 365+ days as required to manage and oversee restoration of the Service and respond to State requests.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 36 | 91

Describe the Service’s support and maintenance management structure, including but not limited to: 1. Point of contact 2. Organizational structure with responsibilities and levels of authority 3. Escalation policies [500 words]

Maintenance Capabilities Describe how the Service will be maintained, including but not limited to: 1. 2. 3. 4. 5. 6. 7. 8.

Locations of service depots Locations and quantities of service technicians Required certifications and training of service technicians Planned levels of spare parts per equipment type Types, location and quantities of test equipment Service issue notification and repair procedures Parts replacement and repair procedures Preventative maintenance procedures

[5 pages]

Network Management System To effectively manage the service level agreements, the Service should have visibility into the status of all critical elements and be monitored using a network management system (NMS). The NMS should monitor in real-time the integrity of all major communications system components of the network core, RAN, dispatch and connectivity networks, including, but not limited to: 1. 2. 3. 4. 5. 6. 7. 8.

Routers and switches Servers, computers and storage devices Repeaters and base stations Simulcast and voting equipment Dispatch equipment Backhaul and connectivity equipment Emergency power systems Site alarm equipment

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 37 | 91

The NMS should have multiple levels of security access. Management and configuration functions should be password protected and logs kept of all entries. For auditing purposes, the State should have unrestricted read-only access to the NMS from DMS office located at 4030 Esplanade Way, Tallahassee, FL, 32399-0450. The State has Internet access at the DMS office that may be used for connectivity, however, all additional equipment, such a VPN appliances are the responsibility of the Offeror. In addition, the State should have unrestricted read-only access from any other internet connection using a secure VPN token. Describe the proposed Service NMS, the equipment that will be monitored and protocols used, how the NMS will be used to ensure that the SLA requirements will be met and how access to the NMS will be provided to the State for auditing purposes. [750 words]

SU Maintenance Service The Contractor should provide the option for state agencies to enter into a maintenance contract or on-demand agreements. The Contractor should offer options for the repair and/or replacement of a SU that is not performing within the required specifications of the Service, has a physical issue (e.g., stuck button or knob or failed display), or has failed to operate. The Contractor should offer options that include an annual preventative maintenance check and tune-up. The Contractor should offer options for on-site maintenance and service depot maintenance. The Contractor should have multiple service facilities within the State of Florida. All SU repair service should be performed within the continental United States. Describe the maintenance service offerings including but not limited to: 1. 2. 3. 4. 5.

Service and repair policies Locations of repair depots Preventative maintenance procedures Typical service and repair times Shipping requirements

[500 words]

Network Status Dashboard To maintain situational awareness, the State should have access to a Network Status Dashboard (NSD) that provides at a high level the status of the Service.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 38 | 91

If technically feasible, the NSD should be generated by the NMS or from the same data received by the NMS. The NSD should be graphical in nature depicting site locations on a geographic map. The NSD should utilize icons, colors and text as a means to relay information to the viewer. The NSD view for each authorized user should be customizable so that the viewer is only able to view the status of elements for which they are authorized to view and the user is able to remove elements from their view should they chose to do so. If technically feasible, the NSD should support a wide range of web browsers and not require the installation of plug-in modules. Describe the proposed NSD, including but not limited the NSD views, the source of the underlying data, user access control and customization and technology requirements of the users of the NSD. [750 words]

Service Level Agreement Performance Monitoring Application To facilitate contract management, the State should have access to a Service Level Agreement (SLA) Performance Monitoring Dashboard that provides at a high level the performance of the Service in meeting the contractual SLAs. See Section 11. If technically feasible, the SLA should be generated by the NMS or from the same data received by the NMS and from the trouble ticketing system and present the Service’s SLA performance utilizing charts and tables. The SLA Performance Monitoring Dashboard should offer a customizable display of the key performance indicator metrics that are representative of the service level agreement and the network status at a summary level in a dashboard-type of view, with the option to drilldown to the lower level underlying data. If technically feasible, the SLA Performance Monitoring Dashboard should provide statistics on all SLA events. For each SLA, the SLA Performance Monitoring Dashboard should provide statistics on: 1. 2. 3. 4. 5.

Quantity of SLA events Minimum, maximum and average response times Minimum, maximum and average restoration times Quantity of SLA violations Cumulative contract credits

If technically feasible, the SLA Performance Monitoring Dashboard should support a wide range of web browsers and not require the installation of plug-in modules. Describe the proposed SLA Performance Monitoring Dashboard, including but not limited the SLA statistics and reporting, the source of the underlying data, user access control and technology requirements of the users of the SLA Performance Monitoring Dashboard. [750 words]

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 39 | 91

Network Operations Center The Service should provide a Network Operations Center (NOC) to monitor the Service and dispatch service technicians to resolve issues. The NOC should be staffed 24/7, 365+ days per year. The NOC should continuously monitor the status of the Service, respond to alarms reported by the Service’s NMS, and receive and manage trouble ticket requests made by the State. The NOC should be physically secured to permit entry of only authorized personnel. To facilitate face-to-face communications and scheduling of meetings, a goal of this ITN is that the NOC contain the day-to-day offices of the Service’s management, administrative and system engineering staff dedicated to the Service. To facilitate State participation in testing, a goal of this ITN is that the NOC be used by the Contractor as a testing lab for the Service to isolate issues and test fixes, test Service and SU software releases, and test compatibility of SUs from other manufacturers. To minimize state personnel travel time, a goal of this ITN is that the NOC be located within ten miles of the DMS office located at 4030 Esplanade Way, Tallahassee, FL 32399-0950. Describe the proposed Service’s NOC, how the NOC meets the State’s expectations including but not limited to: 1. 2. 3. 4.

Monitoring capabilities Staffing levels Location Testing capabilities

[750 words]

Trouble Ticketing System The Service should include a trouble ticketing system for the management of system and subscriber trouble response and restoration. All of the Service’s trouble response and repairs should be documented in the trouble ticketing system. The trouble ticketing system should allow for authorized users to create a trouble ticket by calling a toll-free number and speaking to an agent. The agent should speak English and be physically located at the Service’s Network Operations Center. The trouble ticketing system should also allow for authorized users to create a trouble ticket through a web-based online portal. The online trouble ticketing system should be user friendly and provide guidance to the user as to how to complete a trouble ticket request. The trouble

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 40 | 91

ticketing system should use drop-down lists and menus, where appropriate, to simplify the information entry process for the user. All trouble tickets should be accessible via the web-based online portal for authorized users to view the status of the trouble ticket. Based upon the desired response by the user creating the trouble ticket, the Service should call, email and/or text the user when the trouble ticket is closed. The Service should provide reports to the State on a weekly basis regarding the details and status of opened, closed and cancelled trouble tickets. Describe the proposed Service’s trouble ticketing system, how the trouble ticketing system meets the State’s expectations including but not limited to: 1. Trouble ticket lifecycle 2. Monthly trouble ticketing reporting [750 words]

Infrastructure Trouble Response and Repair The Contractor should respond and correct major failures within the following timeframes: 1. 2. 3. 4.

Telephone response by a technician to a user-created trouble ticket within 15 minutes. Technician on-site within two hours of creation of trouble ticket. Trouble repaired within four hours of creation of trouble ticket. Telephone response by Contractor within 30 minutes of closure of user-created trouble ticket.

For major failures, time frames should be based upon 24 hours-a-day, 7 days-a-week, 365 daysa-year basis. The Contractor should respond and correct minor failures within the following timeframes: 1. 2. 3. 4.

Telephone response by a technician to a user-created trouble ticket within one hour. Technician on-site within four hours of creation of trouble ticket. Trouble repaired within eight hours of creation of trouble ticket. Email or telephone response by Contractor within one hour of closure of user-created trouble ticket.

For minor failures, time frames should be based upon 8 a.m. to 5 p.m., Eastern Time, Monday through Friday, excluding state-recognized holidays.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 41 | 91

When the Contractor detects or the State reports coverage deficiencies in a particular area, the Contractor should respond in a timely manner to determine the root cause of the coverage issue and correct any problems that are within the responsibility of the Contractor. For coverage issues resultant from external causes, the Contractor should work with the State to develop a plan for correcting the problem. Describe the proposed Service’s infrastructure repair and response procedures and how the infrastructure repair and response procedures meet the State’s expectations. [500 words] In an attachment, list possible failure scenarios and propose a categorization of the failure scenario as major or minor. Describe the process by which coverage deficiencies will be reviewed and resolved. [500 words]

Support Teams The Service should provide support teams to resolve system issues that may arise that cannot readily be resolved by day-to-day Service technicians. These teams may be responsible for designing and performing major software release updates to the Service, respond to major site outages and/or catastrophic events, and resolve outstanding technical issues that have not been resolved in a timely basis. Describe the proposed Service’s support team resources, including but not limited to: 1. Organizational structure 2. Technical capabilities 3. When and how these resources will be deployed [500 words]

Technical Support The Contractor should provide technical support to state agencies for non-service affecting issues (service-affecting issues should be managed by infrastructure response and repair procedures). The Service should receive technical support requests on a 24/7 hour, 365+ day basis. The initial response by first echelon technical support should be within one hour or within one hour of next business day if technical support request is made before 8:00 AM or after 6:00 PM EST/EDT. The Service should support unlimited technical support requests by state agencies and users.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 42 | 91

The Service should maintain logs and records of all technical support requests and provide a monthly report to the State of opened and closed requests. The Service should offer consultation and development services to state agencies for the creation and modification of SU personalities. Describe the proposed Service technical support offering, how the Service meets the State’s expectations, including but not limited to: 1. 2. 3. 4. 5. 6. 7.

Technical support request procedure Organizational structure of technical support unit Point of contact Response times and availability Escalation policies Diagnostic capabilities Consultation and development services for creation and modification of SU personalities.

[750 words]

Subscriber Unit Diagnostics and Monitoring The Service should provide a means to monitor the receive transmissions from SUs to determine if an SU is operating outside the Service’s required SU operating specifications. The Service should perform the following measurements: 1. 2. 3. 4. 5. 6. 7. 8. 9.

RF Frequency Error Symbol Frequency Error at 600 Hz Symbol Frequency Error at 1800 Hz Modulation Fidelity Max Frequency Deviation Emission Mask Conformance Receive Signal Strength Indication Signal to Noise Ratio Bit Error Rate

The Service should provide a monthly report to the State of SUs that are operating outside the Service’s required SU operating specifications. At a minimum, the Service should measure the performance of each SU at least once every six months.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 43 | 91

Describe the required SU operating specifications and how the Service will measure all SUs’ performance while operating on the Service, how the Service will achieve a measurement of all the SUs every 6 months, and describe the reporting the Service will provide to the State. [750 words]

Subscriber Unit Compatibility Testing The Service should provide for compatibility testing of SUs from all P25 SU manufacturers with the Service. The State expects that all SUs will met the minimum requirements: 1. Be FCC type-accepted for its application. 2. Meet the performance standards, specifications and recommendations as specified in TIA102.CAAB, TIA-102.CCAB, and TIA-603 3. Meet the technical requirements of the Florida Law Enforcement Communications Plan for Option A equipment. 4. Have passed the test cases listed in the appropriate Project 25 Compliance Assessment Bulletin for the equipment type and have a Supplier’s Declaration of Compliance (SDOC) and Summary Test Report (STR) on file with the DHS and listed by DHS as eligible for grant procurement The State expects the Offeror to provide a list of minimum specifications that the SUs are required to meet to be compatible with the Service. If any specifications exceed those required by the above referenced requirements, detailed justification for the need for the more stringent requirements and why the current requirement is insufficient should be provided. The State reserves the right to accept or reject any requirement that exceeds the states requirements. The Offeror should provide a test procedure for confirming the compatibility of SUs. Each test document should include a description, a list of equipment needed to complete the test, a stepby-step procedure for completing the test, and the expected outcome of the test. The Contractor should provide a facility within the state of Florida to perform compatibility tests that can be witnessed by the SU manufacturer and State. To facilitate State participation in testing, a goal of this ITN is that the facility be part of the Network Operations Center. Describe the proposed compatibility testing that meets the expectations of the State. Indicate any specific SU requirements that exceed the State’s requirements for SUs along with an explanation of the need for the requirement. Describe the testing facility’s capabilities and indicate its proposed location. [500 words] In an attachment, provide a complete set of SU compatibility test procedures.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 44 | 91

SU Installation and Programming Service The Service should provide for the installation and programming of all SUs provided in the initial contract. The Service should provide installation and programming service for subsequently purchased SUs. This service for subsequently purchased SUs may be part of a maintenance service agreement, a separate programming service agreement, or on an as-needed basis. The installation and programming service should be available statewide. The Contractor may provide installation and programming services at the user’s location or at the Contractor’s service locations. Describe the proposed installation and programming service offering including but not limited to: 1. Service locations and capabilities 2. Typical installation times for various vehicle and vessels. 3. Typical Programming turn-around times [1000 words]

Service Management Center (SMC) - Web-based Online Portal(s) The Contractor should provide an online portal for supporting the Service. The portal should be the overarching Service Management Center (SMC) to function as the secure, on-line, web-based portal for the State to access the following applications: • • • •

Service Administration and Configuration Application (Central Device Management) Trouble Ticketing System Network Status Dashboard Service Level Agreement Performance Monitoring Dashboard

The SMC should support multiple authorization levels controlling user privileges and functions. The SMC should recognize the user’s authorization level, and the user’s organization and region by the individual user-id. The SMC should ensure that only authorized staff with an approved purpose can access the SMC applications, perform actions and view data. The SMC, or an application included in the SMC, should contain notification options based on user defined trigger parameters. The SMC should create an email or text of the requested information should a trigger occur. If technically feasible, the triggers should be configurable for key performance indicators such as Grade of Service to provide an alert when the Service is experiencing a high volume of queued calls. Notifications should be able to be defined statewide or regionally by RAN site and respectively as to who receives the alerts.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 45 | 91

In order to analyze trends, applications of the SMC should have a predefined reports menu which includes the ability to download the report data. The reports should have predetermined intervals (monthly), or within date ranges for the managing staff to request. The predetermined intervals (monthly) reports should be retained historically regardless if they are requested. The SMC should provide application security solutions using the extensive set of industry standards and best practices. As an example, contained in the International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC) security guidance for networks (ISO/IEC 27033, ISO/IEC 17099, and ISO/IEC 27002). As a quality assurance measure the SMC and its applications should undergo formal testing, validation, and authentication prior to implementation to provide reasonable assurance of safeguarding the assets and data integrity. The quality assurance measures should include analyzing the application both statically and dynamically for security vulnerabilities, using tools and methods available to developers in order to catch vulnerabilities and identify potential cyber risks. Service Administration and Configuration Application The SMC should provide a means for authorized users to view usage and performance information, or modify user configurations as covered in these Statement of Work sections: 1. SU and RAN Site Registration Monitoring (See Section 3.1.10.2) 2. Alias Database Management (See Section 3.1.10.3) 3. SU Inhibit and Uninhibit (See Section 3.1.10.4) 4. Talk Group Control (See Section 3.1.10.5) 5. Regroup and Cancel Regroup (See Section 3.1.10.6) 6. SU Access Control (See Section 3.1.10.7) 7. Agency / Talk Group Capacity Usage Control (See Section 3.1.10.8) 8. Traffic Data Monitoring, Analysis and Archival. (See Section 3.1.10.9) 9. Text Messaging. If technically feasible, the SMC should provide for authorized users to send and receive text messages to SUs.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 46 | 91

Trouble Ticketing System The SMC should provide a secure web portal to the online trouble ticket system. The SMC should offer visibility into problem management, status of the service requests the user, or managing staff, is authorized to view. (See Section 3.6.8) Network Status Dashboard The SMC should provide a secure web portal to the Network Status Dashboard of the Network Management System information. (See Sections 3.6.3, 3.6.4) SLA Performance Monitoring The SMC should provide a secure web portal to the SLA Performance Monitoring Dashboard. (See Section 3.6.6)

Provide a concise description that demonstrates how the Services Management Center (SMC) and web-based online portals are structured, the functions and features they will contain, the workflow, user authorization and management, how Multi-user / Multi-agency access is provided and the cyber security assurances and safeguards. Explain how the SMC web portal user accounts will be managed, created, authorization, expired, deactivated, and the associated audit provisions. [8 Pages]

SERVICE LICENSING The Service should include all required licenses to utilize the Service at no additional cost to the State. There should be no per-user, per-agency, per-SU licensing cost associated with any offering of the Service for state users, interoperability partners and affiliate users. The Service should permit the quantity of state users, interoperability partners and affiliate users to increase or decrease with no additional charge and any limitation should be based upon technical and performance limits of the Service, not licensing limits. All third-party license costs for Offerorprovided hardware and software should be the responsibility of the Offeror. This section does not apply to the licensing of software features on a SU.

Offeror has read, understands, and will comply with the requirements contained in Attachment F, Special Conditions, Licensing.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 47 | 91

HARDWARE/SOFTWARE UPDATES The Service should be maintained at the latest shipping software release level, unless directed otherwise by the State. The State anticipates the Service’s capabilities will change over the term of the contract, and as such, a goal of the ITN is that the Service should remain current with the latest shipping release. However, it will be at the State’s discretion as to when a software update is to be performed and the State may choose to skip one or more software releases. One goal of the ITN is that all P25 standards-based security related that are currently in the standard developing process, such as P25 link layer encryption, as well as new security related features that have yet to begin the standard development process be provided by the Service at no additional charge to the State when developed and made available by the Contractor to any other customer. The Service should include all costs associated with maintaining the Service at the latest shipping release, including licenses, hardware and labor. Should an underlying subsystem be required to be updated to support the software release, the Service should include all costs associated with updating the subsystem. A subsystem should only be required to be updated when it is necessary for a Service update. Describe the technology refresh plan for the Service including but not limited to: 1. 2. 3. 4.

Current release milestones Planned features and functionality additions Timeframes for planned change in hardware platforms Migration procedures used for release updates.

[750 words]

MOBILE RADIO SYSTEM The State owns two mobile radio systems (MRS) that are used to augment the current system during planned events and can be used to minimize the effects of a catastrophic RAN site failure. These assets along with the associated accessories are to remain the property of the State. Each MRS is comprised of the following: 1. 4-channel (3-working channel) EDACS-EA 800 MHz trunked RAN site (Harris MASTR IIIbased) 2. 4-channel (3-working channel) P25 700 MHz trunked RAN site (Harris MASTRV-based) 3. 20 KW diesel generator set with 80-gallon capacity fuel tank. 4. Two 13,500 BTU HVAC units

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 48 | 91

5. 100 Foot deployable tower An MRS requires the equivalent of a Ford F450 truck with a hitch capable of sustaining 16,000 lbs. with no-load distribution device (standard Ford factory hitch is not suitable). The Contractor should replace the 4-channel (3-working channel) EDACS-EA 800 MHz trunked RAN site with a 5-channel (4-working channel) P25 700 MHz trunked RAN site. The RAN site should operate on the following channels (TX/RX) 1. 2. 3. 4. 5.

Channel 1: 769.23125 / 799.23125 MHz Channel 2: 769.38125 / 799.38125 MHz Channel 3: 769.73125 / 799.73125 MHz Channel 4: 769.88125 / 799.88125 MHz Channel 5: 774.51875 / 804.51875 MHz (Control Channel)

The configuration and programming of the MRS should follow the recommendations of the NPSTC National Regional Planning Council 700 MHz Nationwide Deployable Trunked Solutions Report, October 16, 2015. The existing MRS 700 MHz P25 channels (a separate trunked system from the EDACS-EA system in the MRS) operating on four state-use channels should be able to be integrated into the new 700 MHz trunked system to augment the number of available working channels. If technically feasible, the existing and new P25 700 MHz trunked RAN sites should be capable of being networked into the new Service to allow for wide area communications. If technically feasible, the replacement system should be able to be reconfigured to operate as conventional 700 and 800 MHz mutual aid channels. The Contractor should house and maintain both MRS units. The MRS’s should be housed in the vicinities of Tallahassee and Orlando. MRS’s should be housed in an enclosed storage area and not subject to the weather, however, a conditioned space is not expected. The Contractor should transport, deploy and activate the MRS’s when requested by the State. When requested by the State, the Contractor should deploy the State’s MRS cache consisting of Pelican™ cases of 57 portable SUs, battery chargers and spare batteries with the MRS. The State will retain ownership of the MRS’s and the ownership of the new P25 700 MHz trunked RAN site and associated connectivity shall be transferred to the State upon acceptance.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 49 | 91

Describe the Service’s proposed updates to the State’s MRS units to meet the State’s expectations, including but not limited to: 1. 2. 3. 4.

RAN site upgrades Connectivity additions for networking with the Service Storage facilities description Deployment procedures

[500 words]

SYSTEM TESTING General Prior to cutover, the Service should be fully installed, programmed, made operational, and fully tested by the Contractor according to the agreed upon test scripts, upon which the State should then be notified in writing that the Service is ready for acceptance testing. The implementation schedule should include an appropriate amount of time for the State to witness all such tests. System acceptance testing should consist of factory tests, mechanical installation inspections, field specification tests, field functional and operational tests, and radio coverage tests. The Contractor, in conjunction with the State, should verify that all equipment is fully functional and meets the requirements of the Service’s contract, and has been properly installed per the requirements of the Service’s contract. The Contractor should provide all necessary acceptance test plans, technical personnel, transportation, and test equipment to conduct the performance verification tests. The Contractor should coordinate scheduling of the testing with the State. All deviations, anomalies, and test or specification failures discovered during testing should be documented in a project punch list and remedied by the Contractor in a timely manner. All test results should be recorded in a standardized format to be determined by the Contractor. All recorded test program data should be dated, witnessed, and signed by the designated representatives of State and the Contractor.

Factory Staging and Acceptance Tests The Contractor should provide a factory acceptance test plan and stage all trunked and conventional communication systems and connectivity systems fixed infrastructure equipment at the Contractor’s factory location for conducting a factory acceptance test. The equipment should be made operational as a system and should be factory tested prior to shipment and installation

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 50 | 91

in the field. The State, at their option, may supply representatives to witness the factory staging and testing of the equipment. All equipment should be functional within the factory-staged systems prior to acceptance of the factory acceptance test by State. Connectivity equipment may be staged separately from the trunked and conventional systems at Contractor’s discretion. At staging, all of the infrastructure equipment required to make a fully operational communications system should be assembled into the proposed configuration. As practical, the testing should include all functionality tests (See Section 3.10.3.1), recognizing that some features and functionality cannot be fully tested until the systems are deployed in the field. Each functional test document should include a description, a list of equipment needed to complete the test, a stepby-step procedure for completing the test, and the expected outcome of the test. Propose a methodology for performing factory acceptance test plan that addresses the expectations of the State. The test plan should consider the transition plan and propose solutions in the event the Service is not staged in its entirety. [1000 words] In an attachment, provide a series of proposed test procedures to comprise the factory acceptance test plan.

Service Acceptance Test Plan Contractor should provide a Service Acceptance Test Plan (SATP) for all trunked and conventional communication systems and connectivity systems equipment for establishing the basis of the Service’s acceptance. The SATP should be comprised of service-level functionality tests and site-based tests. Service Functionality Tests Propose a series of tests that will be used to verify that the Service meets the functionality agreed to in the contract. Each functional test document should include a description, a list of equipment needed to complete the test, a step-by-step procedure for completing the test, and the expected outcome of the test. The tests should, as closely as possible, resemble the "real life" application of the Service. Examples of expected tests include: 1. 2. 3. 4. 5. 6. 7.

P-25 features, functionality, programming, and performance Dispatch Console and logging recorder SU roaming Encryption, Authentication, OTAR and OTAP Service failure modes and redundancy tests Location services Interoperability systems

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 51 | 91

8. Administrative controls 9. Network management systems 10. Software and security (SMC, NSD) 11. Trouble ticketing system 12. Mutual aid interface infrastructure 13. SU compatibility testing Propose a methodology for performing functionality tests that addresses the expectations of the State. The test plan should consider the transition plan and propose solutions to demonstrate compliance without the Service being fully constructed. [1000 words] In an attachment, provide a series of proposed test procedures to comprise the Service functionality tests. Site-Based Inspections and Tests Site Inspections and Tests All equipment and installation services provided under the requirements of the Service’s contract should be inspected for compliance to the standards of good engineering practice, all Federal, State, County, and City regulations and codes, and all building codes and ordinances in effect at the sites delineated. Particular attention should be paid to: 1. All installation work performed in a neat and professional manner in compliance with manufacturer’s recommendations 2. All fasteners and hardware tightened and properly torqued 3. All backup power and electrical systems are properly configured and installed 4. All antennas are plumb and of proper orientation 5. All transmission lines are properly installed, labeled, and swept 6. Site free of debris and excavations backfilled, compacted, and restored 7. Towers properly oriented 8. Interior and exterior ground systems properly installed and bonded 9. All SPD devices are appropriate and properly installed and bonded 10. Tower lighting systems fully operational 11. All alarms, circuits, and outlets properly labeled 12. Shelters free from water leaks 13. First aid kits and eye wash stations are installed 14. Fire extinguishers installed The following tests should be performed on the appropriate equipment or structure: 1. Proper operation of site alarms 2. Power distribution panel circuit verifications 3. Proper installation of all lighting (building and tower) and associated switches and controls

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 52 | 91

4. Proper installation and operation of all timers, thermostats, and HVAC systems including cycling of units 5. Proper installation of fire detectors and fire extinguishers 6. Earth ground system test Factory-trained representatives of the emergency power generation system should initially start and verify the system meets the manufacturer’s operational specifications. Upon completion of initial start-up and system checkout, the Contractor should perform a field test to demonstrate load carrying capability and voltage and frequency stability. The Contractor should demonstrate that each emergency power generator will deliver its full rated output power for a period of one hour when connected to a load bank. Emergency power supplies may consist of a combination of DC power plants (rectifiers and batteries), conventional UPS systems providing 120 VAC output from a dedicated battery power source, and UPS systems providing 120 VAC output from power inverters that derive their power from the site’s DC power plant. These tests should include, but not be limited to: 1. Normal operation 2. Simulated power outage to switch to generator 3. Battery/UPS only operation at rated load for specified run times 4. Return to normal operation from the conditions above 5. Maintenance bypass 6. Verification of specified run times The Contractor should provide written and electronic copies of all inspection and test results to the State. Describe the site inspection and testing procedures and special considerations to those procedures to meet the expectations of the State. [250 words] In an attachment, provide the procedures proposed to be used to perform site inspections. Equipment Specification Testing Following equipment installation and system optimization, the Contractor should perform the following tests for each piece of equipment (including any modified and/or relocated existing equipment) to demonstrate the equipment meets the Contractor’s requirements and the State’s expectations. The Contractor should provide written and electronic copies of the test results to the State. Tests should include, but not be limited to: 1. Base stations and repeaters:

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 53 | 91

2. 3.

4.

5.

6.

a. Forward and reflected power at transmitter output b. Forward and reflected power at combiner output c. Insertion loss of combiner d. Receiver threshold sensitivity at the chassis e. Receiver threshold sensitivity through the tower-top-amplifier test port Receiver multi-coupler gain/loss Voting comparator: a. Operational tests to be conducted to verify end-to-end functioning of each channel of each comparator Antenna and transmission line tests: a. All infrastructure site antennas and transmission lines should be tested from the interior of the equipment shelters using Time Domain Reflectometry and a test equipment capable of producing a soft copy of the results on a flash drive in Portable Document Format (PDF). b. The voltage standing wave ratio should be determined at the input connector of the transmission line RF control stations: a. Forward and reflected power at transmitter output b. Proper programming of talk groups/channels, features and functions Connectivity system functionality and performance

Describe the equipment testing procedures and special considerations to those procedures that meet the expectations of the State. [250 words] In an attachment, provide the testing procedures proposed to be used to perform equipment tests.

Coverage Acceptance Testing The State expects that the Service’s radio coverage will be fully tested to validate compliance with contractual requirements. The coverage acceptance test plan (CATP) should be based upon the guidelines contained within TIA TSB-88.3 Revision C. The State expects a high level of confidence in the coverage acceptance testing of the Terrestrial and Maritime Service and Aircraft Service. The State expects the following criteria be part of the CATP: 1. Confidence Level: 99 percent 2. Confidence Interval: 2 percent 3. Service Test Criteria a. For Talk-Out (Service to SU), BER b. For Talk-Back (SU to Service), BER if possible, if not, Subjective Voice Quality 4. Mutual Aid Test Criteria

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 54 | 91

a. For multi-site configured RAN Sites i. For Talk-Out, Signal Strength & Subjective Voice Quality ii. For Talk-Back, Signal Strength & Subjective Voice Quality b. For simulcast RAN Sites i. For Talk-Out, Subjective Voice Quality ii. For Talk-Back, Subjective Voice Quality Propose a coverage acceptance test procedure compliant with the TIA TSB-88.3 Revision C, including the confidence level and confidence interval. Describe possible testing methodologies such that a service with large noncontiguous areas of less-than-desired coverage or spotty coverage would not pass the coverage acceptance test. Describe how coverage testing will consider waterways and waterbodies. Propose procedures for any special performing Maritime testing for areas up to 25 nautical miles from the Florida coastline. Propose procedures that can be used to perform Aircraft Service testing [15 pages]

4 SUBSCRIBER UNITS OPERATIONAL OBJECTIVES Communications Capabilities Objectives Call Processing The subscriber unit should be compatible with a standards-based 700/800 MHz P25 Phase 1/2 Dynamic Dual Mode trunked service. State whether the SU meets the State’s expectations for call processing and describe the SU’s compatibility with standards-based P25 systems from various manufacturers. [100 words] Communications Types SUs should support group calls, individual calls, emergency group calls and alerts. State whether the SU meets the State’s expectations for communications types and describe the SU’s compatibility with standards-based P25 systems from various manufacturers. [100 words]

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 55 | 91

Messaging The SUs may provide users with a means to transmit and receive messages from another. Messages may be free-form alphanumeric text messages, and pre-programmed short messages, status updates, status requests and call alert. State whether the SU meets the State’s expectation for messaging and describe the SU’s compatibility with standards-based P25 systems from various manufacturers. [250 words] Scanning The SU should be capable of scanning conventional channels, Service talk groups, or a combination of conventional channels and Service talk groups. The SU should have a means for a user to temporarily remove a channel or talk group from the scan list (i.e., “Nuisance Delete”). The SU should have a means to restore the scan list back to its original condition. The SU should be capable of setting one or more talk groups with a higher scan priority such that when there is activity on the priority talk group, the SU will switch to that talk group even if the SU is actively receiving traffic from a non-priority talk group. The SU should be capable of scanning talk groups that have been patched together by the Service and to scan channels operating in direct mode (i.e., talkaround mode). Describe how the SU provides scanning capability and any limitations of the SU to meet the State’s expectations for scanning. Describe the SU’s compatibility with standards-based P25 systems from various manufacturers. [250 words]

Service Capabilities Requirements The SUs should support a service that utilizes multisite and simulcast RAN site configurations. For simulcast RAN site configurations, the SU should support a service that utilizes linear simulcast technology. The SU should support a P25 SU ID range of 1 to 15,000,000 or higher. SUs should transmit its SU ID when making a transmission. SUs should support adequate quantity of systems, talk groups and channels to accommodate statewide operation, including roaming with automatic changing of talk groups (See Section 5). In addition to having adequate capacity for statewide operation on the Service, SUs should also have adequate capacity to support the programming of multiple P25 trunked systems utilized by

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 56 | 91

local agencies and up to 64 conventional interoperability channels in repeater mode and direct mode. State whether the SU meets the State’s expectation for the SU’s compatibility with the Service technology and describe the SU’s compatibility with standards-based P25 systems from various manufacturers. Describe the capacity of the proposed SUs to support statewide operation on the Service, multiple P25 trunked systems utilized by locals and up to 64 conventional interoperability channels in repeater mode and direct mode. [500 words]

Wide Area Communications Terrestrial and Maritime Service Roaming SUs should be capable of roaming between various RAN sites while operating on the Service as well as other systems for interoperability purposes. The roaming process should be as automatic as possible and require very little or no interaction by the end user. The SU should be able to automatically register with the Service quickly, especially in the situation where a SU was powered down, transported to a different area of the state, and powered back on. From a service agnostic perspective, describe how the proposed SUs perform roaming on land mobile radio systems and the expected SU registration timeframes.[500 words] Aircraft Service Roaming With the current service, when the aircraft are on the ground, the aircraft SUs are registered with the current Terrestrial and Maritime RAN sites as they do not generally have coverage from the existing Aircraft Service RAN sites. When the aircraft reaches altitude, the users manually switch the SUs to the existing Aircraft Service RAN sites. The SUs do not automatically roam between the current Aircraft Service RAN sites. The SUs should provide comparable roaming functionality as the current service. However, if technically feasible, the process of roaming between the Terrestrial and Maritime Service (when on the ground or at low altitude) and the Aircraft Service (when at altitude) and between Aircraft Service RAN sites should be automatic and therefore not require user intervention. The Service should provide the option for the State to enable SUs to automatically roam between the Aircraft Service RAN sites.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 57 | 91

From a service agnostic perspective, describe how the SUs perform roaming and how the SUs can automatically roam between the Terrestrial and Maritime Service and Aircraft Service. [500 words]

Encryption and Authentication The SU should encrypt all communications calls as determined by the State. The SU should support AES-256 for compatibility with the Service and may support DES for interoperability purposes. The SU should be able to support multiple encryption keys where individual talk groups or groups of talk groups are encrypted with unique encryption keys. The SU should authenticate with the Service based upon P25 standards-based Link Layer Authentication. If supported, the SU should participate in mutual authentication (Service to SU and SU to Service). The SU should support loading and changing of encryption keys by a FIPS 140-2 certified key fill device. The SU should support P25 standards-based OTAR of encryption keys to provide the State a means to change the encryption keys without having to physically touch a SU. Describe, from a service agnostic perspective, the methodology the proposed SU utilizes to provide the following: a) Encryption of communications calls including support for AES and DES encryption algorithms and support for multiple encryption keys b) Manual loading and changing of encryption keys c) OTAR [250 words] Describe, from a service-agnostic perspective, the SUs ability to support P25 standards-based Link Layer Authentication and level of support for mutual authentication. [125 words]

Failure Modes The State is expecting to contract for a Service based upon a high availability/high reliability system providing resilience and tolerance to component and connectivity failures. Insofar as practical, the State expects the Service to maintain trunked and wide area operation and provide for a graceful degradation of trunking when a critical threshold of trunking and connectivity resources are lost.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 58 | 91

However, failures are possible and the SUs should be compatible with the Service to maintain mission critical communications as long as possible. The SU may be required to operate from RAN sites that are disconnected from the Service and therefore operating in a “site-trunking” mode. The SU may also be required to operate from a RAN site that has failed to a conventional mode (i.e. “failsoft”). Describe the SU’s operations and compatibility with various P25 system manufacturer’s failure modes specifically for site trunking and failsoft modes. [500 words]

Location Services The SU may provide the means for SU to transmit its geographic locations to other SUs and applications. The SU’s location service should be in accordance with P25 standard for Tier 2 Location Services. The SU should support the configuration of location update triggers by the Service. The SU should support the following location update triggers: a. b. c. d. e. f. g.

PTT Periodic Emergency Power On/Off Host Request User Request Distance Change

If technically feasible, portable SUs be configurable to not transmit its location when within a defined distance to a mobile SU that has been associated with the portable SU. The intent is to eliminate both a user’s portable SU and mobile SU sending location information at the same time when they are in close proximity as a means to reduce the location service traffic on the system. Describe the SU’s location service capabilities and compatibility with P25 systems from various manufacturers. [500 words]

Over the Air Programming The SUs should support the ability to be reprogrammed over the air via a standards-based P25 data call. If supported, the SUs should be capable of being reprogrammed over broadband type systems such as Wi-Fi™ and cellular-type (e.g. LTE) systems. If technically feasible, the SUs should be capable of transmitting information regarding its current personality programming,

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 59 | 91

feature set and encryption over the air to the OTAP server and/or Fleet Management Application (See Section 4.1.11.2) for review by authorized users. Describe the SU’s over the air programming capabilities including support for being reprogrammed over broadband type system such as Wi-Fi™ and cellular-type (e.g. LTE) systems. Describe the SU’s capability of transmitting information regarding its personality programming, feature set and encryption over the air.[250 words]

Administration and Control Radio Check The SU should support radio checks to allow authorized users of the Service to verify the availability of the SU on the network. Indicate if the SU supports P25-standards based radio check functionality. [50 words] Inhibit and Uninhibit The SU should allow authorized users of the Service to inhibit the SU from operating on the system and to place the SU in a mode that appears to be powered off. The SU should also allow authorized users of the Service to uninhibit a SU. This function should be in accordance with P25 standards. Indicate if the SU supports P25-standards based inhibit and uninhibit functionality. [50 words] Regroup and Cancel Regroup The SU should allow authorized users of the Service to dynamically change the talk group affiliation (a.k.a. regroup) of the SU without requiring interaction by the users. The SU should allow authorized users of the Service to cancel the regroup to return SU to their originally affiliated talk group. Describe the SU support for regroup and cancel regroup. [150 words] SU Access Control The SU should be compatible with a Service that restricts SUs to certain RAN sites, certain talk groups and certain types of calls. In the event the Service restricts the SU from performing a function that is programmed into the SU, the Service should notify the SU and the SU should emit a talk-prohibit tone notifying the user that the operation is not permitted by the Service.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 60 | 91

Describe the SU support for service-based restrictions. [150 words]

SU Performance Specifications The SU should be FCC type-accepted for its application. The SU should meet the performance standards, specifications and recommendations as specified in TIA-102.CAAB, TIA-102.CCAB and TIA-603E. The SU should meet the technical requirements of the Florida Law Enforcement Communications Plan for Option A equipment. The SU should have passed the test cases listed in the appropriate Project 25 Compliance Assessment Bulletin for SUs and have a Supplier’s Declaration of Compliance and Summary Test Report on file with the DHS and listed by DHS as eligible for grant procurement. Indicate if any proposed SU does not meet the State’s expectations for performance and describe any deviations. [250 words] In an attachment, provide product data sheets for each proposed SU. Include copies of the Project 25 Compliance Assessment Program Supplier’s Declaration of Compliance and Summary Test Report for each proposed SU.

SU Feature Specifications The SU should offer a night-mode or covert-mode such that all lights and displays on the SU are turned off. If technically feasible, the SU should display the alias of the caller in lieu of the caller’s SU ID, be managed by and not require provisioning by the user. Upon a user activating the emergency alert, the SU should automatically place an emergency group call without requiring the user to press the PTT, referred to as “Hot Mic”. If technically feasible, the length of time the SU maintains the Hot Mic should be configurable. If technically feasible, the SU should have a user programmable button to allow the user to return quickly to its home system and talk group, bypassing the need for menu selection. If technically feasible, the SU should be able to operate in an encrypted direct mode (talk-around) while scanning system talk groups for activity.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 61 | 91

Indicate if any proposed SU does not meet the State’s expectations for features and describe any deviations. [250 words]

SU Programming Programming Security With the current service, the creation of a personality for the SUs is restricted to one individual to protect against unauthorized access to restricted talk groups and functionality. If technically feasible, a means should be provided to allow individual agencies control over the personality development and programming of their subscribers, however, the capabilities as to what the agency is allowed to program should be able to be configured. At a minimum, the SU should provide a means to restrict programming or modifications to the programming of the Service. The SU should also provide a means to restrict the reading of the personality from the SU and/or restricting the ability to decode a personality after it has been read from a SU. If technically feasible, a physical device, such as a dongle, should be required to physical program a SU to operate on the Service, or to read or modify the SU’s programming. If technically feasible, the dongle should be able to be provisioned with rights to allow only specific operations to be performed. If technically feasible, dongles should be required to remotely re-register on a regular basis to validate that no provisioning changes to the dongle’s programming rights have been changed. If technically feasible, the SU should store information that identifies the user who last programmed the SU and provide this information to authorized users through a remote operation. Describe how the programming of the SU and the programming of the SU into the personality can be restricted only to authorized users. Describe how the reading of a personality can be restricted only to authorized users. Describe any methods that can be utilized to allow individual agencies to develop and program their own subscribers while limiting what the agency is allowed to program. Describe the physical security device that can be used to provide security in the programming of the SUs. [500 words] Programming and Fleet Management Application The Offeror should offer a user-friendly programming application(s) for the development and deployment of SU personalities and management of SU firmware. The application should support creating personalities from templates. If technically feasible, the application should allow for authorized users to remotely retrieve information regarding the personality programming, feature set and encryption keys from an SU for verification and auditing purposes.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 62 | 91

The application should support fleet management functionality such that the agencies can track the programming of each SU. The application should provide detailed reporting on SU programming and firmware revisions. If technically feasible, the application should support multiple users and agencies. Describe the programming and fleet management applications and support for Multi-user / Multi-agency. [500 words]

SU LICENSING The State is interested in the ability to upgrade and/or replace SUs and not repurchase licensed features that were previously purchased for the SU being replaced, regardless of the models of the SUs.

Describe the upgrade and replacement offering that would allow the State to upgrade and/or replace SUs without requiring the repurchase of licensed features that were previously purchased for the SU being replaced, regardless of the models of the SUs. [250 words]

5 ROAMING WITH AUTOMATIC CHANGING OF SUBSCRIBER MODE Depending upon the agency, the current SUs utilize one of two methods of automatically change the subscriber mode (i.e., bank, zone, system) while roaming. If technically feasible, the Service and/or SUs should provide similar functionality. The following subsections provide an explanation of the two methods the current service and SUs provide for roaming with automatic changing of subscriber mode. These explanations are provided for informational purposes only so the Offeror can fully understand the State’s expectations and is not intended to indicate how the Service should implement the functionality.

Roaming Method A The State operates seven RCCs and each RCC is responsible for a portion of the state. For agencies that utilize Roaming Method A, as users roam across RCC jurisdictional boundaries, their talk group communications “automatically” switches to the appropriate RCC. When a user is in their home jurisdiction and their SU is on Talk Group 1, they are in communications with their home RCC. When they roam into a neighboring jurisdiction and without interacting with the SU, they start communicating with the neighboring RCC on one of that RCC’s talk groups. This is accomplished solely through the programming of the SU. From a simplistic perspective, each RAN site entry in the SU programming contains a list of the talk groups the SU is authorized to

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 63 | 91

utilize at the site and each talk group entry is associated with a position on the SU’s selectors. By changing the talk group assigned to a particular selector position, the SU can change talk group affiliations as it roams between RAN sites. For the purpose of explanation, assume that there are two RCCs; RCC A and RCC B and within each RCC’s jurisdiction, there are three RAN sites (Sites 1, 2 and 3 are in RCC A’s jurisdiction and Sites 4, 5 and 6 are in RCC B’s jurisdiction). This is shown below in Figure 1.

Figure 1 - SU Roaming Example

Assume that there are also three talk groups on the system for each RCC jurisdiction (A-TG1, ATG2 and A-TG3 are in RCC A’s jurisdiction and B-TG1, B-TG2 and BTG-3 are in RCC B’s jurisdiction). From a simplistic perspective, within the programming of an SU, there is a list of RAN Sites and eligible talk groups as shown below in Table 1: Table 1 - SU Roaming Personality, Basic Configuration

RCC A Jurisdiction

RCC B Jurisdiction

SU Talk Group Selector Position

Site 1

Site 2

Site 3

Site 4

Site 5

Site 6

1

A-TG1

A-TG1

A-TG1

B-TG1

B-TG1

B-TG1

2

A-TG2

A-TG2

A-TG2

B-TG2

B-TG2

B-TG2

3

A-TG3

A-TG3

A-TG3

B-TG3

B-TG3

B-TG3

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 64 | 91

If a user has selected position 1 on their SU and are in RCC A’s jurisdiction, as they roam within their home RCC’s jurisdiction, they will always remain on talk group A-TG1 and will be in contact with a dispatcher at RCC A. However, when they roam into RCC B’s jurisdiction, the SU affiliates (switches) to talk group B-TG1 because it’s the talk group in position 1. Because radio coverage doesn’t perfectly fit within the RCC’s jurisdictions, the SU programming for users primarily operating in RCC A’s jurisdiction is modified to allow for talk groups from RCC A be eligible on Site 4 (the first site into RCC B’s jurisdiction) and, therefore, the SU does not switch to talk group B-TG1 until it registers with Site 5 as shown below. This is accomplished by creating two Site 4’s in the SU (one with RCC A’s talk groups and one with RCC B’s talk groups) with the same Site ID as shown below in Table 2: Table 2 - SU Roaming Personality, Enhanced Configuration 1 for SUs in RCC A’s Jurisdiction

RCC A Jurisdiction

RCC B Jurisdiction

SU Talk Group Selector Position

Site 1

Site 2

Site 3

Site 4A

Site 4B

Site 5

Site 6

1

A-TG1

A-TG1

A-TG1

A-TG1

B-TG1

B-TG1

B-TG1

2

A-TG2

A-TG2

A-TG2

A-TG2

B-TG2

B-TG2

B-TG2

3

A-TG3

A-TG3

A-TG3

A-TG3

B-TG3

B-TG3

B-TG3

The roaming algorithm of the SU incorporates a list of sites the SU should scan and the list varies based upon with which site the SU is currently registered. In the example, for SUs operating on Site 3, the SU scans Site 2 and Site 4A and not Site 4B. Therefore, the SU can continue to communicate on RCC A’s talk groups even while in RCC B’s jurisdiction. For this to be reciprocal for users that are associated with RCC B, Site 3 is also split into Site 3A and 3B. The valid site scan list for the example is shown below in Table 3 (this example is based upon a simple geographically linear network as shown in Figure 1.)

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 65 | 91

Table 3 – SU Valid Site Scan List

RCC A Jurisdiction

RCC B Jurisdiction

Valid Site Scan List

Site 1

Site 2

Site 3A

Site 3B

Site 4A

Site 4B

Site 5

Site 6

1

Site 2

Site 1

Site 2

Site 4B

Site 3A

Site 5

Site 6

Site 5

Site 3A

Site 4A

Site 2

Site 5

Site 3B

Site 4B

2

A final modification to the programming of some agencies’ SU is made to allow a user to manually change to a RAN site “two-sites-in” to allow users to communicate with RCC A even further into RCC B’s jurisdiction, and vice versa. The SU will not automatically roam to this duplicate site and must be manually selected by the user, therefore, the valid site scan list shown in Table 3 does not change. The updated SU roaming personality is shown below in Table 4. Table 4 - SU Roaming Personality, Enhanced Configuration 2 for SUs

RCC A Jurisdiction

RCC B Jurisdiction

SU Talk Group Selector Position

Site 1

Site 2A

Site 2B

Site 3A

Site 3B

Site 4A

Site 4B

Site 5A

Site 5B

Site 6

1

A-TG1

A-TG1

B-TG1

A-TG1

B-TG1

A-TG1

B-TG1

B-TG1

B-TG1

B-TG1

2

A-TG2

A-TG2

B-TG2

A-TG2

B-TG2

A-TG2

B-TG2

B-TG2

B-TG2

B-TG2

3

A-TG3

A-TG3

B-TG3

A-TG3

B-TG3

A-TG3

B-TG3

B-TG3

B-TG3

B-TG3

If technically feasible, the Service and/or SUs should provide for the equivalent functionality as this is was implemented to accommodate how the state agencies operate. Describe the methodology the proposed Service and/or SUs will utilize to facilitate the roaming requirements of Roaming Method A. Indicate if the proposed methodology relies only on P25standard features, which P25-standard features are implemented, and that the methodology will be compatible with SUs from other manufacturers assuming those manufacturers have implemented the required P25-standard features. [1500 words]

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 66 | 91

Roaming Method B The agency that utilizes Roaming Method B uses a talk group scanning configuration aligned with the agency’s regional boundary to provide users the ability to maintain communications with their home region, to monitor both the home and neighboring region’s talk groups while in a border area and to switch to a neighboring region when they traverse far enough into a neighboring region’s jurisdiction. In this configuration, when “deep-within” their home region’s regional boundary, the users can scan only their home region’s talk groups and likewise, when “deep within” their neighboring region’s regional boundary, the users can scan only their neighboring region’s talk groups. Along the regional boundaries, users scan both the home region talk groups and the neighboring region talk groups. For the purpose of explanation, assume that there are three regions, Region A, Region B and Region C, and within each region’s jurisdiction, there are three RAN sites (Sites 1, 2 and 3 are in Region A’s jurisdiction, Sites 4, 5 and 6 are in Region B’s jurisdiction and Sites 7, 8 and 9 are in Region C’s jurisdiction). When registered to RAN sites within approximately 30-miles of the boundary of two or more RCCs, SUs are configured to scan both the home and neighboring RCCs’ talk groups. See Figure 2 below.

THIS SPACE INTENTIONALLY LEFT BLANK

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 67 | 91

Figure 2 - Roaming Method B Example

Assume that there are also three talk groups on the system for each region’s jurisdiction (A-TG1, A-TG2 and A-TG3 are in Region A’s jurisdiction, B-TG1, B-TG2 and BTG-3 are in Region B’s jurisdiction and C-TG1, C-TG2 and C-TG3 are in Region C’s jurisdiction). Within the programming of an SU for each RAN Site, there is a list of talk groups for each SU bank. There are four banks programmed (A through D) though only Banks A through C are shown. See Table 5 below. Note that the talk group entries are representations of talk group identifiers (TGID) and the display name that is shown on the SU is customizable by site, bank and talk group position. For this example, the talk group scan list for each RAN Site is customized for only the talk groups that are programmed for the particular RAN Site and are denoted in bold text.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 68 | 91

Table 5 – Roaming Method A SU Roaming Personality, Basic Configuration

Sites in Region A’s Jurisdiction SU Talk Group

Site 1

Site 2

Site 3

Bank A

Bank B

Bank C

Bank A

Bank B

Bank C

Bank A

Bank B

Bank C

1

A-TG1

A-TG1

A-TG1

A-TG1

A-TG1

C-TG1

A-TG1

B-TG1

A-TG1

2

A-TG2

A-TG2

A-TG2

A-TG2

A-TG2

C-TG2

A-TG2

B-TG2

A-TG2

3

A-TG3

A-TG3

A-TG3

A-TG3

A-TG3

C-TG3

A-TG3

B-TG3

A-TG3

Sites in Region B’s Jurisdiction SU Talk Group

Site 4

Site 5

Site 6

Bank A

Bank B

Bank C

Bank A

Bank B

Bank C

Bank A

Bank B

Bank C

1

A-TG1

B-TG1

B-TG1

B-TG1

B-TG1

B-TG1

B-TG1

B-TG1

C-TG1

2

A-TG2

B-TG2

B-TG2

B-TG2

B-TG2

B-TG2

B-TG2

B-TG2

C-TG2

3

A-TG3

B-TG3

B-TG3

B-TG3

B-TG3

B-TG3

B-TG3

B-TG3

C-TG3

Sites in Region C’s Jurisdiction SU Talk Group

Site 7

Site 8

Site 9

Bank A

Bank B

Bank C

Bank A

Bank B

Bank C

Bank A

Bank B

Bank C

1

A-TG1

C-TG1

C-TG1

A-TG1

B-TG1

C-TG1

C-TG1

C-TG1

C-TG1

2

A-TG2

C-TG2

C-TG2

A-TG2

B-TG2

C-TG2

C-TG2

C-TG2

C-TG2

3

A-TG3

C-TG3

C-TG3

A-TG3

B-TG3

C-TG3

C-TG3

C-TG3

C-TG3

With this programming, when a SU is registered to Site 1 and the SU is operating on Bank A, talk group position 1 (A-TG1) it is scanning talk groups A-TG2 and A-TG3 for activity. As the user travels toward Region B’s jurisdiction and the SU roams onto Site 3, it begins to also scan talk groups B-TG1, B-TG2 and B-TG3. As the user enters into Region B’s jurisdiction and roams onto Site 4, it continues to scan talk groups A-TG1 through B-TG3 but stays affiliated with talk group

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 69 | 91

A-TG1 because it’s in talk group position 1. However, when the user reaches Site 5, the SU affiliates with talk group B-TG1 (again, because it’s in talk group position 1 on Bank A) and it begins to scan only the talk groups associated with Region B (B-TG1, B-TG2 and B-TG3). Through this means, users are able to roam with automatic talk group changes in a similar manner as users utilizing Roaming Methodology A with the exception that they are able to monitor both RCC’s talk groups when operating in border areas. The ability to monitor all border region’s talk groups while in a border area is very important to the agency that utilizes this roaming mode. The simplified example showed the configuration for three regions though the agency that utilizes this roaming methodology has six regions. However, the agency utilizes only three banks (Bank A, B and C) in their SUs and reuses the bank designation throughout the state. Bank D in the SU is programmed for interoperability talk groups and though statewide interoperability talk groups are consistently programmed for every RAN site, regional interoperability talk groups may change on a site by site basis. Regardless, they are generally not included in the scan list unless specifically added by the user. Describe the methodology the proposed Service and/or SUs will utilize to facilitate the roaming requirements of Roaming Method B. Indicate if the proposed methodology relies only on P25standard features, which P25-standard features are implemented, and that the methodology will be compatible with SUs from other manufacturers assuming those manufacturers have implemented the required P25-standard features. [1500 words]

Enhanced Local Mode and Travel Mode In addition, if technically feasible, the Service provide an enhancement to the roaming as described above and specifically, that the SU or Service have two modes: an enhanced local mode and a travel mode. In the enhanced local mode, the SU/Service behaves as described above but is capable of operating more than “one-site-in” into a neighboring jurisdictional boundary. It is desired that the Service be configurable such that the State can determine, based upon operations, how far into another neighboring RCC that the SUs can roam without changing modes. In the travel mode, the SU/Service behaves as described in Table 1 where the SU switches to the neighboring RCC immediately upon registering with a RAN site in RCC B’s jurisdiction. This allows users that are travelling across the state to stay in contact with the appropriate dispatch center for the area they are in. Ideally, this would occur based upon geographic location of the SU and not depend upon RAN site registrations (i.e., as soon as the SU crosses the jurisdictional boundary).

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 70 | 91

Describe the methodology the proposed Service and/or SUs will utilize to facilitate the roaming requirements of enhanced local mode and travel mode. Indicate if the proposed methodology relies only on P25-standard features, which P25-standard features are implemented, and that the methodology will be compatible with SUs from other manufacturers assuming those manufacturers have implemented the required P25-standard features. [1500 words]

6 TECHNOLOGY EVOLUTION The current SLERS users have indicated a desire for feature and functionality from the Service that cannot be readily provided for by traditional land mobile radio systems due to the limited bandwidth of the communications channels and other technical challenges. During the term of the Service’s contract, technology may exist that allows for the convergence of mission critical push-to-talk voice communications and mission critical data communications. The Service may advance with the evolution through the adoption of broadband to facilitate integration with local agencies’ next generation of mission critical communications. Though the timeframe for such convergence is uncertain, it is realistic to plan for it to occur during the term of the new Service and, as such, the Service should be flexible to permit this. The Service may also provide a means to allow for non-mission critical voice and data communications that operate over current broadband networks. This may be in the form of an application that operates on smartphones and computers that provide IP-based communications with other users on the Service. Should this capability be provided, the offering shall meet the expectations of the State with regards to service licenses (See Section 3.7). Describe how the proposed Service and SUs can facilitate the convergence of state users into a single, standards-based shared communication system and leverage the resources associated with next generation of mission critical communications technology. Describe how the Service and SUs could take advantage of private and public broadband networks to support mission critical communications. Describe how a transition from an LMR-based service to a new Service technology, such as broadband, can be performed. Describe how the following resources deployed to support an LMR-based service can be leveraged to support a new Service based upon different design requirements and/or how the resources can be salvaged when no longer required: 1. 2. 3. 4. 5. 6.

Radio Access Network Core Network Connectivity Network Dispatch Equipment Interoperability Facilities

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 71 | 91

7. Mobile Radio System 8. Mobile SUs 9. Portable SUs [1000 words] Describe capability to provide a non-mission critical voice and data application that utilizes current broadband networks to provide IP-based communications with other users of the Service. Describe licensing requirements, excluding cost, for the end-user application. [750 words]

7 TRAINING This section describes the types of training. The methods and logistics for the delivery resides under the Project Management Training Plan. When the training events are to occur, materials prepared, it is to be coordinated with the overall project schedule to be completed on a timely basis to be most effectual. The State has engineering and technical staff assigned to the SLERS system who will need to increase their competencies with the functions of the new or upgraded system for them to continue to effectively perform their responsibilities. The user organizations will face similar challenges with a new system, learning how to best operate the features and functions. Gaining experience will come with time, although with a mission critical system how the Offeror can best position the law enforcement officers, dispatch centers, user organizations to be ready for the transition should be made clear. The types of training for the targeted stakeholders group, the intended number of attendees, and frequency is to be identified.

SERVICE TRAINING State User Training The Contractor should provide training on the administration and control of the Service and training on the Dispatch Consoles. Administration and control training, interoperability training and Dispatch Console training should be provided in computer-based training format and in person training seminars. The training should be comprehensive and detailed and provide all information and instructions necessary for a user to fully utilize the Service.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 72 | 91

The State expects that the Contractor will provide customized training curriculums, for both computer-based training and training seminars, for Dispatch Consoles for each of the four state agencies that utilize Dispatch Consoles based upon their unique operations. Computer-based training should be web-based and if technically feasible, not require the installation of browser plugins. Training seminars should be provided at each RCC to minimize travel time for state personnel. A goal of this ITN is that Dispatch Console training utilize actual Dispatch Console operating on a functional system supporting SUs so that the training reflects an operational environment to the greatest extent possible. Describe the Service’s training curriculum and how the Dispatch Console training will be customized to operations of each of the four state agencies that utilize Dispatch Consoles. Describe how the computer-based training will be provided. Describe how the training seminars will be provided and any special requirements for the training seminar locations that the Offeror expects the State to accommodate [2000 words]

Technical Training The Offeror should provide training on the design, engineering and operations of all elements of the Service to state technical personnel. The training should be detailed and in-depth so that the technical personnel fully understand the operational theory of the Service, how the Service was designed, how the Service was configured and provisioned and how the Service is maintained, including troubleshooting and repair procedures. The State expects that this training will involve multiple sessions with specific topics. The State expects that some training sessions can be accomplished through computer-based training while others will required training seminars. A goal of this ITN is that hands-on training be on a functional system supporting Dispatch Consoles and SUs. Training seminars should be provided at a minimum of three state-provided locations throughout the state to minimize travel time for state technical personnel. Describe the Service’s technical training curriculum. Describe how the computer-based training will be provided. Describe how the training seminars will be provided and any special requirements for the training seminar locations that the Offeror expects the State to accommodate [2000 words]

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 73 | 91

SU TRAINING State User Training The Contractor should provide training on the operation of the SU. Training should be provided in computer-based training format and in person training seminars. The training should be comprehensive and detailed and provide all information and instructions necessary for a user to fully utilize the SU with the Service. The State expects that the Contractor will provide customized training curriculums, for both computer-based training and training seminars, for SUs for each of the seven state Joint Task Force (JTF) agencies based upon their unique operations and in particular, their wide-area roaming with automatic changing of talk group functionality. Computer-based training should be web-based, online and if technically feasible, not require the installation of browser plugins. Training seminars should be provided at each RCC to minimize travel time for state personnel. The training seminars should follow a train-the-trainer format. A goal of this ITN is that training utilize actual SUs operating on a functional system supporting Dispatch Consoles so that the training reflects an operational environment to the greatest extent possible. Describe the Service’s training curriculum and how the SU training will be customized to operations of each of the seven state JTF agencies. Describe how the computer-based training will be provided. Describe how the training seminars will be provided and any special requirements for the training seminar locations that the Offeror expects the State to accommodate [1500 words]

Technical Training The Contractor should provide training on the programming and provisioning of the SUs to state technical personnel. The training should be detailed and in-depth so that the technical personnel fully understand how to create SU programming personalities, how to program and change the encryption keys in the SUs and how to troubleshoot SU operations. The State expects that some training sessions can be accomplished through computer-based training while others may require training seminars. A goal of this ITN is that hands-on training be on a functional system supporting Dispatch Consoles and SUs. Training seminars should be provided at a minimum of three state-provided locations throughout the state to minimize travel time for state technical personnel.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 74 | 91

Describe the Service’s technical training curriculum. Describe how the computer-based training will be provided. Describe how the training seminars will be provided and any special requirements for the training seminar locations that the Offeror expects the State to accommodate. [1500 words]

8 PROJECT MANAGEMENT PLAN The Offer shall provide project management services in accordance with the Florida Agency for State Technology (AST), Chapter 74-1 of the Florida Administrative code for Project Management.

Staffing Assign a full-time Project Manager (PM) to oversee and take on the responsibility for the success of the project. This individual should be the point of contact to the State, and should coordinate all work and communications with the DMS. This individual should manage and direct the planning of the Contractor’s staff and resources. The Project Manager should possess a thorough knowledge of the scope of the project and components to be provided by the Contractor, and be well experienced in project management. The Contractor’s PM will be required to pass a criminal justice background screening. The Project Manager is subject to DMS approval and continual review. Provide a staff of experienced professionals and subject matter experts for design and support as part of the response. The staff assigned to the SLERS project will be dedicated, full-time resources. These dedicated staff are to remain on the SLERS project for its duration or until their work is completed. The staffing plan should also identify auxiliary personnel who will be engaged part-time and what percentage; and for the sub-contracted personnel listing their estimated involvement and what percentage.

DMS Role DMS’s role is to oversee and review work Contractor performs on the project ensure best practices are followed, risks are identified and mitigated, issues are properly identified and communicated, contractual obligations are met, deliverables meet or exceed quality standards, rigorous methodologies and controls are in place. The role of DMS staff is operational and contractual oversight. If there are task dependencies requiring action by DMS or user agency technical personnel, including the SLERS Security Manager, the Offeror should make sure those tasks are defined. The Contractor should facilitate DMS carrying out the tasks and activities the Contractor is depending on DMS to perform. For areas where task interdependencies exist involving the stakeholders, the Contractor should advise DMS with a description of the task, timeframe and level effort for the work. Managing the work and adhering to the project schedule is the responsibility of the Contractor.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 75 | 91

Propose a detailed Project Management Plan based upon the scope of this ITN and to meet the objectives and on-going support of the contract. The Project Management Plan should be specifically for SLERS and be in accordance with the AST, Chapter 74-1 of the Florida Administrative code but not limited to the following within the plan: 1. Dedicated and Supporting Resources a. Contractor/Vendor b. DMS Role c. State Agencies Role d. Partner Agencies Role 2. Communications Plan 3. Work Breakdown Structure a. Schedule b. Design c. Implementation d. Support e. Key Phase build-out Milestones 4. Risk Analysis and Management Plan 5. Safety Plan 6. Security Plan 7. Quality Assurance Plan 8. Change Management Plan 9. Contract(s) Management 10. Training Plan 11. Implementation Plan 12. Maintenance Plan [15 pages]

9 TRANSITION PLAN DMS requires a detailed Transition Plan that defines the proposed activities that will be completed during the SLERS implementation. Should the Offeror propose utilization of existing resources the Transition Plan should explain how these resources will be leveraged in the transition of the implementation. The Transition Plan should include, but not be limited to: 1. No loss of Regional Communications Center hand-off capability (i.e., at all times, at least two centers operating on each service at the start of the transition and to the end of the transition). 2. No loss of radio coverage during any time. 3. Maintenance of capacity Grade of Service at all times with consideration of public safety user base. 4. No loss of basic mission critical functionality including, but not limited to, group calls, emergency group calls and alerts, and transport of talking party identification.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 76 | 91

5. Minimization of risk. “When scoring proposals, the department shall consider, among other factors, any respondent’s ability to leverage existing resources to the public’s best interest.” Section 2838, Chapter 201666, Laws of Florida.

Propose a detailed Transition Plan based upon the scope of this ITN and meets the transition objectives. Describe but not limited to the following within the plan: 1. Existing and New Resource Allocation 2. Transition and Preparation Planning a. Impact Analysis b. Stakeholder Communications Plan 3. Transition Management a. Engineering Plan b. System build out c. Acceptance (phase/final) d. Migration Cutover Plan e. Fallback Plan 4. Network Support a. Network Operation Center b. Support Services 5. Training – cross reference Training section a. Consoles b. Subscriber units c. DMS d. Agencies [8 pages]

10 DISASTER RECOVERY PLAN To ensure events that are beyond the control of the Contractor are properly handled, a Disaster Recovery Plan will be established in support of SLERS. Propose a detailed Disaster Recovery Plan that addresses but not limited to the following: 1. Plan Objectives 2. Assumptions 3. Definition of Disaster 4. Recovery Teams 5. Team Responsibilities

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 77 | 91

6. Plan Utilization (Invoking) 7. Internal and External Communications 8. Federal, State, Local Roles and Responsibilities 9. Services Restoration 10. Support Timeline Describe the Disaster Recovery Plan. [3 pages]

11 PERFORMANCE MEASURES SLERS will provide system performance, service delivery, and operational service level commitments to meet performance requirements. These commitments shall be based upon guaranteed restoral times and other performance measures, with associated service credits for Contractor non-compliance. Attachment D, Service Level Agreements, consists of: 1. 2. 3. 4. 5. 6.

SLA Requirement; Performance target; SLA Failure Level; Financial consequence for non-performance; SLA details, measurement and violation criteria; and Service applicability.

The term “SLA performance monitoring application” is used to indicate a system that receives information on outages, degradation and other SLA requirements, then provides notifications to users and opens SLA-related tickets. The ITN does not specify how the SLA performance monitoring service interfaces with other system tools or functions that provide system monitoring and management. Service maintenance windows will be granted periodically for system maintenance activities such as hardware and software changes. All service maintenance is to be scheduled and approved by DMS 30 days in advance of the requested maintenance window. DMS reserves the right to deny the maintenance window at its sole discretion. In addition to Attachment D, Service Level Agreements, listed below are requirements associated with SLERS SLAs. 1. The Contractor is required to provide and comply with SLAs defined in Attachment D, Service Level Agreements. 2. SLAs and related service credits are cumulative (applied for each incident). SLA credits restart each month based on the review process and monthly billing cycle.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 78 | 91

3. SLAs are calculated, measured, and paid per incident. 4. Unless there is an explicit reference to “weekdays,” all SLA SLER credits are applicable based on calendar days. 5. Tickets based on phone calls or emails from DMS and SLERS users are to be opened by the Contractor’s NOC staff immediately. 6. The time between the start of an issue and before opening the trouble ticket shall be counted towards the SLA restoral time. For example: if an outage occurred at 1:00PM (based on the alert data) and the trouble ticket was opened at 1:30PM, 30 minutes shall be counted towards the SLA restoral time. 7. Each month, the Contractor, any subcontractors, and DMS shall review all data related to SLAs. Based on this review, credits shall be provided to DMS. DMS is not required to explicitly request or otherwise initiate the SLA review and validation process in order to receive SLA credits. 8. SLAs defined in the SLA matrix shall result in service credits if the applicable performance targets are not met. Assessed service credits shall be applied as credits toward the impacted site’s monthly invoice, or to DMS as appropriate. 9. To support the SLA process, DMS shall have access to the supporting raw data; there shall be no restriction on content – DMS has access to 100 percent of the raw data if needed. Access can be either direct or indirect. Indirect access would be acceptable if there is some security or policy preventing DMS from logging onto a system directly. Indirect access would also be permitted if it would be costly for DMS to have direct access. 10. Simple operational service changes shall be initiated through the Contractor's trouble ticketing system and not require a DMS-approved maintenance window. DMS and the Contractor will agree upon an initial list of simple operational service changes and the list will be updated during the monthly operational meetings based on the review of the performance of service changes. 11. SLERS service transition, as defined in the Offeror’s Transition Plan, is to be accepted by DMS within the applicable performance target if the Contractor is to avoid having to provide DMS with service credits. 12. All required tasks on the SLERS Services checklist listed below is to be implemented, successfully tested, or otherwise approved by DMS before the Contractor is permitted to transition services to SLERS. The checklist is the set of requirements defined within the

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 79 | 91

Statement of Work. However, during the negotiation process, DMS and the Offeror will finalize the checklist containing these tasks; the objective is to clarify and add to the checklist, not to remove any tasks. The Contractor shall not be permitted to transition any services until the Contractor completes all tasks in the checklist. SLERS Services checklist includes but is not limited to: A. Plan, design, implement and deploy services. B. Implement and deploy Service Management Center tools. C. Develop training material on how to use Service Management Center tools. D. Detail Project Management plans. E. Establish adequate staffing to accomplish the objectives for SLERS Services checklist. This includes the project management team. F. Schedule meetings with DMS to start discussions related to the transition and timeline. G. Implement SLA measurement systems and processes. H. Develop a detailed SLA review and validation process. 13. Contractor SLA Accountability A. The Contractor will not be held accountable for SLAs that are beyond their reasonable control, or those due to Force Majeure; see also PUR 1000 for Force Majeure. B. SLAs shall apply in the event of human error. For example, an SLA will apply if a change during a non-maintenance window was thought to be safe but resulted in performance degradation. C. SLAs do not apply during scheduled maintenance window (including emergency) for the service elements listed in the DMS-approved maintenance window request. However, SLAs will still apply for any other service element impacts during and after the scheduled maintenance window. SLAs will apply to performance degradation caused by exceeding the scope of the approved maintenance change request. D. Performance degradation caused by poor engineering design is not exempt from SLA violations.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 80 | 91

E. Tardy dispatch, and dispatch without required repair/diagnostic tools, expertise, and spare equipment does not exempt the Contractor from their accountability for SLA restoral of the services. F. DMS will make the final determination on Contractor compliance with SLAs. Offeror has read, understands, and will comply with the statements contained in this subsection.

Performance Monitoring Baseline The Contractor’s final implementation of its performance monitoring service will be verified against the SLA attachment during production to assure that SLERS performance monitoring is effective in production. Any parameters not meeting the requirements of the SLA matrix is to be corrected prior to production.

Offeror has read, understands, and will comply with the statements contained in this subsection.

Timely Credit Determination and the Application of Credits Timely credit determination and the application of credits are critical to DMS because the State of Florida has fiscal deadlines and rules related to accounting practices. Credits shall be applied to the appropriate account within the target time window shown within the SLA attachment.

Outline the process for determining and issuing credits per Attachment D, Service Level Agreements. [1000 words]

12 END OF CONTRACT PLAN These subsections cover technical, administrative, and contractual topics associated with the end of this contract, and requirements relating to transition between SLERS and the replacement contract for future iterations of this Service or a similar service.

Transition - Contract Completion There will be a need for end-of-contract transition services prior to expiration or termination of the SLERS contract; therefore, the Contractor will work with DMS to devise a transition plan and process to enable a smooth transition of services from SLERS. The full transition of existing

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 81 | 91

services to a replacement contract(s) is hereby explicitly made a condition of the SLERS service. These transition activities will be met before the SLERS contract is considered complete.

Offeror has read, understands, and will comply with the statements contained in this subsection.

Transition - Payment Strategy DMS requires a transition strategy utilizing a site-by-site payment strategy. As sites migrate from SLERS to any replacement contract, DMS will continue to pay only for each site still served under the SLERS contract. During the transition phase, payments to the Contractor will diminish as sites migrate to the follow-on contract.

Offeror has read, understands, and will comply with the statements contained in this subsection.

Overlapping Contracts Overlapping contracts may be required when transitioning from one large infrastructure to another and transition may take multiple years to complete. Sites and services are not considered an exclusive award to the SLERS contract provider and they can be migrated from the SLERS contract to a replacement contract(s) prior to the expiration date of the SLERS contract. DMS is not obligated to maintain SLERS contracted services for any set number of users or locations. If the SLERS contract is terminated before the expiration date, the transition period will begin as required by DMS.

Offeror has read, understands, and will comply with the statements contained in this subsection.

Contract Terms, Conditions, and Rates The SLERS provider will maintain business as usual for all SLERS services until there is a successful transition to a replacement contract. SLERS contract terms, conditions, and rates will remain unchanged even if the transition period extends past the contract end date, and will agree to contract extensions as necessary to accommodate complete transition.

Offeror has read, understands, and will comply with the statements contained in this subsection.

Expeditious Efforts during the Transition

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 82 | 91

DMS recognizes that as sites disconnect from the SLERS the revenue will decrease yet the SLERS infrastructure will remain largely in place. DMS, the Contractor, and the next contract services provider will collaborate to migrate to the replacement contract as expeditiously as possible. During the development of the contract with a follow-on provider, DMS will define milestones for the replacement provider to avoid sites languishing on the SLERS infrastructure.

Offeror has read, understands, and will comply with the statements contained in this subsection.

Transition Assistance During the effort to transition between SLERS and the replacement contract, the Contractor will work with DMS to devise a transition plan and process to enable a smooth transition between SLERS and the next contract services provider. As part of the end of contract transition assistance, the Contractor will: 1. Provide sufficient efforts and cooperation to ensure an orderly and efficient transition of service to the replacement contract. These efforts include taking all necessary steps, measures, and controls to ensure minimal disruption of services during the transition. 2. Deliver to DMS, upon request, whether or not previously made available, the following: A. Up-to-date operations guides and procedures the Contractor follows to provide SLERS services; B. All documentation created for the purpose of supporting, operating, maintaining, upgrading, and enhancing services, including but not limited to, up-to-date operational manuals, training guides, design documents, and configurations for core and RAN; C. Disclosure of the equipment, software, and third-party contract services required to perform SLERS services for DMS; and D. Databases of information, providing database dumps of all service ordering and billing information as needed. 3. Assist DMS and the next contract provider with the planning and installation of any services to facilitate business continuity for the SLERS sites (generally the next contract services provider would be responsible for paying for new service layers supporting the orderly and efficient transition). 4. Answer questions related to the transition on an as-needed basis. For example, the Contractor is to provide transition services assisting DMS and the next contract services

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 83 | 91

provider when an understanding of coverage and planning and other operational and procedural aspects of SLERS. 5. To the extent reasonable, provide such other services, functions, or responsibilities inherent or necessary to the transition, provided that such services, functions, or responsibilities are limited to those that can be delivered with the then current Contractor’s team staffing (including subcontractors if required). Offeror has read, understands, and will comply with the statements contained in this subsection.

13 FINANCIAL CONSEQUENCES Consequences for Non-Performance In addition to the specific consequences explained herein, DMS reserves the right to withhold payment or implement other appropriate remedies, such as contract termination or non-renewal, when the Contractor has failed to perform/comply with provisions of the Contract. These consequences for non-performance shall not be considered penalties. The billing reconciliation for SLA violations takes place once final determination of SLA credits has been completed.

Offeror has read, understands, and will comply with the statements contained in this subsection.

14 OTHER ELIGIBLE SLERS PARTNERS In addition to the JTF and state SLERS partners, the current service supports other eligible users (OEU) through agreements between the OEU and the current service provider in accordance with Florida Administrative Code 60FF-4. The State reviews applications made by OEUs to join SLERS for approval. If approved, the OEU enters into an agreement with the current service provider to utilize SLERS. In some cases, the OEU has funded improvements to SLERS, such as additional RAN sites, that the state users are permitted to utilize. As the current service’s contract term ends on June 30, 2021, it is the State’s understanding that the agreements between the OEU and the current service provider end by June 30, 2021. With

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 84 | 91

the implementation of a new Service, it is important that the current OEUs maintain mission critical communications capability.

Describe how the current OEUs and potential new OEUs will be able to join the new Service. Describe the proposed rate structure for OEUs and how the Service will be marketed to OEUs who are not part of the current service. [500 words]

15 MINIMUM SERVICES TECHNICAL REQUIREMENTS Offeror has read, understands, and completes as specified in Attachment C – Minimum Services Technical Requirements.

16 INFORMATION REQUIRED FOR NEGOTIATIONS Offerors that the State’s evaluation indicate are within the competitive range may be invited to participate in negotiations. The State will provide traffic and frequency resource data to invited Offerors upon the Offeror’s signing of a Non-Disclosure Agreement. The Offeror should utilize this information to finalize the proposed Service design at the start of negotiations. The information requested in this section should only be provided if the Offeror is invited to participate in negotiations and within the timeframes specified in the Invitation to Negotiate. Should the Offeror be selected to participate in the negotiations phase of the ITN, the State expects to participate in a design review with the Offeror to make suggestions for design improvements that will better meet the needs of the State.

Service Design In an attachment, provide detailed diagrams of the proposed Service design including, but not limited to: 1. System Overview Topology 2. Block Diagrams for a. Multisite RAN Sites b. Simulcast RAN Sites c. Connectivity Only Sites d. Network Core Sites e. Dispatch Centers

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 85 | 91

3. 4. 5. 6. 7.

f. NOC g. Other Sites as Required Site Antenna Network Diagrams Rack Elevation Drawings Tower Loading Diagrams Equipment Enclosure Floorplans Emergency Power Systems Block Level Wiring Diagrams

Coverage Prediction Maps Terrestrial and Maritime Service Coverage Prediction Maps Provide coverage prediction maps, for both the Service and mutual aid channels, showing areas where the tile reliability meets or exceeds 85 percent and 90 percent using separate colors to denote tiles: 1. Greater than or equal to 85 percent and less than 90 percent 2. Greater than or equal to 90 percent 3. Greater than or equal to 95 percent Each coverage map should include the predicted service area reliability. The coverage prediction maps shall be based upon 700 MHz, P25 Phase 2, AES encrypted operation and the following parameters: Mobile Coverage 4. For Talk-Out a. Mobile receive antenna shall be modeled with a center of radiation at 5.5 feet above ground and with a gain of 3 dBd. b. SU faded receiver sensitivity (without antenna system factors) shall be modeled as -109 dBm. 5. For Talk-Back a. Mobile transmit antenna shall be modeled with a center of radiation at 5.5 feet above ground with a gain of 3 dBd. b. Mobile transmitter output power (power input to transmission line to antenna) shall be modeled as 35 W. Portable Outdoor Coverage 6. For talk-out a. Portable receive antenna shall be modeled as ¼-wave flexible whip with a center of radiation at 3.3 three feet above ground level with a gain of -15.4 dBd.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 86 | 91

b. SU faded receiver sensitivity (without antenna factors) shall be modeled as -109 dBm. 7. For Talk-Back a. Portable transmit antenna shall be modeled as ¼-wave flexible whip with a center of radiation at 3.3 three feet above ground level (using remote speaker/microphone) with a gain of -15.4 dBd. b. Portable transmitter output power (power input to antenna) shall be modeled as 3 W. Maritime Coverage 8. For Talk-Out a. Mobile receive antenna shall be modeled with a center of radiation at 5.5 feet above ground and with a gain of 3 dBd. b. SU faded receiver sensitivity (without antenna system factors) shall be modeled as -109 dBm. 9. For Talk-Back a. Mobile transmit antenna shall be modeled with a center of radiation at 5.5 feet above ground with a gain of 3 dBd. b. Mobile transmitter output power (power input to transmission line to antenna) shall be modeled as 35 W. For all Terrestrial and Maritime Service RAN sites, provide the following RF coverage parameters: 10. Transmit and receive antenna models, gain, beamwidth, azimuth, downtilt, sidearm length, and mounting height referenced to center of radiation 11. Transmission line type and length for transmit and receive antenna systems 12. Insertion loss values (noted in decibels) for all proposed antenna system components 13. Transmitter power level for all Service’s transmitters 14. Effective radiated power (ERP) level for each site 15. Net amplification gain for the tower top amplifier system 16. Receiver sensitivity specifications for all Service’s receivers 17. BER required for DAQ 3.4 18. The faded performance margin, CF/(I+N), utilized per TSB-88 for the required CPC requirement for DAQ 3.4 19. The minimum received signal level for DAQ 3.4

Aircraft Service Coverage Prediction Maps Provide coverage prediction maps showing areas where the tile reliability meets or exceeds 85 percent and 90 percent using separate colors to denote tiles:

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 87 | 91

1. Greater than or equal to 85 percent and less than 90 percent 2. Greater than or equal to 90 percent and less than 95 percent 3. Greater than or equal to 95 percent Each coverage map should include the predicted service area reliability. The coverage prediction maps shall be based upon 700 MHz, P25 Phase 2, AES encrypted operation and the following parameters: 1. For Aircraft Service operating floor, a. For Talk-Out i. Mobile receive antenna shall be modeled as an equivalent to a ¼-wave antenna at a height of 500 feet AGL with a gain of 1.0 -dBd. ii. Faded receiver sensitivity (without antenna system factors) shall be modeled as -109 dBm. b. For Talk-Back i. Mobile transmit antenna shall be modeled as an equivalent to a ¼-wave antenna at a height of 500 feet AGL with a gain of -1.0 dBd. ii. Mobile transmitter output power (power input to transmission line to antenna) shall be modeled as 10 W. 2. For Aircraft Service operating ceiling, a. For Talk-Out i. Mobile receive antenna shall be modeled as an equivalent to a ¼-wave antenna at a height of 5280 feet AGL with a gain of -1.0 dBd. ii. Faded receiver sensitivity (without antenna system factors) shall be modeled as -109 dBm. b. For Talk-Back i. Mobile transmit antenna shall be modeled as an equivalent to a ¼-wave antenna at a height of 5280 feet AGL with a gain of -1.0 dBd. ii. Mobile transmitter output power (power input to transmission line to antenna) shall be modeled as 10 W. For all Aircraft Service RAN sites, provide the following RF coverage parameters: 1. Transmit and receive antenna models, gain, beamwidth, azimuth, downtilt, sidearm length, and mounting height referenced to center of radiation 2. Transmission line type and length for transmit and receive antenna systems 3. Insertion loss values (noted in decibels) for all proposed antenna system components 4. Transmitter power level for all Service’s transmitters 5. ERP level for each site 6. Net amplification gain for the tower top amplifier system 7. Receiver sensitivity specifications for all Service’s receivers 8. BER required for DAQ 3.4

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 88 | 91

9. The faded performance margin, CF/(I+N), utilized per TSB-88 for the required CPC requirement for DAQ 3.4 10. The minimum received signal level for DAQ 3.4

Capacity Plan Terrestrial and Maritime Service Capacity Plan

Indicate the number of channels (control and working channels), total quantity of available talk paths and calculated Grade of Service for each Terrestrial and Maritime Service RAN site.

Aircraft Service Capacity Plan

Indicate the number of channels (control and working channels) and total quantity of available talk paths and calculated Grade of Service for each Aircraft Service RAN site.

Frequency Plan Provide a detailed frequency plan for the proposed Service that delineates the channel assignments on a per RAN site basis. For all 800 MHz frequencies subject to the Florida Region 9 Plan for Public Safety Communications, Florida Region 9 Interference Program outputs shall be included illustrating compliance with the plan. For all 700 MHz frequencies, the provide analyses showing that the coverage predictions have taken into account issues associated with frequency reuse and that for facilities along the interstate boundary, the field strength of each station’s transmissions is limited to 40 dBµ/m at the state’s geographic border. If the proposed Service requires additional 700 MHz state use frequencies for allocation to campus operation, provide justification and details on the required locations and quantities.

17 BUSINESS OPERATIONS Service Inventory The Contractor will provide and maintain a detailed Service Inventory that uniquely identifies each component that is billable to DMS. The component monthly recurring price must be tied directly to the negotiated Pricing Workbook, ITN Attachment E. The Service Inventory must include the following:

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 89 | 91

1. 2. 3. 4.

Service Identifier – Unique identifier for the service component Service Description – Description of the service component Service Date – Date service is accepted by the DMS Service Location – Physical location of service (applies only to location specific components) 5. Service Monthly Recurring Price – Billable monthly price for the component

New Service Requests DMS will work with the Contractor to establish requests for new service(s) based upon the pricing negotiated in Pricing Workbook, ITN Attachment E. Fulfilling some service requests under this contract will require providing services not readily defined in the Pricing Workbook and/or require the Contractor to determine the quantity of services and/or propose a unique configuration. Examples include new tower location where construction or augmentation is required for which the cost to implement can only be determined after a site assessment by the Contractor. Contractor shall draft a proposal for the new service request for review by DMS. This provides the mechanism for Contractor to respond to requests being made for additional service or in response to potential SLA conditions requiring augmentation. With the approval of DMS, new services/hardware might be subsequently added to the Pricing Workbook, ITN Attachment E, as appropriate. But in all cases, the total cost of the proposed Service request must be defined and approved prior to execution and/or fulfillment. In addition to naming services to be provided, the service request will contain other data necessary to specify and authorize the service like target installation dates, locations, configuration data and documents containing diagrams as necessary. For cases whereby there are variable price components, DMS and Contractor will reach mutual agreement prior to execution of any new service request. Each service request proposal must contain sufficient documentation detail to support implementation requirements and audit processes. Each service request must be approved in writing by DMS.

Invoicing Requirements The Contractor will invoice DMS monthly for all SLERS services. Invoices will consist of 1) a single request for payment on unchangeable format (paper) known as a “hand bill” which reflects 1) the total charges for the month, and 2) electronic detail files that substantiate all billable services. The total of substantiated detail charges must match the single payment request on the handbill. The invoice will include detailed service credits uniquely identified by SLA. These credits will be audited by DMS through review of SLA reporting and invoice auditing. It is the responsibility of the Contractor to apply credit(s) to the invoice for the month in which the SLA credit(s) occurred.

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 90 | 91

Electronic Substantiating Detail File The invoice substantiation file consists of ASCII delimited electronic detail listing all billable services and activities with all unique IDs necessary to be auditable bases for all charges. The detail file must include all charge data on one-time purchases, active service periods, and incremental activities. All charges must be attributable to distinct identifiers from the services as negotiated in Pricing Workbook, ITN Attachment E, and each discrete charge must be distinguished by service identifier.

DMS Review of Contractor Invoices DMS will pre-audit the invoice to match all charges against the current services inventory to the prices associated with the negotiated Pricing Workbook, ITN Attachment E. Barring audit exceptions, DMS will pay the Contractor the total charges for all services rendered. If the electronic substantiating detail provided by the Contractor contains some errors but is: a) complete (i.e. contains all of the required data elements); b) substantially corresponds with the Service Inventory; and c) matches the hand bill, DMS will send an exception report to the Contractor detailing any disputed charges. DMS staff will request credits for any exceptions on the current invoice and work with Contractor staff to reconcile charges and system data to resolve the exceptions.

Offeror has read, understands, and will comply with the statements contained in this section.

THIS SPACE INTENTIONALLY LEFT BLANK

ITN DMS-15/16-018 SLERS, Attachment A – Statement of Work

p a g e 91 | 91