This proposed agreement is published for transparency and review. It does not itself grant software rights, replace an executed Numerish contract or bind a customer. The final agreement requires confirmation of the contracting entity, governing law, licence metrics, support and warranty terms, liability provisions, approval and effective date through Numerish's governed legal publication process.
1. Agreement scope and licensee
This proposed Software License Agreement governs the AEC360 desktop application, eligible cloud capabilities, authorised components, documentation, updates and licensed modules supplied by the applicable Numerish contracting entity. It is subject to the accepted order, entitlements and any negotiated enterprise or government agreement.
2. Definitions and licence record
“AEC360” means the licensed design and engineering software; “Licensee” means the person or entity assigned the entitlement; “Authorised User”, “Device”, “Seat”, “Workspace”, “Term” and “Edition” take their meaning from the relevant order or signed licence record.
3. Licence grant
Subject to payment where applicable and compliance with this Agreement, Numerish grants a limited, non-exclusive, non-transferable, non-sublicensable licence to install and use AEC360 within the accepted edition, user and device quantities, term, territory, project or workspace scope. Ownership of the Software remains with its licensor.
4. Desktop, cloud and hybrid usage
Desktop and cloud offerings may have different feature sets, services, storage and performance characteristics. A desktop licence does not automatically include cloud collaboration, and a cloud entitlement does not automatically include all desktop modules. Hybrid deployments follow the rights defined in the applicable purchase and technical configuration.
5. Trials, educational use and evaluation
Evaluation or educational rights must be identified in the entitlement. Such rights may limit time, eligible users, output distribution, commercial usage or support. Expiration does not transfer ownership of customer project files.
6. Named users, devices and organisational licensing
Access may be tied to named professionals, workspaces, authorised devices or an enterprise pool. Administrators must manage assigned users and license counts. Account sharing, unauthorised concurrent use, cloning, false device identification and circumvention of licence enforcement are prohibited.
7. Activation and periodic entitlement checks
Online activation and signed entitlement leases may be required. Offline operations, sovereign deployments and air-gapped activation are available only where supported and approved by contract. The Licensee must safeguard access credentials and report compromise.
8. Permitted design and engineering workflows
AEC360 may provide architectural, civil, structural, geotechnical, mechanical, electrical, BIM, documentation, analysis and quantity capabilities according to the licensed edition and implemented version. Product roadmaps, previews and future features are not licensed deliverables unless stated in an accepted order.
9. Project files and intellectual property
Licensee and its contributors retain their intellectual property in lawfully created project files, models, drawings, schedules, libraries and other project outputs. AEC360 does not acquire ownership merely by processing, storing or exporting these materials. Third-party library and reference content may be governed by separate licences.
10. Professional responsibility and public safety
AEC360 assists qualified users; it is not a substitute for independent professional judgement, site investigation, code interpretation or competent engineering design review. The responsible registered professional must verify input data, materials, models, assumptions, analysis, compliance and final drawings before construction, manufacture or other safety-critical reliance.
11. Standards, codes and engineering calculations
Design codes, calculation engines, loads, factors, boundary conditions and generated results depend on the selected configuration and software version. Licensee must independently validate applicability, jurisdiction, design assumptions and outputs. Inclusion of a standard name is not a certification, regulatory approval or warranty that every clause is implemented.
12. Interoperability and third-party formats
Import and export formats, including IFC, DWG, RVT, STEP and other CAD/BIM ecosystems, may require separate engines, authorisations or licences and are subject to technical limitations. Not all metadata, geometry, materials, constraints, annotations or version-specific features will transfer without loss. Licensee must review converted files before relying on them.
13. BIM collaboration and shared workspaces
Collaboration, cloud storage, review workflows, synchronization, permissions and version history are subject to purchased capabilities and organisational policy. Licensee is responsible for project member authorisation, publishing approvals and correct file-version coordination.
14. Professional credentials, stamps and seals
Any professional stamp, digital seal or approval tooling must be used only by persons duly authorised in the relevant jurisdiction and discipline. The presence of a credential, digital signature or stamp in a report does not relieve a professional of their statutory and ethical responsibilities.
15. AI-assisted features and automated recommendations
AI-enabled drafting, classification, design suggestions or analyses may be incomplete, biased or wrong. Outputs require appropriate evaluation and cannot autonomously authorize safety-critical design, regulated professional certification or construction release. Use of connected AI providers is subject to relevant privacy and service agreements.
16. Installation, updates and supported systems
Installation and operation require compatible hardware, operating systems and supported software dependencies. GPU support, plugins, analysis engines and operating-system compatibility can vary. Security updates, migration tools and version support depend on the edition and release policy.
17. Third-party components and software rights
Certain interoperability engines, numerical solvers, formats, fonts, libraries and integrations may carry third-party open-source or proprietary licence terms. Such terms apply to the relevant components; this Agreement does not grant rights that Numerish is not authorised to sublicense.
18. Data protection, encryption and recovery
Personal information in accounts and connected services is handled under the Privacy Policy and applicable data-processing terms. Users should protect local and remote project files, maintain tested backups and manage access to devices and workspaces. Available encryption, retention and recovery protections vary by configuration and agreement.
19. Compliance, security and regulated deployments
Industry and government use can require specific cryptographic controls, regional hosting, licensing, vendor due diligence, professional authorisation and independent acceptance. No government-grade certification, regulated approval or universal data residency commitment is created by this Agreement alone.
20. Fees, renewals and capacity
Fees, currencies, devices, subscriptions, upgrade/downgrade rules, storage, team capacity, renewal, termination and cancellation are governed by the accepted quotation, subscription or enterprise order. The Licence Manager may enforce approved technical entitlements; billing disputes remain governed by applicable contractual and statutory rights.
21. Restrictions
Licensee must not distribute counterfeit copies, circumvent licence validation, tamper with signatures, remove proprietary notices, misuse regulated credentials, unlawfully access another party’s models, or permit prohibited automated exploitation. Reverse engineering and interoperability exceptions mandated by applicable law are preserved.
22. Term, suspension and termination
A licence is valid for the term stated in its entitlement and may be suspended or terminated in accordance with the applicable agreement, security requirements and mandatory law. Termination must not be used to intentionally corrupt customer projects. Continued access to services, export options, updates and backups is subject to the executed agreement.
23. Warranties, liabilities and dispute provisions
Any negotiated warranties, performance standards, liability allocations, remedies, indemnities, governing law and dispute forum must be stated in the executed order or other binding agreement, subject to non-excludable legal rights. For project safety and certification, responsibility remains with the relevant qualified professionals and organisations.
24. Conflicts, modifications and contact
A signed and specifically applicable enterprise or government agreement prevails over conflicting public statements. Material changes require controlled publication and applicable notice or renewed acceptance. For legal or licensing enquiries, visit Contact Numerish.