01 · CONNECT

READ-ONLY

02 · OVERLAY LIVE

TIER 1 AUTHORITY

03 · MEASURE + DECIDE

AGAINST TARGETS

ONE OPERATOR

DRAG TO ORBIT

PLTONE OPERATOR, ONE INCIDENT TYPE

One Incident Type.
One Operator.
Measured.

A focused pilot of Overlay on your real incidents: read access plus tier 1 ticket and customer-update authority, with no network changes in the first phase. Results are measured against targets we agree with you before we start.

Apply for the PilotRead the Brief ↓
1incident type
1operator
0network changes

1

Incident type

e.g. core link failures

Real

Incidents

Not a sandbox

T1

Authority

Tickets + customer updates

0

Network changes

In the first phase

6

Measures

Agreed before we start

THE BRIEF

Why this pilot
is different.

It is measured, not demoed.

Targets are agreed with you before we start: time from alarm to complete case file, duplicate tickets avoided, data conflicts found and confirmed, accuracy of affected-customer identification, time to first customer update, and cost per incident.

It is deliberately narrow.

One incident type, for example backhaul or core link failures and their downstream customer impact. Overlay only. Four layers is a large vision; the pilot tests one layer on one incident type, and the rest follows the evidence.

It is safe by design.

Read access plus tier 1 ticket and customer-update authority. No network changes in the first phase. Every action is logged with who or what approved it and why.

SANDBOX VS YOUR REAL INCIDENTSDRAG TO ORBIT

WHAT THE PILOT BUILDS

An early prototype already takes pasted logs, tracks the state of a network, advises on actions and logs incidents, with a human approving any change. The pilot builds and proves the rest on your incidents: live connections to your tools, cross-tool linking, the authority controls and the audit layer.

Time

Alarm to case file

Dupes

Tickets avoided

Accuracy

Affected customers

Cost

Per incident

HOW THE PILOT RUNS

Three phases.
One incident type.

PHASE

01

Connect, Read-Only

PHASE 1 · SET-UP

We agree the targets with you first. Then the data layer connects to the tools involved in the chosen incident type (monitoring, ticketing, inventory, customer records) with read access only. Before Overlay sees a single incident, we map how your records relate and where your tools already disagree.

DELIVERABLES

Agreed targets for every measure, signed off before we start
Read-only connections to the tools behind the chosen incident type
Record map: how customer links, core links, inventory and monitoring IDs relate
Conflict report: where your tools already disagree
Written confirmation of the authority Overlay will hold
PHASE 01 · IN MOTIONDRAG TO ORBIT

PHASE

02

Overlay Live

PHASE 2 · REAL INCIDENTS

Overlay works real incidents of the chosen type with tier 1 authority: it correlates alarms, builds the case file, logs or enriches tickets and keeps customers informed. Conflicting records are attached and escalated to your tier 2, never guessed. No network changes.

DELIVERABLES

Alarms correlated to a single root cause
A complete case file, with evidence, on every incident
Existing tickets enriched instead of duplicated
Holding messages first, full customer updates once facts are confirmed
Every action logged with who or what approved it and why
PHASE 02 · IN MOTIONDRAG TO ORBIT

PHASE

03

Measure and Decide

PHASE 3 · RESULTS

We report against the targets we agreed: what improved, what did not, and what each incident cost. Then you decide what comes next: widen Overlay's scope, add Inlay for tier 2 work, or stop. Your data and systems stay yours either way.

DELIVERABLES

Results against every agreed target
Cost per incident, measured from the first day
Data conflicts found and confirmed, with evidence
Recommendation on Overlay scope and whether Inlay fits
Documented exit: how to disconnect, if you choose to
PHASE 03 · IN MOTIONDRAG TO ORBIT

WHAT YOU KEEP

Your data. Your systems.
Always.

WHAT STAYS YOURSDRAG TO ORBIT

Your Data and Systems

Your systems remain the owners of the data
The data layer reads and mirrors; it takes no actions
Nothing in your stack is ripped out

The Intelligence Store

What the system learned about your network
Built only from outcomes your engineers reviewed
Versioned, inspectable and reversible
Owned by you

A Documented Exit

We document how to leave, from day one
A full audit trail of every action and approval
Results against every agreed target
Your call on what comes next: widen, add Inlay, or stop

WHO THIS SUITS

Is this you?

The pilot is not a fit for every organisation. We would rather say no now than waste your engineers' time.

Organisation
Telecom operator, ISP or fibre network, or any operations team running on many disconnected tools
Current tooling
Monitoring, ticketing, inventory and customer systems kept in separate tools
The pain
Incidents slowed by searching, conflicting records, duplicate tickets and late customer updates
Access
Willing to give read access to the tools behind one incident type
Decision authority
Someone who can approve a focused pilot and agree targets without a long committee chain
Timeline
Ready to agree targets and begin within the next quarter
Mindset
Tired of hype. Ready for an honest engineering conversation, with no pitch and no sales deck.
ONE PILOT POSITION OPEN

If this is you —
let's talk.

No sales deck. No pitch. A direct conversation about your incidents and whether Overlay, Inlay or both are the right response.

Apply for the PilotHow It Works

AFTER YOU APPLY

01You send a message via the contact form.
02Bheki responds within 4 hours. Personally.
03One call — 30 to 45 minutes. No pitch.
04Honest assessment. Yes or no, 48 hours.
05If aligned — pilot scope in 5 business days.
+27 79 739 4470info@entalinity.com
ENTALINITY · SANDTON · PILOT PROGRAMMESTILL DECIDING?