HomeMy WebLinkAboutAcceptance test Plan ProceduresAppendix D — Acceptance Test Plan/Procedures
System Overview
Introduction
The purpose of this document is to provide an Acceptance Test Plan (ATP) with test
preparation and validation procedures for acceptance testing of specific equipment
subsystem to support SMARTNET Trunking Features and System Reliability
Features. The ATP will augment the setup and functional testing done after field
installation.
The system design does not represent a coverage reliability guarantee, explicit or
implied, As a result, Motorola will not be performing or guaranteeing any coverage
performance nor providing acceptance testing with the City of Miami ("City").
Upon notification to the City's project manager that Motorola deems the system to be
fully operational, the following plan will be used to demonstrate that the system
satisfies the functional requirements delineated elsewhere in or appended to this
document. When all steps of this test plan have been successfully executed, the City
shall acknowledge that the system has been satisfactorily implemented and is
accepted as an integrated system.
Prerequisites
Prior to starting the acceptance test demonstration, the following will have been
satisfied:
• The proposed system hardware must be fully installed, optimized, and
operational. Motorola will verify that site installations are performed in
accordance with the Statement of Work.
• City has identified a person to monitor the tests.
Motorola Responsibilities
• Provide any necessary test equipment.
• Provide a representative(s) to conduct the test procedures and to observe and
document the test results as they happen.
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
City of Miami, Florida
Mobile Communications System
IFS No. 28069 — Appendices
July 5, 2007
2.23
City of Miami Responsibilities
• Provide a minimum of one representative to assist in conducting the test
procedures and to monitor, verify, and approve the tests as they are performed.
General Acceptance Testing Parameters
Test Performance
The performance of each test within a Test Step/Session will be carried out on a step-
by-step basis. It is the responsibility of the Motorola test conductor to initiate each
step and to verify the accuracy of each key -in and procedure.
In tests where a majority of the supplied equipment or upgrade is identical, the
customer may elect to perform these acceptance tests on a sampling of the available
equipment. Tests that have passed on the sampled equipment will be considered to
have passed and accepted for all like equipment.
During the test, all unusual occurrences will be noted on a test log and if hardware
malfunctions are involved, appropriate notations will be made in the hardware log.
The failure of a test shall not require the re -running of the entire Field Acceptance
Test. Any failures noted will be entered on a "Punch List" in accordance with the
following "Punch List" procedure. Motorola will re -run any failed portion of the test
following resolution of the problem. Both the City and Motorola will retain copies of
the above logs and any notes made.
Test Verification and Approval
The performance verification portion of the Acceptance Test will consist of
verification of formats and operation using the Acceptance Test Plan as a script. Each
command and its associated operation will be verified and the test log for the
corresponding test initialed by the City's monitor.
At the end of each test and test series, the printed output from the system devices will
be collected, verified at the time of collection, and attached to the test log with the
proper affixed signatures. If the test is not successful, the Motorola test conductor will
retain the output for use in solving the problem and a copy of the output will be
provided to the City's test monitor for reference. If the failing test item is of minor
operational significance, the performance verification test will continue as will the
operational reliability test. All failing test items which are not corrected prior to the
end of the operational reliability test will be cited in a "punch list" letter written by
the customer and will be corrected within a mutually agreeable time frame and under
the system warranty terms of the contract.
City of Miami, Florida
Mobile Communications System
IFB No. 28069 -- Appendices
July 5, 2007
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
2-24
Failing test items, which do not interrupt or prohibit day-to-day communication
operations, are insufficient cause to delay integrated system acceptance if the
operational reliability test is passed successful. If software problems occur during the
acceptance test that prohibits day-to-day communication operations the test will be
discontinued and rescheduled when the problem has been corrected. If only the
customer deems the problem to be severe, i.e., prohibiting day-to-day communication
operations, Motorola personnel are authorized to shut down the specific fixed end
radio equipment (after notifying the City of this proposed action) for as long as
necessary in order to correct the problem. If this occurs, the acceptance test will be
suspended and restarted upon correction of the identified problems.
If proposed new equipment purchased for this SMARTNET system fails during the
Field ATP, Motorola will notify the customer of the schedule repair time. The Field
Acceptance Testing, however, will continue from the point the equipment failed.
Due to regular updates of SMARTNET software, the specific operation and
functionality of features may vary from what is written depending on system release
version. If any versions on this system should change, the City will be notified of any
variations before beginning any tests.
Upon completion of the entire test, the City must itemize in writing to Motorola all
remaining failing test items and all items that do not meet specifications. When
validated by Motorola, these items will then be corrected within a mutually agreeable
time frame and under the system warranty terms of the contract. Corrected items or
functions will be tested per this Field ATP. An authorized City representative will
monitor, verify, approve, and accept these corrections when installed, tested, and
operated in accordance with the terms of the contract.
Acceptance Test Plan Overview
The typical Motorola Acceptance Test Plan consists of several parts that will test the
fixed equipment operation of the radio system. Provided below is a general test plan
that involves the procedures required to verify the equipment functionality.
Fixed Equipment Functionality Test
Motorola will provide the required subscriber units needed to perform the Field ATP
Test. Motorola will program the subscriber radios to perform specific SMARTNET
features for system access.
In addition, the City's fleetmap development of subscribers and SMARTNET access
is not part of this proposal. For proper interface to the Mobile Communications
System, the City will determine the associated system features for access, develop the
radio templates, and program these templates in the City radios required for
subscriber system performance and operation.
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
City of Miami, Florida
Mobile Communications System
IFB No. 28069 — Appendices
July 5, 2007
2-25
Detailed Acceptance Test Plan
Following is the detailed Field ATP for the City as proposed by Motorola to
demonstrate system functionality. When all steps of this test plan have been.
successfully executed, the City shall acknowledge that the system has been
satisfactorily implemented and is accepted as an integrated system.
• SMARTNET Trunking Features
• System Reliability Features
• Console/Microwave Link Operations
City of Miami, Florida
Mobile Communications System
IFB No. 28069 — Appendices
July 5, 2007
Motorola Confidential Restricted
Use or disclosure of this proposal is
subject to the restrictions on the title page
2-26