In previous versions of the report, only the Hazard name was displayed. However, a challenge arose when multiple bowties shared the same Hazard name but had different Top Events. This made it difficult for users to differentiate between them.
To address this issue, we've introduced an enhancement that adds the Hazard Code to the Top Event Name display in the header of both Global and Local reports. This enhancement streamlines user experience by allowing easy identification of these instances without the need to navigate to the details page.
In response to increasing demands from our clients to enhance the sharing and integration of observation and incident data with external systems, we are excited to introduce the Observations API in this release. This new API empowers you to effortlessly exchange essential observation details, further streamlining your incident management workflows and fostering improved data quality and analysis.
The Observations API provides a convenient GET method to retrieve observation details, enabling you to share crucial information with external systems. This feature caters to a range of use cases, from basic observation information to advanced observation data including attachments and follow-ups. By incorporating this API into your applications, we aim to enhance your operational efficiency and solidify our presence in your application ecosystem.
The Observations API is divided into two distinct types of endpoints to cater to varying requirements:
This endpoint facilitates the retrieval of comprehensive observation details, including:
Additionally, you can employ filters based on Observation's Status name, Question ID, and Answer to refine their data extraction.
Through this endpoint, you can retrieve in-depth observation insights, encompassing:
With the Observations API, you can:
We are excited to announce a significant development in response to the numerous requests and growing demand from our valued customers and prospects. We are working diligently on an integration between Enablon IMS (Incident Management System) and INXP (IncidentXP). This integration is set to take both solutions to new heights, offering an unprecedented level of efficiency, data integrity, and user experience.
With the convergence of Enablon IMS and IncidentXP, we are responding directly to industry needs and user feedback: learning from incidents. Often, companies fail to learn from incidents because they don’t identify the root causes and therefore, are not addressing them. By combining Enablon IMS, expert solution for reporting incidents, and IncidentXP, expert solution for root cause analysis, we aim at providing a very comprehensive solution for fighting incidents root causes.
Our Minimum Viable Product (MVP) integration is designed to meet your immediate needs and provide a foundation for a richer and more integrated experience in the future. It a seamless workflow that spans from incident registration in Enablon IMS through to in-depth analysis within IncidentXP, and ultimately, back to the incident registry, with all pertinent data intact. The following features highlight the core components of this integration:
We are committed to enhancing your incident management and root cause analysis processes, and this integration marks a pivotal step forward in achieving that goal. By leveraging the strengths of both Enablon IMS and IncidentXP, we're fostering a more comprehensive and cohesive experience that empowers your teams to navigate incidents and their analyses with unparalleled efficiency and accuracy.
If you are on BowTieXP Enterprise v11.1 or higher, you don't require to insert a new activation code when updating the software. If you are planning your upgrade with a v11.0 or lower version, please reach out to [email protected] to get a version 12.1 code.
In case your BowTieXP Enterprise is hosted in the Enablon Cloud, reach out to your main contact to get more information and plan the upgrade accordingly.