Network
How the service lines, engagements, and products connect.
Every node and edge below comes out of the same files that build the rest of this site. A case study connects to a domain because that's the sector on the record, and to a service line where that service names it as proof — not every study proves a single service, and the drawing doesn't pretend otherwise.
44 nodes · 44 edges
Hover a node to isolate its connections · every node is a link
Reading the graph
What the shape shows.
01
Why the center is thin
Everything hangs off the 3 service lines, the practice areas, and the product groups rather than off the firm. A capability with no delivered work behind it has no case study attached, and on this drawing that shows as a spoke with nothing on the end.
02
Where the case studies sit
Every engagement attaches to the domain it was delivered in. Where a service names it as proof it attaches to that service too, which puts it between two clusters; the rest sit with their domain alone.
03
Why the fringe is dense
The fringe is published software anyone can open — the largest structure on the drawing, because every application in it is public.
The graph, as a list.
Service lines
- AI & Data Science Delivery
Proved by energy, automotive, mining engagements.
- Training & Enablement
Two courses are published in full, session by session. The wider 16-topic curriculum has been delivered and is assembled into custom cohorts on request.
- Decision-Support Platforms
Proved by energy engagements.
Domains
- Government & defense
7 public applications
- Healthcare
Practice area — no published engagement yet.
- Middle East & Gulf
3 public applications
- Federal government
1 engagement
- Energy
2 engagements
- Commercial real estate
1 engagement
- Automotive
1 engagement
- Mining
1 engagement