Campus PV energy platform: light, charging and load on one 3D base

An integrated energy platform for an aviation-base campus, delivered as a 3D digital twin plus a 2D energy-and-carbon back end. PV drills from campus to zone to a single array; charging is tracked down to orders and vehicle movements with V2G reserved; HVAC is modelled floor by floor with AHU settings. Seven buildings, five floor-exploded, four source systems, 25 data parameters.

Industry
Aviation-base campus · integrated energy / carbon management
System type
3D visualisation wall + 2D energy and carbon platform + multi-source integration layer
Key technology
3D engine and shader effects · floor explode and camera animation · energy-flow visualisation · PV, charging and HVAC data integration · demand and carbon accounting · video and AI recognition
Jiding's role
Requirements and scope, 3D scene and UI design, models and motion, front and back end, multi-vendor integration, deployment and training
7Buildings modelled, five of them floor-exploded, plus three car parks
3Subsystems: PV, EV charging and HVAC, on one campus base
25Data parameters: PV 7, charging 8, HVAC 6, video 4
2Delivery phases: DEMO sets the skeleton, FINAL fills the detail

The Load Profile

One meter for a whole campus is the most common starting mistake

An aviation base cannot be described by a single total. Hangars keep lighting and ventilation running around the clock; the catering building starts prepping at four in the morning; offices run nine to six; charging piles rise and fall with vehicle arrivals. Rooftop PV only produces in daylight. Four load shapes share one incoming line, and the meter only says what was spent — not where, and not when it was wasted.

Hangars: the load that cannot stop

Lighting, ventilation and ground equipment in a maintenance hangar run all year. The load is flat but large, and there is no "switch it off" option. What is left is efficiency per unit of work and shifting what can shift — moving ground-equipment charging into the hours when PV output is high.

Catering and offices: two steep ramps

Catering starts before dawn and winds down mid-morning; offices fill at nine and empty at six. The two curves have completely different shapes, and on a monthly total they cancel each other out. Only by building and by hour does the real peak show up.

Charging: a pulsed load

A single 480kW split charger at full output is a sizeable share of a catering building. How many vehicles arrive, when, and for how long decides whether the transformer is briefly overloaded. This load has to be read as a live power curve, not as daily energy.

PV peak 12:30Load peak 19:36PV ≈ load here; surplus is consumed on sitePV at zero000306091215182124PV outputCampus loadRelative values, illustrative
The PV peak is at noon; the campus peak is at night. The gap between them — surplus by day, shortfall by evening — is exactly what storage, V2G and demand management exist to solve, and it is the first question this platform answers every day.
Three facts a total hides. First, maximum demand matters more than energy: one spike fixes the billing for months. Second, PV surplus that cannot be consumed on site is either curtailed or exported, and both discount the return. Third, carbon has to be counted from the energy mix, so every point of green share changes the accounting. Those three map onto the demand module, the PV self-consumption view and carbon management.

The Safety Gate

At an airport, PV has to clear safety before it clears payback

An airfield is large, its roofs are continuous and its sun is good, which makes it look like ideal ground for distributed PV. It is also governed by obstacle limitation, electromagnetic environment and flight safety. Public reports on Chinese airport projects keep returning to three words: anti-glare, wake tolerance and electromagnetic interference. Those constraints decide what granularity the platform has to show PV at.

Glare: reflectance below 2%

Specular reflection from modules can disturb pilots and tower visibility. Chongqing Jiangbei used anti-glare modules and adjusted array tilt and orientation to bring reflectance below 2%, meeting the civil aviation anti-glare standard. For the platform this means arrays must be viewable by location, not as one plant total.

EMI and wake: position beats parameters

Inverters, step-up equipment and cabling produce electromagnetic fields that need assessment near navigation and communication facilities, and runway-adjacent arrays must account for wake loads on their mounts. Taiyuan Wusu tackled exactly these three — glare, wake and EMI — for ground-mounted arrays inside the airfield.

Irregular roofs: not every surface can take panels

Hangars and cargo terminals are long-span steel structures with significant thermal movement, and runway slopes are irregular. Chongqing Jiangbei added wind cables and installed in blocks. In the platform this becomes array zoning: different roof areas of the same building can be different generation units.

30 MWChongqing Jiangbei phase-one distributed PV, ~24 GWh a year, across 19 zones and 50,000+ modules
5.82 MWWuxi Shuofang microgrid phase one, with 450kW/900kWh storage and 125 charging guns
108.5 MWTaiyuan Wusu zero-carbon airport plan, 120 GWh a year, 17MWh storage and V2G
24–34%Renewable share reported for airport projects after commissioning

Sources: public reporting from CAAC News, the Ministry of Transport and the Wuxi SASAC (2026). Used for industry context and airport-specific constraints; unrelated to this project's installed capacity.

Why this section comes before the feature list."PV management system" is easily read as "pull inverter data and draw a few curves". At an airport, where PV can go, when it can generate and how much of it is available are all bounded by safety rules. If the platform can only show a total, maintenance cannot answer the most common field question: are those three rows by the east runway low today?

The Base Map

A 3D base is not a campus model — it is three layers stacked

The usual failure is to build a beautiful set of buildings first and then try to push data into them; the model and the business never line up, and any layout change forces a rebuild. This platform does the opposite: fix the site and its coordinates first, hang devices on points second, add the energy-flow layer last. Each layer stands on its own, so a change in one does not topple the others.

MarketingServicesAdminCateringMRONew hangarOld hangar10kV switchroomEV station

Isometric campus: seven buildings modelled (marketing, services, admin, catering, MRO, new hangar, old hangar). Yellow roofs are PV arrays; yellow dashed lines carry PV from arrays to the switchroom and out to buildings; the blue dashed line feeds the EV station. Structural illustration, not the actual site plan.

Rooftop PV arrays PV power flow EV station feed Building volumes (roof plus two visible faces)

Layer one: site and buildings

Seven volumes, one main car park and two small ones, surrounding roads and green space, placed from the site plan and satellite base map at a single scale. The acceptance test is plain: put anyone who knows the campus in front of the screen and they should name each building at a glance.

Layer two: device points

PV arrays, chargers, HVAC plant, cooling towers and cameras each sit at a coordinate and are bound to a business key. Clicking a device does not open a picture; it opens that device's live data. Which is why the point table is itself a list the client has to sign off.

Layer three: energy flow

Current direction, cooling direction and charging power are layers, not part of the model. Switch one on and the lines move; switch it off and the campus is clean again. One model then serves briefing, duty and walkthrough without three versions.

7buildingsMarketing, services, admin, catering, MRO, new hangar, old hangar
5explodedFloor-by-floor breakdown, down to equipment and vents
3car parksOne large, two small: bays, canopies and vehicles modelled
2animationsFloor explode and vehicle charging, linked by camera moves
Why not all-3D. 3D answers "where, and next to what"; it is bad at "how much more than last month". Force a trend chart into a 3D scene and the type shrinks, the angle fights you and the numbers stop reading true. So the platform splits from day one: 3D for spatial situation, 2D for the ledger, both on one data layer. The next page covers how that split is drawn.

Solar Chain

The solar chain: modules, inverters, step-up, transformers, then the buildings

Campus PV is not four words of "self-generation, self-consumption". Power leaves rooftop modules, is combined and inverted to AC, stepped up to 10kV into the campus grid, then stepped down by each building's transformer to 400V for HVAC, lighting and chargers. Any break along that chain shows up as "less generation", but the cause can be completely different. The platform's job is to split "less" into "which segment".

One chain, five stages: each with its own metering and alarms DC side AC side 01 Arrays by building, by roof 02 Combiner & inverter DC to AC 03 10kV step-up into the campus grid 04 Building transformer down to 400V 05 On-site use HVAC / light / EV Generation / string current Efficiency / cabinet temp Grid power / voltage Building consumption Self-use / export Metering: one main meter at the grid point plus sub-meters per building; the platform reconciles against the main meter.
The chain is not decoration. It is the troubleshooting order: dirty modules, a derated inverter, an overloaded transformer and unabsorbed surplus all look like "low generation" on a curve, but they are four different red dots on this chain.

Three levels: total, zone, single array

The data sheet is explicit: live monitoring and generation statistics must support total, zone and single unit. That is three roles, not three decorations. Management reads total output and green share; operations asks which roof is low today; a technician checks one inverter's string current.

The hard part is naming. A zone must bind to a building and a roof surface, a single unit to a module ID and a string. Once naming drifts, the third level is permanently empty.

Three states, and one "not a fault" exception

Devices run normal, fault, out of service. Out-of-service needs a reason — maintenance, shading, awaiting a part — otherwise a deliberate stop is counted as a failure and equipment health stops meaning anything.

The other category is safety data: temperature, fault messages, warnings. An over-temperature reading usually precedes soiling, poor cooling or a loose joint by a long way, and deserves its own alert rather than waiting for a trip.

ParameterGranularityThe question it answers
Live PV powerTotal / zone / unitHow much now, and how far below yesterday at the same irradiance?
Generation (day / month / year)Total / zone / unitWhat share of the plan is done this month?
Equivalent full-load hoursTotal / zoneAt equal capacity, who is more efficient — and is the gap operations or orientation?
Avoided emissionsTotalThe number used for carbon reporting, which has to survive an audit.
Safety data (temp / warnings)Single unitIs there an early signal — soiling, cooling or a joint?
Maintenance recordsSingle unitWho serviced this, when, and what was done?

Parameters come from the project data sheet v1.0, reorganised around who uses them and what for.

Charging & V2G

Charging is not "a few piles" — it is a chain that can run backwards

A campus charging station is typically one charger feeding many terminals: the 10kV substation feeds a split DC charger in the 480kW class, which allocates power to several DC terminals — liquid-cooled ultra-fast and standard fast, mixed by vehicle and site. Normally energy flows from grid to vehicle; under V2G it can flow the other way. That reversibility is what turns charging from a cost line into a dispatchable resource.

One chain, two directions: the roles swap between day and night 10kV substation campus grid connection Split DC charger 480kW class, power sharing DC terminals ultra-fast / fast Vehicles battery, charge and discharge Forward: grid to vehicle (off-peak charging, power shared on demand) Reverse: vehicle to grid (V2G at peak, only with compatible vehicles and terminals) Three preconditions for reverse flow: a bidirectional vehicle, a bidirectional terminal, and metering plus protection at the grid point. Miss one and V2G stays a demo.
One diagram has to explain both: how charging works in normal hours and how discharge works at peak. The platform therefore reports a charging power curve and a discharged-energy figure, not a single aggregate "charge volume".

Five states: finer than online / offline

Chargers run normal, in progress, completed, fault, out of service. "In progress" and "completed" are business states, not device states — a gun delivering power and a car that just unplugged are both healthy equipment at different stages. Merge them and utilisation stops being measurable.

Orders and vehicles: two different counts

Charging count must be viewable in total and per-terminal orders; vehicle movements are counted separately. "100 sessions" and "60 vehicles" are not the same thing — one is transactions, the other traffic. Traffic drives the vehicle animation; transactions drive revenue analysis.

Safety data: temperature comes first

Charger and terminal temperature, fault messages and warnings belong on their own. High-power faults usually begin with a temperature rise, and protection acting means it is already late. A dedicated temperature curve beats a single "fault" flag.

Why charging belongs in 3D, not just a list. Because the operating questions are spatial: is that bay blocked by a petrol car, is a cable lying across the lane, does the entry-to-exit path actually flow. None of that reads in a table. A short vehicle animation beside live power lets a duty officer see "we are queueing" in one second. The animation is a state expression, not an effect.

HVAC & Floors

HVAC is the campus's largest load, and the hardest to see

Cooling leaves the plant, passes through chilled-water and condenser pumps and the cooling tower, and reaches each floor through ducts. That chain sits above ceilings and inside shafts, so the owner normally sees one total cooling figure and one electricity bill. Floor explosion exists to turn "how much did this building use" into "is the vent on this floor actually working".

L1 Lobby & cateringL2 Vents & panelsL3 AHU plantL4 OfficesL5 Offices & meetingRoof PV & weather station

Floor explosion: five floors plus the roof pulled apart, AHU units on L3, PV arrays and a weather station on the roof. Only five buildings are exploded in the real project; long-span structures such as hangars are handled as a whole — the point is to reveal equipment relationships, not to show off.

Six device types, one cooling chain

Chillers, cooling towers, water chillers, chilled-water pumps and condenser pumps — the data sheet lists device types, but in operation they form one chain: the plant makes cooling, chilled pumps move it, towers reject heat, condenser pumps circulate. Any stop reduces cooling, but the shape differs: a plant stop is a cliff, a pump stop is a decline.

AHU: scheduled by flights and footfall

Air-handling units need parameters by space, flight information and time window, adjusting automatically against predicted footfall, solar gain and ventilation. That requirement fits an airport precisely: a flight wave brings a surge of people, and terminal and office rhythms are nothing alike, so one fixed schedule cannot serve both.

Heat map: see which floor is warm

Colouring each floor by temperature and laying it over the stack is the most direct view in the platform. It does not replace the BMS, but it lets a non-specialist say "that floor is wrong" within a minute. Visualisation here lowers the cost of conversation, not of control.

What to look atGranularityBasis for judgement
Live power drawTotal / zone / unitDeviation from history at the same temperature and hour
Device distribution by floorBuilding / floorWhich floor is densest, which is uncovered
Consumption statisticsTotal / zone / unitYear, month, week, day — for allocation and targets
Safety dataSingle unitTemperature, faults, warnings — plants and pumps differ
MaintenanceSingle unitID, service time, technician, tied to the work order

2D vs 3D

3D answers "where"; 2D answers "how much, and why"

The original scope carried both a "3D visualisation platform" and a full "energy and carbon management platform" checklist — from demand declaration to consumption reports, from carbon accounting to maintenance tickets. These are not old and new; they are a division of labour. Move the 2D functions into 3D and both sides get worse.

Question to answerIn 3DIn 2D
Which building, which floor, which positionYes—
Where energy flows, and whether it is flowingYes—
Live situation for generation, load and chargingYesList backup
How much more than last month, and why—Yes
Whether maximum demand is over, and what to declare—Yes
Carbon accounting, green share, disclosure—Yes
Repairs, dispatch, service history, health—Yes
Briefings, site visits, explaining the campusYes—

The 2D half keeps the books

  • Demand management: actual, forecast and declared demand against each other, with deviation and compliance rates
  • Consumption analysis: year-on-year, month-on-month, zone ranking, zone share, energy per square metre
  • Reporting: a monthly report generated automatically, text and charts, usable for external disclosure
  • Carbon: emissions derived from the energy mix, linked to green share
  • Energy plan: target versus actual per zone, with over- and under-run counted separately

The 3D half reads the situation

  • Campus overview: seven buildings, PV arrays, EV station and distribution node on one screen
  • Energy flow: PV to buildings, substation to chargers, direction and power in real time
  • Floor penetration: open a building and travel down to equipment and vents
  • Device focus: camera moves to a single unit and opens its live data and service history
  • Vehicle animation: arrival, charging and departure as one sequence
One concrete trade-off. The 3D home screen carries four numbers only: total energy, total emissions, efficiency index and consumption trend. No tables, no ranking, no report links. Rankings and reports live in 2D. Not because 3D cannot draw them, but because viewing distance sets type size, and type size sets how much information can exist — from three metres away, only numbers and positions survive.

The Data Bedrock

Fix the 25 parameters first, and four systems have somewhere to land

This project connects to more than one system: PV sits behind an inverter vendor's platform, charging behind an operator platform, HVAC behind a building management system, video behind a surveillance platform. Four vendors, four interfaces, four naming schemes. Design the screens first and you end up with a wall of empty cards. So before work started, the team did one thing: wrote down 25 parameters with granularity and source.

PV 7 Charging 8 HVAC 6 Video 4
25 in total; each one states its granularity (total / zone / unit), source system and interface
PV · 7 Charging · 8 HVAC · 6 Video · 4

PV: from "how much is installed" to "why less today"

  • Type and count: capacity and modules by building and roof
  • Live generation: total, zone and single-unit power
  • Generation statistics: day, month, year and history
  • Device state: normal, fault, out of service with a reason
  • Safety data: temperature, fault messages, warnings
  • Maintenance: ID, service time, technician
  • Avoided emissions: the figure used for carbon reporting

Data usually comes from the inverter vendor's cloud or a local gateway; power is sampled at high frequency, generation is aggregated per minute.

Charging: keep the equipment ledger and the traffic ledger apart

  • Type and count: liquid-cooled ultra-fast, DC fast, AC slow
  • Live charging: power and gun state by site, zone or unit
  • Energy delivered: by station, by charger, by period
  • Session count: total and per-terminal orders
  • Vehicle movements: traffic counted separately from orders
  • Device state: normal, in progress, completed, fault, out of service
  • Safety data: temperature, faults, warnings
  • Maintenance: ID, service time, technician

Interfaces typically come from the charging operator, order data needs paging and de-duplication by time window, and V2G discharge needs its own field.

HVAC: six device types on one cooling chain

  • Type and count: chillers, cooling towers, water chillers, chilled pumps, condenser pumps
  • Floor distribution: which building and floor each unit sits on
  • Live power: total, zone and single unit
  • Consumption statistics: year, month, week, day
  • Safety data: temperature, faults, warnings
  • Maintenance: ID, service time, technician

Most of this lives in the BMS, usually over BACnet or Modbus. If the BMS is closed, the route is a gateway or independent meters.

Video: not just "show me the picture"

  • Cameras by zone: browsed per area and mapped to 3D points
  • Face recognition: authorised access and exception alerts
  • Smoke detection: smoke and fire points within the frame
  • Workwear detection: compliance checks in MRO areas

Video connects over GB/T 28181 or a vendor SDK; AI recognition is an overlay that does not change the existing platform. Face features involve personal data, so scope and retention must be limited.

"To be confirmed" is honest, not vague. In the quotation, the integration line for PV, charging and load equipment reads to be confirmed, because the route depends on whether each vendor opens up and how far. There are three common paths: an open API (best), a read-only database account (good, but watch schema changes), or an added collection gateway (most expensive, most controllable). Fix the parameter table first and the screens survive any of the three.

One entry point, one identity

The brief is explicit: multiple systems managed under one data platform, unified sign-in through a portal or main cockpit, unified device authentication. In practice that means one account system, one role model, and visibility scoped per system — not four systems with four passwords.

Grade the alarms; do not call everything urgent

Device faults, consumption anomalies and parameter anomalies need different responses: a fault sends someone to site, an anomaly first questions the data, a parameter alert may just be a bad threshold. Merge them into one list and the duty officer starts ignoring it within a week.

Two-phase Delivery

Why this kind of project ships in two phases: DEMO sets the skeleton, FINAL fills it in

Every line in the quotation carries two ratios: how much is done at DEMO, how much at FINAL. Overall it is 0.8 to 0.2, but per line the split differs sharply — concept and UI reach eighty percent at DEMO, while 3D assets only reach thirty. That is not stalling; it is ordering the work so rework costs the least.

Work itemDEMO ← → FINALDone at DEMO
Concept and presentation definition80%
UI / UX design80%
Scene and graphic definition50%
Site plate and surrounding GIS30%
Building models and floor split30%
Equipment models (PV / charging / load)30%
Floor explode and vehicle animation25%
Camera moves and shaders50%
Platform framework and home60%
PV / charging / HVAC modules30%
Test, optimisation, deployment30%
Data integration (three systems)Pending
Completed at DEMO Left for FINAL Each cell is 10% of the work, converted from the quotation's phase ratios

First: the parts that set direction

Concept, visuals, platform framework, home screen — eighty percent at DEMO, because they decide what this thing looks like and how it is structured. Get the direction wrong and every model and animation after it is wasted. Letting the client click through a DEMO beats ten document reviews.

Later: the parts that wait on confirmation

Building models, equipment models and animation stop at thirty percent, because their precision depends on three things: accurate drawings, an equipment list and point coordinates. Those usually wait on the client and the vendors. Thirty percent proves the pipeline and the style; the rest lands in one pass when the inputs are complete.

01

Concept & UI

Modules, presentation, UI/UX, scene and graphic definition

02

Scene assets

Site plate, buildings, floor split, equipment, car parks

03

Motion

Floor explode, vehicle charging, camera moves, shaders

04

Engine & features

UI build, asset loading, platform framework, three modules

05

Integration

PV, charging, HVAC and video data, reconciled

06

Deploy & train

On-site deployment, roles, duty training, handover docs

Security & O&M

Security and operations: it has to dispatch work, not just look good

An energy platform has more than one user: the duty officer watches alarms, maintenance watches devices and tickets, management reads reports, security watches video. Four people, one system, and four different front doors.

Video: by zone, by point

Cameras map to points in the 3D scene, so one click brings up the picture. "Something alarmed here" and "what does here look like" become the same gesture instead of a switch to another video system and a walk down a tree.

Three recognitions, three boundaries

Face for authorised access and exceptions, smoke for fire points in frame, workwear for compliance in MRO areas. Recognition assists, it does not enforce — every result needs a human check, and collection scope and retention must be bounded.

Tickets: sorted by urgency

Repairs sort by time, area and urgency, and the system generates start and end times to close the loop. Tickets are not an accessory: equipment health and maintenance strategy are rebuilt from this table's history.

RoleShould seeShould not see
Duty officerLive alarms, device state, videoContracts, pricing, personnel data
Maintenance engineerDevice records, service history, tickets, curvesOther departments' consumption detail
Energy managerDemand, ranking, reports, carbonRaw camera feeds
Management / visitorsOverview wall, green share, avoided emissionsDevice control, parameter push
One rule from experience. Never put a control on the big screen. The wall sits in a public area with a mouse beside it, and one wrong click can stop a bank of chargers. Control stays in the 2D back end with confirmation and an audit log; 3D only looks and locates.

Delivery & FAQ

Handover, and five questions that come up every time

This kind of project hands over more than software: models, effects, interfaces, documents and training. Miss one and it comes back as a question every week after go-live.

Handover list

  • 3D assets: site plate, seven buildings, five floor-exploded, car parks, equipment models
  • Motion: floor explode, vehicle charging, camera moves, energy flow and shaders
  • 3D wall: overview, PV, charging, HVAC, load and video views
  • 2D platform: demand, consumption analysis, reports, carbon, tickets and device ledger
  • Integration: collection, cleaning, reconciliation and back-fill for four systems
  • Accounts and roles: unified sign-in, role split, audit log
  • Deployment and operations docs: install, backup, common faults
  • Training: separate sessions for duty, maintenance and administrators

Rhythm

Scope → parameter and point tables signed off → concept and UI → DEMO review → models and motion → integration → FINAL review → deploy and train. The parameter table and point table are the two most under-estimated documents: until they are fixed, every later stage reworks.

If the client already has models or as-built drawings, the schedule compresses; if even the site plan has to be surveyed, budget time for survey and reconciliation.

Why not just buy a SCADA package or an energy SaaS?

Standard products are good at generic reports and device connectivity, and bad at the specific spatial relationships of these seven buildings, five floors and three systems. That spatial layer is the whole point here: which roof, which floor, which bay. SCADA can draw a diagram but cannot give a floor-penetrable 3D scene; SaaS can produce a report but will not connect into the campus's own 3D base. Hence standard capability plus a custom scene.

What does the client have to provide for the 3D models?

Four things: a site plan or satellite base map for position, architectural drawings for volume, an equipment list with photos for appearance and model, and point coordinates for mounting. The hardest to assemble is building photos and equipment appearance — drawings give dimensions, not material or colour.

What if the PV and charging vendors will not open an interface?

Three routes in priority order: ask for an API or data push; request a read-only database account and agree a change-notification clause; add a collection gateway or independent meters and take the data physically. The third is the most expensive and the least dependent on the vendor. On our side the adapter layer is separate, so changing the route does not touch the screens above it.

The wall is built — which screen does a duty officer actually use?

The 2D one. The wall is for visits, briefings and central monitoring; daily work — tickets, reports, demand checks, parameter changes — happens in the 2D back end. Which is exactly why the project split into two lines instead of pushing every feature into 3D.

Can the numbers here be used for carbon disclosure?

As the basis for internal accounting and trend management, yes; formal disclosure still goes through third-party verification. What the platform can do is aggregate consumption by category and sub-item, tag green energy separately, and keep emission factors and methodology in configuration rather than hard-coded. Then swapping a factor or adding evidence at audit time does not need a code change. Traceable data matters more than a handsome number.

MORE CASES

More Related Cases

Campus PV energy platform
Digital TwinEnergy consumption management, clean energy

Campus PV energy platform

An integrated energy platform for an aviation-base campus, delivered as a 3D digital twin plus a 2D ...

View Details →
Digital-twin bird-repellent system
Digital TwinEcological bird repelling, visual analysis

Digital-twin bird-repellent system

A bird-hazard platform for a regional grid operator's transmission maintenance team, delivered as a ...

View Details →

View All Cases →

Planning a similar production line or enterprise system?

Start with our pricing logic, then let's talk requirements — cost structure, technology comparison and acceptance criteria, all laid out in the open.