In this documents, I am going to be explaining the impact of organisational policies on the troubleshooting and repair process, I am going to be talking about the organisational policies, such as considerations e.g. security, costs, systems downtime, disruption, resource allocation, prioritisation, contractual requirements, trend analysis, escalation procedures, documentation, reporting, contractual legal issues.
An organisational policy is expected to do many things. Primarily it should protect people and information, as well as set the rules for expected behaviour by users, system administrators, management and security personnel. It should also authorise relevant personnel to monitor, probe, investigate, define and authorise the consequences of violations, in addition to defining the company’s baseline stance on security. This can help minimise risk and help track compliance with appropriate regulations.
This policy is mainly responsible for making sure that all the security detail such as password and user accounts are secure so you have to make sure that you are the only person that uses the account. IT systems Acceptable usage policy requires from users to log off the computer as inappropriate people could get the access to the data that they shouldn’t. The user also shouldn’t install the unauthorized software as this could lead to the issues such as making the equipment unusable by affecting it performance. The users also have to make sure that the equipment is secure during the use of it and after. The users within college are not allowed to connect they own device to the college network if they don’t get authorization from the IT Manager.
In term of costs the members of the staff has to make sure that they examine all the purchasing and introduce the environmental criteria to make sure that the equipment meets all the requirements and condition. They are also required to research on the equipment that they are purchasing to make sure that there is no alternatives with are better or cheaper. They also have to encourage the use of recycled paper to make sure that people don’t use it in inappropriate reasons that are not associated with the course as they are spending the college money. If the potential user with in this case is the student brake the equipment the staff have to make sure that it was reported and the person that did it will have to pay back the money for it.
System downtime is usually affected by many issues but they all can be prevented if the right procedures have been taken and the staffs fallow all the legislations. In this case people have to make sure that they have the right equipment for example server. They also should make regular backups so student and teachers work don’t get lost. The regular maintainer should be taken at the end of each week. System downtime could cause a lot of damage as if the system would be down user wouldn’t be able to perform they daily routine.
Disruption is when something unexpected happened and person responsible for that area is not preparing for it. Organization such as College should have plan for everything so in case that something happen they have solution to repair it and prevents it from happening. For example if users lose they work organization should back them up. In order to back the files up they would have to be prepare for this to happen.
All the resources should be right allocated. This mean that there shouldn’t be too much of resources for one place for example you cannot add too much of the paper for the printer as the printer could damage the paper if there are too many resources than it should be the company could lose a lot of money as they might spend money on the unimportant resources. Resources should be well balanced so if the resources are not needed they shouldn’t been used.
The company should prioritize some of the aspect when performing repair as they might be more important and they should be repaired first. For example if network is down and at the same time printer is not working. The person that perform repair should concentrate on repairing network instead of printer as without network printer would be useless.
In a company, the support team staff would be required to work shifts that will provide coverage for the employees when the offices are officially opened, they will also need to provide extra time in the evening and weekends, where they will carry out the essential maintenance which may have to involve some downtime. The hours that an employee will have to work will be set out for them in what is called an employment contract. They will be limited by the EU legislation and some other regulations such as working time regulations, which will provide the basic right and protections such as: A worker can be required to work at most an average of 48 hours a week (though workers can choose to work more if they want to). For night workers there is a limit of an average of 8 hours worked in 24. Night workers are entitled to receive free health assessments. All staff are entitled to 11 hours of rest a day and to one day off each week. When the working day is longer than 6 hours, workers must have an in-work rest break. Workers are entitled to 4 weeks of paid leave per year. These protections may or may not be in place. You should check your contract to find out any special conditions of service before signing.
The records that are kept of incidents and how these are dealt with can provide useful data how successfully the support team are running, so an organisational policy will decide the frequency of analysis and of data and exactly what type of data has to be recorded by the IT supporting team. Trends can then be identified which will then help with the formulation of the plans to provide better and more reliable hardware and software package, it may then also be used to target a form of training for the users who will need them the most. Trend analysis can then also be used to re-allocate budgets and resources to identify the hotspots.
An escalation process in different support establishments vary depending on the type of service that they have. In a technical support group, this involves setting up thresholds for certain issues to be addressed at certain levels. Typically it is a tiered setup. For example, Tier 1 can handle issues that can be easily resolved by just a phone call and when the Tier1 representative feels that the issue cannot be resolved at his level (if for example the problem cannot be resolved by their team alone and needs to be addressed by other support teams/departments with higher level of authority) it is then escalated or moved to the next higher team. This way the issues are segregated depending on their severity and type of resolution.
The procedures of documentation vary from one sector, or one type, to another. In general, these may involve document drafting, formatting, submitting, reviewing, approving, distributing, reposting and tracking, etc., and are convened by associated SOPs in a regulatory industry. Since a key step in the process management journey is the documentation of current processes and any exceptions to those processes, this article explores how to create a template for your process documentation guide. A template makes the process of documenting your processes repeatable. Repeatable is the word to remember here primary aspects of a process documentation guide should be easily duplicated and reused to create additional guides after the first process has been documented. This repeatability feature makes it less painful to create your documentation as you move through all the processes in an organization. It also provides readers with a common format to follow as they research or review processes within your organization.
Reporting may seem like a simple exercise in transparency but it is more than that. In fact, it gives management an additional opportunity for improvement, through readers’ reactions, criticisms and suggestions. Considering stakeholder views also helps to shape strategy, goals and objectives. All the inputs from direct stakeholders should be carefully reviewed as part of a management learning process to adapt and fine-tune the company’s sustainable development objectives.
Contractual Legal Issues
Regardless of whether you use an agency or not, you will require some knowledge of contract law and the ability to negotiate a suitable agreement. IR35 should be at the forefront of your mind throughout this process if you are to keep as much as possible of your pay packet out of the clutches of the taxman. On the most basic level, any agreement reached with a client must make clear that you are a contractor and not an employee. This distinction should be clear in both the contract and your modus operandi. Primarily, your contract should define exactly what you are agreeing to do for the client. In contrast to an employee, whose work may not be defined at all in the contract, you must make sure that the document clearly lays out the service or services that you are to provide.
So in conclusion, this document has been explaining the impact of organisational policies on the troubleshooting and repair process, I am going to be talking about the organisational policies, such as considerations e.g. security, costs, systems downtime, disruption, resource allocation, prioritisation, contractual requirements, trend analysis, escalation procedures, documentation, reporting, contractual legal issues. Hopefully, this would help an organisation in the process of troubleshooting and repair.