Project: June 5, 2015 Issue Date: Audio & Digital Logging System Page 1 … … · · 2015-06-23Project: Dakota Communications Center (DCC) ADDENDUM # 1 RFP Issued: June 5, 2015

Project: Dakota Communications Center (DCC) ADDENDUM # 1 RFP Issued: June 5, 2015 Issue Date: June 22, 2015 Project Name: Audio & Digital Logging System Page 1 of 4

PSC Alliance Inc. Voice: (612) 216-1502 7900 International Drive – Ste. 300 FAX: (888) 384-9171 Bloomington, MN 55425 e-mail: [email protected]

This addendum supplements the specifications for this project. INSTRUCTIONS Amendments modify language in the original specification. Only the text which has been reproduced below is changed from the specification. Deletions are reflected by striking out old words. Additions are reflected by underlining new text. (Example: text struck out indicates deletion text underlined indicates addition.) Clarifications do not change any existing text from the original specification but amplify on intent. INFORMATION

1. Information Only: A pre-proposal meeting was held on June 17, 2015. Three (3) vendor organizations were represented in-person at the meeting and one (1) organization joined via web/conference call access. A list of attendees is attached to this addendum.

CLARIFICATIONS Clarifications to the Specification: The following clarifications flow from questions posed by Vendors and/or discussion at the pre-proposal meeting.

2. Definition of Radio ‘Resources’: In the RFP document and during the pre-proposal meeting, there was discussion about talk groups, conventional channels, and ‘resources’ in the context of system sizing and pricing. For the purposes of this project Motorola MCC 7500 radio ‘resources’ are defined to include both talk groups and conventional radio channels which are, or may be, connected to and accessed by the MCC 7500 console system(s).1

3. RFAI/A9-1-1 SIP Interface: Intrado’s RFAI/A9-1-1 SIP interface specification is a proprietary document which will be made available to the successful vendor. A prospective request to release the interface specification has been made to Intrado but, as this addendum is published, the release authority has not yet been received.

4. Vendor Questions: The following written questions were received from vendors prior to the pre-proposal conference.

a. Capabilities, limitations, and design requirements for the Motorola AIS server is expressed in explicit number of talkgroups. Please provide the approximate number of primary talkgroups the county wishes to recorder? Approximate number of backup/interop talkgroups the county wishes to record? What % of growth should be expected over the life of this recorder?

Answer: Vendors shall refer to #2 above and organize their base quote assuming 120 ‘resources’ available via the AIS.

1 Motorola’s October, 2014 MCC 7500 published console resource guide states the following regarding the Archiving

Information Server (AIS), “The user can configure the 3rd party recorder to monitor and record a set of radio system resources (trunked or conventional). The AIS monitors those identified resources, passes call-control information to the logging sub-system via an API, and redirects audio for those monitored channels to the logging sub-system via the LAN. The logging recorder then records this information to its storage media. (Emphasis added)

mailto:[email protected]



b. Can you describe the present recording system at DCC and Scott noting the number of analog, telephone, and talk groups being recorded at each site?

Answer: Both the DCC and Scott County use Verint logging systems. The DCC digitally logs traffic from the Zone 1 master site via an ATIA (Air Traffic Access Information) interface which will be replaced via this procurement. See also the table attached to this addendum which list currently logged resources. c. Is there any non-ARMER radio being recorded? Conventional VHF or the like? Answer: Both the DCC and Scott County log ‘non-ARMER’ traffic today. Refer to the block diagram and items 2 and 4a above. d. There are no requirements for the new archiving solution to interface with the archiving solution being

used today. Is this an assumed requirement or is the customer willing to use 2 different replay/reconstruction systems during the retention period?

Answer: The DCC currently has the longest retention period for archived recordings (6 months). There is no requirement for the new (replacement) archiving solution to interface to the existing solution. e. Please describe in more detail your requirements for CAD integration in regards to data capture and

storage. Answer: The DCC will migrate onto a TriTech CAD system in 2016. Scott County recently migrated onto an LETG CAD system. At minimum it is desirable for the selected logging solution to be able to begin capturing CAD screen ‘shots’ at intervals selected by the local system administrator upon activation of an ‘off-hook’ closure furnished by the associated position’s VESTA telephone system. Proposals shall describe vendor’s capabilities to perform this type of integration along with assumptions necessary for implementation. f. Does DCC expect the logging network to be a on a private or IT enterprise network? If enterprise, will

the telephony also interface to this same network? Please describe both customer’s networks and how they interconnect.

Answer: For purposes of the proposal response, the vendor shall assume that the logging systems will operate on a private network for both the DCC and Scott County. The vendor’s proposal shall stipulate any required assumptions to allow the traffic to be shared on the local Enterprise network including factors such as firewalls, active directory configuration, sub-netting requirements, etc. g. Will DCC be providing ETH interface at both ends of the fiber? If not, what type of fiber is going to be

used? Answer: Vendors shall assume that the handoff at the ends of the single mode fiber shall be electrical/Ethernet and that handoff shall be provided by the Owner(s). h. No need for instant recall capability for either agency as part of this proposed logging solution? (Internal

Note: DCC did purchase IRR on their MCC consoles, but Scott didn't (DDR notes talk about interfacing to existing) per what was on the FO's).

Answer: Instant recall recorder capability is not being solicited as part of this RFP.




i. Will the redundant AIS (required for Scott) be supplied or is it part of this bid? Answer: If AIS redundancy is required it will be furnished by the Owner(s). j. Is Scott County providing playback clients? If so, what network will they reside on? Answer: The vendor’s proposal shall include the provision of playback clients operating on a private network. The actual implementation of playback access will be negotiated with the successful vendor(s). k. Does Scott County expect the logging network to be a on a private or IT enterprise network? If

enterprise, will the telephony also interface to this same network? Answer: See Answer 4 f above. l. If a independent network is required, is this expected to be provided by logging vendor? Answer: See Answer 4f above. m. Airbus SIP integration has been requested. All metadata and voice recording can be done using other

methods. Once the NG911 I3 standard is finalized, the IP connection will have greater value, but today this is a proprietary integration. Any group that proposes this integration should be clear with their relationship to Airbus for protocol updates/modifications to assure limited system downtime during Airbus upgrades or bug fixes. Will it be acceptable to provide a solution today that meets the recording requirements with a migration to I3 when available? Will Airbus Vesta Voice (RTP) packets and SIP packets though wireshark captures, and capture of the Airbus CDR(Call Detail Records) be available from Airbus ( and/or Customer or Consultant) for additional metadata capture?

Answer: The RFP requests integration with the RFAI-A911 SIP stream provided by Intrado. Airbus’ VESTA equipment is communicating via that SIP interface. The availability date of full i3 9-1-1 functionality in the metro area has not been established and therefore the Intrado RFAI-A911 SIP integration has been requested via this RFP since the date for the DCC’s conversion has been established. Nothing in the RFP precludes any vendor from suggesting a superior interface alternative. See also #3 above. n. The RFP is very thorough and will require a great deal of effort to respond. There is an upcoming Holiday

which will add greater complexity in building an appropriate response. Consequently, we request an additional two weeks to respond.

Answer: A compromise concerning the due date for proposals is identified in Amendment # 5 below. o. Your drawing shows a Digital Logger at the Scott County Alternate 1 site. Is this a Digital Radio Recorder

or a phone recorder?

Answer: The reference to the digital logger at Scott County is intended to depict the ability to both back up and retrieve digitally logged radio traffic collected on the primary AIS installed at the DCC. p. For SNMP alarm ‘trap’ message, what is the system used to collect these messages? Answer: A DPS Telecom “T-Mon” is installed at the Empire campus (DCC location) and used NetGuardian RTUs for alarm monitoring. The T-Mon is equipped with SNMP trap collection software.




AMENDMENTS TO THE RFP

5. Schedule: The schedule of events table (page 1-5) is amended as shown below. Schedule of Events

Description Date RFP Re lease Date June 5, 2015 Writ ten Quest ions Due June 15, 2015; 3:00 PM Central T ime Mandatory Pre-Proposal Pre-Proposal Conference June 17, 2015; 1:30 PM Central T ime Addendum Publ i shed June 30 23, 2015; 53:00 PM Centra l T ime Proposa ls Due & Opened Ju ly 10 17, 2015; 2:00 PM Central T ime Owner ’ s Proposal Evaluat ion Ju ly 11 17 – Ju ly 30, 2015 Ant ic ipated Contrac t Award August 20, 2015 Ant ic ipated Logging System F inal Acceptance for DCC Insta l led Equipment

October 16, 2015

Acqu is i t ion & In tegrat ion of Add-A lternate # 1 Equ ipment & Services i f Selec ted by Scott County

Q1 – 2016 or sooner at the discret ion of Scott County.

Table 1-1

6. References: The paragraph at the top of page 1-15 is amended as shown below.

References shal l be se lected to ref lect the s ize and complex ity of s imi lar ADLRS projects. Included with the l ist shal l be the name, t i t le, address, and telephone number of an off ic ia l famil iar with each c ited project. I f subcontractors are to be used, a s imi lar l is t sha l l be furnished for each subcontractor. No reference sha l l be given for projects not completed (project in-progress) nor for projects completed more than three years previous to the proposal opening date for th is project . I f a contract is awarded to the vendor, the l i st of proposed subcon-tractors shal l not be amended without pr ior written permission of the Owner.

7. Correcting a Typo: Page 2-10 contains a typo. The following sentence is amended as shown below. Scott County has a lso implemented MCC 7500 radio consoles and previously instal led the A irbus Vesta 4 9-1-1 cal l answering system at eight (8) ten (10) workstat ions.

8. Reference Forms Re-Issued: The reference forms (pages 1-48 – 1-53) of the RFP are amended

and re-issued with this addendum.

- End of Addendum #1 - Attachments:

• Reference Forms • Existing Logged Resource Inventory • Pre-Proposal Attendance List


Section 1 Dakota Communications Center (DCC)

PSC Alliance Inc. 1-48 Audio & Data Logging Recording System (ADLRS)

Reference Forms Vendor Reference 1 – Within Minnesota

Organization Name (Must be located in the State of Minnesota & Integrated with ARMER Version 7.13 Trunked Radio System)

Contact Name

Contact Address

Contact Number

Contact e-mail Address

Project Implementation Date

Project Description (Must be in production mode at a Minnesota PSAP)

Change Orders or Deviations from Original Contracted Work



Vendor Reference 2 – Within Minnesota

Organization Name (Must be located in the State of Minnesota & Integrated with ARMER Version 7.13 Trunked Radio System)

Contact Name

Contact Address

Contact Number



Project Description (Must be in production mode at a Minnesota PSAP)




Vendor Reference 3 – May be Within or Outside Minnesota

Organization Name (May be located in the State of Minnesota & Integrated with ARMER Motorola Version 7.13 Trunked Radio System)

Contact Name

Contact Address

Contact Number


Project Implementation Date Project Description (Must be in production mode at a Minnesota PSAP)




Vendor Reference 4 – May be outside Minnesota

Organization Name (May be located in North America and must be integrated with a Motorola Digital Trunked Radio System operating at version 7.13 or higher, and/or has implemented network side, SIP based, 9-1-1 telephone logging.)

Contact Name

Contact Address

Contact Number



Project Description (Must be in production mode; may be outside of Minnesota. If outside Minnesota provide block diagram labeled “Reference #4” with proposal showing integration of the ADLRS system to the applicable radio and/or telephone network)





Organization Name (May be located in North America and must be have implemented a network side, SIP based, 9-1-1 telephone logging installation.)

Contact Name

Contact Address

Contact Number



Project Description (Must be in production mode; may be outside of Minnesota. If outside Minnesota provide block diagram, labeled “Reference #5” with proposal showing integration of the ADLRS system to the telephone network)





Organization Name (May be located in North America and must be have implemented a network side, SIP based, 9-1-1 telephone logging installation.)

Contact Name

Contact Address

Contact Number



Project Description (Must be in production mode; may be outside of Minnesota. If outside Minnesota provide block diagram, labeled “Reference #65” with proposal showing integration of the ADLRS system to the telephone network)


Talk Group / Multigroup Numeric ID / Radio TX Freq Console DCC CASPhone Op1 Yes NoPhone Op2 Yes NoPhone Op3 Yes NoPhone Op4 Yes NoPhone Op5 Yes NoPhone Op6 Yes NoPhone Op7 Yes NoPhone Op8 Yes NoPhone Op9 Yes NoPhone Op10 Yes NoPhone Op11 Yes NoPhone Op12 Yes NoPhone Op13 Yes NoPhone Op14 Yes NoPhone Op15 Yes NoPhone Op16 Yes NoPhone Op17 Yes NoPhone Op18 Yes NoPhone Op19 Yes NoPhone Op20 Yes NoPhone Op21 Yes NoPhone Op22 Yes NoPhone Op23 Yes No

PR. ISLAND EOC Yes Yes NoDK SOT 2 Yes No Yes

East Fire Page Yes Yes NoWest Fire Page Yes Yes No

DK FMAIN-E Yes Yes NoDK FMAIN-W Yes Yes No

DK FGR 4 Yes Yes NoDK FGR 5 Yes Yes NoDK FGR 6 Yes Yes NoDK FGR 7 Yes Yes NoDK FGR 8 Yes Yes No

DK AF OP2 Yes Yes YesDK B2 OP2 Yes Yes YesDK EF OP2 Yes Yes YesDK FF OP2 Yes Yes YesDK H2 OP2 Yes Yes YesDK RH OP2 Yes Yes YesDK IF OP2 Yes Yes YesDK LF OP2 Yes Yes YesDK MF OP2 Yes Yes YesDK MV OP2 Yes Yes YesDK R1 OP2 Yes Yes YesDK SM OP2 Yes Yes YesDK LMAIN 1 Yes Yes NoDK LMAIN 2 Yes Yes NoDK LMAIN 3 Yes Yes No

DK CAR-CAR No No YesDK TAC 10 Yes Yes NoDK TAC 11 Yes Yes NoDK TAC 12 Yes Yes NoDK TAC 13 Yes Yes NoDK TAC 14 Yes Yes NoDK TAC 15 Yes Yes No

DK EABV SWAT Yes Yes YesDK MAAG 1 Yes Yes YesDK PL C5 Yes Yes YesDK PL C6 Yes Yes YesDK PL C7 Yes Yes YesDK PL C8 Yes Yes YesDK PL C9 Yes No Yes

DK PL C10 Yes No YesDK PL C11 Yes No YesDK PL C12 Yes No YesDK INFO 1 Yes Yes No

DK LMAIN 4 Yes Yes YesDK PL C13 Yes No YesDKOTA-911 Yes No No

DK ALL 1 Yes Yes NoDK WEATHER Yes No No

ME TAC 1 Yes Yes NoME TAC 2 Yes Yes YesME TAC 3 Yes Yes YesME TAC 4 Yes Yes YesMETCOM Yes No NoL-TAC1 Yes Yes YesL-TAC2 Yes Yes YesL-TAC3 Yes Yes YesL-TAC4 Yes Yes Yes

DCC ServerCAS ServerNot Logged

DCC LOGGING INVENTORY

Scott County Logged TrafficPer Lori Adamietz

01 OP POS 102 OP POS 203 OP POS 304 OP POS 405 OP POS 506 OP POS 607 OP POS 708 OP POS 809 OP POS 910 OP POS 1011 Fire Alt12 Fire Base 213 SC-LE-INFO14 SC-LE-TAC515 PTAC116 Consolette 617 METCOM18 Ch 2 Base 219 Ch 2 Base 120 Fire Base 121 SC-PSCOMM22 LTAC123 SC-FG-724 SC-FG-825 SC-FG-926 SC-FG-1027 SC-FG-1128 SC-FG-1229 SC-FG-530 SC-FG-631 SC-SO-MAIN32 SC-NO-MAIN

Documents

Project: June 5, 2015 Issue Date: Audio & Digital Logging System Page 1 … … · · 2015-06-23Project: Dakota Communications Center (DCC) ADDENDUM # 1 RFP Issued: June 5, 2015