...
OSD - Observation Specification Disposition
PPR
To determine what time is available for the new proposals, I first have to build an Available Time Model (ATM). The ATM needs to know about pre-commited time from previous approved proposals (e.g., multi-semester, monitoring), sponsored time, maintenance periods, tests, and then also carry-over from the previous semester. I want to be able to import files to specify this information, inspect the imported information, and modify it on the fly as I need. The ATM also depends on the weather and the hardware sometimes (e.g., VLA configuration).
...
Small adjustments in the ATM or and OSD can have big consequences for the available time. As a scheduler, I explore how these changes can make an efficient schedule. As there are a lot of working parts though (many proposals, many inputs to the ATM), I like to return to previous states to assess the impact of a small adjustment. I would like to be able to save a version the schedule so I can return to it later if needed. I would like a detailed version history so I can inspect many different versions if I need to.
| Expand |
|---|
| title | user storiesVersion Control |
|---|
|
As a scheduler I would like version control on my work so I can easily access different versions of the schedule I am building. |
|
| As a scheduler, I want to be able to give the versions a useful name so I can keep track of my work versus other schedulers changes. |
| As a scheduler I want to be able to an AD back to the what the AR was so I can start fresh. |
|
Now that I have the ATM, I can start to assess how the new requests will fit into it. I will need to modify the requests but I want to preserve the original request too. I likely will need to do detailed modifications, like to the sources, resources, or requested time, but sometimes I only want to do broad changes, such as total time. Sometimes these changes will have profound impacts on the intent of the request so I want to make sure I can let the PI and the TAC know about these proposed changes. My main intent is to determine preliminary scheduling priorities and to make sure the information needed for the TAC is accurate.
| Expand |
|---|
| title | user storiesModifying OSDs by Hand |
|---|
|
As a scheduler I want to each Observation Specification Disposition to have a Scheduling Priority. |
|
|
|
|
|
|
|
| As a scheduler I want to copy the OSs associated within this Solicitation into Observation Specification Dispositions (OSDs) so I can modify the OSDs without modifying the OSs. | As a scheduler I would like to inspect the ADs:OSDs associated with this Solicitation so I can decide if their information is accurate. | As a scheduler I would like to modify ADs:OSDs as needed so I can update their information. | As a scheduler I want to see the SRP’s review of about the proposal. | As a scheduler I want to set a “Manual Construction Required” flag per OSD so the proposer will know they have to regenerate their OSs before observing. | As a scheduler I want an OSD to have one Scheduling Priorities (SP) of either A, B, C, F, and N. | As a scheduler I want to set manually the Scheduling Priority (SP) for OSDs. |
|
| As a scheduler I want to know which OSDs were System Generated vs User Generated. | As a scheduler I want to modify the total duration, repeat count, and LST range of an OSD.** | As a scheduler I want to see the Science Comments to PI, Data Management Comments to PI, Technical Comments to the PI and all of the equivalent Internal Comments. |
| As a scheduler I want the ADs with external facilities to be handled differently than internal facilities because their approval process is a different. | As a scheduler I want to know which OSDs need to be modified. |
|
|
| As a scheduler I want to update the information in the Science Target List associated with a OSD***. | As a scheduler I want to know the Scientific Merit Metric of the Proposal. |
| As a scheduler I want ADs with external facilities to either be approved or declined instead of having scheduling priorities. | As a scheduler I want to change the SP of an OSD between any defined in the system. |
|
|
| As a scheduler I want to enter Internal Comments for the TAC on each AD so I can keep notes about my process. |
|
|
| As a scheduler I want to be able to filter on the list of ADs:OSDs so I can easily inspect them. |
|
|
| As a scheduler I want to enter TAC Comments to the PI for each AD so I can prepare for the TAC. |
|
|
| As a scheduler I want to bulk edit the SP of a selected set of OSDs. |
|
|
|
|
|
|
| As a scheduler I want to be able to filter by Proposal ID. |
|
There are some tasks that would be useful if they were automated, as it would take me too long to compile the data by hand. For example, I need to identify source conflicts based on a variety of criteria. I also want OSDs associated with external facilities to be handled differently than OSDs of internal facilities. Finally, I want to use algorithms to help efficiently assign scheduling priorities to OSDs as it may well enough for most cases. That frees up time for me to concentrate on the edge cases and optimization. It is important that I can control which OSDs are having their SPs modified, so I would like a way to "lock" out changes temporarily so neither the system nor a manual edit can be applied until it is unlocked.
| Expand |
|---|
| title | user storiesModiying OSDs with the System |
|---|
|
As a scheduler I want to identify Source Conflicts in the OSDs so I can make a note of them for the TAC. | As a scheduler I want ADs/OSDs that request multi semester observations to be clearly identified in the UI so I can understand how they impact future semesters. | As a scheduler I want the system to generate SPs for OSDs because the algorithm may do the majority of the cases sufficiently. | As a scheduler I want to be able to initiate process multiple times so I can iterate on the assigned SPs given a ATM. |
|
| As a scheduler I want OSDs with SPs of N to not be modified by the algorithm because these OSDs will not be scheduled. |
|
|
| As a scheduler I want OSDs with SPs that are locked to not be modified by the algorithm so the SPs of those OSDs do not change. |
|
|
| As a scheduler I want OSDs with SPs of F to not be modified by the algorithm because these are fixed dates. |
|
|
| As a VLA scheduler I want the automated algorithm to be the Prioritizer. |
|
|
| As a scheduler I want to be able to modify a system generated SP because I know better. |
|
|
...
| Expand |
|---|
|
As a scheduler I want to create a Facility Report so I can provide a narrative about the scheduling issues of my Facility which includes an LST (orGST) pressure plot. | As a scheduler I want to create a Proposal Summary so there is a list of relevant information for each proposal which provides context for the TAC meeting discussion | | As a scheduler I want the version of the schedule to be included in the Facility Report and for it then to not change for the TAC meeting so I can keep editing a new version while the TAC is deliberating. | As a scheduler I want the version of the schedule to be included in the Proposal Summary and for it then to not change for the TAC meeting so I can keep editing a new version of the schedule while the TAC is deliberating. | | As a scheduler I want a way to trigger deployment of an updated Facility Report for the TAC to see. | As a scheduler I want a way to trigger deployment of an updated Proposal Summary for the TAC to see. |
|
OSR
As a TTA member for the OSR process, one or more of us will collaborate on reviewing a proposal. Typically for proposals in the OSR process, we don't modify the requests to the extent as in the PPR process: we either accept what they have proposed or decline it. It would be good to have the same tools to edit OSDs as the PPR process, but I won't define ATMs and build reports because this is just one proposal. I will have external information to understand the available time and if this proposal can be accommodated. After modifying OSDs, as a TTA member I perform the Science and Feasibility reviews as well as form the recommendations for Proprietary Time, Approved Time, Scheduling Constraints, and Scheduling Priorities. I need to modify these attributes and provide OSC Comments to the PI and Internal Comments for the OSC in case I want to capture any specific comments for the Director's Delegate's review or the PI. Once I have made my recommendations, I want to finalize and generator the report for the Director's Delegate's review.
| Expand |
|---|
| title | Recommended Allocation Dispositions for OSR |
|---|
|
| As a TTA member I want each OSD to have a scheduling priority. |
|
|
| As a TTA member I want the same tools as the "Modifying OSDs by Hand". | As a TTA member I want to modify OSC Comments to the PI and Internal Comments from the OSC. |
| As a TTA member I the same tools as "Modifying OSDs by the System" |
|
| As a TTA member I want to be able to reset the OSDs to match the OSs. |
|
|
