814 General Request, Response or Confirmation

Functional Group ID=GE

Introduction:

This Draft Standard for Trial Use contains the format and establishes the data contents of the General Request, Response or Confirmation Transaction Set (814) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to request actions to be performed, to respond to a request for actions to be performed or to confirm information related to actions performed.

Heading:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
M	010	ST	Transaction Set Header	M	1									
M	020	BGN	Beginning Segment	M	1									
			LOOP ID - N1			>1								
	040	N1	Distribution Company (N1~8S)	O	1									
														
			LOOP ID - N1			>1								
	040	N1	Supplier (N1~SJ)	O	1									
														
			LOOP ID - N1			>1								
	040	N1	Name (Retail Customer)	O	1									
	070	N4	Geographic Location	O	1									

Detail:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
			LOOP ID - LIN			>1								
	010	LIN	Item Identification	O	1									
	020	ASI	Action or Status Indicator	O	1									
	030	REF	Reference Identification (Supplier Account Number)	O	>1									
	030	REF	Reference Identification (Distribution Company Account Number/SDID)	O	>1									
	030	REF	Reference Identification (Bill Presenter)	O	>1									
	030	REF	Reference Identification (Bill Calculator)	O	>1									
	030	REF	Reference Identification (Interval Status)	O	>1									
	040	DTM	Date/Time Reference (Customer Authorization Date)	O	>1									
	060	AMT	Monetary Amount (Tax Exemption Percentage)	O	>1									
			LOOP ID - NM1			>1								
	080	NM1	Individual or Organizational Name (Meter Information)	O	1		n1							
	130	REF	Reference Identification (Supplier Rate Code)	O	>1									
	130	REF	Reference Identification (Utility Rate Class)	O	>1									
														
M	150	SE	Transaction Set Trailer	M	1									

Transaction Set Notes

1.	The NM1 loop is used to identify the parties associated with the individual line item (LIN), such as an individual consumer in a consolidated third party Consumer Service Provider transaction.

	Segment:	ST Transaction Set Header
	Position:	010
	Loop:
	Level:	Heading
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To indicate the start of a transaction set and to assign a control number
	Syntax Notes:
	Semantic Notes:	1	The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
	Comments:
Notes:		Required	
		ST~814~000000001	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	ST01	143	Transaction Set Identifier Code	M		ID 3/3	
	Code uniquely identifying a Transaction Set	
 	814		General Request, Response or Confirmation	
Must Use	ST02	329	Transaction Set Control Number	M		AN 4/9	
	Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set	

	Segment:	BGN Beginning Segment
	Position:	020
	Loop:
	Level:	Heading
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To indicate the beginning of a transaction set
	Syntax Notes:	1	If BGN05 is present, then BGN04 is required.
	Semantic Notes:	1	BGN02 is the transaction set reference number.
		2	BGN03 is the transaction set date.
		3	BGN04 is the transaction set time.
		4	BGN05 is the transaction set time qualifier.
		5	BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction.
	Comments:
Notes:		Required	
		BGN~13~20121215123000001~20121215	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	BGN01	353	Transaction Set Purpose Code	M		ID 2/2	
	Code identifying purpose of transaction set	
 	13		Request	
Must Use	BGN02	127	Reference Identification	M		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	A unique transaction identification number assigned by the originator of this transaction.  This number must be unique over time.

Transaction Reference Numbers will only contain uppercase letters (A to Z), digits (0 to 9), dashes (-) and periods (.).  Note that all other characters (spaces, underscores, etc.) must be excluded.	
Must Use	BGN03	373	Date	M		DT 8/8	
	Date expressed as CCYYMMDD	
	The transaction creation date - the date that the data was processed by the sender's application system.	

	Segment:	N1 Distribution Company (N1~8S)
	Position:	040
	Loop:	N1        Optional
	Level:	Heading
	Usage:	Optional
	Max Use:	1
	Purpose:	To identify a party by type of organization, name, and code
	Syntax Notes:	1	At least one of N102 or N103 is required.
		2	If either N103 or N104 is present, then the other is required.
	Semantic Notes:
	Comments:	1	This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
		2	N105 and N106 further define the type of entity in N101.
Notes:		Required	
		N1~8S~DISTRIBUTE-IT INC.~1~007909411~~41	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	N101	98	Entity Identifier Code	M		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	8S		Consumer Service Provider (CSP)	
	Distribution Company	
Must Use	N102	93	Name	X		AN 1/60	
	Free-form name	
	Distribution Company Name	
Must Use	N103	66	Identification Code Qualifier	X		ID 1/2	
	Code designating the system/method of code structure used for Identification Code (67)	
 	1		D-U-N-S Number, Dun & Bradstreet	
 	9		D-U-N-S+4, D-U-N-S Number with Four Character Suffix	
Must Use	N104	67	Identification Code	X		AN 2/80	
	Code identifying a party or other code	
	Distribution Company D-U-N-S or D-U-N-S+4 Number	
Recom.	N106	98	Entity Identifier Code	O		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	40		Receiver	

	Segment:	N1 Supplier (N1~SJ)
	Position:	040
	Loop:	N1        Optional
	Level:	Heading
	Usage:	Optional
	Max Use:	1
	Purpose:	To identify a party by type of organization, name, and code
	Syntax Notes:	1	At least one of N102 or N103 is required.
		2	If either N103 or N104 is present, then the other is required.
	Semantic Notes:
	Comments:	1	This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
		2	N105 and N106 further define the type of entity in N101.
Notes:		Required	
		N1~SJ~SUPPLY LTD~9~007909422CRN1~~40	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	N101	98	Entity Identifier Code	M		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	SJ		Service Provider	
	Supplier	
Must Use	N102	93	Name	X		AN 1/60	
	Free-form name	
	Supplier Name	
Must Use	N103	66	Identification Code Qualifier	X		ID 1/2	
	Code designating the system/method of code structure used for Identification Code (67)	
 	1		D-U-N-S Number, Dun & Bradstreet	
 	9		D-U-N-S+4, D-U-N-S Number with Four Character Suffix	
Must Use	N104	67	Identification Code	X		AN 2/80	
	Code identifying a party or other code	
	Supplier D-U-N-S or D-U-N-S+4 Number	
Recom.	N106	98	Entity Identifier Code	O		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	41		Submitter	

	Segment:	N1 Name (Retail Customer)
	Position:	040
	Loop:	N1        Optional
	Level:	Heading
	Usage:	Optional
	Max Use:	1
	Purpose:	To identify a party by type of organization, name, and code
	Syntax Notes:	1	At least one of N102 or N103 is required.
		2	If either N103 or N104 is present, then the other is required.
	Semantic Notes:
	Comments:	1	This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
		2	N105 and N106 further define the type of entity in N101.
Notes:		Required	
		N1~8R~CUSTOMER NAME	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	N101	98	Entity Identifier Code	M		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	8R		Consumer Service Provider (CSP) Customer	
	Retail Customer	
Must Use	N102	93	Name	X		AN 1/60	
	Free-form name	
	Retail Customer Name	

	Segment:	N4 Geographic Location
	Position:	070
	Loop:	N1        Optional
	Level:	Heading
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify the geographic place of the named party
	Syntax Notes:	1	If N406 is present, then N405 is required.
	Semantic Notes:
	Comments:	1	A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
		2	N402 is required only if city name (N401) is in the U.S. or Canada.
Notes:		Optional - May be required by Applicable Regulatory Authority.	
		N4~~~78111	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	N403	116	Postal Code	O		ID 3/15	
	Code defining international postal zone code excluding punctuation and blanks (zip code for United States)	

	Segment:	LIN Item Identification
	Position:	010
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify basic item identification data
	Syntax Notes:	1	If either LIN04 or LIN05 is present, then the other is required.
		2	If either LIN06 or LIN07 is present, then the other is required.
		3	If either LIN08 or LIN09 is present, then the other is required.
		4	If either LIN10 or LIN11 is present, then the other is required.
		5	If either LIN12 or LIN13 is present, then the other is required.
		6	If either LIN14 or LIN15 is present, then the other is required.
		7	If either LIN16 or LIN17 is present, then the other is required.
		8	If either LIN18 or LIN19 is present, then the other is required.
		9	If either LIN20 or LIN21 is present, then the other is required.
		10	If either LIN22 or LIN23 is present, then the other is required.
		11	If either LIN24 or LIN25 is present, then the other is required.
		12	If either LIN26 or LIN27 is present, then the other is required.
		13	If either LIN28 or LIN29 is present, then the other is required.
		14	If either LIN30 or LIN31 is present, then the other is required.
	Semantic Notes:	1	LIN01 is the line item identification
	Comments:	1	See the Data Dictionary for a complete list of IDs.
		2	LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
Notes:		Required - Only one service may be requested per LIN loop and it is important that the sender order the LIN loops in the order that they would like them processed for all primary services.  It is required that the LIN for Energy Services (CE) be sent prior to all secondary services (HU, HI) if the secondary services are dependent upon the successful enrollment.	
		LIN~2012121500001~SH~EL~SH~CE
LIN~2012121500001H~SH~EL~SH~HU
LIN~HI2012121500001~SH~EL~SH~HI
LIN~20121215SI-00001~SH~EL~SH~SI	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	LIN01	350	Assigned Identification	O		AN 1/20	
	Alphanumeric characters assigned for differentiation within a transaction set	
	On the Request, identifier supplied in this element must uniquely identify each LIN request over time.  This number will be returned on the Response transaction in the same element. 	
Must Use	LIN02	235	Product/Service ID Qualifier	M		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
 	SH		Service Requested	
Must Use	LIN03	234	Product/Service ID	M		AN 1/48	
	Identifying number for a product or service	
 	EL		Electric	
 	GAS		Gas	
Must Use	LIN04	235	Product/Service ID Qualifier	X		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
 	SH		Service Requested	
Must Use	LIN05	234	Product/Service ID	X		AN 1/48	
	Identifying number for a product or service	
 	CE		Energy Services	
 	HI		Historical Interval Usage	
 	HU		Historical Usage	
 	SI		Interval Status	

	Segment:	ASI Action or Status Indicator
	Position:	020
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To indicate the action to be taken with the information provided or the status of the entity described
	Syntax Notes:
	Semantic Notes:
	Comments:
Notes:		Required	
		ASI~7~021	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	ASI01	306	Action Code	M		ID 1/2	
	Code indicating type of action	
 	7		Request	
Must Use	ASI02	875	Maintenance Type Code	M		ID 3/3	
	Code identifying the specific type of item maintenance	
 	021		Addition	
	Used for Enrollment (CE) and Interval Status (SI) Requests	
 	029		Inquiry	
	Used for Historical Usage (HU) and Historical Interval Usage (HI) Requests	

	Segment:	REF Reference Identification (Supplier Account Number)
	Position:	030
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		Optional	
		REF~11~1234567890	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	11		Account Number	
	Supplier Account Number	
Must Use	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	Supplier Account Number	

	Segment:	REF Reference Identification (Distribution Company Account Number/SDID)
	Position:	030
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		Required - Only one of either REF~12 or REF~Q5 may be sent as required by the Applicable Regulatory Authority governing documents.	
		REF~12~0000445648
REF~Q5~00040621002260654	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	12		Billing Account	
	Distribution Company Account Number	
 	Q5		Property Control Number	
	Service Delivery ID	
Must Use	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	Distribution Company Account Number or Service Delivery ID	

	Segment:	REF Reference Identification (Bill Presenter)
	Position:	030
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		Energy Services Request (LIN05 = CE): Required
Historical Usage Request (LIN05 = HU): Not Used
Historical Interval Usage Request (LIN05 = HI): Not Used
Interval Status Request (LIN05 = SI): Not Used	
		REF~BLT~LDC	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	BLT		Billing Type	
	Bill Presenter	
Must Use	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
 	DUAL		The Distribution Company and Supplier both Present Bills to the Customer	
	Used for Dual Billing	
 	ESP		The Supplier Presents the Consolidated Bill to the Customer	
	Used for Supplier Consolidated Billing	
 	LDC		The Distribution Company Presents the Consolidated Bill to the Customer	
	Used for Rate Ready and Bill Ready Distribution Company Consolidated Billing	

	Segment:	REF Reference Identification (Bill Calculator)
	Position:	030
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		Energy Services Request (LIN05 = CE): Required
Historical Usage Request (LIN05 = HU): Not Used
Historical Interval Usage Request (LIN05 = HI): Not Used
Interval Status Request (LIN05 = SI): Not Used	
		REF~PC~LDC	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	PC		Production Code	
	Bill Calculator	
Must Use	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
 	DUAL		Each party calculates its own charges	
	Used for Dual Billing, Bill Ready Consolidated Billing (Supplier or Distribution Company)	
 	LDC		The Distribution Company calculates the Supplier charges	
	Used for Rate Ready Distribution Company Consolidated Billing	

	Segment:	REF Reference Identification (Interval Status)
	Position:	030
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		Energy Services Request (LIN05 = CE): Not Used
Historical Usage Request (LIN05 = HU): Not Used
Historical Interval Usage Request (LIN05 = HI): Not Used
Interval Status Request (LIN05 = SI): Required	
		REF~17~SUMMARY	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	17		Client Reporting Category	
	Interval Status Request - Used to differentiate whether a Supplier would like to receive Monthly Summarized Usage (REF02 = SUMMARY) or Monthly Interval Usage (REF02 = DETAIL)	
Must Use	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
 	DETAIL		Supplier would like to receive Monthly Interval Usage for this Customer	
 	SUMMARY		Supplier would like to receive Monthly Summary Usage for this Customer	

	Segment:	DTM Date/Time Reference (Customer Authorization Date)
	Position:	040
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To specify pertinent dates and times
	Syntax Notes:	1	At least one of DTM02 DTM03 or DTM05 is required.
		2	If DTM04 is present, then DTM03 is required.
		3	If either DTM05 or DTM06 is present, then the other is required.
	Semantic Notes:
	Comments:
Notes:		Energy Services Request (LIN05 = CE): Required
Historical Usage Request (LIN05 = HU): Not Used
Historical Interval Usage Request (LIN05 = HI): Not Used
Interval Status Request (LIN05 = SI): Not Used	
		DTM~129~20121214~1500~ET	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	DTM01	374	Date/Time Qualifier	M		ID 3/3	
	Code specifying type of date or time, or both date and time	
 	129		Customer Contract Effective	
	Date and time of Retail Customer authorization	
Must Use	DTM02	373	Date	X		DT 8/8	
	Date expressed as CCYYMMDD	
	Date of Retail Customer authorization	
Must Use	DTM03	337	Time	X		TM 4/8	
	Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)	
	Time of Retail Customer authorization (HHMM Format), if tracked; otherwise, this will contain 0000. 	
Optional	DTM04	623	Time Code	O		ID 2/2	
	Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow	
 	CT		Central Time	
 	ET		Eastern Time	
 	MT		Mountain Time	
 	PT		Pacific Time	

	Segment:	AMT Monetary Amount (Tax Exemption Percentage)
	Position:	060
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To indicate the total monetary amount
	Syntax Notes:
	Semantic Notes:
	Comments:
Notes:		Energy Services Request (LIN05 = CE): Required for Rate Ready Consolidated Billing, otherwise Not Used.
Historical Usage Request (LIN05 = HU): Not Used
Historical Interval Usage Request (LIN05 = HI): Not Used
Interval Status Request (LIN05 = SI): Not Used	
		AMT~DP~.75
AMT~DP~0	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	AMT01	522	Amount Qualifier Code	M		ID 1/3	
	Code to qualify amount	
 	DP		Exemption	
	Tax Exemption Percentage	
Must Use	AMT02	782	Monetary Amount	M		R 1/18	
	Monetary amount	
	For percentage values, the whole number "1" represents 100 percent; decimal numbers less than "1" represent percentages from 1 percent to 99.9999 percent.	

	Segment:	NM1 Individual or Organizational Name (Meter Information)
	Position:	080
	Loop:	NM1        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To supply the full name of an individual or organizational entity
	Syntax Notes:	1	If either NM108 or NM109 is present, then the other is required.
		2	If NM111 is present, then NM110 is required.
	Semantic Notes:	1	NM102 qualifies NM103.
	Comments:	1	NM110 and NM111 further define the type of entity in NM101.
Notes:		Energy Services Request (LIN05 = CE): Required for Rate Ready Consolidated Billing, otherwise Not Used.
Historical Usage Request (LIN05 = HU): Not Used
Historical Interval Usage Request (LIN05 = HI): Not Used
Interval Status Request (LIN05 = SI): Not Used	
		NM1~MQ~3~~~~~~32~ALL	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	NM101	98	Entity Identifier Code	M		ID 2/3	
	Code identifying an organizational entity, a physical location, property or an individual	
 	MQ		Metering Location	
Must Use	NM102	1065	Entity Type Qualifier	M		ID 1/1	
	Code qualifying the type of entity	
 	3		Unknown	
Must Use	NM108	66	Identification Code Qualifier	X		ID 1/2	
	Code designating the system/method of code structure used for Identification Code (67)	
 	32		Assigned by Property Operator	
	Meter Number	
Must Use	NM109	67	Identification Code	X		AN 2/80	
	Code identifying a party or other code	
	"ALL" - for ALL meters
Meter Number
"UNMETERED" - for Unmetered Services	

	Segment:	REF Reference Identification (Supplier Rate Code)
	Position:	130
	Loop:	NM1        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		Energy Services Request (LIN05 = CE): Required for Rate Ready Consolidated Billing, otherwise Not Used.
Historical Usage Request (LIN05 = HU): Not Used
Historical Interval Usage Request (LIN05 = HI): Not Used
Interval Status Request (LIN05 = SI): Not Used	
		REF~RB~RATE39	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	RB		Rate code number	
	Supplier Rate Code	
Must Use	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	Supplier Rate Code	

	Segment:	REF Reference Identification (Utility Rate Class)
	Position:	130
	Loop:	NM1        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To specify identifying information
	Syntax Notes:	1	At least one of REF02 or REF03 is required.
		2	If either C04003 or C04004 is present, then the other is required.
		3	If either C04005 or C04006 is present, then the other is required.
	Semantic Notes:	1	REF04 contains data relating to the value cited in REF02.
	Comments:
Notes:		Energy Services Request (LIN05 = CE): Optional - May be required by Applicable Regulatory Authority
Historical Usage Request (LIN05 = HU): Not Used
Historical Interval Usage Request (LIN05 = HI): Not Used
Interval Status Request (LIN05 = SI): Not Used	
		REF~NH~RES01	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	REF01	128	Reference Identification Qualifier	M		ID 2/3	
	Code qualifying the Reference Identification	
 	NH		Rate Card Number	
	Distribution Company Rate Code	
Must Use	REF02	127	Reference Identification	X		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	Distribution Company Rate Code	

	Segment:	SE Transaction Set Trailer
	Position:	150
	Loop:
	Level:	Detail
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
	Syntax Notes:
	Semantic Notes:
	Comments:	1	SE is the last segment of each transaction set.
Notes:		Required	
		SE~13~000000001	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
Must Use	SE01	96	Number of Included Segments	M		N0 1/10	
	Total number of segments included in a transaction set including ST and SE segments	
Must Use	SE02	329	Transaction Set Control Number	M		AN 4/9	
	Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set