Deploy with Confidence.
Meet V5 System Requirements.
SYSTEM REQUIREMENTS
Designed for Validated, Production-Ready Environments.
V5 System Requirements define the minimum infrastructure specifications required for secure, validated operation. They guide IT and quality teams in preparing production-ready environments.
1. Server (Database & Application Host)
One server per production site with a static IP hosting the SQL database and V5 services.
Physical or virtual servers are acceptable if resources are guaranteed.
References:
MSA §2.3.1 (Default Deployment), §4.3 (On‑Premise Option), §11.2 (On‑Prem Support)
Required Server Software
- SQL Database: Microsoft SQL Server 2016 Standard or later
- Database Administration: SQL Server Management Studio (SSMS)
- V5 Traceability Database: SG Systems database schema
- SG Systems Management Application: CSV import/export processing
- Reporting: TIBCO JasperReports
- Remote Viewing (if approved by IT policy): UltraVNC Viewer v1.2.10
- Java Runtime Environment: JRE 1.8 or later (64-bit)
IT clarity: This document assumes a standard SQL Server deployment. If SQL is hosted on a separate database server,
the SQL host must meet the server requirements and remain reachable from all endpoints.
Minimum Hardware Specification (Server)
| Component | Minimum | Recommended |
|---|---|---|
| Operating System | Windows Server 2016 or later | Windows Server 2019/2022 (per IT standards) |
| Architecture | 64-bit | 64-bit |
| CPU | 2.8 GHz quad-core | Higher core count for reporting / integrations |
| RAM | 16 GB | 32 GB for ERP integrations and/or higher concurrency |
| Storage | 500 GB free | SSD-backed storage with growth headroom |
| Network | Reliable LAN connectivity | Managed/segmented network per site standards |
Capacity planning: Initial setup is ~10 GB; required storage scales with terminal count, transaction volume,
retention requirements, and reporting output.
Operational Expectations (IT-Owned)
- Static IP & name resolution: assign static IP; DNS hostname recommended
- Backups & recovery: SQL backups, retention, and restore testing (On‑Prem is Customer‑owned per MSA §4.3)
- Patch management: OS/SQL maintenance aligned to change control (regulated change control guidance: MSA §8)
- Time sync: server and endpoints synchronized (NTP/domain time)
- Endpoint protection: AV/EDR policies must not block required services; allowlist if needed
- Monitoring: disk/RAM/CPU capacity and SQL/service health
2. Production / Warehouse / Laboratory Devices (Terminals, Tablets, Scanners)
Endpoints used on the shop floor, warehouse, and laboratory/QC areas connect to the central SQL database over the network and run the terminal/WMS application.
References:
MSA §2.17–§2.18 (Device / Device License) and §4.4 (Peripherals excluded from Device License)
Required Endpoint Software
- SG Systems Terminal/WMS Application
- Java Runtime Environment: JRE 1.8 or later (64-bit)
- Remote Viewing (if approved by IT policy): UltraVNC Server v1.2.10
Minimum Hardware Specification (Production/Warehouse/Laboratory)
| Component | Minimum | Notes |
|---|---|---|
| Operating System | Windows 10/11 (IoT, Pro, or Home) | Per Customer IT standard build and patch policy |
| CPU | 2.0 GHz quad-core | Increase for heavier local workflows |
| RAM | 4 GB minimum | 8 GB recommended |
| Storage | 100 GB free | ~10 GB initial setup; allow OS + updates + logs |
| Display | 1024×768 minimum | Higher resolutions recommended |
| Connectivity | Hardwired Ethernet or Wi‑Fi | Stable connectivity required for transactional systems |
| Ports | USB as required | For scanners, USB scales, and other peripherals |
| RS232 (if used) | RS232 available | Only required if using RS232 scales (USB/Ethernet scales supported) |
Peripherals (Scanners, Scales, Label Printers)
Barcode Scanners
- Must be programmable for AIM ID
- Support CR/LF suffix (where required)
Scales (If Applicable)
- Supported connection types: USB, Ethernet (TCP/IP), or RS232
- RS232 scales require an RS232 port (native) or an IT‑approved USB‑to‑serial adapter
- Ethernet scales should use a stable IP (static or DHCP reservation) and be reachable from the endpoint network
- Confirm protocol/settings during integration (baud/parity for serial; IP/port/protocol for Ethernet)
Label Printers (Networked, ZPL)
- Supported: any networked label printer that accepts ZPL (Zebra‑compatible ZPL)
- Printer should be reachable by IP/hostname from the endpoint(s) performing printing
- Recommended: static IP or DHCP reservation for each printer (avoid IP drift)
- Network printing must pass ZPL unmodified (direct TCP/RAW printing is common; print servers are acceptable if they do not transform ZPL)
Licensing clarity (prevents IT/Procurement churn): scanners, scales, and printers are treated as passive peripherals and are not licensed as “Devices / HMIs” (MSA §2.17, §4.4).
3. Control Center Workstations
Control Center can be installed on local user PCs for administration, QA oversight, and operational control.
Minimum Hardware & Software Specification (Control Center)
| Component | Minimum | Notes |
|---|---|---|
| Operating System | Windows 10 or later | 64-bit required |
| CPU | 3.0 GHz quad-core | Higher specs recommended for reporting/admin workloads |
| RAM | 8 GB | Increase as needed for multitasking |
| Storage | 10 GB free | Allow headroom for exports/reports |
| Network | Connectivity to the server | Stable LAN/WLAN access required |
| Java Runtime | JRE 1.8 or later (64-bit) | Required |
| Display | Unscaled desktop resolution | Avoid OS scaling that can distort layouts |
4. Network, Security & Support (IT Checklist)
This section exists to eliminate common IT follow‑up questions for on‑prem deployments.
References:
MSA §4.3 (On‑Prem responsibilities), §8 (Change Control), §11.2 (On‑Prem support)
Connectivity, Addressing & Ports (Typical)
- Static IP: required for the V5 server
- DNS hostname: recommended for server and network printers
- SQL connectivity: endpoints must be permitted to reach the SQL Server instance (default TCP 1433, or your configured SQL port)
- UltraVNC (if used): allow per Customer configuration/policy (common TCP 5900)
- Network label printers (ZPL): allow printing path per your print architecture (common RAW/TCP 9100 or LPR 515 where applicable)
Security posture: Only open what is required, restrict source subnets, and log administrative access per IT policy.
Final port values depend on your SQL/printer/remote-support configuration.
Backups, DR, Monitoring & Patch Control
- Backups/DR: Customer‑owned for On‑Prem (SQL backups + restore testing + DR plan) (MSA §4.3; §9.4)
- Monitoring: disk capacity, SQL service health, CPU/RAM, and network availability
- Change control: On‑Prem Customers control when updates are deployed; align updates with validation/change control requirements (MSA §8.2)
- Time sync: server + endpoints synchronized (NTP/domain time)
Remote Access & Support Methods
- LogMeIn Rescue (preferred)
- TeamViewer
- Remote Desktop Connection (RDP)
- AnyDesk
Expectation set (On‑Prem): SG Systems provides routine software support and troubleshooting, while Customer maintains the environment (MSA §11.2, §4.3).
Information SG Systems Typically Requests During Onboarding
- Server hostname + static IP
- SQL Server instance/port and authentication approach (per IT policy)
- Approved remote support method and access process
- List of endpoints (production/warehouse/lab) and any device constraints (Wi‑Fi only, kiosk mode, etc.)
- Peripheral list: scanners, scale connection type (USB/Ethernet/RS232), printer IPs/queues (ZPL)
Onboarding formally validates infrastructure readiness as part of Phase 1 (“Plan & Prepare”) — see the linked Onboarding Process page.