Server Data Store

Executive Summary

This section gives a brief outline of the component.

Services Provided

• Services provided to the Maintenance Engineering Support System:
  • List of newly detected errors: This service should gather the information on error reports that are not yet shown in the Maintenance Engineering Support System, and it would send this information to be used by this component.
  • Updated information regarding existing errors: This service would send information changes regarding errors already existing in the Maintenance Engineering Support System, like new identified causes, or similar errors.

Services Needed

• From Event Correlation System: Event Correlation will send information about errors (error detection, symptoms, cause identification, ...) to the Server Data Store when the Event Correlation System detects it. After that, this information will be available for other components to be requested.
  • New ErrorReport: detected error. Associated information: Context Events that provided the information to detect the error. Additionally, it will share the mechanism used to detect the error, in other words, if it has been detected based on information in the knowledge base (detection rules) or if it has been detected through pattern recognition.
  • Give a list of possible causes associated to an existing error report
  • Given an existing error report, provide information about a possible solution
  • Given an existing error report, and a concrete symptom to be mitigated (if the error cannot be solved through the elimination of the cause), provide information about a possible workaround
  • Given an existing error report, provide a small list of similar problems (data aggregation)

Open Questions and Doubts

• Are ontologies efficient enough (speed, space) or do we need a triple store?

Shared Data Structures

• ErrorReport, Issue, Cause, Symptom, Solution, Workaround

Component-specific Errors

see [Component Specific Error Types]

Limitations

see [Component Limitations]