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.
| Table of Contents | ||
|---|---|---|
|
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 |
...
| Define ATM in context of execution period | Apply pre-committed time per facility | Apply maintenance time per facility | Apply carry-over per facility | Inspect ATM | Manual modification of ATM | Modification of OSDs | Assign Preliminary SP | Generate reports: Facility Report, Proposal Summary | Inspect Facility Report, Proposal Summary | Approve ADs | Generate Directors' Reports | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
A1 | A2 | A3 | A4 | A5 | A6 | A7 | A8 | A9 | A10 | A11 | A11 |
PPR Proposal Process High Level Epics to support Project Goals
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 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 PI. Once I have made my recommendations, I want to finalize the review.
Proposed Release Goals
| Version | Goal | Packages | Notes |
|---|---|---|---|
| implement simulating review process and establish testing interface | Review | Enough to carry Proposal Reviews into Allocate phase | |
| establish simple prototype UI and make hand offs of entities between packages | Allocate; Approve | For TAC Prep subphase, assume no changes to ADS:OSDs and do not build ATM. Use random fill of information in Allocation Disposition entity to hand off to TAC UI. Versioning of ATM and ADS to support modification in TAC subphase and Approve phase. | |
| implement building of ATM and UI display in scheduler tools | Allocate | Focus highest priority features | |
| implement Facility Reports, Proposal Summary, and Directors' Report | Allocate; Approve | preliminary reporting pass | |
| implement manual modification and display of ADS:ODS in scheduler tools | Allocate | includes changing details of OSDs and Scheduling Priorities | |
| develop and connect algorithms for assignment of Preliminary Scheduling Priorities | Allocate | e.g., connect to Prioritizer | |
| improve ATM construction, UI display, and reporting | Allocate | ||
| implement OSR Allocate and Approve phases | Allocate; Approve | ||
| implement simulating Allocate and Approve phases | Allocate; Approve | ||