Bold SIMS and Phoenix end of support: preserving central station history

What does end of support mean for your SIMS or Phoenix history?#

End of support for SIMS or Phoenix means the software stops receiving vendor fixes and help, even if it keeps running on your servers. For a central station, the visible risk is running an unpatched system that your listing body, insurers and dealers rely on; the quieter risk is losing years of history during the move to Manitou or another automation platform.

Migrations usually focus on what the new platform needs on day one: active accounts, contacts, zones, schedules and dispatch instructions. Closed accounts, raw signal history and operator action logs are often left in the old database, which then sits on a server nobody wants to maintain. Treat history as its own workstream with an owner and a sign-off.

Check exact dates, support terms and migration options in Bold Group's own customer notices and your support contract. Secondhand summaries are no substitute for the vendor's written terms.

Which history should you export before cutover?#

The history worth exporting is anything you might need to prove what happened on an account, answer a dealer or insurer, or understand how operators responded. The table lists the main record families, a sensible export format and the reason to keep each one.

Avoid exporting only canned reports. A PDF alarm history is readable by a person but loses the keys that tie a signal to its zone, its operator actions and its audio.

Pre-migration checklist for central station history#

A pre-migration checklist keeps the history workstream from being squeezed out by cutover pressure. Run it in parallel with the account migration, not after the old server is switched off.

• 1Name an owner for the history workstream, separate from the cutover lead.
• 2Record the database engine, version, table list and record counts before anything changes.
• 3Read your dealer agreements and note who controls subscriber history and what happens at termination.
• 4Run a test export of one dealer's accounts and confirm that signals, operator actions and audio link correctly.
• 5Write a short data dictionary: table names, field meanings, event codes and disposition codes.
• 6Export every record family with keys intact, then reconcile counts against the source.
• 7Hash the export files and store a read-only copy in company-controlled storage.
• 8Keep a working copy of the legacy system, such as a virtual machine image, so the archive stays readable.
• 9Get written sign-off from operations and management before the old server is retired.

How long should you keep the legacy archive?#

Keep the legacy archive for as long as the longest obligation that touches it. No single period fits every central station, because the obligations come from different places and vary by state, listing and contract.

Write the result down as a retention schedule with a review date, and destroy records only after counsel confirms no hold applies. Keeping everything indefinitely is also a choice with costs: storage, security and the burden of searching it later.

Who controls signal history in wholesale monitoring?#

In wholesale monitoring, signal history usually sits in the central station's database while the subscriber relationship belongs to the dealer, so the dealer agreement decides who controls it. Some agreements treat account data as the dealer's and require its return when a dealer leaves; others say nothing.

Read the agreements before you export, archive or delete anything, and before considering any reuse of the history. Proprietary stations that own their subscriber contracts have a simpler position, but they still need to check subscriber agreements and privacy notices.

Illustrative: a wholesale monitoring center moving off Phoenix#

Illustrative: a fictional wholesale central station monitors accounts for many dealers on Phoenix and plans a move to a new automation platform. The migration vendor's plan covers active accounts and open schedules only.

The operations director adds a history workstream. She exports closed accounts, full signal and operator action tables, the audio index and agency records, writes a data dictionary, and keeps the old server as an isolated read-only virtual machine. Dealer agreements are reviewed, and the dealers whose contracts require return of data receive their histories on encrypted media.

Months later, a dealer disputes a dispatch fine on a closed account. The station answers from the archive the same afternoon instead of trying to revive a decommissioned server.

How SourceX treats central station archives#

SourceX treats central station archives as records of real decisions under time pressure: a signal arrives, an operator verifies, calls, dispatches or cancels, and the outcome is logged. Linked histories like these are the kind of operational records AI developers license, once dealer contracts and subscriber notices allow it.

Every license follows the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Rights review starts with dealer agreements; preparation removes subscriber names, addresses, passcodes and voices; and large archives stay in your own storage or ship on encrypted drives, because SourceX does not host multi-terabyte datasets. The SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization.