Feasibility and baseline
Agree the situation type, operating workflow and available data. Establish the current handling process and the KPIs the NOC can measure.
Network operations · 01 · The problem and the decision
Network-operations AI design sprintWhat is one hour of a Packet Core fault costing you today?
Alarm volume is high, diagnosis takes time and the proposed automation touches several organisations. Establish a defensible use case and a design the operator, vendor and delivery team can review together.
For NOC and assurance leaders, operator engineering teams and vendors assessing a network-operations AI use case.
4–6 weeks elapsedOne agreed network-operations use caseA named architect accountable
02 · What we check
Agree the scope. Inspect the evidence.
The first phase is AIOps feasibility and a KPI baseline. The full sprint adds the target architecture and MVP decision; it is not a commitment to production results.
Architecture and boundaries
Map integrations, retrieval, inference placement, tool authority and operator decisions. Work through vendor and operator dependencies.
MVP decision
Define the evaluation approach, acceptance checks, delivery responsibilities and prerequisites for a bounded MVP.
What we need from you
- A use-case owner in operations and access to relevant network, assurance and vendor stakeholders.
- Agreed, appropriately handled examples of situations and the evidence used to diagnose them.
- The system interfaces, data restrictions and operational measures available for the chosen use case.
Scope and boundaries
- Production integration, autonomous network changes and a guaranteed improvement in diagnosis time are not included.
- The proposal fixes the use case, interfaces, evidence access and decision participants. Additional use cases are separate scope.
03 · What you get
A decision you can act on.
- An agreed use-case definition and KPI baseline, with data limitations recorded.
- A target architecture and integration/responsibility map.
- An MVP evaluation plan, acceptance checks and prioritised delivery backlog.
- A go/no-go recommendation with dependencies, risks and the next decision owner.
04 · Relevant work and a sample
See the thinking behind the review.
A bounded flow for network operations
For Nokia, working with a Tier-1 Nordic operator, Atsky designed the situation-enrichment agent as a four-step flow: retrieve, annotate, recommend and format. The NOC retains the decision; tracing and in-tenancy inference form part of the design.
05 · Duration and price
A defined engagement. An agreed scope.
Scope and price agreedBefore work starts
Bespoke scope and pricing. We quote a fixed fee after agreeing the use-case and interface inventory, access and design depth. The proposal confirms the elapsed delivery window around the evidence and people required. The feasibility/KPI-baseline engagement is the first phase; production implementation, remediation and detailed implementation-ticket engineering are separate.
- Duration
- 4–6 weeks elapsed
- Base scope
- One agreed network-operations use case
- Your data
- Read-only access, in a workspace that holds only your engagement. If your policy requires it, we work with EU-only processing and zero data retention. Any extra cost is named in the proposal.
Our own AI-assisted tooling collects evidence and drafts findings; a named architect checks and signs them. How we work and handle data →
06 · Request a working session
Start with the question you need to resolve.
In 45 minutes, examine one operational problem, the data available and who owns the decision. Use a relevant architecture example to establish whether a design sprint fits.
This requests a 45-minute conversation. We confirm a suitable time with you.
Is the agent use case outside network operations? Explore the agentic architecture review.