Digital Engineering Foundations · Module 1 of 8
What Digital Engineering Is
Digital engineering is not a pile of software. It is the disciplined habit of connecting the requirement, model, data, result, assumption, review and decision that belong together, so another engineer can find them and trust them.
Readiness check
This is the first module of an Advanced course. Tick only what you can do closed-notes.
- Describe one design decision and the evidence that would support it.
- Name at least three artifacts created during a mechanical design task.
- Tell the difference between a CAD model and a drawing.
- Explain why a simulation input file is part of the evidence, not just the report.
- Name the source of truth for a released drawing in a small team.
The core idea
Digital engineering is the controlled connection of engineering information, models, evidence and decisions across the lifecycle.
The practical test for this whole course is one question: can another engineer find the requirement, model, input data, result, assumption, review state and decision that belong together? If not, the team may be using digital tools, but it does not yet have a dependable digital engineering workflow.
The skills, taught in order
This module builds one habit in four steps: define the decision, name the artifacts, keep documents tied to their sources, and know which source is authoritative.
1.1 Start with the decision, not the tool
Digital engineering is the disciplined use of digital models and their underlying data to support lifecycle engineering work. Begin with the engineering decision, name the artifacts that support it, record status, owner, version and approval beside each one, then connect the evidence so the decision can be inspected later. A tool earns its place only when it makes a decision more inspectable.
Micro-example. A bracket is ready for prototype only if its requirements, CAD, material choice, hand calculation, test plan and review note all point to the same baseline.
1.2 Documents, models and digital artifacts
A digital artifact is any controlled digital item used or produced by engineering work: a requirement table, CAD model, mesh, material file, test procedure, script, result image, review record or decision note. Documents do not disappear in a model-based workflow. Their role changes: a document may summarize, approve or communicate evidence, but it must not hide the sources the decision depends on. Classify each artifact by purpose, record whether it is a source, a derived result, a review record or a communication, and never let a screenshot be the only record of a result.
1.3 Lifecycle information and engineering decisions
Mechanical development is not one calculation; it is a sequence of decisions under changing information. Early assumptions are replaced by measurements, supplier data, detailed geometry, simulation and test evidence. Digital engineering helps when it keeps the history visible: what changed, which artifacts were affected, and which decisions still stand. Treat a change as a review trigger, not a reason to panic, and mark assumptions that should be revisited later.
1.4 Authoritative sources and digital continuity
An authoritative source is the approved place to obtain a defined class of information for a defined context: one source for released geometry, another for requirements, another for test records, another for material data. Digital continuity is the ability to carry meaning across those sources without losing identity, status, configuration or review history. Define the information class before naming its source, use stable identifiers that survive folder moves, and check that a link preserves meaning, not just that it opens.
Engineering connection: this is the vocabulary the rest of the course builds on. Module 2 turns "controlled artifact" into a real register with identifiers, versions and baselines.
Worked example 1: is the bracket release defensible?
A student team says the bolted bracket is "ready for prototype." Judge whether that claim is defensible as digital engineering, not just as a set of files.
- ProblemDecide whether "ready for prototype" is a controlled, reviewable decision or an uncontrolled claim.
- Given / findArtifacts on hand: a CAD part, a requirements note, a hand stress check, a material pick, a test plan, a review comment. Find whether they support one defensible decision.
- ModelApply the course test: can another engineer find the requirement, model, input, result, assumption, review state and decision that belong together, all on the same baseline?
- SolveList each artifact and its role: requirement (criterion), CAD (geometry source), material choice (input), hand check (derived result), test plan (planned evidence), review note (decision record). Check they cite the same baseline B0 and that each has an owner and status. If the hand check used an older bolt pattern than the current CAD, they are not on the same configuration.
- CheckThe decision is defensible only when every supporting artifact is identified, current, compatible and reviewed. A missing owner, a stale input, or an unreviewed change breaks the chain.
- Conclusion"Ready for prototype" is an engineering decision, not a file state. It is defensible when the evidence is connected and reviewable, and not defensible just because the files exist.
Worked example 2: tracing an artifact's authority after a change
A supplier changes the bracket's alloy grade. Work out which artifacts become review candidates and which remain authoritative.
- ProblemA material substitution arrives late. Decide what it touches without overclaiming that "everything is now invalid."
- Given / findThe alloy grade changes. Artifacts: drawing, stress check, corrosion note, test evidence from an earlier prototype, release decision. Find the review candidates.
- ModelChange creates review candidates, not automatic invalidation. Ask, for each artifact, whether the changed property (material) was relevant to it.
- SolveStress check: material-dependent → review. Corrosion note: material-dependent → review. Drawing: material callout → update. Prototype test on the old bolt pattern: relevant only if the bolt pattern was unchanged → review candidate, judged on relevance. Release decision: depends on the above → hold until reviewed.
- CheckDistinguish "latest" from "authoritative": the newest file is not authoritative until approved for this baseline. Keep the earlier evidence visible with a review flag, not deleted.
- ConclusionRecording lifecycle context and authoritative sources up front is what makes this change analysis fast and honest instead of a guess.
Misconceptions and diagnostics
| Mistake | Diagnostic question | Correction |
|---|---|---|
| Digital engineering means more software | "Which decision became more inspectable because of the tool?" | A tool is useful only when it improves controlled, reviewable evidence. |
| A dashboard is a digital thread | "Can you trace from a value to its source artifact and configuration?" | A dashboard may display evidence, but it is not the evidence system by itself. |
| Model-based means document-free | "How will reviewers approve and communicate the decision?" | Documents stay useful when they summarize controlled sources instead of hiding them. |
| The latest file is always authoritative | "Who approved it, and for which baseline?" | Latest and authoritative are different properties; approval defines authority. |
| Old evidence is useless after any change | "Was the changed feature relevant to that evidence?" | Change creates review candidates; it does not automatically invalidate everything. |
Practice ladder
List five artifacts behind a simple bracket design, and mark which one is authoritative for geometry, for material, and for requirement status.
Show answer
For example: CAD part (authoritative for geometry), material register row (authoritative for material), requirement register row (authoritative for requirement status), hand-calc file (derived result), test plan (planned evidence). Authority is a property you assign per information class, not per file type.
Place five final-project artifacts on a lifecycle timeline (concept → design → analysis → test → release) and state the decision each one supports.
Show answer
Each artifact should name both a lifecycle moment and a decision, e.g. "load-case note (concept) → supports the sizing decision"; "hand stress check (analysis) → supports the material and thickness decision." An artifact with no decision attached is a candidate for removal.
Define three authoritative sources for the final project, write one stable-identifier rule, and find one likely break in continuity between CAD, analysis and test.
Show answer
Good work names the information class before the source ("released geometry → CAD vault"; "requirement status → requirement register"), gives an identifier rule that survives folder moves (e.g. BRK-CAD-001, not a file path), and identifies a real break, such as an analysis that imported a STEP export instead of citing the controlled CAD revision.
Build a one-page artifact map for one real project of your own: the decision at the centre, the artifacts around it, and an arrow from each artifact to the decision it supports.
What good work looks like
One named decision, every artifact carrying an owner and status, no orphan artifacts, and the authoritative source marked for geometry, requirements and results. This is the deliverable that Module 2 turns into a validated register.
Working with AI, and proving it yourself
Use AI as an examiner, not a solver
Portfolio task
Draft a candidate artifact list with AI, then verify every item against actual project files, delete unsupported entries, and add the owner, status and supported decision for each survivor.
Retrieval and spaced review
Closed notes. Answer out loud, then reveal.
1. What is the central principle of this course?
Engineering decisions should be supported by connected, controlled, reviewable and reproducible digital evidence.
2. What is the difference between digital tools and digital engineering?
Tools create or manage artifacts. Digital engineering controls and connects artifacts to decisions.
3. What is a digital artifact?
Any controlled digital item used or produced by engineering work: requirement, model, mesh, script, result, review record or decision note.
4. What is an authoritative source, and what does digital continuity preserve?
The approved source for a defined information class and context. Continuity preserves identity, meaning, status, configuration and review history across artifacts.
5. What does "change impact" mean here?
A reason to inspect potentially affected artifacts, not an automatic invalidation of all prior evidence.