Inquire: Call 0086-755-23203480, or reach out via the form below/your sales contact to discuss our design, manufacturing, and assembly capabilities.
Quote: Email your PCB files to Sales@pcbsync.com (Preferred for large files) or submit online. We will contact you promptly. Please ensure your email is correct.
Notes: For PCB fabrication, we require PCB design file in Gerber RS-274X format (most preferred), *.PCB/DDB (Protel, inform your program version) format or *.BRD (Eagle) format. For PCB assembly, we require PCB design file in above mentioned format, drilling file and BOM. Click to download BOM template To avoid file missing, please include all files into one folder and compress it into .zip or .rar format.
IPC-2547 Guide: XML Event Messages for Electronics Inspection and Test Equipment
If you’ve ever tried connecting AOI, SPI, ICT, and X-ray equipment to your MES system, you know the frustration. Every vendor has their own data format, their own defect codes, and their own way of reporting test results. Getting unified quality data from a mixed-vendor inspection line often means writing custom parsers for each machine type.
IPC-2547 was designed to solve exactly this problem. As the test and inspection sectional standard within the CAMX framework, IPC-2547 defines standardized XML event messages for inspection equipment, electrical testers, and rework stations. When your equipment speaks IPC-2547, your quality data flows into one consistent format—regardless of whether it came from a Koh Young SPI, an Omron AOI, or a Keysight ICT system.
This guide covers everything quality and test engineers need to know about IPC-2547: what it covers, how it fits within CAMX, the specific event types for each equipment category, and how it compares to the newer IPC-2591 CFX standard.
IPC-2547 is officially titled “Sectional Requirements for Shop-Floor Equipment Communication Messages (CAMX) for Printed Circuit Board Test, Inspection and Rework.” Released in January 2002, this standard defines XML-encoded event messages for quality verification equipment in electronics manufacturing.
IPC-2547 Specification
Details
Full Title
Sectional Requirements for Shop-Floor Equipment Communication Messages (CAMX) for Printed Circuit Board Test, Inspection and Rework
Standard Number
IPC-2547
Release Date
January 2002
Framework
CAMX (Computer Aided Manufacturing using XML)
Message Format
XML encoding schema
Domain Focus
Product and process quality
Required Companion
IPC-2541 (Generic Requirements)
Transport Mechanism
IPC-2501 (Message Broker)
The key thing to understand about IPC-2547 is its scope: it specifically covers equipment that verifies whether products were built correctly. This distinguishes it from IPC-2546, which covers assembly equipment that actually builds the product.
IPC-2547 Equipment Domain
IPC-2547 addresses three main categories of equipment:
Category
Equipment Types
Purpose
Inspection
SPI, AOI, AXI
Visual and X-ray defect detection
Test
ICT, Flying Probe, Functional Test
Electrical verification
Rework
Rework Stations, Repair Systems
Defect correction and board modification
The inclusion of rework equipment is unique to IPC-2547. This capability doesn’t exist in IPC-2546, making IPC-2547 essential for complete quality traceability.
How IPC-2547 Fits in the CAMX Framework
IPC-2547 doesn’t work in isolation. It’s part of the CAMX (Computer Aided Manufacturing using XML) framework developed by IPC in collaboration with the National Electronics Manufacturing Initiative (NEMI) Plug-and-Play Factory project.
CAMX Standards Architecture
Standard
Function
Role in Framework
IPC-2501
Message Broker
Transports all CAMX messages via HTTP/XML
IPC-2541
Generic Requirements
Base XML schema and common events
IPC-2546
Assembly Sectional
Screen printer, P&P, reflow events
IPC-2547
Test/Inspection Sectional
AOI, SPI, ICT, rework events
Think of it this way: IPC-2541 provides the foundation (generic event structure, equipment states, common attributes), while IPC-2547 extends that foundation with specific events for inspection and test equipment. IPC-2501 handles the actual message transport between equipment and host systems.
Why This Layered Approach Matters
The CAMX framework’s layered architecture provides several practical benefits:
Benefit
Description
Consistency
All equipment uses the same base event structure
Extensibility
Extensions allowed without breaking compatibility
Vendor Flexibility
Equipment makers extend the standard as needed
Simplified Integration
One protocol handles assembly and quality equipment
As noted in IEEE research on CAMX, “A key feature of the CAMX standards is that they are extensible, enabling the implementation of enhancements while maintaining backwards compatibility.”
IPC-2547 Event Structure and Cardinality
IPC-2547 follows the event structure defined in IPC-2541, but with specific cardinality rules for inspection and test messages.
Cardinality Indicators
Indicator
Meaning
Usage
0-1
Optional (zero or one occurrence)
Common in IPC-2547
1-1
Mandatory (exactly one occurrence)
Required fields
0-n
Optional, any number
Multiple defects/results
1-n
Mandatory, at least one
Required collections
Unlike IPC-2541 where all attributes are mandatory (1-1), IPC-2547 uses 0-1 to indicate optional fields. This flexibility accommodates different equipment capabilities—a basic AOI might not report confidence scores, while an advanced system might include AI-based detection probabilities.
Event Extensions
All IPC-2547 messages include an Extensions element, allowing vendors to add proprietary data without breaking standard compliance. This is one of CAMX’s major strengths: equipment manufacturers can include additional machine-specific information while maintaining interoperability.
Solder Paste Inspection (SPI) Events in IPC-2547
SPI systems inspect solder paste deposits immediately after screen printing. Since approximately 80% of PCB assembly defects originate from improper solder paste printing, SPI data is critical for process control.
SPI Event Types
Event Type
Description
Key Data
InspectionStart
Board enters SPI system
Board ID, timestamp
InspectionComplete
Inspection finished
Pass/fail, cycle time
PadResult
Individual pad measurement
Volume, area, height, offset
DefectDetected
Paste deposit fails specification
Defect type, location, measurements
SPI Measurement Attributes
Attribute
Data Type
Description
BoardID
String
Unique board identifier
PadLocation
String
Reference designator + pad ID
PasteVolume
Float
Measured volume (mm³ or %)
PasteArea
Float
Coverage area (mm²)
PasteHeight
Float
Deposit height (μm)
VolumeSpec
Float
Target specification
OffsetX
Float
X-direction offset
OffsetY
Float
Y-direction offset
Result
Enum
Pass, Fail, Marginal
SPI Defect Categories
Defect Type
Description
InsufficientPaste
Volume below minimum threshold
ExcessPaste
Volume above maximum threshold
Bridge
Paste connecting adjacent pads
Offset
Paste misaligned from pad
Smear
Paste smeared across pad area
NoDeposit
Missing paste deposit
SPI data becomes especially valuable when correlated with post-reflow AOI results—you can trace solder defects back to specific paste deposit issues.
Automated Optical Inspection (AOI) Events in IPC-2547
AOI systems perform visual inspection at multiple points in the SMT process: post-placement (pre-reflow) and post-reflow. IPC-2547 provides comprehensive event definitions for both scenarios.
AOI Event Categories
Category
Events
Purpose
Board Tracking
BoardEntered, BoardExited
Line throughput tracking
Inspection Control
InspectionStart, InspectionComplete
Cycle management
Results
BoardPass, BoardFail, ComponentResult
Pass/fail determination
Defects
DefectDetected, DefectCleared
Individual defect reporting
Images
ImageCaptured, ImageStored
Defect image reference
AOI Defect Types Supported
IPC-2547 supports the standard AOI defect classifications:
Defect Category
Specific Defects
Component Presence
Missing, Extra, Wrong Part
Component Position
Shifted, Rotated, Skewed, Tombstone
Component Orientation
Polarity Reversed, Upside Down
Solder Joint
Insufficient, Excess, Bridge, Cold Joint
Lead Defects
Lifted, Bent, Damaged, Missing
PCB Defects
Contamination, Damage, Foreign Material
AOI Defect Event Attributes
Attribute
Type
Description
EventType
String
DefectDetected
Timestamp
DateTime
Detection time
EquipmentID
String
Machine identifier
BoardID
String
Board serial number
RefDesignator
String
Component location (e.g., C125)
DefectType
Enum
Missing, Bridge, Tombstone, etc.
DefectCode
String
Vendor-specific code
ComponentPN
String
Expected part number
Confidence
Float
Detection confidence (%)
ImageRef
String
Reference to captured image
XLocation
Float
Defect X coordinate
YLocation
Float
Defect Y coordinate
Automated X-ray Inspection (AXI) Events in IPC-2547
X-ray inspection is essential for BGAs, QFNs, and other packages where solder joints are hidden from optical inspection. IPC-2547 includes specific events for X-ray-based quality verification.
AXI Event Types
Event Type
Description
XrayInspectionStart
Board enters X-ray system
XrayInspectionComplete
Inspection cycle finished
JointResult
Individual solder joint analysis
VoidDetected
Void exceeds specification
HeadInPillowDetected
HIP defect identified
AXI-Specific Attributes
Attribute
Type
Description
ComponentRef
String
BGA/QFN reference designator
BallLocation
String
Row/column identifier (e.g., A1, B3)
VoidPercentage
Float
Void area as % of joint
VoidSpec
Float
Maximum allowed void %
JointVolume
Float
Calculated solder volume
JointShape
Enum
Normal, Collapsed, Bridged, Open
TomographySlice
Integer
3D slice reference
For high-reliability applications (aerospace, medical, automotive), X-ray data provides the hidden joint verification that optical inspection cannot deliver.
In-Circuit Test (ICT) Events in IPC-2547
ICT systems verify component values and board connectivity by probing test points and measuring electrical characteristics. IPC-2547 defines events for both fixture-based ICT and flying probe testers.
Functional testing verifies that the assembled board operates correctly as a complete system under powered conditions.
Functional Test Event Types
Event Type
Description
FunctionalTestStart
Power applied, test initiated
FunctionalTestComplete
Test sequence finished
FunctionPass
Specific function verified
FunctionFail
Function did not meet specification
MeasurementResult
Output voltage, timing, current
Functional Test Attributes
Attribute
Type
Description
TestSequence
String
Test program identifier
PowerVoltage
Float
Applied supply voltage
Stimulus
String
Input signal description
ExpectedResponse
String
Expected output
ActualResponse
String
Measured output
WithinSpec
Boolean
Pass/fail status
Margin
Float
Distance to specification limit
Rework and Repair Events in IPC-2547
One of IPC-2547’s unique features is comprehensive coverage of rework and repair operations. This capability is critical for complete traceability and quality documentation.
Rework Event Types
Event Type
Description
ReworkStart
Repair operation initiated
ReworkComplete
Repair operation finished
ComponentRemoved
Component desoldered from board
ComponentReplaced
New component installed
SolderTouchUp
Manual solder correction
ReworkVerified
Post-repair inspection passed
RetestRequired
Board needs re-inspection
Rework Event Attributes
Attribute
Type
Description
BoardID
String
Board being reworked
OriginalDefect
String
Reference to detected defect
ReworkAction
Enum
Remove, Replace, Reflow, TouchUp
RefDesignator
String
Component location
OldComponentPN
String
Removed component part number
NewComponentPN
String
Replacement component part number
OperatorID
String
Technician identifier
ReworkStation
String
Equipment used
ReworkTime
Float
Duration of repair
VerificationResult
Enum
Pass, Fail, Retest
Why Rework Tracking Matters
For high-reliability applications, rework documentation is often a contractual or regulatory requirement:
Industry
Rework Documentation Requirement
Aerospace
AS9100 requires full traceability
Medical
FDA 21 CFR Part 820 mandates records
Automotive
IATF 16949 requires process control
Military
MIL-STD specifications
IPC-2547’s rework events provide the data structure needed to meet these requirements with automated documentation.
Quality Data Integration with IPC-2547
The real value of IPC-2547 emerges when inspection and test data flows into manufacturing execution systems (MES) and quality management systems (QMS).
Integration Applications
Application
How IPC-2547 Enables It
Real-Time SPC
Standardized data feeds statistical process control
Defect Pareto
Unified defect codes enable accurate analysis
First-Pass Yield
Consistent pass/fail across all equipment
Closed-Loop Control
Inspection data adjusts assembly parameters
Traceability
Board-level quality history
Root Cause Analysis
Correlate defects across process steps
Defect Correlation Example
With standardized IPC-2547 data from SPI, AOI, and ICT:
Analysis
Data Sources
Insight
Paste-to-Solder
SPI volume + post-reflow AOI
Which paste deposits cause joint defects
Placement-to-Test
Pre-reflow AOI + ICT
Component issues caught at test
Process Drift
SPI trends over time
Screen printing degradation
Equipment Comparison
AOI results by line
Line-to-line quality variation
IPC-2547 vs IPC-2591 CFX: Which Standard for Inspection Equipment?
The electronics industry is transitioning toward IPC-2591 Connected Factory Exchange (CFX), released in 2018 and now at version 2.0. Understanding the differences helps with technology decisions.
Technical Comparison
Feature
IPC-2547 (CAMX)
IPC-2591 (CFX)
Release Year
2002
2018
Message Format
XML
JSON
Transport Protocol
HTTP via IPC-2501 broker
AMQP (built-in)
Message Broker
External (required)
Standardized (AMQP/MQTT)
Message Direction
Events only
Events and commands
Extensions
Allowed freely
Requires committee approval
Active Development
Minimal
Very active
Inspection Coverage
Comprehensive
Enhanced
When to Use Each Standard
Scenario
Recommended Standard
New inspection line installation
IPC-2591 CFX
Existing CAMX infrastructure
Continue IPC-2547, plan migration
Legacy equipment integration
IPC-2547 (broader legacy support)
Industry 4.0 smart factory
IPC-2591 CFX
Mixed old/new equipment
Gateway bridging both
As one industry expert noted, “CFX is an emerging standard, and while it receives a lot of press, there are still very few real-life manufacturing implementations. Widespread future adoption is still uncertain.”
Where to Get IPC-2547 and Related Standards
Official Standard Sources
Source
URL
Notes
IPC Store
shop.ipc.org
Official source, PDF download
ANSI Webstore
webstore.ansi.org
Alternative official source
Techstreet
techstreet.com
Subscription available
GlobalSpec
standards.globalspec.com
Engineering resource
Related Standards to Consider
Standard
Purpose
When Needed
IPC-2541
Generic CAMX requirements
Always (required base)
IPC-2501
CAMX message broker
For message transport
IPC-2546
Assembly equipment messages
Complete line coverage
IPC-2591
Connected Factory Exchange (CFX)
New implementations
IPC-A-610
Acceptability of Electronic Assemblies
Defect classification
IPC-7711/7721
Rework and Repair
Rework procedures
Implementation Resources
Resource
Description
IPC-CFX.org
CFX developer resources and SDK
Cogiscan Co-NECT
CAMX/CFX connectivity platform
Aegis FactoryLogix
MES with CAMX support
iTAC MES
Manufacturing execution with CAMX
Frequently Asked Questions
What equipment types does IPC-2547 cover?
IPC-2547 covers three main equipment categories: inspection equipment (SPI, AOI, AXI), test equipment (ICT, flying probe, functional test), and rework/repair stations. This scope focuses specifically on quality verification equipment, distinguishing it from IPC-2546 which covers assembly equipment like screen printers, pick-and-place machines, and reflow ovens. Together, IPC-2546 and IPC-2547 provide complete SMT line coverage within the CAMX framework.
Do I need IPC-2541 to use IPC-2547?
Yes, IPC-2541 is mandatory. IPC-2547 is a sectional standard that extends IPC-2541’s generic requirements. The base XML schema, equipment state model, common event types, and extension mechanisms are all defined in IPC-2541. Without IPC-2541, you won’t have the foundation that IPC-2547 builds upon. Most equipment vendors implement both standards together as part of their CAMX compliance.
How does IPC-2547 handle vendor-specific data?
IPC-2547 includes an Extensions element in every event, allowing vendors to add proprietary information without breaking standard compliance. This is a significant strength of the CAMX framework—equipment manufacturers can include additional machine-specific attributes, custom defect codes, or enhanced measurement data while maintaining interoperability with standard-compliant systems. The extensions don’t require committee approval (unlike CFX).
Should new installations use IPC-2547 or IPC-2591 CFX?
For new installations, IPC-2591 CFX is generally the better choice. CFX offers modern technology (JSON format, AMQP transport), bidirectional communication (commands and events), a standardized message broker, and active development with regular updates. However, IPC-2547 remains relevant for integrating with legacy equipment, connecting to existing CAMX infrastructure, or working with MES systems that don’t yet support CFX. Many manufacturers run both standards during transition periods.
Can IPC-2547 data support regulatory compliance requirements?
Yes, IPC-2547 provides the data structure needed for regulatory compliance in industries like aerospace (AS9100), medical devices (FDA 21 CFR Part 820), and automotive (IATF 16949). The standard’s rework events are particularly valuable for maintaining the complete modification history that regulators require. Each defect detection, repair action, operator identification, and verification result can be captured in standardized format, enabling automated compliance documentation.
Conclusion
IPC-2547 remains a foundational standard for connecting inspection and test equipment in electronics manufacturing. By defining standardized XML event messages for SPI, AOI, X-ray, ICT, functional test, and rework equipment, this standard enables unified quality data collection regardless of equipment vendor.
The standard’s unique coverage of rework and repair operations fills a gap that IPC-2546 doesn’t address, making IPC-2547 essential for complete quality traceability. For manufacturers in regulated industries, this rework documentation capability alone justifies implementation.
While IPC-2591 CFX represents the future of factory communication, IPC-2547 continues serving manufacturers with existing CAMX infrastructure, legacy equipment, or integration requirements that CFX doesn’t yet address. Understanding both standards—and when to use each—helps quality engineers make informed technology decisions.
For any manufacturer serious about quality data integration, defect correlation, and traceability, IPC-2547 provides the standardized foundation that transforms inspection equipment from isolated data silos into a unified quality intelligence system.
Inquire: Call 0086-755-23203480, or reach out via the form below/your sales contact to discuss our design, manufacturing, and assembly capabilities.
Quote: Email your PCB files to Sales@pcbsync.com (Preferred for large files) or submit online. We will contact you promptly. Please ensure your email is correct.
Notes: For PCB fabrication, we require PCB design file in Gerber RS-274X format (most preferred), *.PCB/DDB (Protel, inform your program version) format or *.BRD (Eagle) format. For PCB assembly, we require PCB design file in above mentioned format, drilling file and BOM. Click to download BOM template To avoid file missing, please include all files into one folder and compress it into .zip or .rar format.