The Occurrence Number Two Forces Both Recognise
This connector is not prebuilt. It would be built to your requirement on the REST API and ingestion path the platform already uses for records systems, with scope and effort agreed per engagement. Niche RMS is a police records management system built for large forces and multi-agency data sharing, widely deployed across UK, Canadian and Australian policing as well as large US agencies. Multi-agency sharing is the reason it matters here, because the occurrence number is often the only identifier two forces both recognise.
How it connects
Case and occurrence records would come across from Niche over its API, and the occurrence number would arrive as a custom attribute on the media. Attribute mapping is what carries an identifier across a boundary, and it is the mechanism that also lets an occurrence reference survive a transfer to another agency's deployment through a partner relationship. That chain is the point: the reference holds from the originating force's record, through the evidence store, to whoever receives it.
Evidence would file against the occurrence rather than into a folder chosen by whoever uploaded it. A workflow could then read the record to assemble what a disclosure or a case file needs, which in a large force is work measured in days rather than minutes.
Niche would stay the authoritative record. An engagement would settle two things that matter more in a multi-agency setting than in a single one: whose retention schedule governs evidence attached to a shared occurrence, and what happens to the reference when the receiving force renumbers it locally. Both are usually discovered late.
What you can do together
- File evidence against the Niche occurrence number, so the reference is part of the record rather than a convention.
- Keep that reference intact through a transfer to another agency's deployment, which is what makes shared material traceable.
- Assemble a disclosure bundle with a workflow reading the occurrence rather than a person working from a list.
- Check that every item an occurrence cites is present, and find the gaps before a court date does.
A scenario
- ScopingThe engagement would agree which occurrence fields come across, whose retention governs shared material, and how a renumbered reference is handled.
- SetupThe connection would be configured once against the Niche API with the occurrence number mapped to an attribute.
- FilingInterviews and recovered footage ingest and attach to their occurrence, under the library's access control, retention and custody record.
- SharingMaterial transfers to a neighbouring force's deployment through a partner relationship, the occurrence reference carried across by attribute mapping.
- DisclosureA workflow assembles what the file needs and lists cited items that are absent, weeks before the deadline rather than the day of it.
What stays where
Niche remains the authoritative record
Occurrences, reports and case management stay there, and officers work as they do now.
The occurrence reference travels with the evidence
It arrives as an attribute and survives export and transfer between deployments.
Retention across a shared occurrence is a decision
Whose schedule governs is scoped in the engagement, not assumed by either side.
Processing runs where you deploy the platform
Shared or dedicated SaaS, your own cloud, on premises, or air-gapped, with a network path to Niche where it is hosted.
Products and solutions
Next step
See it on your own Niche RMS instance. We will show the connection made, the data moving and the output, then size it for your deployment.
Request a demonstration or write to sales@vidizmo.ai
sales@vidizmo.ai · vidizmo.ai/integrations/catalog/niche-rms