DI-009 Data Integration - Transformations shall have the ability A restart of a transformation occurs from Transformation to re-start from point of last success the last know completed record/operation instead of from the beginning. DI-010 Data Integration - Transformations shall communicate and Transformation destinations shall be the Transformation submit data through the EDR Data EDR Data Services. Services Data Integration - Transformations shall maintain a log Transformation logs contain Date/Time, DI-011 Transformation indicating execution Date/Time, number and type of records submitted, number and type of records submitted, number and type of records number and type of records accepted, number and type of records rejected, elapsed of execution DI-012 Data Integration - Transformations shall be scalable, Transformations make use of available Transformation harnessing the power of multiple multiple processors processors when needed, releasing when not needed DI-013 Data Integration - Transformation shall provide Configuration files over-ride design time Transformation configurable deployment options values at deployment DI-014 Data Integration - The scheduling component shall be able A transformation has multiple run Monitor/Schedule to support multiple schedules schedules Data Integration - A single Schedule shall have the ability Two or more jobs share the same named DI-015 Monitor/Schedule to be applied to multiple transformation schedule jobs DI-016 Data Integration - Scheduled jobs must be able to enable A scheduled job starts another job Monitor/Schedule and/or execute other jobs DI-017 Data Integration - Court Data from migrating court must be A migration database exists and contains Migration extracted from the ODS into a data received from the ODS Migration Database in SQL Server DI-018 Data Integration - Court Data must be in the exact same format Table structures and definitions in the Migration and structure as JIS, with no migration database are identical to those transformations. from the ODS
DI-009 Data Integration - Transformation Transformations shall have the ability to re-start from point of last success A restart of a transformation occurs from the last know completed record/operation instead of from the beginning. DI-010 Data Integration - Transformation Transformations shall communicate and submit data through the EDR Data Services Transformation destinations shall be the EDR Data Services. DI-011 Data Integration - Transformation Transformations shall maintain a log indicating execution Date/Time, number and type of records submitted, number and type of records accepted, number and type of records rejected, elapsed of execution Transformation logs contain Date/Time, number and type of records submitted, number and type of records DI-012 Data Integration - Transformation Transformations shall be scalable, harnessing the power of multiple processors when needed, releasing when not needed Transformations make use of available multiple processors DI-013 Data Integration - Transformation Transformation shall provide configurable deployment options Configuration files over-ride design time values at deployment DI-014 Data Integration - Monitor/Schedule The scheduling component shall be able to support multiple schedules A transformation has multiple run schedules DI-015 Data Integration - Monitor/Schedule A single Schedule shall have the ability to be applied to multiple transformation jobs Two or more jobs share the same named schedule DI-016 Data Integration - Monitor/Schedule Scheduled jobs must be able to enable and/or execute other jobs A scheduled job starts another job DI-017 Data Integration - Court Migration Data from migrating court must be extracted from the ODS into a Migration Database in SQL Server A migration database exists and contains data received from the ODS DI-018 Data Integration - Court Migration Data must be in the exact same format and structure as JIS, with no transformations. Table structures and definitions in the migration database are identical to those from the ODS
EXHIBIT%20J%20-%20KCDC%20Data%20Replication%20HL%20Design.docx