GAMP5及计算机化系统验证相关知识

上传人:s9****2 文档编号:570256841 上传时间:2024-08-03 格式:PPT 页数:147 大小:5.67MB
返回 下载 相关 举报
GAMP5及计算机化系统验证相关知识_第1页
第1页 / 共147页
GAMP5及计算机化系统验证相关知识_第2页
第2页 / 共147页
GAMP5及计算机化系统验证相关知识_第3页
第3页 / 共147页
GAMP5及计算机化系统验证相关知识_第4页
第4页 / 共147页
GAMP5及计算机化系统验证相关知识_第5页
第5页 / 共147页
点击查看更多>>
资源描述

《GAMP5及计算机化系统验证相关知识》由会员分享,可在线阅读,更多相关《GAMP5及计算机化系统验证相关知识(147页珍藏版)》请在金锄头文库上搜索。

1、Austar Promotes Industry AdvancementGAMP5及计算机化系统验证相关知识鲁抗立科公司自控验证探讨GAMP5(Good Automated Manufacturing Practice)良好自动化生产实践指南A Risk Based Approach to Compliant GxP ComputerisedSystem遵从GxP计算机化系统监管的风险管理方法Different Terminology不同的术语Computerised Systems计算机系统Automation Systems自动化系统Control Systems控制系统Control E

2、quipment控制设备Data Management systems 数据管理系统Computerised System: A system including the input of data, electronicprocessing and the output of information to be used either for reporting orautomatic control计算机系统:系统中包括数据输入,电子化处理和用于报告或自控的信息输出SFDA: Good Manufacturing Practice for pharmaceutical products(D

3、raft for comment)SFDA:药品生产质量管理规范(征求意见稿) Introduce 简介GAMP5( Good Automated Manufacturing Practice -Rev5)GAMP是由国际制药工程协会(ISPE)主编的实践指南。自90年代以来,不断改版的良好自动化生产实践指南被广泛使用并得到国际监管部门的公认。它是计算机化系统验证的指导方针。GAMP5是GAMP的第5版本。计算机化系统由硬件、软件、网络组件和可控的功能和相关文件组成软件硬件固件控制系统操作规程与人员设备受控的功能与流程计算机化系统FDA(FoodandDrugAdministration)TG

4、A(TherapeuticGoodsAdministration)治疗产品管理局(MedicinesandHealthcareProductsRegulatoryAgency waspreviouslytheMCA)(药品及保健产品管理局前身为药品监督局)EMEA(EuropeanMedicinesEvaluationAgencyincludesMHRAandequivalentsfromotherEUcountries)(欧洲药品管理局包括MHRA英国药管局和其它欧盟国家的对等机构)食品与药物监督管理局MCC(MedicineControlCouncil)药品控制委员会 -如不符合管理规定,

5、任何人都有权拒绝。MHRANIHS(NationalInstituteofHealthScience)(国立环境健康科学研究院)HCSC(HealthCanadaSante Canada)加拿大卫生部SFDA(ChineseFDA中国的FDA)Industry Regulators行业监管机构- Regulate to ensure safety of drugs that any of us might take!-通过管理保证我们任何人都可能用到的药品的安全- All have the power to refuse imports if their regulations are not

6、 met.US FDA Automated processes. When computers or automateddata processing systems are used as part of productionor the quality system, the manufacturer shall validatecomputer software for its intended use according to anestablished protocol. All software changes shall bevalidated before approval a

7、nd issuance. These validationactivities and results shall be documented.自动化过程。当计算机或自动数据处理系统做为生产或质量系统的一部分时,制造商需要验证计算机软件系统是按照预先设计使用的。所有软件变更在准许使用前是可验证的。这些验证的活动和结果应该被文档记录。PART 820 QUALITY SYSTEM REGULATION质量系统规则第820部分EMEA Validation: The extent of validation necessary will depend on anumber of factors i

8、ncluding the use to which the system is to be put,whether the validation is to be prospective or retrospective andwhether or not novel elements are incorporated. Validation should beconsidered as part of the complete life cycle of a computer system.This cycle includes the stages of planning, specifi

9、cation,programming, testing, commissioning, documentation, operation,monitoring and modifying.验证:验证的范围基于一组包含应用于系统的因素,无论验证是预见性的还是回顾性的,无论有无新元素的使用。验证应该被认为是计算机系统完整生命周期的部分。这个周期包括设计,规范,编程,测试,调试,文档,运行,监控和修改。Commission Directive 3003/94/ECAnnex 11 Computerised system3003/94/EC调试指令附录11计算机系统SFDA Where automat

10、ed and monitoring systems are used for theseapplications they should be validated to ensure that critical processrequirements are met.使用自动化和监视系统的地方,应该被验证以确保满足关键过程要求Good Manufacturing Practice for pharmaceutical products, Part IIAnnex (Draft for Comment) Chapter 12 Terminal Sterilisation:药品生产质量管理规范第二

11、部分附录(征求意见稿)第12章最终灭菌Addition补充第110条(第1次的是115条款):使用计算机化仓储管理的,应有相应的操作规程防止因系统故障、停机等特殊情况而造成物料和产品的混淆和差错。第164条(第1次的是172条款):如使用电子数据处理系统、照相技术或其它可靠方式记录数据资料,应有所用系统的详细规程;记录的准确性应经过核对。如果使用电子数据处理系统,只有受权人员方可通过计算机输入或更改数据,更改和删除情况应有记录;应使用密码或其它方式来限制数据系统的登录;关键数据输入后,应由他人独立进行复核。用电子方法保存的批记录,应采用磁带、缩微胶卷、纸质副本或其它方法进行备份,以确保记录的安

12、全,且数据资料在保存期内应便于查阅。来源:sFDA药品生产质量管理规范送审版 第2次 Purpose 目的 Cost effective framework of good practice to ensure thatcomputerised systems are fit for the intended use andcompliant applicable regulations良好实践的有效架构以保证计算机系统是满足使用要求和顺从规章要求的 Safeguard: Patient safety, products quality, & dataintegrity保证条款:患者安全,产品

13、质量和数据完整 Provide suppliers guidance on the development andmaintenance of the systems by following good practice.通过良好实践,为供应商提供系统开发和维护的指导Key Concepts关键概念求非常重要 basisformakingriskbaseddecisions.是根据风险作出决定的基础EnduserSHOULDdothefollowing:最终用户应a)IdentifyCriticalQualityAttributes(CQAs)fortheirproductduringdrug

14、development. 在药开发过程中确定其产品的关键质量属性CriticalQualityAttributesforaTablet?片剂的关键质量属性?purity,potency,stability纯度、效价、稳定性.b)ClassifyCQAs intermsoftheireffectonpatientsafety.根据其对患者安全的影响对关键质量属性进行分类ImpactonPatientSafety?对患者安全的影响?purity,potency,stability allhighimpact纯度、效价、稳定性都具有很高的影响GAMP5 KEY CONCEPTS 1- product

15、/Process Understanding GAMP5关键概念-对产品/工艺的理解 fundamentaltodeterminingsystemrequirements.对决定系统要EnduserSHOULDdothefollowing:最终用户应:c)IdentifymaterialattributesandprocessparameterswhichmightaffectanyoftheCQAs 确定能够对任何关键质量属性产生影响的的物料属性和工艺参数e.g.MaterialAttributes/ProcessParametersaffectingPURITY?例如,能够影响纯度的物料属

16、性/工艺参数purityoftheinputmaterials;temperatureofprocessing;ambienthumidity/temperature;cleanlinessofequipment原材料的纯度;工艺温度;环境温湿度;设备的洁净度d)Investigatethedesignspaceforeachattribute/parameterinordertoratetheircriticality.对每项属性/参数的设计空间进行研究以判定其关键性e.g.Howmuchcanambienthumidity/temperaturevarywithoutaffectingth

17、etabletstability?例如,在不影响片剂稳定性的情况下环境温湿度的允许变化范围是多少?GAMP5 KEY CONCEPTS 1- product/Process Understanding GAMP5关键概念-对产品/工艺的理解EnduserSHOULDdothefollowing:最终用户应:e)Usedthatinformationtoproposeacontrolstrategyfortheprocess.通过这种信息来提出工艺的控制策略。e.g.ControlStrategyforAmbientT/RH?例如,环境温湿度的控制策略?GAMP5 KEY CONCEPTS 1-

18、 product/ProcessUnderstanding GAMP5 关键概念-对产品/工艺的理解f)CreateaURSsplittingthatcontrolstrategyintoindividualfunctions(relatedtoCPPs andclassifiedaccordingtotheirimpact).编写URS,将这种控制策略分配到单独的控制功能中(与工艺参数相关并根据其影响进行分类)。Planning cover: 计划包含activities, Responsibility, procedures &time lines活动,责任,流程和时间表Specifica

19、tion: 规范enable system to be developed,verified & Maintained. It maybesupplied by a supplier使系统可以被开Verification验证Normal case (+ve testing), Invalidcase (-ve testing), Repeatability,Performance, Volume/load,Regression, Structural testing常规,非法,重复,性能,负载,不变,结构性测试Validation report: 验证报告Summerising activit

20、ies performed,deviations, outstanding and correctiveactions 总结执行的活动,偏差,超标和动作纠正GAMP5 KEY CONCEPTS 2- Life cycle approach within a QMSGAMP5 关键概念2-质量管理系统内的生命周期法Tabletmanufacturingsystem片剂生产系统Waterforinjectionsterilisationsystem注射用水灭菌系统Buildingmanagementsystem楼宇控制系统Wastetreatmentsystem废物处理系统Ointmentmixi

21、ngvessel膏剂混合罐 214(indirectimpactonly)仅间接影响5(noimpact)无影响3GAMP5 KEY CONCEPTS 2- Life cycle approach within a QMSGAMP5 关键概念2-质量管理系统内的生命周期法Lifecycleactivitiesshouldbescaledaccordingto:应从如下方面对生命周期活动进行评价:a)systemimpactonpatientsafety,productqualityanddataintegrity系统对患者安全、产品质量和数据完整性的影响。e.g.Rankthesecontro

22、lsystemsintermsofimpact:例如,根据其影响性对如下控制系统进行排序:Underlyingoperatingsystemandnetworkinfrastructure操作系统和网络基础架构StandardpackagesuchasSiemenWinCC 如西门子WinCC等标准包FirmwaresuchasPLC如PLC等固件ConfiguredelementsuchasfunctionBlocks如功能块等配置元件Bespokecodedsequence,ladderlogic,C+protocolconversion,etc定制编码序列、梯形逻辑、 C+ 协议转换等

23、GAMPCategory1第1类GAMPCategory3第3类GAMPCategory3第3类GAMPCategory4第4类GAMPCategory5第5类GAMP5 KEY CONCEPTS 3- Scalable Life Cycle ActivitiesGAMP5 关键概念3-可增减生命周期活动Lifecycleactivitiesshouldbescaledaccordingto:应从如下方面对生命周期活动进行评价:b)systemcomplexityandnovelty 系统的复杂性和新颖性e.g.Rankthesesoftwaremodulesintermsoftheintri

24、nsicrisktheyposeduetocomplexity/novelty:例如,根据因为复杂性/新颖性而具有的内在风险对如下软件模块进行排序:“ApplicationofQualityRiskManagementenablesefforttobefocusedoncriticalaspectsofacomputerizedsystem,inacontrolledandjustifiedmanner”进行质量风险管理使我们能够以受控且可以论证的方式将工作重点集中在计算机系统的关键领域。进行初步风险分析并确定系统的影响确定对患者安全、产品质量和数据完整性具有影响的功能进行功能风险分析并确定控

25、制方法执行并检查确认适宜的控制方法审查风险并监控控制效果GAMP5 KEY CONCEPTS 4- Science Based Quality Risk ManagementGAMP5 关键概念4-根据科学进行的质量风险管理“Regulatedcompaniesshouldseektomaximisesupplierinvolvement throughoutthesystemlifecycleinordertoleverageknowledge,experience anddocumentation,subjecttosatisfactorysupplierassessment ” “在进行

26、了很好的供应商评估之后,符合监管要求的公司应在系统的整个生命周期内尽量利用供应商的参与以充分利用其知识、经验和文件。”GAMP5 KEY CONCEPTS 4- Science Based Quality Risk ManagementGAMP5 关键概念4-根据科学进行的质量风险管理WhatdoesAustarhavetooffer?奥星所能提供有:Knowledge: processcontrolexpertise知识: 工艺控制专有技术Experience: validatingcontrolsystemstoGAMP经验: 根据GAMP对控制系统进行验证Documentation:co

27、mprehensivetemplatedocuments文件综合模版文件 planning计划 specification规范 verification确认 reporting报告 Process Owner: The person ultimately responsible for the businessprocess or processes being managed过程所有者:为最终生产或被管理的过程而负责的人 System Owner: The person ultimately responsible for theavailability , support, and mai

28、ntenance of a system and for thesecurity of the data residing on that system系统所有者:为系统的可用性,支持和维护,及系统上数据安全性而负责的人 Subject Matter Expert: Those individuals with specific expertise in aparticular area or field. SME should take the lead role in theverification of computerised systems. SME responsibilities

29、 includeplanning and defining verification strategies, defining acceptancecriteria, selection of appropriate test methods, execution ofverification tests and reviewing results领域专家:在某一领域有某特定技术的人。SME应该引导计算机系统的验证。SME责任包括计划和定义验证策略,定义验收标准,选择合适的测试方法,执行验证测试和审核结果Key Personnel关键人Benefits to both regulated co

30、mpanies & supplier:公司和供应商均得到的益处 Reduction of cost & time taken to achieve and maintain compliance降低实现和维护一致性的费用和时间 Early defect identification and resolution: reduce cost, speed早期的辨识和解决:降低费用,提高速度 Cost effective operation and maintenance高效运行和维护 Effective change management and continuous improvement有效的

31、变更管理和持续性改进 Providing framework for user/supplier co-operation为用户/供应商协作提供框架 Assisting suppliers to produce required docs协助供应商生产要求文档 Promotion of common life cycle, language, and terminology建立常用生命周期,语言和术语 Providing practical guides and examples提供实用的指南和例子Business Benefit 益处 Risk Management风险管理 Change &

32、 Configuration Management变更和组态管理 Design Review设计审核 Traceability追溯性 Document Management文档管理Supporting Processes 支持过程Computerised System Life Cycle计算机系统生命周期Project Stages项目阶段 Identify Compliance standards based on company procedure基于公司流程辨识出一致性标准 GxP Assessment GxP评估 Identify Key Individuals: Process O

33、wner, System Owner, Quality Unit, SME,Supplier, End User标识关键人 Produce User requirement Specification书写URS Determine Strategy for Achieving compliance: Risk Assessment,Assessment of System component, Supplier assessment决定达成一致的策略:风险评估,系统组件评估,供应商评估 Plan计划 Review and Approve Specifications审核和批准规范 Develo

34、p test strategy开发测试策略 Test测试 Report & release报告和发布 Maintain system compliance during Opeartion运行时系统一致性维护 Retirement退役 Regulated Company Activities公司活动 Establish QMS: Documented set of procedures & standards建立质量管理系统:一组流程和标准文档 Establish Requirement (what end user wants)建立需求(最终用户需要什么) Quality planning质

35、量计划 Assessment of sub-supplier分包商评估 Produce specifications书写规范 Perform design review执行设计审核 Hardware & Software production/configuration软硬件生产及组态 Perform testing执行测试 Commercial release of the system系统发布 Provide user requirement and training提供用户需求和培训 Support and maintain the system in operation运行中,支持和维

36、护系统 System Retirement and replacement系统退役和取代Supplier activities供应商活动V-model 验证生命周期和文件架构IF ITS NOT DOCUMENTED ITS A RUMOUR!如果没有被记录下来,一切都是流言!计算机系统的验证实施用户需求说明URSVPQPPRAChangeControl用户需求说明属于客户方文件。文件中列出了客户在本项目系统方面的所有要求。它是编写功能说明(FS)的基础验证计划验证计划是一份描述了整个项目的总体验证策略的文件并列出了客户的监管和质量要求。质量和项目计划质量和项目计划界定了奥星为满足客户的需求在

37、执行项目过程中所采取的质量措施。另外它还列出了项目的结果和项目计划工作。风险评估项目范围内将包括一个风险评估的过程。此风险评估过程界定出了用于控制对GMP要求或客户业务有影响的风险的必要措施。必须确定出这些风险并对其进行评估、文件记录。最后,必须界定出降低这些风险所必须执行的措施并对其进行追踪。变更控制所有能够影响已经批准的文件的系统变更均需根据变更控制规程来进行控制。为了保证可以证明所有这些变更均符合计划、经过评估、批准、并根据符合GMP的形式得以实施并通过文件方式进行了记录,将编写一份项目SOP来界定控制变更时所需进行的工作。 计算机系统的验证实施功能说明功能说明(FS)中描述了如何来实现

38、用户需求说明(URS)中所述的要求和目标。本文件FSDSQPDeviationManagement明确说明了预期系统的实现方式。FS由项目执行方编写,由客户进行审查是否有与URS中所述要求有冲突之处及是否确实能够实现此类要求。FS必须由客户来批准。经过批准之后,FS即作为客户和项目执行方在实现及管理本项目方面具有约束力的协议。设计说明设计说明以更为详细的方式说明了应该如何来在系统中实现各种功能。其中既涉及到硬件说明又涉及到软件说明。确认计划从监管的角度来看以及为了控制风险,必须针对相关的要求进行测试。整套测试在不同的测试阶段进行计划、实施和报告,各阶段在本QPP中做出了说明。在确认计划中规定出

39、了这些测试工作的适宜步骤。确认计划必须考虑客户对一般情况及确认工作的要求,尤其是在URS及验证计划中所规定的要求。此外,风险评估对测试问题的范围及测试方面均具有一定的影响。偏差管理此规程保证所有偏差均必须进行记录和控制,直至它们得以纠正。在确认计划中对此规程进行了描述。 计算机系统的验证实施工厂验收测试工厂验收测试在系统实施完成之后在系统供应商的场地进行。工厂验收测试完成之后客户FATSAT-IQSAT-OQIQ应同意系统发货。进行详尽的工厂验收测试的另一个优点在于能够尽早地检测到软件编程中所存在的错误,以在客户现场安装系统之前将其纠正。客户应到场检查/见证工厂验收测试的执行。现场验收测试-安

40、装确认现场验收测试是为了证明系统根据规定进行了安装、能够在其运行环境下正常工作、且与仪表及设备的界面符合规定。因为现场验收测试的重点在于安装及功能方面,所以进一步被划分为SAT-IQ和SAT-OQ。SAT-IQ是为了证明系统被正确地在客户的目标环境中进行了安装。现场验收测试-运行确认SAT-OQ属于现场验收测试的一部分,它是为了证明系统能够在其运行环境下正常运行,且其与仪表和设备的界面符合规定。安装确认与SAT-IQ相比,IQ应由客户来负责进行。必须要证明系统根据技术说明进行了正确的安装(硬件和软件)。除了SAT-IQ中已经进行的测试之外,IQ中需要包括一些由客户所增加的测试。 计算机系统的验

41、证实施运行确认OQQRVRTM与SAT-OQ相比,OQ应由客户来负责进行。必须要证明系统具有符合技术说明的正确功能。除了SAT-OQ中已经进行的测试之外,OQ中需要包括一些由客户所增加的,在尽可能接近生产工艺环境条件下进行的功能测试。确认报告确认报告汇总出了各单一测试阶段的结果,并报告所出现的重大或轻微偏差是否已经清除。本报告中包括所有测试阶段是否充分完成以及系统是否得以确认的结论。验证报告验证报告汇总出了单一项目阶段的整个结果,并说明了整体最终验证结果。此文件必须以客户为责任方进行编写。可追溯矩阵根据GAMP5,应建立以文件形式记录要求与说明和设计成分之间的可追溯性、以及这些成分与相应测试之

42、间的可追溯性的流程。所有要求都必须在说明文件及测试中得以考虑,不能有任何遗漏项。可追溯性矩阵可帮助项目团队在整个项目过程中审查所有与要求相关的项目。它可以在项目生命周期中双向检查并追踪要求的处理情况。 Any question?GAMP5Software & Hardware Categories软件和硬件类别Category类别TypicalApproach典型方法1,StandardHardwareComponents标准硬件部件Documentmanufacturerorsupplierdetail,serialnumberandversionnumber通过文件记录下生产厂家或供应商的

43、详情、序列号和版本号Correctinstallationtobeverified确认正确的安装ConfigurationManagementandChangecontrolapply适用配置管理和变更控制2,CustomBuiltHardwareComponents定制制造的硬件部件Asperaboveplus:上述内容再加上:Designspecification设计说明Acceptancetesting验收测试ConfigurationandChangecontrolapply适用配置和变更过控制GAMP 5 Hardware Categories 硬件类别Category类别Descr

44、iption说明Typicalexamples典型示例TypicalApproach典型方法1,InfrastructureSoftware基础设施软件Layeredsoftware分层式软件Softwareusedtomanagetheoperatingenvironment用于管理操作环境的软件Operatingsystems操作系统Databaseengines数据库引擎Middleware中间件Programminglanguages编程语言Spreadsheets电子制表软件Versioncontroltools版本控制给你工具Networkmonitoringtools网络监控工具

45、Recordversionnumber,verifycorrectinstallationbyfollowingapprovedinstallationprocedure记录版本号,按照所批准的安装规程验证正确的安装方式。3,Non-configured非配置软件Runtimeparametersmaybeenteredandstored,butthesoftwarecannotbeconfiguredtosuitthebusinessprocess可以输入并储存运行参数,但是并不能对软件进行配置以适合业务流程Firmwarebasedapplications基于固件的应用程序COTssoft

46、wareCOTS软件AbbreviatedLifecycleapproach简化的生命周期法URS用户需求说明Riskbasedapproachtosupplierassesment基于风险的供应商评估方Recordversionnumber,verifycorrectinstallation记录版本号,验证正确的安装方式Riskbasedtest基于风险进行测试Procedureinplaceformaintainingcompliance有用于维持系统符合性的规程GAMP 5 Software Categories 软件类别Softwarethe GAMP 5 Software Categ

47、ories 软件类别Category类别4,configured 可配置Description说明Software,often verycomplex, thatcan beconfigured bythe user tomeet thespecific needsof the usersbusinessprocess.Software codeis not altered这种软件通常非常复杂,可以由用户来进行配置以满足用户具体业务流程的特殊要求。这种软件的编码不能更改。Typical examples典型示例DAQ systemsSCADADCSBMSHMILIMSERPClinical t

48、railmonitoringTypical Approach典型方法Life cycle approach生命周期法Risk based approach to supplier assessment基于风险的供应商评估法Supplier QMS供应商的质量管理系统Record version number, verify correctinstallation记录版本号,验证正确的安装方式Risk based testing in a test environment在测试环境中根据风险进行测试Risk based testing within the businessprocess在业务流

49、程中根据风险进行测试Procedure in place for maintainingcompliance具有维持符合性的规程5, Custom定制Internally,custom externally developeddesigned and IT coded to suit 和外部开发的IT应用程business 序processSame as cat 4 plus 与第4类相同,再加上More rigorous supplier assessment, withpossible supplier audit更严格的公用设施评估,包括可能进行供应商审计Possession of fu

50、ll life cycle 完整的生命周Software Category 3 第3类软件Software Category 4 第4类软件Software Category 5第5类软件GAMP5 Planning Phase 计划阶段URS用户需求说明User Requirement Specification用户需求说明Most important document最重要的文件Describes what the system is supposed to do描述系统预期用途Normally written by the Supplier 通常由供应商编写Controlled Docu

51、ment 受控文件For Cat 3 written for a specific solution 第3类针对具体解决方案编写For Cat 4 & 5 It is written in general 第4、5类整体编写Sufficient, Realistic, Measurable, Achievable充分、现实、可衡量、可达到 Testable: Clear, Precise, basis for formal testing 可测量:清楚、简洁、正式测试的基础 Traceable: Design and testing可追溯:设计和测试 Define priority: Mand

52、atory, Beneficial, Nice to have 规定优先级:必须、有益、有了更好URS-Content 用户需求说明-内容 Introduction: 介绍 Who produced the document 文件编写人 Contractual status 合同状态 Relationship to other document 与其它文件关系 Overview: Background to the project 概述:项目背景 Scope: 范围 System boundaries 系统范围 Key objective and benefits 关键目标和益处 Applic

53、able GXP requirement适用GXP要求 Other applicable regulations 其它适用法规URS-Content: Operational RequirementURS-内容:操作要求 Functions功能 What is the system require to do 系统要求的功能 Calculations计算 Modes of operation (Use Cases) 操作模式(使用示例) Alarms报警 Failure Modes 故障模式 Safety安全 Electronics Records, Audit Trail, & Electr

54、onicsSignature电子记录、审计跟踪、电子签名 Reports, data files, etc 报告、数据文件等URS-Content: Operational RequirementURS-内容:操作要求 Data数据 Data handling requirement (Paper, Electronics) 数据处理要求(物理版、电子版) Data impact 数据影响 Definition of data: format, critical parameters, data range limits, requiredaccuracy, etc 数据的定义:格式、关键参数

55、、数据范围、所要求准确性等 Electronics Records, Audit Trail, & Electronics Signature电子记录、审计跟踪、电子签名 Reports, data files, etc报告、数据文件等 Data migration数据迁移 Data input and subsequent editing数据输入及之后的编辑 Back up & recovery 备份和恢复 Archive requirement存档要求 Data Security and integrity 数据安全和完整性URS-Content: Operational Requirem

56、entURS-内容:操作要求 Technical requirement技术要求 Startup, shutdown, Cold start, Warm start, Hot start启动、停机、冷起、暖起、热起 Disaster recovery灾难恢复 Performance and timing requirement性能和计时要求 Action on Component failure 对部件故障的措施 Hardware requirement 硬件要求 Portability 便携性 Efficiency 效率 Configurability 可配置性URS-Content: Op

57、erational RequirementURS-内容:操作要求 Interfaces 界面 I/O listing I/O列表 Interface to other systems/equipment 与其它系统/设备界面 HMI Users groups and their access rights 用户组及其访问权限 Network protocols supported: serial, OPC, Profibus 所支持网络协议:序列、OPC、 Profibus Environment 环境 Physical condition: Temp, Humidity, Hazardous

58、 物理环境:温度、湿度、危害 Physical space and limitations 物理空间和局限 Utilities公用工程 URS-ContentURS-内容: Constraints 限制条件 Availability ( redundancy?) & reliability 可用性(冗余?)和可靠性 Expansion capability 扩展容量 Future expansion 未来扩展 Expected life time 预期使用寿命 Long term support 长期支持URS-ContentURS-内容: Life Cycle requirement 生命周

59、期要求 Development requirement: GAMP 5 开发要求:GAMP5 Supplier Quality requirement 供应商质量要求 Documentation requirement文件要求Testing Requirement: Internal testing, FAT, SAT测试要求:内部测试、FAT、SATTraining 培训 Support and maintenance service 支持和维护服务 Spares 备件 Any question?GAMP5 Planning PhaseGAMP5计划阶段Quality and Project

60、 Plan质量及项目计划Quality Plan质量计划 A Quality Plan is a key document in defining the project lifecycle. It sets outthe proposed method of meeting the user quality requirements and allowsagreement of the controlling procedures for each project activity. 质量计划是一个关键文件,它界定了项目的生命周期。规定出了为了满足用户质量要求所提议采取的方法,使各项项目工作

61、符合控制规程的要求。 Quality Plan is the responsibility of the supplier 质量计划属于供应商的责任 It should normally be supplied within the first week of signing contract. 一般需在签订合同之后一周内提供 It is written in response to Validation Plan 应作为对验证计划的响应而编写 It needs to be approved by User. 需要由用户来批准 Generally once approved should no

62、t require further revision. 一般批准之后不需再进行修订QP- Contents QP-内容 Relationship to other Documents 与其它文件关系 Applicable standard 适用标准 Relationship to customer Validation Requirements 与客户验证要求之间关系 Non-Conformance with User Requirement 与用户需求的不符合项 Relationship t Project overview 项目概述 Summary of Process to be con

63、trolled 所需控制工艺概述 Relevant GxP regulations 相关GxP法规 Impact on Patient Safety, Product Quality, data integrity对患者安全、产品质量和数据完整性的影响 Project boundaries and interfaces (scope of supply and validation项目范围和接口(供货范围和验证) System Architecture 系统结构 System classification: Hardware and software categories 系统分类:硬件和软件

64、类别QP-Contents QP-内容 Project Life Cycle phases项目生命周期阶段 It should follow GAMP5 Life Cyclemodel 应遵循GAMP5所规定生命周期模型 List what activities will be performed列出所需进行工作 Defines who will be responsible forexecuting each activity 确定执行每项工作的负责人 The level of activity depends on thedegree of novelty 工作的内容取决于新颖性程度 De

65、pending on the size andcomplexity, some documents may bemerged into a single one 根据规模和复杂性,有些文件可以合为一个文件 Documents created need to bereviewed and approved by end user所编写文件需要由最终用户审核批准 计划技术说明报告检查确认配置和编码包括风险管理在内的支持性流程QP-Contents Project Life CycleQP-内容-项目生命周期 Planning Phase计划阶段Review of URS审核URSCreation

66、of Project schedule and approval编制并批准项目进度时间表Creation of Quality Plan and approval编写和批准质量计划QP-Contents Project Life CycleQP-内容-项目生命周期 Specification Phase 技术说明阶段 Creation of Functional Design and Approval 编写并批准功能设计说明 Creation of Hardware Design including Drawings and approval 编写并批准硬件设计说明,包括图纸 Risk Ass

67、essment 风险评估 Creation of Software Design and approval 编写并批准软件设计说明 Creation of Software Module design and approval 编写并批准软件模块设计说明LifecyclePhase生命周期阶段Infrastructuresoftwareelement基础设施软件组件Non-configuredsoftwareelement不可配置软件组件Configuredsoftwareelement可配置软件组件Bespokesoftwareelement定制软件组件Specification技术说明Fu

68、nctionalSpecification(mayalsodetaildesignandconfigurationonasimple/lowrisksystem)功能说明(对于简单/低风险系统也可详细描述设计和配置情况)HardwareDesignandConfigurationSpecificationifjustifiedbyHIGH/MEDIUMriskpriorityorbythecomplexityofthehardware如根据高/中风险优先级别或硬件的复杂性判定需要,编写硬件设计说明和配置说明SoftwareDesignandConfigurationSpecificationi

69、fjustifiedbyHIGH/MEDIUMriskpriorityorbythecomplexityofthesoftware如根据高/中风险优先级别或软件的复杂性判定需要,编写软件设计说明和配置说明SoftwareModuleSpecificationifjustifiedbyHIGH/MEDIUMriskpriorityorbythecomplexityofthesoftware如根据高/中风险优先级别或硬件的复杂性判定需要,编写软件模块设计说明Forallcategoriesofsoftware,settingsandparameterswhicharecriticaltomeeti

70、nguserrequirementsaredetailedwithinthedocumentation.Allothersettingsandparametersarecontrolledelectronicallyviabaselinesofthesoftwaretakenpriortoeachverificationphaseandatprojecthandover.TheashandedoversettingsandparametersaresuppliedtotheenduserwithinthesoftwarebaselineonCD/DVD.Subsequentmodificati

71、onsmadeon-linearecontrolledviatheaudittrail.Subsequentmodificationsmadeoff-linearecontrolledviatheconfigurationmanagementsystemandresultinanewbaselinebeingtaken.针对所有类别的软件,在文件中详细说明符合用户需求所需的关键设定和参数。所有其它设定和参数均根据在每项验证阶段之前及项目移交时所记录的软件基线情况通过电子方式进行控制。将“移交”设定和参数和软件基线情况记录在CD/DVD上交付给最终用户。随后的任何在线更改均通过审计跟踪进行控制。

72、随后的任何离线更改均通过配置管理系统进行控制并形成新的记录基线。Scalability of Activities 工作的可放大性QP-Contents Project Life CycleQP-内容-项目生命周期 Configuration and Coding Phase 配置和编码阶段 Order Hardware 订购硬件 Build System 构建系统 Develop software 开发软件 Produce configuration schedule and Configuration management 制定配置计划时间表和配置管理 Integrate the syst

73、em 集成系统QP-Contents Project Life CycleQP-内容-项目生命周期 Verification Phase 验证阶段 Software Code Review 软件代码回顾 Create Software Module Test Protocol and approve 编写并批准软件模块测试方案 Create Factory Acceptance Test spec Protocol and approve (hardware andSoftware) 编写并批准工厂验收测试规程和方案(硬件和软件) Create Site Acceptance Test Pro

74、tocol and approve 编写并批准现场验收测试方案 Execute Internal Software Module Test and review result 执行内部软件模块测试并审查结果 Execute Internal FAT test and review result 执行内部FAT测试并审查结果 Execute witnessed FAT test and review result 执行并见证FAT测试并审查结果 Ship to site 运至现场 Install and commission 安装调试 Execute Site Acceptance Test a

75、nd Review result 执行现场验收测试并审查结果QP-Contents Project Life CycleQP-内容-项目生命周期 Reporting Phase 报告阶段 Generate system final documentation, review & approve 生成系统最终文件并进行审批 Ensure all the design documents are “as Built” version 保证所有设计文件均为“竣工”版本 Create technical manual 编写技术手册 Provide Training for Operators, eng

76、ineers, etc 为操作人员、工程师等进行培训 Generate Final Quality report and Handover checklist, review andapprove 生成最终质量报告和移交检查表并进行审查 Complete handover 完成移交QP-ContentsQP-内容 Supporting Activities 支持性工作Traceability 可追溯性Change Management 变更管理Configuration Management 配置管理 Items to be controlled 所需控制项目 Version control

77、版本控制Documentation Management 文件管理 Version control 版本控制 Documents to be provided and format 所需提供文件及其格式项目进程报告Project Mile stones项目里程碑QP-ContentsQP-内容 Project Planning 项目计划Project team and its organisation项目团队及其组织Project progress reportingGloryHeProjectManager(PM)(nominatedprimarycontact)(responsiblefo

78、rvalidation)MattSafiValidationconsultantHardwareEngineersIvanGaoAliceLvSoftwareEngineer(s)AliceLvElaineWangQualityManager(QM)QualityAssurance(QA)GloryHeLeadEngineer(LE)DrawingOffice(DO)IvanGaoAny question?GAMP5 Planning PhaseRisk AssessmentGAMP5计划阶段风险评估Risk Assessment风险评估 Identify Critical Quality A

79、ttributes (CQAs) for product during drug development. Theseare attributes like purity, potency, stability which are intrinsic to the 程中确定关键质量属性(CQA)。例如对产品而言非常重要的纯度、效价、稳定性。 Classify these CQAs in terms of their effect on patient safety根据关键质量属性对患者安全性的影响对其分类。 Identify material attributes and process pa

80、rameters which might affect any of the CQAs(eg purity might be affected by: purity of the input materials; temperature of processing;cleanliness of equipment). 确定可能会影响任何关键质量属性(例如纯度可能会受输入原料的纯度、工艺温度、设备洁净度等影响)的材料属性和工艺参数 Identify the Design Space for those material attributes and process parameters (ied

81、etermine how they can vary whilst still giving good quality product) in order to determinewhich are Critical Material Attributes or Critical Process Parameters (CPPs) and to giveeach an impact rating确定这些物料属性和工艺参数的设计空间(即确定在保证良好产品质量的同时其所允许的变化范围)以确定哪些是关键质量属性或关键工艺参数并对其进行影响性评定 Use that information to pro

82、pose a control strategy for the process which will guaranteeoperation within the design space and also guarantee that any necessary data to provethis is collected. 使用该信息为将保证操作在设计空间范围内并保证收集了证明这一点的数据的流程而提出的控制策略 Create a URS which splits the control strategy into individual functions (related to critic

83、alprocess parameters) and classified according to their impact on product quality / patientsafety / data integrity. 编制URS将该控制策略分为各单独的功能(与关键工艺参数相关)并根据其对产品质量/患者安全性/数据完整性的影响将其分类。Risk Assessment风险评估 Risk Assessment report details the risk assessmentand mitigation process throughout the projectlifecycle.

84、风险评估报告详细描述了整个项目周期中风险评定和 Risk Assessment is the responsibility of the user,supported by supplier风险评估是用户的责任,受供应商的支持 Risk Assessment is a continuous process and mustbe carried out at various stages during system lifecycle风险评估是一个连续的过程,在系统生命周期的不同阶段都要执行RA- Contents 风险评估-内容 Relationship to other Documents与

85、其它文件的关系 Applicable standard适用标准 Relationship to customer User RequirementsSpecification与客户用户需求说明之间关系 Project overview项目概述 Summary of Process to be controlled所需控制工艺概述 Relevant GxP regulations相关GxP法规 Project boundaries and interfaces (scope of supply andvalidation项目范围和界面(供货范围和验证) System Architecture系统

86、结构 System classification: Hardware and softwarecategories系统分类:硬件和软件类别Probabilityofafailure?故障可能性?Delectabilityofafailure?故障可检测性?Howriskmanaged?风险如何控制进行功能性风险评估并确定控制模式实施并确认适宜控制审查风险并监控控制 Quality Risk Assessment质量风险评估 Is it GxP?是否属于GxP What hazards?有什么危害? Impact level?影响级别?进行最初风险评估并确定系统影响确定对患者安全、产品质量和数据

87、完整性有影响的功能Doesthesystemgenerate,manipulateorcontroldatasupportingregulatorysafetyandefficacysubmissions?系统是否生成、处理或控制用于支持法规安全性和功效提交文件的数据?Yes/NoDoesthesystemcontrolcriticalparametersanddatainpreclinical,clinical,development,ormanufacturing?系统是否控制临床前、临床、开发或生产相关关键参数和数据?Yes/NoDoesthesystemcontrolorprovide

88、dataorinformationforproductrelease?系统是否控制或提供有关产品放行的数据或信息?Yes/NoDoesthesystemcontroldataorinformationrequiredincaseofproductrecall?系统是否控制与产品召回相关要求的数据或信息?Yes/NoDoesthesystemcontroladverseeventorcompliantrecordingorreporting?系统是否控制不良事件或投诉的记录或报告?Yes/NoDoesthesystemsupportpharmacovigilance?系统是否支持药物安全监视?Y

89、es/NoGxP Assessment GxP评估71Worstcaseimpactonpatientsafety对患者安全的最差情况影响High=potentialforseriousinjuryordeathMedium=potentialforminorinjuryLow=potentialfor高=可能造成严重伤害或死亡中=可能造成轻微伤害低=可能Worstcaseimpactonproductquality对产品质量的的最差情况影响High=potentialforreleaseofproductwhichwouldcauseseriousinjurytoapatient高=可能放行

90、可能导致患者严重伤害的产品Medium=potentialforreleaseofproductwhichwouldcauseminorinjurytoapatient中=可能放行可能导致患者轻微伤害的产品Low=potentialforpoorqualityproductwhichwouldnotbereleasedorwouldnotcauseharmtopatient低=可能导致产生不会放行或是不会对患者造成伤害的低质量产品Worstcaseimpactondataintegrity对数据完整性的的最差情况影响High=lossofdataintegritysuchthatproduct

91、recallcouldnotbecarriedoutorreleasecouldbemadeofproductwhichwouldcauseseriousinjurytoapatient高=数据完整性丧失导致不成召回产品或是放行能够对患者造成严重伤害的产品Medium=lossofdataintegritysuchthatreleasecouldbemadeofproductwhichwouldcauseminorinjurytoapatient中=数据完整性丧失导致放行能够对患者造成轻微伤害的产品Low=lossofdataintegritysuchthatproductwouldneedt

92、obescrappedordatarecordsnotessentialtoproductreleaseorrecallmightbelostorimpaired低=数据完整性丧失导致产品作废或数据记录对产品放行不重要或召回不能或困难System Impact Classification系统影响性分类72GxPCriticalGxP关键Yes/No是/否ImpactLevel影响级别High/Medium/Low高/中/低System Classification 系统分类73Risk assessment method风险评估方法Identification of Controls确定控制

93、 The output of the risk assessment process (risk priority) is used todecide upon appropriate controls. A range of options is available toprovide the required control depending on the identified risk. Theseinclude, but are not limited to:风险评估过程目的是采用合适的控制;依据所辨识出的风险级别可通过一组选项实现控制,这些选项包括以下但不局限以下: Modific

94、ation of process design or system design修改流程设计或者系统设计 Application of external procedures通过外部程序 Increasing the detail or formality of specifications增加规范细节 Increasing the number and level of detail of design reviews增加复查的级别和次数 Increasing the extent or rigor of verification activities增加外部的和严格的验证行动Risk Ma

95、nagement Throughout the Life Cycle整个生命周期过程中的风险控制Any question?GAMP5 Planning PhaseGAMP5计划阶段Functional Specification功能说明Functional Specification功能说明 A Functional Specification is a key document in defining how the customerfunctional requirements, as defined in the user requirements specification,are t

96、o be met. 功能说明是一种重要的文件,界定了是如何来满足在用户需求说明中所规定的客户功能要求的。 Functional Specification is the responsibility of the supplier功能说明属于供应商的责任It is written in response to URS需要根据URS进行编写It provides the main basis for FAT它提供了FAT的主要基础It needs to be approved by User. 需要用户批准 Generally may require further revision durin

97、g the project life cycle. 一般在项目生命周期过程中需要进行修订 FS- Contents FS-内容 Relationship to other Documents 与其它文件的关系 Applicable standard适用标准 Relationship to customer URS与客户URS之间关系 Non-Conformance with User Requirement与用户需求的不符合项 Project overview项目概述 Summary of Process to be controlled所需控制工艺概述 Relevant GxP regula

98、tions相关GxP法规 Impact on Patient Safety, Product Quality, data integrity对患者安全、产品质量和数据完整性的影响 Project boundaries and interfaces (scope of supply and validation)项目界限和接口(供货范围和验证) System Architecture系统结构 System classification: Hardware and software categories系统分类:硬件和软件类别 Assumptions and restrictions 假设和限制F

99、S-Contents-FunctionsFS-内容-功能 Functions 功能 Continuous control 连续控制 Purpose 目的 Operation 操作 Critical parameters involved所涉及关键参数 GxP criticality/impact rating GxP关键性/影响评定 What equipment it controls 所控制设备 Category of software 软件类别 Error handling and data checking错误处理和数据检查 Interface to other modules与其它模块

100、的界面Purposeoffunction功能目的Pressurelooptocontrolthedifferentialpressureofthechamber控制腔体压差的压力回路Criticalprocessparameters关键工艺参数ChamberpressurecriticaltotheoperationofSterilizer.ItmustbecontrolledfromthePressurisephasetoDe-pressurisephase.Itiscontrolledto5Pasetpoint腔室压力对灭菌柜的压力非常关键。必须在从加压阶段到放压过程期间进行控制。需要控制

101、在设定点的5Pa。GxPCritical?对GxP是否关键?Yes是ImpactratingfromURS从URS的影响评级Low低Relatedplantequipment相关工厂设备Inputsignal:ChamberdifferentialPressuresignalPT1.Itmeasuresthedifferencebetweenthechamberpressureandthetechnicalarea.输入信号:腔室压差信号PT1。用于衡量腔室压力和技术区压力之间的差值。Controlloop:PID控制回路:PIDOutputDevice:输出装置:ExternalFanM67

102、(VFDSC1)isusedforadjustingpressure通过外部风机M67(VFDSC1)调节压力Ventvalve(M14)isanon/Offvalvewhichisoperatedbyphasesasrequired. 排风阀(M14)为开关阀,根据各阶段要求进行操作。Categoryofsoftwareused所用软件类别4Configuredmodule4可配置模块Interfacestoothermodules与其它模块的界面None无Moduleoperation模块操作PressurecontrolloopusestheChamberdifferentialpres

103、sureinputsignalandExternalFanVFDtocontroltheChamberpressure.ItacceptsasetpointfromtheRecipeandprovidesaPIDcontrol.压力控制回路通过腔室压差输入信号和外部风机VFD来控制腔室中的压力。它从配方中获得一个设定点并进行PID控制Pressure压力Ventvalve(M14)isanon/Offvalvewhichisoperatedbyphasesasrequired. 排风阀(M14)是一个开关阀,根据各阶段要求进行操作。Pressurecontrolloopalwaysstarte

104、dautomaticallybytheCycleoperation压力控制回路总是通过循环操作自动启动Pressureloopinterlocks:压力回路有如下互锁 Pressurecontrolloopcantoperateifeitherloadingorunloadingdoorisopen 如果上料门或是卸料门在打开状态,压力回路不能运行 Emergencypushbuttonisactivated.IfthepressureisrunningthenitstopscontrollingbyFanstoppingfanandclosingventvalve 急停开关已启动。如果有压力

105、则可通过停风机并关闭排气阀停止控制 IfExternalFanmotoroverloadisonthenthepressureloopstops.Alsoheatingstops.如果外部风机电机过载开,则压力回路停止。同时停止加热Errorhandlinganddatachecking错误处理和数据检查IftheinputsignalorAnalogueModuletothePLCislostanalarmisraisedandPressurecontrolloopsstop.ThiswillalsostopthePressurecontrolloops.如果PLC输入信号或模拟模块丢失,发

106、出报警,压力控制回路停止。也将停止压力控制回路。FS-Contents-FunctionsFS-内容-功能FS-Contents-FunctionsFS-内容-功能 Functions 功能 Sequential control 顺序控制 Purpose目的 Critical parameters involved 所涉及关键参数 GxP criticality/impact rating GxP关键性/影响评级 What equipment it controls 所控制设备 Category of software软件类别 Interface to other modules 与其它模块界

107、面 Operation Flow Chart 操作流程图 Failure modes & error handling 故障模式和错误处理FS-Contents-DataFS-内容-数据 Internal Data Structure and Data Flows 内部数据结构和数据流 Describe the data structure 描述数据结构 Describe interfaces provided 描述所提供界面 Real I/O 真实I/O Modbus Profibus OPC etc FS-Contents-DataFS-内容-数据 Process Data工艺数据 Des

108、cribe the Inputs 描述输入 Where does the data originate (eg hardwired I/O, Modbus from anotherdevice, etc) ? 数据从哪里生成(例如硬件接线I/O、另一装置的Modbus 等)? What quality checking is carried out? (eg alarms on faulty I/O or commslinks) 进行什么样的质量检查?(例如故障I/O报警或comms 链接) How is the data stored (e.g. timestamped, how often

109、, what format) 数据如何存储(例如时间标记、存储频率、格式) Where is data stored? 数据存储位置? What capacity is available? 可用容量? How are live and historical data viewed? 如何查看实时数据和历史数据?FS-Contents-DataFS-内容-数据 Alarm Data 报警数据 Describe the alarms 对报警进行描述 Where does the alarm originate? 生成报警的位置? Where is it time stamped? 时间标记位置?

110、 How is the alarm stored (e.g. what information, timestamped, whatformat) 报警如何存储(例如什么信息、时间标记、格式)? Where is data stored?数据存储位置? What capacity is available?可用容量? How are the current alarm and historical alarms viewed? 如何查看当前报警和历史报警? Alarm Lists 报警清单FS-Contents-DataFS-内容-数据 Audit Trail Data 审计跟踪数据 Desc

111、ribe the Inputs 对输入进行描述 Where does the data originate?生成数据的位置? Where quality checking is carried out (format of operator entries)?需进行什么样的质量检查(操作员输入的格式)? How is the Audit Trail stored (e.g. what information, timestamped,what format) 审计跟踪如何存储(例如什么信息、时间标记、格式)? Where is data stored?数据存储位置? What capacity

112、 is available?可用容量? How are the Audit Trails viewed? 如何查看审计跟踪? Audit trail lists 审计跟踪清单FS-Contents-DataFS-内容-数据 Data Input functions specific to production生产方面具体数据输入功能 Recipes 处方 Describe the structure of recipes 对处方的结构进行描述 Recipes Configuration: new, modify an existing one, etc) 处方配置:新建、更改现有处方等) Re

113、cipe types and parametrs for each recipe 处方类型和每个处方的参数 Error checking and handling 错误检查和处理 Batch data 批数据 What Batch data required 需要什么样的批数据 Entry batch data (e.g. manually, bar code reader) 批数据的输入(例如手动、条形码读码器) Error checking and handling错误检查和处理 Calculations 计算FS-Contents-DataFS-内容-数据 Data output fun

114、ctions specific to production生产方面具体数据输出功能 Trending趋势 Live 实时 Historical 历史 Reports报告 Reports type: Shift, Daily, weekly, Batch报告类别:每班、每天、每周、每批 Report format and contents报告格式和内容 Calculations: Min, Max, Average, etc 计算:最小、最大、平均等 Report Generation 生成报告 Report archive and Retrieve报告的归档和检索FS-Contents-Dat

115、aFS-内容-数据Electronics Records & Electronics Signature, 电子记录和电子签名Compliance with 21 CFR Part 11与21 CFR Part 11 的符合性Electronics Records 电子记录 List of data to be stored electronically 需电子存储的数据清单 Electronics Signature电子签名 Describe Sign, authorisation (double signature) 对签名、权限(双重签名)进行描述 Describe Functions

116、which require Electronics signature andAccess level 对要求电子签名和访问级别的功能进行描述 Describe Parameters which require Electronics signature 对要求电子签名的参数进行描述FS-Contents-InterfacesFS-内容-界面 Process Equipment 工艺设备 I/O List 输入/输出清单Tag 标号Type类型Description 说明Range范围I/O module, Channel allocation 输入/输出模块、通道分配Display form

117、at 显示格式FS-Contents-InterfacesFS-内容-界面 Internal Network 内部网络 Network Type 网络类型 Physical connections 物理连接 Network setting 网络设定 Protocol 协议 Data to be transferred 所需传输数据 External Network 外部网络 Network type网络类型 Physical connections物理连接 Protocol conversion devices 协议转换装置 Network setting网络设定 Protocol 协议 Da

118、ta to be transferred所需传输数据FS-Contents-Interface FunctionsFS-内容-界面功能 Alarms 报警 Alarm priority structure 报警优先级别结构 Alarm grouping 报警分组 Alarm Displaying and Acknowledgment 报警显示和确认 Alarm types (process, system, etc) 报警类别(工艺、系统等) Events and Messaging 事件和消息 Displays 显示 Standard 标准 Custom 定制 Navigation 导航FS

119、-Contents-Interface FunctionsFS-内容-界面功能 Access Control 访问控制 Setting 设定 Max login attempts 最多尝试登录次数 Password expiry period 密码失效期 Password re-use period 密码重新使用期 Minimum user ID length 最小用户名长度 Maximum user ID length 最大用户名长度 Minimum password length 最小密码长度 Maximum password length 最大密码长度 Security Group 安全

120、分组 Operator 操作员 Engineer 工程师 Admin管理员FS-Contents-Interface FunctionsFS-内容-界面功能 Access Rights 访问权限Function功能Access Right 访问权限 User Accounts: 用户账户User ID 用户名Full name 全名Access Level 访问级别FS-Contents-Disaster RecoveryFS-内容-灾难恢复 Power Outage 断电 What happens to outputs on loss of power? 断电时输出将如何反应? What h

121、appens to programs / configurations on loss of power? 断电时程序/配置将如何反应? What happens on restart cold / warm / tepid? 冷/热/温重启时将如何反应? What happens to outputs on restart?重启时输出将如何反应? What happens to run-time data on restart?重启时运行时数据将如何反应? Equipment Failure 设备故障 Indication of failure 故障指示 Effect on control

122、对控制的影响 Effect on process visibility 对工艺可见性的影响 Backup & Restore 备份和恢复 Method of Backup 备份方法 Method of Restore 恢复方法Any question?GAMP5 Planning PhaseGAMP5计划阶段Hardware Specification硬件说明Hardware Specification硬件说明 Hardware Design Specification defines the hardware design on thecontrol system 硬件设计说明规定了控制系统

123、的硬件设计情况 Hardware Design Specification is the responsibility of the supplier 硬件设计说明属于供应商的责任 It is normally written in parallel or after approval of FDS 通常是在批准FDS之后平行编写 It provides the main basis for FAT hardware tests 它提供了FAT硬件测试的主要基础 It needs to be approved by User. 需要用户批准 Generally may require furt

124、her revision during the project life cycle. 一般在项目生命周期过程中需要进行修订HDS- ContentsHDS-内容 Relationship to other Documents与其它文件的关系 Applicable standard适用标准 Relationship to customer URS与客户URS之间关系 Non-Conformance with User Requirement与用户需求的不符合项 Drawings图纸 List of Drawing including Drawing number & Title 图纸清单,包括

125、图纸编号和标题 Panel General Arrangement 面板整体布局 Power Distribution & Earthing 配电和接地 Signal wiring 信号接线 Network Arrangement 网络布局 Interface to external equipment 与外部设备的界面 Cable schedule 电缆列表 Overview 概述 Process to be controlled 所需控制工艺 System Architecture 系统结构HDS- Contents- HardwareHDS-内容-硬件 Computerised Syst

126、em Component 计算机系统部件 PLC Input devices (sensors, buttons, etc) 输入装置(传感器、按钮等) Output devices (Valves, switches, lamps, etc) 输出装置(阀门、开关、灯等) HMI SCADA Cabinets, Panels (控制柜、控制面板) System component detail(系统部件详情) Description 说明 Quantity 量 Model number型号 Version number (Hardware and firmware) 版本号(硬件和固件)HD

127、S- Contents- HardwareHDS-内容-硬件 Labelling 标签 Cubicle labels 隔间标签 Equipment labelling 设备标签 Wiring/termination blocks labelling接线/接线板标签 Earthing 接地 Protective earth 保护接地 Clean earth 洁净接地 Earth studs接地螺栓 Wiring 接线 Signal wiring 信号接线 Power wiring 电源接线 Network cabling 网络电缆HDS- Contents- HardwareHDS-内容-硬件

128、Inputs Allocation 输入分配PLC Input module PLC输入模块Channel 通道Tag No 标号Description说明Signal type信号类别Engineering unit 工程单位Input device 输入装置Range范围 Digital Inputs 数字输入PLC Input module PLC输入模块Channel通道Tag No标号Description说明Signal type信号类别Input device输入装置 HDS- Contents- HardwareHDS-内容-硬件 Analogue Output 模拟输出PLC

129、 output module PLC输出模块Channel通道Tag No标号Description说明Signal type信号类别Engineering unit 工程单位Output device 输出装置Range 范围 Digital OutputsPLC Output module PLC输出模块Channel通道Tag No标号Description说明Output device 输出装置 HDS- Contents- UtilitiesHDS-内容-公用工程 Electrical Supply and Loading 电源和负载 Main Supply 主电源 Air supp

130、ly 供气 Specification for air supply 供气规格 Environment 环境 Operating Temperature & humidity 运行温湿度 IP rating IP等级 Class room rating 房间等级 ATEX rating ATEX等级 Cleaning 清洁Any question?GAMP5 Planning PhaseGAMP5计划阶段Software Specification & Software Module Specification软件说明和软件模块说明Software & Software Module Spec

131、ification软件说明和软件模块说明 A Software Design and Configuration Specification (SDS) defines how the software isdesigned and configured in order to meet the functional requirements of the system. 软件设计和配置说明(SDS)规定了如何来对软件进行设计和配置来满足系统的功能要求。 A Software Module Specification (SMS) defines how a bespoke software m

132、odule isdesigned and configured in order to meet the functional requirements of the system. 软件模块说明(SMS)规定了如何对定制软件模块进行设计和配置来满足系统的功能要求。 SDS and SMS are the responsibility of the supplier SDS和SMS属于供应商的责任 They maybe combined into a single document 可将其合为一个文件 They can optionally be approved by User. 可选择是否

133、由用户批准 Generally may require further revision during the FAT. 一般需要在FAT过程中进行修订SD- ContentsSD-内容 Relationship to other Documents与其它文件的关系Applicable standard适用标准Relationship to FDS 与FDS之间的关系 Project overview项目概述Summary of Process to be controlled所需控制工艺概述System Architecture系统结构System classification: softw

134、are categories系统分类:软件类别SD- ContentsSD-内容 For each Node List Software Modules 对每个节点列出软件模块 Non-Configured (Parameterised) Modules, CAT3 无配置(参数设定)模块,第3类 Network setup parameters网络设置参数 Start-up setup 启动设置 Configured Modules, CAT4 有配置模块,第4类 Continuous control 连续控制 Interlocks 互锁 Custom Modules, CAT5 定制模块,

135、第5类 Sequences 顺序 Custom Ladder logic, Structured text logic 定制梯形逻辑、结构文本逻辑 Custom software (Visual Basic, etc) 定制软件( Visual Basic 等)SD- ContentsSD-内容 Non-Configured (Parameterised) Software Modules, CAT3 无配置(参数设定)软件,第3类 Function 功能 Parameter lists and setting参数列表和设定SP_INT:PV_IN:MAN:LMN:给定参数设定反馈值手动设定输

136、出值SD- ContentsSD-内容 Configured Software Modules, CAT4/5有配置软件模块,第4/5类 Function 功能 Module interface 模块界面 Module Error Handling 模块错误处理 Module configuration/coding environment 模块配置/编码环境 Module Implementation 模块实施 Module parameters and settings 模块参数和设置 Module alarms list 模块报警清单Any question?GAMP5 Verifica

137、tion PhaseGAMP5验证阶段Test Protocols测试方案Test Phases测试阶段A system test phases depends on its size and complexity系统测试的阶段取决于其大小和复杂性Typical test phases include 典型的测试阶段包括Software Module testing 软件模块测试Internal integrated testing 内部集成测试 Hardware硬件 Software软件 FAT test FAT测试 Hardware硬件 Software软件 SAT test SAT 测试

138、 Hardware (IQ) 硬件(IQ) Software (OQ) 软件(OQ)Test Protocols测试方案 A Test protocol or specification defines the testing to be carried out toverify that the system (or its individual elements) meets pre-definedrequirements. 测试“方案”或“说明”规定了为了确认系统(或其单独部件)是否符合其预先规定的要求而需进行的测试 A project may include Software Modu

139、le Test Protocol, FAT protocol, SATprotocol 一个项目中可能会包括软件模块测试方案、FAT方案和SAT方案 Depending the size of the project there maybe a separate Hardware Testprotocol 根据项目的大小,可能会有单独的硬件测试方案 Test Protocols are the responsibility of the supplier They should be approvedby User. 测试方案属于供应商的责任 Generally may require fur

140、ther revision during the FAT. 一般需要在FAT过程中继续修订Test Protocol- Contents测试方案-内容 Relationship to other Documents 与其它文件之间的关系Applicable standard 适用标准Relationship to FDS 与FDS之间的关系Infrastructuresoftwareelement底层软件项Non-configuredsoftwareelement非配置软件项Configuredsoftwareelement组态软件项Bespokesoftwareelement自定义软件项Hi

141、ghRisk高风险Assumeinfrastructureelementsareadequatelychallengedbyfunctionaltestingoftheapplication假设底层项通过程序的功能性测试进行被充分证实Functionaltesting功能性测试FunctionaltestingChallengetesting功能性测试挑战性测试Codereview代码审核Structural(module)testing结构(模块)测试Functionaltesting功能性测试Challengetesting挑战性测试MediumRisk中风险Functionaltesti

142、ng功能性测试Codereview代码审核Structural(module)testing结构(模块)测试Functionaltesting功能性测试LowRisk低风险Codereview代码审核Functionaltesting功能性测试Test Protocol- Contents- Strategy测试方案-内容-策略 Applicable standard适用标准Activity工作DescriptionCodereview代码审核Codereviewofbespokesoftwareelementsagainstbothcodingstandardsandsoftwaredesi

143、gndocumentation根据编程标准和软件设计文档进行自定义代码项的审核Moduletesting模块测试Structural(module)testingofhigh/mediumriskbespokesoftwareelementsagainstthesoftwaredesigndocumentation根据软件设计文档进行高/中风险的自定义软件项的结构(模块)测试SupplierInternalIntegrationTesting供应商内部集成测试UnwitnessedtestsusingtheFATprotocoltocheckcorrectsystemintegrationpr

144、iortoinvitingthecustomertowitnessFAT.在邀请客户目击FAT前使用FAT方案进行非目击测试FactoryAcceptanceTesting-phase1(hardwaretests)-phase2(functionaltests)Witnessedfunctionalandchallengetestingofthesysteminatestenvironmentatsupplierspremises在供应商工厂环境下,对系统进行目击的功能和挑战性测试SiteAcceptanceTesting-phase1(hardwaretests)-phase2(funct

145、ionaltests)WitnessedfunctionalandchallengetestingusingtheSATprotocol.Focusonthoseaspectsofthesystemwhichmaybeaffectedbythemovetotheproductionenvironmentorwhichcouldnotbeadequatelytestedinthetestenvironment.使用SAT方案进行目击的功能和挑战性测试。重点放在系统可能因为放到生产环境下而受到影响的项或者在FAT环境下未能充分测试项Test Protocol- Contents- Strategy

146、测试方案-内容-策略 Phases of Testing 测试阶段TestCoverage:测试覆盖StructuraltestingofmoduleXagainstthesoftwaredesigndocumentation根据软件设计文档进行模块X的结构测试Location:地点AtSupplierspremises.在供应商公司Timing:时间Beforeintegrationofsoftwareandhardware在软硬件集成前Testing:测试ByaSupplierrepresentative由供应商代表Witnessing:证人Notwitnessed.无目击证人Review

147、ing:审核BySupplierprojectmanager由供应商项目经理TestHardwareEnvironment:软件测试环境Definehardwareenvironment.定义硬件环境TestSoftwareEnvironment:软件测试环境DefineSoftwareenvironmenttotestthesoftware为测试软件定义软件环境TestData:测试数据Definetestdatarequired定义需要的测试数据TestUserAccounts:测试用帐户Defineuseraccountsasrequired定义需要的用户帐户Test Protocol-

148、 Contents- Strategy测试方案-内容-策略 Module Testing模块测试TestCoverage:Phase 1 Hardware testsHardwarechecksagainsthardwaredesign针对硬件设计进行硬件检查Processequipmentinterface(inputandoutputsignals)过程设备接口Internalinterfaces(communication/datachecks)内部接口Phase 2 Functional testsProcesscontrolfunctions(continuous/sequentia

149、l)过程控制功能(连续/顺控)Datahandlingfunctions(internaldatastructuresanddataflows,datainputfunctions,datatransformationfunctions,dataoutputfunctions,electronicrecordsandsignatures,datamigrationfromprevioussystem)数据处理功能(内部数据结构和数据流,数据输入功能,数据转换功能,数据输出功能,电子记录和签名,从原系统的数据移植)Interfacestoexternalsystems(communication

150、s/datachecks)外部系统接口(通讯/数据检查)Operatorinterface(alarmandeventstrategy,displays,accesscontrol)操作员接口(报警和事件,显示,访问控制)Systemtechnicaldetail(disasterrecovery,performance)系统技术详情(灾难恢复,性能)Location:Atsupplierspremises.Timing:AfterintegrationofsoftwareandhardwareandbeforeFATTesting:ByaSupplierrepresentativeWitne

151、ssing:Notwitnessed.Reviewing:BySupplierprojectmanagerTestHardwareEnvironment:Performedwithallcustomerequipmentpresentbutnetworksconnectedusing5mpatchcablesinplaceofthesitecablerunsandwithoutcustomernetworkinfrastructure.将所有在场设备连接到测试网络以代替客户的网络环境TestSoftwareEnvironment:Performedwithallapplicationsoftw

152、areloaded.装载所有应用软件Aconfigurationmanagementbaselinetakenpriortothestartofintegratedtest.集成测试前标记组态管理基准线TestData:Definetestdatarequired定义要求测试的数据TestUserAccounts:Defineuseraccountsasrequired定义Test Protocol- Contents- Strategy测试方案-内容-策略 Internal/Integration Testing 内部/集成测试TestCoverage:Phase 1 Hardware te

153、stsHardwarechecksagainsthardwaredesignProcessequipmentinterface(inputandoutputsignals)10%randomcheckInternalinterfaces(communication/datachecks)Phase 2 Functional testsProcesscontrolfunctions(continuous/sequential)Datahandlingfunctions(internaldatastructuresanddataflows,datainputfunctions,datatransf

154、ormationfunctions,dataoutputfunctions,electronicrecordsandsignatures,datamigrationfromprevioussystem)Interfacestoexternalsystems(communications/datachecks)Operatorinterface(alarmandeventstrategy,displays,accesscontrol)Systemtechnicaldetail(disasterrecovery,performance)Location:AtSupplierspremises.Ti

155、ming:AftercompletionofinternalintegrationtestsandbeforereleaseofsystemforshipmenttositeTesting:ByaSupplierrepresentativeWitnessing:ByacustomerrepresentativeReviewing:ByacustomerrepresentativeTestHardwareEnvironment:Performedwithallcustomerequipmentpresentbutnetworksconnectedusing5mpatchcablesinplace

156、ofthesitecablerunsandwithoutcustomernetworkinfrastructure.TestSoftwareEnvironment:Performedwithallapplicationsoftwareloaded.AaconfigurationmanagementbaselinetakenpriortothestartofFATtest.TestData:DefinetestdatarequiredTestUserAccounts:DefineuseraccountsasrequiredTest Protocol- Contents- Strategy测试方案

157、-内容-策略 FATTestCoverage:Phase 1 Hardware testsHardwarechecksagainsthardwaredesignOperatingenvironmentchecksProcessequipmentinterface(inputandoutputsignals)10%randomcheckInternalinterfaces(communication/datachecks)Phase 2 Functional testsProcesscontrolfunctionswhichmaybeaffectedbythemovetothesiteenvir

158、onment(egbecauseoftimingconsiderations)Datahandlingfunctions(datainputfunctions,dataoutputfunctions,datamigrationfromprevioussystem)Interfacestoexternalsystems(communications/datachecks)Location:AtCustomerspremises.Timing:AfterinstallationofthesystemonsiteandpriortofinalsystemhandoverTesting:ByaSupp

159、lierrepresentativeWitnessing:ByacustomerrepresentativeReviewing:ByacustomerrepresentativeTestHardwareEnvironment:Performedwiththesysteminstalledinitsfinalproductionenvironment.TestSoftwareEnvironment:Performedwithallapplicationsoftwareloaded.AconfigurationmanagementbaselinetakenpriortothestartofSATt

160、est.TestData:DefinetestdatarequiredTestUserAccounts:DefineuseraccountsasrequiredTest Protocol- Contents- Strategy测试方案-内容-策略 SATTest Protocol- Strategy测试方案-策略Areas excluded from test 测试所包含领域Orders of Test 测试指令Format of Test Sheets 测试页的格式Procedure for Test Execution 测试的执行规程 How to carry out the tests

161、如何来进行测试 SOP for testing 测试SOP What action to be taken on a test failure (deviations) 测试失败(偏差)后应采取的措施 What action on documentation error 对文件错误应采取的措施 What action to be taken once testing is completed 测试完成之后应采取的措施 How to deal with test Procedure for test review and reporting 测试审查和报告的流程TestPhaseItemRefe

162、renceSignatureInitialsPrintedNamePositionFunction*Test Protocol- Test Environment Record of test PersonnelTestPhaseItemReferenceItemTypeSerialNumberInitialsDateTest Protocol- Test Environment Hardware Environment硬件环境Project Hardware项目硬件TestPhaseItemReferenceTestEquipmentTypeSerialNumberCalibrationDa

163、teInitialsDateTest Protocol- Test Environment Test Equipment测试设备Services服务Consumables消耗品Test Equipment测试设备TestPhaseItemReferenceStandardSoftwareItemVersionatstartInitialsDateVersionatendInitialsDateTest Protocol- Test Environment Software Environment软件环境Infrastructure and Standard Software, CAT1 &3底

164、层和标准软件,1类和3类TestPhaseItemReferenceProjectSoftwareItemFilename(s)VersionatstartInitialsDateVersionatendInitialsDateTest Protocol- Test Environment Software Environment软件环境Application Specific Software, CAT4 & 5专用应用软件,4类和5类TestPhaseItemReferenceDocumentTitleVersionInitialsDateTest Protocol- Test Envir

165、onment Reference Documents参考文档TESTSCRIPTANDRESULTSSHEETTestPhaseItemRefTestRefTitleRunnumber:ObjectivePagesinscript:AcceptancecriteriaPagesappended:RequirementRefPre-requisitesRecordanychangestotherecordedthetestenvironmentTeststepActionDatatobeRecordedActualResult/IncidentRecordExpectedResultPass/F

166、ailPostTestActionsCommentsOverallTestResultIncidentReportReferenceTesterSignatureDateWitnessSignatureDateTest Protocol Tests to be performed执行的测试Test Execution执行测试Testresultsshouldberecordedinsuchawaythatanindependentreviewercanverifythattherequiredtesting didtakeplaceinaccordancewiththeapprovedtest

167、documentation.通过方法记录测试结果,即独立的审核人可以验证所要求的测试的确已经按照批准的测试文档执行 Recordresultsindelibly测试记录不可擦除 Crossoutwithasingleline,initialanddatecorrections划单线来修正签名和日期的 Documentresultsdirectlyastestingoccurs文档结果如实反应发生的测试 AvoidshorthandnotationssuchasticksandOK避免缩略用语,比如对勾和OK Dontleaveblankboxes.不允许留有空格 Markappendedtes

168、tevidencewithtestreference,runnumber,sheetxofy,signanddate.对附加的测试材料,标记出参考号,运行号,第X页共X页,签名和日期 Dateformat“01Jan2005” ispreferredasitisunambiguous(eventoAmericans!)推荐使用的日期格式TestPhaseItemReferenceTestReferenceInitialrunSecondrunThirdrunResultIncidentcrossrefTesterInitials/DateWitnessInitials/DateReviewIn

169、itials/DateResultIncidentcrossrefTesterInitials/DateWitnessInitials/DateReviewInitials/DateResultIncidentcrossrefTesterInitials/DateWitnessInitials/DateReviewInitials/DateTest Protocol Test Report and Post-Execution Review测试报告和已执行的审核Test Result Summary测试结果汇总TestPhaseItemReferenceReportNo.Fault(Yes/N

170、o)Change(Yes/No)BriefDescriptionClosed(signature)DateTest Protocol Test Incident Summary测试偏差汇总Test Protocol Test Acceptance Certificate测试验收证书TitleCustomersupplierReferenceCustomerReferenceTest PhaseItemReferenceWe hereby confirm that the test phase has been completed to our satisfaction subject to t

171、hecompletion of the outstanding items listed belowSigned(Supplier LeadTester) Sign / DatePrinted NameTitleSigned(Reviewer)Test Review and ReportingOncetestingiscomplete,anindependentreviewer(thiswillbeacustomerrepresentativeforawitnessedteststage)needstoconfirmthat:测试一旦完成,独立的审核人(在目击测试阶段,应该为客户代表)需要确认

172、: Alltestsarecomplete已完成所有测试 Allresultsarelegible,accurateandwithnoblanksleft所有结果是清晰,准确和未留有空白的 Allrelevantdocuments/supportingevidentisincluded已包含所有相关文档/支持资料 Testresultshavebeenrecordedinsuchawaythatitisclearwhetheracceptancecriteriaweremet测试结果需要记录并清晰体现出满足了验收标准 Alltestincidentreportsarepresentandhav

173、ebeensuitablycloseddown(ortransferredtotheexceptionslistontheacceptancetestcertificate)所有测试事件报告存在的和已经正确关掉(或到验收测试证书的例外清单中)自控验证实施流程举例Verify Automation System确认自控系统SCADA SystemSCADA系统PMS(Particle Measuring System)尘埃粒子检测系统HAVC Automation System空调自控系统Energy Management System能源管理系统自控验证实施流程举例 续GxP Critical

174、ity Assessment进行GxP关键性评估(“6个问题”)SCADA SystemSCADA系统PMS(Particle Measuring System)尘埃粒子检测系统HAVC Automation System空调自控系统Energy Management System能源管理系统GxP CriticalGxP关键Non-GxPCritical非GxP关键GxP CriticalGxP关键GxP CriticalGxP关键自控验证实施流程举例 续System ImpactClassification系统影响性分类(“3个影响”)SCADA SystemSCADA系统Measurin

175、gPMS(ParticleSystem)尘埃粒子检测系统HAVC Automation System空调自控系统High Impact高级别影响MediumImpact中级别影响Low Impact低级别影响VerifyValidationCategory确定验证范畴Software andHardwareCategories进行软硬件分类Execute Validation according toV-Model of Validation Life Cycle依据生命周期“V-Model”实施验证 Verify Validation Life Cycle确定验证生命周期自控验证实施流程举例

176、 续Verify System Risk确定系统风险Result from Supplier assessment来自供应商评估的结果德国莱茵公司ISO现场审核通过确认书ISO9001中文证书ISO9001英文证书ISPE GAMP5培训证书SIEMENS制药行业亚洲首家合作伙伴-Solution Partner奥星在制药行业十余年积累我们始终在关注和遵守相关的法律法规符合GAMP5的设计施工流程资深专业技术人员及优秀售后服务来自合作伙伴的支持: 专业的技术培训及支持 来自过程领域的项目库 项目过程中的风险分担 符合法律法规的验证模板 价格上的优惠Austar & SIEMENS我们的优势Austar Promotes Industry AdvancementAny Question?

展开阅读全文
相关资源
正为您匹配相似的精品文档
相关搜索

最新文档


当前位置:首页 > 高等教育 > 研究生课件

电脑版 |金锄头文库版权所有
经营许可证:蜀ICP备13022795号 | 川公网安备 51140202000112号