# Framework · EnterpriseOS v1.0 **Seven layers. One operating system.** EnterpriseOS is the framework we use to talk about — and architect — modern enterprises. Each layer has a role, a contract with the layers above and below it, and a maturity model. AI sits at Layer 07 because it depends on the other six. --- ## Layer 01 · Governance & Security *Control Plane.* The control plane sits over everything. Policy-as-code, identity, audit, risk register, board reporting, plus the **Architecture & Intelligence Review Board (AIRB)** — a single AI-forward governance body that consolidates the technology, architecture, AI ethics, and change review boards most enterprises run in parallel. If governance is bolted on after deployment, it never sticks. We design it in from day one — and we make sure the artifacts hold up to your auditors, your board, and your regulators. *Example key metric — % apps with current attestation · mean time from request to AIRB decision.* --- ## Layer 02 · Intelligence *Decision Engine.* Where decisions get made — by humans, by rules, by models. This is the layer that turns information into action: prompts, decision policies, eval suites, model selection, and the feedback loops that make decisions get better over time, not worse. Includes the **Cognitive Architecture** — skills-as-code that defines how the organization thinks, decides, and escalates. The runtime substrate every agent reads from, instantiated as the organization-wide knowledge graph at Layer 04. *Example key metric — AI use-case pipeline depth · % decisions supported by analytics.* --- ## Layer 03 · Automations *Orchestration.* The executable workflows the rest of the stack can call. RPA, workflow engines, scheduled jobs, event-driven triggers, and agent-callable tools — the **BOAT** (Business Orchestration and Automation Technologies) territory. Designed so they can be invoked by a human at a UI, a system in a batch job, or an agent at Layer 07. Tool choice follows the client's existing stack; we recommend pivots only when there's a clear case for it. *Example key metric — automation coverage rate · time saved per automated workflow.* --- ## Layer 04 · Data *Info Architecture.* Clean, permissioned, retrievable knowledge. Warehouse, lakehouse, vector store, plus an **organization-wide knowledge graph** — a markdown-native, link-first map of how the organization's concepts, decisions, standards, and prior reasoning relate. The data instantiation of the [Cognitive Architecture at Layer 02](#layer-02--intelligence) — the substrate every agent reads from when it needs to reason across the organization's accumulated thinking. Most AI failures are actually data failures one level down. Platform-agnostic on the rest: Fabric, Databricks, Snowflake, BigQuery — follow the client's existing stack. *Example key metric — data quality score · % critical data elements with defined ownership · knowledge graph density.* --- ## Layer 05 · Systems *Infrastructure.* The systems of record, APIs, identity, secrets, and the MCP servers that expose them. The layer that makes everything else possible — and the layer that determines whether your AI initiative ships on time or stalls in integration hell. **Your stack is the integration surface. We build on it.** Whatever you've standardized on (Dynamics 365, Salesforce, SAP, NetSuite, Workday, HubSpot for ERP/CRM; ServiceNow, Jira SM, Ivanti, BMC, Freshservice for ITSM) is the system of record we integrate against. When a pivot earns its own ROI case, we make it; otherwise the install stays. *Example key metric — integration reliability (uptime, error rates) · application portfolio health score.* --- ## Layer 06 · People *Human Layer.* Org design, ownership, escalation, accountability. The most underweighted layer in most "AI strategies" — and the one that determines whether a deployed system gets used, trusted, and improved. We design this layer with the same rigor as the technical ones. *Example key metric — team capability score · training completion and application rates.* --- ## Layer 07 · AI · *Next Upgrade* *Agentic Layer.* Layer 07 is the agentic execution layer that operates across the rest of EnterpriseOS. It's not a chatbot. It's not a feature. It's a new way to operate — one that depends on every layer below it being architected correctly. This is the layer clients hire Hiday to deliver. Platform-agnostic by default: we deploy across all major AI platforms (Anthropic Claude, OpenAI / Microsoft Copilot, Google Gemini, AWS Bedrock) and pick what fits the client's regulatory posture, vendor strategy, and use case. The model isn't the moat; the architecture around it is. *Example key metric — agent deployment count · % AI use cases with governance documentation.* → [Read more about Layer 07](/agentic.html) --- ## Diagnostic *Where is your enterprise on this stack? Let's map it together.* We run a 2-week EnterpriseOS diagnostic that scores your maturity at each layer and identifies the lowest-leverage gaps blocking Layer 07. The output is a sequenced roadmap, not a slide deck. → [Request a diagnostic](/contact.html) --- ## Pages - [/](/) — Homepage - [/services](/services.html) — Four service practices - [/agentic](/agentic.html) — Layer 07 deep dive - [/contact](/contact.html) — Start a conversation --- ## Contact - requests@hiday.ai © 2026 Hiday · Phoenix, AZ
Framework · EnterpriseOS
· v1.0
Seven layers.
Seven layers.
One operating system.
EnterpriseOS is the framework we use to talk about — and architect — modern enterprises. Built in practice at enterprise scale, now deployed as the diagnostic backbone for client engagements. Each layer has a role, a set of components, and a key metric. AI sits at Layer 07 because it depends on the other six.
01 · Control Plane
Governance & Security
The control plane sits over everything. If governance is broken, nothing downstream works reliably. We design it in from day one — and we make sure the artifacts hold up to your auditors, your board, and your regulators.
- Architecture & Intelligence Review Board (AIRB) — A single, AI-forward governance body that consolidates the technology, architecture, AI ethics, and change review boards most enterprises run in parallel. One intake queue, one decision record, one risk register — for every initiative above the defined threshold. Prevents shadow IT and shadow AI without slowing the business down.
- App Attestation — Continuous validation that every application has an owner, a purpose, a security review, and a cost justification.
- SaaS Discovery — Multi-source approach (CMDB, P-card, AP, CASB) to find shadow SaaS. Single source of truth for the application portfolio.
- Security Posture — Vulnerability management, identity governance, zero trust, incident response playbooks.
- Business Office — IT financial management, vendor & contract lifecycle, chargeback / showback.
Example key metric · % apps with current attestation · mean time from request to AIRB decision
02 · Decision Engine
Intelligence
Where decisions get made — by humans, by rules, by models. The layer that turns information into action and makes those decisions get better over time, not worse.
- AI Center of Excellence — Centralized expertise, decentralized deployment. Model governance, use-case intake, capability building.
- Agentic AI Strategy — Multi-agent systems, tool-use patterns, orchestration. The frontier. (See Agentic.)
- Cognitive Architecture — Skills-as-code: the institutional layer that defines how the organization thinks, decides, and escalates. The runtime substrate every agent reads from. Instantiated as the organization-wide knowledge graph at Layer 04.
- BI & Reporting — Dashboards, self-service analytics, data storytelling. Table stakes.
- Data-driven decision-making — Cultural as much as technical. "What does the data say?" before "what does my gut say?"
Example key metric · AI use-case pipeline depth · % decisions supported by analytics
03 · Orchestration
Automations
Process automation — the layer where technology directly reduces human toil and accelerates business processes. This is the BOAT territory (Business Orchestration and Automation Technologies) and we govern every initiative inside it the same way: a named outcome, a measurement, and an owner.
- BOAT governance discipline — No "automation for automation's sake." Every workflow inside the BOAT category (iPaaS, RPA, workflow engines, intelligent process automation, agentic systems) carries an outcome, a measurement, and an owner before it ships.
- Workflow automation — Workflow engines, RPA, and agentic automation. Tool choice follows the client's existing stack; we recommend pivots only when there's a clear case for it.
- Incident automation — Auto-remediation of known incident patterns across whatever endpoint management and ITSM platforms the client runs.
- ITSM AI Ops — Predictive incident management, AI-assisted categorization, virtual agent deflection — on the ITSM platform you've standardized on.
Example key metric · automation coverage rate · time saved per automated workflow
04 · Info Architecture
Data
The data infrastructure and management layer. AI and analytics are only as good as the data underneath them. Most AI failures are actually data failures one level down.
- Data architecture — Logical and physical models, flow mapping, integration architecture.
- Data pipelines — ETL / ELT, streaming, batch. Platform choice (Fabric, Databricks, Snowflake, BigQuery, etc.) follows the client's existing stack.
- Data governance — Ownership, classification, quality, lineage. The unglamorous work that makes everything else possible.
- Master data management — Single source of truth for customers, products, employees, and other core entities.
- Organization-wide knowledge graph — Beyond the warehouse and the lakehouse, modern enterprises need a connected map of how their concepts, decisions, standards, and prior reasoning relate. We build these in a markdown-native, link-first pattern that compounds value as the organization writes. This is the data instantiation of the Cognitive Architecture at Layer 02 — and the substrate every agent reads from when it needs to reason across the organization's accumulated thinking.
Example key metric · data quality score · % critical data elements with defined ownership · knowledge graph density
05 · Infrastructure
Systems
The core platform layer — the applications and integrations that run the business. How systems talk to each other without creating spaghetti, and how an AI initiative ships on time instead of stalling in integration hell. Your stack is the integration surface. We build on it. When a pivot earns its own ROI case, we make it; otherwise the install stays.
- ERP / CRM — Whatever you've standardized on (Dynamics 365, Salesforce, SAP, NetSuite, Workday, HubSpot, and the long tail) is the system of record we integrate against.
- ITSM — Same posture. ServiceNow, Jira Service Management, Ivanti, BMC, Freshservice — practice maturity matters more than the vendor logo.
- Integration architecture — API strategy, middleware, iPaaS, MCP servers that expose systems to agents.
- Application portfolio management — Rationalization, lifecycle, build-vs-buy decisions.
Example key metric · integration reliability (uptime, error rates) · application portfolio health score
06 · Human Layer
People
Talent, culture, and capability. The most underweighted layer in most "AI strategies" — and the one that determines whether a deployed system gets used, trusted, and improved.
- Team structure & org design — Reporting lines, spans of control, centralization vs federation.
- Centers of Excellence — The scaling pattern: centralized knowledge, decentralized execution. Applied to Automation, AI, and ITSM / SRE practices.
- Training & upskilling — A 5-week curriculum that moves teams from AI-curious to AI-capable. (See Training.)
- Director-level leadership development — Mentorship, stretch assignments, exposure to strategy. Building the next generation of IT leaders.
Example key metric · team capability score · training completion and application rates
07 · Agentic Layer · Next Upgrade
AI
The emerging and applied AI layer. Separated from Intelligence (Layer 02) because it represents the cutting edge — the part of the stack that's changing fastest, and the layer most clients hire us to deliver.
- LLM integration & orchestration — How enterprise systems connect to and leverage large language models. API design, prompt management, response validation.
- Platform-agnostic by default — We deploy across all major AI platforms — Anthropic Claude, OpenAI & Microsoft Copilot, Google Gemini, AWS Bedrock — and pick what fits the client's regulatory posture, vendor strategy, and use case. The model isn't the moat; the architecture around it is.
- Agentic workflows — Multi-agent systems, autonomous task completion, human-in-the-loop patterns. (See Agentic.)
- Model governance & Responsible AI — Bias detection, output validation, audit trails, explainability. The governance layer for AI specifically.
Example key metric · agent deployment count · % AI use cases with governance documentation
Category & discipline · BOAT
Business Orchestration and
Business Orchestration and
Automation Technologies.
BOAT is the Gartner umbrella term for the technologies that orchestrate and automate enterprise operations — iPaaS, workflow engines, RPA, intelligent process automation, low-code, agentic systems. It's the category that Layer 03 lives inside. Hiday's discipline is to govern every BOAT initiative against four questions, before funding and during delivery — so the category produces business outcomes instead of technical debt.
01
Outcome
What changes for the business when this works? Defined in plain language, before any technical work begins.
02
Measurement
Baseline, target, frequency, source. Leading indicators where they exist. If you can't measure it, you can't govern it.
03
Ownership
A business owner — not just a technical owner — accountable for the outcome. Co-signs the investment, has the authority to pivot or kill.
04
Governance
Registered in Layer 01 from day one: AIRB review, risk assessment, resource allocation, success and exit criteria.
Diagnostic
Where is your enterprise on this stack?
Request a diagnostic
Where is your enterprise on this stack?
Let's map it together.
We run a 2-week EnterpriseOS diagnostic that scores your maturity at each layer and identifies the lowest-leverage gaps blocking Layer 07. The output is a sequenced roadmap, not a slide deck.