...
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 | ||||||
---|---|---|---|---|---|---|
| ||||||
|
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 report for the Director's Delegate's review. 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.
...