I don't want to introduce about myself because this entire session is about introducing myself. That is what you are going to see because I'm going to run through all that I went through. And whatever that I put across may not be the accurate fact. This is what I observed over the 15, 16 years actually. The story that I'm going to tell you started a little earlier than it is mentioned because I joined around 2003 but the story starts a little earlier. So the idea is I'm here not for making this after long time. I'm actually making a presentation without code actually. So if anything doesn't go wrong, anything goes wrong, please excuse me. So okay, so confusion and confusion of the web developer. So the session itself will speak, so we'll get into it. So the agenda of this is how I entered into the industry and how you become a king of web development. If not a king, how you look like a king? That is what I'm going to talk about. So now when I started my career, I started with an airline company where we make softwares for airline ticket booking and all those stuff. And our people are very, very, very strict about UX and all those stuff. And when I started in 2003, there was no rich client and all those stuff. At that point in time, they draw a flight and then they want to book the tickets inside a flight. And we can't get into that discussion and all those stuff we need to do. We have no other choice. So at that point in time, there were two kind of client. So I'm talking about the time where there was no Chrome. The web is not considered as a client at all. So there is something called thin and thick. What is thick? Usually when I say thick, if anybody familiar with VC++, Swing, DB, all those things, they are called thick clients. How many of you have worked on that? Very good, super. Okay, so how we differentiate between thin client and thick client? Thick client, let me talk about thick clients. Thick client means they run on your client machine. So for example, applications like MS World, PowerPoint, Photoshop, they never intend to run in web.  And they run offline. You don't need internet connection to run your applications. And then the application state navigation, that is quite tricky. When I say application state, when you go from one screen to another screen, what is the data that you pass and what is the current screen's data, these are all maintained by the client. And flexible with screen size, okay. So they provide a lot of options where there is something called grid layout, grid back layout, border layout, and all those stuff. The purpose is you take a screen and you minimize or you maximize. Your screen should look solid. And as you keep minimizing, it will keep adjusting. So basically it's flexible layout where the layout does not go and sit there, rather you say, okay, if this much of size sit here. If this much of size, it's like a planning, actually. Planned layout, we were provided with planned layout. So that is one and another thing. Then we usually do thick lines with programming languages. Java, VC++, and all those things. But actually this thin line, right, that is thin client. But whereas in the web, they don't have anything like a programming language. They use something called the JavaScript, which is at that point in time scripting language. It never considers a programming language. And then we used to develop components. We used to develop components. When I say components, a component is not just a text box, combo box, kind of stuff. A component can be a flight, a component can be a room, or a component can be anything that you will be able to visualize. So that is not a component, but you can't even think about components in this. And finally, or most importantly, when you make a connection to the server, it is not just a HTTP. You can make a binary connection also. But the problem, the thing is, they render only what is modified. They don't render your entire page. But whereas here it is all pages. I don't know whether anybody did the paging, at least. So now I will start with the web. What happened to the web at that point in time is, it started around 2000, I mean, I'm just starting from 2003. There's something called servlet. When I say servlet, you write your code. You write code to generate HTML.  You will screw up the application, right? And that's what we are doing initially. And then came JSP. JSP is kind of a markup where it looked like HTML. It looked like HTML. And then we put, at that point in time, it's an interview question to clear the interview, one of the standard questions that we will be asked is, what is the difference between servlet and JSP? If you put HTML code inside Java, it is servlet. If you put Java inside HTML, it is called JSP. And that is how we clear our interviews. And then we all were safeguarded by this guy called Strats. I don't know how many of you are aware of Strats. But Strats is the core reason that we got into at least three digits or four digits salary, actually. At that point in time, if you know Strats, Strats does nothing. Model view controller, the separation of concerns. It will do for you, for your web development. At that point in time, it does a breakthrough. And then we got all our salary takes there. But actually, technically speaking, I think around 2006 it all started. There was people called Tapestry, Vicket. These people, they make component framework. When I say component, it is not the component that we use today. Rather, instead of constructing pages till what we were doing, they started constructing individual components. And then each of these sections are component, but still they were rendered in server. And then 2007, somewhere, JSF came. And then entered GWT. GWT, when GWT came, the idea was very, very new. And people started using GWT, not for any specific features or something like that, because of one single tagline, because Google runs on GWT. And everybody started using GWT. And finally, within six months or something like that, Google decided, no, it's not a good idea to use Java to generate HTML. Scrap it. We scrap, but the projects are gone. So now this is what happened. And this story will come to this later. It's kind of a nonlinear way that we'll go. And my interest towards after started like this, actually. When I joined the industry, I was also one of the developers who thinks that it's the programming that gets into the software job. And then if you go to a software company, every individual that you see are programmers. That's a misconception that I had, like anybody else. But when I entered into the industry and then I got into the company and then I was working day and night, like any other pressure, though, I looked into a specific set of people. And their characteristics were very, very unique, actually. And they always come on time and live on time. Nobody questions them.  They don't speak. Their diagrams speaks, actually. And then whenever we ask a question, the answers are set up predefined. And the best practices are also kind of predefined. When I don't get both, they will give book references. They will say, OK, go and refer to this particular book. And then finally, as they grow, independent of whatever they do, their growth is actually guaranteed. And these are some of the questions. What is the database? And then they say, Oracle, there is no choice for stuff at that point in time. So they say, Oracle, very good choice. And then how do we connect? There are three connections. It's quite tricky to make this decision, actually. There will be three options. JDBC, EJB, Hibernate. Relate that with your JavaScript framework. Relate that with your JavaScript. There are three options. That itself was difficult at that point in time. Now, system integration, JMS. Containers. Containers. At that point in time, the containers are like WebLogic, WebSphere, all these things are there. And when it goes to container, it is like a next level for those people. So they will ask containers, that's tricky part. What is the license that you have? Do you have IBM license? OK, use WebSphere. Do you have Oracle license? Use WebLogic. And that's how they decide containers. And these people are called solution architects. And at that point in time, I decided I will also become a solution architect. And this is how the back-end solution architect's life cycle is. Somewhere there, we started with J2EE. And then we need to upgrade ourselves. After two years, there came Strats and J2EE. After that, Spring, MVC, and Hibernate was a trend. After that, Spring and JPA is a trend. You might ask, what is the difference between these two? All are same. Only name is different. And then Spring, MVC. After 2002, it became easier, because Spring itself integrated everything. So you don't need to go out of everything that you ask. It is like, after a point in time, it is like Spring x, Spring y, Spring z, Spring a, b, c, like that, actually. And then came the biggest market disruption at that point in time. And architects who knows that technology are considered cutting edge architect, actually. And I was one of that, actually. I was having a lot of promotions and all that stuff that point in time. And what is that major disruption that happened at that point in time in that one is Spring Boot. Whenever I started using Spring Boot from the day one. But the moment we talked about Spring Boot, people are really, really, really happy that we are using the latest technology and all that stuff. What is Spring Boot? It is still Spring, but it boots itself. Nothing else. But then that is how the architect's life is. But now I'm coming to our actual story. Please give me the honest answer. How do we choose a JS framework for our application? I will give you the honest answer. So the way that we choose, we need to consider memory utilization, performance metrics. You create a scorecard, ease of use, portability, and all those stuff. And that is how we choose JavaScript framework, really? No, no, no. So now, first of all, let us come to the confusion part. Then we will go to the confessions part. First, the confusion part is this. You need to choose a framework. And I'm just looking at the frameworks. What they say. EmberJS says a framework, it has taken from their own site, actually. A framework for ambitious web development. An Angular is for superheroic, progressive, and React is very simple, JavaScript library for creating building user interfaces. Now I ask my customer, is your application ambitious? Yes, of course it is supposed to be ambitious. Is it supposed to be superheroic? Yes, otherwise I can't beat my competition. Then progress, yes, yes, we need to progress. And then building user interface, what nonsense, new year building and user interface. Now choose the best. And everything looks similar. And then how do you choose the best? So now, the biggest tool, even though the problem is very, very difficult, the solutions are very, very simple. I'm going to list out four logical, mathematical, proven solutions here. So I followed it at least, let me honestly admit it. I followed it. So the first and foremost, the biggest friend for an architect from the front end is Google Trend. Any time you want to analyze the technology, go to Google Trend. And then check. So now look at React, Angular, Mujes. 75 is greater than 50, and 50 is greater than 20, which means React is greater than Angular, I use React. And that's how I choose React. And now the second thing is because someone else uses it, because Google uses it, because Facebook uses it, because Netflix uses it. And that is actually relatively easy. But just consider a civil engineer, and then you go and you want to remove. You are constructing a house. You want to move something from here to here. And then he's saying, OK, use the biggest crane that you have for this multi-story, because Ellen uses it. It sounds stupid, but that's how I actually make things. And the next thing is, in fact, the next thing that's, I once had this problem. In the initial days, when I didn't know this, Farmers and all those stuff, we had a huge debate with my director, React or Angular, which one that we'll choose for our application. And then he told Sadish, as a senior engineer, you need to go and choose. And I was looking at React, good pros and cons, Angular, pros and cons. I was not able to make any decision. And I told him that, no, I can't make any decision.  You should know how to choose the framework. I will tell you, you choose React. And then I was kind of like, I was really, two things. One is, first of all, he told the answer immediately. Second thing is, how come? Because I evaluated day and night. I couldn't find any difference. Anything that I can do with React, I can do with Angular also. But what was the difference? Then he told, OK, you know what? Why I selected React? Because there is 10 people sitting in the bench. They know React. And that is what we do. I know this. I know only this. And then the selection becomes simple. You don't even have the choice. And then new technology. We need to, I mean, it's not a problem with the development in message. But as I have been in the service industry for quite some time, whenever I go to a client, a client wants new technology. They don't care. They want new technology. Once I had a heated argument with my director and then said, no, this anyway will be like, we know that if you choose this, application is going to die. And then he said, OK, no problem. What is your problem? I said, OK, no, the client will not be happy. It's not ethical. But then he told, if you don't do it, he's going to shift to somebody else. And then he's going to do that. Anyway, instead of somebody else do it for your client, you do it for yourself. You choose a new technology. Anyway, if the problem comes, he's going to come to you. Again, it is your work. Then that was a logical answer for me, because anyway, it is going to come to me again. So that's how we chose new technology. So these are all the main factors that we choose this. So now why it happens? So when these kind of confusion happens, I want to understand why it actually happens. What is unique about this web development? What I understood is what I'm going to present. In fact, this is the main thing. So unlike other languages or other libraries where your Java is developed by Java developer, dotnet is developed by dotnet developer. PHP is developed by PHP developer. But web, Java developers comes into web. PHP developer comes into web. Dotnet developer comes into web. And they come with their own pros, their own cons. And that is why this field is not standardized. And then, again, we will resume the story. I actually stopped there, the reason being, until then it was like a flat story. There was nothing interesting. There was no fight. There was no emotion, sentiment, nothing. So now the actual story starts. So around somewhere in 2000, the first thing that happened is, wherever you see this mark, those are the places where there was a battle. People were fighting with each other. And what happened is, it's about choices. Whoever makes a choice, if the choice means the company wins, that happened. And then in these three, there are many of them, but I just put significant events only. So when first time JavaScript became like a library and then people started using real good UI components, and then there was a fight between jQuery, dojo, OUI, and DXTGS. And most of the enterprises chose OUI. The reason being, anybody can guess. Because Yahoo uses it. You learn the technology immediately. So now who? But the problem is ultimately, who was the winner? jQuery. jQuery was a winner so much so that in W3C, more than you find a JavaScript answer, if you find a question, the answer will be in jQuery. And then people who chose jQuery, they were all winner. And then Ajax came into picture. Ajax is, by far, I would consider the most significant thing. See, whenever we read about technology, it's also good to read newspapers also. There are news that makes decisions also sometimes. So this is the time that applications like Gmail and all those stuff can. In fact, Google proposed Ajax. So what happened is, instead of you render an entire page, you render only a specific component. It might be a cakewalk for anybody who is doing it now. It is just a fetch call now. But then, trust me, at that point in time, you were asking a lot of people, how do you do Ajax? If you know Ajax, you will be promoted. That much of hype they were giving for Ajax. It is three lines of code. But you are struggling to understand what is the three lines you could be doing. How is the page not reloaded? How is page not reloaded? That is how you are learning that technology. And from there, it actually goes upwards. And then this is the actual journey. Now, what happened is, people wanted to, see, at least at that point, when Google did that, everybody realized what is the market value of an internet. And everybody wanted to control it, actually, to put it this way. And there were technologies that were made. Till then, where is your publication then, it runs on browsers. And then what happened is, this is quite significant. I don't know how many of you used Flex. Very good. Then you should know what is the side effect. Companies lost plenty of money just because of Flex. And I earned plenty of money just because of Flex. Because at that point, not many people know Flex, actually. So now what happened is, now, yes, there is a limitation with this web technology, HTML, CSS, and JavaScript. And nobody wanted to upgrade those technologies also because there are a lot of politics and all those stuff. And then at that point in time, what some good people decided is, OK, we will give it to us, we will manage it. And then this is from Adobe. This is from Microsoft. This is from Google, I think so. So what they did is, they developed your application still runs on browser.  Your application still runs on browser, but it runs on Microsoft Engine. Your application still a browser, but it runs on somebody else. Which means it is technically not a browser. They are going into some preparatory technology. And at that point in time, everybody realized, OK, if we leave it, we all are going to be losing it. So they all came together. And at that point in time only, JavaScript started, evolving, HTML started evolving. And then people decided, OK, rather we fight within ourselves, let us develop HTML. Let us develop CSS. Let us develop JavaScript. And that is the place where it actually started. Now, the first thing, the colors I matched it. Sorry, last minute I prepared the presentation, but you can match it the color. So we will solve the problem one by one. What these claims were enjoying, we also want to enjoy. That is how it all started. In fact, there's a side story. What happened to the desktop claim? We were doing it with VC++ earlier. And then it became to AWT. And then between VC++ and AWT, AWT is platform independent. In swing, it is like plan form, independent components. Then Eclipse wanted to take it out of Sun Microsystem at that point in time. Then it becomes Eclipse RCP. And then Java FX. Till date, Java FX, everybody technically knows one of the best framework. That's OK. But who knows Java FX? No, nobody. The problem is the desktop client itself is gone. When the desktop client itself is not there, what are you going to do with that good framework or excellent framework? And that is what happened. The story is gone. Now we are into the story now. Now, Media Query. What Media Query did in this one? So responsive layouts, flexible layout. Yes, flexible screen size. Thanks, thanks. So flexible screen size problem is solved with Media Query. And then came Node.js. People talk a lot about server side of Node.js. But server side of Node.js, I think there is still the risk. It is still not true. But the biggest part that I think, the value added at Node.js brought in, which nobody can deny and nobody can actually remove, at least in your future, is the client side tooling, where SAS and all those people are only applicable to Ruby kind of a platform. But now SAS is applicable to us. All the web development tools are now coming in Node.js. Now SAS, why is Node.js and SAS are in this particular color? They are programming languages. OK, Grant. So Grant is the guy who first brought a proper build systems into JavaScript world. In fact, this is one frustration that I had, actually. And I evaluated Grant. I was one of the person who captured that new technology earlier, and I introduced him in the team. And I delivered the product. You know, when I delivered the product, I should be appreciated. But then people were saying, OK, what is the technology that I use, Grant? Why do you use a legacy software? How come Grant becomes legacy? Because at that point in time, there was something called Gulp. There was something called Gulp. And the technology gets outdated just like that, actually. And then Backbone.js. And Backbone.js is the starting point for many MVC frameworks that you see now. And slowly, they are covering all the areas, like applications, state, navigations, maintained by this thing. And then Core.dev and Electron, what do they solve? They run in your client. They run in your client machine. And then finally, local storage, your offline storage, and web component. That is the place where it starts. So finally, this is what I understood. So the lessons that I learned is not just technical. We are supposed to be tactical, also, if you really want to work and survive in web development, actually. A vast experience that you have, consider it is a waste experience. And play like a king. Whenever I say play like a king, whenever we talk about a client, a client will be going and fighting. No. If you watch movies like Braveheart, Gladiator, and big fan of it, this king will not be there in even a single frame of the battleground. When will he come? Once the war is over, he will come, and then he'll think about strategy. And this is how you need to play. And don't trouble the trouble, because if you trouble the trouble, trouble troubles you. And then web is a platform. It is a topic of its own. Because still, many people consider that what is web? HTML, CSS, JavaScript. Then what about REST? What about JSON schema? What about JSON LD? Web is bigger than this UI, actually. And then concepts, tools, techniques, and frameworks. If at all, one thing that you can take from this session, if at all, anything. A simple formula is always in this, if there is a new concept comes, they stay for a longer time. Tools, no problem, because it's use and throw. You can easily migrate.  Framework, be careful. But whenever someone says, OK, we're coming with a new technology in web, please stay away from them. That is what I learned. So now the story ends. So everything we got, everything covered, we are going to rule the UI as a web development. That is what the story ends. But then it doesn't stop there. What about these things? API first, IOTN finally, there is someone called Golden Krishna who is saying no interface is a good interface. When UI itself is not there, what am I going to do with all these new technologies? And I don't know whether it will happen or not. But if it happens, it's up to us. Thank you. Thanks for that. Yeah. I'm going to have to rebut about, say, no interface. And yeah, there is a whole voice down to the edge of UI for the user experience. So it may not be something that we see described just simply the UI itself. Yeah, it's not like no interface means removing it. But the more amount of interfaces that you create, it will be reduced. That's the idea. I'm just considering two things. Earlier, you used to use Net Banking directly. You used to use Net Banking applications. But now you consider from WhatsApp, you can send it to Twitter, you can send it. Which means your AP is your interface. It's not your UI. So slowly, that will get reduced. It's my understanding.


Patriot Prime Reviews is a channel for adult collectors and may not be suitable for children under 13 years of age. Viewer discretion is advised. Hey, what's going on guys? Patriot Prime here once again with another video. But before I get started with the subject of this video, I want to give a huge shout out to my sponsor, toyhacks.com. Toyhacks is a company that provides upgrade decals for modern transformer figures along with reproduction decals for the vintage ones. While visiting Toyhacks, make sure and check out the Toyhacks Armory to see their line of Transformers weaponry in multiple collars. And toy stages for awesome display backdrops. Each purchase from Toyhacks earns you Robocents that you can use for future purchases. You can check your balance anytime in your cart. Toyhacks is a company run by collectors for collectors. So make sure and check out toyhacks.com and tell them Patriot Prime sent you. Now, on to the review. The featured bot in this video is the brand new Transformers Studio Series Core Class Bumblebee Movie Shockwave.  I don't understand why Shockwave is always a core class figure. He was a core class figure back in Combiner Wars and now he's a core class figure here with Studio Series.  Now I got to give a huge shout out to Extra Zero from the channel Figure Action for finding Shockwave for me and sending him my way. Now I'll take a quick look at the packaging. We got Shockwave here in Robot Mode, a scene from the Bumblebee movie. Shockwave there behind the nothing. These new packages just blow my mind. Transformers Studio Series, Silo Box, Shockwave, this Silo Box, Shockwave again. Back of the packaging, you got Shockwave in Robot Mode and Tank Mode. So now without further ado, let's get Shockwave opened up out of this packaging and check him out. And welcome to Patriot Prime Reviews. Now once you get your tiny little Shockwave all opened up and out of the packaging, you'll see he does come with a sheet of instructions that as usual is very well illustrated and easy to follow. And has a mistake, Shockwave's cannon is not on his right hand. And speaking of cannon, you also get his hand cannon slash tank barrel. And I like the looks of this. The paint applications look really good on it with the purple and the silver there for the barrel. And of course you get Shockwave himself. Now this figure really doesn't look that bad. I love the sculpted detail on him. Very G1 inspired. Got the yellow Cyclops eye and his ears as they call them. But I don't like how these ears are so swept back. I like them more sticking straight up like G1. It just looks off to me. But other than that, this is a really good looking figure. Lots and lots of sculpted details. I like the chest section right there. I'm not sure if that is translucent plastic or not, or just very well painted. So yeah, I cannot figure that one out. So the chest looks really good. I'm sure Toyhacks will slap something on there to really change it up a little bit. Makes it look a lot more G1. Moving on down, more sculpted details here. I love the tank treads. He's got tank treads there on the back of the legs and here on the forearms. Now, as you see right now, he has two fists. And we are going to fix that because Shockwave does not have two fists.  You want to flip that all the way up like so. And we'll put this in his left hand where it goes, where it's supposed to go. Get that pegged in. Now that is a tight fit. So once you get that in, now we've got Shockwave looking like Shockwave. And I like that. That is pretty cool, just like he looked in the movie. I just wish he was bigger. Now let's go ahead and get into articulation. The head is on a mushroom peg. So all it's going to do is rotate a 360. The arms can go up and down 360 all the way around. Now there is an elbow bend and elbow rotation. No wrist rotation. Let's see. No waist rotation. Legs can go forward. They can go back. They can go out. They can go in. There is a knee bend. The hips are on a ball joint. So you got a little bit of a rotation right there. The feet can go back and forth, but there's no ankle tilt. So that's your basic core class articulation. So now let's go ahead and get him transformed into his vehicle mode. We're going to pop out the cannon. Put that to the side. First thing we're going to do, go ahead and move the arms up. Now you're going to take the legs and right here at the top of the leg, you're going to kind of bend down and out. So he's popping a squat. Now you're going to grab right here underneath the stomach. Pull this out and flip this around. So this section right here is going to tuck in under his crotch. You'll see it tucked down and there's a little tab right there. Snap that into place. So you've got that going on. Now we're going to bend this section up. Once again, there's another little tab right there. Tab that into place.  Now with the arms, you need to rotate the arms around and rotate the forearm. So you've got this tab. That tab is going to fit right in there in that slot. So the arms will be kind of hooked in at an angle. Let's see if I can get that out of the way. Do the same thing for the other arm. There we go. I get this leg just right because there is a tab right there on the gray part of the leg that you're going to match up to a little slot right there in the arm. See that? Go ahead and do that on the other side. Let me see if I can get it on camera for you. Line your slots up. And there we go. Go ahead and fold the feet down. And now lastly, you're going to take the cannon once again. Flip the handle all the way around like so. So this section here is facing back. And now you're going to plug this handle in the back of Shockwave's head. Now you want to be careful of that. Maybe not push it in all the way because the first time I transformed this guy, I pushed the cannon in. It was all I could do to get that cannon out. I actually had to pop Shockwave's head off in order to pull the cannon out. So that's a very tight fit. So there you've got Shockwave in tank mode. This is a weird Cybertronian tank. It looks a lot like the, what was it? Transformers Prime Beast Hunter Shockwave. That's what this reminds me of.  They at least gave him some wheels. He's got the nice molded in treads. And that's about it. It's a weird looking Cybertronian tank, but nobody's going to sneak up on him because he's got eyes on the back of his head.  Now the only real articulation with the tank is the turret can rotate left and right. It can do a 360 if you lift up. It can't really go up and down much. You got just a little bit, but it kind of falls back into place. So there you go guys. Shockwave in his tank mode. And now for some quick size comparisons. Here is Transformers Studio Series Core Class Bumblebee Shockwave with Deluxe Class War for Cybertron Shockwave, Combiner Wars Shockwave, Kingdom Core Class Megatron, and Kingdom Core Class Soundwave. Transformers Studio Series Core Class Shockwave is great for what he is. He's a representation of Shockwave from the Bumblebee movie. He just needs to be bigger. I mean it's Shockwave. Shockwave should be a Deluxe or a Voyager Class, not Core Class. Though this Core Class figure does have decent sculpting, great articulation. I love the fact that blast effects can be used with the weapon. Oh and the chest is painted plastic, not translucent. Robot mode, pretty good. Not a big fan of the alt mode. So there you go guys. Transformers Studio Series Core Class Bumblebee Movie Shockwave. So does a Transformers Studio Series Core Class Bumblebee Movie Shockwave belong in your collection?  I mean he's not bad. Robot mode is pretty good. He's got great sculpted details, great paint applications, great articulation. Alt mode, alt mode's a little terrible. Not a big fan of that. But you know he's not bad for what he is. I just really wish and hope that we get a Shockwave in Deluxe or Voyager size. I mean, come on man, Shockwave as a core figure just doesn't cut it. We already had this issue with this guy a few years ago.  Now guys, if you enjoyed the video, don't forget to like, don't forget to subscribe and don't forget to hit that bell icon to get notified when I upload new videos. Also, if you're in any position to help out the channel, I do offer channel memberships here on YouTube and I got to give a huge shout out to all my current channel members because it's support like yours that helps keep this channel growing. Also, Dylan and I are heading off to Big Lit Comic Con this weekend in Roanoke, Virginia and I really hope to see some of you there. Once again guys, this is Patriot Prime, signing out. Hula! Hula!


My name is Tracy Inger with Intention Technology. We are a team, Bioscan R, from Tampa, Florida.  And what we're looking at is, can we give people a second opinion so that we can stop misdiagnosis? My mom was diagnosed with a three centimeter aneurysm. And she ended up getting put on bed rest for two years to find out it was actually a three millimeter aneurysm. And it wasn't until she was getting signed up for surgery on the aneurysm that they realized that there was an error, a typo. And you know, with electronic health records and everything like that, it's not that typos aren't gonna happen. It's, can we have things that give that second opinion? That quick second opinion that can go, wait, we missed something. Technology has advanced so much in every other aspect of our economy, but healthcare has really been behind. It's one of the areas where you still use a fax machine.  You know, why are we still using stethoscopes when there's all these digital type devices that can give better information quicker and faster? I had one person come into me and had a rare form of sickle cell anemia that was only effective at high altitudes and had been spending four years looking for, you know, a solution to this through many doctors, almost died multiple times. And in 15 minutes, one of the devices from Russia pulled it up and he was amazed. Our goal isn't to replace doctors. Our goal is to give doctors the tools that they need to be able to do their job better. The Qualcomm Tricorder X twice, you know, helped us to accelerate the technology that I've dreamed about for years because it created an initiative and something that people could stand behind. It's no longer even about just three or four minute diagnosis. It's now, how do you start seeing trends and start understanding where the body is during the day so you can see where your high points or low points are? So you can see that if you go to McDonald's and have that Big Mac, what does your body do? When I can do a diagnosis in 10, 15 minutes and it still takes a doctor three or four days to be able to get lab results and get it back, you know, why can't we not have that technology today? To me, a lot of this stuff isn't new. It's, how do we pull it all together?  And when I heard you speak, he says, what you're doing can really change the world. How do I help? And to have 20 people on my team that are just looking for a way to help, to really a way to make a difference, that is amazing.


Please call the attendance roll. We have 13 present and we have excused Alderman Boran, Van Ackerman, Maddichak. Thank you very much. Next I'd like to ask you to please stand and join me in the Pledge of Allegiance. Just to the flag of the United States of America and to the Republic for which it stands, one nation under God, indivisible, with liberty and justice for all. Next we'll go on to the approval of our minutes from our last meeting, Alderman Hammond. Thank you, Mr. Mayor. I move to approve. Second. Thank you for that motion and support. Those minutes are before us. Is there any discussion? Seeing none, all those in favor, please signify by saying aye. Aye. Opposed? Motion passes. Do we have any resignations? And any council appointments? Scott Lewandowski to be considered for appointment to the Historic Preservation Housing Rehab Loan Commission to fill the unexpired term of Nancy Modry whose term expires for 2020-15, signed by the mayor. Let's do them all together. And County Board Supervisor Charles Conrarty to serve as Spoyton County's representative on the Board of Marina Park and Forestry Commissioners for one-year term expiring April 1, 2015 and for the subsequent one-year term expiring April 2016. And Tyler Ott to be considered for appointment to the Business Improvement District to fill the unexpired term of Larry Schaefer whose term expires 1231-2014, signed by the mayor. Alderman Hammond. Thank you, Mr. Mayor. I move to confirm. Second. Thank you for that motion and support. Is there any discussion? Will the clerk please call the roll on confirmation? Mark, you need to vote. 13 ayes. Motion passes. Excuse me. Next, we'll go on to presentations. May 18th through the 24th is Public Works Week and they're using the jingle of building for today, planning for tomorrow. And I'd like to call Dave Bebel up to give us infrastructure review and a little bit of what's been going on lately at the Public Works Department in Sheboygan, Wisconsin. Thank you, Mayor. Here real quick. It's my pleasure to present to you this presentation basically on the state of the infrastructure in the city of Sheboygan, some of the challenges that we're facing and hopefully give you a better understanding of some of the challenges that we in the Public Works profession face in cities. So I'll get right into it. I know there's a lot of information. I'm gonna go pretty fast to keep everyone on, keep everyone's time and consideration here. So real quickly. Our vision and it's to provide a professional Public Works organization that will offer quality infrastructure and services in a sustainable way that will contribute to making Sheboygan a desirable place to live, work and play. And that goes right into our mission, which is to improve the quality of life by effectively developing, maintaining and improving the infrastructure, natural resources and community services. Public Works is divided into five divisions. Administration and engineering, buildings, grounds, electrical, motor vehicle, parks, forestry and cemetery, streets and sanitation and wastewater treatment. Tonight we have some of our superintendents of those divisions, Ryan Sasmar, city engineer in the back, Sharon Teeson, our wastewater superintendent, Joel Colste, our streets and sanitation superintendent and Joel Curlin, our parks and forestry and cemetery superintendent. Financing of Public Works on an annual basis, 20 million dollars roughly for the city of Sheboygan, for all those divisions. Some vital statistics for our community. We're over 150 years old. We're 14 and a half square miles in size. I like to describe that as we're about two to two and a half miles wide by seven miles long. We go to the interstate to the lake, north and south. We have 200 centerline miles of streets in the city of Sheboygan. 16 bridges, 170 miles of sanitary sewers with an additional 102 miles of storm sewers. 45 signalized intersection, approximately 15,000 signs. We have 1,300 streetlates owned by the city. 5,000 to 6,000, however, are owned by Alliance Energy, which we lease. Annually, we pick up 15,000 tons of garbage, with 3,800 tons being recycled, in addition to that, so around 18,000 pounds. Every week, we make 18,000 stops to pick up garbage in the city. We have 33 parks with almost 700 acres. We have 27,500 street trees. Those are the trees between the sidewalk and the curb. Annually, we bury between 175 to 200 people at the Wildwood Cemetery, which is city-owned. And daily, we treat 12.3 million gallons of sewage. So, real briefly, introductory statements. The city of Sheboygan, overall infrastructure condition is average to good in many of the areas. As I mentioned, we're 150 years old, and as the city ages, so does our infrastructure. Sheboygan is not unique in that aspect with other infrastructure conditions throughout our nation. A little history lesson. After World War II, the city experienced rapid growth, not only in population, but in development, and in development of housing, roads, and sewer and water system parks, and everything was being expanded after World War II. And during these years, after these years, as I said, we were in expansion mode, and basically focused our city resources on expanding to meet that need. This graph here shows that in basically, in the 30s and 40s, not much development, but shortly after the war, going up through peaking in the mid-70s, early 70s, excuse me. I'm not sure if... The number of streets paved in the city was at its peak. Again, showing that we are growing along with the city at that time. Since then, as you can see, we haven't had much need to expand our resources. Here's some photos. I just want to give you a kind of a perspective and history and thinking of some areas. This is a Noel Crest Drive near 18th Street back in 1971. It's a gravel road at that point. We just probably put in the sewer system, laid out some roads for lots to be developed. And that's what it looks like today. Concrete, curb and gutter, sidewalks, street trees, signs, another before and after. This is South, this is Greenfield Avenue on the south side of Sheboygan, looking east at the intersection at Greenfield. You can see housing being introduced in the subdivision, gravel roads, utilities were just recently installed. And that's a picture of it today again. And one last one like this. This is South 12th Place, looking at South High to the north in this picture. You got one house in that area. Again, this is what it is today. And it's about 40, 45 years after the fact. So the life cycle of infrastructure. As I mentioned about, talked about the expansion of it. New utilities, expanding roads, building it. Then it shifts to maintenance. We have to maintain that infrastructure once it's built. It has a life cycle. It has a lifespan, it has to be maintained. And it can be maintained for only such a period before it has to be finally reconstructed. We've developed an indexes for the condition of our infrastructure. This is one example, pavement condition index. We use this to rate all of our city streets on a scale from 100 to zero. 100 being good, as you see in zero to 10 being failing. It's important because the cost of timely maintenance and on this graph, what you'll see here is that, is that if we perform maintenance early at the right optimal time on pavements, for instance, or in any of our infrastructure, this can be said, is that the cost of doing it is incrementally smaller than waiting for it to get further deteriorated. And if we don't time it, and it gets to that point, it's gonna be anywhere triple to four times more expensive to perform any type of repairs. That's ultimately our goal. Unfortunately, a city this size, we can, I'm sure you're all experienced with this yourself, just driving around the city. Many of our streets are beyond the point of doing our basic maintenance. We're in that area where it's costly. This is just of graph showing real quickly the pavement condition index. The pavements into 2000s, they're great. Highest rated, 90s are still high. The pavements that were put into 1980s are still very good. Then we have a flat section from the 80s to the 50s, about a 30 year period. Ideally, we wanna be hitting those streets and getting them maintained, resurfaced, and extending their life cycle. When we get to the 50s and beyond, it starts getting to that point in the curve where we're looking at more expensive rehabilitation options, or if not reconstruction. Again, this is showing the linear streets that were paved when we were in the expansion mode. The next slide corresponds with the maintenance activities. High maintenance in the 70s because of all that stuff that was being put in during the 60s now needs to be maintained about a decade later. So this is the asphalt surfacing program. And you can see, not much activity through the 20s and 30s, but after that, the 70s, the 80s, the 90s, we were doing quite a bit of resurfacing. However, as you can see, it's on a downward trend as well. This is an example of a maintenance strategy. This is resurfacing of Michigan Avenue, probably around the late 50s, early 60s. And you can see the Mayor's Seen Feed facility, and I like this picture because you can see the people standing there on the sidewalk leaning up against the building. And in 2005, it had to be reconstructed. And we still have the same guy sitting there at the corner there. So we talked about the three factors, expansion, maintenance, and reconstruction. They're not separate. They're constantly in their presence and they're constantly competing. And they're competing for the same dollar. And so what we need to do from our perspective is we need to balance that need to expand. We need to make sure we're maximizing our maintenance dollars and strategically reconstructing where it's best for the community. So where does that leave us? We are currently entering another phase of infrastructure management. Infrastructure that was expanded after the war is reaching the end of its life cycle. We'll require significant maintenance, in some cases total reconstruction. And as I mentioned, timing of that maintenance is critical. And ultimately our goal and the best use of city taxpayer dollars. And unfortunately, maintenance projects are typically not funded to the level needed due to conflicting uses, as I mentioned. As was shown in the graph earlier, the maintenance can extend that life cycle and defer the eventual reconstruction. And right now we're struggling to meet all those needs. As I mentioned, the city has over 200 miles of paved streets. The replacement value of that. Put this in perspective, if we had to repave every street, it's about a million dollars per mile. So at $200 million, we could probably get close to repaving our city streets. At $2 million a year invested in our street for street maintenance, it would take us 100 years to complete the city. Unfortunately our pavements don't last 100 years.  Its replacement is between half a billion to a billion dollars for the city of Sheboygan if you added them all up. On average, we're spending around a million dollars annually on street improvements. The operating budget is around 3.25 million, which includes a portion of that street repair, but it also goes to street lighting, traffic, signal maintenance, snow removals included in that, street cleaning. Some projects that are gonna be coming up next year, the North 14th Street Bridge over the Sheboygan River, just south of Erie Avenue. That's gonna be a complete redec next year, as well as in 2017, we're looking at the reconstruction of Caliomet Drive from Main Avenue to North Avenue. And that's also planned. Both of those projects total around 4.5 million. We also have some other DOT projects coming up, North Avenue Reconstruction, which is scheduled for 2018. We're looking at repainting the 8th Street Bridge, the steel, that bridge is already over 20 years old. It needs to be repainted. So there's quite a bit of projects coming up in terms of the street needs. These pictures are of cured-in-place pipe. It's basically inserting a liner in our sanitary sewer system. We spend approximately 500 to 750,000 annually in sanitary sewers. The maintenance, that cured-in-place pipe system, it allows us to fix the pipes without digging up the streets, which saves significant money. Operating budgets for sanitary sewer maintenance and inspection repairs is approximately one and a half million annually. And we have over, again, 175 miles of sanitary sewer with approximately 4,900 manholes. Pipe sizes range from six inches in diameter to 60. Currently, we do not have the sanitary sewer system rated. We're actually starting a proposal. We're funding an engineering study to do just that in order to capture and inventory all of our sanitary sewer system and get a condition rating on it so we can make intelligent decisions in terms of what areas need to be repaired first. That'll be probably a five-year study. And we're looking to probably kick that off later this year and the next year and it's being funded through the wastewater treatment plant. 1998, we had a serious flood in the city of Sheboygan. As a result of that, we've made significant upgrades in our storm sewer system. Again, it has over 105 miles of storm sewer, 3,400 manholes are with that system. Over the past decade, we've invested over $15 million in stormwater management and storm sewer maintenance budget on average are right around 750,000 annually. Catch basins on the corner, you see sometimes they don't work while they're doing their, they collect debris and that's what they're supposed to do, collect debris but if they're not maintained and cleaned out, what happens is they get clogged like these photos show. This is what a cleaned catch basin should be like. It's unfortunate because we just have not been able to clean as many of these catch basins and you talk about the manholes, you look at catch basins are probably gonna be around anywhere from 7,000 to 8,000 different catch basins because there's four typically and an intersection. We're gonna get into city buildings real briefly. City buildings are another area within the public works department. The part of our city infrastructure, city hall here is gonna be 100 years old next year. As you're well aware of city hall, it is in need of some work. It needs a new roof. It needs tuck pointing that has structural issues. It doesn't have central air, it's very inefficient. So it's gonna be a topic within the next five to 10 years here in terms of a capital improvements programming issue. Forestry, forestry is gonna be a major issue real coming up soon with the emerald ash borer. It's around our area, it's just a matter of time it's gonna reach the borer again. And as mentioned, 20 some thousand street trees, approximately 5,000 of them are ash. And that's just in our street trees. It doesn't count the ones that are in the parks or even on private property that are gonna be an issue for us to handle. Parks, park systems in fairly good condition but yet there are several areas such as some of our bathrooms and some of our playground equipment that doesn't really meet the needs of the community or the ADA standards. So again, capital improvements will be showing a plan to address those in the future. And wastewater treatment. Our facility is approaching 40 years old. It has a life cycle just as much as the rest of our infrastructure as we talked this evening. Replacement costs, if we had to build a brand new wastewater treatment facility, it's probably close to a hundred million dollars to replace that facility. We have maintained and done a tremendous job in terms of maintaining and upgrading that system at the treatment plant and been very fortunate to do some great innovative energy efficient programs. But nevertheless, we still have to be diligent and work towards maintaining that facility because it's far too great of an asset to let deteriorate to a point where it becomes insurmountable to fix. But I'd just like to close with a couple of statements that public works, we have a long history of constant improvement and implementing efficient programs to meet the objectives set forth by the budget and the Common Council. I'll give some examples. Population really hasn't grown as you're going in. It's only 6% since 1970. But the area of the city, the area by 50% was 9.6 square miles. Now it's up to almost 14 and a half square miles. The miles the city streets has grown from 1970 was only 143 and a half miles to over 200 today. And Park acreage has nearly doubled to 700 acres from 347 back in 1970. And all these changes have occurred while the department staff has been reduced by over half. In 1970, the department had 216 full-time employees. Today we have 100. And I gotta tell you that the 100 employees that we have are some of the fantastic employees that I would love to work with, I tell you. We've been through some tough times. We've had reductions in the department, but they still offer suggestions. We get the job done. And we're still trying to meet all those levels of service that we did when we had 30 extra people. Lastly, I just want to close with some transformation pictures. Sea rice coal property back probably in the late 50s, early 60s. Outlooked in 1995, the A Street Bridge is being constructed in the aerial view of that peninsula today. Pretty interesting in transformation of a betterment to our community. And lastly, I want to close with the infrastructure investment, and it's a constant struggle between financing expansion and maintaining what we have. Thank you. David, thank you very much for that presentation and to all your staff for all the great work that they do. Are there any public forum for this evening? Yeah, I'm just gonna switch it. Okay. Okay. Public forum this evening, we have one person and that would be Jeff Schucho. Jeff, if you're here, could you come on up? Thank you. Can I have your home address, please? Thank you, pardon me. Can I have your home address, please? Yes, 2508 Indiana Avenue. Okay, and you will have five minutes, sir. Thank you very much. I just wanted to stop in this evening and talk to everyone, and first of all, thank you for this opportunity, mayor, council members, and citizens at home about some stories I've seen in the Sheboygan Press lately and discussed on the radio too about internet access improvements that may come about soon. And I was really excited to hear about this. I believe it was an article in yesterday's paper about the city, county, and the school system working on providing a fiber optic system that we would all share together, which I thought was a great idea to share the cost and improve the services. And the reason I'm stopping and mentioning this tonight is because some businesses along with my own have kind of been left with substandard outdated internet access. I, for one, have no fiber optic access at all, and I've asked for it for a few years now. And what we do have are overextended lines in DSL and actually the cable access that we have. And I don't know much about this sort of thing. I went to school before there were computer classes, but I run a company out of my home where my business is located also. And what I ended up with was some pretty serious problems. I had credit card numbers stolen off my internet. My system's been hacked. And what I was told by some technicians that I had check it out is with these overextended lines, your upload and download speeds can be really seriously affected to the point where your virus protections and your computer don't even work properly. And I got hacked. I had credit card numbers stolen, like I said. And I thought this would be, with this being considered, I would really appreciate it. And a couple other businesses in my area, too, have had some pretty serious problems. If those services could be worked on for businesses along with the school system, I would really appreciate it. With my company, I've received the first full patent on a migratory vertebrate product that we now have on the market. I have three other patents I'd like to work on. But unfortunately, I had to drop all my internet services. They're not really trustworthy. So if there's anything anybody could do to help move that program along, I would really appreciate it. Thank you very much. Thank you, Jeff. Under Mayor's announcements, I'd like to start out with a retirement recognition. Bob Wallace is with us today. He'll be retiring from the Sheboygan Police Department on June 3rd. After serving the city of Sheboygan for 29 years in that role, Bobby Grant, again, his career in law enforcement in 1981, working part-time for Silver Lake Police Department. He completed a recruit school at MATC in 1982 and then took positions with Pleasant Prairie and Twin Lakes Police Departments prior to being hired by the Sheboygan Police Department on June 24th of 1985. During his tenure, he worked in undercover capacity with the county drug unit. He was an advisor to the police department explorer post and was a training field officer and then spent 10 years as a member of the emergency response team. He was promoted to sergeant in June 20th of 1995, lieutenant on February 6th of 1998 and captain on January 4th of 2002. During his past 29 years, he's been involved in many investigations from homicides to robberies, burglaries and thefts, but it's the little things as an officer does that truly demonstrate their dedication to the city and its coworkers. Several of them provided me with a few insights on how who Bob really is. As a field training officer, Bob was patrolling the city on a cold winter night with a new rookie and the roads were covered with ice. As they approached the corner of South 12th Union, Officer Wallace stopped the squad. The rookie asked, what are you doing? Bob exited the squad and he began to spread sand from the DPW box throughout the intersection. Wallace returned and told the rookie that the provision of accidents means that you get to go home on time plus the citizens won't start their day with an unfortunate experience. Another time a frustrated rookie officer told Bob Wallace how a suspect had escaped from his arrest. Bob convinced the rookie to return with him to the address where the suspect had last been seen. And when the rookie and another officer continued to search for the suspect until he was found hiding in a rolled up carpet in a basement stairwell, he was finally taken into custody. In December of 93, Bob investigated a home burglary in the Farmsworth neighborhood. The burglary occurred just prior to Christmas and most of the Christmas presents were stolen from under the victim's Christmas tree. He was able to talk to some neighbors and develop a group of suspect children who lived about a block away. Subsequently, following up on this investigation led to the discovery of the stolen presents and confessions from the teenage children. Steve Cobb, who worked with Bob on this case, said that when they walked back into the victim's home with those presents and saw the reaction on that family, he said, well, it was one of the most memorable moments of my career, and I'm sure it was for Bob too. Most importantly, there are countless stories of Bob Wallace having contact with someone who was down on their luck and needing a helping hand rather than a lecture. Bob would secretly help them out or attempt to connect them with someone who could help them turn their luck around. He was the type of person under the uniform that people respected. Captain Wallace has been involved in many law enforcement changes over the last 29 years. His most recent effort being Wisconsin Act 79, which was signed into law by Governor Walker this year. He worked tirelessly with our area legislators and others to create a law that strengthens the law enforcement's role in working with the Department of Corrections and the supervision of offenders that are placed back into our community. Captain Wallace has been involved in many big cases and achieved much during his career, but we will miss the most is his good judgment, his deep concern for his community, and the strong sense of empathy that he has for others. Bob, would you please come forward to accept this citation? The Certificate of Appreciation by the City of Sheboygan is presented to Bob Wallace for 29 years of dedicated service from June of 85 through June of 2014. Bob, thank you so much, thank you. I'm very uncomfortable in this type of situation. I'm far more comfortable in the squad car, but I've written a few notes and I'll try to add maybe a little bit to help myself out a little bit. First of all, I'd like to thank the mayor and the common counsel for taking this time to recognize my service to the city and the community. I really appreciate it. I feel very lucky and I'm very proud to have been a member of the Sheboygan Police Department. The department truly is a great place to be a police officer and I'm very thankful that I chose Sheboygan as a place to live and work. My 29 years in the Sheboygan Police Department, a total of 34 in law enforcement, has been just as rewarding, challenging, and interesting as I could have imagined it would be way back in 1980. As a police officer, as any police officer has, I've seen my share of tragedy and people at the very worst times of their lives. It has been a privilege to be in a place in a position of trust where I could try to make those times better in some way or to have the opportunity to restore some measure of justice for crime victims. One of the basic tenements of community-oriented policing is teamwork and collaboration, working together with citizens, other departments, and community organizations to achieve shared goals. One of the few frustrations that I have as I leave the police department is after 29 years of service and working with so many people. I owe such a debt of gratitude and thanks to so many people for their teamwork, for their teamwork, their help, and support that I know I won't be able to thank all of them personally.  To Chief Domagalski, I would like to say thank you for your strong leadership of the police department and for making the needs of the community your highest personal and organizational priority. Under your direction and guidance, the Sheboygan Police Department and its personnel are frequently being recognized for their good work and are increasingly being called upon as trainers around the state. Most importantly, the Sheboygan continues to be a very safe community, and that is a great reflection upon the citizens of Sheboygan, you and the men and women of the Sheboygan Police Department. Personally, I can say it has been a pleasure both working with you and learning from you. To my coworkers in the Sheboygan Police Department both past and present, I can say it has truly been an honor and privilege to serve among so many dedicated and talented men and women over the past 29 years. I would like to thank all of the officers, dispatchers, and support staff who have made work at the Sheboygan Police Department so interesting, enjoyable, and challenging. I know that I have failed to tell you frequently enough how proud I am of the important work. That all you do, please support each other as you go about your important duties and be safe. Over the past several years, I've worked together with many of the city department heads and their staff members on shared projects or goals. I have to tell all of you in the various city departments how grateful I am for all of your service and help and your can-do attitude as we approach these difficult problems. To the citizens of Sheboygan, I would like to thank you as well for the opportunity to serve you as a police officer. Finally, and I say the most important for last, I would like to thank my fiance, Tamara Remington, and her children, Emily and Lucas, and my sons, Michael and Steven, for their support and understanding during my years of police service. The sacrifice made by the family of police officers is something that they live every day and is very special and most commendable. So thank you to y'all, appreciate it. On January 16th of 1967, this common council of the city of Sheboygan recognized and endorsed a sister city relationship with Esslingen. At that time, they said that with the hope that this will lead to an lasting friendship between the peoples of Sheboygan and Esslingen, Germany. Throughout the years, I believe that this desire and intent of the common council has been fulfilled. During the past 47 years, different mayors with the help of interested residents have had the privilege and responsibility of keeping this relationship strong and meaningful. I extend a special thanks to the common council's mayors, previous members of the international committee, the former mayors, the people of the people organization, and all who have helped nurture and strengthen our very special sister city relationship with our friends in Germany. Tomorrow, my wife, Julie, and I will travel with a group of 24 Sheboygan residents and a trip to Esslingen to Renew and strengthen this relationship. We look forward to meeting our German hosts and learning more about each other. I feel strongly about maintaining our sister city partnership and look forward to this exchange. This trip will reaffirm our city's commitment as a community to our friends in Esslingen and show that we value this partnership. Whether it's through visits like this, a student exchange program, this partnership exemplifies citizen democracy and global cooperation at a level that helps to promote respect, goodwill, understanding of cultures, and the appreciation of diversity. And then one last announcement. Don't forget Memorial Day is coming up next Monday. We have a nine o'clock parade on A Street and then a 10 a.m. program at Fountain Park. Thank you. The next item on the agenda before us is the consent agenda, Alderman Hammond. Thank you, Mr. Mayor. I move to accept and follow all ROs, accept and adopt all RCs and put all resolutions upon their passage. Second. Thank you for that motion and support with a clerk, please call the roll on the consent agenda. Is there any discussion? Please go ahead. 13 ayes. Passes unanimously. Item number three is communications and petitions. Item 3.1 will be referred to public protection and safety committee. Number four is reports of officers. Item 4.1 will lie over till June 2nd. Items 4.2 through 4.5 will be referred to various committees. Number five resolutions. Items 5.1 through 5.3 will be referred to various committees. Item six, reports of committees. 6.1 is an RC by law and licensing recommending denying a beverage operators license number 9687 based on her failure to accurately review all relevant convictions on her application. And her record of violations related to the licensed activities. Alderman Vanderwill. Thank you, Mr. Mayor. I move the RC be accepted and adopted. Second. It's moved in second and under discussion. Is Roxella Cassandra Trevino here this evening? She's not here. We denied her license based on both the police recommendation and the fact that she had very recent violations. And it was a proof or denied four to zero. Thank you. Is there any other discussion? Seeing none, will the clerk please call the roll? 13 ayes. Motion passes. Item 6.2 is an RC by law and licensing recommending denying a taxi cab drivers license number 0337 based on her record of violations related to the licensed activity and her failure to cooperate with the committee and her status as a habitual law offender. Alderman Vanderwill. Thank you, I move the RC be accepted and adopted. Second. It's been moved and seconded under discussion. Is Lilibeth Velez here this evening? She's not here. We had invited her to our meeting on two separate occasions and she did not show up either time. Is there any other discussion? Seeing none, will the clerk please call the roll? 13 ayes. Motion passes. Item 6.3 is an RC by finance, recommending transferring the appropriations in the 2014 budget, establishing appropriation for the purchase and demolition of 727 North A Street and establishing appropriation for the purchase of the Shukrit Farm and established capital improvements funding for 2014. Alderman Hammond. Thank you, Mr. Mayor. I move to accept and adopt and put the resolution upon its passage. Second. Thank you for that motion and support. Under discussion. Seeing no discussion, will the clerk please call the roll for passage? 13 ayes. Motion passes. Number seven ordinances. Item 7.1 will be referred to the city planning commission. Item number eight, other matters. 8.1 will be referred to the public protection and safety committee. 8.2 is the resolution by Alderman Hammond, authorizing all city officers to keep and preserve public records by means of photographic reproduction. Alderman Hammond. Thank you, Mr. Mayor. I move to put the resolution upon its passage. Second. Thank you for that motion and support. Is there any discussion on the motion? Seeing none, will the clerk please, we can do this by voice vote. All those in favor, please signify by saying aye. Aye. Opposed? Motion passes. Item 8.3 is a resolution by Alderman Heidemann, authorizing the emergency repair and reconstruction of storm sewer and sub grade to the Pennsylvania Avenue bridge abutment as a result of a broken storm sewer pipe that caused major erosion. Alderman Heidemann. Thank you, Mayor. First of all, I need to make a motion to suspend the rules. Second. It's moved and seconded to spend the rules. All those in favor of suspension, please signify by saying aye. Aye. Opposed? Motion passes. Under suspension. Okay, David, would you like to? You want to make a motion on the- Move to suspend the rules. No, we did that already. Okay, then put the resolution upon its passage. Second. Thank you for that motion and support. Under discussion, David, would you like to step forward? Yeah, I think you've probably all seen we actually, the work is already undertaking and it's under construction as we speak. It was a serious situation and we've worked over the weekend and it became evident over this weekend as we started exposing it with the equipment that it was a serious situation. The sidewalk and some of the street panels are completely undermined, no supporting substructure. We're very fortunate one of those panels hasn't caved in causing some serious concern. Right now, the contractor's working, we're estimating between 125 to 150,000 for this repair. Any other discussion? Would the clerk please call the roll for passage? Mark, 13 ayes. Motion passes. Next is a scheduled closed session. Alderman Hammond. Oh, we have to go to other matters first. I'm sorry. City Attorney. Thank you, Your Honor. 8.4 is an R.O. by the city clerk submitting various license applications for the period ending June 30, 2015 and June 30, 2016. Be referred to law and licensing. 8.5 is an R.O. by the city clerk submitting a petition for the vacation of a portion of the paved alley between North 14th and North 15th streets between St. Clair and Erie Avenue, signed by the owners of all the lots and lands of budding that portion of the alley sought to be vacated and the owners of more than one third of that portion of the remainder of the road. Now be referred to the city planning commission. 8.6 is an ordinance vacating a portion of the paved alley between North 14th and 15th streets and between St. Clair Avenue and Erie Avenue. Now be referred to city planning commission. 8.7 is an R.O. by the city clerk submitting various license applications for the period ending June 30, 2015 and June 30, 2016. That'll be referred to the law and licensing committee. 8.8 is an R.O. by the city clerk submitting a petition, notice and list of tax liens of Shboygan County being foreclosed by proceeding in rem 2004, 5, 6, 7, 8, 9 and 10, number 40. That'll be referred to the finance committee. 8.9 is a resolution authorizing and signing an easement for many storm sewer in various locations. Then be referred to the public works committee. 8.10 is an ordinance relating to mid block crosswalks so as to add a mid block crosswalk in the 800 block of Broton Drive. That'll be referred to public protection and safety. 8.11 is an ordinance creating a no parking zone on the west side of Broton Drive south of Washington court. That'll be referred to public protection and safety committee. 8.12 is an ordinance creating a no parking stopping or standing zone on the east and west sides of Broton Drive south of Washington court. That'll also be referred to public protection and safety. 8.13 is an ordinance creating a no parking stopping or standing zone on the east and west sides of Broton Drive north of Wisconsin Avenue. That'll also be referred to public protection and safety. Now, Alderman Hammond. Thank you, Mr. Mayor. I move to convene in a closed session under the exemption provided 19-851-E Wisconsin statutes for the purpose of deliberating the selling of public property where competitive and bargaining reasons can require a closed session. All right. Can I have a break? Would the clerk please call the roll for a closed session? 13 ayes. Motion passes. We'll take a five minute recess and reconvene.