| Papers [1-15] of 100 :: [Page 1 of 7] | | Go to page : 1 2 3 4 5 6 7 —> | Search results on "ENTERPRISE ARCHITECTURE PLANNING": |
|
|
Enterprise Architecture Planning, 2002.
This paper is a case study that uses the principles of Enterprise Architecture Planning (EAP) to correct a data warehousing IS (Information Systems) solution selection problem.
1,815 words (approx. 7.3 pages), 4 sources, $ 58.95
»
Click here to show/hide summary
Abstract
This paper describes the four stages of Enterprise Architecture Planning: Developing a framework for the plan, performing initial migration, performing major application migration and the post-migration stage. The author believes that while executive support is critical for an enterprise-wide project, it also is important that the users understand the benefit of the system and have input into its design. The paper states that using EAP means the company starts by defining the action, technology and transition programs needed well before a budget or timeline is established and the project itself is defined.
Table of Contents
Introduction
Background
Analysis of Previous Data Warehousing Experience
Recommendations for Future Data Warehousing Project
Conclusion
From the Paper
"User education can be critical to the success of EAP, and requires that the company not just seek information from users (as SPFIS did), but also "sell" users on the benefits of the new architecture (which SPFIS did not). The users expected a system which provided them with the same information they had previously, including the same type of reports (not taking into account that their reports were previously generated by individual users). Instead of working with the users to explain how the new reporting system would meet their needs, albeit in a somewhat different form, the users were expected to embrace the new system simply because the CEO wanted it to be so. With earlier "buy-in" by the users, the system could have been better designed to meet their needs and would have had a better chance of providing the maximum benefit to the organization."
| |
|
Enterprise Architecture Planning (EAP), 2002.
The application of enterprise architecture planning (EAP) to determine why the implementation of a data warehousing project failed.
1,818 words (approx. 7.3 pages), 4 sources, MLA, $ 58.95
»
Click here to show/hide summary
Abstract
This paper uses the principles of enterprise architecture planning (EAP), to analyze what went wrong in the application of a data warehousing system for the company SPFIS and detemines what recommendations can be made regarding future projects. It examines how the initial system was implemented through a whim of the CEO lacking clear definition and identifiable milestones. It looks at the four stages of EAP, developing a framework for the plan, performing initial migration, performing major application migration and the post-migration stage and uses them to analyses SPFIS's shortcomings.
From the Paper
"In many cases, significant IS programs lack an executive sponsor and the IS staff struggles to gain support for their project at the highest levels of the organization. This was not the case at SPFIS. Indeed, there was considerable support for the data warehousing project from the CEO, but the CEO failed to appreciate exactly what a data warehouse could and could not do for his organization. This "blind" approach to implementing a data warehouse imposed unrealistic deadlines and resource limits on the IS staff, and ensured that users would not be part of the solution (users were left believing that the data warehouse would be forced on them even though they did not understand its benefits)."
| |
|
Enterprise Architecture, 2002.
A description of enterprise architecture.
3,400 words (approx. 13.6 pages), 6 sources, $ 124.95
»
Click here to show/hide summary
Abstract
This paper describes enterprise architecture as a framework for the system organization.
| |
|
Enterprise Resource Planning (ERP), 2002.
An examination of two companies which supply Enterprise Resource Planning software solutions.
2,647 words (approx. 10.6 pages), 12 sources, MLA, $ 79.95
»
Click here to show/hide summary
Abstract
Enterprise Resource Planning software solutions are software solutions that provide a common, consistent system to capture data organization-wide, to integrate information across corporate functions and to provide tools for planning and monitoring the various functions and processes towards a common purpose. This paper examines the strengths, weaknesses and services of two companies that offer ERP software solutions - PeopleSoft and SAP. The paper shows that SAP is appropriate for larger companies with the resources to support the infrastructure and implementation of a mammoth, all-comprising system, while PeopleSoft is a lower-cost, less demand-intensive alternative.
From the Paper
"PeopleSoft began in the enterprise operations software business by designing software for human-resources executives. They won their customers over with their friendly, customer-focused style. Once the firm was established within their clients? Human Resource departments, it began to offer software for other departments, starting with Finance. This approach worked for them quickly: revenues were only $33 million in 1992, but have risen to about $1.4 billion since then."
| |
|
The Enterprise Resource Planning (ERP) System.
This paper discusses the implementation of an enterprise resource planning (ERP) system, a multi-module application software that helps a business manage the important parts of its business.
1,400 words (approx. 5.6 pages), 2 sources, APA, $ 46.95
»
Click here to show/hide summary
Abstract
This paper explains that the multi-module application software, which form an enterprise resource planning (ERP) system helps a business manage product planning, parts purchasing, maintaining inventories, interacting with suppliers, providing customer service, tracking orders, manage finance and human resources, provide supply chain management, customer relationship management and electronic commerce applications integrated with their ERP software packages. The author points out that the major benefit of ERP systems is the elimination of manual processes that cause operational inefficiencies and poor data quality. The paper relates that the ERP market is characterized by massive consolidation with relatively commoditized software, meaning that software evaluations can safely include a short list of the three leaders, SAP, Oracle and PeopleSoft, and perhaps a vertically focused supplier or a SME specialist such as Microsoft.
Table of Contents
Introduction
The Benefits of ERP
The Pitfalls of ERP
ERP Evaluation Criteria
Top Three ERP Vendors
Conclusion
From the Paper
"The ERP vision of one application and one database for everything your company is doable, there are many factors that must be considered before embarking on such a tremendous undertaking. First, ERP systems are extremely expensive and time consuming. AMR, a leading research and advisory firm, advises that moving to a single instance will cost companies $7 million to $12 million for every billion of revenue, and that projects will still take from one to three years. Even after the initial implementation, ERP's are very complex and typically require costly experts to support and maintain."
| |
|
An Enterprise Resource Planning Process, 2005.
A dissertation on an enterprise resource planning process designed for the Maxim Auto Supply.
5,759 words (approx. 23.0 pages), 18 sources, MLA, $ 138.95
»
Click here to show/hide summary
Abstract
This paper details the design, development, integration and implementation of an enterprise resource planning process for the Maxim Auto Supply Company, a subsidiary of the Midnight Auto Supply Company. Included at the beginning of the paper is the proposal for the dissertation which is then followed by the actual dissertation. The dissertation focuses, specifically, on Midnight Auto Supply and their efforts to become an upgraded subsidiary with a new state of the art computer system that is supposed to efficiently contain and manage such business processes as accounting, sales, marketing, email and b2b communications, as well as all aspects of customer and vendor management, employee database management and payroll and fraud management.
Executive Summary
Framework
Overview of Organization
Transformation Framework
Areas for Improvement
Analysis of How this will Happen
Resources and Timescales
Conclusions
From the Paper
"In our ever increasingly competitive, technologically advanced global economic environment, all business entities search for those ideal processes that can strategically reduce operational costs and increase profits. There has also been an increasing amount of pressure on all the organizations throughout the UK and the world. This pressure has come from the likes of shareholders, consumers and stakeholders that demand that business entities design and mange all aspects of their business processes, including information systems, in as efficient a manner as possible. "
| |
|
Enterprise Resource Planning (ERP) Initiative, 2001.
An examination of resource planning systems and their effects on organizational management.
4,060 words (approx. 16.2 pages), 18 sources, $ 109.95
»
Click here to show/hide summary
Abstract
This paper discusses proposed research toward developing guidelines for implementation of resource planning systems and quantification of results.
From the Paper
"Internet technologies and applications have grown more rapidly than anyone could have envisioned, even as recently as five years ago. They have opened up new means and frontiers of communication, collaboration and coordination between customers, businesses and trading partners.At its most basic, ?electronic commerce? or ?e-commerce? refers to electronic shopping, doing business online or buying products and services through Web storefronts. The terms have evolved to include to all aspects of business and market processes facilitated by the Internet and the World Wide Web."
| |
|
Enterprise Resource Planning, 2006.
A review of the article 'A Second Wind for ERP' by James and Wolf.
675 words (approx. 2.7 pages), 2 sources, $ 26.95
»
Click here to show/hide summary
Abstract
This document discusses an article about enterprise resource planning (ERPs) applications that are used by larger enterprises to integrate the spectrum of their operations within the context of one system. The paper reviews various ERP applications and their attributes, and the belief that continued use and improvement of ERP applications is important as an expanding trend.
From the Paper
"In an article entitled 'A Second Wind for ERP', authors James and Wolf (2000) discuss ERP systems which are essentially a group of software applications that are designed to handle different functional areas within an organization: finance, AR/AP, HR, logistics planning, inventory, marketing, customer service to name a few. While it could be argued this in itself is not novel and to an extent the idea of a software program designed to enhance the functional processes of a department isn't revolutionary, ERP systems are considered the holy grail of organizational effectiveness because of their integrative potential across departments. James and Wolf believe that ERP systems are so coveted because while they both simplify and complicate business processes they remain effective through their useful life cycle (2000, paras.3-6). "
| |
|
Gothic Architecture and Renaissance Architecture, 2005.
A comparative analysis of Gothic and Renaissance architecture.
675 words (approx. 2.7 pages), 3 sources, $ 26.95
»
Click here to show/hide summary
Abstract
This paper compares Gothic architecture and Renaissance architecture, showing the change that came over architecture with the shift from the more massive and decorated style of the Gothic to the cleaner classical lines of the Renaissance, a period which also borrowed from the Moslem style to make new use of the dome, as in religious buildings by Brunelleschi.
From the Paper
"Gothic architecture developed from the Romanesque style and emerged in the twelfth century. It prevailed until the Renaissance beginning in the fifteenth century. Gothic architecture was marked by size and elaborate decorations. However, Gothic architecture was first defined in terms of a change in Romanesque church architecture diagonal ribs were added to the groin-vault, as was first seen at the Abbey Church of St. Denis near Paris (Frankl 1). In part because of its origins, Gothic architecture has long been associated with France and is considered a French style, though in fact, others used it as well. Gothic architecture is probably represented for many people by Notre-Dame de Paris, a facade known from countless stories and other representations as well as for itself. "
| |
|
Enterprise Service Bus Architectures, 2007.
A discussion on enterprise service bus (ESB) architectures in manufacturing.
4,879 words (approx. 19.5 pages), 7 sources, MLA, $ 124.95
»
Click here to show/hide summary
Abstract
The paper examines how many business drivers that are influencing and growing the use of enterprise service bus (ESB) architectures throughout global manufacturing are also making it critical for manufacturers to take into account the need for greater synchronization of supply chains across the many sourcing, supply chain, manufacturing, fulfillment and service centers. The paper discusses how, over and above the need for manufacturers to synchronize these disparate, legacy and often non-integrated systems with enterprise resource planning (ERP), supply chain, distributed order management, and often, global customer relationship management (CRM) systems is the more fundamental challenge of turning all these systems into competitive advantages in the marketplace.
Outline:
Introduction
Table 1: Planning Web Services For Channels: Real-Time Versus Batch Integration
Figure 1: Manufacturer's dilemma regarding mass customization and channel implications of integration
Figure 2: An example of a Brokered ESB Pattern Model
Implications of Visualization Grids on ESB in Manufacturing
Figure 4: Combining BPEL4WP and Key Performance Indicator Financial Performance
Figure 5: An Example of a Manufacturing Dashboard
Figure 6: IBM WebSphere's' Hierarchical Model
ESB as the Catalyst for attaining The Perfect Order
Table 2: Key Performance Indicators (KPIs) Relative to The Perfect Order
Enterprise Service Bus Case Studies
Areas for Future Research
References
From the Paper
"The logic of many global manufacturers is that while they are incurring the costs of attaining compliance to government regulations and standards for financial disclosure, they can at the same time completely re-define their IT strategies to better align with the needs of their business. In this regard many manufacturers today look to compliance as the impetus for change, and the primary reason to re-architecting how information technologies and services support making their organizations more agile and flexible."
| |
|
Materials Resource Planning, 2000.
An overview and exploration of the main differences between materials resource planning (MRP), materials resource planning II (MRP II) and Enterprise Resource Planning (ERP).
1,956 words (approx. 7.8 pages), 2 sources, MLA, $ 62.95
»
Click here to show/hide summary
Abstract
This paper looks at how material requirements planning (MRP or MRPI) was developed in the 1960?s, to enable companies to calculate the number of different components necessary and when they were needed. It traces its development over the years and identifes the main differences between materials resource planning (MRP), its predecessor materials resource planning II (MRP II) and Enterprise Resource Planning (ERP) as well as the pro's and con's of the MRP II concept. Using a basic diagram, the three fundamental functions of MRP are explained which are netting, batching and time phasing.
From the Paper
"Distinguishing MRPII from the original MRP concept is a simple process. MRPI is simply the process of identifying the amount of components required and at what time they are required. This developed into closed loop MRP, which calculated the workload required to fulfil the orders and compared this to the capacity available. MRPII expands on this by calculating the cost of proposed MRP runs, this allowed managers to identify viable production-runs and allowed them further control over the operation. In calculating the costs MRPII works in the opposite direction to MRPI, it starts at the lowest level of the BOM and works its way up until the net-requirements of the finished product is determined."
| |
|
ERP Solutions for Small to Medium Enterprise (SMEs), 2006.
A study of the use of ERP (enterprise resource planning) solutions in SMEs (small and medium enterprises).
3,847 words (approx. 15.4 pages), 19 sources, MLA, $ 105.95
»
Click here to show/hide summary
Abstract
This paper provides a discussion and case study analysis concerning the various strategies that enterprise resource planning (ERP) vendors have developed. The paper uses examples of findings from small and medium enterprises (SMEs) who have utilized these new options. Included is an assessment of what barriers exist in the implementation of ERP systems in SMEs. The study also provides an overview of the relevant issues, as well as those factors that contributed to their success or failure. Salient findings and a summary of the research, including the fact that virtually all small to medium-sized enterprises can take advantage of the benefits offered through a well selected ERP package, are provided in the conclusion, as well as recommendations to follow.
From the Paper
"Today, more and more SMEs are being pressured by an increasingly globalized economy to modify their traditional management styles, both operationally and organizationally, by replacing them with more streamlined and integrated systems that serve to improve the speed and flexibility of their physical and information flows (Jones, 2002), help synchronize demand with supply, and help manage transactions more accurately (Bigras & Gelinas, 2004). There are, however, a wide range of ERP alternatives available to assist in this regard, depending on what size firm is involved (Laursen, 2002). The majority of the ERP software packages are most appropriate for companies with more than $500 million in annual sales and more than 500 employees (Johnston, 2003); however, there are now a number of ERP solutions available on the market and even the main ERP players have solutions that are appropriate for the SME market (Krystkowiak, Bucciarelli & Dubois, 2004; Bielski, 2002). According to the report, "Mid-market Manufacturers and the New Landscape for Enterprise Resource Planning" (2005), "Enterprise resource planning (ERP) systems are streamlining and automating processes that small manufacturers would have found cumbersome to carry out on a global basis. This process improvement, in turn, allows these manufacturers to extend their geographic reach at lower costs" (p. 3). Therefore, ERP packages provide SME managers with more efficient and effective ways to interconnect geographically dispersed stakeholders and integrate existing information and communication technologies (Blenkhorn & Fleisher, 2001)."
| |
|
J2EE Multi-Tier Architecture, 2008.
Examines the four-tier architecture of the Java 2 Enterprise Edition (J2EE) platform.
940 words (approx. 3.8 pages), 4 sources, APA, $ 33.95
»
Click here to show/hide summary
Abstract
This paper describe each of the four-tier architectures maintained by Java 2 Enterprise Edition (J2EE): The client tier also known as presentation tier or application tier, the web tier, the enterprise javabeans tier also known as business tier and the enterprise information systems tier. The author points out that one of the main advantages of using J2EE to create enterprise-wide applications is that it has encapsulated specific functionality into each component. The author stress that the developers using this software can organize their enterprise applications into functionality with some level of abstraction between the various components, which enables the components to be placed in various tiers or levels.
Table of Contents:
Introduction
Client Tier
Web Tier
Enterprise JavaBeans Tier
Enterprise Information Systems Tier
From the Paper
"J2EE ensures that the components function efficiently in the distributed environment and in the various tiers with the help of the following services. J2EE has two CORBA technologies that are used to interact with the legacy systems. They are JavaIDL (Java Interface Definition Language) and RMI-IIOP (Remote Method Invocation- Internet InterORB protocol). Java Message Service (JMS) enables asynchronous communication of fault-tolerant messages. JMS is the glue that binds the various tiers."
|
| Term Paper # 105134 |
temporarily unavailable
|
|
|
|
Timber in Tectonic Architecture, 2006.
An explanation of tectonic architecture and how this form of architecture can make use of timber.
2,245 words (approx. 9.0 pages), 7 sources, MLA, $ 69.95
»
Click here to show/hide summary
Abstract
This paper explains what tectonic architecture is, examines the trend towards this form of architecture, discusses its history, describes the different modes of tectonic architecture and looks at the role that timber can have in tectonic architecture. The paper further explains why a return to tectonic architecture is an environmentally sound move and why timber is an appropriate material to use in tectonic construction.
From the Paper
"There is a growing movement towards tectonics in architecture, a return to the basic form and styles of the old schools of architecture. This movement has occurred as a result of the current tendency to reduce architecture to scenography. Architecture at the end of the 20th century has mostly been treated as a large commodity, with attention to cultural details minimized. Kenneth Frampton says that "among the seductions of the scenographic is the fact that the results are eminently amortizable, with all the deleterious consequences that this attitude entails for the future of the environment." Architecture of this century has been subject to the concept of spatial invention as an end in itself, with abstract art and visual obscurity the high points. The movement back to using the structural unit as the essence of architectural form is gaining strength."
|
|
|
