Best Practices & Governance

Best Practices & Governance

To operate a reliable and meaningful CMDB in the long term, clear standards, roles, and processes are indispensable.

---

1. Ensuring Data Quality

• Data Standardization

  • Consistent field naming and value lists (e.g., Dropdowns instead of free text)
  • Use of validation rules (RegEx, mandatory fields, date restrictions)

• Automated Checks

  • Script fields for plausibility checks (e.g., IP address, date ranges)
  • Scheduled reports via API or CSV export to detect outliers

• Regular Cleanup

  • Duplicate detection and merge processes
  • Archiving of outdated CIs via VersionTrigger and filters

---

2. Roles & Responsibilities

Role	Main Tasks
CMDB-Manager	Maintain CI models, YAML definitions, DynamicFields, monitor data quality
Change-Coordinator	Coordination of changes, approvals in the change workflow, alignment with stakeholders
Asset-Owner	Functional responsibility for specific CI categories (e.g., network, software, locations)
Auditor	Audit checks, verification of version history and compliance reports

Tip: Define clear SLAs for data maintenance and change approvals to avoid delays.

---

3. Review and Approval Processes

1. Two-Stage Reviews

   • Technical Review: CMDB-Manager checks structure and consistency
   • Functional Review: Asset-Owner confirms content accuracy

2. Change-Templates & Checklists

   • Standardized YAML templates for CI changes
   • Checklist for every new field (naming, Tooltip, mandatory, validation)

3. Versioning & Audit-Trail

   • Use of VersionTrigger: DefinitionUpdate for every structural change
   • Periodic reports on all CI versions and field changes

---

4. Community Resources & Further Development

• OTOBO-Community-Forum

  • Exchange on best practices, YAML snippets, plugins, and modules
  • https://otobo.io/community

• Official Documentation

  • YAML schema, API reference, release notes
  • https://doc.otobo.io

• Plugin-Library & GitHub

  • Shared CI definitions, discovery scripts, automation tools
  • https://github.com/OTRS/otobo

• Workshops & Webinars

  • Regular training on CMDB modeling, API integration, and governance

---

Conclusion

Successful CMDB governance is based on:

1. High data quality through standardization and automation
2. Clear roles with defined responsibilities
3. Stringent review processes and a seamless audit trail
4. Active exchange in the community for continuous improvement

With these best practices, you ensure that your OTOBO-CMDB functions as a reliable “Single Source of Truth” in the long term.