Source-linked claim register
Prepared for review within the agreed scope.
CEA decision context
Supplier evidence and configuration comparison
Determine which supplier or equipment alternative satisfies the stated requirements and what remains unresolved before selection.
Decision to be made
Supplier evidence and configuration comparison
Determine which supplier or equipment alternative satisfies the stated requirements and what remains unresolved before selection.
Project context
Where this workflow applies
A bounded comparison of supplier statements, operating conditions, exclusions, units, configuration alternatives and project requirements.
Material inputs
Begin with permissioned, relevant evidence.
High-level project baseline, source material categories, requirements, assumptions, alternatives and responsible roles are agreed before detailed processing.
Platform workflow
Use the same six-step decision workflow.
Establish the baseline, capture source claims, map requirements and alternatives, build design cases, review uncertainty and dependencies, then record and carry forward the decision.
Reviewed outputs
Name the record required for the decision.
Outputs are specific records, not a generic product claim.
Comparison matrix
Prepared for review within the agreed scope.
Missing-condition record
Prepared for review within the agreed scope.
Clarification log
Prepared for review within the agreed scope.
Configuration design cases
Prepared for review within the agreed scope.
Reviewed selection record
Prepared for review within the agreed scope.
Responsible parties
The record does not transfer authority.
The organisation owns its decision; suppliers own their claims and commitments; relevant professionals own technical, legal, safety and regulated review within their scope; Crop Urbanis performs only the work included in the agreed engagement.
Current product boundary
Capability availability follows the canonical status register.
Capability availability depends on current Platform status and the separately agreed project or beta scope.
Status and resources
Continue with the canonical source.
Review current Platform status for implementation and validation; use Technology for architecture and Research for research maturity.
Current Platform status
Implementation, limitations and roadmap.
Technology
Architecture and technical governance.