Ir al contenido principal

"Systems" Heroes or Villians

Regularly there is some dilemma and many myths regarding "systems", which bird of the storms can be criticized, questioned, supported and / or idolized.

You know them when you arrive, when something goes wrong or when your playing the hacker is identified and you are blocked, the rest of the time does not exist.

We will not become purists by invoking the general theory of Ludwig von Bertalanffy's systems, nor will we fall into a battle of concepts. We will simply see it as people identify it on a regular basis: information systems, technological infrastructure, communications. (Maybe we do not agree with the classification, but it is not about a class but about solutions to real life).


When buy a packaged system we assume that it works alone and will solve everything, in case the secret lies in the configuration and adequate training, as well as the development of procedures that facilitate internal control and monitoring of operations. Here, small and medium-sized companies are regularly the first to appear and suffer with network configurations, as well as with licensing. Consider that they usually ask for annual updates to support fiscal changes, support and improvements. Licensing schemes are fundamental.

When you buy an ERP, CRM, BI, WMS; it is configured and adapted to the particularities up to where the system or budget allow it. This will change the procedures regularly and present resistance to change, more due to ignorance and planning, than to the change itself. They carry hidden costs in infrastructure, licensing, maintenance. They handle concurrent or named users, the latter being a more expensive and bureaucratic scheme.

You can also manage the option of hosting or services in the cloud, where the key aspect will be connectivity and security, the connection part becomes more expensive only if they ask for symmetric Internet, but do not lose sight of the fact that the business in this segment is consumption. of storage and transactions. Licensing types also play an important role, as well as scalability.


Develop to the measure, has its peculiarities. On the one hand, the expected functionality is established, on the other, dependence is created if the analysis and design documents are not standardized and the consulting firms do not handle similar qualities. They are adjustable, the licensing is not as expensive as the large systems and usually support the IT area for implementation. They carry their maintenance costs and according to the methodology, but above all to the follow-up, it can be easy to carry and adapt to the needs of the company.

In particular, I do not lean towards a specific brand, each one has its pros and cons. I do not receive commission for selling them, I receive satisfactions, recommendations, new projects; based on the results, times, quality and strategic alignment. It does not benefit private or traditional brands such as Oracle, Sybase, Microsoft, IBM, SAP, etc.

"A good consultant does not sell brands, he is an articulator of solutions" - JMCoach

Methodologies? That methodology that is really understood by the members of the teams and is implemented with attachment and continuous monitoring, will be appropriate. There are no valid certifications if vital mistakes are made and the ego rules. The secret lies in balancing the teams, having a real knowledge of the business, leveraging the commitment of all participants, who must know the strategy fully understand.

With regard to software and hardware, it is often convenient to buy, finance or lease; this is in line with the business lines, tax recommendations, renewal, etc. Whereas everything is periodically renewed in cycles of 3 to 5 years.

The world of systems and technology is fascinating, it does not stop to progress to be an instrument of innovation of services and products, in increasingly competitive, demanding and changing markets.

The success of each project lies in aligning it with the business strategy, communication and monitoring.

If the system crashed, it may be real that the box where it came from, or the server that contains it, has been dropped. However, in practice it is a saturation of the services and the temporary blocking of them. Hence, the infrastructure management part has monitoring, analysis and prevention tasks. Not only do they block us from browsing the internet, they manage security in an integral way. An infrastructure area would gradually mature to prevent this. In addition to the benefits of the technological architecture that sets the guidelines for strategic alignment and solutions.


Regularly the technical support area or help desk is the one that pays for the broken dishes or takes the greatest glories, but it is their job to be day to day with the users assuring that they have their technological resources operating.


In itself the areas of systems, IT or as they are called in your company; They have the mission to be aligned with the company's strategies and provide solutions with availability of services.

By JMCoach
@JormerMx 

http://www.twitter.com/JormerMx
http://mx.linkedin.com/in/MxJormer

Comentarios

Entradas más populares de este blog

Il miglioramento continuo funziona?

 Molte volte abbiamo sentito parlare di miglioramento continuo e non ne vediamo i reali benefici, questo forse è dovuto alla scarsa conoscenza di esso. Potremmo riempirci di teorie e storie sulla qualità totale, Kanban, 5S, 6 Sigma, JICA, ecc. Essendo l'Europa e l'Asia dove vengono accettate con maggiore apertura e attaccamento. In realtà quello che stiamo cercando è innanzitutto identificare se la tua azienda, indipendentemente dalle dimensioni, ha processi, procedure, guide, ecc. Al di là dell'analisi di mesi, l'esperienza ci permette di identificare più cose e se le possiedi, quali: hard data (dati che vengono generati in ogni parte dei processi), coerenza, flessibilità, fiducia delle fonti di informazione, ragione dell'azienda eccetera. Quanto sopra alla fine ci permette di avere una prima panoramica di dove ti trovi come imprenditore / imprenditore, se il tuo personale conosce le procedure, le segue, la comunicazione, conosce il motivo dell'esistenza dell...

Un poco sobre la Arquitectura Empresarial y la Vida Real

Para un gran número de Empresas e Instituciones la planeación estratégica y la ejecución de los proyectos resultantes se dificulta por la falta de una visión integral de la empresa, comunicación hacia todas las áreas y niveles de la empresa. Lo anterior se logra vía la alineación de áreas áreas con los objetivos estratégicos, cultura y visión, apoyados del beneficio de la  tecnología, procesos, estrategia; aunado a las bondades de arquitectura empresarial(AE). La dirección de sistemas necesita de una visión que combine la estrategia, reestricciones, regulación, la arquitectura empresarial, los sistemas de información y los dominios de la tecnología. Esto permite contar con un marco integral (incluso un cross-functional) para analizar rápidamente el impacto de posibles cambios en los procesos o áreas y, para priorizar los proyectos que conduzcan a un mayor valor para la empresa. Esto dotará a las demás áreas de procesos, datos y soluciones para toma de decisiones . Lo anter...

Sobre la importancia de una PMO y no una moda pasajera

Para un alto número de empresas de todos los tamaños hoy sus resultados serían diferentes si conocieran el día a día de sus proyectos y reaccionaran oportunamente para que estos den los resultados esperados, simplificar la operación y administración en cualquier área de la empresa. Hoy se ha convertido en una moda la PMO, más ls resultados son tangibles si te apartas de la moda y pasas a la  experiencia de quienes dan resultado con las buenas prácticas. La PMO (Portfolio, Program and Project Management Office, tomando la referencia del OPM3 del PMI)  en un alto porcentaje de los casos no brinda los resultados esperados. Esto se debe al hecho de que la visión con la cual se le da razón de ser en una institución/empresa/universidad/consultora no es clara o se deja libre a los manejos con ética distinta. Establecer una PMO no se trata de asignar un número de PMs (Project managers) o Scrum masters con certificación o mixtos. Es una cultura de trabajo que involucra el ...