NASA SE Handbook, in your students’ hands.
Blueprint runs against the NASA Systems Engineering Handbook (SP-2016-6105) as a multi-agent pipeline. Every artifact maps to a numbered Handbook section. Every claim cites its source — the same discipline you teach, surfaced automatically. Use it as the reference solution for graduate capstones, generate the SE pack for your next grant proposal, or let students iterate against it as they learn the artifact set from inside.
Free tier covers proposal-SE generation · no card required.
The math against a typical academic cycle.
Phase 1.1 through Phase D — every Handbook §6.7 deliverable.
Each agent maps to a Handbook section. The pipeline is the pedagogy.
3 runs / month — enough for a grant-proposal SE pack or a capstone reference solution.
15 projects. Covers coursework + research generation for one semester.
One grant proposal’s SE pack is one run. One semester of capstone reference solutions is ~10 runs. Starter ($29) covers a research advisor’s annual cadence with room for iteration; the Free tier fits when usage is project- specific.
What the reference pack looks like.
35 artifacts across the NASA SE Handbook §6.7 phases. Each artifact carries Handbook section references in the body — students see the section number next to the claim. The citation structure is the teaching point.
Stakeholder Expectations
- ·Stakeholder register
- ·Needs / Goals / Objectives tree
- ·MOEs + success criteria
- ·Operational scenarios (ConOps)
- ·Constraints register
Technical Requirements
- ·Requirements (Functional / Performance / Interface / Constraint)
- ·Shall-statements with rationale + citation
- ·MOPs traced to MOEs
- ·TPMs with thresholds
- ·Verification method per shall
Logical Decomposition
- ·Functional architecture
- ·Component breakdown
- ·DTRs (Derived Technical Requirements)
- ·Interface register
- ·Allocated baseline trace
Design Solution
- ·Design specs per component
- ·Interface specs (build-to)
- ·Trade studies + rationale
- ·Risk register
- ·Verification + Validation activities
- ·Enabling products plan
Phase-Gate Readiness
- ·SRR / SDR / PDR / CDR readiness assessments
- ·Per gate: entry status, exit status, blocking findings, recommendation
- ·Reference for what a graduate gate review actually looks like
Deep dives.
Three pedagogical angles, with the framing your faculty review committee will recognise.
MBSE coursework tool
Two-layer pedagogy — Cameo / Capella for notation + Blueprint for discipline. Use the SysML 2 / 1.x XMI exports to bridge both.
NASA SE Handbook citations
Two-layer citation — Handbook section reference + source brief chunk. The discipline made visible to students.
Graduate systems capstone tools
Two adoption patterns — reference solution post-submission, or live debugging with citation diffs. Pick one, run both in parallel.
Won’t this short-circuit the learning?
The citations are the answer. Every claim shows the Handbook section that justifies it and the DocChunk in the source brief that the agent extracted it from. Students don’t see “AI prose;” they see structural reasoning with traceable inputs.
Two patterns work in practice:
- Reference solution. Students submit their hand-built artifact set first. After the deadline, distribute Blueprint’s output for the same brief. The compare-and-contrast — “why did Blueprint cite §4.2.1 here? what did I miss?” — is where the learning lands.
- Live debugging. Give students Free-tier access. They run their own brief + iterate against Blueprint’s output. The citations expose the reasoning gap in their writing. Office hours become “why is my MOP traced wrong?” rather than “how do I format this section?”
Pedagogy doesn’t require students to invent the template. It requires them to understand why the template is shaped the way it is. Blueprint shows that shape with citation receipts.
Pricing for research + teaching.
3 runs per month
Most grant proposals fit here
Students sign up free for live debugging
15 projects per month
Cover coursework + research generation
A semester’s reference-solution cadence
100 projects per month
When the lab runs multiple cohorts + active research
Larger lab + multiple advisors
Students individually on Free tier; the lab advisor on Starter or Pro depending on cadence. Institutional license (SSO, billing-on-grant) is roadmapped post-MVP — reach out if your institution needs that today.
Try it on the brief from your last graduate capstone.
- 1
Sign up free
Email + Google or GitHub. No card. ~30 seconds. Use your university address if you want.
- 2
Upload a brief
A past capstone brief, a draft grant proposal, or a NASA-published mission concept. 1,000–3,000 words. Anything your students would otherwise have to read + summarize.
- 3
Generate, then assign
10–15 minutes later you have the reference pack. Bundle as `.zip` of markdown or download per-format standards exports. Distribute to students after their submission, or open the citations panel and walk through how the agents reasoned.
Questions advisors ask.
Is this just letting students copy-paste an AI-generated pack?
Only if you use it that way. The patterns above (reference solution distributed after submission; live debugging where students compare their work to Blueprint's) preserve the learning. The citations are what make this distinct from a generic generator — students see the structural reasoning, not just the output.
Will students cite Blueprint as a tool in their thesis?
Yes, and they should. Blueprint generates artifacts; the engineering judgment is the student's. Citing tools used (software, references, datasets) is standard scholarly practice. Treat Blueprint the way you treat MATLAB, ANSYS, or a SysML editor — it's instrumentation.
What about academic integrity policies on AI?
That's your institution's call. Many programs have moved to a transparency-required position: students disclose AI tool use + explain how the tool's output was integrated. Blueprint's citation structure makes that disclosure easy — students can point to which claims came from their own analysis vs which were Blueprint's. If your institution prohibits AI tools entirely, Blueprint is for your own use as the advisor, not for students.
Can the lab buy an institutional license?
Today: each student + advisor signs up individually on Free / Starter / Pro per their cadence. Institutional licensing (SSO + per-seat billing + grant-billable invoices) is roadmapped. If your lab needs it now, reach out — limited early-access program exists.
Does this replace teaching SysML / Cameo / Capella?
No. Blueprint generates the work product the modeling language describes. Use the SysML 2 / SysML 1.x XMI exports to drop Blueprint output into Cameo / Capella for a model-tool exercise. The two layers complement: Blueprint teaches what artifacts say; the modeling tool teaches how they're represented in notation.
What about citing the NASA SE Handbook itself in our research?
The Handbook (NASA SP-2016-6105) is public, citable, and is exactly what Blueprint's pipeline implements. The graph schema mirrors the Handbook's product-model concepts (Stakeholders, MOEs/MOPs/TPMs, NGOs, requirements, decomposition, V&V, gates) one-for-one. When your students cite §4.2.1 in their requirements doc, that's a Blueprint citation showing exactly where the section maps in the output.
Show your students what the Handbook looks like, working.
Free tier. No card. 3 runs a month. Run one against last semester’s capstone brief and compare what Blueprint produced to what your students built. The pedagogy is in the comparison.
Start free →