Causelink Incident Timeline Beta Release

  • warning: Parameter 2 to securepages_link_alter() expected to be a reference, value given in /var/www/sologic.com/www/includes/common.inc on line 2892.
  • warning: Parameter 2 to securepages_link_alter() expected to be a reference, value given in /var/www/sologic.com/www/includes/common.inc on line 2892.
  • strict warning: Non-static method view::load() should not be called statically in /var/www/sologic.com/www/sites/all/modules/views/views.module on line 879.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /var/www/sologic.com/www/sites/all/modules/views/handlers/views_handler_argument.inc on line 745.
  • strict warning: Non-static method views_many_to_one_helper::option_definition() should not be called statically, assuming $this from incompatible context in /var/www/sologic.com/www/sites/all/modules/views/handlers/views_handler_argument_many_to_one.inc on line 36.
  • strict warning: Non-static method views_many_to_one_helper::option_definition() should not be called statically, assuming $this from incompatible context in /var/www/sologic.com/www/sites/all/modules/views/handlers/views_handler_argument_many_to_one.inc on line 36.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /var/www/sologic.com/www/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /var/www/sologic.com/www/sites/all/modules/views/handlers/views_handler_filter.inc on line 589.
  • strict warning: Declaration of views_handler_filter_node_status::operator_form() should be compatible with views_handler_filter::operator_form(&$form, &$form_state) in /var/www/sologic.com/www/sites/all/modules/views/modules/node/views_handler_filter_node_status.inc on line 14.
  • strict warning: Non-static method view::load() should not be called statically in /var/www/sologic.com/www/sites/all/modules/views/views.module on line 879.
  • strict warning: Non-static method views_many_to_one_helper::option_definition() should not be called statically, assuming $this from incompatible context in /var/www/sologic.com/www/sites/all/modules/views/handlers/views_handler_argument_many_to_one.inc on line 36.
  • strict warning: Non-static method views_many_to_one_helper::option_definition() should not be called statically, assuming $this from incompatible context in /var/www/sologic.com/www/sites/all/modules/views/handlers/views_handler_argument_many_to_one.inc on line 36.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /var/www/sologic.com/www/sites/all/modules/views/handlers/views_handler_filter_boolean_operator.inc on line 149.
Jon Boisoneau, VP Products

September 13, 2016

I’ve been involved in Root Cause Analysis software development for many of the past 15 years.  A big part of my job at Sologic, and one of my favorite parts, is to talk with end users and listen to their requests for new features.  Over the years, I’ve been asked to incorporate an incident timeline into Causelink software.  This is partly due to the fact that an incident timeline is discussed during RCA classes as a way to facilitate cause and effect charting.  Creating a linear timeline is a great first step in defining the multiple causes of a problem.  I’ve found that many of our users currently create a timeline in another program and add it into Causelink as an attachment.  After hearing this feedback, it was obvious that this was a feature we should support.  Therefore, I’m pleased to announce the release of Causelink Incident Timeline Beta!  

Incident Timeline within Causelink RCA Software

The Incident Timeline Beta is included in our standard Causelink Enterprise/SaaS package and that’s how we intend to deliver the production version.  This new, browser-based feature is a result of focus groups that were held with customers and RCA practitioners in 2015.  During those sessions we learned that not only should the timeline be interactive and support the editing of details for each event, but there should also be a way to add these events as causes on the cause and effect chart.  We also learned how the timeline fits into user workflow during an incident investigation, knowledge which helped in making decisions about navigation and user interaction.

These focus group findings were incorporated into the Incident Timeline Beta.  Released to a select group of Beta testers on September 8th and 9th, we are already getting great feedback about how the timeline should be displayed on the screen, printed to PDF, and how closely linked events should be with the causes on the chart.  Beta testers will have access to the system for 10 days, after which we will consolidate their comments and plan for the next iteration.  

We anticipate this major new feature will benefit our user base by making it easier to create a timeline, storing the data in one central location, and providing a great way to share Incident findings with their team.  Look for the Beta 2 release in November 2016 and the production release within Causelink Enterprise/SaaS in early 2017.  

If you would like a demonstration of the Incident Timeline features, sign up here.