The Analysis of Service Management Based Information Technology Systems at PT Mitra Solusi Telematika

Service Point is the spearhead that connects between the customer with the workforce engineer in the process of information technology services to improve IT services in the company. Often companies ignore this, whereas service point is one of the services of information technology services in order to ensure the sustainability of the business offered by the company. Analysis of incident management system in ITOP program and IT services service based on ITIL V3 framework for Service Point at PT Mitra Solusi Telematika is very much needed in effort to improve IT service to support Vision of PT Mitra Solusi Telematika become provider of integrated technology solution. One effort to improve IT services is by developing the process of providing IT services and services as a single point of contact that bridges between customers with all service point staff and IT services. The development of incident ITOP program management and IT support analysis begins with gathering information and analysis through a review of processes within existing ITOP programs, and ITIL V3 framework literature study. Analysis is done to refine the existing process. Once the document is created and developed, the next step is the document verification process to find out the purpose of the incident management process has been met. The results of this development of the management can facilitate the needs and improve IT services especially in Service Point Department PT Mitra Solusi Telematika for IT services to be maintained and measurabl

Rethinking Security Incident Response: The Integration of Agile Principles

In today's globally networked environment, information security incidents can inflict staggering financial losses on organizations. Industry reports indicate that fundamental problems exist with the application of current linear plan-driven security incident response approaches being applied in many organizations. Researchers argue that traditional approaches value containment and eradication over incident learning. While previous security incident response research focused on best practice development, linear plan-driven approaches and the technical aspects of security incident response, very little research investigates the integration of agile principles and practices into the security incident response process. This paper proposes that the integration of disciplined agile principles and practices into the security incident response process is a practical solution to strengthening an organization's security incident response posture.Comment: Paper presented at the 20th Americas Conference on Information Systems (AMCIS 2014), Savannah, Georgi

Patient safety in health care professional educational curricula: examining the learning experience

This study has investigated the formal and informal ways pre-registration students from four healthcare professions learn about patient safety in order to become safe practitioners. The study aims to understand some of the issues which impact upon teaching, learning and practising patient safety in academic, organisational and practice „knowledge? contexts. In Stage 1 we used a convenience sample of 13 educational providers across England and Scotland linked with five universities running traditional and innovative courses for doctors, nurses, pharmacists and physiotherapists. We gathered examples of existing curriculum documents for detailed analysis, and interviewed course directors and similar informants. In Stage 2 we undertook 8 case studies to develop an in-depth investigation of learning and practice by students and newly qualified practitioners in universities and practice settings in relation to patient safety. Data were gathered to explore the planning and implementation of patient safety curricula; the safety culture of the places where learning and working take place; the student teacher interface; and the influence of role models and organisational culture on practice. Data from observation, focus groups and interviews were transcribed and coded independently by more than one of the research team. Analysis was iterative and ongoing throughout the study. NHS policy is being taken seriously by course leaders, and Patient Safety material is being incorporated into both formal and informal curricula. Patient safety in the curriculum is largely implicit rather than explicit. All students very much value the practice context for learning about patient safety. However, resource issues, peer pressure and client factors can influence safe practice. Variations exist in students? experience, in approach between university tutors, different placement locations – the experience each offers – and the quality of the supervision available. Relationships with the mentor or clinical educator are vital to student learning. The role model offered and the relationship established affects how confident students feel to challenge unsafe practice in others. Clinicians are conscious of the tension between their responsibilities as clinicians (keeping patients safe), and as educators (allowing students to learn under supervision). There are some apparent gaps in curricular content where relevant evidence already exists – these include the epidemiology of adverse events and error, root cause analysis and quality assessment. Reference to the organisational context is often absent from course content and exposure limited. For example, incident reporting is not being incorporated to any great extent in undergraduate curricula. Newly qualified staff were aware of the need to be seen to practice in an evidence based way, and, for some at least, the need to modify „the standard? way of doing things to do „what?s best for the patient?. A number of recommendations have been made, some generic and others specific to individual professions. Regulators? expectations of courses in relation to patient 9 safety education should be explicit and regularly reviewed. Educators in all disciplines need to be effective role models who are clear about how to help students to learn about patient safety. All courses should be able to highlight a vertical integrated thread of teaching and learning related to patient safety in their curricula. This should be clear to staff and students. Assessment for this element should also be identifiable as assessment remains important in driving learning. All students need to be enabled to constructively challenge unsafe or non-standard practice. Encounters with patients and learning about their experiences and concerns are helpful in consolidating learning. Further innovative approaches should be developed to make patient safety issues 'real' for students

Security Incident Response Criteria: A Practitioner's Perspective

Industrial reports indicate that security incidents continue to inflict large financial losses on organizations. Researchers and industrial analysts contend that there are fundamental problems with existing security incident response process solutions. This paper presents the Security Incident Response Criteria (SIRC) which can be applied to a variety of security incident response approaches. The criteria are derived from empirical data based on in-depth interviews conducted within a Global Fortune 500 organization and supporting literature. The research contribution of this paper is twofold. First, the criteria presented in this paper can be used to evaluate existing security incident response solutions and second, as a guide, to support future security incident response improvement initiatives

Cost Estimate Modeling of Transportation Management Plans for Highway Projects, Research Report 11-24

Highway rehabilitation and reconstruction projects frequently cause road congestion and increase safety concerns while limiting access for road users. State Transportation Agencies (STAs) are challenged to find safer and more efficient ways to renew deteriorating roadways in urban areas. To better address the work zone issues, the Federal Highway Administration published updates to the Work Zone Safety and Mobility Rule. All state and local governments receiving federal aid funding were required to comply with the provisions of the rule no later than October 12, 2007. One of the rule’s major elements is to develop and implement Transportation Management Plans (TMPs). Using well-developed TMP strategies, work zone safety and mobility can be enhanced while road user costs can be minimized. The cost of a TMP for a road project is generally considered a high-cost item and, therefore, must be quantified. However, no tools or systematic modeling methods are available to assist agency engineers with TMP cost estimating. This research included reviewing TMP reports for recent Caltrans projects regarding state-of-the-art TMP practices and input from the district TMP traffic engineers. The researchers collected Caltrans highway project data regarding TMP cost estimating. Then, using Construction Analysis for Pavement Rehabilitation Strategies (CA4PRS) software, the researchers performed case studies. Based on the CA4PRS outcomes of the case studies, a TMP strategy selection and cost estimate (STELCE) model for Caltrans highway projects was proposed. To validate the proposed model, the research demonstrated an application for selecting TMP strategies and estimating TMP costs. Regarding the model’s limitation, the proposed TMP STELCE model was developed based on Caltrans TMP practices and strategies. Therefore, other STAs might require adjustments and modifications, reflecting their TMP processes, before adopting this model. Finally, the authors recommended that a more detailed step-by-step TMP strategy selection and cost estimate process be included in the TMP guidelines to improve the accuracy of TMP cost estimates

Real world evaluation of aspect-oriented software development : a thesis submitted in partial fulfilment of the requirements for the degree of Master of Science in Computer Science at Massey University, Palmerston North, New Zealand

Software development has improved over the past decade with the rise in the popularity of the Object-Oriented (OO) development approach. However, software projects continue to grow in complexity and continue to have alarmingly low rates of success. Aspect-Oriented Programming (AOP) is touted to be one solution to this software development problem. It shows promise of reducing programming complexity, making software more flexible and more amenable to change. The central concept introduced by AOP is the aspect. An aspect is used to modularise crosscutting concerns in a similar fashion to the way classes modularise business concerns. A crosscutting concern cannot be modularised in approaches such as OO because the code to realise the concern must be spread throughout the module (e.g. a tracing concent is implemented by adding code to every method in a system). AOP also introduces join points, pointcuts, and advice which are used with aspects to capture crosscutting concerns so they can be localised in a modular unit. OO took approximately 20 years to become a mainstream development approach. AOP was only invented in 1997. This project considers whether AOP is ready for commercial adoption. This requires analysis of the AOP implementations available, tool support, design processes, testing tools, standards, and support infrastructure. Only when AOP is evaluated across all these criteria can it be established whether it is ready to be used in commercial projects. Moreover, if companies are to invest time and money into adopting AOP, they must be aware of the benefits and risks associated with its adoption. This project attempts to quantify the potential benefits in adopting AOP, as well as identifying areas of risk. SolNet Solutions Ltd, an Information Technology (IT) company in Wellington, New Zealand, is used in this study as a target environment for integration of aspects into a commercial development process. SolNet is in the business of delivering large scale enterprise Java applications. To assist in this process they have developed a Common Services Architecture (CSA) containing components that can be reused to reduce risk and cost to clients. However, the CSA is complicated and SolNet have identified aspects as a potential solution to decrease the complexity. Aspects were found to bring substantial improvement to the Service Layer of SolNet. applications, including substantial reductions in complexity and size. This reduces the cost and time of development, as well as the risk associated with the projects. Moreover, the CSA was used in a more consistent fashion making the system easier to understand and maintain, and several crosscutting concerns were modularised as part of a reusable aspect library which could eventually form part of their CSA. It was found that AOP is approaching commercial readiness. However, more work is needed on defining standards for aspect languages and modelling of design elements. The current solutions in this area are commercially viable, but would greatly benefit from a standardised approach. Aspect systems can be difficult to test and the effect of the weaving process on Java serialisation requires further investigation

Trust Evaluation for Embedded Systems Security research challenges identified from an incident network scenario

This paper is about trust establishment and trust evaluations techniques. A short background about trust, trusted computing and security in embedded systems is given. An analysis has been done of an incident network scenario with roaming users and a set of basic security needs has been identified. These needs have been used to derive security requirements for devices and systems, supporting the considered scenario. Using the requirements, a list of major security challenges for future research regarding trust establishment in dynamic networks have been collected and elaboration on some different approaches for future research has been done.This work was supported by the Knowledge foundation and RISE within the ARIES project

A safer place for patients: learning to improve patient safety

1 Every day over one million people are treated successfully by National Health Service (NHS) acute, ambulance and mental health trusts. However, healthcare relies on a range of complex interactions of people, skills, technologies and drugs, and sometimes things do go wrong. For most countries, patient safety is now the key issue in healthcare quality and risk management. The Department of Health (the Department) estimates that one in ten patients admitted to NHS hospitals will be unintentionally harmed, a rate similar to other developed countries. Around 50 per cent of these patient safety incidentsa could have been avoided, if only lessons from previous incidents had been learned. 2 There are numerous stakeholders with a role in keeping patients safe in the NHS, many of whom require trusts to report details of patient safety incidents and near misses to them (Figure 2). However, a number of previous National Audit Office reports have highlighted concerns that the NHS has limited information on the extent and impact of clinical and non-clinical incidents and trusts need to learn from these incidents and share good practice across the NHS more effectively (Appendix 1). 3 In 2000, the Chief Medical Officer’s report An organisation with a memory 1 , identified that the key barriers to reducing the number of patient safety incidents were an organisational culture that inhibited reporting and the lack of a cohesive national system for identifying and sharing lessons learnt. 4 In response, the Department published Building a safer NHS for patients3 detailing plans and a timetable for promoting patient safety. The goal was to encourage improvements in reporting and learning through the development of a new mandatory national reporting scheme for patient safety incidents and near misses. Central to the plan was establishing the National Patient Safety Agency to improve patient safety by reducing the risk of harm through error. The National Patient Safety Agency was expected to: collect and analyse information; assimilate other safety-related information from a variety of existing reporting systems; learn lessons and produce solutions. 5 We therefore examined whether the NHS has been successful in improving the patient safety culture, encouraging reporting and learning from patient safety incidents. Key parts of our approach were a census of 267 NHS acute, ambulance and mental health trusts in Autumn 2004, followed by a re-survey in August 2005 and an omnibus survey of patients (Appendix 2). We also reviewed practices in other industries (Appendix 3) and international healthcare systems (Appendix 4), and the National Patient Safety Agency’s progress in developing its National Reporting and Learning System (Appendix 5) and other related activities (Appendix 6). 6 An organisation with a memory1 was an important milestone in the NHS’s patient safety agenda and marked the drive to improve reporting and learning. At the local level the vast majority of trusts have developed a predominantly open and fair reporting culture but with pockets of blame and scope to improve their strategies for sharing good practice. Indeed in our re-survey we found that local performance had continued to improve with more trusts reporting having an open and fair reporting culture, more trusts with open reporting systems and improvements in perceptions of the levels of under-reporting. At the national level, progress on developing the national reporting system for learning has been slower than set out in the Department’s strategy of 2001 3 and there is a need to improve evaluation and sharing of lessons and solutions by all organisations with a stake in patient safety. There is also no clear system for monitoring that lessons are learned at the local level. Specifically: a The safety culture within trusts is improving, driven largely by the Department’s clinical governance initiative 4 and the development of more effective risk management systems in response to incentives under initiatives such as the NHS Litigation Authority’s Clinical Negligence Scheme for Trusts (Appendix 7). However, trusts are still predominantly reactive in their response to patient safety issues and parts of some organisations still operate a blame culture. b All trusts have established effective reporting systems at the local level, although under-reporting remains a problem within some groups of staff, types of incidents and near misses. The National Patient Safety Agency did not develop and roll out the National Reporting and Learning System by December 2002 as originally envisaged. All trusts were linked to the system by 31 December 2004. By August 2005, at least 35 trusts still had not submitted any data to the National Reporting and Learning System. c Most trusts pointed to specific improvements derived from lessons learnt from their local incident reporting systems, but these are still not widely promulgated, either within or between trusts. The National Patient Safety Agency has provided only limited feedback to trusts of evidence-based solutions or actions derived from the national reporting system. It published its first feedback report from the Patient Safety Observatory in July 2005