![]() |
English |
|||||||||||||||||||||||
|
||||||||||||||||||||||||
|
|
|
|
|
||||||||||||||||||||
| Estamos en el proceso de construcción de la versión en español de www.mainboss.com. Disculpe por la inconveniencia. | ||||||||||||||||||||||||
|
MainBoss Automatic Data Conversion DetailsIn order to help customers get started with MainBoss, we have facilities for converting data from other CMMS packages into the format used by MainBoss. We can also convert data stored in some types of computer files (e.g. text).
The Conversion ProcessThe conversion process takes place in two steps:
This two-stage process gives us time to make sure we can handle any special considerations associated with your database. While we're examining the test data, you continue to use your old CMMS system as normal; therefore, your operations won't be interrupted. Once we've worked out any kinks in the conversion process, you send us an up-to-date database and we give you the fastest possible turnaround to get you started with MainBoss. (If necessary, we're prepared to do some back-and-forth with you between the initial conversion attempt and the final production conversion. However, as noted above, there's a limit to what automatic conversion can do. If you want more, the matter will be passed on to MainBoss Implementation Services, which can provide more hands-on conversion help.) What You GetOur automatic conversion processes are intended to give you a database that serves as a foundation for future work. The process is not intended to preserve a perfect history of old work orders, purchase orders, etc. You'll still be able to use your old CMMS to access old information, so we consider it acceptable not to put this data into the new database. The conversion does preserve information that is expected to be necessary in future. For example, it preserves information about equipment, inventory, and so on. The conversion process often highlights inconsistencies in the original data. For example, we have found that the same building might be referred to in many different ways (e.g. "100 Park Street", "100 Park St.", "100 Park", or just "100"). The automatic conversion process assumes these different names refer to different buildings, and will therefore create a separate Building table entry for each different name. Problems may also occur if you make typing mistakes when entering data (e.g. typing "100 Prak" instead of "100 Park"). In order to resolve such problems, you must tell us when different names refer to the same thing. Essentially, you'll look at the results of the first conversion attempt (which will list all the different names the conversion process found). You will then give us a text file that lists all the names and tells which are equivalent to each other. We can then adjust the conversion process so that the final conversion knows which different names refer to the same building. In the standard conversion process, we will not make corrections by hand. You must give us text files that will let us automatically take care of different names for the same thing. (We'll explain how to create such text files after we do the first test conversion.) At times, your original data will have problems that are too serious for our conversion software to handle. Our Implementation Services staff may be able to solve these problems for a fee, but such difficulties are beyond the scope of automated conversion. Making Conversions WorkTo make the conversion process work smoothly, you should do some advance preparation. In particular, you must provide us with any passwords needed to access your data. Experience has shown there may be many passwords associated with a database. Therefore, it's important for you to give us the correct ones. The best way to determine which passwords are needed is to follow this procedure:
|
| Copyright © 2010, Thinkage Ltd. Todos los derechos reservados. |