Background Jobs
Track the progress of long-running operations like collision detection, model conversion, and exports.
Overview
Some operations in BIM AVA can take several minutes:
- Collision Detection - Checking large models
- Model Conversion - IFC → XKT transformation
- GAEB Export - Large bill of quantities
- PDF Export - Comprehensive documents
- GIS Import - Large geodata sets
These operations run in the background so you can continue working.
Jobs Overview
Opening Jobs
Click the bell icon in the top navigation bar.
A badge shows the number of active jobs.
Jobs List
The list shows:
| Column | Description |
|---|---|
| Type | Icon for job type |
| Title | Job description |
| Status | Pending, Running, Complete, Error |
| Progress | Progress bar (for running jobs) |
| Time | Start time or duration |
Job Status
| Status | Icon | Description |
|---|---|---|
| Pending | In queue | |
| Running | Being processed | |
| Complete | Successfully finished | |
| Error | Failed | |
| Cancelled | Cancelled by user |
Job Details
Click on a job for details:
Running Jobs
- Progress - Percentage complete
- Phase - Current processing phase
- Details - Specific information (e.g., "Checked: 500,000 pairs")
- Estimated Time - Remaining time (if calculable)
Completed Jobs
- Result - Summary (e.g., "1,234 collisions found")
- Duration - Total time
- Action - Link to open result
Failed Jobs
- Error Message - What went wrong
- Details - Technical information
- Retry - Restart the job
Cancelling Jobs
Running jobs can be cancelled:
- Click on the job
- Click "Cancel"
- Confirm
Partial Results
For collision detection, already found results are saved. For other jobs, intermediate results are lost.
Deleting Jobs
Completed jobs can be deleted:
Delete Single
- Click on the completed job
- Click "Delete"
Delete All Completed
- Click "Clear All" at the bottom
- Only completed/cancelled jobs are removed
- Active jobs remain
Job Types
Collision Detection
Phases:
- Preparation - Loading models
- Extraction - Extracting geometry
- Detection - Finding collisions
- Storage - Writing results
Details show:
- Element pairs checked
- Collisions found
- Throughput (pairs/second)
- Estimated remaining time
→ See Collision Detection
Model Conversion
Phases:
- Upload - Uploading file
- Parsing - Reading IFC
- Conversion - Creating XKT
- Metadata - Generating JSON
Details show:
- Processed elements
- File sizes
- Errors (if any)
→ See Models
Export
Types:
- GAEB X83/X84/X86
- PDF documents
- Excel spreadsheets
Details show:
- Number of positions
- Generated pages
- File size
→ See Import/Export
Import
Types:
- GAEB files
- GIS data
- Master BOQ application
Details show:
- Imported positions
- Processed features
- Failed entries
Notifications
Browser Notifications
Enable browser notifications for:
- Job completed
- Job failed
- Click bell icon
- Enable "Notifications"
- Allow browser notifications
In-App Notification
Even without browser notifications:
- Badge on bell icon shows new events
- Toast message on completion (when app is in focus)
Performance Tips
Speed Up Collision Detection
- Use AABB method for preliminary check
- Reduce tolerance when there are many hits
- Only check relevant model pairs
Speed Up Conversion
- Use cleaned IFC files
- Remove unnecessary detail levels
- Use IFC4 Reference View when possible
Large Exports
- Export in sections for very large BOQs
- Reduce long text if not needed
- Use GAEB instead of PDF for bulk export
Troubleshooting
Job Stays in "Pending"
- Check server load
- Other jobs may have priority
- Wait or contact administrator
Job Fails
- Read the error message
- Check input data (valid files?)
- Try with smaller data sets
- Contact support for repeated failures
Progress Stops
- Job may still be running (large operations)
- Refresh the page
- For actual stop: Cancel and restart
See Also
- Collision Detection - Collisions between models
- Models - Model conversion
- Import/Export - GAEB and PDF export
- GIS Integration - Import GIS data