Empower Your Business with the Pipeline Integrity Management System for Technical Support

How to create outlook signature

hello everyone welcome to our section data integration integration and effectiveness of pipeline integrity management proverbs which will be part of the integrity program of hue pipeline in 2021 organized by instituto brasileiro de petrolu ebp let me introduce myself my name is ellen costenaro i am a chemical engineer with phd in electrochemical by university of sao paulo i am integrity engineer at congas working with steel pipelining defects analysis inspections pipeline repair and cathodic protection i want to thank ebp for inviting me to mediate this section it's a great pleasure for me to be here so in this section uh in this section we are going to have three lectures one followed by another and the questions will be made in the end of these three lectures i kindly ask you if it's possible to send us your question in english by the chat these speakers have about 20 to 10 minutes and each one 10 minutes each one and then 15 minutes for the four questions uh i also would like to introduce rodrigo solaris who are supporting me with the question rodrigo is a electrical engineer with mba in strategic management of production and mantis masters in electrical engineer in modeling and else of power system both by flumelands federal university rodrigo has solid professional experience in the area of maintenance of gas networks pipeline integrity and cathodic protection he is currently the integrity coordinator at transfortador associated tag so let's start now the first lecture is the title of the first lecture is why a remote monitoring system in the protection cathode this speaker is antonio orta costa he is head of asset integrity at net here it's a natural span group antonio has been working as industrial electronic engineers since 1986 in 1987 he joined catalana de gazillita siddhat current currently net here netergy group uh antonio antonio's member of cocor european committee for the study of corrosion and protection of pipes and pipeline pipeline system drinking water waste water gas and oil and representative of spanish guest association senior guest in the seo court board directors his member from the technical committee ctn 112 of iron ore corrosion and protection of metallic materials he is member of pipeline integrity working group of the spanish guest association sergey guess in this three four years of working life antonio was for ten years head of catholic protection department responsible for the implementation of a set pm maintenance management management system he was responsible for the implementation of the catholic protection remote management system netergy group which includes spain italy brazil mexico and colombia in 2018 he works in he worked in the implementation of dynamic maintenance in catholic protection in that year and now in this year he is the product owner for the implementation of dynamic maintenance in other maintenance activities such as leaky monetary emergency care maintenance of lng plants in atheia so antonio please the floor is yours thank you very much helen uh i read my presentation because my my english is a little corroded for this pandemia hello ladies and gentlemen i will talk about the reasons why remote motoring system is necessary in the cathodic protection maintenance the teacher has a question what happens to iron when it's corroded the student answered it's ugly that's true but maybe we have a leak in the pipeline and sometimes this is the reality i always tell my co-workers that our mission is neither catholic protection nor a remote monitoring system our aim is to safewater our pipelines against electrochemical corrosion the national group is a natural gas transmission and distribution company in spain in the map and in blue you can see the dispersion of our gas pipelines in the geography we have 8 000 kilometers of steel pipeline with cathode protection it is protected by 450 rectifiers 25 dc current returns 58 yes sorry to interrupt you but i think we cannot able to see your presentation no did you share it excuse me okay now what you're seeing sorry yes no no it's okay i i normally i use in our company the teams and the theme is the first time i use it sorry when introduction sorry we mean when we have 8 000 kilometers of steel pipeline with catalytic protection it is protected by 450 rectifiers 25 dc current returns 50 ac air wire and 70 000 control points all the rectifiers see the current and returns an ac air wire has a remote motoring device and 1 800 control points too from static maintenance to the dynamic mountains the normative says that every x-days the cathodic protection parameters must be measured and every hawaii week's other processing must be done but these standards are independent of the pipeline's characteristics and their particularities i think everybody agrees that a summary pipeline at 45 bar maximum operating pressure is not the same as a pipeline in a village at four bar maximum operational pressure is the same example as bicycles in the first one only the man's strength is taken to account static like the actual normative in the second one the man decides what is the best way to use his strength dynamic the future of maintenance the importance of the data and nakia we thought we need needed a parameter to measure the effectiveness of cathodic protection i think everyone agrees that traditional measurements are not enough for building an algorithm to respond to dynamic maintenance there before in 2009 we decided to implement a remote motoring system for catalytic protection cathode protection efficiency parameter this algorithm is based on the a time rule kati katie depends on four variables car r evaluates the pipeline's characteristic this parameter is a function of the published length i evaluates the cathodic rotation installation characteristics rectifiers the c current returns ac earth wire and control points k-rec evaluates the time the rectifier is in service and km evaluates the massive ramen's remote and technical monitoring the sum of therefore variables defines catie if cathy is above 75 points the effectiveness of the cathode protection is adequate if cate is between 61 and 75 points the qatari protection so maybe have a problem and if cathy is below 16 points houston will have a serious problem thank you very much any questions antonio the questions we're going to to have in the end of our three lectures okay now now we are going to the the second lecture of this section uh the title is using software for online integrity management uh it will be presented by alexandre zevolt who is a technical consultant at johns petrol alexandre is pipeline integrity engineer with 15 years of experience with pipelines alexander leads the management stress corrosion braking in within trans petrol and also works with defect analysis and pipeline repairs he has a strong background in pipelining hydraulics hydrostatic tests location class and field assistance recently alexandria has also been working a project for data integration and integrity management software alisha and you have the floor hello ellen thank you so i'll be talking today about the use of software tools for integrity management uh in the view of a pipeline operator from transparent point of view so i would like to kick off by saying that trump's petro is recently spending a lot of time and effort uh in implementing a solution for integrity management that is a bundle of software tools that interconnected will help our integrity management program we can call it a digital transformation process within transparent but it's from digital to that we were already digital since they're already around 2000 and now we're it's a step further into a digital transformation so what i can bring to the audience today is uh is the context in which an integrity management software can assist the integrity management program and integrity management engineers so during this process our team has developed many insights and the foundational concepts that helped us build this project so that's what i'm trying to bring for the audience today so the starting point of this uh this process is the is the four step process for the integrity management program like the pdsca plan do check and act process we have a similar process for the pipeline integrity management which is the cycle i'm showing here it all starts with the data integration so the integration is the starting point and if you have a good data and you can integrate them you can perform a risk assessment and once you perform a risk assessment you can follow follow on and build your integrity assessment and next to the integrity assessment you go to the field actions and implement those actions that those assessment has defined previously so this is basically how i see an integrity management software working so you can see here the gears and the driver gear is data integration the integration moves the risk assessment in which moves the integrity assessment and the the integrity management software help these gears work with less friction let's say so you can ask me uh what is the great deal about data integration well i can say that it's a great challenge if you say you can see here in this in this photo here this could be the the integrity the pipeline integrity engineer looking at different data sources that he receives from the field these data sources come in different references different formats and he's trying to to recognize what the data is telling him and he's trying to come up with well-informed decisions so here you can see that different references uh from different sources of data for example the right-of-way people the writer for inspection uses the right-of-way posts as a reference on the other hand the inline inspection can use the automator of the the tool as a reference and other inspections can use the the very coordinates from the geographical reference so how can you couple and integrate all these data that comes in different references you have you have you also have in the organization different sources you have your your your data your uh your enterprise resource planning some organization use the the resource planning as a tool for the integration you also have your electronic document management system as a source and also your gis i would also mention that some companies still have electronic files and hard copies as a reference but i i'm presuming here that it's not ideal for the implementation of integrity management software and this software or this set of tools also have to show the specialist different formats this guy needs to see data in maps in graphs and in tables okay and he's thinking information integration is a key component for managing system integrity this is a bold statement from this standard here okay so what do we need to start doing this we need good data so in this screen i'm showing a scale that our team has developed to measure the level of maturity that we have or you have each one of you can apply this to your team or to your process how mature is the data you're generating so on the first level that your data is complete is verified and is approved on the second level your data is also available on a corporate system why is that important because then you have revision control and your document is trackable on the third level your data is standardized so every document that is generated with the same results are always on the same format why is that important because the automatic extract transferring load processes are automatic the fourth level will be if this data is geo reference then you can put it on a map and you can cross them with all other sources on a single reference and the fifth level of maturity would be if that that data is integrated across all the software you have working in your organization so if the inspection is recorded on one system but the integrity engineer needed needs that data in another system the systems are seamlessly transferring data without manipulation so we have internally we consider that the fourth level of maturity is when we would be ready to implement an integrity management software that's how we need to be mature about our data and in the context of an integrity management program we consider there are software tools a software tool needs to have a certain set of characteristics well the first one would be that the database is unique so all analysis you name it ili analysis risk external corrosion all are collecting data from a single source so that's uh that assures lower effort for that integration and less human error in the manipulation of this data the third characteristic is be gel referenced i remember the first time i saw google worth working and we cannot go back to how it was before that our data is geo-referenced we can see it on maps tables and graphs uh the fourth characteristic it would be to the system or the software to be connected and that is connected to other corporate systems interconnected within our organization the fifth characteristic would be to generate business intelligence panels like this one for example and if it's connected it's it can generate online bi panels that has much value to stakeholders and the sixth characteristic and i believe is this is the most important for the integrity engineer is that the system to be customizable because every company has its own way or its particularities as how you assess your integrity and your solution needs to be molded to that must be customizable and the values you get to the stakeholders are fast response and timely information both your external clients your internal clients give much value to that you will also have standardized results and you'll be ready for whatever comes next i've heard about uh big data or artificial intelligence mr hermann rosen was talking about a little bit about that i don't know what's coming maybe it's coming but if you're not in this maturity level within your integrity management program you will not be ready and of course when you're going to implement such an integrity management management software or bundle of software you have to overcome some hurdles right so i've listed here five steps for the implementation first ones are hardware and software i would point out that the most important feature is that whatever set of solutions you define you have don't don't forget about connecting every software that you have working together for integrity management program connection is the great word here third one will be data then you can refer to the maturity level i've already discussed and of course a great initial effort will have to be uh put on on place because it's a huge amount of of data that you're gonna need and then you're going to need documents of your pipeline uh it seems obvious but it's not triggered to do that to to take documents from the 70s the 80s and digitalize and register on your database it is a great initial effort then you then comes people right so your colleagues your stakeholders your clients they have to be with you they have to be on board they have to think that this is a good solution that will improve the company so and you also need sponsorship from your management okay this is very important for the implementation and then of course training we actually are in this point here on our solution implementation on training a big amount of training is required and i'm seeing that everyone has its agenda full and you still have to put on a lot of training so this is a very challenging step here and the fifth and most times forgetting step is the workflow uh if you do not define workflows that puts this integrity management software or solution as you name it within your organization and workflow making this solution part of the routine within your procedures in a standardized manner i think that this software will fade out and maybe in some time will not be that much used anymore i guess all the audience have been part of projects uh that you have invested a lot of financial effort a software and maybe two or three years after that the software is no longer in use no one trusts the software so i think that this last step of putting the software into the workflow of your organization is key to to assure a long-term use of the software and and make the the best use of the solution okay so as a cool as concluding remarks i would say that uh an ims uh integrity measurement software of course can bring benefits to an organization never forget that it has to be integrated with all other corporate systems that you have and it's important also to align expectations both from the management and both from your colleagues to know that the software alone will not assure pipeline integrity it's a tool it's one of the tools you have and the key component that will help pipeline integrity is data good data okay the maturity of your data will be fundamental on the assurance of pipeline integrity uh another aspect that is important is engaging people that will will be using the software will will be migrating from one set of tools to another set of tools a new set of tools and for that it's important to define these workflows to that can be responsible for this active use of this software in the long run okay so with that i'll conclude my presentation and go back to uh thank you very much thank you alexandrine and the third and last lecture of this section is data integration for risk analysis in integrity management which will be presented by marcus bartelotti marcus is tbg technical consultant he's a mechanical engineer from federer university of bernardo graduated 1997. he has 24 years of experience in the design construction inspection maintenance and integrity assessment of transportation pipelines since 2006 he has been working for tbg owner and operator of the of the bolivia brazil gas pipeline in brazilian territory working different activities of the pipeline integrity management marks please thank you ellen afternoon everyone can you see my screen yes okay well this presentation is based on tbg's experience in implementing a risk assessment system for the pipeline so when deciding to implement an integrity management program based on international best practices the road starts with the pipeline threats identification data gathering and risk assessment at this stage it's very tempting to believe that buying an integrity software is the magic solution to this new management process so let's look at these three initial steps in its challenges first threat identification potential threats can be identified in international standards statistics and in the experience of subject matter experts a list of variables must be established their function is given information about the level of exposure the existing mitigations barriers and the resistance of the pipeline in an analogous way we must also identify those variables that represent the consequences of a pipeline failure then we start with the data gathering a subject that alexandre explained excellent previously data comes from all available sources design and construction documents inspection prevention and maintenance activities also from operation monitoring systems and from subject matter experts advancing technology is bringing new data rich sources for example regulatory agencies are providing shape files of authorized areas for mining exploration this gave us information on possible blasting activities close to the pipeline another technology our riding use is known as building footprint applying machine learning on satellite images it detects buildings and its geographic coordinates then with the help of gis tools we determine the distribution of buildings within the impact radios along the pipeline following a digital transformation process pbg initiated a right-of-way inspection project with drones again artificial intelligence over images identify elements in the right of way associated with risk variables the high resolution is such that it's capable for example to automatically identify power lines or damaged side marking and many other elements as all the generated information has geographic coordinates we can upload them to the risk assessment database talking about data integration increasingly data comes from different sources in different formats and again alexandria presented it greatly before i i want to just add uh in in the stress that to complicate things a lot of data is generated with different positioning or mileage systems so to integrate data we found a few options put everything into spreadsheets or upload to an integrity software or to a server database or more recently to to the cloud in one hand it's required to ensure data integrity i mean data cannot be easily changed or lost on the other hand database should not be too complicated for uploading editing querying and sharing data with other systems tbd chose a pre-existing oracle database running on a corporate server this solution resolved the data integrity issue as well as the possibility of sharing with other systems to make it accessible to integrity engineers and technicians a web gis tool was developed it allows users with no knowledge of database or even gis to manage the risk data uploading editing can be done manually or in batch using csv spreadsheets query results are presented as tables or graphically in pipeline imagery once data management system was defined let's talk about the risk model selecting the risk model is maybe the main issue in the risk assessment implementation unfortunately the traditional risk assessment methods widely used in industry including oil and gas installations are not feasible for pipelines one of the main reasons is because pipelines are linear assets this means that variables change along the length of the pipeline so risk changes therefore other methods capable for dealing with these characteristics are needed a recently published report by femza the american regulator based on the evaluation on pipeline operators practices classified the used risk models into three types basically the relative index score model the quantitative model and the probabilistic the relative one widespread among operators has a qualitative or numerical input without units an index in other words the result are also numeric unit less a score algorithms basically consider the index of each variable multiplied by its relative weight moving to the quantitative model the input now has units so results are presented in absolute terms a great advantage is that this allows the comparison of results with other pipelines other industry segments and with acceptability criteria the algorithms are more sophisticated and flexible allowing to better represent threats mitigations and other variable behavior the probabilistic one is a type of quantitative model where that uncertainty is considered the probability distribution is uploaded instead of single value so the results will bring also the associated uncertainty tbg implemented a quantitative risk model once selected the risk model now is maybe the time to go to the market to find the software that best suits your needs sotpg acquire a desktop software license designed specifically for pipeline risk assessment not a generic risk assessment software it starts with the connection to the database then the quantitative model is configured in a way that it's fully verifiable and auditable and finally the model can be run obtaining results for probability consequence and risk as pipelines are linear assets its variables are rarely constant along the length so another task the software needs to perform is the dynamic segmentation which is processing data by dividing the pipeline into sections of similar characteristics a new segment is created when any variable changes only after the dynamic segmentation is concluded the risk calculations are executed so the results are presented in tables formats or graphs or it can be exported if you prefer to see in other formats like alignment sheets summarizing the pipeline risk assessment system set up by tbg is a system composed of three independent parts a risk software that runs a quantitative model connected to a server database which is uploaded through a web application all this work is only valid if it achieves the objectives of a risk assessment which are provide information for risk management and for decision making for resource allocations however other horizons we started to explore associating risk assessment with class location based on a study with gas pipelines designed and maintained under osmi b318 the iso 16708 proposed an acceptability criteria for the probability of failure based on the level of social risk in term in terms of class location diameter and operating pressure when the pipeline probability is above the limit for its class location then possible mitigations are evaluated in order to reduce it to an acceptable level using the mitigation module in the risk assessment software those simulations are performed without changing the database this can be applied for example two segments that had their class location increased by simulating mitigation this is possible to identify those measures that could provide acceptable risk levels in a higher class location well this is of course a compensated presentation of our recent experience on this matter and obviously the implementation of such a system is not a quick task to complete so i would like to leave you with this chinese proverb be not afraid of growing slowly be afraid only of standing still thank you very much thank you marcus now we have time for the questions we already have a one here for antonio antonio um question for you what is the main challenge in the implementation and maintenance of the cathodic protection remote monitoring system well the the main difference is to change the the maintenance static every month i go to epc to control every two months i go to a change to a dynamic maintenance and then we can to dedicate our our power in the pipelines and have a royalty problems sometimes we have pipelines in the middle of zones there are nutrients voltage lines of voltage and there aren't problems and the the static maintenance they say go every month it's not necessary if you can remote the system because you can control these pipelines from the the the web this is the difference to attack the problems in the pipelines we have a problems okay now for uh antonio we have another question for you but i'm going to ask now for alicia angry um alexandrine which what is the most difficult step in the implementation of an ims well thank you alan the most difficult step i would say i've presented five steps right but i would say that the most difficult is people of course within transparent we have outstanding integrity engineers i'm not so i'm not saying that that is the challenge the challenge is engaging these guys on a new solution so you have to abandon a way of doing your job and engage in a new way of course when transitioning the first steps will be slower not as efficient and you have to be a little bit patient so this transition is not very uh very trivial right and also everyone is busy it's difficult to to to guarantee let's say 100 hours of training on a new on a new tool uh so i would say that engaging people is is the is the most difficult of course the data i i told data is key and it's a lot of time consuming so maybe people in data these two stacks yes marcos for you what what type of risk assessment model would you recommend for an opera an operator that does not have a lot of data okay yes this is a this is a common question people tend to believe that because i don't have a lot of data i should start with a qualitative model or or a relative indexing model i i would recommend start with the model that will be able to give you the results in the format you need do not choose the model based on your data you have to choose the best model and then you have time to go behind the data remember risk assessment is a continuous improving process so that will be improving along the time if you don't if you think you don't have enough data now you will get it along the ears but if you start with uh with a not good model you will have problem in the future that's my my advice start with a quantitative model okay thank you now antonio back to you um what type of communication is used by this device we use uh uh normal communication by a mobile phone a several mobile phone it's a message data in in on time and i know uh there are sometimes uh in spain now but i remember in in in in mexico we have a problems in in in a source in mountain zones and we have a problem and we use acetyl communications is is normal and sometimes in spain we have a problems with uh a zone there are better coverage with one operator and we use two sims or two sims now since a multi-operator to guarantee the communications okay thank you antonio alexandrine i don't know if it was already answered by marcos let me change we will have a case study of the presented ims system in the next hill pipeline conference uh it's possible i can i cannot assure that right now we have not yet validated the the solution the set of software they have adopted but it's a possibility yeah okay and marcus another one for you how do you use international pipeline failure statistics for example eg ig in your risk assessment process yes statistics are are good uh information especially for calibrating your model as as as the model is a quantitative in in absolute terms in in the same units as the international statistics are presented we can compare our results with with other companies and of course with international statistics sorry i'm organizing here the questions a lot of questions for you another one so i'm back again to antonio antonio is there any intelligent system for calculating the kt parameter yes the parameter is calculated in the in the same system we use all the information and now we have a mobility system and when the operator is measuring encountering the parameter go up to the to the system to the web and every mode between in the sixth day of the month calculate the parameter katie for all the zones and this we analyze the this parameter in the in in in value valuetainment if last 12 months and we have uh in the in the web pro card in the in the web we have a c the the evolution of every zone and you can see if the problem is a communication with work broker if i have a problem with a rectifier stop it i [Music] and another problems but this calculated automatically okay thank you alexandrine what part of the scope on data integration trans-petra has already implemented and for which assets well our solution is based on up a softwares that uh interconnect with each other the main the main point is bring the data that is collected all along transparent pipeline in brazil and comes to our headquarters where the pipeline integrity analysis is performed so we have different tools working together to build that and you asked which assets right yes which assets yeah we have selected a couple of a pipeline just to start with and next year 2022 we'll be implementing in our all our transparent pipeline so the plan is to be completely integrated to until next year so we're gonna wait you in 2023 here yeah yeah back in 22 maybe yes marcus a message here for you congrats on your presentation no one is in doubt about the import importance of operational risk management in the pipeline industry why is this discipline still very little applied systematically what is missing oh i think that alexander have answered this before there is a integrity management risk assessment our management systems are always a new culture and always implementing a new culture is difficult change is difficult all the difficult related to any change are in the implementation of risk assessment and integrity management the the barriers to change to move to another way of working i think this is this is the main reason change culture in pipeline operators is not easy your your microphone is closed i'm sorry alice and another one for you um how can you integrate inline inspection data from different vendors into the ims do vendors need to deliver reports in a standard format do they accept to do it uh that's a good question we have we have been dealing with this issue manually i would say for the last years so we actually receive in different reports in a different format and one of these aspects that i mentioned about data maturity is the data to be repeatable or standardized right so the aim here is to be standardized and when you have to manipulate it manually you can it can lead to two errors human errors so actually we have been developing a a solution within transparent with our own resources to to deal with this problem on on a tool a tool developing within the spectrum but ideally the integrity management software would deal with that issue right if you if it can learn that different tools have different roles for each data you would be automatically importing this data so ideally you can [Music] you can you can inform your your for different formats for the ims and and you can keep the vendors with their standards okay if the your software allows it uh that's one solution i've i've i've seen that the vendors have trouble when you ask them to change the formats because they already have their system developed it takes an effort for them to modify it so it seems to me at first that is easier for the ims to adapt than the vendors to that but maybe in the near future we will have to go to the vendors and ask for any changes it's a possibility too okay uh let's do the last question for you antonio does net here experiment natural gas leaks if yes how do you monitor and manage that data i'm sorry i don't understand well if if you if you experiment if you if you have a natural gas leaks if yes how do you monitor and manage that data uh yes we have a a system we we monitor in all the the pipelines and we do the maintenance for detection the leaks uh in different you know all the country and now we are on a new a new project a product owner of the maintenance the dynamic maintenance because the rule say for example a we every two years to maintain the the pipelines in the zone in the in the urban zones every two years and it's possible you can build a new pipeline in january and in august you ought to to do the the maintenance on this pipeline it's not efficiency and we did we now we work in a new project uh for monitoring for the dynamic uh this pipeline but is in uh we begin this year and now they don't have a results concrete results we have in the middle of the project now okay thank you and marcus the last one for you we have now four minutes less than four minutes to finish we have a question here marcus i understand that the software you presented is only at risk if this is correct how do you manage it to integration with integrity assessment do you want to repeat max okay no i got it uh well as i said the the database is a is an open database so it's it's not difficult to share the results or or using the results of other systems if they are connected to the same uh company's database at the moment we didn't implement an integrity softwares as a whole we have only uh by now the risk assessment model running in the company but it's prepared to to to be connected with any other product since the database can be shared thank you so i i'm gonna finish with these questions because we are almost finishing our section i want to thank uh antonio alesian remarks thank you for invite me again to to mediate this section and we have more two sections today uh critical stages in implementation of new onshore pipelines in brazil and offshore gas production in brazil main current challenges thank you the audience thank you very much