Skip to main content
SAHM

This site uses cookies to improve your experience and analyze visits.

Accept all
Reject all (essential only)
Customize
Learn more about cookies
SAHM logo
  • Home
  • About
  • Pricing
  • Knowledge Hub
  • Support
  • Book a Meeting
  • Customer Portal
  • Employee Portal
  • Contact
Menu

Language

Services

Digital TransformationEnterprise ArchitectureNORA ComplianceEA Tool ImplementationPricing

Expertise

TOGAF FrameworkDGA NORAAvolution ABACUSIT Strategy

Company

About UsContact Us

Resources

Schedule ConsultationRequest DemoCustomer SupportSubmit Ticket

Legal

Privacy PolicyTerms of ServiceCookie PolicyAccessibilitySecurity Policy

Get in touch

info@sahm.sa+966 53 113 0434

2023 - 2026 © SAHM Information Technology. All Rights Reserved. | Riyadh, Saudi Arabia

Back to Guides

EA Organizational Structure

How the EA unit is set up inside the entity: the roles, the reporting line, the job descriptions for the work team, and the place the Chief Enterprise Architect reports through.

In Brief

  • Where this page sits: EA roles and the EA organisational unit. NORA references them; the separate DGA Establishing EA Practice guideline is where they are detailed.
  • The internal structure and reporting line of the EA work team, with each role, its boundaries, and the experience it needs.
  • Gives the team a clear decision path and tells each member what is expected, so tasks and services run without overlap.
  • Main outputs: the role list, the approved structure, the unit founding document, the job descriptions, and a way to bring in outside expertise when needed.

Functional Roles

Chief Enterprise Architect

Leads the work team, signs off the outputs, and is the Accountable (A) party in the responsibility matrix for every step of the national methodology.

Business Architect

Documents and develops the business architecture components: capabilities, services, processes, organisational structure, and policies, and ties them back to the entity strategy.

Beneficiary Experience Architect

Builds the beneficiary experience components: beneficiary segments, journeys, touchpoints, and digital channels.

Data Architect

Develops the data architecture components: entities, data flows, integrations, and data-exchange models inside and outside the entity.

Applications Architect

Develops the applications architecture components in line with the national technical standards, and covers business services and the entity operations.

Technology Architect

Designs the technology infrastructure: networks, servers, cloud environments, and what is needed to run the solutions.

Security Architect

Protects the other domains through cybersecurity controls, identity and access management, and compliance with national policies.

EA Tool Administrator

Runs the EA tool: users and permissions, repository updates, and the reports the team and stakeholders rely on.

Steps to Build the Structure

  1. Detail the functional roles

    Start from the entity approved list of EA tasks and services, derive the capabilities and skills each role needs, and write the job description from there.

  2. Pick the structure model and the sourcing for each role

    Choose the model that fits the entity size and maturity, then decide how each role is filled: an internal hire, a long-term contract, or a temporary external consultant.

  3. Set the reporting line and name the sponsor

    Decide where the EA unit sits inside the entity, closer to strategy management or to the IT function, and name the sponsor the unit reports to.

  4. Draft the unit founding document

    Pull the earlier outputs into one document that covers the unit mandate, the proposed structure, the roles, and the scope of authority, then submit it for formal approval.

Criteria for Organizational Reporting

CriterionStrategy-FocusedIT-Focused
FocusBacks strategy formation and roadmap selection, and leads the entity large strategic digital projects.Aligns the technology capabilities with business direction and develops the technology architecture and the standards that support it.
SponsorHead of strategy or equivalent.Chief Information Officer (CIO) or equivalent.
ScopeThe scope does not change with the reporting line, and every approved task must be delivered.The scope does not change with the reporting line, and every approved task must be delivered.
An EA unit with a clear structure, eight roles each with its own job description, and a flexible way to fill them through internal staff, contract, or consultants, is enough to run the practice in line with the national methodology and the entity maturity targets.
This guideline is issued by the Digital Government Authority under the National Enterprise Architecture Framework (NORA).

Related

Establishing EA practice

EA tasks

EA strategy

EA Organizational Structure | NORA Guide | SAHM