MAD REFERENCE
Designing for supportability and system evolution
A concise supportability reference: equipment access, software dependencies, configuration ownership, recovery procedures, service responsibilities and the evidence needed at handover.
DEFINITION
Supportability is the ability to maintain and restore the intended service.
A supportable installation gives the responsible team access to the equipment, information, software and expertise needed to diagnose a problem, restore operation and make an appropriate change.
Its working life depends on those provisions together with maintenance and planned refreshes. Assess the complete system, including content, networks, external services and the people expected to operate it.
TECHNICAL DETAILMake the responsibilities explicit.
Open the engineering detailClose this sectionLook for the red circuit symbol for engineering detail.
| Area | Information to define |
|---|---|
| Physical access | Equipment locations, ventilation, mounting, safe service access and replacement routes. |
| Asset and configuration records | Models, identifiers, connections, software versions, settings and backups. |
| Software and rights | Dependencies, licenses, update ownership and access needed to restore or modify the installation. |
| Content operation | Media locations, approved versions, publishing procedure and recovery copies. |
| Diagnosis | Available logs, remote access, monitoring coverage and the limits of each observation. |
| Recovery | Startup, shutdown, fault and restore procedures, with the relevant states tested. |
| People and service | Staff tasks, specialist escalation, training, support contacts and response arrangements. |
| Refresh planning | Spares, compatibility checks, replacement assumptions and the record of subsequent changes. |
TECHNICAL DETAILGive the next team a usable record.
Open the engineering detailClose this section
- An asset register and as-built system and network diagrams.
- Configuration backups, content locations and restore instructions.
- Supported software versions, licenses and update responsibilities.
- Tested operating states, recovery procedures and any unresolved limitations.
- Operator training and a distinction between staff tasks and specialist work.
- An agreed maintenance plan, support scope and change log.
STANDARD COMPUTER ARCHITECTURE
Assess replacements by compatibility.
QuickSilver® uses standard computer hardware, providing options for compute and storage refreshes. Each replacement still needs compatible software, drivers, interfaces and performance, followed by appropriate testing.
For a legacy installation, a QuickSilver retrofit establishes the playback and control foundation before selected AV++ capabilities are added. Suitable peripheral equipment may remain after assessment; the new content, interfaces and engineering are scoped separately.
APPLY THE REFERENCE
Ask what the team can actually demonstrate.
Can staff identify a failed component, find its configuration and follow a tested recovery procedure? Can the support team inspect the relevant state with the agreed access? Can a proposed replacement be qualified before it goes into service? Those questions turn the record into evidence.
WORK WITH MAD
What will the next team need to keep this working?
Use the reference to review your handover or existing installation. Mad can help identify missing information, service constraints and a practical support scope.
Discuss supportability