 with at least broadband connection. If you have any problems or require online assistance at any time, please contact Citrix Technical Support at 888-259-8414. Again, that number is 888-259-8414. On the next slide, I would like to discuss how to ask a question, because during the session today, you're going to have an opportunity to type in questions. Let's talk briefly about how to enter a question. Go to the control panel, click on question section to reveal the question section, and enter your question and send. We'll cover as many questions as time allows at the end of our presentation. On the next slide, I want to introduce the FileMaker platform. It truly is a complete database platform. And actually, what I refer our platform as a business productivity platform, and the reason being is we help improve your current workflow process by helping to capture data or content, and then managing the information you have captured and the ability to easily distribute information to others, both inside your organization and outside. And then, of course, the ability to analyze and report on that content. So a true platform. FileMaker products really fall into three buckets. The first one is FileMaker Pro. This is the client license, which you'll be doing all your development of your FileMaker solutions on. The second is FileMaker Server. FileMaker Server is used for both data storage and data backup. Very, very important. And then finally, FileMaker Go. This is a window into your FileMaker data from any iOS device, the iPad, iPad mini, or the iPhone. On the next slide, I want to talk about the fundamental issues with paper and why most organizations need to get rid of paper. So as we all know, paper is very hard to share with remote workers. Paper becomes very obsolete. In fact, the data on the paper becomes obsolete pretty much immediately. Paper processes are very manual and time-consuming. You burn a lot of energy with these type of processes. The most important piece is paper is very unsecure, so not secure whatsoever. And then finally, paper becomes very, very costly from a storage standpoint. In fact, I've got a couple of customers that I work with in the Midwest Territory that have now moved to FileMaker and iPad solutions. One of them is a contractor and or landscaping company. What they're doing now, they've extended all their price quotes and blueprints to the iPad in real-time. So now they could show up at a customer site and share with them the latest price quote. And if the customer could even say, you know what, I want to update that price quote. I want more product and they could do that in real-time immediately. And then also leverage iOS capabilities like signature capture. Same thing with blueprints. If the customer is not satisfied with the current blueprint, they can adjust the blueprint by using their finger. Maybe I want additional flowerpot areas around my patio. Maybe I want a wall-size increase in my home. They could literally do that on the iPad real-time. That information is now saved and sent back to the corporate office to update the final blueprints. I've worked with another healthcare provider and they have all of their customer surveys right on the iPad. They've eliminated all paper surveys. And then also audit checklists around both their office and or hospitals. Much easier process for them and now capturing those checklist processes on the iPad. A third customer, in fact, I just met with them about 30 minutes ago, a credit card company. They've leveraged iPads now in their call center and they've built a coaching solution on the iPad. And what this has done is increased coach and employee interaction. They have more coaching sessions going on between the coaches and the folks on the phone. And that has led to a tremendous cost savings for them. But also, more importantly, it has increased customer satisfaction. On the next slide, I want to introduce the Austin Convention Center. Basically, they've transformed paper-based service order forms, work orders, and floor diagrams into mobile applications that provide a mobile workforce the ability to view, process, and reference event information across a facility that spans six city blocks. So a lot of mobile users walking around a huge convention center that we're leveraging paper in the past now are leveraging iPads. Next slide, I want to talk to the Austin Convention Center how really their life was prior to FileMaker and prior to the iPad devices. So the exhibitors' work orders were based solely on either faxes or paper, very manual process. The orders were keyed into a system, printed out and placed into a binder with diagrams and other paperwork to start deployment or fulfilling changes of the different spaces. Very manual process. On the next slide, I want to introduce the concept of how the Austin Convention Center transformed their business leveraging both the iPad and FileMaker Go. The good news, they were already using FileMaker Pro on the desktop as their billing system. So they could leverage the skill set that they already knew in FileMaker. They very quickly designed work order forms on the iPad, employees now have real-time access to work orders, change orders, and floor diagrams. An easy-to-use touch interface. This saved them so much time and heartache. In fact, this led to fewer errors, faster installs, and increased customer satisfaction on the convention floor. What was really the most important piece regarding the Convention Center was their compelling ROI. With FileMaker Go for iPad, the project payback was less than four months with an annual ROI of 200%. In fact, their estimated annual savings was about $24,000. All right. On the next slide, I want to introduce two gentlemen. They're going to take us through the Wind River Oil Services Business Use Case. The first one is Blake Boyer. He's the Customer Relationships Director at Wind River Oil Services. And then secondly, Paul Costanzo, who is President of Recruiting Pro. Thank you, gentlemen. Thank you. It's a pleasure to be with everyone today and to really go through and explain how Wind River has taken FileMaker and implemented into our systems and some of the transformation of what we've done and how we're able to use it. On the next slide, I'm going to talk briefly about Wind River, what we do, and then kind of go into how we've implemented FileMaker, and especially FileMaker, go out on our job site and some of the future ideas that we have of moving forward and implementing it even more. Wind River does a number of different things. We do oil and transportation services for drilling and for crude oil hauling after the wells have been drilled up in North Dakota. And so we've got a number of different things as far as we've got the trucking services where we're actually hauling water and oil back and forth up in North Dakota, as well as selling, we sell water so that they can use in the drilling process. We sell both hot water and cold water. And then we also dispose of the used water after they've drilled the wells. And so there's a number of different things and we've really been working on implementing FileMaker in all of these systems. And it's been a real challenge as well as something that's been very beneficial to go through and do. Wind River was founded in 2011 and we service both oil companies as well as these trucking companies that are hauling for the oil companies. Paul, if you want to go ahead and go to the next slide for us. On the next slide, it shows a little bit of kind of the previous system that we used. What was happening is at the water depots, the disposals, we had the drivers, they were going around and they were filling out these handwritten tickets and basically showed what the beginning meter was, what the stopping meter was, so that one, we could bill for it. Two, we knew how much water we were selling. And three, there's reporting that we have to do back to the state of North Dakota. We had to get all this information from these remote locations to our office where the data was then manually entered. And as you can see on the right, it took a lot of paper and it wasn't a very fast and efficient process. And there was no live real-time data. So in talking with Paul, we decided that this was a very good opportunity to implement FileMaker Go into what we were doing out at our water depots and disposals. And so if you want to go to the next slide, we can see a little bit more here. So our challenge was figuring out a way to replace this paper-based system, where we were having them, because they were remote locations, it would sometimes take a number of days to get those pages back to the office where they were then scanned and sent from North Dakota to our offices, to our home office where the information was then manually keyed. But what was also happening is they're doing this 24 hours a day, seven days a week, 365 days out of the year. And so there wasn't a good way to be able to get that information live every single day until we came up with this system. So you can see that we've got all these trucks sitting out there and the drivers, our guys are taking the iPad, they're taking FileMaker Go, and they're going around and meeting with the drivers and they're actually capturing all this data directly on the iPad. And it's been very beneficial for us because we're able to see that information live real-time and also be able to invoice directly off of that. There's no more manual data entry on the back end. It's all just happening one time and it's being imported right into our main system. You can kind of see on the iPads here we've got a case that we've had to find that will withstand the elements because in North Dakota the temperatures range from negative 50 in the winter to 100 degrees in the summer. And so with rain, snow, they've been able to still be unable to use the iPads regardless of the weather conditions. And it's been a fantastic implementation process on our side to be able to do this. I'm now going to turn the time over to Paul who is going to go ahead and show kind of how the system works and what we've done to make it work. Thanks Blake. What we'd like to do right now is we're going to depart a little bit from the slides and show you a little bit of the real-life system on an iOS device as well as the desktop component of the software. So I'm going to just exit out of our keynote presentation here. And we'll start off first by showing you, we'll show you on the iOS device. What Blake had talked about before, one of the key elements of this project was the fact that all of the data for several of the Wind River systems resides on a central server. So everything is hosted in the server and on the server and that's what the folks in the home office end up using. In this case, because of the location for this information it was very important that we have the data locally on the iPads at the individual water depots or disposals because of the fact that we couldn't count on the connectivity to be able to go back to the server. So the deployment mechanism here was we had the master system that was on the file maker server and then there was a subset of the data that would be on the device at each location. So for example, this is a test water depot that we've set up and you can see that I've got three tickets right here showing up on the list view. I can go to any one of these tickets on the far left hand side. You'll notice that it'll tell me the status of the ticket. So in this case, I can see that tickets 10 and 9 have been submitted and ticket on the 19th, this ticket is actually still open. So if I go into that ticket, you'll notice that it's partially completed. I filled out the majority of the information, but I haven't yet put a driver's signature on there. And so one of the key things as far as this process was we wanted to make sure that we had data validation of there were certain fields that had to be required before a ticket could be submitted. So in this case, if I try to submit this ticket, it actually tells me that hey, wait a second, you can't submit this until you complete all of those fields and in this case what it is is I have to actually put the driver's signature on there. So the person can go to the driver, they have all the information in place, they can click on the field and then use the signature capture of the iOS device to actually have the driver sign. I apologize, our reflector app is... So I can capture that signature for Sally Thompson and it's going to go back, it's going to store that on the ticket. And so at which time when it stores that on the ticket, I can then now submit the ticket. So if I go ahead and submit it, you'll notice it actually gives me an option to print the ticket out. So if I decide I want to turn around and print this ticket to an air printer, I can do that. Otherwise I can just cancel the print option and it will actually store a PDF right on the device. And you'll notice that it then changes the status to submit it and it also indicates what ticket number it is, as well as keeping track of any of the different types of when it was created and who it was created and all of those different types of data points. So ultimately when I log in the other option is I can go back and say if I want to create a brand new ticket. So I can go into the upper right hand corner. You'll notice that I can click this green plus and once I do that it gives me an option that says do you wish to copy a previous ticket. This was a very interesting feature because initially this was not in the system when we deployed it. Initially every time they started a ticket they had to start from scratch with a blank form. And after we had been out in the field and being deployed a couple of the end users came back and said you know when we're real busy very often we'll be doing several tickets in a row that are very very similar with just a couple little differences. And so they asked us to say is there a way you could have it duplicate the previous ticket. And so we literally went and I believe it was over a weekend we sat down and we implemented this functionality to where now they have an option of saying hey listen if I'm really using the majority of the previous info I can click the copy button and when it creates that new ticket it fills out the core info. So I don't have to go back and select all of the data points. I can just go through and select the points that are most important to me and then I can go through this process. So again you'll notice every time we go to one of these different fields it's giving me a list of the related data. So for example if I go down and I get to the point where there's various lanes at these facilities if I select lane one you'll notice that it automatically pre-populates the starting meter value because that was the ending meter value from the last truck that had gone through that through that lane. So the idea here is we're really trying to minimize the amount of data entry that these folks have to do even something as simple as calculating total barrels. You know for them not to have to sit down and do simple math over and over and over several times a day we've put that into a situation where they can now go through and have it do that for them automatically. They can put notes in here if there's a specific note that they have to put in they can have an optional field of saying you know that this was something that we did you know for a test or some other type of situation and then as we showed before I can go through and click and do my driver signature where I can go in and do that signature capture. You know I can accept it again it's going to automatically come back through and give me the ability to then submit that to where now just like we did before we're now going to embed that PDF inside of the document itself. So that's the process of going through of going through the entire validation piece. One of the other nice things that we added on this if we go and add another ticket in place you'll notice that this time I'll go through and I'll start from scratch so this time I'm going to do a brand new ticket and you'll notice that we have the ability to select obviously related data. So once they select from a variety of all the different trucking companies that they work with I can then turn around and when I select the test trucking company it gives me the related people for just that company. So I'm not having to go through the hundreds and hundreds of drivers that we have in the system I can select a particular driver. Let's say it's a situation where I get down and I make my selection here same thing for the for the oil companies when I select my test oil company I can select a job name. Now in this case I want to show you I have three different job numbers that are available. Let's say that a new job just came online that I don't have in the system a new job number. The green pluses here allow us to add additional related data on the fly out in the field. So not having to call back to the home office they can actually come in here click on the green plus it goes through and they can put in the test well. So again I'm going to say it's for the same test well. But the difference is is now I'm going to say that instead of the job number that we had in there before I'm just going to call it you know three three three two two two. Okay so I can come out I can add this information so now that gets added to the ticket but then you'll notice that it also is in my queue to be utilized for future information that comes through or future tickets that come through and we'll show a little bit about how we validate that when it comes back into the main desktop system as well. Again I can select the commodity going back to the lane I can pick a different lane this time again put a value in there and then finish up with the signature. You'll notice in this case I'm going to leave this one open just so you can see kind of how this how this works relative to the synchronization. So we've now gone through we've added several tickets into the system you'll notice that we've got a variety of submitted tickets as well as an open ticket that's not that hasn't been completed. A couple other things that I want to show just before we go to before we go to the synchronization if I go to one of the submitted tickets if I go back through once it's been submitted if I go back through and try to make a change. So let's say that for whatever reason I look at this ticket 12 and I say you know what it really wasn't it really wasn't 1150 if I go back in and try to make that change it's actually going to ask me do you wish to edit this ticket and we've put in some some logic here in the sense that there was two rules we really put in place they had a limited amount of time that they could edit a ticket and also had to be the same person editing it that entered it because we didn't want you know Charlie Sample to make a change from Fred Smith. So the key thing is as long as the same person they could go in they could make that change and we could say you know what it really wasn't 1150 it was 1125. So now you'll notice a couple things happened once I made that change and did that edit you'll notice that it actually erased the PDF down here because basically now we have to redo that PDF because now it's no longer valid because we've changed the details we've changed the total barrels. It also maintained the same ticket number and it changed the status to open. So now if I go through after I've made that edit and I submit you'll notice again the same process it gives me the ability to print and then it now goes through and generates a new PDF. Also one of the nice things as they go through this process if in fact they ever want to look at one of these just by clicking on the ticket PDF they can then turn around and see that PDF within you know right on the iPad and see all the details of it. So this is what can actually be printed out on the air printer if a driver needs to have a hard copy that they take with them. So the next thing we want to show that I think is probably one of the more intriguing elements of this whole process is you'll notice here at the very top there's a time stamp and the key component of this is this iPad is operating independent from the web for that matter with data locally on the device and so what we wanted to be able to do is now submit this information and sync it back to the main server and we're utilizing a tool here a tremendous tool called mirror sync by the folks from 360 works. If I click the sync button up here in my menu you'll notice it takes me into the mirror sync page and now I can turn around and actually go ahead and do this sync. So what I'm going to do now and what's really powerful about the sync is not only am I taking those tickets sorry about that. Not only am I moving that ticket data from my device back to the server as well as any of the related information. So for example if I'm moving over those new jobs that I created or anything else I have the ability to move all of that information over to the main server as well as bring down any information from the server that anybody else had entered at another location or if Blake had made a change on the main system for a job or for a company that or for an equipment that piece of information can be moved down as well. So all of this information is in essence being synced between the two systems between the IOS device locally and the server on the main in the main office. And so we'll just let this run through a little bit quick. One other note too about the synchronization you'll notice that we are syncing over the signature graphic. So we're syncing over just that field that has the signature in it but we're not actually syncing over the full ticket itself. And really we're doing that for performance sake because of the fact if we did have to synchronize that whole PDF that obviously would slow down the process. So what we did was we just would just let the sync automatically take care of the conflicts and then if we did sync over the PDFs that would obviously slow down the sync process and we found it was much easier to if they needed the PDFs, the ticket PDFs back on the main system they could turn around and just automatically recreate those. So you'll notice the sync has been completed. You'll notice it gives us a printout of exactly what's been changed or what's been done. But now if I go back to my activity we'll see that now what it's done is it's actually taken over and it's moved over the tickets back to the server. So now if we transition over and we go back to our desktop system. So now this is actually the desktop component that goes with, this is the system that sits on the desktop itself and this is what we're using to manage the information as it comes in and out. And so we have a couple options here and that we can have all of these different activities I can go through and I can query these activities based on what's happened. So if I want to go through and say you know show me any of the tickets that are open. So this is going to come through and show me any open tickets. Here is that open ticket that we just created this morning. I can click on that ticket and see. Here's that ticket for ABC text trucking you'll see it's the test well it was the 33322. A point about this and this is where I think you have some real power in terms of that test well 333222 remember that was a brand new job that we entered on the device. And so what we do is we bring that back into the core system and market as being non validated. So the reason we show it in red is the idea that then it lets the person in the home office know that this is a brand new well that someone entered on at one of the depots or one of the disposals. And so now this is something that they can then adjust and validate that to make sure it's a valid that it's a valid form. Obviously the big part of what we're trying to do here is we're trying to look at tickets that have been submitted. So if I go through and I can see you know 288 tickets I can see a whole range. The other thing you'll notice is that on the desktop I'm seeing information from all of the facilities. So you'll see here's a bench from a facility called red mics you'll see we've got some other data in here for the facility that I was working on. We're honoring all of the same file maker menu items just like you normally would in file maker pro such that if I go down and I go through here and I go to find mode. So if I come down and I go to find mode in file maker let's say that all I care about right now is I want to show all of the activity all the tickets in the system from the test depot. So I can go through and select that and in fine mode I can call up just those tickets. So now you'll see I'm seeing the 12 tickets from just the test depot and you'll see we've color coded some things where you know certain tickets once they've been invoiced we're going to color code them as red. If they've been prepared to be invoiced we're going to color code those as gold. So the idea is they can see an entire life cycle for each location as to what's occurred over that period of time. The big part here is that now that we have this data in place we want to go through and actually prepare these tickets for the invoicing process. If I click on this button it's going to call up my list of tickets and you'll notice basically it's going to find any of the tickets that have been submitted that haven't yet been invoiced. Okay so I can go through and I can actually select any of these. If I want to select a variety of them and say okay I'm ready to invoice for these five tickets you'll notice at the bottom it'll tell me the number of tickets I've selected and it'll also tell me the number of barrels and the amount of dollars that we're going to be invoicing on this invoice. The other factor that became important was that the user needed to have the ability, the admin person needed to have the ability to go in and change that barrel rate. So in this case for whatever reason let's say that for this job for specifically the rate instead of 65 cents per barrel it needed to be 85 cents. I can go in and make that change at that level and then that's automatically going to propagate through into my invoicing form. You'll notice that we also showed the different notes that were on here so if there was an issue with that ticket we're going to show that in terms of the notes as well as showing the actual signature graphic. So if they want to just verify a signature, again this is that point we talked about as far as bringing over that ticket or bringing over the signature graphic itself into the core system. And so then I can go through and actually process this into my actual invoice form where I could then export this data and actually generate my invoice. I'll show you just real quick before we leave this. This would be the example of you'll notice that we have a few of these tickets in here that don't have the PDFs. And so we just added a real simple script that just allowed them to go through and recreate the ticket PDFs. So I can just select that script and ask me do you wish to recreate them on the server? I can say yes. And then the nice thing is is these tickets are recreated, the PDFs are recreated and we're storing those in external storage on the server so that now they can still be accessible if they need to show them to a client or send them to a client, they still have access to seeing those PDFs. And that would be the PDF recreated with the signature graphic. So the other part of this became the fact that right now everything that we've shown you to this point from the iOS standpoint has been from an end user perspective or the people at the actual depot or at the actual location. What I'd like to do real quick is I'd like to show you another iPad. So I'm actually going to go through and turn this one off. And I'm going to switch gears to an iPad mini where I'm actually going to go through and now what I want to do on the mini, I'll show you, I'll show the email piece first while we get the mini while we get the mini fired up on the other side of the screen. But if we go to mail, the other thing that we built into the system was the ability to on a daily basis every morning we have some automated scripts that run that actually go and they send out to the management team a status report for each location. So for example, I can call up and this is an email that it's an automated email that comes from Blake that basically shows what the activity was for the test depot location. And so I can see all of the activity that occurred, the start meter, the end meter, the number of barrels, the signature I can see all of those different types of things that occurred for that specific location. And so we've done that so that this can go to the management partners as well as then we have it set up where they have certain customers where they actually are sending these to the customer themselves. So this is an activity or an email that can go to the ABC Test Trucking Company where they can sit and say, okay, here's what's happened. Here's what occurred during the previous 24 hour period. And then finally the last piece is we will also do if there isn't any activity there's an email that goes out just confirming that there was no activity during that time period. So if we can, we'll switch over here to let me just quit this and start it again. Paul, all that boots up real quick. One of the things I wanted to really stress was with that sync point was because of like you said, because of the connection requirements for the, you know, for it to get the information back and forth, being on those remote locations in North Dakota, we wanted to make sure that no matter what happened, if the cell signal went down, if they lost 3G coverage, they could still capture all the data and still be able to submit it to us later without being stuck dead in the water. We didn't want to ever have an issue where we had downtime where our guys all of a sudden were going, wait, I can't do my job. And so we, one of the big portions with doing that was adding that sync in so that no matter if there was zero cell coverage, zero Wi-Fi availability, they could still go through and do that and then when they got connection, then they could go ahead and sync and send all the data would come over regardless of what they, you know, how many, you know, how many hours it had been, whatever, that they had been without coverage. Thanks, Blake. Yeah, that's a great point. So on the mini now, what we're showing here is this is an administrator logging in and what they're seeing now is they have the ability to query the entire set of data. So they can see obviously everything from a test depot or they can actually go through and do, they can actually do a search for a specific date. So if they want to just go through and say, okay, all I really care about is just the information, you know, show me everything from yesterday. Okay, so they can go through and say, okay, everything from that date, I can go through and do that and do that fine. Sorry, my big fingers here aren't doing really well. Okay, and now what this is going to do is this is actually going to bring up. So now you'll see I've got activity showing from not just that location that I was working on the test location, but a variety of different locations. So it gives them an ability to keep a kind of a watch over everything that's happening, not just the specific location on the iPad itself. But then you'll notice that we do have some error checks built in here that if they do try to sync, they're going to get a message saying that as an admin, they don't have the ability to do a sync. Because obviously the only place we're doing syncs are the people from the local depots and disposals. So we want to just transition the last piece we want to show you here real quick is just how we've kind of implemented this even into the core system. And so this is the core Wind River data management tool where we're basically integrating all of the elements that we were just discussing a minute ago in terms of jobs, company, people, invoices. This is their core data management system. And one of the other things moving forward that I think this idea of going paperless, what we showed you on the iPads a minute ago was kind of where a job is starting. The idea of a truck, of a driver going to the depot, picking up a load or going to a disposal, dropping off a load. What we wanted to show you is how their dispatch people are now triggering the entire process right from within FileMaker. So they have the ability, what we've done is we've actually integrated, so within this job, this one or two West Broadway, they can turn around and select a company. So again I can select my infamous test company and I can go through and I can activate various people for this job. So if Blake Boyer is going to be on the job, I can make him active. I can also turn around and I can also say I'm going to make Paul Costanzo active for this job. So basically what they're able to do is they're able to assign trucks to a particular job and then the nice thing about this is they can actually go through and generate a text message right from the job itself directly to those people. So if I turn around and say, okay I now want to send out an SMS message, they can turn around, they can select the job, they can select the drivers that they want for that job, and then they can also specify what the topic is. So in this case, maybe it's the directions to, you know, Marsha Pitt from Bull Moose. So I can literally we've built a library for them where they can store these directions within the system, they can call them up and then with literally three mouse clicks I can turn around and I can actually send this text message to these drivers. And you'll see it in real time on the right hand side here you'll see when the message has been sent and actually when it's been delivered. And then I can actually turn around and go through. If Blake wants to go through, he can actually reply back. So once that information's been delivered, you'll see Blake can turn around and reply back to me. So I can sit and say, you know, he's got the directions. You'll notice it marks it as unread, you know, because of the fact that I haven't read it. So if I want to call up Blake's thread, I can click on this. I can see all of the thread that we've done. I can mark the fact that yes, thanks I've read, you know, I've acknowledged the fact that he sent that back. So now we've basically got him on the way to the one or two West Broadway, West Broadway job. So again, the idea here is we've really tried to create this paperless form or this paperless workflow where we're trying to do everything digitally and move people through this process as they go through being assigned a job to ultimately carrying out the job and then finally invoicing for that job. So if you will, we'll just transition back now to real quickly back to the slide piece. And I think, you know, these are just some of the pieces that we picked out in terms of, you know, some of the real key benefits of FileMakerGo, specifically in this project. Obviously a tremendous amount of time and cost savings in terms of, you know, with this system in place, we've now reduced that dependency of having to manually enter information just the fact of having to try to decipher someone's handwriting. You know, when you look at that stack of paper forms and how difficult it can be to try to turn around and figure out exactly, you know, was that a 7 or was it a 1? You know, trying to do all of those different types of things and in terms of the efficiency, I think one of the key things Blake and I talk about all the time is this idea of basically making sure that we have data integrity. You know, the fact that we're not entering in data more than once. So we're never double entering data. But then the data that's in there is all accurate as it relates to all of the different parts of this process. And I guess, I mean I probably let Blake, if you have any comments relative to the increase in time and employee satisfaction, I mean you're probably more equipped to speak to that than I am actually. Yeah, no, it's been as far as entering the data. I mean we've saved hours every single day on how much data it takes to enter. I mean when there's zero data then obviously the one email that you showed us and there was no history. That one's easy. But if you've got 30,000 barrels moved in any single day, that's a lot of manual entry that we would have to do before that now is done. That would have taken 3, 4, 5 hours to invoice. But now within 5 minutes because it's coming through, I can have that invoiced in 5 minutes. And so that cuts out 4 hours a day that instead of having somebody do that, I can have them on something else that's more effective and is going to help push the work along even better. And so from that standpoint it's been fantastic. And as you said, they're not sitting there having to guess what the driver wrote, what his name is, all that kind of information to get back, they're reporting back to the when we send an invoice, there's no question on what the driver's name was. There's no question on how many barrels they actually took out because they've got the signature, they've got everything right there. That portion has been huge and it's been very successful with our customers as well being able to see that and to be able to get the one customer that we send the daily totals out to. For them it's been very helpful as well because they can turn around and take it to the oil company and say, hey look we hauled X number of barrels, here's the proof from Wind River that we did that. And so that's been very helpful for them as well. Thanks Blake. One of the other things that we were just talking about a short time ago as far as employee satisfaction, I think that whole concept of when we talked about that idea of doing that, that create a duplicate ticket, I think the idea of being able to show the power of FileMaker and FileMaker Go of being able to implement something like that in terms of the iterative nature of taking a suggestion or a feature request and being able to turn it around, it really facilitates buy-in from the employees of saying, hey listen this is something we're striving for efficiency, we want to try to make this process better for everyone. And so I think that was something that we saw first hand knowledge of that they really facilitate the buy-in from the end user perspective being able to do those types of things. For sure. So with that being said just real quick I'll just show you, this is actually our contact info. If you have questions about some of the things that we've shown, again whether it's the app itself or just general information, feel free to reach out to us. This is my contact information. And with that then I will turn it back over to Mark. Thank you Paul and Blake. Wonderful presentation and demonstration of FileMaker technology. If you could move to the final slide. We've got FileMaker resources for everybody on the call today. FileMaker Go 12 is a free download and there's the appropriate link to it. We've got other customer success stories that are great to read about not only around FileMaker Go but also FileMaker Pro that our customers are leveraging as well. And then of course FileMaker Web Seminars. We do these couple times a week. In fact I'll be doing another session on Thursday of this week really showing a demonstration of how to build a FileMaker solution from scratch and then extending it out to the iPad. I believe that is Thursday at 3 o'clock central. It's called 0 to 60 demonstration. And of course the last piece there are FileMaker training resources. This is a great area on our site if you want to learn more about leveraging the FileMaker technology and really getting trained on this technology. It's very easy to use but obviously we always recommend some training for new users. Okay. We're going to move over to our question and answer session. We've got about 10 minutes left here and I will read off the questions and I'm sure Paul and Blake can assist with some of the answers. First question, do we need to use FileMaker Server to use FileMaker Go? Well let me answer that question first and then I'll ping Paul as a FileMaker developer and really kind of get his thoughts on it as well. I always recommend FileMaker Server for my customers. A couple of reasons why. It's a great way of backing up your critical data. And as that question was written to use FileMaker Go, the assumption there is you've got mobile users leveraging iOS devices. So when I hear that I think about multiple users. The only time I ever say not using FileMaker Server where you just leverage FileMaker Pro or Pro Advance is really for maybe a one person or potentially a two person company. If you've got more than one person leveraging FileMaker, I highly recommend FileMaker Server. Paul, if you want to add some color to that and talk to your customers, go ahead. I would totally echo what Marcus said. We started out years ago. We've been doing, it's almost, we're entering our 20th year now and back in the day we used to have some peer-to-peer clients that would utilize our systems. And now it's been several years, probably been at least five years that now we've had everyone on server. And really a lot of it comes back to security. It's just one of those things that it's a security and the peace of mind fact of being able to utilize the backup features of FileMaker. As well as just the fact that there's so much power, it performs a well-crafted solution over a wide area network, performs very well. It gives you tremendous reach as far as what you're able to do with being able to be off-site or at another location, but having your data on some type of a centralized server with FileMaker Server is a very powerful solution. Thank you, Paul. Next question. Can I use my database on my iPad when I'm not online? Well, I think both Paul and Blake showed a couple examples of that. Blake's team for the most part, they're remote in the middle of nowhere. And they also went into seeking technology. So once you do get back to that Wi-Fi location, you're able to sync up your FileMaker Go information. Yeah, that's a beauty part of FileMaker Go. You could be online, of course, but also offline. I've got a lot of customers who leverage FileMaker Go offline, either on a plane or in an office space where they just do not have any Wi-Fi. So that's definitely one of the differentiators of FileMaker Go. Next question. How do you get the FileMaker databases onto the iPads? Well, I'm going to advertise a little bit about an upcoming webinar that I'm actually hosting on Thursday at 3 o'clock Central. I will show you live how to extend a FileMaker solution onto the iPads, but I'm going to push this question to Paul as he's a professional developer. Go ahead, Paul. Why don't you take that question? Normally, there's a variety of different techniques. For the most part, what we do is actually utilize iTunes. I mean, that for us has been the simplest mechanism where usually we will move the database over. Part of using MirrorSync is that you must do an initial sync once the database has been put on the device. So usually we will have the iPad. We'll drag over the file onto the device using iTunes and then perform that initial sync and then from that point forward, it's really operating totally disconnected from the network except at the times when it's doing the synchronization. But there are some great resources out there. There's several different methods in terms of moving over the actual files. Thank you, Paul. Next question. Was the MirrorSync tool created specifically for this company or is it available in the toolkit? Yeah, MirrorSync is actually put out by 360Works. They're a great company out of Atlanta. They have a whole line of tremendous products and we've used it in actually probably three of our solutions now with great success. I mean, it's really allowed us to do to really extend the reach of our systems from utilizing the data locally on the device but yet having that full sync capability back and forth from the hosted file on the server. Okay, next question. What are you using to send SMS to be a file maker and can that be implemented from the file maker go app? Well, actually we're utilizing, it's a custom developed module that we've built specifically for WindRiver and then we're actually using an SMS provider. So behind the scenes there's an SMS provider that's actually providing the actual send and receive functionality and then what we've done is we've actually hooked file maker up through the API of that solution provider to actually facilitate the messages going out and then also coming back. At this point we haven't done it on go. I think that's probably something that we've actually talked about. Actually, Paul, I have actually sent messages from. Okay, there you go. It does work. So Blake, that's very good. So he's ahead of the curve already. Alright, perfect. Well, thank you so much, Paul and Blake. That's all the time we have today for our question and answer session and for all the participants on today's webinar. Thank you for taking time out of your day to view our customer success story.