Coena Node connects applications within large businesses to other businesses, big or small. While it has always been possible for large businsses to connect with each other, Coena Node is revolutionary as it permits large businesses to integrate with small businesses using formal information structures. No more ad-hoc spreadsheets and paper-trails.

Very cost-effective

Coena Node's semantic mapping technology ensures that integration is performed for a fraction of the normal cost of integrating systems together. Existing data is mapped to a common information model that can be shared with other businesses. See how it works.

Connects with any system

Coena Node connects with Enterprise Resource Planning (ERP) systems, Customer Relationship Management (CRM) systems, Warehouse Management systems (WMS), and Supply Chain Management (SCM) systems. Information present in these systems can be selectively shared with other members in the network.

A mature system for small businesses

Revolutionarily, Coena Node provides a state-of-the-art application for connecting small businesses with other businesses. A complete information repository, transactional data handling, and a business messaging platform means that the hassle of dealing with small businesses is a thing of the past.

Large businesses speak the same language

Large businesses that work with other businesses usually don't have common systems. The results of mergers and acquisitions may require 2 very different organizations to work with a common information model. Coena's enterprise technology permits different organizations with different IT systems to talk the same language.

Information models can exist on 3 levels (data, relationships, behaviour). Data is the simplest level, and most busineses exchange information at the level of just data. Consider the following example.

A person working in a business can read this information, and infer that there is an employee named Tim Jones, who works in the Sales department as a Salesperson, and is currently unavailable. It's possible that this inference is wrong, and that Tim Jones is the manager responsible for all Salespersons, and there aren't any new positions open for new sales persons. Data travels well by itself only when the relationships between the data is clear, and different parties interpreting the data can refer to the relationships before making inferences. This is a 2nd level information model, containing data and relationships. To expand on the previous example:

How is an employee's availability or unavailability decided? How are tasks assigned to an employee? What tasks can an employee with a specific role perform? Answers to these questions would constitute behaviour, and would then form the 3rd level of an information model.