nissan cdp Link to heading

Semi-concurrently with the Boeing deal, Bowen served as lead architect for the expansion of Nissan’s Worldwide Financial Planning system. This entailed the design, separate from re-bid and implementation of a system that would include integration with the North American Data Warehouse for all budgeting and planning for Nissan North America’s 18 dimensional financial codeblock. Bowen built the backend in ksh and Perl to supply asynchronous feeds to 37 synchronized Essbase cubes. As well he supervised the transition of this system to the offshore support team.

Bowen worked the full lifecycle and delivered the project in 18 months from end to end using Hyperion Planning, Essbase, ksh & Perl.

Abstract Link to heading

Nissan’s North American Regional Data Warehouse (RDW) used a combination of DB2 sourced data and allocated data from SAP sources as well as a number of spreadsheets. I specified, designed and built and central data platform that scheduled and routed asyncrhonous financial data from multiple different divisions with different rules for submission & resubmission. Specifically I brought under centralized control a large number of datafeeds that had never been named or specified by identifying SMEs from each division and creating a new ontology for control and delivery.

Details Link to heading

Abstract Link to heading

The Common Data Platform or CDP manages and contains the flows of data for the Nissan Planning Application. This document outlines its major functions and describes a design and purpose for the Common Data Platform, an integral part of the backend of the Phase II of FA&B Hyperion Planning system.

Overview Link to heading

The Common Data Platform will streamline data provision and establish standards across all of the Essbase applications. It will handle data management tasks for Essbase cubes whether they are controlled by Planning or independent of Planning. This base data will primarily provide the Actuals Path but will also provide a backup repository for the Budget & Forecast path. Our design is oriented towards building an integrated data provision service that extends and enhances the North American Regional Data Warehouse (RDW) infrastructure that is now providing data for the RDW Essbase cubes

CDP TECHNOLOGY Link to heading

The CDP will generally consist of data interfaces, conversion processes and schedulers. The primary technology of the CDP will be unix utilities and scheduling tools. This framework will be modified from the RDW codebase. In addition, MSSQL will be used in conjuction with the RDW databases in order to manage certain conversions that are best managed with relational technology, especially backup of the Repository databases. The CDP will move data to where it needs to be. Most of the processing in the CDP will be text based with a determined focus on ultimate migration into standard DW best practices. When Excel is the source or target data, VBA code may be used. In addition to export data from Essbase OLAP databases, Jexport or MDX routines will be employed. For integration into Hyperion Planning Repositories, the CDP will execute HAL interfaces to Planning Master Data. Hyperion ElS can be used for data modeling.

CDP MAJOR FUNCTIONS Link to heading

The CDP provides four major functions that fold the multiple databases and data sources into one integrated system.

1. Application Data Flow Management & Registry
2. Master Data Synchronization & Provision
3. Backup, Migration & Data Recovery
4. Miscellaneous Application Support

The CDP will manage three primary data streams.

1. Input Data streams
2. Output Data streams
3. Master Data Stream