# Introduction to Zaikio
Welcome to an Introduction of Zaikio. This guide is meant to give you an overview of the functionalities Zaikio offers and its role in the Zaikio platform.
# What is Zaikio?
Zaikio is the central data exchange and process monitoring station for the Zaikio platform.
# What does Zaikio do?
Data Platform provides an API that allows you to store orders, job specifications (including binary file references), logistics information, and all shop floor specific data (including impositions, worksteps, material requirements, production schedules, etc.). Other apps can then use the same API to retrieve that data. Zaikio is based on a persistent database, so other apps can query the data you provide at any time (as opposed to being a mere forwarding architecture). Data Platform will also check all incoming data for compliance with our standard data model, as well as plausibility. Thus we ensure that connected apps can trust that all information retrieved from Zaikio is compliant and valid from a logical point of view.
In summary, Zaikio's core functions are:
- Data exchange between connected apps regarding orders, job specifications, logistics, and all required data for shop floor operations
- Action triggering by sending events to all connected apps whenever data changes, so that the apps can react
- Process monitoring and shop floor awareness of equipment (IoT) as well as end users through the API and the UI
# What does Zaikio not do?
Zaikio's core functions are data exchange and progress tracking. As such, it is designed solely as a data repository. Zaikio will not generate data by itself. It will not create orders or job specifications, nor does it know how to find files or generate production schedules. It does, however, provide the required data models and API interfaces for third party apps to create that information. In essence, Zaikio is completely reliant on third party applications and data to make it come to live.
# Dissecting Zaikio – the data parts
Zaikio's data model covers a wide range of topics in order to facilitate an end-to-end process for printers. To make the data model and API more accessible we have divided it into the following six components:
# Business API
This part covers everything related to the ordering of printed goods and the business transactions that lie behind it, such as customer information, payment information, invoicing information, etc. The Order is loosely coupled to Jobs via its line items, but apart from this we keep the two independent.
Zaikio can easily be used as a repository for Order information without ever sending a print Job through it, or vice-versa.
Candidate usages include:
- Web2Print solutions
- MIS products
# Jobs API
This part covers everything related to a single printed Job. Since Zaikio's function is that of a data exchange, it doesn't know about templates, instead it requires a complete job specification for every single job produced. Job specifications cover all information necessary to describe a printed item: job parts including their layout (both boxed and path-based), colours, desired substrates, as well as finishings and their application, raw material requirements and confectioning (packaging during production).
Candidate usage is anything integrating with Zaikio.
# Estimation API
This part covers everything required to take a draft Job and produce a detailed costings, quotes and possible production plans.
Candidate usages include:
- MIS products
- Estimation tools
- Procurement tools
# Production API
This part is concerned with the process of turning a Job into a finished product. An extensive set of building blocks for setting up and scheduling intricate work flows provides everything needed to model even gang or batch jobs.
Candidate usages include:
- Imposing tools
- Workflow tools
- Scheduling tools
- MIS products
# Logistics API
This part covers how products and other materials are picked, packed and dispatched to their destinations, including carrier and parcel information, manifests, shipping lists and the like. Throughout Zaikio we strictly separate confectioning (applying packaging during the production process, which is part of the job specification) and commissioning (applying packaging after the production process and are thus part of the logistics API).
Candidate usages include:
- Warehousing tools
- Shipping tools
- Web2Print platforms retrieving Order shipment information
- MIS products
# Shop floor API
The part covers all of the connected devices that participate within the production process of a print Job. Machine or Specialist feedback on production status, problems, delays, availability of resources - all of these are covered here.
Candidate usages include:
- Machines reporting Executions - progress through a
Job'sProductionSlots - Specialists reporting and clearing
JobDelays onJobproduction