Feature Update

Enhanced Study Validation: Ensuring Data Integrity Before Analysis

January 2, 2026

Data quality is the foundation of any reliable risk assessment. Before running complex calculations that model dropped object trajectories, impact probabilities, and potential consequences, users need confidence that their study data is complete and properly formatted. Our enhanced study validation functionality provides exactly that assurance through a comprehensive, centralized validation system.

A Multi-Layered Validation Approach

The enhanced validation system operates across four distinct validation layers, each designed to catch different categories of data issues:

  • Mandatory Field Checks — Ensures required fields contain values before analysis can proceed. Empty crane names, missing object masses, or undefined target diameters are flagged immediately.
  • Data Type Validation — Verifies that values match their expected formats. UUIDs follow the proper 8-4-4-4-12 hexadecimal pattern, colors are valid hex codes, and numeric fields contain actual numbers.
  • Range Validation — Confirms that numeric values fall within acceptable bounds. Negative masses, impossibly small pipe diameters, or out-of-range frequencies are caught before they can corrupt calculations.
  • Foreign Key Verification — Checks that referenced records actually exist in the database. If a lift references a crane that was deleted, validation catches this orphaned relationship.

Centralized Configuration

Rather than scattering validation rules throughout the codebase, the system uses a centralized configuration file that serves as the single source of truth for all field definitions. This approach offers several advantages:

  • Form generation and validation use identical rules, eliminating inconsistencies
  • Adding or modifying validation criteria requires changes in only one location
  • Support for context-specific overrides when certain situations require different limits
  • Clear documentation of all field requirements in one readable structure

Flexible Validation Scope

The validation system supports multiple usage modes to accommodate different scenarios:

  • Full Study Validation — Validates all configured tables before running comprehensive risk analysis
  • Single Table Validation — Checks only specific tables, useful when working with particular data categories
  • Single Record Validation — Validates individual records during data entry, providing immediate feedback

Users can also select which validation types to run, allowing quick mandatory-only checks during data entry while performing comprehensive validation before final analysis runs.

Clear Error Reporting

When validation issues are discovered, users receive clear, actionable feedback. The error display identifies which tables contain problems and provides direct links to open those tables for correction. Rather than cryptic error codes or technical database messages, users see a professionally formatted summary with specific guidance on how to resolve the issues.

"Open each table and complete the required fields before running the analysis again."

This approach transforms validation from a technical hurdle into a helpful guide, ensuring users can quickly identify and resolve data quality issues.

Security Considerations

The validation system includes built-in security measures to prevent injection attacks. All table and column names are verified against a strict alphanumeric pattern before use in queries. Foreign key validation uses parameterized queries throughout, and the system respects study-level data isolation to ensure users can only validate their own data.

Conclusion

Enhanced study validation represents a significant improvement in data quality assurance for offshore risk assessment. By catching data issues before they can affect calculation results, the system helps ensure that risk assessments are based on complete, properly formatted, and internally consistent data. This foundation of data integrity supports more reliable risk analysis and better-informed decision making for offshore operations.

The centralized configuration approach also simplifies maintenance and ensures consistency between data entry forms and validation logic, reducing the potential for discrepancies that could otherwise undermine user confidence in the system.

Share this Post

Related posts