How is the data model logically organized with respect to report DDLs {data definition language} (Data Aggregation, Settlements, Retail, etc)?
Data Aggregation and Settlements data is currently included in one DDL – and can be found in the Settlements DDL posted at http://nodal.ercot.com/readiness/reports/d/index.html. The most current settlements DDL and XSD are available. There are additional extracts that will have their own DDLs outside of those used for shadow settlement (for example, the settlements calendar). The data model is not really logically organized with respect to DDL as a whole. Each DDL represents one extracts set of data. The data per extract is logically organized by table. For instance, all data agg data is in the DAIOUTPUT/AGGOUTPUT/LLSOUTPUT table sets whereas CRR (Congestion Revenue Rights) data is in the CRROUTPUT/CRRAUCTION table sets and settlements data falls into the settlement tables data sets.
Related Questions
- Why can I see some indicator Definitions on the Meta Data screen but the definition information appears in the report that I export/print under Element Name?
- How can I make sure that the Date format on the graph is changed when its format is changed in the Report Data Model Property Inspector?
- Do I report Section G Alternative Schools Accountability Model (ASAM) data for all of my alternative schools?
