Educational familiarization only. This is original TechOpsBase learning content created from privately supplied legacy training and MSG-3 source material. It does not reproduce manufacturer pages, proprietary diagrams, task steps, numerical maintenance limits, dispatch criteria or controlled maintenance data. Current approved aircraft data, effectivity and operator procedures govern all aircraft work.
Resource profile
- Aircraft: Airbus A350 family
- ATA chapter: 38 — Water/Waste
- Resource: A350 ATA 38 Control, Indication and CAN Communication
- Level: Intermediate-to-advanced
- Status: Draft pending technical review
Learning objectives
- Explain distributed control.
- Trace PWIP/FAP data.
- Describe CIDS transport role.
- Recognize bus faults.
- Use BITE and message correlation.
1. Purpose and operational value
The control and indication architecture coordinates distributed smart components and presents usable status to ground and cabin users.
2. Architecture and system flow
The potable-water system uses a dedicated CAN bus and distributed smart-component logic.
The vacuum waste system uses its own buses and autonomous controllers.
CIDS transports data to FAP and supports configuration/software distribution but does not replace the local water/waste control logic.
3. Major components and functions
PWIP
Controls servicing and potable-water components. The component must receive the correct input, perform its intended function and provide a valid output or status. A maintenance diagnosis must separate loss of power, loss of communication, incorrect configuration, blockage or leakage, contamination, mechanical degradation and an upstream or downstream interface failure. Useful evidence includes command, feedback, quantity and local messages. Command, feedback and physical effect must agree before hardware is condemned.
PWS CAN bus
Connects smart water-system components. The component must receive the correct input, perform its intended function and provide a valid output or status. A maintenance diagnosis must separate loss of power, loss of communication, incorrect configuration, blockage or leakage, contamination, mechanical degradation and an upstream or downstream interface failure. Useful evidence includes bus health, node loss and communication faults. Command, feedback and physical effect must agree before hardware is condemned.
VTS buses/controllers
Coordinate toilets, tanks and vacuum equipment. The component must receive the correct input, perform its intended function and provide a valid output or status. A maintenance diagnosis must separate loss of power, loss of communication, incorrect configuration, blockage or leakage, contamination, mechanical degradation and an upstream or downstream interface failure. Useful evidence includes affected subsystem, bus and local BITE. Command, feedback and physical effect must agree before hardware is condemned.
CIDS Directors
Transport ATA 38 status/configuration to FAP and maintenance. The component must receive the correct input, perform its intended function and provide a valid output or status. A maintenance diagnosis must separate loss of power, loss of communication, incorrect configuration, blockage or leakage, contamination, mechanical degradation and an upstream or downstream interface failure. Useful evidence includes interface health, configuration and data availability. Command, feedback and physical effect must agree before hardware is condemned.
FAP Water/Waste page
Displays quantities, cautions, information and controls. The component must receive the correct input, perform its intended function and provide a valid output or status. A maintenance diagnosis must separate loss of power, loss of communication, incorrect configuration, blockage or leakage, contamination, mechanical degradation and an upstream or downstream interface failure. Useful evidence includes source data, page/HMI and message correlation. Command, feedback and physical effect must agree before hardware is condemned.
4. Normal operating sequence
1. Local control
ATA 38 controller or smart component executes the function.
2. Status collection
Local nodes report position, quantity and faults.
3. Data transport
CIDS carries selected information to FAP/CMS.
4. User action
PWIP or FAP sends allowed commands/preselection.
5. Control, monitoring and protection
A blank or wrong FAP page does not prove the local water/waste function is lost.
One lost CAN node can remove multiple related indications and commands.
6. Failure modes and maintenance reasoning
- One component communication fault: Node power, local electronics, wiring or connector.
- Whole PWS bus lost: Common power, CAN wiring or controller.
- FAP only lost: CIDS/HMI or interface.
- PWIP and FAP disagree: Data transport or display versus local measurement.
- Software/configuration issue: Incorrect load, mismatch or incomplete activation.
7. Interfaces with other aircraft systems
- ATA 44 CIDS/FAP.
- ATA 45 CMS/data loading.
- ATA 24 electrical power.
- Smart valves/pumps/sensors.
- Aircraft configuration data.
8. Practical maintenance scenarios
Local function works but FAP shows fault
Trace indication transport, not only component replacement.
Many PWS nodes lost together
Look for common bus/power.
New component not recognized
Check configuration/software and node identity.
9. Technician takeaways
- Local function and remote indication are separate layers.
- Use bus-fault grouping.
- Configuration follows replacement.
- Preserve BITE before reset.
Maintenance boundary
This resource explains architecture, operation, indications and system-level troubleshooting. It intentionally excludes removal/installation instructions, wiring-pin checks, maintenance limits, software part numbers, servicing quantities, inspection intervals and release-to-service criteria.
Review prompts
- What is the required system function?
- Which component commands, processes or physically performs it?
- Which power, fluid, pneumatic or data path is required?
- What command proves the function was requested?
- What feedback or physical effect proves correct operation?
- Which adjacent ATA system can create the same symptom?
- What evidence should be preserved before reset, draining, servicing or software action?
- What hygiene, electrical, pressure, network or safety boundary applies?
