- Organizational sizes or stages where this product may be excessive
- Small organizations with limited asset counts and no dedicated administration team may find the configuration and learning curve disproportionate to needs.
- Industries or use cases where competitors are more aligned
- Enterprises prioritizing a global EAM ecosystem with extensive AI/IoT/partner tooling may find IBM Maximo more aligned to those requirements.
- Organizations focused primarily on office/hybrid workplace booking and employee experience may prefer workplace-centric platforms such as Eptura Workplace.
- GIS-centric municipalities that require Esri-native, map-driven field collection and mobile-first workflows may prefer Cityworks or OpenGov EAM depending on GIS maturity.
- Technical or compliance requirements that may not be met (based on public evidence gaps)
- Procurement processes that require publicly documented SOC 2 Type II, ISO 27017/27018, detailed data residency options, or a public trust center with extensive security documentation should verify those items directly with the vendor, as they were not clearly documented in the retrieved GoAssetWorks materials.
- Budget constraints
- Organizations with tight budgets may find the product less suitable given reviewer comments about pricing; cost modeling should include potential add-on fees and implementation services.
- Procurement guidance and red flags
- If pricing and packaging require negotiation and predictable costs are required, request detailed line-item scoping and clear definitions of what constitutes add-on functionality.
- Current limitations acknowledged by the vendor
- Public vendor materials emphasize capabilities and do not provide a detailed public list of known issues.
- Features on the roadmap (not yet available)
- No comprehensive roadmap details were found in the public sources retrieved for this research.
- Scale limitations
- Scale characteristics are not explicitly documented in the retrieved public sources.
- Security or compliance gaps (public documentation gaps)
- ISO 27001:2022 certification is publicly claimed for AssetWorks Facilities.
- SOC 2 Type I/II, ISO 27017/27018, detailed data residency options, and enterprise identity features (SAML/SCIM) were not clearly documented for GoAssetWorks in the retrieved materials; buyers should validate during security review.
- API limitations or integration constraints
- API documentation is available for some fleet-side products (e.g., Work Order API), but public information on API coverage, rate limits, and feature parity across modules is limited. Buyers should request API specifications and integration guides during technical evaluation.