Paris, France
Operating systems for critical infrastructure
Network Operations · ITSM Governance · Automation · Observability — I build calm, reliable operating systems for multi-entity environments.
Telemetry
Mission-critical systems aren’t explained — they’re proven.
READINESS
Operating posture for critical infrastructure.
Calm · Governed · Evidence-led
Reliability at scaleMulti-entity execution
Reliability is built — then measured.
OPS SYSTEMS LAYER
Engineered systems that turn operations into control
A calm architecture: signals in, decisions out — with traceability, repeatability, and governance.
MODULE 01
Observability Layer
Telemetry, availability, and SLO health across services.
GrafanaCentreonSLOs
SIGNAL → OUTPUT
SignalReal-time + trend
OutputDecision-ready views
MODULE 02
ITSM & Workflow
Incident, change, and request execution with traceability.
ServiceNowGovernanceCAB/Change
SIGNAL → OUTPUT
SignalTickets + SLAs
OutputControlled delivery
MODULE 03
Delivery Intelligence
From raw work to executive synthesis and release readiness.
JiraKPIsNarrative
SIGNAL → OUTPUT
SignalWorkstream status
OutputOne trusted story
MODULE 04
Automation Fabric
Python pipelines that package artifacts and reduce friction.
PythonAPIsExport → PNG → PPT
SIGNAL → OUTPUT
SignalRepeatable runs
OutputLess manual ops
MODULE 05
Compliance & Evidence
Retention, audit bundles, deterministic evidence packaging.
TraceabilityRetentionAudit
SIGNAL → OUTPUT
SignalProof on demand
OutputAudit confidence
MODULE 06
Operational Leadership
Clear comms, calm coordination, measurable service outcomes.
StakeholdersRunbooksRCA
SIGNAL → OUTPUT
SignalHigh-stakes events
OutputPredictable control
Current Mission
Safran — Pilot of Network Operations — Group IT
MISSION SNAPSHOT
Govern and improve Group Network Operations across multiple entities, ensuring quality, compliance, and predictable service delivery across network and perimeter security services.
SYSTEMS RESPONSIBILITY
- Oversee operations and support activities; ensure delivery quality and SLA adherence.
- Keep operational referentials, KB, assets, and decision trees up to date after interventions.
- Act as point of contact for standard/catalog changes and cross-domain coordination.
- Serve as focal point during major incidents: crisis setup, tracking, synthesis, and reporting.
- Analyze demand and operational activity; coach teams on Incident/Change/Problem discipline.
EXECUTIVE SIGNAL
Calm operations. Measurable outcomes. Governance built-in.
Automation & Engineering Leverage
A predictable system beats heroic effort — especially at scale.
- Python automation for reporting, evidence packaging, and readable governance artifacts.
- Power BI operational intelligence: KPIs, trends, and executive-friendly views.
- Centreon/Grafana extraction + visualization pipelines for consistent reporting.
- Python-generated Confluence release notes and structured release communication.
CONTROL MODE
Automation • Traceability • Repeatability
AUTOMATION ARCHITECTURE
Release Intelligence Pipeline
Turns operational signals into executive-ready artifacts — with traceability and archiving.
▾
SYSTEM FLOW
PHASE 1/6
Tap a node to jump. Swipe left/right to advance.
STEP 1 · INPUT
Telemetry Intake
Centreon • Grafana exports
SYSTEM SIGNAL
Creates alignment by producing a single, trusted narrative.
Mobile is simplified by design. Full architecture is available on larger screens.
AUTOMATION ARCHITECTURE
Release Intelligence Pipeline
Turns operational signals into executive-ready artifacts — with traceability and archiving.
Hover a module to highlight the path. Use the selector to explore different operational scenarios.
▾
EXECUTIVE FLOW
Hover a module · Click to pin
INPUT
Telemetry Intake
Centreon • Grafana exports
INPUT
Workstream Signals
Jira • ServiceNow records
CONTROL
Normalization Layer
Mapping • dedupe • KPI rules
ENGINE
Synthesis Engine
Grouping • narrative • metrics
OUTPUT
Artifact Builder
Charts → PNG → PPT
GOVERNANCE
Compliance Archive
Retention • traceability • audit
Why it matters
Turns noisy operations into decisions — fast, repeatable, audit-friendly.
Engineering signal
Inputs → transformation → outputs, with reliability constraints.
Leadership signal
Creates alignment by producing a single, trusted narrative.
EXECUTIVE PROOF
Case studies that show outcomes — not just features
Each case is structured as Before → Intervention → After, with governance and measurable impact.
CASE SELECTOR
Product & Ops Systems — Python + ServiceNow + Jira + Grafana/Centreon
Release Intelligence Pipeline
Operational reporting converted into executive-ready artifacts with traceability and archiving.
TraceabilityNormalizationExecutive narrativeRetention
IMPACT
Faster readiness decisions with a single trusted narrative — produced repeatably, with governance built in.
KEY METRICS
Cycle time
↓ 70–90% (typical)
Manual effort
Near-zero recurring
Governance
Audit-ready outputs
BEFORE
- •Updates assembled manually from multiple tools
- •Inconsistent format across teams
- •Hard to trace what changed and why
INTERVENTION
- •Built a deterministic pipeline: extract → normalize → synthesize
- •Automated chart exports and packaging into PPT-ready assets
- •Added naming conventions + retention for compliance
AFTER
- •One trusted narrative for leaders (stable every run)
- •Faster readiness decisions; fewer late surprises
- •Evidence and artifacts reusable for audits
LEADER OUTCOME
Leadership gained a predictable release narrative — enabling faster go/no-go decisions with confidence.
ENGINEERING OUTCOME
Automation removed manual assembly and stabilized outputs across systems with deterministic structure.
Principles
Operational Philosophy
- 01RESILIENCEACTIVEDesign for bounded failure: detect early, contain fast, recover predictably.
- 02SIGNALACTIVEMake decisions from signals, not stories: observability with accountable ownership.
- 03EVIDENCEACTIVETurn operations into evidence: traceable changes, repeatable outcomes, audit-ready by default.