iTech
Table of Contents
Using iTech
Introduction
Logging on
Interface
Dashboard
Editor
Context menus
Adding and Deleting Items
User Administration
Edit My Profile
User Management
Business Units
Users
Add a user
Password
Edit user profile
Default Roles
Active Projects
Historical Roles
Delete users
Logs
Project Access
System Configuration
User Types
User Roles
Edit classes and properties
Classes
Properties
Input validation
Custom reports
Languages
Deleted projects
System settings
Projects
My projects
Add a project
Project overview screen
Models
Model editor
Model tree
Adding nodes
Managing the model class
Equipment configurations
Context menu
Library
Parts Library
Procedure library
Adding and editing procedures
Rule library
Folder
Symptom
Editor
Equipment/instance selector
Properties tab
Extended properties tab
Parts tab
Fault modes
Procedures tab
Test tab
Generating runtime files
Using the runtime
Loading a model
What data is displayed?
Selecting a symptom
Troubleshooting
Performing tests
Other functions
Automated Learning
Project Locations
Diagnostic modeling
Diagnostic principles
Diagnostic logic
Troubleshooting techniques
Traditional methods
Optimization
iTech technique
Symptoms, alarms and error messages
Test procedures
Repair procedures
Expert knowledge and troubleshooting
Modeling
Functional breakdown
Serial and parallel modeling
Components
Parts
Time/cost to replace
Component type
Virtual links
Modeling tests
Test methods
Fully automated
Semi automated
Manual tests
Test time/cost
Procedures
Rules
Component/test status
Validating your model
Model instances
To properly display this page you need a browser with JavaScript support.
< Previous page
Next page >
Optimization
WHAT IS MOST IMPORTANT TO ALL BUSINESS WHEN IT COMES TO FAILURES?
TIME! MEAN-TIME-TO-REPAIR
Time to test
Time to replace
Not the total number of tests nor the sequence of tests, but TOTAL time taken is important.
iTech
Combines all the techniques
Includes TIME
Time is the most important
Copyright Remy InfoSource Pte Ltd 2020
