Regional ISP - sample dossier

Arkadiusz Kolawa

Founder & CEO

Raven Systems

RAVEN VERIFIED RV-L3 DEMO SAMPLE

Executive Briefing / prepared exclusively for: REGIONAL OPERATOR ISP

OPERATIONAL DECISION-MAKING EXPOSURE

83 days

OBSERVATIONS

6,552,194

OBSERVATIONS

193

CANDIDATE WINDOWS

49 minutes

THE LONGEST WINDOW OBSERVED

Assess decision delay, operational uncertainty, and potential cost of delay.

Document border

THIS IS NOT AN OFFER.

THIS IS NOT A REPORT ON THE STATUS OF THE NETWORK.

THIS IS NOT A REGIONAL ISP QUALITY ASSESSMENT.

One question

Is the time between the first signal and the decision

operational cost is created by a cost that we do not measure today?

Is it worth checking them out?

Boundary: observations are decision-making material and require correlation with data from the regional ISP operator.

Executive Briefing / Prepared exclusively for: REGIONAL OPERATOR ISP

Introductory note

The scope of information has been moved from the briefing cover to a separate explanatory page.

83 days of observations / 6,552,194 observations / 193 candidate windows

OPERATIONAL DECISION-MAKING EXPOSURE

Assessment of decision delay, operational uncertainty and potential uncertainty

cost of delay.

83 days

OBSERVATIONS

6,552,194

OBSERVATIONS

193

CANDIDATE WINDOWS

49 minutes

THE LONGEST WINDOW OBSERVED

Document border

THIS IS NOT AN OFFER.

THIS IS NOT A REPORT ON THE STATUS OF THE NETWORK.

THIS IS NOT A REGIONAL ISP QUALITY ASSESSMENT.

This is an attempt to answer one question: whether the time in between

the first signal and the operational decision creates a cost,

that we don't measure today?

Is it worth checking them out?

The point of the briefing

Determine whether decision latency is a measurable operational issue rather than assessing the network itself.

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Board Snapshot: management decision in 60 seconds

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

WHAT WE KNOW

83 days of observation, 6,552,194 sample metrics and 193 candidate windows. CASE 001 shows

observed candidate decision window: approximately 49 minutes.

WHAT WE DON'T KNOW

We do not know any correlation with the regional ISP operator's operations center, customer reports, crew work and

operator's internal telemetry.

WHAT IS WORTH CHECKING

Does an average of 2.3 candidate windows per day create a decision cost that the organization

today it is not measured as a separate category.

HOW WE MEASURE SUCCESS

Signal-decision time, quality of team dispatch, completeness of evidence, cost of delay, result after

decision and stop/continue decision.

NEXT DECISION

Approve a 45-minute briefing and joint assessment of one real event in read-only mode.

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Executive Summary: Issue for review, not an offer to purchase

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

Conversation anchor

CASE 001: Observed Decision Candidate Window

approximately 49 minutes. This is not a failure claim. This

reason to check whether the decision delay has

Cost.

The scale of the phenomenon

193 candidate windows in 83 days, or an average of 2.3

candidate window per day. This is still a hypothesis

operational, not a list of incidents.

Safe range

Read-only, 5 packages or 14 days, no saving

production, without customer data at the start and without

automatic actions.

Locally confirmed: 83 observation days, 6,552,194 metrics samples and 193 candidate windows.

Management hypothesis: part of the value of a regional ISP operator may arise or disappear between the first signal and the approved decision.

The purpose of the briefing is to determine whether decision delay is a measurable operational problem within the regional ISP operator.

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Why this report was created for a regional ISP operator

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

A large operator wins with scale. The local operator often wins on trust. Trust is not created

exclusively from the parameters of the offer - very often it arises from the quality of the response, clarity of communication and the feeling

that someone close to the client understands the situation.

Proximity to the customer

a regional ISP operator can know the local context faster than

organizations primarily managed by scale.

Response quality

Local advantage becomes visible when

the team knows what to do before the problem grows.

Trust

The customer remembers more than just the failure. He remembers the way

reaction, communication and decision time.

This report was created for the regional ISP operator because the quality of the local operator's response may depend on the quality of the decision. This is

a hypothesis to be tested calmly, not a declaration about the state of the network.

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Questions for Management

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

QUESTION 1

Do we measure the time between the first signal and the approved operational decision?

QUESTION 2

Do we know the cost of waiting before an event becomes obvious to the customer or service?

QUESTION 3

Can we explain after the fact why one operational decision was better than another?

This page intentionally does not contain answers. Its goal is to check whether the topic of decision time deserves 45 minutes of joint operational work.

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

CASE 001: Decision Window Example from Observational Data

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

This is not an example of a confirmed regional ISP failure. This is an example of a window into which outside observations could ask

operator to check the situation in advance before the decision becomes more expensive.

DATE/TIME

2026-04-06 11:35:36 Europe/Warsaw

(09:35:36 UTC)

SOURCE

macbook_packet/external surveillance

METRICS

packet jitter and RTT

POTENTIAL LEAD TIME

approximately 49 min to a more severe deviation

First signal: 2026-04-06 11:35:36 Europe/Warsaw (09:35:36 UTC). Jitter exceeded 50 ms on target 1.1.1.1 and amounted to 124.9 ms. At this point, the operator does not

he still has to take a costly action, but he should be asked: is this an isolated jump or the beginning of a decision window?

Moment of escalation: 2026-04-06 12:25:00 Europe/Warsaw (10:25:00 UTC). Jitter exceeded 500 ms on target 1.1.1.1 and amounted to 755.3 ms. Later peak that day

achieved 1564.9 ms jitter and 1020.4 ms RTT. This is material for a conversation about response time, not an automatic failure claim.

WHAT DATA WERE KNOWN

time, source, target, jitter, RTT, p95/p99 and later scale

deviations

WHAT DATA WAS UNKNOWN

internal cause, customer segment, device,

correlation with data from the regional ISP operator

WHY THIS IS NOT A FAILURE STATEMENT

external observation does not resolve failure or quality

networks without operator correlation

Why this is a good candidate for a pilot

One case is enough to talk about: whether the regional ISP saw it in its own data, whether it was operationally significant and whether an earlier package would have changed the order of operations.

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Cost of waiting: what happens between the signal and the decision

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

Operator costs also arise in times of uncertainty. Without data, the regional ISP cannot provide a hard figure, but it is allowed

build exposure scenarios for verification in the pilot.

Time

Operational risk

Service pressure

Shipping risk

Exposure

5 minutes delay

the risk that a single signal does not get its owner

decision

first questions for support

the team is not ready yet

for verification

15 minutes delay

growing uncertainty whether this is an isolated spike or

pattern

the staff is starting to pick up the buzz

risk of late or wrong shipment

exhibition scenario

30 minutes delay

the problem may affect additional paths or services

the customer sees the wait, not the cause

the opportunity cost of the team increases

potential loss of trust

60 minutes delay

the incident may enter the narrative of the client and management

escalations take on a separate life

the reaction may already be defensive

to be counted by data

pilot

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Operator problem: Value escapes from confirmed failure

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

Place of friction

What the operations team needs to know

What should the management see?

What the pilot checks

First signal

whether the signal has an owner and attention threshold

whether reaction time is measured

whether Raven organizes evidence faster

Unknown

which cannot be proven yet

whether the decision is burdened with false certainty

whether the package limits the risk of excessive

theorems

Sending a team

who is free, how far away, how long the repair will take

what is the cost of wrong order

whether the decision to send a team is measurable

value

Communication

what to say to the customer without making excessive promises

whether the service pressure is decreasing

whether the package provides ready-made escalation material

Result

what actually changed after the decision

Is it worth scaling your practice?

whether a register of values ​​was created

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Market pressure: speed becomes commoditized, response begins to diversify

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

This is not threatening competition. This is a trend: it is becoming more and more difficult to defend an advantage based on speed and declared speed alone

availability. The local operator can win on the quality of the response if he can measure it.

Speed

The offer parameters are comparable and increasing

easier to copy. The customer remembers

However, the moment when the problem was solved

guided.

Reaction

The advantage shifts to the operating loop:

notice faster, decide better, more carefully

communicate, record the result.

Measurement

your regional ISP can check for time advantage

decisions exist in practice, without being public

declaration and without production risk.

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

How decision value is created

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

01

The operator recognizes the window

Not every deviation is a failure. Value begins with separation

signal from panic.

02

The team gets a package

Problem, place, time, known data, unknowns, cost of delay and options are in

one material.

03

Man decides

The system can make recommendations, but the decision and responsibility remain after

manager page.

04

The result goes back to the organization

The pilot checks whether the decision resulted in a measurable operational effect, and more

correct description.

Value vector

Question: regional ISP operator

Validation

Minutes regained

is the signal visible earlier?

decision time

Fewer bad shipments

Is the team going to the right place?

status and result

Less noise

does the service have better context?

communication

A better decision

does the cost of delay become apparent?

value review

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

One incident as a package of decisions

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

Moment

What the operator needs

What the package shows

Financial role

Decision

Signal

whether it requires human attention

metrics, place, time, certainty and unknowns

yet without the purchase cost

open

Evidence

what is known and what cannot be claimed

confirmed / hypothesis / pilot validates

the cost remains a scenario

view

Options

what stock has the least risk

Gold/Platinum information range, no promise of result

budget and cost of waiting

to choose

Team

who can respond and when

status, distance, arrival time, refusal/acceptance

downtime cost

send

Result

whether the decision worked

state change, report, archive

value register

close/escalate

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Evidence/observational data: separating facts from claims

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

Confirmed

Hypothesis

Pilot validates

Limit

83 days of observation

potential decision time advantage

correlation with the data of the regional ISP operator

not a failure claim

6,552,194 metrics samples

potential cost of delay

real impact on operations

not an assessment of network quality

193 candidate windows

potential value of shipping teams

real cost and response time

not a promise of ROI

DNS, HTTP, RTT, jitter, packet loss

potential client exposure

real lead time and result

not automatic action

The principle of credibility

The document is intended to open a conversation about a problem that a regional ISP may not yet be tackling. It is not intended to externally prove guilt, causation, or financial worth without

common correlation.

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Candidate windows: material for joint correlation

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

Date

Source

Metrics

Class

Why is it worth checking?

2026-04-06

telco

Packet loss (%)

candidate

p95 0.00 / max 66.7

2026-04-07

telco

Packet loss (%)

candidate

p95 0.00 / max 66.7

2026-04-08

telco

Packet loss (%)

candidate

p95 0.00 / max 66.7

2026-04-09

telco

Packet loss (%)

candidate

p95 0.00 / max 66.7

2026-04-14

telco

Packet loss (%)

candidate

p95 0.00 / max 66.7

2026-04-15

telco

Packet loss (%)

candidate

p95 0.00 / max 66.7

The candidate window is not an incident. This is an invitation to correlate with the data of the regional ISP operator.

The scale is intuitive: 193 windows in 83 days, or an average of 2.3 candidate windows per day.

The value of a pilot should be judged by the quality of the decisions, not by the number of deviations detected.

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

ROI model: no quotas until confirmed by regional ISP operator

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

Element

How to count in the remote control

What do we need from a regional ISP operator?

Result

The cost of waiting

time from the first signal to the decision x impact scenario

segment, number of customers, margin or service cost

potential exposure

Cost of wrong shipping

team time + travel + opportunity cost + delay of the actual one

shares

team status and intervention history

quality of shipping teams

The cost of a bad decision

escalation + rollback + service noise + reputational risk

the course of the event and the result

comparison of options

Loss avoided

base scenario minus the cost of the selected action

confirmation of the result

value register

Decision to continue

whether 5 packages were enough to demonstrate value

value review

stop / continue

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Pilot KPI: what must be measurable after 5 packages

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

SIGNAL-DECISION TIME

minutes from the first signal to the approved action

COMPLETENESS OF EVIDENCE

what we know, what we don't know, what blocks the decision

QUALITY OF TEAM SHIPPING

the right team, arrival time, acceptance, result

COST OF WAITING

exposure scenario, not a hard amount without data

RESULT AFTER THE DECISION

what changed after the action or after conscious waiting

MANAGEMENT DECISION

whether to continue, extend or stop the program

The pilot ends with a value review. If a regional ISP does not see measurable value, the program should be

stopped without further obligation.

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Controlled read-only validation program

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

Goal

What's going on

What is not allowed

Owner

Gate 1 - range

confirm event classes, data boundaries and remote owner

without customer data, without a contract

Management/Operations

Gate 2 - read-only

connect logs, report summaries or reconstruction data

no production record

Technical

Gate 3 - 5 packets

Raven prepares decision packages; man approves

without autonomous actions

Operations Manager

Gate 4 - value overview

compare decision time, cost, crew dispatch and result

without inflated ROI

Finance/Operations

Gate 5 - stop/continue

stop, expand or switch to a paid pilot

no purchasing pressure

Management

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Decision-making order / human authority

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

Limit

Behavior

Why is it important?

Evidence

Man's authority

Raven recommends, manager decides

blocks dangerous automation

trace of acceptance

Read-only

no production record in the first stage

lowers the risk of implementation

remote control model

No customer data at launch

Validation can start with technical data and

reconstruction

lower legal threshold

data range

The unknowns are visible

the package says what cannot be proven

limits false certainty

unknowns section

Stop/continue

after 5 packages there is a decision, not design drift

cost and sense control

value review

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Which this document does not claim

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

does not claim that every candidate window was a failure.

does not assign a cause without correlation with the regional ISP operator.

the regional ISP operator does not assess the quality of the network.

does not promise specific ROI without a pilot.

does not propose automatic actions on the network.

does not replace manager's decision or operator's responsibility.

Why the pilot is low risk

Read-only, no production records, no access to customer data at the start, no automatic actions, human approves, 5 packages or 14 days, decision

stop/continue after review of values.

RAVEN SYSTEMS - OPERATIONAL DECISION RUNTIME

Proposed next step

Limit: Raven's observations and scenarios are decision-making material, not confirmed operator incidents.

Generated locally - 2026-06-22

If the decision time advantage is operationally important, it's worth it

verify it earlier than it becomes a market requirement.

Approve a 45-minute operational briefing.

Select one real event regional ISP operator for joint evaluation.

Agree on read-only boundaries and no customer data at launch.

One management question

The purpose of the briefing is not to evaluate Raven. The goal is to determine whether decision delay is a measurable operational problem within the regional ISP.

This sample mirrors a controlled management briefing for a regional ISP operator, with customer identity and sensitive values removed.

Raven Systems

Operational Decision Runtime

ravensystems.group

contact@ravensystems.group

Contact person

Arkadiusz Kolawa

Founder & CEO

Raven Systems

RAVEN VERIFIED RV-L3 DEMO SAMPLE