Difference between revisions of "FAQ Configurator and Modelizer"
The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.
(→Salestool for IM) |
(→Releases:) |
||
| (97 intermediate revisions by 3 users not shown) | |||
| Line 7: | Line 7: | ||
=== Releases: === | === Releases: === | ||
| − | Last delivery: | + | *'''Last delivery:''' Delta Package 42, |
| + | '''Relase Date:''' February 3, 2014 | ||
| − | + | <br> | |
| − | < | + | *'''EKB Version''' |
| + | |||
| + | <table width="30%"> | ||
| + | <tr> | ||
| + | <td>devices.ekb</td><td>Version 42001</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>hip4000.ekb</td><td>Version 42006</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>hip4000.sdb</td><td>Version 42006</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>hip4000c.ekb</td><td>Version 42006</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>hip4000c.sdb</td><td>Version 42006</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>hp3kim9.ekb</td><td>Version 42000</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>hpxpr.ekb</td><td>Version 42001</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>lmo.ekb</td><td>Version 39100</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>osbizv1.ekb</td><td>Version 42003</td> | ||
| + | </tr> | ||
| + | <tr> | ||
| + | <td>osov3.ekb</td><td>Version 42000</td> | ||
| + | </tr> | ||
| + | </table> | ||
| − | |||
| − | + | *'''ECS Version''' 7.12o<br> | |
<br> | <br> | ||
| − | *''' | + | *'''Quicksales Modelizer''' |
| − | Version | + | Modelizer Version CR 42006 |
| − | + | <br> | |
| + | *'''SmartOffer''' | ||
| − | + | Rule Version V41.2 | |
| + | ===[https://app-enterprise.unify.com/gdmsproxy/retrieve?id=3265712118 Releasedocumentation]=== | ||
<br> | <br> | ||
| Line 32: | Line 67: | ||
== '''Known Issue''' == | == '''Known Issue''' == | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<br> | <br> | ||
| − | ''' | + | == '''Workaround's''' == |
| − | + | * At the moment none necessarily | |
| − | <br> | + | == <br><br>'''Schedule for Delta Packages'''== |
| − | + | [https://app-enterprise.unify.com/gdmsproxy/retrieve?id=3273209136 Schedule 2014 for Delta Packages] | |
| − | + | <!-- | |
| + | [https://app-enterprise.unify.com/gdmsproxy/retrieve?id=60589744 Schedule 2014 for Delta Packages] | ||
| + | --> | ||
<br> | <br> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== '''Documentation'''¶ == | == '''Documentation'''¶ == | ||
| Line 78: | Line 91: | ||
*'''User manual for the EKB configuration tool''' | *'''User manual for the EKB configuration tool''' | ||
| − | + | <!-- | |
| − | [[Media: | + | *''' '''[[Media:Manual_HiPath_4000_en.pdf]] |
| + | --> | ||
<br> | <br> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | *'''HiPath4000 Expansion Orders''' | ||
| + | Expansion orders of HiPath4000 systems using the IBASE data. | ||
| + | The tool support for HiPath4000 expansion orders is based on the "as-is" data of the customer system concerned, i.e., the actual hardware (and software) configuration at the time of the order. | ||
| + | The necessary hardware information is obtained from the system in the form of a "partial REGEN" batch file, which contains AMO commands for "regenerating" the relevant system hardware configuration (line cards, shelves, locations, etc.). This data is stored in IBASE under the appropriate system number, in addition to the feature numbers (L-numbers) and quantities ordered in previous tool sessions. In the case of new orders, the information is provided by the original KONDA (CONDA) generating batch file, which reflects the "as-is" configuration status of the system only until the first partial REGEN file can be generated. | ||
| + | The partial REGEN batch file is generated in the HiPath system concerned with the aid of a special Service procedure, and automatically stored in the IBASE inventory data. Please refer to the relevant Service page for details. | ||
| + | A newer partial REGEN file obtained from a customer system and loaded in the tool for a system expansion order can also be transferred to IBASE using the "Configuration Service" function of the tool. See also below. | ||
| | ||
| Line 97: | Line 110: | ||
*'''Partial REGEN''' | *'''Partial REGEN''' | ||
| − | + | A "partial REGEN" is an AMO batch file that contains configuration data similar to the KONDA/CONDA (see below), but obtained as output from a HiPath system in response to a REGEN AMO call-up. The AMO commands reflect the "as-is" hardware configuration status of the system concerned, i.e., information on line cards, shelves, locations, etc. The name "partial REGEN" is derived from the fact that the file is required to contain only a limited subset of the total AMO information available in a HiPath system. | |
example [[Media:Teilreg_Beispiel.pdf]] | example [[Media:Teilreg_Beispiel.pdf]] | ||
| Line 103: | Line 116: | ||
| − | |||
| − | + | *'''KONDA/CONDA = Configuration Data''' | |
| + | The CONDA file (KONDA is the German acronym) contains an AMO command batch for generating the hardware and software configuration data in the HiPath system (e.g., boxes, shelf types, line cards, system software, etc.). The CONDA file is generated in the configuration tool when a system is first ordered, and also later as a result of each subsequent system expansion order. The information is stored in IBASE and can also be downloaded from DIAMOS by Service engineers. The CONDA file reflects the "as-sold" status of a system. | ||
example [[Media:KONDA-Beispiel.jpg]] | example [[Media:KONDA-Beispiel.jpg]] | ||
| − | |||
<br> | <br> | ||
| + | <br> | ||
| + | *'''How do I get CONDA access?''' | ||
| + | IF you need the CONDA regularly, an SAP account can be requested.<br> | ||
| − | + | Please contact Mr. Schmidt, Rudolf; FIN IT GO 5; rudolfschmidt@unify.com | |
| − | |||
| − | |||
| + | <br> | ||
| + | *'''KONDA/CONDA or partial REGEN''' | ||
| + | The IBASE data of a HiPath 4000 system will always contain CONDA files ("as-sold" information) and, once this information has first been generated and stored, partial REGEN files ("as-is" information) . For the purposes of the configuration tool, the hardware information contained in the newest file is always definitive. | ||
| + | <!-- | ||
| + | IBASE-Characteristics [[Media:IBASE-Characteristics.pdf]] | ||
| + | --> | ||
| − | |||
| − | + | *'''What information is stored in the IBASE?''' | |
| + | For each HiPath system number stored, the IBASE data contains three (3) distinct data blocks with relevant inventory information. | ||
| + | - Customer data | ||
| + | - Feature data (ordered L-numbers and quantities) | ||
| + | - Hardware configuration data, as defined in the CONDA ("as-sold" information) or partial REGEN ("as-is" information). | ||
| + | <br> | ||
| − | + | After each expansion order, the IBASE content for the system concerned is updated and stored in full. The previous IBASE records remain unchanged and available in the archive. Archived data records can be restored (re-activated) at any time, if required. | |
| − | |||
| − | + | *'''Upload Partial REGEN to IBASE''' | |
| + | ''For direct Sales''<br> | ||
| − | + | please see SIRA-Hompage | |
| − | + | ''For Partners''<br> | |
| − | |||
| − | |||
| − | |||
| − | |||
| + | Upload Partial REGEN via ConfigService | ||
| + | <!--CS Manual [[Media:Config_Service_Manual.pdf]] | ||
| + | --> | ||
IBASE Content Beispiel [[Media:IBASE-Inhalt-ext.pdf]] | IBASE Content Beispiel [[Media:IBASE-Inhalt-ext.pdf]] | ||
| Line 145: | Line 167: | ||
== '''How To Documents'''¶ == | == '''How To Documents'''¶ == | ||
| − | Send Order from Quicksales<br>[[Media:User_Information_QuickSales_Order_Type.pdf]] | + | '''Send Order from Quicksales'''<br> |
| + | <!--[[Media:User_Information_QuickSales_Order_Type.pdf]] --> | ||
| − | + | '''Handling of service features in Quicksales'''<br>[[Media:QS_user_information_regarding_service_features_for_HiPath_4000_systems.pdf]] | |
| + | <br>'''User Manual HiPath4000 Manager'''<br> | ||
| + | <!--[[Media:User_Manual_HiPath_Manager_Upgrade.pdf]] --> | ||
| | ||
| − | How to Resolve Inventory Data Problems in Hipath 4000 Systems<br> | + | '''How to Resolve Inventory Data Problems in Hipath 4000 Systems'''<br> |
| − | [[Media:User Manual_HIP4000_Inventory_Data_Repair_EXT_V1.pdf]] | + | <!--[[Media:User Manual_HIP4000_Inventory_Data_Repair_EXT_V1.pdf]]--> |
| + | <br> | ||
| − | + | '''Required Information when Opening a Trouble Ticket'''<br> | |
| − | Required Information when Opening a Trouble Ticket<br> | + | <!--[[Media:Required_Info_for_QS-Trouble_Tickets.pdf]]--> |
| − | [[Media:Required_Info_for_QS-Trouble_Tickets.pdf]] | ||
== '''Salestool for IM''' == | == '''Salestool for IM''' == | ||
| Line 164: | Line 189: | ||
'''Product Structure '''( QSBW Systeme)<br><br> | '''Product Structure '''( QSBW Systeme)<br><br> | ||
| − | [[Media:Systems-Structure--Delta- | + | [[Media:QS--Systems-Structure--Delta-37-0-12108.pdf]] |
Products with EKB | Products with EKB | ||
| Line 178: | Line 203: | ||
''''Upload Partial REGEN via ConfigService''' | ''''Upload Partial REGEN via ConfigService''' | ||
| − | [[Media:Config_Service_Manual.pdf]] | + | <!--[[Media:Config_Service_Manual.pdf]]--> |
| − | ''' | + | == <br>'''Process''' == |
| − | + | '''HiPath4000 Expansion''' | |
| − | + | Expansion Caracteristics<br> | |
| + | <!--[[Media:Erweiterungsprozess.pdf]]--> | ||
| + | <br> | ||
| − | + | == '''Important Links''' == | |
| − | |||
| − | |||
<br> | <br> | ||
| − | + | [https://enterprise-businessarea.unify.com/ti_ic/deutsch/index.html TI Online -- Technical Information Online] | |
| − | |||
| − | |||
| − | |||
Latest revision as of 15:05, 6 February 2014
Contents
Master Data Configurator and Modelizer
This Wiki provides explainations and answers for ECS and Quicksales Modelizer related topics. As a sales engineer you might be interested in this subject.
Global Information¶
Releases:
- Last delivery: Delta Package 42,
Relase Date: February 3, 2014
- EKB Version
| devices.ekb | Version 42001 |
| hip4000.ekb | Version 42006 |
| hip4000.sdb | Version 42006 |
| hip4000c.ekb | Version 42006 |
| hip4000c.sdb | Version 42006 |
| hp3kim9.ekb | Version 42000 |
| hpxpr.ekb | Version 42001 |
| lmo.ekb | Version 39100 |
| osbizv1.ekb | Version 42003 |
| osov3.ekb | Version 42000 |
- ECS Version 7.12o
- Quicksales Modelizer
Modelizer Version CR 42006
- SmartOffer
Rule Version V41.2
Releasedocumentation
Known Issue
Workaround's
- At the moment none necessarily
Schedule for Delta Packages
Schedule 2014 for Delta Packages
Documentation¶
- Overview of products with configurator within the sales tools
- Media:Overview_EKB_products_Sales_Tools_06.07.2011.pdf
- User manual for the EKB configuration tool
- HiPath4000 Expansion Orders
Expansion orders of HiPath4000 systems using the IBASE data. The tool support for HiPath4000 expansion orders is based on the "as-is" data of the customer system concerned, i.e., the actual hardware (and software) configuration at the time of the order. The necessary hardware information is obtained from the system in the form of a "partial REGEN" batch file, which contains AMO commands for "regenerating" the relevant system hardware configuration (line cards, shelves, locations, etc.). This data is stored in IBASE under the appropriate system number, in addition to the feature numbers (L-numbers) and quantities ordered in previous tool sessions. In the case of new orders, the information is provided by the original KONDA (CONDA) generating batch file, which reflects the "as-is" configuration status of the system only until the first partial REGEN file can be generated. The partial REGEN batch file is generated in the HiPath system concerned with the aid of a special Service procedure, and automatically stored in the IBASE inventory data. Please refer to the relevant Service page for details. A newer partial REGEN file obtained from a customer system and loaded in the tool for a system expansion order can also be transferred to IBASE using the "Configuration Service" function of the tool. See also below.
- Partial REGEN
A "partial REGEN" is an AMO batch file that contains configuration data similar to the KONDA/CONDA (see below), but obtained as output from a HiPath system in response to a REGEN AMO call-up. The AMO commands reflect the "as-is" hardware configuration status of the system concerned, i.e., information on line cards, shelves, locations, etc. The name "partial REGEN" is derived from the fact that the file is required to contain only a limited subset of the total AMO information available in a HiPath system.
example Media:Teilreg_Beispiel.pdf
- KONDA/CONDA = Configuration Data
The CONDA file (KONDA is the German acronym) contains an AMO command batch for generating the hardware and software configuration data in the HiPath system (e.g., boxes, shelf types, line cards, system software, etc.). The CONDA file is generated in the configuration tool when a system is first ordered, and also later as a result of each subsequent system expansion order. The information is stored in IBASE and can also be downloaded from DIAMOS by Service engineers. The CONDA file reflects the "as-sold" status of a system.
example Media:KONDA-Beispiel.jpg
- How do I get CONDA access?
IF you need the CONDA regularly, an SAP account can be requested.
Please contact Mr. Schmidt, Rudolf; FIN IT GO 5; rudolfschmidt@unify.com
- KONDA/CONDA or partial REGEN
The IBASE data of a HiPath 4000 system will always contain CONDA files ("as-sold" information) and, once this information has first been generated and stored, partial REGEN files ("as-is" information) . For the purposes of the configuration tool, the hardware information contained in the newest file is always definitive.
- What information is stored in the IBASE?
For each HiPath system number stored, the IBASE data contains three (3) distinct data blocks with relevant inventory information.
- Customer data
- Feature data (ordered L-numbers and quantities)
- Hardware configuration data, as defined in the CONDA ("as-sold" information) or partial REGEN ("as-is" information).
After each expansion order, the IBASE content for the system concerned is updated and stored in full. The previous IBASE records remain unchanged and available in the archive. Archived data records can be restored (re-activated) at any time, if required.
- Upload Partial REGEN to IBASE
For direct Sales
please see SIRA-Hompage
For Partners
Upload Partial REGEN via ConfigService IBASE Content Beispiel Media:IBASE-Inhalt-ext.pdf
How To Documents¶
Send Order from Quicksales
Handling of service features in Quicksales
Media:QS_user_information_regarding_service_features_for_HiPath_4000_systems.pdf
User Manual HiPath4000 Manager
How to Resolve Inventory Data Problems in Hipath 4000 Systems
Required Information when Opening a Trouble Ticket
Salestool for IM
Quicksales
Product Structure ( QSBW Systeme)
Media:QS--Systems-Structure--Delta-37-0-12108.pdf
Products with EKB
HiPath 4000
HiPath 4000 Manager V5
OpenScape Xpressions V6
'Upload Partial REGEN via ConfigService
Process
HiPath4000 Expansion
Expansion Caracteristics
