Keep Telescope Time, Customer Requests and Data Delivery Aligned

Enquiries for imaging, photometry and dedicated telescope access arrive without enough detail to identify the appropriate service. Sales staff repeatedly ask about instrument needs, observing cadence and intended delivery.

Extract the requested service, aperture or instrument requirements, cadence, scheduling window and purchasing timeline into a lead record. Request missing commercial details and route technical requirements to an observatory specialist before qualification is finalised.

A commercially attractive request may involve targets outside the site's useful visibility window or requirements that the available instrument cannot meet. Sales correspondence alone does not provide a dependable feasibility record.

Assemble submitted coordinates, epoch, target windows, cadence and requested instrument settings alongside approved site and instrument reference data. Flag missing or conflicting requirements and send the evidence pack to a qualified reviewer without issuing an automated feasibility approval.

Proposals can omit important distinctions between reserved hours, attempted observations and accepted data products. Those omissions create uncertainty when weather or quality issues affect delivery.

Build a proposal draft from the approved technical scope, current commercial terms and defined delivery responsibilities. Route pricing, weather treatment, acceptance criteria and nonstandard commitments to authorised reviewers before sending.

A signed customer may still lack an approved target list, nominated contacts, delivery permissions or an agreed file convention. These gaps surface when the first observing opportunity arrives.

Create an onboarding checklist for the purchased observatory service and assign each requirement to the customer or internal owner. Send reminders for outstanding items and hold the readiness milestone until the required reviews are recorded.

Programme agreements may contain reporting dates, delivery deadlines, renewal notices and different definitions of service interruption. Staff can miss an obligation when those terms remain buried in signed documents.

Extract proposed obligations with references to their source clauses, then have an authorised reviewer confirm the interpretation. Track confirmed dates and thresholds against programme records and escalate approaching or potentially breached obligations.

Queue submissions can contain unsupported filter names, ambiguous coordinate formats or exposure settings outside published submission limits. Operators must catch these issues before preparing the observing plan.

Check each submission against the approved schema, instrument configuration and programme-specific limits. Return field-level corrections for administrative errors and route unusual settings to an operator without writing directly to telescope controls.

Time-critical targets, instrument changeovers and customer priority rules can compete for the same observing window. Conflicts are difficult to resolve when programme constraints are scattered across separate records.

Compare candidate requests with the planning calendar, approved priority rules and recorded instrument availability. Present conflicting requests and their constraints to the scheduler, who approves any queue changes.

After an observing interruption, customers may receive inconsistent explanations or ask repeatedly whether their target remains scheduled. Different programmes may also have different weather-related remedies.

Use a confirmed operator incident record to identify affected programmes and draft updates describing completed work, unresolved observations and the next review point. Route replacement-window proposals and contractual remedies for approval before communicating commitments.

Camera servicing, mount inspections and filter-wheel maintenance can be missed when tasks depend on individual reminders. A missing service part can extend an already limited maintenance window.

Track approved calendar-based and usage-based maintenance intervals using available equipment records. Prepare work orders, identify required spares and submit replenishment requests for approval while an authorised operator controls equipment isolation and return to service.

Guiding failures, camera readout errors and enclosure faults require different expertise and urgency. Unstructured fault reports delay assignment and obscure which customer programmes may be affected.

Classify submitted fault reports by equipment, reported symptoms and the observatory's approved severity rules, then attach relevant available logs. Assign tickets to the responsible technical role and escalate safety-related reports to the designated operator without attempting autonomous recovery.

The daytime customer team may not know why an observing sequence stopped or which datasets still need review. Free-text night logs make unresolved actions easy to overlook.

Convert the approved night log into programme-linked summaries covering completed sequences, interruptions, instrument concerns and pending decisions. Assign follow-up tasks to the appropriate roles and retain links to the original log entries.

A science dataset may reach processing without the calibration records required by its instrument configuration and reduction procedure. Staff then have to trace missing flats, darks or bias frames manually.

Compare dataset metadata with the observatory's approved calibration requirements, including applicable filter, binning, temperature and validity-window rules. List missing or mismatched calibration references for the reduction team without declaring the dataset scientifically acceptable.

Frames flagged for trailing, focus drift, saturation or background anomalies can become mixed with otherwise complete deliveries. Customers need a clear decision on what is accepted, rejected or still under review.

Gather existing quality metrics and processing flags, then compare them with the programme's approved review thresholds. Group exceptions by observation and send the evidence to a qualified reviewer for acceptance, rejection or reacquisition decisions.

Customers may receive a download notice before the manifest is complete or before access permissions have been checked. Staff also spend time answering basic questions about which observations a delivery contains.

Require recorded release approval, a completed manifest and confirmed destination permissions before preparing a delivery notice. Include the programme identifier, observation dates, file counts, approved quality notes and the applicable access-expiry information.

Access problems, missing files and questions about acquisition status arrive in the same support channel. Urgent observing-session issues can wait behind routine requests without clear ownership.

Classify each request by programme, issue type, active-session status and the relevant support commitment. Route access questions, data queries and operational incidents to their designated owners, with deadline alerts and escalation for unresolved cases.

The scheduler may record reserved hours while acquisition logs record exposures and the contract bills accepted observing time. Directly copying one record into an invoice can produce unsupported charges.

Match programme identifiers across reservation, execution and acceptance records, then calculate draft billable usage using the approved contract rule. Flag duplicate sessions, missing acceptance decisions and unexplained differences for finance and operations review before invoicing.

Overdue invoices may relate to an unresolved data-quality dispute, a missing purchase-order reference or a genuine payment delay. Sending the same reminder to every account can interrupt useful customer discussions.

Prioritise outstanding invoices using approved collection rules, dispute status and recorded payment promises. Prepare context-specific follow-ups, track promised payment dates and route disputed observing charges to the responsible account owner.

Credit requests require staff to reconstruct the booking terms, interruption record, attempted observations and any replacement service already provided. Incomplete evidence can lead to inconsistent decisions.

Compile the relevant contract clauses, confirmed downtime, acquisition records and prior remedies into a credit review packet. Identify missing evidence and calculate a proposed adjustment only under an approved rule, leaving eligibility and posting to an authorised reviewer.

Dataset access, telescope allocations and support entitlements can remain active after a programme changes or expires. Requests beyond the purchased allocation may also be handled without a documented commercial decision.

Compare active programme terms with recorded access permissions, allocation balances and requested services. Route discrepancies for review and prepare an upgrade brief where additional capacity is requested, without automatically revoking access or changing the contract.

Renewal conversations can begin too late for customers planning seasonal campaigns or time-sensitive target monitoring. Account teams may also lack a consolidated view of remaining allocations and unresolved service issues.

Track confirmed renewal dates alongside allocation usage, delivery history, open issues and customer-stated future observing windows. Prepare a renewal brief and assign follow-up tasks, keeping capacity offers and commercial terms subject to approval.

Requests for clearer FITS metadata, more useful delivery manifests or different scheduling reports are dispersed across tickets and account conversations. Repeated issues may never reach the team responsible for the service.

Group authorised customer feedback by observatory service, instrument and recurring issue, preserving links to the source records. Produce an improvement brief with affected programmes, recurrence counts and assigned review owners without promising unapproved changes.