Skip to content
Mission Network

How the work
actually connects.

A site is usually a list of pages. Federal engineering is a web — every project we run threads through a service line, a sector, a set of partners, and a case study that proves it worked. This is that web, drawn as a graph. 79 nodes, 82 real relationships pulled from the same data the rest of the site is built on.

Hover a node to follow what it touches. Click to open it. Drag to rearrange. Scroll (or pinch) to zoom. On the side, toggle off any category to thin the view.

OCEANS LLC Requirements Development Systems Engineering & Arch… Research, Development, Tes… Mission Data, COPs & Ontol… DHS DoW Other Federal International Law Enforcement Orgs & Labs Transit / Rail Airports Enterprise Architecture & … Operational Test & Evaluat… Aaron Winkler Daniel Brent Daniel Trimper Jamie Hayes Mike Matechak Momena Ali Paul Morrisseau
79 nodes · 82 edges
Reading the graph

Three patterns to look for.

▌ Breadth

Where the partners cluster

Each of the eight sector hubs collects the agencies in its space. Hover a sector to see its weight.

▌ Focus

Four service lines

Requirements, Systems Engineering, RDT&E, Mission Data — every engagement maps to at least one. Hover one to see which case studies and clients have used it.

▌ Bridges

Case studies span service + sector

Each case study connects to the services it used AND the sector it served — they sit on the bridges of the graph, not at the edges.