Contact person: FDV4 Platform Development (Web & Mobile)

Phone:Show

Email:Show

Location: Ski, Norway

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Project: Build FDV4 (Phase 1 MVP) — Web & Mobile
Summary

We’re hiring freelance developers to build the first production-ready modules of FDV4, a digital platform for Facilities Management (FDV) of buildings and infrastructure (bridges, dams, offshore platforms, terminals). The MVP must ship fast, cover role-based dashboards, basic inspections/reporting, and 3D (GIS/BIM) viewing, and run on web and mobile with online/offline field capture. Short timeline; strong delivery may lead to a larger follow-on scope.

Primary users: asset owners and infrastructure operators.

Goals (Phase 1 MVP)

Deliver a usable slice that proves:

Smooth sign-up/sign-in and role-based access.

A configurable dashboard (incl. “traffic-light” status indicators).

Creation of inspections with photos/notes (offline on mobile, with sync).

Read-only 3D model viewing and linking to assets/inspections.

Basic notifications and document navigation (breadcrumbs).

These priorities come from prior EXCON/FDV4 discussions: SSO with email+password; role-based views; traffic-light status; customizable dashboards; early data visualizations; monitoring of stress thresholds/estimated lifetime; 3D with GIS/BIM compatibility; emissions/cost splits by component; notifications; mobile capture/inspect/report (offline); document breadcrumbs; and backend with GIS/BIM server + integration bus.

EXCON H1 establishes a TEA decision model and data backbone (LCA/LCC etc.) that FDV4 should later interface with; Phase 1 only lays foundations for that.

Scope & Deliverables
1) Authentication & Roles

Email+password sign-up/sign-in (no separate username), secure hashing, token/session, password reset.

Role model in backend (owner / consultant / field / admin) with simple policy checks.
Grounded by SSO simplification and role-based functions.

2) Role-Based Dashboard

Configurable cards for assets, inspections due/overdue, open findings.

“Traffic-light” (green/amber/red) indicators for status/risks.

Quick links per role; hide non-relevant metrics for consultants (e.g., lifecycle/carbon).
Backed by meeting points on traffic lights, role-based quick access, and customizable dashboards.

3) Inspections & Reporting (Web + Mobile)

Create inspection, add notes/photos, tag asset/location; offline capture on mobile with deferred sync.

Basic list/detail views and export (PDF/CSV) for reports.

Field app UX optimized for speed.
Matches the “capture–inspect–report”, online/offline requirement.

4) 3D Viewer (Read-Only)

Load a sample structure (IFC/glTF/etc.), orbit/pan/zoom.

Click an element to show metadata and related inspections.

Prepare hooks for future annotations.
Must be compatible with existing GIS/BIM systems.

5) Notifications (Basic)

Server-side rules for due inspections / new critical findings → in-app alerts (email optional in Phase 1).
As discussed re: alerting and threshold-based criticality.

6) Document Handling (Starter)

Upload + folder/tags; breadcrumb navigation.
Per the “breadcrumbs & categorization” item.

Non-Goals (Phase 1)

Full TEA/LCA/LCC analytics, advanced forecasting, complex workflows—these come later, informed by EXCON H1 outcomes.

Tech Preferences (open to proposals)

Web: React/Angular/Vue + TypeScript; charting; 3D via [login to view URL] or similar.

Mobile: Cross-platform (React Native or Flutter) with offline store (SQLite/IndexedDB) + sync.

Backend: REST/GraphQL (Node/Express/NestJS, Python/FastAPI/Django, .NET, or Java/Spring).

Data: SQL (PostgreSQL + PostGIS if GIS), optional document store for files/images.

Integrations (prepare): GIS/BIM server, service bus for system integration, API layer for data “translation”.

Quality & Security

Clear module boundaries, README, env samples, seed data.

Basic unit tests on core logic; lint/format; OWASP-aware auth/inputs.

Containerized dev env (Docker) preferred.

Collaboration

Rapid, agile delivery; weekly demos.

Chat on Discord/Teams (Discord suggested in notes).

Git repo (feature branches + PRs). Short feedback cycles.

Budget & Timeline

Budget: NOK 100,000 for Phase 1.

Timeline: Short; propose a realistic 3–6 week plan with milestones below.

Suggested Milestones

Week 1: Auth + role model + skeleton web/mobile; data model; CI.

Week 2: Role-based dashboard + traffic lights + notifications (basic).

Week 3: Inspections (web/mobile, offline capture & sync).

Week 4: 3D viewer (read-only) + asset linkage; docs upload + breadcrumbs.

Week 5: Polish, tests, packaging, handover demo & short video.

What to Include in Your Proposal

Relevant portfolio (especially: offline mobile, 3D/GIS/BIM, enterprise dashboards).

Tech stack choice and brief architecture sketch.

Milestone plan with deliverables tied to budget.

Risks/assumptions and how you’ll de-risk timeline.

Team size/availability; start date (ASAP preferred)." (client-provided description)