What products make up The Works Suite?
The Works Suite includes Fuzion ProjectWorks, Fuzion ConstructWorks, Fuzion365 FieldWorks, and Fuzion ProgramWorks. Together they address portfolio forecasting and project controls, document and construction management, field productivity, and program governance for construction, engineering, utility, and other high-stakes capital delivery environments.
Each product can be evaluated on its own, while the suite is designed around a coordinated architecture and data model.
Which Works Suite product supports field execution?
Fuzion365 FieldWorks connects field correspondence, site dashboards, and Bluebeam workflows within Microsoft 365. RFIs, submittals, change orders, and transmittals help field and office teams follow the same record. Review identity, licensing, included modules, and integration requirements with Fuzion before selecting a deployment scope.
Field QA/QC and inspections remain planned capabilities, not a current module. Module scope for every suite product is confirmed in your statement of work.
How can ProjectWorks, FieldWorks, and ProgramWorks be deployed?
Fuzion ProjectWorks, Fuzion365 FieldWorks, and Fuzion ProgramWorks describe SaaS or private Microsoft tenant options. ProgramWorks materials also identify Commercial, GCC, and GCC High environments. Eligibility, identity, data governance, licensing, integration scope, and supported capabilities are confirmed with your team for the environment you choose.
These deployment models are distinct from the PaaS model used for ConstructWorks.
How is ConstructWorks offered?
Fuzion ConstructWorks is a document and construction management PaaS, not a SaaS-or-private-tenant offering. It can be Fuzion-hosted or deployed in the customer’s Azure environment, with Fuzion managing the application platform. Its scope includes document understanding, custom forms, configurable workflows, approvals, and rich metadata.
Included modules, AI validation, integration scope, and implementation timeline are confirmed in your statement of work. Workflow alignment does not establish regulatory or nuclear compliance certification.
Can organizations use one Works Suite product independently?
Yes. Organizations can discuss a focused product or module without adopting every application at once. Start with field execution, document workflows, project controls, or program governance; dependencies, integration boundaries, included capabilities, and implementation timeline are confirmed in your statement of work.
This modular structure lets evaluation begin with the operational area that best matches the organization’s current need.
What existing systems does The Works Suite connect with?
Connection points vary by product. Current page materials identify Microsoft 365 and Bluebeam for FieldWorks; SAP, Oracle, Maximo, Microsoft 365, and Power BI as integration options for ProjectWorks; and Primavera P6, EcoSys, OpenText, SAP, Maximo, and Power BI as integration options for ProgramWorks.
Integrations are configured for each client during implementation; connector scope is confirmed in your statement of work.