Exhibit K - (REDACTED) - System Acceptance Plan v2 (FINAL)

Exhibit K System Acceptance Plan
800 MHz Emergency Communications Systems

For Sarasota and Manatee Counties
RFP 142842TM
Exhibit K System Acceptance Plan*

*The contents of this Exhibit K have been redcated in sections
where such content is subject to disclosure under public
records law pursuant to Section 815.045 F.S.
K-1

RFP 142842TM
K-2

RFP 142842TM
Microwave Factory Acceptance Test Plan

Note: This document is a sample and will be modified and submitted to the Counties for approval
prior to testing.
AGENDA
ARRIVAL AND INTRODUCTIONS
FACTORY ACCEPTANCE TEST OVERVIEW / WHAT TO EXPECT / REVIEW FAT PLAN.
SYSTEM TOUR AND FAMILIARIZATION.
FACTORY ACCEPTANCE TEST (FAT)

(Unless otherwise specified, tests will be performed on several sites selected at the time
of FAT)
DAY 1
1.
PERFORM A VISUAL INSPECTION AND INVENTORY EQUIPMENT.
2.
VERIFY SOFTWARE VERSIONS.
3.
VERIFY TRANSMITTER AND RECEIVER FREQUENCIES.
4.
VERIFY RADIO TRANSMIT POWER OUTPUT AT TOP OF RACK (TOR).
5.
VERIFY RECEIVER THRESHOLDS.
6.
VERIFY END-TO-END CIRCUIT CONNECTIVITY AND CONTINUITY AT ALL SITES.
7.
PERFORM A LONG TERM BER (BIT ERROR RATE) TEST (OVERNIGHT TEST).
Note: The residual BER test shall be made under NO FADE CONDITIONS. The test
period shall be a minimum of 12 hours with BER not to exceed the test objective of
Nx10E-12, where N is equal to the number of radio hops (one way).
DAY 2
8.
CHECK LONG TERM BER OVERNIGHT TESTING.
9.
VERIFY TRANSMITTER AND RECEIVER SWITCH OPERATION AS APPLICABLE.

ETHERNET THROUGHPUT.
10. DEMONSTRATE OPERATION OF ALARMS.

11. DEMOSTRATE OPERATION OF CONFIGURATION AND MANAGEMENT TOOL
(PORTAL).
K-3

RFP 142842TM
12. DEMONSTRATE PROVISION NMS- OPERATIONAL CAPABILITIES TO INCLUDE
ALARMS REPORTING, CONTROLS FUNCTIONALITY.
REVIEW FAT RESULTS AND AGREE ON ACTION ITEMS
DISCUSS PLANS FOR SHIPMENT AUTHORIZATION FOR SHIPMENT. SIGN-OFF ON

CERTIFICATE OF ACCEPTANCE
K-4

RFP 142842TM
FACTORY ACCEPTANCE TEST (FAT)
OVERVIEW
Prior to Factory Acceptance Test (FAT), Aviat Networks and a subset of Airbus DS
Communications manufactured equipment are staged on the Aviat factory floor and connections
are made to simulate network connections and system layout per system documentation prepared
by Aviat Networks Configuration Engineering team. Transmission measurements are conducted
between coordinating radio assemblies to assess the overall radio equipment operation. Ethernet
channels are provisioned per the channel plan and each channel is tested to the specification
using appropriate test sets and procedures. For the vendor equipment, tests are conducted in
accordance with recommendations stated in the appropriate product manual(s). Network
Management System monitoring and control functionalities are verified using the Provision NMS
provided for the system or verified using factory provided Provision NMS if NMS is not
provided for the system.
SCOPE OF WORK
Aviat Networks staff will perform the tests as outlined. Any exceptions, additions, or deletions
will be noted in the appropriate section of the FAT document. The customer representative(s) that
witness the FAT test process will initial each test of the master copy of FAT document upon
completion of the test. The Aviat Networks representative will also initial each test as the test
program progresses. The primary representative for each party will sign the Certificate of
Acceptance upon completion of the tests. The signatories are stating that they have witnessed the
FAT as defined in this document, and that witnessed test values were within the specification of
recorded test results on factory test data forms.
ETHERNET TESTING
The RFC2544 Throughput Test method is used for evaluating the transfer performance of the
equipment.
Throughput
Throughput is a measure of how many input frames the network equipment can transfer without
dropped frames. Throughput is measured by inputting frames to the device under test (DUT) at a
known rate and checking whether or not the transferred frames are lost. The input frame rate is
changed to measure the maximum rate at which frames can be transferred without loss.
As an example, frames are input to the DUT at a rate of 10 k fps. The DUT is not able to transfer
all the input frames and part of the frames seem to be lost. In this case, the frame input frame is
lowered to 9.5 k fps and the test is performed again. In this case all the frames are transferred. As
a result, the DUT Throughput is evaluated as being between 9.5 and 10 k fps. Naturally, if all the
frames are transferred without loss in the first test, the frame input rate is raised and the test is
rerun. The frame transfer performance is measured at different rates at different frame sizes and
the maximum rate at which frames are transferred without frame loss is the Throughput.
K-5

RFP 142842TM
TEST FAILURE HANDLING PROCESS

In the unlikely event that any component should fail during factory acceptance testing,
or fail to meet the criteria specified to pass a specific test:
a) Where a failed component can be immediately replaced, it will be and testing will
continue as per the test procedure.
b) If a system test should fail, factory engineers will be given an opportunity to
remedy the problem. A re-test will then be performed
ACCEPTANCE CRITERIA
A punch list of open items will be prepared.
Upon conclusion and satisfactory completion of this FAT, a Certificate of Acceptance
will be signed by representatives of the Counties and Aviat Networks representative to
certify that the equipment has been approved for delivery after all punch list items
have been resolved.
K-6

RFP 142842TM
K-7

RFP 142842TM
PRODUCT(s)
a) Eclipse IRU 600
REFERENCES
a) Instruction Manuals
TEST EQUIPMENT
Description
1
2
POWER METER (HP435 or Equivalent)

STD POWER HEAD (HP8481A or equivalent)
HI POWER HEAD (HP8481B or equivalent)
LOW POWER HEAD (HP8481D or equivalent)
PATH ATTENUATORS
ETHERNET TESTER (SMB600B or equivalent)
BER TESTERS:
Other:
Model
Number*
Serial
Number*
Calibration
Due Date*
*to be filled during Factory Acceptance Test
K-8

RFP 142842TM
PROCEDURE
1.
VISUAL INSPECTION AND INVENTORY:

Visual inspection
1.1.
1.1.1. Verify that equipment is installed per Rack Profiles.

1.1.2. Verify labeling of racks
1.1.3. Using the bill of material list (Rack Build report), inventory all material
hardware for completeness and accuracy.

Mechanical Inspection
1.2.
1.2.1. Check that the shelves are secure and free of defects or damages.
1.2.2. Check that all power wiring is properly secured and aligned.
1.2.3. Check that there are no broken, bent or mis-aligned connectors.
1.2.4. Check that there are no misaligned, dented or twisted shelves.
1.2.5. Check that there is no broken or damaged equipment (connectors,
wiring, etc.)
1.2.6. Check that all cabling and wiring is terminated and secured in place.
Visual Inspection
Mechanical Inspection
RACK #
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
Site Name
K-9

RFP 142842TM
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
COMMENTS:
________________________________________________________________________
INITIALS:
2.
SYSTEMS INTG. TECH.
CUSTOMER REP.
VERIFY SOFTWARE VERSIONS:

2.1.
Using Sales Order Specific documents, configuration/management tool

and/or Provision NMS, check software versions.
2.2.
Verify capacity license(s) and future licenses, if any.
2.3.
Record.
SW Versions
Part
Part Number
Description
COMMENTS:
________________________________________________________________________
INITIALS:
SYSTEMS INTG. TECH.
CUSTOMER REP.
K-10

RFP 142842TM
3.
VERIFY TRANSMITTER AND RECEIVER FREQUENCIES:

Using Aviat Portal or Provision NMS, verify that transmit and receive frequencies
are programmed per requirements.
RESULTS:
RAC
K#
Site Name
Radio
#
TRANSMIT FREQUENCY
(MHz)
TX
TX
#1
#2
Programmed
RECEIVE FREQUENCY (MHz)
Programmed
COMMENTS:
________________________________________________________________________
INITIALS:
SYSTEMS INTG. TECH.
CUSTOMER REP.
K-11
RX
#1
Rx
#2

RFP 142842TM
4.
TRANSMIT POWER OUTPUT (TOR)

4.1.
Mute Transmitter.
4.2.
Install a wave-guide to N-type adapter to the TOR wave-guide flange.
4.3.
Connect calibrated high power head to adapter.
4.4.
Unmute transmitter.
4.5.
Measure/record Power Output at the TOR.
4.6.
Record the Portal reading.
4.7.
Mute Transmitter.
4.8.
Disconnect calibrated high power head and remove N-type adaptor.
4.9.
Restore RF Connection.
4.10. Unmute the Transmitter.
TEST EQUIPMENT: POWER METER, HIGH POWER HEAD

REQUIREMENT:
Freq
Band
(GHz)
Modulati
on
(QAM)
Transmitter Power Output (dBm)x

Capacity
(Mbps )
BW
(MHz)
STD/HI
GH
NP
* Guaranteed at antenna flange port of ACU for Maximum System Gain.

WG Extension/Expansion kit
Deduct 0.1dB for each piece of
RESULTS:
RAC
K#
Site Name
Radio
#
TX #1 (dBm)
SPEC
TX #2 (dBm)
MEASUR
ED
PORTAL
SPEC
MEASUR
ED
COMMENTS:
________________________________________________________________________
K-12
PORTA
L

RFP 142842TM
INITIALS:
SYSTEMS INTG. TECH.
CUSTOMER REP.
K-13

RFP 142842TM
RECEIVER THRESHOLD (NOTE for Space Diversity Hops, each Receiver will be
tested individually)
5.
5.1.
Connect path simulator between coordinating racks.
5.2.
Calibrate path simulator over the dynamic range and note the attenuator
settings vs. Received Signal Level (RSL) at TOR.
5.3.
Fade the path until BER reading is 1X10-6.
5.4.
Record the measured value.
5.5.
Repeat for other units under test.
TEST EQUIPMENT:
BER TESTER, LOW POWER HEAD, PATH SIMULATOR
REQUIREMENT:
Freq
Band
(GHz)
Thresholdx (dBm) @ BER = 1 x10-6
Modulati
on
(QAM)
Capacity
(Mbps )
BW
(MHz)
NP/SD/FD
RCVR # 1
Space
Diversity
RCVR # 2
* Guaranteed at antenna flange port of ACU for Maximum System Gain.

WG Extension/Expansion kit.
46
RACK
#
Deduct 0.1 dB for each piece of
RESULTS:
Site Name
Radio
#
RCVR #1 (dBm)
SPEC
MEASURED
RCVR #2 (dBm)
SPEC
MEASURED
K-14

RFP 142842TM
COMMENTS:
________________________________________________________________________
INITIALS:
6.
CUSTOMER REP.
SYSTEMS INTG. TECH.
END-TO-END CIRCUIT ASSIGNMENTS PER CHANNEL PLAN AND CONTINUITY AT ALL

SITES.
6.1.
Connect Ethernet testers to the circuit under test.
6.2.
Check end-to-end IP circuit continuity.
TEST EQUIPMENT:
Ethernet TESTER.
REQUIREMENT:
Traffic continuity per channel plan.
47 Passed:
Yes____
No____
COMMENTS:
________________________________________________________________________
INITIALS:
7.
SYSTEMS INTG. TECH.
CUSTOMER REP.
LONG TERM BER TEST

7.1.
Restore all connections.
7.2.
Set RF paths to nominal level (about 45 dBm TOR).
7.3.
Set PORTAL BER counter for the circuit(s) under test.
7.4.
Run the test for at least 12 HRS.
TEST EQUIPMENT: INTERNAL BER TESTER
48 CIRCUIT #
50
49 Date/Time
51
K-15

RFP 142842TM
COMMENTS:
________________________________________________________________________
_
INITIALS:
SYSTEMS INTG. TECH.
CUSTOMER REP.
END OF DAY 1
K-16

RFP 142842TM
8.
LONG TERM BER TEST RESULT

8.1.
Check BER result for bit error(s) and bit-error-rate. There should not be any
other error(s), i.e. SL, FL.
8.2.
Record results
REQUIREMENT:
Nx10E-12 where N is equal to the number of radio hops.
RESULT:
CIRCUIT #
DURATION
ERRORS
BER
Date/Time
52
53
54
55
56
57 Passed:
Yes____
No____
COMMENTS:
________________________________________________________________________
INITIALS:
9.
CUSTOMER REP.
SYSTEMS INTG. TECH.
SPACE DIVERSITY RECEIVER SWITCH OPERATION

9.1.
Using Portal or Provision NMS, switch to off-line RAC or remove on-line RAC
unit.
9.2.
Observe switching to the other receiver.
9.3.
Using Portal or Provision NMS, switch to off-line DAC or remove on-line DAC.
9.4.
Observe switching to the other receiver.
9.5.
Restore to normal operation.
TEST EQUIPMENT: BER TESTER

REQUIREMENT:
Traffic continuity after switching occurs.
NODE(S) TESTED:
______________________________________________________
58 Passed:
Yes____
No____
K-17

RFP 142842TM
COMMENTS:
________________________________________________________________________
INITIALS:
SYSTEMS INTG. TECH.
CUSTOMER REP.
K-18

RFP 142842TM
10. DAC GE CARD ETHERNET THROUGHPUT TESTING

10.1. This test attempts to find the highest rate at which the DUT can forward
frames without a loss. It uses a simple algorithm to choose rates between the
previous rate and a new rate; if a port drops frames, it throttles to a lower
rate, and if a port doesnt drop any frame, then it throttles to a higher frame.
For throughput test, the following parameters will be used:
10.1.1. Initial rate of 100% of maximum DUT Data rate
10.1.2. Maximum rate of 100% of maximum DUT Data rate
10.1.3. Minimum rate of 50% of maximum DUT Data rate
10.2. Run test for 64 to 1518 packet sizes
10.3. Record results
Frame size used

(byte)
Typical Expected
Throughput
64
92%
1518
92%
Passed Rate
Packets/Sec
PASS if the throughput for each packet size is consistent with the allocated
bandwidth, FAIL otherwise (There is no PASS / FAIL criterion for RFC2544).
TEST EQUIPMENT: ETHERNET TESTER
REQUIREMENT:
bandwidth.
59 Passed:
Typical Expected Throughput is 92% of allocated
Yes____
No____
COMMENTS:
_________________________________________________________________
_____
INITIALS:
SYSTEMS INTG. TECH.
CUSTOMER REP.
K-19

RFP 142842TM
11. CONFIGURATION AND MANAGEMENT
Demonstrate operation of PC based configuration and diagnostics tool PORTAL:

11.1. Verify configuration functionality.
11.2. Verify control functionality.
11.3. Verify alarm reporting capabilities.
11.4. Demonstrate diagnostic futures.
60 Passed:
Yes____
No____
COMMENTS:
________________________________________________________________________
INITIALS:
SYSTEMS INTG. TECH.
CUSTOMER REP.
K-20

RFP 142842TM
12. PROVISION NMS

12.1. Verify set-up and configuration of Provision NMS.
12.2. Verify IP addresses and IP connectivity of NEs by causing alarms or pinging.
12.3. Verify NMS system interoperation:
12.3.1. Generate events in the NE(s) and observe results in NMS.
NODE(S)/EVENT(S) VERIFIED:
__________________________________________________________
_______
From NMS, change the configuration of NE(s). Verify the change. Put
NE back to original configuration.
NODE(S)/CONFIGURATION(S) VERIFIED:
61
62 Passed:
Yes____
No____
COMMENTS:
________________________________________________________________________
INITIALS:
SYSTEMS INTG. TECH.
CUSTOMER REP.
K-21

RFP 142842TM
Factory Acceptance Microwave

Based upon the successful completion of the Factory Acceptance Test Plan,
Customer hereby:
Grants Acceptance
Grants Conditional Acceptance, subject to the punch-list items noted in
Punch-list Items below.
Customer Representative
Airbus DS Communications Representative
Signature
Signature
Printed name and title
Date
Date
K-22

RFP 142842TM
Punch-List Items
Punch-list Items:
#
Item Description
Anticipated
Completion
Date
1
2
3
4
5
Remarks:
K-23

RFP 142842TM
Punch-list Verification:
The undersigned hereby certify that all items on the punch-list have been
completed.
Signature
Signature
Date
Date
K-24

RFP 142842TM
DC Power Plant Factory Acceptance Test Plan (DRAFT)

DCPLANT_OPER_10 DC Power Plant Normal Operation
Sheet
DCPLANT_OPER_10
Feature
DC Power Plant Operation
Initial Conditions
DC Plant online
Batteries on float charge
Equipment load connected
Step
1
5
6
8
9
10
11
12
Description
Verify DC Power Plant is operating
normally and no faults are active on the
system controller.
Using a calibrated VOM verify the output
voltage and polarity is correct for an
operation of the -48VDC system
Using a calibrated VOM verify the float
charge voltage across each of the
installed battery strings.
Verify proper grounding of the device and

that the return rail / buss bar has been
ground referenced properly.
If equipped with an IP-enabled controller
establish connectivity and verify the
integrated web interface is available.
Verify programmed configuration matches
physical configuration of the DC Plant
Verify SNMP alarming configuration is
correct.
Verify SNMP Trap is sent on alarm
condition. Trigger a battery string fault by
OPENING a battery string breaker.
Return the DC Plant to normal operation
by CLOSING the battery string breaker.
system controller.
Test battery bypass operation by
OPENING all battery string breakers.
Return the DC Plant to normal operation
by CLOSING all battery string breakers.
Purpose
DC Power Plant Normal Operation
Means
Direct Measurement / Observation
Expected Results
No faults indicated by the controller
Measured Output Voltage:
VDC (- source) rail to ground:
VDC (+ return) rail to ground:
Measured String Voltage:
VDC reading of battery string 1:
________
________
________
________
________
Grounding installed and properly terminated.
WebGUI is accessible via the network.

Configuration is correct and valid for the site.
SNMP read/write strings are correct
SNMP server address has been entered and
is correct.
SNMP alarm events have been set
Verify an SNMP trap is sent to the Network
Monitoring System for the battery string fault.
Acknowledge and clear the alarm from the
Network Monitoring System.
No faults indicated by the controller.
Verify that with the battery strings
disconnected that the DC Plant still provides
voltage to the equipment load.
Acknowledge and clear the alarm from the
Network Monitoring System.
K-25

RFP 142842TM
Step
13
14
Description
Verify the DC Power Plant is operating
system controller.
Record results and proceed to next
procedure.
*** END OF TEST ***
Comments:
Expected Results
Record PASS / FAIL Results
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-26

RFP 142842TM
DCPLANT_OPER_20 DC Power Plant Generator Holdover

Sheet
DCPLANT_OPER_20
Feature
Generator Holdover
Initial Conditions
DC Plant online
Step
1
Description
system controller.
Perform an ATS initated generator test
with load transfer by performing the
following;
1) Set the ATS to transfer the load

during test
2) Using a calibrated VOM monitor the
output voltage of the -48VDC Power
Plant
3) Initiate the ATS initated generator
test with load transfer.
Record results and proceed to next

procedure.
*** END OF TEST ***
Comments:
Purpose
DC Plant Generator Holdover
Means
Direct Measurement / Observation
Expected Results
Verify that there is no interruption of output

power from the DC Plant as the ATS
switches the load between the utility source
and the generator (transfer) and when the
load is transferred backed to the utility
source at the completion of the test cycle (retransfer).
Transfer Test Result:
Re-transfer Test Result:
________
________
(expectation is no power interruption to the

equipment load PASS / FAIL)
Record PASS / FAIL Results
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-27

RFP 142842TM
DCPLANT_LOAD_10 DC Plant Load Test

Sheet
DCPLANT_LOAD_10
Feature
DC Plant Load Test
Initial Conditions
DC Plant online
Step
1
Description
Connect the load bank to the DC Power
System output to provide 100% rated
design load for the site.
OPEN all supply breakers in the main
electrical panel feeding the rectifier shelf
causing the DC Plant to run from battery.
Purpose
Load Testing of the DC Plant
Means
Direct Observation
Expected Results
Connect the load bank for testing
DC Plant runs from battery

DC Plant Run-Time (PASS/FAIL)
Run the DC Plant at 100% load for 2hour (radio system) and 8-hours
(microwave).
At the completion of the test CLOSE all
supply breakers in the main electrical
panel feeding the rectifiers returning the
DC Plant to Utility supply and allowing
the batteries to be recharged.
*** END OF TEST ***
Comments:
Radio System (2 hours):

_______
Microwave System Only (8 hours): _______
DC Plant returned to Utility Power
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-28

RFP 142842TM
Factory Acceptance DC Power Plant

Customer hereby:
Grants Acceptance
Signature
Signature
Date
Date
K-29

RFP 142842TM
Punch-List Items
Punch-list Items:
#
Item Description
Anticipated
Completion
Date
1
2
3
4
5
Remarks:
K-30

RFP 142842TM
The undersigned hereby certify that all items on the punch-list have been completed.
Signature
Signature
Date
Date
K-31

RFP 142842TM
Factory Acceptance Test Plan (DRAFT)

Purpose of the Document
This document defines the testing to be performed as part of the Factory
Acceptance Test (FAT) plan of the Vesta Radio network for the Counties. This
document defines the FAT, serves as a record of individual result from testing
(pass/fail is marked on this document) and serves as a record of client approval
(signature block at end of document provides a vehicle for approval).
Scope of the Document

These tests include verification of all the staged elements of the Airbus DS
Communications Vesta Radio system. This document is applicable to Airbus DS
Communications software version < Vesta Radio Software Version>.
Applicable Documents
Reference
Document Title
<INSERT APPLICABLE PROJECT DESIGN REFERENCES>
K-32

RFP 142842TM
Abbreviations
BS
CCH
CNH
CSS
DDF
HTTP
IP
IMG
ISSI
LAN
LRA
MGT
NPCD
NMS
RC
RFSS
RS
SC
SGID
SU
SUID
TAGW
TCH
TTM
UC
URL
UDP
WACN
WAN
Base Station
Control Channel
Core Network Host
Customer Service Software (TB5500i configuration tool)
Digital Distribution Frame
Hypertext Transfer Protocol
Internet Protocol
ISSI Media Gateway
Inter Sub-System Interface
Local Area Network
Location Registration Area
Management
Network Personality and Configuration Definition
Network Management System
RFSS Controller
Radio Frequency Sub System
Radio Sites
Site Controller
Subscriber Group IDentity
Subscriber Unit
Subscriber Unit IDentity
Trunked Analog GateWay
Traffic CHannel
Technical and Tactical Management
Universal Controller
Universal Resource Locator
User Datagram Protocol
Wide Area Communication Network
Wide Area Network
NE PAS SUPPRIMER (NUMROTATION DES PLANCHES CHAP 2)
K-33

RFP 142842TM
Information for Factory Acceptance

The testing will be performed in Phases at the conclusion of fabrication activities
as previously agreed with the Counties. The system configuration for testing will
include both the Primary and Backup control equipment along with eight radio
sites along with seven radio consoles. The purpose of this testing is to
demonstrate that the initial system configuration and system fabrication have
been completed satisfactorily prior to releasing the system from factory. System
specific testing will occur as part the System Acceptance Testing once the
system is installed and fully commissioned.
Network Composition
The radio network will be composed of the following network components which
will represent the testing configuration of the System.
Site Name
<SITE 1>
P25 Devices
Tested Configuration
<SITE 2>
<SITE 3>
<SITE 4>
<SITE 5>
<SITE 6>
<SITE 7>
<SITE 8>
<SITE 9>
Software Release
The software release of equipment composing the network presented for
acceptance is:
Component
Software
Version
Provider
Comments
P25 System
Repeater
Console
Network Configuration
The Radio Network will be configured in accordance with the Airbus DS
Communications Network Equipment Configuration document for the project.
Finalized fielded configuration shall be delivered as part of the As-Built
documentation upon Final System Acceptance and the completion of field
optimization.
K-34

RFP 142842TM
Operational Parameters for Acceptance

Subscriber Units and Groups
For the Factory Acceptance Tests the following configuration will be adopted for
testing:
Up to 5 radios
3 Talkgroups
o TG__
o TG__
o TG__
The associated numbering system is as follows:
Radio
T1
T2
T3
T4
T5
SUid
Groups
Remarks
During the tests, all Subscriber Units and group calls are configured under a
single agency.
K-35

RFP 142842TM
P25 Device Acceptance Tests

Installation Test Sheets
INT_RACK_01 Installation Check
Sheet
Feature
INS_DOC_01
Installation check
Initial Conditions
Site staged and wired
Step
1
3
4
5
Description
Check cabinet equipment layout,
accessories and components
Check chassis ground conductors and
equipotential braids tightening,
continuity, marking
Check Power cables tightening,
continuity, polarity, marking
Check Network cables port
assignments, pinout, marking
RF cables tightening, continuity,
marking
Comments:
Purpose
To check that rack installation is compliant
with requirements
Means
Documentation reflective of As-Built
conditions
Expected Results
Cabinets are configured in accordance with
design documents.
Resistivity is less than 1.0 Ohm from point of
connection of the chassis to point of
connection on the equipment rack grounding
bar.
Wiring is in accordance with design
documents.
documents.
documents.
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-36

RFP 142842TM
Commissioning Test Sheets

COM_DOC_01 Documentation Check
Sheet
COM_DOC_01
Feature
Installation documentation
check
Initial Conditions
Site staged and baseline configuration complete
Step
1
2
Description
Check Network Personality and
Configuration Definition document
availability
Check Site folder Commissioning
reports for devices
Comments:
Purpose
To check that site documentation is available
Means
Documentation
Expected Results
In conformity with the Network Equipment
Configuration documents
System configuration reports are complete
and reflective of as-built parameters.
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-37

RFP 142842TM
Integration Test Sheets

Test Sheet List
IP Connectivity Test Sheets
Test Sheet
Title
INT_NMS-IP_10
NMS IP connectivity
INT_SNMP-IP_10
SNMP IP connectivity
INT_CSS-IP_10
CSS IP connectivity
INT_RC-IP_10
RFSS controller IP connectivity
INT_FS-IP_10
File servers IP connectivity
INT_RS-IP_10
Site controller IP connectivity
INT-ISSI-IP_10
IMG IP connectivity
Configuration Check Test Sheets
Test Sheet
Title
INT_SNMP-PARAM_10
Technical supervision declaration on RFSS
INT_RC-PARAM_10
INT_RC-PARAM_20
INT_RC-PARAM_30
INT_RC-PARAM_35
INT_RC-PARAM_40
INT_RC-PARAM_50
RFSS parameters
RFSS Controller parameters
File server parameters
IMG parameters
SNMP technical supervision
Operational RFSS parameters
INT_RS-PARAM_10
INT_RS-PARAM_20
INT_RS-PARAM_30
Radio Site parameters

Cell configuration parameters
Repeater parameters (CSS)
INT_CONS-PARAM_10
Console parameters
Infrastructure Test Sheets

Test Sheet
Title
INT_RC-LIC_10
RFSS controller licensing status
INT_RC-SOFT_10
RFSS software status
INT_RC-BACKUP_10
RFSS backup
INT_RC-SUP_10
RFSS controller supervision
INT_RC-SUP_11
Redundant RFSS controller supervision
INT_RS-SUP_10
INT_RS-SUP_11
INT_RS-SUP_20
INT_RS-SUP_21
INT_RS-SUP_22
Single-site controller supervision

Redundant site controller supervision
Repeater supervision Repeater monitoring in a normal site (CSS)
Repeater monitoring in simulcast or RX voting site (CSS)
INT_ISSI-SUP_10
IMG supervision
K-38

RFP 142842TM
Functional Test Sheets

Test Sheet
Title
INT_RS-REG_10
Nominal registration of a subscriber unit
INT_RS-VOICE_10
Unit-to unit call: radios in single site
INT_RS-VOICE_11
Unit-to unit call: radios in multi-site
INT_RS-VOICE_20
Group call: single site
INT_RS-VOICE_21
Group call: multi-site
INT_RS-DATA_10
Short data service: single site
INT_RS-DATA_11
Short data service: multi-site
INT_RS-FBM_10
Radio site isolated
INT_RS-FBM_11
Radio site failsoft mode
INT_CONS-VOICE_10
INT_CONS-VOICE_20
INT_CONS-DATA_10
Unit-to unit call: Radio / Console

Group call: Radio / Console
Short data service: Radio / Console
K-39

RFP 142842TM
IP Connectivity Test Sheets

INT_NMS-IP_10 NMS IP Connectivity
Sheet
INT_NMS-IP-10
Step
Feature
NMS-RFSS controller IP
connectivity
Purpose
To check that NMS is operational for TTM
use
Initial Conditions
Network operational
Means
NMS
Description
Check IP configuration of computer:
IP address
Expected Results
Subnet mask

Default gateway IP address

2
Check NMS connection to IP backbone by

local ping to the router or switch
Comments:
NMS working and connected to the IP

backbone
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-40

RFP 142842TM
INT_SNMP-IP_10 SNMP Manager IP Connectivity

Sheet
INT_SNMP-IP_10
Step
Feature
SNMP manager-RFSS
controller IP connectivity
Purpose
To check that SNMP manager is operational
Initial Conditions
Network operational
Means
SNMP manager
Description
IP address
Expected Results
Subnet mask
Check SNMP manager connection to IP
backbone by local ping to the router or
switch
Comments:

SNMP manager working and connected to

the IP backbone
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-41

RFP 142842TM
INT_CSS-IP_10 CSS IP Connectivity

Sheet
INT_CSS-IP_10
Step
Feature
CSS connectivity to IP
backbone
Purpose
To check that CSS is operational
Initial Conditions
Network operational
Means
CSS
Description
IP address
Expected Results
Subnet mask


Check CSS connection to IP backbone by
local ping to the router or switch
CSS working and connected to the IP

backbone
Comments:
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-42

RFP 142842TM
INT_RC-IP_10 RFSS Controller IP Connectivity

Sheet
INT_RC-IP_10
Feature
RFSS Controller IP
connectivity with other
equipment
Initial Conditions
Network operational
Step
Description
Check IP configuration of server or both
servers in the case of a redundant RFSS
controller:
IP address
Subnet mask

Check RFSS controller connection to IP
switch
Check RFSS controller connection to
SNMP manager by local ping from the
SNMP manager
Comments:
Purpose
To check that RFSS controller is operational
Means
NMS
SNMP manager
RFSS Controller
Expected Results

RFSS controller working and connected to

the IP backbone
RFSS controller working and connected to
the IP backbone with access to SNMP
manager
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-43

RFP 142842TM
INT_FS-IP_10 File Servers IP Connectivity

Sheet
INT_FS-IP_10
Feature
File servers connected to
the backbone
Initial Conditions
Network operational
Step
Description
Check IP configuration of file servers:
IP address
Purpose
To check that file servers are accessible by
other equipment within the backbone
Means
NMS
SNMP manager
File server
RFSS, Radio Sites, IMG
Expected Results
Subnet mask
1
Corresponding applications
Program server
Backup server
Debug server
Information server
Check that each application can be ping
by the SNMP manager
Comments:

Correct IP connectivity
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-44

RFP 142842TM
INT_RS-IP_10 Site Controller IP Connectivity

Sheet
INT_RS-IP_10
Feature
Site Controller IP
connectivity
Initial Conditions
Network operational
Step
Description
Check IP configuration of server or both
servers in the case of a redundant RFSS
controller:
IP address
Subnet mask
Purpose
To check that site controller is operational
Means
NMS
SNMP manager
RFSS Controller
Expected Results


2
Check Site controller connection to IP

switch
Check Site controller connection to SNMP
manager by local ping from the SNMP
manager
Comments:
Site controller working and connected to the

IP backbone
Site controller working and connected to the
IP backbone with access to SNMP manager
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-45

RFP 142842TM
INT_ISSI-IP_10 IMG IP Connectivity

Sheet
INT_ISSI-IP_10
Feature
IMG controller IP
connectivity
Initial Conditions
Network operational
Step
Description
Check IP configuration of ISSI media
gateway:
IP address
Subnet mask
Purpose
To check that IMG is operational
Means
RFSS controller
Remote RFSS controller
ISSI media gateway
Expected Results


2
Check IMG connection to IP backbone

by local ping from the SNMP Manager
Comments:
Data server working and connected to the IP

backbone
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-46

RFP 142842TM
Configuration Test Sheets

INT_SNMP-PARAM_10 Technical Supervision Declaration on
RFSS
Sheet
INT_SNMPPARAM_10
Feature
Technical supervision
declaration on RFSS
Initial Conditions
Network operational
Step
1
Description
Log on to SNMP manager
Check RFSS Controller site declaration:
Site
IP device(s)
Purpose
To check that network supervision is
configured
Means
SNMP manager
Expected Results
Access to SNMP manager application
RFSS controller application

Check File server declaration
IP device
3
Information server
Debug server

Program server
Check Radio Site declaration
Site
4
IP device
Site controller(s)

Repeater(s)
Check the numbering plan at the TTM:

Group
o Home groups
o Foreign groups

Units
Comments:
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-47

RFP 142842TM
INT_RC-PARAM_10 RFSS Parameters

Sheet
INT_RC-PARAM_10
Feature
RFSS parameter check at
TTM
Initial Conditions
Network operational
Step
1
Description
Connect to the TTM of the RFSS controller with
a technical operator
Check RFSS parameters at TTM
Basic parameters:
WACN id
Purpose
To check that the network configuration conforms:
RFSS
Means
TTM
RFSS Controller
Expected Results
The page is correctly returned
System Id
System Name
RFSS Id
2
RFSS Name
Multicast addresses:
Unit-to-unit call media

Group communication media

Group communication control
Adjacent site information transmission
3
Check frequency plans at TTM

Comments:

Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-48

RFP 142842TM
INT_RC-PARAM_20 RFSS Controller Parameters

Sheet
INT_RC-PARAM_20
Feature
RFSS controller parameter
check at TTM
Initial Conditions
Network operational
Step
1
Description
a technical operator.
Check RFSS Controller parameters at TTM
Cluster:
Name
Information
Subnet mask
Purpose
RFSS controller
Means
TTM
RFSS Controller
Expected Results
The page is correctly returned.

Redundancy arbiter
IP device A:
Name
2
Mac address

IP address
IP device B (if redundancy):
Name
Mac address
IP address
RFSS application:
Type: RFSS controller expected
Name
Comments:
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-49

RFP 142842TM
INT_RC-PARAM_30 File Server Parameters

Sheet
INT_RC-PARAM_30
Feature
File server parameter check at
TTM
Initial Conditions
Network operational
Step
Description
Check File server parameters at TTM
Cluster:
Name
Information:
Subnet mask
Purpose
File server
Means
TTM
RFSS Controller
Expected Results

Redundancy arbiter
IP device A:
Name
Mac address
IP address
Backup server:
Type: Backup server expected
1
Name
IP address
Debug server:
Type: Debug server expected

Name
IP address
Information server:
Type: Information server expected
Name
IP address
Program server:
Type: Information server expected
Name
IP address
Comments:
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-50

RFP 142842TM
K-51

RFP 142842TM
INT_RC-PARAM_35 IMG Parameters

Sheet
Feature
INT_RC-PARAM_40
IMG parameter check at TTM
Initial Conditions
Network operational
Step
Description
Check IMG parameters at TTM
Cluster
Name
Purpose
IMG configuration
Means
TTM
RFSS Controller
IMG
Expected Results
Subnet mask
Redundancy arbiter
IP device A
Name

Mac address
IP address
Application
Type: IMG
Name
IP address
Comments:
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-52

RFP 142842TM
INT_RC-PARAM_40 SNMP Technical Supervision

Sheet
Feature
INT_RC-PARAM_40
SNMP manager availability
Initial Conditions
Network operational
Step
1
2
3
Description
Check SNMP parameter declaration on
Technical management
IP address
Check SNMP manager availability on Technical
supervision
Comments:
Purpose
To check that technical supervision is available
from TTM
Means
TTM
RFSS Controller
Expected Results
Access to SNMP manager login page
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-53

RFP 142842TM
INT_RC-PARAM_50 Operational RFSS Parameters

Sheet
INT_RC-PARAM_50
Feature
Operational RFSS parameter
check
Initial Conditions
Network operational
Step
Description
Check radio declaration needed for tests
Suid
Check Group declaration needed for tests

Groupid
Comments:
Purpose
To check that the network operational parameters
defined for the acceptance tests are ready
Means
TTM
RFSS Controller
Expected Results
In conformity with the parameters defined in
In conformity with the parameters defined in
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-54

RFP 142842TM
INT_RS-PARAM_10 Radio Site Parameters

Sheet
INT_RS-PARAM_10
Feature
Radio Site parameter check at
TTM
Initial Conditions
Network operational
Step
1
Description
Check Site controller parameters at TTM
Cluster:
Name
Information:
Subnet mask
Purpose
Radio site
Means
TTM
One RFSS Controller
Expected Results

Redundancy arbiter
IP device A:
Name
Mac address
IP address
IP device B (if redundancy):
Name
Mac address

IP address
Site:
Type: Site controller expected
Sub-type
Number
Name
IP address
Repeater(s):
Site number
Channel reference
IP address
Comments:
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-55

RFP 142842TM
K-56

RFP 142842TM
INT_RS-PARAM_20 Cell Configuration Parameters

Sheet
INT_RS-PARAM_20
Feature
Cell configuration parameter
check at TTM
Initial Conditions
Network operational
Step
1
Description
Connect to the TTM of the site controller with a
technical operator.
Check cell configuration parameters
LRA ID
Purpose
Site controller
Means
TTM
Site Controller
Expected Results
Maximum of number of PDCHs

UDP ports: traffic and control
Frequency plan
Channels
Channel Reference
CCH recommended or not
Type: VCH only, PDCH only, VCH or PDCH
capable
Implicit or explicit
o Transmission
2
Frequency Plan ID
Frequency
Channel
o Reception (if explicit)

Frequency Plan ID
Frequency
Channel
Radio area
o ID
o Master capable
Adjacent sites
o Cell-ID
Comments:
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-57

RFP 142842TM
INT_RS-PARAM_30 Repeater Parameters (CSS)

Sheet
INT_RS-PARAM_30
Feature
Repeater parameter check at
CSS
Initial Conditions
Network operational
Step
1
Description
Connect to each repeater using CSS
Check for each Repeater parameters by radio
site with CSS
Identification:
Repeater alias ID
Purpose
Repeater
Means
CSS
Repeater
Expected Results
The repeater is accessible on CSS
Repeater ID
Radio configuration:
RF repeater Tx frequency
Tx channel identifier
RF repeater Rx frequency
2
Rx channel identifier
IP configuration:
Hostname

IP address
Receiver number
Subnet mask
NTP server address
Failsoft information
Alarm configuration
Comments:
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-58

RFP 142842TM
Infrastructure Test Sheets

INT_RC-LIC_10 RFSS Controller Licensing Status
Sheet
INT_RC-LIC_10
Feature
RFSS controller software
licensing status
Initial Conditions
Network operational
Step
1
2
Description
Go into the license menu
Verify that:
The global status is "System operational" on
the TTM
The license dimension items are in
conformity with network declaration
The license feature items are in conformity
with project needs
Comments:
Purpose
Verification of License status for the RFSS
Means
TTM
RFSS Controller
Expected Results
License menu is correctly displayed
The global status displayed is "System operational."

License dimension and feature in conformity with
project information: Network Equipment
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-59

RFP 142842TM
INT_RC-SOFT_10 RFSS Software Status

Sheet
Feature
INT_RC-SOFT_10
RFSS software management
Initial Conditions
Network operational
Step
1
2
Description
Connect to the SNMP manager
Check Activated software at SNMP manager
Comments:
Purpose
Verification of a software version in the program
server
Means
SNMP manager
Expected Results
Verify that the software version present in the list is
in conformity with the list of software given in the
Network Equipment Configuration documents
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-60

RFP 142842TM
INT_RC-BACKUP_10 RFSS Backup

Sheet
Feature
INT_RC-BACKUP_10
RFSS backup
Initial Conditions
Network operational
Step
1
2
Description
On RFSS technical configuration form, on
RFSS controller TTM, click on "Backup button"
After 2mns, on backup server, on backup

frame, click on the "current" menu
On the "Current" frame, click on "Save" button.

Save file "backup.zip" on operator's PC
Comments:
Purpose
Backup of RFSS configuration (tactical + technical,
RFSS controller + site controller).
Means
TTM
RFSS Controller
File server: Backup server, information server
Expected Results
Verify the content of the ticket on the TTM
connected to the information server
Verify that the RFSS controller and the site
controllers backup files appear in the displayed list
with today's date and time
Backup file is on the operator's PC containing files
displayed in backup server's "current" frame
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-61

RFP 142842TM
INT_RC-SUP_10 RFSS Controller Supervision

Sheet
Feature
INT_RC-SUP_10
Initial Conditions
Network operational
Step
1
2
Description
Verify that the global status is "System
operational" on the SNMP manager
Reset the IP device of the RFSS controller

server with TTM technical management
Automatic re-start of the RFSS controller server
5
6
7

operational" at the SNMP manager
Verify that RFSS controller objects are in
nominal state at SNMP manager
Comments:
Purpose
Verification of operational state changes for the
RFSS controller
Means
TTM
SNMP manager
RFSS Controller
Expected Results
The RFSS is displayed as operational
Site, IP device and application objects are not in
nominal state Checked on SNMP manager
supervision
Check that no blocking alarms present at re-start
issue, pooling alarm could be present
The OK global status is displayed
Site, IP device, and application objects are in
nominal state
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-62

RFP 142842TM
INT_RC-SUP_11 Redundant RFSS Controller Supervision

Sheet
Feature
INT_RC-SUP_11
Initial Conditions
Network operational
Step
1
2
3
4
5
6
7
Description
operational" at the SNMP manager
Reset the RFSS controller server with TTM
technical management
operational" on the TTM
Comments:
Purpose
RFSS controller
Means
TTM
SNMP manager
RFSS Controller (IP device A & B)
Expected Results
Site, IP device and application objects are in
nominal state
The RFSS controller is active on the previous
stand-by IPRC
Site, IP device and application objects are in
nominal state
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-63

RFP 142842TM
INT_RS-SUP_10 Single-Site Controller Supervision

Sheet
INT_RS-SUP_10
Feature
Site controller supervision:
single
Initial Conditions
Network operational
Step
1
2
3
4
Description
technical operator
On SNMP manager, check Radio site and IP
device status and alarms
On the TTM technical management, reset the
site controller (IP device)
After re-start of the site controller, check the
radio site status
Comments:
Purpose
Verification of operational state changes for the site
controller
Means
TTM
Repeater
RFSS
Radio sites
SNMP manager
Expected Results
Radio site and IP device are seen OK on the SNMP
manager without any alarm
An SNMP trap notification of the Site Controller is
seen on the SNMP Manager
Radio site and IP device are seen OK on the SNMP
manager without any alarm
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-64

RFP 142842TM
INT_RS-SUP_11 Redundant Site Controller Supervision

Sheet
INT_RS-SUP_11
Feature
Site controller supervision:
redundant
Purpose
Verification of operational state changes for the site
controller
Initial Conditions
Means
TTM
SNMP manager
RFSS
Radio sites
Network operational
Site Controller A: Active
Site Controller B: Stand-by
Step
1
Description
At the SNMP manager, check Site controller
status and alarms
Expected Results
Site controller A is seen OK on the SNMP manager
without any alarm
IP device A: Active
IP device B: Stand-by
On the TTM, select the button "Disable" for site

controller A

status and alarms

Site controller B is seen OK on the SNMP manager
without any alarm
IP device A: Stand-by
IP device B: Active l
On the TTM, select the button "Enable" for site

controller A

At the SNMP manager, check Site controllers

status and alarms
IP device B: Active
Site controller B is seen OK on the SNMP manager
without any alarm
IP device: Active
Comments:
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-65

RFP 142842TM
INT_RS-SUP_20 Repeater Supervision

Sheet
INT_RS-SUP_20
Feature
Repeater supervision
Initial Conditions
Network operational
Step
1
2
3
4
5
6
Description
technical operator
Connect to the CSS on the repeater
status and alarms
On the CSS, put the repeater in "standby"
mode
On the CSS, put the repeater in "running"
mode
Check the RF repeater configuration (CCH,
VCH) at the SNMP manager
Comments:
Purpose
repeater
Means
TTM
CSS
Repeater
SNMP manager
Expected Results
Site controller is seen OK on the SNMP manager
without any alarm
The repeater state "standby" is displayed on the
SNMP Manager
The repeater state "running" is displayed on the
SNMP Manager
Verify that the RF repeater type is CCH or VCH
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-66

RFP 142842TM
INT_RS-SUP_21 Repeater Monitoring in a Normal Site (CSS)

Sheet
Feature
INT_RS-SUP_21
Repeater monitoring (CSS)
Initial Conditions
Network operational
Step
1
2
3
Description
technical operator
Connect to the CSS on the repeater
On the CSS, check the status of the channel
group (menu "Monitoring/Channel
Group/Status")
Comments:
Purpose
Verification of repeaters status within a normal radio
site
Means
TTM
CSS
Normal radio site controller
Repeaters
Expected Results
All repeaters status are displayed
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-67

RFP 142842TM
Functional Test Sheets

INT_RS-REG_10 Nominal Registration
Sheet
INT_RS-REG_10
Feature
Nominal registration of a
subscriber unit
Initial Conditions
Network operational
All radios and corresponding groups are declared in the
tactical database
Step
1
2
Description
Switch on the P25 standard radios declared in
the subscriber database of the RFSS controller
After each full registration attempt, the RFSS
controller sends a registration ticket to the
Information Server
Comments:
Purpose
To check the registration of a subscriber unit under
the coverage of the radio site
Means
TTM
RFSS Controller
Information Server
Radio site: Site controller, repeater
2 Radios
Expected Results
The SUs are registered within the network
Check that after a few minutes the tickets'
Mobility/Affiliation become available at the
Information server's TTM
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-68

RFP 142842TM
INT_RS-VOICE_10 Unit-To-Unit Call: Single Site

Sheet
Feature
INT_RS-VOICE_10
Unit-to-unit call: single site
Initial Conditions
Network operational
Two radios, RA1 and RA2, are authorized, registered
and affiliated to two different groups on the same radio
site
Step
1
Description
Perform a unit-to-unit call between RA1 and
RA2
RA2 answers the call
Stop PTT on RA2, then PTT on RA1
Stop PTT on RA1, then PTT on RA2
After release of the unit-to-unit call

Comments:
Purpose
To check a successful setup of a unit-to-unit call
from radios registered on the same radio site
Means
TTM
SNMP manager
RFSS Controller
2 Radios
Expected Results
Unit-to-unit call is established
Verify that a listener using RA1 can understand the
message transmitted by RA2
message
message
Unit-to-unit call is released
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-69

RFP 142842TM
INT_RS-VOICE_20 Group Call: Single Site

Sheet
Feature
INT_RS-VOICE_20
Group call: single site
Purpose
To check a group call activation with two radios
registered on the same radio site
Initial Conditions
Means
TTM
SNMP manager
RFSS Controller
IMG
2 Radios
Network operational
on the same radio site and have selected the same
talkgroup GRP1 (this group is declared with a non-0
hang-time value)
Step
1
2
3
Description
Initiate a group call with SU1
Press the push-to-talk button on SU1
Wait for the indication that a TCH is available
(beep on SU1)
Talk
Release the PTT
Press the push-to-talk button on SU2 before
the end of the hang-time, then transmit a voice
message
Comments:
Awaited Results
Verify that a listener using SU2 can understand the
message
None
Verify that a listener using SU1 can understand the
message
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-70

RFP 142842TM
INT_RS-DATA_10 Short Data Service: Single Site

Sheet
INT_RS-DATA_10
Feature
Short data service: radio to radio
in single site
Initial Conditions
Network operational
on the same radio site
Step
1
Description
RA1 sends a short message request to RA2
Comments:
Purpose
To check a short message sent successfully from
radio to radio
Means
TTM
SNMP manager
RFSS Controller
2 Radios
Expected Results
The short message request is successfully
delivered to the target RA2
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-71

RFP 142842TM
INT_RS-FBM_10 Radio Site Isolated

Sheet
INT_RS-FBM_10
Feature
Site Controller isolated from the
RFSS controller
Initial Conditions
Network operational
The system is running under normal conditions, and the
site is operational with at least one RFR in CCH mode
and another in TCH mode
An SU authorized and registered on the site
Step
Description
Unplug the IP connection from the radio site to

the RFSS controller on the IP switch
Note: Take care to keep IP connections from
site controller and repeaters
The link is established.

Comments:
Purpose
To check the behavior of a site controller that has
become isolated from the RFSS controller
Means
TTM
SNMP manager
RFSS Controller
Radio site: IP switch, Site controller, repeater
2 Radios
Expected Results
No operational impact on the RFSS controller. The
SC isolated from the RC is still running, and the site
is operational
Verify that the site trunking indication is present on
the radio display
No operational impact.
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-72

RFP 142842TM
INT_RS-FBM_11 Radio Site Failsoft Mode

Sheet
Feature
INT_RS-FBM_11
Radio site failsoft mode
Initial Conditions
Network operational
Two radio, RA1 and RA2, are authorized, registered on
the radio site
Step
1
Description
Stop the IP switch where the site controller and
repeaters are connected
Do not do anything on the radios
Talk between RA1 to RA2
Restart the IP switch
Do not do anything on the radios

Comments:
Purpose
To check that in case of failure between site
controller and repeaters, repeaters and radios
automatically go to failsoft mode
Means
RFSS Controller
Radio site: IP switch, Site controller, repeater
2 Radios
Expected Results
Verify that repeaters on site are in failsoft mode
Verify that the radios detect and display the failsoft
indication
message transmitted by RA1
After the time taken for the switch to reboot, the
trunking function returns
Verify that the site trunking indication is present on
the radio display
Pass/Fail
Customer
Representative
Airbus DS
Communications
Representative
K-73

RFP 142842TM
RF and RF Component Verifications

Test Process
RF tests will follow the sequence described below:
BEGINNING OF TEST
Accessory Normalization
Transmit Frequency Test
Transmit Power at Top of Rack Test
PA Output Level Check
Receive Sensitivity Test
END OF TEST
K-74

RFP 142842TM
RF Tests
Presentation of Measurements
Calibration
All equipment used for test or measurement will have a valid calibration
All accessories utilized are as part of the measurement procedure will be
normalized
Transmission Tests
Utilize LMR Master (option 0019) or equivalent
Utilize normalized accessories
Frequency Alignment
Utilize LMR Master or equivalent
Utilize external 10 MHz reference
Receive Tests
Utilize LMR Master with High Resolution Signal Generator or equivalent
Utilize external 10 MHz reference
Preparation
Equipment and cabling required for testing:
Calibrated LMR Master S412E with:
o Option 0019 High Accuracy True RMS Power Meter
o Modification ND75293 or ND75292 (High Resolution Sig Gen)
50 Test Cables (labeled and easily identified)
30 dB Directional Coupler
40 dB/100 W Attenuator
50 ohm/300W Termination
Adapters as required
Note: Verify all cable connections to ensure proper installation prior to the start of
testing.
K-75

RFP 142842TM
Test Methods
The actual measurement location for the tests will vary. The chart below shows
the measurement location for each of the data points listed in the individual site
tables.
Measurement Data Point
Measurement Location
TX Frequency
Top of Rack
Top of Rack Power
Top of Rack
TX Power
Repeater PA
RX Sensitivity
Repeater (Web Interface)
Note: Top of Rack refers to the connection point where the combined RF is
applied to the transmit antenna system. The RF Engineer will identify this
location prior to testing.
Accessory Normalization
This normalization procedure applies to all cables, adapters, couplers, and
attenuators to be used during the FAT.
Cable, Adapter and Attenuator Correction Factor

Normalize, at the operating frequency, all accessories used during this procedure
including, but not limited to, the following:
Cables
Attenuators
Cables with adapters
Directional Couplers
Procedure
1. Label all devices to be used during the FAT distinctly (C1=Cable 1,
A1=Attenuator 1)
2. Connect the equipment as shown ensuring the Signal Generator port is in
standby
K-76

RFP 142842TM
Anritsu S412E LMR Master

(Top View)
TO
10 MHz
Reference
External
Reference
In
VNA
Port 1
External
Trigger
In
VNA
Port 2
Audio In
RF In
Signal
Generator
Out
GPS
DC Input
Device Under Test
3. Set the signal generator to:

Frequency 852.00 MHz
Output Level -10 dBm
4. Record the RF Power input level in the table below
5. Subtract the power meter indication from -10 dBm output level and record
that value in the Correction Factor (CF) column of the table below.
6. Repeat these steps for all Cables, Attenuators, and Cables with adapters to
be used during the remainder of this procedure.
Device
Sig Gen Out

(dBm)
RF Input
(dBm)
CF (dB)
C1
C2
A1
C1+A1+C2
K-77

RFP 142842TM
Transmit Frequency
1. Place the S412E in P25 mode
2. Utilizing the Web Interface access the station under test
3. Place the TB5500i under test to STANDBY mode
4. Connect equipment as shown below

(Top View)
TO
10 MHz
Reference
External
Reference
In
VNA
Port 1
External
Trigger
In
VNA
Port 2
Audio In
To Top of Rack
Transmit Connection
RF In
Signal
Generator
Out
GPS
DC Input
Attenuator
40 dB / 100 W
5. Place the TB5500i under test to CW mode and energize the output
6. Record the Frequency indicated on the S412E in the data sheets provided
7. Return the TB5500i to STANDBY mode and return the connections to their
original configuration
8. Repeat steps 2 through 6 for the remaining TB5500i to be tested
Transmit Power at Top of Rack

1. Set the S412E to High Accuracy Power Meter mode
3. Ensure all stations under test are in STANDBY mode
CAUTION: Failure to connect the S412E to the coupled port of the directional coupler properly
can result in catastrophic damage to the S412E and power sensor unit.
K-78

RFP 142842TM

(Top View)
TO
10 MHz
Reference
External
Reference
In
VNA
Port 1
External
Trigger
In
VNA
Port 2
Audio In
RF In
Signal
Generator
Out
GPS
DC Input
External
Power
Sensor
To Top of
Rack
Connection
Attenuator
40 dB / 100 W
5. Set the TB5500i under test to CW modulation

6. Energize the TB5500i output
7. Verify the Top of Rack power equal to the value indicated in the data sheet
provided. If the level is within tolerance go to Step 8
8. If the level measured is not within tolerance
Adjust the TB5500i output power level so the level measured at the Top of
Rack is equal to the value indicated in the data sheet provided
9. Record the power level on the data sheets provided
10. Return the TB5500i under test to STANDBY
11. Repeat steps 4 8 for each station in the site
PA Output Level
Note: The levels recorded during the following steps are for information only. DO NOT adjust the
PA output levels.
1. Set the S412E to High Accuracy Power Meter mode
K-79

RFP 142842TM

3. Ensure all station under test is in STANDBY mode
4. Connect equipment as shown below:
CAUTION: Failure to connect the S412E to the coupled port properly can result in catastrophic
damage to the device.

(Top View)
TO
10 MHz
Reference
External
Reference
In
VNA
Port 1
External
Trigger
In
VNA
Port 2
Audio In
RF In
Signal
Generator
Out
GPS
DC Input
TB 5500i (Rear View)
External
Reference
Receive
In
External
Power
Sensor
PA
Output
Attenuator
40 dB / 100 W
5. Set the TB5500i under test to CW modulation

6. Energize the TB5500i output
7. Record the PA Output level indicated on the data sheet provided.
8. Return the TB5500i under test to STANDBY
9. Repeat steps 4 8 for each station to be tested
Receive Sensitivity
Verify with the RF Engineer the configuration of the receive antenna system
without a Tower-Top Amplifier (TTA) and perform the appropriate test.
K-80

RFP 142842TM
Receive Sensitivity (No TTA)

1. Set the S412E to High Accuracy Signal Generator mode with the signal
generator output to STANDBY
3. Ensure all stations under test are in STANDBY mode

(Top View)
TO
10 MHz
Reference
External
Reference
In
VNA
Port 1
External
Trigger
In
VNA
Port 2
Audio In
RF In
Signal
Generator
Out
GPS
DC Input
To Top of Rack
Receive Connection
5. Set the S412E

Output to -110 dBm
Energize the output
6. Slowly decrease the output level of the S412E until the TB5500i Web
interface indicates a BER of 5%
7. Record the level in the data sheet provided
8. Repeat steps 4 6 for each TB5500i to be tested.
K-81

RFP 142842TM
RF DATA Sheet
Site
Name
Repeater
Combiner
Test
Attribute=
Benchmark
Attribute=
Actual
Pass /
Fail
RNE
Review
TX Frequency Test Results

<Site
Name>
<#>
<#>
Tx Freq.
<TX freq. for channel>
TX Power at Top-of-Rack (TOR) Test Results

<Site
Name>
<#>
<#>
Top of
Rack o/p
per ch
<TOR Output Power>
PA Output Level Test Results

<Site
Name>
<#>
<#>
TX Power
<Design Output
Power Level>
K-82

RFP 142842TM
Site
Name
Repeater
Combiner
Test
Attribute=
Benchmark
Attribute=
Actual
Pass /
Fail
RNE
Review
RX Sensitivity Test Results

<Site
Name>
<#>
<#>
TX Power
<Design Receive
Sensitivity Level>
K-83

RFP 142842TM
Factory Acceptance
Customer hereby:
Grants Acceptance
Signature
Signature
Date
Date
K-84

RFP 142842TM
Punch-List Items
Punch-list Items:
#
Item Description
Anticipated
Completion
Date
1
2
3
4
5
Remarks:
K-85

RFP 142842TM
The undersigned hereby certify that all items on the punch-list have been
completed.
Signature
Signature
Date
Date
K-86

RFP 142842TM
Draft Coverage Acceptance Test Plan (CATP)

This Draft Coverage Acceptance Test Plan (CATP) outlines the methodology that
Contractor will follow to verify that the proposed coverage meets the Counties
coverage objectives. During the project, Contractor will work closely with the
Counties to finalize all aspects of the CATP.
Contractors test methodology complies with TSB-88.3-C and is compliant with
the Counties requirements.
This draft CATP is comprehensive, quantifies the coverage area, defines the
coverage requirements, explains how the coverage area will be tested, and
ensures that all parties understand their responsibilities. The final CATP serves
as a record of test results and serves as a method of approval.
Coverage verification is demonstrated through automated testing and subjective
Delivered Audio Quality (DAQ) testing by Contractors personnel.
Representatives of the Counties witness coverage acceptance test performance.
The draft CATP outlines the test methods for the following scenarios:
Automated (objective) drive testing
Outdoor (subjective) DAQ Testing for each in-building zone
Automated Drive Testing

To perform portable at the hip and simulated in-building automated testing, a
drive test vehicle with automatic collection and electronic location hardware is
used. Correction factors are applied, through the use of attenuators, to simulate
portable on the hip and in-building operations. The drive test team will then drive
throughout the service area following a predetermined route, agreed upon by
Contractor and the Counties, collecting RSSI and BER levels and GPS data. At
the conclusion of the data collection, the data will then be converted to a usable
format and analyzed to determine if the system performance goals have been
met.
Note: Radio Coverage Verification Testing is to be conducted during full foliage

conditions in the Counties.
Outdoor DAQ Testing

To perform outdoor DAQ testing within the corresponding in-building zone, a
portable radio equipped with attenuators (to simulate building loss) along with a
half (1/2) wave antenna positioned at hip level with remote speaker, is used to
perform non-automated subjective pass/fail evaluation of the audio transmissions
in the designated Grid/Tile location throughout each building zone. The results
are based on team consensus of the test transmissions as compared to the
Channel Performance Criteria stated as above. The test team performs either a
stationary or moving talk-out/talk-back test using portable radios provided by the
Counties and communicating with the dispatchers or each other. The audio
quality is rated and the result is recorded in the DAQ data sheet.
K-87

RFP 142842TM
Note: Radio Coverage Verification Testing is to be conducted during full foliage

conditions in the Counties.
Test Objectives
Using TIA/EIA TSB-88.3-D and the requirements of this Agreement, coverage
requirements consist of:
System shall provide a minimum Delivered Audio Quality (DAQ) radio signal
of DAQ 3.4 (BER 2%) to portables operating outdoors, and inside of 15 dB, 20
dB, and 30 dB buildings
97% of defined service area within the boundaries of Sarasota and Manatee
Counties with minimum DAQ3.4 @ 2.0% BER for Portable with a half (1/2)
wave antenna at hip level.
95% of defined service area within the four (4) in-building service boundaries
with a minimum of DAQ3.4 @ 2.0% BER for Portable with a half (1/2) wave
antenna at hip level.
Contractor shall meet the following in-building service boundaries as described
and depicted in Exhibit H, Coverage Description and Contract Maps:
15 dB in-building areas in Sarasota and Manatee County
Special 20 dB in-building coverage area for Sarasota and Manatee County
(University Pkwy and Airport)
Overview of Test Procedure

Automated Objective Drive Test
To perform all automated objective radio coverage testing (portable on street at
hip or portable in-building) Contractor will:
Utilize a drive test vehicle equipped with a mobile radio and automated data
collection equipment
Apply 10 dB attenuation to the mobile to simulate a portable worn at the hip,
and apply additional attenuation to simulate building penetration loss as
follows:
o 15 dB in-building boundary: 10 dB+15 dB =25 dB
Drive throughout the defined service area collecting RSSI, BER, and GPS
data
Process the data acquired and converting the data into a usable format for
presentation as the final test results for the CATP
K-88

RFP 142842TM
These tests measure the audio quality through Bit Error Rate (BER)
measurements and demonstrate whether the audio quality meets or exceeds the
DAQ standards specified. At the conclusion of verification testing, if the DAQ
quality standard is not met, a modification plan to bring performance within
specified levels will be proposed.
DAQ Subjective Test

To perform the DAQ test, the test team performs either a stationary or moving
talk-out/talk-back test using portable radios provided by the Counties and
communicating with the dispatchers and/or each other. The audio quality is rated
and the result is recorded in the DAQ data sheet.
A tile must be rated as having a DAQ of 3.4 or better to be considered a PASS. If
a test point is rated less than DAQ 3.4, the tester may move anywhere within 6
feet of the original test point and repeat the test. If the second attempt is
successful, then the test point is deemed a PASS. If the second attempt is also
unsuccessful then the test location will be considered a failure.
In the event both automated and DAQ testing has been performed for a test point
or grid, the DAQ test result will take precedence over the automated testing
result.
CATP Process
The CATP process consists of the following tasks:
Analysis of network performance and parameters
Development of Drive Test Routes and DAQ test plan
Performing the drive tests and DAQ tests
Analysis of results
Optimization of network performance based on site acceptance and
performance testing results*
Formal reporting of the drive test results
Note: Network optimization is not part of the CATP drive testing and requires the
site configuration to be completed and the site acceptance performed. The
analysis of the results will lead to network optimization recommendations, if
necessary.
Prerequisites of the CATP Process

Initial Information
Prior to the execution of the coverage testing, Contractor will ensure the System
is working properly, alarm free, and configured in accordance with the System
design parameters. In addition, the following information must be obtained prior
to commencement of any testing:
System Key
Frequency Plan
K-89

RFP 142842TM
Repeater/system alarm status

All backhaul operation and connectivity are presented without any alarm
Prior to commencement of drive testing all sites within the drive test area must be
verified as working properly, alarm free, and configured in accordance with the
System design parameters.
Dedicated Test Talkgroup

A dedicated test talkgroup shall be used during the coverage acceptance testing
and configured to allow operation throughout the whole coverage area under
test.
Human Resources
Note: It is dangerous and in many areas illegal to drive a vehicle and operate a
computer at the same time. It is for this reason no drive testing is permitted by
Contractors personnel without a dedicated driver and a dedicated equipment
operator present in the drive test vehicle.
Table 1
Required Human Resources
Personnel
(per test team)
One engineer per
drive test team
Driver per Drive
Test Team
Airbus DS Communications
Witness
Sarasota - Manatee County
Deployment
Manager
Console Operator
(Dispatcher)
Organization
Responsibility/Function
Data Collection and Navigation during the
drive test
Operation of the motor vehicle during the drive
test
Witness the drive testing is executed in
accordance with CATP
Airbus DS Communications representative on
the Monitor team and as required during the
drive testing
Customer representative on the Monitor team
during testing
These human resources are typically segregated by their job functions as

follows:
Monitor Team
Dispatcher or other person Provided by Sarasota - Manatee County
Test Monitor Third party, such as the Customers Consultant
Test Monitor Provided by Airbus DS Communications (Optional)
Observers Provided by Sarasota - Manatee County (Optional)
Field Teams
Driver Provided by Sarasota - Manatee County (typically a representative
from the Police)
One Engineer per Field Team Provided by Airbus DS Communications
K-90

RFP 142842TM
Record Keeper Third party, such as the Customers Consultant

Observers Provided by Sarasota - Manatee County (Optional)
Automated Drive Test Equipment

Contractor shall provide the equipment in Table 2 for the execution of the
automated Drive Test. Due to variations in test and peripheral equipment,
Contractor has developed a standard equipment configuration for the execution
of the drive testing. Use of alternative test or peripheral equipment shall not be
allowed.
Table 2
Required Drive Test Equipment
Equipment
Source
Drive Test Vehicle
Navigation Computer and

GPS
STI-9400 or equivalent
and GPS
Test Computer
Tait TM9155 Mobile
Unity Gain, mag. mount
2.15dBi (0dBd) antenna
Notes
Source dependent on mutual
agreement
For drive test route navigation
RSSI data collection and location

tracking
Data storage
RSSI and BER data collection
RSSI signal acquisition
Attenuator Kit
Drive Test Tool Kit
Inverters, jumpers, etc.
To simulate portable on-hip and inbuilding operation

To take case of any issues of
installation, etc. during dive test
To supply AC power as required for
drive test equipment from vehicle
DAQ Test Equipment

The test equipment required for DAQ testing is in Table 3. The Counties will
provide portable radios for use in the coverage tests. The test equipment to be
used should be tested and agreed upon by the Counties and the Contractor.
Table 3
DAQ Testing Equipment
Equipment
Source
Notes
Used to transport the DAQ Remote
Test Team to test locations
Transport Vehicle
A portable with belt

clip and half (1/2)
antenna and remote
speaker
DAQ subjective test
To simulate in-building loss during DAQ

test when general zone testing is
conducted within the corresponding inbuilding zone boundaries
In-line SMA attenuator

(28 dB, 18 dB, 12 dB
and 6 dB)
Source dependent on mutual

agreement
K-91

RFP 142842TM
Drive Test Configuration

The drive test equipment will be configured in accordance with manufacturers
guidelines and Contractors defined test procedure. Attenuators will be
introduced to the antenna system of the Tait TM9155 test radio to simulate body
loss and antenna correction factors for outdoor and indoor operations.
The drive test configuration is illustrated below:
P25 system
Test Equipment Interconnection

GPS Ant.
RX Ant.
Back of the Mobile
Attenuator
GPS
USB Connection
Back of the Computer
Figure 1
Automate Drive Test Configuration
Drive Tests Execution

The test vehicle will collect data in the following manner:
Throughout all accessible tiles within the service area
Evenly distributed samples within each tile (to the maximum possible extent)
K-92

RFP 142842TM
The exact test routes will be determined prior to the drive test and adapted during
the drive test, depending on local constraints. One example is provided below:
Figure 2
Drive Route over Tile Illustration
During data collection along the drive test routes, the test equipment connected
to a mobile and a GPS will continuously acquire the RSSI and Bit Error Rate
(BER) of the channel under test and stamp the recorded measurement with
geographical coordinates.
Outdoor DAQ Tests Configuration and Execution

The portable outdoor DAQ test configuration is illustrated in Figure 3, where the
portable is positioned at belt level with a remote speaker. The portable is
equipped with a half (1/2) wave antenna through an SMA type attenuator
connected to the portable body. When executing general zone coverage testing
an attenuator is selected according to the building zone being tested and as
provided in the following scenarios:
On Street: attenuator value=10 dB
In 15 dB building zone: attenuator value=25 dB
K-93

RFP 142842TM
Half () wave
antenna
SMA type Attenuator
Figure 3
Portable Outdoor DAQ Test Configuration
Manatee
Sarasota
Figure 4
In-Building Zone
For the execution of outdoor DAQ testing, the test team performs either a
stationary or moving talk-out/talk-back test using portable radios provided by the
Counties and communicates with the dispatchers or each other. A tile must be
rated as having a DAQ of 3.4 or better in both directions (field test team to
dispatch and dispatch to field test team) to be considered a PASS. If a test point
is rated less than DAQ 3.4, the tester may move anywhere within 6 feet of the
original test point and repeat the test. If the second attempt is successful, then
the test point is deemed as PASSED. If the second attempt is unsuccessful then
the test location shall be considered FAILED.
K-94

RFP 142842TM
A typical sequence for a DAQ Test initiated by the field test team can be as
follows:
Field test team #1 initiates call: "Field test team #1 to Dispatch operator, Tile
Location X, outdoor environment, in-building zone Y or on street zone, how do
you receive me?"
Dispatch operator answer: "Dispatch operator to Field test team #1, Tile
Location X, Talk Back call test is PASS. And you, how do you hear me?"
Field test team #1: "Field test team #1 to Dispatch operator, Tile Location X,
Talk Out call test is PASS"
Each party then reports the test result in a suitably configured DAQ Test Log
Sheet shown in Table 7, Sample DAQ Test Log Form.
Methodology
This draft CATP is used by Contractor to verify the performance of RF coverage
for public safety land-mobile radio systems. It is based on the signal strength
measurement method and provides an accurate, statistically valid, repeatable,
objective, and cost-effective method to demonstrate compliance with the
coverage requirements of a wireless network.
The methods described in this draft CATP comply with Bulletin TSB-88.3-C,
Wireless Communications Systems Performance in Noise and Interference
Limited Situations Part 3: Performance Verification, published by the
Telecommunications Industry Association (TIA).
TSB-88.3-C defines Channel Performance Criterion (CPC) as the probability of
achieving the desired DAQ/BER over the defined service area. TSB-88.3-C
further defines a service area as the boundary of a specific user's geographic
bounded area of concern. Usually a political boundary such as a county line,
limit, or similar definition for the users business can be defined relative to site
coordinates or an irregular polygon where points are defined by latitude and
longitude. TSB-88.3-C states that service area reliability shall be verified using
tile-based area reliability for all tiles within the service area. TSB-88.3-C also
states that validated service area reliability shall be determined by the
percentage of test locations that meet or exceed the specified CPC.
Channel Performance Criterion (CPC)

The CPC is the specified minimum design performance level in a faded channel.
For this system, the CPC is a Delivered Audio Quality of DAQ 3.4 or better. The
definition of DAQ3.4 is stated in Table 4 below.
Table 4
Delivered Audio Quality Definitions
Delivered Audio
Quality
(DAQ)
Grade of
Circuit Performance
Unusable. Speech present but unreadable.
Understandable with considerable effort.

Frequent repetition due to Noise/Distortion.
K-95

RFP 142842TM
Delivered Audio
Quality
(DAQ)
3
3.4
4
4.5
5
Grade of
Circuit Performance
Speech understandable with slight effort.
Occasional repetition required due to Noise/Distortion.
Speech understandable with repetition only rarely
required.
Some Noise/Distortion.
Speech easily understood. Occasional
Noise/Distortion.
Speech easily understood. Infrequent Noise/Distortion.
Speech easily understood.
Reliability Defined
The reliability is the percent of locations within the covered service area that
meet or exceed the specified CPC DAQ.
Coverage reliability is verified by sampling a statistically significant number of
randomly selected locations, quasi-uniformly distributed throughout the predicted
coverage area. For service area reliability, all tested tiles are included. For
covered area reliability, only those tiles predicted to meet or exceed the criteria
and are drivable are tested. Location information collected during testing will be
used to remove any tiles not included in the specified coverage area. The
method of determining the covered area reliability criteria for Mobile and Portable
at hip are attained as follows:
For portable at hip on-street and portable at hip in-building testing:
If
Tp/Tt x 100 95%
then, CATP testing is considered successful for Portable On Street and Portable
In Building.
Where:
Tp = Total of tiles passed
Tt = Total of tiles tested
This SCATP subscribes the covered area reliability technique. Specific detail on
the number of tiles needing to be tested and the percentage of tiles needing to
pass the test to meet the coverage requirement follows. The percentage
coverage area criteria are computed using the formula above with pass-fail test
result obtained from outdoor DAQ subjective testing.
K-96

RFP 142842TM
Individual Tile Passing Criterion

For automated drive testing, the passing criteria of a tile are determined by:
The median RSSI of all the samples within a tile to be: -98.5 dBm,
The median BER of all the samples within a tile to be: 2.0% for Phase-1
(DAQ 3.4), or 2.6% for Phaes-2 (DAQ 3.4).
For DAQ test, the passing criteria of a tile are determined by:
A tile must be rated as having a DAQ of 3.4 or better.
Determining the Required Number of Test Tiles in the Outdoor

Coverage Area
The Estimate of Proportions formula is a technique described in TSB-88.3-C that
is used to determine that a sufficient number of test tiles have been developed to
accurately validate the Service or Covered Area Reliability. This method has
been shown to provide a high degree of confidence.
The number of test tiles required can be determined from the following equation:
Where:
Tt = the number of test tiles required
Z = the standard deviate unit corresponding to the confidence level
p = the Required Service/Covered Area Reliability as a decimal (i.e., 95% = 0.95)
q = 1-p
e = the sampling error allowance in decimal format ( 0.01, or 1%)
The minimum number of test tiles measured is subject to a limit such that:
Tt 100
Thus, if the result of the estimate of proportions technique produces a result less
than 100 tiles, then a minimum of 100 tiles shall be used.
For this application, the number and size of tiles are computed using the
following tables.
Table 5
Performance Criteria
Covered area reliability (p)
Confidence level
Criteria
97%
99%
K-97

RFP 142842TM
Criteria
Sampling error allowance (e)

Service area size (Sarasota / Manatee County, FL)
1%
725 / 893 sq. mi
Table 6
Confidence Level
Confidence Level
Z (One Tail)
50%
70%
80%
85%
90%
95%
97%
99%
0
0.524
0.841
1.036
1.281
1.645
1.881
2.326
For these particular test requirements, the minimum number of required test tiles
for Portable on Street and Portable in-building is:
The total number of 1,574 tiles will satisfy the minimum number of required test
tiles for Portable on street and for Portable in-building scenarios to achieve
statistical significance.
Constraints on Test Tile Sizes

The minimum test tile size is 100 wavelengths by 100 wavelengths (i.e. 115.7 ft
by 115.7 ft worst case for 850MHz band); however, the minimum practical tile
size is typically about 200 by 200 meters (about 0.124 by 0.124 miles). The
maximum test tile size is 2 km by 2 km (1.243 by 1.243 miles). In some widearea systems, this constraint on maximum tile size may dictate a greater number
of test tiles than the minimum number required by the Estimate of Proportions
formula.
A suitable tile size for testing in this CATP is calculated as follows:
Area of Sarasota County/Minimum Number of Required Tiles (Tt) = 725
mi2/1574= 0.462 mi2 per tile, or 0.68 miles on a side for uniform square
tiles.
Area of Manatee County/Minimum Number of Required Tiles (Tt) = 893
mi2/1574= 0.563 mi2 per tile, or 0.75 miles on a side for uniform square
tiles.
These tile sizes will provide a statistically valid test result. If it is determined that
an excessive number of tiles are inaccessible due to structures on the property,
the tile size can be further reduced while still remaining statistically valid and
remaining large enough to capture the minimum number of sub-samples per tile.
K-98

RFP 142842TM
Test Tile Accessibility

Prior to testing and during the test, Contractor in cooperation with the Counties,
will determine if any tiles are inaccessible for coverage testing due to a lack of
roads, land restrictions, or being water, etc. Contractor prefers to eliminate
inaccessible grids from the calculation if enough grids are available to meet the
minimum required number of grids to present statistically significant sample. In
the event that eliminating the inaccessible grids from the calculation reduces the
grids to below the minimum number of grids required, then the inaccessible test
tiles shall be considered as having passed if they have 97% predicted covered
area reliability.
Measurements in Each Tile

Coverage verification using a combination of BER and received carrier power
(RSSI) is the method preferred by Contractor since this technique provides the
most meaningful data in determining whether the system meets its coverage
objectives. Interference can distort the carrier power reading, causing the
measured value to be higher than the value of the wanted signal. Since BER and
C/(N+I) ratios are closely related, the BER measurement is the ultimate arbitrator
in determining if a location meets the performance objective.
BER measurements are collected using receivers designed for this purpose. The
digital 1011 test pattern is recommended by TSB-88.3-C and APCO Project 25.
A synchronized 1011 test pattern will be transmitted from all sites within the
same simulcast cell. This allows data collection in areas of no predicted
interference as well as areas of predicted interference.
The sample distance (D) for outdoor test route measurements of the local
median received signal power in a test tile should be 28 D 100 . Contractor
prefers to use a one second period as this smoothes the Rayleigh fading while
avoiding changes due to location variability.
Bit Error Rate measurements may require longer distances or time intervals to
collect the required number of test sub-samples. RF coverage verification
involving BER measurements shall be made over one second period.
The number of sub-samples taken for each test sample every second by the
Survey Technology, Inc., STI9400 tool to measure the median power in each tile
shall be at least 100 subsamples. For a 99% confidence interval, TSB-88.3-C
indicates that the measured value is within 1 dB of the actual value if at least
122 sub-samples are taken per tile. Thus, use of the STI9400 stratifies the
requirement for a 99% confidence interval within 1 dB of the actual value with a
minimum of only two samples per tile. Other values of test sub-sampling rates or
confidence intervals may be used as needed, and where used, the sub-sampling
rates shall be computed in accordance with TSB-88.3-C.
Determining if Each Tile Passes or Fails the CPC Requirement

BER/RF Signal Strength Measurements
Measurements shall be taken using automatic data collection equipment
mounted in a vehicle. This equipment is capable of mapping the measurement
data using GPS technology. The equipment to be used is the STI9400.
K-99

RFP 142842TM
This automated data collection equipment collects subsamples of RSSI and BER
and averages these subsamples to obtain one sample (at least 100 subsamples
are averaged to generate one sample). The median of the RSSI and BER of all
the samples collected inside each tile is then taken; a tile is determined to have
passed should the result of this median value of RSSI be equal to or greater than
the required thresholds and the BER be less than or equal to the required
thresholds defined in this Agreement.
Based on the information in 3.3.3, a minimum of two (2) samples collected by the
Survey Technology, Inc., STI9400, will satisfy TSB-88.3-C for a 99% confidence
interval within 1 dB of the actual value for that tile to pass or fail per the CPC
requirements.
Delivered Audio Quality (DAQ) Test

A tile must be rated as having a DAQ of 3.4 or better to be considered a PASS. If
a test point is rated less than DAQ 3.4, the tester may move anywhere within 6
feet of the original test point and repeat the test. If the second attempt is
successful, then the test point is deemed a PASS. If the second attempt is also
unsuccessful then the test location will be considered a failure.
Determining the Coverage Area Reliability for Acceptance

The coverage test acceptance criterion is that the tested covered area reliability
must be equal to or greater than () the required reliability of 95% for Mobile and
Portable at hip on street; and be equal to or greater than () the required
reliability of 95% for Portable in building with a DAQ of 3.4 or better.
After all accessible tiles in the coverage area have been drive tested; the covered
area reliability (%) is determined by dividing the number of tiles which pass
outdoor DAQ test by the total number of tiles tested.
Drive Route and CATP Tiles

The picture below is provided as an EXAMPLE to illustrate the drive route
overlaying with CATP tiles. The final drive route and accessible tiles for the
Counties will be determined and agreed upon by the Counties and Contractor
before actual CATP testing.
K-100

RFP 142842TM
Example: Drive Routes overlaying with CATP Tiles
CATP Drive Routes
CATP Tiles
Figure 5
Example of Drive Routes Overlapping with CATP Tiles
800 MHz P25 System Automated Drive Test

The 800 MHz P25 system is a six site, simulcast system, in which all the sites
were predetermined by the Counties. The automated drive test for 800 MHz
system is a For Information Only Test, for which Contractor will provide the
Counties with the RSSI and BER maps resulting from drive testing. There will be
no PASS / FAIL commitment for the 800 MHz P25 system test result.
K-101

RFP 142842TM
DAQ Test Log Form

The sample log form for DAQ Testing is provided below:
Table 7
Tile
Number
Sample DAQ Test Log Form
Date
Testing
Personnel
Target
DAQ
Talk
out
Test
Result
(DAQ)
Talk
back
Test
Result
(DAQ)
Comments
Documentation
At the end of CATP test completion, Contractor will submit a report to the
Counties detailing the coverage test results. This report includes a form, which is
to be signed by the Counties and Contractor, indicating that the test was
performed in accordance with this CATP, and the results of the test indicate the
acceptance or non-acceptance of the coverage portion of the System. The
Counties have the option of accepting the coverage at any time prior to
completion of the coverage test or documentation process.
The pass/fail evaluations for each test tile are recorded on the test logs. A copy
of the test logs will be provided to the Counties at the conclusion of the coverage
test, along with all other CATP documentation.
K-102

RFP 142842TM
Sarasota - Manatee County Acceptance of CATP

This Coverage Acceptance Test Plan has been read and approved for use as
indicated by the signature below:
Sarasota County Representative
Signature
Signature
Printed Name
Printed Name
Title
Title
Date
Date
Manatee County Representative
Signature
Printed Name
Title
Date
K-103

RFP 142842TM
Coverage Acceptance
Based upon the successful completion of the Coverage Acceptance Test Plan,
Sarasota - Manatee County, hereby:
Sarasota - Manatee County Coverage Acceptance
Sarasota County Representative
Signature
Signature
Printed Name
Printed Name
Title
Title
Date
Date
Manatee County Representative
Signature
Printed Name
Title
Date
K-104

RFP 142842TM
System Acceptance Test Plan (Draft)

[REDACTED Airbus DS Communications Trade Secret]
K-105

Exhibit K - (REDACTED) - System Acceptance Plan v2 (FINAL)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Exhibit K - (REDACTED) - System Acceptance Plan v2 (FINAL)

Загружено:

Авторское право:

Доступные форматы

Exhibit K System Acceptance Plan

800 MHz Emergency Communications Systems

Exhibit K System Acceptance Plan*

Exhibit K System Acceptance Plan

Exhibit K System Acceptance Plan

Microwave Factory Acceptance Test Plan

ARRIVAL AND INTRODUCTIONS

FACTORY ACCEPTANCE TEST OVERVIEW / WHAT TO EXPECT / REVIEW FAT PLAN.

SYSTEM TOUR AND FAMILIARIZATION.

FACTORY ACCEPTANCE TEST (FAT)

PERFORM A VISUAL INSPECTION AND INVENTORY EQUIPMENT.

VERIFY SOFTWARE VERSIONS.

VERIFY TRANSMITTER AND RECEIVER FREQUENCIES.

VERIFY RADIO TRANSMIT POWER OUTPUT AT TOP OF RACK (TOR).

VERIFY RECEIVER THRESHOLDS.

VERIFY END-TO-END CIRCUIT CONNECTIVITY AND CONTINUITY AT ALL SITES.

CHECK LONG TERM BER OVERNIGHT TESTING.

VERIFY TRANSMITTER AND RECEIVER SWITCH OPERATION AS APPLICABLE.

10. DEMONSTRATE OPERATION OF ALARMS.

Exhibit K System Acceptance Plan

12. DEMONSTRATE PROVISION NMS- OPERATIONAL CAPABILITIES TO INCLUDE

ALARMS REPORTING, CONTROLS FUNCTIONALITY.

REVIEW FAT RESULTS AND AGREE ON ACTION ITEMS

DISCUSS PLANS FOR SHIPMENT AUTHORIZATION FOR SHIPMENT. SIGN-OFF ON

Exhibit K System Acceptance Plan

FACTORY ACCEPTANCE TEST (FAT)

Exhibit K System Acceptance Plan

TEST FAILURE HANDLING PROCESS

Exhibit K System Acceptance Plan

Exhibit K System Acceptance Plan

POWER METER (HP435 or Equivalent)

HI POWER HEAD (HP8481B or equivalent)

LOW POWER HEAD (HP8481D or equivalent)

ETHERNET TESTER (SMB600B or equivalent)

*to be filled during Factory Acceptance Test

Exhibit K System Acceptance Plan

VISUAL INSPECTION AND INVENTORY:

1.1.1. Verify that equipment is installed per Rack Profiles.

hardware for completeness and accuracy.

Exhibit K System Acceptance Plan

SYSTEMS INTG. TECH.

VERIFY SOFTWARE VERSIONS:

Using Sales Order Specific documents, configuration/management tool

Verify capacity license(s) and future licenses, if any.

SYSTEMS INTG. TECH.

Exhibit K System Acceptance Plan

VERIFY TRANSMITTER AND RECEIVER FREQUENCIES:

RECEIVE FREQUENCY (MHz)

SYSTEMS INTG. TECH.

Exhibit K System Acceptance Plan

TRANSMIT POWER OUTPUT (TOR)

Install a wave-guide to N-type adapter to the TOR wave-guide flange.

Connect calibrated high power head to adapter.

Measure/record Power Output at the TOR.

Record the Portal reading.

Disconnect calibrated high power head and remove N-type adaptor.

4.10. Unmute the Transmitter.

TEST EQUIPMENT: POWER METER, HIGH POWER HEAD

Transmitter Power Output (dBm)x

* Guaranteed at antenna flange port of ACU for Maximum System Gain.

Deduct 0.1dB for each piece of

Exhibit K System Acceptance Plan

SYSTEMS INTG. TECH.