Laserfiche WebLink
<br />Pat Klaers <br />July 22, 1999 <br />Page Two <br /> <br />DISCUSSION <br /> <br />The decision on whether or not to run an in-house engineering group will hinge largely on what <br />the goals and objectives are. There are many, many different levels of in-house service that <br />could be implemented. I will suggest four. (I am sure there are many more but this will at least <br />serve as a starting point for your thoughts.) The attached chart attempts to layout some <br />generalized functions, staffing levels, and potential revenue to be generated by the scenarios. <br /> <br />If the goals are only financial one must carefully consider all of the costs. The simple chart <br />indicates that significant ad valorem contributions are necessary with smaller staffs. A decision <br />to get into a staff of some size will be required before the group approaches a break,.even point. <br />That staff will of course need to be equipped and housed. The assumptions on equipment follow <br />the chart. The costs of housing the group and other non-labor overhead costs are not <br />recognized in this simple analysis but of course they are there. One must also bear in mind that <br />this group will need to have the opportunity to handle meaningful projects each year from which <br />to generate revenue. Those projects will have to be within the technical purview of the group. It <br />would be unwise for the City to try to staff itself to handle all of the differing kinas of technical <br />work that it will encounter. <br /> <br />There are non-financial advantages to having an in-house engineering group. There can be <br />greater day-to-day accessibility in some cases (One should not overestimate that availability. <br />This decreases as more project work is taken on.) This is somewhat mitigated with our present <br />arrangement in Elk River. Conversely, however, there is the loss of some flexibility. Using a <br />consulting City Engineer allows the City to contract for the engineering services that are <br />required and nothing more. If a certain specialty is required, the City does not have to maintain <br />that expertise in-house idling away until the time for its need arrives. If there are upturns or <br />downturns in the economy the City never needs to be concerned with having too little or too <br />much staff. Fast track projects can be implemented very quickly and do not have to wait until an <br />in-house staff can get to them. <br /> <br />Nevertheless, I believe that there is a level at which an in-house engineering group is a <br />reasonable decision for a City. In order for that to be the case, the City must be at an age and a <br />population base where there is a predictable workload that warrants staffing up to handle it. <br />That is, the community must be a mature community with the majority of its infrastructure ready <br />for or approaching reconstruction. This allows for the in-house group to establish its base load <br />each year and to select projects that are within its size ability and technical capacity to handle. <br />Those projects that fall outside of that range should be given to consultants. <br /> <br />With the rapid growth experienced by the City in the last 8-10 years, Elk River may not yet have <br />met this criterion. Many cities that are still on the growth curve such as Apple Valley and <br />Cottage Grove have put off the establishment of an in-house engineering staff. Other smaller <br />mature cities such as Prior Lake, West St. Paul, and Mendota Heights have in-house staffs. <br /> <br />I would enjoy discussing this issue with you in greater detail if you think that would be helpful. <br /> <br />O:\PROJ\90013SCSm\13S-2203ojUIWWard R. Green Company <br />CONSULTING ENGINEERS <br />