Axion is the only AI knowledge platform built from the ground up for solar and battery energy storage (BESS) EPC by operators who have run these projects, not researchers who have studied them. Every feature, every document category, every agent report reflects a real decision that was made too slowly or a risk that was missed until it cost money.
A 420-page EPCA arrives Friday afternoon. Bid/no-bid meeting is Monday. Your senior PM needs to find the contractual landmines before you commit to a number.
Your PM reads the contract body, then hunts through eight exhibits cross-referencing for inconsistencies. He finds a potential liquidated damages (LD) cap issue in Section 14, but Exhibit C has different language that may expand the exposure. He flags it but is not certain. He misses the Force Majeure exclusion that explicitly carves out pandemic and labor strike events. He misses the domestic content steel requirement buried in Exhibit D that contradicts your current racking quote. He misses the performance guarantee capacity threshold in Exhibit G that, at your current design yield, puts you inside the liquidated damages band on day one.
Three days of review. Two flags surfaced. Three missed. You bid the job and find out at execution what you did not catch at bid.
Same 420-page EPCA. Same Monday bid/no-bid meeting.
The EPCA is ingested Friday afternoon. By Friday evening, Axion's EPCA Review Agent has cross-referenced the contract body against all eight exhibits and surfaced four flags. LD cap mismatch: Section 14.2 states a 15% cap but Exhibit C Schedule of Liquidated Damages contains no corresponding cap, creating potential uncapped delay exposure. Force Majeure exclusion: Section 9.3 explicitly carves out pandemic and labor strike events with no schedule relief available. Domestic content requirement: Exhibit D requires 100% domestic steel, and your current racking quote sources from Mexico. Performance guarantee: Exhibit G sets a capacity test threshold of 98% nameplate. At your current P50 design yield, you are inside the liquidated damages band before you break ground.
Each flag is cited by document, section, and page. A draft question list for the owner is included. Your PM spends Monday morning reviewing the output and preparing for the bid/no-bid meeting, not generating it.
A 350-page bid package arrives for a 150MW solar project. Your estimator needs drawing indicators, preliminary take-offs, red flag alerts, and a list of questions for the owner before the pre-bid site visit in four days.
Your estimator manually reviews each drawing type and notes the completion stage. He extracts module counts and inverter specs by hand from the electrical drawings. He reads the geotech report and flags the corrosive soil note, but misses the pile length requirement for the clay zone on pages 38-41 that will add $400K to the foundation scope. Environmental review is skimped because there is not enough time.
Two days of estimator time. Key geotech risk missed. Questions for the owner prepared from memory rather than document cross-reference.
Same 350-page bid package. Same four-day window.
Package ingested. Pre-Construction Risk and Readiness report generated. Drawing indicators: 12 electrical drawings at 60%, 8 civil at 30%, 4 structural at 10%. The completeness score flags that IFC-level structural drawings are not yet in the package. Automated take-offs: 42,000 modules, 14 central inverters, 3,200 estimated piles.
Red flags: Geotech report pages 38-41 specify 20ft+ pile lengths in the clay zone on the northwest quadrant, which deviates from the standard 16ft assumption in your estimating model. Environmental: tree-clearing restriction window closes November 1 per the U.S. Army Corps of Engineers (USACE) permit. Your construction schedule assumes October clearing. Interconnection: the package references a queue position filed in 2023 with no executed Large Generator Interconnection Agreement. Grid operators report that over 90% of applications contain errors triggering restudies. Your schedule assumes commercial operation date (COD) in month 18, but this queue position has no executed agreement.
Pre-RFI generation: "Your company typically includes a Road Use Agreement on Colorado projects, and this package does not include one. Suggested question for owner: confirm whether a Road Use Agreement is required and who is responsible."
Mid-construction on a 200MW solar project. A request for information (RFI) arrives about firmware compatibility on the Sungrow inverters spec'd two years ago. The engineer who specified them retired six months ago. The OEM rep is out of office.
The PM searches SharePoint. Three versions of the submittal, and nobody knows which is current. The procurement team searches their email for the approved firmware bulletin. It is in someone's inbox from 18 months ago. The site cannot proceed until the question is answered.
Forty-eight to seventy-two hours to get the answer. The subcontractor had already begun installation while waiting. By the time the correct firmware version is confirmed, five units are in with the wrong version. Change order. Schedule slip. Margin gone. The owner's representative notes that your team appears disorganized.
Same RFI. Same project. The engineer who spec'd the inverters retired six months ago.
The PM opens Axion and asks about the approved firmware revision for the Sungrow inverters on this project. Axion identifies the current approved submittal: revision 3, approved March 2025. It cites the specific firmware version, the OEM bulletin number that mandated it, and the installation note from the submittal approval letter.
The PM pulls the cited spec page and answers the RFI in the field meeting, live, in 1.4 seconds. The subcontractor confirms the firmware before installation. No wrong units installed. No change order. The owner's representative sees a team that has complete command of their project documents.
Axion agents are not chatbots. They are structured analytical reports that run across your entire project knowledge base and produce grounded, cited findings: the kind of work that currently takes your best people two to three days.
For an EPC contractor, the documents you ingest into Axion are your competitive intelligence: bid strategies, cost models, supplier relationships, risk tolerances. We built the platform architecture around protecting that intelligence, not exploiting it.
The Axion ontology for solar and BESS EPC was built from the ground up with your document types, not adapted from general construction. Every category reflects a real document that flows through a utility-scale solar or BESS project lifecycle.
The 15 contract risk items we check on every EPCA review. Solar and BESS focused, built from field experience. Enter your details to download the PDF.
Click below to download the PDF. We sent a copy to your email as well.
Download EPCA Checklist (PDF)Companies that load their project knowledge into Axion today will be measurably smarter on every bid, every contract, and every RFI than competitors who start next year. That advantage is not purchasable later. It has to be built now. Transparent pricing. No per-seat fees. First project covered.