Load Profile File Format
Profiles are to be loaded on customer specified maintenance interval (Product recommends doing this weekly or bi-weekly to reduce the CSV file size). Profiles can be either at Meter level or aggregated by the customer from meter data to service transformers that are represented as load points within the NMS. The data provided for each service transformer will represent a profile for a specific date, for study mode only profiles (for example, Peak, Seasonal Peak) a blank date can be provided.
The transformer load profile data is provided as a comma-separated file with a comma separated header.
The expected (but not required) header is:
Date,TransformerName,TransformerAlternateName,FeederName,DayType,
Hour,KW,KVAR,Temperature
For any columns that are optional, and are not configured for a particular project, omit them from the header. For example, if FeederName and DayType are not going to be provided in the CSV, please omit them from the header.
Date,TransformerName,TransformerAlternateName,Hour,KW,KVAR,
Temperature
 
File Characteristics
Values
Fixed length fields?
N
Delimiter
Comma
Header style
Comma separated, optional
Footer Style
No
No of files
Can be feeder based or one file for entire service territory
 
S. No
Field Name
Length
Mandatory
Data type
Order of the element in the record.
Name of the field.
Field Length
Optional (N) or
Mandatory (Y)
 
[Note #]
Data type as per XSD standards.
1
Date (MM/DD/YY)
8
Y [1]
Date
2
TransformerName
32
Y
String
3
TransformerAlternateName
32
N [2]
String
4
FeederName
32
N [5]
String
5
DayType
12
N [5]
Enumerated string (weekday, weekend, peak) or associated Integer key that corresponds to the DayType
6
Hour
2
Y
Integer (max 23)
7
KW
N/A
Y
Floating point
8
KVAR
N/A
Y [3]
Floating point
9
Temperature
N/A
N [4]
Floating point, can be provided in either Fahrenheit or Celsius
 
Note 1: Date can be left blank if the profile is for study mode only (for example, Peak, Seasonal Peak, and so on).
Note 2: Optional fields may be omitted from the file using two consecutive commas.
Note 3: If KVAR is not measured, it can be calculated from KW with a default power factor.
Note 4: The Temperature field is optional. A utility may provide temperature data for location, date, and time. If no temperature data is provided, the adapter will use historical data stored in the NMS database. If this data is going to be omitted, leave the temperature field null.
Note 5: If both FeederName and DayType are made optional, the following changes must be implemented.
1. Modify SRS Rule PA_MeterColumnMap:
• Remove both FeederName and DayType columns from the rule.
• Update the remaining columns’ Rule value2 to reflect the revised sequence. The expected header sequence should be:
Date, MeterID, MeterAlternateName, Hour, KW, KVAR
2. Update SRS Rule PA_TransColumnMap:
• Apply similar modifications as above (i.e., remove FeederName and DayType, update column sequencing accordingly).
3. Update SRS Rule PA_NumDataCol:
• Adjust the value to reflect the new number of columns configured.
4. Important Note:
• If DayType is omitted, study profiles (e.g., peak profiles) cannot be provided via the adapter.
5. If FeederName and DayType are optional, your data header is expected (but not required) to be:
Date,MeterID,MeterAlternateName,Hour,KW,KVAR
If a customer wants to provide input data at the meter level, then the SRS rule PA_ProfileData value has to be set to METER. The data in the CSV file should follow the format defined by the SRS rule PA_MeterColumnMap.
Meter load profile data should be supplied as a comma-separated values (CSV) file with a corresponding comma-separated header. The expected (but not required) header format is:
Date,MeterID,MeterAlternateName,FeederName,DayType,Hour,KW,KVAR