One of the issues that has come up relates to downtime within Amazon Web Services, including the 2 most popular services, Elastic Cloud Compute (EC2) and Simple Storage Services (S3). I have been able to spend some time talking to customers of these services. What I found is that the impact of this downtime varied widely with customers based on their own proactive decisions as to how they were going to use these services.
Our premise at CSA is cloud computing is sure to be the dominant foundation of information systems in the future. We believe that today, in the aggregate, cloud computing is a more efficient, reliable, economical and – yes, more secure alternative to traditional IT options. One of our newest initiatives is CSA STAR (Security, Trust and Assurance Registry). The purpose of this registry is to provide a repository for cloud providers to post information about their security practices that can be scrutinized publicly.
B2B and application integration requirements need to be addressed when migrating “upstream” to a more functional cloud ERP solution. Matching a cloud-based integration solution to the ERP platform makes sense both technically and financially. The challenge will be to find the right combination of cloud providers that meet both the ERP and integration requirements – and work well together.
Automating eBusiness related business processes such as Procure-to-Pay or Order-to-Cash may be one of the reasons to implement a new cloud based ERP solution. So understanding connectivity options will better position you for success during the implementation project. B2B connectivity can mean a lot of things, but I want to focus my analysis on three main crticial areas.
Addressing these new opportunities during the initial requirements stages of an ERP migration project will smooth the overall transition. Integration requirements are inherently technical; but they need to matched to business drivers (such as integration with new line of business applications, new marketplaces, new work flow procedures, etc). Once the business drivers are identified, justifying new B2B integration software will make sense.
A new blog series by application architecture and integration expert, Professor Mike Canniff A typical ERP migration scenario I am seeing is by Small to Medium Enterprises (SME) currently using legacy accounting or SMB systems, such as QuickBooks or Peachtree applications, but need additional functionality and want to “move up the stack”. They may have [...]
As companies on both the buy and sell side of the market struggle to increase margin, our supply chain becomes more complex, the information being exchanged potentially more sensitive, and the networks carrying the data more risk intensive. Two primary liabilities must be managed: continuity and privacy, both of which impact your data security. It goes without saying that the Value Added Network of yesterday can be replaced with a more relevant and current solution provider who can answer today’s business challenges.
One of the top reasons people complain about VANs is the cost. People don’t want to pay the fees, and it’s not hard to understand why. This becomes especially true as hub initiatives (Grocery, Retail or otherwise) start looking at smaller and smaller suppliers. Initially, the cost to send/receive EDI data was hugely expensive per document. Those costs have decreased; however, in the face of continual technical advances, I still consider VANs to be extremely expensive in relation to what you receive.
