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
 
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 1 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
Y
String
5
DayType
12
Y
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 is profile is for study mode only (for example, Peak, Seasonal Peak, etc).
Note 2: Optional fields may be omitted from the file, resulting in 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 provided 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 please leave the temperature field null.
If the customer wish to provide the input data at meter level then the SRS rule "PA_ProfileData" value has to set as "METER". And the data format in csv file should be as per the SRS rule PA_MeterColumnMap.
 
The Meter load profile data is provided as a comma-separated file with a comma separated header. The expected (but not required) header is:
Date,MeterID,MeterAlternateName,FeederName,DayType,Hour,KW,KVAR