Harbinge.rs builds field intelligence products that reduce operational friction.

[email protected]

FAQs

Common questions.

Deployment, Survey Mode, compliance, ServiceNow. Quick answers below.

Support

Frequently Asked Questions

Deployment, compliance, Survey Mode, ServiceNow integration. If you're evaluating Forager, these are the questions that come up most.
  • 1. Do we need to change our building infrastructure or network?
    No. Forager is software. It runs on the Android phones your field techs already carry, with no readers to mount, no access points to reconfigure, and no changes to your network. The only hardware required is the phone. Zero infrastructure changes required.
  • 2. How does Forager record where an asset is?
    The tech picks the room. Forager makes that pick quick and hard to get wrong: it starts from the last confirmed place, and when an asset is new or has moved, it shows a short list of rooms narrowed by floor and by the Wi-Fi and BLE readings the phone sees. Forager never chooses the room for the tech. Every record keeps who confirmed it, when, the room the tech chose, and the Wi-Fi/BLE snapshot from that moment as evidence. If the readings clearly contradict the choice, such as a wrong floor or wing, the tech sees a flag. The radio narrows the list, and the person standing there makes the call.
  • 3. What is Survey Mode and do we need it?
    Survey Mode is an optional setup step. A tech walks each room once and stores a Wi-Fi/BLE snapshot that shortens the pick list for that room. It is recommended, not required: without it, techs pick from the full room list. The Coverage screen shows which rooms have a snapshot, which have a weak one, and which haven't been surveyed yet. Surveys don't expire, but Forager flags rooms that haven't been refreshed in 90 days in case the environment has changed.
  • 4. What happens when an asset is in the wrong location?
    When a tech scans a barcode and the asset's recorded location doesn't match the location on record, the tech sees it and picks the correct room. Forager flags only clear contradictions, such as a wrong floor or wing. The tech can confirm the new location (which updates the CMDB record) or dismiss it if the asset is temporarily out of place. Either way, the event is recorded in the Attestation Log with full details: asset tag, expected location, actual location, tech name, and timestamp. Mismatches are one of Forager's most valuable compliance outputs; they surface CMDB drift that would otherwise go unnoticed until an audit.
  • 5. Is Forager HIPAA compliant?
    Forager is designed for HIPAA-covered environments, and a Business Associate Agreement (BAA) is available for covered entities and business associates. The architecture was built for regulated environments from day one, not retrofitted for compliance after the fact. MAC addresses are hashed before storage so raw device identifiers are never retained. Row-Level Security enforces strict tenant isolation so no user or administrator can access data outside their own organization. No personally identifiable information is collected beyond the asset records your organization explicitly defines. Every confirmation carries a full audit trail: who confirmed it, when, and where. Auditable exports are available on demand for compliance reviews.
  • 6. How quickly can we get started?
    Fast. The IT admin creates the organization, builds the location hierarchy (Site → Building → Floor → Room), uploads floor plan images, and invites field tech accounts. After that, Presence Confirmation is the daily workflow: techs pick the room as they scan, and Forager records who saw what, where, and when. Survey Mode is optional and can be added any time. No hardware purchases, no AP surveys, no network changes required before any of this.
  • 7. How does the ServiceNow integration work?
    CMDB integration is entirely optional; all of Forager's location features work without it. Floor plan visualization, presence confirmation, survey mode, the attestation log, and compliance exports all function independently of any CMDB connection. If you choose to connect, each confirmation a tech makes is sent to ServiceNow or any webhook-capable CMDB. In ServiceNow, Forager updates three fields on the CI record: current location, last verified timestamp, and the name of the tech who confirmed it. Setup uses the Scripted REST API guide in our help center. No middleware required, no batch jobs, no manual entry. The webhook can be toggled off at any time without losing attestation records; confirmations continue to be stored in Forager and you can re-enable delivery whenever you're ready.
  • 8. We run biomedical asset records in Nuvolo. Is that a separate integration?
    No. Nuvolo runs on the ServiceNow platform, so if your biomedical or clinical engineering records already live in Nuvolo, you already have a ServiceNow CMDB. Forager's webhook points at the same ServiceNow instance and updates CI records the same way it does for an IT-only deployment: current location, last verified timestamp, and confirming tech, on whichever table your team maps it to. Expanding from an IT deployment into biomedical is a configuration change (which table and fields to write to), not a new integration to build.
  • 9. What hardware does Forager Mobile require?
    Forager Mobile runs on standard Android devices (Android 10+) with Wi-Fi and Bluetooth enabled, the phones your field techs already carry. No proprietary hardware. Rugged Android and Zebra handhelds work too. Techs need cellular or Wi-Fi data access to sync confirmations, but the app works fully offline and queues records for later sync.
  • 10. Does Forager require a corporate network or company-issued devices?
    No. Forager runs on any Android 10+ device over any internet connection: cellular, home Wi-Fi, or a hospital guest network. There is no VPN requirement, no MDM enrollment, and no corporate network access needed to start. Teams can start on the phones they already have. When your organization is ready to deploy on IT-managed devices, Forager goes through your standard enterprise app approval process like any other Android app; there is nothing unusual about how it is distributed or what network access it requires.
  • 11. What does "zero trust" mean in the context of Forager?
    Zero trust in Forager means protection is enforced at every layer, not just at the perimeter. Device data is hashed before it leaves the mobile app. The cloud backend enforces Row-Level Security so each organization's records are completely isolated, even within shared infrastructure. No data is transmitted in plaintext. Access is governed by role and organization at the database level, not just the application layer. This posture was intentional from day one because our target customers (healthcare providers, financial institutions) operate in environments where a data exposure is a regulatory event, not just a liability.
  • 12. Can techs work offline?
    Yes. Forager Mobile stores confirmations locally and syncs reliably when connectivity is restored. Techs can run full Presence Confirmation sessions in basement equipment rooms, shielded areas, and loading docks without losing any work. The room pick list and checklists work offline too.
  • 13. How fast is a typical asset confirmation?
    Quick. The tech scans the barcode, picks the room from a short list, and the record is written. The Attestation Log updates right away. If a ServiceNow webhook is configured, the CI record is updated as well.
  • 14. What does a typical initial deployment look like?
    Start with one floor or department, or everywhere at once. It is a plain purchase and you deploy it yourself. Field techs run Presence Confirmation as part of normal IT work, and the Attestation Log shows what was confirmed and which mismatches were caught.
  • 15. How do we pull compliance reports?
    The Attestation Log in the app shows the full confirmation history filterable by type (match, mismatch, new asset). The web dashboard Reports page provides date-range exports for auditors; every record shows asset tag, location, tech, timestamp, and confirmation type. Reports can be exported as CSV. The Signal Diagnostic generates a shareable snapshot of the Wi-Fi/BLE environment, attached as evidence to the record.