We're committed to providing you with the latest in Obzervr software updates, what's going on in the industry, and insights from our team.
At Obzervr we have leveraged our years of software engineering experience to create a platform that fits perfectly between a rigid and complex Enterprise system (ERP) on one end of the spectrum and an infinitely custom software solution on the other.
As with all software design, the art is in the ability to balance the needs of flexibility, maintainability and simplicity. This balance cannot be found in a textbook and cannot be done perfectly the first time. This is achieved over years of evolution and trial and error.
We focus more on the events being generated during field activities and less on the complex set of entities and their relationships. An event is any action taken by the field team, or office, that changes the status quo. This is different to the approach of ERP systems, where the core focus is on a complex entity model and providing a User Interface (UI) to manage and manipulate it.
We achieve this by considering the core aspects of fieldwork and the data components that are shared by all fieldwork, regardless of the specific task being undertaken.
Obzervr understands that all work is concerned with the the core concepts of Work done by People at Places on Things. We call this the Fieldwork Transactional data model. This data model forms the core of Obzervr’s platform. While work is planned, executed and completed, events across these core concepts combine to form a current state for any level of complex work.
The work model itself is made up of a more complex set of concepts including Tasks, Measures, Attributes, and many others. The events within this ‘Work’ model form a complex graph of work activity, extremely flexible yet simple to implement and simple to maintain.
Our event-driven structure is what allows many users, across devices to work on the same complex assignment and have all activity merged centrally without conflict. This capability is not found in any mobility platforms we have reviewed.
The first of these models is the Fieldwork Operational or Transactional Model, the second is the Analytics model. The Analytics model de-normalises and reduces the operational model to better suite reporting, aggregation and visualisation.
This model does not simply apply traditional multidimensional data warehousing patterns such as star and snowflake, but includes reducing relationships, pivoting attributes, removing complex keys and presenting an industry, and sometimes even customer specific, model that supports natural language querying and reporting in various visualisation and query tools.
Using these core programming concepts allows the Obzervr solution to run offline and online, with 100 or 10,000 users, as a stable secure mobile app and integrated analytics. Email us today on [email protected] to find out how to take advantage of this pioneering technology.
To receive the latest news and updates from Obzervr about our software, industry insights, and what we're working on, subscribe now.