The President of the United States. The President, Congressman Wrangold, Congressman Gilman, on behalf of the United States delegation to the International Conference and local government from the private sector, that we particularly had a people who have the experience and the knowledge who are working in the field of drug abuse and drug trafficking control, indicated important work of the conference itself. After a very brief political contest for president of the conference, we were able to start work almost immediately on the key issues. I believe that this conference makes a significant here. The first, which you can use for weight lifting and other purposes, is the declaration of political will and also the comprehensive multidisciplinary outline of future activities. In other words, the action plan. And this is being taken to each of the countries that participated so that there will be a tangible representation in writing of what was accomplished at the conference. And perhaps more symbolically, we have for you and for Mrs. Reagan a t-shirt, which represents the theme of the conference and which has the theme, noted drugs and yes to life. And so we hope that you will take that one for yourself and one for Nancy so that you can both have those symbols of what will be worn, I'm sure, by a number of young people around the world to symbolize what is going on at this conference. So with that, Mr. President, we thank you for your support and we appreciate very much the opportunity to serve you and to serve our country as delegates for this conference. Thank you. Thank you all. Good morning to all of you and Ed, thank you for that encouraging report. These documents are a testament to the fine work and success of the US delegation. I'm not surprised, however, because our delegation was composed of high-level officials and experts from all relevant agencies of the federal government. It also included experts from the state and local governments in the private sector, all of whom are vital to our domestic successes in controlling drug abuse. But the important point is that you've brought home real accomplishments, accomplishments that will make a difference in the years to come. On behalf of the American people, Nancy and I thank you for your contributions to this battle to save the youth of our country. An effort like this takes a great team, and a great team requires strong leadership. This delegation is an example of the best in both categories. You had that strong leadership in the Attorney General who was head of the delegation in Deputy Secretary of State John Whitehead and in Ambassador Vernon Walters, our Ambassador to the United Nations. And I'd also like to single out for thanks Ambassador Anne Roblesky and Ambassador Bruce Chapman, both of whom worked for nearly two years on conference preparations and Dr. McDonald, head of the White House Drug Abuse Policy Office. I want to commend you on both your goals and your strategy. You have demonstrated that good planning and strong execution will lead to positive results in UN meetings. Dealing with 138 countries at once gives new meaning to the word complex. Yet your strategies for handling this situation show the skill and the talent our country can bring to bear when we're fully committed. I understand that Vernon Walters called this perhaps the best UN conference he's seen in years and with reason. This was the first time that the UN has held a conference on all aspects of drug abuse, including not only the problems of the users but drug production and trafficking. And it's important to note that this was a very high level meeting attended by representatives of ministerial rank. But the big news involves these two items. First, there was agreement that drug abuse is a global problem. You see, until this conference, some had argued that drug abuse was only a problem of our wealthier industrialized nations, like our own.  And that even in poorer nations, drug abuse poses a threat. For this reason, the declaration of political will adopted by the conference confirms the commitment of 138 nations to take action in the fight against drugs. Second, the conference agreed to a long list of concrete practical steps all countries can take to make a difference. And as part of this effort to be practical, to go beyond discussions to action, negotiations have begun on the drafting of an international convention against drug trafficking, which will be a legally binding document. To all of you, that's a great deal to be proud of. Now there's just one more matter that Nancy and I want to thank you for. We're especially pleased that you brought us these two shirts back from Vienna. And the logo yes to life and no to drugs is a message we've conveyed at home. So now Nancy and I are proud to join you in the rest of the world. No to drugs and yes to life. So again, thank you all very much. Thank you and God bless you all. Some fellows bring flowers home to their wife, not me.


the course on dealing with materials data. We are going to continue our sessions from the previous few sessions on special random variables. Let us review what we have done in the past. We first considered the discrete random variables which have a very special distribution. The first one we considered was the uniform discrete uniform random variable. Then we considered a Bernoulli trial. I see that there is a spelling mistake in Bernoulli trial. It is should be this way. Let me just correct it. It should be Bernoulli trials. Then we found that there are three distributions which come out of repeated Bernoulli trials. The first one is a binomial distribution which has over here. So first is a binomial distribution where you carry out n independent Bernoulli trials and look for the number of successes or number of trials which has resulted in success. Then comes the geometric distribution in which you wait till the first success occurs in your trial. So you carry out number of trials till the first success is encountered. Negative binomial is a rather a generalization of geometric distribution in which you try to get the x. You want to get a probability of conducting x successive trials to get exactly n number of successes. So you have to conduct x independent Bernoulli trials until you get the nth successful trial. Then we came to Poisson distribution and we showed that Poisson distribution occurs in the case where the probability of any occurrence is very small when the sample value is very large. So when a binomial distribution has a very large n but a small probability of success in such a way that n multiplied by p that is the number of trials multiplied by the probability of success remains constant, it tends to Poisson distribution. You will see or you might have already seen in the tutorials and the R sessions that are being conducted that Poisson occurs also well during the nucleation of atoms in the physics in the field of physics. So there also the Poisson distribution is useful. We also saw then the distribution which is called hypergeometric distribution in which we have, we understand that there are m items of which n items are have a special characteristic, maybe they are defective or they are certain kind of atoms or they are certain kind of elements. So it has a special characteristic. So there are m number of total items of which n number has a special characteristic and you are drawing a sample of size x and you want to estimate a probability that exactly k of them will have those characteristics. In that case x follows hypergeometric distribution and we gave an example of 3D atom probe field ion microscopy in which most of this except for Poisson, most of the distributions are covered. Poisson as I said before it has been given separately in the R session giving you certain examples in material science and materials engineering for Poisson distribution. It is very interesting that even in that R session this the same 3D atom probe field ion microscopy example is discussed in more details. Then we moved on to continuous distribution and we introduced first continuous uniform distribution and we mentioned that it has a very special importance when it comes to generating random numbers from different distributions using pseudo random number generator and pseudo random number generator actually tries to generate the uniform distribution, the variants of uniform distribution. Then we introduced a normal distribution and we gave some distributions which I derived from the normal distribution which are chi square, which are chi square t distribution and f distribution. When we move on and we look into the inference in statistics these distributions are going to play a very significant role. So, we come to the our present session we want to cover the importance of normal distribution, the central limit theorem and steps to demonstrate central limit theorem. So, where is the importance of central limit theorem? Well many years ago when Galileo was taking observations from the out in the space and he was observing stars and constellation under the exactly same circumstances he found that the observations did not have were not exactly identical. He was actually unhappy with this fact but it took 200 years for Gauss to come and establish that such an error which can be attributed to human error or to machine error is a common factor and these errors are generally distributed as a normal distribution. We call this normal distribution also as a Gaussian distribution to give a respect to Gauss who realize this particular distribution. Now what is central limit theorem? Central limit theorem actually says that when you have large number of random variables observed independently from nearly identical distributions nearly in the sense that the parameter value may not be the same but the distributions are same then the mean of these largely observed random variable also follows no matter what is the original distribution of the random variable the mean of these observations follow normal distribution. So, here it is exactly stated let us read it. It states that if independently distributed random variables x1, x2, x3, xn with a finite mean and a finite variance for all the values of i then as n tends to infinity sum of these variables sum of these independent random variable follows a normal distribution with a mean as sum of mean and variance as sum of variances. Let us try to understand this. We are not saying that x1, x2, x3, xn follow normal distribution we are saying that it may come from any distribution only condition we are putting is that it has a finite mean and a finite variance particularly finite variance. Yes there are distributions which have infinite mean or infinite variance. So, we are ruling out all such distributions and then we are saying that if you take sum of all these independently distributed random variables xi and if the sample size become extremely large in that case this summation of the variable random variable which is also a random variable let us call it x then x follows a normal distribution. Here is what we have to realize that it follows a normal distribution with a mean mu and variance sigma square mu is a summation of all the mu i's and sigma square is summation of all the sigma i's squares. Now let us look into the proof as to generally how it goes. The central limit theorem is proved using characteristic function and Taylor series expansion. Characteristic function so far in our course we have not introduced however we have introduced what is called moment generating function. Do you recall the moment generating function of any distribution we had introduced and this is a another version sort of another version of a moment generating function and it is called characteristic function. It has the same property as moment generating function that is its first derivative with the limiting value at t is equal to 0 will give you the first moment the second derivative will give you the second moment these are all the raw moments these are not central moments. Only difference is that this particular distribution is has an imaginary part in it which is i which is a square root of minus 1. If you use this expansion for any random variable summation of any random variable and use this expected value and use the Taylor series expansion and then let n go to infinity you will find that all of them follow normal distribution. I am going to skip the proof. Proof is available in variety of textbooks you can go through it. The people who would like to pursue this kind of mathematical statistics further they should go through the proof because taking a characteristic function and using a Taylor series expansion before letting n tend to infinity is a very common technique used for proving many theorems in mathematical statistics. So, here it is repeated again that no matter what may be the original distribution of the random variable some of the independent random variables when n is large is distributed as normal random variate with mean as some of its mean and variance as some of it variance with only one assumption that underlying distribution has a finite variance. So, this also has a very specific version which is a simpler version which you might have come across in your other courses of statistics and this is it states that x1, x2, x3, xn are n independent and identically distributed random variables. Remember that that time we did not say they are identically distributed they were independent and they all had a mean mu i and variance sigma i square. Here we are saying that they are identically distributed random variable with mean mu and finite variance sigma square then as n tends to infinity the standardized normal variate of the mean of x, x bar minus mu divided by sigma square root n. Let us do some revision here as well before we say that it tends to normal distribution. Please recall that expected value of x bar is mu and the variance of x bar in such situation is sigma square by n and therefore, a standard normal variate z would be defined as x bar minus mu divided by square root of sigma sorry sigma square by n. So, this is what is written here that x bar minus mu divided by sigma divided by square root of n the probability that this variate is less than t is approximately equal to probability that a z which is normal 0 1 distributed random variable. So, z is less than t where z is normal standard normal variate. This can be easily demonstrated also by using r which will be done in your r sessions or even using excel which is what I would like to show you here that quickly without using r even by using excel and generating random numbers you can carry out the same, you can work out the sort of a demonstration proof of this particular version of central limit theorem. So, let us see how that happens. So, here I have given the step by step method to follow. So, here what I am trying to show is that I am taking x 1, x 2, x 3, x n as a chi square random variable with k degrees of freedom. Why am I taking chi square? Chi square is a skewed distribution and remember normal is a symmetric distribution. So, we want to show that we take a skewed distribution and when the central limit theorem applies how it comes very close to the normal distribution how it actually turns into a symmetric distribution. So, we want to show that if x 1, x 2, x n follow chi square distribution with k degrees of freedom then the probability of the standardized variable for x bar that is x bar minus mu divided by sigma over square root n is less than t, t is same as probability of z is less than or equal to t as n tends to infinity where z is a standard normal variate. So, to demonstrate for timing we will take n to be 500 and k degrees of freedom of chi square to be 5 and then we take the following steps. We first generate uniform random variables using random function 500 of them. Then we copy the value and value paste it here because with every operation on the excel sheet these number tend to change, these number tend to change if you do not continue with these function, these values tend to change. So, we will copy and value paste it then we apply the chi square inverse function. You please recall what we did, what we said about generating a random variate, random variate distributed by any distribution. So, if you recall we said that if x is distributed as any random variable any random variable then f of x is distributed as uniform 0 1 random variate. So, if you call this y then you can generate x by saying that it is f inverse of y. So, if you have y you can find x and this is exactly what we are doing. Here we have generated sort of y's u 1, u 2, u 3, u 500 then we apply chi square inverse function. So, our f is actually chi square function. So, f inverse is chi square inverse function and therefore I am applying chi square inverse function with a probability this is now a probability remember it is coming from uniform random variable uniform 0 to 1. So, this is probability and this is the what we have taken as degrees of freedom of chi square distribution and we generate chi square phi random variables xi. So, this if I had said that this is xi chi square phi then I am generating x 1, x 2, x 3, x 500 for x 5. Now, I calculate x bar and I also calculate z is equal to x bar minus 5. Remember that expected value of x in this case will be k which is 5 and the variance of x is equal to 2 k which is 10 when x sorry x is distributed as chi square phi. So, when that happens this is the your expected value which is mu and this is sigma square. So, I am taking exactly this ratio I am carrying it out here. So, if this is a this is what I am calculating here repeat the steps 1 to 500 times. So, this 500 data point is n this we are doing 100 times. So, that we can have a nice histogram for to generate z 1, z 2, z 3, z 100 and then plot the histogram and let us see how does it look like. So, you see here I have shown 1, 2 and 3 sample histograms out of 100 we generated 100 histograms actually 100 histograms of chi square phi. So, I have taken the sample of 1, 2 and 3 and you can see that how skewed they look you see the distributions are all skewed. Please note that distribution is heavily skewed I have not drawn it beautifully let me correct it myself. So, that it looks better let us do it again this is better. So, this is a typically skewed chi square distribution same is true here, but when you take the z variable which is summation sorry which is summation or which is x bar minus mu over square root sigma square n then this z variable this is a plot of a z 1, 2, z 100 and this distribution is looks very much of a normal distribution. You see how the skewness has slowly here also I have not drawn it well let me do that. So, if you draw it bit carefully. So, this skewed distribution this skewed distribution as well as this skewed distribution are turning into a normal distribution which is not skewed. You can carry out this exercise further when you learn different graphical ways of testing the two distributions are same. So, you can plot this particular graph which is what is known as a PP plot or a QQ plot. I believe you might have already been introduced to this in your R sessions during descriptive statistics if you have then you can generate this data and plot it like one of those QQ or PP plots and you will see how close it is to normal. So, let us summarize. We started this session by saying that why normal distribution plays a very central and important role because it we encounter it very commonly under many circumstances. It was first discovered to explain the error in observations in the experiments performed under identical condition and we still observe that. The central limit theorem for a large sample made it almost all pervading distribution because as far as the underlying distribution had a finite variance and you had a large number of observations coming from the underlying distribution which are identical in nature, independent in nature. In that case if you take either the mean value or the summation of it, it tends to follow standard normal variate with a common mean, the mean as a summation of mean and standard deviation as a summation of standard deviation. The question is how large should be an n because when we think about it practically, mathematically it is wonderful to say n tends to infinity and you show the or you prove the theorem. But in reality the question comes what is really a large n? Well, the answer is that for generally the naturally less skewed distributions if n is 30 or more it is considered large enough. But if your distribution is heavily skewed in that case convergence to distribution could be slow and you may need very large number of samples. So, that time 30 may not be a good large enough, it may go even further to something like 50, 75, 100 you have to find out how fast it converges. So, with this we complete this session on normal distribution and next we want to take all those distributions which we encounter most commonly in the engineering data and in particular for materials engineering and material science metallurgical data. So, with this we end this session. Thank you.


Good afternoon, everyone. My name is Arastas Mollenge from Cambridge, and I'm going to present this study on behalf of Zipora Gitao and Christina, who is away in the US. Zipora is with us. And also on behalf of the other consortium members, Dr. Odomu is with us and Hebad. This study is on one health studies at human animal environment interface in the Olo Sokut Conservancy Narrow County. This conservancy provides a good platform to apply one health because the people and the animals live in the same environment and together with one life. So it is really a good environment for us to conduct one of the studies. According to the definition of one health, it is an integrative effort of multiple disciplines working locally, nationally, globally, to attain optimal health for people, animals and the environment. And in Kenya in the year 2012, the one health program was initiated and they are followed the creation of the Zoonotic Disease Unit under the Minister of Health. And this was done in collaboration with several ministries, Minister of Health, Livestock, Environment, where they came up with a five year plan on implementation of one health activities in the country. And this platform listed a number of diseases that were to be considered as priority for implementation of one health. So, back to the conservancy. This conservancy was initiated in the year 2006. It is located in Transmara West's Narrow County. And this is part of the Greater Mara Ceregete ecosystem. The conservancy, the conservancy has a membership of 109 households. And at the time of sampling, the population of Livestock was 21,200 cattle, 3,000, 35,850 sheep and goats, 881 dogs. And this is that we carried out in this conservancy, used this one, the other approach in that we did studies on people, animals and the environment. And the one approach is the one that considers funding, data correction, analysis implementation of control interventions, as opposed to separate budget and health professionals working in silos. In many of the projects, we started with some incentives given to the community there, or in the conservancy. All the dogs were vaccinated against Rebis and Kenan Bestempa, and they were also be warmed against industrial elements. Later, the community was also treated for soil transmitted elements. And therefore, some of us were collected from the people, from the dogs Livestock, and the wildlife that is currently being collected. And therefore, these studies I said in the beginning is composed of three abstracts, one on, on intestinal enemies in dogs, and another one on prevalence of intestinal parasitic infection in humans by Zipora Gitao and another one on the knowledge attitude and practices by Dr. So during the sampling process or during the sampling exercise, we collected samples from the community. And in this, during that time we did the CAHPS surveys, you could see in the picture, second picture up there, we were doing some of the interviews actually with the people. Later, we did the human study where we collected data from people. We collected FICO samples for analysis. We collected FICO samples from dogs and samples from blood samples and FICO samples from Livestock. The picture down here is, and this is this was an activity that we did in the conservancy because some of the analysis was done in the conservancy office. In the intestinal enemies in dogs, this study was carried out in partly in the field and part of it in Cambridge. And we published a paper entitled the survey of intestinal enemies in domestic dogs in a human animal environment or interface, the so good conservancy in our county. So there, we all know how dogs are in terms of the interaction with people. And this has shown that dogs play a very critical role in the social being of people. And besides that dogs also transmit very important diseases, particularly in this case, parasitic diseases. The first to us is cystic echinococcuses. The picture of the first picture demonstrates how severe cystic echinococcuses appears in humans, specifically in domestic in pastoralist communities. The second one is the same disease in Livestock. It infects mainly the liver and the legs but also other body organs, also other organs in the in the in the body. And the picture to the right presents what we call the cystic cystic echinococcuses, but mainly presentation of tinea and the tigena in Livestock. And this particular disease is actually of major economic importance, as well as tinea, tinea office which causes cystic echinococcuses in Livestock as well, particularly in ship, caused by tinea office. And the last picture is one of the most important actually neglected diseases in the region, called zinureosis, the information of our cysts in the brain of small livestock. And this is caused by dog transmitted the terpworm called tinea multiceps. So dogs also transmit further diseases of interest to the people, the first two pictures demonstrate what we call cutaneous level migrants. This is mainly when people are getting get infected by and salastomers species, particularly Brasiliases and caninam. They cause this cutaneous level migrants. So caracanis, so caracanis from dogs and cats respectively cause ocular level migrants the second picture, you can see a worm in the high of a patient. This is caused by dog parasites. And the figure below, the photograph below demonstrates the infection of terpworm called spirometra species, which is transmitted by dogs as well, and because of this we call sphagnosis. Creators poridium and geodiasis, protozoan infections that are very important in immunocompromised people, particularly creatures poridium and the dogs transmits these parasites to people and livestock as well. Now we did the study. We started with the vaccination of dogs against Rebis and Kenan distemper, and the dogs were dewarmed. We collected fecal samples from 100 dogs, and the samples were processed in Cambridge. The 100 fecal samples represented 76 out of the 109 households in the conservancy and the pictures they had demonstrated the group that did this work together with the vaccination. So from this study, we found out that of the 100 dogs that were examined, 65 of them had at least an infection with one helmet. And we also found out that uquam was the most common species followed by tinnia, followed by spirometra and tinnies, and the others in that hogar. We noticed that of the 76 households that we sampled, 54 households are dogs infected with at least one helmet. And of importance to note here is that the parasites that we detected in dogs are quite great significance in terms of public health. Toxocara species, toxocara catties and toxocara cannies. Particularly in this case, toxocara cannies cause diseases in humans, as well as the uquam species, tinnia species. All these are important parasites can cause zoonosis. The other parasites cause diseases in dogs, some of them cause very severe diseases, like for example, an astro-stomachaninam causes bleeding. All these diseases are of importance in terms of the health of the animals. And more importantly, also that the parasites we detected in these dogs, some of them are acquired from wildlife. For example, tinnia seriaris and tinnia modegi are tinnia species that are acquired from dogs interacting with wildlife. When dogs prey in the world, they come across underlops, the hair from the wildlife, and this is how the dogs get infected. From this study, we can conclude that nine genera of intestinal parasites were detected in dogs, and uquam species were the most common species in dogs. They said also report the detection of spirometra terraria as the most, as terraria, depletium caninam and mesostatis for the first time in the country. The zoonotic ailments found in dogs pose great risk to the people because they are infectious in people. And the helmets also reported in this study show a clear information that the dogs in that consequence interact with wildlife. And therefore we recommend the control of these helmets in dogs, humans and wildlife cause for corroborative effort from the human animal, environmental health professionals in the context of one health. So the next study is the one on prevalence of intestinal parasitic infection in humans by Zipora Gitao, who is an MSc student in Western Nairobi, serviced by Dr. O'Donwen myself. Parasitic infections are of great importance in terms of public health because they cause great burden of disease into people. And there are common in areas where sanitation is poor and hygiene practices. They are transmitted mainly through fecal root, through food or water, insects, and to some extent through bianimos, zoonosis. And the WHO uses the warming as a measure to stop these infections. So therefore in Kenya in the year 2012, the country started the national school based the warming program with aim to reduce infections in people and the associated mobility. But this program was started in areas with high infections. These are, these were actually the initial the provinces where the infection rates were more than 20%. This was Nyanza, Western coastal province and part of Rifte Valley. But despite all this, the program is faced by a number of challenges that even when people are dewarmed, they get frequently infected. The program is based on school programs, but it doesn't take care of the other people in the community. There's growing evidence showing the drug resistance to the drugs being used. Even after the warming, the environment in which these people live is not taken care of. So the people still get contaminated by the soil where they live, soil water and other parameters. And there is also that possibility of transmission through zoonosis. So this study, this study involved collection of recruitment of patients or participants, you can see the features there that my colleagues were recruiting patients or participants, they collected samples. And the samples were analyzed partly in the field. This is in the field and partly in Cambridge. The results from this study indicated that there was quite high prevalence of parasitic infection in the people. By the first method which was done in the lab in Cambridge, 57% of the people were infected with at least one parasitic infection. The second method which was done in the field is many done on elements. So it's not applied for protozoans and the prevalence was 32%. This range is actually in the range of that region because the earlier study that before the program started at a range of about 53% infections. So from this study, we observed that in Amoeba Estolitica, this power muscofisky complex was the most common infection with that 2%, that 3% followed by Trituris Trituria and by the both methods they agreed that Trituris Trituria was the most common infection. We also found Ascaris rubricoidis in terms of ailments by cataclysm and for mojita concentration, we found Ancelostoma species or Neckita americanas, the wukwams. And interestingly, we found a few cases of human infected with the tiniest species, which we think is most likely tiniest aginata, but we'll type that to be able to know the species. Additionally, we, we intend to type the Jadiarabia because we know some, some of the Jadiar assemblages are known to be zoonotic just to find out whether some of this could be infection from animals, as well as the wukwam species. They are wukwam species that are infectious in humans but originate from animals, particularly Ancelostoma selenica which comes from dogs. So from that study we, we found out that women were more infected than males, and the age bracket between 5 and 14 was the most commonly infected population, and the infection increased with age. And therefore, as our conclusion for this study, we found out that the infection of intestinal protozoan infections suggests that the conservancy of these people live in poor water and sanitation, poor water, sanitation and hygiene conditions. The high prevalence of Elm is in non targeted population requires attention. This, this is to mean that because the most of the programs are based on school go and children live out there, those who are, those that are not in school, or they are not population there is need to focus on those neglected or left out populations to have a whole impact. Then the presence of the senior species confirms the currents of zoonosis in the community and therefore we recommend that the entire community is included in a compressive health and protozoan control program, because as you have seen and from the, even from the ministry point of view that the control programs just does the women or inmates but does not consider the treatment of protozoans, and you could see the infections was very in the community. The last study is the one on one is the one on a knowledge attitude practices relating to risk factors for zoonotic diseases in the or support conservancy using a one other approach, and this was by Christina from the University of Western University of sciences California the US and the other partners. So this study involved 15 of the 15 households out of the one or nine households in the community, and the user one other approach and participatory epidemiology to collect data on people animals and their environment. And the goals for these was to highlight the major risk factors and their needs that perpetuate the transmission of neglected diseases prioritized by wto and the zoonotic disease unit. The study also sought to, to, to understand cultural norms specifically to the conservancy residents. And lastly Taylor culturally sensitive and sustainable control strategies that will be recommended for implementation at the local level. For the cup study, the survey, as says the degree of the knowledge of zoonotic diseases. Transmission treatment and prevention. The attitude towards the zoonotic diseases and practices and general behavior that impact on the risk of exposure. So the results. So the results show that out of the out of the questions that were being asked from the households that for example the first question do you know, do you know these diseases for example anthrax brucellosis cystic echinococosis the second question was asking whether they know whether it affects people or whether they know it affects animals. And they responded by showing that they knew most of these diseases, but a few people, a few of them didn't understand that diseases like cystic echinococosis, sorry, brucellosis brucellosis, brucellosis. No cystic echinococosis and trips somersis affected people. And they, they didn't know that brucellosis and tuberculosis are also infectious in animals. So for the second part of the question was whether they knew what causes the disease, how the diseases treated, and how to prevent it. So it's clear that some of the respondents did not know what causes the disease, particularly for anthrax and cystic echinococosis. Others did not know how to treat it, like trips somersis, and how to prevent it. So these are the responses that we got, the responses that we got from the, from the people interviewed. For this group discussion, we came across a goat that was infected with the sonora cerebraries, what I mentioned earlier, sonoresis. It's the level stage of tinnia multiseps. And the local community called the disease there. It's a very common disease in the area. People knew about it. And it causes some severe clinical symptoms in sheep and goats. And with the permission from the owner of the goats, we were able to slaughter the goat and remove the cysts. And use this as an example to train them on how the disease is transmitted and how it can be prevented. So this is a common disease according to the people in the area. And also our dog studies in the area show that this parasite exists in the dogs, meaning that it transmitted to the livestock. And one thing about this disease is that every infected animal, the end result is dead. So it's a disease that causes serious economic losses to the people. So from the respondents, they showed that they understood how some of the diseases were being transmitted and prevented, like for example, diseases such as rabies. This was through contact with dogs, sleeping sickness. This is through Cessar fly. And they thought that the Cessar fly in this case were being brought by elephants who which live in the in the conservancy. So the people are really clear understanding of the disease and the prevention. And this is a case of anthrax in the in the conservancy. So what we conclude from this we conclude that there was limited awareness of zoonotic diseases. So understanding of the transmission roots. The people were most aware with diseases of diseases of higher consequences such as rabies, because rabies causes death, or diseases that cause high livestock production losses such as TB and glossolosis. There was inadequate or improper water sanitation and hygiene in the in the conservancy, and that people also live with animals. The risk of wildlife increased the risk of transmission. We, we, from this study we were able to establish factors that contributed to the disease perpetuating the diseases, the zoonotic disease and this included lack of access to clean water, lack of health, health education, lack of access to health care, lack of access to veterinary health care, lack of access to education. And therefore this study, this pilot study provided baseline data and identified adaptable adapted control measures for the implementation of sustainable interventions. The proposed combination of one health and the participatory epidemiology could be used in other pastoral communities for disease control and prevention. Towards the end, some community projects were initiated and study with collecting of rainwater. The Minister of Health pledged to construct additional dams for the people and their livestock. The Minister of Health, through the current director of health deployed a clinical officer and lab technician to the health center and also provided more equipment and supplies. The county veterinary services implemented the control vector programs. And this is to control vectors that such as SESA and others, SESA fly and others, and also started the livestock selective livestock breeding programs to increase meat and milk yield. A veterinary officer was also deployed in the conservancy to implement the vaccination programs and disease control programs. And a local aggravates is planning to start veterinary depot in the conservancy. The community recommended implementation of preventing measures against predators. This is by use of fencing and use of lion lights. And therefore the intersectoral intersectoral intersectoral collaboration and community participation were critical to the implementation of these interventions. So I acknowledge the following the director of the conservancy, the count officials from the Minister of Health veterinary services and water and all the other groups that contributed to this work and the people represented by these institutions. Thank you very much for inviting me to come and present this and for listening. Thank you. Thanks for a nice presentation. I think it's very holistic. What you are doing within within the conservancy. I have a question and I'm sure there will be questions from the audience as well. First on I see your final slide on the recommendations, almost like a little bit disconnected from what you're doing, which sort of speaks to how we approach health. So it seems like from the farmers or the people in the conservancy, they worry about predators. Yes, they do. The livestock sector went for breeding programs. And they are clear, you know, disease issues as well. So what would be a comment on that and the second question related to that is, you have done I think what we don't often do with one hell we look for one disease like rabies. I've looked at multiple infections and the NTD programs that are looking to leave one behind and the limit of these NTDs are advocating for integrated programs. What would be a thought around integrating control programs for not just rabies but also the hell means that you are talking about in this presentation. Okay. Maybe I can answer this. The first question maybe everybody will be opening the second question. The first one. The approach that we used or the approach that you are saying is quite important because even from the first slide. I mean it's, many people are doing research on their own. For example, I come from Cambridge. Dr. David O'Donogh is from the University of Nairobi, maybe they have a project there or others that we work with. They do it on their own, but from our own approach point of view, we decided to look at the quite large profile of diseases at a go. And this from the economic sense of view, it also saves money. And it's able to, when we combine the data together, we're able to give quite well informed findings from this particular area. So I think the aspect of integrating many sectors working together gives out a good, a better outcome rather than opposed to people going on their own. Maybe Abad could answer the answer on the first one. So the initial idea to create such a program was everybody talks about one health, but it is more or less a theoretical approach and we wanted a practical approach to see what is possible in a community. And what factors can be brought together to do something in one health. So the first start, we started with do a disease profile. We went in the community and asked them what is your problem. What are the diseases? What do you know about the diseases? Do you know the transmission? And this is then part and parcel of the, of the outcome what was just reported. The problem we have only is that we had very little funding, so we had to do PIP and that's why we wanted to do it all comprehensive and that we have the data together and then go one step forward. Additionally, we approached and the authorities in Iraq and the veterinary services and the medical services and asked them now where do you come in. And they said, well, the one health project, so you must come in. So they pledged what he has reported. They, they said, well, the dispensary was underfunded by, had not enough personnel, and the dispensary was not equipped very well so they stepped in. The dispensary people came in with providing as well personnel for the veterinary services. And our idea was to use them community based that they live with the community and go around from time to time to have in to do a kind of survey and what's going on is an up and down the diseases, periodical and whatsoever. And this is the background of the whole thing and we are still in midst of the whole thing it's not finalized and we want to see and then do it on a yearly basis to see what can be done in so disease surveillance. And thanks for that. Any questions online. There is one, one question online that is asking if you were able to comment on the extent of implementation of one health at the county level. So how well one health has been institutionalized within our county. I will address this to you but I was in the room so maybe this could be a jointly answer question. Thank you. Yes, this is quite difficult for me to to come to comment because this is actually the whole county, but particularly the area we are working on we, the county officials, both in the Minister of Health and the veterinary services are really supported as implementing our project, but from the current perspective will be, it is very difficult for me to comment. Thank you. The question is about the implementation of the one health approach at the county level. I would say that is not optimum yet, but at narrow County, we have quite a variety of activities that are going on under the one health approach, and we are escalating that. And we have some partners, being one of them, and the various activities they are doing. And also some other partners like the Red Cross CP three project. So they're quite a number of activities that we are performing with a one health approach. We, we, we have had quite some collaboration with the health component, including a consultative meeting to make reports last week. And we would probably soon have a consultative forum to even escalate that further with Ilri as a host. So there's something going on with the one health approach. Okay, any other question. Comment. Yes. Thank you very much, Dr. Mollinger and your team. My comment is that you have looked at all the issues which touch on the one health and you have brought them to the fall, because I see in your presentation the findings and the combinations you look at water. And more health. Look at people. And it means you are brought the three pillars of the one health together. And I think your findings, though it may not look very scientific. It may not look like conclusive, but it provides a very good baseline of what somebody can pick to address a one health issue in that particular area. And I think, as you mentioned, it is still work in progress, but I think we can learn from it that if I want to study helmetosis in a, in a rock and find the best way to control it, you are brought all the factors contributing to it. That is a very important aspect. Thank you.


Good morning, good afternoon, good evening everybody. It's my pleasure to introduce our speaker today, Lars Rossum. Lars and I have worked together over a number of years on this initiative. It's my honor to serve as the chair of the forum at the moment, and I will keep my own introduction very briefly, simply to introduce Lars as a distinguished technologist and the chief architect of the IT for IT initiative at Hewlett Packard. He was part of the inception of this initiative, and has constructed the first version of the architect chat, and he leads the initiative that aligns and integrates all of HP's management tools using IT for IT as the reference basis. He's been working on IT and service provider management systems for over 20 years, and has a PhD in computer science and masters in engineering and an MBA in technology management. So without further ado, Dr. Lars Rossum. Thank you Chris. This session will be really why, what and how around IT for IT. So the abstract we sent out for this webinar was really, as has been introduced here, to describe what we've really been working on. Give an overview of IT for IT, what it offers, how you can consume it, and how you can use it in an IT organization, or if you're a consultant, or if you're a tool vendor. It can give a lot of guidance and hopefully lead the industry to a better place than where we are today. The starting point for what we have been doing is really looking at IT as it is today. The observation is that we have a broken chain. There's a lot of things that are quite problematic in IT today. We at the same time are seeing a shift in the industry in how we are consuming solutions, like we are going more and more towards standardized solutions, if possible, the entire concept of multi-supplier, that a single IT organization is not developing everything itself, but is actually consuming services from other suppliers, implies that the area of IT management becomes problematic or becomes more complicated. So buying standardized solutions is great because it puts down cost of IT, but managing it, the cost goes up. We see that there is a number of existing solution framework or general framework for how to manage IT. The most known one is ITA as a framework, but there are other ones out there listed a few on the slide here, but they're more than that. The interesting part is that though they have a lot of details on what you want to do on a process level, it does not really give a prescription on how to manage the service models and the life cycles, and as well as not giving prescription on what kind of systems or components do you need to put in place and how do they interact. Another observation we had was the fact that IT management fundamentally is industry agnostic. So most people want to believe that they are special, and the same goes with IT organization, I talk to many, and in general they go out and state, well, we have a special situation, we have a lot of special problems in our organization, but the more we analyze it, the more it turns out that everybody is really the same.  And so it should also be possible to give a reference architecture for how to manage IT in a standardized way. It actually goes hand in hand with concepts of TOGAP, which is also coming and managed to the open group of you should really, for each area that you do IT for, has a reference architecture, a reference to be architecture. And IT itself is such an area. Just like you would have it for a bank, say accounting, you would have a reference architecture for how an account system should look like, you can have that for IT. We did, of course, as part of that analysis, see that the lack of such a standard really is driving off cost significantly. And that has been one of the driving forces. And we have some examples for some of the early members of this work where just the simple thing of interfacing two incident management systems between a vendor and a consumer of a service could take half year, full year to implement could cost upwards of a million dollars to make such an interface before. And fundamentally it's just exchanging incidents. Shouldn't be an issue. It should just be clock and play ideally. And if you go to ITEL, it doesn't really help you in describing how to do that. There is way too much wiggle room in how you actually arrange your incidents within the ITEL framework. So with that said, we started to look at what is actually going on in IT. And we also decided about, it's not enough that we solve just the operational space of IT. It really starts at the planning side. There is some business process modeling of whatever kind of business problem the lines of business have. That leads to some demand being registered with IT. IT try to translate that into requirement. Projects are being created. They've been developed. Defects are being found. It becomes a request for change into operations. You start to monitor there's incidents and events and problems and maybe some kind of subscription being managed. And everything is linked together by processes. Not by data, but by processes. And everybody referred back to some kind of a service model that says, well, this is the account receivable module that has an issue. Then people have to figure out what that is. How does that relate to conceptually what business was requesting originally? And it turns out the traceability in this is close to zero. And that's not just something I claim. If we go out to most of the organizations, they have that issue that you do not have traceability end-to-end in IT. You might have a little bit of traceability within some of the silos, within the operation space, maybe within the development space, but end-to-end doesn't really exist. So what are we going to do? The first thing we looked at was to say, well, essentially running IT itself should be done the same way as you do any other business. And that implies that you should really look at it from what kind of methods would a business apply in order to become a decision? One of the things that many businesses look at is their production of organized business, which IT really is. It takes demand from external sources like the lines of business and then they produce services that have been delivered by IT. And so Porter is a business guru and he came up with the concept of value chain and it was initially mostly used by production companies. And we looked at that and used that framework and said, what would that look like within an IT organization? And the picture you see here, and there's a couple of different ways of doing that layout, but the picture you see here of the value chain really highlights the essential part of it. The value chain has four essential value streams in IT that are called strategy to portfolio, requirement to deploy, request to fulfill and detect to correct. And the rest of the presentation will really be spent on outlining all the details of these four value streams as they've been called. To support that, there's a number of supporting activities, finance, sourcing, vendor management, intelligence and reporting, et cetera. And these are activities or supporting functions and people call it that as well, which I really share across all of the enterprise. So it's not IT specific finance, it's not IT's its own, but IT needs to interact with finance as it's delivering its value streams or implement the value streams. And by having that view into IT actually resonate a lot with business leaders when we talk to them about the IT for IT framework that we put it into a business perspective. Each of these four essential value streams, they deliver values for IT and can be measured and they are interlinked. If we then dive into that in a bit more detail, the next step here is that we have these four value streams that together makes up IT. The first one, strategy to portfolio. It is really where you would drive the portfolio of IT. You figure out what kind of business innovation should IT support and making sure you have all the right strategies in place and prioritization in place to do the right thing in IT. That's also where you at the end of the day have the end-to-end reporting out of the state of the world, the state of IT. Then we have requirements to deploy. That's where we build capabilities for IT. Essentially, when stuff has been agreed upon that this is something to be developed, something to be delivered by IT, you hand it over to a development organization. So the first part we would call plan. The next one you would call build. Once you have a better capability, you put it into production. So traditionally in IT, you would say plan, build, run. But here in IT, for IT, we introduce the step in between which we call request to fulfill. And that's because one of the things that we realize around IT is that in order to become a modern IT organization, it needs to change its form. It needs to be a service provider or IT organization. Today, they are transforming themselves or should transform themselves. Someone not quite there yet into becoming a service provider. They have served their lines of business. And that implies that in essence, all the capabilities that have been developed should be put into a service catalog be available for consumption by IT. We should also say that requirements to deploy when you build something, you could also source something and you decide that it's not something you build yourself because you get it from a self-supplier or you get it from the cloud somewhere and you put it into the catalog. And then when the lines of business really need an instance of that service, they need a time tracking system. They need an oil planning application. They need an account receivable modules to be upgraded or changed or whatever. It is done in request to fulfill. That's a very expanded version of what traditional IT is called change management. When request to fulfill is then pushing something into the data centers to operations, then you will have run detector correct, which is the run part, making sure everything is healthy, that it gets downgraded, upgraded, monitor the performance, etc., etc. And if there are any issues that they are captured and dealt with and problems are raised and fed back upwards back into requirements. So that's the four value screens in IT for IT. So far, there's actually nothing really mind-shattering about what you've been doing to make your change in IT for IT compared to what you've seen or discussed before is while we're using a few new words. But then it's the request to fulfill that consumed part. So plan build run has become plan build consumed run. Another thing that is introduced in IT for IT is to say, okay, we need to be much better at managing the actual service being built to understand what it is. And this is where IT for IT is going a little bit against what we see in ITO. We're not throwing away what is in ITO. If you look at organizations what they've implemented everybody to some degree is trying to do ITO version 3 or the latest iterations of version 3. But in reality, the service model, most organizations is where ITO version 2 was documented. So that is having an EMDB that kept track of what is the realized service. The service running in the data center. Often the EMDB in operation is populated based on discovery mechanism. So there's a long process going on before you get into operations but certainly things pop up in the data center you discover it by some means and then you populate your CMD. Which is a very backwards way of doing it. I do discuss that this is not good enough the concept of a CMS is around really having a full change management system and managing what is going to happen in the data center earlier in its basis. But in ITO version we actually take it one or two or three steps further ahead. So we really say you need to look at services as starting as a conceptual service model. The conceptual service model is essentially just describing what are the concepts you're delivering to the lines of business and attach to those concepts what are the requirements or the demands that the business has on the service. Business don't care about how it's implemented they only care about what is the difference and at that stage you don't care about the details of what does the APIs look like or the user interface looks like or anything like that they care about whether you can do a a mobile time registration or you can do an account receivable or stuff like that. You take that into the development cycle the sorting cycle of the EMDB and what comes out of that or the process of that you are really creating what we term the logical service model. That is a model that describes what how did I actually design this service. So what is the logical service what is the we'll be describing how is the service actually constructed what modules are part of it what are the APIs that are available what are the the way it can be consumed. But you can instantiate such a logical model by actually installing the service and you might install it one place or several places etc and you might have several logical service releases that all come correspond to the same conceptual service. And then finally you get into the point of saying okay I take that logical service and I hand it into R2F R2F will deliver the service into the data center and instantiate the realized service model. That way you start to be able to create traceability all the way from conceptual to logical to realized and backwards again and we'll come more into the details that need as we go along this presentation. So moving on from from that there was another principle we looked at when we started constructing IT for IT and that is really to do a layer analysis starting with a functional model to figure out what are all the functional areas that IT needs that's basically looking at customer use cases etc going on to a lifecycle model where we look at the what is the essential thing that happens in terms of continuous assessment continuous integration continuous delivery around this service model and the lifecycle of those service models. Then we went in and looked at the information model which is figuring out what are the key controlling IT artifacts or data objects that is part of managing the lifecycle of services and then finally looking at what are the key integration points that will then happen within such a landscape that controls these information model objects and what we wanted to do is to create a normative standard which is what we're doing in the open groups very soon to be released as a public standard is to formalize the information model and this integration area because the top layer is what many of the other frameworks are doing a great job of trying to advise IT around what processes you want to use you can use iPhone, you can use COVID there is a safe framework for development for Bluetooth etc but the underpinning system what are the key controlling data models we need to put in place that we use the same information between systems and between suppliers in the IT state so if we look at that we can then look at the how does this IT for IT really relates to some of these other standards of framework we have in the industry that many of you love or use on a daily basis and the first one that most people ask around is ISO and you could say ISO is essentially a best practice framework for IT processes and the taxonomy of IT it's a good framework it is primarily focused on the operational side of IT not as much the planning and strategy part even though it is part of the latest standard practitioners traditionally mostly use it in operations where IT for IT is a reference architecture for the IT software ecosystem right so it describes what is it that you would put in place in IT in order to manage IT itself so it underpins ISO if we take TOGAP well that's an industry standard architecture framework so it describes how would you go about planning out and introducing IT services and in that sense IT for IT is one of the libraries that TOGAP say you should develop for any area you want to to manage and IT itself is an area you want to manage and finally there is a specification language called ARCHIMATE which is also managed by the open group it's a well-formed model language for business services and we have chosen in IT for IT to use ARCHIMATE as the formal language for the normative standard for IT for IT which is also being aligned with TOGAP so it all forms a very nice complementary set of things to look into the ISO part is another standard unlike the other ones and is not part of the open group and I would say they are competing things in the world around ISO but we do recognize that's very important for quite a number of IT organizations so we make sure that we are reasonable aligned with that Going from this we go a little bit into the structure of IT for IT and here we say well in addition to the normative standard as it just describes that we are creating we also create a number of guidance documents which really describe and actually the purpose is to for it describes how typical capabilities and processes will interlink into the IT for IT normative standard so as we will see in the next few slides we have concept of a component like an application component in ARCHIMATE which is called the functional component and the lifecycle artifact or data object that's part of the normative standard but how that links into scenarios that is described in some guidance documents it's not normative but it's a guide to how you can consume the reference architecture and we have that for a number of scenarios like agile development or how to do SLA management and how to do IT financial management another important aspect of IT for IT is that we've decided to develop it as a layered structure so there are five layers in the in the IT for IT structure the reason for that is that we want to make sure that two things basically that is consumable even if you are not a hardcore architect IT architect that you still be possible to consume it but on the other hand it should be precise and specific which requires that we use a lot of the methods from hardcore architecture disciplines it should also be we should be sure that it's end-to-end complete don't have gaps that it really was end-to-end in IT and if we go into all the detail of specification that you can end up constructing in a language like ARCHIMATE it might be difficult to actually be the forest for the tree so to speak so what we've done is that we say at layer one we have a it's an overview layer it's not the normal to standard itself it's an abstraction of the IT for IT that really allows you to talk about it in a single slide you can have all the concepts of IT for IT in a single slide and you don't use any formal notation language you have a simplistic language we use for it only three different symbols in it so anybody can learn it in five minutes I will show it next slide then we have a layer two where we go one layer deeper each of the values being required of whose slide and we start talking about the flow of data information etc and then layer three is where the real hardcore normative standard is specified in ARCHIMATE it's very comprehensive so it's not easy to just grasp at day one but you can drill into that and then you say the last two layers four and five they become vendor specific we realize that detailing something out into the entity degree of accuracy will take forever and would actually hinder the industry in adaptation so we say layer one, two, three will be formalized in the open group layer four and five will be for each vendor but because of layer three they will be able to interoperate so let's look at IT for IT at the layer one and so first a couple of symbols here as I said there are really three symbols the circle black circle that's a data object or key data object we've identified a small set of key objects about I think it's 33 key objects in total that really controls all of IT into it and they are listed in this there are the blue squares these are functional components they are the essential component you need to put in place in order to manage IT each functional component should really control one key artifact so it becomes minimal you can't really decompose that component further without spoiling some of the traceability so typically you would buy or increment at least as a full functional component at a time and then there is the black line which is just stating that there is a relationship between these or a direct relationship between these components so for instance an incident can be related to a problem and vice versa similar an event can be related to an incident and vice versa if you go further down in a specification we have cardinality etc but at level one these are the only three things we have some of the key data objects are the ones that actually keep track on the real service model the model of what IT delivers to the business and they have a slightly different color as you can see at the bottom so the configuration management component will contain data objects that represent the actual services being delivered to the business so configuration items in essence you know in the DSP and so if we drill into the four value streams strategy portfolio has five functional components controlling in total six key artifacts so at the at the bottom you would see the service portfolio component it's a pretty important one it keeps track on all the conceptual services that IT delivers and also what is here in terms of the conceptual service blueprint which is essentially saying well what are the phases that the conceptual service go through so we have a version one of that of let's say a time tracking system and then we have a version two of the time tracking system which has more business features delivered maybe a business wanted it to be mobile accessible and that would come into version two then there is the portfolio demand component which keeps track on all the backlog items that the businesses are requesting so essentially it's equivalent to business demand coming in that is being managed there then there is the proposal component which keeps track on what is named the scope agreements which essentially are the IT projects that are being kicked off so it's the contract that the IT CIO office or the planners allocate a bucket for and says okay we want this to happen and it's handed over to the requirement to deploy it to actually be developed and of course that relates to the backlog items because it's essentially specified as a collection of backlog items that we decided yes we're going to do it and they are again related to what conceptual services to be delivered and then finally there is the policy component which keeps track on all the policies that IT lives under they will be related into which conceptual services to follow those policies and the enterprise architecture component which are your traditional Spark's EA or a similar kind of systems that would keep track on the service architecture of the business services that these IT services will underpin so of course again they relate back into the conceptual service so these are the five things you need to put in place in order to actually be able to manage IT to track on what is IT delivering and the reality is that most IT organizations today do a very poor job of actually doing this but that would be a discussion for another day moving into requirements to deploy there are more things in play here so essentially there is I have to quickly count here nine components eight nine components that are being put into play there is at the bottom again there is a service design which is where you start designing the service and the release decision component is difficult to read the end here which is where you keep track on what are the compositional things you release out and then you have the usual things you have requirements you have defects you have test cases you have source and bills and and and bill packages and I can't have time today to go into the details here I need to have time for Q&A the important part is the IT project or IT initiative story that is being maintained by the project component that's where essentially the budget is handed over to and a project manager will be sure that all of the things that happens in our city is actually being delivered on time whether it's agile or whether it's a waterfall or any other kind of process you're using you can actually do it using these sets of components the next one is requested for a bill and that's the new one the new kid on the block there's a lot of names in here that would not sound familiar to all of you listening into this presentation the essence here is that we are transforming IT into becoming a service provider which implies that you need to have a consumption component where you can go in and shop for what you want from IT and some of the things that are very difficult to get your head around initially is that IT itself is a consumer of IT so if you need another virtual machine for already you should be able to go into a consumption catalog and and with the profile of the developer you can get a virtual machine for that if you are a person responsible for delivering an IT person responsible for delivering major service in a region you should be able to go in and allocate machines for an extra exchange server installation or even allocate the software that you need to put into production in order to do that you need to manage the offers that you can do you need to understand how is the composition of the offers and then the very important component here is the fulfillment execution component which is the one that actually figures out how to deliver it and the implementation of the fulfillment execution component can be an assistant that just keeps track on the manual things you're going to do so kind of in line with a traditional change request process or it could be fully automated sound-oriented way of saying I'll just press the button and we'll do everything completely automated and then also associated with the customer fulfill is keeping track on what is then actually the usage and then doing the showback charge back to whoever is consuming that component there's not more information about this value stream in the detailed documentation and again I can spend a couple of hours explaining the details of what goes on here but it's a very important new thing in IT for IT compared to what you're used to the final one is detected correct here most people will feel at home because essentially these are the components you need to put in place in order to manage the things that are running in IT you have a configuration management system where or component where you keep track on what are actually the services you have running changes there is controlled by change control with RFCs you have service monitoring of it you have an event component that keeps track of everything that happens you can manage incidents, problem known errors you have to be able to manage service level and that is the executable part of service level they actually come to life much earlier in the life cycle it's a full guidance document around how that works in the IT for IT standard and then the the runbook automation component and so if you take all of that and put it together you get this picture and this is and I forgot to mention that in the beginning but essentially all the material I've shown here is the pre-release of the 2.0 reference architecture of IT for IT which is essentially the thing that will be released as a standard in a month from now what you see if you put it all together there's one important thing is that at the bottom you sort of have a line going through with all the purple circles and you start with the conceptual service becomes the logical then it becomes what you actually release then it becomes the desired service that you want to put into production and then finally what you actually have in production that's a line with the various stages of the service definition is what we call the service backbone and that is what gives you traceability so you can go all the way from a conceptual service or a scope agreement or portfolio backlog item and figure out what was actually done where is it in the development what is which data center have installations of this in which versions how many incidents are actually being created on which versions of that conceptual service so suddenly if you have this in place you can actually have true traceability in IT and with that I'm coming to the end we still have another 20 minutes so there's plenty time for Q&A but essentially in summary IT for IT is not trying to replace anything out there it's complementary to existing frameworks but it addresses something that didn't exist before and that is a prescriptive reference architecture for how to run IT itself we believe it's very robust we have tested it out so it's not even though this standardization is just being finalized in its first release now we have a number of IT departments that are following the IT for IT framework and it's used it for incrementing solutions we have tested it against the latest trends in terms of the API DevOps we actually within my organization we have reference implementations of pretty much everything in the reference architecture many thanks Lars I think we've all struggled a bit with the audio so Simon and I will address that later on so many thanks to all for their perseverance with Lars's final slide up I'd like to respond to the question that said that the relationship between IT for IT and IT is important but what about the relationship with RKMate and TOGAF I think the thing to point out about one of Lars's slides is that it doesn't compare apples with apples I mean the point that we're trying to make here is that some of the understandings of IT for IT mask its rather deceptive simplicity there is a complementarity a very strong complementarity to ITIL but what we are not doing is competing with or anything else in relation to TOGAF or RKMate what we've done as good citizens of the open group if you will is built IT for IT using TOGAF and our representation of it uses the RKMate language so the slide that Lars is just running back to now thank you Lars the top level comparison is a true comparison the other two pieces are highly informative but jolly good question so that's the first one let me go up I've got lots of comments about the audio that I need to whiz between another question that was raised was that the word layer is a bit misleading I'm inclined to agree what we have is a sophisticated leveled abstraction so we have five abstraction levels and again the power of this is actually much more sophisticated than it first seems because the abstraction levels moving downwards enable us without being dependent on any process model to enable vendors like CA, ServiceNow, IBM, Microsoft, HP and the others that are already in the forum to conform to the standard and demonstrate the compliance of their products so that is something new and powerful a prescriptive architecture, a prescriptive standard that can be conformed to right down to the product level and then we can also go upwards so the value of abstraction levels moving up is we can articulate this as Lars has demonstrated to CIO and CIO plus one levels in language which is conceptually consistent with the standard but without overwhelming them in the down in the weeds detail that's obviously need to make the CMDB work and make everything integrate to deliver the services in the value streams so again the comment that layer is a bit misleading I would take that one on the chin these are abstraction levels pardon the clicks I'm trying to scan out between the questions a question was asked IT software ecosystem is there a clickability to telecommunications and IT infrastructure data centers extract etc the answer to that is a qualified no we are dealing with the business of IT this is various labels in different parts of the world and the business but what we're looking at is the business of IT in other words that specific area and I would like to add to that go ahead Lars in the sense I in my past life I've worked a lot with the telecoms industry you could say a lot of telecoms is today in a transformation to become managed service providers so they become more and more IT organizations and in that sense a lot of telecoms can actually use this as well there's also another thing I've looked at ETOM which is the framework for telecoms so to speak it's managed by the telemanagement forum and there are ideas from that that has migrated into to this framework so the concept of consumption the request to fulfill and the concept of having a layered way of presenting it can be traced back to ETOM so we do have some degree of understanding of what goes on there absolutely so I would underscore Lars's elaboration there by characterizing if you will the IT for IT initiative as a long overdue perception of IT service management as its own industry vertical and what we've been able to do with the leveled abstractions is to accommodate the learnings from other standards in other industry verticals to truly appreciate the space that this can occupy in the frameworks and standards landscape out there so we were also asked a question about performance metrics in enterprise architecture and work products such as the ones that are articulated in TODA our response to this is in the substantial guidance material that comes with the reference architecture so just to give you some background we have almost 50 organizations actively contributing to the collateral that you've seen Lars introduce today one of them is Westbury Software who are in the business of performance measurement and management and we have an active work group which is developing KPIs which provide the full insight from the models that Lars has introduced so again there's a huge benefit in our involvement with the open group in that we can draw that if you will structural need from TOGAF and deliver it through one of our own work groups within the forum but a great question there again bear with me while I scroll up so while you scroll up I picked out a question here or two questions but the first one is can you implement IT for IT incrementally very much so that what we recommend all our customers and typically how you would run projects we typically see that people start looking as they detect the correct area and implement some of the functional components around incident event monitoring etc and then move out from there to other parts so you can definitely do it incrementally and it's not a ribbon replace very often existing systems you have in place can be made part of it so typically the first thing you would do is to map your existing landscape into IT for IT and then you discover you can use it as a way of discovering how you would to be architecture could be based on your current as is architecture that is what systems you already have in place a lot of overlap typically takes place in most organizations so it becomes a good backdrop for that associated with that question there was is this primarily an organizational change thing or my comment here would be no it's actually the opposite the IT for IT really supports on terms of is there any kind of way you want to organize yourself and any kind of processes you want to do it's not true that it can be any but the the idea is that it is a staple with respect to the organization the thing is that when you implement software systems in enterprises they typically live for a long time you want them to be safer for a long time and and by making sure that you have a consistent architecture the component you implement any component that living component you want to make sure that that is something you can use for a long time and you might change your organization many times you might change your your processes of how you work but without changing the components we have proven out in the framework that it works with a lot of different processes and organizations that means that we do believe that often you can also get a lot of benefits out of combining the two so I'm not saying you shouldn't do organizational change or process changes why do you do it yeah thanks thanks very much Lars just to elaborate a little further on that I mean the the the real power of this leveled abstraction that you see on the slide in front of you to extend Lars's comments a bit this work is completely process model agnostic so we were asked whether or not this would accommodate Deming's work of PDCA and so on and so forth the answer is absolutely yes this is sufficiently agnostic at the process model level to accommodate anything from waterfall to DevOps and so on and that is the swappability if you will this approach to building the collateral and these upwards and downwards abstractions that you see indicated by Lars's arrow on the right hand side of the slide makes this truly unique and definitely a space filler in the landscape at the moment there's one question here Lars I'm going to direct to you because you're in a much better place to answer it we were asked what do you mean by a realized in quotation marks service model right some people also call it a physical service model so really what we are talking about is the model of what you are actually running in your data center something you have turned on or at least put available in the data center so it can serve customers so it's traditionally what you go out and have in your CMDB or CMS systems and populated typically by a discovery and so physical doesn't refer to the fact that it should be the machines as opposed to the application just means that it is something that now has been realized it no longer has been planning or setting state the it relates to slightly relates to another question because I see there was a little bit of discussion about does it also include machines and ships and what have I and yes it does the service model will when you model what you you are actually putting in the data center you need to go all the way down to the actual hardware so the idea is that IT for IT was managed from the business service level all the way down to the physical machinery that it's all running on top of of course if you have an IT organization that relies on cloud services to deliver a lot of it some of that will be abstracted away from you but we are not protruding ourselves from also managing the physical world Wonderful okay we have a related question which I'll initially respond to but then bring you back in again Lars is the question was can you define what you mean by life cycle level and then the supplement was life cycle of what my response would be it's an end-to-end overview soup to nuts as we would say in the USA but in terms of the specific perspective the life cycle perspective of IT for IT begins from the value chain in the four value streams and the reference architecture is sufficiently rich that the functional components and everything else prescriptive required to design and choreograph all of that activity is rich to support that whole of life cycle and do you think that's a reasonable response Lars or would you care to add anything No I think that's a reasonable response there is always things that can be evolving more and when it comes to the service model and the life cycles of services there's still further work that we're currently doing looking into what other standards are doing here there are interesting standards like heat in the open stack and in Tosca in places for instance and we don't want to replace them with something else we want to make sure we have pointers to them and align to those things there was a question around how we relate to some of the work that is going on by on the UPDM group in OMG I unfortunately I don't know all the details of all the relationships we're doing is the work that we have in IT for IT is growing dramatically over the past year but we do have relationships into the OMG and we're looking into how we can standardize the representation of ARCHIMATE and related things we use an extended version of with some UML part as well in the detail spec and making sure there are exchange formats for that from OMG I don't know the UPDM programming in particular so I hope I sort of answered that one yes indeed there is some more specific ones I'll just take one more I can there was another one is are there already models available in some of the commercial modeling tools FlyMaker, Truce, etc and yes there are some of the people working in the IT for IT group that have implemented versions of it right now within the IT for IT group in OMG we have used the start EA Enterprise Architecture tool for representing ARCHIMATE but we are trying to find an open source tool that is strong enough to be able to capture all this and to not put any favor of any particular vendor but I expect that pretty much every of the major modeling tools will have a version included very soon Wonderful many many thanks Lies for a splendid presentation and thanks to you and those in the webinar for persevering with less than optimal audio I'd like to bring the session to a close now many thanks for your participation


So, one of the most important things about what we're trying to do and teach people is about doing the right thing, but there are many ways in which that can benefit you as a business. People coming out of university, people looking for jobs are looking to work for companies who are seen to be doing the right thing and generally are doing the right thing. Clients are also looking to work for companies who are ticking those boxes as well. So, don't be shy about what you're doing as a company. If you're doing the right thing, get that on social media.  Shout about it because people want to know and people will be interested in working with you and your company. So, do the right thing, save money, build your business and be more sustainable for the future.


What's going on? I am Greg Soss. We enjoyed today by Tom Vecchio of Fandall, who's here to give us the top value plays on the board for week number seven. What's going on, Tom? I'm doing good. You know, coming down to the wire for the last few days, getting his end reports. So let's hop in. Let's get right in there. And let's begin with Pittsburgh Steelers taking on the Tennessee Titans this week. Titans going through the gauntlet right now. And the Steelers wide receiver that most people have been talking about, of course, is Chase Claypool. And Deontay Johnson expects us to return this week. Jiu-Jitsu, Jiu-Jitsu, but he's still around. And yet you don't like any of those wide receivers as their value play. It's James Washington you're turning to at $5,100. I need three other wide receivers on Pittsburgh before James Washington. Why is that the one you like? Yeah, the Steelers certainly have a lot going on when it comes to their receiving core. Deontay Johnson can't stay healthy. I know that he's on my season long team. Jiu-Ju has been underperforming. He's actually been a wide receiver three or worse than 13 of his last 17 games and four of the five games this season. His production is buoyed by the multiple touchdowns that he has. Chase Claypool, I want to say he's their number one wide receiver. That might be a bit of a hot take. But James Washington is sitting here at $5,100, played on 66% of the snaps last week, which was the second highest among wide receivers. He leads the team last week with seven targets. He has the second most targets on the team at 28 sitting behind Jiu-Ju, who only has 30. New York against the Titans who are allowed on 36 feint two points per game to opposing wide receivers. They've been implied team total sitting at 27. So everyone's worried about Deontay Johnson coming back. Everyone wants to go to Chase Claypool. They're still looking to roster Jiu-Ju. And I'm looking at the player who actually has been the most consistent behind Chase Claypool kind of. So I'm taking the savings. I'm taking this game for kind of a shootouts. And I'm taking the savings with Washington.  That's what we're hoping for here. James Washington and his Steelers high flying offense should be in store for a good day. So we hope against Tennessee. The team that the Steelers beat down last week was the Cleveland Browns. And this week you're going to a Cleveland Brown specifically Austin Hooper. Over on Fandall, Austin Hooper priced at $5,400. Tight end position's been a little bit tough to fill this year as it is in most years. Why does Austin Hooper make sense this week for the Browns? Yeah, Hooper checks a few boxes for me this week. I like this matchup against the Bengals. They're around 13.4 fade who points per game to opposing tight ends. That's the sixth most in the league. I think the spot could be in this game against the Bengals is a spot for a bit of a sneaky shootout. We saw the Bengals kind of turn on the offense last week and then they kind of fell apart because their defense is so bad against the Colts. We know that the Browns kind of got beat down. Their defense isn't amazing. And Hooper really is a consistent role in the Browns offense. He just hasn't had that ceiling game. He has the third most targets on the team, the third most red zone targets, the third most receptions. He's behind Landry and Beckham in all these categories, but we just saw this morning that Landry is dealing with a cracked rib. So if there's some inconsistency in their passing game, Hooper is that guy to step up. Looking for consistency. Baker Mayfield is gonna look wherever he can. Hopefully this week that is Austin Hooper. Jarvis Landry battling this rib injury. Baker Mayfield battling his own injuries as well. He's gonna have to potentially check it down. Maybe Austin Hooper will be that guy. As Tom said, checks a lot of boxes. And hopefully the right boxes checks here on Sunday. We've hit a wide receiver. We've hit a tight end. Now let's give you a running back. That's worth discussing here as a good value play. And that brings us to James White. Affordably priced for the New England Patriots this week. James White and Cam Newton. There's a Patriots offense trying to get back in rhythm after stumbling last week against Denver really still seeing the effects and not practicing during their COVID scare. Why does James White on your radar as a value play this week? So last week was, I wanna say just a weird game for the Patriots. They didn't have it together. Their offense was kind of the best overall but we still saw White lead the Patriots running backs with a 54% snap share. He had 12 total touches, 12 total touches which was the highest among all running backs. You know that Harris doesn't play a role in the passing game. Burke had had zero targets last week and his role in the passing game is inconsistent at best. We see White coming in with 19 total targets on the season that's the fourth highest on the Patriots and he missed the game. So we're looking at a running back that has the potential play role in the rushing and passing game most importantly. We have a two and a half or three points spread in this game so it should stay close which I think should kind of squeeze Harris out of the rotation of running backs just because of not gonna be too much of a running situation. And I like the consistency that we saw with White and Newton when they were both healthy. So another game back, another game under their belts looking at this price that I'm saying, I'm taking the receiving upside that James White has this week. James White, the receiving running back for the Patriots for a long time now should have that outside that makes it worth getting into your lineups. Here, Kevin Newton to James White as he continues to just look for targets. He doesn't have any downfield. So checking it down and using guys like Julian Edelman and certainly like James White makes sense for this Patriots offense that as we said, hopes to get back on track. That's gonna do it for us here on Fandal Hurry Up Time. He gave us the studs, he gave us the values. I'm ready for Sunday. Absolutely, me too. If you're looking for more DFS insight, well, we got that for you. Tomorrow, Jim Sonis will join me as we talk about the best DFS stacks for week seven as we wrap up our coverage and get into the weekend. For Tom Decciel, I am Greg Sosner. Thank you so much for watching and we'll see you tomorrow once again for another edition of the Fandal Hurry Up.