Contact Sales & After-Sales Service

Contact & Quotation

  • 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.
Drag & Drop Files, Choose Files to Upload You can upload up to 3 files.

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.

What is IPC-2547?

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 SpecificationDetails
Full TitleSectional Requirements for Shop-Floor Equipment Communication Messages (CAMX) for Printed Circuit Board Test, Inspection and Rework
Standard NumberIPC-2547
Release DateJanuary 2002
FrameworkCAMX (Computer Aided Manufacturing using XML)
Message FormatXML encoding schema
Domain FocusProduct and process quality
Required CompanionIPC-2541 (Generic Requirements)
Transport MechanismIPC-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:

CategoryEquipment TypesPurpose
InspectionSPI, AOI, AXIVisual and X-ray defect detection
TestICT, Flying Probe, Functional TestElectrical verification
ReworkRework Stations, Repair SystemsDefect 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

StandardFunctionRole in Framework
IPC-2501Message BrokerTransports all CAMX messages via HTTP/XML
IPC-2541Generic RequirementsBase XML schema and common events
IPC-2546Assembly SectionalScreen printer, P&P, reflow events
IPC-2547Test/Inspection SectionalAOI, 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:

BenefitDescription
ConsistencyAll equipment uses the same base event structure
ExtensibilityExtensions allowed without breaking compatibility
Vendor FlexibilityEquipment makers extend the standard as needed
Simplified IntegrationOne 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

IndicatorMeaningUsage
0-1Optional (zero or one occurrence)Common in IPC-2547
1-1Mandatory (exactly one occurrence)Required fields
0-nOptional, any numberMultiple defects/results
1-nMandatory, at least oneRequired 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 TypeDescriptionKey Data
InspectionStartBoard enters SPI systemBoard ID, timestamp
InspectionCompleteInspection finishedPass/fail, cycle time
PadResultIndividual pad measurementVolume, area, height, offset
DefectDetectedPaste deposit fails specificationDefect type, location, measurements

SPI Measurement Attributes

AttributeData TypeDescription
BoardIDStringUnique board identifier
PadLocationStringReference designator + pad ID
PasteVolumeFloatMeasured volume (mm³ or %)
PasteAreaFloatCoverage area (mm²)
PasteHeightFloatDeposit height (μm)
VolumeSpecFloatTarget specification
OffsetXFloatX-direction offset
OffsetYFloatY-direction offset
ResultEnumPass, Fail, Marginal

SPI Defect Categories

Defect TypeDescription
InsufficientPasteVolume below minimum threshold
ExcessPasteVolume above maximum threshold
BridgePaste connecting adjacent pads
OffsetPaste misaligned from pad
SmearPaste smeared across pad area
NoDepositMissing 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

CategoryEventsPurpose
Board TrackingBoardEntered, BoardExitedLine throughput tracking
Inspection ControlInspectionStart, InspectionCompleteCycle management
ResultsBoardPass, BoardFail, ComponentResultPass/fail determination
DefectsDefectDetected, DefectClearedIndividual defect reporting
ImagesImageCaptured, ImageStoredDefect image reference

AOI Defect Types Supported

IPC-2547 supports the standard AOI defect classifications:

Defect CategorySpecific Defects
Component PresenceMissing, Extra, Wrong Part
Component PositionShifted, Rotated, Skewed, Tombstone
Component OrientationPolarity Reversed, Upside Down
Solder JointInsufficient, Excess, Bridge, Cold Joint
Lead DefectsLifted, Bent, Damaged, Missing
PCB DefectsContamination, Damage, Foreign Material

AOI Defect Event Attributes

AttributeTypeDescription
EventTypeStringDefectDetected
TimestampDateTimeDetection time
EquipmentIDStringMachine identifier
BoardIDStringBoard serial number
RefDesignatorStringComponent location (e.g., C125)
DefectTypeEnumMissing, Bridge, Tombstone, etc.
DefectCodeStringVendor-specific code
ComponentPNStringExpected part number
ConfidenceFloatDetection confidence (%)
ImageRefStringReference to captured image
XLocationFloatDefect X coordinate
YLocationFloatDefect 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 TypeDescription
XrayInspectionStartBoard enters X-ray system
XrayInspectionCompleteInspection cycle finished
JointResultIndividual solder joint analysis
VoidDetectedVoid exceeds specification
HeadInPillowDetectedHIP defect identified

AXI-Specific Attributes

AttributeTypeDescription
ComponentRefStringBGA/QFN reference designator
BallLocationStringRow/column identifier (e.g., A1, B3)
VoidPercentageFloatVoid area as % of joint
VoidSpecFloatMaximum allowed void %
JointVolumeFloatCalculated solder volume
JointShapeEnumNormal, Collapsed, Bridged, Open
TomographySliceInteger3D 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.

ICT Event Types

Event TypeDescription
TestStartTest sequence initiated
TestCompleteAll tests finished
TestAbortedTest terminated early
ComponentTestIndividual component result
ShortTestShort circuit detection
OpenTestOpen circuit detection
MeasurementResultAnalog measurement value

ICT Result Attributes

AttributeTypeDescription
BoardIDStringBoard identifier
TestProgramStringProgram name/version
FixtureIDStringTest fixture identifier
TotalTestsIntegerNumber of tests executed
PassedTestsIntegerTests passed
FailedTestsIntegerTests failed
TestTimeFloatTotal execution time
FirstFailureStringFirst failing test name

Component Test Attributes

AttributeTypeDescription
RefDesignatorStringComponent location
TestTypeEnumResistance, Capacitance, Inductance, Diode
NominalValueFloatExpected value
MeasuredValueFloatActual measurement
ToleranceFloatAcceptable deviation (%)
UnitsStringOhms, Farads, Henries
ResultEnumPass, Fail, Marginal

Read more IPC Standards:

Functional Test Events in IPC-2547

Functional testing verifies that the assembled board operates correctly as a complete system under powered conditions.

Functional Test Event Types

Event TypeDescription
FunctionalTestStartPower applied, test initiated
FunctionalTestCompleteTest sequence finished
FunctionPassSpecific function verified
FunctionFailFunction did not meet specification
MeasurementResultOutput voltage, timing, current

Functional Test Attributes

AttributeTypeDescription
TestSequenceStringTest program identifier
PowerVoltageFloatApplied supply voltage
StimulusStringInput signal description
ExpectedResponseStringExpected output
ActualResponseStringMeasured output
WithinSpecBooleanPass/fail status
MarginFloatDistance 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 TypeDescription
ReworkStartRepair operation initiated
ReworkCompleteRepair operation finished
ComponentRemovedComponent desoldered from board
ComponentReplacedNew component installed
SolderTouchUpManual solder correction
ReworkVerifiedPost-repair inspection passed
RetestRequiredBoard needs re-inspection

Rework Event Attributes

AttributeTypeDescription
BoardIDStringBoard being reworked
OriginalDefectStringReference to detected defect
ReworkActionEnumRemove, Replace, Reflow, TouchUp
RefDesignatorStringComponent location
OldComponentPNStringRemoved component part number
NewComponentPNStringReplacement component part number
OperatorIDStringTechnician identifier
ReworkStationStringEquipment used
ReworkTimeFloatDuration of repair
VerificationResultEnumPass, Fail, Retest

Why Rework Tracking Matters

For high-reliability applications, rework documentation is often a contractual or regulatory requirement:

IndustryRework Documentation Requirement
AerospaceAS9100 requires full traceability
MedicalFDA 21 CFR Part 820 mandates records
AutomotiveIATF 16949 requires process control
MilitaryMIL-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

ApplicationHow IPC-2547 Enables It
Real-Time SPCStandardized data feeds statistical process control
Defect ParetoUnified defect codes enable accurate analysis
First-Pass YieldConsistent pass/fail across all equipment
Closed-Loop ControlInspection data adjusts assembly parameters
TraceabilityBoard-level quality history
Root Cause AnalysisCorrelate defects across process steps

Defect Correlation Example

With standardized IPC-2547 data from SPI, AOI, and ICT:

AnalysisData SourcesInsight
Paste-to-SolderSPI volume + post-reflow AOIWhich paste deposits cause joint defects
Placement-to-TestPre-reflow AOI + ICTComponent issues caught at test
Process DriftSPI trends over timeScreen printing degradation
Equipment ComparisonAOI results by lineLine-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

FeatureIPC-2547 (CAMX)IPC-2591 (CFX)
Release Year20022018
Message FormatXMLJSON
Transport ProtocolHTTP via IPC-2501 brokerAMQP (built-in)
Message BrokerExternal (required)Standardized (AMQP/MQTT)
Message DirectionEvents onlyEvents and commands
ExtensionsAllowed freelyRequires committee approval
Active DevelopmentMinimalVery active
Inspection CoverageComprehensiveEnhanced

When to Use Each Standard

ScenarioRecommended Standard
New inspection line installationIPC-2591 CFX
Existing CAMX infrastructureContinue IPC-2547, plan migration
Legacy equipment integrationIPC-2547 (broader legacy support)
Industry 4.0 smart factoryIPC-2591 CFX
Mixed old/new equipmentGateway 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

SourceURLNotes
IPC Storeshop.ipc.orgOfficial source, PDF download
ANSI Webstorewebstore.ansi.orgAlternative official source
Techstreettechstreet.comSubscription available
GlobalSpecstandards.globalspec.comEngineering resource

Related Standards to Consider

StandardPurposeWhen Needed
IPC-2541Generic CAMX requirementsAlways (required base)
IPC-2501CAMX message brokerFor message transport
IPC-2546Assembly equipment messagesComplete line coverage
IPC-2591Connected Factory Exchange (CFX)New implementations
IPC-A-610Acceptability of Electronic AssembliesDefect classification
IPC-7711/7721Rework and RepairRework procedures

Implementation Resources

ResourceDescription
IPC-CFX.orgCFX developer resources and SDK
Cogiscan Co-NECTCAMX/CFX connectivity platform
Aegis FactoryLogixMES with CAMX support
iTAC MESManufacturing 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.

Leave a Reply

Your email address will not be published. Required fields are marked *

Contact Sales & After-Sales Service

Contact & Quotation

  • 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.

Drag & Drop Files, Choose Files to Upload You can upload up to 3 files.

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.