Documentation
MicroEng Overwatch Docs
Everything you need to set up, build, and manage automated workflows for BIM coordination, digital engineering, and project document management.
Operator Reference
Browse every operator by category — General, Logic, Navisworks, ProjectWise, CDE, and Integrations. Understand inputs, outputs, and configuration options.
Jump to section →
Setup + Onboarding
Install Overwatch, connect Navisworks and ProjectWise, set up CDE credentials, and configure schedules and watches.
Jump to section →
Security
Understand credential handling, AES-256 encryption, Auth0 authentication, and local-first data processing.
Jump to section →
Troubleshooting
Common issues, diagnostics, and resolution steps for Navisworks, ProjectWise, scheduling, watches, and email.
Jump to section →
Overview
MicroEng Overwatch is a Windows desktop application that automates repetitive workflows for BIM coordination, digital engineering, and project document management teams in the Architecture, Engineering, and Construction (AEC) industry.
Teams use Overwatch to visually build automated processes on a drag-and-drop canvas, connecting modular operators that handle tasks such as Navisworks model federation, file management, naming convention checks, email distribution, document control operations, and AI-powered document analysis. Workflows can run on demand, on a recurring schedule, or in response to file-system changes detected by the built-in watch system.
Overwatch removes the need for custom scripting or manual repetition across project delivery cycles. It gives teams a shared, auditable, and repeatable automation layer that sits alongside their existing BIM and document management tools.
Who Is It For
| Role | How Overwatch Helps |
|---|---|
| BIM Coordinators | Automate weekly or daily federation cycles — append models, run clash detection, export deliverables, and distribute results by email. |
| Digital Engineering Managers | Gain visibility into automated pipelines and standardise repeatable processes across projects. |
| Project Information Managers | Manage ProjectWise document stores, enforce naming conventions, manage metadata, and generate audit reports. |
| Design Technology Specialists | Integrate AEC tools (Navisworks, Revizto, ProjectWise) with cloud platforms (SharePoint, ACC, Google Drive) and enterprise systems (Jira, ServiceNow, Slack). |
Key Capabilities
| Capability | Description |
|---|---|
| Visual Workflow Builder | Build multi-step workflows by dragging operators onto a canvas and connecting them — no coding required. |
| Navisworks Automation | Launch, control, and export from Autodesk Navisworks directly within a workflow. Supports federation, search sets, and multi-format export. |
| ProjectWise Integration | Connect, search, export, upload, and manage Bentley ProjectWise documents as part of automated pipelines. |
| CDE Connectivity | Move files and data between SharePoint, OneDrive, ACC, Aconex, Dropbox, Google Drive, Microsoft Teams, and more. |
| Scheduled Execution | Run workflows on hourly, daily, weekly, or monthly schedules with a unified execution queue. |
| File-System Watches | Monitor folders for file changes and trigger workflows automatically when conditions are met. |
| AI-Powered Processing | Use configurable AI agents to analyse documents, enforce standards, and make structured decisions within workflows. Supports knowledge bases with RAG. |
| Email Distribution | Send emails with dynamic content and attachments to managed contact groups. Supports Resend and Microsoft Outlook providers. |
| Team Collaboration | Share projects, workflows, and contacts across a team with real-time cursor presence and synchronisation. |
| Enterprise Security | Auth0 authentication, AES-256 credential encryption, local-first workflow execution, and Stripe-managed billing. |
System Requirements
Operating System
Windows 10 or Windows 11
Internet Connection
Required for authentication, cloud sync, email delivery, and AI features
Navisworks (optional)
Navisworks Manage 2025 or 2026 — required only for Navisworks operators
ProjectWise (optional)
Bentley ProjectWise client with PowerShell tools — required only for ProjectWise operators
Getting Started
Go from installation to your first automated workflow in five steps.
Install
Download the installer from the MicroEng website and run it. Overwatch installs to your local Applications directory on Windows 10 or 11.
Sign In
Launch Overwatch and sign in with your email through the Auth0 authentication flow. Create an account if you don't have one.
Create a Project
Open the Projects pane and create your first project. Each project contains workflows, contacts, and settings.
Build a Workflow
Add a workflow to your project. Drag operators from the palette onto the canvas, connect them, and configure each step.
Run or Schedule
Execute your workflow manually with the Run button, set up a recurring schedule, or configure a watch to trigger it automatically.
Keyboard Shortcuts
Ctrl + SSave workflowCtrl + ZUndoCtrl + Shift + ZRedoCtrl + CCopy selected nodesCtrl + VPaste copied nodesDeleteDelete selectionCtrl + ASelect all nodesCtrl + FFocus operator searchSpace + dragPan canvasScroll wheelZoom in/outCtrl + 0Fit viewEscapeClose pane or modalUser Interface
Four main areas make up the Overwatch workspace.
Header Bar
Spans the full width. Contains the MicroEng logo, six main navigation tabs (Canvas, Scheduler, Watch, Contacts, Agents, Integrations), and the user account button.
Icon Rail
A narrow vertical strip on the far left with icons for toggling the three side panes: Projects, Operations (Operator Palette), and MicroEng AI assistant.
Side Pane
A collapsible panel for browsing projects and workflows, searching and dragging operators onto the canvas, or using the built-in AI assistant.
Main Content Area
The central area displaying the active tab's content — the workflow canvas, scheduler timeline, watch dashboard, contacts directory, agents configuration, or integrations settings.
Header Tabs
| Tab | Description |
|---|---|
| Canvas | The workflow builder. Drag operators onto a visual canvas, connect them, configure settings, and run workflows. |
| Scheduler | View and manage scheduled workflow runs, execution history, timelines, and the execution queue. |
| Watch | Configure file-system watches that monitor folders and trigger workflows on detected changes. |
| Contacts | Manage your project's contact directory, create user groups, and import/export via CSV. |
| Agents | Configure AI agents, manage knowledge bases, and review decision history. |
| Integrations | Set up credentials and connections for Navisworks, ProjectWise, Microsoft Outlook, CDE platforms, and third-party services. |
Themes
Overwatch supports both light and dark themes. Each theme is independently customisable with controls for canvas grid appearance, node accent colours, border opacity, connector styling, handle colours, and more.
Projects and Workflows
Projects
Projects are the top-level organisational unit. Each project is an isolated container for workflows, contacts, user groups, and settings. Projects can be private (visible only to you) or shared (visible to team members with a Teams licence).
Create a project from the Projects side pane. Give it a name and optional description.
Workflows
A workflow is a sequence of connected operators on a visual canvas that defines an automated process. Each new workflow starts with a Start operator placed on the canvas.
Workflows can be run manually, placed on a recurring schedule, or triggered by a file-system watch.
Workflow Management
| Action | Description |
|---|---|
| Edit Workflow | Load the workflow onto the canvas for editing |
| Run | Execute the workflow immediately |
| Enable / Disable | Toggle whether the workflow can be scheduled or triggered |
| Move Up / Down | Reorder the workflow within the project |
| Delete | Permanently remove the workflow |
Canvas Navigation
| Action | How |
|---|---|
| Pan | Click and drag on empty canvas space, or hold Space and drag |
| Zoom | Scroll wheel, or Ctrl + / Ctrl − |
| Fit View | Press Ctrl + 0 to zoom to fit all nodes |
| Select | Click a node. Shift-click to multi-select. Drag a rectangle to select a region. |
Flow Code Sharing
Flow Code is a shareable text representation of a workflow. Export a workflow configuration and import it into another project or share it with colleagues. Sensitive information (credentials, API keys) is stripped before export. Click the Flow Code button in the canvas header to copy it to your clipboard. Paste Flow Code to reconstruct operators and configurations on your canvas.
Operator Reference
Over 80 operators across six categories. Drag any operator onto the canvas to add it to your workflow.
General Operators
General operators form the foundation of every workflow. They handle workflow control, file management, communication, and human interaction.
Start
The entry point for every workflow. Automatically created when you create a new workflow. Supports a Priority setting (1–99) that determines execution order when multiple workflows are queued. Can be disabled to prevent the workflow from running.
Add Model File
Attach one or more individual model files (NWD, NWC, NWF) to the workflow and optionally load them into Navisworks. Displays file metadata (name, size, modification date). Per-file watch settings: deleted file detection, recent update highlight, file size delta rule.
Add Files from Folder
Scan a folder on your file system, apply filters (extension, filename, recursive), and pass matching files to downstream operators. Supports linking to a Watch for dynamic folder resolution. Auto-refresh on workflow run picks up new files.
Check File
Validate file names against a regex naming convention pattern and split the workflow into pass/fail branches. Files matching the pattern route to the Pass output; non-matching files route to the Fail output. Includes quick convention presets and test preview.
Copy / Move Files
Copy or move files from one location to another with optional renaming and filtering. Parametric filename builder for automatic renaming with tokens (date, project name, etc.). Conflict resolution: overwrite, skip, or rename with suffix.
Delay
Pause workflow execution for a specified duration (seconds, minutes, or hours). Useful for rate-limiting, waiting for external processes, or spacing out operations.
Send emails to contacts and groups with optional attachments and dynamic content. Select recipients (To, CC, BCC) from your project contacts. Customisable subject and body with template tokens. Two providers: Resend (default, via Supabase Edge Functions) or Microsoft Outlook (via Microsoft Graph). Automatic workflow metadata footer.
Approval
Gate workflow execution with a human approval step. Select an approver from project contacts, configure a timeout, and set an action on expiry. The workflow pauses until the approver accepts (continues) or declines (stops).
End
Terminate the workflow and record completion metadata (timestamp, duration, success status). Handles loop iteration when used with the Loop operator.
Logic Operators
Logic operators add flow control and intelligence to workflows, enabling iteration, AI processing, and multi-agent decision-making.
Loop
Iterate through a collection of files one at a time, executing the downstream workflow for each file individually. Collects files from upstream, emits one at a time, and advances when execution reaches the End operator. Repeats until all files are processed.
Agent
Run AI processing on upstream files and data. Select from multiple AI providers (OpenAI, Anthropic, OpenRouter) and models. Customisable system prompt, input template, and output format (text, JSON, or Excel). Supports reading PDF, images, Excel, CSV, and text files. Streaming progress updates during execution.
Council Agents
Run a multi-agent engineering review with an accept/reject decision and detailed audit trail. Configure a council of AI agents with different specialties. Each provides an independent assessment. Optional compliance auditor and chair roles. Binary outcome: ACCEPT (workflow continues) or REJECT (workflow stops).
Navisworks Operators
Control Autodesk Navisworks directly from your workflow. Requires Navisworks Manage 2025 or 2026 with the MicroEng Controller plugin deployed.
| Operator | Description |
|---|---|
| Run ViewPort | Launch the Navisworks engine. Select version (2025 or 2026) and mode (headless or windowed). |
| Close ViewPort | Shut down the running Navisworks engine with clean termination and optional force close. |
| Clear Viewport | Remove all loaded models without shutting down the engine. Useful between Loop iterations. |
| Select Set | Execute a search set or selection set within the active model by name or index. |
| Save As | Export the current model to NWD, DWF, FBX, IFC, or PDF. Parametric file naming with date/project/workflow tokens. |
| Publish to Revizto | Push models to Revizto using the Revizto Scheduler CLI. |
ProjectWise Operators
Deep integration with Bentley ProjectWise document management. Requires the ProjectWise client and PowerShell tools.
| Operator | Description |
|---|---|
| Connect | Authenticate and establish a session with a ProjectWise datasource. Supports IMS authentication and GUI login. |
| Saved Search | Execute a saved search and retrieve matching documents with metadata. |
| Export Docs | Download documents to a local folder. Supports saved search results, folder paths, or document references. |
| Upload Docs | Upload local files with optional check-in and duplicate handling (skip, overwrite, new version). |
| Metadata to CSV | Extract document metadata and export to CSV with custom column selection. |
| Set Attributes | Bulk update document attributes from a CSV manifest. Includes dry-run preview mode. |
| Lock / Check-in | Manage document check-out/check-in state in bulk (Check Out, Check In, or Free). |
| Workflow State | Transition documents through ProjectWise workflow states with comments. |
| Watch | Snapshot a saved search and detect added, modified, or removed documents since the last snapshot. |
| Permissions | Audit or apply folder permission (ACL) templates in read-only or apply mode. |
| Rendition | Generate renditions (PDF, iModel, DWG, DGN) with optional ZIP packaging. |
CDE Operators
Connect Overwatch to cloud-based document management and collaboration platforms. Configure credentials in the Integrations tab.
ACC (Autodesk Construction Cloud)
List Hubs, List Projects, List Top Folders, List Folder Contents, Get Item, Get Version, Download Version, Create Folder, Upload File
Aconex
List Documents (Register), Get Document Metadata, Download Document, Upload Document
SharePoint
List Folder, Search, Get Item, Download Item, Upload File, Create Folder, Move Item, Copy Item (Async), Delete Item, Create Sharing Link
OneDrive
List Folder, Search, Get Item, Download Item, Upload File, Create Folder, Move Item, Copy Item (Async), Delete Item, Create Sharing Link
Dropbox
List Folder, Search, Get Metadata, Download, Upload, Move, Copy, Delete, Create Shared Link
Google Drive
List, Search, Get, Download, Upload, Create Folder, Create From Text, Copy, Move, Update, Share, Delete, Contains/Is/Is Not Filters
Teams
Post Message to a Microsoft Teams channel
Outlook
Send Mail through your Outlook account via Microsoft Graph
ArcGIS Pro
Run Script, Run Tool (geoprocessing)
TeamBinder
SOAP Request, SOAP Request (JSON)
Integration Operators
Connect Overwatch to third-party SaaS platforms for messaging, project management, data management, and more.
| Platform | Operations |
|---|---|
| Slack | Post Message, Upload File, List Channels |
| Jira | Create Issue, Update Issue, Add Comment, Search JQL |
| ServiceNow | Create Record, Update Record, Get Record, Query, Delete Record |
| Google Sheets | Read, Append, Update, Clear, Lookup, Upsert |
| Google Calendar | List Events, Create Event, Update Event, Delete Event |
| Gmail | Send Email |
| Microsoft SQL | Query, Execute |
| MySQL | Query, Execute |
Operator Data Flow
How data moves between operators when they are connected on the canvas.
When operators are connected, data flows from upstream (left) to downstream (right). Each operator produces output data that the next operator in the chain can consume.
| Output Category | Examples |
|---|---|
| File System | File paths, enriched file metadata, folder listings |
| ProjectWise | Document references with metadata, search results |
| Data | CSV data, JSON data, table data, key-value pairs |
| Text | Plain text, HTML, Markdown, AI-generated content |
| Communication | Email drafts, email send results |
| Navisworks | Model state, viewpoints, clash results |
| Control Flow | Boolean values, counts, status codes |
| Analytics | Statistics, diff results, change detection data |
Template Tokens
Operators like Email and Agent support dynamic placeholders that are filled with data from upstream operators at run time. Tokens appear as coloured chips in the editor and reference specific output fields from upstream operators.
{{Add Files from Folder.fileCount}} — Number of files found
{{Save As.exportPath}} — Path of the exported file
{{Agent.response}} — AI agent's response text
Running Workflows
Manual Execution
Load a workflow onto the canvas from the Projects pane, then click the Run button in the canvas header toolbar. Each operator lights up as it executes, showing real-time status. Use Pause to temporarily halt execution, or End to terminate immediately.
Execution Order
Execution starts at the Start operator and follows connection edges downstream. Check File and Loop operators create branching or iterating paths. Execution ends at an End operator. Multiple Start operators execute in priority order (lowest number first).
Status Indicators
| Status | Indicator |
|---|---|
| Waiting | Default appearance — not yet reached by execution |
| Running | Animated glow or pulse effect on the active node |
| Success | Green status indicator |
| Error | Red status indicator with error message |
| Skipped | Dimmed appearance (disabled operators) |
Workflow Log
A real-time log panel on the right side of the canvas shows timestamped entries with node title, status icon, and message. Supports auto-scroll and text export.
Run Inspector
Enable Inspect Run to view per-node execution data: input data received, configuration used, output data produced, execution duration, and error details.
Issues Stack
A validation panel that checks for configuration errors before execution. Errors (red) block the run; warnings (yellow) flag potential issues. Click an issue to navigate to the operator.
Scheduler
Automate workflow execution on recurring schedules.
| Setting | Description |
|---|---|
| Enabled | Toggle the schedule on or off |
| Recurrence | Hourly, Daily, Weekly, or Monthly |
| Time | Specific time or interval for execution |
| Days (Weekly) | Which days of the week to run |
| Day of Month (Monthly) | Which day of the month to run |
Scheduler Tab
Displays a workflow list with schedule status and next run time, a visual timeline of upcoming and past executions, an execution history log with duration/status/results, and the current execution queue.
Unified Execution Queue
Only one workflow runs at a time. Queued workflows are sorted by priority (lower number = higher priority). Queue behaviour options: Queue (wait), Skip (don't run if busy), or Replace (swap with new run).
Watch System (Watches)
Monitor file-system locations and detect changes to trigger workflows automatically.
| Setting | Description |
|---|---|
| Name | A descriptive name for the watch |
| Enabled | Toggle the watch on or off |
| Source Folders | One or more file-system folders to monitor |
| Recursive | Monitor subfolders |
| Pattern Filters | File name or extension filters |
| Cadence | How often to check: interval-based or daily at a specific time |
| Source Logic | ANY (trigger if any source has changes) or ALL (trigger only if all sources have changes) |
Change Detection
| Change Type | Description |
|---|---|
| Added | New files that appear in the watched folder |
| Modified | Files whose content or metadata changed |
| Deleted | Files that are now missing |
| Renamed | Files that have been renamed |
When changes are detected, watches can log a summary and/or trigger a linked workflow for automatic execution. The Watch Diff Detail Window shows all detected changes with file names, change types, before/after metadata, and summary statistics.
Add Model Watch Settings
Individual model files in the Add Model File operator support per-file watch settings:
| Setting | Description |
|---|---|
| Deleted File Detection | Highlights files in red when the path is broken. Status shows "Metadata unavailable." |
| Recent Update Highlight | Green badge if modified within a configurable window (e.g., last 7 days). Ideal for weekly BIM federations. |
| File Size Delta Rule | Flags files whose size changed beyond a threshold percentage. Catches suspiciously small or large exports. |
Contacts and Distribution
Per-project contact directory for managing email recipients, approvers, and distribution groups.
| Field | Description |
|---|---|
| First Name / Last Name | Contact's name |
| Email address (required for email and approval operations) | |
| Company | Organisation the contact belongs to |
| Job Title | Role or position |
| User Groups | Distribution groups the contact belongs to |
| Flags | Custom flags for categorisation |
User Groups
Named collections of contacts for distribution lists. Each group has a colour accent for visual identification. Select a user group as an email recipient to send to all members.
CSV Import / Export
Import contacts from CSV by mapping columns to contact fields. Export all contacts and their details to CSV for external use.
Team Sync
For Teams licence users, contacts synchronise with the cloud backend in real-time. Contacts and groups added by one member are visible to others.
AI Agents
Configure AI agents for workflow operators and standalone assistance.
Agent Configuration
| Setting | Description |
|---|---|
| Name | A descriptive name for the agent |
| Description | What this agent specialises in |
| Provider | AI provider (OpenAI, Anthropic, OpenRouter, etc.) |
| Model | Specific AI model to use |
| System Prompt | Instructions defining the agent's behaviour and expertise |
| Temperature | Response randomness (0 = deterministic, 1 = creative) |
| Max Tokens | Maximum response length |
Knowledge Bases
Each agent can have a knowledge base — reference documents processed into a RAG system. Supported: PDF, Excel, CSV, text, and images (OCR). The agent searches the knowledge base for relevant information and includes it in the context.
MicroEng AI Assistant
A conversational AI assistant accessible from the icon rail. Answers questions about Overwatch features, suggests operator configurations, and helps troubleshoot workflow issues.
Decision History
All AI interactions are logged with prompt, response, workflow context, timestamp, model used, and for Council operations, each member's assessment and the final verdict.
Settings and Theming
Theme Configuration
Light and Dark themes, each independently customisable. Adjust border opacity, node category colours, node text colour, handle colour, connector colour, connector thickness, and canvas background.
Canvas Grid
Toggle the grid on or off. Choose grid type (Lines, Dots, or Cross pattern). Adjust colour, opacity, and spacing. The grid provides an alignment reference for placing operators.
Other Settings
Auto-Save (save workflows after changes), Compact Mode (denser operator palette), Processing Overlay (animated glow on executing operators), and notification preferences for completion, errors, watch triggers, and schedule reminders.
Application Data
User data is stored locally at %USERPROFILE%/FlowCoreUI/users/{userId}/ — including project data, contacts, settings, cached credentials, watch configurations, and execution logs.
Authentication and Subscription
Authentication
Overwatch uses Auth0 for secure authentication. Click Sign In to open your browser, authenticate with your email, and return to Overwatch via the secure microeng://callback protocol. Sessions are maintained with automatic token refresh.
Billing
Overwatch uses Stripe for subscription billing. Manage subscriptions, update payment methods, and view invoices through the Stripe customer portal accessible from the user button. Trial countdowns appear in the application header.
Licence Types
| Licence | Description | Best For |
|---|---|---|
| Solo | Individual licence for a single user. Supports up to 2 devices. | Independent professionals, small projects |
| Teams | Organisation licence with multiple members. Shared projects, collaborative features, centralised billing, personal sandbox for each member. | BIM coordination teams, enterprise deployments |
Teams Features
Shared projects visible to all members, team management with email invitations, admin and member roles, centralised billing, and personal sandbox projects for each team member.
Offline Access
Overwatch caches authentication and subscription status locally with a 30-day grace period. Projects, workflows, and settings remain accessible during network outages. Tokens refresh automatically when connectivity returns.
Integrations Setup
Configure credentials and connections for all external services in the Integrations tab.
Navisworks
Verify Overwatch has detected your Navisworks installation. The MicroEng Controller plugin must be deployed. Specify the installation path manually if not auto-detected.
ProjectWise
Add a datasource connection with credentials. Test the connection and ensure the Bentley PowerShell module is installed (use the Install PW Module button if needed).
Microsoft Outlook / Graph
Enter Azure AD application credentials (Client ID, Tenant ID), authenticate via the Microsoft login flow, and grant Mail.Send and User.Read permissions.
CDE Platform Credentials
| Platform | Credential Type |
|---|---|
| SharePoint / OneDrive | Microsoft Graph credentials |
| ACC | Autodesk Platform Services (APS) client credentials |
| Aconex | API key and instance URL |
| Dropbox | OAuth app credentials |
| Google Drive | Google Cloud service account or OAuth credentials |
Integration Platform Credentials
| Platform | Credential Type |
|---|---|
| Slack | Bot token and workspace details |
| Jira | API token, instance URL, and email |
| ServiceNow | Instance URL, username, and password |
| Google services | Service account credentials or OAuth tokens |
| SQL databases | Connection string, server, database, username, password |
Credential Security
- All credentials encrypted with AES-256-CBC before storage
- Encryption keys are machine-specific (derived from hostname and username)
- Credentials stored in the local vault, never in environment variables or plain text
- Credential passwords are never logged, even in development mode
Email System
Overwatch uses a secure, centralised email delivery system. The desktop application sends email requests to a Supabase Edge Function, which dispatches through Resend. The API key is stored in Supabase Secrets, never on client machines.
| Provider | Method | Use Case |
|---|---|---|
| Resend (default) | Via Supabase Edge Function | Primary delivery for all workflow emails. No per-user setup required. |
| Microsoft Outlook | Via Microsoft Graph API | For organisations requiring emails from their Microsoft 365 domain. |
Email Metadata Footer
Every workflow email includes an automatic footer with project name, workflow name, initiator email, organisation name, and UTC timestamp. This provides clear provenance for automated communications.
Email Security
No local API keys (Resend key stored in Supabase Secrets). Emails sent from verified domains only. HTML content sanitised to prevent injection. 25 MB default attachment limit. Full audit trail via workflow metadata.
Collaboration
Real-time collaboration features for Teams licence users.
Real-Time Presence
When multiple team members have the same workflow open: see other users' cursors on the canvas in real-time (each with a unique colour), view which operators others have selected, and see who is currently viewing in the canvas header.
Shared Projects
Projects marked as shared are visible to all team members. Contacts, user groups, watch configurations, and schedules in shared projects sync across the team through the Supabase cloud backend. Private projects remain isolated.
Troubleshooting
Common issues and resolution steps.
Navisworks
| Issue | Resolution |
|---|---|
| Navisworks cannot be found | Verify the installation path in the Integrations tab. Confirm the MicroEng Controller plugin is deployed. |
| Models stuck in "Metadata unavailable" | Verify file accessibility (check network drives). Refresh the workflow. |
| Navisworks operations timeout | Ensure no dialog is blocking execution. Check the engine version matches the Run ViewPort setting. |
| Cannot connect to Navisworks | Ensure only one instance is running. Close manually opened instances. |
ProjectWise
| Issue | Resolution |
|---|---|
| ProjectWise commands fail | Verify Bentley CLI tools are installed and the datasource is reachable. Check credentials. |
| Could not find PW module | Click Install PW Module in the Integrations tab, or install the PowerShell module manually. |
| Authentication fails | Re-enter credentials. For IMS authentication, verify identity server reachability. |
| Saved search returns no results | Verify the search name matches exactly. Test directly in ProjectWise. |
Scheduler
| Issue | Resolution |
|---|---|
| Scheduler doesn't run | Check for [SCHEDULER] log entries. Restart the application if absent. |
| Missed scheduled runs | The application must be open for the scheduler to operate. |
| Workflow stuck in queue | Check the execution queue. Manually end a hanging workflow from the Canvas tab. |
Watches
| Issue | Resolution |
|---|---|
| Not detecting changes | Ensure the watch is enabled and the folder path is accessible. Verify cadence is configured. |
| Triggered workflow not running | Check the workflow is linked and enabled. Verify the queue is not blocked. |
| False change detections | Check if antivirus or backup software is modifying files. Adjust pattern filters. |
Authentication and Email
| Issue | Resolution |
|---|---|
| Authentication fails | Verify internet connection. Check firewall access to Auth0 and Stripe. |
| Subscription not updating | Refresh the account popup or sign out and back in. |
| API key is invalid (email) | The Resend API key in Supabase needs to be set or refreshed. Contact your administrator. |
| Emails not reaching recipients | Check Resend domain configuration. Verify recipient addresses. |
| Outlook emails fail | Re-authenticate in the Integrations tab. Verify Mail.Send permission. |
| Attachments too large | Default limit is 25 MB. Reduce sizes or use file-sharing links. |
General
| Issue | Resolution |
|---|---|
| Application won't start | Ensure Windows 10 or later. Check no other instance is running. Try reinstalling. |
| Slow performance | Close unused workflows. Reduce operators on a single canvas. Check resource-heavy applications. |
| Data loss after crash | Enable auto-save in Settings. Workflows are stored locally and persist through restarts. |
| CDE/Integration operations fail | Verify credentials in the Integrations tab. Check service reachability. Review the Workflow Log. |
Frequently Asked Questions
What is MicroEng Overwatch?
MicroEng Overwatch is a Windows desktop application that automates repetitive BIM coordination and digital engineering workflows. It provides a visual drag-and-drop canvas where teams build automated processes by connecting modular operators for tasks like Navisworks model federation, file management, email distribution, and document control.
Who is MicroEng Overwatch for?
Overwatch is built for BIM coordinators, digital engineering managers, project information managers, and design technology specialists working in the AEC (Architecture, Engineering, and Construction) industry.
What operating system does Overwatch require?
Overwatch runs on Windows 10 and Windows 11. It is a desktop application (Electron-based) that executes workflows locally on your machine.
Does Overwatch require Navisworks?
Navisworks is only required if you use Navisworks-specific operators (Run ViewPort, Save As, Select Set, etc.). General workflow, email, file management, CDE, and integration operators work independently of Navisworks.
Does Overwatch require ProjectWise?
ProjectWise is only required if you use ProjectWise-specific operators. The Bentley ProjectWise client and PowerShell tools must be installed.
What CDE platforms does Overwatch integrate with?
Autodesk Construction Cloud (ACC), Oracle Aconex, Microsoft SharePoint, Microsoft OneDrive, Dropbox, Google Drive, Microsoft Teams, Microsoft Outlook, ArcGIS Pro, and TeamBinder.
What third-party services does Overwatch integrate with?
Slack, Atlassian Jira, ServiceNow, Google Sheets, Google Calendar, Gmail, Microsoft SQL Server, and MySQL.
How does the scheduler work?
The built-in scheduler runs workflows on hourly, daily, weekly, or monthly schedules. A unified execution queue ensures only one workflow runs at a time, with priority ordering for queued workflows.
What are Watches?
Watches monitor file-system folders for changes (added, modified, deleted, or renamed files) on a configurable cadence. When changes are detected, watches can automatically trigger linked workflows.
How does Overwatch handle security?
Auth0 for authentication, AES-256-CBC encryption for stored credentials, Stripe for billing. Core workflow execution is local-first — operational data stays on your machine. Cloud services are used for account management, email delivery, and team synchronisation.
Does Overwatch support AI capabilities?
Yes. AI Agent and Council Agents operators process files and data using configurable AI providers (OpenAI, Anthropic, OpenRouter). Agents can have knowledge bases for RAG-powered document analysis with citations.
How does team collaboration work?
With a Teams licence, projects can be shared across team members with real-time cursor presence, selection highlights, and synchronised contacts, user groups, and configurations.
Can I share workflows between projects?
Yes. Flow Code is a shareable text encoding of a workflow. Export it from one project and import it into another. Sensitive information is stripped before export.
Is there an offline mode?
Overwatch caches authentication and subscription status locally with a 30-day grace period. Projects, workflows, and settings remain accessible during network outages.
How do I get support?
Visit the MicroEng support page at microeng.app/support or email admin@microeng.app.
Need implementation guidance?
We can walk your team through operator selection, setup sequencing, and rollout best practices for the current pre-release stage.