You are on page 1of 20

Cloudis Ltd

CMPIC Data Import Wizard
User Manual
Document No: UM/05015
Revision: 6
Name
Prepared by:

Signature

Date

Tony Mahaffey (CLOUDIS)

29-NOV-10

Verified by:
Approved by:
DOCUMENT REVISION HISTORY
Rev

Status

Amendment/Reason

Date

Author

1

ISSUED

Initial Creation

22-SEP-05

Tony Mahaffey

2

ISSUED

Include Cable Types, new logging function,
general cosmetic changes.

29-JUN-06

Tony Mahaffey

3

ISSUED

Include Appendix with input data formats.

05-OCT-06

Tony Mahaffey

4

ISSUED

Extend functionality to include Node and
Segment import.

21-MAY-09

Tony Mahaffey

5

ISSUED

Cable Usage no longer mandatory.

24-DEC-09

Tony Mahaffey

29-NOV-10

Tony Mahaffey

Cable Estimated Length column added.
Scope increased to include additional library
data, also merged cable/device data.
New optional update/delete functionality.
6

ISSUED

Option Sets retained between sessions
Preview option.
Device Near Nodes.
Cable Free-format fields x 3.
Bundle fields (Cable and Cable Type)

CMPIC Data Import Wizard, User Manual

DISTRIBUTION LIST
Name

Company and Role

Tony Mahaffey

Cloudis Ltd

Function
Author

1 Introduction
The Data Import Wizard has been introduced as a means of simplifying the population of CMPIC data from
external sources. This functionality is especially useful when migrating legacy data to CMPIC.
The Wizard was originally designed for the import of new data only. As the functionality within this screen is
stacked on top of our API, this has been further extended to permit the update and deletion of data (cable
types excluded), subject to existing API rules. This is managed via a separate, and optional, "action" column; if
this is not used, or a value of "-" is passed, the "action" (insert or update) is determined, based on the
existence (or not) of the record in CMPIC. Deletions may only be attempted by providing the appropriate value
for the action of "D".

2 The Wizard
The Data Import Wizard is divided into 3 views:

Import Detail – allows selection of import files & log file location, as well as other complementary
settings

Column Definition – allows definition of the ordering of fields contained within the import file

Import Progress – providing information on the progress of the import

This document has been prepared specifically for Confidential Use. It remains the property of Cloudis Ltd and
Last Updated: 29/11/2010 17:26
be disclosed to any third party without prior consent.

Document
No: UM/05015
its contents
may not
Revision: 6

© Cloudis Ltd, 2010

Last Updated by: Tony Mahaffey
Page 2 of 20

Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. the log file will exclude successfully-loaded records. 2010 Page 3 of 20 . The initial step in the import process is to define the type of information to import. Pressing Next > validates the information provided and transfers control to the Column Definition view. Cables and Device may be combined in one record. Currently this is restricted to the following data sets (but may be extended to cover other types of data in a future revision): • • • • • • • Device Data Cable Data *or* Cable and Device Data1 Node Data Segment (Network) Data Library Data/Cable Types Library Data/Areas and Compartments Library Data/System Codes Import file This is the full directory/file path for the import file – currently the import file must be in CSV (Comma Separated Values) format Header records The first records in the import file may contain header information. and loaded collectively. If OFF. as well as its location and destination project.1 Import Detail Press the button to access the standard file selection dialog. if ON. Rather than have them produce errors. Apart from certain items of library data. loading of data to the ADMIN project is not permitted. 1 Subject to Project Default "Process Cables/Devices Simultaneously in Wizard". Only those records which the Wizard was unable to load will be shown. User Manual 2. only cables may be loaded.CMPIC Data Import Wizard. Type of data The data available to load. they can be ignored/skipped (up to a maximum of 100 records) Destination project The available destination projects are determined by the permissions provided to the current user. and a destination cabling project must be selected Log file This is the full directory path for the log file. which will be generated as the data is imported from the import file Ignore Successful? If active.

these are detailed in the Appendix. columns A through to J are visible. User Manual NB. E. size. Additionally. which alter the position of the currently selected field.g. These are useful when extra information is contained within the input file. regardless of the inclusion flag. respectively. 2. Subject to the type of data being loaded & project-specific settings. The position of data columns can be managed by means of the Move Up and Move Down buttons. it is possible to insert/delete socalled “filler” columns via the Insert Filler and Remove Filler buttons. Unless it relates to a mandatory value. Whilst the column definitions (name. 2010 Page 4 of 21 .1 Fillers In addition to the standard column definitions (which cannot be removed).2.2 Column Definition The Column Definition view allows for the structure of the input file to be defined. Filler columns are ignored during the import process. the inclusion flag can be activated/deactivated at any point. The inclusion flag only signifies that the data contained within the column should be loaded. type. certain columns will automatically be flagged for inclusion in the input. All modifications to column definitions are instantaneous. NB.CMPIC Data Import Wizard. When run initially. etc) are static. You should make use of the column id (the left-most field) to ensure the column definitions correlate directly to the placement of data in the input spreadsheet.2. Subsequent visits will automatically populate these values with those last used. it does not relate to the column's existence in the input file. As such. To make correlation between a spreadsheet and these definitions easier. 2. all selected columns can be grouped together via the Group Selected button. the input file must contain at least columns A-G. the columns are identified in the same alphabetic fashion as used in most popular spreadsheet programs. the fields shown are blank or set to the default value. but not necessarily relevant within CMPIC. In the screen-shot above.2 Option Sets Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. There is no requirement to “save” changes. although only A-D and F-G are to be used by the Wizard. certain columns may or may not be shown. although the contents of column E will be ignored (columns after the last included column will also be ignored). Initially. 2. the ordering and inclusion of these columns can be defined here.

whilst still providing a full report of any success/failure. which is then immediately available for modification. This will duplicate the contents of the “Standard Option Set” into a new Option Set. User Manual Option Sets are a means of storing multiple sets of column definitions for the same data type. To create a new Option Set. and press the Add Set button. The Preview option permits a “dryrun” of the import to be performed. enter an Option Set name in the field provided. 2010 Page 5 of 21 . Alternatively. NOTE: The Option Set used is retained between sessions. the Data Import Wizard does not retain these between projects. without any data in CMPIC being altered or impacted. Pressing Preview or Finish moves control to the Import Progress view. a subsequent load of device data will show that Option Set as pre-selected automatically. if you load device data with a specific Option Set. Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. Option Sets are project-specific. they are used in much the same way as report parameters within CMPIC report parameter forms. the “Standard Option Set” can be modified as required. NB.CMPIC Data Import Wizard.

Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. If this file already exists. The generated log file will be named data_import_{PROJECT}. User Manual 2. NOTE: Blank lines within the import file (if not ignored as part of the header definition) will be treated as malformed data and shown in the totals and log file as such. Once complete. and two options will now be available: • • Another? – Return to the Import Detail view. and stored in the log file location specified previously. A progress bar also provides a visible clue to the current state of the import.3 Import Progress At this point.CMPIC Data Import Wizard. it will be possible to view the log file for the import just run (ignoring any data from previous imports) via the Show Results button. the progress bar will have reached 100%. and b) Validated against any existing data in the destination project.log (where {PROJECT} relates to the destination project specified in the Import Detail view). a suitable entry is added to the log file and the relevant status counter updated. the data provided in the import file is read and each field is: a) Checked against the field definitions provided. to select another file for import End – Exit the Data Import Wizard In addition. For each record read & processed. any logging is appended to existing log data. 2010 Page 6 of 20 .

the same status counters are shown.3. Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. this option is now made available.CMPIC Data Import Wizard. 2010 Page 7 of 20 . as is the button to permit access to the import log file.1 Preview If the import had been run in preview mode. As the data has not actually been loaded. User Manual 2. as well as the option to begin the process again.

Y Co-ordinate Numeric No The Y-coordinate of the device. Values of "Y" or "N" only permitted. System Code Alphanumeric (6) Yes The system that the device forms a part of. Device ID Alphanumeric (20) Yes Unique Device identifier. usually only of relevance in CAD environments. Corporate No Alphanumeric (20) No Remarks Alphanumeric (60) No ECD Drawing Alphanumeric (30) No No. usually only of relevance in CAD environments.CMPIC Data Import Wizard. User Manual 3 Appendix 3. usually only of relevance in CAD environments. Module Alphanumeric (6) No [also referenced as Unit] Area/Compartment Alphanumeric (6) No The location of the device within the build. Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. if required. Group Alphanumeric (6) No The type of device. X Co-ordinate Free-text additional comments regarding this device. 2010 Page 8 of 20 . Z Co-ordinate Numeric No The Z-coordinate of the device. Column will not be available on single-vessel projects. Permissible values dependant on project reference data. Integer (7) No Location Alphanumeric (17) No Level Code Alphanumeric (6) No Location drawing Alphanumeric (30) No Hazardous Area Code Alphanumeric (6) No Special Features Alphanumeric (6) No Numeric No The X-coordinate of the device. of Terminals Pos. The Hazardous Area Code for the device. Description Alphanumeric (60) Yes Free-text description of the device. 2D Part ID Alphanumeric (30) No 3D Part ID Alphanumeric (30) No Event ID Alphanumeric (20) No Installation event this device should be linked to. The number of terminals (relevant terminal records are auto-created). Checkwire Reqd? Alphanumeric (1) No Installation marker to identify if a "checkwire" should be performed.1 Device Data – Column Specification Column Descriptor Data Format / Maximum Size Mandatory? Additional Information Device Applicability Alphanumeric (21) Yes The applicability for the device. represented in binary form.

User Manual Column Descriptor Data Format / Maximum Size Mandatory? Additional Information Insert/Update/Delete Alphanumeric (1) No Flag to indicate action required. Values of "I" (Insert). 2010 Page 9 of 20 . by default. Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd.CMPIC Data Import Wizard. "U" (Update). "D" (Delete) and "-" (Determine based on existence of data) only permitted. Near Node(s) Alphanumeric (500) No Near node definitions – see Appendix. Non-population of field will result in determination based on data.

Free-format Field 3 Alphanumeric (50) No Free-format field. Estimated Length Numeric Insert/Update/Delete Alphanumeric (1) No Flag to indicate action required. Cable ID Alphanumeric (40) Yes Unique Cable identifier. NSN/Pattern No. To Device Alignment Alphanumeric (1) No The alignment of the cable at the To Device. Permissible values are "L" (Local). "S" (Special) and "D" (Degaussing). "U" (Update). "M" (Main). Free-format Field 1 Alphanumeric (50) No Free-format field. Values of "I" (Insert). System Code Alphanumeric (6) Yes The system which the cable forms a part of. Non-population of field will result in determination based on data. Replaced by Bundle if Cable Bundling in Fill Calculations is active for the project Remarks/Comments Alphanumeric (1000) No Free-text additional comments regarding this cable. Module Alphanumeric (6) No Fit Code Alphanumeric (1) No Corporate Number Alphanumeric (25) No Alphanumeric (12) No Link Reference Installation Fit Code. Alphanumeric (20) No The Cable Type this cable uses Segregation Alphanumeric (6) No The Segregation/EMC Class of the cable. Permissible values dependant on project library data. Values of "C" (Clockwise) or "A" (Anti-Clockwise) only permitted. Only available when Free-format fields are active for the project.CMPIC Data Import Wizard. Only available when Free-format fields are active for the project. represented in binary form. Values of "C" (Clockwise) or "A" (Anti-Clockwise) only permitted. From Device Alignment Alphanumeric (1) No The alignment of the cable at the From Device. Only available when Free-format fields are active for the project. Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. Function Code Alphanumeric (6) No From Device ID Alphanumeric (20) Yes The device this cable runs from. Column will not be available on single-vessel projects.2 Cable Data – Column Specification Column Descriptor Data Format / Maximum Size Mandatory? Additional Information Cable Applicability Alphanumeric (21) Yes The applicability for the cable. Formation Code Alphanumeric (1) No The cable formation. Values of "F" (Flat) and "T" (Trefoil) only permitted. User Manual 3. by default. "D" (Delete) and "-" (Determine based on existence of data) only permitted. 2010 Page 10 of 20 . Free-format Field 2 Alphanumeric (50) No Free-format field. To Device ID Alphanumeric (20) Yes The device this cable runs to. Usage Code Alphanumeric (1) No The usage category.

5. Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. 6. 2.CMPIC Data Import Wizard. User Manual Column Descriptor Data Format / Maximum Size Mandatory? Additional Information Bundle Pos. 12. 2010 Page 11 of 20 . 3. Only available when Cable Bundling in Fill Calculations is active for the project (and if so will replace Formation field). Permissible values of 0. 4. Integer (2) No Bundle definition. 1.

represented in binary form. Cable ID Alphanumeric (40) Yes Unique Cable identifier. To Device Group Alphanumeric (6) No The To Device type. represented in binary form. Column will not be available on single-vessel projects. From Device Description Alphanumeric (60) Yes Free-text description of the From Device. From Device Area Alphanumeric (6) No The location of the From Device within the build. Values of "F" (Flat) and "T" (Trefoil) only permitted. Function Code Alphanumeric (6) No From Device ID Alphanumeric (20) Yes The device this cable runs from. Formation Code Alphanumeric (1) No The cable formation.CMPIC Data Import Wizard. Usage Code Alphanumeric (1) No The usage category. To Device Applicability Alphanumeric (21) Yes The applicability for the To Device. See Appendix for detailed formatting information. To Device Description Alphanumeric (60) Yes Free-text description of the To Device. NSN/Pattern No. From Device Near Node(s) Alphanumeric (500) No Near Node items for From Device. To Device Area Alphanumeric (6) No The location of the To Device within the build. Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. Column will not be available on single-vessel projects. From Device Applicability Alphanumeric (21) Yes The applicability for the From Device. Replaced by Bundle if Cable Bundling in Fill Calculations is active for the project Remarks/Comments Alphanumeric (1000) No Free-text additional comments regarding this cable. To Device System Alphanumeric (6) Yes The System which the To Device forms a part of. From Device System Alphanumeric (6) Yes The System which the From Device forms a part of. See Appendix for detailed formatting information.3 Cable and Device Data – Column Specification Column Descriptor Data Format / Maximum Size Mandatory? Additional Information Cable Applicability Alphanumeric (21) Yes The applicability for the cable. To Device Near Node(s) Alphanumeric (500) No Near Node items for To Device. represented in binary form. From Device Group Alphanumeric (6) No The From Device type. Alphanumeric (20) No The Cable Type this cable uses Segregation Alphanumeric (6) No The Segregation/EMC Class of the cable. 2010 Page 12 of 20 . Column will not be available on single-vessel projects. Permissible values dependant on project library data. To Device ID Alphanumeric (20) Yes The device this cable runs to. System Code Alphanumeric (6) Yes The System which the cable forms a part of. User Manual 3.

CMPIC Data Import Wizard. To Device Alignment Alphanumeric (1) No The alignment of the cable at the To Device. "S" (Special) and "D" (Degaussing). Permissible values of 0. Module Alphanumeric (6) No Fit Code Alphanumeric (1) No Corporate Number Alphanumeric (25) No Alphanumeric (12) No Link Reference Installation Fit Code. Estimated Length Numeric Insert/Update/Delete Alphanumeric (1) No Flag to indicate action required. 6. Only available when Free-format fields are active for the project. User Manual Column Descriptor Data Format / Maximum Size Mandatory? Additional Information From Device Alignment Alphanumeric (1) No The alignment of the cable at the From Device. 2. Values of "C" (Clockwise) or "A" (Anti-Clockwise) only permitted. 12. 4. "D" (Delete) and "-" (Determine based on existence of data) only permitted. 1. 3. Integer (2) No Bundle definition. Non-population of field will result in determination based on data. "U" (Update). 2010 Page 13 of 20 . Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. Only available when Cable Bundling in Fill Calculations is active for the project (and if so will replace Formation field). Formation/Bundle Pos. Values of "I" (Insert). Free-format Field 2 Alphanumeric (50) No Free-format field. Only available when Free-format fields are active for the project. "M" (Main). 5. Values of "C" (Clockwise) or "A" (Anti-Clockwise) only permitted. Only available when Free-format fields are active for the project. Permissible values are "L" (Local). by default. Free-format Field 3 Alphanumeric (50) No Free-format field. Free-format Field 1 Alphanumeric (50) No Free-format field.

Column will not be available on single-vessel projects. Comments Alphanumeric (60) No Free-text additional comments regarding this Node. usually only of relevance in CAD environments. User Manual 3. Values of "P" or "S" only permitted. X Co-ordinate Numeric (20) No The X-coordinate of the Node. usually only of relevance in CAD environments. Non-population of field will result in determination based on data. Values of "Y" or "N" only permitted. Values of "I" (Insert). by default. Only relevant when “Allow Principal/Secondary Nodes” is active for the project. Y Co-ordinate Numeric (20) No The Y-coordinate of the Node. "U" (Update). Principal/Secondary flag Alphanumeric (1) No Flag to indicate if Node is Principal or Secondary.CMPIC Data Import Wizard. represented in binary form. Node Location Alphanumeric (6) Yes The location of the Node within the build (also referred to as Area or Compartment). usually only of relevance in CAD environments. Insert/Update/Delete Alphanumeric (1) No Flag to indicate action required. Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. 2010 Page 14 of 20 .4 Node Data – Column Specification Column Descriptor Data Format / Maximum Size Mandatory? Additional Information Node ID Alphanumeric (12) Yes Unique Node identifier. "D" (Delete) and "-" (Determine based on existence of data) only permitted. Node Applicability Alphanumeric (21) Yes The applicability for the Node. Z Co-ordinate Numeric (20) No The Z-coordinate of the Node. Major Node? Alphanumeric (1) No Flag to indicate if Node should be identified as Major.

represented in binary form. penetration. used as the end point for the Segment. If not supplied. Values of "I" (Insert). used as the starting point for the Segment. Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. To Node Alphanumeric (12) Yes The identifier of an existing Node. Raceway ID Alphanumeric (20) No The Raceway ID of which this Segment is a part.g. Only available when "Allow Non-Standard Penetrations" is active for the project. representing the construction of the Segment. Insert/Update/Delete Alphanumeric (1) No Flag to indicate action required. e. Only available when "Raceways" is active for the project. Segment Type Alphanumeric (30) Yes A valid Segment Type. 2010 Page 15 of 20 . Non-population of field will result in determination based on data. used to determine %weight fill. Segment ID Alphanumeric (20) No The unique identifier of the Segment. A value of 0 (zero) is permissible where weight does not require calculation. User Manual 3. Segment Applicability Alphanumeric (21) Yes The applicability for the Segment. Commas must separate multiple values. by default. "U" (Update). a value will be auto-generated. Segment Length Numeric (20) Yes The length of the Segment. Column will not be available on single-vessel projects. "D" (Delete) and "-" (Determine based on existence of data) only permitted.5 Segment Data – Column Specification Column Descriptor Data Format / Maximum Size Mandatory? Additional Information From Node Alphanumeric (12) Yes The identifier of an existing Node. Span Numeric (20) No The distance between supports. tray. ladder rack. Useable Area Numeric (20) No The available area (overriding Segment Type dimensions) available for cables.CMPIC Data Import Wizard. Allowable Segregations Alphanumeric (200) No Allowable Segregations or Segregation Groups for this Segment.

Integer (5) Yes Core Insulating Material Alphanumeric (30) No Diameter over Ins. allowable values are Y (Yes) & N (No) Cable Usage Alphanumeric (1) Yes The usage category.6 Cable Type Data – Column Specification Column Descriptor Data Format / Maximum Size Mandatory? Additional Information MUN/NSN/Pattern Alphanumeric (20) Yes The unique identifier for this Cable Type Description Alphanumeric (60) Yes Free-text description of the Cable Type Conductor CSA Numeric Yes Conductor Stranding Alphanumeric (10) No Conductor Diameter Numeric Yes Number of Cores Pos.CMPIC Data Import Wizard. excluding screen information Weight of cable. used to determine % weight fill against containing network items Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. No of cores within the cable. Core Numeric No Diameter over Group Numeric No Cable Weight (in Kg/Km) Numeric Yes Diameter over Laid-up Cable Numeric No Cable Layering Alphanumeric (50) No Group Screen/Braid Alphanumeric (10) No Diameter of Group Scr/Br Wire Numeric No Overall Screen Alphanumeric (10) No Diameter of Overall Screen Wire Numeric No Diameter of Overall Screen Numeric No Overall Diameter Numeric Yes Resistance Numeric No Voltage Rating Alphanumeric (10) No Non-metallic content Numeric No Is Cable Armoured? Alphanumeric (1) No Flag to indicate armoured status of Cable Type. User Manual 3. Permissible values dependant on project library data. 2010 Page 16 of 20 .

Permissible values dependant on project library data. allowable values are C (Catalogued). Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. Integer (2) No Bundle definition. 3. P (Preferred) and S (Non-Standard) Formation/Bundle Pos. 12. Only available when Cable Bundling in Fill Calculations is active for the project (and if so will replace Formation field). N (Non-preferred). User Manual Column Descriptor Data Format / Maximum Size Mandatory? Additional Information Minimum Bending Radius Numeric No Type of Cable Alphanumeric (6) No The Cable Type category. 5. Permissible values of 0.CMPIC Data Import Wizard. Hot Code Alphanumeric (6) No The classification of heat resistance for the Cable Type. 4. Permissible values dependant on project reference data. Standard Classification Alphanumeric (1) No The classification for this equipment. 2. Cable Configuration Alphanumeric (6) No The configuration of the Cable Type cores & screens. Permissible values dependant on project library data. 1. 6. 2010 Page 17 of 20 .

Column will not be available on single-vessel projects. User Manual 3. providing this parent area is not the "base level" area.CMPIC Data Import Wizard. represented in binary form. to permit loading of hierarchical area structures. "U" (Update). by default. 2010 Page 18 of 20 . Values of "I" (Insert). Insert/Update/Delete Alphanumeric (1) No Flag to indicate action required. Hot Code Alphanumeric (6) No The Hot Code for the area/compartment. Only available when "Allow Area Hierarchy" is active for the project. Area Applicability Alphanumeric (21) Yes The applicability for the area/compartment. Area Description Alphanumeric (60) Yes A descriptive name for the area/compartment. "D" (Delete) and "-" (Determine based on existence of data) only permitted. if required. Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. Parent Area Alphanumeric (6) No Parent area. Permissible values dependant on project reference data. Non-population of field will result in determination based on data.7 Area / Compartment Data – Column Specification Column Descriptor Data Format / Maximum Size Mandatory? Additional Information Area Code Alphanumeric (6) Yes The unique identifier of the area/compartment.

Column will not be available on single-vessel projects. System Description Alphanumeric (80) Yes A descriptive name for the system. Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd. by default. Insert/Update/Delete Alphanumeric (1) No Flag to indicate action required.CMPIC Data Import Wizard.8 System Code Data – Column Specification Column Descriptor Data Format / Maximum Size Mandatory? Additional Information System Code Alphanumeric (6) Yes The unique identifier of the system. Non-population of field will result in determination based on data. "U" (Update). Values of "I" (Insert). Estimated Cables Pos. Integer (20) No Estimate of number of devices for this system. represented in binary form. 2010 Page 19 of 20 . Integer (20) No Estimate of number of cables for this system. User Manual 3. System Applicability Alphanumeric (21) Yes The applicability for the system. "D" (Delete) and "-" (Determine based on existence of data) only permitted. Estimated Devices Pos.

10)(NODE34. User Manual 3.0) or (NODE33.0. Nodes are constructed of the following components: Example Open bracket Node ID Off Route* On Route* Default?* Close bracket ( NODE33 0 0 N ) In the above example.0. this field should remain unused. Currently. such as (NODE33. regardless of whether the project setting prevents its use or not. If in doubt. the “On Route” value is an expected component. resulting in a possible chain of near node information such as (NODE33.N) Items marked * are optional.N) or (NODE33.Y). NB. or with a zero value. The Off Route and On Route length values default to a value of 0 (zero) and the Default Node value defaults to N (No). up to the limit of 500 characters. 2010 Page 20 of 20 .0. the node would be represented in the import file as (NODE33. Document No: UM/05015 Last Updated: 29/11/2010 17:26 Revision: 6 Last Updated by: Tony Mahaffey © Cloudis Ltd.0) or (NODE33).0..0.CMPIC Data Import Wizard.9 Near Node Definitions Node definitions must be passed to the Wizard in a specific format in order that the data is translated into suitable instructions for loading into CMPIC. Multiple near nodes may be concatenated within the same instruction.5. which allows for the same data to be represented in many possible ways.