|
|
www.johnstark.com |
|
|
|
We'll replace our inefficient current systems with a more powerful tool Currently we have many systems that all do bits of the work that the EDM/PDM system will do. They weren't designed with EDM/PDM in mind. The result is that the overall system is not optimized and performance is not as good as it could be. Once we've got the EDM/PDM system in place, we'll tune it to fit the product development process, and performance will improve dramatically. We'll gain by linking systems together The EDM/PDM system will allow us to link systems together. It will help us build the bridges between Islands of Automation. We'll be able to get rid of unnecessary interfaces and artificial barriers. The result will be that information will flow better. Because there will be much less manipulation and conversion of data, there will be fewer errors, and quality will improve. We won't lose time with unnecessary activities. We'll reduce the overall cost of IS The EDM/PDM system will allow us to link systems together easily. We'll be able to remove unnecessary interfaces and systems. When we install the EDM/PDM system we'll remove any systems that do work done by other systems. We'll remove systems that aren't adding value. That will mean we'll need fewer systems, and we won't have to develop, purchase and maintain so many systems. The end result will be a reduction in overall IS costs. We'll provide better service to our customers Our customers in the product development process will benefit from the introduction of the EDM/PDM system. They'll find it easier to concentrate on their product development activities. Once the IS organization has eliminated all the unnecessary interfaces, systems and databases, it will have much more time to spend on the important activity of supporting users in the development process. They won't have to wait so long for the developments they're asking for. We'll be able to reduce staff levels We'll need fewer IS development staff because there will be less in-house development work to do and fewer interfaces to maintain. We'll need fewer people in the Engineering Computer Systems organization. With one underlying EDM/PDM system, and market-place interfaces between the EDM/PDM system and our CAD systems, there won't be so much development work to do. We'll be able to reduce the paper flow Paper is a very expensive medium for information communication and storage. We'll save money by transmitting and storing data electronically. We'll be able to sell off the storage space we'll no longer need. We'll use the EDM/PDM system's electronic mail functionality to communicate internally, and EDI to communicate with suppliers and customers. We'll benefit from standardization We'll have the same EDM/PDM system in use in all the departments. We'll be able to standardize the database management systems we use, standardize the operating systems, and standardize the development languages. We'll have common EDM/PDM training sessions for people from different departments. The end result will be that we'll save time and money. We'll manage the information resource better With the EDM/PDM system in place there'll be a single controlled source for all engineering information. We'll provide automatic back-up and archiving. We'll be able to standardize data definitions throughout the company. We'll be able to avoid the data duplication and re-definition that we've had in the past. We'll be able to ensure that information is secure but available to users who have access rights. We'll make sure users get the correct version of information. We'll be able to save corporate know-how. We'll provide simultaneous access to business data and engineering data In the past we had one system that gave users access to business programs and data and another system that gave them access to engineering programs and data. People couldn't get at the data in both systems at the same time. With EDM/PDM this problem will go away. We'll use EDM/PDM to manage our computer programs Computer systems have to be managed just like other engineering data. There are all sorts of versions and releases of both the software we purchase and the software we develop in-house. We'll use EDM/PDM to manage the software just like it manages other engineering data. We'll have an effective overall IS strategy The product development cycle runs from product conception to disposal, and we should have an IS strategy that supports this cycle. In the absence of EDM/PDM we couldn't have one because there were so many little bits of system all over the place, and so many discontinuities in the cycle. With EDM/PDM, we'll benefit from a clear overall strategy. We'll be able to get properly organized, reduce costs and improve performance. We'll be able to develop synergies between systems that weren't possible without EDM/PDM. We'll demonstrate we've changed our paradigms With the introduction of EDM/PDM, we'll show our customers that we've changed from a mainframe-terminal paradigm to a client-server paradigm, and from a hierarchical to a horizontal mindset. We'll be able to normalize organizational structures The introduction of a system like EDM/PDM that runs across organizational boundaries provides new opportunities for the IS organization. Individual departments can have difficulty in taking responsibility for a cross-functional system because they don't have company-wide responsibility. Organizations, such as the IS organization, that do have such responsibility can play an important new role. We'll be able to take advantage of advanced IS technology We'll be able to build up a database of corporate know-how. We'll use Artificial Intelligence techniques to exploit this to the full. |