The executive view can be used to browse a group of projects in a single dynamic view. This is similar to a well-built project summary report with the added functionality of allowing the user to drill down into a Project Dashboard view. The Project Dashboard view allows for further research regarding the project in question.

 

 

The executive filters allow for several methods to select a group of projects. If these standard filters do not supply the desired project groupings, then consider the use of the Parent/Child relationship built into the system. With a little imagination the Parent/Child relationship can provide for absolutely any grouping desired. In the example discussed here, we are using a Parent project  representing an entire department. By doing this we have a grouping of projects providing important data to department managers.

 

Depending on how your Solomon company is set up, departments may be defined differently. In the example discussed, the gl_subaccount is what is used to determine the department. A stored procedure is used to maintain the department parent/child relationships. By using a scheduled stored procedure, we have removed the additional effort that would be required to maintain the parent/child relationship. 

 

 

We have modified the columns to the desired headings and content. Proper care has to be taken as to the order of columns being used when  planning this out.

 

 

It is possible to ultimately control the entire content of the Executive view. The only limitation is the columns provided by Spitfire. In version 2.xx there is only one column allowing for a percentage. The remaining columns have numerous default contents that we can be modify the data via SQL programming. In this example we have added an "unbilled" column in an attempt to show those project charges that have not yet been billed.

 

 

The bottom of the executive view summarizes those columns that have been included in the setup.