Staff blog: EMS Data Integration al dente.

It is a rare chance that we can compare the joy of fine cuisine to the rawness and relevance of data in our EMS. How can the culinary art of a top hat restaurant be linked to data integration in the EMS? Well, aside from the fact that it is too close to lunch and I am hungry, the two concepts aren’t too distant from each other.

17.11.2013 ZDJECIA WIZERUNKOWE DLA RESTAURACJI BURGER KITCHEN TOMKA WOZNIAKA , FOT. MARCIN KLABAN

Let’s see… restaurants must cater for their hungry customers. Dumping raw produce on a plate and presenting it to them simply won’t cut it. So, the kitchen must clean and prep the produce, add a combination of sauces, spices and herbs, apply heat and eventually present a meal worthy to the paying customer. Produce arrives from a supplier to the back door and the kitchen will convert that produce into something palatable for the customer at the front of the restaurant.

splunk-logo-2-300x173

Data integration follows the same paradigm. Think of the EMS as the kitchen, data providers as the suppliers and users as the paying customers. So, users make requests to the EMS for information. The EMS requests raw data from various data providers and will aggregate, sort, filter and deliver a result set to the user. Splunk is an example of a data provider, which offers an extensive and powerful service for gathering, collating and filtering vast amounts of raw data. From the user, the EMS can collect information such as their identity and their location, and with that (and more)  the EMS (i.e. kitchen) can craft a tailored query to search that raw data in Splunk (i.e. supplier).  From then, contextually relevant information can be fed back and presented to the user (i.e. paying customer)  in a palatable format.
…mmm saucey data.

Image source: (x) (x)

 

CONTACT US

[contact-form-7 404 "Not Found"]

Simon Galanakis

Solution Design and Senior Developer
Appearition
Simon Galanakis