usage, and when a rules fail to Technical Architecture - work as designed, and provide Rules Engine & Rules recommendations to resolve rule Management failure. Must provide the capability for a rule review and approval process that will validate logic errors, conflicts, redundancy and IV.O.12 Operations Phase - incompleteness across business Business Information and rules to identify any conflicts in Technical Architecture - business rules as they are being Rules Engine & Rules developed, tested, and Management implemented. IV.O.12 Operations - Must provide version control Business Information and including the ability to revert to a Technical Architecture - prior version of the rules if there Rules Engine & Rules are unwanted or unexpected Management consequences of a rule change. Must provide, implement, and maintain a State approved DMA Audit and Control Plan that IV.O.13 Operations Phase - includes approach, strategy, Business Information and architecture, methodology, Technical Architecture - process, tools, resourcing, quality DMA Auditing and Controls and contingency aspects. Must track, log, and provide reporting on, in human readable IV.O.13 Operations Phase - format, data changes including Business Information and State approved audit information Technical Architecture - such as the date, time and user or DMA Auditing and Controls system making the change. Must track, log, and provide reporting on, in human readable format, inquiries, views, reports, or access of data that may require such tracking as a result of law, policy, or data use agreements IV.O.13 Operations Phase - including State approved audit Business Information and information such as the date, time Technical Architecture - and user or system initiating the DMA Auditing and Controls transaction.
Technical Architecture - Rules Engine & Rules Management usage, and when a rules fail to work as designed, and provide recommendations to resolve rule failure. IV.O.12 Operations Phase - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide the capability for a rule review and approval process that will validate logic errors, conflicts, redundancy and incompleteness across business rules to identify any conflicts in business rules as they are being developed, tested, and implemented. IV.O.12 Operations - Business Information and Technical Architecture - Rules Engine & Rules Management Must provide version control including the ability to revert to a prior version of the rules if there are unwanted or unexpected consequences of a rule change. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must provide, implement, and maintain a State approved DMA Audit and Control Plan that includes approach, strategy, architecture, methodology, process, tools, resourcing, quality and contingency aspects. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must track, log, and provide reporting on, in human readable format, data changes including State approved audit information such as the date, time and user or system making the change. IV.O.13 Operations Phase - Business Information and Technical Architecture - DMA Auditing and Controls Must track, log, and provide reporting on, in human readable format, inquiries, views, reports, or access of data that may require such tracking as a result of law, policy, or data use agreements including State approved audit information such as the date, time and user or system initiating the transaction.