Office Onboarding and Service Ownership Ontology
An ontology defining organizational entities, service ownership, access management, communication channels, and approval workflows for knowledge extraction.
An individual employee, contractor, or team member within the organization.
A designated job function, title, or position held by a Person (e.g., DevOps Engineer, Engineering Manager, Procurement Officer).
A functional group of individuals collaborating on specific operational goals or organizational areas.
A top-level organizational unit (e.g., Engineering, Human Resources, Finance) containing multiple teams.
An internal tool, software platform, infrastructure system, or SaaS application used by the organization (e.g., GitHub, Jira, AWS, Datadog).
A structured sequence of administrative steps or workflows, such as IT onboarding, software access requests, or hardware procurement.
A specific phase within a Process where sign-off is required, often bound by financial spend thresholds or role-based governance.
A communication medium, such as a Slack channel, Microsoft Teams group, or email distribution list.
Links a Person to the official Role or job title they currently hold within the organization.
Associates a Person with the Team they belong to.
Indicates that a specific Team is responsible for maintaining, supporting, and administering a Service.
Specifies that individuals holding a particular Role require default or policy-driven access to a Service to perform their duties.
Connects an overall Process workflow to an individual ApprovalStep contained within its execution sequence.
Identifies the designated Role authorized to sign off on or evaluate a given ApprovalStep.
Designates the Person responsible for leading, managing, or overseeing a Team.
Links a Team to its parent Department within the corporate hierarchy.
Links a Team, Service, or Process to its primary communication Channel (e.g., notification channel or support room).
The maximum financial value (numeric monetary threshold) that can be authorized at this ApprovalStep before requiring higher escalation.