12 Tips for Working from Home

slack logo

Join our #work-from-home open Slack group to get more tips and have a social outlet!

Considering the potential increase of the coronavirus, many companies are encouraging–or even requiring–their employees work from home. Working from home can be a difficult transition if you are not used to it: housemates can be distracting. The couch can look oh-so-comfortable, and a 20 minute nap can easily turn into an hour and 20 minute nap. Working from home can seem like the perfect opportunity to get the honey-do list completed and chores that have been piling up can look enticing. The list of readily-available distractions could continue for miles.

We understand the challenges that can come with working from home: RSC is a virtual company. This means that we have no physical office space, so every employee works from home, and we have 20 years of experience and tips we’ve collected on creating an ideal work environment in your home. Below are our staff’s first-hand recommendations. We hope you find them useful!

1) Create a “Work Only” space.

An image of a home office by a scenic window.
Create a comfortable, yet distraction-free, work space.

Aside from helping you focus on work instead of binge-watching “Frasier”, setting up an area at home that is “work-only” can signify to others that you are working and shouldn’t be bothered. Additionally, it helps you de-stress once work is over, because you can mentally “put work away” and fully enjoy the rest of the house and activities that are going on.

2) Set office hours and stick to them.

An image of a home office with a computer, notebook, and other accessories on a desk.
Stick to your office hours.

Treat work hours like sacred time. Set a schedule–it helps to keep your at-home hours the same as a usual nine-to-five workday, or whatever is typical of your organization–and don’t vary from these. Don’t justify that a 45-minute run to the store won’t effect your schedule too much. Don’t let distractions like kids, peanut butter cookies on the counter, or playing with your pets pull you away from your focus.

3) Schedule meetings for mornings.

Leaving the beginning of the work day for meetings is a great way to stay focused throughout the day, because you now have a task that helps you know what you need to accomplish. It also helps motivate you to get out of bed and work instead of pushing your schedule back and procrastinating the work day.

4) Match your work hours to the schedule of your housemates.

An image of a woman wearing glasses at a desk working on a computer. She is smiling and is in an art studio with paintbrushes.
For a distraction-free workspace, work at the same time as the people with whom you live.

Maintaining the same working hours as the people you live with is a great way to enjoy your time off once work is done. It minimizes distractions so everyone can have a quiet environment to work in and doesn’t step on each others’ toes. 

5) Take frequent breaks.

Standing up from the computer is important not only for your posture, but also for your mental health. Getting up frequently and taking a stroll around the yard or house will help you keep a fresh attitude towards work and cut down on the mundaneness of working from home. Some of our staff hold to a strict “get up every hour” rule.

6) Schedule “Leave the House” time.

An image of a dog laying under a desk and office chair while someone in blue jeans, sitting at the desk, works.
Schedule a time to get out of the house and stretch your legs.

Schedule a time to get out of the house and detach from work. Usually, this would include activities like going out to lunch, working out at a gym, or taking a yoga class, but with the stay-in-place mandate applicable to most of us, this principle looks a little different right now. Going for a walk or drive can be great substitutes for this. If you have a garden or yard, walk around it. Even using technology like a wii could help you get in the mindset that will help you de-stress from work and clear your head.

7) Schedule your meals.

On the topic of breaks, it can be easy to get wrapped up in the “I’ll just do one more thing” mentality and forget to eat regular meals. Scheduling a specific time for your meals can help you keep a consistent schedule, maintain energy for the work day, and reinforce taking frequent breaks.

An infographic with RSC's twelve tips for working from home listed.

8) Get ready in the morning just as if you’re going to work.

Dressing the same way you would for the office can help you mentally get in the zone to work, separate your “work-only” space from the rest of the house, and keep you focused on tasks: even the rote, mundane ones. Changing clothes once you’re done working into lounge-around-the-house attire helps you relax and separate even more from the office.

9) Don’t go straight to your workspace in the morning.

An image of a home office in a bedroom with calendars on the wall, a surfboard leaned against the wall, and a small shelf.
Refrain from sleeping right up until your work hours in order to get a few more minutes of sleep.

Give yourself time to ease into the day, enjoy the morning, and prep for work just like you would any other day. Let your house be your house for a little bit before you go into work mode. This, just like many of the previous points, will help you separate the spaces between work and home so you can de-stress after work.

10) Use a headset or noise canceling headgear.

Minimize distractions by using a quality, noise-cancelling headset for when you’re in meetings or listening to music to stay focused. You won’t be able to hear anything that may want to distract you. You’ll be able to  focus well so the day relatively flies by.

11) Invest in equipment to help your posture and joints.

An image of a supportive desk chair by a wood desk with a computer on it.
Invest in supportive equipment for your home office.

Giving your body good support will help make your at-home office comfortable. It’s not worth it to ruin your back, neck, hands, wrists, etc. while working. Some essential pieces to consider for your home office may be:

  • Supportive chair with adjustable height
  • Adjustable-height computer stand for sitting and standing
  • Keyboard for carpel tunnel
  • Mouse for carpel tunnel
  • Footrest
  • extra back support

12) Take advantage of some creature comforts, but not too many.

An overhead image of a woman sitting with her legs outstretched on a bed or couch, working on a computer.
If sitting on the couch helps you focus, then take advantage of that. But don’t use so many creature comforts that you can’t focus.

If you work better with some background noise that you wouldn’t usually be able to put on in the office, then put on some music or white noise. If you have a favorite window to sit by, or a favorite spot in your house, then set up your workspace in that area. If you have a favorite coffee, tea, or beverage that you don’t usually get at work, then pour yourself some of that.

Creature comforts can easily infringe on the “Creating a ‘Work Only’ Space” idea discussed above. It’s easy to surround yourself with too many. Determine which ones and how many help you stay focused and which ones don’t.


Like what you read? Subscribe to the blog and follow us on Twitter, Facebook, and Linkedin to keep up to date with the latest news from RSC, LLC.
Thoughts? Questions? Comment below and let us know what you think! We’d love to hear your insights.

Three SQL Tips to make ARCHIBUS View Development easier

My name is Todd Forsyth.  I’m the Technical Lead at RSC LLC.  We specialize in installing, hosting and managing ARCHIBUS CAFM/IWMS systems.  This is one of a series of posts on how to make that process easier if you’re doing something similar yourself.

If you’ve done much ARCHIBUS customization, you know that the key is building great ARCHIBUS Views, or AXVW files.  And so much of what makes this hard is getting the data that you need into the view.  I’m going to talk about 3 SQL tricks I’ve learned to make this process easier.

Queries Rather Than Tables

Many of the example queries you’ll see in ARCHIBUS views define datasources that connect directly to database tables.  This is useful, of course, but sometimes you need data from multiple tables, which is very difficult, or even impossible, to write a datasource that does this by just referring to the tables directly.

When this happens, it’s time to have the datasource refer to an SQL Query instead of to the tables themselves.   This gives you the opportunity to develop the query in another tool (like SQL Server Management Studio), so you can be sure you have the data right, and then embed the Query in your ARCHIBUS View.

Here is an example from a custom Energy Management View RSC built recently.  This was a BIG query.  I haven’t include the whole query, or all the columns we really used in the datasource definition, but you get the idea:

 

       <dataSource
id=”ds_waterChart” applyVpaRestrictions=”false”>
              <!– Define parameters for the
custom SQL query –>
              <parameter
name=”locationField” dataType=”verbatim”
value=”ctry_id”/>
              <parameter
name=”locationValue” dataType=”text”
value=””/>
              <parameter
name=”timePeriodFrom” dataType=”text”
value=””/>
              <parameter
name=”timePeriodTo” dataType=”text” value=””/>
              <!– Define a custom SQL query
that can be restricted by various location values –>
              <sql
dialect=”generic”>select
                           ‘Water Usage
Comparison’ water_usage_label,
                           ‘Water Cost
Comparison’ water_cost_label,
                           sum(case
                                  when
b.time_period like ‘2013-%’
                                  then   a.qty_volume * c.area_fraction
                                  else   0
                           end) base_usage_hcf
              from   bill_line_archive a
              join
                           bill_archive b
              on            a.bill_id
= b.bill_id
              join
                           rsc_primary_building
c
              on            b.bl_id
= c.primary_bl_id
              and           a.meterseq = c.meterseq
              join
                           bl d
              on            c.bl_id
= d.bl_id
              join
                           vn e
              on            a.vn_id
= e.vn_id
              where  b.bill_type_id = ‘WATER’
        </sql>
              <table
name=”bill_archive” role=”main”/>
              <field
name=”water_usage_label” dataType=”text”>
                     <title
translatable=”true”>Water Usage</title>
              </field>
              <field
name=”water_cost_label” dataType=”text”>
                     <title
translatable=”true”>Water Cost</title>
              </field>
              <field
name=”base_usage_hcf” dataType=”number” size=”12″
decimals=”2″>
                     <title
translatable=”true”>2013 Usage (HCF)</title>
              </field>
       </dataSource>

Use unions to write a few small queries instead of one GIGANTIC query.

Sometimes, writing even a query that can do EVERYTHING you need it to is frustratingly complex.  It is often easier to write a series of SMALLER queries that can be tied together with a UNION operator, where each query does part of the work.

For those not familiar with the SQL Union Clause, it is used to combine the result-set of two or more SELECT statements.  Each SELECT statement within the UNION must have the same number of columns.  The columns must also have similar data types.  Additionally, the columns in each SELECT statement must be in the same order.  As long as you follow these fairly simple rules, it’s easy to sew two queries together as though they were one, then embed the combined query in the SQL clause of an AXVW View.

A recent example was a view that was supposed to show the results of inspections, and to say whether these had passed, or failed.  But “Pass” or “Fail” wasn’t a value stored in the database; I needed to do some logic to decide for each row.

Rather than writing one query, I wrote two.  One that had logic to select all the “Pass” rows, and one to select all the “Fail” rows.  Then I used the “UNION” clause to join them up.  Much easier.

When complexity is high, and so is repetition, use a Database View.

I’m generally not a big fan of using Database Views in connection with the ARCHIBUS Application.  For those not familiar with database views (as opposed to ARCHIBUS Views, which is just another name for an AXVW file) see this link.  Basically an SQL View is a “virtual table,” a SQL query embedded in the database that queries can be written against.  The problem with Database Views is that you have something outside the AXVW that it is dependent on (the SQL View).  So any time you need to change the data that the AXVW is looking at, you need to change the SQL View.  And if you move the AXVW from environment to another, you have to remember to bring the SQL View along, too.

So when should you use one?  Well, sometimes you’ll find yourself using NEARLY the SAME complex SQL Query in several AXVW files, or the SAME SQL Query multiple times in the SAME AXVW file.  Changes to ALL these queries would be very time-consuming.  So in the long term, it’s simpler to store all this oft-repeated SQL logic in one place.  The SQL View.

Usually, a “.sql” text file containing the “CREATE VIEW” statement is made when you create the view.  To make it easier to maintain the view over the long haul, and to migrate it between environment, it’s a good idea to keep this file around.  If you don’t have a better system, it can be handy to add a comment to the AXVW that says “You need this view, too” and reference the text file used to create it.  And to keep thr .sql script for generating the view close, consider storing it with a name similar to the AXVW view in the same folder where the AXVW file lives on your system.  So if you view is “rsc_wr_update.axvw”, you might store the view-creating SQL script as “rsc_wr_update_vw.sql” in the same folder.


Like what you read? Subscribe to the blog and follow us on Twitter, Facebook, and Linkedin to keep up to date with the latest news from RSC, LLC.
Thoughts? Questions? Comment below and let us know what you think! We’d love to hear your insights.

Making Intelligent Use of ARCHIBUS Database Keys

Hi All,

My name is Todd Forsyth.  I’m the Technical Lead at RSC LLC.  We specialize in installing, hosting and managing ARCHIBUS IWMS systems.  This is one of a series of posts on how to make that process easier if you’re doing something similar yourself.

I started out my technical life not as an ARCHIBUS developer, but as a technology consultant at a major technology consulting firm.  In this role, I both installed packaged applications (including Oracle Applications and Kana Customer Service) and developed web-based applications and data warehouses from scratch.

One of the biggest surprises for me in digging into the ARCHIBUS application is how it uses database keys.  And when I say “keys,” I mean the unique values that identify a record.   Things like the Work Request Code (wr_id) in the Work Requests (wr) table.

I’ll talk about what I found surprising, the pros and cons I find with the ARCHIBUS approach, and give some practical advice on what you need to do to use these database keys intelligently.

First a little background on database keys.  As I said, the key is a single value that uniquely identifies each record.  Things like a Work Request Code, or an Employee ID, or a Room Number in ARCHIBUS.  In ADDITION to identifying records in its primary table, these values are ALSO used to tie a lot of data tables in your database together behind the scenes.  For example, each employee record in the employee table also contains columns for Room Code, Floor Code and Building Code, so you’ll know where the employee sits.

Before joining RSC, all the applications and data warehouses I’d had a deep look at used what are called “surrogate keys.”  That is, the key was always a made-up value, most often an integer number that had no intrinsic information stored in it.   In such a system an employee records might have an employee_id value of ‘291716’.    This number wouldn’t have anything to do with the real employee.  It wouldn’t be their employee number or badge number, and CERTAINLY not their name.  To find those, you’d have to use this number to look them up in the employee table.

By contrast, ARCHIBUS uses what are called “natural keys,” where the keys are meant to contain some information about the record they are the key to.  An employee_id in such a system might be something like “TFORSYTH,” telling us something about the employee’s name.

It turns out that there are at least a couple of different schools of thought about the “right” way to build application databases.  Some say that all primary keys should be surrogate, or arbitrary value, keys.  Others find good reasons to use natural, meaningful data as a key.  Let’s take a closer look at why both groups think they’re right:

The Pros and Cons of Surrogate, or “Arbitrary Value” Keys

This is the world I was used to; the way Oracle Applications, and SAP, and PeopleSoft all handle their databases.  There are strengths to this approach, and challenges:

Pros
  • The key has no intelligence built into it. Meaning you cannot derive any meaning, or relationship between the surrogate key and the rest of the data columns in a row.  If things change in a way which would require you to update the basic information about a record (say you want to re-number all your rooms, or institute a new employee numbering system), this can be done without changing this value in a host of tables.    You simply change the meaningful value in the primary or “home” table where that value lives.  You could just update the room number in the room table, for example.  This sure makes it easier when these values need to be changed.
  • Surrogate keys are usually integers, which only require 4 bytes to store, so the keys, and any database indexes which use them, will be smaller in size than their natural key counterparts.  All a fancy way of saying that big queries with lots of tables run faster with surrogate keys.
 Cons
  • If foreign key tables use surrogate keys then you will be required to have a join to retrieve the real foreign key value.  (Meaning if you store the room id where an employee is seated in the employee table, you ALWAYS have to look up the “real” room number in the room table).  You wouldn’t have to do this with natural keys.  Some meaningful data (like a room number) would already be right there.  If you needed to dig deeper, though, like getting the room name, you’d STILL need to go back to the room table to get it.
  • So surrogate keys are not useful when searching for data, since they have no meaning.  You have to go back to the primary table.

 The Pros and Cons of Natural or “Real Data” Keys

This is the type of key structure ARCHIBUS uses, and all of these strengths and weaknesses are those that ARCHIBUS is subject to:

Pros
  • Since the keys store some useful data, you will usually require less joins/tables when writing a query.  I’ve definitely found this to be true in ARCHBUS.  Often you don’t need to join to the building or employee table; it’s enough that you know the key value stored in the local table you’re looking at.
  • Searches are easier because natural keys have meaning, and you don’t need to do so many joins to get to something meaningful
Cons
  • Much more work is required to change the value of the key.  Changing a Building Code, or “bl_id” value, for example, requires that ARCHIBUS look in over 100 tables where this key might be stored.  The ARCHIBUS applications are smart enough to make this change, but a developer who builds on top of ARCHIBUS must constantly keep this in mind, especially if these keys are being stored in custom tables or fields, of if such value updates happen OUTSIDE of ARCHIBUS logic (which can happen when those key values come in from outside, as through an Employee Sync with an HR system.)
  • Your primary key columns, and any indexes that looks at them will be larger because natural keys are usually strings, which take more space to store than “arbitrary” integers.  Larger key columns and indexes mean queries that take longer to run.  However, since ARCHIBUS databases are typically small in size, this isn’t usually a major concern.  Some tuning may need to be done as the database grows, however.

Using ARCHIBUS Keys Intelligently

Now, while the above has been an interesting exercise in the theoretical, it’s not a choice we really get to make in ARCHIBUS.  ARCHIBUS uses Natural Keys.  That said, this implies a few things you need to keep in mind in setting ARCHIBUS up:

  • Don’t pretend you have Surrogate Keys – I’ve known clients who are absolutely SURE surrogate keys are the way to go, even in ARCHIBUS.  They want to assign ONLY numbers to their building, employee, or department keys (or “Codes”.)  This is counter-productive for a couple of reasons:
    • ARCHIBUS exposes the keys in places many other applications expose name or description fields.  So if you want to have a clue what you’re looking at (who is this employee?  Which building is this?  Is this department Accounting or Legal?), you NEED to give this data some meaning.
    • You will find yourself customizing nearly EVERY form you use regularly to go look up the meaningful data you need from its primary table, where it’s being stored in the Description or Name field. This is a recipe for disaster when doing an upgrade.  Save your customizations for things that really matter.
  • Giving your data some meaning doesn’t mean keys are free-form text fields.  You need to be VERY careful about what you put in here.  You might want to think about exposing your potential key value schemes to these four tests before calling them final:
    • Is the primary key unique?  – My example above of using first initial, last name (TFORSYTH) as a primary key for the employee table is a good example of scheme that DOESN’T pass this test.  Adding the employee number might solve this:  (TFORSYTH F2314)
    • Does it apply to all rows?  – Are there some data points that just doesn’t fit the scheme?  What if you have an employee with a last name like “Wolfeschlegelsteinhausenbergerdorff?”  ‘Probably a bad idea to use the WHOLE last name.  Maybe X characters?
    • Is it minimal?  Remember, big size is one of the problems with natural keys.  Keep your values SHORT.  ARCHIBUS does a good job of enforcing this through their default key field sizes.
    • Is it stable over time?  This one is the real kicker.  Can you GUARANTEE that these values will never change?  Of COURSE you can’t.  But if they change ALL THE TIME, you probably need to look harder for something to use as a key.

I hope you’ve found this look at ARCHIBUS keys useful and informative, and that it can help inform the way you set up and use them in your system.


Like what you read? Subscribe to the blog and follow us on Twitter, Facebook, and Linkedin to keep up to date with the latest news from RSC, LLC.
Thoughts? Questions? Comment below and let us know what you think! We’d love to hear your insights.

Friday Training Follow Up: Types of Reports in ARCHIBUS

Robert Stephen Consulting, LLC provides free 30-minute Client Training session every Friday at 10:00AM PST!  RSC prides itself in providing learning opportunities for our clients.  We feel that if our clients know the system better, we will able to work better with them to discover and implement the solutions that they need.

Last week Bob Stephen, our CEO & Managing Director discussed Reporting in ARCHIBUS. Specifically, we covered the Four Types of Reports in ARCHIUBS.  These reports include:

  1. C & VP Level Reports
  2. Director and Manager Reports
  3. Individual Contributor Reports
  4. Reports for Staff at Large

If you’d like to know more about this particular training, email us at training@rsc2lc.com

We’d love to have you join us for this week’s training on Plain AutoCAD Basics this Friday 11/20.  Please register for the training here:
https://attendee.gototraining.com/r/6239139519237186817

Registering is required to receive a confirmation email and a link to the training.

Our weekly client trainings are held Fridays from 10:00 to 10:30am.  This is an opportunity to learn more about an area of ARCHIBUS that you may not be familiar with.

We look forward to seeing you there!

Like what you read? Subscribe to the blog and follow us on Twitter, Facebook, and Linkedin to keep up to date with the latest news from RSC, LLC.
Thoughts? Questions? Comment below and let us know what you think! We’d love to hear your insights.

Friday Training Follow Up: System Navigation

Robert Stephen Consulting, LLC provides free 30-minute Client Training session every Friday at 10:00AM PST! RSC prides itself in providing learning opportunities for our clients. We feel that if our clients know the system better, we will able to work better with them to discover and implement the solutions that they need.

Last Friday’s training was led by our Tech Lead, Todd.  The topic he covered was System Administration, specifically Page Navigation.  Todd discussed the four basic types of navigation:

  1. Accessibility Navigator
  2. Process Navigator
  3. Dashboard
  4. Page Navigator (Home Pages)

Before taking a deeper look at Page Navigator.  During the in depth overview, he covered:

  • How to use Page Navigator
    • What you can have on your Home Page
    • How to toggle between multiple home pages
    • Working on Tasks
    • The Applications Tab
    • The “My Favorites” Panel
  • How to build a Home Page
    • Adding a Navigation Page
    • Building the xml Descriptor Page
    • Background Shading
  • and  of course some Best Practices

If you’d like to know more about this particular training, email us at training@rsc2lc.com

We are excited to announce this week’s Client Training!  It will be held on Friday 11/13.  Below are some details on registering:

Please register for RSC’s Friday Client Training: Reports, specifically Basic Report Types, on Friday, November 13, 2015 10:00 AM – 10:30 AM PST at:https://attendee.gototraining.com/r/743991509845256705

After registering you will receive a confirmation email containing information about joining the training.>

Can’t wait to see you there!


Like what you read? Subscribe to the blog and follow us on Twitter, Facebook, and Linkedin to keep up to date with the latest news from RSC, LLC.
Thoughts? Questions? Comment below and let us know what you think! We’d love to hear your insights.

Tip of the Month: SpaceView Geography

Ever heard of SpaceView?  It is an amazing tool.

SpaceView is a web based employee locator nestled within the firewall of a corporation.  Its concept is simple: keep the information about employees simple and accessible.  Completely automated SpaceView requires minimal maintenance.  Automated AutoLisp routines create the Drawing Web Format (DWF) files each night.  The employee data information is retrieved through a lie query to the CAFM database.  This simple yet effective web-based tool provides such information as vacancies, upcoming moves, furniture layout, organization ownership, telecommunication assets, and conference room and lab location.

With the addition of redlining capabilities, planners can communicate moves, adds, and changes through the web.  Other components include an online work order system with email notification and web-based move requests.

This week we’re sharing a brief SpaceView Geography training video, brought to you by our CEO & Managing Director Bob Stephen.


Like what you read? Subscribe to the blog and follow us on Twitter, Facebook, and Linkedin to keep up to date with the latest news from RSC, LLC.
Thoughts? Questions? Comment below and let us know what you think! We’d love to hear your insights.

What’s wrong with my AutoCAD file?

AutoCAD used to have a reputation for crashing and corrupting files regularly.  Talk to any long time CAD user and you’ll hear plenty of horror stories.

The program has gotten much more reliable, but it is still very complex, and there are a lot of moving parts, so I am often consulted on drawing problems.

There are a lot of tools for investigating what’s in a drawing.  One of my favorites is the QSELECT command. QSELECT provides a console to create a selection based on various criteria.

Certain objects tend to be problematic:

  • Points
    • Since they don’t print, points can be placed anywhere.  They often throw off the drawing extents.
  • Blocks
    • Blocks are extremely useful, but blocks can also become corrupted.  It is worthwhile to keep track of your blocks and know what blocks are supposed to show up in your drawing.
  • Attributes
    • Attributes are ALWAYS supposed to be contained in a block.  If you have an attribute outside of a block, it should be deleted.
  • Proxy objects
    • Proxy objects are created by add-ons to AutoCAD.  They can become corrupted or they may not render properly in a version of AutoCAD that doesn’t have the add-on.
  • Splines
    • Splines are not always rendered properly.
  • 3D shapes
    • 3D shapes add a lot of extra data to the drawing.  It is an extra burden that can cause a drawing to render slowly.  I prefer to remove them when possible.
  • Empty text
    • Text and Mtext containers without text inside can increase the size of a drawing with no benefits.  Recently the PURGE command was adjusted to deal with empty text objects.

By using filtering abilities in QSELECT you can find, adjust, and potentially delete individual items that cause drawing issues.Like what you read?  Subscribe to the blog and follow us on TwitterFacebook, and Pinterest to keep up to date with the latest news from Robert Stephen Consulting, LLC.

Thoughts? Questions?  Comment below and let us know what you think!  We’d love to hear your insights.

This phenomenal article was brought to you by our very own AutoCAD Wizard Matt R!  Matt is our go to guy for all things AutoCAD.  Matt is always willing to help out no matter what the task or assignment is.  His knowledge and expertise in AutoCAD is one of the many things that makes him an invaluable member here at RSC.


Like what you read? Subscribe to the blog and follow us on Twitter, Facebook, and Linkedin to keep up to date with the latest news from RSC, LLC.
Thoughts? Questions? Comment below and let us know what you think! We’d love to hear your insights.

3 Simple Steps to Improving your Reporting Accuracy

Naturally, reporting accuracy can be difficult because of its complexity;  there are many, tiny pieces to the puzzle of reporting that all need to be correct in order to produce an accurate report. Accuracy can be accomplished by following the three foundational principles below.

1. Have a regularly scheduled employee synchronization with the HR department.

A regularly scheduled employee synchronization with the HR department protects your data.  It assures that all employees are up to date in the system and that employee location and assets are current and tracked accurately.

2. Have a single move process that is followed.

No matter how large or small the move is, if you ensure that one particular move process is followed every single time, without exception, your data is significantly more likely to come out accurate.

3. Walk the floors on a regular basis.

Commit to update your data by walking floors anywhere from once a quarter to once a year.  Whichever time period you decide, keep it consistent!  The more consistent you are, the more accurate your data will be, resulting in more accurate reports.

Consistency 

The key to all these processes is consistency. Once these processes are established and consistent, reporting accuracy will be easier and relatively automatic.


Like what you read? Subscribe to the blog and follow us on Twitter, Facebook, and Linkedin to keep up to date with the latest news from RSC, LLC.
Thoughts? Questions? Comment below and let us know what you think! We’d love to hear your insights.

AutoCAD Advantages: BPOLY Command

Here is a little tip shared by one of our AutoCAD experts, Matt, at Robert Stephen Consulting, LLC.  Enjoy!

Background

The BPOLY command is useful to create a polyline that bounds existing geometry. It is much like the HATCH command or a paintbucket/flood-fill in a paint program.

General Usage

Often lines around a room are determined as LINEs or XLINEs. BPOLY is then used to create the polyline that fills the Remaining Area without any gaps.

After all the rooms have been PLINE’d, BPOLY is used to create circulation and other remaining spaces.

Cautions

We’ve found a little problem with the BPOLY command.  The BPOLY command may skip vertexes when you use it on

  • A fairly large area
  • Containing small vertex offsets

There are two solutions:

  1. Split large areas into smaller ones (particularly large circulation spaces).
  2. Use special care to be certain that vertices align.

How big is this problem?  This appears to happen with distances on the order of 1/100,000.  It could cause your total area to be off by fractions of a percent overall.

The real problem arises when we have to track down a remaining area in a drawing and run across these little glitches.  It is becomes difficult to tell where the actual problem lies.

  • Polylines should be Concave whenever possible
  • BPOLY is view dependent, the entire area to be filled needs to be viewable on the screen before running the command.

A complicated area, like this:

Should be simplified to something like this:

As always, we hope you enjoyed our post.  Please comment below with any thoughts, feedback, or questions.  We love hearing from you!


Like what you read? Subscribe to the blog and follow us on Twitter, Facebook, and Linkedin to keep up to date with the latest news from RSC, LLC.
Thoughts? Questions? Comment below and let us know what you think! We’d love to hear your insights.