Enterprise Digital Twins

Your Enterprise, Live - Enterprise Digital Twins in Practice

A 1-hour live session for leaders who want to see how their business is running today — and where it is heading. We show a working enterprise digital twin of a professional services firm: its people, their skills, the projects they are on and the revenue they generate each day, updated daily from Jira and Tempo, and projected forward into the months ahead.

Ask the leadership of a professional services firm three simple questions: What did we earn yesterday? Who is free next month? Where will revenue land at quarter end if nothing changes?

In many firms, each answer lives somewhere different. Last month's numbers are in a finance report. Who is working on what is in the time-tracking tool. Skills are in a spreadsheet, or in the heads of a few senior people. And the forecast is a slide deck, built by hand and out of date by the next partner meeting. Each source is useful. None of them is connected to the others.

An enterprise digital twin connects them: a live, simplified image of how your business actually operates, which shows what has happened, what is happening right now, and how that projects into the future — in one place, with AI you can ask questions in your own words.

The example: a professional services firm

Professional services firms suit a first twin well. The business is people delivering work through projects, and the data mostly exists already — in tools like Jira and Tempo, where hours are booked day by day. What is usually missing is the structure that turns bookings into answers.
The twin we show brings three views together:

• The past — how utilisation, revenue and project delivery have developed over the past months, reconstructed from the booked hours.
• The present — which staff you have, which skills they bring, which projects they are working on, and the revenue each project generates, updated every day.
• The future — a simulation that runs forward from today: how revenue develops at the current pace, where skills will run short, and what changes if a project ends early, is extended, or a new one starts.

Walking our talk

The twin we show is not a mock-up built for the occasion. It is modelled on transentis itself. We have been modelling our own firm for a long time, and bringing it all together in one digital twin is the culmination of that work: our masterdata lives in it, and we run our business on its live dashboards.
For the session we swap in test data. You see the real structure and the real workflow — just not our real numbers.

How it is built

The twin rests on three layers, and we walk through each one:

1. An ontology — the typed vocabulary of the business: staff, skills, roles, clients, projects, rates, bookings, and how they relate. This is what gives the data its meaning.
2. A knowledge graph of the enterprise — the actual firm, described in that vocabulary: who has which skills, who is staffed on which project, which project belongs to which client.
3. Live data — hours and bookings flowing in daily from Jira and Tempo, attached to the nodes they measure. Revenue is not a report someone compiles; it follows from the bookings, the rates and the structure.

A simulation layer sits on top and runs the whole thing forward. And AI runs across all of it: you ask "which skills are fully booked in December?" and get an answer you can trace back to the people, projects and hours behind it.
We built the twin in Metapad, an AI-powered platform for enterprise digital twins. But the approach is the point, not the tool.

Agenda

• 5 min — What an enterprise digital twin is. A short recap of the vision: why many digital twins in practice are operational twins with no connection to business model, strategy or operating model — and what changes when the twin is built on a knowledge graph.
• 10 min — The model underneath. The ontology and the knowledge graph of the firm: staff, skills, projects, clients, rates — and how they connect.
• 15 min — The present and the past, live. Today's state, updated from Jira and Tempo: who is on what, the revenue each project generates, where capacity is tight. Then back through the history: how we got here.
• 15 min — Into the future. We run the twin forward and play out what-ifs — with the audience choosing what to try. A project ends early; a proposal comes in; a key person is away for a month. One change, one run, one look at what moved.
• 15 min — Q&A and what's next. Your questions on the twin, the method and the data — and what it takes to build one for your own enterprise.