Purpose and Philosophy |
The primary purpose of the xTend Framework is to facilitate system-to-system integrations, and data sharing between FactoryLogix, and other software platforms running within your enterprise, such as ERP (Enterprise Resource Planning) or PLM (Product Lifecycle Management) systems.
However, xTend also allows for other types of development projects, including:
Development of fully customized operator interfaces.
Integration with robotic equipment and the factory automation layer.
Customization or extension of system behavior.
Technology | Purpose | Delivery Model |
xLink | Data Collection and Integration to Automated Factory Equipment | Standard and Custom Integrations Provided by Aegis Engineering Team |
xStream | One-way Automated Export of Production Information and Data | Standard, End-User Configurable Module. No Software Development Skill Required. |
Standard xTend Integration Modules | Single or bi-directional XML-based data sharing between FactoryLogix and external systems. | Standard, End-User Configurable Modules that produce or consume XML data files. Provided by Aegis Engineering Team |
xTend API | Direct Integration via Application Programmer’s Interface (API), allowing Integrations of all kinds, including System-to-System Integration, Integration to Automated Factory Equipment, Customized Behaviors, and Customized User Interfaces. | Software Development Performed by End-Users, Consultants, and/or 3rd Party Integrators. Optional XML Interface allows use by those with Minimal Software Development Knowledge and Skill. |
The FactoryLogix system utilizes an SQL-based Relational Database Management Solution (RDBMS) at its core to store all information. Because of this very open approach, it is technically possible for anyone familiar with the SQL language to query and manipulate the information stored within the FactoryLogix database.
However, this approach defeats the purpose of why an MOS system is deployed in the first place. When direct integration to the database layer is employed, the business logic execution, and data integrity enforcements guaranteed by the FactoryLogix system are bypassed. This may lead to corrupt data, bypassed processes, and other undesirable outcomes.
This is why the xTend Framework exists. It ensures that transactions executed against the FactoryLogix system are processed in uniform and consistent way across all users, data sources, and situations. Transactions proceed through the same exact business logic and process flow regardless of whether a factory floor operator initiates the transaction, or a background integration module.
For these reasons, Aegis strongly recommends that the xTend Framework be utilized exclusively for all integrations, and that direct database integration be avoided. Simple mistakes may lead to corrupt data within the FactoryLogix database, which will in turn, cause standard Aegis modules to malfunction.
Support and assistance for issues caused by direct SQL-based integration are not included in Aegis’ standard service level agreement (SLA) which governs our service and support contracts. Such incidents may result in additional support charges and fees.
The concept of end-user configurability is at the core of the FactoryLogix design, and Aegis’ overall value proposition. When Aegis designed FactoryLogix, we set out to build a highly flexible, and largely “out of the box” solution that would fit seamlessly into almost any production environment, minimizing the need for time consuming and costly customization.
Traditional MES/MOS systems provide little more than a database schema, and a core API that is then used by IT staff or 3rd party integrators to build out a usable solution each time the system is deployed in a new environment.
The FactoryLogix system largely eliminates this costly and error-prone deployment model by putting the power of configurability into the hands the manufacturing engineers who understand the production processes and needs of the system at a very deep level. By doing so, costly misunderstandings between IT staff and manufacturing staff are avoided, deployment timeframes shortened, and total cost of ownership greatly reduced.
For example, perhaps a new inline inspection process is added to an existing production line. In the Aegis FactoryLogix solution, manufacturing engineers would simply open the FactoryLogix NPI module, and reconfigure the process definition to include this new operation, and update the routing logic through an intuitive and simple user interface. No code changes or involvement of IT staff is necessary.
In a traditional MES/MOS system, the simple addition of this new operation in the process flow would require IT Staff or 3rd party integrators to re-code the routing logic, and perhaps build a new operator interface for data entry of inspection results.
The Aegis philosophy of configurability is unique to the FactoryLogix solution, and is at the core of our value proposition.
That said, integration from FactoryLogix to other software systems running within the enterprise is a critical element of most deployments. There are also some situations when full customizability is desirable.
With FactoryLogix, Aegis bring the best of both worlds to our customers. Highly configurable processes minimize the need for customization, while the deep and rich programmer’s interface of the xTend Framework gives IT staff and integrators the ability to customize the system to any degree necessary. As such, this key philosophy does not in any way compromise the overall flexibility of the system.