Filtering Your Relyence Analysis Data Views

As the amount of data in your Relyence Analyses grows, it becomes helpful to filter your data views. Filtering your views enables you to pare down the amount of information displayed in your Tables at one time. This allows you to work more efficiently by not requiring scrolling through data or reading a lot of extraneous information not critical to the task at hand.

Using Relyence Approvals and Notifications

Relyence FRACAS offers two unique and fully customizable capabilities to enable you to control and monitor your corrective action activities: Approvals and Notifications. You can optionally use either or both of these features, and set them up to meet your specific requirements. Used in conjunction with one another, they offer a powerful way to enhance your FRACAS process for your team.

Managing User Roles and Permissions in Relyence

Relyence enables you to effectively manage your team members and their associated permission-based roles through the Manage Users and Groups function. You can add team members, define your Relyence groups, assign team members to the appropriate groups, and control team member access to your Relyence modules, or to specific functions within those modules. The level of granularity is completely customizable, and also easily modifiable – so as needs change, your team member roles can adapt accordingly.

Is it CAPA or is it FRACAS?

What’s in a name? Or, more appropriately, what’s in an acronym? In the corrective action and quality management realm a host of acronyms abound: CAPA, FRACAS, CAR, PAR, FRB, NCR, SCAR, CPAR, RCA, IFR, DRACAS, PRACA, PRACAS, CI, QMS. To makes sense of this alphabet soup, take a look at our breakdown, along with a deeper dive into two often seen: CAPA (Corrective and Preventive Action or sometimes Corrective Action/Preventive Action) and FRACAS (Failure Reporting, Analysis, and Corrective Action System).

3 Important C's of FMEAs

FMEAs, or Failure Mode and Effects Analyses, play a vital role in today’s quality-centric organizations. FMEA goals align directly with the goals of quality control (QC) and continuous improvement (CI) objectives. In some cases, FMEAs are a required component of compliance standards. Even if not required for compliance reasons, oftentimes suppliers are required to perform and submit completed FMEAs as part of contractual requirements. In many cases, organizations adopt FMEAs as part of their own internal procedures in order to meet and improve quality objectives. Whether you are new to FMEAs, or are looking to improve your current analyses, it is helpful to consider three important elements: controls, continuous improvement, and collaboration.

All new Relyence 2016 Release 2!

Relyence Corporation has just released the latest version of the Relyence Quality and Reliability platform. Offered as either a cloud-based or on-premise solution, Relyence incorporates the latest in technology with the best in R&M analytics for a comprehensive suite to meet and improve corporate quality objectives.

The Relyence suite is comprised of FMEA (Failure Mode and Effects Analysis), CAPA/FRACAS (Corrective and Preventive Action/Failure Reporting, Analysis, and Corrective Action System), Fault Tree Analysis, and Reliability Prediction modules.

Relyence 2016 Release 2 introduces a host of new powerful features and capabilities to the Relyence suite.