No matter what industry you are in, if you have people in the field visiting assets of any description then chances are you have people taking photographs of those assets. Then at the end of their field visit they have to come back to the office and post process all of those photographs.

So lets assume someone has come back to the office with say 300 digital photos named something like "IMG00972.jpg" - the bare minimum that your team must do is to open each and every photograph and identify which photo belongs to each asset. This is typically done by renaming the photograph to something that tells you what it is such as "RADIO_TOWER.jpg", or if you know the ID/TAG number of the asset then "PA-101A-0473.jpg". But with digital photographs so easy to take it is good practice to take multiple photographs of an asset whilst you have someone in front of the asset. In this case it would be common to add a counter to the name - such as "RADIO_TOWER-001.jpg", "RADIO_TOWER-002.jpg", etc.

The above is the bare minimum that typically happens and doesn't take into account the possible following requirements :

  • Digital cameras routinely take photographs greater than 5MB and if we are taking 300 photos a day and transmitting that over a network of some sort then we can be looking at 1.5GB of data to transmit per day. When dealing with asset photos there is no real measurable loss in detail between a 1.5MB photo and a 5MB photo - just an extra 1GB in data storage and transmittal. To deal with this you may way to scale photos to allow you to more effectively transmit and store them.
  • If you have teams of people generating hundreds of photos a day you are probably looking at some sort of a file management system to ensure that you can retrieve the photos that you want and provide more data integrity than a large file share that is accessible by everyone (allowing anyone to edit / rename / delete photos).
  • Classify the content of the photographs so that you can more quickly retrieve the the photos that you are looking for rather than having to open each and every photo for a particular asset.

To show organizations what they are spending today doing this bare minimum of asset photo cataloguing we have put together the following calculator to show you how much you are likely losing when your people come back into the office and have to start post processing photos. Underneath the calculator we have descriptions of each of the input and output fields.


ORDITAL Photo Cataloguing Calculator
ORDITAL Photo Cataloguing Calculator Input

Fully loaded man hour rate :

Assets per day per person :

Photographs per asset :

Tme to catalogue a photograph :

Number of auditors on project :

Working days per project :

Number of hours per shift :

Average photograph size :

ORDITAL Photo Cataloguing Calculator Output






  • Currency - sets the display for costs and rates
  • Fully Loaded Man Hour Rate - this is the cost per hour to your organization of the person doing the post processing. This rate is fully loaded with salary, travel and other overheads to represent the full cost to the organization of that person carrying out that activity.
  • Assets per day per person - the average number of assets that are typically photographed in a day by a single person. A typical working number for this might be 100 Assets/day.
  • Photographs per asset - the average number of photographs that are taken per asset. We typically recommend that a minimum of 4 photographs is best to ensure that the investment to visit the asset is preserved - 1 TAG, 1 EQUIPMENT, 2 NAME PLATE photos.
  • Time to catalogue a photograph - the average time taken to download a photograph to a computer, open and review the photograph, identify which asset the photograph belongs to, rename the photograph - and if required to scale and upload to a management system. We typically use a 30 second estimate to represent and average / sustained time to catalogue a photograph.
  • Number of auditors on project - the number of people in the field auditing assets
  • Working days per project - the number of days you estimate that the auditors will be active on the current  project
  • Number of hours per shift - the number of hours per day that the auditors are working
  • Average photograph size - an iPhone typically generates 2.5MB photos, a Samsung Galaxy S6 generates 5MB photos. ORDITAL customers typically scale photos back to 1.5MB.


  • Time lost per day - the total number of hours per day for all of your auditors required to post-process photographs in the office.
  • Cost of lost time per day - the total cost per day to your company to post-process photographs in the office.
  • Time lost per project - the total number of man days per project for all of your auditors required to post-process photographs in the office.
  • Cost of lost time per project - the total cost for the project to your company to post-process photographs in the office.
  • Cost to visit single asset - by far the biggest cost component on any audit project is the cost to physically get someone to stand in front of an asset. To maximize the return on investment for this activity you should ALWAYS get that person to photograph the asset, and they should ALWAYS take multiple photos of the asset to ensure that this investment is not squandered through unclear or inadequate images.
  • Assets audited per project - how many assets you would expect to audit for this project
  • Expected data archive size - the total amount of storage space required to hold all of the photos from this project.



ORDITAL provides a mobile app that can be downloaded from the Apple App Store or the Google Play Store, to classify and catalogue asset photographs at the time of capture. The ORDITAL mobile app removes the need for the typical post processing outlined above which results in significant savings to your organization.