Skip to content
ArchNGN

Frameworks

Frameworks are compliance packages you apply at the account level. Applying a framework (for example APRA CPS 234) instantiates its control catalog as reference guidance and enables conformance reporting for your workspaces.

You will find Frameworks under Model in the left sidebar, alongside the Metamodel and Overlays. Applying or removing a framework is an account-admin action.

Browsing the Catalog

Section titled “Browsing the Catalog”

Frameworks are grouped by industry (for example Finance & Payments, Government & Public Sector, Healthcare & Data Privacy, Energy & Critical Infrastructure, and Global Cloud & Cybersecurity) so you can find the regimes relevant to your organisation.

Each framework lists its controls, each with a severity (high, medium, or low) that weights how heavily a gap counts against conformance.

Applying a Framework

Section titled “Applying a Framework”
  1. Open Model → Frameworks.
  2. Find the framework for your industry and obligations.
  3. Click Apply. The framework’s controls are added to your Reference Library as guidance, and conformance reporting is enabled.

Unlike Overlays, you can apply more than one framework at a time. An account may need to satisfy several regimes at once.

Conformance Reporting

Section titled “Conformance Reporting”

Once a framework is applied, ArchNGN reports how well the active workspace conforms to its controls. The conformance report shows which controls are satisfied, which have gaps, and the severity of each gap, so you can prioritise remediation.

Advisory vs Strict Enforcement

Section titled “Advisory vs Strict Enforcement”

Conformance can run in two modes:

  • Advisory: gaps are reported for visibility but do not block work. Use this while you build coverage.
  • Strict: conformance is enforced, so non-conforming designs are flagged as failures rather than warnings.

Account admins switch between advisory and strict enforcement from the Frameworks view.

Section titled “Related”
  • Reference Library: where an applied framework’s controls land as guidance.
  • Overlays: packages that change the metamodel schema (distinct from frameworks, which audit conformance).
  • Workstreams: AI workflows that design and review against your standards.