OSIS Floor Plans – Hovers and Labels

OSIS provides a flexible system for managing the look and feel of floor plans. One example of this is using the hover/label tools to present information to users. We could literally explore your options here for hours, but let’s at least start with a basic scenario – changing a Rooms by Department layer to show different text when a user hovers over a room.

Take a look at the video below to check out the process.

And the best part? That change we just made now applies to EVERY floor plan in your system.

Controlling OSIS Reports with URL Parameters

OSIS Direct Links (ODL) allow users to create specific URLs for every feature of the system.  These ODLs can also include some additional parameters to further specify how the page should look and behave.  The following is a list of URL parameters for reports. Note that these can be added to the end of the standard report URL with the addition of “&” at the end.

Using these parameters helps with sending out the specific look and feel you want for users. It is also a great way to integrate OSIS reports into other systems and applications in precisely the way you choose.

Parameter Description Options
dt Display Toolbar – hides or displays the report toolbar 0 (off) or 1 (on)
dsh Display Sub Header 0 (off) or 1 (on)
dph Display Page Header 0 (off) or 1 (on)
dpf Display Page Footer 0 (off) or 1 (on)
dr Display Restrictions 0 (off) or 1 (on)
cr Clean Report – display a clean report, toggles all the above off (takes precedence over any of the above) 0 (off – has no effect) or 1 (set all off)

By default all the above are set to 0. ie., If un-specified in the URL they will be treated as having the value of 0 (off).

Sample URLs and Results
One of the first things to know about using these parameters is how to find the URL for an OSIS Report. There are several ways to do this. One way is to open the report in OSIS and then use the Create Shortcut function on the report toolbar.

blog_odl_rpturl1

Another approach is to right-click in the report you have opened and select Properties. You can then highlight and copy the URL as shown below.

blog_odl_rpturl2

Now let’s take a look at the Clean Report (cr) parameter too see what effect it has. The standard look of an OSIS Report is:

blog_odl_rptbase-1

With the Clean Report parameter added, it looks like this:

blog_odl_rptcr

Notice that the toolbar, title, headers, and restriction detail areas all disappear.

How about the Report Toolbar?
In OSIS 2.6, you can also specify the type of toolbar you want to appear with the Toolbar Type (tbt) parameter.  This is very helpful for the casual user that is not familiar with the icons in the standard OSIS Report Toolbar. The options are:

Value Toolbar Type
0 Standard – Pinned
1 Non-Flash – Full
2 Non-Flash - Basic

Toolbar Examples
The following is a set of sample URLs and the resulting Report Toolbar that loads. Notice that the only difference in the URL is the tbt (Toolbar Type) parameter at the end.

http://localhost/osis/reports/rpt_adv_main.cfm?rpt_id=151&filt=0&rt=0&ff=0&iz=1&tbt=0

blog_odl_tbt0

http://localhost/osis/reports/rpt_adv_main.cfm?rpt_id=151&filt=0&rt=0&ff=0&iz=1&tbt=1

blog_odl_rpt_tbt1

http://localhost/osis/reports/rpt_adv_main.cfm?rpt_id=151&filt=0&rt=0&ff=0&iz=1&tbt=2

blog_odl_rpt_tbt2

Using ARCHIBUS Web Central’s Preventive Maintenance to Manage Building Contracts

Introduction

Idisis recently worked on a project that stepped outside the traditional boundaries of Preventive Maintenance but utilized the base business concepts and technologies to manage contractual building maintenance referred to as “Facility Management Agreements” (FMA’s).

The FMA’s represent a predetermined list of maintenance items that are performed in a building based on pre-defined contractual terms, maintenance levels and budget allocations.

The Facilities Management program was developed to achieve the following goals:

  • to ensure effective use of maintenance dollars
  • to ensure that school buildings are more efficiently and effectively maintained
  • to ensure that tradesmen are in the schools on a regular basis
  • to increase the confidence of schools in Facilities Maintenance and the services that they provide
  • to improve energy conservation

Project Background

Industry: Public School District
Building sites: 236
Open Schools: 195
Students: Approximately 79,000
Space leased to other organizations: 25,000 m2
Yearly service requests: 26,000
Current Project Phase: Phase I – Service Desk, On Demand Work Management, Preventive Maintenance and Facility Management Agreements

Maintenance & Service Model

A number of services within the School District, such as building maintenance, educational consulting, and technology support, are provided by internal cost recovery units. These units do not receive a budget allocation but rather generate their revenue by charging the requester for labour, materials and services provided. From the School’s perspective, this allows for greater control of how their dollars are spent and prioritized on maintenance and other services. This also allows service providers to staff to appropriate levels and makes them accountable directly to the service requester.

Understanding the FMA Levels

There are three levels within the Facility Management Agreement program:

Level 0 – Mandatory/Regulatory Items

Mandatory maintenance to ensure regulatory requirements are met.

Level 1 – Basic Maintenance
  • Essential services
  • Legal requirements
  • Best practices
  • Economic feasibility
  • Government regulated inspections
  • Repair of critical equipment
  • Security monitoring
  • Snow removal trades personnel
Level 2 – Enhanced Maintenance

This level was designed with the ultimate goal of ensuring the best possible use of a schools maintenance dollars. Level 2 was designed to include all items in Level 1, plus:

  • Ceilings, floors, walls
  • Interior lighting (ballasts)
  • Locker and partition repair (routine wear)
  • Plugged drains and sewers
  • Public address systems
  • Access to carpet cleaning (once every 3 years)
  • Custodial mentoring (3 year rotational basis)
  • Crime Prevention through Environmental Design (CPTED) audits (3 year rotational basis)
  • Insurance claim assessments (3 year rotational basis)

Solution Overview

Product: ARCHIBUS Web Central
Module: Preventive Maintenance for Web Central (an ARCHIBUS “Activity”)
Additional: Idisis Web Central Development: Facility Management Agreement Utility

Basic Workflow
Basic Workflow

Basic Workflow

The ARCHIBUS Web Central Preventive Maintenance (PM) Activity is utilized to generate scheduled maintenance as per the FMA contracts. FMA’s are specific group of work items that take place for each school based on the FMA Level the school chooses to sign up for.

Once the PM’s are generated they are handled by a standard work management process and handed over to each shop for processing and work. The Shops then manage the PM’s through the standard ARCHIBUS On Demand work management process. Once work is complete, the work items are updated to reflect time and materials spent against each PM work request. The district has a trusted in hosue General Ledger (GL) application that interfaces with their PeopleSoft Financials system. The costs are handed off to the trusted GL system for work order billing and purchase order reconciliation.

Another aspect of the project is tracking an annual FMA Budget Allocation and a General Maintenance Budget Allocation for each school. As with any project/contract based process it is important to understand both committed dollars and actual expended dollars. In order to accomplish this reporting Idisis utilized the ARCHIBUS Capital Budgeting Activity coupled with ARCHIBUS’ Project Management Activity.

Projects are entered which represent FMA contracts for each school as well as the annual budget allocation (FMA Contract Amount). The budget allocations are then compared to the total costs reported through the work management process providing “where are we” analysis of both finance and work performed.

Announcing the YODLR (Your OSIS Direct LinkR)

Idisis is extending access to ODL with some new management tools to help you share information and spatial data in OSIS. ODL or OSIS Direct Linking was introduced in v2.4 but we quickly realized that we needed to improve access to this feature. Now users can easily create these direct page links and share OSIS floor plans with others.

If you have never used ODL, this feature allows you to create a “direct link” to any page in OSIS.  Users can then be directed to this page to view a floor plan, map, report, form, or portlet without having to open and navigate OSIS.  This is a great way to securely share information with more casual users without the need to train them.

map_odl2_blog600

The YODLR (Your OSIS Direct LinkR – we couldn’t help it) is a new set of tools that let users quickly generate direct links without the need to remember or look up the series of available parameters that control the ODL.  The create floor plan link YODLR appears below.  You can access the YODLR from our OSIS demo site or grab it from Idisis Labs and try it for yourself!  Please let us know if you need any help getting access at support@idisis.com.

yodlr2_blog600

New In OSIS 2.6 – Feature Spotlight – Custom Reports Framework – Part I

OSIS 2.6 includes the ability to create custom report content utilizing the standard reporting frame work. This allows you to format a report page utilizing data returned by the OSIS reporting engine in a any way you wish while preserving security, VPA/IAC, UDFs, searching and report restrictions.

This tutorial is intended for Advanced Admin users (or the adventurous type) with experience with SQL and ColdFusion.

In the following example we will create a report based on room data and display the output in a tag cloud.

Sample Report

Sample Report

Read the rest of this entry »

OSIS Quick Tip – Quick Dates In OSIS Forms

OSIS Forms offer the ability to enter descriptive names in date fields when specifying a date.  For example: if I wanted to insert tomorrow’s date I could type “tomorrow” into a date field, click off the field and tomorrow’s date value would then display in the field.  In the sample images below we use Friday as the textual representation of the upcoming Friday’s date.

The following is an excerpt from our Wiki on the subject, listing the available textual representations of data and time values:

Date fields have the ability to accept some basic free form text values to generate a date:

{Note: “x” represents the number of days, weeks, months or years.  e.g., “x d” would actually by type as “2 d” or “3 d” when used in a form}

  • current and today – will insert todays date
  • tomorrow – will insert tomorrows date
  • yesterday – will insert yesterdays date
  • next week, next month, next year – will enter the date for the following week(7 days), month, or year
  • last week, last month, last year
  • x day or x days or x d
  • x week or x weeks or x w
  • x month or x months or x m
  • x year or x years or x y
  • Monday, Tuesday etc. plus abr. e.g. Mon Tues etc.
  • Next Monday, Next Tuesday etc.
  • mm/dd/yyyy – will format as dd mm yyyy

Fields set as time fields will attempt to format the users input of a time value.

  • noon – will insert 12:00 PM
  • midnight – will insert 12:00 AM
  • 1pm or 1 PM – will format the date as 1:00 PM
  • 1 – will format the date as 1:00 AM
  • 13 – will format the date as 1:00 PM
  • 1:PM – will correct to 1:00 PM

ARCHIBUS Web Central Quick Tip – What axvw am I looking At?

Ever find yourself wondering what axvw file corresponds to a task in your navigator?  One quick way to find out is to right click and details shall be revealed.

What axvw am I looking at?  Right click and find out.

What axvw am I looking at? Right click and find out.

Applies to ARCHIBUS Web Central 17.2 and 17.3

OSIS Quick Tip – Bookmarking For A Specific Project

OSIS by default presents a user with a list of projects to choose from during log-on.  Some of you may have multiple projects in the list or just the one.  In either case you can specify your project via a bookmark so that the project is automatically chosen for you during the log on process (saves a click.)  In order to do so you would use the “p” switch in your URL string like:  http://localhost/osis/?p=osisdemo.  Of course for your particular system you will need to swap “localhost” for the name of your server and “osisdemo” with the short name (ID) of your project.

Additionally you can apply the same concept when bookmarking many of the components in osis such as reports or maps.  A report example might be: 

http://localhost/osis/reports/rpt_adv_main.cfm?rpt_id=66&filt=0&rt=0&ff=0&pr=1&p=osisdemo

In the case above by appending the &p={your project code here} to a standard report link you can link directly to the report for that project so that during log-on a project selection is not needed.

Notes:  

  • If you do work with multiple projects you will need to log-off in order to load a new project with a different project based link.
  • Applies to OSIS 2.4 or higher

Campus Mapping with OSIS

Campus Mapping with OSIS is often a significant opportunity for our clients to easily expand their systems to analyze information in new ways and share their hard work with others in the organization.

Campus map with integrated floor plans, utility mapping, land information

Campus map with integrated floor plans, utility mapping, land information

The discussion of campus mapping has three major areas of uncertainly for users:
  1. Does campus mapping apply to my type of organization?
  2. What type of information is used in a campus mapping project?
  3. What are other people doing with their campus maps?
Does campus mapping apply to me?
A common misconception with campus mapping functions is that it is a one size fits all engagement.  That there is only one set of source data that can be used, that you must have a traditional college campus, and that you have to create and manage all of the components that make up your maps yourself.  

In our experience with OSIS, we have supported campus mapping projects for:

  • Colleges and Universities with traditional contiguous campuses
  • Research Campuses of Governments and Corporations
  • Airports
  • Corporate Campuses
  • Downtown real estate holdings of Corporations
  • Municipalities
What can I use to create a campus map?
The next issue that often stalls projects is uncertainty over what information can be used to create campus maps.  The answer is often that there are more and more good sources of this information than our users suspect.

There is no one single requirement to successfully add campus mapping to your OSIS projects. Our users have success with DWG format site plans and maps, ESRI data, MapGuide SDF data, corporate database systems, and fly over photography.

What is everyone else doing?
Finally, our users are always interested in what other people are doing with campus maps. The key to this question is to understand what your organizational goals are and how maps can provide additional insight into the planning, analysis, and sharing of those goals.
The list of functions deployed with campus mapping is too lengthy to detail in full here, but the following is list of functions that our clients leverage via OSIS.
  • Building location tracking
  • Campus Master Plan reviews
  • Bus routes
  • Emergency call station locations
  • Reforestation planning
  • Traffic pattern analysis
  • Geographic drill down to floor plans
  • Sound barrier impacts
  • Environmental impact locations
  • Utility line mapping
  • Parking analysis
So how do we get started?
Typically the largest hurdle to the implementation of campus mapping with OSIS is the misunderstanding that the project will be a costly, difficult, or time-consuming process.

Please let us know if this type of information is of interest to you; I think you might be surprised at how quickly you can realize some quick success.

OSIS & As-Built Drawings

Facility record drawings, progress check sets, tender drawings, consultant data…how does this relate to ongoing facilities and project management?

Facility Managers and Project Managers often need to share information. While the facilities group manages existing conditions the project managers are managing “what-if” scenarios and the impact of facility planning and construction on existing conditions.

Enter OSIS...

Once modernizations, renovations and retrofits have been completed there is a need to update the facility management inventory as well as understand each discipline’s impact on the facility management layout. Mechanical HVAC, Electrical, Structural, Power & Communications and Site Conditions become valuable to facility managers for ongoing facility maintenance and planning; and the overlay of facility management information with these disciplines becomes important to project managers for the next phase of planning and construction activities.

Business Needs & Available Technology

The Business Side

Why should project managers and facility managers not share information to make more informed decisions? Good question…Part of this is related to technology and part of this is related to understanding the common business need between these two groups.

Often there is a perception that the technology does not support this, especially via the web or corporate intranets. This is not true and once the perceived barriers between these groups are broken down, business relationships between each group flourish as they are not blocked by technology.

Show Me The Drawings!

OSIS supports the overlay of existing facility management conditions with existing as-built information as well as proposed modernization, renovation and retrofit check set drawings.

Displays Room Inventory, Room Report, Sprinklers & HVAC as-built drawing.

OSIS also provides for cross discipline overlay giving users the ability to look at Sprinkler & HVAC drawings in relation to Power & Communications drawings, for example.

Displays Room Inventory, Sprinklers & HVAC as-built drawing, Power & Auxiliary as-built drawing, Fire Extinguisher locations as equipment assets.