Manage Integrated Observatory system and respond to requests
|Actors||Integrated Observatory Operator|
|References||UC.R1.28 Operate System|
|Uses||UC.R2.39 Manage ION Users
UC.R2.40 Monitor ION Resources
UC.R2.52 Manage ION Processes-Deprecated
UC.R2.37 Control Service Interactions
UC.R2.55 Manage Help Ticket
UC.R2.56 Monitor ION Network
UC.R2.44 Define Service Type During Runtime
|Is Used By|
|Is Extended By|
|In Acceptance Scenarios||AS.R2.01A Operate Marine Observatory, AS.R2.01C Operate Integrated Observatory Network|
|Technical Notes||The R1 use case was achieved at a basic level for operations available in that release.
This use case applies to a much richer set of operations that can be managed in the Integrated Observatory Network.
|Primary Service||COI Resource Lifecycle Services|
|UC Status||Mapped + Ready|
This information summarizes the Use Case functionality.
Perform critical tasks needed to keep the system operational: log in as the operator, allocate system resources, define policies, monitor the network, report issues and actions taken on them, and log out when finished.
- The Integrated Observatory Operator role has all the access permissions needed to perform the necessary functions.
- Some operations may be handled outside the Integrated Observatory, for example in Jira or with external software.
System is operating normally, new operator is not yet logged in.
- Integrated Observatory Operator logs in at beginning of shift.
- Integrated Observatory Operator monitors system displays and messages for issues.
- Integrated Observatory Operator allocates system consumables and defines policies as needed to meet the objectives of the system users and operations teams.
- Allocation of system consumables (disk space, CPU time) takes place in response to system use of those resources. See UC.R2.40 Monitor ION Resources.
- Integrated Observatory Operator manages Resources to satisfy user and operator objectives.
- This includes setting the life cycle state of resources to enable or disable their use or visibility.
- It also includes commanding resources using commands common to all resources (start, stop, reset).
- Integrated Observatory Operator logs requests and their resolutions in issue tracking system.
- Operator requests and suggestions for changes to system are logged in this same issue tracking system. See UC.R2.55 Manage Help Ticket.
- <3> Integrated Observatory Operator can start the system or parts of the system, with a given configuration and deployment policy
- <3> Integrated Observatory Operator can shut down the system or parts of the system in a controlled way
- This also includes shutting down the system in a test, staging, QA, user or any different installation
- No actual shutdown of the primary operational system is intended (though it might be needed in a pinch in Release 2).
- Integrated Observatory Operator logs out at end of shift, saving user interface and other relevant settings.
- Limited settings will be maintained locally to each user in Release 2.
System is running normally, operator has performed necessary functions during shift.
These comments provide additional context (usually quite technical) for editors of the use case.
This use case only addresses operating the Integrated Observatory Network. The operation of marine observatories and components is addressed in S&A use case, for example UC.R2.11 Define Marine Observatory Resources and Policy, UC.R2.10 Manage Marine Platform, and UC.R2.08 Manage Instrument Lifecycle.
The emphasis of this use case is the high-level capabilities required to operate the Integrated Observatory.
Many of the individual steps rely on CEI services, but the forms for those services weren't obvious when the use case was released.
In Release 3, the management of service level agreements with users and execution site providers will be an important part of these capabilities.