...
| Expand |
|---|
|
As a scheduler I would like to define an available time model (ATM) for my facility so I know how much time is available for new Allocation Requests (ARs) to fill. |
|
|
|
|
|
|
| As a scheduler I want the system to determine the ATM based on the precommitted time and weather constraints. | As a VLA scheduler I want to able to make late modifications to the date ranges easily so I don’t have to restart from scratch. | As a scheduler I want to import a list of proposals from past semesters so the time can be filled in the ATM. | As a scheduler I want to define maintenance periods for the facility such that the ATM will not schedule ARs in those blocks of time. | As a scheduler I want the system to calculate time dependent weather coefficients so the prediction of available time is accurate. | As a VLA scheduler I need the ATM to know what configurations are included in the Solicitation so I can be sure to schedule the appropriate ADs. |
|
| As a VLA scheduler I want to able to make late modifications to the date ranges for configurations easily so I don’t have to delete all of my work. | As a VLA scheduler I want to know if the imported proposals are multi semester, tests, or from carry over projects in the UI so I can keep track of the different types of pre-committed time. | As a scheduler I want to define maintenance periods by LST, duration, and date. |
| As a VLA scheduler I want to set the date ranges for each unique configuration so the system can calculate the time dependent weather coefficients. |
|
| As a scheduler I want the modifications I make in date, etc to update the ATM accordingly. | As a GBT scheduler I want to block out time for monitoring projects so I can account for pre committed time that is fixed date accurately. |
|
|
|
|
...
To inspect the ATM, it is most useful to use a pressure plot, which is essentially a histogram of number of the hours requested by the OSDs per time. This tells me how many hours in a certain time bin is being requested or is available. The amount available is many inputs, including weather, frequency, and precommitted time. The amount requested depends on the OSDs of the new proposals. I need to balance the new request against what is available. To do so, I need to really understand the details of both the available time and the requested time. It would also be nice to have a calendar-like view of the ATM, as some of the pre committed time is fixed date.
| Expand |
|---|
|
As a scheduler I want the system to build the Pressure Plots so I can understand the available and requested time demands. |
|
|
|
| As a scheduler I want to inspect the ATM so I can check it is correct. | As a scheduler I want to modify the ATM manually at any point so it can be accurate. | As a scheduler I want to be able to interact with the pressure plot visual tools so I can identify ADs:OSDs. |
| As a scheduler I would like to generate a Pressure Plot to represent the ATM so I have a holistic view of the available Time. | As a scheduler I want the pressure plots the visual tools I use to inspect the ATM to update when I change the ATM so they will be correct. | As a scheduler I want an easy way to modify an OSD I have identified in the pressure plot so I don't waste time tracking it down. |
| As a scheduler I want to inspect the ATM in detail so I understand where it may be under or over subscribed. |
| As a scheduler I want a way to identify underutilized LST/GST ranges so I can modify SPs to efficiently fill those ranges. |
| As a scheduler I want a view that is like a calendar so I can review specific days for fixed date observations of pre-committed time. |
| As a scheduler I want a way to identify overfilled LST/GST ranges so I can modify SPs as necessary. |
|
...
| Expand |
|---|
|
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. |
|
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 |
|---|
|
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 Preliminary 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 PI and all of the equivalent Internal Comments. |
|
| 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 to change the SP of an OSD between any defined in the system (e.g N, F, A, B, C). |
|
|
| 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. |
|
...
| Expand |
|---|
|
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 ADs that have external facilities to be automatically marked with N so they won't be accounted for in the scheduling. | 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 are rejected and 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. |
|
|
...
