The DMS processes, moves, and tracks products -- i.e. files -- as they
flow between ground components.
The DMS manages products that must be approved before they can be used
— the DMS manages which users can sign which products and keeps
track of whether or not a product has been signed.
Major DMS components are the database, the web portal, the central
agent, and the remote agents.
The DMS is a distributed system; the database, web portal, and central
agent run on DMS servers and remote agents are distributed across ground
The DMS is configured via the “model”, a <dms-model> XML document.
The model predicts what should happen, the remote agents report what
actually happened, and the central agent's expectation engine
issues alerts when they don’t agree.
The web portal lets users find products, review product flow, and
sign products and lets administrators manage and tune the DMS.
The DMS is highly configurable; there are about 100
The DMS can generate ICD documentation from the model.
The DMS is designed to run continuously for years, but is robust enough
that its components can pick up where they left off when shut off and
The DMS uses the PostgreSQL database engine. DMS components are coded
using Java, XSLT, and PHP.