SAP Community Network Wiki - Product Lifecycle Management - A Demo on Configurable Network

5/7/12 SAP Community Network Wiki - Product Lifecycle Management - A Demo on Configurable Network

1/15wiki.sdn.sap.com/wiki/display/PLM/A+Demo+on+Configurable+Network

Added by Mohamed Rafi, last edited by Mohamed Rafi on Apr 12, 2009

Welcome, GuestLoginRegister

Getting StartedNewslettersStore

SolutionsSAP Services & SupportAbout SCNDownloadsIndustriesTraining & EducationPartnershipCode ExchangeLines of BusinessUniversity AlliancesEvents & WebinarsIdea Place

A Demo on Configurable Network

Purpose:

The purpose of this page is to brief you about the usage of configurable netw ork, for this I have taken an Elevator Industry as an example.

Scenario:

MR is an elevator industry, w hich involves in manufacturing and installation of Traction Elevators and Hydraulic elevators. Their Elevator capacity ranges are 4,6,8,10,13 & 15 person and can install

elevator upto 8 f loors.Let us assume that duration of installation is dependent on No. of f loors and the manpow er required are dependent on Elevator Capacity(Size of the elevator depends on Elevator

Capacity i.e., Higher the elevator capacity bigger the elevator size)

Requirement:

1. To Create Single Standard Project for both type of elevator.

2. To group and maintain all the activities pertaining to Hydraulic and Traction Elevator in a Single Netw ork.

3. To calculate the Normal Duration of certain activities ,w hich depends on the No. of Floor(user input), automatically during Operative Project Creation.

4. To increase the Capacity required to execute the activity, w hich depends on the Elevator Capacity(user input), automatically during Operative Project Creation.

5. System should pick only the activities related to Traction or Hydraulic, not all, durng Operative project creation based on user input.

1. Standard Project:

Instead of creating tw o standard projects for Hydraulic and Traction elevator, We w ill create single Standard project and all the activities pertaining to traction and hydraulic elevator w ill be created in a

single netw ork. We w ill make this standard netw ork as configurable netw ork such that, w henever user creates operative project copying this standard project, System w ill copy only activities related to

Hydraulic or Traction elevator and not all.

1. Create Standard Project:



2. Create Standard Network

Follow ing are the details of the activities of standard netw ork. Please note that all the activities related to Hydarulic and Traction elevator are included in the same netw ork.

Activities common for all elevator types are marked as "ALL" and related to Traction is marked as "TRAC" and "HYD" for Hydraulic. Also Duration for certain activities w hich depends on No. of Floors

are not maintained. Please refer the above legend for further details.

Maintain the relation of all activities. For example, in case of Traction elevator if "Bedpalte for motor" starts after shaft alignment, and "Pow er Pack Installation" starts after "shaft alignment" for Hydraulic

elevator, then define both Bedplate for motor and Pow er pack installation as successor activity for Shaft Alignment.



Now w e w ill create Characteristic, Class, Dependency and Configuration Profile for the Standard Netw ork.

3. Create Characteristic

We w ill create follow ing characteristic:-

1. TYPE_EL : Which w ill take the character either "HYDL" or "TRAC"

2. FLOOR_EL : Which w ill take the numeric value from 2 to 8.

3. DURA_EL : Which w ill w rite the calculated value based on FLOOR_EL to "Normal Duration" (DAUNO) f ield of Activity Table.

4. CAPIN_EL : Which w ill take the numeric value of 4,6,8,10,13 or 15.

5. CAPC_EL : Which w rite the calculated value based on CAPIN_EL to "Number of Capacities required" (ANZZL) f ield of Activity Table.

DURA_EL :

AFVGD and DAUNO are entered in Reference Table and Field, so that the w hatever value assigned to DURA_EL w ill be assigned to DAUNO also.



Once the reference table and f ield are maintained in Additional data, System w ill overw rite the value entered in Basic data

We w ill change the Number of Char as 2 and decimal places to 0

Class Type:300 Variants w ill be maintained for all Characteristic in Restriction tab...So that no other class type can use the characteristic.



TYPE_EL:

FLOOR_EL:



CAPIN_EL:

CAPC_EL:



Note: Reference Table and Field w ill be maintained only for CAPC_EL and DURA_EL characteristics, and both the characteristics w ill be hidden from display.

4. Create Class

A Class called "ELEVT" is created under class type 300 and all the above characterisctics w ill be assigned to it.



5. Create Configuration Profile for Std. Network

A Configuration Profile called Elevators w ill be created for the Std. netw ork and the above class "ELEVT" w ill be assigned to this profile.



6. Dependencies:

Now We have come to the important part, Local Dependencies w ill be created for the follow ing Std. netw ork activities.

We w ill maintan follow ing "Selection Condition" Dependency for activities 140,150 & 180 w hich belongs to Traction Elevator only:

During creation of Operative project, System w ill include these activities w hen user selects "TRAC"

We w ill maintan follow ing "Selection Condition" Dependency for activities 160 & 170 w hich belongs to Hydraulic Elevator only:



During creation of Operative project, System w ill include these activities w hen user selects "HYDL"

Now w e w ill maintain "Action" Dependencies w hich calculates "Normal Duration" for activities 90, 100, 110, 120, 130 170, 220 & 270:

Whenever user enter values for FLOOR_EL, the system w ill calculate value as per above formula (f loor_el x 0.5) and assigns to the Normal Duration of the activity.

Same kind of action dependencies are maintained for other above mentioned activities but w ith different formula. Please refer to above table.

w henever user enter values for CAPIN_EL, system w ill check w hether CAPIN_EL > 10, if it is satisf ied then it w ill add 1 to the existing value in CAPC_EL.

Same kind of action dependencies are maintained for other above mentioned activities but w ith different formula. Please refer to above table.

2. Operative Project

1. Hydraulic Elevator, 6 Floors and 10 Person Capacity

Our Test Case:



Now w e w ill build Operative Project Copying the Std. Project.

Now System w ill show entry screen to f ill up the Value to the characteristic. Please note the yellow indicator at the bottom of the screen. Which show s that the entry is either incorrect or incomplete.



Now w e w ill give values to the characteristic

Now please note Green indicator, it show s the entries are correct and then press next.

Based on the above values, the system w ill check selection condition and action dependencies w hich is assigned to the activities.Iit w ill pick only the activities w hich is relevant to Hydraulic elevator and

the activity duration w ill be calculated based on No. of Floor and capacities based on Elevator Capacity.



Please compare the result w ith the test case. Since the elevator capacity is > 8, the system has increased the number of capacity required by 1 for the activities 170 and 210.

and the duration of activities 90, 100, 110, 120, 130, 170, 220 & 270 are calculated based on No. of Floors.

2. Traction Elevator, 8 Floors, 13 person Capacity:



Thanks,

A. M ohamed Rafi

Labels

Comments (3)

Follow SCN

Contact UsSAP Help Portal

PrivacyTerms of UseLegal Disclosure

ps_topic



Copyright

Documents

SAP Community Network Wiki - Product Lifecycle Management - A Demo on Configurable Network