FME Flow Asset Inventory Script: Take control of your FME workspaces
Managing a growing library of Workspaces in FME Flow can quickly become complex. Between scheduled automations, compatibility with ArcGIS and Python, shared parameters, and integrations with third-party systems, the risk of breaking something during updates or migrations is real. And without a centralized view, even small issues can spiral into major disruptions.
The FME Flow Asset Inventory Script is your turnkey solution for gaining complete, automated visibility into every Workspace in your environment. Whether you’re planning a migration, preparing for an audit, or simply want to run a tighter ship, this tool puts you in control.
The Value Behind our Inventory
- No more manual digging
Get a centralized report of all Workspaces, configurations, and interdependencies in one place. - Boost performance & reliability
Quickly identify bottlenecks, detect unnecessary complexity, and uncover opportunities to optimize.
- Minimize risk
Know your environment inside and out to prevent outages, broken workflows, and migration nightmares. - Accelerate migrations
All the insights you need to deploy with confidence—organized, complete, and export-ready.

Everything You Need for 360° Visibility
Our all-in-one solution gives you a complete picture of your FME Flow environment. From compatibility checks to API call analysis, every detail is captured so you can manage your platform with confidence and precision.
What’s included in your package?
- Preconfigured FME workspace: A ready-to-use base workspace
- Complete documentation: Step-by-step implementation guide
- Onboarding session: Training and support for initial deployment
- Excel report: Consolidated report of all extracted information
- Optional customizations: Integration with databases (SQL, Oracle, etc.) and visualization through Power BI or other Business Intelligence tools
Deep dive into workspace details
- ArcGIS and Python compatibility
- Saved version (FME build)
- Dependencies (parent, child, blocking)
- Data sources: Reader and writer types, file paths, etc.
- API call analysis (via HTTPCaller and used URLs)
- User parameters and deployment settings
Extracted information from your FME Flow environment
- Workspace names
- Workspace owner
- Repository
- Number of executions (over a configurable time period)
- Workspace descriptions