Starting with a new safety tool shouldn't mean re-typing years of hazard analysis. SAFOPS gives you three real ways in, matched to what your data actually looks like.
Have your hazards, initiating events, and SFR/barrier schedule already tracked in a spreadsheet? SAFOPS's generic importer recognises common column headings (Hazard ID, Frequency, Requirement, SSC Claim, and their usual synonyms) regardless of how your sheets are named, and links records together automatically via a shared reference column.
A dedicated importer reads Cassandra Hazard Management System exports directly — Hazards, Causes, Accidents, and Controls, including the relationship "Links" sheets Cassandra produces — and maps them onto SAFOPS's Fault/Barrier model.
For a hazard buried in a paragraph of an old report rather than a table, paste the text in and the secure Local AI drafts a structured Fault entry — title, hazard statement, initiating events — for you to review and correct. It never invents a dose band, frequency, or fact that isn't stated in your source text, and nothing it drafts is saved until you accept it.
Every import is deterministic, dry-run first, and idempotent — see exactly what will be created before anything is written, and re-running the same import never creates duplicates. Barriers with an ambiguous or unrecognised type are imported as "Defence-in-Depth (no formal claim)" rather than guessed as Engineered, so an import can never manufacture a reliability claim nobody has verified.