FASYS project once again: the Health Continuous Vigilance System

After introducing the FASyS project, and briefing the NOMHAD Application, today we are going to treat the “Health Continuous Vigilance System” itself:

Next figure presents the architecture for the “Health Continuous Vigilance System” developed inside the FASyS project. This system is based on five main parts: Monitoring Module; Response Medical Center; Differential Diagnosis Module; Prevention Plans Module; and Intervention Module. Each of these parts can be influenced by a number of external variables and parameters such as the Electronic Healthcare Record (EHR).

Health Continuous Vigilance System

Given the big amount of generated information in this model, it is necessary to process all the collected data, since such amount of information would not be easily understandable by health professionals. Services and intelligent devices that have been generated will provide a classification of the monitored data. Some data will be set inside a normal range, and others will be out of the settled limits, generating alarms due to this. Furthermore, this classification will help the doctor to organize and evaluate all workers’ data and at the same time it will be able to act more precisely against a particular diagnostic.

Therefore, the Monitoring Module is where is stored all the personal information gathered by the system about the worker himself. All these personal data, obtained from the monitoring, are complemented and improved by variables from several sensors in the factory (collecting temperature or humidity, that is, particular characteristics from the workplaces at which the worker can stay during a work journey), that are joined all together in the Response Medical Center (RMC). The RMC allows to filter and organize the population depending on the changeable rules and on the user role. So, it is in this module where the first amount of data is collected, creating, as a result, personalized records of the workers and establishing alerts which make easier the task of health professionals.

The information stored in the previous module is not enough to make a complete diagnosis. So, data from other sources are needed, such as:

• Data from a medical base of knowledge (it contains relations among diseases, risks, medical tests, medical recommendations, etc).
• Personal data from the health system, which include the previous medical history and it is known as Electronic Healthcare Record (EHR).
• Trend analyzer data. This system is in charge of detecting how some parameters of a person are changing during the pass of time. These parameters can be added to the absolute values in order to get a more complete evaluation of the person.
• Evaluation module results. It can be defined as a “photograph of the person” in a particular moment, with no need to detect a problem.

These four mentioned sources are the subsystems which provide important information to the main blocks. To manage all this information, a Differential Diagnosis Module has been developed (Dr. House influence gets far). This module, through intelligent systems, helps in making decision to health professionals.

The next step is to reach the Prevention Plans Module, where it is defined how to act. The plans to be taken can be of two types: in one hand a medical diagnosis and in the other hand a technical diagnosis, for instance a redesign of the workplace. It is important to remark that these actions are not exclusive. According to this, different levels of action can be established; that is, from very complex levels to more simple levels such as, for example, reminder panels. In addition, the prevention actions carried out in this module can be conducted at three level:

• At the first level, the system reacts automatically. When one of the collected data reaches a condition that the professional wants to be controlled, there is an automatic reaction. This associated reaction can be the activation of an alarm, a protocol in a situation of risk, etc. These automatic reactions are achieved using ECA rules (i.e. Event-Condition-Action rules).
• At the second level, health professionals receive the alerts and then they react in consequence, acting on individual workers. The reaction of professionals can be the assignation of a prevention plan developed before, or the assignation of a prevention plan modified for the worker situation in particular. These ways that define the processes are called workflows. (Note: these workflows will be treated in a more detailed way in next posts).
• The third level is in charge of providing knowledge for the other two levels, improving the protocols, adapting them to new situations and personalizing the recommendations. Innovative intelligent tools are used to manage it.

Finally, the Intervention Module is responsible for performing the particular actuation selected for the problem in question.

How it can be seen in the above figure, the “Health Continuous Vigilance System” is cyclic and works in a continuous fed-back learning way, therefore, after the Intervention Module, it starts again from the Monitoring Module.

Another important aspect to take into account is the personal data privacy. As a consequence of this, only a few people will have access to the EHR (Electronic Healthcare Record), to the personal variables, and to the personal diagnosis.

Finally, to complete a previous post, it should be emphasized that NOMHAD application is used in the Response Medical Center Module; in fact it is the main tool of this module.

A next post will be dedicated to complete the vision of Tissat collaboration on FASyS Project, and we’ll focus on workflows used for prevention protocol implementation, as well as in the use of a “choreographer” to interconnect services, and in the management of PHR (Personal Health Record).

Lego Data Centre … and Walhalla, a European Tier IV DataCenter

Let’s come back for a while to childhood and let’s play with our Legos, this time with a funny new Lego Data Center game:

https://www.youtube.com/v/ekDesN76pQ4?version=3&feature=player_embedded

and now, after this funny time, let’s make business in Walhalla, a Tier IV DataCentre certified by The Uptime Institute and winner of DataCentre Leaders Award in 2010:

Walhalla TIER IV LOGO

Walhalla in Mapa Tier IV

“Europe behind the US on Cloud”, according to Gartner

Yesterday a Santiago Bonet’s twit (@sbonet) advice me about a recent interview (the video is here) to Neelie Kroes, the EU Commissioner for Digital Agenda. In that interview Ms. Kroes states that we are not pleading for an European cloud, but what Europe can offer to the cloud …

EU Commsionner's comments remind me a recent Gartner Report that states Europe is behind the US on cloud Computing.

According to Gartner, while interest in cloud in Europe remains high, the Continent will trail at least two years behind the US (here is the new).

"The opportunities for cloud computing value are valid all over the world, and the same is true for some of the risks and costs," said Paolo Malinverno, vice president at Gartner. "However, some of cloud computing's potential risks and costs – namely security, transparency and integration – which are generally applicable worldwide, take on a different meaning in Europe."

In fact, Gartner has identified four main inhibitors for cloud in Europe over the next few years:

First, the Europe's diverse and ever-changing data privacy regulations inhibit the movement of personal data to the cloud. Indeed, many companies in Europe eschew US cloud service providers for fears of potential conflict between European data protection legislation and the US Patriot Act.

Second, the complexity of business-to-business multi-enterprise integration and processes. Europe's diversity issues are compounded when running common and intrinsically multi-enterprise processes across different countries, claimed Gartner. While European B2B infrastructure providers have turned this complexity to their advantage, diversity makes achieving critical mass more difficult and slows down the execution of players wanting to offer cloud services throughout Europe.

Third, EU policy-making processes and practices can hinder business. Indeed, the legislative process across the EU is slow and the resulting legislation can still vary widely across Europe. E-invoicing is one of the most recent examples of this.

Fourth, the effect on investment of the debt crisis in the eurozone. This has caused major investments to be put on hold, slowing down strategic and game-changing decision-making.

"The bottom line is that the interest in cloud is as high in Europe as it is elsewhere in the world" said David Mitchell Smith, vice-president and a Gartner Fellow. "While these inhibitors will certainly slow down cloud adoption in Europe, they will not stop it – the potential benefits of cloud are too attractive and the interest in its efficiency and agility are too strong to stall it for long."

By the way, Michelle Alexis Cartier started an interesting debate about this subject on LinkedIn with some quite different point of view.

In my opinion, public sector influence in IT business (cloud computing included) is more important in Europe than in USA. So, European Community Administration and the different European Countries Administrations have a bigger role in fostering business around Cloud Computing as users and buyers of services as well as making easy the business around.

In a previous post on my blogs (both http://wp.me/p2cqZY-c6 and http://carloscebrianmartinez.blogspot.com.es/2012/04/first-comments-on-eu-procure-secure.html), I already analyzed the possible impact of “Procure Secure: A guide to monitoring of security service levels in cloud contracts” published on 2012-apr-1 by ENISA (the European Network and Information Security Agency, working for the EU Institutions and Member States). In some way, this guide follows the USA “Federal Risk Assessment Program” (FedRAMP) published in February 2012.

In brief, both reports are based and share similar points. However, besides the different development level of both programmes, in my opinion the main difference is that the USA programme starts with a disrupting event: Cloud First policy that requires USA federal agencies to use cloud-based solutions whenever a secure, reliable, cost-effective cloud option exists. In europe we lack that Cloud Policy, in spite of UK government stepped in that way creating "UK CloudStore", a system designed to make the process of selecting software services simpler and, crucially cheaper for UK public sector procurement officers (see http://wp.me/s2cqZY-550)

As a European IT worker, I think we need a “EU Cloud First Policy” (or something like) to foster the Cloud market both the cloud providers and the cloud consumer companies, as well as the Cloud research & development investments. That won’t be enough, but it’s needed to bring down the 4 barriers that Gartners states cleverly.

FASYS project revisited: the NOMHAD Application

A few days ago we did a brief introduction to FASyS project, Spanish acronym for “Absolutely Safe and Healthy Factory” and, as its name states, it’s an European R&D initiative for improving industrial workers security. Today we are to focus on some aspect of this project, especially on the objectives where Tissat is involved:

Several European statistics confirm that a large number of people have fatal accidents every year in the workplace. For this reason, one of the most important European objectives is to reduce the number of industrial accidents significantly. In fact, one of the European objectives set for 2020 is the 25% reduction in the number of industrial accidents. In order to reduce accidents it is essential to pay attention to the workers, their single workplaces and to their working conditions. In this way, if workers had a safer environment, the number of accidents could be significantly reduced, implying therefore a reduction in costs. Fasys Project, focused on factories of machining and assembly operations, aims to achieve this reduction promoting the use of technologies and giving, at the same time, a principal role to the worker. From now on, the worker, who has represented a neglected element in the factories, will be the center of attention. The increase of his security, and the enhancement of his working conditions and health, will be key elements for the Factory of the Future performance.

For this reason, the future work has to be oriented on new technological applications to get a factory safer and to reduce significantly the number of accidents. To control the accidents it is necessary to anticipate and estimate what can happen. So, prevention is a key point. To manage it, it is important to collect and measure data during a period of time, in order to evaluate their progress. Consequently, the perfect model would be a factory in which the risks and health were controlled at any time. To achieve so, FASyS has different main objectives and one of them (where Tissat is working actively) is to develop a “Health Continuous Vigilance System”. The system includes both the monitoring to characterize workers activity and environment, and aspects related to prevention protocols. To manage it, several systems of collecting data are needed. They can be distributed around the factory and monitor, for example, personal and environment data, or get information, for example, from medical knowledge or previous medical information of the worker. Besides, due to the big amount of generated information (so far a “big data” problem is not reached on the prototype, but it’ll probably appear when moved to more complex environments), intelligent systems for massive data processing are needed. In this way, the information could be easily managed and classified, in order to obtain data from a specific situation that could be required.

Nowadays, the number of sensors for monitoring personal health data is increasing. In addition, sensors that collect environmental parameters in industrial factories are being introduced more and more. The problem encountered so far, and solved in this project, is that these data are not connected. The information is only collected in order to produce isolated diagnosis, but not common results, and the collected data become less relevant if they are not treated together. The final decision, in a dynamic environment like a factory, could be more precise if results came from a study of a diverse set of parameters.

According to FASyS project, the first step to improve the health and safety in factories is to increase the personal and environmental monitored data. Consequently, there is a need to develop a system able to store all this information. So NOMHAD system has been developed.

NOMHAD System

NOMAHD is an application able to stored part of this required information: workers’ personal parameters such as blood pressure, pulse and oxygen saturation. The system performs a prioritization and an intelligent management of alarms. These alarms are based on the rules and protocols accepted by health professionals and by the health system. This service will combine the information, through the prioritized alarm list, with the generation of specific summaries about the state and evolution of the person. This enables a more efficient management of events.

So far, the options managed by NOMHAD are specifically thefollowing:

• To create a patient. The professional will fill the administrative worker data and the medical relevant data for a future evaluation. Patients will also be assigned to health professionals.
• Reception and Display of Monitoring. The system stores the monitoring data of the person. It stores them into a database related to the personal health record in order to be used by health professionals in the future. The monitoring data are displayed in the right way, either in graphical form, numerical, image, etc. The data stored in the system are processed on arrival. A set of several rules, defined by the doctor and adapted to the personal profile, are applied. These rules allow the system to detect potential anomalies found in the data, in order to take decisions. For the definition of the rules, health professionals will have a tool to help themselves with this task.
• To configure alerts. The system will have an alert module that, based on the monitoring data and the limits defined as optimal by a professional, will be able to detect whether the data stored are acceptable or not.
• The possibility of assigning questionnaires. The patient mood could be extracted from these questionnaires. Health professional will choose the questionnaire and will have the possibility to personalize it depending on the needs of each worker in particular. These questionnaires will be available in the future in case the professionals want a subsequent consulting or validations.
• Monitoring. The measurements can be obtained with usual external devices, whose information is introduced afterwards in the system or it can be used integrated elements into the system (controlled, for example, by Bluetooth and transmitting the captured data directly to the system). The design of the system can be extended to introduce new devices.

With the purpose of completing the personal data stored in NOMHAD, FASyS project proposes a connection to the current health system. This connection provides a register about the health state of the person during his lifetime, which collects data such as his diseases, surgically interventions or pains. This health system is commonly known as EHR (Electronic Health Record).

Finally, once the information has been monitored and classified, the next point is focused on the intervention. With the aim of representing prevention protocols for this intervention, workflows are developed. Given the workers singularity, the adaptation of the prevention protocols is needed for each one of them. In this way, the elimination of the occupational hazard is much more effective.

Next day we’ll focus on the architecture of the “Health Continuous Vigilance System”, as well as on the prevention protocol workflows implementation.

Cloud vs. ISO20K & ISO27K …without fighting

In such so fast changing IT sector where everything happens at a frenetic pace and where legislation is going behind innovation, standards and best practices are intended to put some order and concert in the Cloud Computing operations with different success; but are they applicable?, are they useful?, are they suitable?

It is undeniable that the cloud is pulling the industry with determination as well as acceptance by users is increasing, but do ISO20K & ISO27K (and so on) standards fulfill the CloudComputing needs? Are current best practices useful to operate a Cloud?

In other words, should the Cloud adapt to legislation? or should legislation adapt and cover the new Cloud challenges?

These subjects will be discussed next Thursday, 21-june-2012, in Valencia (Spain), in the “Cloud vs. ISO20K & ISO27K …without fighting” meeting (organized by ISACA) to be celebrated at Palacio de la Colomina CEU (s/ Almudín, 1)

http://www.isacavalencia.org/index.php?option=com_content&view=article&id=346:cloud-vs-iso20k-27k-sin-llegar-a-las-manos&catid=8:isaca-valencia

FASyS Project: an European R&D initiative to improve industrial workers security

Now that the FASyS Project is in its last phase and an important milestone, the prototype testing in a living lab (a real factory), is going to be started, I remind that I’ve not written about. So, “its time has come”:

FASyS is the Spanish acronym for “Fábrica Absolutamentte Segura y Saludable”, that means “Absolutely Safe and Healthy Factory”. It’s a project with 40 month duration and a budget of 23.3 M€. It is one of the 18 large Spanish strategic projects supported by the CDTI (Centre for the Development of Industrial Technology) as part of the CENIT 2009 Programme.

With the ambitious goal of improving business competitiveness through new levels of industrial safety and workplace comfort, the FASyS project aims at implementing both the excellence model for integrated occupational health and safety management in the handling, machining and assembly industries, together with a new generation of safety technologies and solutions.

The FASyS project raises the definition of an absolutely safe and healthy factory, and it is structured into 8 sub-projects that are governed by a parallel temporal sequence, in which the maturity of diverse technologies and solutions increases and evolves through the achievement of individual phases:

• SP1 – Scenario, Requirements and Model

SP1 establish the common framework for the entire project FASyS. At SP1, the reference model factory FASyS is defined, and also the scenarios where this model will operate and the architecture that includes the supporting technologies of the implementation of this model.

The FASyS model proposes a new approach in the design, implementation, operation and maintenance of a handling and assembly factory. Facing the traditional models that focus these phases on productivity paradigms to introduce then the health and safety needs of employees, FASyS will define a new model of Sustainable Factory where the employee, his safety, health and welfare ware the central axis in the factory model.

• SP2 – Regulations, Legal, Ethical and Social Aspects

SP2 provides the regulatory, ethical and social frameworks that contextualize the development of technologies. Since the FASyS project aims from a highly monitored scenario, it is important not to forget the ethical and social constraints which also establish a development framework for other technologies in the project. In addition, SP2 develops new business models, thus allowing new players in the system.

FASyS will provide a range of technologies and services that enable a broader vision and rich in the development of security solutions and industrial health.

• SP3 – Sensors and Communications

SP3 is focused on providing communications technologies and the development of (bio)-sensors that will support characterization, monitoring and action services in the context of personalized prevention of FASYS strategies, in order to control not only vital sings of the employees, but as well the conditions of the workstation, including the involved machinery.

SP3 will develop a robust architecture of scalable communication; a development platform for monitoring applications on sensor networks, and it will establish efficient mechanisms for locating objects and people.

• SP4 – Diagnostic Systems and Health Surveillance

SP4 is responsible for the development of new actuation protocols and technologies for the deployment of new personalized systems of diagnostic and continuous health surveillance. To be able of establish and maintain the better health of the employees, it is necessary to process and work with a large amount of data obtained from evaluations, monitoring, censored data, etc. data about the workstation and environment, and data related to the employee’s work profile and background (work, personal, family, health,…), and the medical history, among others.

• SP5 – Risk Detection and Evaluation Techniques

SP5 is intended to define and design the ergonomic, psychosocial and the workplace hygiene risks prevention protocols, and the intelligent mechanisms which will allow the detection of these risks. These new protocols will be supported by a technological platform which will allow a fast and easy deployment of totally contextualized interventions to the worker conditions, the work place and the task to perform.

These contextualized interventions require a high degree of intelligence, for which this SP will focus not only in the definition of the intervention protocols, but also in the development of the semantic description of the context in which they’ll be applied.

• SP6 – Safe Manufacturing Equipment and Processes

SP6 aims at the development of certain capacities related to machine tools which would allow the development of intelligent work safety, well-being and comfort applications and devices. SP6 bases on the need to produce a machine evolution towards an active and cooperative element within the prevention strategies, with the capability to modify its own behaviour to adapt to the environmental and user needs and work in cooperation in an intelligent manner to avoid disasters.

The elimination of risks is foreseen from the machine design. The management of this intelligence and its integration in the global framework of the system are equally parts of the activities of this SP.

• SP7 – Risk Control Platform

SP7 provides those elements necessary to offer intelligence to the environment through the general decision-making from all the information sources generated in all the other FASyS subprojects aiming to control and act over the health and the labour risks linked to the developed tasks while they’re being identified.

The final goal of SP7 is to provide the responsible of work safety with an interface which allows him to establish the most effective means to manage and prevent the existing risks so that those lead the environmental adaptation to the detected situations.

• SP8 – Management and Evaluation Integrated Systems

SP8 has the final goal of designing and defining all those tests which will allow the validation of the proper functionality of the technologies to develop in order to reach the concept of FASyS factory. The new optimized manufacturing processes (work place operations, interrelations, etc…) will be defined and implemented inside the FASyS model, and with the results of the tests and through the user experience obtained by living labs means, the safety and prevention systems evolution plan from the actual model towards the FASyS model will be defined.

This 8 sub-projects has been split in a huge of tasks that are been implemented in 3 phases:

• Phase I (2009-2010 Year) Specification of the FASyS Model and associated subsystems. Ensure the viability of Technologies at subsystem level.
• Phase II (2011 Year) Develop mechanisms to ensure proper and easy integration and interoperability of all FASyS subsystems and technologies.
• Phase III (2012 year) Ensure interoperability and optimization in system operation.

Normal delays on the project evolution produces we are lightly behind schedule and the current forecast is to finish on February 2013.

More information about the project can be achieved in http://www.fasys.es/en/ and we’ll speak again about in next comments, focusing on the Tissat role in this project.

IPv6 Launch Day: 6 june 2012.

This Wednesday, 2012-june-6, is the IPv6 Launch Day, which marks the unofficial kickoff for the Internet transition from IPv4 to IPv6, which will dramatically expand the number of addresses available for web sites, as well as millions of mobile devices with Internet access.

Organized by the Internet Society, and building on the successful one-day World IPv6 Day event held on 8 June 2011, World IPv6 Launch represents a major milestone in the global deployment of IPv6. As the successor to the current Internet Protocol, IPv4, IPv6 is critical to the Internet’s continued growth as a platform for innovation and economic development.

In consequence, major Internet service providers (ISPs), home networking equipment manufacturers, and web companies around the world are coming together to permanently enable IPv6 for their products and services by 6 June 2012.

As everybody knows, TCP/IP (Transmission Control Protocol/Internet Protocol) is the technology that devices use to interact in Internet. IP addresses are the unique identifier that devices use to communicate to each other over the Global Internet. At the inception of the Internet, IP version 4 (IPv4) was and is currently the most widespread protocol used to communicate. By their binary nature, IP addresses are a finite resource (IPv4 assigns 32 bits for an IP address, and therefore has 2³², i.e. 4 294 967 296 possible addresses) addresses. IPv4, specifically, is approaching full deployment globally. The keeper of the free address pool, the Internet Assigned Numbers Authority, (IANA), is fully depleted of IPv4 resources. Also, the Asia Pacific Regional Internet Registry, 1 of the 5 regional registries that report to IANA, is fully depleted of IPv4 resources.

Therefore, to continue the operation of the Internet, Internet Protocol version 6 (IPv6) was created.(IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with this long-anticipated IPv4 address exhaustion, and is described in Internet standard document RFC 2460, published in December 1998). This address space is vast–more than IPv4 and unlikely to be depleted in the next 50 years (IPv6 uses 128-bit addresses, so it has an address space of 2¹²⁸ approximately 3.4×10³⁸). Therefore, it also eliminates the primary need for Network Address Translation (NAT), which gained widespread deployment as an effort to alleviate IPv4 address exhaustion.

However, IPv6 deployment has been slow. While deployment of IPv6 has been accelerating, especially in the Asia-Pacific region and some European countries, areas such as the Americas and Africa are comparatively lagging in deployment of IPv6: the former because so far they have enough Ipv4 addresses, the later because of the poor Internet usage percentage. In December 2010, according to wikipedia (from I get most of data of this comment), despite marking its 12th anniversary as a Standards Track protocol, IPv6 was only in its infancy in terms of general worldwide deployment.

But, in my opinion, when the American Registry for Internet Numbers, (ARIN) is almost running out of addresses and when smart mobile devices and advanced peer-to-peer application (home devices no as much because of NAT) are increasing the need of “real” IP addresses (without NAT).

DataCentres and Networks Providers wishing to grow must transition to include both IPv6 and IPv4, eventually transitioning entirely to the new protocol. However, the important fact is that IPv4 and IPv6 are not compatible.

There are several mechanims for transitioning to IPv6, since “tunneling” to proxying and address translation, but may be the most deployed is “dual stack”. The later means that any device that wishes to be “online” must be compatible with both protocols for some time to work properly. To clarify, the world network operators will be “dual stacking” these protocols for some time. This means that both IPv4 and IPv6 will concurrently run on the same wires, even though they do not interact. In fact, any modern operating system and/or browser is actually IPv6 ready today, and run both IPv4 and IPv6 simultaneous – check out of TCP/IP settings and you’ll see that you should have both types of addresses already.

While both protocols will be running together for some time, not all hardware or connection points support this concept of “dual stacking.” It is imperative to know this as a data center operator as you begin to assess either how to bring your current infrastructure online and/or design/spec future builds so that all equipment selections support both protocols

The main effect of IPv6 Launch Day is that a consortium of major players in Internet infrastructure (between them is Tissat) says parts of their infrastructure will begin supporting IPv6, the next generation of the Internet Protocol (IP) that powers the Web.