We built OpsMoto to solve one problem: manufacturers running Tulip across multiple sites had no single place to see it all. They had to piece it together from spreadsheets and exports across sites and instances. Since then, customers have used OpsMoto to spot underused Automations, compare adoption across plants, and cut reporting time from days to minutes.
We’ve recently rolled out two updates that make that visibility even faster to get to and easier to act on: Map View and AI Chat.
Map View: Your Deployment, Plotted Where It Actually Lives
Here's the thing about most OpsMoto customers. They're rarely running one factory. Two, five, twelve sites, spread across countries, sometimes continents, is closer to the norm. Until now, OpsMoto represented all of that as a list. Instance names in a table. Functional, but not exactly how anyone actually pictures their own operation. Map View fixes that by showing your sites geographically instead of alphabetically.
Two things stand out once you start using it. First, it finally matches how multi-site, multi-country teams already think about their footprint. OpsMoto has always aggregated data across your sites; Map View just presents it the way your brain already organizes it, as pins on a map, not rows in a spreadsheet.
Second, and maybe more useful day to day: it shortens the ramp-up time for anyone who's new to an account. A new CSM. A stakeholder who just inherited a program. Someone from a company that got acquired and is now trying to figure out what's actually running where. Instead of reading through a list of cryptic instance names, they open the map, see it and understand where Tulip runs. Live sites, located where they're located. Onboarding becomes compressed into a glance.
AI Chat: Ask a Question, Get an Answer
OpsMoto's original argument was that manufacturers shouldn't have to earn visibility by manually stitching together exports and spreadsheets. AI Chat pushes that same argument one layer deeper. Once your data is centralized, the fastest way to see it isn't always another chart to build, it's just getting an answer to the question you actually had. AI Chat is a panel that now lives in OpsMoto. Type a question the way you'd ask a colleague, and it answers using your Tulip operational data. There’s no need to build more dashboards, figure out the right filters, or remember query syntax. Ask what you need to know because AI Chat knows what's happening in your operations.
That's only possible because AI Chat isn't a generic chatbot bolted onto a BI layer after the fact. Most business intelligence tools need someone in the middle, translating shop-floor reality into a query some database can parse. AI Chat skips that translation step entirely, because automations, stations, and completions are already how OpsMoto and Tulip model your operation. Ask about an automation and it already knows what that means in your world, not a generic abstraction of one borrowed from a different industry. And if your team has its own conventions on top of that, a preferred definition for a metric, a default it should assume unless told otherwise, org admins can teach AI Chat those standing instructions directly from the AI Chat tab on the settings page, so it keeps speaking your language even where that language gets specific to you
Visibility across sites, especially regulated ones, only earns trust if it comes with real governance. That's been true of OpsMoto since day one, and AI Chat holds to the same standard. It can look at your data, but it can't touch it, so there's no risk of a question accidentally changing anything. It only draws from the operational data OpsMoto already tracks, nothing more sensitive comes into play. Every question gets checked before an answer comes back, with safeguards built in.
Cutting manual reporting overhead was always the third leg of OpsMoto's original pitch, alongside visibility and governance, and AI Chat is where that shows up most obviously day to day. Getting an OpsMoto chart into a QBR deck used to mean rebuilding it somewhere else by hand. Now, with AI Chat you can generate a chart based on your question, export it directly, and drop it into whatever report you're already building.
Where This Leaves Your Deployment
Map View and AI Chat sit on top of the same Overview, Automations, and App Trends data OpsMoto already gave you. Nothing about what's tracked has changed, just how quickly you can learn about your deployment. If you're already an OpsMoto customer, both are live now. If you haven't brought OpsMoto into your operations yet, talk to your CSM to discuss joining the Beta program.
Digitally transform your operations with Tulip
See how systems of apps enable agile and connected operations