Printed Documentation - Honeywell
eCATS User Guide
Honeywell Confidential & Proprietary
This work contains valuable, confidential, and proprietary information. Disclosure, use or reproduction outside of Honeywell Inc. is prohibited except as authorized in writing. This unpublished work is protected by the laws of the United States and other countries.
Notices and Trademarks
Copyright ©2010 by Honeywell International Inc.
While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its Customers.
In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The information and specifications in this document are subject to change without notice.
Honeywell is the registered trademarks of Honeywell International Inc.
Other brand or product names are trademarks of their respective owners.
Honeywell International
Aerospace
111 S. 34th Street
Phoenix, AZ 85034
1-602-231-1324
Table Of Contents
Introduction 1
eCATS - Electronic Corrective Action Tracking System Overview 1
System Features 1
Home 3
To send Feedback about the site 3
Registration 3
Honeywell ID Registration 3
ECATS User Profile Registration 3
Profile Request Process for Honeywell Suppliers 4
Profile Request Process for Customers 5
Profile Request Process for Honeywell Employees 6
Login 7
Logging on to eCATS 7
Changing or Forgot Password 7
Home page 9
Initiate CAR 10
Step 1: Initiate CAR – Select CAR Type 10
Step 2: Assign People 10
Step 3: Product Process 16
Step 4: Finding Event 18
Team 20
Response 22
Approval 26
Follow-up 27
Effectiveness 29
History 31
Comment 32
Locate CAR 32
Initiating a CAR 33
Draft CARS 34
Locating a CAR 34
Responding to a CAR 35
Extension of Due Date 38
Creating a CAR with a new Dash 39
Attaching Documents 40
Waiting Owner Implementation, Following up and Closing a CAR 41
To Schedule a Follow-up Review 41
Accepted by the Follow-up Reviewer 41
Rejected by the Follow-up Reviewer 42
Advanced Search 42
Select Saved Reports 43
Quick Filter 44
Additional Filter 46
Field Selection 48
Reports 50
Generating a Report 53
Quick Filter 57
Report Format Selection 58
PDF Format 58
Drill Down by Month 58
Excel Report 58
HTML Data Extract 59
Administration 60
SBU Maintenance 61
Modify SBU Name 61
Enterprise Maintenance 62
Adding an Enterprise Code 63
Modify Enterprise Name 64
Deleting an Enterprise Code 65
Site Maintenance 66
Adding a New Site ID 67
Modify Site 67
Deactivating a Site ID 69
Adding a New Product Line 70
Deleting a Product Line 71
Adding a New Cell 72
Deleting a Cell 73
Adding a New Department 74
Deleting a Department 74
Customize Code Lists 75
Customize Supplier Lists 77
Supplier 78
Search and view the details of a Supplier 78
Adding a New Supplier 79
Modify Supplier 80
Deleting a Supplier 81
Adding a New Supplier User 82
Modify Supplier User 83
Deleting a Supplier User 84
Manage Internal Users 85
Internal User 87
User Level 87
Role of the User 87
Adding a New User 88
Modify User 90
Deleting a User 92
Inactive a User 92
Move User 93
Reset Password 95
Review Registration 96
Glossary 97
Index 99
Introduction
eCATS - Electronic Corrective Action Tracking System Overview
eCATS was originally developed for Honeywell Aerospace. Due to its ability to interface with Customers, Suppliers, FAA, and External Registrars, it is now widely used by other Honeywell business units.
eCATS is a software application for documenting corrective and preventive action in response to nonconformities. It meets Customer, FAA, and External Registrar quality record requirements and enables standardization of corrective and preventive action processes.
Cause Analysis and Mistake Proofing (CAMP) workshop or on-line training is recommended to understand the process of the eCATS application.
System Features
1. eCATS is a web-based application, centrally maintained, and updated in a single server.
2. Internet Explorer 5.0 or later at a resolution of 1024 x 768 pixels is required to run eCATS. eCATS does not require any special software. It is easily accessed by any computer with an Internet access and an Internet browser.
3. Secure Socket Layer (SSL) for data encryption keeps the information safe. Each user has a login ID and limited access to the application.
4. The system complies with Honeywell’s export control requirements, giving each CAR the capability to be individually set as export controlled. The system security references the nationality of the issuing site (not that of the lead or requestor), CARs that are marked as export controlled will only be accessible to users named on the CAR or that have the same nationality as that listed for the issuing site.
5. eCATS is integrated with e-mail and MS Office tools. When an action is required or overdue, an e-mail reminder is automatically sent to the responsible persons.
6. Home page: This section maintains the updated information about each CAR from initiation until closure. It lists all of the CARs that the user is associated with.
▪ Search CARs
▪ Create new CARs
▪ View, Respond, and Approve existing CARs
▪ Schedule Follow-up and Effectiveness reviews
The Search section allows the user to search by site, status, and dates. Advanced Search gives the users additional options.
7. CAR. This section contains:
▪ Draft CARS List
▪ Initiate CAR
▪ Advance search
8. Report: The Report section allows the user to find detailed information across multiple organizations. Report defines fields and filter conditions to create queries that can be viewed online or exported. Reporting runs pre-formatted reports and forms with user specified filter conditions.
[pic]Note
• Each user must exit the CAR by clicking Exit after completing the necessary actions. This allows the next user to proceed with the CAR. If a user does not exit the CAR, the CAR is opened in a read-only mode to other users.
• The user is automatically logged off after a thirty minute period of inactivity. Typing is not considered as an activity. Interaction with the server is required. For example, moving from one page to another is considered activity.
A pop-up message appears. Click OK.
[pic]
• The system prompts the user with a message five minutes before logging you out. Click OK to remain logged in.
[pic]
• The maximum size of each document attached is 6MB.
• The maximum limit of the text field is 4000 characters. Avoid using apostrophes in the text fields.
Home
Login to eCATS through the Home page:
To send Feedback about the site
1. Click the Technical Support link on the left pane of the screen.
2. Enter the subject in Subject.
3. Enter issue or feedback regarding the CAR or site in Feedback.
4. Enter your e-mail ID in From.
5. Click Send Message.
The VeriSign Secure Site image symbolizes that the site is a secure site network utilizing Secure Sockets Layer (SSL) encryption assuring system integrity and protection.
[pic]
The application is best used with the Internet Explorer browser and must be displayed with a resolution of 1024 x 768 pixels.
--------------------------------------------------------------------------------------------
Registration
Suppliers and Customers can register from the Home Page. Registration is a two part process, the first part is the Honeywell ID registration and then the second part is the eCATS user profile registration.
Honeywell ID Registration
For internal Honeywell employees, the Honeywell ID is your EID and the password is your network password (LDAP).
Suppliers and Customers will create a Honeywell ID by clicking on the “Don't have Honeywell ID? Register” link on the sign in page. The Common Web Authentication (CWA) site used to create your Honeywell ID is not part of the eCATS tool. Follow the instruction on the screen or use the help link provided in the CWA for assistance. If the Supplier or Customer has a Honeywell Id for other applications, (Supplier portal, etc.) the same ID will be used here and a new one is not required.
ECATS User Profile Registration
• Honeywell Employees can request the creation of their user profile through their local eCATS Site Administrator.
• Suppliers and Customers can register for an account by clicking on the “New Supplier/Customer users please register here”.
• Send feedback, issues, and requests for clarification to Technical Support by clicking on the Help in the top menu of the home page.
Profile Request Process for Honeywell Suppliers
1. Click the “New Supplier/Customer users please register here”.
2. Click here to Register as Supplier.
3. Enter the information in the fields provided.
|Fields |Description |
|Company (mandatory) |The name of the Supplier's company. |
|Duns # (mandatory) |Dun & Bradstreet number used as the unique ID of the Supplier. If a Supplier does not |
| |have a Duns, use the Honeywell OneSource Supplier ID. (see Supplier scorecard through the|
| |Supplier Portal) |
|First Name (mandatory) |The first name of the user. |
|Last Name (mandatory) |The last name of the user. |
|Title |The title is the designation of the person. |
|Address 1 (mandatory) |The address includes the company name, street address and the building name of the |
| |Supplier. |
|Address 2 |Additional address, as applicable. |
|Address 3 | |
|City (mandatory) |The city where the Supplier resides. |
|State (mandatory) |The state where the Supplier resides. |
| |Select the state from the drop-down [pic] menu. |
|Zip/Postal (mandatory) |The zip or postal code of the area where the Supplier resides. |
|Country (mandatory) |The country where the Supplier resides. |
| |Select the country from the drop-down [pic] menu. |
|Phone (mandatory) |The contact number of the Supplier. |
|Fax |The fax number of the Supplier. |
|Mail Stop |The mail stop is the building mail address of the Supplier. For example, MS22. |
|Email (mandatory) |The e-mail address of the Supplier. |
|Primary Honeywell Site |The site with which the Supplier is conducting business. |
|(mandatory) | |
| |Contact the Supplier Quality representative to get your site code. |
| |Click[pic]. All the site codes are displayed in a new window. |
| |Select the site code by clicking the Site Code hyperlink. |
|Honeywell LDAP |Pre-populated with Honeywell ID |
|Submit |Click Submit to request an eCATS account. |
|Clear |Click Clear, to clear all the fields. |
|Back |Click Back to go to the eCATS Registration screen. |
4. Click Submit to send a request for an account. An e-mail is sent to the administrator of the primary Honeywell site. When the account is approved the login ID is sent in an e-mail to you.
5. You receive an on-screen confirmation message from eCATS.
[pic]
Profile Request Process for Customers
1. Click the “New Supplier/Customer users please register here”.
2. Click here to Register as Customer.
3. Enter the information in the fields provided.
|Fields |Description |
|Company (mandatory) |The name of the Customer's company. |
|First Name (mandatory) |The first name of the user. |
|Last Name (mandatory) |The last name of the user. |
|Title |The title is the designation of the person. |
|Address 1 (mandatory) |The address consists of the company name, street address and the building name of the |
| |Customer. |
|Address 2 |The additional address to specify the accurate location. |
|Address 3 | |
|City (mandatory) |The city where the Customer resides. |
|State (mandatory) |The state where the Customer resides. |
| |Select the state from the drop-down[pic] menu. |
|Zip/Postal (mandatory) |The zip or postal code of the area where the Customer resides. |
|Country (mandatory) |The country where the Customer resides. |
| |Select the country from the drop-down[pic] menu. |
|Phone (mandatory) |The contact number of the Customer. |
|Fax |The fax number of the Customer. |
|Mail Stop |The mail stop is the building mail address of the Customer. For example, MS22. |
|Email (mandatory) |The e-mail address of the Customer. |
|Primary Honeywell Site |The site with which the Customer is conducting business. |
|(mandatory) | |
| |Contact the Quality representative to get your site code. |
| |Click [pic]. All the site codes are displayed in a new window. |
| |Select the site code by clicking the Site Code hyperlink. |
|Honeywell LDAP |Pre-populated with Honeywell ID |
|Submit |Click Submit to request an eCATS account. |
|Clear |Click Clear, to clear all the fields. |
|Back |Click Back, to go to the eCATS Registration screen. |
6. Click Submit to send a request for an account. An e-mail is sent to the administrator of the primary Honeywell site. When the account is approved the login ID is sent in an e-mail to you.
4. You receive an on-screen confirmation message from the application.
[pic]
Profile Request Process for Honeywell Employees
All internal Honeywell users shall request the access through their local eCATS administrator.
OR
1. Click on the “Click here to contact administrator.
2. Enter Request for an account in Subject and give your details in Feedback.
3. Enter your e-mail ID in From.
4. Click Send Message. Your login ID will be sent as an e-mail to you.
[pic]Note
• Read the Honeywell Privacy Policy before clicking Submit.
Login
Logging on to eCATS
1. Enter the eCATS address in your web browser.
[pic]
2. Enter the assigned Honeywell ID and password.
3. Click Sign In. The Select Profile page is displayed, if the login was successful. Select Profile from the drop-down box, click Next. The first page displayed will be the user’s action items.
• [pic]Note: Most users have only one Profile
• Suppliers and Customers use Honeywell ID
For information about Registration for Honeywell ID, see Registration.
• Honeywell Employees will use EID and LDAP password.
Changing or Forgot Password
1. The Honeywell ID password can be changed by clicking on the “Forgot Password?” link on the log in screen and following the prompts.
2. The eCATS profile password is only used to associate an existing eCATS Profile to a new Honeywell ID. Newly created profiles have the association already completed and the password is not needed. If the eCATS profile password needs to be reset, contact an eCATS administrator for assistance.
Home page
Home page
▪ Find a specific Corrective Action Request (CAR) by providing details like CAR ID , Status, or Date Initiated, and clicking the search button
▪ Initiate a CAR by clicking Initiate New CAR.
This screen contains an Action Item table with the list of CARs and their status. The CARs are classified into three types:
• CARs in Approval or Response Phase
• CARs in Implementation Phase
• CARs in Effectiveness or Followup Review Phase
The following table provides a description of the fields for the CAR list on the Home page. The list of CARs being displayed can be changed using Change Display drop down filter.
|Field |Description |
|CAR ID |The unique ID assigned to a CAR that is generated. |
| | |
| |Example:OTH20100002-01 |
| |OTH - the eCATS site code of the site that generated the CAR. |
| |2010 - the year when the CAR is generated. |
| |0002 - the sequence number of the CAR. |
| |-01 - the sequential dash number for related CARs. |
|CAR Status |The status of the CAR. Examples include: Initiation in Progress, Waiting for Owner |
| |Assignment, etc. |
|Person Responsible |The name of the person responsible for the current status on the CAR. |
|CAR Type |Primary CAR types are: Internal, Supplier, and External. There are additional CAR types |
| |for Preventive Action, Supplier RMRA, and Supplier Reversals. |
|Initiation Date |The date when the CAR was initiated by the Lead/Requester. |
|Due Date |Due date assigned for the current stage of the CAR process. |
|Requester |The person who raised the issue for a CAR. |
|Owner |The person assigned by the SPOC or the Lead/Requester to take corrective action. |
|SPOC |A Single Point of Contact has the authority to assign an Owner to a CAR. The SPOC is |
| |also responsible for ensuring that the appropriate Root Cause analysis is followed and |
| |is the initial approver of the CAR response. |
|Lead |The Lead and the Requester are usually the same person. |
| |For example, the Lead is a Production or Quality Engineer. |
[pic]Note
• [pic]Symbol in the CAR ID column indicates that the CAR has attachments.
• The CAR is highlighted in red if the due date has passed. An action must be taken immediately.
• The CAR is highlighted in yellow three days before the due date. It reminds the responsible person to take action before the due date.
Initiate CAR
Step 1: Initiate CAR – Select CAR Type
|Type (mandatory) |The Lead/Requester must select the type of the CAR to be initiated from the drop-down menu. |
| |The Type designates the source type of the corrective action, e.g. Customer, Internal Audit, |
| |Supplier, etc. The selection determines the fields present in Select CAR Type. |
| |The fields on the Assign People page change based on CAR type selection. |
Step 2: Assign People
|Field |Description |
|CAR # |The unique ID assigned to each CAR. The value is NEW by default and a unique number is |
| |assigned as soon as CAR initiation is complete. |
|Status |The status of the CAR may be Initiation in Progress, Waiting for Owner Response, etc. The |
| |status is Initiation in Progress by default. |
|Export Controlled |If this check box is selected, only users of the Lead site with the same country of |
| |citizenship and those named on the CAR will have access to it. |
| | |
| |If this check box is checked, it indicates that the CAR is marked as export controlled to |
| |comply with Export Control laws. |
| | |
| |Export controlled CAR data cannot be viewed, edited or included in any report by a user who is|
| |not of the same nationality or site as that entered in the CAR. |
|Void CAR |Select the field to nullify an existing CAR. |
| |[pic]Note |
| |The field is displayed only to users with the Level of an Administrator. |
| |The Lead/Requester, SPOC or Owner can request the administrator to void a CAR. |
| |The administrator must enter reason for voiding the CAR in the CAR comments. |
| |Voided CARs are not included in reports. |
Lead Information (Initiated By)
The Lead initiates the CAR, and assigns the Requester and SPOC/ Coordinator. The fields in this section are automatically completed using information based on the User ID. The following table provides the fields available under Lead Information section:
|Field |Description |
|Lead Site (mandatory) |The site associated with the person who is logging on to the system. |
|Initiation Date/Time |The date and time at which the CAR is generated. |
|Lead Name (mandatory) |The person initiating the CAR. |
|Lead ID (mandatory) |The ID of the person initiating the CAR. |
Requester Information (Reported By)
The Requester identifies nonconformity, including product nonconformance or other requirements violation (e.g. failure to follow a work instruction), or identifies an opportunity for preventive action. The Requester can initiate a CAR or ask the Lead to initiate a CAR on their behalf. The Lead and the Requester can be the same person. The Lead must enter the Event Date, the date on which the nonconformance was found.
Depending on the type of the CAR, the fields in the Requester Information section change. Additional fields are displayed for the following types of CARs:
▪ Customer Audit
▪ Customer Complaint
▪ Customer Hardware
▪ Customer Non-Hardware
▪ DCMA
▪ Disclosure
▪ ERP Initiated - Customer
▪ HSE Regulatory
▪ ISO 14001 Audit
▪ ISO Registration Audit
▪ Investigate
▪ OEM Failure
▪ PQDR
▪ Perf Review Institute
▪ Regulatory
▪ Reliability
▪ Request for Information
▪ Space Station Audit
▪ Supplier – RMRA
▪ Supplier Reversal
The following table provides the fields available under the Requester Information section:
|Field |Description |
|External Requester Approval * |Select the check box if the Requester is external, (Customer, FAA, Third Party Registrar) |
| |that requires approval before closure. |
|Requester Name (mandatory) |The name of the person who requests CAR issuance. |
| |To choose the Requester Name, click Look up. A pop-up window appears with search criteria |
| |based on the User ID or Last Name. |
| |Enter the User ID or Last Name and click Submit. To view all records, leave the fields blank |
| |and click Submit. The number of records found is displayed, and a table is updated with the |
| |search results. |
| |Select the Requester Name by clicking the User ID hyperlink. The Requester Name, Requester |
| |ID and Phone number are automatically completed. |
|Requester Company (mandatory for |The external company which initiated a CAR, e.g. DNV, FAA or Customer. |
|external CAR types) * |To choose the Requester Company, click Look up. A pop-up window appears displaying the |
| |search criteria based on the Company Code or Company. |
| |Enter the Company Code or Company and click Submit. To view all records, leave the fields |
| |blank and click Submit. A table displays with search results and the number of records. |
| |Select the Company Name by clicking the Name hyperlink. The Requester Company, Phone and Mail|
| |Stop are automatically completed. |
|Requester ID (mandatory) |Requester ID is automatically completed. |
|Phone |Phone number is automatically completed. |
|Contact Name * |When the CAR is initiated by a Customer or on their behalf, a contact name must be provided. |
|Contact Phone * |When the CAR is initiated by a Customer or on their behalf, a phone number must be provided. |
|Mail Stop |The mail stop is the building mail address. |
|Requester CAR # |The CAR # issued by the Customer or other external agency. |
|Audit Reference |The Audit Reference Number if the CAR was the result of an Audit. |
|Event Date |The date on which the event was found. |
| | |
| |To choose the Event Date: |
| | |
| |Enter the date manually in the dd-mmm-yyyy format. |
| |OR |
| |Click[pic]. Select the date from a calendar. |
[pic]Note
• When the CAR is initiated by (or on behalf of) a Customer, the FAA, or a third party auditor , the Requester Name is replaced with the Requester Company.
• * indicates the additional fields that are displayed.
Owner Information (Assigned To)
The SPOC/Coordinator is a person of authority in the function/department that they are representing. If the Owner is not assigned by the Lead/Requester, an e-mail is sent to the SPOC/Coordinator requesting owner assignment. The owner is then assigned by the SPOC/Coordinator. The Lead can assign the Owner, when the Owner and Lead are Honeywell Employees.
The following table provides the fields available under Owner Information section:
|Field |Description |
|Owning Site (mandatory) |The CAR is assigned to the site that is responsible for correcting the nonconformance. For |
| |inter-site CARS, the primary SPOC who also acts as the site focal is automatically populated. |
|SPOC/Coordinator (mandatory) |The person who co-ordinates the action to be taken. |
| |To choose the SPOC/Coordinator, click Look up. A pop-up window appears with search criteria based |
| |on User ID or Last Name. |
| |Enter the User ID or Last Name and click Submit. To view all records, leave the fields blank and |
| |click Submit. A table is updated with search results. |
| |Select the SPOC/Coordinator by clicking the User ID hyperlink. |
|Owner Name |The person assigned by the SPOC or the Lead/Requester to be the owner of the CAR. |
| |To choose the Owner, click Look up. A pop-up window appears with search criteria based on User ID |
| |or Last Name. |
| |Enter the User ID or Last Name and click Submit. To view all records, leave the fields blank and |
| |click Submit. A table is updated with search results. |
| |Select the Owner by clicking the User ID hyperlink. |
|Owner ID |Owner ID is auto-filled when Owner is selected. For Supplier CARS, the Owner is the Supplier |
| |company identified by their DUNs number. |
|Product Line |Product Line may be automatically completed based on Owner, |
| |OR |
| |To choose Product Line, click the drop down arrow. A list appears containing the available Product |
| |Lines. |
| |Select the appropriate Product Line Name. |
|Department |Department may be automatically completed based on Owner, |
| |OR |
| |To choose Department, click the drop down arrow. A list appears containing the available |
| |Departments. |
| |Select the appropriate Department Name. |
|Cell |Cell may be automatically completed based on Owner, |
| |OR |
| |To choose Cell, click the drop down arrow. A list appears containing the available Cells. |
| |Select the appropriate Cell Name. |
|Date/Time to Owner |CAR date and time of owner assignment is auto-completed. |
|Extension Counter |The counter keeps track of the number of extensions. Date changes during the initiation process |
| |are not counted as an extension. |
| | |
| |If dates are changed after initiation, they are counted as an extension. If the date is changed by|
| |an administrator, a pop-up message appears asking if this should be counted as an extension. |
| | |
| |[pic] |
| | |
| | |
| |To confirm, click OK. The Extension Counter increments. |
| |In rare cases an administrator may choose to not count a date change as an extension, e.g. when |
| |correcting date errors. |
|Lead Approval Due Or Requester Due|The date when the feedback regarding the corrective action cause analysis, response, and approvals |
|Date |must be entered on the CAR is due. |
| | |
| |To choose the Due to Requester date: |
| |Enter the date manually in the dd-mmm-yyyy format. |
| |OR |
| |Click [pic]. Select the date from the calendar. |
|SPOC Approval Due to Requester |SPOC evaluation of response and analysis is due on this date. SPOC Approves or Rejects response to|
| |the CAR by this date. |
| | |
| |To choose the SPOC Approval Due to Requester date: |
| |Enter the date manually in the dd-mmm-yyyy format. |
| |OR |
| |Click [pic]. Select the date from the calendar. |
| | |
|Owner’s Response Due |Owner evaluation of response and analysis is due on this date. Owner Approves or Rejects response |
| |to the CAR by this date. [pic] |
| | |
| |To choose the Due from Owner date: |
| |Enter the date manually in the dd-mmm-yyyy format. |
| |OR |
| |Click [pic]. Select the date from the calendar. |
[pic]Note
• DUNS # is provided by Dunn & Bradstreet that uniquely identifies a Supplier or Customer. The number is available in OneSource and on the Supplier Portal.
Command Buttons
The following command buttons are common to all pages in the CAR.
[pic]
|Command Buttons |Description |
|Previous |Goes back to previous page. |
|Next |Goes to next page |
|Save |Saves information entered into the CAR. |
|Submit |Submits to next approver. |
|Create Dash |Opens a new CAR with a sequential Dash Number when the new CAR is related to the old CAR. |
|Exit CAR |Click this button to exit the CAR and go to the main menu. |
Step 3: Product Process
Product Data
Complete the product information to conduct a cause analysis to resolve the CAR. Include the following details about the part:
|Field |Description |
|Honeywell Part # |The part number of the product requiring corrective action. |
|Serial # or Date Code |The serial number or the date code of the product requiring corrective |
| |action. |
|Part Name |The part name of the product requiring corrective action. |
|Program/System Name |The program or system name requiring corrective action. |
|Customer Part # |The Customer's part number of the product requiring corrective action. |
|Mfg. /Vendor ID # |The ID number of the Manufacturer or Vendor who built the product requiring |
| |corrective action. |
|Commercial - Qty Inspected |The quantity of the commercial products that were inspected. |
|Government - Qty Rejected |Not Applicable |
| |[The quantity of the government products that were rejected.] |
|Reject Tag # |The Customer’s rejection tag number. |
|ITR/nonconformance # |The ITR Nonconformance number assigned to the product requiring corrective |
| |action. |
|Repair Order # |The internal repair order number assigned for tracking the hardware through |
| |the repair process. |
|Received Date |The date when the hardware was received from the Customer. |
| | |
| |To choose the Received Date: |
| |Enter the date manually in the dd-mmm-yyyy format. |
| |OR |
| |Click[pic]. Select the date from the calendar. |
|P.O / Contract # |The purchase order number or the contract number of the product requiring |
| |corrective action. |
|Blue Print Revision |The revision level of the hardware. |
|Mfg. Assembly Doc. # |The manufacturing assembly document number of the product requiring |
| |corrective action. |
|Mfg. Assembly Doc. Date |The manufacturing assembly document date of the product requiring corrective |
| |action. |
| | |
| |To choose the Mfg. Assembly Doc. Date: |
| |Enter the date manually in the dd-mmm-yyyy format. |
| |OR |
| |Click[pic]. Select the date from the calendar. |
|Mfg. Assembly Doc. Operation |The manufacturing assembly document operation of the product requiring |
| |corrective action. |
|MRB Reference # |The material review board reference number of the product requiring |
| |corrective action. |
|Customer MRB Reference # |The Customer material review board reference number of the product requiring |
| |corrective action. |
|Customer MRB Approval |The Customer material review board approval of the product requiring |
| |corrective action. |
|MRB Quantity |The material review board quantity of the product requiring corrective |
| |action. |
Process Data
|Field |Description |
|Quality System Element |Select the AS9100/ISO9000 code indicating the Quality System Element related |
| |to the finding or the appropriate Quality System Element for the CAR. |
|Reference Doc # |Enter Reference Document number, e.g. PRO, AP, AC, INS, INF or other document |
| |number of the product requiring corrective action. |
|Reference Document Revision |The reference document revision. |
|Reference Document Title |The title of the reference document of the product requiring corrective |
| |action. |
|Reference Document Rev. Date |The reference document revision date of the product requiring corrective |
| |action. |
| | |
| |To choose the Reference Document Rev. Date: |
| |Enter the date manually in the dd-mmm-yyyy format. |
| |OR |
| |Click[pic]. Select the date from the calendar. |
[pic]Tip
If you find necessary information is missing, contact the Requester for further information and clarification.
Step 4: Finding Event
The Lead/Requester fills in the information on the requirement violation that led to the corrective action request.
A good Finding Event data includes:
• Only basic facts.
• A simple explanation of:
o What happened?
o When and/or where the event occurred. For example, the final hour of the burn-in process, during contract review, during final test on line 7, etc..
• Use complete sentences.
• Keep the information simple enough to be understood by anyone who reads this CAR.
• Do not use acronyms.
Requirement
Record the specific requirement violation. In the case of Preventive Action CAR types it is potential violation, and may include the text for the Quality System Element that was selected in the Product/Process page. For example, if a procedure was not followed, enter the section of the procedure where there was a problem.
Finding / Event Description (mandatory)
Enter a clear, concise explanation of the event. The event is an occurrence resulting in non-conformities, product or process failure, Customer complaint, Customer escape, audit findings, failure modes, accidents, or other problems. The finding/event text field must contain a description of the occurrence where the nonconformance was discovered. An example would include a deviation from the Customer's requirements.
The finding is the result of the event, e.g. audit nonconformances, or product delivered is not functioning properly or damaged.
Event Code (mandatory)
The event code must correspond to the Finding/Event Description.
Choose the Event Code from the drop-down menu based on the Code or Description.
Event Type (mandatory)
The event type is typically used for audit findings to identify the nature of the finding or the event that took place. The following are the major event types:
1. Adequacy - a procedure existed, but was not adequate.
2. Compliance - an adequate procedure existed, but was not followed.
3. Conformance - an adequate procedure existed, but was not followed properly.
4. Existence - a procedure did not exist.
The Event Type must correspond to the Finding/Event Description.
Choose the Event Type from the drop-down menu based on the Code or Description.
Event Category /Severity (mandatory)
Choose the Event Category/ Severity code from the drop-down menu. Event Categories include:
▪ CRT - Critical
▪ CCP - Customer Complaint
▪ I - I - Major
▪ II - II - Minor
▪ NON - Non Conformance
▪ O - Observation
▪ CMP - R&O - Customer Complaint
▪ CNC - R&O - Customer Concern
▪ ESC- R&O - Escape
▪ FS - R&O - Flight Safety
▪ IE - R&O - Internal Escape
▪ REJ - R&O - Reject
▪ CCP - Customer Complaint
Required Responses
The Lead/Requester must choose a minimum of three responses from the following table for the initiated CAR. The Owner must conduct a root cause analysis to determine the correct response and takes action. The Response can be any of the following:
|Cause |Description |
|Direct cause |The initial event that led to a deviation from the requirements. This is the first cause |
| |in the cause chain. |
|Contributing cause |The cause that contributed to the event, but by itself would not have contributed to the |
| |event. All causes are contributing causes, but the first and last causes are given special |
| |names. |
|Root cause |The last cause in the cause chain |
|Specific Action / Containment |The action taken to correct or control the consequences of the direct cause and the |
| |effects. |
|Preventive Action |The action taken to prevent the recurrence of the event that was observed in the root and |
| |contributing causes. |
|Systemic Action |The action taken to ensure that the event does not occur in other areas. |
|Other affected Products / Processes|The identification of products and processes that could be affected by the event. |
|Investigation Activities | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| |The activities involved in investigating the causes for the occurrence. |
[pic]Tip
For future reference, Note the CAR ID before exiting the CAR.
Team
The owner can assign team members who control, use, or depend on the process for which the CAR was initiated. These members are the natural team members as they have the vested ownership of the problem to be solved.
[pic]Note
At Aerospace sites, at least one member of the team must have Cause Analysis and Mistake Proof (CAMP) training or have a CAMP facilitator assist the team.
The natural team must know when to expand to a qualified team and must be able to identify that resource. The qualified team members are those who can provide necessary resources to understand the problem by providing a particular technical expertise, management support, or help in cause analysis and mistake proofing.
The team must contain a minimum of two people. Two people from different backgrounds and responsibilities putting forth different ideas can add a great value to the process. The team must not get too large, become uncontrollable, or have members without any responsibilities.
The Owner selects team members on the Team page as follows:
1. Search for team members by clicking Search & Add. A pop-up window appears with the search criteria based on user ID or last name.
2. Enter the User ID or Last Name and click Submit. To view all records, leave the fields blank and click Submit. The number of records found is displayed. A table is updated with the search results.
3. Select the team members by clicking the Select box.
4. Click OK. The selected team member's name, department, phone, and mail stop is displayed.
5. The owner can delete a particular resource from the team by checking the Select box and clicking the Delete button.
[pic]
6. Enter the Event Question. It is a why question the team uses to define the problem being analyzed and to build a cause chain. The event question is derived from the Event Description in the Finding Event page.
An Event Question is:
▪ Short
▪ Simple
▪ Concise
▪ Focused on one problem.
▪ A question starting with "Why"
An Event Question does not:
▪ Tell what caused the event
▪ State what to do next
▪ Explain the event
[pic]Note
During the response phase, event question is mandatory. If the event question is not entered, the error message below will appear.
[pic]
Response
The owner determines corrective action after the CAR is issued. As a response, the owner builds a cause chain. The Owner then determines the direct, contributing, and root causes before providing solutions or the corrective actions to contain the effect of the event.
[pic]
The following table provides information regarding the various causes and the corrective action required for each cause:
|Cause |Description |Action |Description |
|Direct Cause |The first cause in the |Specific Action |The actions taken to correct the direct cause |
| |cause chain that directly |/Containment |and/or the effect. Promise Date is the date of |
| |resulted in the event. | |completion and is mandatory if checked on the |
| | | |Finding/Event page. |
| | | | |
| | | |To choose the Promise Date: |
| | | |Enter the date manually in the dd-mmm-yyyy format. |
| | | | |
| | | |OR |
| | | |Click [pic]. Select the date from the calendar. |
| | | |The date is updated in the field in the dd-mmm-yyyy|
| | | |format. |
|Contributing Cause |The causes that |Preventive Action |The actions taken against the contributing causes |
| |contributed to an event | |to prevent the recurrence of the event. Promise |
| |but, by itself, would not | |Date is the date of completion and is mandatory if |
| |have caused the event. The| |checked on the Finding/Event page. |
| |causes between the direct | | |
| |cause and the root cause | |To choose the Promise Date: |
| |are classified as | |Enter the date manually in the dd-mmm-yyyy format. |
| | contributing causes. | |OR |
| | | |Click [pic]. Select the date from the calendar. |
| | | |The date is updated in the field in the dd-mmm-yyyy|
| | | |format. |
|Root Cause |The last cause in the |Preventive Action |The actions taken against the root cause to prevent|
| |chain. | |the recurrence of the event. Promise Date is the |
| | | |date of completion and is mandatory if checked on |
| | | |the Finding/Event page. |
| | | | |
| | | |To choose the Promise Date: |
| | | |Enter the date manually in the dd-mmm-yyyy format. |
| | | |OR |
| | | |Click [pic]. Select the date from the calendar. |
| | | |The date is updated in the field in the dd-mmm-yyyy|
| | | |format. |
[pic]Tip
As a minimum, the Owner responds to all fields checked by the Lead/Requester in the Required Responses on the Finding Event page, during the process of initiating a CAR.
[pic]
The other fields consists of:
|Field |Description |
|Systemic Action |Actions taken to ensure that the finding does not occur in other areas, implemented as a Plant |
| |or System-wide action. Promise Date is the date of completion and is mandatory if checked on the|
| |Finding/Event page. |
| | |
| |To choose the Promise Date: |
| |Enter the date manually in the dd-mmm-yyyy format. |
| | |
| |OR |
| |Click [pic]. Select the date from the calendar. The date is updated in the field in the |
| |dd-mmm-yyyy format. |
| | |
|Other Affected Product/Process |List the other products and processes that are or may be affected by the same or similar event. |
|Investigation Activities |The activities performed to investigate the causes of the finding. |
| |[pic]Tip |
| |Do not use someone’s name. Use generic functions / titles. |
| |Do not blame or single out others. |
| |Be careful what you say and how you say it, because Customers can see this information. |
| |This is the place to capture miscellaneous data carefully rather than the comments section. This|
| |data can be changed if necessary. |
|Root Cause Code (mandatory) |The root cause code must correspond to the Root Cause. |
| |To choose the root cause code, click the drop down arrow. A list will of available codes will |
| |appear. |
| |Select the desired code. |
|C/A Code (mandatory) |The C/A code must correspond to the corrective actions taken. |
| |To choose the corrective action code, click the drop down arrow. A list will of available codes |
| |will appear. |
| |Select the desired code. |
|Response Signoff - Owner |The name of the owner is automatically completed when the owner selects the Response Completed |
| |check box. |
|Response Signoff - Date |The date and time the response is saved is automatically completed. |
|Response Completed |The owner selects the check box when the response is complete. |
| |[pic]Tip |
| |When the response is not complete, the owner can save the responses by clicking Save. |
| |The data entered in the Response page can be changed until you check the Response Completed |
| |check box. |
| |The owner selects this check box only when all the responses are recorded. |
| |If the plan cannot be completed within the Due from Owner date in the Assignment page, the owner|
| |can request to the Lead/ Requester for an extension. These extensions are counted in the |
| |extension counter. |
Approval
The Owner obtains approval of both the SPOC/Coordinator and the Lead/Requester for the corrective actions specified in the Response page.
Owning Site SPOC/Coordinator Disposition
The following table provides the fields available under Owning Site SPOC/Coordinator Disposition section:
|Field |Description |
|Name |The name of the SPOC/Coordinator is automatically completed when the SPOC/Coordinator selects |
| |the accepted or rejected check box. |
|Date |The date and time at which the SPOC/Coordinator has accepted or rejected the owner's response |
| |to the CAR. |
|Accepted |The SPOC/Coordinator selects the check box if the owner's response is accepted. Click Submit, |
| |the date field is completed automatically. |
|Comments |The SPOC/Coordinator can fill in any comments about the disposition. |
|Rejected |The SPOC/Coordinator selects the check box if the owner's response is rejected. Click Submit, |
| |the date field is completed automatically. |
|Rejection Count |The rejection count value is incremented automatically depending on the number of times the |
| |SPOC rejects the owner's response. |
Lead Site Requester Disposition
The following table provides the fields available under Lead Site Requester Disposition section:
|Field |Description |
|Name |The name of the Lead is automatically completed when the Lead selects the accepted or |
| |rejected check box. |
|Date |The date and time at which the Lead has accepted or rejected the owner's response to the CAR. |
|Accepted |The Lead selects the check box if the owner's response is accepted. Click Submit, the date |
| |field is completed automatically. |
|Comments |The Lead may add comments about the disposition. |
|Rejected |The Lead selects the check box if the owner's response is rejected. Click Submit, the date |
| |field is completed automatically. |
|Rejection Count |The rejection count value is incremented automatically depending on the number of times the |
| |Lead rejects the owner's response. |
Follow-up
When the Lead's disposition is accepted in the Approval page, the application prompts the Lead/Requester to schedule a follow-up review. The Lead/Requester selects a reviewer to follow up on the Owner's response to the CAR and to complete the information in the Follow-up page.
Follow up Reviewer Information
|Field |Description |
|Reviewer |A reviewer must verify all corrective actions were implemented as stated. The follow-up reviewer can be a |
| |team member or any person capable of assessing the corrective actions. |
| |To choose the Reviewer, click Look Up. A pop-up window appears with search criteria based on the User ID or |
| |Last Name. |
| |Enter the User ID or Last Name and click Search. To view all records, leave the fields blank and click |
| |Search. The number of records found is displayed. A table is updated with the search results. |
| |Select the Reviewer by clicking the Select radio button. |
|Scheduled Date |The date when the follow-up must be completed. |
| | |
| |To choose the Due from Owner date: |
| |Enter the date manually in the dd-mmm-yyyy format. |
| |OR |
| |Click [pic]. Select the date from the calendar. |
|Actual Date |The date when the follow-up was conducted. |
| | |
| |To choose the Due from Owner date: |
| |Enter the date manually in the dd-mmm-yyyy format. |
| |OR |
| |Click [pic]. Select the date from the calendar. |
| |[pic]Tip |
| |When clicking Save, a pop-up message may appear indicating that the record cannot be saved because of the |
| |following incomplete data . To correct, change the actual date to today’s date and not a date in the future. |
| |[pic] |
| | |
|Remarks |The reviewer may enter remarks about the review conducted. |
|Follow-up Code |Select the follow-up code from the drop-down menu. The auditor/reviewer must choose one of the following |
| |codes: |
| |FNS - Follow-up Review not Scheduled |
| |N/A - Not Applicable |
| |PHY - Physical |
| |INP - In-process |
| |OEF - Objective Evidence On File |
| |REV - Review of Revised Documentation |
| |SRV - Surveillance of Subsequent Process |
| |AOE - Awaiting Objective Evidence |
| |[pic]Note |
| |When the Lead/Requester does not change the Follow-up code when scheduling a review, the following pop-up |
| |message appears. |
| | |
| |[pic] |
Disposition
|Field |Description |
|Name |The name of the reviewer is automatically completed when the reviewer marks the disposition as Accepted or |
| |Rejected by selecting the respective check boxes. |
|Date |The date and time of the disposition save by the Reviewer. |
|Accepted |The reviewer selects the Accepted check box if there is evidence that the owner has performed all the |
| |promised actions on the CAR. |
|# of Follow-ups |The number of follow-up reviews conducted is automatically updated when the Follow up is performed. |
|# of Follow-up |The number of extensions on the follow-up scheduled date is automatically updated when the schedule date is |
|Extensions |revised. |
|Rejection Count |The counter value automatically increments when the reviewer selects the Rejected check box and clicks |
| |Submit. |
|Rejected |The reviewer must select the Rejected check box, if: |
| |there is no proper evidence that a corrective action has been taken by the owner. |
| |the problem for which a CAR was initiated has not been addressed. |
Effectiveness
An effectiveness review verifies that the completed actions actually fixed the original problem without creating any new problems. The Follow-up Reviewer selects an Effectiveness Reviewer.
The team members determine how the effectiveness of the corrective action can be tested or measured. The Effectiveness Reviewer checks for proof that the problem is prevented and there is no chance of another occurrence of the same event. Plan on periodic effectiveness checks if the problem is serious or you do not have complete control over implementing the corrective actions.
Effectiveness Reviewer Information
The following table provides the fields available under Reviewer Information section:
|Field |Description |
|Reviewer |The reviewer verifies that the corrective actions taken by the owner are effective. |
| |To choose the Reviewer, click Look Up. A pop-up window appears with search criteria based on |
| |the user ID or last name. |
| |Enter the User ID or Last Name and click Search. To view all records, leave the fields blank |
| |and click Search. The number of records found is displayed. A table is updated with the search|
| |results. |
| |Select the reviewer's name by clicking the Select radio button. |
|Scheduled Date |The scheduled date is the date when the effectiveness review is to be performed. |
| | |
| |To choose the Date/Time to Owner date: |
| |Enter the date manually in the dd-mmm-yyyy format. |
| |OR |
| |Click [pic]. Select the date from the calendar. |
|Actual Date |The actual date is the date when the review was conducted. |
| | |
| |To choose the Date/Time to Owner date: |
| |Enter the date manually in the dd-mmm-yyyy format. |
| |OR |
| |Click [pic]. Select the date from the calendar. |
|Remarks |The reviewer enters remarks about the review conducted. |
Disposition
The Disposition section provides the result of the effectiveness review. The effectiveness reviewer selects the accepted check box if the audit evidence is sufficient; or rejects. The reviewer issues a new CAR if new events are found where corrective action needs to be performed.
|Field |Description |
|Name |The name of the effectiveness reviewer is automatically completed when the reviewer marks the disposition as|
| |Accepted or Rejected by selecting the a check box. |
|Date |The date and time of the disposition, by the effectiveness reviewer. |
|Accepted |The effectiveness reviewer selects the Accepted check box if there is evidence that the corrective actions |
| |is effective over a period of time. |
|Create New CAR |To reject and close the current CAR and open a new CAR with a sequential dash number: |
| |Reject the current car and click Submit. |
| |Select the Close and Create New Car radio button and click Submit. |
| |A pop up window will appear, click OK to proceed. |
| |[pic] |
| |Click Create New CAR. A pop-up message appears indicating that the current car is closed successfully and a |
| |new CAR is created. An e-mail is sent to the Owner as notification that a CAR has been assigned and action |
| |must be taken. Another e-mail is sent to all the stakeholders of the old CAR informing them that the CAR is |
| |closed. |
| |[pic] |
| |Click OK. A pop-up message appears asking for confirmation. |
| |[pic] |
| | |
| | |
| |To open a the new CAR, click OK. |
|Rejected |The effectiveness reviewer selects the Rejected check box, if: |
| |there is no proper evidence that a corrective action taken by the owner is effective. |
| |the corrective actions have affected other areas and created new problems. |
History
The complete history of the CAR is recorded and displayed with date and time. This includes, which includes who initiated the CAR, the owner, what response was taken, the list of automated e-mails and the changes made to the CAR. The History page provides a complete report of the stages the CAR has undergone. Contents of this page are automated and accurate.
The following details can be viewed:
|Field |Description |
|Non-Status Changes |The steps followed in processing a CAR. |
| | |
| |The process steps are: |
| |Initiated By |
| |Initiated Date |
| |Owning Site Assigned |
| |Owner Assigned |
| |Response Date |
| |SPOC Disposition |
| |Final/Rqst. Disposition |
| |External Disposition |
| |Follow-up Disposition |
| |Change History |
| |Email History |
|Initiated By |The name of the person who initiated the CAR, the Lead. |
|Initiated Date |The date and time when the incident occurred. |
| |For example, if the Lead or SPOC assigned the owner on 9th August 2006, the information is |
| |displayed as follows under Non-Status Changes: |
| | |
| |09-AUG-2006 09:47:23 AM |
| | |
|Owning Site Assigned | |
|Owner Assigned | |
|Response Date | |
|SPOC Disposition | |
|Final/Rqst. Disposition | |
|External Disposition | |
|Follow-up Disposition | |
|Change History |The changes made are saved and are listed in Non-Status Changes. |
| |The name of the person and the time that the change was made is recorded. |
| | |
| |For example: |
| |Anita Johney made the following changes on 14-AUG-2006 03:54:55 AM: |
| |- CAR Initiation date set to 14-AUG-2006 02:52:29 AM |
| |- CAR is Initiated by Anita Johney |
|Status Changes |The list of automated e-mails sent by the application is recorded in the Status Changes area. |
| | |
| |For example: |
| |Car changed by User Anita Johney on 14-AUG-2006 03:59:16 AM |
| |- Subject : Waiting for Owner Assignment |
| |- To : anita.johney@ |
Comment
Comments may be entered at any stage of the CAR. Comments provide additional information regarding the CAR or the process of resolving a CAR effectively.
1. Enter the comments in the text box provided.
2. Click Add New Comment. The comments are displayed in a tabular format, along with the name of the user and the date and time at which the comments were entered.
3. To save the new comments, click Save.
[pic]Note
• Comments added cannot be changed, be thoughtful about the comments you insert.
• Comments cannot be added after the CAR is closed.
Locate CAR
CAR links are displayed in the Home screen for CARs assigned to the user as Lead, Requester, SPOC, Owner, Team members, or reviewer.
To locate other CARs, search for the CAR by entering the criteria and clicking Search.
see Search
[pic]
Initiating a CAR
The Lead/Requester logs on to eCATS to initiate a CAR. The User (name) and profile are displayed at the top left side of the screen.
Initiating a CAR consists of the following steps:
1. Click Initiate CAR from the home page.
2. Select the Type of the CAR. The CAR # is NEW and the Status is Initiation in Progress by default.
3. Click the Next to proceed to the Assign People page.
[pic]Note
• All the fields marked in red are mandatory.
4. Enter the details about the Lead, Requester, and Owner. Enter Event date, site details, and due dates for the SPOC, Requester, and Owner under the Assign People page.
▪ Answer the disclosure questions if required.
5. Click the Next to proceed to the Product and Process Details.
▪ Enter the details of the product in the Product Details section.
▪ Enter the details of the related documents in the Process Details section.
6. Click the Next to proceed to the Findings and Events page:
▪ Enter the information about the requirement that was not met in the Requirement section.
▪ Enter the description of what was executed differently from what is required, in the Finding/Event description section.
▪ Select the Event Code, Event Type, Event Category/Severity from the list of codes provided in the drop-down menus.
▪ Select the check boxes for the required response in the Required Response section.
▪ Provide any additional information that may be helpful in the comments box at the bottom of the page.
7. Click Submit. A pop-up message appears indicating the CAR is saved successfully.
[pic]
8. Click OK. An e-mail notification is sent to the SPOC requesting Owner assignment and the Status changes to Waiting Owner Assignment. If the lead entered an owner during the initiation process, an email is sent to the SPOC and the Owner; the Status of the CAR changes to Waiting for Owner Response.
9. Exit the CAR by clicking Exit to enable the SPOC or owner to log on and take action. The owner may assign team members to resolve the CAR.
Draft CARS
CAR can be saved as a draft by using the option save as Draft.
Later this CAR can be submitted .
[pic]
Locating a CAR
A CAR can be located using the following methods:
1. In the Home page, enter the CAR ID or part of a CAR ID to be located into the CAR ID field. Click on Search.
[pic]
2. If only one CAR matches the search, the car will be opened to the Assign People page, if there are multiple CARS that match your search a window with the matches will open. Select the desired CAR by clicking on the CAR ID number.
[pic]
Responding to a CAR
The owner is required to respond to the CARs before the due date. Team members may be assigned to take action, or the owner can resolve the CAR.
The CAR Resolution cycle is as follows:
|Typical Order |Category |Abbreviation |Expected Time Frame (in Days) |
|1 |Waiting Owner Assignment |WOA |1 |
|2 |Waiting for Owner Response |WOR |14-30 |
|3 |Waiting for SPOC Approval |WSA |1 |
|4 |Rejected at SPOC Approval |RJ1 |1 |
|5 |Waiting for External Approval |WEA |3-4 |
|6 |Rejected at External Approval |RJ3 |3-4 |
|7 |Waiting Owner Implementation |ORI |7 |
|8 |Pending Follow-up Review |PFU |Based on CAR |
|9 |Rejected at Follow-up |RJF |1-2 |
|10 |Pending Effectiveness Review |PEF |Based on CAR |
|11 |Rejected at Effectiveness |RJE |1-2 |
|12 |Closed |CLD |30-90 |
[pic]Note
• All users are required to save and exit the CAR. This will ensure that the next user has access to modify the CAR.
Responding to a CAR consists of the following steps:
1. In the Home page, search for the CAR ID or click the CAR ID hyperlink. The Owner reviews details in the Assignment, Product/Process, and Finding Event pages.
2. To assign a team for resolving the CAR, Click the Team Activity page:
▪ Select the team members.
▪ Enter the event question in the Event Question field.
4. Click the Response to CAR page:
▪ Enter the Investigation Activities and Other Affected Product/Processes.
▪ Enter the Direct, Contributing and Root causes.
▪ Select the Root Cause code by clicking the Drop down menu.
▪ Enter the actions taken to contain the event and prevent recurrences in Specific Action/Containment, Preventive Action, and Systemic Action including the Promise Dates.
▪ Select the C/A code by clicking the Drop down menu.
5. The Owner selects the check box Check When Complete when the actions to contain and resolve are complete. The Submit button will be grayed out until the box is checked. The Owner is automatically completed with the owner's name.
6. Click Submit. A pop-up message appears asking if the CAR is to be submitted.
[pic]
7. Click OK. The Response Date is automatically completed with the date and time when the CAR was submitted. An e-mail is sent to the SPOC/Coordinator for approval. The Status of the CAR changes to Waiting for SPOC Approval.
8. The SPOC/Coordinator logs on and reviews the pages from the Assignment to the Response. In the Approval Details page, the SPOC/Coordinator can approve or reject the Owner's response to the CAR.
To Reject
▪ Select the check box for the Rejected field. The name is automatically completed in the SPOC field and the Rejection Count value increments.
▪ Comments are mandatory when the CAR is rejected. An e-mail is sent to the Owner for further investigation and the Status of the CAR changes to Rejected at SPOC.
▪ The Owner logs on and reviews the response in the Response page. If necessary, the owner will change the team members from the Team page or the responses in the Response page. The process repeats (see Step 3) until the SPOC approves the CAR.
To Accept
▪ Select the check box for the Accepted field. The name is automatically completed in the SPOC field.
▪ Click Submit. The Date is automatically completed with date and time when the CAR was submitted. An e-mail is sent to the Lead/ Requester for their approval. The Status of the CAR changes to Waiting for Lead/Requester Approval.
9. After the CAR is approved by the SPOC, the Lead/Requester logs on and reviews the pages from the Assign People to the Respond to CAR. In the Approval Details page, the Lead/Requester can approve or reject the Owner's response to the CAR.
To Reject
▪ Select the check box for the Rejected field. The name is automatically completed in the Requester field and the Rejection Count value increments.
▪ Comments are mandatory when the CAR is rejected. An e-mail is sent to the Owner for further investigation, and he Status of the CAR changes to Rejected at Lead Approval.
▪ The Owner logs on and reviews the response in the Respond to CAR page. If necessary, the owner will change the team members from the Team Activity page or the responses in the Respond to CAR page. The process repeats (see Step 3) until the Lead/Requester approves the CAR.
To Accept
▪ Select the check box for the Accepted field. The name is automatically completed in the Requester field. Click Submit.
▪ A pop-up message appears to schedule a follow-up review.
[pic]
To schedule a follow-up review
▪ Click OK. The CAR changes to the Follow-Up Review page.
▪ Select a reviewer name from the look up window, then click Submit. The CAR is sent to the Owner for Implementation. See Following up and Closing a CAR.
To cancel a follow-up review
▪ Click Cancel. A pop-up message titled Reasons for not scheduling a review appears. Enter the reasons for not scheduling a review. This automatically fills the Remarks of the Reviewer Information section in Follow-up page.
[pic]
▪ Click OK. The CAR changes to the Follow-Up Review page. On this page, select a reviewer name from the look up table and click Submit. The CAR is sent to the Owner for Implementation. The Follow-up Code, by default will be FNS- Follow-up Review not Scheduled.
Extension of Due Date
An extension is required if the owner is unable to complete the corrective actions by the due date. The owner can submit a request to the lead/requester for an extension. The lead/requester extends the due date if the reasons provided by the owner for an extension are reasonable.
The process of extending the due date of the owner by the Lead/Requester is as follows:
1. In the Home Page Click the CAR ID link of the CAR that requires an extension of the due date.
2. In the Assign People page and under the Due Dates Information section, the Lead/Requester can extend the Owner’s Response Due, SPOC Approval Due to Requester, and the Lead Approval Due Or Requester Due Date by clicking[pic]. Select the date from the calendar.
3. Click Save. An e-mail notification is sent to the owner with the new owners due date. A pop-up message appears indicating the CAR is saved successfully.
[pic]
[pic]Note
If the Lead and the Requester are different, only the Lead can extend the due date of the Owner.
Creating a CAR with a new Dash
When multiple owners (for example, Internal Users and a Supplier) must provide separate answers to a single event, create CARs with a new dash for each owner. The CARs are related and can be identified easily when created with the same CAR number, but with a sequential dash number.
To create the new dash number:
1. In the Home page screen, search for the CAR ID or click the CAR ID hyperlink for which you want to create a new dash number.
2. In the Assign People page, click Create Dash at the bottom of the screen. An XX replaces the current dash number.
[pic]
A pop-up message appears saying that the dash CAR is created.
[pic]
3. Click OK. Make the necessary changes to the corrective action record.
4. Click Save. A pop-up message appears indicating the CAR is saved successfully.
[pic]
5. Click OK. The sequential dash number is assigned and displayed on this record. An e-mail notification is sent to the owner. The status of the CAR is changed to Waiting for Owner Response.
Attaching Documents
Documents are attached as evidence to the action in the response. Findings in the audits can also be documented and attached.
Documents of any format can be attached to the CARs by anyone associated with the corrective action process.
The process of attaching documents is as follows:
1. In the Home page, click on Attachments, the CAR changes to the Attachments page.
[pic]
• Browse and select the file.
• Enter a file description to provide information about the attachment.
• Click Attach. The attached file information is present in a tabular format.
[pic]
[pic]Note
• To go the previous page, click the Previous button.
• To view the file, click on file hyperlink.
• The maximum size of the file that can be attached is 6MB.
• To delete the file, check the Select box then click Delete.
Waiting Owner Implementation, Following up and Closing a CAR
After the owner's response is approved by the SPOC and the Lead, the application prompts the Lead for a follow-up review. If the Lead/Requester chooses not to have a follow-up review, the CAR is closed.
[pic]Note
In Aerospace, all the CARs associated with preventive and/or systemic action require a follow-up review.
To Schedule a Follow-up Review
• In the Follow-up page, the lead/requester:
• Selects the reviewer and clicks Submit. An automated e-mail is sent to the Owner and the status changes to Waiting Owner Implementation.
• After the owner completes the implementation stage by checking the Implementation Complete check box and submits the CAR, the status changes to Pending follow up review.
• The follow-up reviewer logs in and checks for evidence in the form of attached documents to prove that the actions have been completed.
• The reviewer selects a Follow-up Code.
• In the Follow-up page, select the date of the review in Actual Date.
• The follow-up reviewer can accept or reject the Owner's response to the CAR.
Accepted by the Follow-up Reviewer
o Select the check box for the Accepted field. The Name of the follow-up reviewer is automatically completed in the Disposition section. Click Submit. The system prompts the reviewer to set an effectiveness review.
[pic]
o To schedule an effectiveness review
▪ Select the effectiveness reviewer.
▪ Schedule a date for the review to be conducted in Scheduled Date.
▪ Click Submit. An automated e-mail is sent to the effectiveness reviewer. The Status of the CAR changes to Pending Effectiveness Review.
The effectiveness reviewer logs in and checks the effectiveness of the corrective action over a period of time.
▪ In the Effectiveness page, select the date on which the review was conducted in Actual Date.
▪ The effectiveness reviewer can accept or reject the Owner's response to the CAR.
Accepted by Effectiveness Reviewer
▪ Select the check box for the Accepted field. The Name of the effectiveness reviewer is automatically completed in the Disposition section.
▪ Click Submit. The date and time when the CAR is saved is automatically completed in the Date field. An automated e-mail is sent to all the stakeholders informing them the CAR is closed and no more action is necessary on this issue. The Status of the CAR is changed to CLOSED.
Rejected by Effectiveness Reviewer
▪ Select the check box for the Rejected field. The Name of the effectiveness reviewer is automatically completed in the Disposition section.
▪ Click Submit. The date and time at which the CAR is saved is automatically completed in the Date field. An automated e-mail is sent to the owner and the team members informing them that the CAR is rejected and they must revise their response to the CAR. The Status of the CAR is changed to Failed Effectiveness Review.
[pic]Note
▪ If the effectiveness is failed then a new CAR shall be created by clicking Close and Create New Car.
Rejected by the Follow-up Reviewer
▪ Select the check box for the Reject CAR field. The Name is automatically completed and the Rejection Count value is incremented in the Disposition section.
▪ Click Submit. An automated e-mail is sent to the owner and team members informing them that their actions have not been completed and submitted within the due date. The Status of the CAR is changed to Failed Follow-up Owner Action Required.
▪ The Owner must login and take action- to resolve the CAR. The status is then changed to Pending follow up review. The procedure repeats from the Follow Up review until the CAR is closed.
[pic]Note
▪ Owners are not allowed to change or modify the owners response at Failed Follow-up Owner Action Required.
Advanced Search
The Advanced Search provides filters to customize reports. The user may generate reports with only the information required, eliminating the unnecessary details.
[pic]How do I get there?
In the Home page, click Advanced Search
OR
Click Advanced Search in the CAR menu
The following sections are common for all types of filters:
Select Saved Reports
Generate customized reports by selecting:
▪ The data in the fields.
▪ Any additional filters.
▪ The fields to be displayed in the report.
▪ The sort order field .
The report criteria can be saved and re-used.
To Save selected Report
1. Select the fields to generate a customized report from the Quick Filter and Field Selection pages.
The following fields are common to all the tabs in Browse/Export.
|Field |Description |
|Select From Previously Saved |The selection criteria of the previous selections can be saved and re-used. |
|Selections | |
|Stored Selection |The name of the current selection. |
2. Enter the name of the Stored Selection.
3. Click Save.
Additional filters:
Quick Filter
The Quick Filter allows filtering of the CARs based on Business Units, Requester, Owner, etc.
For more information, see detailed Quick Filter section below.
Additional Filter
The Additional Filter allows additional filtering of the data obtained from the Quick Filter. Specify the filter conditions for the report. For more information, see detailed Additional Filter section below.
Field Selection
The Field Selection allows selection of the fields to be displayed in the report. For more information, see detailed Field Selection section below.
The data can be Sorted in the Field Selection based on multiple selected fields in an ascending or descending order using the Up and Down arrows.
Quick Filter
Select Quick Filter Fields
The Quick Filter section provides field selection capability.
|Field |Description |
|Select CAR IDs |The report generated contains CARs with the CAR ID or the part of the CAR ID |
| |specified. |
| | |
| |Specify a part of the CAR ID in Select CAR IDs. For example, to obtain all the CAR IDs|
| |of the site OTHER, enter OTH. All the CARs generated from that site are obtained in |
| |the report. |
| |To add the CAR ID to the selected list box, click [pic] |
| |To delete the CAR ID from the selected list box: |
| |Select the CAR ID to be deleted. |
| |Click [pic] |
|Part# |The report generated contains CARs with the specified Part#. |
| | |
|Date From |The report generated containing CARs with this Start Date. |
| |Click [pic]. Select the date from the calendar. |
|Date To |The report generated contains CARs with this End Date. |
| |Click [pic]. Select the date from the calendar. |
|Business Unit |The report generated contains CARs from the specified Business Unit. |
| | |
| |Select the Business Unit from the drop-down menu. |
|Enterprise |The report generated contains CARs from the specified Enterprise. |
| | |
| |Select the Enterprise from the drop-down menu. |
|Leading/Owning Site |The report generated contains CARs with the specified Owning Site. |
| | |
| |Select the Owning Site from the drop-down menu. |
|Requester |The report generated contains CARs with the specified Requester. |
| | |
| |To choose the Requester, click[pic] A pop-up window appears with search criteria based|
| |on the Requester ID or Requester Name. |
| |Enter the Requester ID or Requester Name and click Submit. To view all records, leave |
| |the fields blank and click Submit. The number of records found is displayed and a |
| |table is updated with the search results. |
| |Select the Requester by clicking the Name hyperlink. |
|Coordinator/SPOC |The report generated contains CARs with the mentioned Coordinator or SPOC. |
| | |
| |To choose the Coordinator/ SPOC, click[pic]. A pop-up window appears with search |
| |criteria based on the SPOC ID or SPOC Name. |
| |Enter the SPOC ID or SPOC Name and click Submit. To view all the records, leave the |
| |fields blank and click Submit. The number of records found is displayed. A table is |
| |updated with the search results. |
| |Select the Coordinator/ SPOC by clicking the Eid hyperlink. |
|Owner |The report generated contains CARs with the specified Owner. |
| | |
| |To choose the Owner, click[pic]. A pop-up window appears with search criteria based on|
| |the Owner ID/Supplier Code or Owner Name. |
| |Enter the Owner ID/Supplier Code or Owner Name and click Submit. To view all records, |
| |leave the fields blank and click Submit. The number of records found is displayed. A |
| |table is updated with the search results. |
| |Select the Owner by clicking the Eid hyperlink. |
|Status |The report generated contains CARs with the specified Status. |
| | |
| |Select the Status from the drop-down menu. |
|Type |The report generated contains CARs with the specified Type. |
| | |
| |Select the Type from the drop-down menu. |
|Elements |The report generated contains CARs with the specified Elements. |
| |Elements are the AS9100, ISO9000 Standards and other specifications for which the CAR |
| |is issued. |
| | |
| |Select the Elements from the drop-down menu. |
|Ignore Selections |When this check box is selected, ignore the selections made. |
To customize the report, click Additional Filters, see detailed Additional Filters section below.
To select the fields to be displayed in the customized report, see Field Selection.
[pic]Note
• If fields have not been selected from the Field Selection page before clicking Accept, a pop-up message appears.
[pic]
Additional Filter
To Specify the Filter Conditions:
1. Select the AND or OR logical condition from the drop-down menu.
2. Select the field from the drop-down menu, for the AND operation or the OR operation, for the data generated from Quick Filter.
3. Select a relation operator from the drop-down menu. It specifies the relational condition of the value of the field selected in Step 2.
4. Enter the value of the field selected in Step 2 to which the relational condition in Step 3 must match.
5. Click Add.
6. Select the fields to be displayed in the customized report using Field Selection.
|Field |Description |
| [pic] |Select the logical conditions AND or OR from the drop-down menu. |
| |The field names can be CAR ID, CAR Status, Owner Name, etc. |
|[pic] |Select the field name from the drop-down menu. |
| |Select one of the relational operators from the drop-down menu. |
|[pic] |The relational operators in the drop-down menu are: |
| |= |
| | |
| |> |
| |>= |
| |< |
| |Edit/View Supplier (Company).
|Field |Description |
|DUNS# |The unique ID of the Supplier. |
|Supplier Name |The Supplier's name. |
|Address #1 |The address consists of company name, street address and the |
| |building name. |
|Address #2 | |
|Address #3 | |
|City |The Supplier’s city. |
|State |The Supplier’s state. |
|Country |The nationality of the Supplier. |
|Zip/PostalCode |The zip or the postal code of the Supplier. |
|Phone |The contact number of the Supplier. |
|Fax |The fax number of the Supplier. |
|E-Mail |The e-mail address of the Supplier. |
|Mail Stop |The building mailing address of the Supplier. |
|Contact Name |The contact name of the Supplier. |
|Active |A flag indicating the user is active. |
|Secondary Contact Phone |The Secondary contact details of the Supplier. |
|Secondary Contact E-Mail | |
|Secondary Contact Name | |
2. A new window appears with search criteria based on the Supplier name or Supplier DUNS number (#).
3. Modify the Supplier information as required.
4. Click Update. A pop-up message appears indicating the Supplier record is updated successfully.
[pic]
5. Click OK.
Deleting a Supplier
The Supplier can be deleted by a user with the access level of Super User, SBU Administrator, Enterprise Administrator, or Site Administrator.
To Delete a Supplier:
1. Select the Supplier to be deleted.
i. Click Manage Supplier->Edit/View Supplier (Company). A new window appears with search criteria based on the Supplier name or Supplier DUNS.
ii. Enter the Supplier Name or Supplier DUNS and click Search. To view all records, leave the fields blank and click Submit. The number of records found is displayed, and a table is updated with the search results.
iii. Select the Supplier Name by clicking the DUNS hyperlink.
iv. The information about the Supplier displays.
2. Click Delete. A pop-up message appears asking for confirmation.
[pic]
3. To confirm Supplier deletion, click OK. A pop-up message appears indicating the Supplier is deleted successfully.
[pic]
4. Click OK.
[pic]Note
If the system is unable to delete the Supplier, modify the Supplier and mark as inactive.
1. Click Modify. A new window appears containing information about the Supplier.
2. Clear the Active check box.
[pic]
Adding a New Supplier User
A Supplier user can be added by a user with access level of Super User, SBU Administrator, Enterprise Administrator, or Site Administrator.
To Add a new Supplier User:
1. Click Manage Supplier->Add Supplier (User).
2. Search to verify the User does not already have an account in eCATS.
3. A new window appears with search criteria based on the Supplier name or Supplier DUNS.
4. Update the Supplier user information as required.
[pic]
5. Click Save. A pop-up message appears indicating the user record is created successfully.
[pic]
6. Click OK.
Modify Supplier User
The Supplier user information can be modified by a user with access level of Super User, SBU Administrator, Enterprise Administrator, or Site Administrator.
To Modify Supplier User information:
1. Click Manage Supplier->Edit/View Supplier (User).
[pic]
2. A new window appears with search criteria based on the input.
3. Modify the Supplier user information as required.
4. Click Update. A pop-up message appears indicating the User is modified successfully.
[pic]
5. Click OK.
Deleting a Supplier User
The Supplier User can be deleted by a user with access level of Super User, SBU Administrator, Enterprise Administrator, or Site Administrator.
To Delete a Supplier user:
1. Click Manage Supplier->Edit/View Supplier (User).
2. A new window appears with search criteria based on input.
3. Click Delete.
[pic]
.
4. A pop-up message appears asking for confirmation.
[pic]
5. To confirm that, click OK. A pop-up message appears indicating the Supplier User is deleted successfully
. [pic]
Manage Internal Users
[pic]How do I get there?
To go to User Maintenance from the Main Menu:
1. Click Admin.
2. Click Manage Internal Users.
The Site Administrator sets up the internal users through Add Internal Users.
The administrator can:
1. Add users.
2. Modify users.
3. Delete users.
4. Move users.
5. Reset Password.
6. Review Registration.
7. Associate Profiles.
The following table provides information regarding the fields in Manage Users accounts:
|Field |Description |
|User Type |The type of user. |
| |Select the user type from the drop-down menu. The user can be a Customer, Supplier, or an |
| |Internal User. |
|Customer Company (when User Type |The name of the Customer company. |
|is Customer) |Select the Customer company from the drop-down menu. |
|Supplier Company (when User Type |The name of the Supplier company. |
|is Internal User) |To select a Supplier company, click [pic]. A pop-up window appears with search criteria based |
| |on the Supplier Name, DUNS Number or Local Vendor Code. |
| |Enter the Supplier Name, DUNS Number or Local Vendor Code and click Submit. To view all |
| |records, leave the fields blank and click Submit. The number of records found is displayed. |
| |A table is updated with the search results. Select the user by clicking the Eid hyperlink. The|
| |User and other fields are automatically completed.. |
|Site (when User Type is Internal |This field is automatically completed based on the name of the User. |
|User) | |
|User |The name of the user who has requested an account. The user could be any of the following: |
| |Customer |
| | |
| |To select the User, click [pic]. A pop-up window appears with search criteria based on the ID|
| |or Last Name. |
| |Select one of the following: |
| |All Users |
| |All Customers |
| |Selected Customers Only |
| |Enter the ID or Last Name and click Submit. To view all records, leave the fields blank and |
| |click Submit. The number of records found is displayed. A table is updated with the search |
| |results. |
| |Select the user by clicking the Eid hyperlink. The User and other fields are automatically |
| |completed. |
| | |
| | |
| |Supplier |
| | |
| |To select the User, click [pic]. A pop-up window appears with search criteria based on the ID|
| |or Last Name. |
| |Select Current Site Only. |
| |Enter the ID or Last Name and click Submit. To view all records, leave the fields blank and |
| |click Submit. The number of records found is displayed. A table is updated with the search |
| |results. |
| |Select the user by clicking the Eid hyperlink. The User and other fields are automatically |
| |completed. |
| | |
| | |
| |Internal User |
| |To select the User, click [pic]. A pop-up window appears with search criteria based on the ID|
| |or Last Name. |
| |Enter the ID or Last Name and click Submit. To view all records, leave the fields blank and |
| |click Submit. The number of records found is displayed. A table is updated with the search |
| |results. |
| |Select the user by clicking the Eid hyperlink. The User and other fields are automatically |
| |completed depending on the selection. |
| | |
|User ID |The unique ID of the user. |
| |Employee ID for Internal Users |
| |DUNS # for Suppliers |
| |Atlas # for Customers |
|First Name |The first name of the user. |
|Last Name |The last name of the user. |
|User Title |The user’s title. |
|Country |The nationality of the user. |
|Phone |The contact number of the user. |
|Fax |The fax number of the user. |
|Mail Stop |The building mailing address of the user. |
|E-mail |The e-mail ID of the user. |
|LDAP EID |The user’s Honeywell ID |
|Active |Active status; checked indicates the user is active. |
Internal User
Internal users have the following additional fields associated with them to provide more information about their work:
|Fields |Description |
|Product Line |The product line along which the user works. |
|Cell |The cell of the user. |
|Department |The department to which the user belongs. |
Honeywell Employees are the internal users. To request an account in eCats, send name and EID to the corresponding site administrator.
User Level
Access can be assigned to several levels. The user-level is defined by clicking one of the following option buttons in the screen:
|User Level |Customer |Supplier |Internal User |
|Super User |No |No |Yes |
|SBU Administrator |No |No |Yes |
|Enterprise Administrator |No |No |Yes |
|Site Administrator |No |No |Yes |
|Coordinator/SPOC |No |No |Yes |
|Initiate & Respond |Yes |Yes |Yes |
|Respond Only |Yes |Yes |Yes |
|No Access |Yes |Yes |Yes |
Role of the User
The role of the Customer, Supplier and internal users are defined in the following table:
|Roles |Customer |Supplier |Internal User |
|Lead |Yes |Yes |Yes |
|Owner |Yes |Yes |Yes |
|Requester |Yes |Yes |Yes |
|Follow-up Reviewer |Yes |Yes |Yes |
|SPOC |No |No |Yes |
|Site Focal Point |No |No |Yes |
|Effectiveness Reviewer |Yes |Yes |Yes |
Command Buttons
The command buttons and their usage is defined in the following table:
|Buttons |Description |
|Save |Click this button to add a new user. |
|Update |Click this button to save the data entered. |
Adding a New User
The new user can be added by a user with the access level of Super User, SBU Administrator, Enterprise Administrator, or Site Administrator.
To add a new User:
1. Click ADMIN.
2. Click Manage Internal Users
3. Click Add Internal User
4. Enter the User ID and the new user's site and personal information.
[pic]
5. Select the user access level for the user.
[pic]
6. Click Save. A pop-up message indicates the new user is added successfully.
[pic]
7. Click OK.
[pic]Note
• For Internal Users:
▪ Enter the EID as the User ID.
▪ Select the Product Line, Cell, and Department from the respective drop-down menus.
• For Customers, the User ID is generated automatically after the personal information is entered and saved.
Modify User
User information can be modified by a user with the access level of Super User, SBU Administrator, Enterprise Administrator, or Site Administrator.
The administrator can modify all user information except the User ID. The administrator can also modify the user level and the roles of the user.
To Modify User information:
1. Click Manage Internal Users
2. Edit/View Internal User
3. Click Look Up
4. A pop-Up window appears, enter the user EID or last name to be modified
5. Click Search
6. Click on users EID
[pic]
7. Edit the information of the user.
[pic]
8. Edit the user access level.
[pic]
9. Click Update. A pop-up message appears indicating the user is modified successfully.
[pic]
10. Click OK.
[pic]Note
• The User ID cannot be modified.
• For Internal Users:
▪ Select the Product Line, Cell, and Department from the respective drop-down menu for the user.
Deleting a User
The user can be deleted by a user with the access level of Super User, SBU Administrator, Enterprise Administrator, or Site Administrator.
To Delete a User:
1. Click Manage Internal Users
2. Edit/View Internal User
3. Click Look Up
4. A pop-Up window appears, enter the user EID or last name to be
Deleted.
[pic]
5. Click Search
6. Click Delete
[pic]
7. A pop-up message appears indicating the user is Deleted successfully.
[pic]
Inactive a User
The user can be inactivated by a user with access level of a Super User, SBU Administrator, Enterprise Administrator, or a Site Administrator.
To Inactivate a User:
1. Click Manage Internal Users
2. Edit/ View Internal User
3. Click Look Up
4. A pop-Up window appears, enter the user EID or last name to be
Inactivated
[pic]
5. Click Search
6. Uncheck the Active checkbox
[pic]
7. Click Update
[pic]
8. Click Ok. To Delete the user, click OK
[pic]
9. Click Update. A pop-up message appears saying that the user is modified successfully.
[pic]
Move User
The Enterprise Administrator moves the users if they are transferred from one site to another. The CARs assigned to the user are not affected when the user changes site. The users are still responsible for the CARs assigned to them. The Enterprise Administrator of the old site must move the user from the old site to the new site.
To Move the User from the old site to the new site:
1. Click Manage Internal Users
2. Click Move user
3. Click on Look Up
4. A pop-Up window appears, enter the user EID or last name to be Moved.
[pic]
5. Click Search
6. Select the SBU Enterprise and Site Under Move To box
[pic]
7. Click Move, To move the user, click OK
[pic]
8. A pop-up message appears indicates the user is modified successfully.
[pic]
[pic]Note
The enterprise administrator of the new site cannot transfer the user from the old site to the new site.
Reset Password
Passwords can be reset by a user with the access level of a Super User, SBU Administrator, Enterprise Administrator or a Site Administrator.
To Reset Password:
1. Click Manage Internal User
2. Reset Password
3. Enter the Last or First name of the user
4. Click Search
[pic]
5. Click on radio button to select user.
6. To reset the password, click Reset Password. A pop-up message appears asking for confirmation.
[pic]
7. To confirm that you want to reset the password, click OK. A pop-up message appears indicating the password is reset.
[pic]
[pic]Note
When the administrator resets the password, the password is the same as your User ID.
This only resets the eCATS profile password, and does not reset the Honeywell ID password.
Review Registration
The registration review is done by the administrator for Suppliers and Customers. The administrator checks to determine if the requesting Supplier's company is already registered. See Supplier Maintenance.
If there is a registration request from a new Supplier, the company must be registered by the administrator before approving.
Compare the DUNS# with the data in the Select Supplier Company drop-down menu. The administrator approves the registration request if there is a matching DUNS#. The administrator will reject if the DUNS# does not match or is an invalid DUNS#.
[pic]How do I get there?
To go to Admin Tab from the Main Menu:
1. Click the Manage Supplier
2. Click the Review Registration
To Review the Registration process:
1. Click Review Registration. A new window appears.
[pic]
2. Select the Supplier from the drop-down menu.
3. Click Accept or Reject.
4. Click Approve to approve the Supplier or Reject to reject the Supplier.
Glossary
A
Reviewer: A person who assesses the actions taken by conducting an independent review to determine if the corrective actions have been effective in preventing recurrence.
C
Cause: A factor leading to an event.
Cause Analysis and Mistake Proofing (CAMP): Cause Analysis and Mistake Proofing is a process for finding the cause for an event and facilitating corrective action through mistake proofing to prevent recurrence of the event.
Cause Chain: A diagram showing the causes linked in sequence from the Event Question to the Root Cause.
Contributing Cause: The cause that contributed to an event, but by itself, would not have caused the event. It is the cause after the direct cause. For a simple problem, there may not be any contributing causes, for a complex problem there could be dozens.
Corrective Action: A set of planned actions implemented for the purpose of resolving the problem.
D
Direct Cause: The cause that directly resulted in an event. It is the first cause in the cause chain following the problem statement.
E
Event: A term used for a product failure, out of control process, audit findings, accident, Customer complaint, etc..
Event Question: A short, simple, concise, focused on one problem question beginning with "why". An event question does not indicate the cause of the event, state what to do next, or explain the event.
F
Follow Up: A review done by a team member to ensure all corrective actions were implemented as stated.
H
Honeywell ID: for internal users it is the EID number, for Suppliers and Customers it is the ID created using the Common Web Authentication (CWA).
N
Natural Team: A group of people having vested ownership of the problem to be solved.
P
Preventive Action: Preventive Action or Preventive Corrective Action are actions taken to prevent the recurrence of the event, focusing on Root Cause and Contributing Causes.
Q
Qualified Team: The natural team, including other individuals, who provide necessary resources to understand the problem or assist in the cause analysis and mistake proofing process.
R
Root Cause: The last cause in the cause chain analysis. Root Cause is not always the most significant cause in the chain and sometimes cannot be corrected easily or completely.
S
Secure Sockets Layer (SSL): A protocol developed by Netscape for transmitting private documents through the Internet. SSL uses a cryptographic system that uses two keys to encrypt data. The two keys used are: a public key known to everyone. a private or secret key known only to the recipient of the message.
Specific Action: Specific Action or Specific Corrective Actions are used to correct the Direct Cause and its effect, as a form of damage control. The purpose is to limit or stop the problem from getting worse and repairing whatever was affected. Specific Corrective Action does not prevent recurrence of the event.
V
Vested Ownership: Users of the process, controllers of the process, or people that rely on the process have a vested ownership of the process.
Index
A
Abbreviation 35
Accept 35, 58
Accepted
Lead selects 26
SPOC/Coordinator selects 26
Accepted 26
Accepted 35
Access eCATS 92
Access rights
user varies 85
Access rights 85
Accessed
CAR 35
History tab 31
Accessed 31
Accessed 35
Accessed 66
Accurate 31
Actions 26, 35
Actions specified 26
Active 66, 78, 85, 92
Active Acitve 90
Active site 66
Activities
SBU administrator 60
site administrator 60
Activities 60
Actual Date 41
Add
filter condition 46
record 78
supplier enter 78
Add 46
Add 60
Add 61
Add 63
Add 66
Add 78
Add New Comment 32
Add Supplier 78
Adding
Supplier 78
Adding 78
Additional Filter 42, 46
Additional filter creates 42
Address 66
Address1 66
Address2 66
Admin tab 85, 92, 93
Administration link 85, 92
Administration Overview 60
Administrator
responsibilities 60
suppliers 96
Administrator 60
Administrator 78
Administrator 85
Administrator 90
Administrator 96
Administrators
types 60
Administrators 60
Affected products 35
After changing
password 7
After changing 7
ALL CARS 58
All users 35
Allows eCATS 66
AM 31
Analysis
corrective actions 66
resolve 16
Analysis 16
Analysis 66
AND
Select 46
AND 46
Approval
SPOC/Coordinator 35
Approval 26
Approval 35
Approve
registration 96
Approve 35
Approve 96
Approved 35, 96
Approved check box
select 96
Approved check box 96
Approving 96
Assign
Owner 9
Assign 9
Assign team members
resolve 33
Assign team members 33
Assigned
product requiring corrective 16
Assigned 16
Assigned 31
Assigned 33
Assigned 35
Assigned 66
Assigned To 92
Assigned User ID
Enter 7
Assigned User ID 7
Assignment 35, 39
Assignment tab 33, 39
Atlas 85
Attached documents 41
Attachments 9
Audit 41
Auditor 41
Auditor Information
Remarks 35
Auditor Information 35
Authentication 7
Authority 33
Automated 31, 41
Automated e-mails 31
Automatically 35, 66
Automatically inserted 35
B
Back
Internet Explorer 58
previous 58
Back 58
Back 66
Based
ID 90
supplier 78
Supplier DUNS 66
Based 66
Based 78
Based 90
Based on CAR 35
Behalf 33
Belong
User ID 7
Belong 7
Belong 33
Blank 78, 90
BLK 46
Blue Print Revision 16
Board approval
product requiring corrective 16
Board approval 16
Board quantity
product requiring corrective 16
Board quantity 16
Board reference 16
Browse 42, 58
Browse Export 42
Browse Export Overview 42
Browse/Export 42
Building 66, 78
Building mailing 78
By Type 58
C
C/A
Select 35
C/A 35
Calendar opens 16
Cancel
record 78
Cancel 35
Cancel 78
CAR
access 35
Creating 39
duration 39
exit 35
information regarding 32
initiate 33
initiated 31
Initiating 31, 33
Lead/Requester approves 35
number 58
Owner 33
quit 33
resolve 35
resolving 9
respond 35
Responding 31, 35
select 33
SPOC approves 35
stage 32
CAR 9
CAR 16
CAR 26
CAR 31
CAR 32
CAR 33
CAR 35
CAR 39
CAR 58
CAR 60
CAR 92
CAR 92
CAR BY CAR 58
Car changed 31
CAR changes
Status 35
CAR changes 35
CAR consists
Initiating 33
Responding 35
CAR consists 33
CAR consists 35
CAR effectively
resolving 32
CAR effectively 32
CAR Exportable 66
CAR ID 9, 39, 46
CAR ID hyperlink 35, 39
CAR Initiation 31
CAR Resolution cycle 35
CAR Status 9, 46
CAR TYPE 33, 46
CAR Type hyperlink
obtain 58
CAR Type hyperlink 58
CARS 66
CARs assigned
respond 35
CARs assigned 35
CARs issued
number 58
type 58
CARs issued 58
CARs issued per
number 58
CARs issued per 58
Categories
following 33
Categories 33
Category 35
Cell
Delete 66
The description 66
Cell 60
Cell 66
Cell Code 66
Cell record 66
Cell Text 66
Change
following 31
password 7
team members 35
Change 7
Change 31
Change 35
Change History 31
Changing Password 7
Characters 66
Check 96
Check box
Clear 78, 90
Select 35, 66
Check box 35
Check box 66
Check box 78
Check box 90
Check box adjacent
selecting 61, 62
Check box adjacent 61
Check box adjacent 62
Check box Check When Complete
select 35
Check box Check When Complete 35
Check boxes
Select 33
Check boxes 33
Checked signifies 78
Checks
effectiveness 41
Checks 41
Choosing
Type 33
Choosing 33
City 66
Clarification 16
CLD 35
Clear
check box 78, 90
Clear 78
Clear 90
Clear All 46
Click Here To Add hyperlink 66
Clicking
DUNS hyperlink 78
Eid hyperlink 90
Search icon 35
Clicking 35
Clicking 78
Clicking 90
Clicking Accept 46
Clicking Change Password 7
Clicking Exit 33
Clicking Locate CAR 32
Clicking Save 33
Close 58
Code
Select 66
Code 33, 60
Code 66
Code List selected
Depending 66
Code List selected 66
Code Lists
Select 66
Code Lists 66
Comment 32
Comments 32, 35
Commercial - Qty Inspected 16
Communicate 60
Company 33
Compare
DUNS 96
Compare 96
Completed 35
Conduct 16
Confirm
deletion 66
password 7
Confirm 7
Confirm 66
Confirm 78
Confirmation 78
Confirmation appears
asking 66
Confirmation appears 66
Consecutive 31
Consists 66, 78
Contact
SPOC 7
Contact 7
Contact 78
Contact Name 78
Contain
actions 35
event 35
Contain 35
Contain 66
Contains 46, 78
Contents 31
Contract 16
Contributing 35
Coordinator Disposition 35
Coordinator/SPOC 85
Corrective 39, 41
Corrective Action Request 9
Corrective actions
analysis 66
Corrective actions 9, 39, 41, 60
Corrective actions 66
Corresponding 31
Corresponding incident occurred 31
Country 66
Create
folder named macrocsv 58
Create 58
Create 60
Created
product requiring corrective 16
Created 16
Created successfully 78
Ctrl 48
Cumulative Turn Time 31
Customer 16, 33, 85
Customer MRB Approval 16
Customer MRB Reference 16
Customer Part 16
Customers 7, 60, 85, 96
Customers Only 85
Customize
supplier lists 60
Customize 60
Customize Code Lists 66
Customize drop-down menu 66
Customize Supplier Lists 66
Customize Supplier Lists allows 66
Customized 46
Customizing
lists 66
Customizing 60
Customizing 66
D
Data Maintenance 32, 33, 35, 39
Data Maintenance>Assignment tab 66
Date Code 16
Date field 41
Days 35
Dd-mmm-yyyy format 16
Decide 35
Default
local customization overrides 66
Default 33, 35
Default 66
Defect
Requester finds 33
Defect 33
Defined contact 66
Definition 66
Delete
Cell 66
Department 66
Product Line 66
record 78
SBU codes 60
selected filter condition 46
site IDs 60
want 78
Delete 46
Delete 60
Delete 61
Delete 66
Delete 78
Delete customers 60
Delete hyperlink 66
Delete product 60
Delete suppliers 60
Delete users 60
Deleted 66, 78
Deleted successfully 66, 78
Deleting
User 92
Deleting 92
Deleting 92
Deletion
confirm 66
Deletion 66
Department
Delete 66
The description 66
Department 66
Department 85
Department Code 66
Department Text 66
Depending
Code List selected 66
Depending 66
Description
Enter 33
Description 16, 31
Description 33
Description 46
Description 66
Description 78
Details
Enter 33
following 31
Owner reviews 35
supplier 66
Details 16
Details 31
Details 33
Details 35
Details 66
Develop metrics 60
Difference 31
Direct
Enter 35
Direct 35
Directory 58
Displayed 7, 31, 33, 46, 58, 66, 78, 90, 96
Displayed depending
selection 78
Displayed depending 78
Displays 61, 62
Disposition 31, 41
Documents 33, 41
Does Not Contain 46
Download Data hyperlink 58
Download Template hyperlink 58
Downloaded template
open 58
Downloaded template 58
Drill Down 58
Drill Down By Month 58
Drive 58
Drop 46
Drop-down menu 33, 46, 90, 96
Drop-down menus 66
Due 35
DUNS
Compare 96
DUNS 78, 85
DUNS 96
DUNS hyperlink
clicking 78
DUNS hyperlink 78
Duration
CAR 39
Duration 39
E
ECATS
Enter 7
Lead/Requester logs 33
Logging 7
ECATS 7
ECATS 33
ECATS 60
ECATS 85
ECATS Sign In>Main Menu>e-CATS Contacts 7
ECATS tool
Manage 60
ECATS tool 60
ECATS users 60
Effectiveness
checks 41
Effectiveness 35
Effectiveness 41
Effectiveness 85
Effectiveness auditor 41, 85
Effectiveness auditor logs 41
Effectiveness reviews 41
Efficiency 66
EID 85
Eid hyperlink
clicking 90
Eid hyperlink 85
Eid hyperlink 90
Eliminating
unnecessary details 42
Eliminating 42
E-mail 7, 33, 35, 78
Email History 31
E-mail ID
supplier 78
E-mail ID 78
E-mail notification 33
Email Password opens 7
Employee ID 85
Enter
actions 35
assigned User ID 7
description 33
details 33
Direct 35
eCATS 7
event 35
Event Date 33
ID 90
Login Page 7
modified 62
modified strategic 61
site specific 66
Supplier DUNS 66
Supplier Name 78
User ID 7
Enter 7
Enter 16
Enter 33
Enter 35
Enter 46
Enter 61
Enter 62
Enter 66
Enter 78
Enter 90
ENTERPRISE 62, 63, 66
Enterprise Administrator 60, 67, 85, 92, 93
Enterprise Code 62, 63
Enterprise Maintenance 62, 63
Enterprise Maintenance Administrator 62
Enterprise Name
modify 62
Select 62
Enterprise Name 62
Event
contain 35
Enter 35
Event 33
Event 35
Event 39
Event Category/Severity 33
Event Code
Select 33
Event Code 33
Event Code 66
Event Date
enter 33
Event Date 33
Event Question 35
Event Type 33
Events
Summary 58
Events 58
Excel file 58
Excel format 48
Excel Report 58
Except
User ID 90
Except 90
Executed differently 33
Exist 58
Exit
CAR 35
want 78
Exit 35
Exit 78
Expected Time Frame 35
EXPORT TO WORD 58
External Approval
Waiting 35
External Approval 35
External Disposition 31
F
Fax 78
Field
selecting 48
Field 48
Field Selection 42, 48
Field Selection tab 46
Filter 42, 46
Filter condition
add 46
Select 46
Filter condition 46
Filter Conditions
Specify 46
Filter Conditions 42
Filter Conditions 46
Filters 42, 58
Final Requestor Approval
Waiting 35
Final Requestor Approval 35
Final/Rqst 31
Finding
led 35
Finding 35
Finding Event tabs 35
Finding relates 16
Finding/Event description 33
Finding/Event tab 33
FNS 35
Focal 60
Folder named macrocsv
Create 58
Folder named macrocsv 58
Following option buttons 85
Follows
categories 33
changes 31
details 31
formats 58
steps 33, 35
Follows 9
Follows 31
Follows 33
Follows 35
Follows 41
Follows 58
Follows 60
Follows 66
Follows 85
Follow-up 35, 41, 85
Follow-up auditor 41, 85
Follow-up auditor logs 41
Follow-up Code 35, 41
Follow-up Disposition 31
Follow-up Review 35, 41
Followup Review Phase 9
Follow-up tab
passes 35
transfers 35
Follow-up tab 35
Follow-up tab 41
Forgot Password 7
Formats
following 58
Formats 58
Forms 58
Function/department 33
G
Generated 46, 58
Government - Qty Rejected 16
Granularity 66
Guidance 66
H
Hardware
track 16
Hardware 16
Hardware product
print 16
rejected 16
Hardware product 16
History 31
History tab
access 31
History tab 31
Honeywell 85
Honeywell Employee 33
Honeywell Employees 7, 33, 85
Honeywell Part 16
HTML Data Extract 58
Html format 48
HTML Report 58
I
ID
based 90
Enter 90
supplier 78
ID 16, 66
ID 78
ID 90
If
owner 31
If 31
Incase 35
Incremental
total 31
Incremental 31
Incremental Turn Time 31
Incremented 35
Indicates
Quality System Element 16
Indicates 16
Indicates 35
INF document 16
Information 41
Information regarding
CAR 32
Information regarding 32
Initiate
CAR 33
Initiate 33
Initiate 85
Initiate New CAR 33
Initiated
CAR 31
Initiated 31
Initiated 33
Initiated By 9, 31
Initiated CAR
Save 33
Initiated CAR 33
Initiated Date 31
Initiating
CAR 31, 33
CAR consists 33
Initiating 31
Initiating 33
Initiation 33
Inputs
provide 35
Inputs 35
INS 16
Inspected 16
Instances 33
Instructions 58
Internal 9, 33, 39, 46, 85
Internal Honeywell Employee 33
Internal repair 16
Internal users 60, 85
Internet Explorer
Back 58
Internet Explorer 58
Invalid DUNS 96
Investigation 35
Investigation activities 35
ITR Nonconformance 16
ITR/nonconformance 16
L
Last Modified 61, 62
Lead
ask 33
Lead 9, 26, 31, 32
Lead 33
Lead 35
Lead 41
Lead 85
Lead Approval 35
Lead rejects 26
Lead selects
accepted 26
Lead selects 26
Lead Site 26
Lead Site Requester Disposition 26, 35
Lead/Requester 9, 26, 35, 41
Lead/Requester Approval
Waiting 35
Lead/Requester Approval 35
Lead/Requester approves
CAR 35
Lead/Requester approves 35
Lead/Requester chooses 41
Lead/Requester logs
eCATS 33
Lead/Requester logs 33
Lead/Requester logs 35
Led
finding 35
Led 35
Level 9, 63, 67, 92
Lists
customizing 66
Site Specific Table 66
Lists 31, 60
Lists 66
Local 58
Local customization overrides
default 66
Local customization overrides 66
Local vendor
assign 66
Local vendor 66
Locate CAR 32
Located 66
Logging
eCATS 7
Logging 7
Logical
Select 46
Logical 46
Login 7, 33, 41
Login Page
enter 7
Login Page 7
M
Macrocsv 58
Mail Stop 78
Mailed 7
Main menu 7, 33, 35, 42, 78, 92
Main Screen 61
Maintenance 66, 85, 92, 93
Manage
eCATS tool 60
Manage 60
Manage CAR Reviews 60
Manage users 60
Management
valuable 60
Management 60
Manager 33
Mandatory 33, 35, 78
Manually 16
Manufacturer 16
Manufacturing assembly document 16
Marked 33
Master
Select 66
Master 66
Master Table 66
Match 46, 66, 96
Matching DUNS 96
Mfg 16
Missing contact
Requester 16
Missing contact 16
Modified
enter 62
Modified 61
Modified 62
Modified 90
Modified strategic
enter 61
Modified strategic 61
Modified successfully 61, 62, 66, 90
Modify
Enterprise Name 62
record 78
SBU Code 61
SBU names 60, 61
site 60
Modify 60
Modify 61
Modify 62
Modify 66
Modify 78
Modify 90
Modify User Details 90
Monitor 60
Monitor CAR progress 60
Month 58
Month hyperlink
obtain 58
Month hyperlink 58
Month Report provides 58
Move users 60, 85, 93
MRB Quantity 16
MRB Reference 16
N
N/B 46
Name
product requiring corrective 16
supplier 78
Name 16
Name 41
Name 46
Name 60
Name 66
Name 78
Nationality
supplier 78
Nationality 78
Need
response 33
Need 33
NEW 33
New codes 66
New Follow-up 41
No Access radio button 90
Number
CARs 58
CARs issued 58
CARs issued per 58
product requiring 16
product requiring corrective 16
records 78, 90
Number 16
Number 58
Number 78
Number 90
O
Obtain
CAR Type hyperlink 58
Month hyperlink 58
Requester hyperlink 58
Obtain 58
OK 7, 35, 61, 62, 66, 78, 90
Opens
downloaded template 58
Windows Explorer 58
Opens 7
Opens 58
Opens 61
Opens 62
Opens 66
Opens 78
Opens 90
Opens 96
OR 16, 46
OR logical condition 46
ORed 46
Organization 33
OTH20060002-01 9
Owner
CAR 33
If 31
requesting 33
SPOC assigned 31
Owner 26
Owner 31
Owner 32
Owner 33
Owner 35
Owner 39
Owner 41
Owner 42
Owner Assigned 31
Owner Assignment
Waiting 31, 35
Owner Assignment 31
Owner Assignment 35
Owner details 66
Owner implement
actions 35
Owner implement 35
Owner incase
assign 33
Owner incase 33
Owner logs 35
Owner Name 46
Owner Response
Waiting 35
Owner Response 26
Owner Response 35
Owner Response 39
Owner Response 41
Owner reviews
details 35
Owner reviews 35
Owner Signoff 35
Owners 39
Owners response
reject 35
Owners response 35
Owning Site 26
Owning Site Assigned 31
Owning Site SPOC 35
P
P.O 16
Pane 7
Part Name 16
Passes
Follow-up tab 35
Passes 35
Password
After changing 7
change 7
confirm 7
Password 7
PDF Format 58
PEF 35
Pending Effectiveness Review 9, 35, 41
Pending Follow-up Review 35, 41
Perform 60
PFU 35
Planned actions implemented
set 16
Planned actions implemented 16
Postal 78
Press cancel 35
Prevent recurrences 35
Preventive Action 35
Previous
back 58
Previous 42
Previous 58
Previous selections
selection criteria 42
Previous selections 42
Print
hardware product 16
Print 16
Privilege 9, 33
PRO 16
Problem 16
Proceeding 33
Process Data 16, 33
Process Step 31
Processes 35, 85
ProdLine Code 66
ProdLine Text 66
Produced 58
Product 16, 33, 66, 85
Product Data 16, 33
Product Line
Delete 66
The description 66
Product Line 66
Product Line 85
Product Line record 66
Product Process 16
Product requiring
number 16
Product requiring 16
Product requiring corrective
assigned 16
board approval 16
board quantity 16
created 16
name 16
number 16
Product requiring corrective 16
Product/Process 35
Product/Process tab 33
Products 16
Program/System Name 16
Progress 33
Promise Dates 35
Prompts 7
Provide
inputs 35
Provide 31
Provide 35
Provide education 60
Purchase 16
Purpose
resolving 16
Purpose 16
Q
Quality System Element
indicating 16
Quality System Element 16
Quantity 16
Quick Filter 42, 46
Quit
CAR 33
Quit 33
R
Raised 35
Received Date 16
Record
add 78
cancel 78
delete 78
modify 78
save 78
Record 66
Record 78
Recorded 31
Records
number 78, 90
Records 78
Records 90
Re-enter 7
Refer 7
Reference Doc 16
Reference document
title 16
Reference document 16
Reference Document Rev 16
Reference Document Revision 16
Reference Document Title 16
Register 60, 96
Registered 96
Registration
approve 96
review 96
User ID 7
Registration 7
Registration 85
Registration 96
Registration requests 96
Reject
Owners response 35
Reject 35
Reject 41
Reject 96
Reject Tag 16
Rejected
hardware product 16
Rejected 16
Rejected 35
Rejected 41
Rejection Count 26, 35, 41
Rejection tag 16
Relation operator
Select 46
Relation operator 46
Relational condition
specifies 46
Relational condition 46
Relational operators 46
Remarks
Auditor Information 35
Remarks 35
Repair 16
Repair Order 16
Repeats 35
Report 42, 48
Report Format Selection 58
Reported By 42
Reports by selecting 42
Represented 58
Representing 33
Represents 66
Reproduced 58
Requester
missing contact 16
Requester 9
Requester 16
Requester 32
Requester 33
Requester 35
Requester 42
Requester 58
Requester 85
Requester finds
defect 33
Requester finds 33
Requester hyperlink
obtain 58
Requester hyperlink 58
Requesters 58
Requesting
owner 33
Requesting 33
Requesting supplier's 96
Required Response 33
Requirement 33
Requiring corrective 16
Reset password 60, 85
Resolve
analysis 16
assign team members 33
CAR 35
Resolve 16
Resolve 33
Resolve 35
Resolves
site problems 60
Resolves 60
Resolving
CAR effectively 32
purpose 16
Resolving 9
Resolving 16
Resolving 32
Respond
CAR 35
CARs assigned 35
Respond 35
Respond 85
Respond Only 9, 85
Responding
CAR 31, 35
CAR consists 35
Responding 31
Responding 35
Response
need 33
Response 9, 31
Response 33
Response 50
Response Date 31, 35
Response Phase 9
Response tab 26, 35
Response Turn Time 50
Responsibilities
administrator 60
Responsibilities 60
Responsible 93
Review
scheduling 41
Review 41
Review 85
Review registration 60, 85, 96
Reviews
registration 96
tabs 35
team members 35
Reviews 35
Reviews 96
Revision 16
Role
User 85
Role 85
Roles 85
Root Cause Code 66
Root causes
Select 35
Summary 58
Root causes 35
Root causes 58
S
Save
initiated CAR 33
record 78
Save 31
Save 33
Save 35
Save 61
Save 62
Save 66
Save 78
Save 90
Saved automatically 35
Saved successfully 33, 35
SBU 61, 63, 66, 67, 85, 92
SBU Administrator
activities 60
SBU Administrator 60
SBU Administrator 85
SBU codes
delete 60
modify 61
SBU codes 60
SBU codes 61
SBU codes 63
SBU Maintenance 61, 63, 67, 92
SBU Maintenance Administrator 61, 63, 67, 92
SBU names
Modify 60, 61
Select 61
SBU names 60
SBU names 61
Scheduled Date 41
Scheduling
review 41
Scheduling 35
Scheduling 41
Search
Supplier 78
Search 66
Search 78
Search criteria 66, 78, 90
Search icon
clicking 35
Search icon 35
Search option 33
Search results 78, 90
Select
AND 46
approved check box 96
AS9100A/ISO9000 16
C/A 35
CAR 33
check box 35, 66
check box Check When Complete 35
check boxes 33
Code Lists 66
codes 66
Enterprise Name 62
Event Code 33
filter condition 46
logical 46
master 66
relation operator 46
Root Cause 35
SBU Name 61
supplier 66
Supplier Name 78
team members 35
Type 33
User Type 90
Select 16
Select 33
Select 35
Select 46
Select 58
Select 61
Select 62
Select 66
Select 78
Select 90
Select 96
Select Current Site Only 85
Select Excel Report 58
Select Explore 58
Select From Previously Saved Selections 42
Select HTML Data Extract 58
Select Save Target As 58
Select Supplier Company drop-down menu 96
Selected
transfer 66
Selected 46
Selected 66
Selected filter condition
delete 46
Selected filter condition 46
Selected signifies 78
Selecting
check box adjacent 61, 62
fields 48
Selecting 48
Selecting 61
Selecting 62
Selection
depending 85
displayed depending 78
Selection 48
Selection 78
Selection 85
Selection criteria
previous selections 42
Selection criteria 42
Sequence 9
Sequential Dash Number 9, 39
Serial 16
Set
14-AUG-2006 02 31
planned actions implemented 16
Set 16
Set 31
Sign 7
Single Point
Contact 9
Single Point 9
Single Point Of Contact 9
Site
active 66
Modify 60
Site 9
Site 60
Site 66
Site 67
Site 92
Site 92
Site Address
update 66
Site Address 66
Site Administrator
activities 60
Site Administrator 9
Site Administrator 60
Site Administrator 85
Site Administrator 92
Site Administrator 92
Site IDs
delete 60
Site IDs 60
Site Maintenance tab 66
Site problems
Resolves 60
Site problems 60
Site specific
Enter 66
Site specific 66
Site Specific Table
lists 66
Site Specific Table 66
Sites 60
Sites contact 66
Sort 42, 48
Sort Selection 42
Specific 66
Specific Action/Containment 35
Specific codes 66
SPOC
contact 7
SPOC 7
SPOC 26
SPOC 32
SPOC 35
SPOC 41
SPOC 85
SPOC Approval
Waiting 35
SPOC Approval 35
SPOC approves
CAR 35
SPOC approves 35
SPOC assigned
owner 31
SPOC assigned 31
SPOC Disposition 31
SPOC rejects 26
SPOC/Coordinator
Approval 35
SPOC/Coordinator 26, 33
SPOC/Coordinator 35
SPOC/Coordinator logs 35
SPOC/Coordinator selects
accepted 26
SPOC/Coordinator selects 26
Stakeholders informing 41
Start 58
Status 33, 35, 41
Step 31, 33, 35, 46
Stored Selection 42
Strategic Business Unit 61, 66
Summary
Events 58
Root Causes 58
Types 58
Summary 58
Super User 60, 61, 63, 67, 85, 92
Supervisor 33
Supplier
Adding 78
based 78
details 66
e-mail ID 78
ID 78
name 78
nationality 78
search 78
select 66
Supplier 33, 39, 50
Supplier 66
Supplier 78
Supplier 85
Supplier 96
Supplier Company 33, 85
Supplier DUNS
based 66
Enter 66
Supplier DUNS 66
Supplier DUNS 78
Supplier enter
add 78
Supplier enter 78
Supplier lists
Customize 60
Supplier lists 60
Supplier Maintenance 78
Supplier Name
Enter 78
select 78
Supplier Name 66
Supplier Name 78
Supplier Name 85
Supplier record 78
Supplier resides
State 78
Supplier resides 78
Supplier site 66
Suppliers
administrator 96
Suppliers 7, 35, 60, 85
Suppliers 96
Systemic Action 35
T
Tab 31, 41, 42, 85
Tabs
reviews 35
Tabs 35
Tabs 42
Tabular format 58, 66, 96
Team 85
Team members
change 35
reviews 35
Select 35
Team members 32
Team members 35
Team members 41
Team members informing 41
Template 58
Text 66
The description
Cell 66
Department 66
Product Line 66
The description 66
Title
reference document 16
Title 16
Title 85
Title 90
Total
Incremental 31
Total 31
Track
hardware 16
Track 16
Transfer
selected 66
Transfer 66
Transfers
Follow-up tab 35
Transfers 35
Type
administrators 60
CARs issued 58
choosing 33
Select 33
Summary 58
Type 9
Type 33
Type 58
Type 60
Typical Order 35
U
Unnecessary details
eliminating 42
Unnecessary details 42
Update
Site Address 66
Update 66
Updated 61, 62, 78, 90
Updated successfully 78
Updates 60
Upload 66
User
Deleting 92
Role 85
set accounts 85
User 32, 39, 63, 67
User 85
User 92
User 92
User ID
Registration 7
User ID 7
User ID 85
User ID 90
User ID 93
User moves 85
User Type
Select 90
User Type 85
User Type 90
User Type 92
User Type 92
User varies
access rights 85
User varies 85
Users 7, 9, 33, 60, 66, 92, 93
User-specified 50
V
Verify 66
View Report hyperlink 58
Viewing 31
W
Waiting
External Approval 35
Final Requestor Approval 35
Lead/Requester Approval 35
Owner Assignment 31, 35
Owner Response 35
SPOC Approval 35
Waiting 31
Waiting 35
WEA 35
Weekly metrics 60
WFA 35
Wildcard character 41
Windows Explorer
open 58
Windows Explorer 58
WOA 35
WOR 35
WSA 35
X
XX replaces 39
Y
Yellow 9
[pic]
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
Related searches
- honeywell generator 22kw
- honeywell air purifiers replacement filters
- honeywell ultraviolet light treatment system
- honeywell water heater mixing valve
- who makes honeywell standby generators
- honeywell mixing valve problems
- honeywell damper motor
- honeywell am 1 series troubleshooting
- honeywell 3 way mixing valve
- honeywell am 1 series mixing valve manual
- honeywell thermostatic mixing valve problems
- honeywell pro series thermostat manual