Concept of Operations - CalgaryToSpace/CTS-SAT-1-Wiki GitHub Wiki

"The purpose of this document is to document everything we expect from the system, from the point of view of someone operating it" - Kaleigh Beer

'2.0 System Scope' = "This section gives an estimate of the size and complexity of the system. It defines the system’s external interfaces and enabling systems. It describes what the project will encompass and what will lie outside of the project’s development." - Kaleigh Beer

'2.3 Enabling Systems' = "Any systems outside of the operational environment that support the lifecycle activities of the satellite (e.g. test, installation, maintenance, project organization)" - Kaleigh Beer. Parker Link also clarified that assembly tools, such as the laminar flow table, fall under this subsection.

'3.0 Description of Envisioned System' = "This section describes at a functional level the various elements that will make up the system, including the users and operators. These descriptions should be implementation free; that is, not specific to any implementation or design but rather a general description of what the system and its elements will be expected to do." - Kaleigh Beer

'3.4 Modes of Operation' = "Make sure we distinguish between the software states and the satellite modes. e.g. “Data collection” mode is when the satellite operates the MPI, but the software state would be “nominal operations” both while collecting data and while waiting for a telecommand" - Kaleigh Beer

'3.4.6 Pointing Mode' = "Used for acquiring nominal attitude as well as rolling the satellite" - Kaleigh Beer

'3.5 Proposed Capabilities' = "These capabilities cover the entire life cycle of the system’s operation" - Kaleigh Beer

Very quick edit of what's in the ConOps & what different sections mean & include. Needs to be formatted better, & highlighted to SAT-2

In the development & completion of the ConOps, it should be noted that if one image is chosen to be a high-level diagram at a certain time, its structure must be preserved (in the sense of orientation, labelling conventions, etc), and that the changing of components needs to be easy to illustrate. Perhaps it is best to use some form of layer-based drawing software, w/ a common scale between individual images to make it easy to replace, highlight, remove, & add them to it. Assuming all these are kept w/in a large 3D model, this can be done by getting screenshots of the model at the same zoom level & have them be individual layers, labelled for final production.