Skip to content

    Connected story / For system integrators & machine builders

    Reduce integration risk and engineering hours on machine projects.

    Developing production software for each machine project adds risk and consumes engineering hours. IntelliTrack™ provides established production functions and a consistent, tested controls interface, reducing the custom code your team needs to develop, test and support.

    Discuss an integrator projectDownload the detail sheet (PDF)

    Custom software adds development and support obligations to every project.

    A customer may already have an ERP and an HMI, yet still need product tracking, data collection, recipe checks, product genealogy, quality reporting, and operator dashboards. Building those functions separately expands the project scope and leaves your team responsible for maintaining each one. IntelliTrack™ provides a configurable platform maintained by FDS. A consistent, well-tested controls interface speeds implementation and reduces variation across stations and projects, while subscription pricing offers a lower barrier to an initial project than a large upfront software commitment.

    Use a standard interface to deliver the production functions your customer needs.

    1. Implement the equipment interface

      Use AOIs, FBs, and Collections for product checks, recipe exchange, and results. The configured production rules return a result that the machine sequence must honor. Apply the same interaction pattern across stations and test each machine's responses.

    2. Use the production record during acceptance

      Use OEE and loss reporting alongside product records. Quality counts come from IntelliTrack™'s own pass/fail results, giving the project a consistent record to support agreed machine-performance acceptance criteria.

    3. Hand over the operational functions

      Configure dashboards, alarm guidance, shift handoff, and product history around the customer's daily work. Use the available branding options to identify your company in the delivered system, with a clear plan for training and ongoing support.

    Project leadership

    Reduce project risk by building on tested interfaces and established production functions, with less new software behavior to commission.

    Controls teams

    Decrease engineering hours spent on repeated interface design, debugging, and support. Apply familiar interactions across machines and projects.

    Commercial teams

    Offer production and quality functions alongside the machine, with subscription pricing for an initial project and branding that keeps your company visible.

    Illustrative workflow

    A machine builder wants to demonstrate performance and remain visible after handover.

    The builder agrees on acceptance conditions with the customer, captures states and production results, and uses OEE and loss reports as supporting evidence. The customer receives dashboards and product history under the agreed branding. This illustrates a combined delivery; the OEE report is evidence for agreed criteria, not formal machine qualification by itself.

    Plan the setup around your process.

    Review subscription terms, eligible licenses, and the available branding options in a project quotation. Establish representative loads, data quality, and acceptance criteria before using OEE as performance evidence. Proven patterns still need application-specific testing.

    Questions your team may ask

    How does this reduce risk and engineering hours?

    Tested interfaces and established production functions reduce the custom software your team needs to design and debug. Consistent interactions mean fewer variations to commission and support. The machine-specific mappings, control responses, and recovery behavior still need verification.

    Does OEE validate the machine?

    OEE can support agreed performance acceptance with a consistent production record. Formal qualification or acceptance also needs defined conditions, correct inputs, representative runs, and the other tests required by the contract.

    How does the subscription help us start?

    A subscription provides an entry path that can be scoped into the initial project. Confirm the current subscription, deployment, and support terms for your project before building them into a proposal.

    Can we promote our own company through the installation?

    Branding options can keep your company visible in the installation. Review the eligible license and exact customer-facing branding surfaces during quotation so the proposed experience matches what can be delivered.

    Can we use the same platform in regulated and non-regulated installations?

    Yes. GxP Mode controls electronic-signature gates for applicable human decisions. Approval counts, role access, audit trails, and production quality rules remain active in both modes, so the platform supports either installation without switching off quality enforcement.

    Review the software scope for your next machine project.

    Bring a machine concept and acceptance requirements. We can scope the interfaces, customer features, subscription, and branding together.

    Discuss an integrator projectKeep the PDF detail sheet

    Continue the story