Mambaye Lo

The founder

Mambaye Lo

Ph.D · Lead Enterprise Architect

Mambaye Lo, Ph.D, is a Lead Enterprise Architect with 16 years of digital transformations across retail, energy, banking and automotive, bridging strategy, data and IT delivery.

The evaluation method of Aura Supply Chain and Aura Decide builds on this research: each option is qualified by its improvement potential and its degradation risk, with no arbitrary weights. For you, that means your options are compared honestly, even when the data is incomplete.

  • 16 yearsof IT transformations
  • Ph.DAFIS best thesis award 2014
  • 4 sectorsretail, energy, banking, automotive
  • Lead EAENGIE, Capgemini, ADEO
Background and research

Background: head of enterprise architecture at ENGIE (B2C, since 2024); managing enterprise architect at Capgemini, including head of product for iPaaS & Datahub for the intelligent supply chain (2022-2024); lead architect of ADEO's industrial platform — global sourcing, supply chain, finance (2017-2021); consultant at CESAMES in complex systems architecture (2013-2017).

The doctoral thesis (LGI2P, Mines Alès), defended in 2013 and winner of the AFIS Best PhD Award (2014), deals with architecture evaluation in systems engineering, applied to the design of mechatronic systems.

This research extends the systems engineering meta-model, formalises design traceability links and proposes a design-choice support model, implemented with Core (Vitech) and MATLAB on the case of a power-assisted wheelchair.

Why Aura

Four problems Aura was built to solve.

  1. 01

    You wait for perfect data that will never come

    Complete data never arrives when the decision is due. Aura was born from a conviction: under uncertainty, you need evaluation methods that are simple, readable and robust. Rather than a single score built on debatable weights, Aura qualifies each option by its improvement potential and its degradation risk. The method builds on doctoral research into architecture evaluation and design-choice support.

  2. 02

    Your alerts arrive, your decisions do not follow

    We have seen expensive control towers struggle to connect to companies’ information systems, then produce alerts nobody knows how to qualify. The problem is not the dashboard: it is the lack of a shared model saying what each piece of data means, where it comes from, what it causes and who should decide.

  3. 03

    Your automated agents would decide without a frame or guardrails

    Plugging automated agents into systems nobody can describe simply automates opacity. At Aura, architecture work comes before the tool. An ontology describes the company’s objects and their relationships; it makes connecting to existing sources far simpler. Combined with explicit causal rules (this event, in this context, produces this effect), it gives automated agents a safe frame: the company can hand more to AI without losing control of its decisions.

  4. 04

    In your supply chain, uncertainty is a daily fact

    Supply chains constantly face an uncertain world: drifting supplier lead times, shifting demand, logistics disruptions. This is precisely where robust evaluation, an explicit model of the IT system and causal rules help most: seeing earlier, comparing options honestly, deciding while keeping the trace.

Research

A method tested by research, not improvised.

Doctoral thesis · 2013 · in French

Contribution à l’évaluation d’architectures en Ingénierie Système : application en conception de systèmes mécatroniques

Extended systems engineering meta-model, traceability of design decisions, design-choice support model.

Read on HAL

Article · INCOSE INSIGHT · 2013 · first author

Evaluating Alternatives for Designing Mechatronic Systems in a Systems Engineering Context

M. Lo, P. Couturier, V. Chapurlat

View on Wiley

Conference paper · 2012 · first author

Needs for Tracing the Consequences of Decisions in Mechatronics Design

M. Lo, P. Couturier

Find the paper

Article · Mechatronics journal · 2014

Tracking the consequences of design decisions in mechatronic systems engineering

P. Couturier, M. Lo, A. Imoussaten, V. Chapurlat, J. Montmain

Read on HAL

See how these methods apply in the sprints

Next step

Bring a real problem. Work it on the platform.

Start the 14-day trial, connect your sources and follow every decision with its proof. Subscribe when you are ready.