Engineering Delivery and Business Value
First Enquiry, Discovery and Feasibility
Follow a rational path from initial discussion to a funded engineering feasibility study.
You are moving a project through the decision covered by “First Enquiry, Discovery and Feasibility” and need evidence before the next commitment.
Understand what belongs in an initial enquiry, what a defined paid discovery should produce, and how a feasibility study converts important unknowns into evidence for a go, conditional-go, hold or no-go decision.
- Select or check first
- Payment does not predetermine the answer. A valuable study may conclude that the original idea should change, wait, use a standard product or stop. Its value lies in producing decision-quality evidence within the agreed scope.
- Controlling assumption
- Requirements, exclusions, evidence, responsibilities, acceptance criteria and change control are explicitly agreed.
- Top risk
- Copying a diagram, rating or example without matching the real topology, duty, environment and failure consequences can produce an unsafe or misleading result.
- Proof
- Check the exact manufacturer data, units and limits, then verify the result by calculation, measurement or a controlled acceptance test.
Start with the basics Optional foundation before “First Enquiry, Discovery and Feasibility”
Engineering-project basics
A build becomes controllable when the need, assumptions, interfaces, evidence and ownership are written before hardware choices become difficult to reverse.
- Requirement
- A requirement states a necessary, testable outcome or constraint. A preferred solution is not automatically a requirement.
- Assumption
- An assumption is treated as true for a decision but still needs an owner, evidence and a plan for what happens if it is wrong.
- Verification and validation
- Verification asks whether the design meets its specified requirements. Validation asks whether the delivered result solves the user’s real need in its intended setting.
- Prototype and production release
- A prototype answers selected questions. Production release additionally needs controlled parts, repeatable assembly, acceptance evidence, service information and change control.
- Scope and change control
- Scope defines included work, deliverables, interfaces and exclusions. Change control records why an approved baseline changes and what cost, schedule or risk follows.
How to use this article: For every decision, record the owner, evidence, acceptance criterion and condition that would force the decision to be reopened.
On this page
An enquiry, a discovery engagement and a feasibility study are three different commitments. The enquiry tests whether there may be a sensible problem to explore. Discovery defines the question, evidence and deliverables of professional investigation. Feasibility then examines the most important technical, operational and commercial uncertainties. Keeping these gates distinct prevents a friendly first conversation from being mistaken for a quotation, design or promise to build.
A useful first enquiry describes the situation before prescribing the machine
Diagram description
The proposed handling machine and four-step path are illustrative. No site survey, engineering analysis or supply commitment is shown.
| Describe | Useful details | Avoid assuming |
|---|---|---|
| Current operation | People, sequence, equipment, cycle, shifts and known interruptions | That the visible manual step is the true constraint |
| Object or process | Range of sizes, mass, materials, variation and sensitivity | That one sample represents production |
| Desired outcome | Quality, rate, exposure, traceability, energy or service target | That “fully automatic” is a measurable requirement |
| Site context | Space, utilities, environment, access and connected equipment | That a concept can be installed without interface work |
| People and safety | Operators, maintainers, bystanders, access and foreseeable interventions | That guards alone resolve every hazard |
| Business boundary | Timing, decision owner, investment range and reason for change | That a budget is a fixed quotation or proof of viability |
Photographs, short videos, process records, representative parts, drawings and nameplates can make an initial discussion concrete. Sensitive information should be shared through an agreed channel and only to the extent needed. The engineering team should state what has not been checked: an image cannot confirm dimensions, structural capacity, electrical condition, software ownership or safe access.
Use three decision gates with explicit outputs
| Gate | Main purpose | Typical output | What it is not |
|---|---|---|---|
| Initial enquiry | Check alignment, urgency and obvious constraints | Recorded problem statement, open questions and proposed next step | A completed design or firm performance commitment |
| Paid discovery | Define investigation scope and gather controlled evidence | Agreed study plan, assumptions, interfaces, deliverables and responsibilities | Unlimited consulting or hidden production engineering |
| Feasibility study | Test critical uncertainties and compare bounded concepts | Evidence, risks, options, estimate range and decision recommendation | Proof that detailed design and commissioning will be problem-free |
A paid discovery phase needs a defined statement of work
Diagram description
The screens, analysis and drawings are illustrative; actual deliverables depend on the signed discovery scope and available evidence.
| Scope item | Questions to settle |
|---|---|
| Decision to support | What decision will the study enable, who makes it and by when? |
| Inputs | Which samples, records, drawings, site access and subject experts will be available? |
| Activities | Which surveys, measurements, calculations, concept comparisons or trials are included? |
| Deliverables | Will outputs include requirements, concept layouts, risk register, tests, assumptions or estimate ranges? |
| Exclusions | Which detailed drawings, code, certification, procurement or production work is outside the phase? |
| Ownership and confidentiality | Who may use the outputs, models and data, and what remains background intellectual property? |
| Acceptance | How will completion, review comments and corrected deliverables be handled? |
| Change control | What happens when new evidence changes the time, question or scope? |
Feasibility is a structured attack on the largest unknowns
Diagram description
The machine and review sheet are conceptual. They do not represent a certified design, verified calculation or approved risk assessment.
| Area | Representative question | Possible evidence |
|---|---|---|
| Process | Can the operation achieve the required result across representative variation? | Sample trials, measurement study and failure cases |
| Mechanical | Can the structure, motion and tooling carry loads with acceptable life and tolerance? | Calculations, vendor data, models and targeted tests |
| Electrical and controls | Are power, sensing, actuation, interfaces and failure states practical? | Load schedule, I/O concept, communications survey and state analysis |
| Safety | Which hazards exist over use, setup, cleaning, maintenance and foreseeable misuse? | Documented risk assessment and risk-reduction concept |
| Environment | Will heat, dust, water, vibration, corrosion or electromagnetic conditions matter? | Site data, ratings review and environmental test plan |
| Integration | Can the concept coexist with buildings, utilities, networks and adjacent equipment? | Interface register, site survey and responsibility map |
| Operation | Can people run, recover, clean and maintain it with available skills? | Use cases, off-normal scenarios, access review and training concept |
| Delivery | Are cost, schedule, supply and support credible enough for the next decision? | Range estimate, assumptions, lead-time evidence and risk register |
Not every uncertainty needs a prototype. Some are resolved by a measurement, calculation, drawing review or authoritative component data. Others need a bench test because the interaction is not predictable with enough confidence. The study should explain why each method is proportionate, record assumptions and show residual uncertainty instead of converting it into false precision.
Finish with a decision, not a folder of unexplained files
| Outcome | Meaning | Minimum record |
|---|---|---|
| Go | Evidence supports the next defined phase | Selected concept, requirements baseline, risks, budget range and next authorization |
| Conditional go | Progress is sensible after named conditions are met | Condition owner, evidence required, due point and effect if unmet |
| Hold | The idea may be viable but timing, inputs or business case are not ready | Reason, information gap and a review trigger |
| Redirect | A different process, standard product or smaller intervention fits better | Comparison and consequences of the recommended alternative |
| No-go | Risk, capability or economics are outside the accepted boundary | Evidence, assumptions and conditions that could change the conclusion |
A go decision authorizes only the next agreed phase; it is not production acceptance in advance. Preserve traceability from the original need through requirements, evidence and unresolved risk, then define how later verification will be recorded. The distinction between an encouraging demonstration and accepted equipment is explained in Prototype Proof Versus Production Acceptance. A clean study leaves both parties able to see what is known, what is assumed and what must happen next.
Selection boundary and evidence to keep with the decision
Treat “First Enquiry, Discovery and Feasibility” as a selection problem, not only a definition. Record the required result, alternatives considered, the controlling assumption and the condition that would change the choice.
Keep evidence proportional to consequence: Check the exact manufacturer data, units and limits, then verify the result by calculation, measurement or a controlled acceptance test. Revisit the decision when the load, environment, duty, interface, regulation or maintenance plan changes.
One-minute questions
Questions to answer before you apply this lesson
What should I select or check first for First Enquiry, Discovery and Feasibility?
Payment does not predetermine the answer. A valuable study may conclude that the original idea should change, wait, use a standard product or stop. Its value lies in producing decision-quality evidence within the agreed scope.
Which assumption can change the conclusion?
Requirements, exclusions, evidence, responsibilities, acceptance criteria and change control are explicitly agreed.
What can go wrong if I copy the example directly?
Copying a diagram, rating or example without matching the real topology, duty, environment and failure consequences can produce an unsafe or misleading result.
How do I verify the result in the real system?
Check the exact manufacturer data, units and limits, then verify the result by calculation, measurement or a controlled acceptance test.
Sources and further reading
- Systems Engineering Handbook: 4.1 Stakeholder Expectations DefinitionNational Aeronautics and Space Administration · 2026-10-13Primary handbook material reviewed for stakeholder identification, operational scenarios, measures of effectiveness, agreement, baselining and early capture of off-nominal conditions.
- Systems Engineering Handbook: 4.0 System Design ProcessesNational Aeronautics and Space Administration · 2026-10-13Primary handbook material reviewed for transforming stakeholder expectations into requirements, defining constraints, comparing alternatives through trade studies and documenting design decisions.
- Safety of machinery — General principles for design — Risk assessment and risk reduction (ISO 12100:2010)International Organization for Standardization · 2026-10-13Official standard record reviewed for machinery life-cycle hazard identification, risk estimation, risk evaluation, reduction, documentation and verification.