Revision History Document Version # Document Date Summary of Changes Revised By 0.1 01/15/2016 Initial Draft Vijay Kumar 0.2 05/03/2016 Edits based on Peer-Review Rename Database from STG to Integrations Worktables Update Requirements table Update Table of Contents Update Design diagrams and text as per the current requirement and feedback from peer review Vijay Kumar AOC Internal Review/Approval List This document requires the following AOC internal approvals. Name Title Date Vijay Kumar Solution Architect Eric Kruger Program Architect Sree Sundaram Project Manager
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
DI-037 Data Integration - Initial Load (of JIS Data) The initial load shall record the date and time of the initial load A log entry for the initial load exists. DI-038 Data Integration - Initial Load (of JIS Data) The initial load shall use the same transformations created to support continued updates. The same transformations for the initial load is also used by subsequent updates. DI-039 Data Integration - Court Migration Post migration, if it is determined that the migration was not successful, the AOC Migration database shall be used to re-insert previously purged records. The JIS Database and the EDR are back to the state prior to migration DI-040 Data Integration - Transformation Transformations shall only pull data that has been added or updated since the last transformation execution Transformations use the date and time recorded in the log from the previous pull. DI-041 Data Integration - Transformation Transformations shall record the start time of the transformation The start time is recorded in the transformation log DI-042 Data Integration - Transformation Transformations shall log current status of execution (i.e. started, loading, complete with no exceptions, complete with exceptions, etc.) A review of the log throughout the execution of the transformations show what operations have completed and which ones are currently running. DI-043 Data Integration - Staging The staging area must be able to identify deleted records and retain for possible re-insertion. Records deleted at the source are present in the corresponding ZDEL table.