Documents » implementation of documentations for aircraft.
Abstract: Learn how Boeing
Aircraft and Missile Systems reduced its manufacturing costs and increased production, while decreasing its warehouse footprint, and keeping all of its current staff in place.
PubDate: 4/29/2005 9:33:00 AM
Abstract: In the airline industry, aircraft maintenance is an activity that has to be done throughout the day, so maintenance personnel must be available at all times. The complexity of the operation increases the need for a maintenance personnel management system.
Abstract: Bar code technology allows users to analyze information to develop more accurate maintenance, personnel, and financial planning. In particular it can hasten the data recording processes in a maintenance system, as seen in its use in the aircraft maintenance process.
Abstract: At Nagoya Guidance and Propulsion Systems (NGPS), more than half of production time goes into to products such as aircraft guidance systems. In 2003, NGPS installed Asprova’s advanced planning and scheduling system for greater efficiency from the planning it had been doing manually until that time. In 2007, NGPS added the sales module for more uniform production planning. Learn more about the efficiencies NGPS gained.
Abstract: KLM Catering Services (KCS) Schiphol prepares and delivers 45,000 meals a day for 12 airlines, 350 flights, and 50 different types of aircraft. KCS also manages non-food supplies such as beverages, sales trolleys, and navigation bags to the private airport lounges in Schiphol Airport. Find out why it’s achieving a delivery performance of over 99 percent.
Abstract: When Lockheed Martin sells technology such as aircraft to its customers, it also provides training systems for both pilots and maintenance personnel. The training system must handle student and instructor registration, and training records and certifications—with scheduling for students and resources. Find out about the learning management system with simulator training functionality that the company chose.
Abstract: Software implementation can be complex. Even when it seems all your business processes and systems are “go” after the implementation of an enterprise resource planning (ERP) solution, there might still be room for improvement. Find out how a post-implementation system assessment of technical and functional systems can improve data capture accuracy, increase user buy-in, and boost your return on investment (ROI).
Abstract: It’s crucial to define the scope of an electronic medical system implementation, as well as to outline each stage of the project and the resources that will be needed. A failed implementation will paralyze the operational capabilities of a health care organization, but the right methodology will help ensure a successful implementation.
Abstract: Because of the risks inherent in any financial implementation, it’s essential to get back to business basics. These implementations need to be understood and planned for. Thus, there are a few premises that must be addressed in the planning stages of a financials implementation. If these premises are followed in a disciplined manner, the nosebleed of implementation can be avoided.
Abstract: The Microsoft Dynamics NAV Rapid Implementation Methodology (RIM) automates standard processes, speeds up implementation time, and drives the sharing of best practice knowledge and solutions between partners. But in order to understand how RIM can be used in an implementation project to get implementations up and running smoothly and quickly, it is important to understand the different components of RIM.
Abstract: White papers offer no shortage of advice about what best practices can lead to enterprise resource planning (ERP) implementation success. But equally important is a thorough understanding of what practices are to be avoided during an implementation. This white paper reviews four “worst practices” that should be avoided at all costs—unless you want to go out of your way to cause your ERP implementation to fail.
Abstract: It’s a sad but well-known fact that many software implementation projects run out of time and money. Certain crucial activities tend to have striking effects on the cost of an implementation. But it’s possible to stick to plans and budgets, provided that you do the right things and avoid the traps. Discover which parts of a software implementation are worth spending extra money on in order to minimize risk and cost.
Abstract: Are you preparing to oversee an enterprise resource planning (ERP) implementation project? Are you worried about the statistics that report less-than-successful ERP implementations? While there are many reasons a given implementation project may be less than perfect, there are a few steps you and your ERP implementation team can take to increase your chances of success. Learn about the five steps to a positive outcome.
Abstract: Implementation of a radio frequency identification system is best approached in four phases to ensure its success. Discussed here are the second and third phases, which deal with testing and validation, and the importance of setting up a pilot implementation.
Abstract: Product lifecycle management (PLM) implementation brings its own set of challenges, whether considering vendor selection, employee perception management, or actual implementation. However, based on experience and study, it is possible to describe the best practices for overcoming these challenges.
Abstract: Here are four worst practices that can contribute to the failure of an enterprise resource planning implementation—or the implementation of any other enterprise software, for that matter. Protect your investment and prevent disaster by steering clear of these major mistakes.
Abstract: At the Connections 2000 Logility user conference in New Orleans, users recounted implementation stories. Few were as striking as that of the Komatsu’s DRP implementation modifications, a testament to human ingenuity.
Abstract: webMethods, Inc. has released a set of Packaged Integrations — pre-built software solutions that can be used to rapidly automate common cross-application business processes. The company claims Packaged Integrations make it possible to accelerate implementation by up to 80 percent and reduce implementation costs by up to 70%.
Abstract: The biggest single issue in ERP is the failure of a successful implementation. It is mind-boggling to continually encounter companies who make major ERP gaffes in this day and age, especially since most of the trials and tribulations of MRPII implementation were suffered and learned from in the early 1980's with alpha, beta and gamma releases. The pertinent question is what are the main causes of ERP failure and what can be done to prevent this from happening to you? There are twelve major reasons for why companies get bogged down or fail in implementing ERP. This white paper addresses them.