FavoWeb™ (Selected by LOCKHEED MARTIN for the JSF (F35) Project)

▒  1 day FREE Seminar on the World Leading FRACAS Tool FavoWeb on Friday 14 September  2007

Further to the recent Successful Seminar we have decided to run this FREE Seminar again!  We wish to Invite you to our Head Office in Fareham to attend the above FREE Seminar on Friday 14 September 2007.  This is a GREAT opportunity for you to  learn more about the POWER of FavoWeb and find out WHY more and more Companies are deciding to BENEFIT from this tool! 

You will also have a chance to have an in depth Demonstration of the Tool and meet up with some of the Users and have all your questions answered by the Developers of this Powerful Tool.  You cannot afford to miss this opportunity if your company is considering the introduction of a FRACAS Tool.  Please contact us TODAY to book your place as places are LIMITED.  Thank you in advance and look forward to hearing from you!

Failure Reporting Analysis & Corrective Action System

**********See also ASENT FRACAS for a SQL based alternative**********
Main Features                   

    Collect Failures
    FRBs and Corrective Actions
    User Roles
    Email Notification
    Workflow Control
    Report Generation
    Import/Export Data

Collect Failures                                                                                                    

FavoWeb™ allows construction of user defined forms for collecting failure data.

These forms include the latest methods and controls, such as combo-boxes, links, file attachments, logical trees and more, that can eventually reduce the human factor error in feeding data to a minimum.

In addition, FavoWeb™ can network to external systems in the organization for required input data such as PDM, ERP, human resources and more (compliance with most common databases such as Oracle, AS400, DB2 etc.) 

 FRBs and Corrective Actions                                                                          

FavoWeb™ supports failure review board (FRB) and corrective action diary management, including distribution to board members and action items (AI). These managerial tools are used to diagnose epidemics and conduct preventive maintenance to eliminate problems in the future.

 User Roles                                                                                                           

FavoWeb™ differentiates the users and divides them into several customizable groups.

Each group can be given different permissions and roles.
For example:
INITIATOR user role authorized only to initiate failures and input the failures symptoms.
ANALYST user role authorized only to add analysis documentation.
REVIEWER user role authorized approve or reject the analysis or corrective actions taken.
ADMINISTRATOR user role authorized to make administrative modifications and customization to the application.

 Email Notification                                                                                                

Each action or state in FavoWeb™, can be defined to trigger an Email notification message, that can be sent to any user or group of users.

The Email message is fully customizable by the system administrator.

This feature allows managers to be notified of problems that have yet to be resolved and escalate problem to the attention of repair-experts.

Workflow Control                                                                                                 

The FavoWeb™ 's concept includes reporting failure information on a product from different stages of its life cycle.

Also each failure can be cut down to several input forms theoretically reported by different people.

A first level failure report can be followed by a second level report etc.

All these tasks and responsibilities are independent and need to be inside a closed-loop mechanism controlling work inside the organization.

This mechanism is called Workflow.
From the user point of view, the workflow mechanism is opened by choice as a tasks window.

This window includes all lines of information needed for the user group's work.

Every task has a status - open in the beginning, then in-work after opening the task, then closed at the end.

The change of the status is controlled by the user, where closing a task must include a user and password.

Opening a task (clicking on the line), automatically opens the relevant window (failure window for instance) and changes the status of the task to in-work. A log file records all task activities for later research and inquiries.

Report Generation                                                                                               

FavoWeb™ has a powerful tool that allows the user to construct various reports, save them to a template (if needed), view them in the browser or export them to an Excel worksheet for further analysis.

The report generator has built in reports such as failure distribution and failure list, and special reports like MTBF, MTTR and Weibull distribution can be easily applied upon request.

Import/Export Data                                                                                              

FavoWeb™s flexibility allows users to import external data to the application using a simple Excel spreadsheet file.

These data can be used in the application to define a product, a clock or a batch insertion of failure data.

In addition, all the data collected in the system database can be exported to an Excel spreadsheet.

One of the most important characteristics FavoWeb™ has is its Definition Flexibility. No matter what industry the organization belongs to, the application can be customized to fit the requirements. This is done with the help of an administration utility. This utility helps the company's administrator to define each functional module (Failure reporting for instance), to include different input forms, user-defined fields for each input form, design and style output reports and even select interface language.

The FavoWeb™ system is a logistic application allowing collection of failure information and other types of data like corrective action and testing from processes related to different activities of a product in an organization. The application supports activities in different Life Cycle Phases like production, development and maintenance.
FavoWeb™ has a highly level of adaptability and flexibility. The application's input screens, functional modules and user reports can be customized and tailored to the organization's definitions. The adaptation process takes place during the installation time in cooperation with the System Administrator and the organization professionals. The application is operating on the organizational intranet platform and can be ran through any workstation connected to the network and having a Microsoft Explorer 5 and up installed. The application is Oracle database based.
All processes are monitored and controlled through an online workflow mechanism giving each working level control over its tasks and responsibilities.

FavoWeb™ 's reliable information is based on the end-user motivation to report every deficiency and system failure. This is done through a user-friendly interface and by tailoring input forms to the specific user needs. Another concept is to make reporting job easy. Connection to PDA's (WindowsCE etc.), using barcodes and other hand terminals is the way we make-work easy.
Also we've issued a US patent on failure reporting through voice recognition, and we'll supply this version in the next year.

The FavoWeb™ 's concept includes reporting failure information on a product from different stages of its life cycle. Also each failure can be cut down to several input forms theoretically reported by different people. A first level failure report can be followed by a second level report etc. All these tasks and responsibilities are independent and need to be inside a closed-loop mechanism controlling work inside the organization. This mechanism is called Workflow.
From the user point of view, the workflow mechanism is opened by choice as a tasks window. This window includes all lines of information needed for the user group's work. Every task has a status - open in the beginning, then in-work after opening the task, then closed at the end. The change of the status is controlled by the user, where closing a task must include a user and password. Opening a task (clicking on the line), automatically opens the relevant window (failure window for instance) and changes the status of the task to in-work. A log file records all task activities for later research and inquiries.