So workflows

Req##

Requirement description

Priority

NC.KYIV.KMA.2014.FLW.SOW.1

The system should provide the ability to create a WorkFlow process based on Service Order with Status = ‘Processing’ for different scenarios (‘New’, ‘Modify’ and ‘Disconnect’).

M

NC.KYIV.KMA.2014.FLW.SOW.2

The system should provide the ability to create the defined Tasks under each WorkFlow and assign these Tasks to particular User Groups.

M

NC.KYIV.KMA.2014.FLW.SOW.3

For ‘New’ scenario at first the system should check automatically the availability free ports on router. If router has free ports the system should create the Task and assign it to Provisioning Engineer Group.

If router does not have free ports the system should create the Task and assign it to Installation Engineer Group.

M

NC.KYIV.KMA.2014.FLW.SOW.4

The system should provide the ability to reassign particular Task from one User to another user under defined User Groups

M

NC.KYIV.KMA.2014.FLW.SOW.5

The system should provide the ability to complete or suspend particular Task. After completing defined Task the system should create automatically next Task.

O

NC.KYIV.KMA.2014.FLW.SOW.6

The system should allow Installation Engineer to install and create new router in the system.

M

NC.KYIV.KMA.2014.FLW.SOW.7

The system should allow Provisioning Engineer to assign the port of the router and create the circuit and refer the assigned port to Service Instance (for ‘New’ scenario).

M

NC.KYIV.KMA.2014.FLW.SOW.8

The system should allow Provisioning Engineer to unassign the port of the router and remove the circuit and brake reference between the assigned port and Service Instance (for ‘Disconnect’ scenario).

M

NC.KYIV.KMA.2014.FLW.SOW.9

The system should allow Provisioning Engineer to modify some parameters for particular Service Instance (for ‘Modify’ scenario).

O

NC.KYIV.KMA.2014.FLW.SOW.10

After completing all Tasks under Service Order the system should change automatically the Status of Service Order from ‘Processing’ to ‘Completed’. And the system should change automatically the Status of Service Instance from ‘Planned’ to ‘Active’ (for ‘New’ scenario) and from ‘Active’ to ‘Disconnected’ (for ‘Disconnect’ scenario)..

M

NC.KYIV.KMA.2014.FLW.SOW.10

The system should allow to document port as ‘free’ while provisioning ‘Disconnect’ scenario, so the port can later be reused for new SI.

M

Req##

Requirement description

Priority

NC.KYIV.KMA.2014.FLW.RI.1

The system should document Devices and provide ability to create one in provider location.

M

NC.KYIV.KMA.2014.FLW.RI.2

The system should document the Ports as entities linked with Device.

M

NC.KYIV.KMA.2014.FLW.RI.3

Device is introduced by Cisco 7606 with preinstalled 60 GE Ports. All ports could be used for end user connect.

M

NC.KYIV.KMA.2014.FLW.RI.4

The system should document physical link to end user as Cable.

M

NC.KYIV.KMA.2014.FLW.RI.5

The system should document logical entity of provided Service as Circuit.

M

NC.KYIV.KMA.2014.FLW.RI.6

The system should allow deleting of Cables and Circuits.

M

NC.KYIV.KMA.2014.FLW.RI.7

The system should take into account dependencies between Cables and Circuits.

M

NC.KYIV.KMA.2014.FLW.RI.8

The system should allow linking Cable and Circuit by common used Port.

M

NC.KYIV.KMA.2014.FLW.RI.9

The system should allow creating Devices, Ports and Cables only by Installation Engineer.

M

NC.KYIV.KMA.2014.FLW.RI.10

The system should allow creating Circuits and linking it to Ports by Provisioning Engineer.

M

Req##

Requirement description

Priority

NC.KYIV.KMA.2014.FLW.EML.1

The system should send e-mails to users, based on business rules.

M

NC.KYIV.KMA.2014.FLW.EML.2

The system should notify users via personal e-mails, and via e-mails sent to user groups.

M