Intelligent Document Processing ideal and non ideal project scenarios

Question

I read about IDP how advance and easy to use Appian's IDP for document processing. I am wondering a scenario where Appian's IDP is not an ideal solution to use? Does it have any limitations?

Vinay Katta · Accepted Answer

Few limitations I can think of: 
 
 Appian IDP supports only PDF docs as inputs as of now, if there is any doc of any other type, we might want to convert that manually or use some smart services to convert them ourselves. 
 AI may not be 100 % accurate always, so if it our app is data sensitive/critical, then we should always route it to reconciliation step or manual data fix updates post extraction phase. 
 Process workflow cannot be synchronous, as in we can't expect to view a form or see any immediate results once we submit the document for processing initially, this needs to be later viewed as a task or in a record later post processing of extraction phase which usually takes around 1-2 minutes on an average. 
 Google AI/ML is comparatively better than Appian AI, for data extraction/parsing. I recommend using Google AI/ML for more accuracy/confidence. 
 I believe the ML training is not carry forwarded while we deploy the app to higher environments, and we have to re-train it again from scratch, which adds and extra overhead. Someone please correct me if I'm wrong here.

Intelligent Document Processing ideal and non ideal project scenarios

Top Replies