What is XO?
So what was XO?
XO stands for eXtensible Objects. As a .NET software engineer and architect I always had a keen interest in business model frameworks. The XO framework was a design paradigm for creating business objects and handling business rules such as data validation and integrity.
Primarily focused towards asset management, the XO framework allowed data to be pulled from a variety of sources into a cohesive whole. This process incorporated data validation and integrity rules to ensure data conformance, or at least for the business to be aware of how much data was correct or incorrect. This scenario is especially apt when data it’s sourced from a 3rd party.
Once data is compiled from disparate data sources it can be analysed and reported on.
XO to eSensible
eSensible is now the official successor of XO, predominantly focused at the huge volumes of data involved in Oil & Gas data and information management, plant design, engineering, construction, procurement, and operations. The eSensible suite of small applications offer a simple yet powerful toolset in managing disparate data and documents from a variety of sources, collating that data, filtering valid and invalid data (data quality), and providing simple reports that greatly ease managing data on a corporate scale.
The current eSensible toolset comprises of DataGate, essentially an ETL tool with Class Library/Business Model Validation, and DataHarvester, a regular expression “Find in Files” tool aimed at extracting any pattern (such as an Engineering Tag/Asset number) from a document repository.