ITIL V3:持续服务改进阶段详解

需积分: 9 1 下载量 11 浏览量 更新于2024-10-16 收藏 2.09MB PDF 举报
"Service_Operation 是 ITIL (Information Technology Infrastructure Library) V3 体系中的一个核心模块,专注于服务生命周期中的持续服务改进阶段。这个课程旨在教授学员如何在 IT 服务管理中实施有效的运营,确保服务的高质量、高效率和稳定性。ITIL V3 的服务生命周期包括五个主要阶段:服务策略、服务设计、服务转换、服务运营和服务持续改进。本课程关注的是服务运营阶段,这一阶段涉及到日常服务交付和管理,以及与客户、业务和供应商之间的交互。 在 Service Operation 中,学员将学习到的关键知识点包括: 1. **服务运营的角色与职责**:理解服务台、IT 运营团队、应用管理和技术管理等关键角色的职能,以及它们在服务运营中的协作。 2. **流程详解**:深入探讨事件管理、问题管理、变更管理、配置管理、发布管理等核心流程,了解它们如何协同工作以确保服务的稳定性和可用性。 3. **服务级别管理**:学习如何设定并维护服务级别协议(SLAs),确保服务满足业务需求和客户期望。 4. **IT 质量与性能管理**:理解如何度量服务质量和性能,使用这些指标来驱动持续改进。 5. **业务连续性和灾难恢复**:学习如何规划和实施策略以减少中断风险,确保业务关键服务的连续性。 6. **合作与供应商管理**:了解如何与内外部供应商建立有效的合作关系,共同提升服务质量。 7. **决策制定**:学习在服务运营中如何做出快速而正确的决策,平衡服务成本与风险。 通过这个课程,学员不仅会掌握理论知识,还将有机会进行实践练习,以提高在实际工作中实施这些概念和流程的能力。此外,该课程提供的认证将证明个人对 ITIL 服务运营的理解和专业能力,对于提升职业生涯和组织内的影响力具有重要意义。 课程资料由 TSO (The Stationery Office) 出版,并可通过多种渠道购买,包括在线商店、电话订购和邮件。TSO 还在伦敦、贝尔法斯特和爱丁堡设有实体店,方便学员获取教材。出版此书是根据英国政府的版权许可,若需重用或再版其中的内容,需要向 OPSI(Office of Public Sector Information)申请 Click-Use 许可证。" 这个资源是关于 ITIL V3 服务运营的知识体系,它提供了服务生命周期中服务运营阶段的全面指导,对于那些希望提升 IT 服务管理能力的专业人士来说,是一份宝贵的教育资源。

SELECT PIS.SHOW_FLT_DETAIL AS SHOW_FLT_DETAIL -- new , PIS.SHOW_AWB_DETAIL AS SHOW_AWB_DETAIL -- new , PIS.DISPLAY_AIRLINE_CODE AS CARRIER_CODE , DECODE(PIS.REVERT_FLOW,'N',PIS.FLOW_TYPE,DECODE(PIS.FLOW_TYPE,'I','E','I')) AS FLOW_TYPE , PIS.SHIP_TO_LOCATION AS SHIP_TO_LOCATION , PIS.INVOICE_SEQUENCE AS INVOICE_SEQUENCE , PFT.FLIGHT_DATE AS FLIGHT_DATE , PFT.FLIGHT_CARRIER_CODE AS FLIGHT_CARRIER_CODE , PFT.FLIGHT_SERIAL_NUMBER AS FLIGHT_SERIAL_NUMBER , PFT.FLOW_TYPE AS AIRCRAFT_FLOW , FAST.AIRCRAFT_SERVICE_TYPE AS AIRCRAFT_SERVICE_TYPE , PPT.AWB_NUMBER AS AWB_NUMBER , PPT.WEIGHT AS WEIGHT , PPT.CARGO_HANDLING_OPERATOR AS CARGO_HANDLING_OPERATOR , PPT.SHIPMENT_PACKING_TYPE AS SHIPMENT_PACKING_TYPE , PPT.SHIPMENT_FLOW_TYPE AS SHIPMENT_FLOW_TYPE , PPT.SHIPMENT_BUILD_TYPE AS SHIPMENT_BUILD_TYPE , PPT.SHIPMENT_CARGO_TYPE AS SHIPMENT_CARGO_TYPE , PPT.REVENUE_TYPE AS REVENUE_TYPE , PFT.JV_FLIGHT_CARRIER_CODE AS JV_FLIGHT_CARRIER_CODE , PPT.PORT_TONNAGE_UID AS PORT_TONNAGE_UID , PPT.AWB_UID AS AWB_UID , PIS.INVOICE_SEPARATION_UID AS INVOICE_SEPARATION_UID , PFT.FLIGHT_TONNAGE_UID AS FLIGHT_TONNAGE_UID FROM PN_FLT_TONNAGES PFT , FZ_AIRLINES FA , PN_TONNAGE_FLT_PORTS PTFP , PN_PORT_TONNAGES PPT , FF_AIRCRAFT_SERVICE_TYPES FAST , SR_PN_INVOICE_SEPARATIONS PIS --new , SR_PN_INVOICE_SEP_DETAILS PISD--new , SR_PN_INV_SEP_PORT_TONNAGES PISPT --new WHERE PFT.FLIGHT_OPERATION_DATE >= trunc( CASE :rundate WHEN TO_DATE('01/01/1900', 'DD/MM/YYYY') THEN ADD_MONTHS(SYSDATE,-1) ELSE ADD_MONTHS(:rundate,-1) END, 'MON') AND PFT.FLIGHT_OPERATION_DATE < trunc( CASE :rundate WHEN TO_DATE('01/01/1900', 'DD/MM/YYYY') THEN TRUNC(SYSDATE) ELSE TRUNC(:rundate) END, 'MON') AND PFT.TYPE IN ('C', 'F') AND PFT.RECORD_TYPE = 'M' AND (PFT.TERMINAL_OPERATOR NOT IN ('X', 'A') OR (PFT.TERMINAL_OPERATOR <> 'X' AND FA.CARRIER_CODE IN (SELECT * FROM SPECIAL_HANDLING_AIRLINE) AND PPT.REVENUE_TYPE IN (SELECT * FROM SPECIAL_REVENUE_TYPE) AND PPT.SHIPMENT_FLOW_TYPE IN (SELECT * FROM SPECIAL_SHIPMENT_FLOW_TYPE) AND PFT.FLIGHT_OPERATION_DATE >= (select EFF_DATE from SPECIAL_HANDLING_EFF_DATE) )) AND PFT.DELETING_DATETIME IS NULL AND FA.AIRLINE_UID = PFT.AIRLINE_UID AND FA.DELETING_DATETIME IS NULL AND PTFP.FLIGHT_TONNAGE_UID = PFT.FLIGHT_TONNAGE_UID AND PTFP.RECORD_TYPE = 'M' AND PTFP.DELETING_DATETIME IS NULL AND PPT.TONNAGE_FLIGHT_PORT_UID (+)= PTFP.TONNAGE_FLIGHT_PORT_UID AND PPT.RECORD_TYPE (+)= 'M' AND PPT.DISCREPANCY_TYPE (+)= 'NONE' AND PPT.ADJUSTMENT_INC_FLAG (+)= 'Y' AND PPT.DELETING_DATETIME (+) IS NULL AND FAST.AIRCRAFT_SERVICE_TYPE_UID = PFT.AIRCRAFT_SERVICE_TYPE_UID AND FAST.DELETING_DATETIME IS NULL AND PIS.TEMPORAL_NAME = TO_CHAR((CASE :rundate --new WHEN TO_DATE('01/01/1900', 'DD/MM/YYYY') THEN TRUNC(SYSDATE) ELSE TRUNC(:rundate) END ), 'YYYYMM') || '00' AND PIS.INVOICE_SEPARATION_UID = PISD.INVOICE_SEPARATION_UID --new AND PISD.INVOICE_SEP_DETAIL_UID = PISPT.INVOICE_SEP_DETAIL_UID --new AND PISPT.PORT_TONNAGE_UID = PPT.PORT_TONNAGE_UID --new AND PIS.PRINT_SUPPORTING_DOC = 'Y';上面是oracle的写法,请转成spark SQL的写法。

2023-06-02 上传

代码优化 public Result phmOperate(Operation<PhmOperation,PhmCause> operation) { HlwExmMessage msg = messageService.queryMsgById(operation.getMsgId()); if (msg!=null){ if (msg.getOperateMsgId()!=null){ return new Result<>(Status.UN_ACCESS_OPERATION,"消息已处置,重复处置无效!"); } HlwExmMessage<DocOperateMsg> msg2 = messageService.queryDocToPhmMsg(msg.getTaskId()); Integer msgId2 = msg2==null?null:msg2.getMsgId(); if (!Objects.equals(msg.getMsgId(),msgId2)){ //当前被处置消息与任务最后一条消息不是同一条消息, //原因:第一次审查通过后,药师正准备提交审方结果时,医生重新修改医嘱提交,造成药师审核的医嘱信息已过期。 // 最终会形成一个审方任务干预记录中有两个及以上药师审核通过,也有可能药师不通过,造成审方流程错乱 return new Result(Status.UN_ACCESS_OPERATION,"被处置消息已过期,处置无效,医生已修改医嘱,请刷新任务!"); } Integer forward = msg.getForward(); if (HlwExmMessage.FORWARD_DOC_TO_PHM.equals(forward)){ List<String> operations = msg.getOperations(); //处置代码 PhmOperation opCode = operation.getOperation(); if (operations.contains(opCode.name())){//校验操作是否合法。每个消息可处置方式不同: return operate(operation, msg, opCode)? Result.SUCCESS: new Result<>(Status.UN_ACCESS_OPERATION, "当次就诊已作废,处置失败!"); }else { return new Result<>(Status.ERROR,"非法处置:当前消息可选择的处置方式"+operations.toString()); } } } return new Result<>(Status.ERROR,"被处置消息无效!"); }

2023-05-25 上传

代码优化 HlwExmMessage msg = messageService.queryMsgById(operation.getMsgId()); if (msg!=null){ if (msg.getOperateMsgId()!=null){ return new Result<>(Status.UN_ACCESS_OPERATION,"消息已处置,重复处置无效!"); } HlwExmMessage<DocOperateMsg> msg2 = messageService.queryDocToPhmMsg(msg.getTaskId()); Integer msgId2 = msg2==null?null:msg2.getMsgId(); if (!Objects.equals(msg.getMsgId(),msgId2)){ //当前被处置消息与任务最后一条消息不是同一条消息, //原因:第一次审查通过后,药师正准备提交审方结果时,医生重新修改医嘱提交,造成药师审核的医嘱信息已过期。 // 最终会形成一个审方任务干预记录中有两个及以上药师审核通过,也有可能药师不通过,造成审方流程错乱 return new Result(Status.UN_ACCESS_OPERATION,"被处置消息已过期,处置无效,医生已修改医嘱,请刷新任务!"); } Integer forward = msg.getForward(); if (HlwExmMessage.FORWARD_DOC_TO_PHM.equals(forward)){ List<String> operations = msg.getOperations(); //处置代码 PhmOperation opCode = operation.getOperation(); if (operations.contains(opCode.name())){//校验操作是否合法。每个消息可处置方式不同: return operate(operation, msg, opCode)? Result.SUCCESS: new Result<>(Status.UN_ACCESS_OPERATION, "当次就诊已作废,处置失败!"); }else { return new Result<>(Status.ERROR,"非法处置:当前消息可选择的处置方式"+operations.toString()); } } } return new Result<>(Status.ERROR,"被处置消息无效!");

2023-05-25 上传