Skip to content
Public Framework

An Open Framework for modeling public administration

Ideas shape administration. Concepts give form to public services. The framework brings coherence to transformation.

Public Framework provides a shared language — a metamodel, twenty principles and a modeling application — so that institutions, lawyers, civil servants and IT suppliers describe the same administrative reality in the same way.

Watch the video presentation

Available for Windows and macOS (Apple Silicon). Linux coming soon.

Public Framework mission patch: the P mark launching like a rocket above a public building, orbiting the Earth
12 layers · Modeller 1.0-RC2

Why Public Framework

Before we digitalize the state, we must learn to model it

Too often, digitalization turns a paper form into an online form without re-examining the logic of the procedure. Public Framework starts from understanding the institution: the competences, services, processes and administrative objects that software has to serve.

  • A shared language

    Administration, suppliers, lawyers and citizens use the same concepts with the same meaning.

  • Modeling before implementation

    No system is designed without a clear understanding of the processes it serves.

  • Governance and traceability

    Versioned models, clear responsibilities and an explicit link between law, service and system.

Video presentation

Public Framework in four minutes

It all starts with a problem. A shared language, a shared understanding and a coherent transformation — explained in brief.

The metamodel

Twelve layers, one coherent representation

Ten layers form a chain: from policy intent and legal basis, through services, information and applications, to hosting, operations and the continuity of the public service. Every element has a stable identity, and the relationships between elements are typed and checked.

Read the specification

Policy intent

  1. STRStrategy & Public Policy

    Why does the institution act?

    • Policy
    • Goal
    • Objective
    • Indicator
  2. LEGLegal Framework

    On what legal basis?

    • LegalResource
    • LegalProvision
    • LegalObligation
    • Competence
  3. ORGOrganisations & Services

    What does the institution offer, and to whom?

    • PublicOrganisation
    • PublicService
    • ServiceChannel
    • Procedure
  4. INFInformation

    With what information?

    • InformationEntity
    • Dataset
    • BaseRegistry
    • CodeList
  5. APPApplications

    With what software?

    • SoftwareSystem
    • Component
    • API
    • DataExchange
  6. DELSoftware Delivery

    How is the software produced?

    • SourceRepository
    • Pipeline
    • Artifact
    • Release
  7. RUNDeployment & Runtime

    Where and how does it run?

    • Environment
    • Cluster
    • Node
    • Deployment
  8. HSTHosting

    Who hosts it, and where?

    • HostingProvider
    • DataCentre
    • CloudRegion
    • HostingContract
  9. OPSOperations & Security

    How is it operated and protected?

    • Monitor
    • BackupPolicy
    • DisasterRecoveryPlan
    • SecurityControl
  10. CNTContinuity & Fallback

    What happens when the systems fail?

    • DisruptionScenario
    • ImpactAssessment
    • FallbackProcedure
    • RestorationPlan

Service continuity

Cross-cutting layers

Two layers sit outside the chain and cut across it: how the architecture changes, and the concepts that concern several layers at once.

  • IMPImplementation

    How does the architecture change?

    • Programme
    • Project
    • Funding
    • ArchitectureState
  • XCross-cutting Concepts

    What conditions, choices and uncertainties shape the architecture?

    • Requirement
    • ArchitectureDecision
    • Risk
    • Evidence

Principles

Twenty principles for meaningful digitalization

See all principles
  1. Digitalization must have purpose, not just technology.

    The goal is not to deploy applications but to genuinely solve the problems of citizens and civil servants.

  2. Modeling comes before implementation.

    No system is designed without a clear understanding of the processes it serves.

  3. The process defines the application, not the other way around.

    IT solutions must reflect real processes, not force them to conform to technology.

  4. Institutions must become able to define their own requirements.

    The civil servant is not only a beneficiary but the operational architect of digital transformation.

  5. All actors must speak the same language.

    A shared vocabulary is needed between administration, suppliers, citizens and consultants.

  6. The framework is alive and adaptable.

    Public Framework evolves together with society, technology and legislation.

Model public administration on your own machine

The Public Framework desktop app helps you build and verify models based on the metamodel. Available now for Windows and macOS on Apple Silicon.

Downloads are temporarily unavailable

We have paused downloads for a short while. Please check back soon.

Linux — coming soon

All download options