SignalOps AI: Motion Design for a Predictive Maintenance SaaS Platform
SignalOps AI is a self-initiated motion design project built around a fictional AI-powered predictive maintenance platform.
The idea was to create a short SaaS explainer focused almost entirely on interface animation, data visualization and typography, without relying on characters or traditional illustrated scenes.
The result is a 30-second video showing how a predictive maintenance system can turn machine data into a clear maintenance priority before downtime becomes a problem.
The concept
The video starts from a simple idea:
Downtime doesn’t happen all at once. It builds up in the data.
Instead of introducing the platform through a generic product overview, I wanted the animation to follow the logic of the software itself.
The viewer first encounters the problem as something abstract. The interface then gradually reveals where that problem is hiding: charts, alerts, asset health scores and maintenance priorities.
The visual narrative progressively narrows the viewer’s attention until one specific machine emerges as critical: Pump 04.
From there, the platform moves from monitoring to action.

Building a believable SaaS environment
I developed the fictional interface in Figma, defining the screens, data, visual hierarchy and states required by the narrative.
Rather than designing every possible section of a complete application, I concentrated on the parts that were necessary to make the product feel coherent and credible during the video.
I created a fictional industrial dataset around assets such as pumps, motors, compressors and conveyors.
The interface includes:
-
asset health monitoring
-
critical alerts
-
predicted failures
-
failure risk forecasting
-
maintenance priorities
-
AI activity
-
asset details
-
maintenance history
-
work orders
The objective was not to simulate a complete real-world software product, but to build a convincing environment where every screen and piece of information supported the narrative.

Turning data into motion
A large part of the project involved deciding what information should move and why.
Instead of animating every interface element at the same level, I used motion to progressively guide the viewer through the hierarchy of information.
Numbers update.
Charts build themselves.
Forecast curves appear over existing data.
Rows become highlighted.
The interface gradually isolates the asset that requires attention.
This allowed the animation to move from a complex dashboard toward a very specific piece of information without explaining every feature individually.
One of the key moments is the transition from the complete dashboard to the isolated Pump 04 row.
The rest of the interface fades away, leaving only the relevant information:
Pump 04 / Line A / 87% risk / Critical
The UI itself becomes a transition element, connecting the general overview with the detailed asset monitoring section.
Typography as part of the interface
Typography also plays an important role in the opening sequence.
The initial statement is progressively revealed across the screen before a graphic underline expands and becomes the transition that introduces the platform.
Rather than treating titles as separate graphic cards, I wanted typography, interface elements and transitions to feel like parts of the same visual system.
The teal accent used throughout the UI therefore works both as a visual identity element and as a device for directing the viewer’s attention.
Motion with a purpose
With SaaS interfaces there is always a trade-off between showing the product and overwhelming the viewer with information.
A real dashboard may contain dozens of metrics at the same time, but animation makes it possible to control when those elements become relevant.
For this project I used camera movement, selective emphasis, animated graphs and temporary reduction of visual information to determine where the eye should move next.
The goal was not simply to make the interface look dynamic.
The motion had to explain the relationship between:
data → prediction → priority → action
That sequence became the underlying structure of the video.

From Figma to After Effects
The interface was created and prepared manually in Figma before being brought into After Effects for animation, compositing and final visual treatment.
Individual interface components were separated and animated independently rather than treating the UI as a static screen.
This made it possible to control charts, values, highlights, cards and individual interface sections while maintaining a consistent visual system.
Subtle perspective shifts and camera movements were also used to move between the complete dashboard and individual pieces of information without making the result feel like a simple screen recording.
A one-week personal production
The project was completed in roughly one week.
Working on a short self-initiated piece allowed me to concentrate on a specific communication problem: how to explain a software product whose value exists mainly inside data, dashboards and automated processes.
It also became an exercise in restraint.
Not every element needed to animate.
Not every feature needed to be explained.
The main challenge was deciding which information actually helped move the story forward.
Project details
Type: Self-initiated project
Format: SaaS explainer / UI motion design
Duration: 30 seconds
Industry concept: Predictive maintenance / Industrial AI
Tools: After Effects, FigmaRole: Concept development, interface design and adaptation, motion design, animation, compositing and sound design
Your product has a story. Let's make it move!
