웹 기반 프락카스

Incident (failure) reporting

In XFRACAS, each “incident” deals with a single instance of a failure, suggestion or other event so you can track how it was addressed and capture sufficient detail for reliability and related analyses:

• Fully describe the incident and link or attach relevant files.
• Identify the responsible part(s) and notify owners.
• Record the operating time/usage when the failure occurred.
• Assign responsibility for specific actions and track their completion.

Tools for capturing findings from failure analyses on returned parts

If parts are removed/replaced and returned for more in-depth failure analysis, XFRACAS can capture additional details, such as the RMA number, sales order number or work order number, findings from the visual inspection and detailed analysis, fault history or sensor data, or other test results.

Tools for tracking the completion of assigned actions

Throughout XFRACAS, you can assign actions to system users and track their progress and completion.

• Descriptions of the assignment with links or relevant attachments
• Automated e-mail notifications for the person responsible and other users who need to monitor or approve the actions taken
• Reports and charts to track progress and completion

Root cause analysis and team-based problem resolution

In XFRACAS, a “problem” is a larger issue that may require a team-based approach to understand the root cause and implement improvements. Designed to prevent similar issues from recurring, problems allow you to.

• Use any method from 4 to 8 steps (8 Disciplines, Six Sigma DMAIC, DCOV, CAPA)
• Fully describe the problem and link or attach relevant files
• Link to all related incident reports
• Capture findings from root cause analysis
• Assign responsibility for specific actions and track their completion
• Track review and sign-off by a Failure Review Board (FRB)

Charts, dashboards and custom XSLT

XFRACAS provides built-in tools to create graphical charts — bar, pie, area, step, scatter and line — for any set of results.

• Highly customizable
• Full drill-down capability
• Configurable dashboards
  
  

For even more customized output, you can:

• Output results to XML, which can be used as a web-based data source in a variety of third-party reporting tools, such as Microsoft Excel (via the Get External Data > From Web feature, for example).
• Define your own custom XSLT style sheets (Extensible Stylesheet Language Transformations).

Data for reliability analysis

The incident reporting process in XFRACAS can produce clean, usable data for reliability analysis in Weibull++. If data entry is based on fully serialized systems, you can extract complete time-to-failure and suspension data by system, subsystem and component.