Start Today. 
Onboard Rapidly. Accelarate Production.

This initial step lays the foundation for a successful deployment. We bring together your key team members and our project manager to review implementation goals, facility setup, timelines, and responsibilities. We confirm deployment per the MSA (On-Premise by default; Hosted only if elected on the Order Form) and record your selected licensing model (User- or Device-Based) and subscription tier (Express / Professional / Enterprise). Estimated time: 1–2 hours Stakeholders involved: Project Lead, IT, QA, Production, SG Systems PM MSA Reference: §3 – Implementation Process; §2.2 (Hosted), §2.3 / §2.3.1 (On-Premise & Default), §4.4 (Licensing). Everyone aligned before the heavy lifting begins.

We review IT prerequisites based on deployment type. For On-Premise, we confirm server specs and network access; for Hosted, we validate connectivity and tenant access. We inventory HMIs (PCs/tablets) that will consume Device Licenses if that model is chosen; peripherals (scales, scanners, printers) integrate but are not licensed as Devices. Estimated time: 2–4 hours Stakeholders involved: IT, Facilities, Installers MSA Reference: §2.13–§2.14 (Device / Device License), §3.3 (Customer responsibilities). Clear HMI vs. peripheral boundaries avoid licensing ambiguity.

We identify the internal team for QA, IT, Production leadership, and operators, with clear roles and responsibilities to reduce friction later. Estimated time: 1–2 hours Stakeholders involved: Department Leads, QA, IT, Production Supervisors MSA Reference: §3.3 – Customer responsibilities & timeline. Clear accountability from day one.

We scope recipes, materials, inventory, locations, equipment, and user/device records to prepare master data load; confirm ERP sandbox access and tier-appropriate initial workflows. Estimated time: 1–3 hours Stakeholders involved: QA, Production, IT MSA Reference: §2.9 (Customer Data), §4.5 (ERP Integration), §3.1 (tier scope). Early scoping minimizes disruption during onboarding.

We configure modules per your selected tier, set roles/permissions, automation rules, batch templates, and compliance settings. License enforcement is enabled to match your model (User- or Device-Based) and minimums (min 3 user licenses or min 1 device license). Estimated time: 3–6 hours Stakeholders involved: SG Systems, QA, Production Supervisors MSA Reference: §3.1 (tiered scope), §4.4 (Licensing & Restrictions). Your system reflects your process—not the other way around.

We load and validate core datasets: materials, formulations, packaging specs, customers, suppliers, equipment, and locations—plus user accounts or device registry aligned to the licensing model. Estimated time: 3–5 hours Stakeholders involved: QA, Admin, Production Lead MSA Reference: §2.9 (Customer Data), §4.4 (Licensing), §3.1 (tier). Clean data enables smooth operations.

Role-based training for operators, supervisors, QA, and IT. We cover license assignment flows (named user vs device registration) and reassignment rules (permanent personnel changes or device retirement/replacement). Estimated time: 4–6 hours Stakeholders involved: Operators, QA, Supervisors, SG Systems Trainer MSA Reference: §10.3 – Training. Confidence and compliance from day one.

We connect your ERP per standard scope (one ERP, one API interface) and integrate HMIs and peripherals for shop-floor execution. We validate data flows and confirm licensed access behavior (blocking unlicensed sessions). Estimated time: 4–8 hours Stakeholders involved: SG Systems, IT, ERP Admin, QA MSA Reference: §4.5 – ERP Integration; §4.4 – Licensing enforcement. Systems that talk to each other reduce errors and rework.

Your team validates workflows before go-live. We confirm license checks (user/device) behave correctly across HMIs and roles and that deployment specifics (Hosted vs On-Premise) are set. Estimated time: 2–4 hours Stakeholders involved: QA, Production, SG Systems PM MSA Reference: §3 – Implementation; §4.4 – Licensing. Readiness is both compliance and confidence.

For regulated environments, we assist with IQ/OQ documentation and align future updates to change control. Estimated time: 3–6 hours Stakeholders involved: QA, Compliance Lead, SG Systems MSA Reference: §7.4 – Validation & Qualification Support; §8 – Change Control & Updates. Documentation aligned to industry expectations.

We monitor production cutover, verify license enforcement, and ensure deployment-specific items (e.g., Hosted uptime, backups; On-Premise infra) are operating as intended. Estimated time: 2–4 hours (across go-live day) Stakeholders involved: QA, Operators, Production Supervisors, SG Systems PM MSA Reference: §3 (Implementation); §11 (SLA for Hosted specifics). Close support through the first production shifts.

Ongoing support follows your SLA. Hosted customers receive uptime, RTO/RPO commitments; On-Premise customers receive operational/technical support with infrastructure owned by Customer. Estimated time: Ongoing (initial surge: 4–8 hours first week) Stakeholders involved: Production, QA, SG Systems Support MSA Reference: §11.1–§11.7 (SLA commitments for Hosted); §11.2 (On-Premise support scope). Sustained responsiveness as you move to steady-state operations.