& cplSiteName &
Comments
Newest First  |  Oldest First  |  Threaded View        ADD A COMMENT
Page 1 / 2   >   >>
kq4ym
kq4ym
11/16/2017 | 10:48:09 AM
Re: Trexit
Getting over the stumbling block when it's a "big fight to convince the operations organization that the engine works and they can trust it," will probably be easier said than done until folks have enough experience to trust the results of AI, natural speech recognition and other new tech, so that the machines "earn their trust."
mendyk
mendyk
11/3/2017 | 2:18:50 PM
Re: Trexit
Agreed -- the work has to start somewhere. And at the root of that somewhere there needs to be a plan to get from the current mess to an optimal end result. As they say in sportsball world these days, trust the process. But to do that, you need a process to trust.
brooks7
brooks7
11/3/2017 | 2:14:29 PM
Re: Trexit
Dennis,

Definitely the fight should not be given up, I just think that you have to assume that it will not improve to start.  You can improve it even with humans involved.  Having forms that have data limits checkers and such can be of great value.  But I think for a really, really long time there will be error and the need for human intervention.

The best part is that the cleanup can be automated over time as well, or at least 80% of it.  If people run into situations on an ongoing basis that have a fix, they can build a cleanup task that runs periodically.  This can first report errors and then potentially automate the fixes for them.  Those kind of tools are what I have always called "1 Button Bobs".  One of the challenges is that SPs often spend little time in creating their own toolsets for this.  One way to justify it is to evaluate how much time is spent on cleaning up issues and then justifying the tool by the time reduction.  As a side benefit, service uptime and customer satisfaction are improved as well.

seven

 

 

 
Duh!
Duh!
11/3/2017 | 1:52:58 PM
Re: Trexit
"[R]etrospectively cleaning up what is often a large amount of data entered over a very signifcant amount of time" is a huge problem for incumbents' copper networks. Some of the cables, cross boxes, and terminals out there pre-date business data processing (arch.).  The condition of those database records is downright scary.
mendyk
mendyk
11/3/2017 | 1:33:27 PM
Re: Trexit
The point is that process improvement is critical to any automation efforts. I don't think that surrendering the fight because it's a really hard one is the best option, and in fact it may be the worst one. As it is now, I've had a DirecTV account for more than 10 years now. My name on the account is spelled incorrectly. None of the humans I've contacted about this issue were able to correct it. So anecdotally, how much worse could a machine be than a complete fail?
brooks7
brooks7
11/3/2017 | 12:28:14 PM
Re: Trexit
Dennis,

 

All software is bug free and anticipates every situation.  So, the moment that AI figures out what should be made, how the business model will be executed, collect all possible data associated with it, process all data, never have any bugs, have no network or hardware failures...then it will be error free.

<Less Snark>  A lot of the issues deal with situations that are not completely planned for.  That makes a data model that requires support.  Think of it this way:  Imagine a Customer Database....now add in resellers and distributors....now have some of them go out of business or get bought by other resellers.  Who manages the commission checks?

seven

 

 
mendyk
mendyk
11/3/2017 | 9:47:26 AM
Re: Trexit
It sounds like humans are responsible for the poor data quality, and humans are the only answer to dealing with that problem. But if data entry processes were more automated, wouldn't that go a long way to mitigating the "garbage in" problem? The garbage has to be dealt with at some point. It makes sense to do it in a way that aligns with automation plans.
GypsumFantastic
GypsumFantastic
11/3/2017 | 7:19:33 AM
Re: Trexit
Including removing duplicate data :-D :-)
fahim
fahim
11/3/2017 | 6:54:50 AM
Re: Trexit
RPA is very sensitive to the smallest of differences in data unless it has been specifically built to handle every variant.  A human being can usally tell that "LON:1234,567" is "LON-1234-567" entered incorrectly.  Automation becomes horribly complex if you need to support every possible way that information has been manually entered and it's a war you never win because you are constantly discovering new ones (which you usually only find out about because an automation fails and a customer interaction has been sub-par).

The remedy to this is to ensure operational organisation understands that when the operational guide says enter the information as "XXX-NNNN-NNN" you need to religiously do that, and not some variant that may be obvious to any human eyes looking at it.  Helping them understand that RPA is very mechanical and requires consistency is really challenging, because you are asking people to break habits that they have built up over a number years (the 'but I've always done it like this' conversation).  This conversation becomes exponentially more difficult if you have to take local practices, especially those that are inorganically integrated, and align them.

There are two aspects here: retrospectively cleaning up what is often a large amount of data entered over a very signifcant amount of time, as well as constant governance that data quality standards remain very high for anything new that is enetered.  AI/ML and Big Data tools may be able to help with this but you don't get them for free, and avoiding 'garbage in' in the first place is usually a better strategy.

 

Fahim Sabir

 

 
Carol Wilson
Carol Wilson
11/3/2017 | 12:37:58 AM
Re: Trexit
Agreed, it is an ongoing process to keep databases accurate. 
Page 1 / 2   >   >>


Featured Video
Upcoming Live Events
October 22, 2019, Los Angeles, CA
November 5, 2019, London, England
November 7, 2019, London, UK
November 14, 2019, Maritim Hotel, Berlin
December 3-5, 2019, Vienna, Austria
December 3, 2019, New York, New York
March 16-18, 2020, Embassy Suites, Denver, Colorado
May 18-20, 2020, Irving Convention Center, Dallas, TX
All Upcoming Live Events