The operating knowledge to run it — current, and findable.
Develop, review, and approve the procedures your operation runs on — keep them current and findable, and preserve the know‑how before it walks out the door.
The procedures your operation depends on shouldn’t live in people’s heads.
When the knowledge to run the operation is tribal, scattered across shared drives, or out of date, opening day inherits the risk. Operating knowledge is the owner’s to author, keep current, and get into the team — deliberately.
Tribal & stale
- Critical know‑how lives with a few people — and leaves when they do.
- SOPs and EOPs are scattered, unversioned, and hard to find.
- Nobody’s sure which copy is current, or who approved it.
- Teams train and operate off whatever copy they happened to save.
Governed & current
- Procedures are owned, versioned, reviewed, and approved.
- The current version is findable — and it’s the one that counts.
- Training and operations draw on the current, approved version.
- Knowledge is captured before it walks out the door.
Author → Approve → Train → Operate → Improve.
A living loop that keeps operating knowledge current and in use — and turns it into readiness evidence and an AI‑ready foundation.
Develop, review, and approve — with version control that holds.
Treat operating procedures like the controlled documents they are: authored collaboratively, approved deliberately, and always findable in their current form.
Develop, review, approve
Author SOPs and EOPs collaboratively, route them for review, and record approval — with a clear owner.
Versioned & findable
Everyone can find the current version fast — and it’s unambiguous which copy is authoritative.
Gap analysis
See where required EOPs and SOPs are missing, stale, or overdue for review — before an auditor does.
Capture the know‑how — and make it AI‑ready.
Institutional knowledge is one retirement away from lost. Capture it, learn from every launch, and turn it into a clean foundation your data and AI can actually use.
- K‑01Capture before attritionPreserve institutional knowledge from experienced staff and departing consultants before it leaves.
- K‑02Learn from every launchSurface lessons learned and fold them back into procedures and training — continuous improvement, not a binder.
- K‑03A clean, AI‑ready foundationStructured, current operating knowledge is the data foundation grounded AI depends on — a Citiri principle we call Checkpoint 0.
Knowledge that becomes evidence and data
Approved procedures and competency records feed the evidence chain, and structured knowledge grounds Opti — so the know‑how compounds instead of decaying.
It’s governed operating knowledge — not a document dump or an EAM.
Operating Knowledge governs the owner’s procedures and institutional know‑how — the authoritative source your team trains and operates on. Training people on those procedures — familiarization, delivery, and competency — is its own capability, Familiarization & Training. And it isn’t your asset register: as‑built and O&M asset records live in your EAM, CMMS, and document systems.
It integrates with your systems of record — it doesn’t replace them.
Asset and maintenance data stays in EAM/CMMS; controlled documents can live in your DMS. Operating Knowledge connects to them and focuses on the operating procedures and knowledge your team runs on — kept current and accountable.
Powered by CitiriOS. The know‑how behind the operation.
Operating knowledge is the authoritative source your team trains and operates on, and it grounds the AI — connecting to familiarization, trials, and the evidence chain.
Make your operating knowledge current and usable.
Book a demo built around your SOPs, EOPs, and operating procedures — from authoring and approval to knowledge your team can find and trust.
Figures shown are illustrative, not a customer result. CitiriOS integrates with — and does not replace — EAM, CMMS, or document management systems. Checkpoint 0 is a Citiri concept for an AI‑ready operational data foundation. Opti suggests and cites; people author and approve.