Frequently Asked Questions

Q1: What is Five Hundred?

Five Hundred is a solar O&M CMMS (computerized maintenance management system) built natively inside Microsoft 365. It is developed by WIZSP and deploys entirely inside the client’s own Microsoft Azure tenant, eliminating third-party cloud subscriptions and ensuring full data sovereignty for European solar operators. Five Hundred is designed for operators managing portfolios of 50MW or more across multiple sites.

Q2: How is Five Hundred different from other solar CMMS platforms?

Five Hundred is the only solar CMMS that runs natively inside Microsoft 365 — using Power Apps, Dataverse, Power Automate, Power BI, Teams, and Azure Entra ID — without requiring a separate SaaS subscription. Competing platforms such as UpKeep, Fiix, and IBM Maximo require third-party cloud infrastructure, monthly subscription fees, and custom API integrations to connect with Microsoft tools. Five Hundred is already inside the Microsoft ecosystem your team uses daily.

Q3: What does “CAPEX pricing” mean for a CMMS?

A CAPEX (capital expenditure) pricing model means you pay a one-time implementation fee rather than a recurring monthly or annual subscription. Five Hundred uses a CAPEX model: clients pay for the implementation project, then own the platform permanently with no ongoing licence fees. Over a five-year horizon, this typically delivers 60–80% lower total cost of ownership compared to SaaS-subscription CMMS platforms, which charge per user or per site indefinitely.

Q4: Where is my data stored when I use Five Hundred?

All data is stored inside your own Microsoft Azure tenant — the same infrastructure environment your organization already controls. WIZSP does not host, access, or process your operational data. This architecture means your solar O&M data never leaves your organization’s legal control, satisfying EU GDPR requirements, NIS2 compliance obligations, and any investor data sovereignty contractual requirements.

Q5: Does Five Hundred comply with the EU NIS2 Directive?

Five Hundred’s architecture is inherently aligned with NIS2 requirements for operators of essential services in the energy sector. Because all data resides inside the client’s own Azure tenant, the platform satisfies NIS2’s requirements for supply chain security, incident reporting data integrity, and network security measures without requiring third-party data processing agreements. Operators using cloud-hosted CMMS platforms from non-EU vendors face specific NIS2 exposure that Five Hundred eliminates by design.

Q6: How does Five Hundred integrate with SCADA systems?

Five Hundred connects to SCADA alarm feeds via Power Automate, Microsoft’s workflow automation platform. When a SCADA system generates an alarm — such as an inverter fault — Power Automate automatically creates a structured work order in Five Hundred’s Dataverse database, assigns it to the responsible technician based on site and fault type, and notifies them via Microsoft Teams. This eliminates the manual triage step that typically delays fault-to-technician assignment by 30–90 minutes.

Q7: How does Five Hundred help with IEC 62446 compliance?

IEC 62446 is the international standard defining documentation requirements for PV system commissioning and ongoing operation. Five Hundred includes a structured IEC 62446 documentation module that captures, stores, and version-controls all required commissioning records, inverter certificates, string test results, and IR thermography reports. Because documents are stored in SharePoint — part of Microsoft 365 — they are automatically subject to audit-trail, versioning, and role-based access controls that satisfy IEC 62446’s documentation integrity requirements.

Q8: What is the minimum portfolio size for Five Hundred?

Five Hundred is designed for solar operators managing portfolios of 50MW or more across multiple sites. Below this threshold, the operational complexity that justifies a purpose-built CMMS — multi-site work order management, structured preventive maintenance scheduling, investor reporting automation — is typically insufficient to deliver the return on investment that CAPEX software requires. For operators at 50MW+ with multiple sites and field technician teams, Five Hundred typically reaches ROI breakeven within 18 months.

Q9: Can Five Hundred be used without Microsoft 365?

No. Five Hundred is built natively on Microsoft 365 and requires an active Microsoft 365 tenant. This is a deliberate architectural choice, not a limitation. For operators already on Microsoft 365 — which includes more than 70% of mid-to-large European enterprises — this means Five Hundred deploys inside infrastructure already licensed, secured, and supported by their IT department. For operators not yet on Microsoft 365, WIZSP can advise on tenant setup as part of the implementation scoping process.

Q10: Does Five Hundred replace Microsoft Dynamics 365 Field Service?

Five Hundred serves a similar work order and field service use case to Microsoft Dynamics 365 Field Service but is purpose-built for solar O&M workflows rather than generic field service. Key differences: Five Hundred includes solar-specific asset hierarchies (inverters, string boxes, trackers, meters), IEC 62446 documentation modules, SCADA alarm integration, and solar investor reporting templates — none of which are native to D365 FS. Five Hundred also typically costs significantly less to implement for a solar operator of 50–500MW than a full D365 FS deployment.

Q11: How does Five Hundred price its implementation?

Five Hundred uses a CAPEX pricing model with a fixed-price core platform and separately scoped module add-ons. The final implementation price is determined by four variables: total portfolio size in megawatts, number of active technicians, number of managed sites, and required day-one modules. WIZSP provides a fixed-price proposal after a scoping conversation — there are no hidden per-user fees, and the price does not increase as the portfolio grows after go-live.