50 likes | 174 Views
Task Force API Accounting Process Implementation. File name convention for ENTSO-E CE Accounting and Settlement process V1.0, 20.8.2010.
E N D
Task Force APIAccounting Process Implementation File name convention for ENTSO-E CE Accounting and Settlement process V1.0, 20.8.2010
The recommendation is to have standard file-names for the data messages. The name should contain Area Y EIC codes of concerned SO, business day, label of document, version and time stamp in acknowledgment document. When the message is created it should get the actual time stamp in UTC time File name convention August 21, 2014 3
SOMA yyyymmdd_SOMA_EIC-Y-Area1_EIC-Y-Area2_vvv.xml SOVM yyyymmdd_SOVM_EIC-Y-Area1_EIC-Y-Area2_vvv.xml SOAM yyyymmdd_SOAM_EIC-Y-Area1_EIC-Y-Area2_vvv.xml SOVA yyyymmdd_SOVA_EIC-Y-Area1_EIC-Y-Area2_vvv.xml CBSR d. yyyymmdd_CBSRd_EIC-Y-CC_EIC-Y-CB_vvv.xml CBSR w. yyyymmdd_CBSRw_EIC-Y-CC_EIC-Y-CB_vvv.xml (Note: date = first day of Recording period) CASR d. yyyymmdd_CASRd_EIC-Y-CB_EIC-Y-CA_vvv.xml CASR w. yyyymmdd_CASRw_EIC-Y-CB_EIC-Y-CA_vvv.xml (Note: date = first day of Recording period) CC = Coordination Centre, CB = Control Block, CA = Control Area yyyy = Year, mm = Month, dd = Day File name convention August 21, 2014 4
yyyymmdd_type_ EIC-Y-SO1_EIC-Y-SO2_vvv_ACK_time stamp.xml Where yyyymmdd_type_ EIC-Y-SO1_EIC-Y-SO2_vvv = SOMA, SOVM and SOAM source files. Time_stamp = Date and time when ACK was generated = yyyy-mm-ddThh-mm-ssZ With yyyy = Year mm = Month dd = Day T = T hh = Hour mm = Minute ss = Second Z = Z Note: Per definition there is no ACK on the messages SOVA, CBSR and CASR because these documents should be provided on the publication frame work. However currently there is no publication frame work available, hence data are provided to CC, CB, CA and other way around. In this case is makes sense to have an ACK also on this documents. File name convention for ACK August 21, 2014 5