CS Wind OffshoreApp HubAalborg · presentation

CS WIND OFFSHORE · AALBORG

Many tools.
One front door.

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

ProductionQualitySafety
AApp
Hub
DocumentsProjects
Shared
status

THE ROLE

Find it. Open it. See the shared picture.

The Hub is both a directory for the app ecosystem and a common window onto selected operational status.

01

Discover

Browse the grouped app directory or search across the Hub's app records.

/
02

Open

Read an app's description, then continue to the tool for that part of the work.

/apps/[id]
03

See shared status

Use the Production Dashboard for selected, cross-source aggregate views.

/production-dashboard

Two 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 · 24 CATALOGUE RECORDS

Different jobs. A connected set of tools.

The map uses each app's saved category and lifecycle status. The static inCatalog flag is shown separately from the full app list.

Active Planning Maintenance Archived inCatalog flag

11 records have inCatalog: true; search uses all 24 records. Lifecycle labels are not usage or quality metrics.

RELATIONSHIPS IN THE CATALOGUE

Work connects across specialist apps.

These links summarize relationships declared in the app catalogue. They describe a relationship, 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

From a question to the right tool.

The landing view starts with featured catalogue entries. Search can find across all app records; a detail view adds context before the app opens.

01 · SEARCH

Start with the work

Search names, descriptions and catalogue details.

02 · UNDERSTAND
App detailPurpose · capabilities · relationships

Check the fit

Read what the app does and how it relates to others.

03 · CONTINUE
Open application

Continue in the app

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

Keep ownership clear. Make status easier to see.

Two simplified paths, based on the repository architecture. Sync paths have explicit destinations; read paths feed selected Dashboard views.

APrepare or syncControlled write path
BRead and presentSelected data path

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 · PRODUCTION DASHBOARD

One shared picture. Role-appropriate access.

Open Manager surface

The same repository and D1 records serve two access boundaries. Select Manager or User below. The live Dashboard currently refuses embedding from this presentation address, so open the selected surface in its own authorized tab.

LIVE APPLICATION

Production Dashboard

Embedded viewing is refused by the app or sign-in boundary. Open the selected live surface to use its real controls and current data.

Open Manager surface ↗
Browser presentation uses the real, access-controlled surfaces.
Open Manager · Open User
REAL APP · MANAGER / USERSAME D1 RECORDS · ROLE-BASED ACCESSManager-only controls stay within the Manager surface.

LIVE APPLICATION · INTRODUCTION OF TP

Explore the TP in its 3D context.

Open 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.

If browser policy blocks the live view, open Introduction of TP directly.
Live 3D application is available during the browser presentation.
Open Introduction of TP
REAL APP · LIVE 3D MODELCOMPONENTS · DIMENSIONS · FACTORY / PROCESS VIEWSExpansion follows successful model loading.

LIVE APPLICATION · TP PUNCHLIST

Follow a punch from TP to item.

Open app in a new tab

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.

If the live view is blocked by browser security or sign-in, open TP Punchlist directly.
Live application view is available during the browser presentation.
Open TP Punchlist
REAL APP · LIVE SESSIONTP → DISCIPLINE → SECTION → PUNCH ITEMChanges made in the app are real operational actions.

LIVE APPLICATION · REPORTER

From a field report to a weekly picture.

Open Reporter in a new tab

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.

If sign-in is needed, use your authorized Reporter session or open Reporter directly.
Live application view is available during the browser presentation.
Open Reporter
REAL APP · LIVE SESSIONFIELD MODULE → REVIEW → ANALYTICS / WEEKLY REPORTUse an authorized Reporter session to open operational views.

LIVE APPLICATIONS · QUALITY / DOCUMENTS / PROJECTS

Choose an app. Explore its real workflow.

Open FlowGuide in a new tab

E-NCR, PM Master and Document Control load as live applications here. FlowGuide currently refuses embedded viewing from this presentation address; open it directly to use the real workflow.

LIVE APPLICATION

FlowGuide

Embedded viewing is refused from this presentation address. Open FlowGuide in its own authorized tab to explore the current process flow and linked documents.

Open live FlowGuide ↗
Open the live applications online:
FlowGuide · E-NCR · PM Master · Document Control
REAL APPS · LIVE SESSIONSFLOWGUIDE · E-NCR · PM MASTER · DOCUMENT CONTROLUse each app's authorized session and controls.

OPERATING EFFECT

See the work with less re-assembly.

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

Source updatesManual consolidationRepeated status views
Illustrative work pattern · not a measured baseline

WITH THE HUB PATTERN

Owner-managed sourceDefined sync / read routeShared aggregate view
Architecture capability · not a quantified saving
01 One place to start02 Source ownership stays explicit03 Shared status can be refreshed and reviewed

PROPOSED NEXT STEPS · DISCUSSION

Grow trust in the connections.

A discussion frame, not an approved roadmap. Confirm priorities with the people who own the apps and data.

01 · NOW

Keep the entry clear

Maintain accurate app descriptions, lifecycle labels and role boundaries.

02 · NEXT

Make freshness legible

Explain source ownership and update state where people use shared views.

03 · LATER

Extend with evidence

Add connections when ownership, access and operational value are agreed.

A useful Hub is built on clear ownership
and dependable paths between tools.

DATA FLOW DETAIL