Although this deck was started in 2009, it was the primary tool used in talking about GenevaERS (renamed as the IBM Scalable Architecture for Financial Reporting in 2009) since 2012.
Documentation of its development is contained in the book Balancing Act: A Practical Approach to Business Event Based Insights, available for download from ledgerlearning.com.
The following is an extract of of the GenevaERS Version 3 Operations User’s Guide.
Version of 3 of GenevaERS followed on Version 1, built for the State of Alaska, and Version 2, constructed for various state governments. It was the first commercialized package. It and all the prior versions included CICS interfaces and JCL for the Performance Engine Execution.
Until very recently, most of the program names in the Performance Engine job stream were recognizable from this document. Below is two chapters from the documentation, the major one on the Extract Engine job stream, which included the view selection and logic table build processes, and one explaining the control reports for these programs.
The following is an extract of of the GenevaERS Version 3 ViewBuilder User’s Guide.
Version of 3 of GenevaERS was followed on Version 1, built for the State of Alaska, and Version 2, constructed for various state governments. It was the first commercialized package. It and all the prior versions included CICS interfaces.
Most all of the features in the ViewBuilder have been carried forward in some way to the 2020 version. Thus the below is a selection of the major functions of the CIC screen.
The following is an extract of of the GenevaERS Version 3 System Administration User’s Guide.
Version of 3 of GenevaERS was followed on Version 1, built for the State of Alaska, and Version 2, constructed for various state governments. It was the first commercialized package. It and all the prior versions included CICS interfaces.
In the 2020 version of GenevaERS, many of the administration functions still remained, including creating Logical Records, Field Definitions, Physical Files, and Joins. But there are a number of unique capabilities of Version 3 that were never carried forward, including the ability to define dynamic screens, place records and fields on those screens, define edit processes for values, and create, update, retrieve, or delete (crud) functions against those values.
Thus the below includes a selection of each of the System Administration Guide, giving a sample of these capabilities.