HomeMy WebLinkAbout2002-049
CORPORATION OF THE MUNICIPALITY OF CLARINGTON
BY -LAW 2002-049
being a by-law to authorize the execution
of a Motorola Agreement with the City of
Oshawa acting as agent for Clarington,
Whitby, Pickering and Ajax to purchase
the SYSTEM (hardware and software)
THE CORPORATION OF THE MUNICIPALITY OF ClARINGTON HEREBY
ENACTS AS FOllOWS:
1. THAT the Mayor and Municipal Clerk are hereby authorized to execute, on
behalf of the Corporation of the Municipality of Clarington and seal with
the Corporate Seal, a Motorola Agreement with the City of Oshawa acting
as agent for Clarington, Whitby, Pickering and Ajax to purchase the
SYSTEM (hardware and software); and'
2. THAT the agreement attached hereto'as Schedule "A" form part of this
By-law.
By-law read a first and second time this 2nd day of April, 2002
By-law read a third time and finally passed this 2nd day of April, 2002
-
utton, Mayo~_--~- ~:- _ :--:: : ~ ~-- _ :
- ~,::- - - ....,., -~
- ,",:::,-- - --_..<~ - /'
-....::: - -- ..-
- -
-. -~ -.. -
unicipal_Clerf:~~~~:--
Communications System Agreement
Motorola Canada Limited through its Commercial, Government, and Industrial Solutions Sector, North
America Group ("Motorola"), having a place of business at 8133 Warden Avenue, Markham, Ontario L6G
183 and the Corporation of the Town of Ajax, the Corporation of the Municipality of Clarington, the
Corporation of the City of Oshawa, the Corporation of the City of Pickering and the Corporation of the Town
of Whitby (hereinafter referred to collectively as "Customer" and individually as "Ajax", "Clarington, "Oshawa",
"Pickering" or 'Whitby"), enter into this Communications System Agreement ("Agreement"), pursuant to which
Customer will purchase and Motorola will sell the System, as described below. Motorola and Customer may
be referred to individually as "party" and collectively as "parties."
For good and valuable consideration, the parties agree as follows:
Section 1
EXHIBITS
The Exhibits listed below are incorporated into and made a part of this Agreement. In interpreting this
Agreement and resolving any ambiguities, the main body of this Agreement will take precedence over the
Exhibits and any inconsistency between Exhibits A through E will be resolved in the order in which they are
listed below.
Exhibit A
Exhibit B
Exhibit C
C-1
C-2
C-3
C-4
C-5
C-G
Exhibit 0
0-1
0-2
Exhibit E
Section 2
Motorola "Software License Agreement"
"Payment Schedule"
"Technical and Implementation Documents"
"Functional Specification version 1.0 " dated February 2002
"Equipment List" dated March12, 2002
"Statement of Work" version 1.0, dated February 2002
"Factory Acceptance Test Plan" or "ATP" version 1.0, dated February 2002
Field Acceptance Test Plan, version 1.0 dated February 2002
"Moscad Fire Hall Alerting System Acceptance Test Plan"
Maintenance and Support Agreements
Enhanced System Support Statement of Work ("ESS Statement of Work")
Five (5) year Extended Warranty
"System Acceptance Certificate"
DEFINITIONS
Capitalized terms used in this Agreement shall have the following meanings:
"Acceptance Tests" means those tests described in the Acceptance Test Plans.
"Beneficial Use" means when Customer first uses the System or a Subsystem for operational purposes
(excluding training or testing).
"Contract Price" means the price for the System, exclusive of any applicable sales or similar taxes and freight
charges.
"Effective Date" means March 27, 2002.
"Equipment" means the hardware listed in the Equipment List.
"Fixed Network Equipment" (FNE) means the Motorola supplied Equipment which is the core of the System,
and is generally attached in a permanent manner to an installation facility. Subscriber Equipment is
specifically excluded from FNE.
Motorola Contract No.
"Infringement Claim" means a claim that the Equipment manufactured by Motorola or the Motorola Software
infringes a Canadian patent or copyright.
"Motorola Software" means Software that Motorola Inc., a Delaware corporation, owns and which Motorola
Canada Limited licences under authorization from Motorola Inc.
"Non-Motorola Software" means Software that a party other than Motorola owns.
"Proprietary Rights" means the patents, patent applications, inventions, copyrights, trade secrets,
trademarks, trade names, mask works, know-how, and other intellectual property rights in and to the
Equipment and Software, including those created or produced by Motorola under this Agreement and any
corrections, bug fixes, enhancements, updates or modifications to or derivative works from the Software
whether made by Motorola or another party.
"Software" means the Motorola and Non-Motorola Software in object code format that is furnished with the
System or Equipment and which may be listed on the Equipment List
"Subscriber Equipment" means portable and mobile radios.
"Subsystem" means a major portion of the entire System that performs specific functions or operations as
described in the Technical and Implementation Documents.
"System" means the Equipment, Software, and services combined together into a system as more fully
described in the Technical and Implementation Documents.
"System Acceptance" means the Acceptance Tests have been successfully completed.
"User Gear" means Subscriber Equipment.
Section 3
SCOPE OF AGREEMENT AND TERM
3.1. SCOPE OF WORK. Motorola will provide, ship, install and test the System, and perform its other
contractual responsibilities, all in accordance with this Agreement. Customer will perform its contractual
responsibilities in accordance with this Agreement.
3.2. CHANGE ORDERS. Either Motorola or the Customer may request changes within the general
scope of this Agreement including changes to the System by adding one or more additional Remote
Dispatch Centre to those which are identified in section 2.1 of Exhibit C-1. If a requested change causes an
increase or decrease in the cost or time required to perform this Agreement, Motorola and Customer will
agree to an equitable adjustment of the Contract Price, Project Schedule, or both, and will reflect such
adjustment in a Change Order, provided that if the requested change is the addition of one Remote Dispatch
Centres, and is requested prior to May 15, 2002 and the Customer pays Motorola the fixed amount of
$15,000.00 to compensate Motorola for its additional design work and the preparation by Motorola of a
quotation of the cost of adding one Remote Dispatch Centre to the System, no restocking fee or other cost to
the Customer will be charged by Motorola for the cancellation of an order for Equipment or Software or the
restocking by Motorola of returned or no longer required Equipment or Software referable to the
establishment of the additional Remote Dispatch Centre and/or the System provided however, that the
equipment has not been shipped to Customer. Neither Motorola nor the Customer is obligated to perform
requested changes unless both Motorola and the Project Manager execute a written Change Order. The
parties agree that any Change Orders representing an increase or decrease in the purchase price shall be
deemed valid if signed in counterpart. The parties further agree that notice of any such Change Order may
be effected by facsimile.
3.3. TERM. Unless otherwise terminated in accordance with the provisions of this Agreement or
extended by mutual agreement of the parties, the term of this Agreement shall begin on the Effective Date
Motorola Contract No.
2
and shall continue until the date of System Acceptance or expiration of the warranty period as set forth in
Section 9, whichever occurs last.
3.4. ADDITIONAL EQUIPMENT OR SOFTWARE. For three (3) years after the Effective Date of this
Agreement, each of Ajax, Clarington, Oshawa, Pickering and Whitby may order additional Equipment,
Subscriber Equipment or Software provided it is then available. Each order must refer to this Agreement and
must specify the pricing and delivery terms. The applicable provisions of this Agreement (except for pricing,
delivery, passage of title and risk of loss to Equipment, and payment terms) will govern the purchase and
sale of the additional Equipment or Software. Title and risk of loss to additional Equipment will pass at
shipment, and payment is due within twenty (20) days after the invoice date. Motorola will send the party
ordering the additional Equipment or Software an invoice as the additional Equipment is shipped or Software
is licensed and only that party or those parties who have ordered same will be liable for the costs thereof.
3.5. MAINTENANCE SERVICE. During the warranty period, Motorola will provide maintenance services
for the Equipment and support for the Motorola Software pursuant to the terms of this Agreement, including
the ESS Statement of Work and shall ensure that support exists for any Non-Motorola Software supplied.
Such services and support are included in the Contract Price, including support for Non-Motorola Software.
After the warranty period, Customer may purchase maintenance services for the Equipment by executing a
separate Maintenance Agreement and the Customer may purchase extended support for the Motorola
Software by executing a Software Subscription Agreement.
3.6. MOTOROLA SOFTWARE. Any Motorola Software, including subsequent releases, is licensed to
Customer solely in accordance with the Software License Agreement (other than software development kits,
if applicable, which have separate software license agreements). Customer hereby accepts and agrees to
abide by all of the terms and restrictions of the Software License Agreement.
3.7. NON-MOTOROLA SOFTWARE. Any Non-Motorola Software is licensed to Customer in accordance
with the standard license, terms, and restrictions of the copyright owner on the Effective Date unless the
copyright owner has granted to Motorola the right to sublicense the Non-Motorola Software pursuant to the
Software License Agreement, in which case it applies and the copyright owner will have all of Licensor's
rights and protections under the Software License Agreement. Motorola makes no representations or
warranties of any kind regarding Non-Motorola Software.
3.8. SUBSTITUTIONS. At no additional cost to Customer, Motorola reserves the right to substitute any
Equipment, Software, or services to be provided by Motorola, but only if the substitute meets the
specifications and is of equivalent or better quality and value to the Customer and is approved by the
Customer. Any such substitution will be reflected in a change order.
Section 4
PROJECT SCHEDULE
Motorola and Customer agree to perform their respective responsibilities in accordance with the Project
Schedule as contained in Exhibit C-3. By executing this Agreement, Customer authorizes Motorola to
proceed with performance of this Agreement. No notice to proceed, purchase order, authorization or
resolution, or other action is required for the performance of this Agreement to begin.
Section 5
PAYMENT OF CONTRACT PRICE
5.1. CONTRACT PRICE. The Contract Price in Canadian dollars is $6,142,385.00 (excluding options, as
defined in Exhibit C-2). A pricing summary may be included with the Payment Schedule. Motorola will
submit to Customer invoices according to the Payment Schedule. Except for a payment that is due on the
Effective Date, Customer, but not including Oshawa, will make payments to Motorola within twenty (20) days
after the date of each invoice. Customer will make payments when due in the form of a check, cashier's
check, or wire transfer drawn on a Canadian financial institution.
Motorola Contract No.
3
5.2. OVERDUE INVOICES. Overdue invoices will bear simple interest at the rate of ten percent (10%)
per annum, unless such rate exceeds the maximum allowed by law, in which case it will be reduced to the
maximum allowable rate.
5.3. FREIGHT, TITLE, AND RISK OF lOSS. All freight charges will be pre-paid by Motorola and added
to the invoices. Title to the Equipment will pass to Customer upon shipment, except that title to Software will
not pass to Customer at any time. Risk of loss will pass to Customer upon delivery of the Equipment to the
Customer. Motorola will pack and ship all Equipment in accordance with good commercial practices.
Section 6
SITES AND SITE CONDITIONS
6.1. ACCESS TO SITES. In addition to its responsibilities described elsewhere in this Agreement,
Customer will provide (i) a designated project manager; (H) all necessary construction and building permits,
zoning variances, licenses, and the like; and (Hi) access to the work sites identified in the Technical and
Implementation Documents as reasonably requested by Motorola so that it may perform its duties in
accordance with the Performance Schedule and Statement of Work.
6.2. SITE CONDITIONS. Customer will ensure that all work sites it provides will be safe, secure, and in
compliance with all applicable industry, federal, provincial, and/or local occupational health and safety
statutes and regulations. To the extent applicable and unless the Statement of Work specifically states to
the contrary, Customer will ensure that these work sites will have (i) adequate physical space for the
installation, use and maintenance of the System; (ii) adequate air conditioning and other environmental
conditions; (Hi) adequate electrical power outlets, distribution and equipment for the installation, use and
maintenance of the System; and (iv) adequate telephone or other communication lines for the installation,
use and maintenance of the System, including modem access, and adequate interfacing networking
capabilities. Before installing the Equipment at a work site, Motorola will inspect the work site and advise
Customer of any apparent deficiency or non-conformity with the requirements of this Section. This
Agreement is predicated upon normal soil conditions.
6.3. SITE ISSUES. If Motorola or Customer determines that the sites identified in the Technical and
Implementation Documents are no longer available or desired, or if subsurface, structural, adverse
environmental or latent conditions at any site differ from those indicated in the Technical and Implementation
Documents, Motorola and Customer will promptly investigate the conditions and will select replacement sites
or adjust the installation plans and specifications as necessary. If such change in sites or adjustment to the
installation plans and specifications causes a change in the cost or time to perform, the parties will equitably
amend the Contract Price or Performance Schedule, or both, by a change order but the signing of such a
change order by Oshawa will not obligate Oshawa for the payment of any monies whatsoever to Motorola.
Section 7
TRAINING
If Motorola is providing Customer training under this Agreement, it will be described in a written training plan
that is part of the Statement of Work. Customer will notify Motorola immediately if a date change for a
scheduled training program is required. If Motorola incurs additional costs because Customer reschedules a
training program less than thirty (30) days before its scheduled start date, Motorola is entitled to recover
these additional costs but not as against Oshawa.
Section 8
SYSTEM ACCEPTANCE
8.1. COMMENCEMENT OF ACCEPTANCE TESTING. Motorola will provide to Customer at least ten
(10) days notice before the Acceptance Tests commence. System testing will occur only in accordance with
the Acceptance Test Plans.
8.2. SYSTEM ACCEPTANCE. System Acceptance will occur upon successful completion of the
Acceptance Tests described in the Acceptance Test Plans. When System Acceptance occurs, the parties
will memorialize this event by promptly executing a System Acceptance Certificate. If the Acceptance Test
Motorola Contract No.
4
Plans includes separate tests for individual Subsystems or phases of the System, acceptance of the
individual Subsystem or phase will occur upon the successful completion of the Acceptance Tests for such
Subsystem or phase, and the parties will promptly execute an acceptance certificate for the Subsystem or
phase. After completion of the Acceptance Tests, if Customer believes that the System fails the Acceptance
Tests, Customer will provide to Motorola a written notice that includes the specific details of such failure. If
Customer fails to provide to Motorola such notice within forty-five (45) days after completion of the
Acceptance Tests, System Acceptance will be deemed to have occurred as of the completion of the
Acceptance Tests. Minor omissions or variances in the System that do not materially impair the operation of
the System as a whole will not postpone System Acceptance or Subsystem acceptance, but will be corrected
according to a mutually agreed schedule.
8.3. BENEFICIAL USE. Customer acknowledges that Motorola's ability to perform its implementation
and testing responsibilities under this Agreement may be impeded if Customer begins using the System
before System Acceptance. Therefore, Customer may not commence Beneficial Use before System
Acceptance without Motorola's prior written authorization, which Motorola will not unreasonably withhold.
Motorola is not responsible for System performance deficiencies that occur during unauthorized Beneficial
Use. Upon commencement of Beneficial Use, Customer assumes responsibility for the use and operation of
the System.
8.4 FINAL PROJECT ACCEPTANCE. Final Project Acceptance will occur after System Acceptance
and when all deliverables and other work have been completed. When Final Project Acceptance occurs, the
parties will promptly memorialize this final event by so indicating in the appropriate place on the System
Acceptance Certificate.
Section 9 REPRESENTATIONS AND WARRANTIES
9.1. SYSTEM FUNCTIONALITY. Motorola represents that the System will perform consistently with the
System design and functionality specifications contained in the Statement of Work in all material respects.
Upon System Acceptance or Beneficial Use, whichever occurs first, this System functionality representation
is fulfilled. Motorola is not responsible for System performance deficiencies that are caused by ancillary
equipment not furnished by Motorola attached to or used in connection with the System or for reasons
beyond Motorola's control, such as (i) an earthquake, adverse atmospheric conditions, or other natural
causes; (ii) the construction of a building that adversely affects the microwave path reliability or radio
frequency (RF) coverage; (iii) the addition of frequencies at System sites that cause RF interference or
intermodulation; (iv) Customer changes to load usage or configuration outside the specifications; or (v) any
acts of parties who are beyond Motorola's control.
9.2. EQUIPMENT WARRANTY. For two (2) years from the date of System Acceptance or Beneficial
Use, whichever occurs first, Motorola warrants that the Fixed Network Equipment under normal use and
service will be free from material defects in materials and workmanship. If System Acceptance is delayed
beyond six (6) months after shipment of the Equipment by events or causes within Customer's control, this
warranty expires thirty (30) months after the shipment of the Equipment. Motorola warrants Subscriber
Equipment under the terms and conditions of Motorola's five (5) year extended warranty attached hereto as
Exhibit "02".
9.3. MOTOROLA SOF1WARE WARRANTY. Unless otherwise stated in the Software License
Agreement, for two (2) years from the date of System Acceptance or Beneficial Use, whichever occurs first,
Motorola warrants the Motorola Software in accordance with the terms of the Software License Agreement
and the provisions of this Section 9 applicable to the Motorola Software. If System Acceptance is delayed
beyond six (6) months after shipment of the Motorola Software by events or causes within Customer's
control, this warranty expires thirty (30) months after the shipment of the Motorola Software.
9.4. EXCLUSIONS TO EQUIPMENT AND MOTOROLA SOF1WARE WARRANTIES. These warranties
do not apply to: (i) defects or damage resulting from use of the Equipment or Motorola Software in other than
its normal, customary, and authorized manner; (ii) defects or damage occurring from misuse, accident,
liquids, neglect, or acts of God; (iii) defects or damage occurring from testing, maintenance, disassembly,
repair, installation, alteration, modification, or adjustment not provided or authorized in writing by Motorola;
Motorola Contract No.
5
(iv) breakage of or damage to antennas unless caused directly by defects in material or workmanship; (vi)
defects or damage caused by Customer's failure to comply with all applicable industry and Occupational
Health and Safety Act (Ontario) standards; (vii) Equipment that has had the serial number removed or made
illegible; (viii) batteries (because they carry their own separate limited warranty); (ix) freight costs to ship
Equipment to the repair depot; (x) scratches or other cosmetic damage to Equipment surfaces that does not
affect the operation of the Equipment; and (xi) normal or customary wear and tear.
9.5. WARRANTY CLAIMS. Before the expiration of the warranty period, Customer must notify Motorola
in writing if Equipment or Motorola Software does not conform to these warranties. Upon receipt of such
notice, Motorola will investigate the warranty claim. If this investigation confirms a valid warranty claim,
Motorola will (at its option and at no additional charge to Customer) repair the defective Equipment or
Motorola Software, replace it with the same or equivalent product, or, only where the loss of use of the
defective Equipment or Software would not render the balance of the Equipment or Software unusable for
the purpose intended or materially impair the functionality of the System, refund the price of the defective
Equipment or Motorola Software. Such action will be the full extent of Motorola's liability hereunder. If this
investigation indicates the warranty claim is not valid, then Motorola may invoice Customer for responding to
the claim on a time and materials basis using Motorola's current labour rates. Repaired or replaced product
is warranted for the balance of the original applicable warranty period. All replaced products or parts will
become the property of Motorola.
9.6. ORIGINAL END USER IS COVERED. These express limited warranties are extended by Motorola
to the original user purchasing the System for commercial, industrial, or governmental use only, and are not
assignable or transferable except that the representations and warranties provided for in section 9 of this
Agreement shall accrue to the benefit of and shall be enforceable by the successor of any of Ajax,
Clarington, Oshawa, Pickering or Whitby as they exist on the date of this Agreement which is amalgamated
with any other municipality, or from which territory has been annexed to any other municipality, including
territory which remains after an annexation under the jurisdiction of Ajax, Clarington, Oshawa, Pickering or
Whitby or under the jurisdiction of a successor of any of those municipalities.
9.7. DISCLAIMER OF OTHER WARRANTIES. THESE WARRANTIES ARE THE COMPLETE
WARRANTIES FOR THE EQUIPMENT AND MOTOROLA SOFTWARE PROVIDED UNDER THIS
AGREEMENT AND ARE GIVEN IN LIEU OF ALL OTHER WARRANTIES. MOTOROLA DISCLAIMS ALL
OTHER WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING THE IMPLIED
WARRANTIES OR CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.
Section 10
DELAYS
10.1. EXCUSABLE DELAYS. Neither party will be liable for its non-performance or delayed performance
if caused by a "Force Majeure" which means an event, circumstance, or act of a third party that is beyond a
party's reasonable control, such as an act of God, an act of the public enemy, an act of a government entity,
strikes or other labor disturbances, hurricanes, earthquakes, fires, floods, epidemics, embargoes, war, riots,
or any other similar cause. Each party will notify the other if it becomes aware of any Force Majeure that will
significantly delay performance. The notifying party will give such notice promptly (but in no event later than
fifteen days) after it discovers the Force Majeure. If a Force Majeure occurs, the parties will execute a
change order to extend the Performance Schedule for a time period that is reasonable under the
circumstances.
10.2. PROJECT SCHEDULE DELAYS CAUSED BY CUSTOMER. If the Project Schedule is delayed
because of Customer (including any of its other contractors), (i) Customer will make the promised payments
as if no delay occurred; and (ii) the parties will execute a change order to extend the Project Schedule and, if
requested by Motorola, compensate Motorola for all reasonable charges incurred because of such delay.
Delay charges may include costs incurred by Motorola or its subcontractors for additional freight,
warehousing and handling of Equipment; extension of the warranties; travel; suspending and re-mobilizing
the work; additional engineering, project management, and standby time calculated at then current rates; and
preparing and implementing an alternative implementation plan. However, in no event shall
Motorola Contract No.
6
Oshawa be liable for the payment of any monies whatsoever to Motorola under this or any other section,
subsection or article of this Agreement, notwithstanding Oshawa's execution of this Agreement, any change
orders or any other documents whatsoever.
Section 11
DISPUTES
11.1. SETTLEMENT PREFERRED. Motorola and Customer will attempt to settle any claim or controversy
arising from this Agreement (except for a claim relating to intellectual property) through consultation and
negotiation in good faith and a spirit of mutual cooperation. The respective project managers will confer and
attempt to settle a dispute. The dispute will be escalated to appropriate higher-level managers of the parties,
if necessary. If cooperative efforts fail, the dispute will be mediated by a mediator chosen jointly by Motorola
and Customer within thirty (30) days after notice by one of the parties demanding non-binding mediation.
Motorola and Customer will not unreasonably withhold consent to the selection of a mediator, and they will
share the cost of the mediation equally. The parties may postpone mediation until they have completed
some specified but limited discovery about the dispute. The parties may also replace mediation with some
other form of non-binding alternative dispute resolution (UADR").
11.2. LITIGATION. Any claim relating to intellectual property and any dispute that cannot be resolved
between the parties through negotiation or mediation within two (2) months after the date of the initial
demand for non-binding mediation as described above in Section 11.1.shall then be submitted by either party
to a court of competent jurisdiction in the Province of Ontario or Canada. Each party consents to jurisdiction
over it by such a court. The use of ADR procedures will not be considered under the doctrine of laches,
waiver, or estoppel to affect adversely the rights of either party. Either party may resort to the judicial
proceedings described in this section before the expiration of the two-month ADR period if (i) good faith
efforts to resolve the dispute under these procedures have been unsuccessful; or (ii) interim relief from the
court is necessary to prevent serious and irreparable injury to such party or any of its affiliates, agents,
employees, customers, suppliers, or subcontractors.
Section 12
DEFAULT AND TERMINATION
12.1. DEFAULT BY MOTOROLA. If Motorola fails to achieve System Acceptance in accordance with this
Agreement or otherwise breaches a material obligation under this Agreement, Customer may consider
Motorola to be in default, unless Customer or a Force Majeure causes such failure. If Customer asserts a
default, it will give Motorola written and detailed notice of the default. Motorola will have thirty (30) days
thereafter either to dispute the assertion or provide a written plan to cure the default that is acceptable to
Customer. If Motorola provides a cure plan, it will begin implementing the cure plan immediately after receipt
of Customer's approval of the plan.
12.2. DEFAULT BY CUSTOMER. If Customer fails to pay any amount when due under this Agreement,
indicates that it is unable to pay any amount when due, or otherwise breaches a material obligation under
this Agreement, Motorola may consider Customer to be in default, unless Motorola or a Force Majeure
causes such failure. If Motorola asserts a default, it will give Customer written and detailed notice of the
default and Customer will have thirty (30) days thereafter to (i) dispute the assertion, (ii) cure any monetary
default (including interest), or (iii) provide a written plan to cure the default that is acceptable to Motorola. If
Customer provides a cure plan, it will begin implementing the cure plan immediately after receipt of
Motorola's approval of the plan. Motorola may stop work upon a material default by Customer.
12.3. FAILURE TO CURE. If a defaulting party fails to cure the default as provided above in Sections 12.1
or 12.2, unless otherwise agreed in writing, the non-defaulting party may terminate any unfulfilled portion of
this Agreement. In the event of such termination, the defaulting party will promptly return to the non-
defaulting party any of its Confidential Information (as defined in Section 15.1). If Customer is the non-
defaulting party, terminates this Agreement as permitted by this Section, and completes the System through
a third party, Customer may as its exclusive remedy recover from Motorola reasonable costs incurred to
complete the System to a capability not exceeding that specified in this Agreement less the unpaid portion of
the Contract Price. Customer agrees to use its best efforts to mitigate such costs and to provide Motorola
with detailed invoices substantiating the charges.
Motorola Contract No.
7
Sectkm 13
lNDEMNBFjCATiON
13.1. GENERAL INDEMNITY BY MOTOROLA. Motorola will indemnify and hold Customer harmless from
any and all liability, expense, judgment, suit, cause of action, or demand for personal injury, death, or direct
damage to tangible property which may accrue against Customer to the extent it is caused by the
negligence, or intentional acts of Motorola, its subcontractors, or their employees or agents, while performing
their duties under this Agreement, provided that Customer gives Motorola prompt, written notice of any such
claim or suit. Customer shall cooperate with Motorola in its defense or settlement of such claim or suit. This
section sets forth the full extent of Motorola's general indemnification of Customer from liabilities that are in
any way related to Motorola's performance under this Agreement.
13.2. GENERAL INDEMNITY BY CUSTOMER. Customer will indemnify and hold Motorola harmless from
any and all liability, expense, judgment, suit, cause of action, or demand for personal injury, death, or direct
damage to tangible property which may accrue against Motorola to the extent it is caused by the negligence
of Customer, its other contractors, or their employees or agents, while performing their duties under this
Agreement, provided that Motorola gives Customer prompt, written notice of any such claim or suit. Motorola
shall cooperate with Customer in its defense or settlement of such claim or suit. This section sets forth the
full extent of Customer's general indemnification of Motorola from liabilities that are in any way related to
Customer's performance under this Agreement.
13.3. PATENT AND COPYRIGHT INFRINGEMENT.
13.3.1. Motorola will defend at its expense any suit brought against Customer to the extent that it is based
on an Infringement Claim, and Motorola will indemnify Customer for those costs and damages finally
awarded against Customer for an Infringement Claim. Motorola's duties to defend and indemnify are
conditioned upon: (i) Customer promptly notifying Motorola in writing of such Infringement Claim; (H) Motorola
having sole control of the defense of such suit and all negotiations for its settlement or compromise; (iii)
Customer providing to Motorola cooperation and, if requested by Motorola, reasonable assistance in the
defense of the Infringement Claim.
13.3.2. If an Infringement Claim occurs, or in Motorola's opinion is likely to occur, Motorola may at its option
and expense procure for Customer the right to continue using the Equipment or Motorola Software, replace
or modify it so that it becomes non-infringing while providing functionally equivalent performance, or, where
the Infringement Claim occurs following the expiry of the Software warranty provided in the Software License
Agreement, grant Customer a credit for such Equipment or Motorola Software as depreciated and accept its
return. The depreciation amount will be calculated based upon generally accepted accounting standards for
such Equipment and Software.
13.3.3. Motorola will have no duty to defend or indemnify for any Infringement Claim that is based upon (i)
the combination of the Equipment or Motorola Software with any software, apparatus or device not furnished
by Motorola; (ii) the use of ancillary equipment or software not furnished by Motorola and that is attached to
or used in connection with the Equipment or Motorola Software; (Hi) any Equipment that is not Motorola's
design or formula; (iv) a modification of the Motorola Software by a party other than Motorola; or (v) the
failure by Customer to install an enhancement release to the Motorola Software that is intended to correct
the claimed infringement. The foregoing states the entire liability of Motorola with respect to infringement of
patents and copyrights by the Equipment and Motorola Software or any parts thereof.
Section 14
LIMITATION OF LIABILITY
This limitation of liability provision shall apply notwithstanding any contrary provision in this Agreement.
Except for personal injury or death, Motorola's total liability, whether for breach of contract, warranty,
negligence, strict liability in tort, indemnification, or otherwise, will be limited to the direct damages
recoverable under law, but not to exceed the price of the Equipment, Software, or services with respect to
which losses or damages are claimed. ALTHOUGH THE PARTIES ACKNOWLEDGE THE POSSIBILITY
OF SUCH LOSSES OR DAMAGES, THEY AGREE THAT MOTOROLA WILL NOT BE LIABLE FOR ANY
Motorola Contract No.
8
COMMERCIAL LOSS; INCONVENIENCE; LOSS OF USE, TIME, DATA, GOOD WilL, REVENUES,
PROFITS OR SAVINGS; OR OTHER SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL
DAMAGES IN ANY WAY RELATED TO OR ARISING FROM THIS AGREEMENT, THE SALE OR USE OF
THE EQUIPMENT OR SOFTWARE, OR THE PERFORMANCE OF SERVICES BY MOTOROLA
PURSUANT TO THIS AGREEMENT. This limitation of liability will survive the expiration or termination of
this Agreement. No action for breach of this Agreement or otherwise relating to the transactions
contemplated by this Agreement may be brought more than two (2) years after such cause of action first
accrues, except for money due upon an open account. For the purposes of this section, a cause of action
first accrues on the date when a party knows or ought reasonably to have known that a cause of action
exists.
Section 15
CONFIDENTIALITY AND PROPRIETARY RIGHTS
15.1. CONFIDENTIAL INFORMATION.
15.1.1. During the term of this Agreement, the parties may provide the other with Confidential Information.
For the purposes of this Agreement, "Confidential Information" is any information disclosed in written,
graphic, verbal, or machine-recognizable form, and is marked, designated, labeled or identified at the time of
disclosure as being confidential or its equivalent; or if in verbal form is identified as confidential or proprietary
at the time of disclosure and confirmed in writing within thirty (30) days of such disclosure. Notwithstanding
any other provisions of this Agreement, Confidential Information shall not include any information that: (i) is
or becomes publicly known through no wrongful act of the receiving party; (ii) is already known to the
receiving party without restriction when it is disclosed; (iii) is, or subsequently becomes, rightfully and without
breach of this Agreement, in the receiving party's possession without any obligation restricting disclosure; (iv)
is independently developed by the receiving party without breach of this Agreement; or (v) is explicitly
approved for release by written authorization of the disclosing party.
15.1.2. Concerning the Confidential Information provided to it by the other party, each party will: (i) maintain
the confidentiality of such Confidential Information and not disclose it to any third party, except as authorized
by the disclosing party in writing or as required by a court of competent jurisdiction; (ii) restrict disclosure of
Confidential Information to its employees who have a "need to know" and not copy or reproduce such
Confidential Information; (iii) take necessary and appropriate precautions to guard the confidentiality of
Confidential Information, including informing its employees who handle such Confidential Information that it is
confidential and not to be disclosed to others, but such precautions shall be at least the same degree of care
that the receiving party applies to its own confidential information and shall not be less than reasonable care;
and (iv) use such Confidential Information only in furtherance of the performance of this Agreement.
Confidential Information is and shall at all times remain the property of the disclosing party, and no grant of
any proprietary rights in the Confidential Information is hereby given or intended, including any express or
implied license, other than the limited right of the recipient to use the Confidential Information in the manner
and to the extent permitted by this Agreement.
15.2. PRESERVATION OF MOTOROLA'S PROPRIETARY RIGHTS.
15.2.1. Motorola owns and retains all of its Proprietary Rights (as defined in Section 2) in the Equipment and
Software. The third party manufacturer of any Equipment and the copyright owner of any Non-Motorola
Software own and retain all of their Proprietary Rights in the Equipment and Software. Nothing in this
Agreement is intended to restrict the Proprietary Rights of Motorola, any copyright owner of Non-Motorola
Software, or any third party manufacturer of Equipment. All intellectual property developed, originated, or
prepared by Motorola in connection with providing to Customer the Equipment, Software, or related services
remain vested exclusively in Motorola, and this Agreement does not grant to Customer any shared
development rights of intellectual property. This Agreement does not involve any Software that is a "work
made for hire."
15.2.2. Except as explicitly provided in the Software License Agreement, nothing in this Agreement will be
deemed to grant, either directly or by implication, estoppel, or otherwise, any right, title or interest in
Motorola's Proprietary Rights. Concerning both the Motorola Software and the Non-Motorola Software,
Motorola Contract No:
9
Customer agrees not to modify, disassemble, peel components, decompile, otherwise reverse engineer or
attempt to reverse engineer, derive source code or create derivative works from, adapt, translate, merge with
other software, reproduce, or export the Software, or permit or encourage any third party to do so.
Section 16
GENERAL
16. 1. TAXES. The Contract Price does not include any amount for, provincial sales tax, or federal excise
tax (G.S.T.) all of which, if exigible on this transaction, will be paid by Customer, excluding Oshawa, except
as exempt by law. If Motorola is required to payor bear the burden of any such taxes, Motorola will send an
invoice to Customer and Customer, excluding Oshawa, will pay to Motorola the amount of such taxes
(including any applicable interest and penalties) within twenty (20) days after the date of the invoice.
Customer will be solely responsible for reporting the Equipment for personal property tax purposes.
16.2. ASSIGNABILITY. Neither party may assign this Agreement without the prior written consent of the
other party, except that Motorola may assign this Agreement to any of its affiliates or its right to receive
payment without the prior consent of Customer.
16.3. SUBCONTRACTING. Motorola may subcontract any portion of the work, but such subcontracting
will not relieve Motorola of its duties under this Agreement.
16.4 WAIVER. Failure or delay by either party to exercise any right or power under this Agreement will
not operate as a waiver of such right or power. For a waiver of a right or power to be effective, it must be in
writing signed by the waiving party. An effective waiver of a right or power shall not be construed as either (i)
a future or continuing waiver of that same right or power, or (ii) the waiver of any other right or power.
16.5. SEVERABILITY. If a court of competent jurisdiction renders any provision of this Agreement (or
portion of a provision) to be invalid or otherwise unenforceable, that provision or portion of the provision will
be severed and the remainder of this Agreement will continue in full force and effect as if the invalid provision
or portion of the provision were not part of this Agreement.
16.6. INDEPENDENT CONTRACTORS. Each party shall perform its activities and duties hereunder only
as an independent contractor. The parties and their personnel shall not be considered to be an employee or
agent of the other party. Nothing in this Agreement shall be interpreted as granting either party the right or
authority to make commitments of any kind for the other. This Agreement shall not constitute, create, or in
any way be interpreted as a joint venture, partnership or formal business organization of any kind.
16.7. HEADINGS AND SECTION REFERENCES; CONSTRUCTION. The section headings in this
Agreement are inserted only for convenience and are not to be construed as part of this Agreement or as a
limitation of the scope of the particular section to which the heading refers. This Agreement will be fairly
interpreted in accordance with its terms and conditions and not for or against either party.
16.8. GOVERNING LAW. This Agreement and the rights and duties of the parties will be governed by and
interpreted in accordance with the laws of the Province of Ontario and Canada.
16.9. ENTIRE AGREEMENT. This Agreement, including all Exhibits, constitutes the entire agreement of
the parties regarding the subject matter hereof and supersedes all previous agreements, proposals, and
understandings, whether written or oral, relating to such subject matter. This Agreement may be altered,
amended, or modified only by a written instrument signed by authorized representatives of both parties. The
preprinted terms and conditions found on any Customer purchase order, acknowledgment or other form will
not be considered an amendment or modification of this Agreement, even if a representative of each party
signs such document.
16.10. OSHAWA NOT LIABLE. All parties acknowledge and agree that, notwithstanding the
execution of this Agreement by Oshawa, that Oshawa, regardless of the execution of any change order or
document in its capacity as Project Manager or otherwise, shall accrue no liability to Motorola or any other
party whatsoever under the terms of this Agreement, including its exhibts, schedules or appendices, except
Motorola Contract No.
10
with respect to its obligations as a Licencee under the Software Licence Agreement only. The execution of
any documents by Oshawa as the Project Manager shall not bind Oshawa to the payment of any monies to
Motorola or any other party whatsoever and it is acknowledged and agreed that any documents, save for this
Agreement and Exhibit A, that are executed by Oshawa or any of its officers or employees are executed
solely in its capacity as the Project Manager on behalf of the Customer and not on its own behalf and
Oshawa will accrue no liability thereunder whatsoever.
16.11 OSHAW A PURCHASE ORDERS. The Corporation of the City of Oshawa, in its capacity of
Project Manager, will issue one or more purchase orders to Motorola. Notwithstanding that the purchase
orders will come from the City of Oshawa, it is acknowledged and agreed that Oshawa submits such
purchase orders as the Project Manager only on behalf of, Ajax, Clarington, Pickering and Whitby and not on
Oshawa's own behalf and will not be held responsible for the payment of any monies whatsoever to Motorola
or any other party. It is further understood that Motorola shall invoice the Project Manager against such
purchase orders and the Project Manager will forward payments on behalf of Ajax, Clarington, Pickering and
Whitby, but the Project Manager shall not be liable for any payments pursuant to such invoices.
16.13. NOTICES. Notices required under this Agreement to be given by one party to the other must be in
writing and either delivered in person or sent to the address shown below by certified mail, return receipt
requested and postage prepaid (or by a recognized courier service with an asset tracking system, such as
Federal Express, UPS, Purolator or DHL), or by facsimile with correct answerback received, and shall be
effective upon receipt:
Motorola, Canada Limited
Attn: Contracts and Compliance Manager
8133 Warden Avenue
Markham, Ontario L6G 1 B3
Fax (905) 948-5270
Customer
Attn: Commissioner of Corporate Services, City of Oshawa
50 Centre Street South
Oshawa, Ontario L 1 H 3Z7
fax: 905-436-5623
16.14. COMPLIANCE WITH APPLICABLE LAWS. Each party will comply with all applicable federal,
provincial, and local laws, regulations and rules concerning the performance of this Agreement or use of the
System. Customer will obtain and comply with all Industry Canada ("IC") licenses and authorizations
required for the installation, operation and use of the System before the scheduled installation of the
Equipment. Although Motorola might assist Customer in the preparation of its IC license applications, neither
Motorola nor any of its employees is an agent or representative of Customer in IC or other matters.
16.15AUTHORITY TO EXECUTE AGREEMENT. Each party represents to the other that (i) it has obtained
all necessary approvals, consents and authorizations to enter into this Agreement and to perform its duties
under this Agreement; (ii) the person executing this Agreement on its behalf has the authority to do so; (iii)
upon execution and delivery of this Agreement by the parties, it is a valid and binding contract, enforceable in
accordance with its terms; and (iv) the execution, delivery, and performance of this Agreement does not
violate any bylaw, charter, regulation, law or any other governing authority of the party.
16.16 MULTIPLE PARTIES. The rights as contained within this Agreement in favour of the Customer
shall accrue and apply severally to each of Ajax, Clarington, Oshawa, Pickering and Whitby. The rights of
each of Ajax, Clarington, Oshawa, Pickering and Whitby may be severally enforced.
16.17 The obligations as contained within this Agreement as against the Customer shall apply severally
against each of Ajax, Clarington, Pickering and Whitby only and the failure on the part of one to comply with
the terms of this Agreement shall not be taken as a failure on the part of any other or all of them under this
Agreement. Notwithstanding anything in this Agreement, Oshawa shall have no obligations under this
Agreement to any party whatsoever.
16.18 This Agreement may be executed in counterparts by the execution of Schedules "A", "B", "C", "0"
and "E" hereto by Ajax, Clarington, Oshawa, Pickering and Whitby, respectively.
16.19. SURVIVAL OF TERMS. The following provisions shall survive the expiration or termination of this
Agreement for any reason: Sections 3.6 and 3.7 (concerning Software licensing); Section 11 (Disputes);
Motorola Contract No.
11
.
.
.
Section 13.3 (Patent and Copyright Infringement); Section 14 (Limitation of Liability); 15.1 (Confidential
Information); and 15.2 (Preservation of Motorola's Proprietary Rights).
The parties hereby enter into this Agreement as of the Effective Date.
o lelL. 0
7l"'l2t? rml2y J-tANA 6F'f2
-nthA"f) 2~ ~OOZ-
I have the authority to bind the Corporation
f'15.1fftikCiI6"
~ppr(.:.'..':',:..... T~ F ~~
. , " - arm
IVi\....-
Con~act~(;'::O.'!2E'ian~ej
Motorola Contract No.
12
Schedule "An
Sianatorv Paae for the Town of Aiax
This is Schedule "A" to the Communications System Agreement between Motorola Canada Limited through
its Commercial, Government, and Industrial Solutions Sector, North America Group and the Corporation of
the Town of Ajax, the Corporation of the Municipality of Clarington, the Corporation of the City of Oshawa, the
Corporation of the City of Pickering and the Corporation of the Town of Whitby dated March 27, 2002.
A ?FTHE
L,
Mayor
~~
Cler~ / . .;---
Date /~ cP7 ;d't<<
Motorola Contract No.
/3
..{1(
Schedule "B"
SIGnatorv paae for the' MunlclDalltv of Clarinaton -
This is Schedule uen to the Communications System Agreement between Motorola Canada Limited through
its Commercial, Government, and Industrial Solutions Sector, North America Group the Corporation of tne
Town of Ajax. the corporation of the Municipality of Clarington, the Corporation of the City of Oshawa. the
Corporation of the City of Pickering and the Corporation of the Town of Whitby dated March 27. 2002.
THE CORPORATION OF THE
MUNICIPAL! F CLARlNGTON
Mayor
~
D~~ March 27, 2002
M~l'\)la C~I1~ct No.
',', .:~ </~~ ..;..~:;
. 'j':.:';':;:;":~.::1:'" : :
. ".; ~ .
lif
..~ .
,"! I
. "
'''j
l..:.:.
. ~ ,-"." :':
.. : . - ~.". j<' : ~~. I
,
,. ,
.'1 .
: .'-: .
. ;::".~ ~:...:.,.
Schedule "C"
Sianatorv Paae for the City of Oshawa
This is Schedule "C" to the Communications System Agreement between Motorola Canada Limited through
its Commercial, Government, and Industrial Solutions Sector, North America Group and the Corporation of
the Town of Ajax, the Corporation of the Municipality of Clarington, the Corporation of the City of Oshawa,
the Corporation of the City of Pickering and the Corporation of the Town of Whitby dated March 27, 2002.
THE CORPORATION OF mE
~OSHAWA
~r ,.I:~. .../J.
Mayor
~'-
Clerk
Date: -.t:f Ovrc..h ')..1 ) ).-.0 0 )....
Motorola Contract No.
IS"
?
Schedule "D"
Sianatorv Paae for the City of Pickerina
This is Schedule "D" to the Communications System Agreement between Motorola Canada Limited through
its Commercial, Government, and Industrial Solutions Sector, North America Group and the Corporation of
the Town of Ajax, the Corporation of the Municipality of Clarington, the Corporation of the City of Oshawa,
the Corporation of the City of Pickering and the Corporation of the Town of Whitby dated March 27, 2002.
THE CORPORATION OF THE
CITY OF PICKERING
~~
~a-y:~-. Arthurs
.#~
Clerk {7 Bruce Taylor
Date: March 27 t 2002
Motorola Contract No.
l~
.,...,-
Schedule "E"
SiQnatorv PaQe for the Town of Whitby
This is Schedule "E" to the Communications System Agreement between Motorola Canada Limited through
its Commercial, Government, and Industrial Solutions Sector, North America Group and the Corporation of
the Town of Ajax, the Corporation of the Municipality of Clarington, the Corporation of the City of Oshawa,
the Corporation of the City of Pickering and the Corporation of the Town of Whitby dated March 27, 2002.
THE CORPORATION OF THE
TOWN OF WIDTBY
~#'4"'~~
Mayor. 0" ~. "0.
'"" ]v, "
0(. ~ /It
Clerk
Date:
Motorola Contract No.
17
~
Exhibit A
Software License Agreement
Motorola, Canada Limited, through its Commercial, Government, and Industrial Solutions Sector ("Motorola"
or "Licensor") and the Corporation of the Town of Ajax, the Corporation of the Municipality of Clarington, the
Corporation of the City of Oshawa, the Corporation of the City of Pickering, and the Corporation of the Town
of Whitby (jointly and severally referred to as "Licensee"), hereby enter into this Software License
Agreement ("Agreement"). For good and valuable consideration, the parties agree as follows:
Section 1
SCOPE
Licensor will provide proprietary software and/or radio communications, computer, or other electronic
products ("Products") containing embedded or pre-loaded proprietary software to Licensee. All such software
that is owned by Motorola Inc. or Printrak International Incorporated, a Motorola Company ("Printrak") is
referred to as "Software." Product and Software documentation that specifies technical and performance
features and capabilities, and the user, operation and training manuals for the Software (including all physical
or electronic media upon which this information is provided) are collectively referred to as "Documentation."
This Agreement contains the terms and conditions pursuant to which Licensor will license, and Licensee may
use, the Software and Documentation. Licensor warrants that it is authorized to license any Software owned
by Motorola Inc. or Printrak under the terms and conditions set forth in this Agreement.
Section 2
GRANT OF LICENSE
Licensor hereby grants to Licensee a personal, non-transferable (except as permitted in Section 8 below),
limited, and non-exclusive license under Licensor's applicable proprietary rights to use the Software and
related Documentation for the purposes for which they were designed and in accordance with the terms and
conditions of this Agreement. The license granted authorizes Licensee to use the Software only in object
code format and does not grant any rights to source code. For the purpose of this Agreement each of the
Corporation of the Town of Ajax, the Corporation of the Municipality of Clarington, the Corporation of the City
of Oshawa, the Corporation of the City of Pickering and the Corporation of the Town of Whitby is declared to
be a separate Licensee.
Section 3
LIMITATIONS ON USE
3.1. Licensee may use the Software only for Licensee's internal business purposes and only in
accordance with the Documentation. Any other use of the Software is strictly prohibited. Licensee may not
for any reason modify, disassemble, peel components, decompile, otherwise reverse engineer or attempt to
reverse engineer, derive source code, create derivative works from, adapt, translate, merge with other
software, copy, reproduce, distribute, or export any Software or permit or encourage any third party to do so,
except that Licensee may make one copy of Software provided by Licensor to be used solely for archival,
back-up, or disaster recovery purposes. Licensee must reproduce all copyright and trademark notices on all
copies of the Software and Documentation.
3.2. Licensee may not copy onto or transfer Software installed in one Product device onto another
device. Notwithstanding the preceding sentence, Licensee may temporarily transfer Software installed on
one device onto another if the original device is inoperable or malfunctioning, provided that Licensee
provides written notice to Licensor of such temporary transfer and such temporary transfer is discontinued
when the original device is returned to operation. Upon Licensor's written request, Licensee must provide to
Licensor a written list of all Product devices in which the Software is installed and being used by Licensee.
3.3. Concerning Motorola's Radio Service Software ("RSS"), if applicable, Licensee must purchase a
copy for each location at which Licensee uses RSS. Licensee's use of RSS at an authorized location does
not entitle Licensee to use or access the RSS remotely. Licensee may make one additional copy for each
Motorola Contract No.
computer owned or controlled by licensee at each such location. Upon Licensor's written request, licensee
must provide to licensor a written list of all locations where licensee uses or intends to use RSS.
Section 4
OWNERSHIP AND TITLE
Title to all copies of Software will not pass to Licensee at any time but remains vested exclusively in Motorola
Inc. or Printrak. Motorola Inc. and Printrak own and retain all of their Proprietary Rights in any form
concerning the Software and Documentation, including all rights in patents, patent applications, inventions,
copyrights, trade secrets, trademarks, trade names, and other intellectual properties (including any
corrections, bug fixes, enhancements, updates, or modifications to or derivative works from the Software
whether made by Licensor or another party). Nothing in this Agreement is intended to restrict the
proprietary rights of Motorola Inc. or Printrak or to grant by implication or estoppel any Proprietary Rights. All
intellectual property developed, originated, or prepared by Motorola Inc. or Printrak in connection with
providing to Licensee Software, Products, or related services remain vested exclusively in Motorola Inc. or
Printrak, and this Agreement does not grant to Licensee any shared development rights of intellectual
property. This Agreement does not involve any software that is a "work made for hire."
Section 5
CONFIDENTIALITY
Licensee acknowledges that the Software and Documentation contain Motorola inc. and Printrak's valuable
proprietary and confidential information and trade secrets. Licensee will take necessary and appropriate
precautions to maintain and guard the confidentiality of the Software and Documentation, using at least the
same degree of care that Licensee applies to its own confidential information but not less than reasonable
care. Precautions will include informing Licensee's employees and agents who are authorized to use the
Software and Documentation that such information is confidential and may not to be disclosed to others.
Licensee will not disclose the Software and Documentation to any third party except as permitted by this
Agreement or expressly in writing by licensor. Licensee will limit access to the Software and Documentation
to Licensee's employees and agents who need to know and are authorized to use the Software and
Documentation as permitted by this Agreement.
Section 6
LIMITED WARRANTY
6.1. The warranty period for the Software will commence upon the date of System Acceptance or
beneficial use, whichever occurs first, and will continue for two (2) years subject to the remainder of this
Section 6.1. For Integration Framework software products, Printrak's Law Records Management System
software products and Printrak's Premier CAD SETM software products, the warranty period shall commence
as stated in the applicable agreement and will continue for 120 days. For Printrak Printrak's LiveScan
software products, the warranty period shall commence as stated in the applicable agreement and will
continue for 90 days. For Software that is application software that is provided on a per unit basis, the
warranty period for subsequent units licensed is the remainder (if any) of the initial warranty period or, if the
initial warranty period has expired, the remainder (if any) of the term of the applicable Software Maintenance
and Support Agreement.
6.2. During the applicable warranty period, Licensor warrants that the unmodified Software, when used
properly and in accordance with this Agreement, will be free from a reproducible defect that eliminates the
functionality or successful operation of a feature critical to the primary functionality or successful operation of
the system. Whether such defect occurs will be determined solely with reference to the Documentation. For
Software involving radio frequency systems and Products, the primary functionality of a voice communication
system is subscriber-to-subscriber, subscriber-to-dispatcher, and dispatcher-to-subscriber voice
communication; and the primary functionality of a data communication system is point-to-point data
transmission. Licensor does not warrant that Licensee's use of the Software or Products will be uninterrupted
or error-free or that the Software or the Products will meet Licensee's particular requirements.
6.3. Before the expiration of the applicable warranty period, Licensee must notify Licensor in writing if the
Software does not conform to this warranty. Upon receipt of such notice, Licensor will investigate the
Motorola Contract No.
2
warranty claim. If this investigation confirms a valid warranty claim, Licensor will (at its option and at no
additional charge to Licensee) repair the defect, replace the defective Software with the same or equivalent
software, or refund the price of the defective Software or individual Product in which the Software is
embedded or for which it was provided. Such action will be the full extent of Licensor's liability and
Licensee's sole remedy for a breach of this warranty. If the investigation indicates the warranty claim is not
valid, then Licensor may invoice Licensee for responding to the claim on a time and materials basis using
Licensor's current labor rates.
6.4. LICENSOR DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE
TRANSACTION COVERED BY THIS AGREEMENT IS A LICENSE AND NOT A SALE OF GOODS;
THEREFORE, IT IS NOT COVERED BY THE UNIFORM COMMERCIAL CODE.
6.5 For any Non-Motorola Software delivered hereunder, Motorola shall assign to Licensee all applicable
warranties made available from the copyright owner.
Section 7
LIMITATION OF LIABILITY
EXCEPT FOR PERSONAL INJURY OR DEATH, LICENSOR'S TOTAL L1AIBLlTY, WHETHER FOR
BREACH OF CONTRACT, WARRANTY, NEGLIGENCE, STRICT LIABILITY IN TORT, OR OTHERWISE,
WILL BE LIMITED TO LICENSEE'S DIRECT DAMAGES RECOVERABLE UNDER LAW, BUT NOT TO
EXCEED THE PRICE FOR THE SOFTWARE, THE PRODUCTS PROVIDED BY LICENSOR IN WHICH
THE SOFTWARE IS EMBEDDED OR INSTALLED, OR THE SERVICES SPECIFICALLY RELATED TO
THE SOFTWARE WITH RESPECT TO WHICH LOSSES OR DAMAGES ARE CLAIMED. ALTHOUGH THE
PARTIES ACKNOWLEDGE THE POSSIBILITY OF SUCH LOSSES OR DAMAGES, THEY AGREE THAT
LICENSOR WILL NOT BE LIABLE FOR ANY COMMERCIAL LOSS, INCONVENIENCE; LOSS OF USE,
TIME, DATA, GOOD WILL, REVENUES, PROFITS OR SAVINGS; OR OTHER SPECIAL, INCIDENTAL,
INDIRECT, OR CONSEQUENTIAL DAMAGES ARISING FROM THIS AGREEMENT OR THE SALE OR
USE OF ANY SOFTWARE OR PRODUCTS. This Limitation of Liability provision will survive the termination
of this Agreement. Licensee must bring any action under this Agreement within one (1) year after the cause
of action arises.
Section 8
TRANSFERS
Licensee may not transfer Software to any third party without Licensor's prior written consent, which
consent may be withheld in Licensor's reasonable discretion and may be conditioned upon the transferee
paying all applicable license fees and agreeing to be bound by this Agreement. Notwithstanding the
preceding sentence, if Licensee transfers ownership of radio Products to a third party, Licensee may assign
its rights to use the Software (other than Radio Service Software and Motorola's FLASHport@ Software)
embedded in or furnished for use with those radio Products; provided that Licensee transfers all copies of
such Software and the related Documentation to the transferee, and the transferee executes a transfer form
to be provided by Licensor upon request (which form obligates the transferee to be bound by this
Agreement).
Section 9
TERM AND TERMINATION
Licensee's right to use the Software will begin when this Agreement is mutually executed by both parties and
will continue in perpetuity unless Licensee breaches this Agreement, in which case it shall be terminated
immediately without notice by Licensor. Notwithstanding the foregoing, the Licensor acknowleges that there
is more than one Licensee under this Agreement and that a breach of this Agreement by less than all of the
Licensees shall not entitle the Licensor to terminate this Agreement as against those licensees not in breach.
In addition to termination, Licensor shall be entitled to all available remedies at law or in equity (including
immediate injunctive relief without proving damages and repossession of all non-embedded Software and
associated Documentation. Licensee acknowledges that its breach of this Agreement will result in
irreparable harm to Licensor for which monetary damages would be inadequate. Within thirty (30) days after
Motorola Contract No.
3
termination of this Agreement, Licensee must certify in writing to Licensor that all copies of the Software and
Documentation have been returned to Licensor or destroyed and are no longer in use by Licensee.
Section 10
NOTICES
Notices required under this Agreement to be given by one party to the other must be in writing and either
delivered in person or sent to the address shown below by certified mail, return receipt requested and
postage prepaid (or by a recognized courier service with an asset tracking system, such as Federal Express,
UPS, Purolator or DHL), and shall be effective upon receipt. Change of address must be in writing to the
other party.
Licensor
Attn: Contracts and Compliance Manager
8133 Warden Avenue
Markham, Ontario L6G 1 B3
Fax (905) 948.5270
Licensee
Attn: Commissioner of Corporate Services, City of Oshawa
50 Centre Street South
Oshawa, Ontario L 1 H 327 _
fax: 905-436-5623
Section 11
GENERAL
11.1. COPYRIGHT NOTICES. The existence of a copyright notice on the Software will not be construed
as an admission or presumption that public disclosure of the Software or any trade secrets associated with
the Software has occurred.
11.2. COMPLIANCE WITH LAWS. Licensee will comply with all applicable laws and regulations, including
export laws and regulations of Canada and the United States. Licensee will not, without the prior
authorization of Licensor and the appropriate governmental authority of Canada or the United States, in any
form export or re-export, sell or resell, ship or reship, or divert, through direct or indirect means, any item or
technical data or direct or indirect products sold or otherwise furnished to any person within any territory for
which the Canadian or Unites States Government, or any agency thereof, at the time of such action, requires
an export license or other governmental approval. Violation of this provision shall be a material breach of
this Agreement, permitting immediate termination by Licensor.
11 .3. WAIVERS. Failure or delay by either party to exercise any right or power under this Agreement will
not operate as a waiver of such right or power. For a waiver of a right or power to be effective, it must be in
writing signed by the waiving party. An effective waiver of a right or power shall not be construed as either a
future or continuing waiver of that same right or power, or the waiver of any other right or power.
11.4. ASSIGNMENTS. Licensor may assign any of its rights or subcontract any of its obligations under
this Agreement, or encumber or sell any of its rights in any Software, with prior written notice to Licensee.
11.5. ENTIRE AGREEMENT AND AMENDMENT. This Agreement constitutes the entire agreement of the
parties regarding Licensee's use of the Software and may be altered, amended, or modified only by a written
instrument signed by an authorized representative of each party, except that Licensor may modify this
Agreement as necessary to comply with applicable laws and regulations. This Agreement will be fairly
interpreted in accordance with its terms and conditions and not for or against either party.
11.6. GOVERNING LAW. This Agreement will be governed by the laws of Canada to the extent that they
apply and otherwise by the laws of the Province of Ontario.
11.7. SEVERABILITY. If any provision of this Agreement is determined by a court of competent
jurisdiction to be invalid or otherwise unenforceable, that provision will be severed and the remainder of this
Agreement will remain in full force and effect.
Motorola Contract No.
4
.
.
.
11.8 All rights, benefits and obligations under this License Agreement shall accrue to and are binding
upon Licensee and shall be enforceable by and against the successor of any of Ajax, Clarington, Oshawa,
Pickering or Whitby as they exist on the date of this Agreement which is amalgamated with any other
municipality, or from which territory has been annexed to any other municipality, including territory which
remains after an annexation under the jurisdiction of Ajax, Clarington, Oshawa, Pickering or Whitby or under
the jurisdiction of a successor of any of those municipalities.
In witness whereof, the parties have caused duly authorized representatives to execute this Software
License Agreement on the dates set forth below.
11.9 MULTIPLE LICENSEES. The rights and obligations as contained within this Agreement in
favour of, and as against, the Licensee shall accrue and apply severally to and against, as applicable, each
Licensee and the failure on the part of one to comply with the terms of this Agreement shall not be taken as a
failure on the part of any other or all of them under this Agreement. The rights of each Licensee may be
severally enforced. This Agreement may be executed in counterparts by the execution of Schedules "A", "S",
"C", "0" and "E" hereto by Ajax, Clarington, Oshawa, Pickering and Whitby, respectively.
Licens~, . ~,,,'i'_ __
Sy: . '
Name:' o~tLJ(,IPNO
Title: "7El' e-:::!3f.'F ~ 6ft
Oate: "'h( 't.. z,b()'L-
I have the authority to bind the Corporation
fIi?J'j~~Hlg L
/' Appro\[.> Fnrm :
t ~'i1i-; ---. I [
. ~o?!r'3c;ts (;Cornpliancf)
Motorola Contract No.
5
Schedule "A"
Sianatorv Paae for the Town of Aiax
This is Schedule "~' to the Software Licence Agreement, being Exhibit A to the Communications System
Agreement between Motorola Canada Limited through its Commercial, Government, and Industrial Solutions
Sector, North America Group and the Corporation of the Town of Ajax, the Corporation of the Municipality of
Clarington, the Corporation of the City of Oshawa, the Corporation of the City of Pickering and the
Corporation of the Town of Whitby dated March 27, 2002.
Mayor
_..~~
ClerV~- ~
Dat~. - ~~ d't1)JI
Motorola Contract No.
~
%
Schedule "B"
Si9natorv Pa98 for the MunlclDalitv of Clarlnaton
This is Schedule "B" to the Software Licence Agreement, being Exhibit A to the Communications System
Agreement between Motorola Canada Limited through its Commercial, Government, and Industrial Solutions
Sector, North America Group and the Corporation of the Town of Ajax, the Corporation of the Municipality of
Clarington, the Corporation of the City of Oshawa, the Corporation of the City of Pickering and the
Corporation of the Town of Whitby dated March 27. 2002.
Mayor. .
Cler~
Date: . .March-).7, 2002
Mctorclla;Contr.iaNp.,
-],.
I' "
, 1. I . :,~.
** TOTRL PRGE.03 **
Schedule "C"
SiQnatorv PaQe for the City of Oshawa
This is Schedule "C" to the Software Licence Agreement, being Exhibit A to the Communications System
Agreement between Motorola Canada Limited through its Commercial, Government, and Industrial Solutions
Sector, North America Group and the Corporation of the Town of Ajax, the Corporation of the Municipality of
Clarington, the Corporation of the City of Oshawa, the Corporation of the City of Pickering and the
Corporation of the Town of Whitby dated March 27,2002.
THE CORPORATION OF THE
CITY OF OSHA W A
~~- / ~...'p.
~7-
~~<:.-
Clerk
Date:
MavrJ\ ~l \ d<Jo'A
\
Motorola Contract No.
~
~
Schedule "0"
Signatory Page for the City of Pickering
This is Schedule "0" to the Software Licence Agreement, being Exhibit A to the Communications System
Agreement between Motorola Canada Limited through its Commercial, Government, and Industrial Solutions
Sector, North America Group and the Corporation of the Town of Ajax, the Corporation of the Municipality of
Clarington, the Corporation of the City of Oshawa, the Corporation of the City of Pickering and the
Corporation of the Town of Whitby dated March 27, 2002.
THE CORPORATION OF THE
CITY OF PICKERING
.~~
Mayor ~.~.raY ~eA rthurs
-c. .'~
- .
. --.
-. ._~
Clerk~. ffruce 1-ay 10 r
Date: March?7, ?OO?
Motorola Contract No.
q
..A-"
Schedule "E"
SiQnatorv PaQe for the Town of Whitby
This is Schedule "En to the Software Licence Agreement, being Exhibit A to the Communications System
Agreement between Motorola Canada Limited through its Commercial, Government, and Industrial Solutions
Sector, North America Group and the Corporation of the Town of Ajax, the Corporation of the Municipality of
Clarington, the Corporation of the City of Oshawa, the Corporation of the City of Pickering and the
Corporation of the Town of Whitby dated March 27,2002.
THE CORPORATION OF THE
TOWN OF WHITBY
~4~
Mayor ,,- '
Clerk
Date:
Motorola Contract No.
[0
~
SYSTEM ACCEPTANCE CERTIFICATE
Customer Name:
Project Name:
This System Acceptance Certificate memorializes the occurrence of System Acceptance.
Motorola and Customer acknowledge that:
1. The Acceptance Tests set forth in the Acceptance Test Plan have been successfully
completed.
2. The System is accepted.
Customer Representative:
Motorola Representative:
Signature:
Print Name:
Title:
Date:
Signature:
Print Name:
Title:
Date:
FINAL PROJECT ACCEPTANCE:
Motorola has provided and Customer has received all deliverables, and Motorola has performed all other
work required for Final Project Acceptance.
Customer Representative:
Motorola Representative:
Signature:
Print Name:
Title:
Date:
Signature:
Print Name:
Title:
Date:
Motorola Contract No.
EXHIBIT "E"
PAYMENT SCHEDULE
Except for the first payment which is due when Customer executes this Agreement,
Customer agrees to make payments to Motorola within twenty (20) days after the date of
invoices that will be submitted by Motorola according to the following payment
schedule:
1. 30% of the total contract price will be due when Customer executes this
Agreement;
2. 60% of the total contract price will be invoiced immediately after the Equipment
is shipped from Motorola's facilities;
3. 5% of the total contract price will be invoiced immediately after System
Acceptance; and
4. 5% of the total contract price will be invoiced immediately after Project
Completion.
Motorola Contract No.
EXHIBIT C-1
SECTION 2
SYSTEM FUNCTIONAL
SPECIFICATION
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
TABLE OF CONTENTS
1110 I NTRO DUCTION II.... llla"II.II... ...III..II.....IlIlIl..IIIUI....... le..IIIl.'lIelllll.'II.....'. III .1I11111111111111111111111 1111 1I..llll8 1
2.0 GENERAL SYSTEM OVERViEW........................................................... 1
2.1 System Architecture .... .... ...... ...... .... ................. ............... .......... ... ..... ...... 1
2.2 System Capacity and Expandability ........................................................ 2
2.2. 1 MTC3600 Controller... ................. ..................................................................... 2
2.2.2 Simulcast System................................. ............................................................ 2
3.0 INFRASTRUCTURE DESCRIPTION ...................................................... 3
3.1 Prime Site and Co-located Remote Site (Oshawa City Hall) ................... 3
3. 1. 1 Site Description.... ..... ....................... ............... ................. ............. .................... 3
3. 1.2 Site Equipment.......................... ...................... ......................................... ........ 3
3. 1.3 GPS / Rubidium Frequency Standard ........................................ ....................... 4
3. 1.4 Digital Multiplex Equipment............................................................................... 4
3. 1.5 Site Backup Power................. .......................................................................... 7
3.2 Transmit / Receive Sites.......................................................................... 7
3.2. 1 Site Description...................................................................................... ........... 7
3.2.2 Site Equipment... .......... ....................... ................................................. ............ 8
3.2.3 Remote Site Simulcast Controller ......................................................... ...........10
3.2.4 Quantar Trunking Repeater........ ..... .................................... ............................ 11
3.2.6 GPS / Rubidium Frequency Standard .......................................................... .... 13
3.2.7 Digital Multiplex Equipment.............................................................................. 14
3.2.8 Site Antenna, Transmitter Combining, and Receiver Multicoupling Systems.... 15
3.3 Battery Backup Power ........................................................................... 19
4.0 CONVENTIONAL STATIONS ............................................................... 20
5.0 FIRE DEPARTMENTS PAGING ........................................................... 20
6.0 SITE LINKING SUBSySTEM................................................................ 20
6.1 System Overview......... ....... ..... ..... ........ ........................ ......................... 20
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
8.1.1 DigiTac Comparator .............................................................................. 24
8.2 Analog Audio Processing and Distribution............................................. 25
8.2.1 Universal Simulcast Controller Interface (USCI)...............................................25
8.2.2 Digital Simulcast Modem /I (DSM /I) ................................................................25
9.0 TRUNKING SYSTEM OPERATIONAL FEATURES............................. 26
9.1 Physical Parameters. ... ........ ........ ..... ......... ... ........... ..................... ... ...... 26
9.2 Trunking Features - Infrastructure ......................................................... 27
10.0 GOLD ELITE CONSOLE UPGRADE AND REMOTE DISPATCH
10.1
10.1.1
10.1.2
10.1.3
10. 1.4
10.1.5
10.1.6
10. 1.7
10.1.8
10.1.9
10.2
10.3
10.4
11.0
11.1
11.2
11.2.1
11.2.2
11.2.3
12.0
12.1
12.1.1
12.1.2
12.1.3
12.2
12.3
12.3.1
12.3.2
12.3.3
CENTRE .............. ........ I..... I' ....1. II ...... I' II I........ ............ I' ....... ..... II.. .....1111. 30
Gold Series Central Electronics Bank (CEB) ......................................... 30
Trunking Base Interface Module (TBIM) ..........................................................31
Base Interface Module (BIM) .... .......... ............................... ....................... .......31
Logging Recorder Interface (LORI)...... .......................................................... ..31
Trunked Input/Output Multiplexed Interface (TIMI) ...........................................32
Remote Operator Console Interface (ROCI) ....................................................32
Console Operator Interface Module (COIM)......................... ............................32
Auxiliary Input/Output Module (AUX I/O).................. ........................................32
Power Supply..... ................... ........ ........... ......................................... ............ ..32
Battery Backup............................................................................................... .32
CEB Configuration ................ ............. ....................... ............................. 33
Console Operator Positions......................... ........ ............ ......... ........ ..... 33
Technical Specifications................................ ........................................ 34
TRUNKING SYSTEM PERFORMANCE............................................... 35
System Access...................................................................................... 35
Simulcast Optimization Parameters......................................... .............. 35
Transmitter Carrier Frequencies..................................................................... .35
Amplitude Adjustment...................... .............................................................. ..35
Phase Delay.................................................................................................... 36
TRUNKING SYSTEM FAILURE OPERATION ..................................... 36
System Redundancy and Reliability...................................................... 36
Redundant Prime Site Controller........... ........................................................ ..36
Redundant Trunking Control Channels .......................................................... ..37
Backup Power........................................................................ ........................ .37
System Diagnostics and Alarms............................................................ 37
Failure Scenarios................................................................................... 38
Prime Simulcast Controller Failure.................................................................. .38
Console Operator Position Failure .......................... ........................ .................39
Console System CEB Failure.......................................................................... .39
Use or disclosure of this proposal is subject to the restrictiolls 011 the title page.
Motorola Confidential Proprietary
@ MOTOROI.A
11
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
12.3.4
12.3.5
12.3.6
12.3.7
12.3.8
12.3.9
13.0
13.1
14.0
14.1
14.2
14.3
14.4
15.0
15.1
15.2
16.0
16.1
17.0
17.1
17.2
17.3
17.4
Voting System Failure..................................................................................... .39
Analog Audio Distribution Failure.....................................................................40
Remote Site Controller Failure............................................ .......................... ...40
Control Channel Failures.............................................................................. ...40
Voice Channel Failure....................................... ............................................. ..41
T1 Network Failures........................................................................................ .42
SYSTEM COVERAG E....... ............. ........ ......................... ......... ............ 42
RF Coverage Design............................................................................. 42
SYSTEM OPTIMIZATION AND MAINTENANCE EQUiPMENT........... 43
Test Equipment..................................................................................... 43
Spares........................................................................ ........................... 43
Redundancy.......................................................................................... 44
Remote Site Channel Bank Data Acquisition......................................... 44
MOBILE SUBSCRIBER EQUiPMENT.................................................. 44
MCS2000 Mobile ........ .............. ..... ......... ................... ........... ................. 44
Optional Fire Hall Fixed Mobiles............................................................ 47
PORTABLE SUBSCRIBER EQUIPMENT ............................................ 47
XTS3000 Portable................................................................................. 47
OPTIONAL VEHICULAR REPEATER.................................................. 49
Purpose................................................................................................. 49
Overview............................................................................................... 49
Features................................................................................................ 50
Vehicular Repeater Simulcast Prevention ............................................. 51
Use or disclosure of this proposal is subject to the restrictions on the title page.
Motorola Confidential Proprietary
@ MOTOROLA
111
Fire Departments of Durham Region
TRlJNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
SYSTEM FUNCTIONAL SPECIFICATION
1.0 INTRODUCTION
This document details all of the functional and technical elements of the SmartNet Simulcast
Analog Trunking System, as proposed by Motorola for the Fire Departments of Durham Region.
2.0
GENERAL SYSTEM OVERVIEW
2.1
System Architecture
The voice radio trunking system will be a wide-area, 5-site, 9-channel SmartNet Simulcast
Analog Trunking System, operating in the 800 MHz trunking band. Refer to the System Block
Diagram in Appendix A of this document. The system will include five (5) transmit/receive
(transceiver) sites to provide the coverage described in Section 13 of this document, and in the
Coverage Design and Verification Methodology Document. All of the trunked channels will
support analog voice communications. The sites, which will be used by the system, are:
· Oshawa City Hall (Prime Site and Co-located Remote Site)
· Pickering (Remote Site)
· Whitby (Remote Site)
· Bowmanville (Remote Site)
· Orono (Remote Site)
· Oshawa Fire Hall #1 (Communications Centre)
· Pickering/Ajax Remote Dispatch Center
The Oshawa City Hall will serve as the Prime Site. The system Remote Sites will be linked to the
Prime Site via a leased or dedicated T1 facility. Leased or dedicated T 1 facilities may consist of
fiber optic or copper wire links. The T 1 transport network must satisfy certain technical
constraints, which are described in Section 6 of this document. Motorola is not proposing to
supply the T1 transport network.
Use or disclosure of this proposal is subject to the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
The new system infrastructure will integrate existing CentraCom Elite dispatch console
equipment, and a System Management terminal currently located at Oshawa Fire Hall #1.
Existing conventional base stations used for paging, will be replaced.
Please note that, during the upgrade operations, the system will experience some interruptions.
2.2 System Capacity and Expandability
The Trunked Radio System infrastructure will include expansion capacity, with respect to sites,
channels, and subscribers. The expansion capability of some of these system elements is
described below.
2.2. 1
MTC3600 Controller
The MTC3600 Controller will be configured for a Simulcast system and will be equipped for a
capacity of approximately 48,000 individual unit IDs, and 4,000 talkgroups (2000 talkgroups if
Priority Monitor is used).
2.2.2 Simulcast System
The Simulcast System will consist of five sites and nine channels. It can be expanded to a
maximum of 10 simulcast sites (transmit/receive or receive only), and a maximum of 28
channels.
Table 2-1 summarizes the system infrastructure capacity.
Table 2-1 - System Infrastructure Capacity
Equipped Capacity
Simulcast System Sites 5 10
Channels 9 28
Talkgroups 4000 (2000) 4000 (2000)
Radio Unit IDs 48000 48000
Use or disclosllre of th is proposal is subject/(} the restrictiolls 011 the title page.
Motorola Confidential Proprietary
@ MOTOROI.A February 2002
2
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
3.0
INFRASTRUCTURE DESCRIPTION
3.1 Prime Site and Co-located Remote Site (Oshawa
City Hall)
3. 1. 1 Site Description
The Prime Site will be located at Oshawa City Hall. All of the trunking control, audio
processing, and audio distribution equipment will reside at the Prime Site. The equipment at the
Prime Site will be mounted in 19" lockable cabinets. Refer to the Rack Layout Diagrams in
Appendix A of the Site Requirements Plan.
3. 1.2 Site Equipment
The major equipment components that will be located at the Prime Site are listed in Table 3-1.
For the components related to the co-located Remote Site see Table 3-5.
Table 3-1 - Prime Site Equipment
Equipment
Prime Site Simulcast MTC3600 Controller
Redundant Prime Site Simulcast MTC3600 Controller
Universal Simulcast Controller Interface
Qty
1
1
9
9
3
1
DigiTac Voting Comparators
Premysis Channel Banks
GPS / Rubidium Frequency Standard (Including GPS Antenna and Cable)
The function and configuration of the Prime Site GPS / Rubidium Frequency Standard and
Digital Multiplex equipment are summarized in the following sections. The configuration and
functionality of the remaining Prime Site equipment is described in later sections.
Use or disclosure of this proposal is subject 10 the restrictiolls 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
3
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
3m 1.3 GPS I Rubidium Frequency Standard
A GPS / Rubidium frequency standard will be supplied at the Prime Site. This device will be
used to provide a 1 pulse-per-second (PPS) signal to the multiplex Digital Simulcast Modem
(DSM II) cards that are housed in the channel banks. The GPS 1 PPS signal will provide a very
precise time reference, which will be used to synchronize the simulcast signal launch times from
the system transmit sites. Table 3-2 provides a summary of the GPS / Rubidium frequency
standard specifications.
Table 3-2 - GPS/Rubidium Frequency Standard Specifications and Configuration
Technical Specifications
Size
Operating Temperature
Main Power Input
Stability of 5 MHz reference (GPS disciplined)
Stability of 5 MHz reference (No GPS)
Number of 5 MHz output ports
Number of 1 PPS output ports
GPS Antenna Connector
5 MHz and 1 PPS Outputs Connector
3m 1 m4 Digital Multiplex Equipment
10.5" H x 19" W x 17.4" D
00 C to +500 C
120 V AC, 60 Hz nominal
10E-12
10E-1O
12 (expandable to 28)
8 (expandable to 28)
N-type Female
BNC-type Female
The Prime Site will be equipped with three (3) Premisys IMACS/800 T 1 channel banks as
described below.
Channel Bank 1: Master Channel Bank
Channel Bank 2: Sub-Channel Bank #1
Channel Bank 3: Sub-Channel Bank #2
The Master Channel Bank is used to connect to the Whitby remote site, and the co- located
remote site. The Sub Channel bank #1 is used to connect to the Bowmanville remote site and the
Orono remote site. The Sub Channel bank #2 is used to connect to the Pickering remote site.
Use or disclosure of this proposal is subject to the restrictions on the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
4
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Each channel bank at the Prime Site will be configured with the required modules for routing
audio and data between the various Prime Site components and the system Remote Sites.
Technical details of the multiplex equipment are described in Section 4. The following tables
summarize the configuration of the channel banks at the Prime Site.
Table 3-3 - Master Channel Bank Configuration
Transceiver Site Links Qty: 2
Number of TIs Equipped 3
Number of 1 PPS Inputs 2
Card Type Qty Functions
CPU 1 System control and processing
Redundant CPU 1 System control and processing
Interface Card 1 External connections and dial-up modem
Dual TI Card 2 Provides 2 T 1 interface
Redundant Dual T 1 Card 1 Provides redundant 2 T 1 interface
Power Supply 1 Provides power to the unit
Redundant Power Supply 1 Provides back up power to the unit
CSU Plug in Module 6 Required for connection to Tl
DSM II Card 6 4 Wire. 600 Ohm voice card for analog simulcast
channels (4 ports per card)
Sub-Rate (SRU) Data Card 1 RS232 interface for digital equipped channels and
Remote Site Controller data (10 ports per card)
Use or disclosure of this proposal is subject to the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
5
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Table 3-4 - Sub-Channel Banks #1 Configuration
Transceiver Site Links Qtv: 2
Number of Tis Equipped 3
Number of 1 PPS Inputs 2
Card Type Qty Functions
CPU 1 System control and processing
Redundant CPU 1 System control and processing
Interface Card 1 External connections and dial-up modem
Dual T 1 Card 2 Provides 2 T 1 interface
Redundant Dual T 1 Card 1 Provides redundant 2 T 1 interface
Power Supply 1 Provides power to the unit
Redundant Power Supply 1 Provides back up power to the unit
CSU Plug in Module 6 Required for connection to T 1
DSM II Card 6 4 Wire, 600 Ohm voice card for analog simulcast
channels (4 ports per card)
Sub-Rate (SRU) Data Card 1 RS232 interface for digital equipped channels and
Remote Site Controller data (10 ports oer card)
Use or disclosure oftilis proposal is subject to tile restrictiolls 01/ tile title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
6
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Table 3-5- Sub-Channel Banks #2 Configuration
Transceiver Site Links Qty: 1
Number of TIs Equipped 2
Number of 1 PPS Inputs 2
Card Type Qtv Functions
CPU 1 System control and processing
Redundant CPU 1 System control and processing
Interface Card 1 External connections and dial-up modem
Dual TI Card 1 Provides 2 T 1 interface
Redundant Dual T 1 Card 1 Provides redundant 2 T 1 interface
Power Supply 1 Provides power to the unit
Redundant Power Supply 1 Provides back up power to the unit
CSU Plug in Module 4 Required for connection to Tl
DSM II Card 3 4 Wire, 600 Ohm voice card for analog simulcast
channels (4 ports per card)
Sub-Rate (SRU) Data Card 1 RS232 interface for digital equipped channels and
Remote Site Controller data (10 ports per card)
3. 1.5 Site Backup Power
A UPS has been included with the Prime Site equipment to provide one hour of back up power to
the equipment. The AC power consumption and other physical requirements of the equipment at
the Prime Site are provided in the Site Requirements Plan.
3.2 Transmit I Receive Sites
3.2. 1 Site Description
The system will include four (4) remote transmit/receive sites and one (1) co-located
transmit/receive site. Refer to the Site Requirements Plan for information regarding the space,
power, HV AC, cable tray locations, and general installation requirements of the site equipment.
Use or disclosure of this proposal is subject 10 the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
7
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
The system remote transmit/receive sites are listed below. Refer to Section 13 of this document
for location coordinates and antenna height information.
. Oshawa (co-located)
. Pickering (remote)
. Whitby (remote)
. Bowmanville (remote)
. Orono (remote)
3.2.2 Site Equipment
The equipment listed in Tables 3-6 to 3-10 will be located at the remote transmit/receive sites.
All of the trunked radio system equipment, including the repeaters and channel banks, will be
powered from single phase, 3-wire, 115 V AC, 60 Hz primary power. All of the equipment will
be mounted in open racks, except the equipment at the co-located remote site. Refer to the Site
Rack Layout Diagrams in Appendix A of the Site Requirements Plan. Equipment intercabling
will be facilitated through the use of Motorola's Modular Panel Interconnect System. This
system will use standard AT&T interconnect panels mounted in the same racks as the equipment.
Audio, data, and control interconnections between various pieces of equipment will be routed to
and from the interface panels via modular 8-pin RJ45 cables. A cable tray system, supplied by
The Fire Departments of Durham Region, will be used for inter-rack cabling purposes.
Table 3-6 - Oshawa City Hall Co-located Remote Site Equipment
Eauipment
Remote Site Simulcast MTC3600 Controller (ReSC)
800 MHz, 100 W Quantar Trunking Repeaters
Quantar Repeater Batteries
la-Channel Transmitter Combiner
12-Channel Receiver Multicoupler
Duplexer (existing)
800 MHz Antenna (existing)
Transmission Line Cable (1 %" foam dielectric)
Qtv
1
9
9
1
1
I
I
180 ft. (assumed)
Use or disclosure of this proposal is subject 10 the restrictiolls 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
8
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Table 3-7 - Pickering Site Equipment
Equipment Qty
Remote Site Simulcast MTC3600 Controller (ReSC) 1
800 MHz, 100 W Quantar Trunking Repeaters 9
Quantar Repeater Batteries 9
GPS / Rubidium Frequency Standard (Including GPS Antenna and Cable) 1
Channel Bank 1
10-Channel Transmitter Combiner 1
12-Channel Receiver Multicoupler 1
800 MHz Dual Antenna 1
Transmission Line Cable (1-1/4 in. foam dielectric - Transmit and Receive) 400ft ea
(assumed).
Table 3-8 - Whitby Site Equipment
Equipment Qtv
Remote Site Simulcast MTC3600 Controller (ReSC) 1
800 MHz, 100 W Quantar Trunking Repeaters 9
Quantar Repeater Batteries 9
GPS / Rubidium Frequency Standard (Including GPS Antenna and Cable) 1
Channel Bank 1
lO-Channel Transmitter Combiner 1
12-Channel Receiver Multicoupler 1
800 MHz Dual Antenna 1
Transmission Line Cable (1-1/4 in. foam dielectric - Transmit and Receive) 160ft ea
(assumed).
Use Of di.\'clo.mre of this proposal is subject to the restrictions on the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
9
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Table 3.9 - Bowmanville Site Equipment
Equipment
Remote Site Simulcast MTC3600 Controller (ReSC)
800 MHz, 100 W Quantar Trunking Repeaters
Quantar Repeater Batteries
GPS / Rubidium Frequency Standard (Including GPS Antenna and Cable)
Channel Bank
10-Channel Transmitter Combiner
Qtv
1
9
9
1
1
1
1
1
170ft ea
(assumed).
12-Channel Receiver Multicoupler
800 MHz Dual Antenna
Transmission Line Cable (1-1/4 in. foam dielectric - Transmit and Receive)
Table 3-10 - Orollo Site Equipmellt
Equipment
Remote Site Simulcast MTC3600 Controller (ReSC)
800 MHz, 100 W Quantar Trunking Repeaters
Quantar Repeater Batteries
GPS / Rubidium Frequency Standard (Including GPS Antenna and Cable)
Premysis Channel Bank
10-Channel Transmitter Combiner
12-Channel Receiver Multicoupler
800 MHz Dual Antenna
Qtv
1
9
9
1
1
1
1
1
Transmission Line Cable (1-1/4 in. foam dielectric - Transmit and Receive)
180ft ea
(assumed).
3.2.3
Remote Site Simulcast Controller
Each transmit/receive site will include a Remote Site Simulcast Controller (ReSC). The primary
function of the ReSC will be the management of the control and voice channel trunked repeaters
at the site. The ReSC decodes inbound signaling from radio units and sends call requests and
diagnostics to the Prime Site Simulcast Controller. It will also receive call assignment and status
messages from the Prime Site Controller. The technical specifications of the ReSC are listed in
Table 3-11
Use or disclosure of this proposal is subject to the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROl.A February 2002
10
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Table 3-11 - Remote Sue Controller Specifications
Technical Specifications
Link to Prime Site Controller
2400 bps, RS-232C Asynch
9
28
Channel Capacity (Equipped)
Channel Capacity (Capable)
Power Requirements
Power Consumption
Physical Dimensions
Ambient Operating Temperature Range
Relative Humidity
120 V AC, 60 Hz nominal
2.5 A @ 120 VAC
14" H x 19" W x 14" D
00 C to +500 C
5-85% non-condensin.e:
3.2.4
Quantar Trunking Repeater
Nine (9) 800 MHz, 100 W Quantar trunking repeaters will be located at each transceiver site. The
repeaters will be equipped for analog voice communications.
The Quantar repeaters will be mounted in a 7.5' rack, except the Quantars at the co-located
remote site. One (1) plug-in test microphone will be supplied for use at each transceiver site.
Each Quantar repeater will include the following features:
Controls
On / Off Switch
Speaker Volume
Microphone Jack
Indicators
Programming and Diagnostic Port
Power On
Transmit
Failsoft Operation (continuous transmit)
Use or disclosure of this p/'opo.ml is subject to the restrictiollS 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
11
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Other Features Internal Speaker
Transmit Fail Alarm
Audio Interface: 4 wire analog
The specifications for the 800 MHz Quantar Trunking Repeater are listed in Table 3-12.
Table 3-12 - 800 MHz Quantar Trll1lking Repeater Specifications
Physical Characteristics
Size 8.75" H x 19" W x IT'D
Transmitter Connector N-type Female
Receiver Connector N-type Female
External Frequency Reference BNC-type Female
Protective Circuitry Single-stage circulator on Tx output
All assemblies include RF shielding
Ambient Operating Temperature Range -300 C to +600 C
Main Power Input 90-264 V AC, 47-63 Hz
DC Power Ooeration 24VDC
Electrical Specifications
Transmitter
Frequency Range 851-870 MHz
RF Power Output 100 W maximum (adjustable down to 20 W)
Continuous Duty
RF Output Impedance 50 Ohm
Radiated & Conducted Spurious Emissions 80 dB below carrier
Modulation Deviation :t 5 kHz maximum for 25 kHz channel
Frequency Stability :t 0.0001 %
Line Audio Sensitivity -35 dBm to 0 dBm variable
FM Hum and Noise 50 dB nominal for 25 kHz channel;
ref. 1000 Hz tone @ 3 kHz deviation
Transmitter Audio Response +1, -3 dB from 6 dB per octave
pre-emphasis; 300-3000 Hz referenced
to 1000 Hz at line input
Use or disclosure of tlr is proposal is subject to the restrictions on tire title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
12
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Physical Characteristi.cs
Transmitter Audio Distortion Less than 3% @ :t 3 kHz deviation,
ref. 1000 Hz tone
Transmitter Sideband Noise Attenuated 90 dB for 25 kHz channel
Receiver
Frequency Range 806-825 MHz
RF Input Impedance 50 Ohm
Channel Spacing 25 kHz
Sensitivity (EIA 12 dB SINAD) 0.30 IlV
Sensitivity (20 dB Quieting) 0.42 IlV
Selectivity 80 dB for 25 kHz channel
Frequency Stability 0.0001%
Intermodulation Rejection 85 dB
Spurious and Image Rejection 100 dB
Audio Response +1, -3 dB from 6 dB per octave
de-emphasis; 300-3000 Hz referenced
to 1000 Hz at line input
FM Hum and Noise 50 dB nominal ref. to 1000 Hz tone @
3 kHz deviation (25 kHz channel)
Audio Output 5 W, maximum distortion 5% ref. 1000 Hz
Multiplex Output -20 dBm to 0 dBm @ 1 kHz,
Distortion less than 3% @ 1 kHz
Regulatory
Industry Tvpe Approval Number 109194195C
3.2.6 GPS / Rubidium Frequency Standard
A GPS / Rubidium frequency standard will be supplied, at each transmit/receive site. This device
will supply a 5 MHz reference signal to each transmitter and a 1 pulse-per-second (PPS) signal to
the DSM II cards. The 5 MHz output derived from the Rubidium oscillator will provide a very
precise and stable external frequency reference for the transmitters. The 1 PPS signal will be
used to synchronize the simulcast signal launch times from the transmit sites.
The specifications of the GPS / Rubidium frequency standard are included in Table 3-13.
Use or disclosure of this proposal is subject to the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
13
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Table 3-13 - GPS/Rubidiwn Frequency Standard Specifications and Configuration
Technical Specifications
Size 10.5" H x 19" W x 17.4" D
Operating Temperature 00 C to +500 C
Main Power Input 120 V AC, 60 Hz nominal
Stability of 5 MHz reference (GPS disciplined) lOE-12
Stability of 5 MHz reference (No GPS) lOE-10
Number of 5 MHz output ports 12 (expandable to 28)
Number of 1 PPS output ports 8 (expandable to 28)
GPS Antenna Connector N-type Female
5 MHz and 1 PPS Outputs Connector BNC-type Female
3.2.7 Digital Multiplex Equipment
Each transmit / receive site, except the co-located remote site, will be equipped with a Premisys
IMACS/800 T1 channel bank. The IMACS/800 channel bank will be configured with all the
necessary cards to permit the interfacing of the site control and RF equipment to a standard T 1
link. Technical details ofthe multiplex equipment are provided in Section 6. Refer to Table 3-14
for the configuration of the channel banks at the transceiver sites.
Table 3-14 - Transmit / Receive Site Channel Bank Configuration
Transmit I Receive Sites Qty: 4
Number ofTls Equipped 1
Number of 1 PPS Inputs 2
Card Type Qtv Functions
CPU I System control and processing
Interface Card I External connections and dial-up modem
Single Tl Card I Provides T 1 interface
CSU Plug in Module I One required for every single T1 card
Power Supply I Supplies Power for the unit
DSM II Card 3 4 Wire, 600 Ohm voice card for analog simulcast
channels (4 ports per card)
Sub-Rate (SRU) Data Card 1 RS232 interface for digital equipped channels and
Remote Site Controller data (8 ports per card)
Use or disclosure of this proposal is subject to the restrictions all the title page.
Motorola Confidential Proprietary
@ MOTOROI.A February 2002
14
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
3.2.8
Site Antenna, Transmitter Combining, and Receiver
Multicoupling Systems
The 800 MHz antenna system equipment at each transceiver site will consist of the following
major components: antenna, transmission line cable and connectors, equipment jumper cables, in-
line surge suppressors, transmitter combiner, and receiver multicoupler. Appendix A of the Site
Requirements Plan includes Interconnect Diagrams of the antenna system components for each
site.
Table 3-15 - Oshawa City Hall Site Antenna System Specifications & Configuration
Site Antenna 800 MHz
Type Omnidirectional Collinear
Quantity 1 (existing)
Physical Dimension (length) 15 ft.
Weight 27 lbs.
Connector N-type Female
Gain 10 dBd
Height Above Ground 160 ft.
Transmission Lines
Type 1 1,4" foam dielectric heliax cable
Quantity 1 (new)
Length 180 ft.
Weight 0.66 Ibs./ft.
Surge Suppression Polyphasor in-line coaxial protector
Transmission Line Jumpers W' foam dielectric heliax cable
Equipment Jumpers ;/2" superflex cable
Transmitter Combiner
Type 10-channel waveguide / ferrite
Maximum Input Power 150W
Frequency Range 851-869 MHz
Channel Spacing 250 kHz
Connector Tx Input N-type Female
Connector Antenna 7116" DIN-type Female
Receiver Multicoupler
Type 12-channel
Frequency Range 806-824 MHz
Connector Rx Output BNC-type Female
Connector Antenna N-type Female
Duplexer Existing
Use or disc/oSllre o.f/his proposal is subjec//o /he res/ric/iolls Oil/he /i/le page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
15
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Table 3-16 - Pickering Site Antenna System Specifications & Configuration
Site Antenna 800 MHz
Type Dual Omnidirectional Collinear
Quantity 1
Physical Dimension (length) 23 ft.
Weight 481bs.
Connector N-type Female
Gain 9 dBd
Height Above Ground 380 ft. (assumed)
Transmission Lines
Type 1 14" foam dielectric heliax cable
Quantity 2 (1 for Transmit, 1 for Receive)
Length 400 ft.
Weight 0.66 lbs./ft.
Surge Suppression Polyphasor in-line coaxial protector
Transmission Line Jumpers Y2" foam dielectric heliax cable
Equipment Jumpers Y2" superflex cable
Transmitter Combiner
Type lO-channel waveguide / ferrite
Maximum Input Power 150W
Frequency Range 851-869 MHz
Channel Spacing 250 kHz
Connector Tx Input N-type Female
Connector Antenna 7/16" DIN-type Female
Receiver Multicoupler
Type 12-channel
Frequency Range 806-824 MHz
Connector Rx Output BNC-type Female
Connector Antenna N-type Female
Table 3-17 - Whitby Site Antenna System Specifications & Configuration
Site Antenna 800 MHz
Type
Quantity
Physical Dimension (length)
Weight
Connector
Gain
Height Above Ground
Dual Omnidirectional Collinear
1
23 ft.
481bs.
N-type Female
9dBd
140 ft.
Use or disclosure of this proposal is subject to the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
16
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Site Antenna 800 MHz
Transmission Lines
Type I 1,4" foam dielectric heliax cable
Quantity 2 (1 for Transmit, 1 for Receive)
Length 160 ft.
Weight 0.66 lbs./ft.
Surge Suppression Polyphasor in-line coaxial protector
Transmission Line Jumpers '12" foam dielectric heliax cable
Equipment Jumpers W' supertlex cable
Transmitter Combiner
Type lO-channel waveguide / ferrite
Maximum Input Power 150W
Frequency Range 851-869 MHz
Channel Spacing 250 kHz
Connector Tx Input N-type Female
Connector Antenna 7/16" DIN-type Female
Receiver Multicoupler
Type 12-channel
Frequency Range 806-824 MHz
Connector Rx Output BNC-type Female
Connector Antenna N-type Female
Table 3-18 - Bomanville Site Antenna System SpecijicatiollS & Configuration
Site Antenna 800 MHz
Type
Quantity
Physical Dimension (length)
Weight
Connector
Gain
Height Above Ground
Transmission Lines
Dual Omnidirectional Collinear
1
23 f1.
481bs.
N-type Female
9 dBd
150 f1.
Type
Quantity
Length
Weight
Surge Suppression
Transmission Line Jumpers
Equipment Jumpers
1 1,4" foam dielectric heliax cable
2 (1 for Transmit, 1 for Receive)
170 ft.
0.66 Ibs./f1.
Polyphasor in-line coaxial protector
W' foam dielectric heliax cable
W' supertlex cable
Use or disclosure of th is proposal is subject 10 the restrictiolls 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
17
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Transmitter Combiner
Type 10-channel waveguide / ferrite
Maximum Input Power 150W
Frequency Range 851-869 MHz
Channel Spacing 250 kHz
Connector Tx Input N-type Female
Connector Antenna 7/16" DIN-type Female
Receiver Multicoupler
Type 12-channel
Frequency Range 806-824 MHz
Connector Rx Output BNC-type Female
Connector Antenna N-type Female
Table 3.19 - Orono Site 800 MHz Antenna System Specifications & Configuration
Site Antennas 800 MHz
Type Dual Omnidirectional Collinear
Quantity 1
Physical Dimension (length) 23 ft.
Weight 481bs.
Connector N-type Female
Gain 9 dBd
Height Above Ground 160 ft. (assumed)
Transmission Lines
Type 1 W' foam dielectric heliax cable
Quantity 2 (1 for Transmit, 1 for Receive)
Length 180 ft.
Weight 0.66 lbs./ft.
Surge Suppression Polyphasor in-line coaxial protector
Transmission Line Jumpers h" foam dielectric heliax cable
Equipment Jumpers W' superflex cable
Transmitter Combiner
Type lO-channel waveguide / ferrite
Maximum Input Power 150W
Frequency Range 851-869 MHz
Channel Spacing 250 kHz
Connector Tx Input N-type Female
Connector Antenna 7/16" DIN-type Female
Receiver Multicoupler
Use or disclosure of this proposal i,l' slIbjec'tlO the restrictiolls 011 the title page,
Motorola Confidential Proprietary
@ MOTOROLA February 2002
18
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Site Antennas 800 MHz
Type
Frequency Range
Connector Rx Output
Connector Antenna
12-channel
806-824 MHz
BNC-type Female
N-type Female
3.3 Battery Backup Power
All of the radio system equipment at the transceiver sites will normally operate from 120 V AC
primary power. In the event of a main AC power failure, battery backup power will be supplied
for the Quantars. A 24 VDC sealed lead-acid battery will be provided for each trunking repeater.
A UPS, supplied by The Fire Departments of Durham Region, will back up the remaining site
equipment. Each Quantar trunking repeater station will be equipped with an internal DC charger
to maintain the battery voltage. If the repeater station senses the loss of AC power, it will
automatically revert to DC operation from the battery supply. The battery backup time will be
based on the following duty cycles:
Trunking control channels: 100% duty cycle (continuous transmit)
Trunking voice-only channels: 50% transmit / receive, 50% standby duty cycle
The backup time requirements and repeater battery sizes are summarized in Table 3-20.
Table 3-20- Transceiver Site Battery Backup Time & Battery Sizing
Site Backup Time Battery Sizing Battery Sizing
(Control Channel) (Voice Channel)
Oshawa 8 hours 127 AH 79AH
Pickering 8 hours 127 AH 79AH
Whitby 8 hours 127 AH 79AH
Mitchell's Corners 8 hours 127 AH 79AH
Orono 8 hours 127 AH 79AH
Use or disclosure of this proposal is subject to the restrictions all the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
19
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
4.0
CONVENTIONAL STATIONS
The existing conventional radio stations will be integrated into the Fire CENTRACOM console
system, but will operate independently from the trunked radio simulcast system. In all cases,
standard Tone Remote Control operation is assumed.
5.0
FIRE DEPARTMENTS PAGING
New conventional VHF base stations (MTR2000) will be provided to replace existing paging
base stations, however, battery back up has not been included. The current complement of VHF
pagers will continue to function as normal after the Upgrade and will be independent of the
trunking system. Motorola assumes the use of standard tone-only or tone and voice paging code
plans, which are the same type used by the Centracom Gold Elite Console.
6.0
SITE LINKING SUBSYSTEM
6.1
System Overview
The Trunked Radio System will utilize Tl facilities, for inter-site linking. The Tl network will
be supplied by The Fire Departments of Durham Region, and will consist of leased or dedicated
T 1 fibre or copper circuits.
6.2 Digital Multiplex Equipment
Premisys IMACS/800 Tl channel banks will be used for the Trunked Radio System digital
multiplex equipment. The IMACS/800 is a modular, two-sided card cage enclosure. It is a
software configurable platform, and will include a terminal configuration port to permit remote
programming and set up from a VT -100 type terminal or equivalent (not supplied by Motorola),
at the Prime site. The IMACS/800 will also provide a diagnostic and alarm port. Remote site
access and channel bank network management will be accomplished through the Tl network via
a dedicated SRU (Sub Rate Unit) data port. Refer to Table 6-1 for the physical specifications of
the channel bank.
Use or disclosure o/this proposal is subject to the restrictiolls 011 the title page.
Motorola Confidential Proprietary
@ MOTOROI.A February 2002
20
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Table 6-1 IMACS Channel Bank Specifications
Physical Specifications IMA CS/800
Size 9" H x 17" W x 15.5" D
Main Power Input 90-135 V AC, 50-60 Hz
Power Consumption 125 W (typical)
Operating Temperature 00 C to +500 C
Storage Temperature -200 C to +800 C
Humidity 0% to 95% relative humidity, non-condensing
The channel unit specifications are listed in Table 6-2.
Table 7-2 - Channel Unit Technical Specifications
Channel Unit Specifications
Frequency Response
Terminal Impedance
Alignment
Crosstalk
Envelope Delay
Distortion
Return Loss
Test tone levels
VF level stability
IMA CS/800
+0.15 to -1.5 dB from 300 to 3400 Hz
600 Ohm
+7/-16 dBm
200 Hz <-55 dBmO
1000 Hz <-65 dBmO
2000 Hz <-65 dBmO
3000 Hz <-64 dBmO
600-3200 Hz 1200 IlS
800-2800 Hz 550 Ils
1000-2600 Hz 350 J..tS
Harmonic distortion output products less than -40 dBmO
ref. 1000 Hz @ 0 dBmO
4w transmit: 1 kHz
>28 dB
300 Hz to 3 kHz >23 dB
4w receive:
1 kHz
>28 dB
300 Hz to 3 kHz >23 dB
Transmit: -16 dBm input
Receive: + 7 dBm output
:to.5 dB of reference loss (20 years, 95% of circuits)
Use or disclosure of this proposal is subject 10 the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
21
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Ch.annel Unit Specifications
IMA CS/800
Phase Jitter
<30 peak-to-neak
6.3 Interface Requirements for T1
The IMACS/800 channel bank will interface to the inter-site transport network via a standard Tl
link. The requirements of the Tl network are summarized in Table 6-3. These requirements
must be strictly adhered to, to ensure proper operation of the IMACS/800 channel bank and the
DSM II.
Table 6-3 Tl Circuit Requirements
TI Circuit Reauirements
Line Rate 1.544 Mbps, :t50 bps
Line Code (Zero Bit Suppression) B8ZS
Format ESF
Impedance 100 Ohm
Bit Error Rate <lOE-5
No compression DSM II requires that no compression be performed on T 1
slot.
'Clear' Channel DSMII requires T1 time slot to be a 'clear' channel, i.e.,
none of the 8 bits can be modified in any manner.
Circuit Switching/Alternate Routing No constraints except for maximum path (circuit) delay
requirement of 5 ms.
T! Network Clocking Accurate to within :t50 ppm
Total transport path time delay <5 ms
(Master site to any remote transmitter site)
7.0
TRUNKING CONTROL
The Prime Site will contain the main control and audio processing equipment. The key trunking
system control device will be the Prime Simulcast MTC3600 Controller. This device will
interface to all other subsystems such as, dispatch consoles, system management terminal, and the
transceivers.
Use or disclosure of this proposal is subject to the restrictions on the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
22
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
7.1 Prime Simulcast MTC3600 Controller
The specific function of the Prime Simulcast MTC3600 Controller will be the management and
control of the overall Simulcast system. The Prime Simulcast Controller will manage the
operation of the system remote sites via data communication links to the Remote Site Controllers.
The simulcast analog channels will be controlled by the Prime Simulcast Controller through the
USCI (Universal Simulcast Controller Interface), which distributes control channel and low speed
trunking data, generated by the Prime Simulcast Controller, to the remote sites. The technical
specifications of the Prime Simulcast Controller are listed in Table 7-1.
Table 7-1 Prime Simulcast MTC3600 Controller Specifications
Technical Specifications
Link to Remote Site Controller 2400 bps, RS-232C Asynch
Number of Remote Site Controller Links (Equipped) 5
Number of Remote Site Controller Links (Capable) 10
Power Requirements 120 V AC, 60 Hz nominal
Power Consumption 2.5 A @ 120 VAC
Physical Dimensions 14" H x 19" W x 14" D
Ambient Operating Temperature Range 00 C to +500 C
Relative Humiditv 5-85% non-condensing
8.0
ANALOG AUDIO VOTING AND
DISTRIBUTION
8.1
Analog Audio Voting
The simulcast trunked radio system will include receiver voting capability. The DigiTac
comparator will be used to vote analog audio from the system remote sites. The voted audio will
be routed to the dispatch consoles and to the simulcast distribution network for additional
processing and distribution to the remote transmit sites. The DigiTac will select or "vote" the
best received signal on the basis of audio quality.
Use or disclosure of this proposal is subject to the restrictions all the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
23
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
8.1.1 DigiTac Comparator
A DigiTac comparator will be required for every system channel (9).
The DigiTac comparators will be configured as listed in Table 8-1.
Table 8-1 DigiTac Comparator Configuration
Description
Voting Capacity (Equipped) 5 Sites (voting inputs)
Voting Capacity (Capable) 8 Sites (voting inputs/single chassis)
Other Ports 1 Console Audio port
1 Voted Audio output port
Test Handset 1 handset
Mounting Configuration Lockable Cabinet
Power Supply 1 for every 2 or 3 Comparators
The specifications for the DigiTac Comparator are listed in Table 8-2.
Table 8-2 DigiTac Comparator Technical Specifications
Technical Specifications
Power Requirements 120 V AC :t 20%,60 Hz nominal
AC Current Draw (Power Supply) 4.2 A @ 120 VAC
Power Backup Building UPS at Prime Site
Mounting Configuration 19" EIA Rack Mounting
Selection Process (analog signals) Signal-to-Noise, 2.0 dB steps
Input / Output 600 Ohms, balanced
Line Input Sensitivity -26 to 0 dBm or -15 to +11 dBm @ 1 kHz
Line Output -25 to+ll dBm @ 1 kHz
Frequency Response Flat +1.0 dB from 200 to 3400 Hz
Output Distortion Less than 3% @ 1 Hz @ 0 dBm
Hum and Noise 60 dB below output level of 0 dBm
Timing by System Response Access time less than 50 ms, up to 10 votes per second
Carrier Delay 5.0 seconds nominal adjustable, from 100 ms to 10
seconds
Use or disclosure of Ihis proposal is subjecllo Ihe reslricliOlls olllhe lille page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
24
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
8.2 Analog Audio Processing and Distribution
The system trunked channels, which will support analog voice operation and/or control channel
capability, will utilize special audio processing and distribution hardware, as described below.
8.2. 1
Universal Simulcast Controller Interface (USCI)
Each channel will be equipped with a Universal Simulcast Controller Interface (USCI). The
USCI will perform processing of voted (or console) audio from the DigiTac comparator, and will
combine the audio with low speed trunking data from the Prime Site Simulcast Controller. The
USCI will also distribute the system wide PTT, from the Prime Site Simulcast Controller, to each
transceiver site. A single USCI card cage will house eight (8) USCI modules. The system will be
equipped with two USCI card cages and nine (9) USCI modules to support nine (9) channels.
8.2.2 Digital Simulcast Modem /I (DSM II)
The DSM II will be used to provide the audio delay, amplitude and frequency response
performance required by the simulcast system. It will include a Digital Signal Processor (DSP),
which will permit real-time, automatic software control of audio signal amplitude and time delay.
Through such adjustments, a simulcast signal originating at the Prime Site can be "launched"
from each transceiver site in the system at the same time and with identical characteristics
(amplitude level and frequency response).
The DSM II will fit into the IMACS/800 Tl channel bank, and can only be used on this platform.
It is a multiport card, with four (4) full duplex ports per card. One DSM II card will be required
for every four (4) analog simulcast channels. To support a nine (9)-channel infrastructure, each
channel bank will include three (3) DSM II cards. The DSM II will utilize a GPS (Global
Positioning System) disciplined 1 PPS input as a time reference. This signal will be provided to
both the Prime Site and Remote Site DSM II cards. Using this GPS based time reference, the
Remote Site DSMs will measure the transport time delay of the channel and insert the required
"buffer" so that the simulcast signal, originating from the Prime Site, is launched at the same time
from each remote site.
The specifications for the DSM II are listed in Table 8-3.
Use or disclosure of th is proposal is subject to the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
25
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Table 8.3 DSM II Technical Specifications
Technical Specifications
Audio Levels
Audio Line Interface
Audio Level Step Size
Maximum Time Delay of Transport System
Time Delay Step Size
Time Delay Accuracy
Signalling
1 PPS Physical Interface
I PPS Electrical Interface
9.0
System Functional Specification
Section 2
Version 1.0
Tx Input / Rx Output minimum range: -10 dBm :t 4 dB
4-wire, 600 Ohm
0.1 dB
5 ms
I Ils
:t 3 Ils
2 sets of E and M Signalling Circuits
BNC-type Female
50 Ohms, TTL level
TRUNKING SYSTEM OPERATIONAL
FEATURES
9.1
Physical Parameters
The key physical parameters of the Trunked Radio System (that is, characteristics which are
entirely a function of the physical capacities and architecture of the trunking control
infrastructure) are summarized in Table 9-1.
Table 9-1 Trunking System Physical Parameters
Parameter Capacity I Settin~
Dedicated Control Channel Speed 3600 bps
Low Speed Data Sub-audible 150 bps
Number of Trunked Radio Channels (Equipped) 9
Maximum Number of Control Channels 4
Maximum number of Individual Addresses (unit IDs) 48,000
Maximum number of Talkgroups 4,000 (2000 with Priority Monitor)
Priority of Access Levels 8
Use or disclosure of this proposal is subject to the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
26
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Control Channel:
The control channel signaling information will be assembled into a sophisticated coding format
(using 23 ms. data packets), with sufficient error detection and correction capabilities to ensure a
high level of system reliability. The control channel data will be modulated for a 3600 bps over-
the-air transmission. Inbound channel requests from field radio units and subsequent outbound
channel assignments from the trunking system will be transmitted over the control channel.
Channel Connect:
Once a voice channel has been assigned, the repeater involved in the call will transmit low speed
data continuously so that other radios that come into service during the call will be able to join the
conversation in progress. Inbound, the field radio unit will transmit a sub-audible connect tone
while it is keyed. This ensures that only authorized radios are able to access the trunking system.
Controller Links:
The links between the Prime Simulcast Controller and the Remote Site Controllers will be
RS232, 2400 bps asynchronous data links. RS232 sub-rate data cards (SRU) in the IMACS/800
channel banks at the remote sites will be used for the transport of Remote Site Controller data.
9.2 Trunking Features - Infrastructure
The Trunked Radio System will be APCO-16 compliant. The infrastructure will support the
following operational features.
Channel Assignment The trunking system may assign users to any of the 8 system
channels (1 channel is the control channel), thereby distributing
the radio load among all the available channels.
Misdirected Radio Protection The system will prevent radios from staying on channels to
which they have not been assigned and will prevent radios from
listening to talkgrouDs to which they are not programmed.
Transmission Trunking Operation Talkgroups can be programmed for transmission trunking
operation. In this mode, each user PTT will initiate a channel
request, and the channel assignment is terminated immediately
when PTT is released. If any talkgroup member initiates a PTT
while another talkgroup member is talking, that user will receive
Use or disclosure of this proposal is subject to the restrictions Oil the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
27
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
6.5 Training Course Material
Motorola will provide one copy of the course material for evaluation prior to the scheduled
beginning of a training course. This material will meet the requirements of the Training Plan
contained in Section B.7 of this Statement of Work. One copy of the lesson plan per student
will be included for each course chosen by the Durham Fire Departments.
6.6 Equipment Inventory list
Upon delivery of the console equipment, a Motorola representative will go to the Durham
Fire Departments receiving facilities and perform an inventory. The Durham Fire
Departments representative will also participate in performing this inventory. A list will be
generated outlining what has been received and what equipment is still outstanding, if any.
When both Durham Fire Departments and Motorola representatives have signed this list to
approve correctness, a copy of it will be given to the Durham Fire Departments
representati ve.
6.7 Field Acceptance Test Procedures and Coverage
Acceptance Test Procedure
The Field Acceptance Test Procedures document describes the standard Motorola
procedures, which will be followed to perform the tests, listed in the Field Acceptance
Testing Plan. The Field Acceptance Test Procedures will be provided to the Durham Fire
Departments for approval no later than two weeks prior to the start of the Field Acceptance
Test.
As the coverage testing will require travel throughout the entire region to validate coverage
projections, Durham Fire Departments will be responsible for supplying an individual with
the appropriate authority to accompany Motorola onto properties for this testing. This will be
for a time period of 2 weeks.
Use or disclosure orthis COil tract is subject to the restrictiollS Oil the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
11
Durham Fire Departments
SMARTNET RADIO COMMUNICA nONS SYSTEM
Statement of Work
Section 6
Version 1.0
6.8 Provisional Acceptance Certificate
Motorola will prepare a Provisional Acceptance Certificate of completion. The Durham Fire
Departments representative will sign this certificate to confirm Provisional System
Acceptance. Refer to Section 8.3 for the procedure.
6.9 Punchlist Report
Any unresolved issues that remain at the end of the Provisional Acceptance Test will be
listed on a Punchlist Report. This report will consist of a list of the issues and will be
accompanied by a completed Punchlist Report Form for each issue with a detailed
explanation of the problem.
6.10 Infrastructure Equipment Service Manuals
These manuals will cover troubleshooting information, installation instructions, list of
replacement parts, description of operation, operating instructions, theory of operation, block
diagrams, schematics, component layout, complete parts lists, programming instructions,
performance specifications, and mechanical and physical details.
6.11 User Gear Operator Manuals
Each piece of user gear will come with an operator instruction manual. This manual will
describe the standard features and operations of the equipment.
6.12 System Manual
The System Manual will contain the As-Built information for the upgraded 800MHz
Durham Fire Departments system. This manual will include the following:
&I As installed rack layouts and floor plans
G Console Configuration/Fleetmap templates
Use or disclosure of this cOl1tract is subject to the restrlctiol1s 011 the litle page.
Motorola Confidential Proprietary
@ MOTOROL.A February 2002
12
Durham Fire Departments
SMARTNETRADlO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
. System Functional Specification
. System Block Diagram
6.13 Final Acceptance Certificate
Motorola will prepare a Final Acceptance Certificate and present it to the Durham Fire
Departments representative for signing as described in Section 8.4 of this document.
7.0 TRAINING PLAN
7.1 User Training
A short training course will be provided to enhance the user knowledge of the new system.
The user-training course will be delivered in 2-hour sessions to better meet the shift
requirements of the Durham Region Fire Department. This will include a training manual for
each participant.
8.0 SYSTEM ACCEPTANCE
8.1 Scope
This section details how the Acceptance Test will be performed by Motorola and witnessed
by Durham Fire Departments personnel to confirm that the installed equipment is complete
and meets all acceptance criteria. The Acceptance test will verify the functionality of the
equipment provided as described in the System Functional Specifications.
Motorola will provide procedures and check sheets for each test. If deficiencies are found
during the testing, both the deficiencies and their resolutions shall be agreed upon and
documented.
The Acceptance Tests will verify operational and functional performance of the installed
equipment and associated control equipment. Durham Fire Departments will make available
the required existing subscriber equipment (Portable and Mobile radios) to perform the
Use or disclosure aftltis cO/ltraCT is subject to the reslricti(l/ls Oil the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
13
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
acceptance testing. Representatives from the Durham Fire Departments and Motorola will
sign and date the Acceptance Test Procedure upon successful completion of the
corresponding test. By signing and approving an acceptance test, the equipment shall be
deemed to have passed that Acceptance Test.
Refer to the Acceptance Test Plan document for a complete description of the tests that will
be performed.
8.2 Punchlist
If any failures occur during Acceptance Testing, they will be documented using the
Punchlist Report form. A punchlist item will be assigned a severity level, by mutual
agreement of both parties, and the corrective action will be documented. If the punchlist
item cannot be corrected during the course of testing, it will remain open until a fix is
verified. When a fix is tested and verified, both Durham Fire Departments and Motorola
representatives must sign and date the Punchlist Report, in order to formally close the report.
Minor corrective action should not impact any previous test results. Punchlist Reports will
also be used to document failures and deficiencies found subsequent to Provisional
Acceptance and prior to Final Acceptance. Failures and deficiencies found subsequent to
Final Acceptance will be handled as warranty issues.
A punchlist report will only be generated for problems within Motorola's Scope of Work.
8.2. 1
Punchlist Report Severity Levels
Punchlist RepOlt severity levels are defined as follows:
Severity Description
1 System does not work.
An error which prevents completion of an essential function.
2 Adverse effect without a work around.
Problem not correctable with an alternate sequence.
3 A work around solution does exist.
However, if more than 20 Severity 3 items are found, this will become a
Severity 2 issue.
4 An annoyance which does not affect essential functions.
Use or disclosure of this contract is subject to the restrictiollS all the tille page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
14
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
Severity
Description
5 Any item not covered by the above categories, which is either non urgent, or
of an investigative nature.
8.3 Provisional Acceptance
Provisional Acceptance will be granted by the Durham Fire Departments within 5 working
days after the completion of the following milestones.
1. The Field Acceptance Test has been completed and there are no outstanding Severity 1 or
2 Punchlist Reports.
2. There are no more than 20 Severity 3 Punchlist Reports still open; and
3. One of the following occurs:
a) Durham Fire Departments has deemed that the equipment supplied is ready for
productive, operational use;
b) The equipment is used for activities other than training or testing; or
c) Fourteen (14) calendar days or more have elapsed since the completion of
milestones 1 and 2 above.
At this point Provisional Acceptance will be granted by the Durham Fire Departments and
the equipment will be made available for beneficial or day-to-day use. A punchlist of any
outstanding Severity 3, 4 or 5 Punchlist Reports will be reconciled and it will be the
responsibility of Motorola to correct these prior to Final Acceptance of the system.
8.4 Final System Acceptance
Final System Acceptance will be granted by the Durham Fire Departments within 5 working
days after the completion of all the following tasks:
1. Resolution of all Punchlist Reports contained in the punchlist at Provisional Acceptance.
'") Resolution of any Severity 1 and 2 Punchlist Reports identified subsequent to Provisional
Acceptance.
Use or disclosure o{lhis cOlltracl is subjeC110 lhe reslrictiollS Oil lhe title page.
Motorola Confidential Proprietary
([!;; MOTOROLA Februa1Y 2002
15
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
3. Completion of Training according to the schedule.
4. Completion of user equipment installation according to the Installation and Cut over plan
5. Delivery of all Documentation according to the schedule.
6. Documented procedures are in place for continued support after the project is complete.
At this point a Final Acceptance Certificate will be completed and signed by both Motorola
and the Durham Fire Departments.
Use or disclosure {4this cOlltral'l is subjeCl to the restrictiollS Oil the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
16
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
EXHIBIT A1 CHANGE ORDER FORM
CHANGE ORDER Change Order No:
Initiated by: Contract No:
Customer
Motorola Canada Limited
Description of Change Requested:
Proposed Change:
Total Price of This Change: $ Date Issued:
Delivery Schedule Change (If Any):
Agreed to for and on the Behalf of Agreed to for and on the Behalf of
Motorola Canada Limited Durham Fire Departments
Signature Date Silmature Date
Name and Title Name and Title
Use or disclcJSllre (~f"this colltracr is subject to the restrictions Oil the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
17
EXHIBIT C-4
SECTION 3
FACTORY
ACCEPTANCE TEST PLAN
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Factory Acceptance Test Plan
Section 3
Version 1.0
TABLE OF CONTENTS
1.0 PURPOSE AND SCOPE ............................................................................ 1
2.0 SYSTEM TEST CONFIGURATION AND EQUIPMENT REQUIREMENTS1
3.0 GENERAL CONDUCT OF TESTING ......................................................... 2
4.0 TRUNKING FEATURES AND SYSTEM TESTS........................................ 2
4.1 Talkgroup Call.. ....... ........ .................... ............ ................................ ....... ..... 2
4.2 Announcement G roup Call.......................................................................... 2
4.3 Busy Queuing and Call Back ...................................................................... 2
4.4 Continuous Assignment Updating.............. ................................................. 3
4.5 Recent User Priority.................................................................................... 3
4.6 Talk Prohibit / Out-of-Range .......................................................................3
4.7 Call Alert and Private Call........................................................................... 3
4.8 T alkgroup Scan........................................................................................... 4
4.9 System Channels Functional Verification ...................................................4
5.0 CENTRACOM ELITE DISPATCH CONSOLES ......................................... 4
5.1 T alkgroup Call Operation............................................................................ 5
5.2 PTT -I D Display..............:............................................................................ 5
5.2 Console Priority.......................................................................................... 5
5.3 Multi-Select / Patch Operation ....................................................................5
Multi-Select: ......................................................................................................... 5
Patch: .. ... .. .. .. .. .. . .. . .. ... . .. .. ... .. .. . ... .. . . . .. .. .. .. ... . . . .. . .. .. .. .. .. . .. .. . . .. .. . . . .. . .. . .. .. .. .. .. .. ... . . ... ... 5
6.0 F AI LU RE SCENARIOS.. .... ... .....1111.............111......11..........11. ..11.................... ....... 6
6.1 Voice Channel Repeater Failure................................................................. 6
6.2 Control Channel Repeater Failure ..............................................................6
6.3 Remote Site Controller Failure.................................................................... 7
6.4 Prime Site Controller Failure....................................................................... 7
6.5 T1 Network Link to Single Remote Site Failure .......................................... 7
Use or disclosure of til is proposal is slIbjeCl 10 the restrictio/1s 011 the title page.
Motoll"Ola Confidential Proprietary
@ MOTOROLA
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Factory Acceptance Test Plan
Section 3
Version 1.0
Use or disclosure ofthi.\ proposal is subject 10 the restrictiolls 011 the title page.
Ivlotorola Confidential Proprietary
@ MOTOROLA
11
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Factory Acceptance Test Plan
Section 3
Version 1.0
FACTORY ACCEPTANCE TEST PLAN
1.0 PURPOSE AND SCOPE
The purpose of the Factory Acceptance Test Plan is to verify the basic operation and
functionality of The Fire Departments of Durham Region 800 MHz SmartNet, Simulcast,
Analog, Trunking System, in Motorola's factory staging area, the Customer Centre for
System Integration (CCSI). The Factory A TP has been designed to validate the ability of the
system to deliver the designed and contract required system functionality to the end users.
System functions and features not included within this A TP plan will not be tested. All of
the system infrastructure equipment will be staged at CCSI in Schaumburg, Illinois, with the
following exceptions:
1) Site backup power systems
2) Existing Console Equipment and SmartNet System Management terminals
3) Site antennas and transmission lines
4) Existing Oshawa City Hall infrastructure
The Factory A TP Plan provides a list of the Test Procedures, including a brief description,
which Motorola will execute with Durham Region Representatives at CCSI. The actual Test
Procedure sheets will be provided to The Municipal Fire Departments of Durham Region
before the scheduled start of the Factory Test.
2.0 SYSTEM TEST CONFIGURATION AND
EQUIPMENT REQUIREMENTS
The complete fixed RF network, with the exceptions noted in Section 1.0 of this document,
will be staged at CCSI. This includes all of the equipment at the Prime Simulcast Control
site and Remote sites. Sample user equipment (mobile and portable radios) will be used to
verify the functionality of the trunked radio system. User equipment configurations and
programming will not be specifically tested in the factory. The final user equipment
Use or disclosure of this proposal is subject to the restrictiollS 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Factory Acceptance Test Plan
Section 3
Version 1.0
programming templates will be reviewed and a radio of each type functionally tested, as part
of the Fleetmapping process.
3.0 GENERAL CONDUCT OF TESTING
The test procedures listed in this document do not need to be performed in the order
presented. The duration of the Factory Acceptance Test should be approximately two (2)
days. Any deviations to the prescribed test procedures will be recorded on the test procedure
forms. A test will be considered complete and successful when the operation or function
described under the test meets or exceeds the specified requirements.
4.0 TRUNKING FEATURES AND SYSTEM TESTS
4.1 Talkgroup Call
The talkgroup is the primary level of organization for communications on a trunked radio
system. Radios with talkgroup call capability will be able to communicate with other
members of the same talkgroup. This provides the effect of a private channel down to the
talkgroup level. This test will demonstrate that a talkgroup transmission initiated by a radio
user will only be heard by system users, who have, the same talkgroup selected.
4.2 Announcement Group Call
An announcement talkgroup call provides the capability for subscriber units on different
talkgroups to receive a multi-group call. This test will demonstrate the operation of
announcement talkgroup calls.
4.3 Busy Queuing and Call Back
If a radio user depresses the PIT while all the system channels are in use, a series of busy
tones will be heard until a channel is assigned, or until the PTT is released. For
convenience, any users requesting system access during a busy period will be put in a queue
on a FIFO (first-in, first-out) basis. When a channel does become available, the "system"
wi II notify the first user by "calling back". A talk permit tone alerts the radio user of the call
Use or disclosllre oftllis proposal is subject to the reslrictions on lhe (itle page.
Motorola Confidential Proprietary
(fJ....') MOTOROLA February 2002
'--./
2
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Factory Acceptance Test Plan
Section 3
Version 1.0
back. This feature allows the radio user to depress the PTT button once and wait for the call
back, instead of continuously keying in an effort to gain a voice channel. This test will
demonstrate the busy queuing and call back features of the system.
4.4 Continuous Assignment Updating
When a talkgroup is assigned a voice channel, the trunking system controller continues to
transmit the channel assignment information on the control channel, for as long as the
talkgroup is using the channel. This test will demonstrate that a radio which has recently
been turned on or entered the service area, will be steered to the appropriate voice channel to
join the rest of the talkgroup in the conversation.
4.5 Recent User Priority
The Recent User Priority feature is used to provide uninterrupted communications on the
trunked radio system. Recent User Priority assures that users who have previously been
assigned a voice channel will receive priority over other system users of the same priority
level.
Recent user status ends if a PTT is not activated within approximately 10 seconds of the
channel assignment ending. This test will demonstrate the use of the Recent User Priority
feature.
4.6 Talk Prohibit I Out-of-Range
This test will demonstrate that a subscriber radio will generate a "Talk Prohibit / Out of
Range" tone when the trunking system is not accessible or is out of range.
4.7 Call Alert and Private Call
The Call Alert feature allows a subscriber radio (or console operator) to selectively alert an
individual radio unit. The signalling is done on the control channel and produces an audible
and visual alert on the target radio.
Use or disclosure of this proposal is subject 10 the restrictions on the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
3
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Factory Acceptance Test Plan
Section 3
Version 1.0
The Private Call feature allows a subscriber radio (or console operator) to selectively call
individual radio units and conduct a conversation, which other radios in the talkgroup cannot
monitor.
Note: All subscriber radios in the system are capable of being programmed to receive Call
Alerts and Private Calls, however only a select group of radios should be programmed to
send and receive Call Alerts and Private Calls. This test will demonstrate the operation of
the Call Alert and Private Call functions using two appropriately programmed subscriber
radios.
4.8 Talkgroup Scan
The Talkgroup Scan feature enables a subscriber radio unit to automatically monitor specific
talkgroups or channels for any activity. The radio "listens" for activity on each talkgroup in
the scan list for a brief interval and then moves on to the next talkgroup in the list. Scanning
continues until either the scan mode is turned off or the PTT is pressed. This test will
demonstrate the operation of the Talkgroup Scan function using two subscriber radio units.
4.9 System Channels Functional Verification
The Trunked Radio System will be equipped with nine (9) trunking channels. Channels 1
through 4 will be Control and Voice capable, and channels 5 through 9 will be Voice-Only
capable. The system control channel will rotate between channels 1,2,3 and 4, which
means that, at any given time, eight (8) channels will be available for voice calls. This test
will demonstrate that each channel can be assigned for a voice call.
5.0 CENTRACOM ELITE DISPATCH CONSOLES
Note that the staged console equipment is not intendea for stand-alone operation. Only the
new CBB boards and card cages will be available for testing which are add-ons to the
existing equipment and do not make up an entire dispatch console system. Only a sample of
tests will be performed. The CCSi implementation will provide sufficient functionality to
demonstrate the following features.
Use or disclosure (if this proposal is subject to the restrictiolls Oil the title page.
Motorola Confidential Proprietary
Cf!) MOTOROLA. February 2002
4
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Factory Acceptance Test Plan
Section 3
Version 1.0
5.1 Talkgroup Call Operation
This test will demonstrate talkgroup call processing and system access (including system
busy and callback features) for a Console Operator Position.
5.2 PTT-ID Display
The console operator positions will display the alias (or trunked unit ID) of subscriber radios
in the talkgroup resource window, each time a subscriber unit initiates a PTT. The
subscriber radios will be programmed to send their ID on every transmission. This test will
demonstrate the display, queuing and processing of PTT unit IDs at the console position.
5.2 Console Priority
The console operator is provided with priority access on any channel or talkgroup, which can
be monitored at the console operator position. Through console priority, a dispatcher can
override any field radio unit transmissions. While the dispatcher is transmitting, it is still
possible for a field unit to "get into" the system, as the dispatcher will be able to hear anyone
calling in. This test will demonstrate the console priority capability of the system.
5.3 Multi-Select I Patch Operation
Multi -Select:
This function allows the console operator to group a number of talkgroups (or channels)
together such that when the general transmit is activated, all of the multi-selected talkgroups
(or channels) will transmit at the same time with the same console transmit audio. Using the
Multi-Select feature, the console operator can talk and listen to all of the selected talkgroups
grouped; however, the members of the individual talkgroups cannot talk or listen to
members of other talkgroups. This test will demonstrate the procedure for setting up and
transmitting on multi-select groups from a console operator position.
Patch:
This function allows the console operator to group ("patch") two or more talkgroups (or
channels) together, thereby enabling voice communications between the "patched"
Use or disclosure ((( this proposal is subject to the restrictiollS 011 the title page.
Motorola Confidential Proprietary
@ MOTOROL.A February 2002
5
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Factory Acceptance Test Plan
Section 3
Version 1.0
talkgroups and the dispatcher. Talkgroups included in a patch set-up are merged on to a
single voice channel for the duration of the patch operation. Using the Patch feature, the
console operator can talk and listen to all of the selected talkgroups in the patch. In addition,
the members of the individual talkgroups can talk or listen to members of other talkgroups in
the patch. This test will demonstrate the procedure for patching talkgroups together at a
console operator position.
6.0 FAILURE SCENARIOS
Before the following tests are performed, the system must be stable and fully operational,
with no known failures.
6.1 Voice Channel Repeater Failure
When a voice channel repeater fails at a remote site, the affected channel is automatically
removed from service at all remote sites. This test will demonstrate the system's reaction to
a single voice channel failure and the fault reporting provided.
6.2 Control Channel Repeater Failure
The system includes four (4) control channel capable repeaters at each remote site. This test
will demonstrate how the system recovers from control channel failures. The following
failure scenarios will be verified:
1) If the assigned control channel fails at a remote site, the channel is removed from
service system-wide, and another channel is assigned for control channel duty.
2) If a different control channel repeater fails at four different remote sites, the system will
revert to a wide area failsoft mode of operation due to the lack of a common, functional
control channel at the remote sites. Note: the system will not automatically continue
full mode trunked operation with fewer sites.
3) If all control channel repeaters fail at the same remote site, and at all other sites all of
the control channel repeaters are operational, the affected remote site is removed from
service, or idled. The system will continue to operate in trunking mode with the
remaining sites.
Use or disclosure of this proposal is subject to the restrict/Oils Oil the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
6
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Factory Acceptance Test Plan
Section 3
Version 1.0
6.3 Remote Site Controller Failure
If a Remote Site Controller fails due to a power failure or other cause, the system will
continue to operate in wide area (simulcast) trunking mode without the failed remote site.
This test will demonstrate the system's reaction to a Remote Site Controller failure.
6.4 Prime Site Controller Failure
If the main Prime Site Controller fails, operation will switch to the backup controller with no
disruptions to normal operations, except that in-progress calls will be interrupted. If both
Prime site controllers fail, the system will revert to wide area failsoft mode. Users will be
steered to pre-programmed repeater channels based on talkgroup selection, and will be given
a visual (depending on the type of field radio) and audible indication of the failsoft
condition.
6.5 T1 Network link to Single Remote Site Failure
If a link to a remote site fails, the system will continue to operate in wide area (simulcast)
trunking mode without the failed remote site. This test will demonstrate the system's
reaction to a remote site Tllink failure.
Use or disclosure o(lhis propos(ll is slIbjecllo lhe reslricliollS ollrhe rille p(lge.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
7
EXHIBIT C-5
SECTION 3
FIELD ACCEPTANCE
TEST PLAN
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Field Acceptance Test Plan
Section 3
Version 1.0
TABLE OF CONTENTS
1.0 PURPOSE AND SCOPE ............................................................................ 1
2.0 SYSTEM TEST CONFIGURATION AND EQUIPMENT REQUIREMENTS1
3.0 GENERAL CONDUCT OF TESTING ......................................................... 2
4.0 TRUNKING FEATURES AND SYSTEM TESTS........................................ 2
4.1 Talkgroup Call.. ................ ........... ............... ............................ .............. ....... 2
4.2 Announcement Group Call.......................................................................... 3
4.3 Busy Queuing and Call Back ......................................................................3
4.4 Continuous Assignment Updating............................................... ................ 3
4.5 Recent User Priority.................. .................................................................. 3
4.6 Talk Prohibit / Out-ot-Range .......................................................................4
4.7 Call Alert and Private Call........................................................................... 4
4.8 Talkgroup Scan........................................................................................... 4
4.9 System Channels Functional Verification ...................................................4
5.0 CENTRACOM ELITE DISPATCH CONSOLES ......................................... 5
5.1 Talkgroup Call Operation .................................. .......................................... 5
5.2 PTT -10 Display........................................................................................... 5
5.2 Console Priority.......................................................................................... 5
5.3 Multi-Select / Patch Operation ....................................................................5
Multi-Select: ......................................................................................................... 5
Patch:....................................:.............................................................................. 6
5.4 Paging Interface.......................................................................................... 6
5.5 Conventional Channel Operation................................................................ 6
5.6 Trunked Talkgroup to Conventional Channel Patch ................................... 6
5.7 Logging Recorder Outputs.......................................................................... 7
6.0 SMARTNET SYSTEM MANAGEMENT ..................................................... 7
6.1 SystemWatch Terminal................................................................. .............. 7
6.2 System Management Terminal (SMT) Functions........................................ 7
7.0 F AllU RE SCENARIOS .............................................................................. 7
Use or disclosure oftilis proposal is subject 10 the restrictio/lS 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Field Acceptance Test Plan
Section 3
Version 1.0
7.1 Voice Channel Repeater Failure............................. .............. ...................... 7
7.2 Control Channel Repeater Failure ..............................................................8
7.3 Remote Site Controller Failure.................................................................... 8
7.4 Prime Simulcast Controller Failure ............................................................. 8
7.5 T1 Network Link to Single Remote Site Failure .......................................... 9
8.0 SITE INSPECTIONS AND TESTS ............................................................. 9
Use or disclosure o{ this proposal is subject 10 the restrictions OIl the tille page.
Motorola Confidential Proprietary
@ MOTOROLA
11
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Field Acceptance Test Plan
Section 3
Version 1.0
FIELD ACCEPTANCE TEST PLAN
1.0 PURPOSE AND SCOPE
The purpose of the Field Acceptance Test Plan is to verify the basic operation, functionality,
and installation quality of The Fire Departments of Durham Region 800 MHz SmartNet,
Simulcast, Analog, Trunking System. The Field ATP has been designed to validate the
ability of the trunked radio system to deliver the designed and contract required system
functionality to the end users. System functions and features not included within this ATP
will not be tested. Successful completion of the Field A TP will fulfill part of the Final
Acceptance requirements.
The Field A TP provides a list of the Test Procedures, including a brief description, which
Motorola will execute with The Fire Departments of Durham Region Representatives. The
actual Test Procedure sheets will be provided to The Fire Departments of Durham Region
before the scheduled start of the Field Test. In addition to the functional tests covered in the
Factory Acceptance Test Plan, the Field ATP will include the following elements:
1) Site Inspections and tests will be performed.
2) System coverage will be verified during the Field Acceptance Test phase, and is
described in a separate document, titled Coverage Design and Verification
Methodology.
3) Limited testing will be done on Console functionality.
4) Existing infrastructure will be tested.
2.0 SYSTEM TEST CONFIGURATION AND
EQUIPMENT REQUIREMENTS
The complete fixed radio network, including the T 1 transmission system, must be installed
and fully optimized before the System Field A TP can commence. This includes all of the
equipment at the Prime Simulcast Control site and Remote sites. All of the system Remote
Use or disclosure of this proposal is subject to the restrictions on the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Field Acceptance Test Plan
Section 3
Version 1.0
sites must be operational during the test to demonstrate simulcast system performance and
basic RF coverage. The system installation checklists and test results sheets shall be
available to indicate that the system equipment has been properly installed and optimized
prior to the beginning of the Field ATP.
User Equipment:
The following "user" equipment will be required for the Field Acceptance Test:
. SmartNet XTS3000 portable radios
. SmartNet MCS2000 mobile radios
. Fixed mobile radios
. CentraCom Gold Series Elite Console operator positions
. SmartNet System Management terminal
3.0 GENERAL CONDUCT OF TESTING
The test procedures listed in this document do not need to be performed in the order
presented. The duration of the Field Acceptance Test should be approximately three (3) full
days, including the time required for site visits. Any deviations to the prescribed test
procedures will be recorded on the test procedure forms. A test will be considered complete
and successful when the operation or function described under the test meets or exceeds the
specified requirements.
4.0 TRUNKING FEATURES AND SYSTEM TESTS
4.1 Talkgroup Call
The talkgroup is the primary level of organization for communications on a trunked radio
system. Radios with talkgroup call capability will be able to communicate with other
members of the same talkgroup. This provides the effect of a private channel down to the
talkgroup level. This test will demonstrate that a talkgroup transmission initiated by a radio
user will only be heard by system users, who have, the same talkgroup selected.
Use or disclosure (!I'this proposal is subject to the restrictions 011 the title page,
Motorola Confidential Proprietary
@ MOTOROL.A February 2002
2
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Field Acceptance Test Plan
Section 3
Version 1.0
4.2 Announcement Group Call
An announcement talkgroup call provides the capability for subscriber units on different
talkgroups to receive a multi-group call. This test will demonstrate the operation of
announcement talkgroup calls.
4.3 Busy Queuing and Call Back
If a radio user depresses the PIT while all the system channels are in use, a series of busy
tones will be heard until a channel is assigned, or until the PTT is released. For
convenience, any users requesting system access during a busy period will be put in a queue
on a FIFO (fi.rst-in, fust-out) basis. When a channel does become available, the "system"
will notify the first user by "calling back". A talk permit tone alerts the radio user of the call
back. This feature allows the radio user to depress the PTT button once and wait for the call
back, instead of continuously keying in an effort to gain a voice channel. This test will
demonstrate the busy queuing and call back features of the system.
4.4 Continuous Assignment Updating
When a talkgroup is assigned a voice channel, the trunking system controller continues to
transmit the channel assignment information on the control channel, for as long as the
talkgroup is using the channel. This test will demonstrate that a radio which has recently
been turned on or entered the service area, will be steered to the appropriate voice channel to
join the rest of the talkgroup in the conversation.
4.5 Recent User Priority
The Recent User Priority feature is used to provide uninterrupted communications on the
trunked radio system. Recent User Priority assures that users who have previously been
assigned a voice channel will receive priority over other system users of the same priority
level.
Recent user status ends if a PTT is not activated within approximately 10 seconds of the
channel assignment ending. This test will demonstrate the use of the Recent User Priority
feature.
Use or disclosure ()ltilis proposal iI IubjeN (() the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
3
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Field Acceptance Test Plan
Section 3
Version 1.0
4.6 Talk Prohibit I Out-of-Range
This test will demonstrate that a subscriber radio will generate a "Talk Prohibit / Out of
Range" tone when the trunking system is not accessible or is out of range.
4.7 Call Alert and Private Call
The Call Alert feature allows a subscriber radio (or console operator) to selectively alert an
individual radio unit. The signalling is done on the control channel and produces an audible
and visual alert on the target radio.
The Private Call feature allows a subscriber radio (or console operator) to selectively call
individual radio units and conduct a conversation, which other radios in the talkgroup cannot
monitor.
Note: All subscriber radios in the system are capable of being programmed to receive Call
Alerts and Private Calls, however only a select group of radios should be programmed to
send and receive Call Alerts and Private Calls. This test will demonstrate the operation of
the Call Alert and Private Call functions using two appropriately programmed subscriber
radios.
4.8 Talkgroup Scan
The Talkgroup Scan feature enables a subscriber radio unit to automatically monitor specific
talkgroups or channels for any activity. The radio "listens" for activity on each talkgroup in
the scan list for a brief interval and then moves on to the next talkgroup in the list. Scanning
continues until either the scan mode is turned off or the PTT is pressed. This test will
demonstrate the operation of the Talkgroup Scan function using two subscriber radio units.
4.9 System Channels Functional Verification
The Trunked Radio System will be equipped with nine (9) trunking channels. Channels 1
through 4 will be Control and Voice capable, and channels 5 through 9 will be Voice-Only
capable. The system control channel will rotate between channels 1,2,3 and 4, which mean
that, at any given time, eight (8) channels will be available for voice calls. This test will
demonstrate that each channel can be assigned for a voice call.
Use or disclosure of this proposal is subject 10 the restrictiollS 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
4
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Field Acceptance Test Plan
Section 3
Version 1.0
5.0 CENTRACOM ELITE DISPATCH CONSOLES
The following tests will be performed on the consoles at the Oshawa Communications
Centre and at the consoles at the remote dispatch centre.
5.1 Talkgroup Call Operation
This test will demonstrate talkgroup call processing and system access (including system
busy and callback features) for a Console Operator Position.
5.2 PTT-ID Display
The console operator positions will display the alias (or trunked unit ill) of subscriber radios
in the talkgroup resource window, each time a subscriber unit initiates a PTT. The
subscriber radios will be programmed to send their ill on every transmission. This test will
demonstrate the display, queuing and processing of PTT unit IDs at the console position.
5.2 Console Priority
The console operator is provided with priority access on any channel or talkgroup, which can
be monitored at the console operator position. Through console priority, a dispatcher can
override any field radio unit transmissions. While the dispatcher is transmitting, it is still
possible for a field unit to "get into" the system, as the dispatcher will be able to hear anyone
calling in. This test will demonstrate the console priority capability of the system.
5.3 Multi-Select I Patch Operation
Multi-Select:
This function allows the console operator to group a number of talkgroups (or channels)
together such that when the general transmit is activated, all of the multi-selected talkgroups
(or channels) will transmit at the same time with the same console transmit audio. Using the
Multi-Select feature, the console operator can talk and listen to all of the selected talkgroups
grouped; however, the members of the individual talkgroups cannot talk or listen to
Use or disc/oSllre ()f'this proposal is subject 10 the restrictiolls 011 the lille page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
5
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Field Acceptance Test Plan
Section 3
Version 1.0
members of other talkgroups. This test will demonstrate the procedure for setting up and
transmitting on multi-select groups from a console operator position.
Patch:
This function allows the console operator to group ("patch") two or more talkgroups (or
channels) together, thereby enabling voice communications between the "patched"
talkgroups and the dispatcher. Talkgroups included in a patch set-up are merged on to a
single voice channel for the duration of the patch operation. Using the Patch feature, the
console operator can talk and listen to all of the selected talkgroups in the patch. In addition,
the members of the individual talkgroups can talk or listen to members of other talkgroups in
the patch. This test will demonstrate the procedure for patching talkgroups together at a
console operator position.
5.4 Paging Interface
The paging feature is used for sending pages to individuals or groups. Individuals and groups
are represented by aliases and can be accessed through a list of aliases in a standard page
dialog window or resources on the folders. This test will demonstrate the ability to page an
individual at the console operator position.
5.5 Conventional Channel Operation
Each console operator position will include a conventional channel resource window for the
new conventional channel that will be incorporated into the console. This test will
demonstrate the console capability for accessing and monitoring the conventional channel,
and enabling/disabling the repeater operation.
5.6 Trunked Talkgroup to Conventional Channel Patch
The console system will provide the capability to patch conventional channel radio users to
radio units on the trunked radio system, through the console patch feature. This test will
demonstrate the procedure for patching a conventional channel to a trunked talkgroup at a
console operator position.
Use or disclosure of'this proposai is subject to the restrictioIIS 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
6
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Field Acceptance Test Plan
Section 3
Version 1.0
5.7 Logging Recorder Outputs
The CentraCom console logging recorder interface "de-trunks" the audio from talkgroup
calls, to ensure that trunked talkgroup audio is always recorded to the same track on a
logging recorder. This test will demonstrate that the logging recorder output for each
talkgroup is routed to the correct track (audio will be monitored at the appropriate punch
block terminals if logging recorder is not ready or available).
6.0 SMARTNET SYSTEM MANAGEMENT
6.1 SystemWatch Terminal
This test will verify the operation of the SystemWatch terminal for the new channels at the
Oshawa Fire Dispatch Centre.
6.2 System Management Terminal (SMT) Functions
This test will verify the operation of the SMT for the new channels at the Oshawa Fire
Dispatch Centre.
7.0 FAILURE SCENARIOS
Before the following tests are performed, the system must be stable and fully operational,
with no known failures.
7.1 Voice Channel Repeater Failure
When a voice channel repeater fails at a remote site, the affected channel is automatically
removed from service at all remote sites. This test will demonstrate the system's reaction to
a single voice channel failure and the fault reporting provided.
Use or disclosure of tills proposal is subject to tile restrictiolls Oil the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
7
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Field Acceptance Test Plan
Section 3
Version 1.0
7.2 Control Channel Repeater Failure
The system includes four control channel capable repeaters at each remote site. This test
will demonstrate how the system recovers from control channel failures. The following
failure scenarios will be verified:
1) Ifthe assigned control channel fails at a remote site, the channel is removed from
service system-wide, and another channel is assigned for control channel duty.
2) If a different control channel repeater fails at four different remote sites, the system will
revert to a wide area failsoft mode of operation due to the lack of a common, functional
control channel at the remote sites. Note: the system will not automatically continue
full mode trunked operation with fewer sites.
3) If all control channel repeaters fail at the same remote site, and at all other sites all of
the control channel repeaters are operational, the affected remote site is removed from
service, or idled. The system will continue to operate in trunking mode with the
remaining sites.
7.3 Remote Site Controller Failure
If a Remote Site Controller fails due to a power failure or other cause, the system will
continue to operate in wide area (simulcast) trunking mode without the failed remote site.
This test will demonstrate the system's reaction to a Remote Site Controller failure.
7.4 Prime Simulcast Controller Failure
If the main Prime Simulcast Controller fails, operation will switch to the backup controller
with no disruptions to normal operations, except that in-progress calls will be interrupted. If
both Prime site controllers fail, the system will revert to wide area failsoft mode. Users will
be steered to pre-programmed repeater channels based on talkgroup selection, and will be
given a visual and audible indication of the failsoft condition.
Use or disclosure (!(this proposal is subject to the restrictions on the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
8
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Field Acceptance Test Plan
Section 3
Version 1.0
7.5 T1 Network Link to Single Remote Site Failure
If a link to a remote site fails, the system will continue to operate in wide area (simulcast)
trunking mode without the failed remote site. This test will demonstrate the system's
reaction to a remote site Tllink failure.
8.0 SITE INSPECTIONS AND TESTS
PART A: The following items will be checked to verify the installation quality and
configuration of the system infrastructure sites. In general, the site installations should
conform to Motorola's R56 Installation Quality Standards.
1) Equipment room layout
2) Equipment inventory, configuration and rack layouts
3) Electrical system
4) Heating, ventilation, and air conditioning
5) UPS and battery installation
6) Cable routing
7) Antenna and transmission line installation
8) Grounding and bonding
PART B: The following tests will be performed to demonstrate proper site operation:
1) Site alarm reporting (Motorola equipment)
2) Site emergency power system test
(The operation of the site backup power systems will be demonstrated, however the
backup time duration will not be verified).
Use or disclosflre ()f this proposal is subject 10 the restrictiollS 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
9
EXHIBIT C-6
SECTION 3
MOSCAD FIRE HALL ALERTING
SYSTEM ACCEPTANCE TEST
PLAN
The Fire Departments of Durham Region
MOSCAD FIRE HALL ALERTING SYSTEM
Acceptance Test Plan
Version 0.1
TABLE OF CONTENTS
MOSCAD FIRE HALL ALERTING ACCEPTANCE TEST PLAN........................ 1
1.0 Acceptance Test Plan Types .... .................... ...... ....... .... ................................. 1
1. 1 Factory Acceptance Test............ ....................... ...................... ................................. 1
1.2 Field Functional Acceptance Test... ......................... ........ ............ ............................. 1
2.0 Scope of Document..... .............. ........... ...... ...... ........ ..... ... ......... .... .... ......... .... 1
3.0 Methodology of A TP ....................................................................................... 2
4.0 GENERAL CONDUCT OF TESTING ........................................................ 2
5.0 Fire Hall Alerting.................................................................. ........................... 3
5. 1 MOSCAD Fire Hall Alerting on Elite Consoles..................................................... 3
5.1.1 Alerting A Single Fire Hall..............................................................~......... 3
5.1.2 Alerting Multiple Fire Halls Oshawa/Whitby/Clarington ............................ 3
5.1.3 Alerting Multiple Fire Halls Pickering/Ajax AND
Oshawa/Whitby/Clarington ...................................................................... 3
5.2 Printing Events/Alarms........................................................................................ 3
6.0 Installation Checklists................ ............. .............. ............................... ........... 4
Use or disclosure of this proposal is subject to the restrictiolls Oil the ritle page.
Motorola Confidential Proprietary
@ MOTOROLA
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
MOSCAD Fire Hall Alerting Acceptance Test Plan
Section 3
Version 1.0
MOSCAD FIRE HALL ALERTING
ACCEPTANCE TEST PLAN
1.0 ACCEPTANCE TEST PLAN TYPES
Motorola will contract to perform the following two acceptance tests:
1. A Factory Acceptance Test
2. A Field Functional Acceptance Test
1.1 Factory Acceptance Test
The Factory Acceptance Test will be conducted in Motorola's Customer Centre for System
Integration (CCSI) facility in Schaumburg, Illinois. The infrastructure will be assembled
and tested as a complete system along with the 800 MHz SmartNet system infrastructure.
1.2 Field Functional Acceptance Test
Following system installation and dry run testing, Motorola will perform the Field
Functional Acceptance Tests. These tests will include the tests completed at CCSI as well as
some additional tests that could not be performed at the staging facility such as those related
to the sites and installation. The Field Functional Acceptance Test will occur after
installation of the network infrastructure at the Halls and Dispatch Centres.
2.0 SCOPE OF DOCUMENT
The purpose of the MOSCAD Acceptance Test Plan is to verify the basic operation,
functionality, and installation quality of the system. The ATP has been designed to validate
the ability of the system to deliver the designed and contract required system functionality.
System functions and features not included within this A TP plan will not be tested.
The ATP provides a list ofthe tests, including a brief description, which Motorola will
execute with the Fire Departments of Durham Region representatives. The actual Test
Use or disclosure of this proposal is subject to the restrictiolls all the title page.
Motorola Confidential Proprietary
@ MOTOROLA. February 2002
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
MOSCAD Fire Hall Alerting Acceptance Test Plan
Section 3
Version 1.0
Procedure sheets will be provided to the Fire Departments of Durham Region before the
scheduled start of the Factory and Field Acceptance Tests.
3.0 METHODOLOGY OF ATP
There will be two (2) MOSCAD-L Low Capacity Fire Hall Alerting Systems in this system.
One will be used to alert the Fire stations in Oshawa/Whitby/Clarington area, the other one
will be used to alert the Fire stations in Pickering/Ajax area.
Two (2) Fire Halls in Oshawa/Whitby/Clarington and two (2) Fire Halls in Pickering/Ajax
will be tested for command activation as a group. The system will be tested in a closed loop
fashion, meaning that multiple functions may be tested during one process. In addition to
command activation, the Fire Hall RTU will be tested for correct status feedback. In this
case, only a sample of two (2) Fire Station RTUs will be tested for correct Status feedback
since each Fire Station has the same hardware and runs an identical software program.
In the event that a part of the system fails a test, the system will be re-tested when Motorola
determines that a corrective action was taken to ensure proper operation.
After the system's functionality has been proven to the Fire Departments of Durham Region,
and both a Motorola representati ve and a Fire Departments of Durham Region representati ve
have signed the ATP document, the Acceptance Test will be considered to be successfully
completed and the system functionality deemed acceptable.
4.0 GENERAL CONDUCT OF TESTING
The tests listed in this document do not need to be performed in the order presented. The
duration of the Acceptance Test should be approximately four full days, including the time
required for site visits. Any deviations to the prescribed test procedures will be recorded on
the test procedure forms. A test will be considered complete and successful when the
operation or function described under the test meets or exceeds the specified requirements.
Use or disclosure of this proposal is subject 10 the restrictiolls Oil the title page.
Motorola Confidential Proprietary
([!j MOTOROLA February 2002
:2
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
MOSCAD Fire Hall Alerting Acceptance Test Plan
Section 3
Version 1.0
5.0 FIRE HALL ALERTING
5.1 MOSCAD Fire Hall Alerting on Elite Consoles
The MOSCAD-L Low Capacity Fire Hall Alerting System works on the Motorola
CENTRACOM Gold Elite Fire Dispatch Workstation computers, two of which will be used
to perform the tests. It will not be necessary to perform all the tests on both consoles,
therefore, the tests will be performed on one or the other or may alternate between the two
consoles with each test.
5. 1. 1 Alerting A Single Fire Hall
This test will demonstrate the ability to alert one Fire Station RTU with tone and voice.
5. 1.2 Alerting Multiple Fire Halls Oshawa/Whitby/Clarington
This test will demonstrate the ability to alert two Fire Station RTUs from the
Oshawa/Whitby/Clarington area at the same time for one incident.
5.1.3 Alerting Multiple Fire Halls Pickering/Ajax AND
Oshawa/Whitby/Clarington
This test will demonstrate the ability to alert two Fire Station RTUs in
Oshawa/Whitby/Clarington area and at the same time, alert two Fire Station RTUs in the
Pickering and Ajax area.
5.2 Printing Events/Alarms
This test will demonstrate that the Dot-Matrix printer, co-located with the PEPs, will
print out alarms and events in real-time.
Use or disclosure of this proposal is subject to the restrictiolls 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
3
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
MOSCAD Fire Hall Alerting Acceptance Test Plan
Section 3
Version 1.0
6.0 INSTAllATION CHECKLISTS
The system installation checklists and test results sheets shall be made available by Motorola
to indicate that the system equipment has been properly installed and optimized prior to the
beginning of the Field A TP.
The following items will be checked independent of who has installation responsibility to
verify the installation quality and configuration of the MOSCAD Fire Hall Alerting
Equipment. The site installations should conform to Motorola's R56 Installation Quality
Standards and MOSCAD Site Requirements Plan.
1) Equipment room layout,
2) Equipment inventory and configuration,
3) Electrical system
4) Heating, ventilation, and air conditioning
5) UPS and battery installation,
6) Cable routing,
7) Fire Hall Antenna,
8) Fire Hall P A Connection.
Use or disclosure i!j"this proposal is subject to the restrictiolls Oil the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
4
EXHIBIT 0-1
STATEMENT OF WORK
ENHANCED SYSTEM SUPPORT
1.0 Definitions
Capitalized terms used in this Statement of Work and not otherwise defined within the
Statement of Work, Communications System Agreement or other applicable Agreement
have the following meanings:
1.1 Case: Electronic tracking document for requests for service through the System
Support Center.
1.2 Continuously: Seven (7) days per week, twenty four (24) hours a day, three
hundred sixty-five (365) days a year including holidays.
1.3 Core Release: A new version of Software that adds Standard Features and major
enhancements. These new versions are signified by changes to the first digit of
the version identifier number (e.g. SmartZone 2.0.3 to SmartZone 3.0).
1.4 Customer: The end-user Customer as identified in the Communications System
Agreement, Service Agreement or other applicable Agreement.
1.5 Customer Support Plan: A document mutually developed by Motorola and the
Customer that provides information about the Customer and the System and
describes the specific processes by which Motorola will deliver and the Customer
will receive the services promised under this Statement of Work.
1.6 Enhancement Release: A superseding issue of Software, which adds to,
improves, or enhances the performance of Standard Features contained in the
then currently shipping Software version. These releases are signified by
changes to the second digit of the version identifier number (e.g. SmartZone 3.1
to SmartZone 3.2).
1.7 Equipment: The equipment specified in the Equipment List as set forth in the
Communications System Agreement, Service Agreement or other applicable
Agreement, including any additions to the Equipment List during the Warranty
Period.
1.8 Enhanced System Support (ESS) Period: The 12 month period commencing at
the start of the Warranty Period for Equipment and Software as defined by the
Communications System Agreement.
1.9 Event: An alarm or informational notification received by Motorola through the
Network Management tools.
1.10 Firmware: Software in object code form that is implanted or embedded in
hardware.
1.11 Infrastructure: The fixed Equipment excluding mobiles, portables, and
accessories.
1.12 Maintenance: The process for determining the cause of Equipment failure,
removing, repairing, or replacing parts or elements necessary in order to conform
Use or disclosure ()j'this proposal is subject to the restrictiolls 0/1 the title page.
Motorola Confidential Proprietary
([!y MO"ff'OROLA December 2001
the Equipment with the manufacturer's specifications along with system specific
specifications, delivering and reinstalling the parts, and placing the Equipment
back into operation.
1.13 Motorola Software: Software whose copyright is owned by Motorola.
1.14 Response: Response times are defined as when a technician, a remote systems
technologist or a remote network specialist is actively working the technical
issue, remotely or on-site, as determined by Motorola.
1.15 Restore/Restoration: The effort required to bring Equipment to the level for which
it was designed, engineered and adjusted for performance in accordance with
the manufacturer's published specifications, although such Equipment may not
necessarily be malfunctioning.
1.16 Servicer: a Motorola Authorized Service Station or Motorola Field Service
personnel.
1.17 Software: Includes Motorola and any non-Motorola Software that may be
furnished with the Communications System.
1.18 Standard Business Day: Monday through Friday, 8:30 a.m. to 4:30 p.m., local
time, excluding Motorola holidays.
1.19 Standard Feature: A software functionality for components of Customer's System
that is available to Customer in the standard software release.
1.20 Start Date: Effective start date as listed on the Service Agreement or other
applicable Agreement.
1.21 System: System is the communications system as defined in the
Communications System Agreement or other applicable Agreement.
1.22 System Acceptance: Unless otherwise defined in the Communications System
Agreement, the date upon which Motorola has successfully completed all of the
System tests as described in the acceptance test plan.
1.23 System Support Center: a Motorola facility located in Schaumburg, Illinois, the
purpose of which is to serve as Motorola's centralized system support facility to
compliment the field support resources. The System Support Center is
hereinafter referred to as the "SSC."
1.24 Systemic: A software/hardware product defect related to or affecting the
designed system operation.
1.25 Technical Support Operations: A centralized telephone support help desk that
provides technical support for Motorola customers who have purchased
Commercial Government and Industrial Solutions Sector (CGISS) products or
have a contract for technical support.
Use or disclosure qj'this proposal is subject to the restrictiollS Oil the litle page.
Motorola Confidential Proprietary
@ MOTOROLA December 2001
2
STATEMENT OF WORK
ENHANCED SYSTEM SUPPORT
Description of Services
Enhanced System Support (ESS) is a bundled service and support package designed to support
both the software and hardware components of a new System during the ESS Period. By
combining these services into a comprehensive and cohesive offering, Motorola is able to most
effectively deliver technical support, diagnostic assistance, and restoration services in a thorough
and timely manner.
During the ESS Period, ESS services supplement and compliment the Warranty as described in
the Communications System Agreement. The full offering of ESS services is included in the
Purchase Price of the System. After the ESS Period expires, these services are available for
purchase under a separate agreement.
ESS services will be provided in accordance with the terms and conditions set forth at the end of
this Statement of Work and in the Software Subscription Agreement which is attached as an
exhibit to the Communications System Agreement. If any conflict exists between the Statement of
Work provisions and the Terms and Conditions, the Terms and Conditions shall prevail.
Motorola Enhanced System Support is comprised of the following service products that will be
described in greater detail later in this Statement Of Work:
. Dispatch Service
. Technical Support
. Network Monitoring Service
. OnSite Infrastructure Response
. Advanced Replacement
. Software Subscription Agreement
. Infrastructure Software Installation
. Software Upgrade Design
. System Audit
Expansion, Replacement, or Phased Implementation Equipment
As indicated above, ESS services are provided to support a new System. However, if after
System Acceptance new Equipment is being integrated with an existing System to expand the
System, replace a major part of the System. or provide a subsequent phase of the System if it
was originally sold as a multiple phase project, then such new Equipment will be covered as
follows:
If the existing System is covered under its original ESS program, the new Equipment will be
covered as if it were part of the original System for the remainder of the ESS Period.
Use or disclosure of this proposal is subject to the restrictiolls 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA December 2001
3
If the existing System is not covered under its original ESS program but is covered under a
service agreement with Motorola to provide services, then the new Equipment will be covered at
the same level of service for the remainder of the term of that service agreement and the price for
the service agreement will be increased to cover the additional Equipment.
If the existing System is not covered under either its original ESS program or a service agreement
with Motorola, the new Equipment is covered only by the Equipment warranty and not by ESS.
ISO and Plant Exclusion
The ESS program originated from and was designed to support Motorola's radio systems
business. After the ESS program was established, Motorola acquired certain companies and
later created its Integrated Solutions Division ("ISD") as part of its Commercial, Government, and
Industrial Solutions Sector. ISO includes Motorola's affiliated companies, Printrak International,
Incorporated ("Printrak") and Suncoast Scientific, Incorporated ("Suncoast"), as well as the
products of the former Software Corporation of America (such as TxMessenger™, Premier
MDCTM and other application software products under the "Premier" product name, and
AirMobile™). Neither the ESS program nor the Software Subscription program covers the
software, hardware, or services provided by ISO or by Plant Equipment, Inc. ("Plant"), Motorola's
primary E911 solution subcontractor. ISO and Plant products and services may be covered by
separate maintenance and support agreements.
1.0 Motorola has the following responsibilities:
All services described in the ESS Statement of Work will be provided in accordance with
the terms of the Communications System Agreement and will cover only the Equipment
and related Software.
Prepare a Customer Support Plan in conjunction with the Customer, preferably before
System Acceptance.
2.0 Customer has the following responsibilities:
2.1 Prepare a Customer Support Plan in conjunction with Motorola, preferably before
System Acceptance. The Customer must provide all information necessary to
complete the Customer Support Plan.
2.2 Cooperate with Motorola and perform all acts that are reasonable or necessary to
enable Motorola to provide the ESS services to Customer.
Statement of Work
Dispatch Service
Description of Services
The Call Center Operation (CCO) at Motorola's SSC provides Continuously a central point of
contact for technical customer service requests. The CCO is staffed with customer support
representatives who will coordinate the appropriate service response and resources. Service
requests are tracked and monitored by Motorola from creation to close through an electronic
Case process.
1.0 Motorola has the following responsibilities:
1.1 Continuously receive technical service requests from Customer or Motorola via
telephone.
Use or disclosure of this proposal is subject to the restrictio!1s on the title page.
Motorola Confidential Proprietary
@ MOTOROLA December 2001
4
1.2 Open a Case and gather information from Customer to perform the following:
· Characterize the issue
· Determine a plan of action
· Assign and track the Case to resolution.
1.3 Dispatch a Servicer as required by standard procedures and provide necessary
Case information collected in section 2.2.
1.4 Verify with Customer that Restoration is complete or System is functional, if
required by Customer's repair verification preference as set forth in section 3.1.
If verification by Customer cannot be completed within 20 minutes of Restoration,
the Case will be closed and the Servicer will be released.
1 .5 Ensure the required personnel have access to Customer information as needed.
1.6 Escalate the Case to the appropriate party upon expiration of a Response time.
1.7 Close the Case upon receiving notification from Customer or Servicer, indicating
the Case is resolved.
1.8 Notify Customer of Case status via pager or em ail at the following Case levels as
determined in section 3.1:
· Open and Close; or
· Open, Assigned, Arrival, Deferred, Closed.
1.9 Provide periodic activity reports to Customer.
2.0 Customer has the following responsibilities:
2.1 Provide Motorola with the following pre-defined information prior to service Start
Date:
. Case notification preferences
· Repair verification preference
2.2 Call the SSC and provide the following information to the customer support
representative:
· Assigned System ID number
· Problem description and site location
· Other information as requested by Motorola to open a Case
2.3 Verify with the SSC that restoration is complete or System is functional, if
required by Customer's repair verification preference stated in section 3.1.
2.4 Complete and submit all required database and escalation procedure forms to be
entered and stored at the System Support Center prior to System Acceptance.
2.5 Submit changes in any information supplied in the Customer Support Plan to the
Customer Support Manager.
2.6 Cooperate with Motorola and perform all acts that are reasonable or necessary to
enable Motorola to provide the Dispatch Service to Customer.
Use or disclosure olthis proposal is subject to the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA December 2001
5
Statement of Work
Technical Support
1 .0 Description of Services
The Technical Support Operation at Motorola's SSC provides to Customer's technical
staff centralized remote telephone support for technical issues that require a high level of
communications systems expertise or troubleshooting on the Equipment. The Technical
Support Operation is staffed with technologists who specialize in the diagnosis and
resolution of system performance issues. Technical Support (i) shall not include software
upgrades that may be required for issue resolution; and (ii) is only available for those
system types supported and approved by Technical Support Operations.
Technical Support is applicable to the following system types: SmartZone v2.0.3 and
higher, SmartZone/OmniLink, E911, Private Data v2.0.3 and higher, and SmartNet. The
following equipment is not supported by Technical Support: Micor, DeskTrac Repeater
Model #l35sum7000; MSF 5000 that are not part of a SmartZone system, NCP, and
Darcom.
2.0 Motorola has the following responsibilities:
2.1 Provide Technical Support Operation availability for all Severity One issues
Continuously.
2.2 Respond to requests for Technical Support in accordance with the Response
times defined in Table B and Severity levels defined in Table C in Appendix 1 at
the back of this Statement of Work.
2.3 Advise caller with procedure for determining any additional requirements for
issue characterization, Restoration, or known fix for issue resolution.
2.4 Attempt remote access to system for remote diagnostics, if possible.
2.5 As needed, coordinate with the Servicer or Customer in the field until close of the
Case.
2.6 Coordinate technical resolutions with agreed upon third party vendor(s), as
needed.
2.7 Escalate support issues to Motorola engineering and product groups, if
necessary.
2.8 Provide a focal point for any Systemic issue and manage the Systemic issue to
resolution.
2.9 Escalate the Case to the appropriate party upon expiration of a Response time.
2.10 Provide remote assistance, if needed, to install an Enhancement Release
provided pursuant to the Software Subscription Agreement.
3.0 Customer has the following responsibilities:
3.1 Complete and submit all required database and escalation procedure forms to be
entered and stored at the System Support Center prior to Start Date.
3.2 Submit changes in any information supplied in the above documents to the
Customer Support Manager prior to the change taking effect.
3.3 Contact the System Support Center in order to access the Technical Support
Operation, provide name of caller, name of Customer, System ID number,
Service Agreement number, site(s) in questions, and brief description of the
problem.
3.4 Supply on-site presence when requested by System Support Center.
@ MOTOROL.A
Use or disclosure of th is proposal is subject to the restrictions on the title page.
Motorola Confidential Proprietary
December 2001
6
3.5 Validate issue resolution prior to close of the Case.
3.6 Allow Motorola remote access to the System.
3.7 Cooperate with Motorola and perform all acts that are reasonable or necessary to
enable Motorola to provide the Technical Support services to Customer.
Statement of Work
Network Monitoring Service
1,0 Description of Service
Network Monitoring Service electronically monitors specific elements of the System for
Events. When an Event is detected, it is forwarded to the Motorola System Support
Center using system specific monitoring tools. The System Support Center is staffed
with trained technologists, who acknowledge the Event, run available diagnostic routines,
and initiate an appropriate response.
Network Monitoring Service is applicable to the following system types: SmartZone,
SmartZone/OmniLink v2.0.3 and higher, E911, Private Data v2.0.3 and higher with a
WNG box, and SmartNet. The following equipment is not supported by Network
Monitoring Service: Private Data systems without a WNG box, Micor, DeskTrac
Repeater; MSF 5000 that are not part of a SmartZone system; MTR 2000; MSR 2000;
and NCP Data Base Stations.
When the Customer Support Plan is prepared or at any time thereafter during the ESS
Period, Customer may elect to "Opt-Out" of the Network Monitoring Service by notifying
Motorola in writing. Upon receipt of such notification, Motorola will not perform further
Network Monitoring Service. Customer may choose to "Opt Back In" to Network
Monitoring Service for the remainder of the current term of the applicable agreement by
notifying Motorola in writing, provided that (i) Customer is responsible for any equipment,
engineering, testing, installation and other charges required to enable Network Monitoring
Service; and (ii) Customer and Motorola execute a written change order to enable
Network Monitoring Service.
2.0 Motorola has the following responsibilities:
2.1 Recommend and coordinate installation of any needed connectivity or monitoring
equipment.
2.2 Provide dedicated 56k frame relay necessary for monitoring SmartZone,
SmartZone/ OmniLink, and Private Data system types.
2.3 Verify connections and Event monitoring prior to System Acceptance or Start
Date.
2.4 Monitor System Continuously.
2.5 Access the Customer's System to perform remote diagnostics as indicated per
Customer in section 3.6.
2.6 Create a Case when action is required.
2.7 Disable and enable System devices as needed for Servicers who go to the
Customer's site when intervention is needed.
2.8 Verify service of Event as needed.
2.9 Provide activity reports to Customer on Case history.
2.10 Provide Performance Reports for SmartZone, SmartZone OmniLink, and Private
Data system types.
Use or disclosure o(this proposal is subject to the restrictions on the title page.
Motorola Confidential Proprietary
(f!) MOTOROLA December 2001
7
3.0 Customer has to the following responsibilities:
3.1 Allow Motorola remote access Continuously to obtain System performance data.
3.2 Purchase any connectivity or monitoring equipment as determined by Motorola.
3.3 Cover any installation costs of connectivity or monitoring equipment.
3.4 Notify the System Support Center when Customer performs any activity that
impacts the System. (Activity that impacts the System may include, but is not
limited to, installing software or hardware upgrades, performing upgrades to the
network, or taking down part of the System to perform maintenance.)
3.5 Allow Servicers access to Equipment (including any connectivity or monitoring
equipment) if remote service is not possible.
3.6 Provide Motorola with pre-defined information prior to Start Date necessary to
complete Customer Support Plan
3.7 Order and maintain dedicated dial-up phone lines for telephone service for
SmartNet and E911 system types.
3.8 Cooperate with Motorola and perform all acts that are reasonable or necessary to
enable Motorola to provide the Network Monitoring Service to Customer.
Statement of Work
OnSite Infrastructure Response
1.0 Description of Service
OnSite Infrastructure Response provides for on-site technician Response as determined
by pre-defined severity levels set forth in Table C and Response times set forth in Table
A-1 in order to Restore the System.
2.0 Motorola has the following responsibilities:
2.1 If Motorola is providing Technical Support service in addition to this OnSite
Infrastructure Response service, Motorola will first respond in accordance with
the Technical Support service Statement of Work and Table 8, unless required to
respond otherwise in the Communications System Agreement or other applicable
Agreement. If, in the performance of the Technical Support responsibilities,
Motorola determines that an on-site technician is necessary, dispatch will occur
promptly after such determination is made and on-site Response will occur in
accordance with Table A-2.
2.2 If Motorola is not providing Technical Support but only providing OnSite
Infrastructure Response, Motorola will respond in accordance with this Statement
of Work and Tables A-1 and C.
2.3 Perform diagnostics on the component/Field Replacement Unit (FRU) /assembly.
2.4 Restore the System by replacing defective component/FRU/assembly.
2.5 Provide the FRU but only if the Advanced Replacement Statement of Work
applies.
2.6 Provide materials, tools, documentation, physical planning manuals, diagnostic,
and test equipment necessary to perform the service.
3.0 Customer has the following responsibilities:
Use or disclosure of this proposal is subject to the restrictiolls all the title page.
Motorola Confidential Proprietary
@ MOTOROLA December 2001
8
3.1 Establish and maintain a suitable environment for the Equipment and provide the
Servicer full, free, and safe access to the Equipment so that the Servicer may
provide services.
3.2 If the Advanced Replacement Statement of Work does not apply, supply the FRU
or assembly as needed in order for Motorola to Restore the System as set forth
in section 2.4.
3.3 Maintain and store any and all Software needed to Restore the System.
3.4 Cooperate with Motorola and perform all acts that are reasonable or necessary to
enable Motorola to provide the OnSite Infrastructure Response services to
Customer.
Statement of Work
Advanced Replacement
1 .0 Description of Services
Motorola will provide Customer with an advanced Field Replacement Unit (FRU) in
exchange for Customer's malfunctioning FRU. A malfunctioning FRU will be evaluated
and repaired by Motorola's System Support Center (SSG) and returned to the SSC FRU
inventory upon completion of repair. Non-standard configurations and Customer-
modified units are excluded from this service.
2.0 Motorola has the following responsibilities:
2.1 Maintain and provide access to an inventory of FRU, subject to availability, that
can be shipped from SSC to Customer upon request as described in section in
3.1. Notwithstanding any statement to the contrary, the SSC reserves the right to
provide to Customer a new or reconditioned FRU. The FRU will be of the same
kit and version, and will contain similar boards and chips, as the Customer's
malfunctioning FRU.
2.2 Program FRU to original operating parameters based on templates provided by
Customer. If Customer's template is not provided or is not reasonably usable, a
generic template will be used. Motorola reserves the right to upgrade the FRU at
no additional charge to Customer.
2.3 Properly package and ship FRU from the SSC FRU inventory to Customer's
address.
2.4 A FRU is sent next day air via Federal Express Priority Overnight or UPS Red
unless otherwise requested. Shipments outside of the above mentioned carrier
programs, such as NFO (next flight out), are subject to additional charges.
2.5 Motorola will pay shipping and handling during normal operating hours of Monday
through Friday 7:00am to 7:00pm CST. Shipments outside standard business
hours are subject to additional shipping and handling charges.
2.6 When sending the FRU to Customer, provide a return air bill in order for Customer
to return the malfunctioning FRU.
2.7 Evaluate and repair Customer's malfunctioning FRU and return it to the SSC FRU
inventory upon completion of repair.
3.0 Customer has the following responsibilities:
3.1 Call the SSC and request the FRU. The initial call to the SSC may be from
Servicer if Servicer is acting on Customer's behalf pursuant to the OnSite
Infrastructure Response Statement of Work.
Use or disclosure afthis proposal is subject to the restrictions on the title page.
Motorola Confidential Proprietary
(f!) MOTOROLA December 2001
9
3.2 Provide model description, model number, serial number, type of System and
firmware version, and address of site location for FRU.
3.3 Provide Customer purchase order number to secure payment for any cost as set
forth in section 2.3.1, 2.3.2. or 2.3.3.
3.4 Upon receipt of the FRU from the SSC FRU inventory, properly package
Customer's malfunctioning FRU to the SSC within 5 days for evaluation and
repair as set forth in section 2.4. Customer must send the return air bill,
referenced in section 2.3.3 back to the SSC in order to ensure proper tracking of
the returned FRU. Customer will be charged for a replacement a FRU not
properly returned.
3.5 Maintain templates of Software/applications and Firmware for reloading of the
FRU as set forth in section 2.2.
3.6 Cooperate with Motorola and perform all acts that are reasonable or necessary to
enable Motorola to provide the Advanced Replacement services to Customer.
Statement of Work
Software Subscription Agreement
1.0 Description of Service
Motorola provides most Software releases by means of a Software Subscription
Agreement (USSA"). As more thoroughly discussed in the SSA, Motorola will provide to
Customer periodic bulletins, which announce and explain available Enhancement
Releases and Core Releases for Motorola Software for use with upgrade-capable
Motorola Equipment covered by the SSA.
Non-Motorola Software (Le., Software whose copyright is owned by a party other than
Motorola) and some Motorola Software are excluded from the Software
Subscription program. Examples of excluded Motorola Software are: Software
developed or provided by a Motorola business sector other than CGISS; Radio
Service Software; mobile and host applications, message switch, and related
software (such as TxMessenger™, Premiere MDCTM, Airmobile™, and Virtual
Control Head) that are marketed by Motorola's Integrated Solutions Division of
CGISS or by Motorola's affiliated companies, Printrak International, Inc. and
Suncoast Scientific International. These excluded Software products may be
covered by a separate maintenance and support agreement.
2.0 Motorola has the following responsibilities:
2.1 Provide to Customer bulletins announcing Enhancement Releases and Core
Releases.
2.2 Provide to Customer available Enhancements Releases and Core Releases as
ordered by Customer. If Customer orders a new Enhancement Release or Core
Release, provide those Standard Features included in the release that apply to
Customer's existing System.
3.0 Customer has the following responsibilities:
3.1 Customer must contact its Motorola representative to order an available
Enhancement Release or Core Release.
3.2 Pay any charges associated with additional engineering or hardware required for
each Enhancement Release or Core Release that Customer chooses to order
Use or disclosure of this proposal is subject to the restriC/iollS O/l the ritle page.
Motorola Confidential Proprietary
(f!) MOTOROLA December 2001
10
and install. Additional engineering may be required if Customer's System has
specially developed options.
3.3 Use the Software and releases in accordance with the terms of the Motorola
software license agreement executed by Customer or Motorola's standard
software license agreement if no license was signed.
3.4 Cooperate with Motorola and perform all acts that are reasonable or necessary to
enable Motorola to provide the Software Subscription Agreement services to
Customer.
Statement of Work
Infrastructure Software Installation
1.0 Description Of Service
Infrastructure Software Installation provides the technical resources to install and activate
one (1) Enhancement Release per year.
2.0 Motorola has the following responsibilities:
2.1 Install Enhancement Releases that have been provided pursuant to a Motorola
Software Subscription Agreement.
2.2 Install additional hardware as required by the Enhancement Release.
3.0 Customer has the following responsibilities:
3.1 Purchase additional Equipment needed to implement an Enhancement Release.
3.2 Inform System users of upgrade plans and scheduled System downtime.
3.3 Cooperate with Motorola and perform all acts that are reasonable or necessary to
enable Motorola to provide the Infrastructure Software Installation services to
Customer.
Statement of Work
Software Upgrade Design
1.0 Description of Service
Software Upgrade Design includes design services for Enhancement Releases only.
Motorola will review System audit data along with an equipment list to ensure there will
be no Software incompatibilities between equipment that is not being upgraded versus
equipment which is being upgraded with an Enhancement Release. Motorola will identify
additional equipment and engineering that is required as a result of the upgrade and will
recommend a plan for installation.
2.0 Motorola has the following responsibilities:
2.1 Review Infrastructure System audit data as needed.
2.2 Identify additional System equipment needed to implement an Enhancement
Release.
2.3 Complete a proposal defining the Enhancement Release, equipment
requirements, installation plan, and impact to System users that will fulfill the
Customer's upgrade requirements.
Use or disclosure of this proposal is subject to the restrictions Oil the title page.
Motorola Confidential Proprietary
(fJ\) MOTOROLA. December 2001
\~
11
2.4 Advise Customer of probable impact to System users during the actual field
upgrade implementation.
3.0 Customer has the following responsibilities:
3.1 Contact Motorola upon receiving a bulletin to engage the appropriate Motorola
resources for an Enhancement Release or Core Release.
3.2 Cooperate with Motorola and perform all acts that are reasonable or necessary to
enable Motorola to provide Software Upgrade Design services to Customer.
Statement of Work
System Audit (only applicable if needed for Software Upgrade Design)
1.0 Description of Service
A System Audit provides the technical resources to gather System configuration
information. Depending on the specific requirements for the audit, information such as
Software versions, hardware versions, model and serial numbers, equipment distribution
and System layouVarchitecture is gathered and retained by Motorola. Motorola will
provide a copy of the audit data to Customer.
2.0 Motorola has the following responsibilities:
2.1 Determine information to be collected in the audit, which may include Software
versions, hardware versions, model and serial numbers, equipment distribution
and System layouVarchitecture.
2.2 Contact Customer to schedule a mutually acceptable date and time for the audit,
and inform Customer of scheduled System down-time in order to complete the
audit.
2.3 Service will be performed during Standard Business Day hours.
2.4 Collect System audit data.
2.5 Provide Customer a copy of the audit data collected.
2.6 Notify Customer if malfunctioning Equipment is discovered during the audit and
whether that Equipment cannot be audited due to the malfunction.
3.0 Customer has the following responsibilities:
3.1 Provide Motorola full, free, and safe access to the Equipment so that the Servicer
may collect the audit data.
3.2 If subscriber units are to be audited:
3.2.1 Provide a central location for the Servicer to receive the radio units and
collect audit data.
3.2.2 Communicate to all Customer subscriber users the audit schedule and
location to bring the units.
3.3 If Motorola is unable to collect audit data on Equipment due to either Equipment
malfunction or Equipment unavailability/access, Customer may be responsible
for additional time and travel charges for the second attempt to obtain the audit
information for that Equipment.
3.4 If travel is required beyond two (2) hours or 120 miles by vehicle from the prime
site to a remote site to deliver this service, the Customer is responsible for
incremental travel and expenses incurred.
3.5 Cooperate with Motorola and perform all acts that are reasonable or necessary to
enable Motorola to provide the System Audit services to Customer.
Use or disclosure of this proposal is subject to the restrictiolls 0/2 the title page.
Motorola Confidential Proprietary
@ MOTOROLA December 2001
12
Appendix 1
TABLE A-1 - OnSite Infrastructure Response Times
SEVERITY RESPONSE
Severity 1 Within 4 hours from receipt of notification
Severity 2 * Within 4 hours from receipt of notification*
Severity 3 * Within 24 hours from receipt of notification*
*Standard Business Day
TABLE A-2 - OnSite Infrastructure Response with Technical Support Response Times
RESPONSE
Within 1 Hour from receipt of request for Technical Support
On Site within 4 hours from time of dis atch
Within 4 Hours from receipt of request for Technical Support
On Site within 4 hours* from time of dis atch*
Within next Business Day from receipt of request for Technical Support*
On Site within 24 hours* from time of dis atch
*Standard Business Day
SEVERITY
Severity 1
Severity 2 *
Severity 3 *
TABLE B - Remote Technical Support Response Times
SEVERITY RESPONSE
Severit 1 Within 1 Hour from recei t of notification
Severit 2* Within 4 Hours from recei t of notification
Severit 3* Within next Business Da
*Standard Business Days
TABLE C -Severity Definitions
Severity Level Problem Types
Severity 1 Major system failure
33% of System down
33% of Site channels down
Site Environment Alarms (smoke, access, temp, AC Power)
Response is provided Continuously.
Severity 2 Significant System Impairment
Response is provided during Standard Business Days
Severity 3 Parts Questions
Upgrades
Intermittent problems
System problems presently being monitored
Res anse is rovided durin Standard Business Da s.
Use or disclosure of/his proposal is subjec/ /() /he res/ric/ions oil/he /i/le page.
Motorola Confidential Proprietary
([!) MOTOROLA December 2001
13
TERMS AND CONDITIONS FOR ESS
SECTION 1 SERVICE DESCRIBED
A. Motorola will provide ESS services for the Equipment in accordance with the following
standards: (i) Motorola parts or parts of equal quality that are new or are warranted as
"like new" will be used; (ii) the Equipment will be serviced at levels set forth in Motorola's
product manuals; and (iii) service procedures that are prescribed from time to time by
Motorola for its products will be followed.
B. Motorola may provide additional services ("Above-Contract Services") at Customer's
request that will be billed at Motorola's then applicable service rates.
C. Customer must maintain, and upon request by Motorola, provide a complete equipment
list indicating serial numbers, model numbers, location of Infrastructure Equipment, and
whether any Equipment is labeled intrinsically safe for use in hazardous environments.
D. Customer must immediately notify Motorola in writing when any Equipment is lost,
damaged, or stolen.
E. If Equipment cannot, in Motorola's reasonable and expert opinion, be properly or
economically serviced for any reason including excessive wear, unavailability of parts,
the state of technology, or practical feasibility, Motorola may: (i) modify the scope of
services related to such Equipment; (ii) remove such Equipment from ESS coverage; or
(Hi) increase the price to service such Equipment.
F. Customer must notify Motorola immediately of any Equipment failure.
SECTION 2
EXCLUDED SERVICES
A. ESS Services do not include the repair or replacement of Equipment that has become
defective or damaged due to misuse, abuse, accident, liquids, neglect, acts of God, or
Customer's failure to comply with all applicable industry and OSHA standards.
B. Motorola has no obligation or responsibility for any transmission medium, such as
telephone lines, computer networks, or the worldwide web, or for Equipment malfunction
caused by such transmission medium.
C. Unless specifically included in a writing executed by Motorola, Service of Equipment
does not include items that are consumed in the course of normal operation of the
Equipment, such as batteries, magnetic tapes, and computer supplies.
D. ESS Services do not include reprogramming of Equipment unless part of an
Enhancement Release or replacement.
SECTION 3 RIGHT TO SUBCONTRACT/ASSIGNMENT Motorola may assign its rights
and delegate its obligations and may subcontract any portion of Motorola's performance under
the ESS program.
SECTION 4 TIME AND PLACE OF SERVICE ESS Services will be provided at the
location specified in the ESS Statement of Work. When Motorola performs service at the
Equipment's location, Customer agrees to provide Motorola, at no charge, a non-hazardous and
secure work environment with adequate physical space, shelter, heat, air conditioning, light, and
power, and with full and free access to the Equipment. Customer will provide all information
pertaining to the hardware and software elements of any system with which the Equipment is
interfacing that enable Motorola to perform its obligations under this ESS program. Unless
Use Dr disclosl/re of this proposal is subjec//o the restrictiollS 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA December 2001
14
otherwise specified in the ESS Statement of Work, the hours of service will be 8:30 a.m. to 4:30
p.m., local time, excluding weekends and holidays. Customer will pay any charges associated
with helicopter or other unusual access requirements or expenses.
SECTION 5 WARRANTY Motorola warrants that its services under this ESS program will
be free of defects in materials and workmanship for a period of ninety (90) days from the date of
performance. MOTOROLA DISCLAIMS ALL OTHER WARRANTIES OR CONDITIONS,
EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
SECTION 6 LIMITATION OF LIABILITY Except for personal injury or death, Motorola's total
liability for any claim under the ESS program, whether such claim is based upon breach of
contract, warranty, negligence, strict liability in tort, or any other cause of action, will be limited to
the actual direct damages recoverable under applicable law but such amount shall not exceed the
greater of (a) the annual price of the affected Service, or (b) $50,000. IN NO EVENT WILL
MOTOROLA BE LIABLE FOR ANY COMMERCIAL LOSS; INCONVENIENCE; LOSS OF USE,
TIME, DATA, GOODWILL, REVENUES, PROFITS OR SAVINGS; OR OTHER SPECIAL,
INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES. If a claim is made for breach of
the warranty in Section 5 above, Motorola at its option may re-perform the affected service
instead of paying damages. This Limitation of Liability will survive the expiration or termination of
Motorola's duty to provide services.
@ MOTOROLA
Use or disclosure (~fthis proposal is subject to the restrictiom Oil the title page.
Motorola Confidential Proprietary
December 2001
IS
EXHIBIT D-2
MOTOROLA CANADA LIMITED
FIVE (5) YEAR EXTENDED WARRANTY
(STANDARD)
This Factory Depot Service plan is available in addition to the Standard Commercial Warranty for certain Motorola manufactured
subscriber products for a consideration over and above the price of the product paid by the original purchaser or lessee and is in
effect from the date the standard commercial warranty expires. This plan is available for the purchase at the time of equipment
order.
All covered subscriber equipment requiring service must be sent to a designated Motorola Factory Depot only. All inbound
shipping or transportation charges to Motorola must be paid by the purchaser. Motorola will pay for outbound/return shipping
via Motorola's normal shipping methods.
THIS PLAN PROVIDES SUBSCRIBER PRODUCT INTERNAL COMPONENT REPAIR COVERAGE FOR FOUR YEARS
BEYOND THE STANDARD COMMERCIAL WARRANTY (WITH THE EXCEPTION OF BATTERIES WHICH ARE
NOT COVERED BY THIS PLAN). THIS PLAN ALSO EXCLUDES REPAIR COVERAGE OF ANY SUBSCRIBER
PRODUCT ACCESSORIES; SUCH AS BUT NOT LIMITED TO ANTENNAE, MICROPHONES, MICROPHONE CORDS,
CARRY CASES AND BELT CLIPS. THERE ARE NO WARRANTIES EXPRESS OR IMPLIED REGARDING THE
FACTORY DEPOT SERVICE PLAN, INCLUDING, WITHOUT LIMITATION THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
If a product covered by the factory depot service plan fails to perform in accordance with the published specifications for that
product in effect at the time of purchase, Motorola, at its option, will either repair or replace the Product(s) at an authorized
Motorola Factory Service Depot designated by Motorola and such action on the part of Motorola shall be the full extent of
Motorola's liability under the factory depot service plan. Repair, at Motorola's option, may include the replacement of parts or
boards with functionally equivalent reconditioned or new parts or boards. Replaced parts, boards or Products, are covered for the
remaining time period of this plan. All replaced parts, boards or Products shall become the property of Motorola.
LIMITATION OF LIABILITY: EXCEPT FOR PERSONAL INJURY, MOTOROLA'S TOTAL LIABILITY ARISING OUT
OF OR RELATED TO THIS PLAN WHETHER FOR BREACH OF CONTRACT, WARRANTY, OR OTHERWISE, IS
LIMITED TO THE PRICE OF THE PARTICULAR PRODUCTS COVERED BY THIS PLAN OR SERVICES PERFORMED
HEREUNDER WITH RESPECT TO WHICH LOSSES OR DAMAGES ARE CLAIMED. CUSTOMER'S SOLE REMEDY IS
TO REQUEST MOTOROLA AT MOTOROLA'S option TO EITHER REPAIR OR REPLACE PRODUCT(S) COVERED BY
THE FACTORY DEPOT SERVICE PLAN. IN NO EVENT WHETHER FOR BREACH OF CONTRACT, WARRANTY, OR
OTHERWISE, WILL MOTOROLA BE LIABLE FOR INCIDENTAL, SPECIAL OR CONSEQUENTIAL DAMAGES TO THE
FULL EXTENT SUCH MAY BE DISCLAIMED BY LAW INCLUDING, BUT NOT LIMITED TO. LOSS OF PROFIT OR
REVENUE, LOSS OF USE OF THE PRODUCTS OR ANY ASSOCIATED EQUIPMENT, LOSS OF DATA, COST OF
CAPITAL, COST OF SUBSTITUTE PRODUCT(S), FACILITIES OR SERVICES, OR DOWN TIME COSTS OR FOR ANY
CLAIM AGAINST CUSTOMER BY ANY PARTY. NO ACTION SHALL BE BROUGHT FOR ANY BREACH OF THIS
PLAN MORE THAN ONE (1) YEAR AFTER THE ACCRUAL OF SUCH CAUSE OF ACTION.
This plan does not cover defects, malfunctions, performance failures or damages to the unit resulting from:
a) Use in other than its normal or customary manner.
b) Misuse, Vandalism, Accident or Neglect; or
c) Improper disassembly, testing, operation, maintenance, installation, modification, adjustment or repair.
Also not covered by this plan is the radio frequency coverage or range over which the Product(s) will transmit and receive signals.
THIS EXTENDED WARRANTY APPLIES ONLY WITHIN CANADA.
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
a talk prohibit tone. Transmission Trunking is a System wide
setting.
Message Trunking Operation Talkgroups can be programmed for message trunking operation.
In this mode, the channel assigned for the talkgroup call will
include an adjustable "hang time" to allow users to respond on
the same channel, thus avoiding the need to re-initiate a channel
request sequence. Message Trunking is a System wide setting.
Continuous Assignment Updating A radio that has been turned off or out of range will
automatically re-acquire the control channel and join any active
calls that are in its talkgroup selection.
Radio Registration A radio will register onto the trunking system upon powering-
on, returning from out-of-range, or switching talkgroup
selection.
Push-To-Talk ID (PTT ID) A radio will send its individual ID to the system at the
beginning of each transmission.
This applies to both transmission and message trunking
operation.
Call Queuing If the system is busy, any incoming call requests will be queued
according to a defined priority level. The queue will store at
least 16 call requests.
Call-Back When a channel is made available to a queued call request, the
requesting radio will be automatically directed to the available
channel and notified of this via an audible alert.
Call-Back Priorities or The order in which queued calls are serviced will depend on the
System Access Priority Levels priority level of the call requester (radio unit) or talkgroup.
Calls of the same priority level will be handled on a First-In-
First-Out basis. Calls for the same talkgroup will be treated as a
single request for assignment at the level of the highest priority
of the caller in the group, and the highest priority caller will be
treated as the first caller. The system will support up to 8
individual radio unit or talkgroup priority levels, Emergency
being the highest and 8 being the lowest.
Recent-User Priority When queued call requests are serviced, recent users and users
Use or disclosure (!f this proposal is subject to the restrictiolls all the title page.
Motorola Confidential Proprietary
@ MOTOROLA. February 2002
?O
_0
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
in the same talkgroup will be treated with higher priority than
new call requests from users at the same priority level. This will
avoid fragmentation of conversations within a message.
Dispatcher Pre-empt
(Console Priority)
Dispatchers will be able to pre-empt an ongoing call on a
selected talkgroup and make an immediate transmission to that
talkgroup, while continuing to monitor the radio that is
transmitting.
Types of Calls:
The following types of calls will be supported by the
infrastructure.
Multiple-talkgroup Call
This is the primary level of organization for communications in
a trunked radio system. Radio users assigned to a given
talkgroup will be capable of "talkgroup calls" and will under
normal operation, only be able to communicate with other
members of the same talkgroup. This provides the effect of a
private channel down to the talkgroup level.
Three approaches will be possible:
. Console Patch
Talkgroup Call
. Announcement Talkgroup
. Multi-Select
Console patch utilizes the "talkgroup merge" method by which
different talkgroups are merged into a temporary "super"
talkgroup. As implied by the name, a console patch (or multi-
select) is a dispatcher controlled function.
The Announcement Talkgroup approach is implemented
through radio programming. Using this method, different
talkgroups are affiliated to a common Announcement
Talkgroup, and radio users on different talkgroups are able to
communicate with each other.
Multi-Select is also a dispatcher function. It will provide a
temporary grouping of talkgroups for a console transmission.
The talkgroups will be "merged" into a "super group" for the
Use or disclosure of th is proposal is subject to the restrictiollS 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
29
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
duration of the console message. Unlike a console patch, users
in Multi-Select groupings will not be able to talk to each other.
Individual Call An individual radio user or dispatcher will be able to initiate a
Private Conversation calI to another radio user across talkgroup
boundaries. No other talkgroup members will be able to
monitor the private conversation.
Call Alert (Selective Alert) An individual radio user or dispatcher will be able to send a
page to another radio unit. The target radio unit will generate
alert tones (which are independent of the volume setting on the
radio) and display the CalI Alert sender's ID.
Dispatcher Alert Tones A dispatcher will be able to send one of three distinct tones from
the console to the members of the selected talkgroup. The alert
tone will be heard on the receiving radios, and is dependent on
the volume setting of the radio.
10.0 GOLD ELITE CONSOLE UPGRADE AND
REMOTE DISPATCH CENTRE
The CentraCom Gold Series Console System currently consists of three (3) local Elite dispatch
operator positions, three (3) fixed mobiles and one (1) Central Electronics Bank (CEB) cabinet.
The console operator positions and the CEB at Oshawa Fire Hall #1 will be upgraded.
The remote dispatch centre will include two (2) more operator positions to be remotely connected
to the Communications Centre in Oshawa.
An additional computer is required to act as Server for the system (the current Server can only
perform as a client as well as a server for up to 3 total clients) and has been included.
The required T 1 and leased line connections for the Remote Dispatch Comm Centre, are found in
the Site Requirements Plan.
10.1 Gold Series Central Electronics Bank (CEB)
The CEB at Oshawa Fire Hall #1 will be used to interface the console operator positions to the
trunked radio network. The upgrade required to the CEB will be to add four (4) Trunked Base
Use or disclosure of'this proposal is subject to the restrictiollS 011 the title page.
Motorola Confidential Proprietary
([1;) MOTOROLA February 2002
30
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Interface Modules (TBIMs), five (5) Base Interface Modules (BIMs), two (2) Console Operator
Interface Modules (CalM), eight (8) Auxiliary Input/Output (AUXIlO) boards, two (2) Remote
Operator Console Interface (ROCI) boards, two (2) Trunked Input/Output Multiplexed Interface
(TIMI) boards and one (1) Logging Recorder Interface (LORI) board. As well, software/firmware
refresh on existing boards will be required. The increase in boards will also require two additional
. cardcages, a power supply, batteries, and a cabinet. The following is a brief description of the
Central Electronics Bank (CEB) modules.
10. 1. 1 Trunking Base Interface Module (TBIM)
The Trunking Base Interface Module (TBIM) provides the capability to operate a remotely
controlled trunking base station. Four (4) additional TBIMs (based on the increased number of
trunking channels) will be used to provide dispatch trunking communications for the System.
10. 1.2 Base Interface Module (BIM)
The Base Interface Module (BIM) provides the capability to operate a remotely controlled
conventional base station. One additional (BIM) will be used to provide tone remote control
operation of the additional conventional channel that is currently in use but not apart of the
Console system. The OFM and Regional channels are already connected to the console. Another
four (4) BIMs will be used to connect to the paging stations in Whitby, Pickering and Clarington.
The BIMs will convert digital audio from the TDM bus in the CEB to an analog signal for
transmission to the remote base station. From the remote base station to the console operator
position, the BIMs will convert the analog audio to digital form.
The Base Interface Modules provide logging outputs for conventional (non-trunking) channels.
These will also be standard 2-wire, 600 Ohm audio outputs.
10.1.3 Logging Recorder Interface (LORI)
The upgrade will provide up to eight (8) additional track logging recorder interfaces. The logging
interface will "de-trunk" the audio from talkgroup calls to ensure that the talkgroup audio will
always be recorded to the same track on a logging recorder. The CEB logging recorder interface
will remove digitized talkgroup audio from the TDM bus and convert it back to analog audio for
logging recorder use. It will also provide the physical 2-wire, 600 Ohm audio output connections
for the logging recorder, on 66-type punch blocks. The punch blocks will be located in the CEB
equipment room.
Use or disclosure (){this proposal is subject ro the restrictions 011 the tirle page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
31
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
10. 1.4 Trunked Input/Output Multiplexed Interface (TIMI)
Two (2) additional TIMls will be added to the CEB. The TIMI interface will provide the
connection to the Redundant Prime Site controller from the CEB.
10. 1.5 Remote Operator Console Interface (ROCI)
The ROCI provides the remote operator console interface to the CEB. It contains line drivers to
drive speaker audio across a phone line to the dispatch position and a line receiver to receive
microphone audio from the dispatch position.
10. 1.6 Console Operator Interface Module (COIM)
A Console Operator Interface Module (COIM) is required for each dispatch position in the
system. The COIM provides the link to a dispatcher position from the CEB.
10.1.7 Auxiliary Input/Output Module (AUX I/O)
Eight (8) AUX I/O boards will be installed. The AUX I/O provides the capability to operate the
Low Capacity MOSCAD-L Fire Hall Alerting System. For more information on the MOSCAD
Fire Hall Alerting System see the MOSCAD Fire Hall Alerting System Functional Specification.
10. 1.8 Power Supply
A new continuous duty power supply will provide the required regulated DC voltage levels to the
CEB. A regulator circuit will incorporate over-voltage and short circuit protection to prevent
damage to the console equipment. The CEB will be supplied with a dual power supply for
redundancy and load sharing purposes.
The old power supplies in the existing CEB Cabinet will be replaced with the same style power
supply that will be installed in the new CEB Cabinet.
10. 1.9 Battery Backup
The battery backup that is required for the new CEB will be supplied. Furthermore, the same type
of batteries that will be supplied in the new CEB cabinet will be supplied to replace the old CEB
batteries.
Use or disclosure oft/lis proposal is subject to the restrictions 0/1 the title page.
Motorola Confidential Proprietary
(jJ;i MOTOROLA February 2002
'-../
~!
J_
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
10.2 CEB Configuration
Table 10-1 summarizes the new configurations of the CEB.
Table 10.1 CEB
Module Quantity
Operator Position Interface (COIM) 5 (3 existing)
Remote Operator Interface (ROCI) 2
Conventional Channel Interface (BIM) 7 (2 existing)
Trunking Channel Interface (TBIM) 9 (5 existing)
Auxiliary Inputs/Outputs 16 (16 existing)
Trunked Input/Output Interface Module (TIMI) 4 (2 existing)
Logging Recorder Interface (tracks) 16 (8 existing)
10.3 Console Operator Positions
The existing console operator positions will continue to provide the functionality associated with
a standard Gold Elite Operator position but will be upgraded to windows 2000 platform.
Below is a list of the existing and additional dispatch equipment, which will be located in the
communications centres.
Use or disc/osure orthis proposal is subject to the restrictiolls 0/1 the title page.
Motorola Confidential Proprietary
@ MOTOROLA. February 2002
~ -,
.).)
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Table 10-2 Dispatch Equipment
Existing CentraCom Gold Series Console Electronics Bank (CEB)
Additional CentraCom Gold Series CEB Cabinet
Existing Dispatch Console Positions (Gold Series Elite)
Additional Remote Dispatch Console Positions (Gold Series Elite)
Existing Console Fixed Mobile Radios (inc!. Antennas and RF cable)
Additional Remote Console Fixed Mobile Radios (inc!. Antennas and RF cable)
1
3
2
3
2
New Server
10.4 Technical Specifications
The technical specifications of the console system equipment are summarized in Table 10-3.
Table 10-3 Console System Technical Specifications
General Specifications
Operator Positions Desk top Elite based
Power Requirements 120 V AC :t 10%, 60 Hz nominal
Current Drain 1.0 A @ 120 VAC
Power Backup Existing Building UPS
Operator Audio Interface
Speakers Select and Unselect with independent volume control
Mic Sensitivity -65 dBm for + 11 dBm line output
Mic Input Range -65 to -35 dBm
Metering VU bar type meter
CEB Base Station Interface
Input Level o to -13 dBm, adjustable
Input Impedance Selectable, 600 Ohms or 10 kOhms
Output Level + 11 dBm maximum into 600 Ohms
Output Impedance Selectable, 600 Ohms or 10 kOhms
Frequency Response + 1, -3 dB, 300 to 3200 Hz, ref. 1000 Hz
Harmonic Distortion Less than 2% @ maximum output
Hum and Noise 50 dB below +11 dBm output
Use or disclosure (!lrhls proposal Is subjecrlO rile resrrlcrlons onrhe rlrle page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
34
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
11.0 TRUNKING SYSTEM PERFORMANCE
11.1 System Access
The following performance specification assumes that: 1) a channel is immediately available to
service the call request, 2) the subscriber unit is in a good signal strength area, and 3) the delays
introduced by customer provided system infrastructure links do not exceed the specification
provided by Motorola for T1 circuits.
. The nominal, elapsed time from a subscriber unit or console PTT to a voice channel
assignment (channel grant), will be 500 milliseconds.
11.2 Simulcast Optimization Parameters
In a simulcast system the primary concern is the audio quality in the coverage overlap areas. The
potential for simulcast distortion exists if a mobile or portable radio receives signals of
approximately equal amplitude from two or more transmitter sites. The field radio can
experience audio degradation due to the lack of PM capture (where one of the received signals is
dominant) if the arriving signals are out of phase (arrive at different times). To minimize the
effects of simulcast audio distortion in any non-capture, coverage overlap areas, three types of
system equalization will be utilized in the Trunked Radio System: 1) equalization of transmitter
carrier frequencies, 2) equalization of transmitter modulation levels, and 3) equalization of all
time delays in the transmitter audio paths. These three parameters will be accurately controlled to
within very close tolerances, in order to minimize audio degradation.
11.2. 1 Transmitter Carrier Frequencies
Through the use of the Rubidium Frequency Standard, the repeater carrier frequencies will be set
and maintained to within :t 0.1 Hz.
11.2.2 Amplitude Adjustment
The transmit audio levels of each simulcast channel will be adjusted to within :to. 1 dB.
Modulation (deviation) level adjustments for each channel will be determined via the test
equipment at the Prime Site, and these values will be stored in the Remote Site DSM II channel
bank cards.
Use or disclosure of this proposal is subject to the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
35
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
11.2.3 Phase Delay
To minimize the effects of simulcast audio distortion in coverage overlap areas, all time delays in
the transmitter audio paths will be precisely controlled. The launch times of simulcast analog or
digital signals, from each transmit site, will be equalized to within :1:3 microseconds.
The process employed by the system to equalize analog simulcast signal time delays is described
below.
At the Prime Site, a 1 PPS GPS derived signal is encoded by the DSM II into the outbound data
stream, along with the digitized audio to be simulcast. At the Remote Site, the receiving DSM II
"looks" for the incoming marker, as well as monitoring its locally generated 1 PPS signal. When
the 1 PPS signal is received, a pre-set down counter begins to decrement. When the incoming
marker arrives, the down counter is stopped, and its remaining value yields the magnitude of
delay (buffer) that must be inserted into the incoming audio slot. For example, ifthe pre-loaded
value in the down counter is 10 ms., and the propagation time to the Remote Site is 7 ms., the
Remote Site's down counter would begin counting down from 10 IDS. (started by locall PPS
signal) and would stop 7 ms. later when the incoming marker is received. This will result in 3
ms. worth of delay buffering being added to the incoming audio slot. The same process repeated
at each Remote Site results in the simulcast signal (from the Prime Site) being launched at the
same time from each of the system Remote Sites. The process results in a simulcast system that
will optimize itself, with respect to time delays, "on-the-fly" (updated every second).
12.0 TRUNKING SYSTEM FAILURE OPERATION
12.1 System Redundancy and Reliability
The Trunked Radio System, by virtue of the inherent reliability of the infrastructure equipment,
and the various levels of redundancy incorporated in the system design, will exhibit a very high
level of availability. The major redundancy and backup features of the system are summarized
below.
12. 1. 1 Redundant Prime Site Controller
The trunking system includes a hot standby redundant Prime Site Controller (MTC3600). The
standby controller remains idle, until a controller failure occurs. The TBAR switch automatically
Use or disclosure ofrhis proposal is subject to the resrricrio/1s Oil rhe rirle page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
36
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
changes the controller operations over to the idle controller and deactivates the active controller.
This allows the primary controller to be serviced without system downtime or failsoft mode.
12. 1.2 Redundant Trunking Control Channels
The trunking system will include three (3) redundant control channels. If the active control
channel fails at a Remote Site, one of the three alternate control channels is automatically
assigned as the new active control channel system-wide.
12. 1.3 Backup Power
A UPS has been included for the Prime Site. Each infrastructure site in the Trunked Radio
System will be equipped with Emergency Backup batteries for the Quantars. It is assumed the
Fire Departments of Durham Region will provide a UPS for the remaining equipment at the
remote sites and the dispatch communication centres.
12.2 System Diagnostics and Alarms
The Trunked Radio System will provide an extensive range of diagnostics, alerts and alarms,
through the existing System Manager Terminal. Below is a list of some typical system
alerts/alarms, which are available.
1. Remote site #n in failsoft due to Remote Site Controller malfunction
2. Remote site #n in failsoft due to IRE malfunction
3. Remote site #n in failsoft due to no Rill for control channel
4. Remote site #n in failsoft due to no wide area Till available
5. Remote site #n, transmit path to and through repeater #x malfunctioning
6. Remote site #n, transmit path to and through repeater #x malfunctioning (due to low power
or high reflected power)
7. Remote site #n, receive path to and through repeater #x malfunctioning (due to illegal carrier
received)
Use ordisc/osllre of this proposal is subject to the restrietiollS Oil the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
37
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
12.3 Failure Scenarios
The Trunked Radio System's normal mode of operation will be with the trunked radio
infrastructure fully operational. Wide area trunking with full system coverage will be available
for dispatchers and field personnel, and all user communications will be conducted through the
trunked radio system and its talkgroup structure. Although the system includes several levels of
redundancy, failures may occur which could reduce the functionality of the trunking system for
the duration of the failure condition. Some of these potential failure modes and their effects are
described in the following sections. The following failure scenarios assume that the trunked radio
system is operating with no other equipment failures.
12.3. 1 Prime Simulcast Controller Failure
Failure:
The Prime Simulcast Controller fails.
Result:
The Redundant Prime Simulcast Controller will take over.
Failure:
The Redundant Prime Simulcast Controller and the Prime Simulcast Controller
fail.
Result:
The system will revert to a wide area failsoft mode of operation (conventional
simulcast system operation with receiver voting and transmit audio equalization).
Full system coverage will be preserved. Users will be steered to pre-programmed
repeater channels based on talkgroup selection, and will be given a visual (model
WIll) and audible indication of the failsoft condition.
Use or disclosllre of this proposal is sllbjectlo the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
38
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
12.3.2 Console Operator Position Failure
Failure:
A single console operator position or its CEB Interface fails.
Result:
The operator position will be disabled, but general system operation or the
remaining console operator positions are not affected.
12.3.3 Console System CEB Failure
Failure:
The CEB fails.
Result:
The console operator positions will be "disconnected" from the trunking system.
The system will continue to operate in wide area (simulcast) trunking mode, and
dispatchers may continue to access the trunking system over-the-air via the
existing backup fixed mobile radios.
12.3.4 Voting System Failure
Failure:
The voting comparator for a single channel fails.
Result:
The comparator for the affected channel will not process audio. A call in progress
at the time of the failure will be interrupted. However normal wide area
(simulcast) trunking system operation will continue with the remaining channels.
Use or disclosure qfthis proposal is subject to the resTrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROL.A February 2002
39
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
12.3.5 Analog Audio Distribution Failure
F ailllre:
A component (USCI or DSM II) for a single channel in the analog simulcast audio
distribution network fails.
Result:
The affected channel will be disabled and any active call on this channel will be
interrupted. Normal wide area (simulcast) trunking system operation will continue
with the remaining channels.
12.3.6 Remote Site Controller Failure
F ailllre:
A Remote Site Controller fails.
Result:
The system will continue to operate in wide area (simulcast) trunking mode
without the failed remote site. System users may notice reduced coverage in the
area of the failed remote site, but otherwise there will be no loss in system
functionality.
12.3.7 Control Channel Failures
Failure:
A single control channel repeater fails at a Remote Site.
Result:
The affected control channel is removed from service at all remote sites, and
another channel is assigned for control channel duty. General system operation is
not affected.
Use or disclosure oft/zis proposal is subject 10 the restrictiollS ol1t/ze title page.
Motorola Confidential Proprietary
(iJ\) MOTOROLA. February 2002
-.--../
40
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Failure:
A different control channel repeater fails at four Remote Sites.
Result:
The system will revert to a wide area failsoft mode of operation due to the lack of a
common, functional control channel. This type of failure is very unlikely to occur,
since the system will be equipped with four control channels. Should such a
failure occur, it would be possible to disable, on the Prime Site Controller, one of
the remote sites with a failed control channel repeater. This will allow the system
to regain a control channel, and continue wide area trunking without the manually
disabled remote site.
Failure:
All control channel repeaters fail at the same Remote Site.
Result:
The affected remote site is removed from service, or idled. Any active calls on one
of the control capable channels will be interrupted however general system
operation is not affected. Users may experience reduced coverage in the area of
the failed site. Note: this failure reaction assumes that there are no failed control
channel repeaters at any other remote site.
12.3.8 Voice Channel Failure
Failure:
A voice channel repeater fails at a Remote Site.
Result:
The affected voice channel is removed from service at all remote sites. Any active
calls on the failed repeater channel will be interrupted however general system
operation is not affected. If several voice channels are disabled, users may
experience more "busies".
Use or disclosure oIt/lis proposal is subject to the restrictions on the title page.
Motorola Confidential Proprietary
@ MOTOROLA. February 2002
41
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
12.3.9 T1 Network Failures
Failure:
All T 1 links to the Prime site fail.
Result:
The system will revert to single site trunking from the co-located transmit/receive
remote site at the Prime site.
Failure:
One Tllink to a remote site fails.
Result:
The system will continue to operate in wide area (simulcast) trunking mode
without the affected remote site. All active calls will be interrupted however
general system operation will not be affected. System users may notice reduced
coverage in the area of the failed remote site.
13.0 SYSTEM COVERAGE
13.1 RF Coverage Design
The Trunked Radio System has been designed to provide portable-based radio coverage within
Durham Region as per the customer specified requirements. Portable receive operation is
assumed to be chest level. Refer to the Coverage Design and Verification Methodology for a
detailed description of the radio coverage performance to be delivered and verified by Motorola.
The coverage reliability and audio performance, which will be provided by the system, is based
on the radio sites described in Table 13-1. Coverage reliability predictions generated by
Motorola's propagation prediction tool, "Mozaik", have been based on the availability of these
radio sites at the indicated coordinates. It is important to note that, with the exception of Oshawa,
these sites have been selected for location only. Motorola does not provide any assurance that
these sites will be available for installing equipment or mounting antennas.
Use or disclosure of th is proposal is subject to the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
42
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Table 13-1 - System Radio Sites
Site # Site Name Type Coordinates Antenna
Lat & Long Hei~ht (ft)
1 Oshawa City Hall Transmit! 43 53 45 N 160
Receive 78 51 57 W
2 Pickering Transmit! 43 55 04 N 380
Receive 79 06 44 W (assumed)
3 Whitby Transmit! 43 55 00 N 140
Receive 78 57 24 N
4 Bowmanville Transmit! 43 54 55 N 150
Receive 78 41 14 W
5 Orono Transmit! 44 00 57 N 160
Receive 78 34 08 W (assumed)
14.0 SYSTEM OPTIMIZATION AND MAINTENANCE
EQUIPMENT
14.1 Test Equipment
The Trunked Radio System will include an 800 MHz Test Radio (for receiving signals from
remote transmit sites) for the optimization of the simulcast system.
14.2 Spares
Although a detailed analysis was not performed to determine the most prudent type and quantity
of spares, the following items are optional and are a compliment of spares for essential system
equipment:
. Prime Controller Console Interface Spares
. USCI Spare
. GPS 5Mhz and IPPS Spare
<II Channel Bank Spares
<II Quantar Spares
@ CBB Power Supply
Use or disclosure ol This proposal is subject 10 the restrictions Oil the tiTle page.
Motorola Confidential Proprietary
@ MOTOR01.A. February 2002
43
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
. CEB Trunking Spares
. Spare COIM
. Gold Elite OP Spares
Spares are required to ensure that the reliability objectives are met for the system, however they
have not been included at this time.
14.3 Redundancy
The following equipment is included in the equipment list for redundancy:
. Redundant Prime Site MTC3600 Controller
· Redundant Power Supply, CPU board and dual Tl Wan for Master Channel Bank and
Sub-Channel banks at Prime Site
The redundant equipment is required to ensure that the system remains functioning at a high
reliability.
14.4 Remote Site Channel Bank Data Acquisition
The Trunked Radio System will include the capability to access and configure the remote site
channel banks from the Prime Site equipment room, via the Tl network. A laptop PC with
terminal emulator software, such as Procomm, will be required for this purpose. Motorola has
not supplied the PC.
15.0 MOBILE SUBSCRIBER EQUIPMENT
15.1 MCS2000 Mobile
This radio will be used by The Fire Departments of Durham Region with exception to Oshawa.
The radio model will be an MCS2000 Model I Remote Mount. Oshawa Fire will continue to use
their current model of mobiles.
Use or disclosure of this proposal is mbject to the restrictiolls oil/he title page.
Motorola Confidential Proprietary
@ MO'TOROLA February 2002
44
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Table 15-1 lists the functional features provided in the MCS2000 Model I radio. For a detailed
explanation of the features listed below, please refer to the appropriate section of the user manual
provided with the radio. Note also that, the actual deployed functionality is subject to overall
system, as well as individual subscriber configuration.
Table 15-2 lists the accessories included with this radio model.
Table 15-3 lists the options available, but not included, with this radio model.
Table 15-1 MCS2000 I Mobile Features
MCS2000 I Mobile Feature Description
Channel/Talkgroup capacity 48
Conventional channels Included in 48 channel/talkgroup capacity
Dual mode Operation in trunking or conventional modes is user
selectable
Failsoft operation Radio gives indication of system controller failure and
switches to a default channel
Programmable EEPROM Radio features and parameters are field modifiable and
stored in EEPROM
Adjustable time-out timer Radio has adjustable timer limiting continuous
activation of PTT button: 60 sec maximum.
Scan lists 20
Scan list, # of talkgroups/channels per list 10
Priority scan A maximum of two (2) channels in a trunking
talkgroup scan list can be designated as priority
talkgroups.
PTT -ID Radio sends its unique ID on each PIT
Emergency Pressing emergency button sends in emergency
message to console if radio is programmed for
emergency.
On/Off/Volume control switch Rotary type
Power On and Tx indications Front panel supplies indication
Channel/Talkgroup selector Rocker switch is used to select desired mode
Use or disclosure of this proposal is subject to the restrictiolls (}Il the title page.
Motorola Confidential Proprietary
@ MOTOROLA. February 2002
4S
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
MCS2000 I Mobile Feature Description
Out of range indicator Visual and/or auditory signal when radio cannot locate
control channel
System busy indicator Audio tone on PTT when no voice channel is available
Call alert Receive, send from pre-programmed list
Call alert lists 1
Call alert list, # IDs per list 10
Private Call Receive, send from pre-programmed list
Private Call lists 1
Private Call list, # IDs per list 10
Alphanumeric display Talkgroup/channel aliases and operational messages
displayed on an 8 character display
Preset squelch control EEPROM parameter to determine signal level required
to unmute speaker
Trunking, conventional, and simplex mode select Single rocker switch used for scrolling through all
channels and talkgroups
Automatic talkgroup select on power-up Radio automatically selects the last previously selected
talkgroup/channel
Automatic retry Radio automatically sends retries on a PTT until an
acknowledgment is received or the number of retries
has expired
Speaker 7.5W external speaker with 8" of cable is included
Remote mount Adds 17" control cable, 22" power cable, control head
back plate, radio front plate, and standard mounting
hard ware
Table 15-2 MCS2000 I Mobile Accessories
M CS2000 I
Ignition sense cable
Power up or down radio when vehicle is turned on or
off
Table 15-3 MCS2000 I Mobile Options
I MCS2000 I I Option Description
Use or disclosure orthis proposal is subject to the restrictions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
46
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
M CS2000 I Option Description
Dash mounted Radio comes with standard mounting hardware
required for dash mount installation
Dual Control Head Allows for remote operation via two control heads
with Model II or III MCS2000 onlv.
15.2 Optional Fire Hall Fixed Mobiles
The Fire Departments of Durham Region may purchase a MCS2000 model I, II or III supplied in
the control station configuration for communications at each Fire Hall.
Table 15-4 lists the accessories included with this radio model.
Table 15-4 Fire Hall Fixed Mobile Accessories
Fire Fixed Mobile Accessorv DescriDtion
Control Station Operation Adds a base tray, power supply, desk microphone, and
10" power cable.
Speaker Included in base trav
Battery backup power supply A battery/charger combination sufficient to run the
radio for 8 hrs at 25 Watt 5/5/90 will be provided.
Automatic battery reverting is provided during AC
power failures.
16.0 PORTABLE SUBSCRIBER EQUIPMENT
16.1 XTS3000 Portable
The basic analog portable radio used by The Fire Departments of Durham Region is the XTS3000
Model II. Table 16-1 lists the functional features provided in this radio model. For a detailed
explanation of the features listed below, please refer to the appropriate section of the user manual
provided with the radio. Note also that, the actual deployed functionality is subject to overall
system, as well as individual subscriber configuration.
Table 16-2 lists the accessories included with this radio model.
Use or disclosure olthis proposal is subject to the restrictions on the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
47
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Table 16-1 XTS3000 Portable Features
XTS3000 Portable Feature Description
Channel/Talkgroup capacity 48
Conventional channels Included in channelltalkgroup capacity
Dual mode Operation in trunking or conventional modes is user
selectable
Failsoft operation Radio gives indication of system controller failure and
switches to a default conventional channel
External reprogramming connector Weather sealed universal connector on side
Programmable EEPROM Radio personalities are field modifiable and stored in
EEPROM
Scan Radio has channel and talkgroup scan capability
Priority scan A channel in a trunking talkgroup scan list can be
designated as a priority talkgroup.
PTT - ID Radio sends its unique ID on each PTT
On/Off/ Volume control switch Rotary type, top mounted
Emergency Pressing emergency button sends in emergency
message to console if programmed in the radio.
Power On and TX indications Top mounted indication
ChannellTalkgroup selector 16 position rotary knob and 3 position toggle switch
are used to select desired mode.
Out of range indicator Auditory signal when radio cannot locate control
channel
Battery low alert Indication that battery charge is low
System busy indicator Audio tone on PTT push when no voice channel is
available
Call alert Receive only
Private Call Receive only
Alphanumeric display Talkgroup/channel aliases and operational messages
displayed on a 4line x 12 character front-mounted
display
Selective Call Decode
Selective Radio Inhibit Decode
Use or disclosure orthis proposal is subject to the restrictiolls 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA. February 2002
48
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
XTS3000 Portable
Trunking, conventional, and simplex mode select
Feature Descri tion
Rotary and toggle switch used for scrolling through all
channels and talkgroups
Automatic talkgroup select on power-up
Radio automatically selects the last previously selected
talk rou Ichannel
Submersible
Ruggedized
Safety Yellow Housina
Adjustable time-out timer
Yellow housina increases visibility of the radio
Radio has adjustable timer limiting continuous
activation ofPTT button
Table 16-2 XTS3000 Portable Accessories
XTS3000 Portable
Case accommodates ultra-hi
Nylon Carr Case
T -Stra
Included with case
antenna
7" flex antenna
Multi-unit enhanced desktop charger
(wall mount kit available)
Charges 6 batteries in 1 hr
17.0 OPTIONAL VEHICULAR REPEATER
17.1 Purpose
The purpose of this section is to describe the function and features of the optional vehicular
repeater.
17.2 Overview
The vehicular repeater is a Futurecom SGI Mobexcom II Vehicular Repeater designed to operate
in cross-band operation. It is interfaced to and works with the 800 MHz MCS2000 Mobile Radio.
The Futurecom Vehicular Repeater provides extended portable radio coverage. Three specific
modes of operation can be selected:
Use or disclosure oftltis proposal is subject to the restrictiolls Oil the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
49
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
Mobile Mode - The Mobile mode of operation is selected when repeater functions are not
desired. The vehicular repeater is completely disabled and the mobile radio system operates as if
the repeater was not there.
Local Mode - The local mode of operation is selected when interfacing to the trunked system is
not required. Full communications between the vehicular repeater and nearby portables are
achieved. The MCS2000 does not retransmit the communications to the trunking system (or
dispatch). When the mobile operator presses the Push-to-Talk button, only the vehicular repeater
transmits.
System Repeat Mode - The SYSTEM repeat mode is selected when full communications among
all radio parties are desired. In this mode both the MCS2000 mobile radio and the vehicular
repeater are enabled, permitting communications between portable radio users, the mobile
operator and the dispatcher, as well as any other users on the mobile talk group. The mobile user
simultaneously keys both the mobile radio and vehicular repeater transmitters when using the
microphone Push-to-Talk button.
17.3 Features
The following table describes the features available for the vehicular repeater.
Table 17-1 Vehicular Repeater Features
Features Availability
Group Call Yes
Selective Call Yes (with the mobile radio ill)
Call Alert No
Emergency Call Yes
Telephone Interconnect No
Talk Permit Tone Yes
Use or disclosure of this proposal is subject to the restrlctions 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
50
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
System Functional Specification
Section 2
Version 1.0
System Busy Tone Yes
Auto Call Back Yes
Failsoft Mode Yes
Mode Switching Notification Yes
Simulcast Prevention Yes
17.4 Vehicular Repeater Simulcast Prevention
When several vehicles equipped with a vehicular repeater are located at the same location, only
one can be used without resulting in interference. When there is more than one vehicular repeater
at a site, one vehicular repeater will transmit and the other will go into a random delay state.
Upon expiration of the delay state, the unit will 'listen' on the transmit frequency for other
vehicular repeaters. If there are no other vehicular repeaters transmitting, the unit will begin to
transmit.
Use or disclosure of this proposal is subject to the restrictiolls 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
51
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
EXHIBIT C-2
Price List
Version 4.0
DATE: Mar. 12,2002
TO: The Fire Departments of Durham Region
CUSTOMER REF. NO.:
MOTOROLA REF. NO.:
Motorola Pricing Summary PST & GST ARE EXTRA
ITEM DESCRIPTION MODEL QTY AVG. UNIT PRICE EXTENDED PRICE
Infrastructure
1 Prime Site (Oshawa City Hall) Controller Equipment 1 $254,654.00 $254,654.00
2 Prime Site Simulcast I Voting Equipment 1 $613,707.00 $613,707.00
3 Comcenter (Oshawa Fire Hall #1) Dispatch Equipment Upgrade 1 $140,937.00 $140,937.00
4 Remote Dispatch Center 1 $62,024.00 $62,024.00
5 Co-locate Remote Site (Oshawa City Hall) Equipment 1 $264,445.00 $264,445.00
6 Remote Site (Pickering) Equipment 1 $377,268.00 $377,268.00
7 Remote Site (Whitby) Equipment 1 $369,108.00 $369,108.00
8 Remote Site (Bowmanvllle) Equipment 1 $371,148.00 $371,148.00
9 Remote Site (Orono) Equipment 1 $369,696.00 $369,696.00
10 Upgrade Paging Stations at Whitby and Clarlngton 3 $6,109.67 $18,329.00
11 Upgrade Paging Stations at Pickering 3 $5,952.00 $17,856.00
12 MCS Mobile Radio-Pickering 25 $2,751.00 $68,775.00
13 MCS Mobile Radio-AJax 16 $2,751.00 $44,016.00
14 MCS Mobile Radio-Whitby 21 $2,751.00 $57,771.00
15 MCS Mobile Radlo-Clarlngton 19 $2,751.00 $52,269.00
16 XTS3000 Portable Radio-Pickering 60 $4,629.00 $277,740.00
17 XTS3000 Portable Radio-Ajax 30 $4,629.00 $138,870.00
18 XTS3000 Portable Radio-Whitby 26 $4,629.00 $120,354.00
19 XTS3000 Portable Radlo-Clarington 40 $4,629.00 $185,160.00
20 XTS3000 Portable Radio Accessory 1 $24,312.00 $24,312.00
21 MCS Mobile Radio Manuals & Programming Kit 1 $1,590.00 $1,590.00
22 XTS3000 Potable Radio Manuals & Programming Kit 1 $2,547.00 $2,547.00
23 MOSCAD for Whitby, Oshawa & Clarington 1 $123,557.00 $123,557.00
24 MOSCAD for Pickering & Ajax 1 $105,661.00 $105,661.00
25 MOSCAD Services 1 $117,904.00 $117,904.00
TOTAL PAGE 1 $4,179,698.00
SUB TOTAL $4,179,698.00
SHIPMENT PER
PAYMENT Keith Lyon
Toronto Sales
F.O.B. MOTOROLA Canada Limited
Note: 01'\0(" ~T~
If this contract can be signed 'before March ~ the price will be reduced by $100,000. Included in the contract will be a mutually
agreed upon schedule for all activities including dates that radio sites must be built and telephone circuit must be installed and
tested. If the customer meets both site preparation ~~Phone circuit milestones, the price will be reduced by $50,000, If the Detail
Design Review (DDR) can be finished before May ,t e price will be reduced by $75,000. User Gear prices will remain in effect
for 2002. Additional user gear orders till the end of 2006 will be 15% off the then list prices for single orders less than $250,000 and
20% off the then list prices for single orders over $250,000.
Motorola Confidential Proprietary
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
Price List
Version 4.0
DATE: Mar. 12,2002
ITEM DESCRIPTION MODEL QTY AVG. UNIT PRICE EXTENDED PRICE
Services
26 51 Services 1 $1,443,233.00
SI Services - Civil Work Site Develooment
27 Oshawa City Hall - Site Development 1 $74,545.00 $74,545.00
28 Mitchel's Corner - Williams Site 1 $0.00 $0.00
29 Whitby Bell Site - Portion of Shelter - R56 1 $23,576.00 $23,576.00
30 Bowmanville Water Tower - 10ft tower section/Rigging/Shelter/Compound 1 $0.00 $0.00
31 Telus - Orno - Shelter/Rigging/Compound Enlargement 1 $298,181.00 $298,181.00
32 Pickering Comm Center 1 $22,363.00 $22,363.00
33 Pickering Transit Site 1 $70,675.00 $70,675.00
Additional Loaaina Tracks
Infrastructure
34 Additional Cardcage and Power Supply for CEB 1 $13,839.00 $13,839.00
35 8 Logging Tracks 1 $10,582.00 $10,582.00
36 8 Additional Logging Tracks 1 $4,334.00 $4,334.00
Additional Loaaina Tracks Services
37 51 Services 1 $1,359.00 $1,359.00
TOTAL PAGE 2 $1,962,687.00
CUMULATIVE TOTAL $6,142,385.00
iv1otorola Confidential Proprietary
2
Fire Departments of Durham Region
TRUNKED VOICE RADIO SYSTEM
G MOTOROI..A Quotation DATE: Feb. 01,2002
TO: The Fire Departments of Durham Region
CUSTOMER REF. NO.:
MOTOROLA REF. NO.:
Motorola PricinQ Summary-Options PST & GST ARE EXTRA
DATE: Feb. 01,2002
ITEM DESCRIPTION MODEL aTY AVG. UNIT PRICE EXTENDED PRICE
1b Infrastructure Spares 1 $114,239.00 $114,239.00
2b Optional Channel Banks for Remote Dispatch Center 1 $41,464.00 $41,464.00
3b Optional Access Base Radio 1 $5,064.00 $5,064.00
4b Optional Dash Mount Mobile 1 $2,503.00 $2,503.00
5b Optional Mobile Dual Control Head 1 $4,390.00 $4,390.00
6b Optional MTS Portable 1 $3,218.25 $3,218.25
7b Optional MTS Accessories 1 $2,109.00 $2,109.00
8b Optional UPS (1hr 30 mln) at the Remote Site 1 $5,612.00 $5,612.00
9b Optional XTS Remote Speaker Mic. 1 $125.00 $125.00
10b Optional Vehicular Repeater 1 $13,838.00 $13,838.00
11b Optional XTS Single Unit Charger 1 $198.00 $198.00
TOTAL PAGE 1 $192,760.25
CUMULATIVE TOTAL $192,760.25
Motorola Confidential Proprietary
Price List
Version 1.0
EXHIBIT C-3
SECTION 6
STATEMENT OF WORK
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
TABLE OF CONTENTS
1.0 INTRODUCTION .... ......................................................................... .......... 1
2.0 PROJ ECT SCOPE .......... ........................... ............................................... 1
3.0 PROGRAM RESPONSIBI L1TIES.. ............. ................................. .............. 1
3.1 Responsibility Matrix.................................................................................. 2
4.0 PROJ ECT MANAG EMENT ....... .................. ............................... ..... .......... 3
4.1 Meetings.................................................................................................... 3
4.2 Reporting. ........ .............................................................. ............................ 4
4.3 The Change Order Process.......................................................................4
5.0 PROJECT SCHEDULE ................................................................111............ 5
5.1 Project Schedule.................. .................. ........................ ............. ...... ......... 5
5.1 Explanation of Project Milestones.............................................................. 5
5. 1. 1 Contract Signing................................................................................................. 5
5. 1.2 Detailed Design Review............................................. ......................................... 5
5.1.3 Equipment Orders Placed on Motorola Manufacturing Facilities.......................... 6
5.1.4 Complete and Approve Fleet Map....................................................................... 6
5. 1.5 Site Ready to Receive Equipment.............. .......... ...... ........................... .............. 6
5. 1.6 CCSI Staging .. ... ....... ... ......... ... ......... ...... ... ......... ...... ... ..... ......... ..... ........ ... ......... 6
5. 1.7 Factory Acceptance Testing .................. .............. ...... .............. ............................ 7
5. 1.8 Equipment Shipping ................ .................. ........ ......................... ............. ............ 7
5.1.9 Equipment Received by Durham Fire Departments............................................. 7
5.1.10 Infrastructure Installed, Confirmed and Optimized............................................... 7
5.1.11 Provisional Acceptance of Infrastructure ............................................................. 7
5.1.12 Install Pickering / Ajax Dispatch Positions (Single Location)................................ 7
5.1.13 Provisional Acceptance of Dispatch Positions..................................................... 8
5.1.14 Install MOSCAD Fire Hall Alerting Equipment..................................................... 8
5.1.15 Provisional Acceptance of MOSCAD Fire Hall Alerting Equipment ...................... 8
5. 1. 16 User Gear Installed, Configured and Optimized ................................. ........ ......... 8
5.1.17 Provisional Acceptance of User Gear.................................................................. 8
5. 1. 18 Training Complete....................................................................................... ........ 9
5. 1. 19 Final Acceptance ........ ................... ................................................ ..................... 9
6.0 DOCUMENTATION PLAN ..............III11.III1I11.IlI.i:I.lIll1.II.III1I1I1I1.II...IlI.IIlIlIl....lII.lIl1l11Il.1I11l........III1...., 9
6.1 Site Requirements Document.................................................................. 10
6.2 Site I nspection Report ............................................................................. 10
6.3 installation Plan (Method of Procedure)................................................... 10
Use or disc/oSllre of this proposal is subjen 10 the restrictiolls 011 rhe title page.
Motorola Confidential Proprietary
@ MOTOROLA.
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
6.4 Training Course Schedule....................................................................... 10
6.5 Training Course Material ......................................................................... 11
6.6 Equipment Inventory List ......................................................................... 11
6.7 Field Acceptance Test Procedures and Coverage Acceptance Test
Procedure......... ....................................................................................... 11
6.8 Provisional Acceptance Certificate ........................ ...... ............................ 12
6.9 Punchlist Report ........................ ................................ .............................. 12
6.10 Infrastructure Equipment Service Manuals .............................................. 12
6.11 User Gear Operator Manuals .................................................................. 12
6.12 System Manual.......... .............................................................................. 12
6.13 Final Acceptance Certificate ............ .... ....... .......... ....... ............................ 13
7.0 TRAINING PLAN ................................. .................................................... 13
7.1 User Training ........................................................................................... 13
8.0 SYSTEM ACCEPTANCE ........................................................................ 13
8. 1 Scope ...................................................................................................... 13
8.2 Pu nch list.............. .. ...... ........ . .. .. . .. . . .. . ... ... . ..... ... . .. .... ..... .. . .. ... .... .. . .. ........... 14
8.2.1 Punchlist Report Severity Levels........................................................................ 14
8.3 Provisional Acceptance........................................................................... 15
8.4 Final System Acceptance ........................................................................ 15
EXHIBIT Al CHANGE ORDER FORM....................................................................................17
Use 01" disc/ullIre oj'this proposal is subject to the restrictions 0/1 the title page.
Motorola Confidential Proprietary
@ MOTOROLA
II
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
STATEMENT OF WORK
1.0 INTRODUCTION
The purpose of this Statement of Work (SOW) is to define the deliverables required to
upgrade the current 800 MHz, City of Oshawa Fire Department system; VHF, City of
Whitby Fire Department system; and VHF, City of Clarington Fire Department system; and
VHF, Town of Ajax system; and VHF, City of Pickering system to an 800 MHz, Durham
Fire Departments system. This SOW also describes how Motorola will manage the project,
as well as the process by which acceptance of the work shall be granted by Durham Fire
Departments. The functionality of the system shall be in accordance with the Functional and
Technical Specification. The demonstration of the systems performance shall be in
accordance with the Acceptance Test Plan. The Price List lists the material and services to
be provided as well as the prices for each.
2.0 PROJECT SCOPE
This project is for the supply of material and services as (defined in the Price List) associated
with the upgrade to the Durham Fire Departments system. Motorola will design,
manufacture, install and commission the equipment as detailed in this SOW and the price
list.
3.0 PROGRAM RESPONSIBiliTIES
This section summarizes the responsibilities of both parties. Changes in these responsibilities
may trigger changes in other parts of this contract.
Use or disclosure oftilis COlllract is subject to the resrrictiolls Oil rhe rirle page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
3.1 Responsibility Matrix
Legend:
R - Responsible to perform the task
I - Provides input to the party responsible to perform the task
Notes - See clarification below this table
Item Description Notes Motorola Durham
Fire
Departme
n15 Dept.
1 Sign contract for supply and commissioning of equipment and 3 R R
services detailed in the Price List
2 Identify new frequencies for expansion I R
3 Site development and preparation, including building, HV AC, 1,2 I R
AC/DC power, Grounding, Floor Space and Cable raceways.
4 Provide shipping destination in the Durham Regional area. R
5 Develop Method of Procedure (MOP) for system upgrade activities 3 R I
and cut-over plan.
6 Manufacture and/or procure all material 3 R
7 Stage equipment at CCSI. 3 R
8 Factory Acceptance Testing. 3 R R
9 Ship equipment. 3,8 R I
10 Inventory the delivered equipment. 3 R I
11 Provide all telephone and site linking equipment. 2 I R
12 Provide and install all required external power sources (AC and DC) 2 I R
13 Install and commission infrastructure equipment. 1,3,5 R
14 Install all required cables between supplied equipment. 3,5 R
15 Perform Field Acceptance Test inclusive of Coverage Testing 3,8 R R
16 Program and install user gear according to installation plan. 3,5,6 R R
17 Commission supplied user gear. 3,8 R R
18 Design configuration databases in the system. R I
19 Enter and update console data, perform database administration. 7 R I
20 Provide training as detailed in this proposal. 3 R I
21 Provide warranty for equipment supplied under this contract. 3 R
22 Remove and dispose of old equipment. R I
23 Provide the documentation listed in Section 6.0 of this SOW. 3 R
24 Issue Contract Change Orders (CCO) for any changes or additional 3 R I
work.
25 Provide consulting services, changes or additional work as per 3,4 R I
I potential Contract Change Orders.
Notes:
1. Site development to follow guidelines of Motorola R56 Quality.
'I Detailed Requirements provided in Appendix A (Site Requirements).
l}sf or disclosure ofrhis cOl1lmcr is subject to rhe resrricriolls ollrhe rille page.
Motorola Confidential Proprietary
([5) IiWOl'f/"OIROu..A February 2002
2
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
3. Current standard Motorola procedures will be used.
4. These services to be provided at the per diem rate shown in the Price List.
5. Installation to include all activities from removing of packaging to powering up.
6. Motorola will program and install user gear for Durham Fire Departments. This proposal
includes up to 5 different radio templates and up to 50 talk groups.
7. Motorola will enter the initial sets of data, train the customer to become Data Base
Administrators (DBA) and assist the DBA in the initial stages.
8. Tests to follow Acceptance Test Procedures compiled by Motorola and approved by
Durham Fire Departments. Motorola will test and the Durham Fire Departments will
witness and approve.
4.0 PROJECT MANAGEMENT
The Project Manager defines all project activities in Motorola via a project implementation
plan. This plan is used to define the project organization, the internal and external division of
responsibilities, work breakdown structure, schedule, resource planning, project monitoring
and project controlling processes. Due to the size and scope of this project it is
recommended that Durham Fire Departments identify a Project Manager that will be the
central point of contact for Motorola.
4.1 Meetings
Both Motorola and the Durham Fire Departments will schedule meetings, upon mutual
agreement. Both the Durham Fire Departments and Motorola will approve meeting locations
and agendas, twenty-four hours prior to the meeting date. This will allow for the proper
resources of both groups to be made available to ensure each agenda item is fully responded
to. Supplemental meeting items can be included at the time of the meeting. The following is
a list of potential meeting subjects.
· Project Kickoff
.. Progress Meetings
fl> System Fleetmapping
ED Equipment Inventory and Pre-Installation
Use OJ" disclosure of this ('oll1mo is subjec1to the restrictiolls 011 the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
3
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
. Installation and Cut-over Plan
. Training Plan
. System Acceptance
. Project Closeout
4.2 Reporting
The Motorola Project Manager will prepare Monthly Progress Reports and submit them to
Durham Fire Departments Project Manager. The Monthly Progress Report will constitute the
basis for analysis of the achievements in the past month, and planning of future activities.
Motorola may generate other reports, if deemed necessary. Durham Fire Departments may
also wish to receive additional reports on a periodic basis, or to cover specific issues. The
reporting scheme will be discussed and agreed to at the kick off session.
4.3 The Change Order Process
Contract change requirements may arise from time to time during the execution of the
project.
Changes to the scope of work which affect system functionality, the schedule, or the price
list will trigger a contract change request. Such a request can be made by either the Durham
Fire Departments or Motorola. Either party must obtain the other's concurrence to change
any commitments contained in this agreement prior to proceeding.
A preliminary estimate cost of the change order will be provided to the requesting party
within one week of receiving a request. The written preliminary estimate will give the tasks,
cost and duration (if any) required to execute the detailed change order proposal and the
change order itself. If the requesting party chooses to proceed with the change order,
preparation after approving the preliminary estimate, a detailed change order proposal will
be prepared (Exhibit AI).
The detailed change order proposal will include revisions of any contract sections that are
affected. Before the change order is implemented both the Durham Fire Departments and
Motorola are required to agree to and sign the document.
VIe or di"closure (!!'this COlllract is subject to lize restrictions Oil the title page.
Motorolia Confidential Proprietary
(A) MOTOROLA February 2002
'-.../
4
Durham Fire Departments
SMARTNET RADIO COMMUNICA nONS SYSTEM
Statement of Work
Section 6
Version 1.0
5.0 PROJECT SCHEDULE
5.1 Project Schedule
Times are indicated in weeks after Signature of Contract. The completion date is a function
of the proposed contract signature date.
Milestone Activity Week of CompletiOl
ARO
1 Contract signing Project Initiation
2 Detailed Design Review Project Start
3 Equipment orders placed at Motorola manufacturing facilities 2
4 Complete and Approve Fleet Map 3
5 Sites ready to receive equipment 12
6 CCSI Staging 16
7 Factory Acceptance Testing 18
8 Equipment Shipped 19
9 Equipment Received by Durham Regional Fire 21
10 Infrastructure Installed, Configured and Optimized 31
11 Provisional Acceptance of Infrastructure 32
12 Install Pickering / Ajax Dispatch Positions (Single Location) 35
13 Provisional Acceptance of Dispatch Positions 36
14 Install MOSCAD Fire Hall Alerting Equipment 40
15 Provisional Acceptance of MOSCAD Fire Hall Alerting Eq. 42
16 User gear Installed Configured and Optimized 51
17 Provisional Acceptance of User gear 53
18 Training Complete 56
19 Final Acceptance 58
5.1 Explanation of Project Milestones
5. 1. 1 Contract Signing
The contract will include all the relevant documents. All information required to execute the
project must be included in the contract prior to this milestone being achieved.
5. 1.2 Detailed Design Review
Upon receiving certified frequencies from Industry Canada a Detailed Design Review will
be completed. At this point the final sites should also be selected. The frequency information
and the final site selection will permit us to validate our design for Intermodulation among
the sites. There will also be the requirement to have inventoried the current user and making
Use or disclosure of this COil tract is mbjecr to the restrictiolls Oil the titie page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
5
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
final selection of the new user gear prior to placing the equipment order. When these items
have been completed this milestone will be achieved and the equipment order can be placed
on the factory.
5. 1.3 Equipment Orders Placed on Motorola Manufacturing
Facilities
Upon confirmation from the manufacturing facility that the order has been received and a
manufacturing date has been given, this milestone will be achieved.
5. 1.4
Complete and Approve Fleet Map
Representatives from all five Fire Departments will meet to create the Fleet Map that will be
the basis of communications and operations for the system functionality
5. 1.5 Site Ready to Receive Equipment
Motorola will conduct a site inspection as soon as the site preparation work is finished. The
site inspection will ensure that all the required work is completed and the sites are at an R56
level and compliant to the Site Requirements document. This milestone will be achieved
once the inspection is complete and all, if any, deficiencies are resolved. Motorola will be
able to supply civil services required for the currently identified sites. Pickering - Coast
Guard Tower, Whitby - Bell Mobility Tower, Oshawa City Center - Prime Site, Clarington
- Bowmanville Water Tower, Clarington - Telus Tower. There may be a need in several
cases to perform feasibility studies or tower loading studies prior to locating equipment at
these locations. These services are not part of the current offering and will be provided via
the change order process as required. The need for Shelters and compound expansion has
been included as part of the Coast Guard, Bowmanville, and Telus sites. The Mitchell's
Corner site owned by Williams Communication and the Whitby site owned by Bell Mobility
will both have to be negotiated by the Durham Fire Departments. Services associated with
these two sites are not included in this quotation.
5.1.6 CCSI Staging
This milestone will be achieved once the equipment has been received by the Customer
Center for System Integration according to detail racking and programming information
supplied by the project engineer.
Use or disclosure oftllis COil tract is subject to the restrictiOlls 011 the tille page.
Motorola Confidential Proprietary
(/J0 MOTOROLA. February 2002
6
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
5. 1.7 Factory Acceptance Testing
Upon completion of the staging at CCSI a formal factory functional test will be performed.
This testing will be witnessed and approved by the customer at the factory location in
Schaumberg, n.... The details of the testing procedure will be clearly outlined in the Factory
Acceptance Test plan.
5. 1.8 Equipment Shipping
This milestone will be achieved post customer approved factory acceptance testing. This will
allow the staged equipment to be loaded for delivery to the customer location.
5. 1.9 Equipment Received by Durham Fire Departments
This milestone will be achieved once the equipment has been received by the Durham Fire
Departments at the contractual shipping destination Should there not be room at the
destination an alternate one will need to be secured.
5. 1. 10 Infrastructure Installed, Confirmed and Optimized
Soon after the equipment is received at the specified Durham Fire Departments location the
configuration and installation of this equipment will begin. Once this equipment is
configured, installed and optimized this milestone will be achieved.
5. 1. 11 Provisional Acceptance of Infrastructure
Following the installation and commissioning of the equipment the Field Acceptance test
will be performed to verify the functionality of the Infrastructure. Once this test is
successfully completed, both Motorola and the Durham Fire Departments will sign a
Provisional Acceptance Certificate and the Provisional Acceptance milestone will be
achieved. Refer to Section 8 for more details on the Acceptance process.
5. 1. 12 Install Pickering / Ajax Dispatch Positions (Single
Location)
This milestone will be achieved once the equipment has been installed and optimized in a
single location. This location should conform to the R56 spec such that it will permit optimal
Use or disclosure of this colltrac{ is subject to the restrictiolls all the tille page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
7
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
efficiency from the equipment. An environment that does not conform could result in
unacceptable performance.
5.1.13
Provisional Acceptance of Dispatch Positions
Following the installation and conunissioning of the equipment the Field Acceptance test
will be performed to verify the functionality of the Dispatch positions. Once this test is
successfully completed, both Motorola and the Durham Fire Departments will sign a
Provisional Acceptance Certificate and the Provisional Acceptance milestone will be
achieved. Refer to Section 8 for more details on the Acceptance process.
5.1.14
Install MOSCAD Fire Hall Alerting Equipment
Soon after the equipment is received at the specified Durham Fire Departments location the
configuration and installation of this equipment will begin. Once this equipment is
configured and installed this milestone will be achieved.
5. 1. 15 Provisional Acceptance of MOSCAD Fire Hall Alerting
Equipment
Following the installation and conunissioning of the equipment the Field Acceptance test
will be performed to verify the functionality of the MOSCAD system. Once this test is
successfully completed, both Motorola and the Durham Fire Departments will sign a
Provisional Acceptance Certificate and the Provisional Acceptance milestone will be
achieved. Refer to Section 8 for more details on the Acceptance process.
5. 1. 16 User Gear Installed, Configured and Optimized
Soon after the equipment is received at the specified Durham Fire Departments location and
item 5.1.7 has been met, then the configuration and installation of this equipment will begin.
Once this equipment has been configured and installed this milestone will be achieved.
5. 1. 17 Provisional Acceptance of User Gear
Following the installation and conunissioning of the equipment identified in 5.1.16, the Field
Acceptance test will be performed to verify the functionality of a portion of the User gear.
Once this test is successfully completed, both Motorola and the Durham Fire Departments
Use or disclosure of this contract is subject to the restrictiollS on/he Ii/Ie page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
8
Durham Fire Departments
SMARTNET RADIO COMMUNICA nONS SYSTEM
Statement of Work
Section 6
Version 1.0
will sign a Provisional Acceptance Certificate and the Provisional Acceptance milestone will
be achieved. Refer to Section 8 for more details on the Acceptance process.
5. 1. 18 Training Complete
When Motorola has delivered the specified training to Durham Fire Departments this
milestone will be achieved.
5. 1. 19 Final Acceptance
When Durham Fire Departments and Motorola have signed the Final Acceptance Certificate,
this milestone will be achieved. It will require reviewing the coverage maps and resolving all
severity 1 and 2 punchlist items.
6.0 DOCUMENTATION PLAN
Standard Motorola equipment manuals will be supplied, as well as third party equipment
manuals as provided by the manufacturer.
The following documents will be prepared and delivered to Durham Fire Departments in
accordance with the project schedule. These documents are described below.
Document Quantity
Supplied
1 Site Requirements Document 1
2 Site Inspection Report 1
3 Installation Plan (Method of Procedure) 1
4 Training Course Schedule 1
5 Training Course Material 1 per student
6 Equipment Inventory List 1
7 Field Acceptance Testing Procedures 1
8 Provisional Acceptance Certificate 1
9 Punchlist Report 1
10 Infrastructure Equipment Maintenance Manuals 1
11 User gear Manuals 1 per unit
Use or disclosure of"this contract i.l SlIbject to the restrictioll.l Oil rhe titLe page.
Motorola Confidential Proprietary
@ MOTOROLA. February 2002
9
Durham Fire Departments
SMARTNET RADIO COMMUNICATIONS SYSTEM
Statement of Work
Section 6
Version 1.0
Document
Quantity
Supplied
1
1.
12 System Manual
13 Final Acceptance Certificate
6.1 Site Requirements Document
This document will provide a description of all the site requirements, which must be met for
the Motorola supplied equipment to meet the specifications contained in this contract. The
purpose of this document is to communicate these requirements to the Durham Fire
Departments, so that the site preparations can be done accordingly.
6.2 Site Inspection Report
Motorola will prepare this document to confirm that the site preparations, which are the
Durham Fire Departments responsibility as stated in R56 CD Rom, are completed as per the
required standards.
6.3 Installation Plan (Method of Procedure)
Motorola will provide a Method of Procedure (MOP) document that will detail the
equipment configuration and installation tasks and their sequence. The Durham Fire
Departments will approve the MOP document prior to the start of the upgrade. The Durham
Fire Departments will also provide Motorola with information about operational
requirements, which must be taken into account during the upgrade period.
6.4 Training Course Schedule
No later than three weeks prior to the scheduled date of equipment installation, Motorola
will provide a detailed schedule for all the training to be provided within the scope of this
SOW. We will be training no more than 8 dispatch operators on the dispatch function and 8
trainers that will be instructing the firefighters directly. The train the trainer approach has
proven quick and effective. Should an alternate approach be required for either operations
this would have to be addressed via the change order process. The training schedule will be
prepared in close cooperation with the Durham Fire Departments.
Use or disclosure of this cOlltract is subject to the restrictiolls Oil the title page.
Motorola Confidential Proprietary
@ MOTOROLA February 2002
10