ERICSSON ///
 
PROGRESS REPORT
Uppgjord - Prepared
EPL/X/AS C Israelsson
Datum - Date
1998-05-15
Rev
A
Dokumentnr - Document no
20/12021-4/FCP1010211/1 Uen
Godkänd - Approved
EPL/X/AS (C Israelsson)
Kontr - Checked
 

Tillhör/referens - File/reference
 
Information copy                           Distribution List
EPL/X/A      Nils Granered                 EPL/X/AS     Bo Nordeman
EPL/X/AS     Lars M}nsson                  
EPL/X/AT     G\ran Axelsson                
EPL/X/AX     Clas H\gvall                  
EPL/XC       Tomas Forsberg                
EPL/S$/XV    Jan Pettersson                
                                           

Progress Report May-1 (w.20), EPL Design in V5.2 ML

Contents
1Results achieved since the last report

2

Expected Result

3

Time Schedule and Budget

4

Deviations from plan

5

Risks

6

Actions

7

Other Matters

8

References


1   Results achieved since the last report

The FSD work is ongoing. The period of inspections is ongoing. Two FSD documents have now reached TAPP status.


Details:


- FF, Administration updating ongoing, RFINS 15/5
-> EPA?, CR not yet answered.
any meaning now?
plan RFPCSSS w.21
plan TAPP 25/5


- FF, Connection of V5.2 links ongoing,
RFINS 4/5 (log 15/5)
plan RFPCSSS 15/5 (log 29/5)
plan TAPP 29/5


- FF, Impacts in non-V5 funct. ongoing,
RFINS 6/5 (log 13/5)
RFPCSSS 15/5 (log 19/5)
plan TAPP 26/5


- FF, Link handling & blo/deblo ongoing,
RFINS 12/5 (log 14/5)
plan RFPCSSS 15/5
plan TAPP w.23


- FF, Tone Sending ongoing,
RFINS 8/5 (log 12/5)
plan RFPCSSS 15/5 (log 26/5)
plan TAPP 26/5


- FF, C-channel handling ongoing, PREL 13/5
plan RFINS 18/5
plan RFPCSSS 25/5


- FS, ML interfaces ongoing
EPL team input not started


- FD, AM traffic via LIV5 ongoing
plan RFINS w.21
plan TAPP w.22


- FD, Link id verification ongoing
plan RFINS 15/5 (log w.22)
plan TAPP w.22


- FD, Link blo/deblo ongoing (review 8/5)
plan RFINS w.21 (log w.22)
plan TAPP w.22


- FD, Interface link handl ongoing,
RFINS 17/4 (log 15/5)
plan TAPP 22/5


- FD, C-channel handl not started
plan started Sept.-98


- FD, RPG switch-over not started


- COD, LOBLI TAPP 8/5


- COD, LOBLE TAPP 8/5


- POD, C-channel sw-over failure ongoing
plan RFMAXE 18/5


- POD, Current logical C-ch data ongoing
plan RFMAXE 18/5


- OPI, Op. init C-channel sw-over investigation started
plan RFMAXE w.22


- OPI, C-channel sw-over failure investigation started
plan RFMAXE w.22


- AI2, V5CCH not started
- AI2, LITS not started
- AI2, LIV5G not started
- AI2, V5PRTCL not started

The BSD phase has started. A kick-off was held 12/5, with the main issue to do the team plan.

New resources have started in the design.

BSD planning is ongoing, (with discussions about reorganization, more resources and necessary documents), trying to reach the timeplan goals.

2   Expected Result

The FSD work will continue and be finalized. Inspections shall be done, and the documents techn. approved and stored.

The project documentation will be finalized and stored.

The BSD shall start in all teams. Planning shall be checked and actions done to minimize risks, and reach the timeplan goals.

3   Time Schedule and Budget

ALREADY USED MH:
Amount of used mh tot: 3824 mh (Mar-beginning May)
Amount of used FSD mh: 2765 mh
Amount of used BSD mh: 53 mh

WORK TO BE DONE:
Amount of FSD work: 3744 mh (techn. work) -> 5000 mh tot
Amount of BSD work: 5493 mh (techn. work) -> 7000 mh tot
Amount of follow-up: 4000 mh

ESTIMATED REMAINING:
Estimated remaining FSD work: 890 mh (techn. work)
-> 1100 mh tot

FSD details, see chapter 1.


MS3 30/3 -> 15/5 -> 31/5?
MS4 30/4 -> 31/5


AD0 25/6
AD1 17/7
AD3 19/8
AD4 2/9

4   Deviations from plan

Delayed MS3.


Delayed MS4. FSD phase ready end April, was the planned goal, (delayed FSD start = delayed FSD end).

Main part of BSD (techn.) delayed to end May. BSD partly started in the beginning of May (new resources starting to read).

Some BSD resources have been delayed to 18/5.

Some new resources to come.

5   Risks

The delay of the Feasibility impacts the FSD directly as the resources are the same in the two phases. In consequence also the BSD will be affected.

Delay of input from the base documents.

Delay/removal of resources (due to problems in earlier projects). Is actually already a fact. More to come?

The C-channel handling, which is big and complex.

When are AI2s really needed? Possible to have ready at 26/5 (SP2)? These documents are dependent on the FSD documentation.

More coordination needed than expected.

Requests of review/inspection resources are very late.

Seems like almost everybody wants to have vacation during July. Someone must be here for the AD delivery.

6   Actions

Checking on what can be left out and what can be done later without major impact, is ongoing.

Resource discussions are ongoing.

The C-channel team is under re-organization.

Requests for team external BSD expert/review help shall be considered early.


7   Other Matters

-

8   References

-