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.