TM1 Design Queries

[vipul.bahl@gmail.com]

Hi Experts,

We are in a middle of a design activity for a client and we have few concerns. Kindly help us in resolving the same:

Environment:

Tool: Cognos TM1 10.1.0
OS: Windows 2008 R2
Development single server: RAM 28 GB
Production two servers (App & Web server): 32 GB Web and 64 GB App
Users: 400

We are proposing that the interface provided to the users is 'Web Application' (Contributor) since there is an approval work-flow for budgeting.

Concern /Clarification Sought:
   
1. There are a couple of choices: create one contributor application for the entire set with one e-list or have multiple contributor applications with their individual e-lists. Are there advantages/ disadvantages of either which would compel a particular approach?
2. The e-list would have 400 odd ownerships (total users). Are there concerns around the number of users that can be accommodated in a Contributor application?
3. Are there any tweaks/ methods to enhance performance on 'Contributor'. Alternately are there any design elements to guard against to ensure performance in 'Contributor'?
4. While the typical infra sizings are provided on generic parameters before model design, are there any sizing templates to ascertain the design related sizing required? Would the cube and model design cause a sizing significantly different from the generic sizing?
5. Based on the number of dimensions and dimensional elements, the current cube cells exceed 1.5 trillion and have a sparsity of about 45%. While we understand that TM1 is extremely scalable in terms of size, would this become an issue when we use the application on 'Contributor'?
6. In certain scenarios it becomes necessary to use dynamic subsets. Are there alternatives and will these be issues in a Contributor based application?

Regards,
VB