NOK Configuration for the Linthal 2015 Project

Note:

1. The official project name is PSW Limmern (Linthal 2015 is a project above, which include PSW Limmern)

2. NOK is being renamed as Axpo

3. Axpo Informatic will host our server. They seem to be quite independent of NOK and the Linthal project

4. This page describes a configuration method for the Linthal project, which could become a model
   • for configuring other project too.

Terminology

1. Zust. = Approval (Zustimmung)
2. Indextyp = Document code type

Contact Names

Main address:

• Axpo AG - Hydroenergie, Parkstrasse 23, CH-5401 Baden
• +41-56-200-4483

Contacts:

• Name	Description	Email	Phone
  Martin Gmür	Main contact for system configuration	Martin.Gmuer@axpo.ch	+41-56-200-3872
  Norbet Wohlkinger	Commercial contact	Norbert.Wohlkinger@nok.ch	T: 056-933-4483, M: 079-630-3150
  Martin Hase	Leiter Baustelle	Martin.Hase@axpo.ch
  Emil Bieri	Electro-Mechanical Leiter	Emil.Bieri@axpo.ch
  Rene Käppeli	Axpo Informatik	Rene.Kaeppeli@axpo.ch	T:056-200-4538, M:079/609-6147

Discussions and Input Data from NOK

2009.10.16: AH/GMM/etc. Meeting in Baden to discuss classification system and workflows

1. Request for feature (for document/revision security): New flag in Drawings and/or Revision record:
   • Public to Bereich
   • Public to entire system

2. Request for feature: New workflow step F Freigabe, a final approval that is performed after all the

   • other Z (Zustimmung) approvals, and before the Submit workflow step. To be called Release in English.

3. New ApprovalStatus: Nicht efforderlich (e.g. N/A - Not Required). Rules:

   • Plan date: optional

   • Complete date: must be empty

   • Initials: optional

4. Summary of German language approval steps:
   • Offen
   • Erteilt
   • Erteilt mit Kommentar
   • Abgelehnt
5. Implement new workflows:

   • DCAAAAR - Design-Check-App1-App2-App3-App4-Release

   • DCAAAARS - Design-Check-App1-App2-App3-App4-Release-Submit

   • RCAAAAR - Receive-Check-App1-App2-App3-App4-Release

   • RCAAAARS - Receive-Check-App1-App2-App3-App4-Release-Submit

6. Request for improved event history to see exactly what was changed in workflows.

7. Idea for new Comment field for each Approval and Release workflow step

   • Did not commit to implementing this feature
   • NOK agreed to use tasks/comments for recording comments associated with approvals

New configuration files sent after the meeting from GMM:

1. 2009.10.19 DrawMGT PSW Limmern Struktur v01.xls -- Master configuration file for classifications

   • Worksheet Indextyp -- describe drawing code format and file names
   • Worksheet Attribute PSW Limmern -- list of all the classification and other reference data

2. 2009.10.19 DrawMGT Indextyp-Attribute v01.xlsx -- List of document code types and their components

3. 2009.10.19 DrawMGT Doktypen-Prozesstyp v01.xlsx -- List of (project) document types and their

   • corresponding document code types and workflow types. Note that we will implement the project document type as a classification field, and separate from the documentTypeId.

4. 2009.10.19 DrawMGT Prozesstypen Tabelle v01.xlsx -- List of desired workflows

Note that that attribute lists in the file 2009.10.19 DrawMGT PSW Limmern Struktur v01.xls generally have a set of code letters. E.g. Bereich has code aa. These same codes also appear in the document code definition and the names of the .txt and .sql files (see below).

2009.10.23: Emails from GMM for Training

1. Training schedule: mails: 10/23/09 8:42 AM and 10/23/09 11:37 AM

   1. Montag, 9. November 2009, 13:00 - 16:00, Axpo AG Baden, Teilnehmer: 6 Neue, E. Bieri, M. Gmür Rescheduled to Dri 13th (see below)

   2. Dienstag, 10. November 2009, 13:00 - 16:00, Axpo AG Baden, Teilnehmer: 5 Neue, M. Hase, M. Gmür
   3. Mittwoch, 11. November 2009, 13:00 - 16:00, Bauleitung Tierfehd (Linthal), Teilnehmer: 4 Neue, M. Hase, M. Gmür
   4. Freitag, 13.11.2009, 9-12 Uhr, Axpo AG Baden, Teilnehmer: 6 Neue, E. Bieri, M. Gmür

2009.10.23: Phone call AH/GMM

1. Official project name is PSW Limmern.

2. Change workflow step name E (Erhalten/Receive) to B (Bekommen).

3. The old (original) test system test is to be kept.

   • The new update of the data from the meeting or 2009.10.16 should go in the beta system.

4. OK to delay deployment of production system to the Axpo hosted server to the end of the year

Project to DrawMGT Configuration Mapping

This section describes how the mapping from the NOK spreadsheet 2009.10.19 DrawMGT PSW Limmern Struktur v01.xls and the DrawMGT database tables.

• Worksheet Name	NOK Description	DrawMGT Table	Notes
  Groups	Workgroups	Groups
  Ref-aaa	Bereich	ContractRef
  Ref-b	Projektphase	ProjectPhaseRef
  Ref-cc	Fachbereich	CategoryRef
  Ref-ddd	Objekt	LocationRef
  Ref-eee	Kontakt	SiteClassification2Ref
  Ref-ff	Dokumententyp	?	Keep separate from DocumentTypeRef
  Lage	Lage	AlignmentRef
  Taetigkeit	?	WorkTypeRef

NOK DOcument Coding System

Drawing and Revision Code Format

Note: NOK calls the drawing code Indextyp

Drawing Code

• Document Code

  -

  Revision Code

  File Extension

  aaa

  -

  b

  -

  cc

  -

  ddd

  -

  eee

  -

  ff

  _

  ####

  -

  XXX

  -

  v

  ##

  .yyy

Component Description

• Part	Description
  aaa	Bereich
  b	Projektphase
  cc	Fachbereich
  ddd	Objekt
  eee	Kontakt
  ff	Dokumenttyp
  ####	Laufnummer (drawingNo)
  XXX	Teilnummer, 1-3 alphanumeric characters, optional
  -
  v	Constant
  ##	Versionsnummer (revisionNo)
  .yyy	File name extension

Generated SQL Configuration Files

The NOK configuration information lives in the drawmgt-cfg configuration tree:

• cfg/linthal/site/data

Most of the configuration is generated from an Excel file:

• linthal-configuration.xls

The initial worksheet called Overview lists the mappings from the NOK attribute lists to their corresponding DrawMGT classification tables. Note that DrawMGT V11.3 has four extra classification tables SiteClassification1-4.

The generation is perform by saving each separate worksheet in the Excel file, in tab-separated format, into a file of the same in the data directory.

• E.g. Save the ContractRef worksheet as ContractRef.txt

• Save the other worksheets too

Then run a script to generate SQL files:

• generateRefData.sh

This script reads the .txt files and outputs .sql files

Then load the SQL into the database:

  mysql -u... -p...
    create database linthal113dev;
    use linthal113dev;

    source app/schema/drawmgt-schema.sql
    source app/schema/data/refdata.sql

    source cfg/linthal/site/data/linthal-configuration.sql

    quit

Run genMeta.pl