Inspection App System Requirements Document

Introduction

The Inspection App is a comprehensive software solution designed to facilitate NEN 2767 building inspections. This application is intended to be a SaaS platform that provides a responsive web frontend, a mobile-friendly inspection app, and a secure, scalable backend. The system will support multi-tenancy, ensuring isolated data for multiple organizations/clients, and will comply with GDPR regulations.

System Overview

The Inspection App will be built using modern web technologies to ensure a robust and scalable solution. The application will consist of the following components:

• Frontend: A responsive web application built with React/Next.js.
• Mobile App: A mobile-friendly inspection app developed as a Progressive Web App (PWA) or using React Native.
• Backend: A secure and scalable backend using Node.js or Python with FastAPI.
• Database: A relational database using PostgreSQL.
• File Storage: For storing photos, floor plans, and reports.

The application will be designed to handle offline-first capabilities, allowing users to perform inspections without an internet connection and sync data once back online.

Functional Requirements as Story Points

EPIC 1: Core NEN 2767 Inspection Model

• As an Inspector, I should be able to score conditions using the NEN 2767-1 model with severity, extent, and intensity.
• As a User, I should be able to search a database of standardized NEN 2767-2 defects.
• As a User, I should be able to use NL/SfB coding for building elements.
• As a User, I should be able to view a decomposition hierarchy from Asset to Material.
• As an Inspector, I should be able to automatically calculate condition scores upon defect entry.
• As a User, I should be able to reference NPR 4768 photos and definitions.

EPIC 2: Mobile Inspection App (Fieldwork)

• As an Inspector, I should be able to use the app offline for inspections.
• As an Inspector, I should be able to enter defect data using standardized screens.
• As an Inspector, I should be able to capture photos and videos linked to defects.
• As an Inspector, I should be able to annotate photos and floor plans with drawings and text.
• As an Inspector, I should be able to use speech-to-text for notes.
• As an Inspector, I should be able to scan QR/barcodes to identify building parts.

EPIC 3: Object & Asset Management

• As a User, I should be able to manage a central registry of properties.
• As a User, I should be able to access a library of building elements with lifespan and maintenance cycles.
• As a User, I should be able to view inspection and maintenance history per element.
• As a User, I should be able to upload and visualize floor plans with clickable inspection points.
• As a User, I should be able to see the last inspection date per element.

EPIC 4: Multi-Year Maintenance Planning (MJOP)

• As a User, I should be able to generate a multi-year maintenance plan from condition scores.
• As a User, I should be able to estimate costs using an editable cost library.
• As a User, I should be able to perform scenario analysis for maintenance strategies.
• As a User, I should be able to prioritize maintenance based on condition scores and risk.
• As a User, I should be able to export budget tables and charts.

EPIC 5: Reporting & Exports

• As a User, I should be able to generate NEN-compliant report templates.
• As a User, I should be able to use a drag-and-drop custom report builder.
• As a User, I should be able to generate PDF reports with white-label branding.
• As a User, I should be able to export raw data to Excel, CSV, and XML.

EPIC 6: User Management & Collaboration

• As an Admin, I should be able to manage role-based access control.
• As a Client, I should be able to view reports and MJOPs in a secure portal.
• As a Team Leader, I should be able to assign inspections and track progress.
• As a User, I should be able to view a full audit trail for changes.

EPIC 7: Integrations & API

• As a Developer, I should be able to access a comprehensive REST API with documentation.
• As a User, I should be able to use Single Sign-On with Azure AD and Google Workspace.
• As a Developer, I should be able to integrate with ERP/financial systems via webhooks.
• As a User, I should be able to view properties on a GIS map.
• As a User, I should be able to import BIM (IFC) data to pre-populate building elements.

EPIC 8: Administration & Configuration

• As an Admin, I should be able to manage and update official NEN 2767-2 defect lists.
• As an Admin, I should be able to add custom defects and scoring rules.
• As an Admin, I should be able to manage a custom cost library for maintenance tasks.
• As a User, I should be able to receive automated email reminders for re-inspections.

EPIC 9: Analytics & Dashboards (“Wow” Factor)

• As a User, I should be able to view real-time dashboards with condition score summaries.
• As a User, I should be able to perform portfolio-wide comparative analytics.
• As a User, I should be able to view a risk matrix of condition scores vs. failure probability.
• As a User, I should be able to perform trend analysis and degradation prediction.
• As a User, I should be able to receive AI/ML suggestions for predictive maintenance.

EPIC 10: Security & Infrastructure

• As a User, I should be able to ensure encryption at rest and in transit.
• As a User, I should be able to use Multi-Factor Authentication.
• As an Admin, I should be able to manage automated daily backups and disaster recovery plans.
• As a User, I should be able to ensure GDPR/AVG compliant data handling.

User Personas

• Inspector: Conducts on-site inspections, enters defect data, and captures media.
• Admin: Manages user roles, configurations, and system settings.
• Client: Views reports and maintenance plans through a secure portal.
• Team Leader: Assigns inspections and monitors team progress.
• Developer: Integrates external systems and maintains the API.

Core User Flows

• Inspector conducts inspection -> enters defect data -> captures photo/video -> syncs data when online.
• Admin updates defect lists -> configures scoring rules -> manages user roles.
• Client accesses portal -> views reports and MJOPs -> downloads data.
• Team Leader assigns inspections -> tracks progress -> reviews audit trails.
• Developer accesses API -> integrates ERP system -> documents integration.

Visuals Colors and Theme

• primary: #1E3A8A (Deep Blue)
• primary_light: #3B82F6 (Light Blue)
• secondary: #F97316 (Coral)
• accent: #10B981 (Emerald)
• highlight: #F59E0B (Amber)
• bg: #F3F4F6 (Light Gray)
• surface: rgba(255, 255, 255, 0.8)
• text: #111827 (Dark Gray)
• text_muted: #6B7280 (Muted Gray)
• border: rgba(209, 213, 219, 0.2)

Signature Design Concept

Interactive Inspection Map

The homepage will feature an interactive map of a building where users can click on different parts to view inspection details. Each building element will be represented as a clickable area that, when hovered over, displays a brief summary of its condition score. Clicking on an element will open a detailed view with photos, defect entries, and maintenance history.

• Animations: Use motion/react for smooth transitions and hover effects.
• Interactions: Users can drag to pan across the map and zoom in/out for detailed views.
• Micro-interactions: Hovering over elements will trigger subtle animations to indicate interactivity.
• Responsive Design: The map will adjust to different screen sizes, ensuring usability on both desktop and mobile devices.

LANDING HERO MOTION BRIEF

The landing hero will depict a dynamic transformation of a building's condition over time. Starting with a pristine building, visible defects will appear as the timeline progresses, showcasing the app's ability to track and manage building conditions. The animation will loop every 10 seconds, with interactive elements allowing users to pause and explore specific defects.

• Layers: Foreground (building elements), Midground (defect animations), Background (cityscape).
• Loop: A seamless 10-second loop showing the building's condition changes.
• Interaction: Users can click on defects to view more information.
• Reduced Motion: For users with motion sensitivity, a static version will be available.

Interaction Model & Motion Direction

• Intended Interaction Model: Parallax
• Description: The landing page will utilize a parallax effect to create depth, with layers moving at different speeds as users scroll. This will enhance the storytelling aspect of the inspection process, drawing users into the narrative of building maintenance