Specification

Flux is an AI hardware engineer. Use a Project Specification to agree on what your greenhouse soil-moisture monitor must do before you design it.

Define the product requirements

Ask Flux to record measurable requirements, constraints, and decisions in the Project Specification.

Write a Project Specification for this greenhouse monitor. Include its users, moisture range, number of probes, reading interval, and success criteria.

Add the operating environment, battery life, phone connection, charging method, and installation requirements. List decisions that need my input.

In Files, select New in the Documents panel to create a project document. See Project files.

Set constraints and acceptance checks

Ask Flux to connect each requirement to a measurable test or design constraint.

Add a requirement that the monitor reports soil moisture at the selected interval and runs for the specified battery life.

List the enclosure, probe, and charging constraints that affect the board design. Add an acceptance check for each one.

Open Files, select New in Documents, and record the requirements in the Project Specification. Keep units and pass criteria with each requirement.

Make the design plan

Ask Flux to turn the agreed specification into a plan for the enclosure, board, firmware, and tests.

Create a design plan for this monitor. Start with its enclosure and mounting needs, then plan the electronics, firmware, and tests.

Link each design task to a requirement in the Project Specification.

Specify the operating conditions

Ask Flux to describe the conditions that the monitor must handle. Include greenhouse temperature, humidity, water exposure, sunlight, soil range, installation location, and expected maintenance.

Add operating conditions for a greenhouse monitor installed near watering lines. Include condensation, splashes, direct sun, and seasonal temperature changes.

List the soil moisture range, probe depth, reading interval, wireless range, and battery run time that the design must meet.

Open Files, select New in Documents, and create or update the Project Specification. Record the value, unit, source, and acceptance check together. This keeps product decisions in one place while the enclosure, schematic, and firmware change.

Write a measurable requirement for the sensor range and reading interval.
State the expected battery life and the duty cycle used to estimate it.
Record the wireless connection and the distance from the monitor to the phone or gateway.
Add the installation position, probe length, cable route, and charging access.
Ask Flux to list values that need a product decision.

Separate requirements from design choices

Ask Flux to keep product outcomes separate from implementation choices. A requirement states what the device must do. A design choice records how the current project meets that requirement.

Separate the monitor requirements from the proposed design choices. Keep the moisture range, run time, and installation workflow as requirements.

List open choices for the probe, controller, battery, enclosure material, and phone connection. Link each choice to a requirement.

Use the Project Specification to record agreed outcomes. Keep part numbers and circuit details in the schematic, and keep enclosure dimensions in the mechanical design. Ask Flux to summarize decisions that affect more than one area. For example, the battery choice affects enclosure volume, mounting, charging, and firmware power estimates.

Group requirements by user behavior, electrical performance, mechanical fit, and manufacturing.
Identify dependencies between the probe, connector, board outline, cable opening, and housing.
Record each accepted design choice and the requirement it satisfies.
Update the document when the team changes a product decision.

Define acceptance checks and project records

Ask Flux to turn each requirement into a check that you can complete during design or bring-up.

Add an acceptance check for battery life, probe readings at dry and wet soil levels, wireless reporting, and charging access.

Create a verification table with requirement, method, expected result, and project evidence for this monitor.

Open Files, select New in Documents, and keep the acceptance table with the Project Specification. Create project documents for test results, datasheet findings, and design notes when those records need their own structure. Flux can also create an interactive project page for a checklist or calculation. Ask for inputs and outputs that match the requirement you want to evaluate.

Name the requirement being checked.
Describe the measurement or inspection that provides evidence.
State the expected result with units and tolerances.
Link the check to the schematic, firmware, board, or enclosure feature.
Record the result with the project files when the check is complete.

Review the specification after each major change. Ask Flux to list the requirements affected by a board, enclosure, probe, or battery update before you continue.

Ask Flux to keep the Project Specification aligned with the design as the project changes.

Compare the current monitor specification with the board, enclosure, and firmware. List requirements affected by the changed battery and probe.

Update the acceptance table with the test evidence for charging access, moisture readings, and battery run time.

Use Files to update the Project Specification and related project documents. Keep the requirements, acceptance checks, and design decisions connected to the same greenhouse monitor revision.

Continue with Industrial design and concept.

Last updated on

Was this page helpful?