Microstrategy Status Report

Customer / Project Sterling Jewelers, Phase 1, 15109

STATUS REPORT V1.10 Customer Contact Foluso Fayomi, [email protected]

MicroStrategy Contact Sai Charan, [email protected]

MICROSTRATEGY STATUS REPORT

ENGAGEMENT STATUS SUMMARY FOR 07/18/2011-07/22/2011 n CATEGORY STATUS COMMENTS Overall 4 Working on creating and testing data mappings

Scope 3 Scope has been defined for this week and next week. The scope keeps on changing depending on user requirements and the availability of data.

Time 3 Currently all deliverable timelines are being met.

Risk 2 The Schema objects are connected directly to the Transactional data. There is no separate data model for the data warehouse.

2 There are no time, product, or geography hierarchies in the Credit module

2 We are creating attributes without consulting the users so we have to do a lot of re-work when the users give us their feedback.

2 Modifying the schema on the fly, ie. editing relationship to fix a specific report is good for that 1 report but this can break other reports. There’s no test plan made to existing reports to make sure the change didn’t break them.

Procurement 5 No procurement issues detected.

RECOMMENDATIONS

STATUS DETAILS

- As per the meetings with Merchandising department this week, they requested us to build a separate folder for Special Orders with new attributes and metrics matching the Special Orders Universe in Business Objects.

- Started off with building the Special Orders in MSTR from scratch. Adjusted some of the related mappings and testing the new attributes and metrics to match the Business objects attributes.

- Resolving the tream track issues besides the Special Orders universe.

- Live assistance on Friday for the Merchandizing department.

- Meetings with Foluso and BI Team members regarding the critical issues and daily status.

Sravan’s Notes:

- Working on the issues assigned to me in team track. I’m respoinsible for Operational Amdiminstration department team track issues.

- Most of the issues deal with data mappings, where I had to remap the attributes to get the right results or match up with Business objects joins.

- Testing the newly created objects in the development.

- Mettings with Foluso on some of the critical issues.

SCOPE MANAGEMENT

List the discussed project changes that impact scope and final decisions related to these changes. Participants are those that contributed to the decision making process. Participant roles are qualified using RACI: Responsible (not used in relation to scope), Accountable (individual responsible for the decision), Consulted (individuals that contributed to the decision), and Informed (individuals or groups notified of the change)

Proposed Change Decision and Impacts Decision Participants

The initial plan was to convert just the Business Objects reports to MicroStrategy. Now Foluso and the team discuss with users converting their personal database schemas and converting some of the MS Access reports and schemas. Even though Foluso says that we are only meeting with the users to get their requirements for future phases, he still asks Pat to map some attributes and metrics for some users and answer user requests. This is leading to a scope creep. There needs to be a cutoff point where we won’t accept any new requests in the current phase.

The users also keep changing their minds about what they need. Even though there were several meetings with the users initially to get their requirements, they were not educated enough about the tool so now they have different requirements after they saw the tools. They asked us to delete 200 attributes that were created for credit department because they don’t need them.

Ray and Foluso expressed a lot of interest in pursuing Dashboards and Mobile in the near future but not until all reports are converted. In addition, I also think not until they have a DW! Foluso showed me their plan for Phase 1 DW which is just a copy of OLTP DB. Currently the reports are slow cause the data are not aggregated so unless a DW model is designed and architected, we won’t get to deliver DB and mobile at an acceptable performance. I also offered to help convert some of the reports so we can complete at deadline and not just be a support team to the users who are responsible for converting their own reports.

TIME MANAGEMENT

HOURS AND SCHEDULE

THIS NEXT PERIOD SCHEDULE PERIOD CONSULTANTS MON TUE WE THU FRI HOURS D Sai Charan Amujala 40 √ √ √ √ √ Sravan 40 √ √ √ √ √ Total 80

TASK SUMMARY

Summary of active and pending tasks, for more details see the Project Schedule for this project

Activity Status Comment

Worked on addressing helpdesk In Progress S.C. requests from users and logging previous ones in Team track.

Troubleshoot some meta data In Progress S.C. errors for credit, sales and merchandising

Work on conversion of 72 reports Completed J.Y. from Supply Chain - Merchandise

Work on fixing SDK problem with On Hold J.Y. clustered environment on Data Lineage

Work on conversion of their largest On Hold J.Y., S.C. This is supposed to be their most complex report with 26 report: Assortment Review queries. Foluso says if we get this converted the rest should be easy. Sai and I will tackle this as a team when I come back on 6/13.

RISK MANAGEMENT

Risks and issues currently being managed, for more details see the Risk and Issue Log for this project

LEVEL RISK ITEM ISSUE MITIGATION PLAN

HIGH The Schema objects are connected All the attributes and facts are I discussed this issue with Foluso directly to the Transactional data. connected directly to the transactional and the rest of the team. Foluso There is no separate data model tables. There is no star schema so told me that they purchased an for the data warehouse. there are no lookup or fact tables. ETL server to start building a Those transactional tables do not have proper data model with a star any indexes built into them. This leads schema. Patrick will be getting ETL to the reports being extremely slow to training and he will work on

run and the attributes are mapped to creating this model. For the time tables that contain millions of rows. A being we will have to work with table scan across those millions of the current structure, then Shelly rows has to be done every time an will convert all the attributes and attribute element search is done (for facts to point to the new model filters, prompts, …etc.) once it gets created.

UPDATE 03/25: Foluso and Patrick met and Foluso decided that they will just replicate the Transactional tables to a separate environment. They will not build a data warehouse OLAP structure (no star schema). I am not sure why they purchased the ETL tool (Datastage). They could replicate the tables in Oracle directly. Patrick already does that for the Training environment.

HIGH There are no time, product, or There are no defined time, product, or Spoke to Foluso and the rest of the geography hierarchies geography hierarchies. This makes it team. The hierarchies will be almost impossible to build dashboards created using the ETL tool. or be able to drill on reports.

UPDATE 03/25: Since they will not be building a data warehouse, I am not sure how we will create those hierarchies. I will have to speak to Foluso to see if we can build them in the new replicated database. IBM will come inhouse to install the ETL tools in Three weeks, then Patrick will take a training in tht tool afterwards. So, those hierarchies cannot be built before May.

HIGH We are creating attributes without In Merchandising, a lot of assumptions I asked Foluso to get an analyst consulting the users so we have to about attributes and relationships are from the merchandise department do a lot of re-work when the users made since the team that works on to help us with the mappings but give us their feedback. mapping has no business knowledge. he said if we get the users involved they will require more things and it Also in Credit, the users are not will take more time. So, his involved enough in the mapping solution was to make assumptions process. This week, they asked us to and finish the mappings, then the delete 200 attributes that were users can test it and tell us what is created because they do not need wrong afterwards. them. That’s a waste of hours and hours of development time. UPDATE 04/08: we are already getting a lot of requests from users for changes that need to be made in the mappings and display of attributes.