The Owner
J B Holeman is the President and owner of Oversight-Inc. Oversight-Inc developed a suite of Checker Services and GuardChecker is the original Service. Oversight is located in Greenville, SC, and we are an active member of ASIS International.
After graduating from West Point, J B spent a career in the US Army commanding troops and procuring major weapon systems. After retiring as a full colonel, he spent 10 years as a C level executive in both large engineering and construction companies. After many years working for large organizations, he was eager to build his own business and work for himself. J B invests in startup companies; helped found the local angel investment group, UCAN; and started Oversight Inc., where he works on a daily basis. See his LinkedIn page.
How We Started
The concept of Oversight started in 2004 when JB was the President of a small security company. The local Lockheed Martin facility was already a customer and we were trying to win a new job securing the final construction phases of a new nine story Marriot Hotel. The site was on the edge a questionable side of town. As a result, the client wanted to prevent the loss any of the new furnishings being installed in the rooms, ballrooms, and administrative offices.
The client wanted objective confirmation that all the areas were being checked and the frequency of the checks. Eventually Oversight developed their own, much improved guard monitoring service, called GuardChecker.
As we were marketing that new service to a major Contract Management Agency in New York City, they asked if we had a “real time” service that could them if one of the guards they had contracted for, did not report for duty as contractually required.
Unfortunately, we did not offer that capability but we agreed to find one and add it to our Service. To our surprise, we could not find a single company in the United States or the rest of the world that offered such a service. There was a ton of software on the market that would respond AFTER someone initiated a phone call, but nothing existed that would alert a client if someone did not place a call, make computer entry, or initiate some action.
As a result we developed NoShowChecker. The good news was that it fit very nicely into the entry form protocol we had already established for the other Checkers.
Now, we can easily satisfy that contract management agency’s requirement and send them a “real time” alert them when a NoShow occurs and before the client calls asking embarrassing questions.