...
OSD - Observation Specification Disposition
PPR Proposal Process
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).
| Expand |
|---|
| title | user storiesDefining the ATM |
|---|
|
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 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 |
|---|
| title | user storiesBuilding the ATM |
|---|
|
As a scheduler I want the system to build the ATM 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 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 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. |
|
...
Once I am satisfied assigning scheduling priorities and providing comments for the TAC, I need to generate some reports for the TAC. I need both a summary of the ATM and the OSDs for my facility as well as an overview of the proposals/OSDs. I want these in different formats and I will both want a way to interact with the information associated with the Proposals in an efficient way when I'm at the TAC. I will likely do a lot of filtering by different proposal/OSD attributes. I also will want a way to generate a printed view of these summaries/reports because the TAC likes to look at pdfs too.want to export a Preliminary Facility Report based on a specified version of the ATM+OSDs. A Preliminary Facility Report includes the pressure plots for my facility and a csv with the data (TBD). I will take this data and the pressure plots and externally generate a pdf that is the Facility Report. Eventually, I will want to upload materials for the TAC to use during their discussions. For my facility, I want to upload the Facility Report (pdf) and a presentation (pdf). These documents should accessible through the TAC interface and their access is restricted to the TAC and TTA members. I may need to upload a different copy later, so I will want to replace (without versioning) the uploaded files.
For my proposals requesting my facility, I want to generate a Facility Proposal Summary, where the facility is VLA, VLBA, and GBT. This information should be generated into the TAC page so the TAC members can view it for their meeting. I may want to update the data in the Proposal Summary later for example, after the Large Proposal Meeting is finished.
| Expand |
|---|
|
| Expand |
|---|
|
As a scheduler I want to create export a Preliminary 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 deliberatingto specify which version of the ATM+OSDs are exported. | 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 Proposal Summary 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. |
|
...
| I do not think we want to do this. |
|
Proposal Summary
A Proposal Summary is the primary way a TAC interacts with the proposals and the review process. It is likely an interface with specific details (see TAC meeting, the image linked under Facility Documents, summary.
OSR Proposal Process
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 . The report for the Director's Delegate's review is technically not part of the OSR. In practice there is no real report that is produced.
| 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. |
|
|
