Technical Resources | RTDC

Architecture notes

How layers, zones and interfaces are structured, and why.

How to Approach Brownfield Infrastructure ModernisationModernising a live environment starts with discovery and dependency mapping. This note sets out how to decide what to keep, refresh, migrate or retire, and how to sequence the change.

Design considerations

The factors that shape design decisions for a given environment.

Engineering Edge Devices for Outdoor and Remote EnvironmentsThe conditions, calculations and design decisions that determine whether edge equipment keeps working at a roadside, a utility site or in a vehicle.

Deployment guides

Sequenced approaches to rolling out equipment and configuration.

How to Plan a Multi-Site Network DeploymentA sequence for rolling out a network across many locations: site classification, standard templates, staging, pilot, controlled waves, and per-site acceptance.

Operations notes

Practices that keep running systems observable and controlled.

Designing Monitoring Before CommissioningWhy the monitoring model belongs in the architecture, how to derive metrics and thresholds from the design, and how to prove that alerts reach the people who must act.

Managing Configuration Across Distributed SitesPractices for keeping equipment at many locations consistent with an approved design: baselines, templates, version control, drift detection and controlled change.

Capacity-planning guides

Sizing against load, growth, retention and degraded operation.

Planning Backup Around Recovery ObjectivesHow to turn recovery point and recovery time objectives into backup design, size the backup window and storage, and verify that restores work.

Integration checklists

What to define and verify for each system interface.

Establishing Interface Control in Multi-System ProjectsA checklist for defining, owning, changing, testing and monitoring each interface between systems, so that integration is controlled rather than improvised.

Site-readiness checklists

Conditions a site must meet before equipment arrives.

What a Data Centre Readiness Assessment Should CoverA structured checklist for assessing whether a facility, and the estate inside it, is ready for a refresh, expansion, migration or new platform.

Testing frameworks

Structures for proving that a system meets its criteria.

Building an Acceptance Test Plan for Complex ICT ProjectsHow to derive acceptance criteria from requirements, structure test cases, handle defects and record evidence so that acceptance is a verifiable decision.

Maintenance frameworks

Records and routines that sustain systems over long service periods.

Why Asset Registers Matter in Long-Term OperationsWhat an asset register should hold, which operational questions it answers, and how to keep it accurate over years of change.

Designing for Maintainability in Field InfrastructureDesign choices that make remote equipment faster and safer to repair: access, replaceable units, fault isolation, standard spares, configuration restoration and evidence capture.

Technology explainers

Plain-language explanations of how a technology behaves in practice.

Designing High Availability Across the Complete ICT StackAvailability is a property of the whole service chain. This note explains how redundancy at each layer combines, where hidden shared dependencies sit, and why failover has to be tested.

Have a requirement in this area?

Tell us about the programme, the sites and the stage you are at, and we will respond with the technical questions that matter first.

Discuss an ICT Requirement