MassMasterTM repository workflows
Governed data, dictionaries, reports, validation checks, effectivities, and Nastran-oriented workflows.
MassMaster NexusTM
Git-enabled visual engineering workspace
Distributed change control for aircraft mass properties.
MassMaster NexusTM helps distributed teams branch, compare, review, baseline, merge, and trace weight, CG, inertia, BOM, payload, source provenance, and effectivity data as aircraft configurations evolve.
Visual traceability
Trace tree selections directly into the aircraft display.
Nexus makes mass properties spatial. Engineers can select layers, BOM items, source groups, or FE-derived entities and immediately verify their aircraft location in a shared 3D workspace.
Capability status
Separate current capability, pilot scope, and roadmap before publishing.
Nexus should be presented with explicit status labels so buyers understand what is available, what is pilot/preview, and what remains roadmap.
Nexus visual review workspace
3D model context, entity tree, layer support, selected FE part workflows, and branch/revision review depending on deployment scope.
Future expansion
Abaqus data models, payload screening, and deeper operational loading workflows.
Engineering change review
Review engineering changes with history, branches, and comparisons.
Nexus supports Git-backed workflows for reliable change tracking, branch comparison, restoration, review, baselining, merge, and contribution from multiple engineers.
That model aligns mass properties work with the parallel, contributor-driven reality of modern aircraft development while preserving aircraft-aware semantics for source, credibility, effectivity, weight, CG, inertia, and BOM structure.
Change-control equivalents
Use the Git mental model, then make it aircraft-aware.
Repository technology is infrastructure. The larger value is the MassMasterTM configuration-control model above the data: versioning, review, provenance, effectivity, and reproducibility.
Trade study, variant, test article, or fleet configuration
Explore alternatives without corrupting released data.
Delta in weight, CG, inertia, BOM, or effectivity
Explain configuration movement quickly and defensibly.
Certified, flight-test, simulation, or delivery state
Reproduce prior reports, exports, and simulation inputs.
Nexus workflow
From source data to visual validation.
Load the controlled repository
Bring MassMasterTM data, model context, layers, and source records into one review surface.
Interrogate entities
Review assembly structure, source categories, credibility, mass markers, and FE parts.
Validate visually
Find missing, duplicated, misplaced, or suspicious mass items before downstream teams rely on them.
Coordinate change
Compare revisions, branches, configurations, and review states through the workgroup process.
Simulation-ready validation
Validate baywise mass and inertia before analysis teams depend on it.
Nexus helps engineers interrogate distributed mass properties, baywise inertia, and FE-derived structure before downstream loads, dynamics, aeroelasticity, and simulation workflows rely on the data.
STEP-derived source data
Promote exact geometry-derived mass properties into controlled records.
For generic demo geometry, Nexus can show STEP model context and support exact mass-property extraction workflows without exposing raw implementation details on the public site.
Roadmap language
Future workflow expansion should be visibly labeled.
Future-facing capabilities can include deeper Abaqus-specific automation, payload development, payload screening, and deeper operational loading workflows. These should stay clearly marked as planned until production-ready.
RoadmapAbaqus data models
RoadmapPayload development
RoadmapPayload screening
RoadmapOperational loading workflows
Pilot discussion
Review NexusTM against representative mass properties workflows.
Use a sanitized demo model or approved program data to evaluate review flow, data traceability, configuration change, and simulation support.