| nies in the middle of selecting new construction | | | | miss a beat. Thus, they will need to know what is |
| software have likely realized that what sounds | | | | required from them for any potential software |
| simple on paper is far from as easy task. | | | | solution to identify areas where current hardware |
| Organizations that are the most successful in this | | | | may not mesh with the new software. |
| undertaking, in terms of both identifying the best | | | | 6) Other Departments - this includes any other |
| possible solution and implementing it as quickly as | | | | departments in your company that will be |
| seamlessly as possible, generally have somebody | | | | impacted by new software. Which departments |
| or group of people in charge of the new software | | | | these are will depend on your organizational |
| project. If an individual is chosen, this person | | | | structure and company size. |
| needs to have an intimate knowledge of both | | | | 7) Sub-contractors - These indidivuals need to be |
| software and of the company's operational | | | | aware of how your change in software will impact |
| procedures. Further, the individual needs to have a | | | | their business operations with your company. |
| deep understanding of how the software and | | | | 8) Suppliers - as with sub-contractors, your |
| company operations impact each other. This | | | | suppliers will need to know what changes are |
| includes knowledge and experience working with | | | | required on their end to allow you to make the |
| software interfaces and the standard data | | | | most of your new software. |
| collection/protocols for construction companies. | | | | 9) Vendors - When selecting software, be sure to |
| Unfortunately, most companies do not have an | | | | pay as much attention to selecting the right |
| individual with these qualifications working for | | | | vendor as you do selecting the right software. |
| them, so the purpose of thise article is to | | | | Check their service history, ongoing relations with |
| describe the kind of input that decision makers | | | | clients, and so on to ensure you aren't without |
| should seek out from other areas of the | | | | the support you need down the road. |
| company as well as provide a list of areas that all | | | | 10) Other members, as deemed necessary based |
| companies must research extensively when | | | | on the size of your company and your company's |
| evaluation potential construction management | | | | unique operational procedures. |
| software packages. | | | | Factors that All Companies Need to Consider and |
| Input and Software Selection Team Members | | | | Evaluate |
| that are Good to Have | | | | While smaller companies will likely not benefit from |
| While larger companies will have the advantage of | | | | having a full team dedicated to selecting new |
| being able to assign one individual to oversee the | | | | software, there are still things that all companies |
| entire software selection process, all companies | | | | much consider when evaluating new construction |
| will need to get input from multiple areas of the | | | | software. |
| company. The following segments of the entire | | | | At the very least, all companies need to complete |
| organization should be included, to some extent, in | | | | a thorough evaluation of the following factors and |
| the new software identifcation and evaluation | | | | research points: |
| team. Some of these members will need to be | | | | 1) Product varieties - How many are there? What |
| permant members of the team while others can | | | | makes them different? |
| be consulted on an "as needed" basis. To what | | | | 2) Vendors - How many are there? What makes |
| extent members are "as needed" or permanent | | | | them different? |
| will very depending on the company. | | | | 3) Product history - look for testimonials from |
| 1) End users - this group consists of anyone that | | | | trusted sources or check construction software |
| will be responsible for using the software, | | | | reviews |
| particularly those responsible for inputting data | | | | 4) Vendor history - testimonials |
| 2) Management - Mid and upper level managers | | | | 5) Product functionality - while most software |
| will be the ones that use the software primarily | | | | does the same "stuff" the manner in which it |
| for reporting purposes. As such, it is important to | | | | does it will be different. What is right for one |
| know what kinds of data are relevant for the | | | | company may not work for another. |
| particular company. | | | | 6) Product protocols - what reports are standard? |
| 3) Accounting - Changes in software will impact | | | | Can it create the custom reports you need? |
| how data is recorded and reported for accounting | | | | 7) Product interface - this will come down to |
| purposes. Thus, the accounting department (or | | | | personal preferences more than anything, but is |
| third party accountant) will need to be involved in | | | | important that you choose software that is the |
| identifying the best software. | | | | most user friendly for your set of users. Again, |
| 4) Payroll - Regardless of if your company has an | | | | this will vary based on your unique company. |
| internal payroll department or uses an external | | | | 8) Product integration - will there be any issues |
| payroll service, they will need to provide valuable | | | | integrating it with your current processes? Do you |
| input in terms of selecting new construction | | | | need to change processes or search for a |
| accounting software. | | | | different piece of software? |
| 5) IT (Information Technology) - Your IT | | | | 9) Other - This will depend on the unique |
| department will play an integral role in installing the | | | | organizational structure, personnel, and processes |
| new software while allowing the company to not | | | | of your organization. |