Sweet Songs To Play At B-ball Game

Como montar un Sistema de información y no morir en el intento

Dear, as has become common to call to ask about information systems that implement some well-known in their companies, it seems friends who sell packages applications generally focus on simply offering its software , stick it in the eyes of the customer and then in the implementation process literally anything mounted. Generally the present implementation methodologies the following steps:

1. Process Blueprint: which details the functional structure of the business, usually at this stage is that time pressures in the implementor the level of detail is not adequate, are recurrent in this phase phrases like: That's more detail in the parameterization, this one we can be adjusted during the testing, they can connect from other information system, are unnecessary red flags, etc.


2. Configuring the tool: during this phase will be to perform the customization of the package information fields are enabled to be used, defines the structure of information within the platform (which should have been defined in the blueprint), making connections to external information systems. Usually during this phase, changes are made which change the initial model of the blueprint and not documented, fit business processes to process models which by default is the tool under the excuse "is that this is handled by the package," and in order to start a hell of changes at the end when the process is not systematized with the right information to manage changes after creating a dependency of the implementer of the platform.


3. Integration with third parties: implementers generally say they do, but generally do not adequately measure the scope of the effort involved, or point to point integrations are the basic level of data synchronization failures generate data, etc. Is a peak that must be taken into account from the beginning of the project that is usually overlooked.


4. function tests: is the phase that allows process owners to verify that what they really need is reflected in the model implemented, is necessary during this phase the functional user feel free to check it that the business really needs is reflected within the system.


5. Communications Plan: This plan starts at the time when the company decides to implement an information system, not the end or mid-project. Now a communications plan is not just putting banners or signs in the company, or speeches or courses for employees. The communications plan should be focused on how to change a work culture within an organization, it must ensure that they are "Sponsors" in functional areas, creating incentives for the use of new technology, communicating the benefits of new tool and really make it useful for the company. (Not a burden more)


6. Kick off system: Fiesta, wine, happy all the information system started ... and once it starts trading.


7. Stabilization: Issues data quality and consistency of information, audit parameterized processes within the system, how to handle the error (If this is a learning process?)

Before purchasing a system information would be good to follow these guidelines and you may survive this adventure:

• Ask for what you , if you will generate value to your business and how they want to make you this value. That's what I want out of that system and keep it very clear as "north" during the implementation process, because the systems engineers will want to change it. (This is not like buying a Excel)


• Identify where is the information to use, is key to have much clarity about the sources of information as it becomes part of your business processes, define what information is essential within the value chain and which is supportive. Document your processes involving information flowing through them.


• Know and clearly on their processes, especially those who will be supported by the information system, identify which processes outside the scope of the information system are input, or depend for those who will be automated. Usually the settings are incomplete in the absence of this information. Information system has to reflect your business and must be documented, for this there needs analysis tools that combine functional technical aspects. (RUP is one of them) Think


• first in Information Architecture and after the technology architecture, technology TOOL is a result of its intelligence. Any information system is useful if you have sufficient clarity of use. Please do not bring your business to depend on others, it is absurd that the systems engineer is done by defining what your business should do. Search


• who has experience in sector, especially the implementer knows the business (which is almost impossible to find, in addition to being risky because of the conflict of interest that may generate) is advisable to perform a combination of functional expert sector and technical Deployer, which ensures that there is no relationship judge and party during the implementation process. In addition, each in its own, is very expensive for companies to hire someone who has both roles within the project because: it can more easily implement what you stay, lose bargaining power when implemented, creates dependency.


• Be pessimistic, think that both can grow your business and ask yourself if the system can grow with it, usually all say they can grow indefinitely. You think so? Think of another year may change their strategy and they can focus on other products, projects or services. The system supports the changes? As these changes would cost?


• sure have "sponsors" within user areas, if you do not have, identify, import, do something .. they are the only way for the organization to adopt the technology, otherwise you risk working with little junk information will help manage your business and use the investment sub you just made.


• Try it, and retest recompruébelo Always be testing the technology, any change document it, check the quality of their information, if you have problems with it, implement controls. Ensure that the system does the job it was purchased, otherwise seek help. Duden


• a vendor information system that ignores their business model - note that usually want to sell the package and are always experts in medicine, banking, energy, etc. A sea of \u200b\u200bknowledge ....

Some questions to ponder: Have you ever taken your information system in time I had planned? has been that all processes have been systematized properly? had problems with re-parameterizations? the data quality is adequate? has adequate management reports to their business model?

Gentlemen, its information systems are the heart of your business, is a management tool unique and unrepeatable (Can you imagine that all companies operate the same way? As competing?) Reflects each of the processes and activities BUSINESS , if your information system is flexible, scalable and adaptable to the changing needs of its business model have made a good choice. Otherwise, run the risk of having a "leech" within your company that will be difficult to remove when you do not have clear information structure, as this structure is reflected in its business model and if your system really adds value to business.

Good luck with this adventure and whatever I have.