<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>On the Development of a Pipeline for Processing Hydrometeorological Data</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Evgenii D. Viazilov</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Denis A. Melnikov</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alexander S. Mikheev</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>RIHMI-WDC.</institution>
          <addr-line>6, Koroleva St., 249035 Obninsk</addr-line>
          ,
          <country country="RU">Russia</country>
        </aff>
      </contrib-group>
      <fpage>110</fpage>
      <lpage>119</lpage>
      <abstract>
        <p>For the first time in worldwide for hydrometeorology, data processing pipeline is proposed. Approaches to its implementation are defined. The stages and software for such processing are highlighted. The main method of the universal data replenishment mechanism with the results of the pipeline is an integrated database with a wide set of metadata. The creation of information products at various stages of the pipeline is considered. It is proposed to create new services for the pipeline. The main control mechanism for pipeline data processing is considered to be tools of monitoring the state of hardware, software and information resources. This requires a transition from monitoring individual stages to automatic comprehensive monitoring of the data processing pipeline state. Tasks of the administrator of the data processing pipeline are defined. In fact, when using pipeline processing, a transition must be made to fully automatic data processing without human intervention.</p>
      </abstract>
      <kwd-group>
        <kwd>Pipeline Data Processing</kwd>
        <kwd>Automatic Processes</kwd>
        <kwd>Data Integration</kwd>
        <kwd>Information Products</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Two streams of data are in the field of hydrometeorology. First - the data is received
in real time via the Global Telecommunication System of the World Meteorological
Organization. Streaming data is continuously generated by thousands of data sources,
which send telegrams with weather messages simultaneously and in small amounts
(several kilobytes). Telegrams are processed and on their basis weather forecasts are
issued. Real time data is three-hour cycles, but the load is distributed over the main
time of observation and it turns out to be uniform and predictable. The second stream
of data is beginning 30 days after the end of the previous month. For some
hydrometeorological stations, data are received with a delay from a month to a year,
depending on stations hard inaccessibility. In this stream any part of the data can
process and recalculating as needed. To obtain annual information on climate change,
it is necessary to process data and analyzes changes for the previous year within three
months after the end of the year. Most of day-to-day operations associated with
different software maintenance remain the prerogative of personnel. These are
associated with significant material costs. The low level of automation of day-to-day
operations is becoming a serious obstacle to improving the efficiency of existing
systems.</p>
      <p>
        In recent years, digitalization and digital transformation have been gaining
momentum [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Digitalization is the introduction of digital technologies at all stages of
data processing. Digital transformation is a complex automatization of data processing
from their collection to decision-making in business processes in the form of a
continuous data processing pipelining. The digital transformation is aimed at
increasing the automation level of data management and the efficiency of their use.
      </p>
      <p>A pipeline is a method of organizing calculations used for processing of stream
data in order to fully automate this processing and perform several operations
simultaneously at different stages of the pipeline. For this it is necessary to move from
a loosely coupled set of applications to the creation of an integrated control system for
all stages of data processing. A pipeline requires optimization of existing software,
reducing its complexity and increasing manageability.</p>
      <p>
        Ideas of self-governing systems in information technologies are expressing for a
long time, and movement in this direction is observing on. A pipeline data processing
is using for next directions [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]:
 Operation systems the UNIX family. In Unix-like operating systems a pipeline
is a mechanism for inter-process interaction on the base of data streams.
 Development of software. Here a pipeline consists of a chain of processing
elements (processes, threads, routines, functions, etc.), arranged so that the
output of each element is the input for the next.
 Performing regular operations for moving and processing data in the Amazon
cloud [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        Currently, term the pipeline has become often used in data processing, for
example, to organize a chain of processes for converting source data processing
scenarios into 2D and 3D representations [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], monitoring sales processes, projects
execution [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], other fields [
        <xref ref-type="bibr" rid="ref6 ref7">6, 7</xref>
        ]. In [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], the term "pipeline" is not used directly, but in
fact, the "fully automatic launch of necessary tasks" of consumers is considered when
processing a huge volume of operational remote sensing data.
      </p>
      <p>
        Roshydromet has examples of "end-to-end" digital technologies. For example, in
the Hydrometeocentre of Russia [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] there is a "pipeline" for decoding real-time data,
assimilation, interpolation into grid points to obtain analyses and forecasts. The same
decisions have in others world meteorological centers. The Russian Research Institute
of Hydrometeorological Information - World Data Center has developed the
technology for automatic data integration, which includes such steps as metadata
description of a data provider, delivering metadata and data to the integration server,
uploading them to an integrated database (IBD), building of cartographic layers, data
visualizing on the portal and providing it to consumers. All these stages of data
processing (except for the metadata description) are carried out without the
participation of personnel.
      </p>
      <p>
        The main components of the data processing pipeline are [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]:
 Data integration tools as a basis for their using.
 Organization of the workflow based on established rules, according to which
processing results are automatically delivered to certain services.
 Providing data processing in the form of a sequence of operations for receiving
information products.
 Monitoring of the execution of all data processing stages.
      </p>
      <p>
        To improve the efficiency of data management it needs to integrate their. External
data requires increased information about their origin, especially about processes by
which they were created. Integrated data becomes easily discoverable and available in
online [
        <xref ref-type="bibr" rid="ref11 ref12">11, 12</xref>
        ]. With the development of pipeline data processing must use data
integration tools, software robots, machine-to-machine data exchange methods, cloud
technologies, micro service architecture.
      </p>
      <p>A pipeline processing robotization consists in automating such massive processing
stages as data replenishment and subsequent ordering with data control according to
specified rules. Rules of processing create and storage in the form of a knowledge
base that allows moving to a new stage of data processing or return to the previous
stage if there is a failure of software.</p>
      <p>
        Now cloud technologies are actively developing, which provide not only data
storage services, but also dedicated software and hardware resources for their
processing. Micro services architecture [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] gives a new impetus to the organization
of software, including for pipelining data processing.
      </p>
      <p>The organization of continuous data processing and hydrometeorological support
(GMS) of consumers observed, aggregated, forecasted and climatic information is in
fact the implementation of a new paradigm of digital transformation. To organize such
a GMS, it is necessary to create a computational pipeline for continuous processing of
hydrometeorological data. The purpose of developing a pipeline for processing of
hydrometeorological data is to increase the efficiency of processing incoming
heterogeneous and distributed data. The objective of the research are determination of
approaches for the implementation of pipeline processing of data (definition of stages
and software for such processing, organizing data storage and processing, obtaining of
information products, delivery of data and information to consumers, monitoring of
the pipeline).</p>
    </sec>
    <sec id="sec-2">
      <title>2 Approaches for Implementing</title>
    </sec>
    <sec id="sec-3">
      <title>Hydrometeorological Data Processing</title>
      <p>2.1</p>
      <sec id="sec-3-1">
        <title>Stages of Data Processing in Pipeline</title>
        <p>a</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Pipeline for</title>
      <p>Highlighted stages of data processing on the example in oceanography are showing in
Fig. 1 and include:
 Collecting data from observation platforms.
 Inverting of observed data - presentation in a different order in relation to
observed data in the form, for example, time series.
 Quality control of received data.
 Interpolation of observed data in time (time series) and or space (points of a
regular grid), which are widely used for aggregation and obtaining various
statistical characteristics.
Buoys</p>
      <p>Ships of voluntary</p>
      <p>observatins</p>
      <p>Select
Dates of reaching
thresholds</p>
      <p>Research
vessels
Select</p>
      <p>Join
Interpolation for time</p>
      <p>Spatial ordering</p>
      <p>Inverted data sets
Filtering and
anti</p>
      <p>aliasing
Calculation of the annual
variation in parameter</p>
      <p>values</p>
      <p>Forecast at a point
Calculation of probability,
repeatability
Calculation of
correlation and
spectral functions
Approximation of
correlation and
spectral functions</p>
      <p>Interpolation for vertical on</p>
      <p>standard horizons
Calculating of hydrophysical</p>
      <p>parameters
Calculation of basic statistical</p>
      <p>moments with check for
stationarity and normality of</p>
      <p>distribution
Ordering by space and time
Calculation of direction and
velocity of current by the
dynamic method in grid points</p>
      <p>Classification of fields of
synoptic type
Spatial forecast</p>
      <p>Decision support
Extreme values and
dates of manifestation</p>
      <p>Spatial interpolation to grid
points</p>
      <p>Coastal
stations</p>
      <p>Select
Data sets for</p>
      <p>disciplin
Sound channel
characteristics</p>
      <p>Classification of
vertical distribution of</p>
      <p>parameters
Calculation of the
parameters of the</p>
      <p>upper
quasihomogeneous layer</p>
      <p>Statistical
characteristics
Classification of
water masses
Characteristics of
macro regions
Typical fields</p>
      <p>Grid data</p>
      <p>
        Metadata
• Identifying anomalies or assessment exceeding of the threshold values of
observed parameters and assigning of dangerous levels.
• Information delivery to consumers using the Short Message Service (SMS).
• Forecast of impacts and issue of recommendations in case of parameters
dangerous levels.
• Monitoring of all stages of data processing [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ].
      </p>
      <p>Stages of hydrometeorological data processing, regulations for their work, metrics
values and tools of implementation are presented in Table 1.</p>
      <p>iIdmemnteifdiicaatteiloynafter 3 min after detection SMS</p>
      <sec id="sec-4-1">
        <title>1.5 Data visualization</title>
      </sec>
      <sec id="sec-4-2">
        <title>Of necessity</title>
        <p>Forecast of impacts, give out of Immediately upon r3emceiinvui ntegsianfftoerrmation Support
Decision
1.6 recommendations receipt</p>
      </sec>
      <sec id="sec-4-3">
        <title>2.1 Cataloging, storage of data</title>
      </sec>
      <sec id="sec-4-4">
        <title>Annually</title>
        <p>2.2 tJiomine,, ivnevretirctianl,gs,pinatceerpolation in</p>
      </sec>
      <sec id="sec-4-5">
        <title>Data becomes</title>
        <p>accessible</p>
        <p>Obtaining climatic
2.3 generalization</p>
      </sec>
      <sec id="sec-4-6">
        <title>Annually</title>
        <p>
          Pipeline of data processing is based on the elimination of manual operations for
searching, preparing for processing, and delivery data from one stage to another,
automatic preparation of metadata and loading of created, or replenished, or updated
inverted, calculated, generalized and of climatic data into integrated data base (IDB).
For the pipeline processing data following tools are required [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]:
• Monitoring of data receiving from different sources.
• Decoding of telegrams and data bases creation of real time.
• Integration of real time and deferred data.
• Data storage in IDB.
• Data management, including metadata.
• Obtaining information products at various stages of data processing.
• Delivering of information about the disaster using SMS.
• Visualization of metadata and data.
• Decision-making support.
• Managing of services connecting all processes together, organizing multi-stage
data processing.
• Monitoring the state of the pipeline of data processing.
        </p>
        <p>
          Automatic data processing is as follows. After the new piece of data arrives, a
trigger starts the data decoding procedure. Further, after decoding is completed, the
second trigger starts the next stage of processing – data loading into IDB and etc.
calculation, interpolation, and detection of anomalies. To obtain aggregated
information, the data undergoes multi-stage processing - merging separate pieces of
data from various disciplinary data sets, ordering and interpolating in time or space,
obtaining calculated new parameters, statistics, etc. An important point of such a
pipeline is that results of almost all processing operations are saved for use in various
applied tasks, for example, to calculate various properties of the atmosphere and
hydrosphere (characteristics of the sound channel, statistical characteristics, annual
variations, etc.). Saving inverted and calculated data sets is technologically expedient
and economically beneficial, since the cost of creating them each time a query is
executed is much more expensive than them creating, saving and reusing [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. When
implementing pipeline, following requirements must met:
• New sources of data are included in the processing as needed.
• Full automation of data processing is carrying out up to the creation of an
autonomous data processing system.
• Universal mechanism of IDB replenishment is used.
• All creating datasets should have pre-prepared metadata, while several
attributes (for example, the date of observations end and the geographic area)
are changed automatically when data replenishment.
• Various information products are automatically created, which should be
delivery to specific consumes by a personalized subscription to it.
• Scheme for connecting new data and applications (services) is open for their
inclusion in the pipeline data processing.
• New services are configured for creating of different information products
types, for any geographic area, parameters, and scales of data aggregation.
• Execution of all stages of data processing is constantly monitored and in case
of indicating failures the process is repeated.
2.2
        </p>
        <sec id="sec-4-6-1">
          <title>Data Integration</title>
          <p>The pipeline of data processing is based on their integration. Data integration can
produce in two ways. The first - is data description using metadata, regular data
delivery, and transformation of structures, casting from local names and codes to
system-wide, data loading into IDB. The second method of data integration allows,
based on previously created application programming interfaces (API), web services
or Representational State Transfer (REST) services, to form data tables in real time to
include in the existing processing scheme. This ensures that all required data sources
are connected in a timely manner. This approach hides the location and format of the
data from consumers. At the same time, the data is not moved to a centralized storage,
but remains in the same place where it was created or stored. Each data provider is
responsible for its accessible, security, completeness, quality and relevance of data.
Integrated data must be structured, well described, understandable, easy to use. They
are obtained through transparent, known transformations, so that can trace all the way
from data source to consumers. An example of such data integration has in Unified
system of information for World Ocean (ESIMO)1.
2.3</p>
        </sec>
        <sec id="sec-4-6-2">
          <title>Obtaining of Information Products</title>
          <p>The scheme for obtaining and using of information products based on pipeline data
processing, shown in Fig. 2. Consumers browse products catalog, available for
distribution by tools of access to distributed data.</p>
          <p>,
tssenym iton Application funcatbioounts:dvisiasssuutaeblrisszc,ardtiipaottniao,dnde,eldtievecectriisyoi,onfnoorsfeudcpiapssaotssrt,tearns,aglyetnicesr,ation of warnings
ittirso iitcan Data catalog - metadata: data retrieval (point, profile, mesh, object files)
a f
reg ,ied
iifend itizaon Universal access to data: applicamtioanpss,eSrQviLce,sAPI, web services, REST services,
:U ro
itry tauh Integrated data from external sources and processing results: observations,
ceu forecasts, climate (relational DBMSs,tdaatitoanfsr)om cloud storage, automatic weather
S
Fig. 2. Scheme of information products obtaining and using.
2.4</p>
        </sec>
        <sec id="sec-4-6-3">
          <title>Configuring Applications Interface Requirements</title>
          <p>To organize the operation of the pipeline, it is necessary to have a tool for a simple
quick setting of requirements for the interfaces of services, applications with
information products. Interfaces must allow customizing data requirements (sources,
regions, parameters, presentation forms - data tables, maps of observed and or
predicted data, climate information, time series graphs). This will leads to better
scalability of applications, more efficient use of computing resources. Need to manage
product creation workflows, his distribution and respond more quickly to detected
disasters. The customization interface includes features to help consumers manage
their data requirements. A pipeline must include information product requirements
editor and tool of workflow management of product creation.</p>
        </sec>
      </sec>
      <sec id="sec-4-7">
        <title>1 http://esimo.ru</title>
        <p>2.5</p>
        <sec id="sec-4-7-1">
          <title>Monitoring of the State of Data Processing Pipeline</title>
          <p>To organize monitoring of the data processing pipeline, in addition to monitoring
individual stages of processing, testing and restoration of individual complexes, it is
planned to create an automatic monitoring of the state and operability of the entire
pipeline. It is important to include the ability to automatically run tests, data quality
check and metadata descriptions. It is necessary to receive proactive information about
incidents in the execution of data processing stages so that the system can
automatically take corrective actions. All incidents should be recorded. The protocol
must contain information about at what stage of processing the incident occurred, for
what reason and what was done by the system in this situation. With the help of
monitoring, can accumulate statistics on stages of data processing and find bottlenecks
for their subsequent optimization. In this case, tasks of the pipeline administrator are
following:
 Analysis of data processing - reasons for the slowdown.
 Violation of the service level agreement (SLA).
 Investigation of SLA violations.
 Quick setup of monitoring operations for new objects.
 Calculation of the number of consumers and indicators of GMS.
 Assessment of indicators of state of data processing stages in time.
 Coordination of management of events occurring on the data processing
pipeline.
3</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Discussions</title>
      <p>If in the old paradigm of data processing the sources of information were separate data
sets and databases, then in the new paradigm with the help of metadata a whole data
domain is opened, representing results of observations and their processing, including
forecasts, and climatic data. When using a new paradigm that uses pipelining data
processing, it is possible not only to obtain information products from any stage of
processing, but also to connect them to existing models of calculations, analyzes and
forecasts. Thus, it becomes possible to set tasks for the system such as exporting data,
preparing them for use in models, describing expected results of data processing. At
the same time, the consumer does not need to worry about how to export data for his
task. Everything that is the result of pipelining data processing is loaded into the IDB.
In the ideal scenario of using data, any consumer, without the intervention of
specialists, can find the necessary data, get it up-to-date and test the hypothesis of its
use. In the future, the selected technology for obtaining and using data is included in
the automatic service of this consumer.</p>
      <p>
        In this case, there is a transition to autonomous data processing. APIs, web
services, REST services are the foundation of this automation. With the help of them
can automatically receive data from integrated, distributed sources, which present
responsible for authors from many organizations. When integrating data into ESIMO
[
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], multi-stage data processing has already been implemented. The software is
restored automatically. Data providers are responsible for data relevance and ensuring
data availability. Monitoring the relevance of the data for making a decision is an
organizationally complex process. Relevance of data is assessed on the basis of a daily
automatic check of the frequency of information updates in comparison with the value
of this indicator, specified in metadata description. If the data is submitted late on the
web-portal, it is necessary to identify at which stage a failure occurred (as a result, the
stage is not completed) or where a processing time increased. If the monitoring system
detects that the data is not available online, then it is necessary to check the operation
of the server on which the data is located, the network operation. The database
operation is evaluated the monitoring tool, based on an automated check of every five
minutes.
      </p>
      <p>Modern hydrometeorological support should be personalized, easily customizable
for new types of products, new rules for identifying disasters. It is necessary to
implement methods of fast deliver of data, which necessary for heads of enterprises.
The personalization is configured starting from the preparation of information
products and ending with its use in decision-making. To do this, it is necessary to
identify individual characteristics of each consumer, fixing his "digital footprints"
completed requests on data, used business processes that depend on the
hydrometeorological situation, existing experience in using data, location, and current
situation at the enterprise.
4</p>
    </sec>
    <sec id="sec-6">
      <title>Conclusions</title>
      <p>For the first time in worldwide for hydrometeorology, it is proposed to organize the
end to end pipeline of data processing from observation to decision making. Such data
processing is a natural stage in the development of applied tasks. As a result of the
implementation of pipeline data processing, it will become possible:
• Expanding the composition of integrated data from various sources.
• Realization of preliminary data processing and creation of inverted and
calculated data sets automatically.
• Automatically preparing regular information products and analyze data.
• Using of various methods of data processing (interpolation, aggregation,
statistical processing, correlation analysis, etc.).
• Automatic transmission of detected anomalies or exceeding of threshold values
to consumers.
• To issue forecasts of impacts and recommendations for decision-making.</p>
      <p>A data processing pipelining is especially important for disasters risk reduction,
climate change mitigation, and disaster adaptation. In this case, a universal mechanism
for the preparation of indicators for various disasters are created on the basis of
climatic, forecast and observed data, which should also be delivered automatically to
enterprises heads.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Viazilov</surname>
          </string-name>
          , E.D.:
          <article-title>Digital transformation of hydrometeorological support for consumers</article-title>
          .
          <source>Obninsk, RIHMI-WDC</source>
          ,
          <volume>450</volume>
          (
          <year>2021</year>
          ). In publishing.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Samarev</surname>
            ,
            <given-names>R.S.</given-names>
          </string-name>
          :
          <article-title>Review the state of the pipelining data processing area</article-title>
          . Proceedings V.P.
          <article-title>Ivannikov Institute for System Programming of Russian Academy of Sciences</article-title>
          , vol.
          <volume>29</volume>
          , no.
          <issue>1</issue>
          ,
          <fpage>231</fpage>
          -
          <lpage>260</lpage>
          (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <article-title>3. Questions and answers about the AWS Data Pipeline</article-title>
          , https://aws.amazon.com/ru/datapipeline/faqs/,
          <source>last accessed</source>
          <year>2021</year>
          /07/27.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>Sales</given-names>
            <surname>Pipeline</surname>
          </string-name>
          <article-title>: how to use it in a CRM system</article-title>
          , https://activesalesgroup.ru/pajplajnprodazh/,
          <source>last accessed</source>
          <year>2021</year>
          /07/27.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Rodchenko</surname>
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>Pipeline of projects</article-title>
          , https://storedigital.ru/it-dict/pajplajn/,
          <source>last accessed</source>
          <year>2021</year>
          /07/27.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>What</given-names>
            <surname>Is</surname>
          </string-name>
          <article-title>a Data Pipeline? https://hazelcast</article-title>
          .com/glossary/data-pipeline/,
          <source>last accessed</source>
          <year>2021</year>
          /07/27.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Branowski</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Belloum</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <article-title>Cookery: A Framework for creating data processing pipeline using online services</article-title>
          .
          <source>14th International Conference on e-Science. IEEE Computer Society</source>
          . The Netherlands. Amsterdam, University of Amsterdam, 368-
          <fpage>369</fpage>
          (
          <year>2018</year>
          ), https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&amp;arnumber=8588721, last accessed
          <year>2021</year>
          /07/27.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Aleksanin</surname>
            ,
            <given-names>A. I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aleksanina</surname>
            ,
            <given-names>M.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Babyak</surname>
            ,
            <given-names>P.V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Eremenko</surname>
            ,
            <given-names>V.S.:</given-names>
          </string-name>
          <article-title>Integration of satellite data and service providers</article-title>
          .
          <source>Proceedings “Current Problems in Remote Sensing of the Earth from Space”</source>
          , vol.
          <volume>16</volume>
          . №
          <volume>3</volume>
          ,
          <fpage>288</fpage>
          -
          <lpage>300</lpage>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Stepanov</surname>
            ,
            <given-names>Yu.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhabina</surname>
            ,
            <given-names>I.I.</given-names>
          </string-name>
          :
          <article-title>ASOOI-XEON4 is a multi-machine operational automated technology of the State Institution "Hydrometeorological Center of Russia", designed for information support, regulated counting and the formation of products of various predictive models</article-title>
          .
          <source>Collection of articles "80 years of the Hydrometeorological Center of Russia"</source>
          ,
          <fpage>435</fpage>
          -
          <lpage>452</lpage>
          (
          <year>2010</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <article-title>The pipeline of IT services</article-title>
          .
          <source>Journal “Open Systems. DBMS"</source>
          , no.
          <issue>07</issue>
          , (
          <year>2008</year>
          ), https://www.osp.ru/os/2008/07/5478483, last accessed
          <year>2021</year>
          /07/27.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Viazilov</surname>
          </string-name>
          , E.D,
          <string-name>
            <surname>Lamanov</surname>
            ,
            <given-names>V.I.</given-names>
          </string-name>
          :
          <article-title>On the creation of computational arrays of oceanographic data</article-title>
          .
          <source>Gidrometeoizdat, Proceedings of RIHMI-WDC, no. 128</source>
          ,
          <fpage>3</fpage>
          -
          <lpage>13</lpage>
          (
          <year>1985</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Vyazilov</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Melnikov</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mikheev</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>New Approaches for Delivery of Data and Information Products to Consumers and External Systems in the Field of Hydrometeorology</article-title>
          .
          <source>In: Supplementary Proceedings of the XXII International Conference on Data Analytics and Management in Data Intensive Domains (DAMDID/RCDL</source>
          <year>2020</year>
          ). Voronezh, Russia,
          <source>October 13-16</source>
          ,
          <fpage>182</fpage>
          -
          <lpage>194</lpage>
          (
          <year>2020</year>
          ). http://ceur-ws.org/Vol2790/paper17.pdf,
          <source>last accessed</source>
          <year>2021</year>
          /07/27.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Richardson</surname>
          </string-name>
          , Chris: Microservices.
          <article-title>Development and refactoring patterns</article-title>
          . Peter, SPb.,
          <volume>544</volume>
          (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Zabbix</surname>
          </string-name>
          , https://www.zabbix.com/,
          <source>last accessed</source>
          <year>2021</year>
          /07/27.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Viazilov</surname>
          </string-name>
          , E.D.:
          <article-title>Creation and use of databases</article-title>
          . Palmarium Academic Publishing, Germany.
          <volume>545</volume>
          (
          <year>2018</year>
          ).
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>