Sign Nebraska Travel Agency Agreement Mobile

Document type sign travel agency agreement nebraska mobile

I'm so yeah my name is Manish my last name is actually engineered just in case you're wondering what's going on I get asked all the time I'm actually on the business side I'm not part of IT here but uh Diana's my counterpart here in the technology team and I don't know if we show the technical the safe harbor that we've all seen a thousand times so just really quickly we're gonna be going through just kind of a back on and who we are just the business problem that we had at moma and then how we went about solving that basically and we'll do a quick live demo here they were just trying to hammer out so and then we'll tell you kind of the results of what happened and the results just came in this past Saturday so this is all very recent very new for us so really quickly we were found in 1929 we are not affiliate with a San Francisco Momo we have an operating budget of about a hundred and fifteen million we have a hundred and forty thousand members everything from low end members who pay $85 a month to very high end members who pay ten twenty thousand dollars a year for their membership here's some of our famous works you may recognize starry night one of our most famous pieces we have other works like Jackson Pollock that you may think that you could probably paint yourself other famous pieces by Andy Warhol were Alex ensign we have some more contemporary pieces Marina Abramovic did a performance piece where she SAT for like 10 hours at a time basically and people came and could sit across summer we had a the rain room you may have heard of it was a building that was built outside of moma in the lot next to us and basically you could walk in and it would rain everywhere except where ever you were standing and the wait times got 29 hours to get into this so this kind of leads into what are our business problems one of them is these long wait times people love our art and they want to come and we have a lot of crowds a lot of tourists come especially when it rains they come to the museum here's our current setup we have four of these in the lobby right now you can see we have a laptop that is supposed to be mobile but really it's connected to a bar code or a mouse one printer to printers three printers just to give you an idea of everything that's going on so it's hard to deploy not really mobile I talked a little bit about the long lines we had this is going down the block this was a couple months ago you can see the crowds that come that they have to sell tickets to so we say one thing that we want the art at moment to be challenging but we want the experience to be easy this is not that easy to get in so this is what we were working with no one of the other issues is that we're expanding the museum just like the SF over here where we're building on we're gutting our lobby we're getting rid of all the tables we're going to have multiple points of entry and we really don't know how the new museum is going to be yet so we're basically tasked with coming up with a solution for a architecture that we're not even certain yet so it's a little bit of a tough point so we had to kind of come up with a fluid dynamic solution and so that's why we went with mobile and one of the other things too is we have other locations we have moma ps1 out in Queens which is across the river and you see we get large crowds there as well that we have to deal with and we do events outside of the museum here we had a vent at the Rockaways on the beach just about an hour outside of moma we actually showcase more art outside of our building last year than we did inside of the museum so it just shows you that we really have to take our business now everywhere throughout the throughout the world we did a big donor event in Chelsea which is the art neighborhood in Manhattan and we basically kind of wanted to invite some of our high-end donors to a little gallery and here's Diana and myself and our front desk manager trying to sell memberships there we weren't completely successful but we're able to use the app that we came out with so here's the implementation process here's how we went about doing this we hit here's our core team we basically had a business team within moma myself and basically we included the front desk manager where people from all the different departments and then we had a technical team that diana know if you want to speak to the technical team good afternoon everyone um I'm Diana pan I'm responsible for technology at the Museum of Modern Art in New York and we've been working with Salesforce since about 2011 and it's been quite a journey for us this application which is our mobile application to support membership and visitor services we had it in our head for a couple of years and really very recently we launched it in July actually July 21st and we've been evolving it since so the team that supported this is I know this is one question people frequently have how big is your team we're museum we're very poor and my staff in technology is just a couple of people and so we partnered with a pee really with our Salesforce implementation and they were extremely instrumental in helping us and then we also partner with a mine tree who already has a relationship with the museum and so a lot of our development was done offshore so um in terms of our technical team we had a few people myself on site and then um and then we had a UI UX person as well as developers a QA team offshore it was challenging but it worked out quite well so um I want to talk a little bit about our implementation process so um because this is a brand new application and as you saw from manish the other slide there was this Windows application that communicated with a as400 and that is 400 was a 30 year old application so you're going from a Windows client application environment to possibly something that's mobile because we needed we needed to be mobile we needed to explore different tablets so so this wasn't like any other software development project because because um we needed to look at not just the application but we needed to look at the device we so we needed to ask ourselves is it going to be a samsung because Samsung has just given the museum a large grant or should we look at Apple because we know a lot of our users use apples so in the end we we chose the Apple iPad and then of course that came with a whole bunch of questions should it be the mini should it be the larger one or should it should we worry about the one that's going to be announced tomorrow so many many questions and then all those connectors to printers they were they were issues too so number one we don't like printing actually but we know that our demographics because the member pool they actually like to have something physical many of them like to walk away with a card they like to walk away with a receipt so we knew we had to support some amount of printing but it was also our goal to get rid of some of the printing and move towards email receipts possibly ecards down the road so that's still in our future not yet everything's phased so there was a great deal of research just plain research sitting down with our users looking at what they're doing today looking at the device so if it's an Apple iPad what are all the possibilities that can connect to it from a printer standpoint and then because it's going to be mobile we needed to just look at holding it because we have people on our staff their union they're part of a union so we have to make sure that everything we've build and give to them is ur go friendly so a very heavy iPad with a scanner associated with it you know I tried it out I entered my password and my wrist was too tired after that so I knew that was not the way to go and we settled on the ipad mini and um oh the process I'm just talking and talking um okay so so so we did a lot of the point I'm making is proof of concept and prototyping is very very important and then of course in the application design process we wanted to make sure that it was fewest number of clicks you're going from a keyboard based application to touch screen so we allocate a time for a beta launch so our July launch was actually a beta launch and we wanted to learn from the users okay and then of course during the development phase we kept checking scope making sure there's no scope creep and then once we started to launch we took an approach of a very phase launch so even right now if you go to the museum at the mem ship tests you'll see two of the new iPads and you'll see two of the old stations and so we're slowly rolling it out one two and then three and then it before and we've deployed mobile people out there already and we've had incredible results but we've also learned from it so we changed some of our user interface to adapt to what we've learned in the beta so a phased approach is really key and then the other point I really want to make is post production support don't think that you roll it out and you're done make sure that you allocate time money and people for post-production support ok back to manish thanks sorry shrimping ahead there so part of the planning part we didn't just we look at a lot of the data going on right now in our lobby and we looked at things like the lobby our categories that were selling for our memberships and we saw that a majority of them were the lower end members but we also had some very high end members coming to the lobby so we want it to be while there's less percentage of those those people were just as important if not more important than the other members so we want to make sure we flag those members and you can see that they're like a VIP member basically within the app and then we also looked at what their transactions like are they new or they renewing and basically a new member you have the key and all of their data from scratch or renew is basically just renewing them and you already have their name and address and we saw that ninety percent of the renewals wanted everything to be the same they weren't trying to change your address or anything so we want to make that as quick as possible for them to renew so we looked at it really a lot of a data as well and then we looked at like basically like where are people coming from and we have a lot of different countries that come to the moma so we had a make sure we had multinational support we had a lot of different languages different addresses that we could enter in into our system and we didn't look at data we also sat down there like Diana said we sat down at the front desk and we worked there for a couple of days we got our hands dirty I was trembling with fear trying to sell memberships and trying to speak Portuguese to people who were wanting to buy a membership and so Diana talked a little bit about the technical solution okay so so this is at the super high level our application solutions so so as I said we ended up with the iPad so really excited about it but we also have to have a lot of connections in and out of this iPad so the easy part actually is Salesforce so after we decided on samsung vs apple and what kind of sleeve to have it held in and what kind of scanner we also have to think about the application so is it a hybrid application is it is it a native application so all those were considerations and we settled on a hybrid approach where we're using this visualforce pages remoting into web services for a lot of the business logic and so that's on the salesforce side and then the web services also processed our payment so credit card payments were supported there we we also have connections back to our our finance our finance systems for accounting through through there up here we have iOS plugins directly on that's native to the iPad that we so it connects to our credit card scanner which is also used for our membership card scanner and then a bunt a couple printers a Bluetooth printer for those who still opt for a a printed receipt and we're finding that most people don't so we're excited about that and then the membership card people still like to walk away with something although and that's okay sometimes we'll mail it mailing has a cost so for people who want to mail it will make a separate request to our vendor that prints cards so that's and then I also want to make a note up here we we have integrations back to our other systems such as ticketing because by the time you purchase a membership and when you enter the museum we want to make sure that it can be scanned so it needs to have integrations back to our old our existing ticketing systems and down the road it will have integrations to our retail systems as well because if you buy a membership you might want to buy our exhibition catalogue and and so we want we want this to be the one stop you know person comes they buy the membership they can buy the exhibition catalog and then they can enter the museum so in terms of technical considerations I talked about the hybrid vs vs native as well as salesforce1 we looked at as well the external peripheral devices many of it the printers of course there there are I OS plugins the mobility we rely on moma Wi-Fi but Wi-Fi as you can see it's not always reliable that's why I was over there really nervous but it's good right now so I hope you'll be good during the demo but we also have a data plan which we will we will have for all the devices so we don't have to be entirely reliant on them on spotty Wi-Fi ok and the redundancies so um so we have our sales force team somewhere here we expect sales force to be up ninety-nine point nine nine nine nine nine nine nine percent because we actually don't have another redundant solution right now so sales first were to go down right now we we wouldn't be able to run this demo but I know that would just never happen right um but we have looked at other options and we're still exploring the use of Heroku for a simple redundant solution and and smart store we looked at but there were some limitations in terms of amount of data so we're probably not going to go with that approach okay so Kumar over here who's been with our um mindtree team we're very lucky and fortunate to have him be at this presentation as well he comes to us from Bangalore and he was the chief architect for the the technical solution during the implementation phase so he's going to talk to you a little bit about some other issues related to security and performance in the actual build out Thank You Donna hi everybody I'm going to take you through these security the performance and the framework implementations of our application as mentioned by donna asses and hybrid application is closer is it this is fine yeah as mentioned by Dinah this house is an hybrid application so we use a sort for our authentication with hybrid applications the data on the way of pages and the effects everything is inside sales force how about some data which is which can be local device so that you can access this faster it's always better to hit the memory rather than hitting the disk for your data so for that we use the Smart store mechanism in which the data is stored as soup objects inside sales force inside your local device and then Salesforce takes care of this life span of the data inside the soup objects every time your user is user session is validated and if it's successful the data is persisted inside the soup objects and once the session times out or the user manually logs out then the Salesforce mobile sdk takes care of wiping out the data from the smart store so it's the optimal box features which is given by the Salesforce and it is encrypted too so that adds security to our lair the performance of our application which you are going to visit witness in the demo but I'll tell you it's not because of our performance tuning mechanism its new design consideration it was the primary factor which decided our design of the application there is a lot of business process associated with moma so we categorize them into synchronous as well as asynchronous mechanism the minimum data that is required for our visitor to enter the museum is processed first so that he goes inside the museum and all the other activities will be happening in the background as I mean thanks to the future annotation method of the epochs and with this we made sure that our visitor spends more time inside the museum with the art rather than spending time with our service associate and standing in the queue and we use visualforce remoting for accessing our web service layer instead of the wrist or the contemporary so based mechanisms and which gives faster access to the service layer and also bypass certain by governor limits like the heap size so that helps us axor I mean increase our performance in our application like any other mobile application we cash the images the stylesheets the JavaScript frameworks and also the HTML templates so that the pages are loaded much faster ok let's go to the demo I mean you be back whaddaya all right let's actually show you guys how this works here so we'll try to put this up on their app here and here's the app you can see diana is addressed as a sales associate if you can't see her i was trying to find her in the keynote and she actually waved this shirt in the air and i was like oh my god so all right so this is a way of some of our art in the background here for people to see and I lacked a part of a member coming to the desk good morning may I help you yes I'd like to renew my membership my name is Manish so the search is through social search because it's faster and it could search across multiple objects so I'm searching here one of the things we learn we used to have auto-suggest in the search bar but we learned that that was and didn't work out so well so I do find one each year I have my card here if you'd like to scan it I would wait there he is there anish Mary and Manny and you'll note so we have a built-in a card scanner here that functions both as a barcode scanner and a credit card swiper so it's a dual purpose for the ipad it really makes it mobile we're trying to cut down on the number of devices tied to it so yeah so here you can see I'm the primary contact with a secondary Mary Manny my kid oh yeah um I love to engineer what can I help you with I'd love to renew my membership so um so these are the different functions I can help him with today but it looks like he wants to renew his membership and because as Manish mentioned earlier renew is one of the most common features so we put in a single single click renew just like a single page right here out so it's one click and that's been one of the most successful features of this that people come in as a large crowd you hit that button and it just keeps all of the same preferences and takes you to a basket and it has a family membership and he can choose to just check out now or he can do something else in this case what actually I forgot my address changed I just moved okay so let's go in and update your address so we'll keep it with Family Center che so we'll keep it a family membership oops and you tap the pencil icons here brings up memberships and these are all contacts within an account if you're curious of how it looks in Salesforce so addition address 25 West fifty-third Street and this part here is pulling in from google geolocation API so we're cleaning all the data and it's kind of pre populating here so this helps speed up a transaction this goes back to we want to make the transaction as fast as possible so we can get it within a few clicks and then we also merge an apartment number because Google doesn't have apartment numbers in their addresses so one of the things I mentioned with the beta period this was actually one that we played with a lot with the user interface and we learned that basically there's no address we found where it didn't come up so we were able to hide a lot of the other fields but if if one such address did come up we could still manually enter it she kept on this T here and you see that it broke out the fields and this is happening locally so then yeah so then we just save ok so we've changed his address we're ready to renew him mr. engineer is there anything else I can help you with actually I my friend Kumar yer I'd like to buy a ticket as well ok Jessa Kumar yes I don't have any other friends ok so this goes into the ticketing portion of our our applications so he only has one friend today so we'll just do one guest ticket and this is oh good sorry all this data is being tracked within Salesforce so we're able to capture when members come in how many guests they have and things like that so I'm looking ok so we have to hurry up um ok so mr. engineer are you ready to check out yes ok and this is hitting our live production system I just want to mention that so um how would you it's a it's two hundred eighty dollars and how would you like to check out ah i use my corporate career fair you checked guys a credit card okay and would you like your receipt email to your pretty yes please email it to me okay and we're maybe i'll print as well today ok so this device is the same device where we scan the member card and we're charging his real-life credit card see runs he's going okay and I have an add-on membership so basically in the card printer it's prompting us to put in a separate membership card in the printer and then complete transaction you see we have a Bluetooth printer here voila and that's the end of the presentation well actually there's just one one little bit more um ok so so we'll just switch over to the other oh I forgot to print a ticket ok the ticket is printing so we separated the ticket and they receive ok I think we just have a few minutes here so we'll try to just fly through here to leave it open for questions yeah we have like one question here I think Sandra's telling us yes yes back there yeah it is not sales first one I'll let Kumar him yeah hello thank you for your question this is hybrid remote approach what we have taken with the Salesforce Mobile SDK yes I yeah we used okay the UI libraries what we used where the force TK and the remote DK libraries plus the UI what you see the wonderful UI is from the bootstrap and the angularjs things and we use HTML local file storage with this march toward frameworks and these are the different types of overview I can say and we can discuss in detail also few any other questions so it took let's see we started documenting requirements well we started working on the UX in December and we launched it in July yeah but we had a lot of things going concurrently as well we had user ability with proof of concepts going that mat lam yer and other teams were working on so a lot of things were having concurrently okay I think that's all we have time for I just want said we're gonna post the presentation I know a lot of you are taking pictures and taking copious notes we are going to post a presentation so I just want to thank the folks from Umeh for sharing their attorney with us so thank you all for coming