Data Historians in the Data Management Landscape

  • Brice Chardin
  • Jean-Marc Lacombe
  • Jean-Marc Petit
Part of the Lecture Notes in Computer Science book series (LNCS, volume 7755)


At EDF, a leading energy company, process data produced in power stations are archived both to comply with legal archiving requirements and to perform various analysis applications. Such data consist of timestamped measurements, retrieved for the most part from process data acquisition systems. After archival, past and current values are used for various applications, including device monitoring, maintenance assistance, decision support, statistics publication, etc.

Large amounts of data are generated in these power stations, and aggregated in soft real-time – without operational deadlines – at the plant level by local servers. For this long-term data archiving, EDF relies on data historians – like InfoPlus.21, PI or Wonderware Historian – for years. This is also true for other energy companies worldwide and, in general, industry based on automated processes.

In this paper, we aim at answering a simple, yet not so easy, question: how can data historians be placed in the data management landscape, from classical RDBMSs to NoSQL systems? To answer this question, we first give an overview of data historians, then discuss benchmarking these particular systems. Although many benchmarks are defined for conventional database management systems, none of them are appropriate for data historians. To establish a first objective basis for comparison, we therefore propose a simple benchmark inspired by EDF use cases, and give experimental results for data historians and DBMSs.


Data Historian Data Management System Range Query Programmable Logic Controller Continuous Query 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Arasu, A., Babcock, B., Babu, S., Datar, M., Ito, K., Motwani, R., Nishizawa, I., Srivastava, U., Thomas, D., Varma, R., Widom, J.: STREAM: The Stanford Stream Data Manager. IEEE Data Engineering Bulletin 26(1), 19–26 (2003)Google Scholar
  2. 2.
    Arasu, A., Cherniack, M., Galvez, E., Maier, D., Maskey, A.S., Ryvkina, E., Stonebraker, M., Tibbetts, R.: Linear Road: A Stream Data Management Benchmark. In: VLDB 2004: Proceedings of the Thirtieth International Conference on Very Large Data Bases, pp. 480–491 (2004)Google Scholar
  3. 3.
    Aspen Technology. Database Developer’s Manual (2007)Google Scholar
  4. 4.
    Golab, L., Johnson, T.: Consistency in a Stream Warehouse. In: CIDR 2011: Proceedings of the Fifth Biennial Conference on Innovative Data Systems Research, pp. 114–122 (2011)Google Scholar
  5. 5.
    Invensys Systems. Wonderware Historian 9.0 High-Performance Historian Database and Information Server (2007)Google Scholar
  6. 6.
    Olson, M.A., Bostic, K., Seltzer, M.I.: Berkeley DB. In: Proceedings of the FREENIX Track: 1999 USENIX Annual Technical Conference, pp. 183–191 (1999)Google Scholar
  7. 7.
    OPC Foundation. Data Access Custom Interface Standard (2003)Google Scholar
  8. 8.
    OSIsoft. PI Server System Management Guide (2009)Google Scholar
  9. 9.
    Transaction Processing Performance Council. TPC Benchmark C Standard Specification (2007)Google Scholar
  10. 10.
    Transaction Processing Performance Council. TPC Benchmark H Standard Specification (2008)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Brice Chardin
    • 1
    • 2
  • Jean-Marc Lacombe
    • 1
  • Jean-Marc Petit
    • 2
  1. 1.EDF R&DFrance
  2. 2.Université de Lyon, CNRS, INSA-Lyon, LIRIS, UMR5205France

Personalised recommendations