Renewable energy installation and service
Connect the commercial promise
to delivery, assets and service.
PromiseInstalled asset
For renewable technology businesses that sell, deliver, install and support customer assets. Survey, design status, equipment, installation, commissioning, the installed asset and any service responsibility are one connected chain. We help connect that chain through Microsoft business applications, data and operational intelligence.
This is an installation and service proposition. It is not a claim of engineering design, certification or grid-connection expertise.
In short
What renewable leadership is actually trying to control.
Before capability, the question is which outcomes need to move. These are outcome areas to baseline, not benchmark promises.
Pipeline quality
Whether an enquiry is a real, surveyable, deliverable opportunity before it is promised a date.
Site and survey readiness
Whether site information is complete enough for design and installation to rely on it.
Commercial handover
Whether delivery inherits the scope, assumptions and exclusions that were actually sold.
Equipment readiness
Whether the equipment behind an installation date has been ordered, received and allocated.
Installation reliability
Whether committed installation dates hold, and what causes them to move when they do not.
Project margin
Whether the cost of an installation is visible before it closes rather than after invoicing.
Customer communication
Whether the customer can be told status, date changes and completion without a manual hunt.
Commissioning completeness
Whether testing, certification and documentation exist as evidence rather than as an assumption.
Installed-base visibility
Whether the organisation knows what it installed, where it is and what remains under warranty.
Service control
Where service forms part of the commercial model, whether entitlement, work and cost are controlled.
Scope
Who this page serves, and who it does not.
This is an adjacent specialist proposition rather than a claim to cover the whole renewable-energy market. Saying so is more useful than implying coverage we cannot evidence.
Business models in scope
- Installers and integrators that sell, design, install and support customer solutions
- EPC and project delivery organisations delivering engineered installation projects
- Service and O&M providers maintaining an installed base
- Equipment distributors supplying installation programmes
- Mixed models combining installation, project delivery and ongoing service
Not claimed here
- Utility-scale developers and generation portfolio owners
- Energy traders and PPA management
- Grid operators and connection authorities
- Pure equipment manufacturing operations, where the manufacturing proposition applies instead
The operating principles repeat across solar PV, storage, EV charging and heat technologies, but design, equipment, installation, commissioning and service requirements vary by technology. We do not provide specialist renewable engineering design or certification.
The operating reality
The customer buys an outcome. The organisation coordinates an entire chain of commitments behind it.
Requirement, site, survey, design, equipment, supplier, availability, installer, project, schedule, certification, commissioning, finance, asset, warranty and service are all connected, whether or not the systems are.
The customer buys an outcome
Behind a single agreed price sits a chain of commitments across design, equipment, people, schedule and aftercare.
The site decides what is possible
Survey information, access and constraints shape the design long before anyone reaches the installation date.
The design creates the cost
Equipment, quantity and configuration are commercial decisions, not only technical ones.
Procurement decides whether the plan is real
Lead times and availability can set the installation date, whatever the schedule says.
External dependencies sit outside the plan
Site readiness, approvals, connection activity and third parties still need an owner, a date and a status.
The asset outlives the project
Commissioning, handover, warranty and service can run for years after the project closes.
When these are disconnected
- Handoffs become manual
- Customer updates become difficult
- Project margin becomes harder to see
- Field teams lack context
- Procurement becomes reactive
- Leadership struggles to see delivery risk
Winning the customer is only the beginning. The commercial promise has to survive delivery.
A quoted installation creates commitments across design, equipment, procurement, resource, schedule, cash, installation, commissioning and aftercare. If those commitments are not connected, coordination cost rises with volume.
Why this is not the construction page
The underlying project controls are familiar. The difference is how site, technical design, equipment, installation, commissioning and installed-asset service interact.
Commercial commitment, project, procurement, field activity and subcontractors are covered under Construction. This page adds the specialist layer around a renewable installation.
Site qualification
Whether the site supports the solution being discussed at all.
Technical survey
Structured measurement, photographic and constraint information the design depends on.
Design status
Version, approval and the commercial consequence of the design, held alongside the project.
Equipment configuration
What specific equipment, quantity and configuration the design commits the business to buy.
Equipment availability
Whether the committed equipment can arrive in time for the date given to the customer.
Installation package
The complete set of equipment, documents, people and prerequisites an installation needs.
Commissioning
The testing, certification and documentation that prove the installation is complete.
Installed equipment
Serialised equipment becoming an asset with a configuration and a location.
Warranty
What responsibility remains, for how long, and who carries it.
Post-installation service
Planned and reactive work against a known asset and its history.
External approvals
Approval or connection activity outside the organisation, where it applies.
One connected journey
Connect opportunity to operational asset.
Thirteen stages, running across six threads: customer, project, equipment, asset, finance and data. Installation-led renewable businesses may coordinate many of these stages across several systems and teams.
- Customer
- Project
- Equipment
- Asset
- Finance
- Data
Attract
Enquiries, campaigns and referrals arriving into one place rather than several inboxes.
Qualify
Site suitability, requirement, permissions, access and timing understood early.
Survey
The site captured as structured operational information rather than notes and photos in isolation.
Design
System design status, equipment, quantity, configuration, assumptions and approvals.
Quote
Products, labour, subcontract, margin, scope, exclusions and payment terms.
Contract and win
The agreed commercial and technical baseline the installation will be delivered against.
Commercial handover
The point where the promise made to the customer transfers intact into delivery.
Procure
Supplier orders, lead times, project allocation and shortages made visible.
Plan
Installation date, team, subcontractor, equipment readiness and site prerequisites.
Install
Work orders, tasks, checks, photos, parts, time and issues from the field.
Commission
Testing, certification, documentation and the point the installation becomes an asset.
Handover
Customer documentation, warranty position and the agreed service responsibility.
Service
Reactive and planned work against a known asset and its history, where service applies.
Optimise is not a final operational stage. It is an optional post-live business route, taken where a live platform contains improvement worth funding.
Contract and commercial baseline
The project team should inherit the deal that was actually sold.
Installation should begin from an agreed commercial and technical baseline, not from everybody's memory of the quotation.
- 01Scope
- 02System and equipment design basis
- 03Assumptions
- 04Exclusions
- 05Customer responsibilities
- 06Dependencies
- 07Milestones
- 08Payment terms
- 09Equipment
- 10Subcontract assumptions
- 11External dependencies
- 12Acceptance
- 13Warranty and service position
Survey and design
The business platform should control the commercial and operational consequences of the design.
It does not need to replace the specialist tool that creates the engineering design. Survey information has the same rule: capture or consume it, but do not assume it replaces specialist survey technology.
Survey information
- Customer, site, location and contact
- Survey date, surveyor and status
- Measurements, photographs and documents
- Access, constraints and risks
- Follow-up actions and owner
The business platform may control
- Design status and version reference
- Equipment, quantity and configuration
- Assumptions carried into the quotation
- Approvals and approval evidence
- Documents linked to site, project and asset
- The commercial consequence of the design
Specialist design systems create
- Engineering calculations
- CAD and technical drawings
- Technical system design
- Specialist equipment configuration tools
We do not claim specialist renewable engineering capability. Which design integrations can be referenced is a business decision, not an assumption.
Design change
A design change after order is a commercial event as much as a technical one.
Change, impact, approval and the revised commercial position should be visible. Not every technical change is chargeable, and treating it as automatic damages trust.
01
Design
A technical revision is raised against the agreed design basis.
02
Equipment
Equipment, quantity or configuration changes as a result.
03
Procurement
Purchase commitments, lead times and receipts are re-checked.
04
Cost
Material, labour and subcontract cost move with the revision.
05
Schedule
Installation readiness and the committed date are re-tested.
06
Customer commitment
Whether the change affects what the customer was promised is decided, not assumed.
07
Margin
The revised commercial position is visible before the work proceeds.
External dependencies
An external dependency still needs an owner, status and impact even when InteliSense does not control it.
Installation programmes can wait on activity outside both the platform and the organisation. We do not take responsibility for statutory, technical or grid approvals, but the programme still has to see them.
The control
Dependency
The specific external activity the installation waits on.
Owner
A named party, inside or outside the organisation.
Required date
When it has to clear for the installation date to remain credible.
Status
Current position, updated as evidence rather than as an assumption.
Impact
What moves if it does not clear.
Action
The next step and who takes it.
Dependencies that can hold an installation
- Customer and site readiness
- Site access
- Engineering approval
- Grid or connection activity, where applicable
- Specialist certification
- Financing or funding confirmation
- Supplier commitments
- Subcontractor availability
- Equipment availability
- Other third parties
Which of these apply depends on the technology, the site and the contract.
Installation readiness
An installation date is a commitment supported by readiness across several dependencies, not simply a calendar booking.
Where readiness is tested before the date is confirmed, fewer installations move after the customer has been told.
Customer ready
Decisions made, commitments understood and availability confirmed.
Site ready
Access, preparation and prerequisites in place.
Design ready
Approved design version, with the equipment it commits.
Equipment ready
Received, allocated and staged for this installation.
Resource ready
The right team, skills and duration allocated.
Subcontractor ready
Scope issued, accepted and scheduled.
Dependencies ready
External dependencies cleared or accepted as a risk.
Documentation ready
Method, safety, certification and customer documentation available.
Equipment through the chain
- Customer commitment
- Design
- Equipment requirement
- Purchase commitment
- Receipt
- Project allocation
- Installation readiness
Equipment availability can decide whether the project plan is real. Where that chain is broken, the installation date is an opinion.
What we examine
The detail behind the chain.
These are the areas we work through with installation-led renewable organisations. Not every business needs all of them, and we will say so where that is the case.
- Lead, account, opportunity, site, requirement and expected close
- Solution outline, survey status, commercial value and expected install period
- Is the opportunity real, and is the site understood?
- Can operations support the timing being implied to the customer?
Deeper qualification
Where the detail decides the answer.
Open only what is relevant to your operation.
Value realisation
A new business platform is not the renewable-energy outcome.
The outcome is whether the organisation can control the customer commitment, installation and installed asset more effectively. That runs through a chain, and every link can break it.
01
Business outcome
The outcome leadership is trying to move, stated before any platform decision.
02
Baseline
What is true today, measured from your own information rather than assumed.
03
Operating change
What has to change in how the work is run, not only in the system.
04
Platform capability
The capability that supports the change, kept as small as the model allows.
05
Adoption
Whether the teams involved actually run the process in the platform.
06
Result
The measured position after the change, against the same baseline.
07
Review
Whether the change held, and whether further work is justified. No change is a valid outcome.
Business applications and operational technology
The business platform does not need to become the equipment-control system.
It needs the information required to manage the customer, asset and service responsibly. Dynamics does not replace SCADA, energy management, monitoring or vendor technology unless a solution is explicitly designed to do so.
Business applications may own
- Customer and site
- Contract and commercial position
- Project and schedule
- Installed asset identity and configuration record
- Warranty and service entitlement
- Work order and service history
- Cost, invoicing and margin
Specialist systems may own
- Device telemetry
- Technical performance data
- Equipment control
- Diagnostics
- Specialist equipment configuration
- Real-time operational signals
Where the two connect
Data and intelligence can connect relevant information where a decision justifies it: linking an installed asset to a monitored device, or a service case to a diagnostic signal. That is an integration decision with a defined purpose rather than a default position.
Explore IntegrationInstalled asset and service
Handover is where the project becomes an asset with a long life ahead of it.
Where service and maintenance form part of the commercial model, the installed asset can become the start of a longer customer relationship. Not every installer has recurring service revenue, and the model should be qualified rather than assumed.
01
Installed asset
Created at commissioning, with serial, configuration and location.
02
Warranty and entitlement
What is covered, by whom and until when.
03
Planned work
Scheduled maintenance where the commercial model includes it.
04
Reactive work
Faults raised against a known asset rather than an address.
05
Parts
Replacement equipment issued, tracked and charged where applicable.
06
Technician
The right skills, documentation and asset history at the point of work.
07
Outcome
What was found, what was done and what remains outstanding.
08
History
A record that supports both service and the next commercial conversation.
09
Review or renewal
Where an agreement exists, whether it continues and on what terms.
What the asset record may hold
- Asset ID
- Customer
- Site
- Equipment
- Serial numbers
- Configuration
- Commissioning date
- Warranty position
- Service entitlement
- Service history
- Documents
Platform fit
Choose against the operating model, not the sector label.
CRM, Field Service and Power Platform are separate decisions rather than one product choice. The combination follows how work is sold, delivered and serviced.
Business Central
A potential commercial and operational core where finance, project, purchasing, inventory and service requirements fit the platform responsibly.
- Finance, customers, suppliers, purchasing, inventory and jobs in one system
- Project cost, committed cost and invoicing against installations
- Multi-entity and intercompany where the group structure requires it
- Extends through Power Platform for survey, field and approval processes
CRM and customer engagement
Where customer, opportunity, site and commercial context need one record.
- Lead, opportunity, site, survey status and quotation in a single customer view
- Site and relationship history available to Sales and Delivery together
- Commercial and service context alongside the customer, not in a separate list
- A customer record is not the same decision as a field execution platform
Field Service
Where work-order, scheduling, technician, installed-asset and parts depth justify it.
- Work orders, scheduling and mobile execution at genuine volume
- Installed assets, warranty and service agreements as operational records
- Parts, entitlement and planned maintenance across an installed base
- Field Service should be selected because the field operating model needs it, not because engineers work away from the office
Power Platform
Where focused capture, forms or workflow are a proportionate answer.
- Survey and site capture apps linked to the customer record
- Field capture where full service management is not justified
- Approvals, checklists and notifications across the installation journey
- Often the smallest capable answer alongside a commercial core
Finance & Supply Chain
Where the future operating model requires deeper enterprise finance, supply chain, warehouse, planning, multi-entity or governance capability.
- Deeper supply chain, warehouse and planning capability
- Higher transaction volumes and more complex group structures
- Advanced demand and procurement planning across entities
- These are InteliSense qualification patterns, not Microsoft company-size thresholds
What the platform decision is qualified against
- Project and installation model
- Legal entities and group structure
- Sites and locations
- Inventory, serials and staging
- Field and service depth
- Equipment and configuration control
- Integrations, including specialist design and monitoring systems
- Reporting and data ownership
- Security and external users
- The operating model the business is moving towards
We recommend the smallest platform capable of the operating model. Growth and company size are not the deciding rule.
Leadership view
The same operation, seen from six chairs.
Each role needs a different cut of the same information. Where those views disagree, definitions, ownership, timing and source should be examined before creating another report.
CEO
Is the organisation creating control or coordination cost?
- Order intake
- Delivery capacity
- Customer outcomes
- Installed base
CFO
Do we know the true cost of an installation before it closes?
- Project margin
- Committed cost
- Cash
- Multi-entity view
Operations
Which installations are at risk this month, and why?
- Schedule
- Equipment readiness
- Resource
- Subcontract
Sales
Can we commit to this timing with confidence?
- Pipeline
- Survey status
- Lead times
- Install capacity
Procurement
What demand is coming, and what will constrain it?
- Lead times
- Shortages
- Allocation
- Supplier performance
Service
Do we know the installed base we are responsible for?
- Asset record
- Warranty
- Service history
- Renewals
Delivery route
The right route depends on how much is still undecided.
Eight commercial routes, established in sequence. Data & AI is a capability rather than a starting route.
01
Operating model fit
Business model, survey, design boundary, equipment, installation, asset and service model agreed first.
02
Platform fit
The smallest capable combination of Microsoft capability for that operating model.
03
Delivery fit
How the work should be delivered. Only then is any accelerated route qualified against its own criteria.
Assessment
Where material uncertainty needs reducing first.
A bounded diagnostic that establishes what is true before a recommendation is made.
Explore AssessmentsTransform
Where the future operating model still needs defining.
Design the installation and service operating model before automating it.
Explore TransformStandard implementation
Where the platform and operating model are sufficiently understood.
Conventional governed delivery with a defined methodology and decision ownership.
Explore ImplementationRAPID qualification
Where bounded strict fit supports acceleration.
Acceleration is qualified against the relevant product route's own criteria, after operating model and platform fit.
Explore RAPIDRecover
Where an implementation has lost confidence or control.
Establish what is actually true before deciding what to change.
Explore RecoveryOptimise
Where the live platform contains worthwhile friction.
A justified improvement against a measured baseline. No change remains a valid outcome.
Explore OptimiseSupport
Where agreed capability needs dependable operational service.
Keeping live installation, service and finance processes operating.
Explore SupportPartner transition
Where the platform may remain but the partner needs changing.
A transfer of responsibility, with tenant, environments, source control and knowledge under customer control first.
Explore Partner Transition
After go-live
Support
Keep agreed capability operating.
Customer Success
Review whether the platform remains aligned to business priorities.
Optimise
Execute a justified improvement.
Data & AI
Use only where a qualified decision or use case warrants it.
No change is a valid review outcome.
Confidence gates
Four points where the installation model is re-confirmed.
A gate is a decision point rather than a warning. Each one can end in proceed, adjust or stop, and the answer is evidence rather than optimism.
Gate 1
Before design
Operating model confidence
Whether the business model behind the installations is understood well enough to design against.
Confirmed at this gate
- Business model and technology or service context
- Customer journey from enquiry to installed asset
- Survey and design process, including what happens outside the platform
- Project, procurement and installation model
- Asset ownership and the service model, where one exists
- The business outcomes leadership is trying to move
Decision
Proceed to platform and architecture · Investigate a specific area further · Transform first, where the operating model is not yet agreed · A different industry route, where this is not an installation-led business
Gate 2
Before build
Platform and architecture confidence
Whether the platform combination and the system boundaries hold once the detail is examined.
Confirmed at this gate
- Business Central or Finance & Supply Chain as the commercial core
- CRM, Field Service and Power Platform selected against the operating model
- Specialist design systems and what they continue to own
- Operational and telemetry systems and what they continue to own
- Data ownership, integration and reporting
- Security, external users, licensing and the first-release scope
Decision
Proceed to build · Re-scope the first release · Retain or introduce a specialist system · Select a different platform combination
Gate 3
Before cutover
End-to-end proof
Whether a representative installation has been proved through the platform, including the exceptions.
Confirmed at this gate
- Opportunity, qualification, survey, design, quote and contract
- Commercial handover, procurement, project and schedule
- Installation, commissioning, asset creation, service and finance
- Design change and equipment shortage
- Customer or site delay and subcontractor delay
- Installation issue, equipment replacement and commissioning exception
- Warranty or service case against a created asset
Decision
Proceed to cutover · Remediate a specific failure · Re-test the affected path
Gate 4
Before go-live
Operational go-live readiness
Go-live is ready when live customer commitments can continue without losing the connection between site, project, equipment, asset and financial position.
Confirmed at this gate
- Customers, sites, open opportunities and quotes
- Active projects, equipment, inventory and supplier orders
- Project commitments, schedules and work orders
- Assets, serial numbers, warranty and documents
- Integrations, mobile users and security
- Trained teams and the agreed support position
Decision
Go · No-go · Controlled deferral of a defined scope
Shared responsibility
We can connect the process. We cannot make technical, commercial or regulatory decisions on behalf of the business.
Saying so at the start is more useful than discovering it during testing.
The customer owns
- Technical and engineering decisions
- Site and survey truth
- Commitments made to customers and commercial terms
- Equipment specification and supplier relationships
- External approval responsibilities
- Project priorities and warranty or service policy
- Data validation, user acceptance testing, cutover and adoption
InteliSense may provide
- Business process design and architecture
- Configuration and development
- Integration and data migration
- Testing and reporting
- Cutover support
- Risk visibility
Held jointly
- The end-to-end proof at Gate 3
- Decision ownership and escalation
- Adoption across Sales, Delivery, Field, Service and Finance
- The go-live decision and what is deferred
Cutover
The cutover challenge is not moving records.
It is ensuring every live installation still has an owner, equipment position, schedule, commercial position and next action.
- Owner
- Status
- Commercial position
- Equipment position
- Next action
- Dependency
Live commitments at cutover
- Leads, opportunities and surveys in progress
- Quotes issued and awaiting decision
- Active projects and their commercial position
- Purchase orders and expected receipts
- Equipment reservations and allocations
- Installations booked and part complete
- Engineer schedules and subcontractor commitments
- Commissioning activity awaiting evidence
- Warranty cases and open service work
Foundations
Data, adoption, security and licensing decide whether it holds.
These areas quietly determine whether the installation journey survives its first month.
Data migration
Historic information should move because the future operating model needs it, not simply because it exists.
- Customers, contacts and sites
- Opportunities, surveys and quotes
- Projects, suppliers and purchase orders
- Equipment, serial numbers and inventory
- Active installations and installed assets
- Warranty, service history and open service work
Adoption
The system cannot create a connected installation journey if every team continues to keep its real status somewhere else.
- Sales
- Surveyors
- Designers
- Procurement
- Project managers
- Schedulers
- Warehouse
- Installers
- Subcontractor coordinators
- Service
- Finance
Security and licensing
User, access and licence design should be qualified together, particularly where mobile, front-line or external users are involved.
- Office users
- Field users
- Mobile workers
- Subcontractors and external users
- Customer service
- Finance
- Service and integration identities
Integration
Specialist design tools, monitoring platforms, supplier systems and customer portals each need a defined owner for the data they hold. Which integrations InteliSense can reference is a matter of record rather than assumption.
Explore IntegrationData & AI
Much of the information already exists. It is held in different places.
Sales, survey, design, procurement, project, field and finance each describe part of the same installation. Bringing them together is what makes exception detection and decision support possible.
Practical AI examples
- Survey summarisation
- Document handling
- Knowledge retrieval
- Communication drafting
- Field note structuring
- Proposal support
These are examples rather than guaranteed outcomes. AI should not make technical design, commercial or safety-critical decisions.
Automate administration first
- Handover checklists
- Approval routing
- Purchase requisitions
- Certification chasing
- Status notifications
- Warranty registration
Automate administration before automating judgement. Not every manual process needs AI, and AI is not a substitute for delivery governance.
Operational intelligence
Examples from our current demonstration portfolio.
These are warehouse demonstrations built on synthetic data. They may be relevant where a renewable organisation runs a meaningful equipment operation, but they are not renewable-energy models and they are not sector proof.
Optimisation and recommendation
Warehouse slotting advisor
Level 1 demonstration, synthetic data
Relevant where equipment volume and staging complexity exist. It is a warehouse demonstration rather than a renewable-energy model.
Forecasting
Warehouse labour and backlog forecast
Level 1 demonstration, synthetic data
Forecasts movement patterns in warehouse and staging operations. It is not evidence of renewable sector delivery.
Risk prediction
Pick wave SLA risk predictor
Level 1 demonstration, synthetic data
Identifies dispatch work at risk of missing its window. Again, a warehouse demonstration rather than a sector product.
Potential renewable use cases to assess, not products
- Installation slippage risk
- Equipment shortage risk
- Project margin risk
- Quote conversion analysis
- Service demand forecast
- Warranty and service pattern analysis
Decision
Which decision would change, and who makes it.
Data
Whether enough consistent history exists to learn from.
Signal
Whether the outcome is genuinely predictable from that data.
Timing
Whether the answer arrives while intervention is still possible.
Action
What the organisation would actually do differently.
Baseline
How today's performance is measured before anything is claimed.
Risk
What a wrong answer would cost.
Cost
What it costs to build, run and keep the model honest.
Evidence
Customer experience of working with InteliSense.
Our published videos evidence Dynamics delivery with InteliSense. Renewable Energy-specific customer evidence will be presented here when its sector, engagement and published claims have been verified.
Customer voice
What customers say about working with us.
Customer voices
InteliSense customers
Hear our customers talk about InteliSense
How we work
Connect the chain. Keep the platform proportionate.
Start with the operating model
Sales, survey, design, procurement, installation, asset and service are one chain, not five systems.
Protect the commercial promise
What was quoted, assumed and excluded should survive the handover into delivery unchanged.
Choose the smallest platform capable
We would rather explain why you do not need something than sell you complexity you cannot absorb.
Respect the specialist systems
Engineering design and equipment technology can stay where they are. The business platform controls the commercial consequence.
Make delivery risk visible early
Earlier visibility gives the team more options to intervene before the outcome is fixed.
Treat the asset as a long relationship
Commissioning and handover create an asset the business may be responsible for over many years.
Where to start
Five questions before a conversation.
This is orientation rather than a recommendation. It does not select a product, and your answers are carried into the enquiry so nothing is repeated.
Indicative signal
Answer the questions and we will show a likely starting point. This is orientation rather than a recommendation, and we do not decide platform fit or acceleration from a form.
Your answers are carried through, so you will not be asked to repeat them. Final qualification is always a conversation.
Common questions
Questions renewable installation leaders ask.
From first enquiry to installed asset
Can you see an installation from enquiry to serviced asset in one place?
If sales, survey, design, procurement, field activity and service each hold part of the answer, the first step is not necessarily another system. It is understanding where the chain stops connecting.