Views

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.

Jump to: navigation, search
(Schedule for Delta Packages)
(Releases:)
Line 7: Line 7:
 
=== Releases:  ===
 
=== Releases:  ===
  
Last delivery: Delta Package 38  CV 3
+
Last delivery: Revision  Package 38.1  
Relase Date: February  25, 2013
+
Relase Date: March 4, 2013
  
 
<br>
 
<br>
Line 14: Line 14:
 
*'''EKB Version'''
 
*'''EKB Version'''
  
hip4000.ekb Version 38011<br>
+
hip4000.ekb Version 38103<br>
 +
hip4000c.ekb Version 38103<br>
 +
devices.ekb Version 38100<br>
 +
hp3kim9.ekb Version 38101<br>
 +
kondah4.ekb Version 37102<br>
 +
hpxpr.ekb Version 38013<br>
 +
osov3.ekb Version 38100<br>
 +
 
 +
ECS              Version  7.12f<br>
 +
 
 
<br>
 
<br>
  
Line 23: Line 32:
 
*'''Quicksales Modelizer'''
 
*'''Quicksales Modelizer'''
  
Modelizer Version 38009
+
Modelizer Version 38106
  
 
<br>
 
<br>
 
*'''SmartOffer'''  
 
*'''SmartOffer'''  
  
Rule Version 38006
+
Rule Version V38.1.08
  
 
=== [https://app-enterprise.siemens-enterprise.com/gdmsproxy/retrieve?id=3265712118 Releasedocumentation]  ===
 
=== [https://app-enterprise.siemens-enterprise.com/gdmsproxy/retrieve?id=3265712118 Releasedocumentation]  ===

Revision as of 09:05, 15 March 2013

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: Revision Package 38.1 Relase Date: March 4, 2013


  • EKB Version

hip4000.ekb Version 38103
hip4000c.ekb Version 38103
devices.ekb Version 38100
hp3kim9.ekb Version 38101
kondah4.ekb Version 37102
hpxpr.ekb Version 38013
osov3.ekb Version 38100

ECS Version 7.12f





  • Quicksales Modelizer

Modelizer Version 38106


  • SmartOffer

Rule Version V38.1.08

Releasedocumentation




Known Issue

Workaround's

  • At the moment none necessarily



Schedule for Delta Packages

Schedule 2013 for Delta Packages


Documentation


  • 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


  • 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).


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 CS Manual Media:Config_Service_Manual.pdf

IBASE Content Beispiel Media:IBASE-Inhalt-ext.pdf



How To Documents

Send Order from Quicksales
Media:User_Information_QuickSales_Order_Type.pdf

Handling of service features in Quicksales
Media:QS_user_information_regarding_service_features_for_HiPath_4000_systems.pdf


User Manual HiPath4000 Manager
Media:User_Manual_HiPath_Manager_Upgrade.pdf  

How to Resolve Inventory Data Problems in Hipath 4000 Systems
Media:User Manual_HIP4000_Inventory_Data_Repair_EXT_V1.pdf

Required Information when Opening a Trouble Ticket
Media:Required_Info_for_QS-Trouble_Tickets.pdf

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

Media:Config_Service_Manual.pdf


Process

HiPath4000 Expansion

Expansion Caracteristics
Media:Erweiterungsprozess.pdf


Important Links


TI Online -- Technical Information Online