What explains the lack of effective communication between systems in traditional non-ERP models?

• A. It is the consequence of a fragmented systems design process.
• B. Systems develop quickly.
• C. Systems are constructed on similar and compatible technology platforms.
• D. Systems develop working together.

Answer: (A)

In traditional non-ERP models, systems are often developed and maintained in isolation by different departments. This fragmentation means there’s no consistent approach to data definitions, interfaces, or business processes. When each system uses its own data formats, codes, and rules, exchanging information becomes awkward and error-prone, leading to silos and poor cross-system communication. ERP systems, by contrast, standardize data and interfaces so modules can “talk” to each other smoothly, reducing these gaps.

The other statements don’t explain the problem: developing quickly doesn’t by itself cause poor communication; if systems were built on similar, compatible platforms, communication would typically improve; and systems that develop working together describe the desired outcome, not the cause of the issue.