SCP-2568
Safe
~
medium confidence
SCP-2568
Expected annual
$152K
One-time setup
$272K
Annual recurring
$148K
Personnel
3
Estimated one-time setup is approximately $272,500 with recurring annual costs of about $148,000. The main cost drivers are custom electromagnet/control hardware and development, facility buildout/electrical work, and ongoing skilled staff and contingency reserves.
One-Time Capital Costs
Total: $272K
Annual Recurring Costs
Total: $148K/yr
Cost Scenarios
📊
Baseline
(baseline)
$148K/yr
Normal year with routine operation, maintenance, and no major incidents.
routine_operation
scheduled_maintenance
🚨
Minor Incident
$158K/yr
Sensor or coil failure requiring emergency repairs, short downtime, and minor replacement parts and overtime.
sensor_failure
coil_replacement
power_glitch
🚨
Major Breach
$348K/yr
Power-supply or control bug leads to uncontrolled motion, equipment destruction and medical costs; significant repairs and investigations required.
control_software_bug
power_supply_failure
multiple_unit_interaction
🚨
Catastrophic Breach
$1.6M/yr
Large-scale explosion/structural damage and fatalities from multiple interacting instances or failed redundancy, requiring reconstruction, legal settlements, and long-term remediation.
simultaneous_power_failures
software_bug + multiple_instances
unanticipated_anomalous_interaction
Personnel
3 total
| Role | Count | Notes |
|---|---|---|
| Security Officer / MTF Agent | 1 | [#12] Part-time onsite guard or dedicated restricted-access security; costs included in staff_wages. |
| Technician / Maintenance | 1 | [#13] Shared 0.25–0.5 FTE technician for routine inspection, calibration, and maintenance; modeled as one headcount with fractional FTE. |
| Research Scientist | 1 | [#14] Part-time researcher (≈0.2 FTE) to run experiments and monitoring; salary portion included in staff_wages and research budget in research_and_monitoring. |
Confidence Notes
Estimates are based on analyst ranges in the notes; many hardware and staffing costs are well-understood but control software complexity, required redundancy, and contingency sizing introduce uncertainty.