In v0.3, TTA tools is developing the Allocate and Approve packages, which supports the Allocation Disposition and Allocation Approval phases of the Proposal Process. Both the PPR and OSR proposal processes are in scope for this version.
Project Goals
Package
Purpose
Project Goals for PPR Proposal Process
Project Goals for OSR Proposal Process
Allocate
Recommend Preliminary Scheduling Priorities
Define Available Time Model
Build Available Time Model
Assign Preliminary Scheduling Priorities to Observation Dispositions
Generate Facility Reports
Generate Proposal Summaries
Allocate
Recommend Scheduling Priorities
Recommend Scheduling Priorities per Observation Dispositions (TAC)
Recommend Scheduling Priorities per Observation Dispositions
Approve
Approve Scheduling Priorities
Generate Reports
Approve Scheduling Priorities per Observation Dispositions
Generate Directors' Report
Approve Scheduling Priorities per Observation Dispositions
To determine what time is available for the new proposals, I first have to build an Available Time Model (ATM) for my facility. The ATM needs to know about pre-committed 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).
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.
When the ATM is first defined for my facility I want it to use the execution period set in the Solicitation.
As a scheduler I want to be able to modify the execution period the ATM uses for my facility so I can support my facility specific scheduling requirements.
As a scheduler I want to be able to make late modifications to the execution period my facility references so I do not have to delete all of my work.
As a VLA scheduler I want the configuration defined in the Solicitation to each have an execution period in the VLA ATM.
As a VLA scheduler I want to modify the execution periods per configuration so the available time per configuration is accounted for correctly in the VLA ATM.
As a scheduler I want algorithms to build the ATM for my facility using facility specific constraints so I can add projects and precommitted time to it.
As a scheduler I want to define pre-committed time for my facility's ATM so ADs will not be scheduled in those blocks of time.
As a scheduler I want to import projects that constitute pre-committed time so the time is correctly reserved for these projects.
As a scheduler I want to manually add pre-committed time to the ATM so it is accounted for.
As a s scheduler I want to easily discern the different types of blocked off time in the ATM so I know how the time is being accounted for.
As a scheduler I want to define maintenance periods for the facility so ADs will not be scheduled in those blocks of time.
As a scheduler I want to be able to upload a file with LST/GST, duration, date, and name/description that defines the maintenance periods.
As a scheduler I want to be able to manually add maintenance periods.
As a scheduler I want to define time in the ATM for carry-over projects so ADs will not be scheduled in those blocks of time.
As a scheduler I want to import the details of carry-over projects so the time is accurately accounted for in the ATM.
As a scheduler I want to manually add the details of a carry-over time.
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 pre-committed 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.
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.
As a scheduler I want to inspect the ATM so I can check it is correct.
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 to inspect the ATM in detail so I understand where it may be under or over subscribed.
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 to modify the ATM manually at any point so it can be accurate.
As a scheduler I want to be able to edit or delete existing pre-committed time periods.
As a scheduler I want to be able to edit or delete existing carry-over time.
As a scheduler I want to be able to edit or delete existing maintenance periods.
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 version control on my ATM so I can easily access different versions of the ATM that I am building.
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.
As a scheduler I want to each Observation Specification Disposition to have a Scheduling Priority.
As a scheduler I want the OSDs to have only one of the Scheduling Priorities defined in the system so the algorithms know how to process the OSD.
As a scheduler I want OSDs associated with external facilities to be processed differently than internal joint proposals.
As a scheduler I want an algorithm to apply a preliminary Scheduling Priority.
As a scheduler I want to manually apply a preliminary Scheduling Priority.
As a scheduler I want to preserve the PIs request as I determine preliminary scheduling priorities.
As a scheduler I want modifications to ODs to not affect OSs so I do not modify what the user requested at submission.
As a scheduler I want a way to restore one or more ODs to what the user requested in their OSs.
As a scheduler I would like to inspect the ADs:OSDs associated with this solicitation so I can decide it their information is accurate.
As a scheduler I want to modify ADs:OSDs as needed so they are accurate.
As a scheduler I want to see the results of the Review Process phase so I know how to schedule the proposals.
As a scheduler I want to be able to set a flag per ODS that indicates to the system and the PI that the ODS cannot be processed through the usual proposal creation algorithms.
