Glossary

Document ID: M17-CERT-001-D10

Audience: All customer roles

Last updated: 2026-09-17

Applies to: Jakten Platform 2.0

A

Activation — One-time process that binds a Platform deployment to a subscription using an activation key.

Activation key — Secret code used to activate one company deployment. It is not a user password or seat.

Assurance — Short name for Jakten Assurance, the module that governs and defends an estimate: packages, versions, cost model, changes, reviews, Basis of Estimate, and the governed handoff to Risk. It is not construction quality assurance (QA/QC), which concerns work in place; Assurance concerns the estimate.

Authoritative population — The current governed set of Estimate items composed from each Package. Missing data is not treated as zero.

B

Benchmark Pack — Immutable publication of eligible Assurance evidence for later comparison and company learning.

Basis of Estimate (BoE) — The structured explanation of scope, basis, methods, assumptions, qualifications, commercial evidence, and totals behind an Estimate Version.

C

Command Center — Lead-estimator home inside Jakten Assurance.

Commercial Attention — Factual list of unresolved conditions and their consequences; it is not a readiness verdict.

Company role — The one role each user holds across the company: Administrator, Editor, Reviewer, or Executive. Reviewer and Executive are read-only.

Company standard — Governed reusable definition, such as a WBS, unit, cost type, discipline, metric, Project Driver, Version type, dropdown list, or template.

D

Deployment — One installed Jakten Platform environment holding a company's Platform, Assurance, and Risk data set.

Deployment Health — Status on About & Deployment covering identity, licensing, legal state, updates, migrations, compatibility, and product health.

Dependency — Modeled statistical relationship among Risk estimate packages or groups.

E

Entitlement — Licensed right to use a product module under a subscription.

Estimate Version — Platform-owned project milestone or working version that supplies context to Jakten Assurance and Risk. Each is created from one of the company's Version types and keeps the name it was created with. Saved or issued evidence is version-specific.

Evolution — Assurance workspace for frozen cross-version comparison and historical commercial change.

F

Finding — Governed review observation recorded against a frozen or prepared review basis.

Frozen evidence — Historical artifact whose content is retained as issued or saved rather than recalculated from current data.

J

Jakten Assurance — Estimate assurance and governance module for packages, plan, cost model, change, knowledge, review, BoE, issue, and Risk handoff.

Jakten Platform — Company and project shell for users, access, licensing, standards, reports, and product hosting.

Jakten Risk — Monte Carlo risk and contingency module for estimate uncertainty, dependencies, risks, events, simulation, comparison, and reporting.

L

Line Exposures — Line-level Risk workspace for uncertainty and risk treatment attached to estimate rows. (Renamed from "Risk register".)

Living BoE — Working Basis of Estimate assembled from governed evidence and authored narrative before issue.

M

Metric result — Recorded output of a governed Company Metric evaluated against a specific Estimate state and population.

Module — Licensed product workspace hosted by Platform, such as Jakten Risk or Jakten Assurance. An administrator turns a module on for the company; each project then uses only the modules chosen for it.

Module role — A user's role within one module, such as Assurance Editor or Risk Viewer. It defaults from the company role and can only narrow it.

P

Package — Commercial boundary within an estimate that owns its current authoritative item population and related evidence.

Platform Server — Service hosting shared Platform APIs and the product stores for an office deployment.

Project Driver — Project physical quantity, such as area, tool count, or capacity, used to normalize Assurance knowledge and metrics.

Project role — A member's role on one project: Manager, Contributor, or Viewer. A Manager staffs and archives the project and chooses its modules.

Project setup — The step-by-step Create project flow: project and profile, modules, structure, metrics, first Estimate Version, team, and review. Nothing is saved until the last step.

Publication — Immutable, versioned handoff or artifact used across a governed boundary, such as Assurance to Risk.

R

Risk event — Discrete project risk or opportunity modeled separately from line-level uncertainty.

S

Seat — Named-user license assignment for a paid product. It is not a device license or concurrent-use pool.

Should-Cost Register — Project-scoped Assurance workspace for procurement packages, quotes, should-cost inputs, variance, and workflow.

Single-user deployment — Platform and product services running on one person's Windows PC.

Standard Metric — Governed metric definition published at company level and applied through the Estimate state workflow.

Suite update — Installer update for Platform and bundled product modules, started manually from About & Deployment.

V

Version type — A company-defined name estimators choose when creating an Estimate Version, such as 30%, 60%, or IFC. Each maps to a Jakten stage so projects compare across companies. Renaming or retiring a type changes only new Versions; a second Version of the same type on a project is labeled "Rev 2".

W

Workstation — End-user Windows PC connected to the Platform Server in an office deployment.

WBS — Work breakdown structure used to organize projects, Estimate items, and related Risk context.

Related documentation