Rethinking ERP

posted to group
thumbnail Datasheets and White Papers

More details...Hide details...

0 Replies
1 Members participating
 
+0   -0

Tags on this Discussion

Contributors to this discussion

Jason R

0 thums-down icon 0 thums-up icon Like it? You don't like it. You flagged this post. Deleted by a manager. You deleted this post. You like it!

Jason R
3:19pm, September 18, 2007

edit icon

Since 1992, we've seen the impact of new business trends: the blurring of business boundaries, the rise of global workforces, and an increased climate of governance. The labor pool is more diverse, more specialized, more internet savvy, and more focused on information than on manufacturing. And new technologies such as Software-as-a-Service, Web Services, Service-oriented Architecture, and open source are making their way from the consumer Internet into the workplace.

"Query.com is really making a leap on several fronts at once – technologies used, applications architecture, and a complete rethinking of human resource management that's focused on achieving business outcomes."

And yet if you look at the information systems that are in place running today's enterprises (or even some of the "on-demand" offerings from legacy vendors) you're looking back at 1992. Those ERP systems are built on huge code lines and complex relational schemas. You get one shot to change them (at initial implementation) and then the core sets like concrete. So even though business has changed over the past 15 years, business systems haven't - they can't. Current ERP solutions "embrace" change by adding on new functionality around that concrete foundation. The entire enterprise software industry has become focused on providing add-ons to the aging cores of the market leaders.

At Query.com we're taking a different approach. We see the opportunity to use modern technology, on-demand delivery, and a fresh approach to business applications to provide a new system of record that delivers functionality relevant to the way business works today.

Reply

This discussion is closed to replies.