Classes / Shared specialties / Command Department
Command Track: Contracts, Money, Hiring and Planning · Module 4 of 4 · about 30 min
Planning technical work
NASA uses Technology Readiness Levels (TRL) from 1 to 9 to say how mature a technology is. TRL 1 is basic principles observed. TRL 9 is an actual system proven in operations. Being honest about TRL keeps plans and budgets grounded.
The NASA Systems Engineering Handbook lays out a disciplined way to build complex things: define what the system must do, write requirements, design, verify that it meets them and validate that it solves the real problem. Small crews can use a light version of the same steps.
Every plan needs a few things: a clear goal, a scope that says what is out as well as in, a schedule with the critical path, a budget, named owners and a list of risks with what you will do about each one.
A business plan does the same for the company. The SBA's guide covers the market, the offer, operations, management and financial projections. The point is not the document; it is thinking through how the business will actually make money before you spend it.
We separate technology maturity, requirement compliance and usefulness in the intended operation. NASA's readiness levels describe demonstrated maturity with a relevant environment and system scope. A component's strong history does not establish that a changed integrated system has the same maturity. A slide claiming a level is not the supporting demonstration evidence.
Verification asks whether the realized product meets the specified requirements. Validation asks whether it meets the intended stakeholder use in its actual or appropriately represented environment. A product can pass a narrow specification and still be unsuitable if the requirement omitted an important user need. The NASA handbook also warns against transferring prior verification of reused hardware into a new application without assessing equivalent requirements and environments.
Worked example, fictional review: a tool meets its stated weight and output requirements but cannot be used by the intended crew in the required workspace. Passing those measurements does not establish operational usefulness. A separate prototype worked in a laboratory but is described as already proven in mission operations without the required evidence.
Practice, on paper: we map invented needs, requirements, methods, results and remaining assumptions. Our self-check separates maturity, verification and validation rather than treating one pass label as all three. We approve no design, conduct no hazardous test and claim no flight readiness.
Sources
- NASA: Technology Readiness Levels
- NASA Systems Engineering Handbook
- SBA: Write your business plan
- NASA Systems Engineering Handbook: Product realization
Module quiz
10 questions, 8 correct to pass. You'll see what you missed and why, and you can retake it.