{"id":602,"date":"2007-02-21T01:00:25","date_gmt":"2007-02-21T09:00:25","guid":{"rendered":"https:\/\/systematichr.com\/?p=602"},"modified":"2006-12-29T12:02:25","modified_gmt":"2006-12-29T20:02:25","slug":"adp-on-soa-leading-edge","status":"publish","type":"post","link":"https:\/\/systematichr.com\/?p=602","title":{"rendered":"ADP on SOA Leading Edge?"},"content":{"rendered":"
ADP\u2019s product and vertical mix of multiple products to multiple market segments has always been problematic. Combine this with their philosophy that they can seel everything HR from payroll and benefits administration to portal and background checks to any single client and you have a user interface nightmare looming on the horizon.<\/span><\/p>\n

SOA makes it easier for ADP to create new services and sell them to its base of nearly 500,000 payroll customers and 70,000 time and labor management customers. <\/span><\/p>\n

I\u2019ve always been an advocate that an organization should strive to have a consistent UI (user interface) brought forward to the end user of any application. But the fact of the matter is that you have to have the back end infrastructure available to bring the applications forward on a consistent platform before you can create single instance UI (portal) on the front end. This is where SOA comes into play.<\/span><\/p>\n

ADP’s service-oriented architecture also lets it offer employers services through products sold by other companies. “It allows us to attack verticals that we otherwise couldn’t get at, because we’re partnering with a company that has strong software that’s attractive to that market,” Bongiorno says. For example, ADP sells its payroll services to customers of Microsoft’s small-business accounting software and is talking with ERP vendors about similar partnerships.<\/span><\/p>\n

ADP\u2019s SOA infrastructure consists of 6 pretty normal components as described by InformationWeek:<\/span><\/p>\n