Nexus · positioning

Nexus is the Felixfusion product for sourcing, compliance, and contract intelligence across the energy infrastructure equipment and EPC layer. This page is the positioning view: what the engine reads across BESS, solar, wind, and balance-of-plant procurement, the ruleset it carries, the horizons it runs across, and the engagement shapes it is built to deliver. Written for procurement leads, EPC originators, lender diligence groups, and project finance teams who want the layer below the marketing surface.

What the engine does

Nexus sits where the procurement lead sits. Its job is to turn an equipment shopping list into a defensible decision: every credible supplier surfaced, every quote scored against market benchmarks, every compliance trigger flagged, and every contract clause mapped to a provenanced library of past terms. The engine is an AI-assisted workbench, not an autonomous agent. A senior procurement lead signs every brief before it leaves the system.

The stack is built on two named engines. Sourcing runs the intake: equipment specifications parsed against a live supplier index, fit-scored against scope, footprint, certifications, and past performance, and carried through a five-stage pursuit pipeline from RFI to PO. Contracts runs the evaluation and drafting: a live compliance matrix on UFLPA, IEC 62933, ICV, and the buyer's own technical requirements, with each clause mapped to a provenanced library of MSAs, EPC contracts, and warranty schedules. Sourcing decides who can credibly bid. Contracts decides whether the package is bankable.

Primary procurement scopes in the runtime today are utility-scale BESS systems, solar modules and inverters, wind turbines and towers, balance-of-plant equipment (transformers, switchgear, MV / HV cabling), and EPC services. The methodology ports to data-center power equipment (UPS, generators, switchboards), grid interconnection scope, and large-load BTM packages; those extensions carry the same two engines with sub-scope rule overlays.

Horizons run from the day a project capex line lands in scope through warranty-period performance review. Time granularity matches the decision at hand: weekly for supplier index refresh, daily for active RFQ progression, release-to-award for compliance and bankability, and quarterly for contract performance and supplier scorecards.

The four surfaces Nexus reads

Every procurement decision rests on four surfaces. Sourcing reads the first two. Contracts reads the second two. The four together drive a package from spec to signed PO.

The supplier surface (Sourcing). A normalised index of credible suppliers across BESS, solar, wind, and balance-of-plant. Each supplier carries a structured profile: factory footprint, certified capacity, IEC and UL conformity, financial signals, sanctions and forced-labour screen, past delivery on comparable scope, and live lead time against current order book. Refreshed continuously against published RFQ awards, port-of-loading data, and certified bill-of-materials disclosures.

The quote surface (Sourcing). Every active RFQ the procurement team is running, indexed against the supplier surface and benchmarked clause-by-clause. Price, lead time, payment terms, performance guarantees, and warranty depth land in a single comparison view. Quote amendments, clarification rounds, and best-and-final revisions surface as a change-log against the original RFQ.

The clause surface (Contracts). The buyer's existing MSAs, EPC contracts, equipment supply agreements, and warranty schedules, structured as queryable prior art. Each clause carries provenance (which contract, which counterparty, which year, on what scope, at what price band) and a freshness score against the current standards used in NEM, ERCOT, and GCC closings.

The compliance surface (Contracts). Every UFLPA exposure, every IEC 62933 / IEC 61215 / IEC 61400 standard, every ICV obligation, and every buyer-specific technical requirement parsed from the bid pack and tracked Y or N or Partial with page references on both sides. The matrix is a live working artefact from RFQ release, not a last-week deliverable. It is the artefact lenders and project finance read first.

Sourcing — supplier index and RFQ pipeline

Sourcing is the part of Nexus that watches the supply base. It maintains a continuously refreshed index of credible suppliers across BESS, solar, wind, and balance-of-plant, and scores every supplier against the firm's specification: cell chemistry, system voltage, container size, augmentation strategy, ICV obligation, sanctions and forced-labour exposure. Fit-scored suppliers land in a saved-search feed per programme. Nothing credible is missed; nothing irrelevant reaches the inbox.

Forced-labour and trade-policy screening is first-class. UFLPA Entity List exposure, polysilicon traceability, and sanctioned-counterparty triggers are extracted from supplier disclosures, port-of-loading manifests, and industry registries automatically, with an evidence row per trigger. Buyers serving US and EU markets stop discovering polysilicon-traceability gaps at lender diligence; the Sourcing engine surfaces them at supplier-shortlist stage.

Every active RFQ enters the five-stage pipeline: Spec Lock, Shortlist, Quote, Best-and-Final, Award. Each stage owns structured artefacts, not freeform notes. The Shortlist stage carries the engine's verdict with confidence and factor list; the procurement lead reads the reasoning and signs off. Best-and-Final rounds are captured in-system with named negotiators and amendment trails. When the next programme needs the precedent, the artefact is retrievable in seconds rather than buried in email.

The post-award scorecard loop closes the system. Delivered-on-time, delivered-on-spec, warranty-claim count, and field performance feed back into the supplier index and the Shortlist factor weights. The next programme starts with what the buyer actually learned, not with a vendor brochure.

Contracts — compliance matrix, clause library, package assembly

Contracts is the evaluation and assembly engine. It takes a live bid pack and produces the three artefacts the lender, the project finance team, and the EPC counterpart actually read: a complete compliance matrix, a redlined contract draft against a provenanced clause library, and the technical schedules and warranty annexes that have to be exact.

The clause library is the foundation. Point the library at the buyer's archive of MSAs, EPC contracts, equipment supply agreements, and warranty schedules and it parses each document, extracts clause-level positions, and tags each by counterparty, scope, year, jurisdiction, and outcome (closed, escalated, amended). Every entry carries provenance (source contract, deal team, counterparty, scope, price band) and a freshness score. The library maps standard sections — limitation of liability, performance guarantee, liquidated damages, change-in-law, force majeure, ICV — so a redline pass against any new template is grounded in what the buyer actually negotiated last time.

The compliance matrix compiles itself as the engine parses the RFQ pack. Every UFLPA-relevant component, every IEC 62933 / IEC 61215 / IEC 61400 / UL 9540 / NFPA 855 standard, every ICV threshold, and every buyer-specific technical requirement is extracted from the spec, numbered, and scored against the supplier's quote and past delivery record. Each matrix row links to the spec page where the requirement lives and to the quote page where the response sits. The lender does not have to search.

Package assembly is AI-assisted, not AI-autonomous. The engine proposes redlines clause-by-clause with citations back to the library and surfaces the variance against current market terms. The procurement lead reviews each redline, edits where the commercial position needs sharpening, and signs off. Matrix rows that were Partial become Y as the redline lands. Under a compressed clock this approach is what keeps the package bankable when manual contract review alone cannot.

The supply-chain ruleset Nexus carries

Any credible procurement tool has to know the supply-chain ruleset in the same way a grid-diligence tool has to know the NEM. Nexus's runtime carries an operating picture of every regime that decides packages before commercial terms are read.

UFLPA. US imports of solar modules, polysilicon, and certain BESS components face a rebuttable presumption of forced-labour risk unless documentary traceability is provided. The engine maintains the Entity List, the high-priority sector flags, and the documentary expectations on a continuous basis, and surfaces exposure at supplier-shortlist stage rather than at customs hold.

BESS technical standards. IEC 62933 series (energy-storage system performance and safety), UL 9540 (energy-storage system certification), UL 9540A (thermal-runaway test), and NFPA 855 (installation standard) are the standards lenders and AHJs read first. Contracts tracks which standards are referenced in each spec and flags suppliers whose certifications are stale, partial, or jurisdiction-mismatched.

Solar and wind technical standards. IEC 61215 (PV module qualification), IEC 61730 (PV module safety), IEC 61400 (wind turbine series), and the IECRE conformity assessment regime define what a bankable module or turbine actually means. The engine reads each supplier's conformity package and flags the gaps that lender technical advisors disqualify on.

ICV (in-country value). GCC procurement increasingly requires a documented ICV score on equipment and EPC packages. Nexus tracks the per-country methodology (UAE, Saudi Arabia, Oman, Qatar) and surfaces the ICV uplift each shortlisted supplier can credibly claim, with evidence drawn from the supplier surface.

Trade agreements and tariffs. CETA, USMCA, and CPTPP procurement chapters shift duty exposure on key BESS, solar, and wind components. Section 201 / Section 301 / AD-CVD orders carry their own trigger surface for US imports. The engine tracks which regime governs each shipment and applies the right duty and origin checks before quote ranking.

Where packages actually die

Energy-infrastructure procurement teams lose packages for predictable reasons. Sourcing and Contracts are engineered around those failure modes.

Lender disqualification, not commercial terms. The primary disqualifier is an incomplete compliance matrix or a stale standards package, not a high price. A single missing UL 9540A test report or a UFLPA documentary gap holds the package up at financial close. Contracts' live matrix closes this category before the lender call.

Missed late breaks. Standard updates, AHJ rulings, sanctions adds, and entity-list updates land continuously during the RFQ window. A package built against the standards as of release misses the new exposure. Sourcing's continuous refresh and change-log surface every material edit against every active programme.

Polysilicon and forced-labour gaps. A US-bound module package without the UFLPA documentary trail is detained at port. An EU-bound package without the EUDR-aligned diligence record fails customer review. The Sourcing trigger detection catches these at shortlist stage, before the LOI.

Performance-guarantee mismatch. EPC and equipment-supply contracts disqualify on liquidated-damage caps, performance-curve guarantees, and availability commitments that do not match the buyer's PPA or capacity-market position. The clause library benchmarks every guarantee against the buyer's own past closings before redline lands.

Post-award scorecard drift. Buyers that do not run a structured scorecard repeat the same supplier mistakes. Contracts' outcome-loop captures delivered-on-time, delivered-on-spec, and warranty-claim signals, then refreshes the Shortlist factor weights so the next programme starts smarter.

Sample engagement shapes

Nexus is built to serve a handful of distinct engagement shapes. The patterns below are indicative rather than exhaustive: the engine runs Sourcing and Contracts underneath each of them, with the deliverable and cadence adjusted to the shape.

Single-package compliance matrix and award pack. A procurement lead has a named BESS, solar, or wind RFQ under a compressed clock and needs the compliance matrix compiled plus the redline pack drafted to a procurement-lead-signed award memo. Target turnaround depends on RFQ depth and library coverage; a utility-scale BESS package is built to move from RFQ release to lender-readable award memo inside the response window with review buffer.

Ongoing programme subscription. A procurement team running a multi-site BESS or hybrid build-out across a year needs Sourcing continuously watching the supplier surface, refreshing UFLPA and standards exposure, and standing Contracts ready on every RFQ. Delivered as a recurring subscription with named procurement-lead access, library refresh, Shortlist verdict surface, and compliance-matrix compilation on demand.

Clause-library build-out. A buyer wants its last five to ten years of MSAs, supply agreements, and warranty schedules restructured into queryable prior art before running more programmes through Contracts. Engagement shape: Contracts' ingestion pipeline points at the buyer's archive, parses each agreement, tags clauses, establishes provenance, and publishes a freshness-scored library.

Lender-side supplier audit. A project-finance group running diligence on a sponsor's preferred BESS, solar, or wind supplier needs every UFLPA, IEC, UL, NFPA, and entity-list exposure surfaced automatically with evidence rows populated from supplier disclosures and port data. Sourcing plus Contracts delivered with the lender-diligence overlays enabled by default and signed by the lender's TA.

GCC ICV-sensitive capture. A GCC EPC originator or sponsor running utility-scale BESS or hybrid renewables tenders needs ICV-aware supplier scoring, in-country fabrication evidence, and country-specific contracting-vehicle indexing. Sourcing and Contracts delivered in GCC mode with UAE / KSA / Oman ICV methodologies captured in the compliance-matrix format.

Response horizons

Different programmes need different horizons. Nexus is built to run at the granularity the programme actually requires.

The week the spec locks. Sourcing detects the new programme, parses the spec at clause level, scores supplier fit against the spec, and surfaces the Shortlist input. Fit-scored suppliers are available to procurement leadership within one refresh cycle of spec release.

The working days inside the RFQ window. Contracts compiles the compliance matrix on day one and updates it live as quotes land. Redlining iterates against the live matrix. Best-and-Final negotiations capture their amendments in-system.

The award window. Final clause-by-clause walk, performance-guarantee schedule, warranty annexes, UFLPA / IEC / ICV traceability pack, and award memo for the procurement committee.

The quarter after award. The post-award scorecard loop closes: delivered-on-time, delivered-on-spec, warranty-claim count, and field-performance signals feed back into the supplier index and the Shortlist factor weights so the next programme starts smarter.

What AI-assisted procurement actually changes

The direction of travel is well understood. Energy-infrastructure procurement is moving from spreadsheet-driven sourcing to AI-assisted sourcing that keeps a senior human in the seat. The change is not autonomy. The change is compression of the mechanical work that used to consume a procurement team's entire response window so the senior humans can spend their time on the judgement calls that win packages.

Nexus's methodology accounts for this trajectory explicitly. AI-assisted clause retrieval and matrix compilation is one envelope. Human judgement on supplier fit, win themes, pricing strategy, and counterparty risk is a separate envelope. The engine surfaces where the boundary is rather than collapsing it. Packages that try to cross the boundary (AI-autonomous redlining without procurement-lead sign-off) lose at lender review because the redline does not reflect the buyer's actual position. Packages that keep the boundary clean compress response time without losing the judgement layer.

None of this changes the core question a procurement lead is asking. It changes how much of the response window can go to answering it.