API's Updated

For many of you, API's are a term you hear thrown around and rarely understand their true power. That's not your fault. Many times they are never used, barely touched or tapped into, so it's no surprise that when they are updated it may not seem like it matters. But for those that know their capabilities, this update is for you! We have added new API calls (accessible through your account at https://dev.scout.systems), as well as made minor updates to some of the pre-existing GETs. Here's a breakdown of what we've just released...

'Unit Parent Units' GET (!!NEW!!)

Pass through any unitID and you'll be given all of the units it's embedded in (it's parents!). This is a great way to find where changing steps on a unit-in-unit might have a trailing effect on another unit. It's also a great way to understand where edits to say Tools or Materials within one unit might affect a parent unit's build as well.

'Work Order History' GET (!!NEW!!)

Passing through any work order ID will return the sequential 'status' types of the job itself (for instance: 'job started', 'setup', 'build', 'paused', 'schedule break', etc). It will also include their timestamps and which operator did the action. You can use this to drill down more specifically into your operator's actions, and/or can allow you to re-create the Station or Operator Production History reports' charting for yourself.

'Users Applied Hours' GET

We made sure to give you the total SETUP, BUILD, NVA, and APPLIED HOURS across all jobs within the date range specified in the call, specific to the userID you pass through. You can use this to track Operator specific applied hours within our system. Note: this data will only appear for jobs completed within the date range you use in the call.

'Work Order Applied Hours' GET

We give you a breakdown of the SETUP, BUILD, NVA, and APPLIED HOURS for each separate user involved in any work order you search. This allows you to track separate data for jobs with multiple operators who may have touched it.

'Work Order Search' GET

We had been playing around with including the Build/Setup/NVA time results directly into the search for a work order ID, but we found that this was computationally inefficient. So use this call to get your work order ID, and then pass that ID through the 'Work Order' GET or the 'Work Order Applied Hours' GET to grab your time breakdowns.

'Materials' GET (!!NEW!!)

The release of our Material Library a few months back made us realize that a GET for all of your Materials was necessary. Hit this call and we'll return a quick list of your Material Names, Part Numbers and MaterialID's.

'Material Detail' GET (!!NEW!!)

We also realized that you may want to know just where your materials are used throughout all of your work areas. So this call allows you to pass through a MaterialID (see previous note about the Materials GET!!), and get unitIDs where those materials are located. Compare these IDs against your stored list of units (pulled from the 'Units' GET) and you'll be able to find which work area the unit is in and other valuable data you can pass along to your Designers in the event that you need to update materials used.

API's are powerful. You can use them to sync your data from one system to another, or to embed content into your own reporting systems, or simply to catalog data in a spreadsheet for further analysis.

If you or anyone at your facility is in need of API access, please reach out. We're more than happy to get you started!