{
 "note": "Role-based competency profiles mapped to the Higher Ed Enterprise Model: HERM business capabilities (BRM v3.2.0), data topics (DRM), application and technology components (ARM, TRM), and this site's process, lifecycle, journey, service and outcome layers. Levels, descriptors and pathways are illustrative for the fictional Example State University. Replace them with your own job architecture.",
 "levels": [
  {
   "n": 1,
   "name": "Foundation",
   "title": "Business analyst I",
   "years": "0–2 years",
   "scope": "Works on defined pieces of a project with guidance.",
   "does": "Documents current processes and requirements using the site's templates; checks work with a senior analyst.",
   "moveUp": "Leads discovery for one process end to end and can explain where it sits in the capability map."
  },
  {
   "n": 2,
   "name": "Practitioner",
   "title": "Business analyst II",
   "years": "2–5 years",
   "scope": "Owns the analysis for a project or a single unit's processes.",
   "does": "Runs workshops, maps and measures processes, writes requirements and demo scripts, and links each to capabilities, data and systems.",
   "moveUp": "Shapes the scope of an initiative across units and is trusted to frame the problem before solutions are discussed."
  },
  {
   "n": 3,
   "name": "Senior",
   "title": "Senior business analyst",
   "years": "5–8 years",
   "scope": "Leads analysis across units, systems or a full lifecycle.",
   "does": "Frames initiatives, builds the business case, coaches other analysts and keeps process, data and application views consistent.",
   "moveUp": "Sets analysis standards for the institution and advises leaders on where to invest."
  },
  {
   "n": 4,
   "name": "Lead",
   "title": "Lead or principal business analyst",
   "years": "8+ years",
   "scope": "Sets the practice for the institution.",
   "does": "Owns methods and standards, sits on architecture and portfolio review, and develops the analyst community.",
   "moveUp": "Moves into enterprise architecture, portfolio leadership or a process excellence role."
  }
 ],
 "roles": [
  {
   "id": "analyst",
   "name": "Business analyst",
   "summary": "Maps and measures how work actually happens, designs future-state processes with the people who do them, and turns them into requirements, test cases and a case for change. Uses the enterprise model as the shared map: every process, requirement and data question is tied to a capability.",
   "playbookRole": "analyst",
   "competencies": [
    {
     "id": "cap",
     "name": "Capability mapping and assessment",
     "area": "Model literacy",
     "why": "Ties every request to the capability it serves, so scope, owners and overlaps are visible before solutions are chosen.",
     "know": [
      "HERM BRM structure: value chains, level 1 and level 2 capabilities",
      "Difference between a capability, a process and a system",
      "Capability scoring: maturity, importance, support"
     ],
     "lv": [
      "Finds the capabilities a request touches using the capability map.",
      "Runs a capability assessment for one unit and records scores with evidence.",
      "Uses capability heat maps to frame initiatives and spot overlaps across units.",
      "Owns how the institution assesses capabilities and keeps the map current."
     ],
     "map": [
      {
       "l": "BRM",
       "c": "BC206",
       "n": "Business Capability Management",
       "h": "Capabilities.dc.html"
      },
      {
       "l": "BRM",
       "c": "BC209",
       "n": "Enterprise Architecture",
       "h": "Capabilities.dc.html"
      },
      {
       "l": "Model",
       "c": "",
       "n": "Capability wheel",
       "h": "Capability-Wheel.dc.html"
      }
     ],
     "res": [
      {
       "t": "How to run a capability assessment",
       "k": "Method guide",
       "h": "EA-Toolkit.dc.html#tool=cap-method"
      },
      {
       "t": "HERM capability scoring",
       "k": "Interactive tool",
       "h": "EA-Toolkit.dc.html#tool=cap-score"
      },
      {
       "t": "Surface capability gaps",
       "k": "Use case",
       "h": "Use-Gaps.dc.html"
      },
      {
       "t": "Find redundant capabilities",
       "k": "Use case",
       "h": "Use-Overlap.dc.html"
      }
     ]
    },
    {
     "id": "process",
     "name": "Process discovery and modeling",
     "area": "Process",
     "why": "Shows how work really happens, including the workarounds, before anything is redesigned or automated.",
     "know": [
      "Process architecture levels: value chain to task",
      "BPMN for workflows, swimlanes for hand-offs, SIPOC for scope",
      "Observing and interviewing the people who do the work"
     ],
     "lv": [
      "Documents a current-state process from interviews using the house notation.",
      "Leads discovery for a process end to end and models it at the right level.",
      "Maps processes across units and lifecycle stages, and links steps to systems and data.",
      "Sets modeling standards and maintains the process architecture."
     ],
     "map": [
      {
       "l": "BRM",
       "c": "BC216",
       "n": "Business Process Management",
       "h": "Capabilities.dc.html"
      },
      {
       "l": "Process",
       "c": "",
       "n": "Process architecture",
       "h": "Process-Architecture.dc.html"
      },
      {
       "l": "Process",
       "c": "",
       "n": "Workflows",
       "h": "Workflows.dc.html"
      },
      {
       "l": "Lifecycle",
       "c": "",
       "n": "Lifecycles and stages",
       "h": "Lifecycles.dc.html"
      }
     ],
     "res": [
      {
       "t": "Process mapping and measurement",
       "k": "Method guide",
       "h": "EA-Toolkit.dc.html#tool=process-map"
      },
      {
       "t": "Modeling standards: which notation where",
       "k": "Method guide",
       "h": "EA-Toolkit.dc.html#tool=notations"
      },
      {
       "t": "Process architecture",
       "k": "Model",
       "h": "Process-Architecture.dc.html"
      }
     ]
    },
    {
     "id": "improve",
     "name": "Process measurement and improvement",
     "area": "Process",
     "why": "Turns opinions about a process into evidence: cycle time, hand-offs, rework and where students wait.",
     "know": [
      "Cycle time, touch time, wait time, first-pass yield",
      "Lean waste and root-cause methods",
      "Small tune-ups versus redesign versus automation"
     ],
     "lv": [
      "Collects baseline measures for a process using the template.",
      "Runs a process tune-up and reports before-and-after results.",
      "Leads improvement across units and chooses between tune-up, redesign and automation.",
      "Builds the institution's improvement method and coaches others in it."
     ],
     "map": [
      {
       "l": "BRM",
       "c": "BC216",
       "n": "Business Process Management",
       "h": "Capabilities.dc.html"
      },
      {
       "l": "BRM",
       "c": "BC165",
       "n": "Quality Management",
       "h": "Capabilities.dc.html"
      },
      {
       "l": "Framework",
       "c": "",
       "n": "Lean Six Sigma",
       "h": "LSS.dc.html"
      }
     ],
     "res": [
      {
       "t": "Current-state process measurement",
       "k": "Template",
       "h": "EA-Toolkit.dc.html#tool=process-measure"
      },
      {
       "t": "Process tune-up",
       "k": "Method guide",
       "h": "EA-Toolkit.dc.html#tool=tune-up"
      },
      {
       "t": "Process tune-up charter",
       "k": "Template",
       "h": "EA-Toolkit.dc.html#tool=tune-charter"
      },
      {
       "t": "Find operational efficiencies",
       "k": "Use case",
       "h": "Use-Efficiency.dc.html"
      }
     ]
    },
    {
     "id": "req",
     "name": "Requirements and solution evaluation",
     "area": "Solutions",
     "why": "Describes what the institution needs in terms vendors and builders can test, and checks what already exists before buying.",
     "know": [
      "Requirements tied to capabilities and functions, not to a product",
      "Demo scripts drawn from real scenarios",
      "Functions and features of the core systems"
     ],
     "lv": [
      "Writes clear requirements and acceptance criteria from a process map.",
      "Builds requirements and demo scripts for a selection and scores vendor demos.",
      "Leads solution evaluation and checks requirements against existing systems' functions first.",
      "Sets how the institution evaluates solutions and sits on intake review."
     ],
     "map": [
      {
       "l": "ARM",
       "c": "AC010",
       "n": "Programme & Project Management",
       "h": "ARM.dc.html"
      },
      {
       "l": "Model",
       "c": "",
       "n": "Core systems functions and features",
       "h": "Core-Systems.dc.html"
      },
      {
       "l": "Model",
       "c": "",
       "n": "Application portfolio",
       "h": "Application-Portfolio.dc.html"
      }
     ],
     "res": [
      {
       "t": "Requirements and demo scripts",
       "k": "Template",
       "h": "EA-Toolkit.dc.html#tool=requirements"
      },
      {
       "t": "Vendor and solution intake",
       "k": "Checklist",
       "h": "EA-Toolkit.dc.html#tool=intake"
      },
      {
       "t": "Evaluate before you buy",
       "k": "Use case",
       "h": "Use-Intake.dc.html"
      }
     ]
    },
    {
     "id": "data",
     "name": "Data and information analysis",
     "area": "Data",
     "why": "Knows which data each process creates and uses, who owns it and what it means, so reports and integrations agree.",
     "know": [
      "HERM DRM topics and entities",
      "Data ownership, stewardship and definitions",
      "Reading a data flow and a report specification"
     ],
     "lv": [
      "Lists the data a process creates and uses, with its source system.",
      "Maps process steps to DRM entities and confirms definitions with data stewards.",
      "Leads data analysis for an initiative, including quality issues and reporting needs.",
      "Shapes how analysis and data governance work together across the institution."
     ],
     "map": [
      {
       "l": "BRM",
       "c": "BC135",
       "n": "Information Management",
       "h": "Capabilities.dc.html"
      },
      {
       "l": "BRM",
       "c": "BC211",
       "n": "Business Intelligence & Reporting",
       "h": "Capabilities.dc.html"
      },
      {
       "l": "DRM",
       "c": "DT006",
       "n": "Student Management",
       "h": "DRM.dc.html"
      },
      {
       "l": "DRM",
       "c": "DT024",
       "n": "Role",
       "h": "DRM.dc.html"
      }
     ],
     "res": [
      {
       "t": "Govern data by capability",
       "k": "Use case",
       "h": "Govern-Data-by-Capability.dc.html"
      },
      {
       "t": "Data governance (DAMA-DMBOK)",
       "k": "Framework",
       "h": "DAMA.dc.html"
      },
      {
       "t": "Data reference model",
       "k": "Model",
       "h": "DRM.dc.html"
      }
     ]
    },
    {
     "id": "journey",
     "name": "Journey and service design",
     "area": "Experience",
     "why": "Designs from the student, faculty or staff member's side, so changes fix the experience, not just the back office.",
     "know": [
      "Journey mapping and lenses for different constituents",
      "Service blueprints: front stage, back stage, support",
      "Lifecycle stages and the services that support them"
     ],
     "lv": [
      "Contributes to a journey map and collects pain points from users.",
      "Builds a journey map and service blueprint for one service.",
      "Designs services across units using lifecycle stages and journey lenses.",
      "Sets service design practice and links it to the service catalog."
     ],
     "map": [
      {
       "l": "BRM",
       "c": "BC218",
       "n": "Service Management",
       "h": "Capabilities.dc.html"
      },
      {
       "l": "Experience",
       "c": "",
       "n": "User journeys",
       "h": "Journeys.dc.html"
      },
      {
       "l": "Experience",
       "c": "",
       "n": "Org units and services",
       "h": "Org-Services.dc.html"
      }
     ],
     "res": [
      {
       "t": "Service blueprint",
       "k": "Template",
       "h": "EA-Toolkit.dc.html#tool=blueprint"
      },
      {
       "t": "Journey builder",
       "k": "Interactive tool",
       "h": "Journey-Builder.dc.html"
      },
      {
       "t": "Improve the experience",
       "k": "Use case",
       "h": "Use-Experience.dc.html"
      }
     ]
    },
    {
     "id": "engage",
     "name": "Stakeholder engagement and facilitation",
     "area": "People",
     "why": "Gets the right people in the room and keeps them there, including students and the staff who do the work.",
     "know": [
      "Stakeholder analysis and engagement planning",
      "Workshop design and facilitation",
      "Change impact on roles and units"
     ],
     "lv": [
      "Supports workshops and records decisions and actions.",
      "Plans and runs workshops for a project and manages its stakeholders.",
      "Facilitates across units with conflicting interests and brings the change impact forward.",
      "Coaches others in facilitation and advises leaders on engagement."
     ],
     "map": [
      {
       "l": "BRM",
       "c": "BC207",
       "n": "Change Management",
       "h": "Capabilities.dc.html"
      },
      {
       "l": "Model",
       "c": "",
       "n": "Org units",
       "h": "Org-Services.dc.html"
      }
     ],
     "res": [
      {
       "t": "Stakeholder engagement plan",
       "k": "Template",
       "h": "EA-Toolkit.dc.html#tool=stakeholders"
      },
      {
       "t": "Plan a change safely",
       "k": "Use case",
       "h": "Use-Change.dc.html"
      }
     ]
    },
    {
     "id": "value",
     "name": "Value and business case",
     "area": "Value",
     "why": "Shows what a change is worth and to whom, in terms leaders and finance recognise.",
     "know": [
      "Linking capabilities to institutional outcomes",
      "Benefits, cost and effort-impact",
      "Five-year total cost of ownership"
     ],
     "lv": [
      "Estimates effort and impact for proposed changes.",
      "Builds the benefits register for a project and tracks it after launch.",
      "Builds the business case for an initiative, tied to strategic outcomes.",
      "Advises the portfolio on value and sets how benefits are measured."
     ],
     "map": [
      {
       "l": "BRM",
       "c": "BC230",
       "n": "Business Planning",
       "h": "Capabilities.dc.html"
      },
      {
       "l": "BRM",
       "c": "BC210",
       "n": "Portfolio & Programme Management",
       "h": "Capabilities.dc.html"
      },
      {
       "l": "Value",
       "c": "",
       "n": "Outcomes and value",
       "h": "Outcomes.dc.html"
      }
     ],
     "res": [
      {
       "t": "Effort-impact sheet",
       "k": "Template",
       "h": "EA-Toolkit.dc.html#tool=effort-impact"
      },
      {
       "t": "Benefits register",
       "k": "Template",
       "h": "EA-Toolkit.dc.html#tool=benefits"
      },
      {
       "t": "Five-year TCO and business case",
       "k": "Template",
       "h": "EA-Toolkit.dc.html#tool=tco"
      },
      {
       "t": "Set the investment agenda",
       "k": "Use case",
       "h": "Use-Investment.dc.html"
      }
     ]
    },
    {
     "id": "auto",
     "name": "Automation and integration awareness",
     "area": "Solutions",
     "why": "Knows what the platforms can do, so designs fit how systems connect and which automation tier is right.",
     "know": [
      "Automation tiers: configure, low-code, workflow, RPA",
      "How integrations and APIs move data between systems",
      "Where workflow orchestration belongs"
     ],
     "lv": [
      "Recognises when a step could be automated and flags it.",
      "Recommends an automation tier for a process using the guide.",
      "Designs future-state processes across systems with IT and integration teams.",
      "Shapes the institution's automation approach with architecture."
     ],
     "map": [
      {
       "l": "TRM",
       "c": "TC103",
       "n": "Workflow Orchestration",
       "h": "TRM.dc.html"
      },
      {
       "l": "TRM",
       "c": "TC129",
       "n": "Low-Code Application Platform",
       "h": "TRM.dc.html"
      },
      {
       "l": "TRM",
       "c": "TC080",
       "n": "Robotic Process Automation",
       "h": "TRM.dc.html"
      },
      {
       "l": "TRM",
       "c": "TC079",
       "n": "API Management",
       "h": "TRM.dc.html"
      }
     ],
     "res": [
      {
       "t": "Choosing an automation tier",
       "k": "Method guide",
       "h": "EA-Toolkit.dc.html#tool=auto-tier"
      },
      {
       "t": "A process automation service",
       "k": "Playbook",
       "h": "Practice.dc.html#process-automation"
      },
      {
       "t": "An integration and API layer",
       "k": "Playbook",
       "h": "Practice.dc.html#integration"
      }
     ]
    },
    {
     "id": "ai",
     "name": "AI and emerging technology literacy",
     "area": "Solutions",
     "why": "Judges where AI helps a process, where a person must stay in the loop, and what data it may reach.",
     "know": [
      "AI risk tiers and human oversight",
      "What an agent needs from processes, data and systems",
      "Change impact of AI on roles"
     ],
     "lv": [
      "Explains how AI is used in a process and its limits.",
      "Assesses AI readiness for a process with the checklist.",
      "Designs processes with AI steps and clear human decision points.",
      "Advises on where AI changes work across the institution."
     ],
     "map": [
      {
       "l": "Model",
       "c": "",
       "n": "AI readiness",
       "h": "AI-Readiness.dc.html"
      },
      {
       "l": "Model",
       "c": "",
       "n": "AI inventory",
       "h": "AI-Inventory.dc.html"
      }
     ],
     "res": [
      {
       "t": "AI readiness and change impact checklist",
       "k": "Checklist",
       "h": "EA-Toolkit.dc.html#tool=ai-readiness-check"
      },
      {
       "t": "Agent workflows with humans in the loop",
       "k": "Playbook",
       "h": "Practice.dc.html#agent-workflows"
      },
      {
       "t": "Scope AI safely",
       "k": "Use case",
       "h": "Use-AI.dc.html"
      }
     ]
    }
   ],
   "profile": {
    "1": {
     "cap": 1,
     "process": 1,
     "improve": 1,
     "req": 1,
     "data": 1,
     "journey": 1,
     "engage": 1,
     "value": 1,
     "auto": 1,
     "ai": 1
    },
    "2": {
     "cap": 2,
     "process": 2,
     "improve": 2,
     "req": 2,
     "data": 2,
     "journey": 2,
     "engage": 2,
     "value": 1,
     "auto": 2,
     "ai": 2
    },
    "3": {
     "cap": 3,
     "process": 3,
     "improve": 3,
     "req": 3,
     "data": 3,
     "journey": 3,
     "engage": 3,
     "value": 3,
     "auto": 2,
     "ai": 2
    },
    "4": {
     "cap": 4,
     "process": 4,
     "improve": 3,
     "req": 4,
     "data": 3,
     "journey": 3,
     "engage": 4,
     "value": 4,
     "auto": 3,
     "ai": 3
    }
   },
   "moves": [
    {
     "to": "Enterprise architect",
     "d": "Widen from processes to the whole model: applications, data and technology.",
     "focus": [
      "cap",
      "data",
      "auto"
     ],
     "h": "EA-Toolkit.dc.html"
    },
    {
     "to": "Process improvement lead",
     "d": "Go deeper on measurement and Lean Six Sigma methods.",
     "focus": [
      "improve",
      "process",
      "engage"
     ],
     "h": "LSS.dc.html"
    },
    {
     "to": "Product owner",
     "d": "Own a system or service and its backlog over time.",
     "focus": [
      "req",
      "journey",
      "value"
     ],
     "h": "Core-Systems.dc.html"
    },
    {
     "to": "Data steward",
     "d": "Own definitions, quality and access for a data domain.",
     "focus": [
      "data",
      "cap"
     ],
     "h": "Govern-Data-by-Capability.dc.html"
    },
    {
     "to": "Change lead",
     "d": "Lead how people move from the old way of working to the new one.",
     "focus": [
      "engage",
      "journey",
      "ai"
     ],
     "h": "Use-Change.dc.html"
    }
   ]
  }
 ],
 "others": [
  {
   "id": "analyst",
   "name": "Business analyst",
   "layers": [
    "BRM",
    "Process",
    "DRM",
    "Experience",
    "Value"
   ],
   "ex": "Capability mapping, process discovery and measurement, requirements, journey and service design."
  },
  {
   "id": "ea",
   "name": "Enterprise architect",
   "layers": [
    "BRM",
    "ARM",
    "TRM",
    "DRM",
    "Value"
   ],
   "ex": "Capability-based planning, application rationalization, target architecture, architecture decisions and review."
  },
  {
   "id": "steward",
   "name": "Data steward",
   "layers": [
    "DRM",
    "BRM",
    "Process"
   ],
   "ex": "Data definitions and ownership by capability, data quality, access decisions, reporting lineage."
  },
  {
   "id": "owner",
   "name": "System or product owner",
   "layers": [
    "ARM",
    "BRM",
    "Experience",
    "Value"
   ],
   "ex": "Functions and features coverage, roadmap and backlog, vendor management, recovery and continuity."
  },
  {
   "id": "lss",
   "name": "Process improvement lead",
   "layers": [
    "Process",
    "Lifecycle",
    "Value"
   ],
   "ex": "Process measurement, Lean Six Sigma methods, automation tiers, benefits tracking."
  },
  {
   "id": "change",
   "name": "Change lead",
   "layers": [
    "Experience",
    "BRM",
    "Value"
   ],
   "ex": "Change impact by capability and role, readiness, communication, AI and change literacy."
  },
  {
   "id": "service",
   "name": "Service manager",
   "layers": [
    "Experience",
    "BRM",
    "ARM",
    "TRM"
   ],
   "ex": "Service catalog and ownership, service levels, ITSM practices, continuity of tier 1 services."
  }
 ]
}