Importing CSV data into OSIS

The CSV Data Import is an OSIS utility tool to quickly migrate data into 7 standard OSIS models. Each model will have a separate template used for importing the data.

Notes

MAKE SURE THE CSV IS ENCODED IN UTF-8 FORMAT

  1. Encoding and Saving with Notepad++
    • Open the file in Notepad++
    • click Encoding -> Convert to UTF-8
    • save as .csv
  2. Saving with Excel
    • File -> Save As -> Browse
    • Select CSV - Comma delimited (.csv) as file type
    • In the save as menu click the Tools dropdown > Web Options and save as Unicode(UTF-8)
    • Click OK, then save file

Only include fields you wish to update, or include ALL columns when creating a new record

Asset Standards

Asset Standards are the generic assets that an organization owns. These assets are not tracked individually.

Columns

Available Columns

  • title
  • label
  • model_no
  • asset_type
  • description
  • building
  • floor
  • room

Required Columns

  • title
  • asset_type
Assigning Asset Standards to Locations
  1. Building
    • include the building code in their respective columns
  2. Floor
    • include the building and floor code in their respective columns
  3. Room
    • include the building, floor and room codes in their respective columns
Examples

Importing Assets without Locations

Sample data #1 | title | label | model_no | asset_type | description | |————|————-|—————-|—————–|——————-| |Task Chair|LazyBoy Chair|02123|Furniture|This will need to be approved by your manager|

Sample data #2 | title | asset_type | |————|————-| |Lamp|Furniture|

Importing Assets with Locations

Sample data #3 | title | asset_type | building | floor | |————|————-|————-|————-| |Lamp|Furniture|HQ|19|

Sample data #4 | title | asset_type | building | floor | room | |————|————-|————-|————-|————-| |Lamp|Furniture|HQ|19|107|

Employees

#####Columns Available Columns

  • employee_id
  • name_full
  • name_abbreviated
  • phone (max-length 24 characters)
  • email
  • status

Required Columns

  • employee_id
Examples

Sample data #1 | employee_id | name_full | name_abbreviated | phone | email | status | |————|————-|—————-|—————–|——————-|——————-| |doe john|John Doe|John D|880-5558888|john@doe.com|active|

Sample data #2 | employee_id | name_full | |————|————-| |doe john|John Doe|

Sample data #3 | employee_id | phone | email | status | |————|————-|————-|————-| |doe john|880-5558888|john@doe.com|active|

Location

Locations in OSIS represent physical built spaces in the real-world. A typical set of locations for the built environment includes buildings, floors in a building, and rooms on a floor in a building. This information will usually come from an IWMS system of record but can also be created within OSIS itself if needed.

#####Columns Available Columns

  • location_type (any of - building, floor, room, desk)
  • region
  • site
  • building
  • floor
  • room
  • desk
  • address
  • city
  • state
  • country
  • description
  • name (indicates primary name of location)
  • label (indicates another label which could used to identify location)
  • alt_label
  • lat
  • lng
  • floorplan_x
  • floorplan_y

Required Columns

  • location_id
  • location_type
  • building
Examples

Sample building data #1 | location_id | location_type | building | country | state | city | name | |————|————-|—————-|—————–|——————-|——————-|——————-| |HQ|building|HQ|United States of America|Pennsylvania|Philadelphia|Headquarters|

Sample building data #2 | location_id | location_type | building | name | |————|————-|—————-|—————–| |HQ|building|HQ|Headquarters|

Sample building data #3 | location_id | location_type | building | floor | |————|————-|—————-|—————–| |HQ-01 (building code - floor code)|floor|HQ|01|

Sample building data #4 | location_id | location_type | building | floor | room | |————|————-|—————-|—————–|—————–| |HQ-01-110 (building code - floor code - room code)|room|HQ|01|110|

Location Classification

Location Classifications are used to categorize locations records.

#####Columns Available Columns

  • class_id
  • label
  • level

Required Columns

  • class_id
  • label
  • level
Examples

Sample data #1 | class_id | label | level | |————|————-|—————-| |EXT|External Area|Room Category| |LAB-BENCH|Bench Lab|Room Type| |UNAVAIL-WKSTN-NA|Workspace that is currently not accessible|Room Type| |non_occupiable|Non-Occupiable|Occupancy Status|

Location - Employee Tags

Location - Employee Tags import will create the tag, then creates the relationship between the Employee, Location and Tag.

#####Columns Available Columns

  • tag_title
  • tag_description
  • building
  • floor
  • room
  • employee_id
  • employee_email

Required Columns

  • tag_title
  • building
  • one of employee_id or employee_email
Examples

Sample data #1 | tag_title | tag_description | building | floor | employee_email | |————|————-|—————-|—————-|—————-| |Fire Warden|Person of Contact during a fire|HQ|19|doe_john@tgd.com|

Sample data #2 | tag_title | building | floor | room | employee_email | |————|————-|—————-|—————-|—————-| |Fire Warden|HQ|19|101|doe_john@tgd.com|

Location - Sensor Mapping

Location - Sensor Mapping import will create or update a sensor and assign the sensor to a location.

#####Columns Available Columns

  • sensor_id
  • tag_description
  • building
  • floor
  • room
  • active

Required Columns

  • sensor_id
  • building
Examples

Sample building data #1 | sensor_id | building | |————|————-| |HQ-ONLINE|HQ|

Sample floor data #2 | sensor_id | building | floor | |————|————-|————-| |hq-19-sensor|HQ|19|

Sample room data #3 | sensor_id | building | floor | room | |————|————-|————-|————-| |hq-19-sensor|HQ|19|101|

Theme Rules

A theme rule is a distinct stylization used on a floor plan layer, to highlight specific rooms based on assigned groups (classifications, organization, teams & tags)

#####Columns Available Columns

  • label (individual label for each rule)
  • fill_color (theme rule fill color)
  • line_color (theme rule line color)
  • fill_opacity (Opacity of the fill color. A value from 0-1, Any Opacity number between 0 and 1 will make the element semi-transparent)
  • line_opacity (Opacity of the line color)
  • line_weight (specifies how bold lines should for the theme rule)
  • hatch_pattern (Available patterns -> None, “Diagonal (back)”, “Diagonal (forward)”, Cross, Grid, Horizontal, Vertical)
  • hatch_color (color of the hatch applied)
  • hatch_opacity (opacity of the hatch drawn)
  • menu_order (order in which the rule appears in the legend)
  • key1_field (Available keys -> classification, owned_org, occupying_org, tag)
  • value_level
    • if key1_field IS classification, available value levels are - Room Category, Room Use, Room Type, Room Standard
    • if key1_field IS ANY of owned_org or occupying_org, the available value levels are - Business Unit, Department, Division
    • if key1_field IS tag leave this field blank, please provide value_name instead
  • value_name (Name of field that is to be styled i.e. Label of the Organization, Team or Classification)
  • value_code (Unique code of field that is to be styled OSIS specific identifiers - class_id, org_id, team_id, tag)

Required Columns

  • label
  • fill_color
  • line_color
  • fill_opacity
  • line_opacity
  • line_weight
  • hatch_pattern
  • hatch_color
  • hatch_opacity
  • menu_order
  • key1_field
  • One of the Following is required
    1. value_level & value_name
    2. value_level, value_name & value_code
    3. value_code