1 of 3

Requesting Observations

Freeform Text

XML

Spreadsheet

CSV

OCS

JSON

What format should be used for an observation request?

Nothing

Acknowledgment

OCS

OCS

Final Status

OCS

Real-time Status

What user feedback should be returned?

Personal Communication

Automated Email

OCS

OCS

Web Portal

OCS

JSON API

How should user feedback be returned?

Site Visit

Personal Communication

Shared Spreadsheet

Email

OCS

Web Portal

OCS

API

How should a user submit an observation request?

Compatibility

Incompatible

Preferred

Available through Open OCS

OCS

2 of 3

Personal Communication

Shared Spreadsheet

Queued Scheduling

Per Semester

Nightly

OCS

OCS

Periodically (Several times per night)

OCS

Dynamically (Real-time)

How

frequently should the schedule be updated?

Nothing

Final Status

OCS

OCS

Periodic Updates

OCS

Real-time Updates

What

scheduling information should be accessible to users?

Automated Email

OCS

Web Portal

OCS

JSON API

How should a user access scheduling information?

Compatibility

Incompatible

Preferred

Manual

Partially Automated

OCS

Fully Automated

How should a schedule be built?

Long Term Support Considerations

Rubin's LSST will last 10yrs and the community will want facilities to follow-up discoveries for that entire time. The long term cost of manual operations should be weighed against the cost of ongoing software maintenance.

OCS

Available through Open OCS

3 of 3

Raw Frames Only

Raw

Frames + Calibrations

Support

Personal Communication

Automated Email

OCS

Web Portal

OCS

JSON API

Phone

Serving User Data

Partially Processed Fits Files

Fully Processed

Fits Files

Fully

Reduced Scientific Data

What level of data reduction is available?

Never!

Within a Few Days

End of Night

OCS

Immediately

How quickly can a user access their data?

Ticketing System

Email

Website

How can a user access support or documentation?

Compatibility

Incompatible

Preferred

How should a user access their data?

Available through Open OCS

OCS