| 0 |
|
| 1 |
- EPICS integration is planned.
- A decision on the implementation of the IOC is made.
|
| 2 |
- Device support for the component is ready.
- Firsts tests confirm that the chosen implementation is viable.
|
| 3 |
- Basic functionality of the component is implemented in the IOC.
- Confirmed with successful operation under testing conditions.
|
| 4 |
- The component can be safely operated and monitored from the IOC alone.
- It does not need frequent manipulation via other means.
- The record database includes useful settings for
- alarm thresholds
- hardware limits
- scan rates
- units and value conversion
- deadbands
|
| 5 |
- All functionality needed for operation during experiments is implemented in the IOC.
- No physical access to the component is required to start up the IOC, operate the component as needed, and shut down the IOC.
- Stable long term operation is possible.
- State of the IOC can be saved and restored on demand using autosave (preferred) or BURT.
|
| 6 |
- Process variable lists are available (preferrably automatically generated) that are used in external tools, such as the database archiver, the datastream archiver, the gateway.
- Mapping from hardware channel addressing to physical detector channels (e.g. hostX:busY:moduleZ:channelA -> detA:scintillatorB:pmtC) is done via record aliases.
|
| 7 |
- High level controls and monitoring of the component IOC allow integration with other components of the sub-system.
- Parameters for different states of operation are defined.
|