Resources
Documents you can take to your team.
Open workbooks and reviewer guides you can read and print now, and licensed briefs and decks that arrive by email. Each one names who owns the problem, what it costs to leave alone, and the one next step.
Showing 6 of 6 documents.
Open now.
Ordinary pages. Read them, print them, and take the CSV templates into your own spreadsheet. Every worked example is synthetic and says so.
From alarm to incident brief: a read-only NOC pilot
Open workbook. Telecommunications. Web page, printable. CSV template.
For NOC leads, service assurance managers and incident reviewers
Test whether a cited incident brief reduces evidence-assembly effort without hiding uncertainty or giving an assistant control of the network. One synthetic incident, worked end to end, with the evaluation measures and the human boundary.
Next step Assess one incident class against historical data.
Order fallout: diagnose the activation delay
Open workbook. Telecommunications. Web page, printable. CSV template.
For Fulfilment leads, enterprise operations, inventory owners and revenue assurance
Find which exception is actually blocking activation, who owns the next check, and whether the commercial effect is a delay or a validated loss. A synthetic order journey with provisioning and inventory exceptions and the diagnostic rows to copy.
Next step Review one order journey.
AI pilot business-case and acceptance workbook
Open workbook. General. Web page, printable. CSV template.
For Operational sponsors, finance reviewers and pilot owners
Decide whether one bounded workflow is worth testing, and what evidence would justify stopping or progressing. Editable hypothetical economics with realisable capacity, review and operating costs, three scenarios and explicit acceptance gates.
Next step Establish your operational baseline.
Private AI deployment: what stays where?
Reviewer guide. General. Web page, printable.
For CISO, architecture and procurement reviewers
Decide whether an operational AI pilot may access enterprise data. Managed, self-hosted and disconnected inference as distinct options, the data flows to trace, the permission and deletion tests to run, and the evidence to ask for before approval.
Next step Book an architecture review of one data flow.
Licensed copies by email.
Each PDF is licensed to the person who requests it, marked for that recipient, and reaches them by email. The public page or preview says what is inside before you ask.
Charging assurance: six reproducible tests before launch
Use-case brief. Telecommunications. v1.1, September 2026. 15 pages.
Six synthetic charging workflows for charging, QA, billing and revenue assurance teams: explicit tariff assumptions, inputs, expected outputs, boundary cases and expert acceptance checks. Illustrative, not delivered customer case studies.
ThirdEye for BSS and charging: use-case proposal
Solution deck. Telecommunications. v1.1, September 2026. 15 pages.
A fourteen-slide illustrative proposal for telecom BSS and charging teams: five proposed workflows, the application and inference boundary, required employee controls, a focused pilot and what Akima operates.
A 30-minute briefing
The document opens the conversation. The briefing answers your questions.
Bring the questions the document raised. We cover the decision, your data and security model, a cited answer over a sample, and the shape of a pilot.