Versions Compared

Old Version 179

changes.mady.by.user Allison Costa

Saved on

compared with

New Version 180

changes.mady.by.user Allison Costa

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DescriptionJIRASlice 1Slice 2

Solicitation

  • Specify name of Solicitation
  • Specify Capabilities in Solicitation
  • Set Execution and Call period

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1437




  • Uses existing Solicitation and Proposal generator
  • Give Solicitation Name, Proposal Process, Number of Proposals

Status
subtleTrue
colourGreen
colorgreen
titlein progress

  • Set as Demo/Test

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1470




  • Separate Solicitation and Proposal Generation
  • Upload JSON for Solicitation Configuration

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1453

Proposal Generation

  • specify number of proposals
  • specify number of science categories
  • use capabilities defined in Solicitation to generate demo/test proposals
  • Fully supported proposals

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1437





  • Uses existing generator paired with Solicitations
  • Proposals are belong to 1 category
  • Simple proposals - no real allocation requests

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1453

  • Separate Solicitation and Proposal Generation
  • More realistic proposals
  • Science Categories from Solicitation
  • Expanded user database

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1184
Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1466

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1546

Close Solicitation

Use existing structure


Panel Configuration

  • Create SC based on SCs of proposals
    • Set Name, Science Category
  • Associate users with SRP
  • Specify a chair
  • Associate proposals with SCs

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1436




  • Create 1 panel
  • Assign SC
  • Fill 6 non TTA members
  • Assign Chair
  • Assign Proposals

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1313

  • Create 1 to 6 panels
  • Assign each a unique Science Category

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1545

Vetting

  • Vet all proposals automatically

Jira
showSummaryfalse
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1436



  • Vet all proposals without modification

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1312


Finalize Panel Configuration


  • use existing framework; hookup FE

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1471

  • use existing framework; hookup FE

Conflicts

  • Fill out Conflict Declarations
  • Certify
  • Per panel, per SRP? Bulk options

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-901



  • Per panel button
  • set all to Available unless AutoConflicted
  • Certify Conflicts

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1472


ISRs

  • Assign Review Types satisfying minimum SRsPerProposal and 1 Primary and 1 Secondary per proposal
  • If assigned P,S,T, fill out comments and score randomly
  • If test solicitation, the comments should state the Proposal ID, the individual score, the reviewer name, and Review Type of reviewer
  • If Demo solicitation, the comments should be simulated comments.
  • Per panel, per reviewer, bulk options?

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-901



  • Per panel button
  • Use pattern for comments for all ISRs
    • Review Type not None
    • Review State not Blank
  • Randomize score
  • Assign Review Types randomly
    • 1 primary
    • 1 secondard
    • 1 tertiary

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1473



Finalize ISRs

per panel, per reviewer, bulk options?


  • per panel button to finalize ISRs

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1474

  • per panel button to finalize ISRs

Initiate Consensus Phase


  • hook up existing structure per panel

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1475

  • hook up existing structure per panel

Consensus

  • Fill out Comments for each
  • Complete PPR

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-901




  • Use appended ISR comments to make PPR Proposal Process comments for PI
  • Complete Reviews per panel

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1476

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1477


Finalize PPR


  • per panel

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1478

per panel


Simulate All

  • Simulate full PPR Review Process

Jira
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1547

Version 0.3 Outline

DescriptionJIRAUI prototypeSlice 1 - v0.2.2Slice 2 v0.2.2

Scheduler

  • Source Conflict identification





Scheduler Tools

  • Construct Preliminary Allocation Dispositions (priorities and time)
    • Inputs:
      • Proposal Information (current Semester):
        • Sources, Resources
          • Cluster ID; Time; LST/GST range, Config (VLA); Band;Fixed Date?
        • Linear Ranks
      • Other:
        • Carryover from previous semesters
        • Sponsored time
        • Maintenance Time
    • Fine Tuning inputs
      • Manual inspection of carryover etc
    • Algorithm to determine scheduling priorities and available time
      • How initial priorities are determined are Facility specific
        • e.g., VLBA is straight quartiles
    • Fine Tuning
      • Manual inspection of pressure plot
      • Annotate recommendations
        • e.g., promote N → C to fill gaps
    • Output to TAC
      • Cluster ID; Time; LST/GST range, Config (VLA); Band; Priority
      • Pressure Plots

Scheduler Tool UI

  • per facility
  • versioning
  • view of Proposals
  • view of PPR Proposal Review
  • new tools


  • Allocation Dispositions (1 - 1 with Allocation Requests)
    • Observation Specification Dispositions
  • Proposal Summary (1 - 1 with Proposals)
  • Facility Reports (per facility)
  • Available Time Model
  • Versioning
  • ATM is all available per facility - no precommitts
    • Inspect ATM
    • Pressure Plot
  • Creation of AD
  • Versioning of ATM, AD
  • Copy OS into OSDs
  • View AD:OSDs
  • See PPR Proposal Process Output (Comments/Score)
  • Assign a Preliminary Scheduling Priority per OSD
  • Record comments
  • Write Narrative per Facility
    • Bare bones, capture comments
  • Create Proposal Summary
    • Bare bones
TAC Meeting

Review Proposals

Scheduling priority Recommendations


Director's Review

Update Scheduling Priorities/Approval
TTA Member Tools

Generate Metrics
Mechanism to track project completion (Need for carryover)  Not in Scope



...