> For the complete documentation index, see [llms.txt](https://docs.net2grid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.net2grid.com/net2grid-energy-ai-cloud-interface-specifications/monthly-grid-intelligence/input/profiles.md).

# Installation Profiles

## Installation Profiles

This document describes the Installation Profile specifications required for the DER Detection services of the Monthly Grid Intelligence tier.

The DER profile model is intentionally lightweight and focuses only on location-related attributes.

***

### Supported Profile Attributes

DER Detection currently supports the following installation profile attributes:

| Attribute    | Description                                       | Acceptable Values             |
| ------------ | ------------------------------------------------- | ----------------------------- |
| `country`    | The country in which the installation is located. | ISO 3166 alpha-2 country code |
| `postalCode` | The postal code of the installation.              | Any valid postal code         |
| `timezone`   | The timezone of the installation.                 | Any valid timezone            |

***

### Profile Usage

DER Detection is primarily data-driven and can operate without installation profile information.

However, providing accurate profile data improves:

* regional climate interpretation
* HVAC behavior detection
* solar production interpretation
* timezone alignment
* overall DER detection quality

Providing all three supported attributes is strongly recommended.

***

### Default Profile Behavior

NET2GRID EnergyAI® supports an optional Default Profile mechanism for DER Detection.

The default profile is configured per label partner and may provide fallback values for:

* `country`
* `postalCode`
* `timezone`

***

#### Default Profile Rules

* If no installation profile exists, the default profile is used entirely.
* If the installation profile is partial, missing attributes may be inherited from the default profile.
* If the installation profile contains all supported attributes, only the installation profile is used.

This inheritance mechanism ensures that DER Detection always has a coherent minimal location profile available.

***

### Profile Update Behavior

Profiles may be updated by uploading a new profile file for the same installation.

The latest uploaded profile replaces the previously stored profile for the installation.

Partial profile updates are not supported. All desired attributes should be included in the new profile file.

***

### Profile Validation

Uploaded profile files are validated before being accepted.

Validation may include checks such as:

* valid JSON structure
* supported attribute names
* valid country codes
* valid timezone values

Invalid attributes may be ignored or rejected depending on the validation severity.

***

## Profile File Structure

Each installation profile is provided as a single JSON file.

The DER Detection profile contains only the `home` section.

| Section | Description                    |
| ------- | ------------------------------ |
| `home`  | Installation location metadata |

***

### Filename Format

```
{external-installation-id}_profile.json
```

Example:

```
123456789_profile.json
```

***

### Upload Location

Profile files are uploaded through AWS S3 using the agreed bucket structure.

#### Path Format

```
s3://{bucket_name}/{labelpartner}/profiles/
```

***

## JSON Structure

### home

Contains installation location metadata.

Example:

```json
{
  "home": {
    "country": "NL",
    "postalCode": "1234AB",
    "timezone": "Europe/Amsterdam"
  }
}
```

***

## Example Profile File

```json
{
  "home": {
    "country": "BE",
    "postalCode": "3500",
    "timezone": "Europe/Brussels"
  }
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.net2grid.com/net2grid-energy-ai-cloud-interface-specifications/monthly-grid-intelligence/input/profiles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.