Kreeshiv logoKreeshiv Energy Emission Monitoring Tool
System documentation

Technical Architecture, Data Flow and GHG Methodology

A factual description of the current Kreeshiv Energy Emission Monitoring Tool release, prepared for technical review, copyright-registration support, implementation discussions, and audit-support reference.

Release
0.1.0

Current documented application version

Application
Next.js web system

Public pages, protected workspace, and PDF reporting

Documentation date
August 23, 2026

Reflects the currently deployed architecture

Architecture

Overall system architecture

The current release is a single Next.js application deployed on Vercel. Public information, authentication, the protected calculator, the calculation engine, and PDF reporting are maintained in one source project.

Major modules

Module responsibilities and interaction

Public website and SEO

Server-rendered public pages present the product, solutions, resources, legal notices, security information, and contact channels. Route metadata, canonical URLs, structured data, robots rules, and the XML sitemap support discoverability.

Authentication and session control

The login endpoint checks a configured administrative username and password on the server. A successful login creates a signed HTTP-only session cookie before the protected workspace is served.

Organisation and activity data

Users configure organisation identity, location, reporting period, employee count, and activity quantities covering fuel, energy, transport, refrigerants, water, waste, materials, travel, food, freight, commuting, and home working.

Emission-factor registry

Typed factor tables are derived from the supplied GHG calculation workbook. Each factor retains its unit, source sheet, and source cell or range where available, supporting traceability from input to output.

Calculation and validation engine

Deterministic TypeScript functions convert activity data to kg CO2e, group results into Scope 1, Scope 2, and selected Scope 3 categories, convert totals to tonnes, and flag missing country or category factors.

Dashboard and reporting

The workspace provides total and scope metrics, category contribution views, source summaries, validation warnings, tabular outputs, an on-screen report, and a client-ready downloadable PDF.

Calculation methodology

Activity data × emission factor

kg CO2e = activity quantity × factor
t CO2e = kg CO2e ÷ 1,000

Factors are mapped from the supplied workbook GHG_emissions_calculator_base.xlsx. Calculation categories retain workbook sheet and cell references where available. Country-specific electricity factors are selected from the organisation or activity country.

Scope 1 — direct emissions

  • ✓Stationary fuels
  • ✓Refrigerants and fugitive emissions
  • ✓Owned passenger vehicles
  • ✓Owned delivery vehicles

Scope 2 — energy indirect

  • ✓Purchased electricity
  • ✓Purchased heat and steam
  • ✓Owned electric-vehicle electricity
  • ✓District cooling

Selected Scope 3 — other indirect

  • ✓Well-to-tank fuels and T&D losses
  • ✓Water, waste, and materials
  • ✓Business travel and accommodation
  • ✓Freight and commuting
  • ✓Food and home office
Validation rules flag missing grid or country factors. A warning causes the affected activity to remain uncalculated rather than silently applying an assumed value. Users remain responsible for source-data quality, factor suitability, organisational boundaries, and external assurance requirements.
Workflow

Automation, notification and escalation

  1. 1

    Authenticate

    The administrator signs in through the server-validated login flow.

  2. 2

    Set reporting context

    Organisation, location, employee count, and reporting period are confirmed.

  3. 3

    Enter activity data

    Quantities are recorded against the relevant fuel, energy, travel, waste, water, freight, and other categories.

  4. 4

    Calculate automatically

    The calculation engine applies the configured factors and recomputes scope and category totals immediately.

  5. 5

    Review validation

    Missing grid or country factors appear as on-screen warnings that must be resolved or documented.

  6. 6

    Review and report

    The dashboard is reviewed and a dated PDF is generated for management or audit-support use.

Implemented automation

Recalculation, scope aggregation, category ranking, validation, browser-state saving, report rendering, and PDF preparation occur automatically after user input.

Current notification boundary

Warnings are displayed inside the workspace. The current release does not send email, SMS, messaging, ticketing, or automated escalation notifications. Review, correction, approval, and follow-up remain human-controlled.

Data architecture

Data-flow diagram and storage model

The current release has no central application database. Calculator information stays in the user's browser on that device; authentication is handled separately through the server and a signed cookie.

Data setLocationCurrent behavior
Credentials and signing secretVercel server environmentUsed only by server-side authentication; credentials are not written to browser storage.
SessionSigned HTTP-only cookieExpires after 8 hours, or 30 days when “Remember me” is selected.
Calculator stateBrowser local storagePersists on the current browser/device until the user or browser clears it.
ReportsGenerated in the browserDownloaded by the user; the application does not centrally archive generated files.

API and integration details

  • Internal login endpoint: POST /api/login accepts the login form, validates credentials server-side, and establishes the session.
  • Logout route: clears the session cookie before returning the user to the login page.
  • PDF integration: the React PDF renderer creates the report in the browser from calculated state.
  • Current boundary: there is no external ERP, utility, accounting, audit-platform, email, messaging, or cloud-database integration in this release. The contact form provides an email fallback rather than transmitting form data.

Security, access and data management

  • ✓Credentials and the HMAC signing secret are held in server environment variables.
  • ✓Credential and signature checks use timing-safe comparison.
  • ✓Sessions use HMAC-SHA256 signatures and HTTP-only, SameSite=Lax cookies; Secure is enabled in production.
  • ✓The protected /app route verifies the session on the server and redirects unauthenticated users.
  • ✓Calculator data is browser-local and is not a substitute for an encrypted records repository or managed backup.
  • ✓The current release has a single configured administrative identity; multi-user RBAC, database audit logs, and central retention controls are not implemented.
Audit ecosystem context

Support for standards-related evidence workflows

The tool can support consultancy, evidence preparation, management review, and carbon-footprint discussions connected with customer or audit programmes such as SA8000, WRAP, RJC, and Disney FAMA. It organises GHG activity data and produces supporting reports; it does not itself perform certification or social-compliance audits.

No accreditation or affiliation is implied. Certification-body relationships, programme approvals, audit conclusions, and use of third-party marks must be confirmed and documented separately by the legally authorised organisations.

SA8000
WRAP
RJC
Disney FAMA
Technical evidence

Available supporting artefacts

Source application

Typed Next.js and React source for the public site, protected workspace, calculations, authentication, and reports.

Factor workbook

The supplied GHG emissions calculator workbook used as the traceable base for factor and worksheet mappings.

Calculation references

Scope categories retain worksheet or range references, supporting review against the original workbook logic.

Live system outputs

Public pages, authenticated dashboard views, validation messages, report preview, and downloadable PDF output.

Need a controlled technical-document package?

Contact Kreeshiv Consultancy for a dated project-specific package, verified partnership details, authorised screenshots, or implementation material suitable for a reviewer or registration submission.

Request documentation