´óÏó´«Ã½

Architecture Overview

Each event contains a complex set of data that defines, bounds and constrains the who, what, where, when, how and why to support automated validation, execution, and verification of that event. This data includes:

Metadata: Defines the basic information about the event: Its name, description start/stop time and relationship to other events.

Resources: Models of physical items and their properties that are tracked in the plan. Examples include spacecraft with orbit vector property, battery with power property and operator crew with hours worked.

Budgets: Metrics used to allot consumable properties on some resources used during the event, like 10 kilograms of fuel mass over a maneuver.

Operations: Scripts that connect to external simulation modeling tools which calculate resource properties over the event.

Constraints: Limitations placed on resource properties. For example, Sensor pointing has a Sun keep out of XX degrees.

Objectives: Shows the mapping of what mission objectives this event is meant to satisfy. Allows the planners to verify that the planned mission satisfies all end-user objectives.

Events can be decomposed to the nth level. The decomposition should go down to the level at which an appropriate operation can be used to simulate the desired behaviors with operator scripts or commands. The organization and decomposition of events is flexible, allowing separate missions to each implement their own standards.