MANUAL TROUBLESHOOTING VS GUIDED TROUBLESHOOTING
Manual troubleshooting depends on the technician's experience and diagnostic process, while guided troubleshooting uses predefined logic, alarms, measurements, and step-by-step instructions to lead the technician toward the fault. One puts the diagnostic decision-making with the person; the other shifts it into the system or procedure — and on an AGL system, both capabilities are needed.
At a Glance
| Feature | Manual Troubleshooting | Guided Troubleshooting |
|---|---|---|
| Approach | Technician-driven | Procedure/system-driven |
| Main input | Experience, drawings, measurements | Alarms, diagnostics, predefined logic |
| Troubleshooting path | Technician decides | Step-by-step guidance |
| Skill dependency | Higher | Lower to moderate |
| Diagnosis time | Can be longer | Usually faster |
| Consistency | Depends on technician | More consistent |
| Documentation | Often manual | Can be automatically/standardized |
| Fault isolation | Technician determines | System/procedure narrows fault |
| Typical tools | Multimeter, Megger, drawings | HMI/software + test instruments + diagnostic procedure |
| Best suited for | Complex/unusual faults | Known/repeatable fault conditions |
Manual Troubleshooting
Manual troubleshooting means the technician independently determines the fault using system drawings, wiring diagrams, equipment manuals, test instruments, alarm indications, visual inspection, previous experience, and logical elimination.
AGL LIGHT NOT WORKING
↓
CHECK CCR
↓
CHECK OUTPUT CURRENT
↓
CHECK CIRCUIT
↓
CHECK CABLE
↓
CHECK TRANSFORMER
↓
CHECK CONNECTOR
↓
CHECK FIXTURE
↓
IDENTIFY FAULT
The technician decides what to check next at every stage of the process.
Guided Troubleshooting
Guided troubleshooting provides a predefined diagnostic path, delivered through a CCR HMI, AGL control and monitoring system, maintenance software, diagnostic interface, alarm/fault database, or decision tree.
AGL LIGHT FAULT
↓
SYSTEM ALARM
↓
"CHECK CIRCUIT CURRENT"
↓
CURRENT NORMAL?
↙ ↘
YES NO
↓ ↓
CHECK CHECK CCR /
FIXTURE CIRCUIT
The technician follows the recommended steps rather than selecting the sequence independently.
Who Makes the Diagnostic Decisions
Both methods rely on a competent technician performing real tests — the difference is where the decision-making sits at each step of the process.
Manual
TECHNICIAN
↓
ANALYSES FAULT
↓
SELECTS TEST
↓
INTERPRETS RESULT
↓
SELECTS NEXT TEST
Guided
SYSTEM / PROCEDURE
↓
RECOMMENDS TEST
↓
TECHNICIAN PERFORMS TEST
↓
RESULT ENTERED / DETECTED
↓
NEXT STEP PROVIDED
Manual troubleshooting puts more diagnostic decision-making with the technician. Guided troubleshooting shifts more of the diagnostic logic into the system or procedure.
Series Circuit Fault
Suppose the monitoring system reports a series-circuit fault. The two approaches reach the same goal by different routes.
FAULT ↓ VISUAL INSPECTION ↓ CHECK CCR ↓ CHECK CURRENT ↓ CHECK CABLE ↓ CHECK TRANSFORMERS ↓ CHECK CONNECTORS ↓ CHECK FIXTURES
FAULT DETECTED
↓
STEP 1: Check CCR output
↓
NORMAL? YES
↓
STEP 2: Check circuit
resistance/current
↓
ABNORMAL? YES
↓
STEP 3: Check circuit
section
↓
STEP 4: Check isolation
transformer
↓
STEP 5: Check fixture
In the manual case, the technician uses experience to determine the sequence. In the guided case, the troubleshooting path is already defined by the system or procedure.
CCR Fault: Abnormal Output Current
Manual Troubleshooting
The technician checks, in whatever order judgement suggests:
- Input supply
- Output current
- Current transformer/sensing
- Control circuit
- Power electronics
- Protection system
- Connections
- Internal components
Guided Troubleshooting
OUTPUT CURRENT LOW
↓
CHECK INPUT SUPPLY
↓
INPUT OK?
↙ ↘
YES NO
↓ ↓
CHECK CHECK
OUTPUT SUPPLY
CURRENT
↓
CHECK CURRENT
SENSING
↓
CHECK CONTROL
SIGNAL
The guided path reduces unnecessary testing by narrowing the check sequence before the technician even picks up an instrument.
Experience vs Structure
Manual Troubleshooting
Requires stronger knowledge of AGL series circuits, CCR operation, electrical measurements, wiring diagrams, isolation transformers, protection systems, and fault behaviour.
Technician experience has a major influence on troubleshooting speed and accuracy.
Guided Troubleshooting
The technician still needs technical knowledge, but the system/procedure provides the diagnostic structure on top of it.
TECHNICIAN KNOWLEDGE
+
GUIDED LOGIC
↓
FASTER DIAGNOSIS
Guided troubleshooting does not eliminate the need for competent personnel — it structures how their competence is applied.
Finding the Fault on a Long Series Circuit
This is where guided troubleshooting is particularly useful, especially on a circuit with several sections downstream of the CCR.
CCR │ ├── Section 1 ├── Section 2 ├── Section 3 ├── Section 4 └── Section 5
CHECK 1 → CHECK 2 → CHECK 3 → CHECK 4 → FAULT Technician progressively tests each section.
FAULT ↓ SECTION 3 SUSPECTED ↓ CHECK SECTION 3 ↓ CONFIRM FAULT Monitoring data points straight to the section.
Where the monitoring system has suitable diagnostic information, guided fault localization can significantly reduce troubleshooting time on long circuits.
Manual vs Guided in Day-to-Day Maintenance
| Activity | Manual | Guided |
|---|---|---|
| Visual inspection | ✔ | ✔ |
| Multimeter testing | ✔ | ✔ |
| IR testing | ✔ | ✔ |
| Cable fault diagnosis | ✔ | ✔ |
| CCR fault diagnosis | ✔ | ✔ |
| Alarm interpretation | Technician | System/procedure assisted |
| Fault location | Experience-based | Logic-assisted |
| Step-by-step instructions | Not necessarily | Yes |
| Automatic recommendations | — | Possible |
| Technician judgement | High | Still required |
Where Each Method Wins and Falls Short
Flexible; suitable for unusual faults; works without advanced diagnostic software; makes full use of technician experience.
Time-consuming; technician-dependent; greater possibility of missed steps; results can vary between technicians.
Faster fault isolation; consistent procedure; easier for less-experienced technicians; reduces unnecessary testing; better standardization; can integrate alarms and monitoring data.
Depends on correct diagnostic logic; may not handle unusual faults well; requires suitable monitoring/software; still requires physical testing for confirmation.
Guided Troubleshooting Is Not Automatic Repair
Guided troubleshooting should not be confused with automatic repair. The monitoring system may identify or narrow down the problem, but the technician still needs to verify the fault using the appropriate test method before any repair takes place.
MONITORING SYSTEM
↓
DETECTS FAULT
↓
IDENTIFIES SUSPECTED AREA
↓
GUIDES TECHNICIAN
↓
TECHNICIAN TESTS
↓
FAULT CONFIRMED
↓
REPAIR
Full Engineering Parameters
| Parameter | Manual Troubleshooting | Guided Troubleshooting |
|---|---|---|
| Decision source | Technician judgement | System/procedure logic |
| Diagnostic path | Chosen step-by-step by technician | Predefined and followed by technician |
| Speed on known faults | Variable | Usually faster |
| Speed on unusual faults | Can be more effective | May not fit the logic tree |
| Consistency across technicians | Lower | Higher |
| Entry barrier for new staff | Higher | Lower |
| Dependence on software/monitoring | Low | High |
| Documentation trail | Manual/paper-based | Can be automatic/standardized |
| Requires physical confirmation test | Yes | Yes |
How to Remember the Difference
MANUAL TROUBLESHOOTING
↓
TECHNICIAN THINKS
↓
TECHNICIAN TESTS
↓
TECHNICIAN FINDS
GUIDED TROUBLESHOOTING
↓
SYSTEM/PROCEDURE GUIDES
↓
TECHNICIAN TESTS
↓
SYSTEM/LOGIC NARROWS
↓
FAULT FOUND
One-line distinction: manual troubleshooting is experience-driven, while guided troubleshooting is logic/procedure-driven.
Manual Troubleshooting vs Guided Troubleshooting
Manual troubleshooting is fault diagnosis performed by a technician using system knowledge, drawings, test instruments, observations, and experience to identify the root cause.
Guided troubleshooting is fault diagnosis supported by predefined decision logic, alarms, monitoring data, and step-by-step instructions that direct the technician toward the fault. For AGL systems, both capabilities matter: guided diagnostics for speed and consistency on known fault conditions, and manual troubleshooting capability retained for complex or unexpected faults the logic tree wasn't built for.
Neither approach replaces the other — a competent technician using guided tools for routine faults, with manual troubleshooting skill in reserve for the unusual ones, is the most resilient setup for AGL maintenance.
Engineering & Expert Notes
Write Down Your Own Sequence Anyway
MethodEven with guidance, note steps and results.
Do Not Switch Off Judgement
JudgementGuided logic cannot cover every case. Question results that look wrong.
Update the Guide From Findings
ImprovementFeed lessons back into procedures.
Train on Both Approaches
TrainingStaff need the principles as well as the tool.
Frequently Asked Questions
Manual troubleshooting depends on the technician's experience and diagnostic process to find the fault. Guided troubleshooting uses predefined logic, alarms, and step-by-step instructions to lead the technician toward the fault.
No. The technician still needs technical knowledge and still performs the physical tests. Guided troubleshooting supplies the diagnostic structure; it does not replace competent personnel.
No. The monitoring system or procedure may identify or narrow down the suspected fault area, but the technician still needs to confirm the fault with the appropriate test method before any repair is carried out.
Guided troubleshooting is usually faster for known or repeatable fault conditions because it narrows the check sequence up front. Manual troubleshooting can be more effective for complex or unusual faults that don't fit a predefined logic tree.
Manual troubleshooting typically relies on a multimeter, Megger/insulation tester, and wiring drawings. Guided troubleshooting adds an HMI or maintenance software layer with a diagnostic procedure or decision tree on top of the same test instruments.
Best practice is to use guided diagnostics for speed and consistency on known fault conditions, while retaining manual troubleshooting capability and technician experience for complex or unexpected AGL faults.
Governing Documents
For an actual project or maintenance program, always verify the current edition of the applicable documents.
ICAO Annex 14 / Aerodrome Design Manual
General framework for AGL system performance, monitoring, and maintenance expectations that both manual and guided troubleshooting approaches must satisfy.
CCR / Monitoring System Manufacturer Manuals
Define the alarm logic, HMI diagnostic screens, and recommended fault-finding sequences used in guided troubleshooting for a specific CCR or monitoring platform.
DGCA / AAI Requirements
For Indian airport projects, also verify applicable DGCA requirements, AAI requirements, airport-specific technical specifications, project drawings, and maintenance manuals.
Final Engineering Note
A guided procedure or decision tree is only as good as the logic behind it. It should be developed from the approved design, manufacturer documentation, and actual fault history — not assumed to cover every case.
Manual and guided troubleshooting are not competing methods — one is the fallback skill set, the other is the fast lane for faults the system already knows how to recognize.
Compare the Systems. Then Learn How to Engineer Them.
Understanding the difference between AGL systems is the first step. The next step is knowing how to design, install, test, commission and maintain them correctly.
Build Practical AGL Engineering Skills
Go deeper with structured training from Precision AGL Academy, covering:
Learn how AGL systems work as part of a complete airport lighting system, not just as individual components or configurations.