3 ms·

Thanks for a complete list. I was not sure I could legally use the names on my website.

cgio 11y ago
No worries. I played around a little, given that I have done implementations with all the systems I mentioned above, and it looks interesting at first sight. I would have to look into it in more detail. By the way, I tried to create a new spreadsheet and it creates it (test) but when I try to view it, it gives me an error. It looks pretty easy for someone who knows what they are looking for, but others would be confused.
- egeria_planning 11y ago
  Thanks for testing. There are some misleading error messages. I will look into it. The problem was you did not "apply metadata" (from the tools menu) after creating a spreadsheet. If you have any ideas I would really like to simplify the UI. A spreadsheet gets much more complex with multidimensional data model. My idea was that people who are familiar with tools like TM1 or BPC would use the system to create planning solutions for their small and mid-size clients.
  - cgio 11y ago
    Just one piece of advise. Do not sacrifice usability for elegance. I can see you consistently apply a model that builds on metadata abstractions. Nevertheless, it is not conceptual consistency but expectations that should drive interactions. A difficult balance, given that consistency also improves accuracy of expectations but if you take big vendors, that consistency approach was taken to the limits by BPC. This is why everything feels like 10 extra steps. When someone creates artefacts they should be immediately available. The only thing that should necessitate a metadata application from a user perspective should be metadata (as in dimensions changes, not even member additions) and logic changes (if you need to optimise your calculations graph.) The rest should be transparent and separated at least visually from metadata. You can keep security in metadata, but calculation is a separate concept and you will most probably have to separate it when, as per your roadmap, you look into workflows. Do not get confused by the consistency. Look at the concepts from a user perspective and hide elegance in implementation if you can. I hope this helps. I will send you an email and we can discuss in more detail.

cgio 11y ago

No worries. I played around a little, given that I have done implementations with all the systems I mentioned above, and it looks interesting at first sight. I would have to look into it in more detail. By the way, I tried to create a new spreadsheet and it creates it (test) but when I try to view it, it gives me an error. It looks pretty easy for someone who knows what they are looking for, but others would be confused.

egeria_planning 11y ago
Thanks for testing. There are some misleading error messages. I will look into it. The problem was you did not "apply metadata" (from the tools menu) after creating a spreadsheet. If you have any ideas I would really like to simplify the UI. A spreadsheet gets much more complex with multidimensional data model. My idea was that people who are familiar with tools like TM1 or BPC would use the system to create planning solutions for their small and mid-size clients.
- cgio 11y ago
  Just one piece of advise. Do not sacrifice usability for elegance. I can see you consistently apply a model that builds on metadata abstractions. Nevertheless, it is not conceptual consistency but expectations that should drive interactions. A difficult balance, given that consistency also improves accuracy of expectations but if you take big vendors, that consistency approach was taken to the limits by BPC. This is why everything feels like 10 extra steps. When someone creates artefacts they should be immediately available. The only thing that should necessitate a metadata application from a user perspective should be metadata (as in dimensions changes, not even member additions) and logic changes (if you need to optimise your calculations graph.) The rest should be transparent and separated at least visually from metadata. You can keep security in metadata, but calculation is a separate concept and you will most probably have to separate it when, as per your roadmap, you look into workflows. Do not get confused by the consistency. Look at the concepts from a user perspective and hide elegance in implementation if you can. I hope this helps. I will send you an email and we can discuss in more detail.