yCloudx frequently asked questions

yCloudx is a connected platform for computerised maintenance management (CMMS), enterprise asset management (EAM) and facility operations. Cloudy AI and connected technologies support selected workflows, from field reporting to operational insights. Built in Malaysia, yCloudx brings maintenance, asset and facility records into one operational context.

It supports facility, maintenance and engineering managers, technicians, asset teams and operational administrators who need to plan work, manage records and monitor performance.

yCloudx serves maintenance-intensive organisations including property and facility management, manufacturing, government, healthcare, hospitality and industrial operations. The relevant modules and workflows depend on each organisation’s needs.

Yes. yCloudx can support a small maintenance team or a larger organisation with multiple sites and user roles. Discuss your users, asset volumes and workflow requirements to define a suitable scope.

Yes. Operations can be organised by entity, system site, building, location, section and asset, with access and reporting configured for the agreed structure.

Yes. The yCloudx web platform supports multiple languages. Each user can choose their own language, or a company can set one default for everyone. Additional languages can be added on request.

A computerised maintenance management system helps teams plan maintenance, manage work orders and keep service records. Explore yCloudx CMMS & Maintenance for the detailed workflow.

Enterprise asset management connects asset information with lifecycle activities, maintenance history and operational decisions. Explore yCloudx Asset Management (EAM).

CMMS focuses primarily on maintenance execution and records. EAM takes a broader view of assets throughout their lifecycle. yCloudx connects both so maintenance activity can be reviewed alongside the asset record.

Yes. Preventive Maintenance supports recurring schedules and planned work. Corrective Maintenance supports fault reporting, assignment, repair and reviewed completion.

Yes. Supported asset workflows cover registration, assignment, verification, transfer and disposal, with maintenance history and depreciation information where configured.

Yes. Maintenance and asset records connect with wider facility workflows such as locations, vendors, tenants, compliance and utilities. See Facility Management for the wider scope.

Alongside maintenance and assets, selected modules cover spare parts, meters, projects, tenant and visitor management, compliance documents, utility billing and workforce operations. Choose the capabilities relevant to your operation rather than deploying everything at once.

Yes. Module selection and configuration can be agreed around your operational requirements and subscription scope. Confirm dependencies and any implementation work during the requirements review.

Yes. Spare Parts & Inventory supports stock records, stock-in and stock-out activity, critical-stock visibility and purchase requisitions, with links to maintenance and assets where configured.

Yes. Meter Management supports reading records, reading history, trends and configured rules that can trigger maintenance work.

Yes. Dedicated Project Management and Utility Billing modules extend operational management. Their setup and connection to other workflows are agreed during implementation.

Cloudy is the AI layer within supported yCloudx workflows. It helps users draft information, interpret input and explore operational records. It supports people’s decisions rather than replacing their responsibility to review the result. See Cloudy AI.

Assist helps draft information from text; Voice interprets spoken input; Inspect analyses images or documents; Insight helps users ask questions about authorised system data; Predict reviews available history for risk signals and maintenance recommendations.

Yes. Cloudy supports multilingual interaction, including voice input in supported workflows. Confirm the languages and terminology relevant to your team during a demonstration.

Yes. Cloudy Inspect can extract information and suggest descriptions, classifications or follow-up actions from supported images and documents. Users should check the source and review suggestions before applying them.

Yes. Authorised users can ask questions about available yCloudx records to explore summaries, historical patterns and recurring issues. Answers depend on accessible data and the supported workflow, and should be checked against source records.

Cloudy Predict analyses available maintenance and operational history to identify patterns, potential risk signals and preventive actions. It is decision support, not a guarantee of failure prediction. Results depend on the quality and completeness of the underlying records.

Yes. Native mobile apps are available for supported yCloudx workflows. Confirm device compatibility and the modules your users need during your demonstration.

Yes. Technicians can access assigned work, review asset context and update supported maintenance workflows while working on site.

Yes. Supported mobile maintenance workflows allow users to capture updates offline and synchronise later. Confirm which forms, attachments and operations are available offline for your deployment.

Yes. QR codes support access to relevant records and workflows, including asset identification and fault reporting where configured.

Yes. Supported work-order workflows allow teams to add photos and attachments to document reported conditions, work performed and completion evidence.

Yes. Integration can connect yCloudx with other enterprise systems, subject to available APIs or interfaces, access permissions and an agreed implementation scope.

Yes. API-based integration is available. Discuss the required records, data direction, update frequency and authentication requirements so the team can confirm the supported endpoints and scope.

Yes, where the required interfaces are available and the integration is agreed. yCloudx complements enterprise ERP with maintenance, asset and operational workflows; it should not be assumed to replace a full accounting or general-ledger system.

Yes. BIM Integration connects building-model context with supported operational and asset workflows. Model availability, mapping and implementation requirements should be reviewed first.

Yes. IoT Integration can bring connected readings into agreed monitoring or maintenance workflows. Device compatibility, data access and trigger rules depend on the selected interfaces and configuration.

Yes. Single sign-on is available. Compatibility with your identity provider, access policies and deployment requirements should be confirmed during the integration review.

Yes. yCloudx is available as a cloud-based platform, allowing authorised users to access supported workflows without managing the hosted application infrastructure themselves.

Yes. On-premise deployment is available where appropriate. Infrastructure, security, maintenance, backup and support responsibilities should be agreed before deployment.

Implementation typically includes a requirements review, module and workflow configuration, data preparation, testing, training and rollout. The plan depends on your scope, data readiness and integration requirements; there is no single fixed duration for every organisation.

Existing records can be assessed for migration. The team will review source formats, data quality and field mapping, then agree what can be imported and how it will be validated.

Yes. Modules, forms, responsibilities and supported workflows can be configured around agreed requirements. Any additional development or integration should be scoped separately rather than assumed to be included.

Yes. Training is available to help administrators and users work with the agreed modules and workflows. Format, audience and coverage are defined as part of the implementation or support arrangement.

Your organisation owns the data it enters into its yCloudx account. Available export options and any migration or offboarding requirements should be reviewed with the team and reflected in the service agreement.

yCloudx uses layered measures including encrypted connections, controlled user access and backups. The applicable hosting, operational controls and customer responsibilities depend on the deployment. No system should be described as completely secure.

Yes. yCloudx uses HTTPS to encrypt connections to the hosted service. Discuss any additional encryption or network requirements during your security review.

Backups are part of the hosted service arrangements. Confirm retention, recovery procedures and responsibilities for your deployment; on-premise backup arrangements must be agreed explicitly.

Access is assigned through user accounts, roles and permissions so users can work with the relevant modules and records. Your organisation should define responsibilities and review access as staff and roles change.

Contact the yCloudx team with your required hosting location, security policies and procurement criteria. Confirm the agreed arrangement before implementation rather than assuming a particular region or certification.

Software updates are included under the applicable subscription agreement. Confirm the update and maintenance arrangements for your deployment, especially for on-premise installations or separately scoped custom work.

The subscription scope is agreed around your selected modules and operational requirements. Request a proposal for your organisation rather than assuming a standard price covers every deployment, integration or service.

Yes. Additional modules can be discussed as your requirements develop. The team will review configuration, data and integration dependencies before agreeing the expanded scope.

Yes. Customer support is provided under the agreed service arrangement. For user guidance, explore the Knowledge Base; contact the team to confirm support channels and coverage.

Use the Contact Us / Request a Demo form. Tell us about your sites, assets and current challenges so the demonstration can focus on relevant workflows.