Summary Descriptions of Consulting Projects

• Summary of software technologies of which I used to develop the solutions

  • Oracle’s Hyperion Data Relationship Management/DRM (formerly MDM)

  • Oracle’s Hyperion FDM, Essbase, Shared Services (security integration)

  • Oracle and Microsoft databases

  • Programming languages

    • MS SQL stored procedures, Oracle’s PL/SQL

    • MS Windows batch command scripting for automation/scheduling

    • Oracle Javascript within context of DRM’s command and control language

    • Hyperion MDM custom property language (prior to Oracle javascript)

• Summary of various software technologies in which my solutions interfaced as an upstream source or downstream subscriber

  • Peoplesoft and SAP GL

  • Oracle GL, OBIEE, EBS, SiteHub, Planning, Essbase, HFM, FDM/FDMEE, EPMA, OFSAA

  • Oracle and Microsoft databases for staging between DRM and other environments

  • Salesforce.com, Clarity project management, Concur expense management, Perfect Commerce facilities planning

• Summary of responsibilities/duties across all the consulting projects

  • Architect/Designer, System Install/Config/Administrator, Programmer/Builder

  • Software/Solution testing including working with larger dedicated client testing divisions

  • Instructor/Trainer including training material for application business users, QA testers, IT admins

• Summary of typical descriptions or activities of my consulting projects

  • Common team sizes between 16 and 60 split between consultants and client personnel

  • Medium to large projects budgeted in the millions of dollars and sometimes spanning years an phased rollouts

  • My development approach typically resembled agile methodology

  • I would have responsibility and accountability for producing project plan timelines and integrating int the larger plan through development activities

  • Every separate downstream subscriber application requirements had direct impact to my initial an then evolving design, develop, test, and train deliverables for my project timelines

• If I said I could build something specific in DRM and have it done by a specific deadline, then I delivered as expected. No project was ever late or over budget due to my inability to deliver as I described

• My experience allowed me to plan design flexibility that would allow for rapid adjustments to changing requirements or constraints

• Summary of frequent elements and goals across achieved solutions

  • DRM provided a framework where I built collections of imports to bring external source data inside, built properties for end users to directly enhance the detail of metadata, built properties to derive metadata values without additional input, built validation rules for data quality review/enforcement, built collections of exports to specific application technical requirements for consumption, built automation capability within a given client supported environment, and provided data governance to drive the process

  • Solutions provided framework to support ongoing future enhancements within a traditional version release cycle across development environments into production

  • Solutions resulted in improved data quality, transparency, and timeliness of getting the right information to the right people at the right time

  • Solutions often had a mix of being fed basic key metadata from ‘record of source’ systems and then augmented that from a mix of business owner data stewards or derived from code driven rules and then pushing subscriber specific, enhanced metadata sets, downstream to target applications providing the strategic improvements in data quality and transparency

  • Supported blending source updates into DRM that can be tens of thousands of members upon which alternate views were maintained which provided for real time reporting changes not yet realized in production back office systems until they ‘caught’ up

  • DRM provided hierarchy control and governance supporting multiple consolidation target applications from a handful of reporting cubes to over a 100 across multiple applications covering multiple years and multiple versions of forecasting models

  • Daily publishing of the delta of DRM metadata changes to drive other dependent operations

  • Published to data warehouse staging tables to be incorporated into custom ETL processes of data for other legacy systems providing reporting consistency across the organization

  • Provided updates to non reporting systems such as internal POS systems and external Vendor supply chain operations

  • Built various methods to integrate with any existing internal automation or scheduling solutions providing various levels of automation from approved steps to lights out end to end

  • Utilized DRM javascript programming language (in later versions) providing rules based data quality and automation and reducing the manual, error prone manual data entry

  • Provided guidance into Information Governance, SOX compliance, and data warehouse best practices o Reverse engineered complex legacy processes and delivered new abilities to drive reconciliation and audit processes

• Selective samples of customizing the DRM framework beyond typical GL and entity consolidation

  • On multiple projects, turned DRM into a rules based code generator to update target applications by using DRM’s natural hierarchical and attribute based visual interface to provide users a holistic view, provided change/audit control, and published out application specific technical code

    • Provided security access configuration to reporting applications

    • Provided data filtering code to an ETL rules engine

  • Provided complex reporting structures for sales and expense planning/forecasting out 10+ years by dynamically calculating time based retail store status changes for future periods

    • Alternate view reporting hierarchies dynamically built during publishing based upon physical master hierarchy properties (stores by age, comparative status, store status, etc)

    • Alternate view reporting hierarchies dynamically built during publishing that provided distinct 11 year view comparison capability driven by those future store status calculated values

    • Allowed for new/remodeled/closed store planning into the future periods and to forecast sales and expenses into those periods accordingly

  • Provided weekly, global reporting for nearly 80,000 employees for new, terminated, CC shifted, retired, temporary leave, etc.

    • Job activity classification derived from Sales, Operations, Product, and Support

    • HR based position reporting down to actual employee id

    • Various statistical measurements (FTE, Headcount, CC movement breakdown, etc)

    • Gender, job grade, building id, and incentive plan classification

    • Wage related costing classification

    • Allowed executives to verify strategic goals across an extremely complex and fluid labor force