Computer Automation Department\'s Bas Case

Computer

Automation Department's BAS Case Study

This quick report is an analysis of the Automation Department's BAS concerns. There are specific and identifiable problems within the existing system; namely, there are many different control BAS units in the new and existing buildings. At first this problem appears to be a physical issue because of the multiple units, specifications, buildings and a lack of standardization which has lead to duplication and cost inefficiencies. However, the real concern that may not be addressed is a failure to communicate or agreement between departments as well as a lack of managerial approval for previous projects. The only way there should have been a solution rendered is if it had been presented to a top level managerial team for evaluation and approval.

For this reason, an alternative solution that would fit this communication deficiency would be to use an influence diagram that is updated by all appropriate departments and management teams. An influence diagram is nothing more than a list of factors for a specific problem that utilizes a combination of arrows and signs that show relationships between the various parts of the problem. An influence diagram has detailed rules that help decision makers pay strict attention to various differentiating options and the variables of a problem. (Zumuda, 2004)

Although the example above is not for the Automation Department's specific problem, the diagram does lay a foundation of what can be achieved by using the influence diagram as a decision making tool.