Discover
Browse the grouped app directory or search across the Hub's app records.
/
App Hub
CS WIND OFFSHORE · AALBORG
A guided tour of the App Hub: where to find the tools, how work connects, and how shared production status comes together.
A 19-minute introduction · Based on the repository catalogue and architecture
THE ROLE
The Hub is both a directory for the app ecosystem and a common window onto selected operational status.
Browse the grouped app directory or search across the Hub's app records.
/Read an app's description, then continue to the tool for that part of the work.
/apps/[id]Use the Dashboard for selected, cross-source aggregate views.
/production-dashboardTwo jobs, one entry point. The catalogue helps people choose a tool; the Dashboard combines selected status without taking ownership of every source dataset.
THE ECOSYSTEM · 8 FEATURED APPS
A focused selection from the apps shown on the App Hub landing page, arranged in the same four groups.
This presentation selection does not change the App Hub catalogue or its search results.
RELATIONSHIPS IN THE CATALOGUE
Only the eight featured apps appear here. Each arrow reflects a relationship declared in the App Hub catalogue, not necessarily a live data feed.
Connected does not mean duplicated. Each app keeps its own purpose; the relationship map helps explain where work can be referenced or handed across.
THE ENTRY EXPERIENCE
The landing view starts with featured catalogue entries. Search can find across all app records; a detail view adds context before the app opens.
Search names, descriptions and catalogue details.
Read what the app does and how it relates to others.
The Hub is the entry point; specialist work remains in its app.
Keyboard shortcut “/” focuses landing search in the current implementation. The presentation itself also supports keyboard scene navigation.
DATA FLOW · OWNERSHIP · FRESHNESS
Two simplified paths, based on the repository architecture. Sync paths have explicit destinations; read paths feed selected Dashboard views.
This diagram omits credentials, file paths, operational values and implementation exceptions. Not every connection is read-only: the Sync Hub has approved write paths.
LIVE APPLICATION · DASHBOARD
The same repository and D1 records serve two access boundaries. Select Manager or User below, then enter the selected surface's access code.
LIVE APPLICATION · INTRODUCTION OF TP
Sign in to explore the real 3D model. Once the protected model opens, this view expands beneath the presentation header. Inspect components, dimensions and centerlines, or switch to factory and production views.
LIVE APPLICATION · TP PUNCHLIST
This is the working TP Punchlist application, loaded live. Choose a TP, department, inspection type or punch item inside the frame to follow the real screen.
LIVE APPLICATION · REPORTER
The real Reporter app has four field modules: safety walks, incident reports with photos, maintenance breakdowns and improvement ideas. Its desktop view supports analysis and weekly reporting; mobile starts from a four-tile launcher.
LIVE APPLICATIONS · QUALITY / DOCUMENTS / PROJECTS
Choose an application below. Each live application starts at its own sign-in screen for this presentation.
OPERATING EFFECT
The codebase provides a basis for shared status and defined refresh paths. Time savings and financial return are not presented here as measured outcomes.
WITHOUT A SHARED PATH
WITH THE HUB PATTERN