Availability: Arranged through sales
Every BPS project runs the same arc, and every stage bends to the project. That is the point of a service over a product: the intake matches your source systems, the review depth matches your risk, and the deliverables match the software they land in.
The arc
- Discovery. A call with your stakeholders to map the backlog: document types, where they live, what identifiers they carry, the coordinate context, and what done looks like. Scope and rate are set together here.
- Pilot, when the use case needs proving. A sample of your own documents runs through the pipeline so the results speak before the full engagement is committed. Descriptions outside scope (see Limitations and expectations) surface here, where finding them is cheap.
- Processing. The pipeline runs in parallel across the backlog in batches, tuned to your document formats and regional survey conventions.
- Review. Results route through human review in confidence order, riskiest plots first, in the bulk processing review interface.
- Delivery. Output in the agreed formats with the per-batch processing report. See Deliverables and reporting.
- After. Support, refinement, and, where the project calls for it, custom development: integrations with your systems, dashboards, and reporting built to requirement. Many engagements hand off to the API so the dataset stays current as new documents record.
What makes engagements differ
Document quality, identifier discipline in the source files, how much reference GIS exists, and how custom the deliverable is. Preparing your data covers the parts you control.