CS 564 – UML

Example: Wine Merchant Ordering System

Quintessential Wine Distributors sell wine to local exclusive hotels. The new ordering system will enable their customers to place orders via a web site that enables the customer to build an order. Customers select quantities of specific wines from the on-line catalog, building the order and then, when finished, they submit the order. Each item is priced through a price list and the cost of orders is the sum of the individual items. Customers receive order confirmation and notice of planned delivery via email. Customers can view order at any time.

The order is relayed to the warehouse where each line item is considered and if it can be satisfied in full, the necessary stock is assigned to a delivery. If it cannot be satisfied in full, the delivery is held until new stock appears. Stock turns over regularly, so there is not a significant delay. A copy of the order accompanies the delivery. The warehouse inventory system is already in place.

Orders are checked to see how payment is to be made. Orders may be pre-paid with credit cards or if the customer has a good credit line, they may be invoiced. An existing accounting system keeps a credit indication and produces the invoice. The customer is invoiced when the order is submitted and the order is not considered closed until it is paid.

Certain customers are allowed to make priority orders where delivery is made even if the order is incomplete. Delivery of outstanding items occurs after the back-ordered stock arrives. Priority orders are taken first when allocating newly arrived stock.

Static Structure

• Examine Nouns• Analyze

• Relevant• System?

• Attribute• price

• Commonality• Hotels are Customers• Do Hotels order or do

people order?

Customer Hotel

Order Catalog

Order Confirmation Line Item

Priority OrderStock

Delivery

Static Structure

• Generalization• Car is a Vehicle• Boat is a Vehicle

• Specialization• Priority Order is a

special Kind of Order

Order

Priority Order

Static Structure

• Associations• Relation Name• Roles• Multiplicity

• Types• Recursive• Attributed• N-ary

Company Employeeemploys

works for

1 *employer employee

Employeeclerk

manager

reports toleads

1

*

Company Employee1..* *

EmploymentFrom: Date

To: Date

Train Seat1..*1

Passenger

1..*

Reservation

Static Structure

• Aggregation• Entirety-Part

• Composition• Existence-

dependent parts

Car Wheelshas1 3..4

Document Paragraph0..*1

Static Structure

Customer

Hotel

Orders

Catalog

Order Confirmation

Line Item

Priority Order

Stock

Delivery

cont

ains

Held Order

has1 *

1

1..*

Static Structure

Customer

Hotel

Orders

Catalog Item

Order Item

Priority Order

Employee

Delivery

cont

ains

Held Order

has1 *

1

1..*

Catalog ItemContains1 *

1 *employs

Location

has 11..*

1..*

1

Conta

ins1

1

delivered to

Example

• Develop Use Cases• From Requirements• Identify Actors• Identify Main Tasks

• Access/Modify Information

• Inform system of any environmental changes

• Reports of unexpected events

• Use Case Concept• Complete, orthogonal,

externally visible functionality• Initiated by an actor• Identifiable value to the actor

OrderingSystem

Customer

<<actor>>AccountSystem

<<actor>>Inventory

Shipping Clerk

ViewStatus

Create & Submit Orders

Example

• Dealing with Out of Scope Requirements• Business Models

• Use Case Concepts• Complete, orthogonal,

externally visible functionality• Initiated by an actor• Identifiable value to the actor• Extends

• Show Optional or Conditional Behavior

• Includes• Show a use case making full

use of a common use case

OrderingSystem

Customer

<<actor>>AccountSystem

<<actor>>Inventory

Shipping Clerk

ViewStatus

Create & Submit Orders

ReceivePayment

UpdateHeld Orders

PrepareDelivery

<<extend>>

Use Case DocumentationUse Case 1 Create Order & Submit

Brief Description A customer wishes to order a delivery of wine. Provided that the customer has a non-delinquent account or has pre-paid, the wine ordered is removed from inventory and delivered to the customer.

Actors Customer, Inventory, Shipping Clerk, Account System

Trigger Customer visits web site & creates an order.

Preconditions Customer has established and account.

Customer email address is known.

Customers are pre-designated to enter priority orders.

Main flow Customer visits web site, signs on and is validated. Customer selects items from the online catalog and builds an order. Customer is appraised of current cost of order. Customer may denote that the order is a priority Customer submits order when done.

A customer order number is assigned and the customer’s credit and account status are checked. If credit is OK or the account shows pre-payment, then the order is sent to the inventory system. …..

Alternative flows Priority Order

Account is delinquent. Action taken ? Cancelled ?

Changes to or cancellation of the order?

Order cannot be fulfilled ?

Postconditions Order has been created and is either been cancelled or been fulfilled.

Package Diagram

• Groups related use cases

• Forms basis for a functional partitioning from the users point of view.

• Shorthand for tracking within the project

Order Entry

ViewStatus

Create & Submit Orders

Use Case DocumentationRequirement Use Case

The customer can request a wine delivery by logging on to WWSM’s web site and submitting an order.

UC 1

The customer builds the order by selecting items from the on-line catalog and specifying a quantity.

UC 1

Only customers that have an account with WWSM can create an order. UC 1

At any time during the process of creating an order, the customer can determine the current price of the order.

UC 1

The customer signifies that the order is complete by submitting the order. When an order is submitted, it is assigned an order number.

UC 1

Customers with the priority privilege may designate an order as priority. UC 1a

The customer can view the status of an order at any time by logging on to WWSM’s web site and requesting status on all open orders.

UC 2

Once an order is submitted, it is checked to see if it is pre-paid or whether the customer has an account in good standing. If these conditions are not met, the order is held until the conditions are met or the order is cancelled.

UC 1

…

Requirements Request Analysis

• Captures description and source

• Prioritization• References to Use

cases and other documents

Requirement #: Requirement Type: Event/UseCase #:

Description:

Rationale:

Source:

Fit Criterion:

Customer Satisfaction: Customer Dissatisfaction:

Dependencies: Conflicts:

Supporting Materials:

History:

Snow Cards

CRC Cards

• Process for capturing domain knowledge in the class structure

• Group activity• Domain experts• OO experience• Product responsibility

• Process• Brainstorm classes• Review and form initial

model• Review scenarios and

identify responsibilities and collaborators

class namesubclasses:superclasses:

responsibilities collaborators

CRC Cards: Example

• Wine Merchant• Initial Objects

• Shipper• Object in system that fulfills

user requests

• Packer• Set of objects that draws

wine from stock.

• Bottle• Set of objects that

represent wines

• Scenario• Customer orders wine

class name :Shippersubclasses:superclasses:Check out book for user Borrower, Book

class name :Packersubclasses:superclasses:Can borrow Book

Know set of books

class name :Bottlesubclasses:superclasses:Know if overdue

Check out

Calculate due date

Know due date

Know borrower

Know in or out

Using CRC for Integration

Ordering System• Initial Objects

• Customer• Identifies customer

• Pre-Order• Creates order with customer

• Order• Order submitted by customer

• Accounting• Verifies credit and prints

invoice

• Inventory• Assigns inventory to order

• Dispatcher• Prepares delivery

• Scenario• Create Order – inventory

available

class name : customersubclasses:superclasses:Authenticate user

Accounting

class name :pre-ordersubclasses:superclasses:Assign order number

CatalogAdd/delete items

class name :ordersubclasses:superclasses:Email confirmation

Assign line itemKnow orders

Update assigned status

Post order for delivery

Know if order is fulfilled

Know users

Authorize Users

Know priority customers

Verify credit

Submit Order Order, Accounting

Price Order for user

Customer

Inventory

class name :dispatchersubclasses:superclasses:Delivery Report

Assign Order to Route

Order, Location, Customer

Order

Print Shipping Slip Order

Completed delivery status Order

Activity Diagrams

• Behavioral• Functional

Decomposition• Parallelism• Swim Lanes• Multiple Transitions

Activity Activity

[x>0]

[x<0]

[x=0]

[x>0]

[x<0]

Synchronization Splitting

As of 4 Nov

Activity Chart

EnterOrder

CheckCredit

[submitted]

[aborted]

[denied] AllocateInventory

[approved]

PrepareDelivery

ReceivePayment

Create Order& Submit

<<trace>>

Order Entry Finance FinanceShippingInventory

Management

Update HeldOrders

<<extends>>

Held Orders

Activity Diagram

OrderAssigned

Assign HeldOrders First

For each order item

Held Orders Done?

AllocateInventory

[not done]

<<trace>>

RequestOpen Items Inventory

Inventory Arrived

For each priority order

Items Available

Items Not Available

For each order item

HoldOrder

UpdateOrder Item

UpdateOrder Item

Post toDelivery

[done]

PriorityOrder?

[no]

New ItemsAssigned?

[no]

For all unfulfilled orders

For all fulfilled orders

Guidance

• Simplicity

• Effective communication

• Iterate between Use Case, Behavioral, and Structural

Activity DiagramAllocate

Inventory

<<trace>><<extends>>

Update HeldOrders

Held Orders

New Orders

FulfillOrders

Submit Held Orders for

Assignment

Submit New Orders for

Assignment

Held Orders

Completed

(AND)

FulfillOrders

Activity DiagramFulfill

Orders

<<trace>>

HoldOrder

Post toDelivery

PriorityOrder?

[no]

New ItemsAssigned?

[no]

AssignInventoryTo Order

Order Fulfilled?

[no]

For each order

All Orders Assigned

Activity Diagram

OrderAssigned

For each order item

<<trace>>

RequestOpen Items Inventory

Items Available

Items Not Available

UpdateOrder Item

UpdateOrder Item

Assign Inventory to

Order

Activity Diagram

<<trace>>

Update HeldOrders

SelectHeld OrdersInventory Inventory

Arrived

AllocateInventory

Sequence DiagramCustomer Accounting Pre-Order Order Inventory Dispatch

Customer

Login

Authorized

Credit Check

Good Credit

Select Create Order

Catalog

Enable Catalog Access

Select Items

ItemsSet Quantity

Done with items

Order Price

Submit Submit Order

Email Confirmation

Submit OrderInvoice Customer (mail)Request Items

Items Assigned

Order Ready for Dispatch

Shipping Clerk

Delivery Report

Assign Orders to Route

Delivery

Status Order

Delivery CompletePaymentPayment Received

Integration

Tier 1: Functional Architecture

Tier 2: Use Cases

FunctionalArchitecture

FunctionalArchitecture

Functional components and embedded systems

Use Cases

Use Cases

Behavior Models

Behavior Models

Static Structure

Static Structure

Sequence Diagrams

Sequence Diagrams

CRC Cards

CRC Cards

Tier 3: Use Case Scenarios

Tier 3: Detailed Functional Requirements

Customer Requirements

Customer Requirements

Case Study

Requirements for New Phone Line Administration System

Functional & Non-Functional Requirements

Requirements Specification Spec

1. Project Title, Revision Number and Author2. Scope and Purpose of the system3. Measurable Organization Value4. Description5. Feature List including ICED T and Simplified QFD

analysis6. Interfaces7. Constraints8. Change Log and Expected Changes9. Responses to the unexpected10. Measurements11. Glossary12. References

Line Card (Upper Half)

Phone Number

Acct Number

Service Card

Route Block

Name

Address

SwitchModule

Panel orBay

Port Date Order

M. Reg. Ana. Access

Cable Pair Terminal BindingPost

Account, Service, & Customer Info

Original Order, Order Date, &

Switch Port Identification

Outside Plant Segments

Premises Equipment (Ignore)

Line Card (Lower Half)

N

Time Class Date

CommTime

Trouble Found, Cause, andWork Done

Time OK

Repeating Trouble History Segments

Trouble History Block

Test Shows GivenTo

TimeGiven To

TroubleReported

O

I

BA TroubleCode

AP

AP

AP

AP

AP

AP

AP

AP

AP

Last Trouble Cleared on Previous Card

No Troubles that year

Trouble History Event

Trouble Report

Ticket Number

Phone Number

Center EC

Class Category

Trouble Description

Date

Commitment

Reach Number

Access

Date Time Call Reason

TR Class

Initial Trouble Report

8350764

321

West 57th

264-7004

Res CD

Name

Address

Type

105

Conrad, Charles

2240 N. Hubbard

NDT, All Phones

8-15-75 8:00ABefore After

Time

264-3535Called Number

3:00P

8-12-75 10:32A

OOS

NewCommitment

NewAccess

Before After New Reach Number

Customer Calls

(Continuation)

(Continued)

WP IST RTE RSLT RemarksEC

Cause Disp ECType

TestDate

TestTime

Test Results EC

Initial Test

Trouble Processing

Steps & Close

Information

Don’t worry about data elements,Worry about the structure

Don’t worry about data elements,Worry about the structure

JiffyLOOP Vision

• Integrated physical and logical corporate OSP database

• Broadband Ready

• Customer Contact Information

• Base for replacing legacy systems

• Loop Qualification

• EWO Decision Support

ControllerCRM

Copper Loop Plant

CentralOffice

YourHouse

Manhole

Cable

Terminal

Drop

MOV

• Reduce time to assign DSL for qualified lines from an average of three days to 10 minutes while the customer is on-the-phone

• $15 to $30 per line per year labor savings

Value Proposition

• Mid-band loop qualification for Internet services

• Access qualification for Long Distance

• Enterprise Loop Database

• Broadband migration strategy

• Legacy System strategy

JiffyLOOP Value Breakdown

• Projected savings for specials assignment ~ $7.50 per access line

• Projected savings for loop makeup, cable throws, and cable rewires ~ $7.00

• Projected savings for automated LFACS update with cable throw and loop makeup information ~ $10.00 per access line

• Total savings of ~ $24.50 per access line per year

JiffyLOOP Costs

• Conversion cost ~ $5.00 per access line• JiffyLOOP CoGs ~ $5.00 per access

line• Includes Hardware and OS, JiffyLOOP

software, maintenance, 3rd party software, and network software

• Profit ~ $5.00 per access line• Total cost of ~ $15.00 per access line

JiffyLOOP Cost / Benefit

• 1-year payback

• $24.50 per year savings after payback

• Instant Loop™ qualification for the front office

• Integrated physical and logical network database

• Reusability of network data for such departments as planning, marketing, asset management, construction and dispatch

‘Buy Not Build’ Philosophy-

• Company 1 provides the PRIS Loopmake-up and cable throw modules

• Company 2 provides the DB-ABLE physical Database & Blueprint generator

• Companies 1 and 2 DB-3 extend DB-ABLE to include spatial and logical data. New Database is DB-ABLE/heavy

More partners

• Company 3 provides external interfaces and legacy encapsulation

• Company 4 provides Outside Plant Engineer client

Evolution Plan- Does it fit your FMO

• Step 1- Combine Physical and Logical Data Bases • Step 2 Mechanize Engineering Design Functions • Step 3 - Replace Street Address Guide • Step 4 – Replace Inventory Data Base• Step 5 – Replace Assignment and Repair

Generic Telco Operating Expense Model

G&A22%

Prod & Svc Support

27%

Customer Operations

& Sales24%

Deprec. & Amitoriz.

22%

Data Admin

7%

SW/NT Ops19%

Acct Mgmt15%

Eng9%

Cust Svc15%

Prov/Inst18%

Rpr/Mtce

17%

Total Operating Expenses $450 per line

(nominally)

Total Operating Expenses $450 per line

(nominally)

Operations Expenses $230 per line

(nominally)

Operations Expenses $230 per line

(nominally)

Churn Cost — Transition Metric

1.0

1.2

1.25

1.4

1.6

1.8

0% 5% 10% 15%

PROV & MAINT EXPENSE

MULTIPLIER (average over

all lines)

CHURN RATE

CHURN RATE > 5% TRANSITION TO NEXT LEVEL

WORST CASE

NOMINAL CASE

POTS Environment

Causes of Churn

Churn Is Due To:

• Unplanned POTS Growth

• Other Narrowband Services Growth (e.g.., Business DS1)

• Offering Broadband Services

• Maintenance Problems

Why is this churn expensive?

• 80:20::20:80 rule

Even though 80% of manual assignments

can be eliminated with flow-through the 20%

that remains takes 80% of the work.

• 1:3::3:1 rule (worst case)

Every new line or maintenance change

requires three rearrangements; for every

three rearrangements one error is made.

Provisioning Paradigm Shift

MDF Switch

DirectOrder Entry

Service OrderProcessing

Installation

MechanizedAssignment

MemoryAdministration

NetworkInventory

ServiceNegotiation

ServiceActivation

Inventory

Activation

•Activate in Near Real Time•Use Real Data, not the Model•Effective Use of Logical Resources•Activation of POTS/Video

Data QualityIssues

ONU HDT

Switch

LegacyEnvironment New OS-LP

Maintenance Paradigm Shift

MDF Switch

LoopSurveillance

TroubleReceipt

Test

Analysis

Dispatch

Limited Real-TimeDetection

Surveillance

Dispatch

Correlation

TroubleReceipt

•proactive Maintenance•Customer is no longer the Alarm System•End-to-End Customer Care (Telecommunications/Video)

ONUHDT

Switch

BB Laser

LegacyEnvironment New OS-LP

Instant Loop

QueryLFACSQueryLFACS

P2

DB-AbleDB-AbleD2

Initiate LMULDB CreationInitiate LMU

LDB Creation

P3

Analyze Dataand Create

Options

Analyze Dataand Create

Options

P5

DataRequest

EE1

LFACS

EE1

LFACS

EE2

COSMOS

EE2

COSMOS

AnalyzeILRN

AnalyzeILRN

P1

EE3

Instant Loop

EE3

Instant Loop

ILRN DataQuery

Analyze Data and Determine

if LMU is Possible

Analyze Data and Determine

if LMU is Possible

P6

M* QueueM* QueueD1

CreateLMU LDBCreate

LMU LDB

P4

LMU LDBLMU LDBD3

LFACS and Cosmos Data

LFACS and COSMOS Data

LFACS &COSMOSRequest

ILRN

FormattedLFACS &COSMOS

Request

SQL to AccessDB Creation

LMULDB

EE3

Instant Loop

EE3

Instant Loop

EE1

LFACS

EE1

LFACSRMA

No

Yes

Customer

ReturnYes/NoAnswer

Instant LoopLFACS M* PRIS Server PRIS Client MapGen LDB Database

DB-Able

Register

Check & RequestILRN

Place inQueue

ILRN DataFormatLFACSRequest(s)LFACS

Request(s)

LFACSData

LFACSRequest(s)

LFACSData

Loop LDBReport Request

Loop LDB Report Request

Loop LDB Report Completion NoticeCreate LoopLDB Report

Loop LDB Report Completion Notice Loop Computation

& Loop Value Analysis

Determine ifLMU is possible

Return Y/NY/N

C.S.R.C.S.R.

C.S.R.C.S.R.

ILRN

As-Built PostingLFACS M* PRIS Server PRIS Client MapGen LDB Database

DB-Able

Retrieve EWO Retrieve EWO

FTP EWO Packet Notification

RedlinesRedlines

EWO Completionand LFACS Data

EWO Completionand LFACS Data

ChangeStatus

AddChanges

Update LFACS

Affected Tile List

Tile Mapgen

Tile LDB

DMSDMS

GeoBaseGeoBase

Completion Notification

FTP and Archive Final Post EWO

CreateDWG

CreateLDB

FTP Tile & LDB

Check-outEWO from

DMS

LDB Update

Update Completion Notice

Completion Notice

EWO RMA

Geo Base TilesGeo Base TilesD1

Analyze Data and Create

Options

Analyze Data and Create

Options

AnalyzeData

AnalyzeData

P3

CreateIn-service

Count Reports

CreateIn-service

Count Reports

P4 P5

CreateEWOLDB

CreateEWOLDB

P9

CreateEWO

MapGen

CreateEWO

MapGen

P8

CreateGeographic

Extent

CreateGeographic

Extent

P7

DB-AbleDB-AbleD2

UpdateJiffyLOOP

UpdateJiffyLOOP

FinalizeEWO

FinalizeEWO

P10

RouteEWORouteEWO

P11 P12

Geo Base TilesGeo Base TilesD1

DB-AbleDB-AbleD2EE2

Construction

EE2

Construction

PrepostEWO LDB

Tile MapGenand Tile LDB

DMSDMSD3

Archive EWO

PendingUpdates

EWOLDB

API

EWOLDB

API

EWOMapGen

EWOPacket

EWOMapGen

TerminalData

View/Browse

EWO LDB Request View/Browsex,yExtents

EWO MapGenRequest

Options

Selection UserSelection

UserSelection

P6

EE1

LFACS

EE1

LFACS

EWO LDB

ECCRReport

AnalyzeRMA

AnalyzeRMA

P1

ECCRReport

ECCR Request

EE1

LFACS

EE1

LFACS

EE1

LFACS

EE1

LFACS

In-serviceCount Report

In-serviceCount Request

ComplementsRanges

M* QueueM* QueueD4

ECCRReportECCRReport

P2

RMA

Query

RMA DataAffectedComplements

EE1

LFACS

EE1

LFACS

EWOPacket

PRIS QueuePRIS QueueD1

OptionsQuery

EWO RMALFACS M* PRIS Server PRIS Client MapGen LDB Database

DB-Able

Register

Check & RequestRMA

Place RMA in Queue

EWO RMA DataCreateComplementRange

ECCRRequest

ECCRReport

ECCRRequest

RMA

FormatECCRRequest

ECCRReport Browse Tile to

Determine AffectedComplements

Format In-ServiceCount Request

In-Service CountRequest

In-Service CountRequest

In-Service CountReport

In-Service CountReport

Determine Options and Place in Queue

UserSelectsOption

Check andRequest Options

Receive Options

EWO RMA (cont’d)LFACS M* PRIS Server PRIS Client MapGen LDB Database

DB-Able

DetermineGeographicExtents

CreateDrawing(s)

Launch & ScheduleEWO MapGen(s)

Launch & ScheduleEWO MapGen(s) Create

EWO LDBCompletion NoticeAdd SpliceChevrons & Engineering Notes

EWO CompletionNotice

Setup EWOSetup EWO

UpdateDB-Able

EWO LDB Update

Completion orErrors

Completion Notice

ErrorsCompletion Notice

Completion

User Re-evaluate

Cancel LDB Update(Partial or All)

Affected Tile Listand EWO for Archival

Tile Mapgen

Tile LDB

Completion Notification

CreateDWG

CreateLDB

DMSDMS

GeoBaseGeoBase

FTP and Archive Final Post EWO

FTP Tile & LDB

CS 564 Requirements © 2004 Prof. Bernstein

JIFFY LOOP Client / Server ArchitectureServer Platforms

Hardware Operating System

• HP • Solaris• HP – UX• Linux

Server Software• PRIS Application• Broad Band Engineering Tools• DB - Able / Heavy Database• MapGen• NetGen• Validation & Connectivity• DB - Able Migration Tool

CAD / GIS• AutoCAD• Autodesk World• Autodesk World Express• Autodesk Mapguide

Client Platforms

Operating SystemHardware

• Pentium 133 MHz pen hardware 24 megabyte minimum

• Windows XP

Client Software• DB - Able Toolbar (GUI)• DB - Able Conversion Tool (GUI)• Data Maintenance Tool (GUI)• GeoCode• DB - Traveler (pen system)• PRIS EWO Tools• PRIS Facility Assignment Tools• PRIS SAG & Living Unit Tools

UNIXServer

Network• TCP / IP

Database• Oracle

Addressable Market

• 250 million loops in North America• Conservatively, 75% are twisted pair loop or

roughly 187 million access lines• 75% of the access lines provide POTS

(Plain Old Telephone Service); 25% provide Special Services

• 500 million loops worldwide and growing• INTERNET Service Providers• Cable Companies

Special Service Circuits

• 25% or 50 million lines are used for specials (DS1, DS3, T1, T3, and other non-POTS services)

• Of these 12.5%, 25 million require special re-engineering

• Loop makeup and cable throws are needed for:• Specials• Plant Extensions• Rehabilitation

• FACS does service provisioning: POTS and non-design specials automatically; Design Specials manually

• Services needing design do not flow-through FACS.

• POTS circuits have been tuned (bridge taps, load coils, inductors, etc.) for low-fi voice. Special services require the removal of all such devices to enable high speed digital data transmission.

Present Method of Operation

Present Method of Operation (cont’d)

• Loop make-up is computed by outside plant engineers relying on outside plant blueprints.

• Most outside plant engineering records are paper documents

• Cable throws are designed by hand.

• Cable throws are manually posted to LFACS

FMO

• Automate specials assignment, loop makeup, and cable throw EWO’s

• Loop qualification status to the customer service representative

• Maintain left-in equipment data for DSL

• Combine the What, Where and How of the copper plant to create an enterprise database

JiffyLOOP Stakeholders

• Customers• Developers

• Telephone Technicians

• Application Technology Companies

• Platform Supplier Companies

• Investors

JiffyLOOP

• 9 month to 12 month payback

• Complete Conversion of outside plant physical, spatial and logical data

• EWO decision support

• Automatic ADSL and other design special service provisioning

• Instant Loop™ qualification for customer contact

Other JiffyLOOP Benefits

• Integrated physical and logical network database

• Loop Unbundling Database

• Data Mining for as planning, marketing, asset management, construction and dispatch departments

• Customer Contact Information

• Base for replacing legacy systems