Product Requirements Document

the organization · Internal Tool · v2.1 · May 2026

---

Document Information

Executive Summary

The Anomaly Upload Validator is a browser-based internal tool that automates the pre-upload preparation of inspection datasets for the the Internal Platform. It accepts raw the source inspection platform exports in CSV or XLSX format, validates them against the platform upload specification, converts field values across three nomenclature systems (the source inspection platform → the Internal Platform → the Output Platform), enables human-in-the-loop resolution of unmatched values, and produces a formatted multi-tab XLSX working document ready for upload.

The tool is distributed as a single self-contained HTML file requiring no installation, no server, and no authentication. All data processing runs client-side — no inspection data is transmitted externally.

Problem Statement

Background

the OEM wind farm asset owners engage both the organization and third-party inspector the Source Platform for blade inspections. When third-party-sourced data needs to be ingested into the Internal Platform and submitted to the Output Platform, it must pass through two conversion layers and conform to the the Internal Platform upload specification.

Problems Identified

• Manual pre-upload checking was performed in spreadsheets with no standardized process, leading to inconsistent results and occasional failed uploads.
• Field value conversion across three nomenclature systems was performed manually using a reference spreadsheet, requiring significant coordinator time per dataset.
• Unrecognized field values had no structured resolution workflow — they were either missed or required escalation to Engineering via email.
• Multiple the source inspection platform export formats exist across different client datasets, causing conversion failures when the wrong template was applied.

Impact: Each failed upload or conversion error requires manual rework estimated at 30–90 minutes per dataset.

Goals & Success Metrics

Users & Personas

Data Coordinator (Primary User)

Receives raw the source inspection platform exports from clients and prepares them for upload to the Internal Platform. Non-technical. Needs clear pass/fail feedback without reading code or formulas.

Engineering / Data Lead (Secondary User)

Owns the conversion mapping tables and is responsible for extending them when new damage types or component combinations appear. Comfortable with spreadsheets. Needs to update the Conversions tab without breaking the output.

Operations Manager (Stakeholder)

Needs confidence that data being uploaded to the Internal Platform and onward to the Output Platform is accurate and complete. Reviews compliance scores and flags for escalation.

Scope

In Scope — v2.1

• File ingestion: CSV and XLSX from the source inspection platform
• Column-level validation: presence and naming of all required and conditional fields
• Row-level validation: field format rules (date, severity, Yes/No, blade side, numerics, coordinate pairs)
• Four-tier status system: Error, Manual Review, Check Internally, Warning
• Conversion engine: the source inspection platform → the Internal Platform → the Output Platform
• Three converted field groups: Element/Component, Anomaly Type, Blade Side
• Human-in-the-loop Manual Review resolution with dropdown selectors
• Dataset summary: anomaly count, unique turbines, site breakdown
• Export: Validation Report CSV + Converted XLSX (Damages Report + Conversions tabs)
• Multi-format support: Dataset A (Component + Material) and Dataset B (Component + Element) structures

Out of Scope — v2.1

• Cross-field conditional validation (e.g. BladeChamber required when Damage Location = Internal)
• Duplicate anomaly ID detection
• Direct upload to either platform from the tool
• User authentication or access control
• Audit logging of validation runs (deferred — requires Apps Script or API access)
• Persistent storage of resolved manual review mappings across sessions
• Automated extension of VLOOKUP ranges when Engineering adds rows to Conversions tab

---

Functional Requirements

FR-01 File Ingestion

FR-02 Column Normalisation

FR-03 Column-Level Validation

FR-04 Row-Level Validation

FR-05 Conversion Engine

FR-06 Status System

FR-07 Manual Review Resolution

FR-08 Results Dashboard

FR-09 Exports

---

Non-Functional Requirements

---

Conversion Mapping Summary

Element / Component

Source: Component + Material column (falls back to Component + Element if Material absent)

Derivation: IF(LEN(Material)>0, Component & " - " & Material, IF(LEN(Element)>0, Component & " - " & Element, Component))

Output: Input Component → the organization Element → the OEM Element

Anomaly Type

Source: Type + Subtype column (falls back to Anomaly Type + Subtype if Type absent)

Derivation: IF(LEN(Subtype)>0, Type & " - " & Subtype, Type)

Output: Input Damage Type → the organization Anomaly Type → the OEM Anomaly Type

Blade Side

Source: Blade Side column (direct lookup — no concatenation)

Output: Blade Side → the organization Blade Side → the OEM Blade Side

---

Supported Dataset Formats

---

Assumptions & Constraints

Assumptions

• All source files are the source inspection platform exports. Tool is not designed for other inspection platform formats.
• The first sheet of any XLSX file contains the inspection data.
• Column names are consistent within a given client's export format.
• Engineering is responsible for maintaining and extending the Conversions tab.
• the Internal Platform upload specification does not change between tool versions without a corresponding tool update.

Constraints

• No server infrastructure available — tool must run entirely client-side.
• Google Apps Script deployment is restricted by company IT policy for user-facing web apps. Distribution via shared Google Drive is the approved method.
• SheetJS is the only permitted third-party dependency.
• VLOOKUP row ranges in exported XLSX are calculated at export time. Engineering adding rows beyond the current range requires manual formula updates.

---

Future Considerations

---

Sign-off

---

Anomaly Upload Validator · the organization · Internal Use Only · May 2026