Skip to content

Core concepts

The things you work with in Aevy: what they are, how they fit together, and where you meet them.

How to read this

Read it top to bottom the first time; after that, treat it as a reference. Almost everything in Aevy hangs off an asset, so that is where we start. For a one-line lookup, the glossary holds the same concepts as a table.

An asset is a single renewable energy project: a solar plant, a wind farm, a storage site, an EV charging site, or a combination of those. It is the home base everything else attaches to: its documents, its equipment, its work, its people. The Assets section of the sidebar lists every asset you can see.

A system is a major technical part of an asset: a turbine, the substation, an inverter station. It holds the specifications and location for that equipment, and it is what inspections and defects roll up to. The systems and components guide walks the views.

A component is a part inside a system: a gearbox, an inverter, a rescue kit. Components are the level where inspections and defects actually land, and they add up to their system’s state. Components are mapped to systems when your asset is set up, so the hierarchy is already in place when you arrive.

A document is any file kept against an asset: contracts, permits, reports, manuals, inspection logs. Documents arrive through a sync with your source, so there is no upload step and nothing to file by hand. When one lands, Aevy reads it, classifies it, and pulls out its facts. The documents guide covers finding and reading them.

Three fields classify every document so you can filter to it:

  1. Type. The top category: contract, report, design, notification, invoice, and so on.
  2. Subtype. A refinement within the type: a contract might be an amendment or an appendix; a report might be a statutory inspection or an audit.
  3. Scope. The subject area, which depends on the type: a contract is tagged O&M, EPC, or PPA; a report might be legal, technical, or financial.

A signature state alongside these tells you whether the document is signed, partially signed, or not signed.

A fact is a single structured value Aevy pulled out of a document: a warranty start date, a base fee, an insured sum. There are several hundred kinds, and they turn a PDF into data you can filter, query, and ask Squirrel about. Every fact keeps a link to the exact line it came from; the lineage guide shows how to reveal it.

Documents rarely live alone. Aevy links versions and relatives of the same document: a newer version marks the older one Superseded, a copy is marked Duplicate, and amendments and appendices point at the agreement they belong to, each with a link to the active version.

Pinning keeps a document one click away on its asset: the current contract, the latest inspection. Pinned documents gather on the asset and under the Pinned filter on the Documents page. The favorites and pinning guide covers it.

A suggestion is Aevy proposing a specific change to your data after reading a document: a component to add, a reminder to create, a property to set. A suggestion is always a draft: nothing changes until you accept it, and each one names the document and page it came from. The suggestions guide covers the review loop.

Every suggestion carries a percentage: Aevy’s own estimate of how well the document supports it. Treat it as a prompt for attention, not a verdict: the score tells you where to look hardest, not what to decide.

Aevy keeps four kinds of work record, and they meet you in the same shape: a list per page, the shared filter bar, and an activity feed on each record.

  1. Reminder. A dated task on an asset: a calibration to run, a certificate to renew. See the reminders guide.
  2. Punchlist item. A defect or issue found on an asset, tied to the system or component it affects, with a severity and a status from report to resolution. See the punchlist guide.
  3. Event. Something happening on an asset on a date, with a start, an end, and a status: a maintenance window, an inspection visit, a renewal. See the events guide.
  4. Obligation. Something a contract requires you to do or hold, tracked on the cadence the contract defines. An obligation is not a task itself: it defines what must be done and how often, and an unmet one is a non-compliance. See the compliance guide (beta; some screens still say “requirements”).

A contact is a person tied to an asset or a company: a project manager, an O&M lead, a manufacturer’s representative, with the details you need to reach them. Contacts have their own page in the sidebar menu.

A company is an organization involved with an asset: an owner, an operator, an O&M provider, a manufacturer, an insurer. Companies group the contacts who work there.

A comment is how you talk about a record without leaving it. Every record with an activity feed takes comments at the top of that feed, so the discussion sits next to the history. See the activity log guide.

Type @ anywhere you write to name a specific record in a sentence: an asset, a document, a task, a teammate, or Squirrel itself. The mention points at the record itself. See the mentions guide.

Squirrel is the AI asset manager in the chat panel. It answers from your own data using the same tools you have, shows the steps it took, and cites the documents behind its answers. When it proposes work, the proposal arrives as a suggestion for you to accept or dismiss. See the Squirrel guide.

Activity is the audit trail. Every meaningful change to a record is logged with who did it and when, and when Aevy acts, it is in the log like anyone else. Use Notify me on a record to hear about the changes you care about.

A mode is the lens you work through, and it shapes the sidebar menu to fit the job: Asset Management for the day-to-day, Due Diligence for reviewing a deal, and Owner for the lighter ownership-level view. Switch modes from the organization name at the top of the sidebar; the getting around guide shows where.