OpenWellsEDMReporting
Start with the specific environment
OpenWells deployments differ by product version, EDM configuration, permissions and local workflows. Before designing an extraction, confirm the authorised source, required well and operational entities and available vendor-supported interfaces.
Identify the intended reporting grain
A well summary, a job-level report and a daily operational dataset each require different record relationships. Mixing child records without defining the reporting grain can multiply rows and distort measures.
Build a traceable extract
- Document the source entities and join conditions.
- Confirm operational date and time fields.
- Distinguish well, wellbore, job and daily-report identifiers as relevant.
- Validate totals and classifications against known application reports.
- Review authorisation, security and downstream refresh requirements.
Connect to analytics carefully
Once the extract is tested, datasets can be structured for BI or warehouse workloads. The target model should preserve operational meaning, clarify definitions and avoid hidden transformations.
Specific EDM schema objects and integration interfaces must be verified for the customer’s licensed environment. This article deliberately avoids assuming a universal schema.