As many people joked on the webinars, it is the longest anyone has ever seen me stay in the presentation and out of the product.  Well, this is the reason why – so that I have a ready made presentation with lots of information and references to share with you.

As always, please feel free to get in touch with any questions or if you simply want to see this stuff in action.  We can either do a call and web meeting or I can get you a login to our demo site to play with it yourself.

I hope you find something you never knew was there!

The condition of your building and equipment including their outstanding deficiencies and deferred maintenance liabilities affect their value and their ability to support your business. The Condition Assessment activity lets you manage this cost and risk. This Web-based application coordinates teams to assess the conditions of even very large and dispersed real estate holdings.

It ensures completeness of coverage by assigning assessors specific checklists of tasks within the assessment program, and it accepts reports from both hand-held devices and Web forms.  The activity presents analyses of your assessment items based on their importance to safety, risk to the organization, or drag on the organization’s mission.  It then puts these assessment items directly into action – by grouping them into capital packages for funding and by creating On Demand Work requests to route the task to in-house or out-sourced teams.

Enhanced Preventive Maintenance Activity

There are significant improvements to improve the speed, process efficiency, and accuracy of preventive maintenance.

Scheduling Equipment In-bulk

You can now assign procedures to multiple pieces of equipment and define PM schedule rules for multiple equipment-procedure combinations.

Service-level Agreements

You can assign pre-defined Service Level Agreement to preventive maintenance requests.  The Service Level agreement can automatically route the work to the proper craftsperson, enforce rules for time to respond to the issue, and automatically issue the work request if that is desired.

Scheduled Generation

You can automatically generate Work Orders for Preventive Maintenance Work Requests according to a set of rules that you define.

Load Balancing

You can edit schedules directly from the 52-week PM Work Schedule report in order to balance the workload for trades.

Planning Board

You can also use the Planning Board to schedule Preventive Maintenance Work Requests to craftspersons just the same as you schedule On Demand Work Requests.

New Web Central Features & Improvements for V.18.2

Data Transfer Action

A Data Transfer action lets you move data into and out of Web Central using Excel spreadsheets and csv files.  Use this feature for transfers, backups, offline data development by admins or services providers, and countless other uses.

The action has:

• Options to compare new, updated, and removed items between data sets both before and after you invoke the command.
• An error log to flag any records that could not be imported because they violated business rules.
• An optional Transfer Status field that lets you use the Web Central Smart Search console to filter on the inserted, updated, deleted, no change, or missing (that is not in the imported set).

Export Action

ARCHIBUS still supports the Export action, which also can export to XLS format.  The distinction is that:

• Data Transfer exports data in accurate machine-transferrable format (e.g. dates use ISO format, enumerations use the  language-independent stored value)
• Export exports data in human-readable format (e.g. dates use the current user’s locale, enumerations use the translated display value of the user’s chosen language, etc.)

Data Management & Technical Enhancements

Cascading Update and Delete

Some changes need to cascade between tables.  For instance, if you rename a Department Code, you want that change to cascade to any rooms, equipment, work requests, and so forth assigned to that department.
Previously, you could only perform cascading updates and deletions in Sybase databases or in the Windows Client/Server projects.  With V.18.2, you can perform them in Web Central on Oracle and Microsoft SQL Server Projects as well.

Merge Command

This form prompts for an old primary key and a new one, and merges all child records for the old key (e.g. Building “HQ”) beneath the new one (e.g. Building “HCN”).  The command then removes the record with the old key. The effects of the command are similar to a cascading update, however, the new value can already exist.

The command is useful for when you reorganize your space hierarchy, organizational hierarchy, or standards codes, and you wish to merge two categories into one without losing the assignments of the child records within that category.  Without this command, you have to move the child records table by table.

Download the full resolution video of this feature here: OSIS 2.8 – Sneak Peek – Report Quick Sort

The first feature in this series we’ve coined as Report Quick Filters. This is a new feature similar to the currently available filtering ability in OSIS but way more user friendly and a lot quicker to use. Additionally, for system managers these are very easy to implement in your environment for your existing reports: simply turn them on for a given field in a report. Of course there are advanced features you can use if you so desire such as filter linking so that one set of filter criteria restricts another. e.g., A building selection restricts a list of departments.

Some key features of filters:

• Auto filter setting uses the system determined filter style. This can be overridden should you choose to do so.
• Some filter controls include:
• Date picker
• Multiple selection check boxes
• Free form input box
• Drop down boxes
• Ability to link one filter to the next so that a selection from one restricts the choices in another
• IAC applies to filters and filter lists
• Add descriptions to your filters to help guide the user.

Download the full resolution video of this feature here: OSIS 2.8 – Sneak Peek – Quick filters

The Report Transformed Into a Portlet

An OSIS portlet is simple in structure and consists of the following pieces:

• A database record describing the portlet (stored in the osis_portlets table)
• A file stored in the osis/cfm/portlets directory that acts as a container for the portlet
• A file or set of files that contain the content of the portlet. This content could be a custom SWF file, some ColdFusion code, content from other systems (e.g. a Twitter feed), or in the context of this article an OSIS report

Requirements

• An OSIS 2.6 install – use of a development environment is strongly recommended
• Some basic SQL and ColdFusion programming knowledge
• OSIS report authoring experience
• That you have read and understand parts I and II of this series

The Steps

Step 1 – Create The Report

For this tutorial we will utilize the same report created in Part I. (see New In OSIS 2.6 – Feature Spotlight – Custom Reports Framework – Part I ) You can either create a new report from scratch or copy your existing one (make note of the new report ID).

Step 2 – Create The Report Template

Using your favorite text editor create a new CFM file called o_rpt_003.cfm in your “{osis install directory}/cfm/tpl/o_reports/o_sample” directory. Within that file copy the following code:

Custom Report Code

<cfquery name="SumQueryBldg" dbtype="query" maxrows="5">
	SELECT dv_id, udf_dv_id label , COUNT(rm_id) room_data FROM reportdata_qry GROUP BY dv_id, udf_dv_id ORDER BY room_data DESC
</cfquery>
<script type="text/javascript">
	function openReportWithRestriction(restriction_xml) {
		var url = "rpt_adv_main.cfm?cr=1&ml=0&rpt_id=000&pr=1&omod=" + restriction_xml;
		rptWin=window.open(url,"win1",'toolbar=0,location=0,directories=0,status=0,menubar=0,scrollbars=1,resizable=1,width=1000,height=650');
		rptWin.focus();
	};
</script>
<cfxml variable="restriction">
	<?xml version="1.0" encoding="UTF-8"?>
		<osis>
			<mod_reporting>
				<restrictions>
					<restriction condition="=" field="dv_id" field_udf="(SELECT dv.name FROM [[SCHEMAOWNER]]dv dv WHERE dv.dv_id = rm.dv_id)" group=") AND (" table="rm" value="$ITEMLABEL$"/></restrictions>
			</mod_reporting>
		</osis>
</cfxml>
<cfchart title="Top 5 Room Count By Division" format="flash" xaxistitle="Division: " chartWidth="310" chartHeight="300"
	yAxisTitle="Count of Rooms" pieSliceStyle="sliced"
	url="javascript:openReportWithRestriction(""#JSStringFormat(restriction)#"");" show3D="yes">
    <cfchartseries type="pie" query="SumQueryBldg" itemcolumn="label"
        valuecolumn="room_data" paintStyle="light" >
    </cfchartseries>
</cfchart>
<style>
	div.rpt_cust_content_wrapper  {
		margin-left: 0;
		margin-right: 0;
	}
</style>

Ensure the report from Step 1 above has a its”Fixed Format Report Name” set to:

/osis/tpl/o_reports/o_sample/o_rpt_003.cfm

Step 3 – Create The Portlet Container

Under the “{osis install directory}/cfm/portlets” directory create a new CFM template called p_tut_003.cfm. Within that CFM file add the following code (remember to replace rpt_id=000 with the ID of your report from Step 1):

Portlet Container Code

<table>
	<tr CLASS="TR_BODY_CTRL">
    	<td>
			<iframe id="p_tut002" scrolling="no" style="border: none;" width="310" height="320" src="/osis/reports/rpt_adv_main.cfm?rpt_id=000&filt=0&rt=0&ff=0&iz=1&cr=1&slo=0"></iframe>
		</td>
	</tr>
</table>

Step 4 – Add Portlet Meta Data

In the osis_portlets table add a portlet record using “TUT_003″ as the Portlet ID.

Step 5 – Select The Portlet For Your Dashboard

In OSIS user settings select the portlet for use on your dashboard (myOSIS.)

This works well for specific use scenarios but what if I wanted to apply the setting application wide such that no report displays the restriction indicator or no report displays the project name in the report title? The answer: Set them in your Application.cfm file.

For the example above in the OSIS Application.cfm file after the line you can add the settings for the variables using the URL scope:

Application.cfm Snippet

<cfset url.dpd = 0 />
   <cfset url.dr = 0 />

The Original Report

The Modified Report

In this installment we will create a custom graph representing the same set of data.

The Final Report

Requirements

• An OSIS 2.6 install – Use Of a Development Environment Strongly Recommended
• Some basic SQL and ColdFusion programming knowledge
• OSIS report authoring experience

The Steps

Step 1 – Create The Report

For this tutorial we will utilize the same report created in Part I. (see New In OSIS 2.6 – Feature Spotlight – Custom Reports Framework – Part I ) You can either create a new report from scratch or copy your existing one (make note of the new report ID).

Step 2 – Create The Report Template

• Download and copy this file into the following directory:
  

  {osis install directory}/cfm/tpl/o_reports/o_sample

• Ensure the report from Step 1 above has a its”Fixed Format Report Name” set to:
  

  /osis/tpl/o_reports/o_sample/o_rpt_002.cfm

Understanding the Template From Step 2

Manipulate Query Data

<cfquery name="SumQueryBldg" dbtype="query" maxrows=5 >
SELECT dv_id, udf_dv_id label , COUNT(rm_id) room_data FROM reportdata_qry GROUP BY dv_id, udf_dv_id ORDER BY room_data DESC
</cfquery>

The query returned via OSIS is returned in the variable reportdata_qry. The field names contained therein are the same as those you have defined in your report. this includes any UDF fields. In this sample we have sorted the query in descending order by the COUNT of room codes and have grouped by the rooms division assignment. As this is a top 5 type report we have limited the number of rows returned to 5 using the cfquery variable maxrows.

Javascript For Drill Down Report Link

<script type="text/javascript">
function openReportWithRestriction(restriction_xml) {
var url = "rpt_adv_main.cfm?cr=1&ml=0&rpt_id=55&pr=1&omod=" + restriction_xml;
rptWin=window.open(url,"win1",'toolbar=0,location=0,directories=0,status=0,menubar=0,scrollbars=1,resizable=1,width=1000,height=650');
rptWin.focus();
};
</script>

This Javascript function provides the method to open a report in a new window based on the chart item (pie slice) clicked on in the report. Don’t forget to replace rpt_id=55 with your report ID: e.g., rpt_id=210.

Generate Standard OSIS Restriction For Report

<cfxml variable="restriction">
<?xml version="1.0" encoding="UTF-8"? >
<osis>
<mod_reporting>
<restrictions>
<restriction condition="=" field="dv_id" field_udf="(SELECT dv.name FROM [[SCHEMAOWNER]]dv dv WHERE dv.dv_id = rm.dv_id)" group=") AND (" table="rm" value="$ITEMLABEL$"/></restrictions>
</mod_reporting>
</osis>
</cfxml>

This block of code generates the XML format restriction used by OSIS reporting. The restriction in this sample will restrict the linked report to the specific division clicked on in the chart. The $ITEMLABEL$ is a placeholder for the label which in this case is the divisions name (from the dv.name field.) As such we have also specified that the restriction is based on a UDF.

Use CFCHART to Generate the Chart

<cfchart title="Top 5 - Room Count By Division" format="flash" xaxistitle="Division: " chartWidth="800" chartHeight="600"
yAxisTitle="Count of Rooms" pieSliceStyle="sliced"
url="javascript:openReportWithRestriction(""#JSStringFormat(restriction)#"");" show3D="yes">
<cfchartseries type="pie" query="SumQueryBldg" itemcolumn="label"
valuecolumn="room_data" paintStyle="light" >
</cfchartseries>
</cfchart>

In this final block of code we use the standard ColdFusion CFCHART tag to generate a pie chart.

Additionally, a standard search only page can be found by following this link: Idisis Search. From here you have access to a simple interface to search for information on any of our sites including the OWIKI (OSIS Help), our main web site, and our Blog (knowledge base).

Below is a sample from our OWIKI. Notice the links at the top of the search results, these will allow you to further refine your search via a single click.

Here is a sample from our blog site. Notice the results are identical to the search on our WIKI.

We will continue to refine and enhance the search to make it as easy as possible to get to the information you need and would appreciate any feedback.

Let us know what you think!

The Final Result

Requirements

• OSIS 2.4 or greater
• Experience in creating OSIS reports
• Knowledge of Javascript and SQL would be helpfull

Overview

The basic method was to utilize two standard OSIS reports, using one for the content of the main report with the chart while using the other to drive the pick list.  I threw in a little html and Javascript kung-fu to make each work in conjunction with each other.

The Steps

The main report with chart

1. Create an OSIS report utilizing the Work Request (wr) table as the basis for the report using the OSIS Create and Edit Reports tool
2. On the Report Classification, Headers and Titles pane we will need to set both a custom Report Header and a custom Page Footer
   

   Editing The Report - Custom Headers and Footers

   • The Report Header is a series of links (two in this case) using standard HTML that will provide a link to the pick list report (created later) and allow the user to clear any applied restrictions in the main report.  Take note of the report ID which in my example is 376 as this will need to be changed to the ID of the next report we will create.
     <ul>
     <li><a href="/osis/reports/rpt_mbody.cfm?rs=10&sr=1&ml=1&da=0&rpt_id=376&wca=" target="info">Select a Building To Filter This Report</a></li>
     <li><a href="/osis/reports/rpt_adv_main.cfm?ml=0&rpt_id=375&filt=0" target="reportframe">Clear Filter</a></li>
     </ul>

   • The Page footer contains a style definition to hide various parts of a standard OSIS report such as the title, footer, and header information.  I have included it in this sample in order to make a cleaner looking report.
     <style>
     #rpt_title_wrapper, #rpt_pageheader_wrapper, #rpt_pagefooter_wrapper, .rpt_chart_control_wrapper {
     display: none;}
     </style>

3. Add three report fields one based on the prob_type field, one on the wr_id field and one on the bl_id field.  Once saved you can edit each based on the following settings
   
   

   Overall Field Layout

   • For Building Code Field
     
     

     Building Code Field

   • For Problem Type Field
     

     Problem Type Field

     UDF For Problem Type

     ISNULL(wr.prob_type,'None Assigned')

   • For Work Request Field

     Note: For this field I have used a UDF and named the field as a UDF.  The outcome would be equally as effective if you used the wr_id field directly.

     
     

     Work Request Field

     UDF for Work Request

     wr.wr_id

4. Specify report features
   

   Report Features

The secondary report for the pick list

1. Create an OSIS report utilizing the Building(bl) table as the basis for the report using the OSIS Create and Edit Reports tool
2. Add a single field to the report based on the Building Code (bl_id). This field, after saving the report, will utilize the UDF statement contained in this file: udf_for_building_code_field
   

   Building Code Field

Though the ARCHIBUS application client is ultimately tied to the Windows platform, the web client is based on Java technology and impartial in regards to its Operating Systems (OS) and the browsers that may consume it. Essentially, one may find themselves running their database on a Sun Solaris OS while hosting Web Central on a Mac OS (can’t wait until the release of Snow Leopard!) and serving up the solution to Linux users via the Google Chrome browser.

The following steps will outline an overview for configuring Web Central on a Unix platform which encompasses different flavors such as Linux, Solaris, Irix, Ubuntu and Mac OS.

First, we can no longer deploy Web Central via a Windows executable. If the idea of this causes you to squirm, then just understand that this can be done but leave the how part to your system administrator.

Secondly, we must ensure that JRE and Apache Tomcat are installed as standalones on your system as per documentation of the software. I will mention that close attention must be paid to the environment variables such as [JAVA_HOME]. For example, Solaris demands that the path be set via the command prompt while Mac OS recommends the creation of an environment.plist.

Configuring environment variable JAVA_HOME on Mac (01)

Please note that this can be done on either the root or per user profile. Java path may vary depending on the location chosen for the install of the JRE. Furthermore, OS such as Solaris is case-sensitive even at the folder level.

Configuring environment variable JAVA_HOME on Mac (02)

To ensure that the Web Central files are properly deployed by your Tomcat engine, the archibus.war package must be placed at the following location:

\tomcat\webapps\

Finally, we must configure the Tomcat engine to include a runtime command that ARCHIBUS has embedded within the Windows batch file. For those running Tomcat version 5.x, this configuration file is called catalina.sh. A memory specification must be declared to properly instruct resource allocation for the orderly execution of the application. The example below assumes that the server has 1 GB of memory readily available for the application.

Configuring Catalina.sh

Of course, make sure that your afm-projects.xml and afm-secure.xml are configured based on your project and database settings.

Start up Tomcat in your terminal:

./startup.sh

If for any reason, your Tomcat server and the ARCHIBUS application do not deploy, check the error messages captured in \tomcat\logs\*.logs and \tomcat\webapps\archibus\WEB-INF\config\archibus.log respectively.

Web Central on Sun Solaris

Software used in this setup:

Java Runtime Environment (JRE) 1.5.0_16

Apache Tomcat 5.5.27

ARCHIBUS Web Central 17.3.3.031

Oracle DB Server 10 R2

Mac OS X 10.5.6

Solaris 10 update 2

Ubuntu 8.10