A single solar project creates dozens of business relationships across developers, EPCs, manufacturers, distributors, and service providers. Aarvi Projects keeps requirements, participants, procurement, and material readiness aligned on one shared workspace — while each company keeps its own ERP and project tools.
Solar project collaboration
Keep participants aligned on one project workspace — scope, roles, and shared commercial context without forcing everyone onto a single ERP.
Arizona Sunrise–scale builds routinely involve an owner, developer, EPC, multiple OEMs, regional distributors, logistics partners, and later O&M. Email threads and spreadsheet “material trackers” break under that load. Aarvi gives the project a shared identity: who is on it, what is required, what has been sourced, and what is still at risk — while purchase orders, invoices, and telemetry stay in each company’s systems of record.
- Shared project identity across organizations — one workspace, many companies
- Clear participation and roles without collapsing company boundaries
- Living context for requirements, sourcing decisions, and delivery status
- Designed for utility-scale and commercial builds — not a generic task board
Project participants
Invite EPCs, suppliers, developers, owners, and service providers into the project with the right commercial and delivery roles.
Participation is grounded in network relationships and project roles — not anonymous open access. Each organization sees the project through the lens of what they buy, sell, or deliver.
- Multi-company participation on one project
- Role-aware collaboration across the ecosystem
- Trust grounded in network relationships
Project requirements
Capture structured demand — what, quantity, where, when, and technical needs — before defaulting to an RFQ.
A requirement is the bridge from project need to fulfillment. Inventory, contracts, approved suppliers, warranty paths, and RFQs all start from clear demand — not from an empty RFQ form.
- Equipment, materials, and service requirements
- Destination and timing for site or staging yards
- Technical specs attached to demand
Project procurement
Source equipment against project requirements through inventory checks, contracts, approved suppliers, or network discovery.
Policy-aware paths come first: internal stock, contract release, then approved-supplier RFQ or network discovery when needed. Competitive RFQ is a tool — not the only door.
- Demand-to-fulfillment orchestration — not RFQ-first by default
- Align POs and awards to project need
- Compare suppliers with project destination in mind
Project delivery
Procurement does not end at the PO. Track fulfillment through production, shipment, transit, and site receiving so teams see material readiness across suppliers.
EPCs and owners need category-level readiness: modules may be on site while motors are still in transit. Shared delivery status reduces construction surprises without inventing a second ERP.
- Ordered → in production → shipped → in transit → received
- Material readiness across categories and partners
- Visibility for EPCs, owners, and suppliers on the same project
How it works
- Step 1
Open the project
Create a project workspace and invite the organizations that must collaborate.
- Step 2
Capture requirements
Structure equipment and service demand with destinations and timing.
- Step 3
Source against need
Use inventory, contracts, RFQs, or direct POs according to policy.
- Step 4
Track to site
Follow delivery status until material is ready for installation.