How this design information was used in developing the event sequence. Describes the specific application and relevance of the design information.
Optional
assumptionsAny assumptions or limitations in applying this design information. Documents important considerations when using this design information.
Optional
dateDate of the source document
Optional
descriptionDescription of the design information
Optional
requirementRequirement identifier for traceability
Optional
revisionDocument revision identifier
Identifier for the design source document
Type of source document (e.g., "drawing", "calculation", "specification")
Optional
standardSection number in relevant standard (e.g., NRC RG 1.247)
Specific aspects of the event sequence supported by this design information. Indicates which parts of the event sequence this design information is used to support.
Optional
operatorActions?: booleanWhether this supports operator actions (e.g., access paths, control locations)
Optional
phenomenologicalImpacts?: booleanWhether this supports phenomenological impacts (e.g., environmental conditions, physical phenomena)
Optional
successCriteria?: booleanWhether this supports success criteria (e.g., system capabilities, performance requirements)
Optional
systemDependencies?: booleanWhether this supports system dependencies (e.g., physical connections, shared components)
Optional
timing?: booleanWhether this supports sequence timing (e.g., system response times, mission times)
Interface representing design information specific to event sequences. Used to document the design basis and technical information supporting event sequence development.
Example
Implements
ES-D1