Services · Private 5G · Rollout & Setup

From site survey to a verified industrial service

Seven phases, three products

How MatreComm takes a Private 5G network from survey and towers to core, voice, services and day-2 operations — and where CraftCore, CraftIMS and CraftTWIN do the work. Phases overlap on the ground. Each closes on an agreed exit gate, and the twin is built from day one — so the network is operable the day it goes live.

The rollout at a glance

Seven phases, one at a time

Use the tabs, the arrows, the dots or your keyboard's left and right keys to move through the phases.

Phase 01 · Survey & design

Design around what the plant needs to do

Exit gate · approved design, sizing & BoQ

Use cases & goals

Applications on the network — AGV/AMR, machine vision, robotics, sensors, remote ops — and the latency, availability and continuity each one needs.

RF & site survey

Coverage zones across factory, warehouse or outdoor areas; tower, pole and small-cell spots; power and backhaul; licensed or captive spectrum.

Architecture & sizing

On-prem, hybrid or cloud; central control with site-local UPF; HA 1+1 with DC–DR; every function inside the customer's network perimeter.

Where the products come in

CraftTWIN

Starts the twin: enterprise → region → plant, port or campus → zone, with the assets and processes each zone runs. 2D/3D RF coverage planning [roadmap].

CraftCore

Sized to the device and throughput plan — Model A 1 Gbps · 1K, B 5 Gbps · 10K, C 10 Gbps · 20K, D 20 Gbps · 50K subscribers.

Phase 02 · Towers, RAN & transport

Put radios on air over solid transport

Exit gate · radios on air, transport verified

Towers & civil works

Masts, poles or rooftop mounts as surveyed; power, earthing, cabling and fibre to every radio site.

RAN install

Radio-agnostic and plug-and-play — no on-site radio specialist. Only authorised devices can join the coverage area.

Transport & L3 switch

1/10/25 GE optics; IS-IS, BGP, Segment Routing, MPLS, DSCP marking. Outdoor option to ETSI EN 300 019-1-3 Class 3.3.

Where the products come in

CraftTWIN

Onboards every radio, cell, DU, CU and controller — modelled, not just polled — and maps each cell to the zones and assets it serves.

CraftCore

Integration profile per radio vendor for N2 (SCTP 38412) and N3 (GTP-U, UDP 2152); per-device throughput, radio latency and cell occupancy once attached.

Phase 03 · Core install

Install and bring up CraftCore

Exit gate · all NFs up, RAN attached, HA proven
≤ 1 hrSystem bring-up, excl. hardware install
≤ 2 hrBackup restore
99.95%Core availability target
1+1HA, with DC–DR geo-redundancy

Hardware

1 GE electrical + 10/25 GE optical; DPDK, SR-IOV, NUMA, CPU pinning.

Functions

4G EPC + 5G SA on one codebase; 4G → 5G SA with no hardware swap.

Data & tenancy

ScyllaDB, RF=3 recommended; per-tenant slices, quotas and views.

Management

GUI, CraftCLI, REST API and Prometheus exporters per NF.

CraftTWIN

Core feed goes live — NF, session, policy and user-plane context stream into the twin, deeper than any read-only overlay on a third-party core.

Phase 04 · Voice & IMS · Optional

Add voice and push-to-talk with CraftIMS

Exit gate · test calls & PTT groups passed
01

Install CraftIMS

Deploy the SIP/IMS control plane beside CraftCore, inside the perimeter.

02

Connect over Cx

Diameter Cx to CraftCore's UDM for subscriber data and authentication.

03

Enable users

Turn on voice for subscriber profiles, in bulk or one at a time.

04

Add MCX / PTT

Integrate mission-critical push-to-talk apps for crews and field teams.

Where the products come in

CraftIMS

MatreComm's own SIP/IMS control plane, independent of third-party IMS stacks — Cx per 3GPP TS 29.228/229 on port 3868.

CraftCore

In-house UDM answers CraftIMS over Cx; MCX/PTT application integration is supported in the core. One vendor across core and voice.

Phase 05 · Service deployment

Deploy the services the plant runs on

Exit gate · every device mapped, SIM to application

SIMs

Bulk or single provisioning; outside SIMs blocked at the MME/AMF.

APNs & IPs

20+ APNs; traffic split by APN, IMSI, Cell-ID or QoS; static IPs.

Slices & QoS

Each application class mapped to its approved slice and QoS flow.

Edge path

Site-local UPF and local breakout; DNS caching for local content.

RMF goal

Declare the latency or continuity goal and the actions RMF may take.

Where the products come in

CraftCore

Runs all five steps. Self-service portal on desktop or mobile: add SIMs, change APNs, name devices, see per-SIM APN status and live connection counts.

CraftTWIN

Builds one identity chain per device — SIM → UE/CPE → industrial asset → site/zone → the application it serves — kept current through every change.

Phase 06 · Test & acceptance

Prove the application-to-core loop before go-live

Exit gate · signed acceptance against agreed targets
1Select2Baseline3Set goal4Degrade5Reason6Govern, act7Verify8Measure

Conformance

CraftCore and CraftIMS run an automated regression and 3GPP Rel-17 suite across core and IMS signalling, plus SBI, N2/N3/N4 and Cx checks.

Your hardware

Indicative Model D figures — UPF breakout 1–3 ms, session setup 80–150 ms, ~5,000 TPS — are confirmed here, not assumed.

Your numbers

Baseline → pilot → target for time to detect, explain and restore, repeat incidents and process downtime.

CraftTWIN

Runs the proof: twin evidence, probable cause, blast radius and verified recovery for the controlled fault — on one industrial service, end to end.

Phase 07 · Operate & assure

Run the service, not just the network

Steady state · 24x7 L3/TAC support
CraftTWIN

1 · Detect

Uplink degrades on cell C; vision frames drop; the inspection station is at risk.

CraftTWIN

2 · Explain

Probable cause with evidence and confidence; blast radius to devices, apps, zone, SLA.

CraftCore · RMF

3 · Act

Governed change to policy, QoS, session or UPF path — inside the approved envelope.

CraftTWIN

4 · Verify

The application outcome is checked, not command success; roll back or escalate if not.

Autonomy is a setting — per action class, site and maintenance window

Observe-onlyRecommendApproval-gatedBounded, preapprovedManual-only actions stay manual

RMF governs network and core behaviour only — never industrial machinery or safety systems. Every action leaves an audit trail.

Phase 1 of 7

Target architecture

One network, three MatreComm layers

CraftTWINOperational twin & Private 5G UNMS over every layer below — RAN, core, SIM/UE, edge, application and SLA.

Devices

AGVs, robots, cameras, scanners, sensors — via SIM/UE or CPE.

NR · LTE →

RAN

gNB / small cells; radio-agnostic, plug-and-play.

→

Transport

L3 switch, outdoor-rated option; IS-IS, BGP, SR, MPLS.

N2 · N3 →

CraftCore 4G/5G core, one codebase

5G SA — AMF · SMF · UPF · PCF · NRF · NSSF · UDM · AUSF

4G EPC — MME · S-GW · P-GW · HSS · PCRF

RMF — application goal → governed action → verified outcome

CraftIMS

SIP/IMS voice and MCX/PTT apps, Diameter Cx to the UDM

N6 →

Edge & apps

MEC workloads: vision inference, AGV fleet control, control gateways.

Ports · rolling out at a container terminal

What changes when the site is a port

Quay & berths

STS cranes, lashing crews, vessel ops

Container yard

RTG/RMG cranes, straddle carriers, tractors

Gate

OCR and CCTV cameras, truck processing

Terminal & plaza

Handhelds, tally devices, offices, parking

Phase 01 · SurveyCraftTWIN

Stacks move daily — plan for a changing yard, with high-mast and quay-side radio sites. The twin models port → terminal → berth, yard and gate zones.

Phase 02 · RAN & transportCraftTWIN

Salt air, wind and long fibre runs along the quay — specify the outdoor-rated L3 switch option, and model every mast and cell.

Phase 03 · CoreCraftCore

One core for many terminal operators — each gets its own slices, quotas and management view on shared port infrastructure.

Phase 04 · VoiceCraftIMS

Berth, yard and gate crews coordinate on voice and MCX/PTT apps over the same private network — no separate radio system to run.

Port services on one network

Remote crane videoOwn slice, site-local UPF, RMF continuity goalCraftCore
Yard vehiclesSession continuity as they cross yard cellsCraftCore
Handhelds & tallySIM self-service; APN per terminal operatorCraftCore
Gate OCR & CCTVUplink-heavy; local breakout to edge analyticsCraftCore
Crew voice & PTTVoice and MCX/PTT apps for berth and yard teamsCraftIMS

Illustrative incident · CraftTWIN

  1. 1Uplink degrades on a yard cell
  2. 2Crane camera feed stutters; remote moves slow down
  3. 3The berth's vessel turnaround is at risk

CraftTWIN traces cell → crane → berth with evidence; CraftCore's RMF applies the governed fix; CraftTWIN verifies the crane feed is back.

RMF governs the network only — crane safety systems stay with the crane.

Plan · phase gates & handover

Every phase closes on a gate

01

Survey & design

Design, sizing & BoQ approved

TWIN · Core
02

Towers, RAN & transport

Radios on air, transport verified

TWIN · Core
03

Core install

NFs up, RAN attached, HA proven

Core · TWIN
04

Voice & IMS

Test calls & PTT groups passed

IMS · Core
05

Service deployment

Every device mapped to its app

Core · TWIN
06

Test & acceptance

Acceptance signed vs targets

All three
07

Operate & assure

Ongoing

Handover to the NOC; steady-state SLA

TWIN · Core
Handover & support

24x7 L3/TAC support (IST) · 3-year software + hardware AMC · field engineers and periodic training · FCAPS that plugs into the operator's UNMS

Next steps

Start with one site and one service