NAVICORE ONE company operating system · Part 52 · How it fits together
Decision checklist
See the questions NAVICORE asks before any new feature is added to NAVICORE ONE.
What this page describes is the intended scope from the product specification. The status label shows how far along this area is.
Illustrative layout, not a live screenshot.
What it is
Before a new feature is built, eleven questions are answered: where it belongs, which shared service it uses, what permissions it needs, what is audited, what happens in another company's workspace, whether it works across web, desktop and mobile, whether the demo stays isolated, whether licensing applies, whether another company can reuse it, whether it keeps the architecture intact, and whether it fits the current build scope.
The problem
Features added in a hurry weaken permissions, auditing and isolation one shortcut at a time.
What NAVICORE ONE does
NAVICORE ONE asks the same eleven questions of every new feature, covering module, shared services, permissions, audit, isolation, apps, demo, licensing, reuse, architecture and scope.
The result
New features strengthen the product instead of eroding it.
Who uses it, and when
- The NAVICORE engineering team
- Before building anything new
- Product decision-makers
- When deciding whether a feature belongs
How it works, step by step
Eleven questions
Sequence stated in the product specification.- 1
Which module does it belong to?
- 2
Which shared service does it use?
- 3
What permissions does it need?
- 4
What gets audited?
- 5
What happens in another company's workspace?
- 6
Does it work on web, desktop and mobile where appropriate?
- 7
Does the demo stay isolated?
- 8
Does licensing apply?
- 9
Can another company reuse it?
- 10
Does it keep the architecture intact?
- 11
Does it fit the current build scope?
Key functions
Module & shared service
Every feature has a home and uses the shared core.
Permissions & audit
Every feature declares who can use it and what is recorded.
Isolation
Every feature considers what happens in another company's workspace, and in the demo.
Apps
Every feature considers web, desktop and mobile.
Licensing & reuse
Every feature considers entitlements and reuse by other companies.
Architecture & scope
Every feature preserves the architecture and fits the current scope.
How it connects to other parts
- Part 50Foundation
The shared core
Understand the shared services every module builds on, so the whole product behaves as one.
- Part 51Foundation
Product layers
See the ten layers NAVICORE ONE is made of, from licensing and identity to the apps.
- Part 05In build
Roles & permissions
Decide exactly who can see and do what, down to a department, team or single project.
- Part 23In build
Audit trail
Keep a permanent record of who did what, when and what changed, for every important action.
- Part 02Live
Companies & workspaces
Give each company its own isolated workspace, set up the way that company actually runs.
- Part 03In build
License platform
Control which modules, users and limits each customer gets, from one place.
See it in action
Ask for a demo, or tell us how you would like to partner.