How Everest is Organized
Main Menu
The large menu buttons will display the current numeric total of those open items for the logged in user unless there are none.
Accounts
Accounts are organized into Account Types, a user defined list. For example:
Account Types are defined in Setup | Drop Down Lists | Account Types.
Internal Areas
A user defined list which can be based on departments, production lines, manufacturing facilities, branch offices or any organizational structure. Contacts for internal areas can include any staff members within each area, but Contacts for internal areas do not login to Everest. Separate from Contacts, the list of users is maintained in Setup | User Information | Users.
Add and edit Internal Areas in View | Internal Area List.
Accounts and Internal Areas consist of a Notebook organized with identical Tabs. The full configuration for Accounts offers two additional Account Notebook Tabs for Categories and Comments. The two required Tabs are Concerns and Contacts, shown highlighted in the default example list (below), all other Tabs are optional.
Tabs are enabled/disabled based on User Group settings defined in Setup | User Information | User Groups .
Tab Names (except for Contacts) may be customized in Configuration | Button and Tab Names. The Tab name for the Contact Tab will adopt the Data Name for 'Contact' in Configuration | Data Names.
| Account Notebook |
| Concerns | Contacts | Activities | Categories* | Comments | Documents | Equipment* |
| Internal Area Notebook |
| Concerns | Contacts | Activities | Documents | Equipment* |
Concerns
Concerns are also organized with Notebook Tabs. The Concern Tab is the only required Tab, shown highlighted in the default example list (below), all other Tabs are optional.
Tabs are enabled/disabled based on User Group settings defined in Adminstration | User Information | User Groups.
Tab Names (except for Concerns) may be customized in Configuration | Button and Tab Names. The Tab name for the Concern Tab will adopt the Data Name for 'Concern' in Configuration | Data Names.
| Concern Notebook |
| Concern | Reference* | Product* | Returns | Repairs* | Actions | Attachments |
Everest can be highly customized through Configure Options, User Groups and other settings. Each User belongs to a User Group with a unique login. User Groups define Access Privileges including the visibility of the available Menu Buttons and Notebook Tabs.
Concern content can also be highly tailored for specific organizational requirements. User defined fields, Action Types, Concern Types and Cause Categories are important ways information is organized. Notebook Tabs can be re-labeled to match local terminology, often defining a purpose very different from the default settings. Many of the standard data names can also be re-labeled to match local terminology.
Concerns are classified with a three-tiered list called Concern Type + Category + Reason that is user defined. Product Defect Classifications, Priority and Cause Categories are also user defined lists. Charts and Reports provide selection criteria based on these classifications. Each Concern Category can have unique default Due Days, a default Owner, and Standard Actions which will be automatically generated to create the expected or recommended workflow. Product Defect Classifications can be defined in a one, two or three level hierarchy with a related Defect Findings selection list optional. Multiple Defect Classifications may be associated with each Product. A Chart drill down feature provides a detailed visual analysis of Defects in relation to Products or Product Groups. Terminology may be customized to replace the default term, 'defect' in Configuration | Data Names.
A Resolution Tab is optional for the Concern View. When enabled, the Resolution text box is located on the Resolution Tab instead of the Concern Tab, along with two additional text boxes; Findings and Root Cause. The data names for the text boxes on the Resolution Tab can be relabeled in Configuration | Data Names. This Concern View configuration is not related to the Corrective Action in Actions but it does use similar terminology.
Actions
Actions drive the resolution process associated with each Concern. Actions can be delegated by assigning them to a User who is eligible to be an Action Owner. Investigations can be documented, email messages can be sent and letters can be printed. The list of available Action Types is user defined to support multiple workflows with separate steps or tasks. Users add a new Actions into the Concern by choosing them from a selection list as needed.
Action Reply Type formats:
An Action Report can be viewed, printed or emailed. The Response format is used for Action Types that expect a Reply. Some Action Types, such as a general product alert or letter, may not require any Reply.
See also