 This is Mark Ringo, Business Account Manager at FileMaker, and I'm your host for today's Getting Rid of Paper-Based Process Web Seminar, where you'll learn how FileMaker's customers like Austin Convention Center and iScience have leveraged FileMaker Go to replace paper. But before we get started, I have some brief housekeeping notes on the next slide. For best experience, we strongly recommend that you participate in this Web Seminar with at least a 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. During today's presentation, you'll have an opportunity to type in questions. On the next slide, we will talk briefly about how to enter a question. Go to the Control Panel, click on Questions 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. The FileMaker platform is not just one product. It is a group of products and technologies that all work together. With the FileMaker platform, you can create custom business solutions on Windows and Mac with FileMaker Pro and FileMaker Pro Advanced. FileMaker Pro is our flagship product and it's what you use to build solutions. However, if you build solutions for a team of people, you'll want to use FileMaker Pro Advanced, which comes with power tools such as the Script Debugger, the Data Viewer, Database Design Report, and also allows for custom menus and much more. FileMaker Server is the hub of any successful FileMaker deployment, which allows you to host your FileMaker solution and provides automated backups and remote administration. And you'll need FileMaker Server to use our new FileMaker WebDirect, which is breakthrough web technology that runs custom business solutions directly in a web browser on a desktop or laptop with no web development skills required. FileMaker Go brings your FileMaker solution to your teams on iPads, iPhones, and iPod touch devices. All your FileMaker solutions created with FileMaker Pro will simply work on these mobile devices. And best of all, FileMaker Go 13 is free at the App Store. So anybody that's on the webinar tape, you've got an iPhone or iPad, go out to the App Store and you can download FileMaker Go version 13 for free and start playing with it. We've got a couple starter solutions that come along with FileMaker Go. On the next slide, I'd like to discuss the benefits of FileMaker Go. What if you can instantly update current inventory levels from the warehouse while scanning bar codes? What if you can capture digital signatures to close sales deals on the road? What if you can collect research data, including photos and audio files in the field? Also swipe through patient's medical records in the emergency room. And what if you could conduct teacher evaluations in the classroom? These are just some examples of FileMaker customers today who are leveraging iPads or iPhones for their business. On the next slide, I'd like to discuss why our customers have gotten rid of paper-based processes. Paper is hard to share with remote workers. The data on paper becomes very obsolete very quickly. And leveraging paper can be a very manual process. And the biggest issue that we see with paper is security. It's just simply not secure. And storage has become very, very costly. And then the biggest issue that both prospects and customers complain about is, with paper, you may have multiple versions of the truth. In fact, we've got customer-safe contractors and landscaping-type companies that literally now meet with their customers and they're able to provide them with a price quote right from their iPhone and iPad. And the customer can simply review. And if they accept the terms of the quote, they could use their finger and sign right there on the mobile device. They could also take a look at specific blueprints and make changes to the blueprints that the contractor provides them right from the mobile device. On the next slide, I want to discuss the Austin Convention Center business use case. Austin Convention Center transformed paper-based service order forms, work orders, and floor diagrams into a mobile application that provides a mobile workforce the ability to view, process, and reference event information across a facility that spans six city blocks. On the next slide, let's discuss how Austin Convention Center operated before FileMaker Go. The exhibitors' work orders were based solely on faxes and paper. The orders were keyed into a system, printed out, and placed into a binder with diagrams and other paperwork to start deployment or fulfill changes. This was a very manual process. On the next slide, let's look at how the Convention Center has become more efficient with FileMaker Go on iPad. The good news, Austin Convention Center was already using FileMaker Pro for their billing system so they could leverage the skill set that they already knew in FileMaker. They didn't have to learn anything new. They very quickly designed work order forms on the iPad. Employees now have real-time access to work orders, change orders, and floor diagrams and easy-to-touch interface. This led to fewer errors, faster installs, and increased customer satisfaction. But more importantly, they had a very compelling return on investment. With FileMaker Go for iPad, the project payback was less than four months with an annual ROI of 200%. In fact, according to the IT service manager, there was an estimated annual savings of 24,000. If you'd like to learn more about this business use case from Austin Convention Center or other FileMaker customers leveraging FileMaker Go on iOS devices, go out to FileMaker.com, learn solutions, then customers, and then stories. And you'll get an opportunity to browse through our library of customer success stories. And some of those, like Austin Convention Center, has a video that accompanies them. At this point, I'd like to introduce Jeremiah Hammond of DB Services. He's going to be taking us through the customer success story for iScience. Thank you, Mark. Today, we're going to look at a case study from iScience of a physical inventory count process that started out paper-based, transitioned to spreadsheets, and ultimately ended up as an iPad application in FileMaker Go. We'll focus on how easy it is to get up and running with an iPad application in Go, highlighting the ease of which you can set up a FileMaker solution to use the iPad's built-in camera to attach photos to a record, and then utilize barcode scanning for faster and more accurate data entry. So iScience's primary objective is to design what spaces and equipment are needed in new or revamped STEM facilities, and then procure that equipment for each space, so spaces meaning rooms, and then STEM facilities, so STEM stands for science, technology, engineering, mathematics, STEM facilities such as hospitals and laboratory centers, things like that. iScience has around 50 employees across the globe. They work on pretty big projects, facilities over one million square feet in size. One of their current projects, the University Medical Center for Louisiana State University, LSU, UMC, is this medical center is replacing Charity, the previous hospital that was rendered useless during Hurricane Katrina. There's a $1.75 million dollar budget for equipment and furniture, and construction was budgeted for about $1.3 billion to give you an idea of the size of projects iScience works on. In this particular case, this facility is expected to open July 1st, 2015. iScience itself is headquartered in Glendale, Arizona, but the majority of employees are on site at whatever project they're working on because these facilities are so large they have to manage everything on site. So iScience went through a couple of systems previously before the iPad application. So in the 90s, they used a paper-based system. You can actually see the paper form there on the left. These systems all center around counting physical inventory, and counting physical inventory only matters on projects, on facilities that are being revamped or being replaced. And the idea here is that these facilities want to reuse the equipment that was in the previous facility for the new one to save on how much it's going to cost to supply equipment into the new facility. So at the beginning of a project, iScience goes through and walks through the previous facility and catalogs all the equipment that's there. And the way it works is they send out teams of two, where one person has a clipboard with that paper form on it, and a second person has a film camera to take a photo of the equipment. So the first person, they'll walk up to a piece of equipment in a room, equipment like operating table or an MRI or a computer, what have you, they'll walk up to that piece of equipment and the person with the paper form starts filling in basic information about it, what's its serial number, what's its make, model, description, and then the location of that piece of equipment. So what building are they in in the facility, what's the floor, what's the room number, and then where exactly in that room is this piece of equipment located. And then the second person who's taking a photo will take the photo and then tell the person, hey, tell the person with the paper form, hey, this is photo number one of film roll three, so that the paper form could, you know, the person could fill in like okay that's that photo so they can come back to it and they can find it later if need be. So they can go, when they're looking at the inventory records they can go okay that inventory record I want to see that photo, okay that's photo one out of three. The, so back at the end of the day the teams would go back to the office and would transcribe what's on the paper form into a spreadsheet on a PC, so you'd have this master spreadsheet on a PC and then they would develop the film rolls and put the resulting photos in a photo album and then have a reference, they would put a reference number in each photo so you would go find it later. So needless to say the whole process was very time consuming. There was a mixture of electronic and physical data. You had double data entry with transcribing the paper form to a spreadsheet and then you had to haul around this physical photo album which, you know, it took a while to even find, when you're trying to find a photo it takes a while and sharing photos of course very inefficient. So there's plenty of places for improvement here. And so in the 2000s when laptops and digital cameras became more ubiquitous, I science transitioned from using the paper form to using a laptop and from using the film camera to using a digital camera. So the, the, there was no more double data entry needed because the person in the laptop could just enter in the data directly into the spreadsheet and you have a digital camera now so there's no physical, you don't need physical photos, you have all digital data. So that definitely saved a ton of time. But this process had its own inefficiencies. The photos were a big part of the inefficiencies. You had to transfer the photos from the digital camera back to a desktop, back to where the master spreadsheet's located. And when you transfer these photos you would have to worry about unique photo names. The, I science only had multiple teams going out, multiple teams of two each day. So when you have, when you take the, the digital cameras from all the teams and you move the photos to the computer, the desktop, you have to make sure you don't have any name conflicts. So you could either rename the photos and make sure all the photos have unique names so they don't override each other. Or you could make folders for each digital camera and each day so that you can just put their respective photos in those folders so there's no, no conflicts there. And then once you did all that, you had to update the master spreadsheet to reflect the changes, the new name or where the, you know, the folder structure. Either way, very cumbersome time consuming process. So the master spreadsheet itself would get very large and it would be hard to search because these spreadsheets would get to be over tens of thousands of records. Data entry is pretty inconsistent on the spreadsheets on the laptops because there weren't any drop-down lists, checkbox sets, ways to standardize input. And then they're also dealing with battery life issues on, on the camera and on the laptop. You, these, these laptops and cameras just wouldn't last throughout the entire day so they're scrambling for outlets and whatever room they're in and that definitely slows down the cataloging process. So these were the previous systems that were used prior to the iPhone application of FileMaker Go. So in, in 2012, High Science was beginning a project here in Indianapolis revamping the Wishard Hospital downtown and they, just by how the, the cards fell, they were supposed to have three years to do the project but they ended up only having one and because of the time crunch, they, they needed to find a faster way to do inventory besides using, they needed something faster than laptops and digital cameras. So they were thinking about having an iPad application. And so they started searching online for applications, for inventory applications, mobile applications and they just couldn't find anything that, that really fit their needs. They, you know, they found, they found systems that are either too complex, too bloated, didn't fit their workflow, were desktop applications, not mobile applications. They just, there wasn't really a good fit out there. And then, iScience ran into FileMaker, eventually ran into FileMaker and they, they took their, the inventory starter solution and realized, wow, this, this, this handles most of the, the, the problems we're trying to solve. So they started running, they customized Jerry, Jerry Club, the president of iScience, he, he took the starter solution from FileMaker and customized it to fit their workflow. And they ended up using that starter solution for the Wishard project, for cataloging inventory for the Wishard project. And I'll, I'll show you, I'll show you guys that here in a little bit. So the, the, the major problems that the iPad application was trying to solve, trying to, it, it needs to have the ability to use the iPad's built-in camera to snap a photo. It needs to store that photo in the inventory record itself so that you don't have to go hunting and finder for the photo if you want to look at it. It's just, when you see the inventory record, boom, there it is. So that increases just efficiency on that alone. And they wanted to use a barcode scanner to, to have information automatically populate into a new inventory record based on a tag number, based on that barcode. It's a tag number. And this, this actually what is relevant to the LSU project at the Wishard project is where they needed this barcode scanning to work. And I will, I'll, I'll show you guys that in a little bit. But that's where we, DB Services, came in. We, the, the starter solution handled the photo side and got that all working, but the out of population of data, we, we ended up doing for, for iScience. Okay, let's go ahead and dig in to these two systems. So I'm going to show, I'm going to go ahead and show the starter solution that iScience had for the Wishard project, the previous solution, and then I'll show you what their current system, the one that we built, how that looks. So, first thing we're going to do is to show the starter solution. I am going to go ahead and put that on my iPad. So to do that, I'm going to use iTunes. So let me get that going here on one second. My, my iTunes is trying to back up my iPad. See if I can get it going. Okay, good. All right, so in, on it, in iTunes, you would select your iPad here. So you got my iPad. And then you go to apps, and if you scroll down to the bottom, you should see FileMaker go in the list here in the apps list. And then on the right, you will see a list of documents for FileMaker Go. And all you do to get a FileMaker file on to go is you just drag from the desktop into this list of documents, the file that you want to open up and go. So there you go. Simple as that. Let's go ahead and get go up and running here. Let me show you guys that. Let's get that on the desktop. Okay. All right, so I got go here. Let's go to the device, let's open up the Wishard starter solution. Okay. So this is a list of, I got some sample data from the Wishard project, not a lot, just to handful of records here. This is a list view. So I'm just going to tap on one of them to take you to the detail screen. So this is really where Jerry customized, the iScience customized the system. So you'll see there's already some branding here. You got the iScience logo, you've got the name of the project. So Jerry, Jerry the president, he did all this. He customized the starter solution all in one weekend. I'll show you what he did, but it was enough for him to get up and running, and it solved majority of the requirements here. So he changed some of the styling here, changed a little bit of the way this looks. And then he removed fields from the screen here that weren't relevant. When you get a starter solution up and running, when you create a starter solution, there's already some fields there for you, some standard fields, there were just some that didn't apply to the workflow. So he removed some and then added ones that were relevant. So you've got this department, you've got room number, room name, you know, what's the item manufacturer, so on and so forth. So he went through, he made fields, he added them to the screen and he changed the labels here. And then he also put drop down lists where they made sense. You'll see the little arrows here. If I click on one, you'll see the list show up. So there's, you can standardize data entry. I can just click on that and if I go back up to the top, excuse me, you'll see there, put the value in the field. And so he went through all the fields where it made sense to standardize data entry and he went ahead and did that. And then he also added these checkbox sets here on the right, which are very similar, they're very similar to value lists, how to set them up. So he, you know, standardize data entry and he also made data entry faster in this case. You can just check, check, check, you just tap on it and there you go, tap on it. There you go. And then finally, the big thing, the big thing that this did is it had a photo field on it. The inventory start solution already had a photo field and it allowed, it allows you to use the iPads built in camera. So let me go and show you that. I'm going to make a new inventory record. I'm just going to name it test and you'll see here that you just tap on the field to take a photo. So I'm going to tap on that. I'm going to press camera here on the right and then I'm going to go ahead and you notice the camera comes up, I'm going to take a photo of my keyboard here and then I'm going to press use photo, there you go. So just by that photo field alone, we solved the major problems with photos. No more need for a digital camera. You can use the iPads built in camera for this. And then a file maker automatically takes that photo and stores it with the inventory record that you're on. So there's no more hunting for photos and finders. And Jerry, iScience didn't have to do anything. It was just already there out of the box. So I'm going to go ahead and show you, even though it came out of the box, it's very simple to add a photo field. It's also very simple to add value lists. So I want to go ahead and show you how to do that. So I'm going to close this, then I'm going to, I'm going to go ahead and show you the desktop here. So to make changes to layouts, to make design changes, coding changes, you have to use FileMaker Pro on the desktop. FileMaker Go is meant only for, it's meant only for data entry. So I have the wizard solution up here. I'm going to go to that iPad details screen. And you'll see that's what we were looking at on the iPad. So let me go ahead and let me do the photo field first. So I'm going to go in the layout mode here. This is where I can make changes to the layout. Then I'm going to go up to the database, so File, Manage, Database. And then I want to make sure I'm in the inventory table, because that's where I want to add a second photo field to, so I am. So I'm going to type in photo to here to name the new field. And then I'm going to change the type on the right to container. Container fields are where you store binary data. So in this case, we're storing photos. Instead of we're not doing text, we're doing binary. So I've just made a container field, and I'm going to press Create. And there you go, the container field's been made. I'm going to go ahead and press OK here. And then I'm going to add the photo field to the layout. I'm going to use the field picker up here. And I'm going to scroll down to my new photo to field. At the bottom, then I'm going to drag it on the layout. I'm going to resize it so it fits in this little top left corner. And then I'm just going to save the layout up here. And that's it. That's all you need to do to add a new photo field to a layout. And I'll show you that this field works identical to this here in a second. So the second thing I want to show you is adding a new value list and how simple that is. So if you go to the dimensions field, I'm going to go here down at the bottom, use this. So let's bring in the inspector pallet. Go to the Data tab. And then right here, you've got edit box. That's what this field currently is set up as. It's set up as a free form field. Just type whatever you want. I want to change this to drop down list. And then values from where do you want to have your value list derived from. We're going to go ahead and make a new value list. So I'm going to press New here. Let's call it dimensions. Let's just add a couple test values, 5 by 5, 10 by 10, 15 by 15. Press OK. And then to be consistent with the way that iScience set up the field, I'm going to go ahead and add an arrow to show and hide the list. I'm going to check this little box right here. And I'll save my layout again. OK, so we've added the photo field. We've made the value list. So you can see the photo field is here. The value list, you've got the dimensions there. I'm going to show you that this works on an iPad. So I'm going to replace the old version with the new version. So to do that, I'm going to use iTunes again. And there's other ways to move files from the iPad or from a desktop to an iPad. iTunes is one as I'm showing. You can also attach it to an email and just send it via email. And then you can use Dropbox as well. So there's a number of ways you can do this, but we're going to use iTunes for this demo. I'm going to go ahead and drag it and override what's already there. You'll see it's asking, do you want to replace the old version? The new one I do replace. Let's go ahead and take a look at my iPad. I'll get that back up here. And I will show you that. Just open up Wishart again. Just go here. And you'll see that the Photo2 field is there now. This is the updated version. And that the dimensions does have a dropdown. So OK, so I'm going to move the current system that I signed using to my iPad here. So let me do that. And let's bring back up my iPad. OK, I'm going to open up the current system here. OK, the first thing you'll see that it looks pretty different from the starter solution. That's because we actually built this system from scratch. We didn't continue with the starter solution, mainly because the starter solution had other things that we didn't need in it. We just wanted to have a fresh start. And we decided to skin the application so the colors are more along the lines of the branding of iScience. iScience is blue, grays. So instead of the brown and the blues. And you'll see up here in the top that there's three modules. You've got the inventory module, which is the main module. And these other two modules are really set up. And they're for the auto population of data based on the tag numbers. So you've got financial asset module here. And you have a C equipment module here. And if you notice, you've got the asset number here. And this is what's on the barcodes so that this is what will fill in on the inventory record. And then the description from this asset number, make, model, serial number, et cetera, will fill in on the inventory number when you type in that asset number. And the C equipment is the same way. It just has a C number here. So these financial asset numbers and C equipment numbers are just numbers that are assigned from Louisiana State. They're from different databases. One's from financial database and other ones from a clinical engineering database. But the idea is iScience was leveraging this data to speed up data entry on the inventory collection side. So that's what they wanted us. That was the primary focus of this application was to build the ability to put in an asset number or a CE number and for all the information that it could to populate automatically so they can catalog numbers faster and more efficiently, which ultimately will save them money and it saves the client money as well, the hospital in this case. So I'm gonna go and show you how that works. I'm gonna make a new inventory record here. And so you'll see that the description's blank. We do have these filled in and I'll go over that in a minute. But the rest of it, like the details here, manufacturer make, model, serial number, et cetera, those are all blank. So all this information should fill in when I type an asset number. So I'm gonna do that manually. So I'm gonna go one, four, one, five, zero. So you'll notice that it didn't find anything here. We actually have an indicator that says if it found a match or not. So that this increases the accuracy of the input. So I noticed I mistyped, I added an extra one here. So let me get rid of one of those and I do that. There we go, now it says found and you'll see the description filled in and then the details here, the manufacturer make, model, serial number, et cetera, all filled in and that came from the financial asset number record that matched this asset number. So let me just show you that the CE number as well works. So once I clear up the asset number, notice all the information cleared itself out. So I'm gonna type a CE number in here. If we go, there we go. So the same information, description, manufacturer make, model, et cetera, all filled in. So it saved them a significant amount of data entry time and it made the data entry very accurate. So they wanted to go a step beyond this and they wanted to be able to, they wanted to be able to scan the barcodes and then have the barcode contents automatically populate the asset number or the CE number. So they used a third party Bluetooth scanner, handheld scanner for this, but you can also use FileMakers native barcode scanning and that's what I'm gonna show you guys here today. So let me go and I made a separate layout for the native barcode scanning. So I added a scan button here. Let me show you how that works. So let's make a new item and I'm gonna press the scan button and it's gonna bring up the camera because the camera is what's used to scan a barcode. So you'll see I have a barcode right here and I'll put it in front of the camera and it should capture it once it focuses itself well enough. There we go. And so you see it filled in the FileMaker, filled in the asset number from the barcode and it did the same thing as manually entering it and auto-populated all the data. So let me go and show you how easy it is to set up that scan button to set up scanning, barcode scanning with the native FileMaker capabilities here. So let's close this file and let's go back to the desktop because again we need to use FileMaker Pro in the desktop to do any design changes. So I'm gonna open up that same system and I'm gonna go and just use this, the main layout here to add the button. So I'm gonna go in the layout mode and then I'm gonna go to insert menu up here and go to button to add the button and the barcode scanning is just one script step which you can select from the standard set of script steps here. So I'm gonna do insert from device and then I'm gonna specify, I'm gonna pick the target field, I'm gonna pick the field that FileMaker is gonna put the barcode contents into. In this case it's gonna be the asset number field. So I'm gonna press okay there and then what are we inserting from? We're inserting from barcode. That's what you wanna select and you can just go and press okay on the screen. Press okay and then we need to name the button, name it scan just like the other one. I'm gonna drag it here in the top left. That's where we got some room in the layout and then I'm gonna save the layout. So now we have our button here and now I'm gonna take this new version of the system and put it on my iPad just like the wizard changes we made. So let me get iTunes back out here. Let me drag this and press replace. And let's go ahead and open up my iPad again. Let's open up the inventory tracker system. So this is the new version. You'll see that I have the scan button here now in my iPad. So I'm going to make a new record and I'm just going to do the same thing as before. I'm gonna press the scan button and you will see that it works just like the other scan button does. There we go. So simple as that to add barcode scanning to FileMaker Go. Okay, so the final thing I want to show you here is I'm sure you're thinking how if you have a handful of teams going out with local copies of this application and gathering data every day, how do you get all that data back together? So there's a number of ways you can do this. In the case of iScience, they were totally fine with taking the copies the copies of the file from each iPad, all the copies from the iPad and importing them in manually into a master copy on a desktop. Let me go and show you how that works. Let me, I'm going to, I need to move a copy I'm going to move a local copy here onto the iPad and let me open that up on the iPad. Get this up. Okay, so I've got this, go to my device. All right, I've got this import file. This is a local copy. I just want to show you what's in it. So we have four records here and they just, each one have photos and this is just, these are all the inventory I took for one day. Let's just pretend this is all the inventory I took for one day. I got these four pieces of equipment that I did and I want to go ahead and get that into the master. So what I do is I close my copy here on the iPad and I go to iTunes and I do the opposite. Instead of moving something from the desktop into iTunes, I'm going to move something out of iTunes into the desktop. So let me drag, just click on this here, iTunes and I'm going to drag it to the desktop. There it is. And I'm going to open up the master. I have a master copy here on the desktop and I'll open that up, File Maker Pro. And you'll see there's five records in the master and once I'm done importing from the iPad copy, I should have nine. So if I go up to file here and go import records file, I'm going to go and select my, let's go select the local copy which I believe is right here. Okay, here's the iPad copy. So it brings up field mapping, a field mapping dialogue. So you need to make sure that everything's set up here appropriately. I'm just going from inventory. So the source here is the iPad copy. So I'm trying to import inventory records from the iPad to inventory into the inventory table in the master. So we're doing inventory to inventory and we want to arrange by matching names since these are identical copies of the same application. And I just want to make sure all the arrows are matching up here and they are. So I'm just going to press import and then just press that again and File Maker said, hey, we added four. Great, if I do a show all here, you'll see I have nine records now. And there are my records from the iPad. So that's what I signed for the other day and we could have gotten more elaborate on this method but for what they wanted for the LSU system, this the auto population and everything was so, you know, the increase in efficiency was so great that they didn't need the more elaborate syncing solution at that time. So the transition from the paper to the spreadsheet to the iPad application, it reduced time to take inventory threefold with much greater accuracy and it resulted in lower fees for iScience's clients, the hospitals and it also gave greater profit margins to iScience. So that's it. Thanks, Jeremiah. That was a great presentation and demonstration. Oh, well, hold on, Mark. Let me, I apologize. I do have one other thing here. Our services, if you're interested in DB services, helping you get up and running with a mobile application and File Maker Go, feel free to contact us. We offer support, development, training and coaching and licensing services. You can learn more at our website, www.dbservices.com. Thank you, Mark. On the next slide here, I wanna talk about some of the File Maker resources that we have available out on our website. These are important links that you can definitely copy down. As I mentioned at the beginning, File Maker Go 13 is free to free download. More customer success stories. I mentioned this at the beginning as well. We've got a whole library and videos of different success stories, like the couple that you heard about today. And then we've got traditionally every week, we've got web seminars on different topics, including this one, paper replacement. And then finally, we've got some training resources as well. So, next slide please. This being probably the most important File Maker training series, this is our basics. And this is actually a free download. So for the new folks on the phone today that are just learning about File Maker, this is a great training session for you to download, File Maker Basics. It's for beginning developers. And then if you get to the point where you wanna start developing solutions for your organization, we have the advanced version as well.