I assume that the 15 ft perimeter zone depth used in energy analysis is so that the interior heat gains do not cancel out the envelope heat losses in winter (when it is say -40 outside). Design loads programs are not affected since interior heat gains are not deducted from the heat losses. Office Building Envelopes are being designed to have up to 90% glass. The glass can be from the bottom of the floor slab to the underside of the next floor slab. The ceiling depth next to the glass is zero and it slopes down to about 3 feet 2 to 5 feet away from the glass. Day-lighting can now reach 25 ft away from the glass. Also, when you turn the day-lighting option on, the lighting load goes down and the heating load goes up.
Can energy analysis programs have perimeter zone depths of up to 25 ft or equal to the depth of the actual perimeter space (rarely will it be less than 10 ft and could go up to the core zone) for day-lighting and set another zone depth of 2 to 5 ft for heating?
In DOE2.1E I used the following to define the Utility Type for district steam specified per 1000 lbs & CHW per Ton-Hour.

ENERGY-RESOURCE $ EST = 220, LST = 210, 975 btu/lb $
RESOURCE = DISTRICT-STEAM UNIT-NAME = K-LBS/HR DEM-UNIT-NAME = K-LBS/
SOURCE-SITE-EFF = .60 ENERGY/UNIT = 975000 ..

ENERGY-RESOURCE
RESOURCE = DISTRICT-CHW UNIT-NAME = TONS DEM-UNIT-NAME = TON-HRS
SOURCE-SITE-EFF = .90 ENERGY/UNIT = 12000 ..

In DOE2.2 it is UNIT-INDEX and DEM-UNIT-INDEX and the defaults are 50 and 34 for both. In eQUEST they are called "Energy Billing Units Label" and "Demand Billing Units Label". How do I specify the Units since the Utility Rate Units in different parts of the US and world vary?
DOE2.2 does not appear to have the DOE2.1E Commands and Keywords for SPACE-CONDITIONS, ZONE-CONTROL and SYSTEM-CONTROL. I have used this in DOE2.1E to set up ?Design Criteria? for different types of Spaces (based on building room types), types of Zones (terminal boxes, etc) and types of Systems (VAVS, PIU, WLHP ? starting with that shown in the DOE2.1E BDL Summary). Templates of this type of information can be transferred from one project to another and edited for the project. It is similar to the TRACE700 Project Library. DOE2.2 has SET-DEFAULT that allows master data for one room, zone and system type.
It is possible that I do not understand the DOE2.2 and eQUEST programs well enough and I have missed something. The 6 DOE2.2 Manuals could do with more examples showing the BDL for modeling PV, GSHP, TES, Load Management, etc. Case studies would show the full picture.