Documents » covere later.
Abstract: Businesses wary of larger initial upfront investments can start with an easily affordable subscription at ACCPACcrm.com and have the knowledge that any investments in their data, customizations, and training are fully protected should they
later need or want to move their solution on-premises.
PubDate: 6/3/2004
Abstract: This article describes the author's experience with the development of the first Yugoslav Internet payment processing system. The system's architecture is very similar to the Three Domain (3D) model that started to emerge later. This success story is worthwhile sharing with a wider audience.
Abstract: Red Hat announces the availability of the source code for IA-64 platforms, the first of which will be Intel’s “Itanium” processor, due later this year.
Abstract: ERP first developed as a form of inventory control and later grew to link disparate bodies of information together from across the enterprise. Now, ERP enhancements include SCM, CRM, and e-commerce features, just to name a few. However, where is this technology going? What does it mean now?
Abstract: Source code for a future Microsoft OS, code-named “Whistler”, mysteriously appeared on the Internet in mid-March. How did it get there? Does it matter? And why does Microsoft management keep making statements that are later retracted?
Abstract: After insisting the perpetrator of the February Distributed Denial of Service attacks would be caught and punished, a month later, the Department of Justice, and Janet Reno, are keeping a low profile on the antics of an altogether different, but in many ways more serious, cyber attack. Take Remote Data Service precautions today. Here's how.
Abstract: Vendors' traditional pricing strategies aren't going to work much longer. Sooner or later, prices will be determined by what the market is ready to bear rather than be based on what vendors think is a profitable way to deliver solutions.
Abstract: Be Inc. will offer the newest version of its operating system for free later this quarter. Version 5 for the desktop will be available for download to pre-registered individuals.
Abstract: In 1981, Eric Allman developed sendmail to route messages between disparate mail systems. Two years later, in 1983, sendmail version 4.2 was shipping with 18 different vendor UNIX systems.
Abstract: System planning is the Achilles’ heel of a data center physical infrastructure project. Planning mistakes can propagate through later deployment phases, resulting in delays, cost overruns, wasted time, and a compromised system. These troubles can be eliminated by viewing system planning as a data flow model, with sequenced tasks that progressively transform and refine data from initial concept to final design. Learn more.
Abstract: Here's an all-too typical scenario. Management at a multinational company decides to implement a standardized enterprise resource planning (ERP) solution. Everyone expects to cut costs and improve core end-to-end processes. But 13 months later, vital key performance indicators (KPIs) don’t improve as planned. Discover how a company focused on user performance to bring its ERP reality back into alignment with its vision.
Abstract: The 802.11n standard promises to extend today’s most popular wireless local area network (WLAN) standard by increasing reach, reliability, and throughput. The final standard, predicted to be ratified later this year, is expected to trigger broad-scale deployment of bigger and faster networks. Find out about the essential new technologies used by 802.11n, and their impact on network planning, installation, and operation.
Abstract: Effective CRM deployment can bring many productivity gains. And although free customer relationship management (CRM) tools may sound great to overburdened company directors, there are five reasons why free CRM tools should be avoided. For one, free isn’t always free, as hidden costs can undermine your budget. Find out about the other reasons why it’s better to tighten your CRM budget now, rather than go bust later.
Abstract: To promote fast growth, small businesses often sacrifice process control for creativity. But sooner or later, unstructured creativity compounded by fast growth leads to the inability to make fact-based business decisions. Learn about four steps to developing a business strategy that can help you run your business more effectively by applying better control over your cost structure, minimizing risk, and anticipating change.
Abstract: Deploying and migrating JaveEE applications is hard work, the kind that is error-prone, repetitive, and time-consuming, resulting in lost man-hours, soaring costs, and potential configuration issues that are bound to pop up later. In response to this complex environment, Phurnace Software has created a software application that accelerates the deployment of JavaEE applications and helps to minimize errors.
Abstract: What does Visibility’s .NET enterprise resource planning (ERP) solution have that others don’t? .NET technology. And because it contains no legacy code, it provides a system that’s accessible using a web-browser and has a user interface equal in functionality to a client-server application. In fact, any client PC with Internet Explorer 5.5 or later can operate it—without compromising the quality of the user experience.
Abstract: Qualitel couldn’t keep up with the growing demand for its electronics. With revenues increasing 30 to 40 percent per year, its order entry and accounting systems were rapidly becoming obsolete. Qualitel needed a solution—and fast. Just one year later, after selecting and implementing an enterprise resource planning (ERP) system, Qualitel’s revenue exploded 471 percent to $12.89 million (USD).
Abstract: The later in the system development life cycle (SDLC) major errors are discovered, the more expensive it is to fix them. In fact, errors in released software are up to 80 times more expensive to fix than defects in the specification stage. That’s why you should adopt a methodology that brings the early stages of the SDLC up to a high level of maturity, in a way that’s consistent, proven, and optimized for success.
Abstract: The frequency of breakdowns in the IT client relationship is reaching epidemic proportions. Indeed, an IT client breakdown is comparable to the onset of an illness. If caught early enough, treatment is often relatively painless. However, if left to advance to the later stages, or full maturity, the treatment will not only be invasive, but also require significant recovery time.