Skip to content
OTOBO Community Guide

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

Section titled “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

Section titled “2. Roles & Responsibilities”
RoleMain Tasks
CMDB-ManagerMaintain CI models, YAML definitions, DynamicFields, monitor data quality
Change-CoordinatorCoordination of changes, approvals in the change workflow, alignment with stakeholders
Asset-OwnerFunctional responsibility for specific CI categories (e.g., network, software, locations)
AuditorAudit 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

Section titled “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

Section titled “4. Community Resources & Further Development”

  • OTOBO-Community-Forum

  • Official Documentation

  • Plugin-Library & GitHub

  • Workshops & Webinars

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

Conclusion

Section titled “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.

Frequently asked questions

Why is CMDB governance crucial for OTOBO's long-term reliability?

CMDB governance establishes the essential framework of clear standards, defined roles, and robust processes that ensure the Configuration Item (CI) data within OTOBO remains reliable and trustworthy over time. Without effective governance, data quality can degrade, leading to inaccurate information that undermines the integrity of related processes like ticketing and change management. Successful governance, as highlighted in the guide, is built on high data quality, clear responsibilities, stringent review processes, and active community engagement, making the OTOBO-CMDB a dependable "Single Source of Truth."

Quellen / Sources:

What are the best practices for improving CMDB data quality in OTOBO?

Improving CMDB data quality in OTOBO involves a multi-faceted approach focusing on standardization, automation, and regular maintenance. Key practices include: Data Standardization through consistent field naming, using dropdowns over free text, and implementing validation rules (e.g., RegEx, mandatory fields). Automated Checks can be set up using script fields for plausibility checks (like IP addresses or date ranges) and scheduled reports via API or CSV to detect data outliers. Furthermore, Regular Cleanup is vital, involving duplicate detection, merge processes, and archiving outdated CIs using features like VersionTrigger and filters.

Quellen / Sources:

How are roles and responsibilities defined for CMDB governance in OTOBO?

Clear definition of roles and responsibilities is fundamental to effective CMDB governance in OTOBO. The guide outlines several key roles: the CMDB-Manager maintains CI models, YAML definitions, and DynamicFields, while also monitoring data quality. The Change-Coordinator is responsible for coordinating changes, approving them within the change workflow, and aligning with stakeholders. Asset-Owners hold functional responsibility for specific CI categories (e.g., network, software, locations). Lastly, Auditors perform audit checks, verify version history, and ensure compliance. It's also recommended to define clear SLAs for data maintenance and change approvals to prevent delays and ensure accountability across teams.

Quellen / Sources:

What review and approval processes are recommended for CMDB changes in OTOBO?

To maintain high data integrity, OTOBO CMDB governance recommends stringent review and approval processes. This includes Two-Stage Reviews: a Technical Review by the CMDB-Manager to check structure and consistency, followed by a Functional Review by the Asset-Owner to confirm content accuracy. The use of Change-Templates & Checklists is also crucial, involving standardized YAML templates for CI changes and a checklist for every new field covering aspects like naming, Tooltip, mandatory status, and validation. Finally, Versioning & Audit-Trail features, such as using VersionTrigger: DefinitionUpdate for every structural change and periodic reports on all CI versions and field changes, ensure a seamless audit trail and accountability.

Quellen / Sources:

Where can OTOBO users find community resources and support for CMDB best practices and further development?

OTOBO offers a vibrant ecosystem for users to find support, share best practices, and contribute to further development, especially concerning CMDB governance. Key resources include the OTOBO-Community-Forum (https://otobo.io/community) for exchanging best practices, YAML snippets, plugins, and modules. The Official Documentation (https://doc.otobo.io) provides essential information like YAML schema, API reference, and release notes. Users can also leverage the Plugin-Library & GitHub (https://github.com/OTRS/otobo) for shared CI definitions, discovery scripts, and automation tools. Additionally, regular Workshops & Webinars offer training on CMDB modeling, API integration, and governance, fostering continuous improvement within the community.

Quellen / Sources: