Answers for your IT department
Before the system goes onto the shop floor, someone will ask where the data is, who can access it and what happens when the cooperation ends. Here are the answers.
Your server or the cloud
The system runs on your server or in the cloud. You choose, and the decision can be changed at contract renewal.
Continuous, daily and weekly backups
A continuous copy of the database plus full backups once a day and once a week. We test a restore during implementation.
Access by role
The operator sees their workstation, the shift leader their area, the manager the plant. Every correction has an author and a time.
The data is yours
You export reports at any time, and at the end of the contract you receive a full export of the database.
Where the data runs
One database per plant, access only through the browser over HTTPS.
Your server or the cloud
In the Enterprise plan the system runs on a server in your network. In the other plans it runs in a cloud we administer. The operator and manager work the same way in both.
Each plant's data kept apart
Each plant is a separate organisation in the system. Every record in the database is assigned to an organisation, and isolation policies in the database make sure one plant's query never reaches another plant's data.
Encrypted connection
The tablet, the management panel and the gateway at the machine connect to the system over HTTPS. Nothing is installed on the workstation apart from a browser.
Service access
The DiGi team enters a plant's data only within the support written into the contract. On your server, your IT decides about remote access.
Backups and restore
A continuous copy plus full backups daily and weekly.
Three levels of backup
The database is copied continuously, and on top of that a full backup is made once a day and once a week. The retention period is written into the contract.
Restore tested
The implementation checklist has the item: backups configured and tested by a restore. We do not close the go-live without it.
On your server
Backups can be made by your IT following our checklist, or by us if we have remote access. We agree this before go-live, not after the first failure.
Raw signals without corrections
Machine signals are written to a log nobody edits. Counter corrections are separate records, so after a restore you can see what was raw and what was corrected.
Who sees what
Ready-made or custom roles, permissions per area of the system.
Login
Every user logs in with their own account. Passwords are stored only as a cryptographic hash, and the session expires after inactivity. The shop floor screen has its own read-only account.
Ready-made and custom roles
Nine factory roles: administrator, production manager, shift leader, operator, quality inspector, quality manager, technologist, auditor, TV screen. You can also build your own roles for your plant.
Permissions per area
Every area of the system, from plant setup to quality reports, has its own level: none, read or edit. Separate flags decide, for example, who may correct other people's entries, backdate data or export data.
Scope of visibility
A quality inspector can be limited to selected departments or workshops. The quality manager sees everything.
Change log
Who, when, what was before and what is after.
Value before and after
Corrections of production, downtime, scrap, changeovers, shift reports and permissions are written to the log with the value before the change, after the change, the author and the time.
Undo does not erase the trace
An undone correction gets its own entry and a revocation mark. Nothing disappears from the log.
Source of every reading
An inspection result records where it came from: the gauge, a file or by hand, and which gauge was used.
View for the auditor
The log is available in the panel to roles with the right permission. The auditor role has read access without the right to edit.
How new versions arrive
In the cloud we do it, on your server at an agreed time.
In the cloud
We deploy new versions. Changes to the database structure are a separate, controlled step done before the release, not automatically at system start.
On your server
We agree the update date with your IT, outside the production shift. You get the list of changes before the update.
One version for everyone
All plants run on the same version of the system. A fix made for one plant reaches the others.
Four interface languages
Polish, English, Ukrainian and Spanish. Every user has their own language, independent of the rest of the plant.
Your data, at any time
Reports to a spreadsheet and PDF, the full database at the end of the contract.
Reports
Every report, from OEE to the control chart, exports to CSV, an XLSX spreadsheet and PDF. Scheduled reports arrive by e-mail as files.
Control plans
You import and export control plan characteristics as CSV. The same file works both ways, so a plan prepared in a spreadsheet enters the system without retyping.
End of cooperation
At the end of the contract you receive a full export of the database. Cloud data is deleted within the period written into the contract.
Export permission
Data export is a separate permission, independent of the right to view reports. You decide who in the plant may take data out of the system.
Machines, gauges and ERP
A gateway at the machine with a token, ERP exchange agreed with your IT.
Gateway at the machine
The DiGi gateway sends run signals and counters over HTTPS. Every machine has its own access token, stored in the system only as a hash. The gateway keeps a queue on disk, so a network outage does not lose signals.
Measuring gauges
The gauge connects to the tablet by cable, USB or Bluetooth. The reading lands in the measurement field without drivers or programs on the workstation.
ERP and other systems
Data exchange with ERP, warehouse or planning is agreed individually: through an API, files or database views. Scope and format are agreed with your IT or the system vendor.
Network on the shop floor
The tablet and the gateway need Wi-Fi or a wired network with access to the system. The gateway runs as a Windows service at the machine.
Who is responsible and what happens after
Rights to the code, support and parting without surprises.
Rights to the system
DEVS Sp. z o.o., the owner of the DiGi brand, holds the rights to the system and its code. The customer gets a licence to use it, and the shop floor data belongs to the customer.
Who develops the system
The DEVS team writes and maintains the system, and we run implementations together with our partner VXCONTROL. A request from the shop floor goes straight to the people who build the system.
Support under the contract
The scope of support, request channels and response times are written into the SLA agreement, matched to the plan and to where the system runs.
End of contract
You receive a full export of the database, and on your server the system simply stays with you until the licence expires. No fees for handing over data.
Ask for details
We answer IT and procurement questions before the pilot, not after the contract is signed.
Dariusz will answer questions about the contract, data, support and how working with DiGi looks.
Phone: (+48) 668 211 736
Email: dariusz@digi.com.pl