In the new digital world where data lives everywhere, data catalogs are essential to your Enterprise Data Strategy. Herewith a graphic highlighting some of the key providers.
Early notification of the PowerMapping suite I with some associates are bringing to market. Select Customer and Project feedback very good. Also evolve into a Service called MapTo.
It have the ability to rapidly take non-standard arguably unknown data and rapidly correlate it with one or more Industry models. Accelerators for IAA and Guidewire exist with Acord, eTOM, TIA and others to follow.
Suite consist of a a) Mapper (POWERMAPPER) seeded from an Enterprise Repository allowing Project teams to do data mapping whilst the Project is doing what it is suppose to do. It also consist of the b) Validator (POWERVALIDATOR) that can validate mappings and provide degree of compliance. Lastly a cloud based repository service c) POWERDRIVE create enterprise knowledge ensuring mappings are getting more accurate in time. It also drive next gen visualisations amongst others data lineage and flow.
Suite is showing clear value when new Platforms are introduced with heavy duty legacy conversions typical in Insurance(new Product Admin Platforms). Also been used when driving data exploration when designing service interfaces and data warehouses.
What make YOU see the outline of a solution? Whether you are the builder, planner, designer or even the change agent that helps motivating for the new solution… what makes you see it?
The obvious is that any solution must be done for a reason and therefore you must be clear on what you are solving for. In doing so, the biggest problem I observe is that solution crafter’s are ignoring the 3 to FIVE rule.
The rule simply imply that ANYTHING about the solution you write down or draw should never be less than 3 items or more than 5 items.
OK here is the test; look at your latest Powerpoint deck, your Visio outline or even your emails describing the outline of the problem and/or the solution. If you cannot count the items you have a big problem… you are in no-where land. If the points typically are more than 5 you are fuzzy and cannot see the problem/solution and therefore other people that you are communicating with will even see it less. If however, you consistently describe the problem, solution and options respectively in 3-5 points you are seeing it. If you consistently do it in 3 you are on the money.
Current thinking dictates Data Models to be re-presented as ERD’s or UML structures when looking at structured data. Herewith something different when one wants to find patterns within the Data. Example is the IBM IAA BDM Model shown within a Cluster Circle Packing visualisation.
Labels is not shown to respect IBM copyright. Example was specifically chosen to show how it would work across a well matured data model with about 2000 entities and over 1200 attributes in support.
Recently I went through the AppStore thinking it may be quite easy to enter and manage it from a tablet. Though most are visually quite appealing they almost all fail when one want to edit time records, add additional properties or even report slightly different to what the App allows.
This led me back to faithful pivots with simple time-entries in Excel. Herewith sanitised version I use myself, just remember to refresh Pivot for latest views.
Right now, right or wrong, the active/recorded Business conversation in Corporates are largely embedded in Powerpoint which make it quite difficult if one wants to convey data bound visuals that are created in specialist tools like Visio or other Architecture specific tools. Those of you that struggles with this will understand exported images from these tools is not the answer either.
Enter Powerpoint Data Pump. You create your data in Excel and then use PowerPoint in a mail merge style whereby a new slide is generated for every row of data. Each column of data corresponds to named shapes (all you have to do is name the shape in Powerpoint the same as the column name) and the slide would be generated with appropriate data.
It is ideal for Visual Diagrams(Maps); for example Capability or Component Maps previously largely drawn by hand in Powerpoint or inclusive in other speciality tools. Therefore you can design “infographic” consisting of multiple shapes that is “linked” to the data and once generated will allow you to use these shapes either individually or leave them as normal slides.
A Business Case usually captures and motivates the reason why a given solution journey is embarked upon. Typically this is a well structured document that tells the story and outlines what benefit is expected at the end.
You can view or download the Calculator here.
This Post is not about the document but more about a way for the Solution Architect to quickly build a simple financial case in support. There is a fallacy that a business case is a thick tedious manuscript, written by professional consultants in an incomprehensible language. Hope it helps!!!
Good Solution Architects are not always renowned for keeping people up-to-date with status reports whilst solution is unfolding… right? …. mostly because the excitement at hand is creating the solution.
Being in that position many times I have created the following Solution Status Template for myself…. Download and see if it works for you.
Here is one of my versions you may download and modify to get a running start.
It is based on Excel with simple way to add data for reporting. Optionally you can also download and run the supporting cartridge for Telco’s and in so doing, modify the base Dashboard to become Telco/Mobile Network Operator specific.