WPM

1
Work Programme Management
WPM
Whats behind the icon?
2
(No Transcript)
3

• Tab 1 fields related to the identity and
  ownership of the items
• Reference id
• Deliverable type / number
• Responsible committee / working group

4

• Tab 2 sundry fields
• Title
• STF
• Current state (drafting, in Public Enquiry,
  published, etc.)
• EC mandate

5

• Tab 3 relational fields and rapporteur
• Keywords (AND combination possible)
• Projects (AND combination possible)
• Rapporteur (editor) name

6
In addition, it is possible to distinguish
between active and stopped items. Active
includes completed items (published deliverables)
which have not been withdrawn. It is not
restricted only to items which are still being
worked on.
7
(No Transcript)
8
(No Transcript)
9
(No Transcript)
10
Deliverable class R indicates a revision of an
existing item. Only use D for a brand new
deliverable document (spec).
11
Deliverable type will probably be same as
previous TS Technical SpecificationTR
Technical Report
12
Serial number use existing value modified
according to these rules
13
If moving to a new years release, increment the
number at the end. This shows the major version
number. Here we see 03.46 v7.x.x i.e. release
1998. Change this to 8 for a release 1999 spec
i.e. 03.46 v8.x.x .
Rule 1
0346Q7
0346Q8
14
If providing an update to an existing release,
add a suffix R1. If there is already a suffix
R1, change it to R2. (Or change R2 to R3, etc..)
Here we see 03.46 v7.0.0 (say) being changed to
7.1.0 (say).
Rule 2
0346Q7
0346Q7R1
15
Leave the creation date as the current date
unless there is some very good reason to change
it.
16
The new WI probably belongs to the same
committee. If not, change it as necessary.
17
You probably wish to make only a single copy.
WPM can make multiple copies if you wish.
18
Normally start with a clean schedule (milestone
set) by selecting Default.
19
Check this if there are comments associated with
the original record which you want to retain in
the new one. Normally, do not copy them.
20
When you click Duplicate, after an are you
sure? panel, the original WI record is copied,
incorporating the changes you required. Click
Update to make the necessary manual changes to
the new record ...
21
These fields will reflect the changes you made
whilst making the duplicate record.
22
You must now update the necessary fields of the
new record as shown in the following slides ...
23
The title will be unchanged ...
24
except for the version and possibly the
Release year.
25
Hint The scope field describes the work to be
undertaken in developing the deliverable. It is
not the text of the scope clause of the final
document.
Enter new Scope field text.
26
Hint If there is no current rapporteur, enter
the name of the committees support officer.
Check that the rapporteur identity is correct
enter the new one if not.
27
Verify the Support Officer identity.
28
The project set will be unchanged, unless the new
WI relates to a different release delete the old
release project and add the new.
29
Clear the pages counts (paper and soft).
30
Add a secretariat comment to justify the
creation of the new WI.
Hint ETSI rules demand that you furnish four
supporting ETSI member organizations in a
separate comment. This rule is relaxed for SMG
and 3GPP!
31
Most other fields can safely be ignored.
Except the schedule
32
(No Transcript)
33
You must modify the stock schedule proposed by
WPM to eliminate irrelevant milestones. You can
also add sets of milestones (then delete the ones
from the set you dont want).
34
You can add individual user selectable (code
5S) milestones.
You can - and must! - modify the milestone text
to describe the step desired.
35
Remember to fill in the date the event was
achieved ...
and to indicate the version of the spec at that
time.
36
WPM is also available on the web (read-only)
http//webapp.etsi.org/WorkProgram/Expert/QueryFor
m.asp
37
So much for theory. Now lets see a worked
example ...
38
MCC expert provides a new version of an existing
spec.
39
Identify the WPM Work Item which pertains to this
spec. You can use the status database to help
you in this ...
P\mcc\Databases\Status_SMG-3GPP-combined_JMM\stat
us_smg_3GPP.mdb
Run query jmm_Spec_Search--SMG3GPP_with_MIs
40
Find the spec of interest in the list. Take care
to choose the correct version.
Note that in this instance, no WI yet exists for
v6.2.0 - so start with the latest of the same
Release which does exist.
41
Take this WI reference (copy it to the clip board
if you wish).
42
Click Find.
The WI appears.
Insert (paste) the same WI reference into the
Full Search field of the WPM Select Work Item
screen.
Open it.
43
The WI record opens. (Depending on your screen
settings, you may see a multi-tab version of the
same thing.)
Click Duplicate to create a new record for the
new version of the spec.
44
Within WPM, the Duplicate Work Item window
appears.
45
Ensure the Class is R (for revision)
Add R1 to the WI reference (or change R1 to R2,
etc.).
46
Ensure the Technical Body is correct. Many GSM
items have been moved to a WG of a 3GPP TSG.
If necessary, change the TB using the pull-down
list.
47
Click Duplicate ...
It is normally not useful to copy over the
schedule ...
or the comments.
48
and confirm the creation of the new WI.
49
The new WI record is created.
Click Update to make changes.
50
Title change version no.
Scope indicate CRs at meeting no.
Check rapporteur name. (Type in correction if
necessary, and select from list offered if more
than one match.)
Clear page count.
Check Support Officer name.
51
Schedule eliminate unwanted milestones.
Milestones 2 to 7B can be selected ...
and deleted.
52
Schedule choose US milestone.
53
Schedule select Start of work milestone.
Schedule click Insert after.
Schedule The new US milestone appears.
Schedule Enter free text into milestone.
54
Schedule enter the version number resulting from
the plenary meeting.
Schedule enter the achieved date for milestones
1 to 8 as the last day of the meeting.
Schedule some (calculated) target dates appear
automatically.
55
save
Add a comment.
Record created.
56
save - then close
57
The End !