Generic input-output logic and data schema
Awaiting source text
This section is a heading in the source handbook with no text beneath it yet. Nothing has been written here in its place.
What is known so far
There is no generic schema in the source, but there are concrete ones. Each of the technical processes ends with an output schema defining what it hands to the next stage:
| Process | Its output schema |
|---|---|
| Asset and network evaluation | Output schema |
| Problem framing and scope | Output schema |
| Risk reduction analysis | Output schema |
| Detailed option assessment | Output schema |
| Portfolio optimisation | Output schema |
The definition of a module also requires that every module declare specific inputs and outputs and clearly defined information flows. See What makes something a module.
What this page should cover
The generic form underneath those specific schemas: the common fields, the data types, and the rules an additional module would have to satisfy to interoperate.
This is the section a team would need before extending the DSP with a new module.