Brian Smith
Program Manager
Information Worker New Markets
Microsoft Corporation
What is Six Sigma
How we can expose project data to the
Project Guide
How we can expose external data through Project Center
How we can work with WSS templates
Pulling it all together with InfoPath
A rigorous approach to solving problems and improving processes by leveraging facts and data
Can be viewed from multiple perspectives
Philosophy
Measure
Methodology
Sigma
6 sigma
5 sigma
4 sigma
3 sigma
2 sigma
1 sigma
Defects per million Cost of Poor
Quality
3.4
<10% of sales World Class
230 10 to 15%
6,200 15 to 20% Industry average
67,000
310,000
700,000
20 to 30%
30 to 40% Noncompetitive
Histogram of C1, C2
Normal
900
800
300
200
100
0
700
600
500
400
132 138 144 150
Data
156 162 168
Variable
C1
C2
Mean StDev N
150.1
6.086 1000
150.0 0.9662 1000
Standardized data driven approach to problem solving
Process and input focus
Variance reduction and process optimization
Eliminating the opportunity for defects to occur
110
100
90
80
70
60
50
40
30
20
Subgroup
50
40
30
20
10
0
0
D M A
Problem “Y” Data
Integrity
Analyze
Inputs
LSL
Baseline
X X X
X X
X X
X
Problem
Statement 0 4 8 12
Process
A B C
16
Screen
Inputs
CTQ Statistical Toolset
I
Process
Changes
X
1
..X
2
Improved
“Y”
LSL
X
X X
“Y”
10
Inputs
X X X
X X
X X
X
30 Y= X
1
..X
2
40
0 4 8 12 16
50
C
Lock down
X’s
X
1
..X
2
Sustain
The Gain!
60 70
UCL=101.4
Mean=65.80
LCL=30.19
UCL=43.75
R=13.39
LCL=0
What is the Microsoft Office
Solution Accelerator for Six
Sigma?
A solution built on top of Microsoft
Office Project that aids the management, control and reporting of
Six Sigma project programs
A case study of how to extend Project to solve a specific business problem
Dynamic Project Guide
Financial tracking application
Extension to Windows SharePoint
Services integration
InfoPath Project Selection form
Microsoft Office Data Assistant for
PowerPoint
Project Data Service access to task content
Navigation
Document access
Context sensitive help
Uses .NET application rather than static XML file
Screen Shot of Project Guide
Hosting Office Web Components in
Project Professional and Project Web
Access
Accessing project related data through
Project Center views
So how does Project Center see our data?
Data table for Financials
One or more views to filter the data
Final view linked to Project
Stored Procedure
Project Center Reporting & Selection
How does the Project Center view get its data?
Columns are specified in the
MSP_WEB_VIEW_FIELDS
These will then be available to be added to Project Center views
The display text is specified in
MSP_WEB_CONVERSIONS
The data is found from the result of the stored procedure
MSP_WEB_SP_SEC_GetPortfolioViewRSBasedOnFiel dList
MSP_WEB_VIEW_FIELDS table
The table holds the references to all the fields available within Project Center views
A full reference can be found in pjsvrdb.htm on the
Project Server CD (in the docs directory)
Key fields to note:-
WFIELD_NAME_OLEDB
The name of the field used in the Microsoft Project OLE DB provider
WFIELD_NAME_SQL
The name of the field in the Microsoft Project Server database
(in the stored procedure in a few slides time)
WFIELD_NAME_CONV_VALUE
Refers to the CONV_VALUE field in the
MSP_WEB_CONVERSIONS table, which provides the localized description of the field
Continued….
MSP_WEB_VIEW_FIELDS table
WFIELD_TEXTCONV_TYPE
The type of field
1 String
4 Date
5 Percent (for example, 5%)
9 Cost (for example, $5.00)11Cost rate (for example,
$5/hr)
12 Units
15 Plain number
Only numeric values will be “rolled-up” in the views!
MSP_WEB_CONVERSION table
This table holds the localized string values referred to in the previous table
STRING_TYPE_ID
Refers to a valid STRING_TYPE_ID in the
MSP_WEB_STRING_TYPES table
CONV_VALUE
The ID value of the string (link to previous table)
LANG_ID
The ID of the language in which the conversion text is displayed, for example: 1033 is the language ID for
English, the default language for the database
CONV_STRING
The text value of the string
MSP_WEB_SP_SEC_
GetPortfolioViewRSBasedOnFieldList
This stored procedure gets the data from the database for the Project
Center views
The procedure is listed in the notes field for reference, including in bold our addition to link to our view table
In summary…
We add rows to the Project center tables
We amend the stored procedure to also link to our summary data view
We create the Financial view to have the per project data we want
We use multiple views for ease of following the flow – it could be one
Project and Windows
SharePoint Services
Integration
Project Specific WSS sites
Create sites that match the project template – complete with content
Front end or back end templates
Object Link Provider
Map content of site to tasks within project
Your friend on the command line
How do I load templates?
stsadm.exe -o addtemplates -f
<sixsigma.stp> -title "Six Sigma template"
description “Description goes here"
What templates do I have loaded?
stsadm –o enumtemplates
What is the “name” that the createsite method expects?
_GLOBAL_#1 or something similar
Collect project ideas
Rank based on customizable criteria
Create project and collaboration site based on templates
Take all or some of these scenarios to extend the use of Project and Windows
SharePoint Services
The source code for the Microsoft
Office Solution Accelerator for Six
Sigma will be made available to partners on request
Training session – date to be advised
Limited support – 90 days post training
© 2004 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.