|
-
Radio Deployment Scheduling Discussions Underway: During the next two months, the PSERN Project will be contacting agencies to discuss and finalize the Radio Deployment Schedule. It is important that Project Contacts review the Scheduling FAQ with their staff and prepare to discuss scheduling.
-
PSERN Operator Hiring: The PSERN Operator is hiring an Administrator III to support the operational needs of the new PSERN System.
-
Hiring for DAS Transition: The Project is still recruiting for two more Electronic Communications Specialists to perform DAS (Distributed Antenna System) quality assurance work.
-
DAS Property Reminder: Properties with Distributed Antenna Systems (DAS) need to hire a DAS Vendor to be ready for the transition next year. There are over 650 DAS in King County, so the DAS Vendor community will be very busy reconfiguring and validating DAS. Contracting paperwork is often time-consuming, so secure a DAS Vendor soon!
-
Fire Marshal & DAS Vendor Forum: The PSERN Project will be hosting a webinar on November 2nd from 10am – 12pm for Fire Marshals to review their approach to DAS code compliance in transitioning to the new PSERN System and to answer questions. DAS Vendors who are interested in attending, please email DAS-PSERN@kingcounty.gov.
The PSERN Project has completed the first phase of the BER (Bit Error Rate) signal quality and the DAQ (Delivered Audio Quality) or “Can you hear me now?” testing in the metropolitan area. During that process, there were a number of tiles (.2-mile testing squares) that were identified as inaccessible, but after conducting further research, we are pleased to announce that approximately 2000 tiles that were previously designated as inaccessible will be able to be tested. We expect testing of those tiles to be complete this month. Results will be shared when all testing is completed.
There are many elements that must be integrated in the Radio Deployment Schedule to meet time and resource constraints, so the Project will be following these steps to collaboratively determine exact scheduling details with agencies:
- Collect vehicle information from agencies with mobile radios.
- Draft the Radio Deployment Schedule dates/times/locations based on the deployment waves, vehicle information, contract requirements to install 35 mobile radios a day, and providing multiple mobile installation depots, as well as multiple portable distribution locations for minimizing agency travel time.
- Review the draft schedule with each agency to answer questions and integrate any needed adjustments.
- Obtain agency commitment to fulfill the schedule.
Once all agencies commit to the Radio Deployment Schedule, the Project will begin a reminder schedule of reconfirming the deployment details 1 month prior, 1 week prior, and 1 day prior. Agencies will be responsible for notifying the Project as soon as possible if they need to reschedule.
|
|
|
Dates are accurate as of 9/23/21:
-
Site Construction: April 2016 - November 2021* (building radio towers and infrastructure)
-
Programming Templates: October 2019 - November 2021 (developing/programming per radio)
-
Radio Frequency Coverage Testing: March 2021 - October 2021* (testing end-user signal quality)
-
Operational and Functional Testing: November 2021 - December 2021 (testing system and end-user radio functions and features)*
-
Radio End-User Pilot Testing: December 2021 - January 2022 (proof of concept end-user testing)
-
Radio Deployment & Transition: January 2022 - October 2022 (distribution of agency radios)
-
Full System Acceptance: March 2023 (transition operations to PSERN Operator)
*Update since last month
|
|
|
There are two reasons that the Project needs to collect specific vehicle information from agencies to create the Radio Deployment Schedule. The first reason is that the duration of a mobile radio installation varies based on the type of vehicle and therefore that information is needed to determine adequate appointment duration. The second reason is that the current radio ID’s will be used by the new PSERN radios and so the exchange of old and new radios must be exact. Current radio ID’s are being reused because the PSERN radios will need to maintain interoperability with neighboring analog radio systems, like Snohomish County, Pierce County, Port of Seattle, Port of Tacoma, and City of Tacoma. All analog ID numbers in the region are already in use, so careful management is key to maintaining interoperability.
Next year agencies will be receiving their new PSERN radios during the Radio Deployment and then transitioning to the new PSERN System. It is helpful to recognize that although both events will be following wave groupings, they are distinct events that can be decoupled if necessary because they depend on separate milestones. The Radio Deployment will begin when the radios for a wave have been received, the programming of those radio templates are complete (including both analog and digital channels), and the deployment schedule is set. Agencies can transition to the PSERN System when the Pilot Test, Operational/Functional Test, and Coverage Test are all successful and they have received their new PSERN radios.
If, for example, the testing is not complete prior to the start date of Wave 1 Radio Deployment, but the radios have been received, programmed, and deployment scheduled, the deployment can move forward. The agencies however would not transition to the new PSERN System until the testing is successful. They would simply continue to use the current analog KCERCS System on their new PSERN radios. Additionally, if testing is not complete after all of Wave 1 agencies have received radios, buildings with Distributed Antenna Systems (DAS) may delay turning off their DAS until there is a set date for transition. This parallel approach will allow the Project to ensure that radios are deployed efficiently, DAS downtime is minimized, and that the new PSERN System meets all requirements before transition.
|
|
|
|
