scope:

This standard establishes the requirements for the omnidirectional exchange of information between manufacturing processes and associated host systems for assembly manufacturing. This standard applies to communication between all executable processes in the manufacture of printed board assemblies - automated, semiautomated and manual - and is applicable to related mechanical assembly and transactional processes.

Purpose

With the growth and acceptance of digital modeling and practices in manufacturing, the lack of a holistic Industrial Internet of Things (IIoT) standard for the transfer of information between machines, systems and processes has become a severe limitation to the growth of digitization and computerization in the electronics manufacturing industry, inhibiting technology innovations such as Industry 4.0 and Smart Factories being available to all companies in the industry, regardless of size, sector and location.

This Connected Factory Exchange (CFX) standard provides a true ''plug and play'' Internet of Things (IoT) communication environment throughout manufacturing, where all equipment, manufacturing processes and transactional stations can communicate with each other without the need for the development and use of bespoke interfaces. CFX-enabled equipment and solutions from different vendors work seamlessly together.

There are many types of users of this CFX standard, including equipment vendors, solution providers, in-house information technology (IT) groups, etc. The many types of data included in CFX are used in different ways depending on the application; for example, closed-loop feedback systems, live production dashboards, traceability (IPC-1782), manufacturing execution systems (MES) control, lean supply chain management, active quality management, production control, etc.

As CFX data is fully omnidirectional, any CFX endpoint connection can consume data as well as create it. As an illustration, consider the scenario in which a single machine from a certain vendor is connected in-line with other machines from different vendors. CFX messages are sent from the single machine to other machines in the line, and to host systems such as MES. The single machine can also receive CFX messages from all other machines in the line, as well as from the host systems in order to optimize the machine operation and enable the vendor of the machines to create added-value functionality, such as to support machine-specific Industry 4.0. In this way, a smart, digital, Industry 4.0 factory will be comprised of many different Industry 4.0 computerization applications, each of which can be provided by different suppliers, at the machine, line, site and even enterprise levels, all working together, sharing data seamlessly through CFX.

This CFX standard supports the concept of big data by including data of different types from across the factory, including performance, materials, resources, users, quality events, product tracking, etc., all of which can be combined to create a bigdata environment. CFX, therefore, provides many kinds of added value opportunities to the whole manufacturing operation, including, for example, improving operational efficiency and productivity, quality and reliability, agility and responsiveness. This CFX standard helps organizations ensure that end users/consumers will receive products and services that meet or exceed their expectations and in the timeliest and most economically viable method.

Application of This Standard

This standard defines the communication protocol and content across all assembly production processes, irrespective of type or method of operation. It can also be applied to transactional operations. There are no restrictions in terms of product classification sector, size of operation or location. Surface-mount technology (SMT) production is not required to be a part of the factory. Though intended to support all aspects of printed board production, the use of CFX can be extended downstream to include, for example, mechanical assembly, personalization, packing and shipping, as well as upstream to include, for example, electrical and mechanical subassemblies.

CFX and the Hermes Standard

This CFX standard is complementary to IPC-HERMES-9852. The Hermes Standard, as an advanced, intelligent Surface Mount Equipment Manufacturers Association (SMEMA) standard replacement, provides near-instant line control, passing information about production units as they pass down the line. CFX provides vertical messaging that is complementary to Hermes.

Updates to This Standard

The IPC Connected Factory Exchange Initiative Subcommittee intends to make frequent incremental revisions to this standard to support additional machines and processes. Version updates are identified by version number and the change (added, removed, etc.), so the reader can easily identify changes in each version. See Figure 1-1 for an example of this version change tracking using a portion of Table 8-5 of this standard as an example.

Appendix A also provides an itemized version history.

All messages in this standard apply to IPC-2591, Version 1.0 and subsequent versions, unless otherwise stated.

Definition of Requirements

The words shall or shall not are used in the text of this document wherever there is a requirement for materials, preparation, process control or acceptance.

The word ''should'' reflects recommendations and is used to reflect general industry practices and procedures for guidance only.

Line drawings and illustrations are depicted herein to assist in the interpretation of the written requirements of this Standard. The text takes precedence over the figures.

Order of Precedence

The contract shall take precedence over this standard, referenced standards and drawings.

In the event of conflict, the following order of precedence applies:

1. Procurement as agreed and documented between user and supplier.

2. Master drawing, design brief or tech pack reflecting the user's detailed requirements.

3. When invoked by the customer or per contractual agreement, this standard.

When documents other than this standard are cited, the order of precedence shall be defined in the procurement documents. The user can specify alternate acceptance criteria.

Conflict

In the event of conflict between the requirements of this standard and the applicable drawing(s) and documentation, the applicable user-approved drawing(s) and documentation govern.

Some examples of documentation include the contract, purchase order, technical data package, engineering specification or performance specification. In the event of a conflict between the text of this standard and the applicable documents cited herein, the text of this standard takes precedence. In the event of conflict between the requirements of this standard and drawing(s) and documentation that has not been user approved, this standard governs.

Clause References

When a clause in this document is referenced, its subordinate clauses apply, unless the requirement references specific subordinate clauses.