The Hidden Cost of Running an Observatory.
When discussing observatory infrastructure, costs are usually framed in terms of hardware, facilities, and major software systems. Telescopes, instruments, enclosures, maintenance contracts, and data storage are visible, measurable, and accounted for.
What is less visible is the total cost of operating the system over time.
A significant part of that cost does not appear in budgets. It appears in the day-to-day effort required to keep operations running.
Where the Cost Actually Lives
Part of this cost is technical.
Observatories often rely on a collection of independent tools: control software, scheduling systems, data pipelines, monitoring tools, and communication platforms. Keeping these systems aligned requires ongoing effort. Interfaces must be maintained, data flows must be checked, and small inconsistencies must be resolved before they become larger issues.
Much of this work is incremental and rarely documented. A script is added to move files. A configuration is adjusted to match a new instrument. A workaround is introduced to handle a specific edge case. Over time, these small additions accumulate and become part of the operational fabric.
Another part of the cost is human.
Operators spend time coordinating actions, confirming states, and ensuring that different parts of the system remain consistent. Communication happens across multiple channels, and decisions are often reconstructed from partial information. New team members require time to understand not only the systems themselves, but also the informal practices that keep them working together.
This knowledge is unevenly distributed. Some individuals become central because they understand how the system actually behaves. Their presence reduces friction. Their absence reveals how much of the system depends on implicit understanding.
There is also a cost in reliability.
When systems are loosely connected, failures are not always explicit. A process may stop silently. A data transfer may be incomplete. A configuration mismatch may go unnoticed until it affects observations. Detecting and resolving these issues requires attention, experience, and time.
None of these costs are exceptional. They are part of normal operations. But taken together, they represent a substantial share of the effort required to run an observatory.
Toward More Coherent Systems
Observatories do operate successfully in their current form. Over time, teams develop practices, tools, and workarounds that allow them to manage complexity and keep operations running.
This works, and in many cases it works well enough.
But it also means that part of the system’s effectiveness depends on accumulated effort rather than on the structure of the infrastructure itself.
A small example comes from La Silla Observatory in the early 2000s. At the time, the control rooms of the main telescopes — the 3.6m, the NTT, and the 2.2m — were located in their respective buildings. Each instrument was operated in relative isolation, even though they were part of the same site.
Around 2005, a dedicated building was introduced to bring these control rooms together. From a practical perspective, this made operations more comfortable. But more importantly, it changed how the telescopes were operated as a whole.
Proximity made differences more visible, but it also made commonalities clearer. Operators could observe how each system behaved, share practices more naturally, and collaborate across telescopes.
The fact that they relied on similar software made this even more apparent. Nothing fundamental changed in the hardware. But the organization of the system did.
When control, coordination, and data management are handled within a more consistent framework, a similar effect appears. Information does not need to be reconstructed across multiple tools. Decisions remain attached to the operational context in which they were made. Interfaces become internal rather than external.
The value of this coherence is not always immediately visible. It does not appear as a single improvement, but as a gradual reduction of friction across many small interactions.
Less time spent checking, reconciling, and maintaining.
Fewer implicit dependencies.
More predictable behavior as systems scale.
Observatories are inherently complex, and no system will remove that complexity. But the way it is organized has a direct impact on how much effort is required to operate it.
And that difference is often only fully appreciated once the system becomes more coherent.
No responses yet