12 results found

1. Division and Department IDs versus Names

   Most organizations use a code for the Division and Department IDs which mean nothing to the Facilities teams or general users. The users typically refer to the organization units by their Names.

   Automatic ID look up functionality that was introduced in ARCHIBUS tries to solve this problem but it only does a partial job at best at this.

   Some critical views where the Automatic ID lookup doesn't work are listed below:
   1. Space Console - Organization section
   2. Space Console Floor Plan Legends
   3. Space Console - Floor Plan labels

   There needs to be a better approach to surface the Department and Division names (amongst others like Building Name, Site Name, Employee Name, etc) on all views instead of only the IDs.

   Most organizations use a code for the Division and Department IDs which mean nothing to the Facilities teams or general users. The users typically refer to the organization units by their Names.

   Automatic ID look up functionality that was introduced in ARCHIBUS tries to solve this problem but it only does a partial job at best at this.

   Some critical views where the Automatic ID lookup doesn't work are listed below:
   1. Space Console - Organization section
   2. Space Console Floor Plan Legends
   3. Space Console - Floor Plan labels

   There needs to be a better approach to surface the… more

   37 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Completed  ·  5 comments  ·  Platform  ·  Delete…  ·  Admin →

2. Drag and Drop Document Attachment

   Please activate the drag and drop file attachment option on all document upload fields. After the drops a file on the Document field, the "Check In New Document" popup could still appear giving the user the chance to add a Description.

   35 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Completed  ·  4 comments  ·  Platform  ·  Delete…  ·  Admin →

3. 508 / WCAG Accessibility Compliance

   As a Federal Government customer I need all of my software to comply with section 508 compliance regulations.

   28 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Completed  ·  3 comments  ·  Platform  ·  Delete…  ·  Admin →

4. Archibus REST APIs

   We would like to develop a set of REST APIs that allow access to key Archibus data and workflow. This idea is meant to get feedback on which data and workflow elements are most important.

   Internal topic on this is: https://serraview.atlassian.net/wiki/spaces/AD/pages/524156999/Platform+REST+APIs. It covers the following priority use cases that we'd like to validate.

   1. Generic get records from a table. As an experienced Archibus system integrator, I would like to have a generic API that allows me access to database table records so that I can respond to customer use cases that are not covered by specific needs. I'd need to specify the table, the fields needed, and a restriction that's applicable to that table. An example is "get all fields in the lease table where the due date is in the next week". Another example is to stream documents into a document management system.

   2. Service Requests managed in Archibus. As an FMer or a systems integrator for the FM customer, I want to allow employees to log service requests in an external system like ServiceNow, and for those requests to route to Archibus to be fulfilled, and I want status changes to be communicated back to the employee, so that I can efficiently utilize two systems together for different purposes.

   3. HR Integration. As an FMer or systems integrator, I want to connect to external system, such as Workday, in order to get accurate and complete employee and organization information into Archibus, so that I can leverage that data for occupancy planning and asset management while maintaining an external system of record. A nightly feed from my HR system is fine. Also, I would like to get out of Archibus the most current employee location assignments, so that I can feel that information back to my HR system. Only seat assignments that have changed since the last time I ran the API should be brought over.

   4. Primary FM tables. As a system integrator, I need to have access to key space data in my FM system so that the data can be used in external systems. Examples include:

        Get building information in my portfolio to aid capital planning
        ESRI in higher ed: Get building information for ESRI/map consumption
          All buildings at once
          All active buildings
          Buildings restricted by site
      

   5. Drawings. As a system integrator, I want to use an external system for wayfinding, service requests, reservations, and other employee-experience uses while keeping Archibus as the system of record for all floor plans, so that I may leverage all of that floor plan data for my employees.

   6. Financials. As a system integrator, I want to get rent and cost transaction details from Archibus so that I can sync them to my financial system, and in that way I can use Archibus for lease-related costs while making sure all financial information is accurate and in one place.

   7. Service Requests managed in an external system. As an FMer or systems integrator, I want to allow employees to log service requests in Archibus, but for some of those requests to transfer to an external system to be fulfilled, and I want status changes to be communicated back to the employee, so that I can use one system for all employee requests and another system to fulfill certain types of requests, such as move and project requests.

        IT tickets go to an IT system
        Move tickets go to the system that box movers use to execute the move
      

   8. Leases. As a user of Serraview for space-planning, I would like to see lease information related to the buildings and floors that I'm working with so that I can use that information in my planning and stacking efforts. Applicable information includes lease areas and end dates.

   We would like to develop a set of REST APIs that allow access to key Archibus data and workflow. This idea is meant to get feedback on which data and workflow elements are most important.

   Internal topic on this is: https://serraview.atlassian.net/wiki/spaces/AD/pages/524156999/Platform+REST+APIs. It covers the following priority use cases that we'd like to validate.

   1. Generic get records from a table. As an experienced Archibus system integrator, I would like to have a generic API that allows me access to database table records so that I can respond to customer use cases that are not covered by specific needs. I'd need… more

   20 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Completed  ·  6 comments  ·  Platform  ·  Delete…  ·  Admin →

5. Enhance reporting and configuration options

   Consider additional configuration options where possible to aid in reporting.

   Consider a re-do of the View Definition Wizard.

   Examples of better configuration include:

   • Choosing fields or attributes to view on reports or panels
   • Defining and using calculated fields
   • Allowing Option fields to be displayed on some views so that they can be used to create personalized reports
   • Store and use more user-defined fields, like those in Asset Management

   Consider these changes for specific views in Foundations as well (buildings, rooms, assets, employees).

   19 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Completed  ·  4 comments  ·  Platform  ·  Delete…  ·  Admin →

6. Fully adopt local time zone support across all Domains/Applications

   While building operations utilizes time zones in the city table to insert the relative time instead of absolute (typically GMT), this support is limited to only Operations. Customers often complain that their times are off by a few hours, or sometimes off by a day, because the times are stored based on server time, and not on the user's location time.
   So for example, a move request entered today might show in the system as being entered tomorrow if the server time is sufficiently ahead of local time.
   As more and more clients are global and utilizing a single instance across multiple time zones, this can become very confusing to sort out.

   While building operations utilizes time zones in the city table to insert the relative time instead of absolute (typically GMT), this support is limited to only Operations. Customers often complain that their times are off by a few hours, or sometimes off by a day, because the times are stored based on server time, and not on the user's location time.
   So for example, a move request entered today might show in the system as being entered tomorrow if the server time is sufficiently ahead of local time.
   As more and more clients are global and utilizing a single instance… more

   17 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Completed  ·  3 comments  ·  Platform  ·  Delete…  ·  Admin →

7. Host UI applications and REST APIs on the same server

   From Jean-Sébastien Clisse js.clisse@aremis.com:

   The main issue [with REST APIs] for us will be the fact that we cannot run the Webcentral and the API at the same time. It always difficult to convince our customers to build/maintain a second webserver. Even if it’s on the same machine because it takes hardware resources (like RAM) and human resource to maintain the server.

   v25.1 requires separate servers: https://serraview.atlassian.net/wiki/spaces/AD/pages/590251436/REST+API+-+System+Integrator+s+Guide#Configure-Web-Central

   12 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Completed  ·  4 comments  ·  Platform  ·  Delete…  ·  Admin →

8. Rest API available in Archibus SaaS

   Archibus Rest API should be accesible with Archibus SaaS in order to be able to integrate it with other systems

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Completed  ·  1 comment  ·  Platform  ·  Delete…  ·  Admin →

9. Dedicated App for Workplace

   Create an improved, dedicated, APP for Archibus Workplace
   * Services
   * Hoteling
   * Reservation

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Completed  ·  2 comments  ·  Platform  ·  Delete…  ·  Admin →

10. In Workplace - Change the tile label "Locate a Person or Room" to reflect its expended functionality

    Currently, Workplace displays the label "Locate a Person or Room", however, the feature functionality is more expansive and allows us to also locate floorplan assets like equipment, or furniture, and Org allocations like departments.

    I suggest changing the 'tile' label to reflect its functionality:

    Name suggestions:
    * Locate a Floorplan Feature
    * Locate a Person, Room or Assets
    * Locate Stuff
    * Find Something
    * Lookout

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Completed  ·  0 comments  ·  Platform  ·  Delete…  ·  Admin →

11. Workplace to be a NATIVE APP

    Make Workplace a NATIVE APP like OnSIte because:
    - Is it the oneApp used by the majority of Employees in a company (to make Service Requests, to reserve workplaces and book meeting rooms) so is the selling point
    - being on so many mobiles is the mouth to mouth marketing and if users are happy & proud will spread the word.
    - security check in big companies will not accept a non-native app without a VPN on-behalf, which will make Workplace expensive and will be eliminated as a solution
    - OnSite is great but is used by a limited number of users compared with the potential of Workplace, so let's "unleash the beast"!

    Make Workplace a NATIVE APP like OnSIte because:
    - Is it the oneApp used by the majority of Employees in a company (to make Service Requests, to reserve workplaces and book meeting rooms) so is the selling point
    - being on so many mobiles is the mouth to mouth marketing and if users are happy & proud will spread the word.
    - security check in big companies will not accept a non-native app without a VPN on-behalf, which will make Workplace expensive and will be eliminated as a solution
    - OnSite is great but is used by a limited number… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Completed  ·  0 comments  ·  Platform  ·  Delete…  ·  Admin →

12. Improve the Cascade Feature - Allow option to only perform cascading updates

    The out of the box Cascade feature is a useful tool but presents a liability for anyone using it due to the Cascade Delete option. If a user deletes a record, they may unintentionally cause other records to be deleted. For this reason, we typically turn the Cascade feature off in our implementations.

    We recommend Archibus add options to only cascade updates and/or cascade deletes. If we can turn off the cascade delete option, the cascade updates feature will make the Archibus system more user friendly and usable -- avoiding errors when someone simply needs to change a Room Category or other background data.

    The out of the box Cascade feature is a useful tool but presents a liability for anyone using it due to the Cascade Delete option. If a user deletes a record, they may unintentionally cause other records to be deleted. For this reason, we typically turn the Cascade feature off in our implementations.

    We recommend Archibus add options to only cascade updates and/or cascade deletes. If we can turn off the cascade delete option, the cascade updates feature will make the Archibus system more user friendly and usable -- avoiding errors when someone simply needs to change a Room Category… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Platform  ·  Delete…  ·  Admin →
    Completed  ·  ying.qin@SpaceIQ.com responded

    Available in 25.4 or later.