Currently, we have been using Workplan and Schedule in Autodesk Construction Cloud this a powerful tool for planning and collaboration. We prefer Workplan, over Schedule, as it has the ability to be able altered. Opposed to Schedule which still relies on working in another product to adjust dates etc, so there is duplication here which makes it ineffective. Workplan is much better solution as it allows you to work in one platform to make changes, but its potential is limited by the lack of any accessible APIs and webhooks.
Enabling these capabilities would deliver significant benefits:
1. Seamless Integration
- APIs allow Workplan data to connect with ERP systems, scheduling tools, and reporting platforms like Power BI.
- Eliminates manual data entry and reduces errors, improving efficiency across the project lifecycle.
2. Automation of Repetitive Tasks
- Webhooks enable event-driven automation (e.g., trigger notifications when tasks change status, auto-update dashboards).
- Saves time for project teams and ensures real-time visibility.
- We are a homebuilder and have a few standard templates for schedules that we use over and over, the import function is great as it imports the plan, but we have zero ability to be able to trigger any other tasks, such as milestone payments in our ERP, etc.
3. Enhanced Customization
- APIs empower developers to build custom workflows, dashboards, and mobile apps tailored to unique business needs that they already have.
- Supports innovation without waiting for native feature releases.
4. Data Transparency and Analytics
- Exposing APIs ensures open access to structured data, enabling advanced analytics and predictive insights.
- Helps organizations leverage AI and machine learning for better forecasting and risk management.
5. Industry Standard Practice
- Other platforms already offer robust API ecosystems if Autodesk where to provide this in workplan they would be providing similar capabilities which will ensure Autodesk remains a leader in connected construction technology.
