we will go through some of the test standards or it was told in the earlier session like the test standards we must for test that or the test will be in order to have a test plan, specification procedure, we will go through what is the test plan, sorry what is the test standard then we will try to apply what are the standards we will go use with an example and to recap some of the session inputs from the last class we went through the specification example just based on how to write how what is the format, what are the contents of test paper and how it is designed so what are the steps that is needed, similarly test procedure also we had discussed, test procedure should be 100% covering the test piece, we also went through the test procedure example which identified the grouping of the test paper test cases only we have identified in the test specification and that is grouping of the test procedure what we will do is we will lay out the practical steps of the test paper which we have laid out in the test case of the test procedure, very simple but then independent of the test paper which has mentioned the of the test and all line, the mapping to the test and all line with each of the procedure we will have to see the difference, in the end we will identify the various tools and setup and test bench whatever it is, it only there are two types, one is automated, the other one is manual type both are similar in terms of the tools and the rest except that manual testing we use the white box approach that means the embedded target procedure, in the earlier session we went to the example test procedure test procedure is organized as per the template and it will help into all the test cases which are given to the test procedure and we will refer some of the external document, interval document, system of supply document also we have discussed about automation testing, PC based application and manual testing also we have identified the tools used, the hardware tools and software tools we will not go through again all this, we will share all these templates and examples so that you have any questions you can take back from me on this example okay then we had discussed about the setup procedures how it should be laid out and to build a program on to the embedded and how we are going to do it etc also we came to know that test execution can be done through the scripts the scripts are developed based on the test procedure steps, test procedure steps can be part of an Excel sheet the spreadsheet can be used for automating the PC based testing then we had discussed about manual testing which has integrated development environment which has multi course methods to be developed various separate personal steps for manual testing these are the typical testing environment where in the tools and all that interfaces are driven through the PC the interface could be any of the interface connected with the target interface could be canned with the manual speed and to feed the real time values we use a break of box or test panel which will have all the test speeds and logs etc then we had fabricated automated test procedures the test flow will be written here and the script what we have done in the earlier stages could be inserted basically the script can be inserted or we can refer to the considered scripts here similarly the manual testing procedures how it should be this also can be done through the script as it is script also can be developed for an IDE that integrates with development environment which will have a connection on the debugger debugger accepts those commands automatically therefore we can have pretty conditions for the particular two tests those three conditions are in between the type of testing manually used before we start the test it could be setting some values or setting our own capacity so also we have a third example of automated test setup manual testing how it should be also we can have a test software build information inside the Android software as I said the software will be something like a special build which will allow user to monitor or track or get the data only from the target then we will highlight the tools function any special instructions to plug in the tools whether tools are qualified or those qualified data all will be implemented here then we will have a session called software download procedure it will allow us to download the software that is the both the test course here so we come to test standards for us to do all these activities there has to be a standard against which the test software against the test software also it has other information which will be used for evaluating or reviewing the tests which are done in the test exhibition space so the standards it establishes the embedded software system software test stage designing the specific standards applicable for the system and the test base if any variants that can be applied if any deviation or if any changes for a specific that needs to be done all these standards will be highlighted and it highlights the purpose of the test standards in terms of methods tools or any rules or guidelines that has to be used for this case for design and development so these standards will be frozen during test plan these standards have to be available when we are done with the test plan this is the software planning or test plan this is used by the testers for example the role is the response to a safety critical objective of 100% coverage of high level requirement that means this role can be the user of the testers has to cover 100% of the requirement and there will be some guidelines which will be method for the other participants the high level test case can have a normal range robustness etc so all these design also the test cases in terms of for testing course condition all these will be part of the test standard so we will go through an example test standard basic template will be test planning, test procedure where in all the stakeholders the tool chain and the revision and all these things so basically test standards will have an introduction with purpose responsibilities test control mechanism compliance and the reliability of the test as you can see the standard, the standard we will go through and then we will use the function so the next the selection of the test 해부 it is a problem this is the result How the system how the space should be we have single time frame, the same time frame ్ ప్త్శ చ్మారోఏని ఇ్లెం ప్మారోని ఇలో చ్యాస్ంంద్ ప్స్మారోని ప్స్టు గసిచిసిన్స్ చ్స్ంద్ సిక్ట్ ప్మాస్ప్యం �!బ్లా చాన్టి వ� చితాలింలి గార్ని. మ౨ియా. పోరిక్త్త్ పాలి మ౨్. ందాాలిమ౶కాట్చార్, చానార్నిమ౶ర్ మద్. పిర్గుర్నా. పిల్నిట్. పిక్టికాని. థావార వారజి, వాడి వాంితబి. పిసివాయెండి. గారర ది నివ్ల మి. ఇదిసిలి పిక్సి. ఆది . గ౒గరందియాల Darwin rock కార్ముర్రు చార్లులు నినాయాలిమిన్ల్లు లిమియు. దిర్పిందియాని దిలులోమారి. మౕందిదిను మనార్ను . పధోటిఇవార్. చివార్టి ఆర్ప ఇిని ఇర్ల్కోధింది. , కారంలేకెతకని కిచిపి ఇసాన౿కెకి . వట్బిలేకికాంది. మంచి నిమంటోచి మది పకండికి. మాతరి ముర్లాన్ప్. ఇలెలి ఴర్త్ల్. మాత్ల్లెర మాన్ర్లి కి మయాస్. సింిమాస్టా. ప్నిలి ప్ప్చి లానిలి ప్సఞి మాత్నకిలి ఆడిస్. పత్ so after high level test cases description shall comply with this document that means after this document pointers the high level test cases are to be done that means that the rules guidelines will compare to different in this document that will be followed to the level test cases on this document and this document talks about rules and guidelines what are the differences the rule is a response to safety criteria of this test guidance is formalisms and template constitute all this will be part of the this guidance will give a pointer to the user after step in terms of m methods what are the critical details about how test data should be developed it is a strictly a guidelines stop the rule is a mandatory stop the verification of the application of rules guidelines can be done that means once the test cases or procedures the execution is done that means to be verified against this document that is one of the rule 6 this is the one rule that is part of the rule 6 that now coming to methods and rules for design and development of this paper the aim of high level test cases description activity is the verification of executable update which complies with the software requirements executable update is robust with high level requirements that means the executable program or the program that is running on the embedded target should be complied with the software requirements it should come up to the SRF and it should be robust with the high level requirements and it should take care of all the robustness in terms of the test environment or the development and the executable object or if compatible with the target computer okay so next one is to verify that the embedded software product satisfies its high level requirement the software high level test cases should receive the following application that means all the test cases that is developed for a high level software requirements these are all a few examples can be tailored or a specific need of this update can be done requirements of hardware software and the service should be robust only in the best requirement those needs to be taken into into the experience or in the case of the requirement these should be these are all a life if someone wants to do an integration in the case of the aspects of the software the test cases activity as we call in the SRF this kind of document and this is the plan for all this that we consider as the input for development in the test case output of the test case activity is the software description document that is the test case document itself will be in the output of the test case development okay now coming to normal range test cases basically this section identifies what are the methods that are used for requirement test cases there are normal range there is well equivalent slots there is the limits value the table based logic equation or any specific cases or other steps all this will be highlighted this again depends on the target that is being under we will go through in some normal range test cases we will have normal range inputs of the normal range of testing for the specific the requirement follows the user to see that value is something like 1 to 10 the normal range is between 1 to 10 anything between 1 to 10 is called as normal range this 1 to 10 is normal range next as I said there should be an equivalent class that should be analyzed for that specific requirement so equivalent class will be applied on these inputs and also there is one point I think very important that a requirement can take only one input based on the condition it could try several or thank you for that so how are you going to do it how are you going to identify so we need to have consideration of the output also based on the input and other conditions this is very important so the equivalent class should be applied on both the input and the input as I said yesterday the input could be 1 it would be 5, 7, 8 and etc generally what we use is the boundary cases for that particular requirement as I mentioned so one definitely has to be there can have to be there because these are falling on the boundary there can be an intermediate value so that is 5 similarly that output of the requirement is 15 and 20 so both the needs should be exercise that means we should write a case in particular way that all the outputs that are derived out of a particular requirement should fall into one of this case design of course suppose 15, 20, 25, 3 outputs are there which will make sure that 15 and 25 are exercised definitely as a normal range and the need range as 20 so that we have exercised all this normal as the equivalent class okay next we have a limit values that means objective of this analysis is to verify the ability of the target system to respond to the input taken at the limits of the input what it means is that if there is an input of say 1 and the requirement says 1 plus or minus 0.1 that means 10 percent of that 1 is used then that needs to be exercise if we should have an ability to analyze the requirement in terms of the limit values that means 1 plus or minus 0.1 means it could be 1 minus 0.1 that means input can take 0.1 minus 0.1 that means input can take how much 0 1 minus 0.1 that means 9 and that will take 1 so this means to be used there are this is useful especially for the analog inputs where we use analog which have a power transfer etc that is very important after the limit values next we have a tables suppose there are inputs mentioned with the help of the table in a structure then at least one case should be created for each bounds of the table and one another should be created for an intermediate point which is similar to the normal table saying that if the requirement is pointing to the table table needs to be exercise in terms of either an input or also based on the bounds if a lower bound upper bound and it should be an intermediate point okay next one is the logic equations if there are any logical equations like this is our and etc etc we need to use ncdc function also to obtain the input I will tell you what is ncdc is one of the important aspects of invirect owner modify the condition and this is how I will explain what is that that needs to be considered especially for multiple inputs or multiple inputs and ed% etc ఀిలెన చగిందారుంచిందటిక౮ిపిaf. నిఆసారిసారేనుటికిందిందానిందారేటి. అమిమందిందిందిందిందిందారినినింది. ఠ ార్తోకిలె మరర్ ప౎ర్తోకినేనినింది. నివసి నింది సెరింద్లాదార తమారాయిందింది. సి మారింద౿ న౸ిందాపిని. మియvänd పింరెతఖరి ధి aney ఓలాయా క్యి టలికైతెబాబ�)] మంెఇ , సటినిల్జక, is an event which pouch and AP . yet move to different stage within the software. o踨arry that course we have a August next dish. ఆర్ర్ లెవార్ర్ర్యు ఇట్వ్ర్ పొవమాస్యర్లికొరార్ మ్ంరోకొర్రో. మ్రార్ స్ర్రంటన్లం పెరెత్టం పుత్త్తమ్నంనంనినంనిక్. న పిడి మత�이ికినిత౾సి థంతిస్టి. గామం. సిందాయస్ పట్టి. సిసితియస్టాని నిటినిసి. మతికా ఉట్నమండలంది నివార్చి ఆపినినిస్న్. ిలార్టిని. మార్టాపిచాత్లు నిరండ్, మర్. కిమా మార్టా మార్టి అపొర్. in సింి పౚ ఆల్యా కెయెవాసాలు సైతింది ఓట సంత్హి, హారాసిదెయా తీటాసిటార్ సారా సిఇ్యఋ సారంద్య మేందాక్ప్టి కెయెసంది సన్లూది వినolé ఆంరనినితికరి. మర్లిం ఇకోమలు. అగాార్లి. అగార్. నింరటంటీలు. పైనాచి నిమరంకోనం. పైపై. పికింబతిని. పైపైసిపెడిసి. పైరికిస్సం. దా The next one is the first is the perfect test case of the development standard for the goals that is required for the requirements that this test case shall be applied on each of the high level requirements that means every test case should fall into the standard we are coming. So for each requirement the following elements are in different inputs the inputs of the requirements and which means the decisions in the requirement text that causes the requirement test case, equivalence class inputs I think in this format we have all the test cases expected based on this what are the outputs it will be having different. All this information should be added to the test as I said the beginner should be here and the test case the next tool is for each function requirement tested I will tell you the requirement of the test case. Yes sir. It should follow the identity key format as the requirement shall be covered at least one test case. We correct one. As I said every requirement is to be tested whatever the way you want to do the automated way or manual way or manual way whatever doing that you need to do that. Yes sir. Definitely there has to be one test case for each of these requirements and this will be correct one. The next tool is each test case of a test case table shall be covered by one scenario and very correct one. The same as whatever we spoke on the test table and the boundary values and all the things I need to correct. For each test case to define the value of the inputs and outputs of the associated requirements of the time required. If there are any supported requirements that also needs to be time required. Typical example for this will be a derived requirement. Derived requirement is something like sometimes what will happen is the this is talking about the derived requirement or any supportive requirement. What will happen is the primary requirement may be sufficient to address the functionality. We need to have a supportive requirement or it is called as derived requirement something like we have a multiple inputs that needs to be defined in detail. What will happen is the primary requirement we may not be able to define it completely. What we will do is we will highlight in the primary requirement these are the inputs that we need. And in the supportive or derived requirement we are going to mention that those inputs will take the value of this value of that which is called this law. Why this derived requirement is needed? Because alphalation of the requirement is very important. This requirement has to be unique and it cannot be AND data. That means one requirement cannot have a multiple requirement. That is a significant role that has to be addressed with a follow especially in the aerospace segment as seen. One identification or one requirement will address only one requirement it will not have multiple requirements. If you want to have multiple requirements tagging to that requirement then you have to identify the next requirement. That is what is the associated requirement or if needed you can have a derived requirement. So that is about this rule. Next rule is each scenario. This case and of course here it should be qualified as normal thing or you can add more based on the need. Similarly this type of testing is used normal thing or this type of thing you have discussed. Some test procedure you may not be able to execute on the car. You should have an index code and you can identify how it will be reviewed. Next one is your procedure. How procedures are AND different? That is I think we have gone to the example test procedure. It is similar to that. So unique idea is named parent for each test procedure. We are AND different. Who is responsible? I have said what type it is. Normal course norms review case. And what is the precondition and review case? To satisfy the course start of the test procedure. In case any external inputs that is to be used for testing that particular requirement. Description means how I am going to test it. This should be a description para certificate. Or we can add all the steps that is required in terms of practical. One of the products we have used in the test sheet because it is impossible to specify one step, two steps, three steps. So this is a test certificate. We should have this in the test sheet which will identify all the steps for previous to modified option for an upcoming document for the course. There are three in here too. That is one of the projects we have used. Up to the user depending on the maintainability requirement. All these can be done. Of course in the test certificate results we will highlight the proof of correction for each of these options. All the tests are done. And test branch or test setup specification needs to be encountered here before the procedure. Guidelines. These are all rules. Rules have to be followed manually. Guidelines are based on the need. Some requirements may need one guideline. Other requirements may need other guidelines. Guidelines are the precision. Something like a general guideline. This guideline. So one example description of the scenario should be here and after. The expected result should be different for each scenario. The scenario should have an output. It should result in an output. The test setup specification should be different for each scenario. As I said, each scenario has to be identified for the test setup. All and all will be needed. The preconditions should be identified for each scenario. Some of the requirements may not have preconditions. Directly, it can be done with preconditions. By itself, it may not have preconditions. In the case, it may have not preconditions. So let's take a look at the guideline. And in the end, we have the tools used to produce the test case development time. Usually it will be a document template. In the case example, we have a pump already. The repetition of the same. So the test case should be identified. Covering of the subject requirement. The scenario should be different for each scenario. The test case should be identified. The test case should be identified. The appendix installed all the test cases in the specific dialect. This is also part of the test case. The static analysis of the test case, the manual of the test case. All that will be part of the coverage. That is about the test case standard. So now up till now we have gone through test case. For example, we started with a test plan. Test case or test specification. Test procedure development. And testing standard. So with the help of that I wish to give you the name of the test case. Simple example I had to develop the test case. So you all know whiteboard. So the whiteboard requirements I have put the four requirements. What will be the appendix test case? The whiteboard. So requirements are something like whiteboard shall have a length of three feet but whiteboard shall allow to write on it. Whiteboard shall allow to erase the written words. Whiteboard shall allow to write colors like black, blue, green and red. That is why it is called whiteboard. So what we call now? For this what are the test cases? The few test cases which I have already discussed. I shall be whiteboard. I am very clear that the end time width of the board is three feet first requirement. Next test case could be check whether one can be able to write on the board. That is the next test case. You should allow to write. So that is why we have to write the test case. The next requirement you have tested with check whether one can be able to write on it. We will use verify in short games. For each test we have verified with check what we have to do. So measure the whiteboard the next test case is on. So we have written words which is the different, we should have to write that is the first thing. Next thing will be, we should be visible both are very important, also you can add to me something like this, verify what is the supplement basically, we have a stress here black you భా్ర్ మెయ్చ్పయు పోముయు సిట్బ్ాలీ సిసిసిలియాస్హివం సిలా్స్రై సిజసార్స్ట్ని టార్చ్చ్న్ నాంటికరక్ట్ంట్ ముపేస్టార్ర్. తర కానకలి ఆవసంలింది. ఇండారంలి.iper champions. మటరండంలి బక౾. కం. నిల బకి ని. ఉని. వపరంలి మంన౿ చాండ మినానందా బ్ల్న్ మతాల మి the you can have a generalize the requirement because we know that what whiteboard we are testing so this case is interesting because of that right here is the words written and written you have to verify that the words are erased it is there good that we have all the requirements sometimes what will happen the intuition user may add more requirement because he has a good knowledge of the system the system is whiteboard so during the review what will happen this will result in modifying the requirement I have seen that or this will result in adding further requirement so in that way as I mentioned yesterday the testing team or the tester should be independent so he can think out of the box he can think from his perspective so this is the example test we need doubts or anything is there on this we can ask okay let us come to having gone through all this test case standard test of the test test specification plan I have put the question simple question in that side many of you can have this answer that we have written out why we need test plan and what are the elements that we can identify so simple question write test strategy for the user set of requirement you know what is the test strategy by now and he should write test strategy for testing the below requirement below requirement is attached here and embedded unit instrument just put an example UI product the software requirement are as per so we should have a test strategy how it is I will further put the next question and together we can see the example is there is more of operation on the part so the next question is write the test cases there are different operational requirements that you for now we can write for that most of the operation we can see how good they are and we can write test cases we can write test format we should be writing and as I said you can use a test sheet to write test sheet planning this is of course an example of a test case scenario or procedure example we can enter the test step 1 2 3 step name just highlight what I am going to do in the description I am going to tell that that all the inputs as mentioned in the pre-condition so pre-condition means it will be pointing to a section which will fluctuate the conditions that are required for executing this particular test so after that we are going to power on the unit then we will set the status or error because it will be depending on the status to error because we want to test on the most of operation where it is going to go etc we will have just a time we can write in that country I will share with you the example basically there is a requirement write the test strategy as we need to write the test strategy how I am going to address the complete requirement unit first and the complete requirement first once you understood the FRS there is one section called most of the test you need to write test case and you can use the complete we will open the FRS you can go through this we will have the FRS will have a system overview I have to put the simplest requirement it is called embedded so the overview of this embedded it will have the below initialization maintenance and internalization then we have a monitoring it is also called as waiting test there is a failure there is a fail mode so this will have all the failures to be detected any actions that are required at the level of failure that are fail that are fail then we have a download management I told you earlier that embedded software needs to be downloaded on to the target so software should have a program I mean the software should have a function which will accept this downloadable program usually the embedded system target will have two sets of subsystems one is a loop loader other one is an application usually there will be changes in the application loop software plus loader this is called loop software this is responsible for downloading the new program the new program should be new program remains some systems will have programmable boot loader also suppose you want to upload or download new loader itself what we will do? we will have the loop software so that is the download mode of management this is responsible for loading the new loader basically download management is a set of functions which are part of loop loader and some functions are also in the application next one is disk form so disk form will not go into detail what is disk form so disk form will be used basically in the separate device and it will be filled in a embedded system it will be a reliable memory here only on the external world this can be accessed to fetch any of the data or if user wants to program new configuration of calibration basically in the separate device this is part of loop this is called embedded system this is called failure that is to be stored when the system is on this will be a memory which is identified as failure failure is given that will be solved then this is a typical embedded application this is called unit control this embedded unit has a control function which will drive which will drive and will get the PWA that because probably I will not go because I do not have scope of this you can google and get an information about this this requirement of this function is applicable how you can try this target while driving we have different parameters voltage control, current control then we have a specific motor control MTR PTR so we will also drive and control so it is a metastart it is a motor speed it is a motor current so I try to put the simplest of performance there are other complexity involved so let us look at this we will just highlight the basic requirements of the functionalities of a typical embedded there is an activation and a connection the data the actual interface or the inputs or the outputs how it is going to be communicated in the embedded package that is with the help of scan the same thing you have highlighted the embedded unit is a power of the motor control so we will be following motor drive control and monitoring and now for digital network failures and data transmission there are several things failures storage in the memory and many maintenance that is required software loading software management we done the help of scan communication there are of course few LEDs to the help of IOLINES that will be in the process and actually it is for the user for you you will need to use the system by using the STL so let us discuss about the measurement I think that is the measurement so there are different things that is involved in the software requirement we should identify operational requirements it will identify initialization it should identify download accordingly you can see the performance operational requirements these are the operational requirements that we have in the small depiction of the different most of operations so there is a unit mode there is an operational mode there will be maintenance mode download these are some of the over here operational requirements operational requirements with the operation we have to explain coming to the the modes of operations what are the modes that are very useful so these are the requirements you can go to when you can explain you can go to so what are the requirements for different modes which mode is there which mode is there when we have to download all this powering as part of the embedded target which we are going to there are specifications so there are timing requirements there are performance requirements there are communication requirements we can we have these requirements so you partitioning requirements will be there there is no separate powering different applications one single application is done some industries they call boot as well as application it is not developed it is simple application so in different states embedded will be implemented what are those states what are the number of states those of the state level state of the state requirement then we have functionality again we need how it is going to be initialization is there building the system there etc similarly we have a point management development management and there is a section in the end tolerance is constant as I said in this state we have tolerance so we call the requirement of so what we need to do is there is a most of operation what we saw just now you need to write this case that is here these are the most of operation there are 1, 2, 3, 4, 5 in each application maintenance so the embedded instrument should be in one of this instrument one of this model upon power up it will be in the initialization then initialization is fine then it will go for operation when maintenance is required because for maintenance the new software the download is required similarly if there are any failures when doing operation or maintenance it will go for failure then it will be depicted you can see there is a small note for each of the arrow so that is nothing but a transition how it will go to the next from maintenance to operation so the mode should be operational it will become here the mode is something like a version where it is below some of the requirements I will not explain in detail about high requirements for most of the operation in the type and where it is that is the mode test case design ex procedure and standard I will pass over the test plan we will be explaining once we are clear about this


n systems. And some of the patterns that you might see and might need to think about things that you might need to think about when you're designing those systems with your technical teams. And maybe don't have time for questions, but I think that's about it. Thank you very much, Austin. That was really fantastic. A quick message to all of you. If this went over your heads, that's perfectly fine. A lot of it went over my head as well. I think the important thing is that this is a reference which we can go back to and refer to when we're actually working with the subject matter. It will be available on YouTube. And this is something that you can then refer to when you're working on the solution architecture. It's what we spent the most amount of time on, on the Medexus Mali case, which will be presented after the break now by Per Kronslev. So it's what we most spent time on was working out these workflows. How does the functional requirement align with the technical capacity, with the contextual then implementation of these servers and how that is actually functioning. So again, the expectation was not that you would understand everything in detail, but rather you would have an overall understanding and a reference place for when you're actually dealing with these issues. So I'll be somewhat strict with the time now. We're three minutes over. We'll take a break. We can come back three minutes past at the top of the hour, so in 15 minutes. And then we'll start with the presentation on Mali. I'm not sure if Austin will have time, but if so he can answer some questions either on Slack or part of the Q&A after Per's presentation. All right. So 15 minute break and then back with the Mali use case and Medexus ELMIS. Again, big thank you to Austin. Thanks, Rana. Yep. Happy to answer questions. Have a good one. Yep. So we started the recording. Thank you again, Alice. So Per will be presenting the Medexus ELMIS. So give a general overview of the system. Again, many people ask us which system do we choose and we say, you know, choose in here and every one of them. So we've invited Per and a few others to present. So this is part of that. And then he'll also present the Mali use case where we've integrated DHS2 and the Medexus ELMIS. And he'll go through that. And we can, of course, take more questions and explain some of the work and the decisions that were made there. It was myself, George McGuire, also Austin McGee and some others involved in that project. So I'll hand over to Per and we can take more questions at the end. And also don't hesitate to ask questions in the Slack channel. Over to you, Per. Okay. Thank you. So I've been asked by Brennan to present two things. First, the software in general, I'll use some slides. I'm not going to start going to the demonstration, but I'll use slides to explain what the software can do. And after that, I'll talk about the use case. And I'll leave some time after for questions. So I will try to keep this at maximum 25, 30 minutes or something like that. Yeah. Okay. So now I'll put the PowerPoint on. Yeah. There we go. I think this is going to work. Presentation mode would be good. Well, yeah, we see your screen now. Yeah, you don't see it in the presentation mode, I think. That should help. It's a presentation mode. Yeah, we got it. So okay. So first I'll go through what this software is and what it can do. And a little bit also about iPLas solutions. Yeah. And my name's there plus an email address. So my name is Pierre Kronzler. I am what they call a senior supply chain consultant. So I've been working in this world for quite a while in a number of countries. I think most countries in South Africa. Yes. So I'll go through the background, a little bit of the company, the designer indexes, equating all its features. So I'm talking about implementation, about dashboards, a little bit of a Brunner case study, and then we'll get to the Mali case study. So background. iPLas solution is a Dutch company, NGO. We are a major procurement agent for the Global Fund upstream. That means buying products for HV, malaria and TB and so on from a long range of countries. Downstream reduced in-country system strengthening. We work with Brunner, DRC, Mali, and Nigeria. We've got Training Park from the Academy. We work on raping and fading on data. And we have this ENRS component. Yes. So what's it about? What do we want to solve? We want to solve, we want to give this real-time visibility in the supply chain. The ability to see what's on stock, what's being delivered, what's being ordered step by step in the supply chain. And we are in 2022, and this is still actually a big issue in many countries because we've got the payroll-based systems, lots of places. This is what we want to solve with this software. So what is Midex? It's not that old. It was created around, started in like 2017. And the thinking has been to kind of start over, use the experience obtained over many years with various pieces of software with ways of doing things and create something simple and targeted the health facility and district level. So not, it's not starting from the top. It's not starting from the same purpose for going down. This is starting from the basis of how to manage a health facility, how to manage a district. That's where it starts from. And as I said, in 2017, it's cloud-based and it's Android-based. So it's made to be used on phones and of course can be used on a computer also. And it's thought as an end-to-end product, trying two means you can be able to track the products from the center medical store all the way to the health facility. It has various reporting capabilities and features. It's actually designed around also the vertical programs. That's another part of the thinking that was in it from day one. It must serve the managers of vertical programs, both at national level and at district level and so on and so forth. It's got these reporting capabilities. It's available as software, as a service, meaning that you can have it the way that it's all managed away from you. And it's simply a service you got. It's got multi-user interfaces. You can do some on smart phones and tablets and it's network agnostic. Now, it does not change right now. I do not actually understand. One moment. Okay, next one. So which kind of features does it go? Forecast and demand planning. So using the history to propose what's the forecasted demand in the future and give an idea of that and then you can, of course, work with it from there. It's got management of the expires and batch numbers, lots. You may choose if you want to do by FIFO, first expire first now, or by FIFO, first infos are. That's up to you. You can track and manage your batches in your expires. So your picking principles are up to you and this is all shown in dashboards. We also have what's called intelligent inventory management. What that means is, again, it's targeted these health facilities and the needs there. So we can track the programs and the donors. So if there's a given donor who wants to know what happened to the products which has been sponsored by this donor, then it's made for that and, of course, it's also made for that. If you want the malaria program to know what happens to everything they have, it can be filtered by that and be tracked down to the only malaria product. It can manage the observable stock, so how much is on creatine. And you can set inventory levels. That means that you will set it by program, you can set it by product, it's up to you. But what stock level is your target stock level? Do you want three months of stock and health facilities level? Do you want two months, five months? It all depends, of course, on the infrastructure and the challenges you have. But you set that level and then the software will help you calculate how much to replenish based on the stock level you've set. You can design your warehouses so you can have one or more warehouses at a given health facility or a district and then you can divide them by bins in the software if you wish to do so. Of course, the more you divide things, the more complicated it gets and that's not always a good idea, but the options there. You can set mechanisms for stock rationing, so you avoid to stock out or so you start rationing, giving you a two little product and system. So the most important feature is this real-time stock visibility. That obviously depends upon that everybody updates the system ongoing. But you can monitor the stock status and the system will also tell if you are approaching stock out. So it starts warning you when you have less than one stock left in your system, when you have two weeks stock left in the system at a given destination and warns you this is this destination and you're approaching to go stock out and therefore you should start doing something to replenish. There's mostly the pull or push for filling process. It's a choice you can have. I mean, so you can work with informed push, meaning that the system calculates how much to replenish, how much to ship to a health facility based on the stock level they should have. Or you can work with the pull system, where you let the health facility fill in an order form and then they ask for what they need from the district level or some level store. So next one. Yes, that's another feature. Co-chain management or management of co-chain equipment. Actually both. So you can set the volume, the physical volume of your freezers and fridges by each health facility in the system and then the system will not let you send more co-chain vaccines to that facility than there actually is freezer room for. So if you can use it to calculate your capacity needs, you can calculate I have so many cubic meter of freezer and fridge space and how much vaccine can I send through the system. You can also manage in it the equipment maintenance. That means that you will also register the age of the equipment, the type of the equipment, all that and the maintenance status. So you can manage that these and these piece of equipment need replacement. They get too old and you can hook the system up with the RTMDs, the remote temperature monitoring devices which is in the equipment. So Medexas will then tell that these and these specific freezers in that health facility is having frequent too much temperature preferences. So this is the co-chain features to monitor that. Now, transformment. So another thing, managing the transformer. Again this is a simple version because it's made for a facility level but also a health facility and district level. District level you often have distribution by milk so-called milk rounds by fixed routes. Or you can have that or you can also have of course routes which you improvise from time to time. But you can use this one to set routes by health facilities and then monitor that the transportation happens in this route. So you put the products on a truck tells it goes on this route. It goes out, the software knows and has gone out on the route and then when you get the proof of delivery back later you will then confirm yes I got the product actually reached the destination. On DHIS2, we're very happy that we've made, I think it was also mentioned in the earlier presentation and so on. But we make quite some effort to get integrated with DHIS2 and we are very keen on that. So we have a two-way integration meaning that we can get data from DHIS2, I'll get back to the implications of that, and we'll send data to DHIS2. So both ways and that has a number of advantages. One is of course that we should, any LMIS data should go, most countries to DHIS2 for national dashboards and surveillance. But there's also a lot of advantages in getting data from DHIS2 in terms of setting up solutions for the smaller health facilities. We can do budget and credit management meaning you can set budgets by health facility and then monitor that they only reach that budget when they buy from the district, for instance. So we have dashboards, some graphical user interfaces, so you can see a map of your country, region, what you need, and then comes out these little dots on what color they have. They're green, they're fine, red, they're not so fine. And you can of course regulate this, but in general it's of course obviously the red ones will basically go out of stock or overstocking, green ones adopt meter fine. So the various dashboards and then you can set the KPI's down here, stock art durations, percent of stock art, expiry rate, so on and so forth. The KVAS can be swapped depending on what you need, these are just common ones. More dashboards, stock levels can be set for a specific program, typically a value. Stock art analysis, stock art is a big issue of course, many places, so there's specific analysis for finding the places where they're stock art and then you can go, like this one shows here, you could go put your mouse on a given spot which has turned orange for instance and then you can see okay it's that product which is out of stock or going out of stock where this one's then close to be stock art. So you can, so this graphical user interface, you can find things and say okay here looks like it's a problem, what is the problem? You put the mouse on it, click on it and say oh it's that product, this program, so on. So it's a great thing on this stock art analysis. This is basically more of the same from Burundi stock art analysis, so there's some specific health facilities, I mean there are obviously many more health facilities but this is for the ones which has a problem and you can find these ones, do something about it, but the KPI is here to the right. Shipment calculation, yes it helps you set the milk balance, set the distribution pattern and monitor the shipments that things moved and that yeah that they have and that has been confirmation of the proof of delivery. Let's see batch recall, yes that can do too, you need to find out what happened to give batch, where did it end up and you can search on a specific package, specific shipment, various specific things throughout the software. Now let's say okay, here comes something, oh that was too big, sorry, yeah implementation. So if I keen on that this needs to be done with local help, ownership, so there are several things on this which are where we think are very important to emphasize. One is that we will have always a local software company involved in this as far as possible as well, so we get into it from the start but then we need when we leave it, it must be in the hands of local minister of health, local software people. This integration of DHIS2 gives us the opportunity to set up solutions at the lower level where we actually do not put our software out there necessarily but we can use interfaces with DHIS2 screens, DHIS2 user interface, which they very likely anyway already are in and this saves training, this saves money because one of the big issues around these LMS systems is to maintain them and to train people, that's why thousands of people and that's very costly. So if we can use this to have only the higher level using it, but lower level use DHIS2, that's a good thing. Fees, it's an ongoing issue and it's one of the big issues around the maintenance of these LMSs. So we've got two ways around this, one way is the traditional annual license fee but we also work with a one-off national professional license, meaning that you can get that paid, if that is paid under the project, under the implementation one-off and then that's it and from then on you do not pay for using it. So the next one, that was that on the DEXAS. Now I will switch to the presentation on the specific Mali case and then after that I think we should take some questions. This is great pair, we already have a few questions in the Slack channel but continue and we can take this up. Well maybe we should take those now then or what, what do you think? No I think you should go ahead with the presentation and we'll take them all at the end, I think that's best. Okay, your choice, let's see. Is it on the screen? Yeah, it's there now, right? Yeah, so you can see now right now it's on the screen? Yes, perfect, go ahead. So this looks a bit different but that's because it's, this project is a USAID project and there's a lot of formalities around this so there's also around the design of the PowerPoint. So now that's because we had a very concrete case where we have a part of a larger health project in Mali and in that context has been created a solution integrating deoxys and DHIs too. So that is what I would like to talk a little bit about now. So this is, it's a larger health project, it's called Kenya since it's in Mali and it is implemented by Palladium actually and we are a sub-component to this. So only one piece out of six important pieces there. Now the project itself, I will of course not begin to this but it's touching upon all sorts of aspects around the the management of the health system there for all these health facilities. It's specifically targeted health facilities and districts, that's the level. Now the objectives is to strengthen the management especially related to women and children in a number of ways including the supply chain and this one or the job, people who just have that, here comes it. Now let's start. So the big challenge we have is that we could say that these ELMA solutions, they're nothing new to them and they've been there for 15 years. We've seen them and it gets boring to tell the whole story but challenges are any solution has to work for thousands of health workers. These people have limited basic training and there's a staff turnover, many places 30% of the staff turns every year. So these solutions often work technically but they're complex for users. So this complexity demands training costs and training many people also because of the turnover. This is an issue and the ministers of health working on this, they don't have stable budgets for license fees either. So anything that demands an annual payment is a challenge. Now, so in Mali we worked on dealing with this. Yes, so therefore these ELMAs are costly to implement and costly to maintain. But like in Mali, DTIS-2 is operated at every health facility and we are there combining therefore the HMS and the ELMAs. And we have started this now and we hope to grow even further where we are now. Now, so the current situation in Mali which I actually think is close to the same as in DRC is that, well it's changing right now actually because we're implementing but then say a year ago the situation was that you had a fully paper-based flow of information, fully paper-based in terms of the products procurement. So paper-based ordering from health facility to the district level, paper-based ordering between the community health worker and the health facility and district also managed by and large on paper and then ordering on paper from city by bus. So that's all on paper, the product flow. But at the same time you got DTIS-2 implemented as an HMIS and you're having data being entered into screens, DTIS-2 screens every month gathered and shown in the national dashboard which in Mali is called OSP Santé. So that's the situation. Now, here comes the concept, what we're doing. So we want to use the existing DTIS-2 infrastructure to secure LMI status directly from health facilities. So we're going to take those screens they haven't anyway put in and then take that data and use that to work with the supply chain. And by that minimise the need for training. So we're going to pull data from DTIS-2 into the full EMS application indexes and generate orders for replenishment. So the architecture, well, I will not cover it, it will take far too long, but there are two steps in this. One, the most simple one is the health, the products which are for free, program commodities. There we get the data every month, it goes into Medexis and we are calculating this replenishment or a shipping data. Then there's a second step which is the products which are procured by the health facilities. Sorry, CSPLUM is a health facility in Mali. So that's obviously more complicated a bit because the health facility will buy the product, so there's a financial transaction involved, but that is also managing. Right now, we're implementing the phase one. And data will remain to go to the national dashboard. We're not touching the dashboard. It stays. Now, so the perspective, I know this is a business slide, but the perspective is that this update stays the same for short on paper between community health worker, health facility manager, things on paper, but they enter that data into DTIS-2 and that data is exchanged with Medexis. And then we can use that to calculate replenishment orders. So that's what we want to do. That's what we have set up now and are doing. Longer term, you can of course do more. Longer term, we can get the community health workers on mobile phones. So they get their data straight in. We do a number of things. This is also about development, about starting a process. But it's hopefully not something that's just like this and then it stays like this for the next 10 years. It's hopefully a path to a change. So, yeah, I know those were a bit too busy, but where are now? So we got the integration is there. We got the solution anchored with the local partners, local HISPs that's implementing. And they also maintain these things on the local server. And we got agreements with Minister of Health, local authorities, that's all in place. We passed this one. So we've done the pilot, we're rolling out now. Here comes something interesting to talk about. So one part is technically, figuring out programming, all that. Another one is the process and not to be underestimated. So here are some quotes on this, which I think I really learned, right? So it doesn't take that long to figure out a possible solution. As it says here, some months, but the dialogue to get moving takes more than a year. And I think that must be respected and must be done. Dialogue very important. And Minister of Health engagement is absolutely essential. And we, I guess, we are guilty, like other people also, to some extent. So we get very happy with this interesting solution. I work with the technical people and all that. But sometimes we forget to talk enough with the stakeholders. And that is an issue. And it must be made very important to keep these stakeholders, special needs of health, informed, engaged, so on and so forth, and use that energy. Working with the University of Oslo, Oslo has been essential for us, lots of good ideas, lots of nice work together, discussions, learnings. It's important to put together this technical concept before engaging the stakeholders. So these stakeholders can see in a few, but it's also important to keep them informed. And in the work process, I would say there is a risk that for technical people, they find it's more rewarding to spend energy on the technical solution compared to the organizational focus, the process part. But both things are very important. I think that's about it, Brenner. Let's see, yeah. Yeah, that's it. Questions? And so now I should get to the Slack channel. So I'll take down the presentation. Is that okay, Brenner? Yeah, that'll be great. Thank you so much, Per. Thank you for that input. So going over the Medexus ELMIS, the software, and then the Mali use case. So this was really great, I think, to share. There are quite a few questions already in the channel, and I can just ask them to you now when you can answer directly. But it would also be great if you can share with us the presentation so we can share with the participants that they can have access to that. And then you also have, you shared your contacts there. So just to share with the participants that you can reach out to Per, if you have also questions that we don't take up immediately here. But thanks again for sharing that. And we're still on this journey with Mali and the integration, but things are going well. And I think it's the showing the fruits of this collaboration. If I quickly go to some questions here directly to you and for Medexus ELMIS first pair, there's one from Gerald Thomas saying, our major problem with most of these technologies is internet connectivity. And I didn't see anything on Medexus talking about data capture through SMS channel. If you can say something about that. Yeah, okay. So yes, can choose an issue. But we have one answer, which is that the application can work offline. But obviously not a long time. That means that the way we've set this up now is that you can work with it on your mobile phone offline, but at some stage you need to get online. So we have not set this up for now to work through simple SMS capture. I know what you mean. But for now, you set this up so you can use your mobile phone offline. Then you can, which is many places, then you go somewhere and then you update, then it hooks up and update once a week or when you're able to. So that's what we can do now in that context. But yes, it's a great issue. I think though it should be mentioned, I think in that context, that we must remember that if you're talking about the management of the product flow of products here, if you're having like, if you capture a good deal of the sites, all the ones in the cities, you're having a very large part of the product flow. So I'm not saying the remote ones are not important, but I'm saying that even if you have all the ones where you can capture the information, you're having a very large control of the product flow. So anyway, yeah, can you take this one? I can take the next question while I do that. I'm just showing the word of the day on the screen. Can anybody, can everybody see that? Yes, it's there. All right. So the word of the day is canteen. I know that's probably been the most asked question so far today. So there you have it. But the other question, Pair, I think it's more, it's a broader question. And I think it's very important. And I gave quite a long answer in the Slack channel. So then I'll give it to you, but I can comment on it afterwards as well. But the question was from Alex Watila asking, some of the features for facility are overlapping between what Madexis can do and what DHS2 can do. What can we say to that? So I posted a long answer, a long reply, which I can comment on as well here. But I wanted to just have your thoughts here as well, as you did share some of these aspects in your presentation. Okay. Well, I'll say first of all, when you do that, actually implementations, you have to of course, watch out. I mean, you don't want to give the users double work. That's the last thing you want to do. Don't do that. So what you do is you would take care that a given data only is put in into one of the applications. And if you have an integration of DHS2, well, you might as well get it from DHS2. You definitely don't want the users to experience that they have to put the same data in two places. That would not be good. But that is fixable. I think that can be worked on. I don't know what, maybe what's your comment to the same? I had quite a few points. And I think it goes back to one of our first discussions we had, Per. Now this relates to the initial assessment. And for Mali specifically then, the data that you were looking to access, the stock data from facilities was already being entered in DHS2. The facilities and devices, users were already set up and using the system. The entire implementation, infrastructure, human capacity support was already in place. So the idea of implementing the Medexa system at a level, collecting the same data, which was already digitized and readily available, was already present. So I think that was one of the starting points that I think we had when discussing Mali is, again, back to your first point here, there's no need to develop then a parallel system with a parallel app, maybe device structure to collect the data that's already available there. So I think that was one of the key starting points in the assessment phase is to see what is the value added of using Medexa's ELMIS at facility level versus integrating with the data already being collected by DHS2. I think that was the key starting point. There's a few other things we can also elaborate on and discuss further, but I think that was the main aspect to consider. Another point that I also mentioned is that if it is a better solution, if given the requirements that the country has for their solution that implementing the ELMIS or ERP down to facility, both in terms of cost and sustainability, functionality and so on. If it is best suited to have that end-to-end solution, I mean by all means we support that. We're not by any means promoting this as the only option. We're trying to promote a solution that is implementable, realistic, sustainable, cost-effective. So there are all these advantages again that I mentioned in the beginning in the overview presentation where we look to maximize the use of DHS2, the existing implementations of DHS2, looking for these synergies to use a buzzword, and then how can we add to this ELMIS landscape? We're not proposing this as the only solution. I'll stop there. I think George, if I saw you, maybe had a comment for this as well. Maybe I lost George. Maybe he's muted. So yeah, it's a unique opportunity. Maybe George, are you there? Yeah, I think while we wait for George's comment, we can maybe move on to the next question or he can also reply on Slack. A specific indexes question then, Per, if an entity wishes to install Medexus on a server premise rather than in the cloud, is it possible? Yes, it's possible. We know that the ministers of health of various countries, they prefer often to have it on their own machine or their own server. We would, though, say that it's more manageable and easier to maintain if it can stay in the cloud. But yes, it's an option. But there's a number of good reasons actually for having it in the cloud. It is easier, substantially easier to maintain this whole thing around management and backup and all sorts of things, which are big advantages if it can stay in the cloud. But yes, you can have it on the whole server. It's possible. So we've got George back.  Yeah, thank you. Can you hear me now? Yes, we hear you George. Okay, apparently you have to be unmuted by the host every time. I just wanted to comment on the question about duplicating of data, which is very close to my heart. My clear advice on that is to avoid any duplication of data. So typically we see that despite Medex is keeping an exact record at the batch level of all the stock that is sent, the consignment sent from a warehouse to a facility that people are spending a lot of time recording the stock receipts at the facility level. So my advice is clearly, and that's our philosophy, core component of our philosophy is to at the facility level, to collect only the data that is available only at the facility level. And that is the stock on hand. And that is the monthly demand or the consumption, because that is not available in Medex or in any ERP system. But everything else like the stock that received or the request, everything else are clear recommendation. As you have seen Medex is a sophisticated ELMS system that is made for logistics. Keep it there. And this is by the way also a recommendation for the analytics. You can have some very simple dashboards that show tomorrow directly from the stock on hand from the consumption data in DHIS2. But anything else we recommend build the dashboard or use a dashboard in Medex and we are looking into ways of like maybe pushing scheduled reports to DHIS2. But this is a very, really an excellent point. We really are very keen on trying to duplicate any data. We really want to help workers to focus on providing services and collecting only the essential data that is otherwise not available. Thank you. Okay. All right. Thanks for that, George. I think that's also related to a point that we had another question from it was Gia Kani. I also sent a extensive, a long reply in the channel. Why we should not use DHIS2 for end-to-end supply chain management? Why do we need an LMIS at all? I think George touched on a few of those points there. We're focusing on this facility level and then relying on a dedicated supply chain management LMIS system to do all of this more extensive management of the supply. We're really looking to capture essential data at consumption level and not overstressing the DHIS2 system with features that it's not built or capable to manage. And I have some of those listed and we'll get into those also throughout the week. I think, I guess, in that context, what we mentioned is that there's several connections that people have done quite a lot to try to build things around DHIS2 to do this job because DHIS2 is out there. But I think it's been a general experience that it's not made for those transactional things. It's a data-catholic tool, right? So that's, yeah, it just doesn't have exactly that. Whereas you have a tool that's made for transactional work for the supply chain, it can do some other things. So integration is simply probably a better solution somehow. All right, I have another two questions for you, Per here. Maybe short answer. One of them is minimum requirements for the Medexus application and device compatibility. Mineral requirements, okay. So it's built for really low resource setting. So you can run it on an Android phone, quite totally normal Android phone. No problem. We'll do that. Of course, it's what we call the Medexus Lite version. There are limits. It's nothing else by the screen and by the data you want to move, but you can run it on an Android phone, the one used every day by millions of people. So that's, you can say that's a mineral requirement. There's certainly advanced stuff, if you need that, then you actually have to have a good functioning laptop. But it's a choice both ways goes. You said the other question was? You're on my mind, yeah. George has a comment, but let me just ask a quick follow-up. Does it also support bring your own device or do you need to have a device managed by the organization or agency?  You hear, you snap, yeah. That was another question. Over to you, George. You have another comment. Yes, thank you. I just wanted to briefly comment on the question why DHIS2 at a strategic level decided not to build another end-to-end ELMS. And there are several reasons. So one was already indicated or implied. DHIS2 has very specific data model, and it's not built for logistics management information system. It's built as an HMIS system. And we don't have time for details, but it's not really adapted to an LMIS. The second reason is we would just be reinventing the wheel. There's already excellent systems like M-Supply, Medexys, others that are recommended. Brenno has presented the guideline. And the third reason is personally I have worked in Excel. I have worked in an organization spending five years and developing a bespoke system from the scratch. It's going to take five years realistically. Huge amount of money and developers. You will need a whole team. So why should the University of Oslo, the HIST Center, invest in that where there's already several tools? And maybe the last point, I think Priya mentioned that people have already tried to develop a DHIS2 to make an LMS out of it. I think that the complexity of an LMS is totally underestimated. People think it is easy. It is easy just to report stuff, but it actually it's really complicated and it would take a huge, huge effort. So we definitely not going to go there. Thank you. Great. Thanks a lot for that, George. I think a lot of those comments, as he said, some of it was implied in the first two presentations both by Mike and myself on the DHIS2 landscape and the LMS overview. I've included quite a few of those in the Slack channel, but feel free to come with these questions again. I think understanding the general approach that we're trying to build something that adds to the landscape, adds to an existing gap, doesn't overlap with other solutions and can be implemented and sustainable. If you're simply checking off and ticking off the box of features, stock reporting at facility, short DHIS2 LMS and all of the different tools will check that box. But again, we're looking to add to a real-world implementation scenario. And I think the Mali example is a good example of that as Para has shown. And the discussion that we went into is how can this adapt to this existing context? They're already collecting data in DHIS2. The data is there. What is the need to implement a parallel solution to collect something that requires this integration? So it's the question of, again, level of effort for the value added to the supply chain system. All right. I think this is good. I don't see any new questions for Medexas specifically.  We just have nine minutes to go or so. No, I just want to thank you for the opportunity. And then I'll ask you a question. So I send you the PowerPoint of what I do. I put it on the Slack, what I do. Yeah, you can share with me by email or Slack, and we'll upload it to the Share Drive. I'll show you a link to the Share Drive as well so you have access to all of the different resources. And I think all of the participants you should already have access to that. If you haven't seen it, we have the link in Slack as well. Okay. I wanted to also say that I think it's really great you're having so many participants. And I think there's so much opportunity, so much opportunity in getting these ELMS out there because just the pure value of the products going down those supply chains is very large. And that this is today still not quite under control. It's not good. And there's a huge potential in bringing this in savings, in the savings lives, and there's a lot to get there. So, yeah. Thank you for the initiative. Okay. Big thank you to Per. Thank you for the contributions. And we're looking forward. You're more than welcome to join with the other sessions as well. And we'll have this expert lounge open Q&A after the full day tomorrow. So, you're also welcome to join that and then people can connect bilaterally during that session. So, just to end for the day, a quick recap. We have this presentation on the HMIS and HIS landscape, so the information management landscape in a country where you have the health information and now the logistics data and how that can come together for triangulation for improving both supply chain management and health program management. With DHS2, you have an existing system that's been implemented at scale in up to 69 countries. And you have that references for that on the website of where it's been used. And then you already have it being used in many different ways to capture stock data. But then what George and I have really pushed is for using DHS2 in a best case or a best practice way that will support this integration that will maximize the existing DHS2 implementations, does not overuse the system or over stress what it's able to deliver, but rather fills a gap which is really digitizing last mile data. So, the first data mile at facility level. So, that's really the intention here is that we provide a solution that adds to the existing landscape in a very practical way. I think it's really, we push for this integration approach and there's a lot of implications and things to consider. It can be complex, but I think we have a good understanding from the start what the objectives are and we have this engagement from the technical teams on what can be achieved, aligning the workflows with the data flows and aligning the different stakeholders. There's a lot that can be gained. The presentation from pair, I think highlighted that in Mali and we have a few other examples that we can also point to. Where tomorrow we'll go more into the pure LMIS stock management in DHS2. So, the day will be dedicated really to that. Stock reporting, George McGuire will be leading those sessions providing both a demo and configuration of these different tools using DHS2. You can already go into the sandbox as I've already mentioned and test some of these things out. Try to use it with your mobile device if possible and that will really give you an idea of how it is to be in a facility and using this tool for stock data capture at that level. And then at the end of the day we'll have MSupply presenting their solution, their central LMIS tool and what their features include and implementation or integration example as well with DHS2. So, we'll be looking forward to that. And then at the end of the day, as I mentioned, we'll have a longer expert lounge where you can come with your questions, use case, and we'll give some extra time to engage with each of you. One last maybe comment, a general comment to the group. It's been really great to see so many people participating and connected. It's a partly diverse group. So, either you have from what we saw from the registrations, more of an LMIS supply team background and then you're maybe new to DHS2 or you have more of a DHS2 background. You've been working with some stock data but then this whole LMIS thing is partly new. So, we're trying to cater to both groups. You may fall out of these two groups. We're trying to cater to either the LMIS or DHS2. So, one or another topic may be a bit boring to you when we're repeating things that are part of your area of expertise. But bear with us. We're trying to make sure that there's a global and holistic understanding from all of these groups on how these features can be best implemented to support the LMIS landscape and the information management landscape in your contexts. All right. So, without any more delays, I just want to thank everybody for participating. Thank you for today and welcome back tomorrow at 10 a.m. when we continue on day two of this DHS2 LMIS Academy. If anybody wants to stay connected beyond this time, George and I are available and maybe a few others should take some more questions. So, stay connected and ask me questions.


Good morning, welcome to CMC Markets on Friday the 28th of January 2022 and this quick look ahead at the week beginning at the 31st of January. With me, Michael Houston, and it's certainly been another volatile, tempestuous week. You can run out of adjectives to describe some of the moves that we've seen this week. In fact, this month, if we look at the way equity markets have moved, there has been evidence of some divergence between what US markets have been doing. This week we've seen US markets hit seven month lows. On Monday we saw the FTSE 100 hit a one month low. Yesterday FTSE 100 was able to reverse all of its losses for the week. But has now since then slipped back into negative territory for the week as it closed the end of last week. Around about 7500 and it's trading slightly below that now. So there's an awful lot for markets and investors to consider obviously there's tensions on the Russia-Ukraine border. At the moment they continue to simmer ever so slightly underneath the surface, helping to push Brent crude prices up to $91 a barrel. Earlier this week we've got, or we've had, the US Federal Reserve latest meeting where, despite the fact that the Fed didn't announce any changes to its current program of asset purchases, it will continue to add to its balance sheet all the way till March. But the fallout from Powell's press conference was quite something to behold. To be quite honest, where do you start? No surprises around the statement, decision-keep, monetary policy on hold. Press conference really saw the heat quickly come out of the mid-week rally. Certainly if we look at the daily candles on this FSC 100 chart, you can certainly see it's been a week of two-halves, very sharp declines in the first part of the week, consolidation. And then Wednesday, Thursday, we saw a move higher. Let's start with the NASDAQ because I think the NASDAQ is particularly interesting, given how we started the week and where we are now.  We pretty much reversed all of that to actually close modestly higher on the day. And on the Tuesday we came crashing lower again. Wednesday up, making high for the week, and then came crashing back down the following day. I mean, this sort of volatility, these sort of price swings. On successive days, I might add, we haven't seen this sort of volatility on US markets. I'm reliably informed, according to Bloomberg, since the 1980s, and that is really quite something. If we look at US short-term rates, we can also see that the two-year yield has gone this week alone from just below 1% to 1.2%. And this month alone has gone from 0.7% to 1.2%. So you've gone 50 basis points in the space of a month, which when you consider for how long the two-year yields were doing nothing for most of last year, it's quite something when you look at that chart. So I think what Powell was particularly good at doing on Wednesday was keeping his options open. We are going to get a rate hike in March. That much seems almost certain. He didn't rule out a 50 basis point rate hike, but then why would he? He didn't rule out a 1% rate hike either, and he's not going to do that. He passed up the opportunity to rule out any possibility. The good thing about that is it keeps the Fed's options open and rule nothing out, rule nothing in. It wasn't the messages that markets wanted to hear. And in essence, it was the Fed saying to markets, the days of hand-holding are over. The priority now is inflation, and you better get used to it. And that's why we're seeing the moves that we've been seeing notably in bond markets, but less so on the long end. If we look at, say for example, the US 10-year, which used to be very representative of what the Federal Reserve was looking to do over the course of the past few days, we've hit loads of 1.9%, but we weren't able to move above the highs that we saw earlier this month. So even though the Fed was very, very hawkish and people are talking about five rate hikes this year, six rate hikes, seven, what have you, the US 10-year really wasn't affected by any of that. All the movement was in the short end. That's flattening the curve. So long-term interest rate expectations haven't really changed that much. It's just really a question of how quickly the Fed is going to normalise monetary policy going forward. And I think that's a harder thing, I think, for markets to get their heads around. They're not worried about the fact that they're going to get six or seven rate hikes. They're worried about the timeframe of when they're going to get them. I myself think that it's highly unlikely that the Fed will be able to do anywhere near as many as the markets are currently pricing in. But that's just me. So we've had the biggest one-day jump in the two-year yield since March 2020, and yet the 10-year has barely moved. So really, where does that leave us? Well, if we look at this move in the two-year, I mean, it does look really, really stark. But now look at it over five years. And then suddenly it doesn't look as stark as perhaps maybe it was. I mean, if you look at two-year rates in 2018, they're at 3%, or just below. Now they're at 1.2%. So even with rates currently as they are, they are still below the levels that were pre-pandemic. So I think there's an element of markets freaking out. The bigger question is whether or not it's justified in the price action. On a technical basis, some very important things have happened over the course of the past few days. For a start, the known stack is below its 200-day moving average, and the 50-day moving average is starting to roll over. So that in itself is significant. It means that the bias has shifted from buying the dip to selling the rip or selling the rally. That for me I think makes it very, very difficult to articulate a case for continuing to buy the dip when it comes to US markets. We could certainly see a move back to 15,000 on the 200-day moving average. And even with the decent numbers that we've seen this week from the likes of Apple, Microsoft, and obviously we've got Amazon and Alphabet next week, it's going to be very, very difficult to make a case for new record highs for the NASDAQ if the rate trajectory plays out as markets are currently pricing. If we look at the S&P 500, again, it's a similar sort of story. What's significant about this though is that the 200-day moving average is currently acting as resistance when any moves higher. And again, we've hit a seven-month low on the S&P. We've seen quite a bit of volatility. We haven't taken out those seven-month lows despite all of this week's volatility. And even though we've made a new high on the week, these long shadows point to huge degrees of uncertainty as to the future direction of US equity markets. The fact that you're getting these very strong moves to the highs and the lows, but when you strip out the overall direction, there really isn't that much of a change, suggests that there's an awful lot of uncertainty out there. So really, you've got to trade the markets based on that, which means that this level here, the 200-day moving average, which managed to hold the rebound that we saw on Wednesday, is going to be a very key level going forward when it comes to the future direction of US markets. If we look at the Dow, we've got a similar sort of playbook playing out, again, the 200-day moving average. So the 200-day moving average is going to be an area that I'm going to keep my eye out for on any moves higher. As we look at the DAX, the DAX again, 200-day moving average, is continuing to find itself limited by that. What's concerning about this more than anything else is these are starting to roll over a little bit the 50-day, and that suggests that sentiment is starting to turn a little bit negative, but on the plus side, this 15,000-area still looks pretty solid, even allowing for the intraday penetrations lower that we've seen over the course of the past six to seven months. We've seen it here, we've seen it here, we've seen it here. What's important is that we haven't closed below it, and we've held above it here and here. So what we could see is just further volatility within a sideways range, and that's something that could also play out when it comes to the NASDAQ as well. For C100, still looking fairly positive, yes, we broke below 7,400, which obviously was very unwelcome given the fact that we fell to a one-month low, but what was important was that we didn't actually fall significantly below the 200-day moving average, or this broader, stronger support around about here, and now we're back within touching distance of 7,600. Of all of the indexes that we've looked at over the course of this little discussion, is probably most constructive in terms of further upside on the FTSE 100. Why? Well, simply because we haven't made new record highs on it. It is undervalued relative to its peers, and despite all of the concerns about politics in the UK, it is very much an internationally focused index. So when people talk about political risk potentially weighing on UK assets, I tend to park that because that generally tends to be pushing a political narrative and not a financial mark, it's one. And I've got very little time for political narratives when it comes to talking about financial markets. So that's where we are with respect to the FTSE. It still looks constructive, and as such, I see no reason to change my longer term view on that. The dollar's had a good week. It's had an absolute ripper of a week. Posted highest level since June 2020 on the back of the hawkish narrative from Powell's press conference. That's pushed Eurodollar lower. So Eurodollar breaking down the next target on this particular chart here. Well, the next one's 108. Obviously, looking at it from a slightly shorter term point of view, you've got to look at 111 initially. It was around number and then 110. But this breakdown of this trend line here and the breakthrough the lows and this low here in June 2020 suggests that we could well see further losses for the Euro back towards 111 and 110 over the course of the next few sessions. And we do have the European Central Bank rate meeting next week as well. And obviously we have, we have UK, EU flash CPI for January. And that could feed into the narrative that the ECB is not going to be raising rates this year at all, because their argument is that inflation in the Euro area is transitory. And legs significantly behind that of the US. Certainly the first argument I'm struggling with the second argument not so much. Euro sterling continuing to track lower watching paint dry.  But ultimately I still expect that to continue to drift lower. The big level on the upside and only rebounds is 84, 84, 20. So you need to pay attention to that. But certainly in terms of the overall trend, we still remain very much towards the downside. And I really don't expect that to change anytime soon. So very much sell the rally type moves there cable continues to break down. This is a bit of a struggle. This is, this is a little bit of a kin to try to catch a falling knife, which I would discourage anyone to do. Metaphorically and literally, we have continued to drift down. We're now below the 50 day moving average, which is not what I wanted to see below 134 20. That keeps the pressure on the downside, particularly when the dollar is as strong as it is. Obviously we've got the Bank of England meeting coming up this week. And we've also got the European Central Bank rate meeting this week. So those two central bank meetings could have a very big part to play. Not only on the direction of Euro dollar and cable, but euro sterling as well. And I think now will be a good opportunity to talk about those two because I think when we're talking about the Bank of England, we really do need to be cognizant of the fact that they are very unreliable when it comes to forward guidance. And we also need to remember that they did, they did raise the base rate by 15 basis points in December by an 8 to 1 majority, which was a little bit of a surprise given the fact that they chose not to act by a 7 to majority in November. However, like the Fed, it does appear to have been a significant shift in mindset from where they were only a few weeks before. So we can only presume on what prompted the change of heart. I think obviously it's a welcome change from the group think narrative that appears to be becoming increasingly embedded in the economic discourse right now. I think two interventions may well have been crucial in changing the Bank of England's mind. Firstly, the IMF urging the central bank to get on with it. It's surprising it took the IMF to get them to do that and not an inflation rate of an excess of 5%. There you go. This is where we are. We're now looking at RPI at 7.5%, CPI at 5.4% with an expectation on the part of the Bank of England that we're going to hit 6% by April. So this could see another rate rise this week by 25 basis points to 0.5%. Now, you're going to get the howls of anguish from people who say that this won't do anything to curtail the effective supply chain disruptions, blah, blah, blah. That completely misses the point. You can't keep interest rates at current levels forever. I'm not suggesting for one moment that we should be ripping interest rates higher back to 2%, 3% or 4%. And I don't think anyone else is, but you can't leave them where they are and completely ignore the inflation genie indefinitely. You have to try and start to normalize to a more reasonable level of rates at 0.25%. It's not priced in at the moment. The markets are already pricing in higher rates. So a 25 basis point rate hike this week will merely put market rates or base rate where the markets are already pricing it. So really, it's a question of whether or not Andrew Bailey, as governor on the Bank of England, can start confronting the risks that more embedded inflation will have on the UK economy going forward. Now, he's gone on the record as saying that it isn't his job to steer financial markets on interest rates. Sorry, mate. It is. That is your job. It's in your job description. It's your job to communicate to financial markets. And the sooner you get your head around that, the better. The Federal Reserve do it very, very well. ECB probably not so much. But ultimately, he needs to restore the Bank of England's credibility in the eyes of the financial markets. So this week would be another opportunity for him to try and rebuild that credibility. So 25 basis points we could well see come the 3rd of February. Later on, we get the European Central Bank rate meeting as well. And Madame Lagarde will have to defend why she thinks the ECB should keep interest rates currently where they are. So we have 5% free CPI. Now, this week's CPI numbers flash CPI numbers out of the EU could give her cover to basically continue to pedal that narrative because there is an expectation that the annualized numbers for January will fall from 5% in December to 4% in January. The reason for that is because of the one-off effects from last year, which pushed German CPI numbers up by over 2% on the month. And the reason for that was a raft of measures and the reintroduction of VAT after being emergency cut in the wake of the first lockdown, as well as various climate change measures or taxes that boosted German CPI in January. So EU CPI was at a much higher level a year ago than pretty much everyone else. So that means that the jump to this year is likely to be lower in relative terms. Obviously, it will allow the ECB to pedal the narrative that inflationary pressure is transitory. So if you've got import prices or PPI in the various Eurozone countries trending at 25, 30 and 35%, I think everyone knows that's a rather fallacious argument. No change is expected from the ECB, though we could get some indications as to whether or not they could increase their asset purchase program while at the same time is winding down their PEP program. Because their PEP program is due to roll off in March. So we could get some messaging around that and whether it will look at increasing its PEP program to compensate. And that's currently running at 20 billion euros a month. One other thing to keep an eye out for will be how new Bundesbank President Jocham Nagel basically influences the debate over inflation risk, given his warning last month that the ECB needed to be vigilant, given his concern that inflation risks are very much elevated to the upside. So we've got ECB, we've got Bank of England, we've also got US non-farm payrolls. Probably I think the most surprising thing about the payrolls numbers that we've seen in recent months is headline numbers have been very, very weak. The last two months in December we saw 199,000 jobs added, which was well below the 450,000 consensus, and it was also well below the ADP report of 807,000. So in both November and December the number of jobs added has been disappointing, which would suggest to me that even with US employers having to pay up to get people back into the workforce, workers don't appear to be in a hurry to return despite over 10 million vacancies and only 3 million fewer workers. So there appears to be an awful lot more caution about consensus estimates now having been burnt two months in a row. Expectations for the January report for 178,000 jobs to be added and the unemployment rate to remain steady at 3.9%. Again, I'll be keeping an eye out for wages because they were much more resilient in December, they rose 4.7%, which was well above the expectations of 4.2%. So certainly I think wage pressure, a decent wages number could well reinforce the hawkish narrative that we heard from Powell earlier this week. On the company's front, we've got two or three that I've got my particular eye out for, Shell being one of them, Royal Dutch Shell soon to become just Shell. Their numbers in Q3 were a little bit disappointing. If we look at this chart here, we can still see that we're still well below the levels we were in 2020. So there's certainly plenty more upside to go. There's certainly been one of the early winners so far this year with oil and gas prices where they are. And I think that's likely to continue. But I think more than anything, apart from the actual numbers themselves, in Q3 we got calls for the company's breakup from activist investor Dan Loeb's third point group. He appears to be frustrated with respect to the underperformance of the business. And to be quite honest, when you look at that share price chart, it's not really hard to see why, when you look at where they were and where they are. Now obviously they've had to write off an awful lot of assets over the course of the past two years. They've also sold off its Permian Basin business for $9.5 billion. And it'll be really, I think, interesting as to whether or not they've been able to rebound from the disruptions from Hurricane Ida, which cost the business $400 million, as well as higher costs elsewhere. With natural gas prices at record highs in Europe, multi-year highs in the US, shareholders appear to think the company should be doing better. And I would agree with that they should be. Shell management said they expected to see a much better performance in Q4. They better be right. Otherwise we could see third point making a lot more noise than they were in Q3 and could well ramp up pressure on senior management. Shell's Q4 numbers on the third of Feb. Going to be a busy day on the third of Feb Thursday with Bank of England and ECB. So certainly enough to keep everybody's hands full. And then we've got BT Group, another perennial under Performa. Now, since BT reported back in November, the shares have done pretty good. They've done pretty well, pretty good. That's a terrible adjective. They've done pretty well. But they're still below the levels that were in June last year. It's delivered on its cost-saving programs ahead of schedule. Q2 EBITDA came in better than expected. The first half revenues came in at $10.3 billion. Their open reach fiber to premises network has now reached $6 million premises. Bill costs are starting to come down as they become much more efficient in rolling out. And there's been renewed chatter about selling off open reach, which is starting to get a little bit boring and a little bit tiresome. You don't sell off your best performing business. But what you do do is sell off the bits of the business that are low margin and really don't offer an awful lot of value. And that's where BT does appear to be making progress. There does appear to be an agreement in place to sell the BT Sport Channel for around 580 million pounds. Negotiations here are still ongoing. There is interest from other parties. And it'll be very interesting to see whether or not those numbers have been firmed up and they're able to offload that because that is a very deep hole in terms of trying to maintain subscribers at the same time as keeping people hooked. And as we saw from Netflix's results earlier this week, margins in that business aren't getting any easier to maintain. So I think for BT to focus on what it's good at and to leave broadcasting to somebody else is probably the best way forward. So that's BT Sport or BT rather. We've also got Amazon and Alphabet. And Microsoft numbers earlier this week were very good. Azure posted some fairly decent numbers. And again with Amazon they have underperformed considerably over the course of past month or so. Quite a bit lower than they were. And more importantly they've moved below this key support level here. Their costs have gone up hugely. They have been one of the key winners of the pandemic but their costs have gone up massively. I think when we look at Amazon we want to look at their cloud business, web services as a bright spot in Q3. Revenues came in at $16.1 billion and they've been increasing quarter on quarter. They're obviously having to face increased competition from the likes of Microsoft and Alphabet who are also reporting this week. But in terms of Q4 we should see much higher sales. Christmas, New Year, so Thanksgiving and Christmas tends to be a really strong quarter for Amazon in the same way that it is for Apple. So we're expecting to see sales in the region of between $130 billion to $140 billion. But we also need to be cognizant that costs will be an awful lot higher as well. And they warned about that in Q3. They said they're going to be spending an extra $4 billion in this quarter on additional costs. So there's a possibility we might not even see the company make a profit in Q4. And I think that's one of the reasons why the shares have struggled since November. Annual expenses could be in the region of $20 billion and they were originally slated to be at $12 billion at the beginning of the year. Nonetheless, should still be a fairly decent year for Amazon. The bigger question I think for me is whether or not it'll be enough to prevent further declines in the share price. And a similar sort of story for Alphabet, Google. I've seen a similar breakdown in the share price there. For similar reasons really, total revenues have been strong over the course of the past few months. The change in the privacy changes, Google was able to shrug off from Apple, largely because of the fact that most of its business comes from its Android operating system. Revenues from YouTube did see a modest drag because of the iOS changes, but advertising continues to be their key source of revenues coming in well in excess of $50 billion in the last quarter. So still expected to see some fairly decent numbers from Alphabet. Again, keep an eye on costs. It's a recurring theme for a lot of companies. Shouldn't be a big issue for Alphabet, but you never know. So again here, I think there's going to be, there's a good chance now that below the 200 day moving average, we could see further weakness in the share price there. So that I think you'll find is pretty much it for this week. I've probably gone on for a lot longer than I intended to. But don't forget, we've also got the non-farm payrolls webinar on Friday, Friday the 4th of February. So please feel free to join me for that. And I'll cover the numbers as they break as well as take you through the various key chart points of all the key instruments. And in the meantime, I wish you all a great weekend and see you all same time, same place next week.