Why Choose CG4
CG4 is certified by ServiceNow and has been since the 2014 Dublin release and will remain certified and current with all new releases.
We have customers of all sizes, some tracking up to a million assets and down to a few hundred assets.
We have customers from all Industries: retail, medical, education, government, military, financial, manufacturing, energy, media, communication and many more!
We offer a no-cost Proof of Concept/Trial.
Short Implementation Timeline.
Asset Tracking Features
Configure an unlimited number of CG4 modules to match steps in your asset lifecycle.
Barcode and RFID
Wide variety of scanning devices.
Native, hosted and local deployment options.
Online and offline capabilities.
CG4 + SERVICENOW
BEYOND ASSET TRACKING
Even though CG4 is known for asset tracking, we have released a new version of the CG4 app that includes features that will potentially help in many areas of your ServiceNow implementation, not just asset tracking. Here is a brief introduction to the four new features!
CG4 Record History
Stores history of every single insert, update, and deletion performed against all records on the target table, including the details of every single field value associated with those actions.
This history is kept no matter where the insert, update, or deletion came from--CG4 or any other source, including actions made directly in ServiceNow. This history is completely reportable--over time, by user, by record, etc. This history also gives you the ability to pick any point in time and view all of the field values as they were at any point in time in the past--as long as the time is after the time when the history-tracking functionality was enabled for the target table.
In CG4 Remediation, you have the ability to halt any transaction you want to from happening, requiring that those transactions get approved by designated users before allowing those actions to actually happen on the target table/record.
You can halt any insert, update, or delete transactions being attempted against the target table that you want, based on the transactions matching conditions that you specify ahead of time.
For instance, before any asset gets created in Location A, I want to be able to approve whether or not each asset actually gets created. If I approve the transaction, the record gets created; if I reject the transaction, the asset record is not created.
You can set up similar rules to halt and review any updates or deletions that are being attempted against records on the target table.
CG4 Data Restoration
In CG4 Data Restoration, you have the complete ability to restore your data (the entire table, or just subsets of data) back to any point in time in the past (as long as that time is after the history-tracking functionality was enabled for the target table).
If data gets deleted, you can restore it. If data doesn't get deleted but gets messed up, you can restore it back to the true values as they were before the corruption happened.
If you know the exact time window when the error happened, you have the ability to:
(1) restore all values to what they were before the error time window happened, yet
(2) retain any changes that were made to records after the error time window happened.
The end result is that the errors will be removed from your data without necessarily having to lose all useful data that has been accrued since the error happened.
In CG4 Audit, you can specify any conditions you want--not necessarily only location based--to generate a list of all records that you are expected to find as a part of your audit, and then your CG4 scans will be compared against that list of expected records to determine which records are compliant, missing, overages, etc.
The evaluations of which records are expected as a part of the audit vs. which records are found during the audit are determined using real-time ServiceNow data, instead of using lists of expected records that are “pulled” or snapshotted at the start of the audit, meaning that:
(1) there won’t be any inaccuracies in audit results that happen because you are comparing scans against old data (even a data lag of one to two days since the start of your audit could introduce false problems into your audit results), and
(2) any ServiceNow users interacting with records on the target table do not need to halt their normal interactions with records in order to keep them from skewing audit results.
There is also the ability to have the same audit performed by more than one team and compare the results...we can get to whatever level of detail you would like!
All the above features can be enabled on any ServiceNow table or custom table; you can use these features in a variety of areas in your ServiceNow implementation.