RSGIPI specific Workflow
The process begins with capturing vehicle images via AI Camera encrypted links using mobile device. These encrypted links are generated through an API call by the client. Below is the comprehensive flow.
Workflow
-
Encrypted Link Generation:
The process begins with generating the encrypted links via an API call to our API service.
1.1 Save vehicle details (applicable only for RSGIPI)
1.2 Generate the encrypted link for image capture
POST https://rsgipipp.api.camcom.ai/gen-aicam-url result: https://aicamera.staging.camcom.ai/rsgipipp/JUhZ6N8f3f6yJcPuDnn559JxSbLChfQzPnRUudYwYu7FsxKUHRSxdn1ask5H8WfASrkYf24UCZPw5XRc38g1e9wn6GCumWepUdfNRbkkiMHjoeMNoB4HaYRXB2LfgRbcTT3WJHhmJkpy3WGocJf6WCoxXMei1RL5fLxXZVB83nzjLk1 https://aicamera.staging.camcom.ai/rsgipi2wpp/Z4tBqBW1ZD47dAGu9rYeDo3YoFJph2YRTzWpXAHV6caxuVRCA1dQ7BaFcK3w2WSKVdRkhL4FuA33YMtFB8NXCLMXkDAmWK1QL2fpFzxQ7ftPDRzH2kP6amVjaxRUdkucf4gcS8mt9jdpfyrai34Vttc8D
RSGIC source names: rsgicpp rsgic2wpp rsgic3wpp rsgiccvpp rsgicmiscpp RSGIPI source names: rsgipipp rsgipi2wpp rsgipimiscpp rsgipipcpp rsgipigcpp • is_recapture: Indicates the purpose of the link. • If the value is 0, the link is used to capture inspection images. • If the value is 1 or 2, the link is used to recapture the vehicle using video. • capture_mode: Specifies the image capture mode of the AI camera. • Possible values: auto or manual. • vehicle_type • RSGIC "vehicle_type": 1 - 4 Wheelers "vehicle_type": 2 - 2 Wheelers "vehicle_type": 3 - 3 Wheelers "vehicle_type": 4 - Commercial vehicles "vehicle_type": 5 - Miscellaneous • RSGIPI - Vehicle types and sub types "vehicle_type": 1 - 4 Wheelers "vehicle_type": 2 - 2 Wheelers 'Two Wheeler' "vehicle_type": 5 - Miscellaneous 'JCB' 'Agricultural tractors' 'Rollers' 'Cranes' '4 Wheeler Ambulance' "vehicle_type": 6 - Passenger Carrying 'Four Wheeler - Taxi' 'Three Wheeler' 'Maxi Cab' 'Van' 'Bus' "vehicle_type": 7 - Goods Carrying 'Three Wheeler' 'Light commercial vehicle' 'Heavy commercial vehicle'
-
Image Capture:
The client will send this link to the Agent/Client their communication channels. Then the end user captures the images of the vehicle using their mobile device.
-
Upload to CAAS API:
A background service runs in the AI Camera environment to upload captured images and associated data to the CAAS API once image capture and document upload are complete. The subsequent OTP screen does not affect the image upload process.
-
AI Assessment:
Once the vehicle images are submitted, our CAAS platform performs the AI assessment on the images to identify the damaged part and calculates the health scores.
For inspections that require AI assessment, the ai_assessment field in the
insurance_vehicle
table is set to 1, distinguishing AI-based inspections from passthrough image cases.Note: AI assessment is enabled only for 4-wheeler taxis classified under the “Passenger Carrying” vehicle type. For all other vehicle types in the CV environment, AI assessment is not enabled, and images are passthrough.
-
Callback Service and STP:
The callback service sends the assessment results to the client’s API. In addition, the PI callback service calculates the STP (Straight-Through Processing) based on predefined and agreed-upon rules. Depending on the STP outcome, the inspection is classified into three categories:
• Category A – Auto-approved cases • Category B – Requires manual review • Category C – Requires review by senior-level personnel
-
Link Expiry & Background Service: link_expiry_service
-
Callback: Vehicle Recapture
- Callback: Review Complete - vehicle details, assessment data, a link to PDF - report and STP data
- Callback: link expiry - 10 days, inspection is not received
- Callback: recapture link expiry - 24 hrs, recapture is not complete
Features and services
The features listed below have been implemented specifically to meet RSGIPI requirements
-
User Types: eMotor_SmartUse and VIR Head
-
Review page features:
- View vehicle details
- View STP details
- View OCR readings
- Page Lock
- Part Annotations-V2