Empower your export process with pipeline integrity data for Export

How to create outlook signature

so thanks everybody for joining in we're here to talk about the bridge both import and export lots of best practices I'm particularly excited about this presentation because it's actually a continuation of a four-part webinar series that I've been giving the last three months so this is the the final session we've been following data from the point of capture through verification validation storing in pcs reporting and now we're going to finish it up with the bridge so integrating that data with these other data sets or work order management systems or GIS so just a quick agenda I'm going to run through a recap of the first three sessions just so y'all everyone is on the same page of what we've been talking about we're gonna go over some bridge basics and then dig right into a ton of best practices for bridge imports exports automation we'll wrap up with some use cases that you guys can take home and apply in your environments so the first session which for the record all of the recordings of the previous three sessions are on our youtube channel or pushing a lot of content under your YouTube channel as much as possible so be sure to check those out be sure to check your inbox for notes from Leslie and Anna on our marketing team about when these webinars are going to be scheduled we're not only doing them on a software we're doing them on hardware we're doing them on the AC mitigation stuff that clay is talking about right now so stay tuned for that and keep checking it lon Duke seen here in his natural habitat was my co-panelists for the first presentation he went over some tips for doing accurate closed interval surveys every time so some pre assessment items like what type of pipe is it what's the coding are do I have all my current sources and a the bull do I need to do interruption when was it installed has there ever been a problem lots of things that you should know before you get out and do a closed interval survey so you're equipped to handle anything that comes at you he went through some best practices as well over how to set up your Allegro including some tips on how to stop your survey wire from breaking highlighted some lesser-known but critically important features and win over best practices for troubleshooting your survey while you're in the field in the second session we taught you how to import those closed interval surveys that he gathered into survey manager with the Allegro file formats or flat CSV files we went through some of the secret sauce that survey manager brings to the table by automatically lining up these day plots based on GPS and quickly highlighting issues like uh knitted skips so that they can be corrected before you commit it to your database record lots of tools and survey manager around finding spikes looking for exceptions and lots of tools and survey manager to quickly rectify those problems really common problems that you see when gathering closed interval surveys specifically and of course you know any of the changes that we make and server manager where we have an audit log so it's not like someone can change something and it's just gone forever what the original value us we're tracking all that for you just like we do in pcs in the third session I went over reports and survey manager and in PCs specifically overlaying surveys and snap view and running reports on those so those of you that are familiar with it we have a really neat looking report called the chart PDF and it looks kind of like this it takes your chart across the top and the map across the bottom in definable sections so you can do thousand-foot sections and it automatically parses those files and lines your chart and your map up so you could imagine enough anyone here has ever thought of survey companies do it but you can imagine how much time it would take to narrow down to those thousand foot sections on a chart and then narrow down to it on a map and make sure it's all lined up with your comments with your wave forms all you have to do is click abut in survey manager we went over some of the exception reports which for those of you that don't know we're we're including your starting and ending lat/long on your exceptions for these closed interval surveys so you know exactly where to go to start to find these problems or do your side drains or whatever follow-up surveys that you're gonna do and then we took it a step further and did something that I think probably everyone in this room has asked for it at least one point we took we use the comments and objects reports to extract test station data specifically deep hole data from a closed interval survey and import that into PCs to calculate 100 millivolt shift ICU your job and they're a little bit crisp so so we have a report that parses these comments including test stations and you can extract your potential readings that you got on a closed interval survey and bridge it into PCs too and in this case we calculated under millivolt shift so that's all in the third session if you want to take a look at it it's our YouTube channel and then we went over exception reports in PCs so now what's next we gathered our data it's been verified it's been corrected we collaborated between the field in the office we collaborated with subject matter experts that look at these surveys all the time the data has been stored in our database of record it's safe we ran our annual reports now what are we gonna do of course the next logical step is to get that data out you know these days we're asked more and more to share our data with other datasets to get a better idea of you know the health of our pipeline we're not the only group that are gathering readings at a pipeline and so our data is super critical to that we're going to kind of dig through on the PCs side the really just through the bridge which is our tool that we use to integrate all of your CP and and closerto survey and Atmospheric and valve and custom facility type data with with other systems so I know a lot of people in the room here are familiar with the bridge so I didn't want to take this the approach of just walking through the bridge basics I really wanted to give you some best practices I think I've done a lot of data projects for a lot of people in this room and a former life that I had at American innovations as a TSE II which is now a compliance data specialist so I spent a lot of my time crunching numbers and spreadsheets and working with a bridge to import y'all's datasets and so I'm gonna leverage that in this presentation but for those of you that aren't aware just want a refresher the bridges is a mass import and export tool so we're taking large data sets and we are importing them to our database for a variety of reasons it could be that you acquired a company it could be that you have some historical data that you want imported it could be that you have another data set that historically had been tracked outside of PCs and you want to start scoring on a pcs you could build each individual facility one at a time and every record one at a time the bridge is going to save you so much time if you know how to do it it's a it's a super powerful tool and you can be very dangerous if you don't know what you're doing the bridge I think we probably all been in a case where we ran a bridge and it went terribly and now you have a bunch of duplicates that you have to clean up and and we're gonna we're gonna talk about ways to mitigate that it comes in three flavors we have a bridge import have a bridge export and we have a bull horn bridge we're going to talk about the first two in this presentation because the bull horn bridge is really automatic we're pinging your bull horn directly from the website and pulling those readings in if they're aligned nothing real fancy about it other than its automated the real the real place where you can screw up is with when you're when you're talking about importing and exporting files and of course it's fully automated well I try to talk about that yesterday during my presentation at the beginning of the day but we ran out of time so I went through it really fast so I pulled those slides and added them to this presentation so spend a little more time on that that's one of the new features that we have in 114 okay so still same pretty basic the the file format is super critical we're talking bridge imports and the way that you're going to get that data in is through flat files it's going to be the excel file CSV or txt no duplicates in the data need to make sure that all of your Intel key fields are matching that's your what we always at a i/o is called row code y'all call it a million other things segment code facility no valve section valve section code it's the same thing what pipe is it what is the unique name unique code for that pipe and then what's the milepost there's there's some nuance there depending on the facility type I have a handy slide for a reference so that once y'all get this presentation you can print it off if you want a quick reference guide of what the Intel Keys are for different facility types there shouldn't be any duplicates in the data we're gonna the bridge is going to do a pretty decent job about preventing that from happening but you need to be aware of duplicates because the data could be wrong we have lots of tools through the allegro through pcs that help keep all of your inspections unique your maintenance items unique any new facilities unique but when we're talking about integrating with other systems I have no idea if you have those same rules in place so what could be in a new plug it to PCs may not really be duplicated in the other system so it's something to be aware of and we're going to talk more about that you can't have any duplicates in your column headers as well so I guess when we take a step back when we're talking flat files it's going to be the very first row of your file is what column all of the data below it pertains to and then you have rows and rows and rows and rows of data hundreds of thousands of rows millions of rows sometimes well not much more than a million because the cap on Excel is not much more than a million but you can't have any duplicate column headers because then pcs doesn't know which field to map those those columns to and then you can't have any gaps if you have any gaps it'll it'll just grab everything before the gap and bring it in pretty basic stuff but I have actually we were joking earlier about giving out s so I have a bunch of opportunities for you ought to get s and this is the first opportunity is I mentioned that you can import using a text file which sounds super archaic right but why would you want to do that is anyone know do what yes oh no no restriction on the the length of a field so that that could be a problem where text comes into play that's not what I was thinking of though I was thinking something else that's good format that's it so format is it's a problem in Excel it tries to be really helpful but sometimes it kind of misses the mark you know when you have a string of numbers when I say string I mean like it's text and they're only numbers it converts it to scientific notation so you're not bothered by you know having 20 numbers well that breaks a lot of the links that we have in PCs so having a text file it doesn't convert it to scientific notation we also see it a lot you know as we're integrating with other systems we use all these weird codes right so like in our demo data we we have T 1400 and that's the unique name for a pipe segment but you know as a technician I'm going to call it Austin to Dallas like what it is or where it's located or long horn 2 or whatever it is so those codes are really there to help keep everything in sync so the data that's in pcs can map back to these other systems because they're critically important you have to have these keys between these databases in order to move data back and forth well if your code kind of looks like a date like in ovo 9 it convert Excel will convert that to November 9th or November 2009 because things you're trying to put in a date and that that break your bridge so two things to be aware of probably edge cases sounds like Rob's run into them yes trailing zeros yeah it chops them out and it's a pain you know because in Excel you can format the cell to text but if you click on it it just revert sit back to general and you lose those trailing zeros you have to like not even breathe on the file or it's going to change the format that's some stuff to be aware of all right this is a shame free room right now so this and this is your opportunity to get some coins I think likely everyone who has used the bridge is probably going to get coins for every single one of these so have has anyone ever accidentally created thousands of facilities Uriel's got his hand up I know I have Tony TAS yeah me too have you ever created thousands of real codes those are trickier they're harder to clean up anyone ever seen new region in their hierarchy yeah yeah and yeah and we're just gonna wait for a little bit on this last one right yeah lots of admin in the room probably want to mitigate that anyone ever waited for a bridge process only to realize that some of the data didn't come through file simpie yeah yeah I think I really I think if you have used the bridge you've run into all four of these things and it's kind of crazy you know we get our question lis so it that's that's a quick way an easy way to do it for those of you for those of you joining online the question was if this happens how do we clean it up what's the best way to do it who do we talk to at AI to clean it up so if you have facilities that are duplicated that's an easy one you could use a separate bridge to move them to a different row code like a placeholder row code and then delete the row code and that deletes everything underneath it that's a really quick way to do it you could also we'll talk about this here in a little bit but you can also move inspections and maintenance in 2.0 with facility key bridging something that we didn't have before so if you create thousands of inspections or maintenance you can mass move those to a test point mass delete them what you can't do is mass delete row codes those are individual so that's where you probably want to talk to Tony and we can help you out yep yep I'm not actually going to talk about that at all but if you all aren't familiar with that it's it's a different way to mass move data within the UI so it essentially gives you you you navigate to where it lives and you navigate to where it should be and you had a move button and you say ok and it's done have to worry about the bridge go ahead right so so the way it's typically done is with pest environments so and that's what that's one of the best practices that we're gonna I'm going to talk about yeah security yeah I mean you would just restrict their access general user isn't in a need especially in access they don't need access to the bridge your bullhorn bridges are automated that in version seven that they weren't automated right so they would need to go hit that bullhorn interface button you don't have that problem anymore really admin should be the only ones that are running bridge because they can create these problems yeah at admin admin should be the only one who had access to bridge yeah yeah so I've done that too so so first two yeah just just to repeat the question for everybody online when you have a closed interval survey the start date is one of the intel keys which we'll talk about it a little bit well in the bottom right corner of your cell when you're manually populating that there's a little black square box you double click it and if you're not paying attention that date increments by a day for a hundred thousand records or however many records are in the survey so when you import it because it's an intel key for the survey now i have a hundred thousand surveys that I accidentally imported that tony has to clean up that's another one that we can't do a good job cleaning up preview this one yes this is your first line of defense bridge preview absolutely it's gonna it's going to mitigate against creating lots of these duplicates across the board grow codes individual facilities duplicate inspections maintenance CI survey folders this is it's it's a way for you to verify your data before you're committing it to pcs and I I think it's counterintuitive because it's an additional step right there are two buttons one says preview on says import import doesn't run the preview it just imports it as is it's faster because you don't have the other step but preview is gonna save you time because you don't you don't have to go back and clean these problems up especially in a compliance world where this this stuff is critical that the the integrity of our databases are so critical it's it's so much it's wiser to take the extra time to you know resharpen your acts if you will and and make sure the data is gonna go the right spot that's right so some some things about preview pay attention to the colors across the top of the bridge preview window you're gonna see a bunch of a bunch of different colors and we have a number of records that fall into these types so everyone wants to see green for everything right no that's right yeah I think in the CP world that the answer is it always depends you know I know that's the answer that clay always gives when y'all ask him questions about how something should be signed it's the same thing with the bridge the answer is it depends it depends on the type of bridge you're running if you're trying to create new records Green is good if you're not Green is very bad those are duplicates so so be aware of the the data that you're importing and what your your end goal is to know when new is good or new as bad rejected generally is is not a great thing it means that something is misaligned we'll see that here when we talk about facility key bridging what's another tool in your tool belt to help you link these data sets to other systems that kind of thing is usually in my experience either it's a problem with the data and so you can defer the bridge we'll talk about that here in a second and go fix your data and run it again redundant is duplicate so what that means is the rows and your Excel spreadsheet are duplicated based on the Intel Keys those those row code milepost inspection date so when you see something like that and you know that it should not be duplicated that's where you should go in and and pop up in that excel file again and take a look at that data more clearly warnings are not always bad and we'll skip over reformat a reformat adjust changes pretty much like the case of well I guess if it's all uppercase it'll do camelcase or remove some spaces it's it's not really anything you should be worried about just let it let it do its thing there can be I'll show you a different way to do it but it's not like you know how infield computer send how you can go and manually select the rows that you want to be sent to a DAT file we don't have a feature like that but we can there's no stopping us from doing that would be valuable change tracking has come a long way since then probably as well we can hook that up to these temp tables as well think that would be a problem from a technical standpoint sure yep I was always really anal about my bridges and I would run them run previews cancel run another pre you cancel or defer always checking the source file to make sure that it was perfectly good before I imported it I know that there there are there's logic baked into PCs that does a lot of this stuff for you for example and this may be a little bit over blush but when I would add inspection records new facilities with inspection records you could just import the facility inspection bridge and it's going to build your facilities it's going to check your activates and import your inspections well I would break that down into each of its components I build the hierarchy build the row codes build the information records with the activates and then build the inspections it takes a lot longer but when you get when you get to the end of it it's it's a safer way to approach it anyway back on track in the bridge preview there is a warning section there's also rejection section at the far right of that of that window you're gonna see if something was is showing up as a warning why it was a warning these warnings sometimes are not bad sometimes they require for their evaluation so there's three of them here the first one says an input value for casing status of electrolytic short was not found in the pic list that's one of the bad ones that means your data is not going to go in because the pick list that it's trying to match to doesn't have a matching value definitely something to look out for the other two are not as bad there are criteria checks the data is still going to come in it's just saying hey you have a problem here you may already know you have a problem but we're telling you just to be safe that's right yep right you could imagine you know the reason we have picklists right is to stop all these million permutations of the same thing like technician for example I could have David go shady Gosha Gaucher Dave go Shey go shady all of these all of these different permutations of the exact same thing it makes the data really hard to query so picklists really helped with that and we're preventing you maybe probably not more so than we should and it should match up right across systems yeah right know when to use the defer button so this is one of the ones at the bottom right corner of the window what this does is like like Tony mentioned the bridge preview pre processes these Excel spreadsheets or text files and loads them in as temp tables in PCs so that you can have access to this you where we're pre validating the data because it's stored in this nice safe table you can come back to it whenever you want so if you have problems with these warnings or duplicates that you need to go investigate further use the defer button go look at your source file if the source file is right and the stuff is actually duplicated you don't have to run the preview again you can just load the same preview and hit the Run button and it's going to process it's going to save you a lot of time right yeah it'll leave it there that's right so it sits in your job queue as a preview available job and you'll see a preview icon on that row that you can click Pop's the same preview window open and you can defer it again if you want to you can cancel it from there or you can run it yes yeah I think you can you can get there from the bridge as well in the job status tab yeah know when to reject data items and do reject data items so this this comes into play when you have multiple data items in a bridge which a data item in a bridge is a different type of record in the same bridge definition so when I said I would split that test point inspection bridge up into row codes and test point information and test point inspections my bridge has three data items if my rows and my test point information are good I'm gonna let those process I may still have to fix some stuff on the test point inspection side so I can reject that individual data item and it's gonna save me time by not having to process the other two files on the the next time I want to try and import my test point inspection bridge and that's just by a little toggle at the top except that it rejected you just click that the last thing that we'll talk about is actually we're going to talk a lot more about this but this is another super helpful tool especially when integrating your data with other data sets so facility key bridging lets you do do lots of things one of the things that it does is it does not create duplicates if it doesn't find a match between the file you're trying to import and PCs it could be you know it could be good because you don't want to create duplicates it could be bad because you now you have to do some work to figure out why it doesn't line up ultimately err on the safe side and use facility keep bridging when you when you can this this tool is is easier to manage than your Intel Keys on facilities alone so for test points you have ro code and milepost depending on the record type it's also effective date or inspection date or repair found date so those are three fields you know at most that you have to recognize well I guess also the repair codes of four for maintenance items that you have to make sure are all matte in order to map to the correct facility and record with facility key bridging you're eliminating that to one one individual field it's much easier to maintain in pcs and specifically other systems its pcs was designed in a very specific way and these other systems are probably solving different use cases they don't really maybe not care about a row code or a mile post they care about the facility themselves they care about the records themselves that's their main focus and so it's it's too much information to dump all of this superfluous information in the other system when you could have a hook or a key between the two databases and bring that data in and that's what once you have this key that's how your systems talk to each other show you here in a minute it is a good question I think you probably know the answer though so another thing that facility key bridging can do is move facilities when you're not using facility key bridging and you want to move a facility from one mile post to another from one row to another because it's never gonna find the match of where it's supposed to be you're gonna create a duplicate because it doesn't have a matching pcs so it thinks it's new and it's trying to be helpful with facility key bridging it says I don't care what my road code is what my mouth post is what my facility ID is what the inspection date is validate on this field and change my Road code change my mile post to whatever is in that spreadsheet so you need a mass move facilities this is the tool to use facility key bridging no we can add it but now I think the focus has been on facilities we expanded it a little bit in 2.0 so we're a step further but we didn't take it to those indirect surveys yeah yeah that's fair Aled we can look at adding that in the future for sure okay so what fields are available to use is your facility key bridge ID so this is that exposed grid every every table in pcs has this 16 digit unique identifier its total gibberish numbers and letters with dashes but it's is unique yeah it keeps everything that there's like a 1 and how many million percent chance 10 million 20 million it's it's it's a crazy high number percent chance that would ever be duplicated essentially it's never gonna be able to be duplicated so almost there two bullet points ahead so you can also use if you don't want to use bridge ID for example if 16 characters is too much to fit in the other system you have a different key or you want to link use the other systems key to link to pcs you can build a UDF it's got to be a permanent information level field a character field and then it can be whatever you want couple options there bridge ID is safest option because it is pulled directly from the tables and you cannot edit it at all so definitely I would encourage that you use that this is something that I didn't get to get to in my presentation yesterday but with facility inspection and maintenance linking we're now exposing those same grids on the facility inspection and facility maintenance tables so you can link those records back and change those Intel Keys on those records as well so you don't have to maintain the date/time down to the timestamp or you about the format in Excel and if it's gonna change it all you do is throw both of your grids in bridge ID facility maintenance ID facility inspection ID and it knows exactly where it's supposed to go that was a that was a big customer request okay I know we have some version 7 people in the room let's talk about facility key bridging in version 7 a little bit I remember doing data projects where I wanted to use facility key bridging and if for those of you that are familiar in version 7 it takes you through lots of wizards right so it's like building this import definition takes me through seven or eight pages it's a whole bunch of clicks to get where you want to go and at the end of it when you want to run it and you don't have you don't have it changed a facility key you're on your preview wait for your preview to load and realize facility key wasn't wasn't set up you have to cancel it go to this specific spot in tools their utilities data options click through this wizard pick your facility keep but then you realize you forgot to build your facility key field so then you go to field and UDF customizations you add the field you import that data it's it's a it's a million step process and then you go through the whole bridge again so that has been streamlined in in PCs axis oh that's right that's exactly right yeah yeah if you don't change it back it won't it it'll keep using that facility key in PCs access when you build a bridge of definition we have a check box that says use facility key bridging all you do is check that box and then further on in the bridge when you're mapping your fields you have radio buttons that lets you pick what you want your facility key to be so there are two examples here now one at the very top is for my facility the one at the bottom is for my facility inspection records so they're both mapped they're both facility keys that are serving different purposes one for facility one for the record it's much easier much easier way to approach it much fewer clicks right yeah you don't and you don't have to go through a wizard right it's it's on the same page part of the reason you want to use facility key bridging is because you have to remember all this stuff so this is really a reference for y'all in case you want to use it in the future this is just the table that breaks out the the intel key fields for different facility types it doesn't have the inspection record facilities are rather the inspection record intel keys but you don't have to remember any of this stuff if you just use facility key bridging it's a good question so because I've done this before the required fields for foreign bonds are Iroko to milepost if you have an RM you tied to that bond and you update the facility record and you don't have it populated you're gonna wipe out your link to that RM u so it's a good idea to use that regardless if your bonds have RM use good good question i almost forgot to mention that okay yes no you're absolutely right yep it might actually apply it to test points as well all right I have what I think is a tricky question URI all got this one so maybe it's not that tricky thing okay for which of the following does your current hierarchy selection matter it only matters on one of these options manual well don't ruin it manual import automated import manual export automated export let's see yeah I was gonna get everyone raised their hands everyone's gonna get a coin now you only get a coin and no one else gets coins no I'm just kidding everyone everyone still could get a coin for that for participating so I think this is this is a common misconception about the bridge the only time it matters is when you're exporting what your hierarchy selection is so when I'm importing a bridge I don't have to go into the hierarchy and pick the row codes that I'm bridging in it's gonna map them without them being selected same thing for automated bridges actually automated bridges are a lot more different because they don't care at all ever about what your hierarchy is looking at if you need to filter those data sets you have to use filters which are which are on the bridge level as well the only time it does matter is is for manual exports which functions varies similarly to reports so my export tips know when to just use report exports instead of bridge exports really the bridge is is for continued use so if you're if you're dumping a huge data set out that you need to offload to a different server let the job let the job service process that it so you can keep on doing your job that's when you want to use the bridge if you need to do it multiple times so you're exporting data for another system on a consistent basis that's where you want to use the bridge if it's a one-off deal it's a small data set it's much fewer clicks to just run it as a report and just click the export option you're going to get it in the same format so definitely leverage that when we're talking about automated bridges if you need to fill through your data set you're gonna have to filter it in two places there's one that are for for the common facilities or rather the common fields that's at the very top of the bridge and then each individual data item will have their own data items specific filters so if you're trying to bridge you know you wanna you want to filter down to a specific region and then for test points you want to say show me where I'm not meeting criteria those those filters occur in multiple places so just be aware of that rename your files so this is something that we help with when we're when we are talking about exporting data to a file and another system is going to import that it's important to rename your file so that whenever the BRIT the next bridge is run on whatever schedule is set for you don't lose what was in that file especially when we're talking about the next the next bullet point there it really depends on the bridge type so there are multiple options here you can have a full bridge which is everything data inserted since last bridge or data changed since last bridge Kevin mentioned this yesterday with email notification is very similar so a full bridge takes into account everything in the database if it's automated its do that every single time so it's that's not a great option if your other system can just pull those records in and match them up with the datasets that have already been exported from PCs much better to just use data inserted since last export or data changed since last export good it so kinda it has to it has it does a full regardless for your initial bridge and then it's because it has to establish a baseline of what you know when am I looking at these records to know what has been inserted or changed that's right no that changed yeah so the the rename checkbox renames it looks at the folder renames the file if it finds a matching one to the timestamp that this next bridge is running and then it inserts the new one so we're we're programmatically retaining those old files for you if you do that checkbox that's a 2.0 change tables different unless unless you rename well with export to table yes that's correct exactly the application isn't going to rename those tables I don't see well you definitely could yeah sure so the export formats that we have very similar to import formats xlsx csv text but we can also export to a sequel table that's kind of what we've been talking about a little bit it's got the exact same settings as far as customization goes it includes derived fields that's what this has been a huge ask from our customers for a long time as I have this other sequel system I want to hook it straight up to your tables and we have to tell them well you could do that but you might have problems with you know metadata being captured and you're not going to have any derived fields because a lot of a lot of the magic that we have happens at run time or it's stored in sort teachers or temp tables that are not accessible from these raw data fields so export the table just like the normal bridge packages all that information up including the calculated fields and dumps them to a sequel table that can then be queried by whatever system you want it's actually in a different database than your CP system of record so if they blow that database up all of your data is totally fine there's there's no no there's very limited risk to anything happening to your database of record it's faster the reason it's faster is because we're not rendering these files so whenever the sequel is done processing that's it it builds the table and you're done that's great to know great to know the captions are sold separately so they're actually in a separate column the reason we have it like that I'm sorry separate table not separate column the reason we have it like that is because we are pushing the back end table names for the table that contains all of your data because the captions are editable so you change your caption you don't want to break the link that that table has to whatever system it's that's using that data and so you can always join the table and you know include those captions at yourself if you want to with a sequel query the yeah yeah I mean that's going to be included every time right so but but it's good because like I think I think maybe I was meant we were talking about this yesterday like if you have structure pipe to soil and then you change it to structure on or PS on PS off all of those different permutations they can change whatever you want and you don't want to have to remember oh I have to go update my bridge and update this all of these other things in order to get this this data to continue to flow into whatever thing it needs to flow into okay let's talk a little bit about automation so this is that this is the slide that I wanted to show yesterday I showed you the version 113 slide this is 114 and 2.0 so all of the scheduling for pcs bridges has been lined up with email notification and it's totally configurable and you can understand when it's going to when it started running when it's going to run next and go in and quickly change that to whatever you want so daily weekly monthly quarterly and you can say every second quarter on the third day of the the second quarter if you wanted to do a semi-annual bridge on the third day of that second half of the year or first half of the year that there's there's whatever options you know you can dream up whatever whatever you need other than what Ray needs which is less than daily sure so this is this is M Bridge imports projects ports your bridge definitions can both import and export so you can schedule them you know an hour apart you dump your data out it goes to another system it does some stuff it spits out a file then an hour later we import that change data back to PCs it also works for export to table yeah yeah good yeah there's other challenges there though right because if we're talking your database that's lots of Records and the job service is doing lots of the heavy lifting but you'll see times where tables are deadlocked and so it you may see performance implications for users so really the recommendation is that all this stuff happens off hours it would be the change since the last time that bridge ran so whatever it thinks it changed so you may see some duplication it's a-ok so really quickly I have a few use cases I'm going to run through likely some of y'all or all of y'all are doing some permutation of these it's really just a way to kind of get your mind flowing on how you can start integrating PCs data with other systems so one way that we would see this is maybe around new pipelines where you go out and use an Allegro to create new facilities down the pipeline and you increment um 1 2 3 4 however many you have bring the data back into pcs set your bridge up to dump that data out for GIS system to consume they figure out the exact footage of where it is then they push that data back into pcs so some of the stuff that we talked about you can do it file table you would export with filters down to that specific row probably use facility key bridging on the way back but you can mix and match this stuff I'm sure Gina and Ray like that step three is GIS magic okay another one that we see is pretty common as tracking work orders in another system so this process has been made a lot better with the enhancements in 2.0 by facility inspection and facility maintenance ID facility key bridging that's a lot of facility in one sense so it's the same idea you're gonna but this is an automated export right so nightly I'm exporting my new maintenance items to this work order management system nightly that that system is pushing out any changes or any updates so that pcs can consume and since we're maintaining those hooks at the facility and the record level I don't have to have matching dates or Intel Keys stored across multiple systems all I'm doing is maintaining those hooks across both both systems that's how you would bridge it in on a daily basis the last option I have for you is exporting data to be consumed in a dashboard so we're gonna export it through export to table it'd be faster to just query on it from a sequel perspective dashboarding engine is going to take over and then KC is going to give a presentation next about what we can do with that data using dashboards that's