On a more off the wall note, I just realized that we have a bit of a double take (ha!) here concerning the idea and name “PowerPivot Twins”. The code name for PowerPivot was “Project Gemini”. The name Gemini had been chosen for this project because of its meaning:
Gemini – Gemini (pronounced /ˈgɛmɪnaɪ/, Latin: twins, symbol ♊) is one of the constellations of the zodiac known as “the twins“
Within the BI world, the “twins” are the traditionally conflicting ideas of the Users who are trying to model, analyze, and share the data and the IT Administrators who are trying to provision, administer, and secure the data. With PowerPivot, we are able to unite these “twins” because we are:
- Giving Users the ability to understand the data by giving them more power within the tool they trust: Excel
- Giving IT Administrators the ability to manage all of this data by using the information management tool of choice: SharePoint.
But even more interesting than the fact that the “PowerPivot Twins” allows us to pay homage to our “twins” roots within Gemini…even we, the PowerPivot Twins ourselves, pay homage to the idea of these two “twins”.
I, Denny Lee, work for the SQL Customer Advisory Team; in the case of PowerPivot I typically represent the customer – i.e. the Users. Dave Wickert works for the Analysis Services team; in his previous role as an Analysis Services guru and current role as the PowerPivot SharePoint Integration PM, he typically represents the IT Administrator.
So we, the “PowerPivot Twins”, pay homage to Project Gemini not just in reference to our twins roots, but also that we ourselves represent the two equal parts of the BI twins.
Just food for thought (or perhaps I just need more sleep) 
