A useful starting point and best practices for Tulip Tables

The best practice usage of Tulip Tables may not be immediately obvious, as in contrast to a traditional MES:
a. Tulip Apps themselves commonly host certain master data (e.g. the manufacturing process steps, context regarding the tools/equipment used, etc…).
b. Tulip’s ‘Completion’ Records feature provides an easy way to store immutable historical process data, thereby greatly mitigating the need to store this data into separate tables.
c. Tulip solutions are purpose-built in a bottoms-up fashion yielding a concise table model compared to a rigid top-down data model that ultimately falls short of business needs.
d. Tulip solutions may interact with third-party sources of truth to fetch certain context in real time (e.g. the Bill-of-Material for a Work Order from an ERP system).

Thus, Tulip Tables are typically used, and best used, for one of two purposes:

  1. Physical Artifacts
  2. Operational Artifacts

Learn more and see more details including starting point table structures on the Tulip Knowledge Base at: Common Tulip Tables.