-
When to Use This Checklist
-
Step 1: Verify Network Prerequisites (The IT Conversation)
-
Step 2: Define Access Levels Before the First Invitation
-
Step 3: Validate Filament Profiles—All of Them
-
Step 4: Conduct a 15-Minute User Training Session (It's Not Optional)
-
Step 5: Establish Print Job Policies (Before Someone Prints Something Weird)
-
Step 6: Schedule Maintenance Reminders in Digital Factory (Or Build Your Own)
-
Step 7: Plan Your Rollback (Yes, You Might Need One)
-
Final Note: Avoid These Two Mistakes
Look, I'm not going to tell you that setting up a Digital Factory (the Ultimaker cloud platform) is hard. It's not. The software is well-documented, the Wi-Fi setup is straightforward, and within an hour you can have a printer sending data to the cloud.
The hard part—the part I learned the expensive way—is everything around the technical setup. The conversations you didn't have. The permissions you didn't set. The filament profiles you assumed would 'just work.'
I've been handling technical deployments for B2B 3D printing operations since 2019. In that time, I've made (and documented) six significant deployment mistakes, totaling roughly $14,000 in wasted material, delayed projects, and damaged team trust. After the third rejection from a production manager in Q1 2024, I created our team's pre-check checklist.
It has seven steps. Here they are.
When to Use This Checklist
This checklist is for anyone rolling out Ultimaker Digital Factory to a team of 2-20 printers in a professional environment. It's for the person who's read the docs, knows how to connect a printer to Wi-Fi, but wants to avoid the 'we should have talked about that first' phone calls two weeks in.
The seven steps cover: prerequisites, access, filament profiles, user training, print job policies, maintenance scheduling, and a rollback plan. Each step has a specific check point.
Step 1: Verify Network Prerequisites (The IT Conversation)
This is the step everyone assumes is fine. It's not. Digital Factory requires each printer to maintain a stable connection to Ultimaker's cloud servers. In many manufacturing environments, the printers are on a separate VLAN or behind a firewall that blocks outbound traffic on certain ports.
The surprise wasn't the network setup itself. It was the stability. We had a production floor where printers would connect, work for a few hours, then drop off. Turns out the Wi-Fi access point near the print farm was overloaded by other devices. Every disconnection meant a missed print completion alert, which meant a delayed job.
Check point: Before connecting a single printer, run a connectivity test from the printer's location for 24 hours. Use a laptop or a dedicated device to confirm the connection is stable. Talk to IT about bandwidth and firewall rules. Document the allowed ports and IP ranges (Ultimaker publishes these).
Step 2: Define Access Levels Before the First Invitation
Digital Factory has user roles: Admin, Operator, and Viewer. It's easy to invite everyone as 'Operator' and figure it out later. Don't.
In my first rollout (2019), I gave Operator access to everyone who asked. Within a week, someone accidentally canceled a print job for a part that was due the next morning. The part was ruined. The machine was idle for 3 hours while we figured out what happened. $320 in material plus a missed deadline.
Here's the thing: the problem wasn't malicious. The user thought they were canceling their own job. But Digital Factory, by design, allows Operators to manage all jobs on a printer unless you restrict this.
Check point: Create a role matrix before inviting anyone. Who needs to start/stop jobs? Who only needs to view status? Who gets admin rights? Document it. Then invite accordingly. It's easier to elevate access later than to deal with accidental cancellation.
Step 3: Validate Filament Profiles—All of Them
Ultimaker Cura comes with excellent default profiles. But if you use third-party filament (or even different spools of Ultimaker material from different batches), the profiles may need adjustment.
I once ordered 20 spools of a specialty PLA for a client. The material profile in Cura looked correct. The first print on a new S5 came out beautifully. So we loaded all printers with the same material and started production. Two days later, we had four failed prints across two printers. Same material, same profile, different results.
The surprise wasn't the material. It was the printer-to-printer variation. Slight differences in nozzle condition, bed leveling, ambient temperature. We hadn't validated the profile on each individual printer before scaling.
Check point: For each filament type you plan to use, run a test print on each printer that will use it. Use a calibration print (a 20mm cube or a Benchy) and document the results. If a profile works on Printer A but fails on Printer B, adjust the profile or queue repairs. Do this before any production print.
Step 4: Conduct a 15-Minute User Training Session (It's Not Optional)
I used to think 'show them the interface and they'll figure it out.' No. Wait—that's wrong.
Here's what actually happens: You show the interface. Everyone nods. Two weeks later, someone asks 'how do I know if my print finished?' because they didn't notice the email notification setting was off. Or they upload a job but forget to assign it to a printer, so it sits in 'queued' for hours.
Check point: Schedule a 15-minute session per user. Cover three things: (1) How to upload and assign a print job. (2) How to check job status and notifications. (3) What to do if a print fails (pause vs. cancel vs. ignore). Have them do it on a real printer. Don't use a demo environment.
After the third such session, I created a one-page Quick Start guide. We've caught 47 potential errors using that guide in the past 18 months (I keep a log). It's saved us an estimated $8,000 in avoided rework.
Step 5: Establish Print Job Policies (Before Someone Prints Something Weird)
Digital Factory allows any Operator to send any job to any printer. Great for flexibility. Terrible for consistency if you don't set ground rules.
In September 2022, someone uploaded an STL file with a part that was meant to be printed in ABS—but the printer was loaded with PLA. The job completed. The part looked fine. But it failed the heat test on day one. Total cost of that mistake: $450 in production waste plus a 3-day delay for redo.
Check point: Define and communicate which printers are assigned to which materials. Use the printer naming feature in Digital Factory (e.g., 'S5 - PLA Only,' 'Method XL - ABS & PC'). If your team is larger, consider using the 'Printer Groups' feature to enforce this. Document the policy and include it in your user training.
Step 6: Schedule Maintenance Reminders in Digital Factory (Or Build Your Own)
Digital Factory tracks printer usage—hours run, material used, etc. You can use this data to schedule maintenance. But if you don't set up reminders, it won't happen.
We had a printer running continuously for 3 months. No issues. Then the nozzle started clogging. Then the bowden tube degraded. The cumulative downtime across four printers from neglected maintenance in 2023 was roughly 12 days. That's 12 days of lost production capacity.
Check point: For each printer, set a maintenance schedule in Digital Factory (or your own system). At minimum: nozzle replacement every 500 hours, PTFE tube check every 200 hours, bed leveling check weekly. Use the printer's 'Usage' tab to track this. If you're managing 5+ printers, create a shared calendar or use Digital Factory's API to automate alerts.
Step 7: Plan Your Rollback (Yes, You Might Need One)
This is the step most people skip. They assume Digital Factory will work perfectly forever. It won't. Not because the software is bad—it's excellent. But because something will change: your network, your IT policy, a firmware update.
In late 2024, Ultimaker pushed a firmware update that changed how certain printers reported their status. Our Digital Factory dashboard started showing printers as 'Offline' even though they were printing fine. Panic ensued. It took 4 hours to confirm it was a reporting bug, not a connectivity issue.
Check point: Before full rollout, define: (1) What is your fallback if Digital Factory goes down? Can each printer still run from USB/SD card? (2) Who has the admin credentials to force an override? (3) What's the communication plan if you need to pause all remote operations? Document this. Store it somewhere accessible (not on a manager's personal drive).
Having a rollback plan isn't pessimism. It's what separates a professional deployment from a hobbyist setup. Simple.
Final Note: Avoid These Two Mistakes
Mistake 1: Assuming 'One Profile Fits All.' No two printers are identical. Even two S5 units fresh out of the box can have slight variations. Validate per printer.
Mistake 2: Skipping the Conversation with Your Team. Digital Factory is a tool. It doesn't replace communication. If your team doesn't know who's responsible for what, the tool won't fix that. It'll just make the confusion faster.
5 minutes of verification beats 5 days of correction. The checklist above takes about 90 minutes to run through on a 5-printer setup. In my experience, it's saved us roughly 10x that time in avoided problems. Your mileage may vary—but I'd rather you learn from my mistakes than make your own.
