Work Programme Management WPM Whats behind the icon

Work Programme Management WPM What’s behind the icon?

There are three tabs with a variety of fields you can use to select the Work Item records of interest.

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

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

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

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.

Click “Duplicate” to create a new WI record based on the present one.

You will be offered this panel.

Deliverable class: “R” indicates a revision of an existing item. Only use “D” for a brand new deliverable document (spec).

Deliverable type: will probably be same as previous: TS = Technical Specification TR = Technical Report

Serial number: use existing value modified according to these rules:

If moving to a new year’s release, increment the number at the end. This shows the major version number. Here we see 03. 46 v 7. x. x i. e. release 1998. Change this to 8 for a release 1999 spec i. e. 03. 46 v 8. x. x. Rule 1 0346 Q 7 0346 Q 8

If providing an update to an existing release, add a suffix R 1. If there is already a suffix R 1, change it to R 2. (Or change R 2 to R 3, etc. . ) Here we see 03. 46 v 7. 0. 0 (say) being changed to 7. 1. 0 (say). Rule 2 0346 Q 7 R 1

Leave the creation date as the current date unless there is some very good reason to change it.

The new WI probably belongs to the same committee. If not, change it as necessary.

You probably wish to make only a single copy. WPM can make multiple copies if you wish.

Normally start with a clean schedule (milestone set) by selecting “Default”.

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.

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. . .

These fields will reflect the changes you made whilst making the duplicate record.

You must now update the necessary fields of the new record as shown in the following slides. . .

The title will be unchanged. . .

… except for the version and possibly the Release year.

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.

Hint: If there is no current rapporteur, enter the name of the committee’s support officer. Check that the rapporteur identity is correct; enter the new one if not.

Verify the Support Officer identity.

The project set will be unchanged, unless the new WI relates to a different release: delete the old release project and add the new.

Clear the pages counts (‘paper’ and ‘soft’).

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 3 GPP!

Most other fields can safely be ignored. Except the ‘schedule’:

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 don’t want).

You can add individual “user selectable” (code 5 S) milestones. You can - and must! - modify the milestone text to describe the step desired.

Remember to fill in the date the event was achieved. . . … and to indicate the version of the spec at that time.

WPM is also available on the web (read-only): http: //webapp. etsi. org/Work. Program/Expert/Query. Form. asp

So much for theory. Now let’s see a worked example. . .

1 MCC expert provides a new version of an existing spec.

Identify the WPM Work Item which pertains to this spec. You can use the ‘status’ database to help you in this. . . P: mccDatabasesStatus_SMG-3 GPP-combined_JMMstatus_smg_3 GPP. mdb Run query jmm_Spec_Search--SMG+3 GPP_with_MIs

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 v 6. 2. 0 - so start with the latest of the same Release which does exist.

Take this WI reference (copy it to the clip board if you wish).

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.

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.

Within WPM, the “Duplicate Work Item” window appears.

Ensure the “Class” is R (for “revision”) Add R 1 to the WI reference (or change R 1 to R 2, etc. ).

Ensure the “Technical Body” is correct. Many GSM items have been moved to a WG of a 3 GPP TSG. If necessary, change the TB using the pull-down list.

It is normally not useful to copy over the schedule. . . Click “Duplicate”. . . … or the comments.

… and confirm the creation of the new WI.

The new WI record is created. Click “Update” to make changes.

Title: change version no. Scope: indicate CRs at meeting no. (GSM 02. 07 version 6. 2. 0 Release 1997) CRs at SMG#31. Check Support Officer name. Check rapporteur name. (Type in correction if necessary, and select from list offered if more than one match. ) Clear page count.

(GSM 02. 07 version 6. 2. 0 Release 1997) CRs at SMG#31. Milestones 2 to 7 B can be selected. . . Schedule: eliminate unwanted milestones. … and deleted.

Schedule: choose US milestone.

Schedule: select “Start of work” milestone. Schedule: click “Insert after”. Schedule: The new US milestone appears. SMG#31 Schedule: Enter free text into milestone.

Schedule: enter the achieved date for milestones 1 to 8 as the last day of the meeting. Schedule: some (calculated) target dates appear automatically. Schedule: enter the version number resulting from the plenary meeting.

save Add a comment. Record created.

save - then close

The End !