Mon ami le TGV

test

2013-12-18T15:54:00.001+01:00

Whatsnew - AMUSE X30.doc Page 1 of 76

AMUSE – Release X.3.0

What’s new in this Release

INDEX

GENERAL...................................................................................................................................... 4

q New starting screens in AMUSE Menu System [Ph. 2] ......................................................... 4

q Unified forms for Libraries and Project Activities................................................................. 6

q Search tool in Listbox........................................................................................................ 8

q Windows 7 compatibility................................................................................................... 8

q Resizable Forms [Ph. 2]..................................................................................................... 9

q Job Opening Form........................................................................................................... 10

q Link to FW Ticket............................................................................................................ 10

ENGINEERING............................................................................................................................ 11

q Engineering Applications – NEW USER INTERFACE......................................................... 11

q Engineering Libraries - User’s Manual [Ph. 2].................................................................. 11

q ECA Description length increased to 80 char [Ph. 2]......................................................... 11

q ECA Version – New Table & Application .......................................................................... 12

q Project ECA List – Initialization by ECA versions.............................................................. 13

q Requisition Sets – New Table & Application..................................................................... 14

q Piping Classes – New Filter by Spec in DET and MACRO applications.............................. 15

q Piping Classes – Search tool in MIDCHAR Listbox........................................................... 16

q FW Unique Codes (table D001) – Filtering Options and Full Decoding............................... 17

q Client Codes (table D002) – New Filtering Options............................................................ 18

q Client Codes (table D002) – Full Decoding and Editing...................................................... 20

q Client Codes (table D002) – Export / Import through Excel file [Ph. 2]................................. 21

q W/S/V Library (table D292) – New Filtering Options............................................................ 25

q MTO – Enhanced Macro Explosion Process [Ph. 2]........................................................... 26

q Free Reporting – Export CSV files saved with ; as separator.............................................. 28

q Free Reporting – MR Comparison with PO & Received Qty................................................ 28

q Free Reporting – Number of output records automatically calculated.................................. 28

q URS 005a - Extended Coding capability for piping material................................................ 29

q URS 038 - Enhanced Bulk Requisitions Title...................................................................... 32

q URS 005b - Increase digits for SPEC field [Ph. 2].............................................................. 33

q URS 006 - Improved Management of Client Codes [Ph. 2].................................................. 33

q Automatic email at MR Summary building for missing Weights [Ph. 2]................................ 34

q Automatic email at MR Summary building for missing Client Codes [Ph. 2] ........................ 36

q Mail Monitor [Ph. 2] ......................................................................................................... 37

CAD INTERFACE.......................................................................................................................... 40

q URS 007 - AMUSE to SP3D interface [Ph. 2]..................................................................... 40

LIBRARY APPLICATIONS SCREEN [Ph. 2]........................................................................ 41

q (CAD020 - Geometric Standards) [Ph. 2]................................................ 41

(CAD030 - Library ‘owner’ DET codes) [Ph. 2]...................................... 42

AMUSE – Release X.3.0

q (CAD100 – MASTER Table) [Ph. 2].................... 43



(CAD120 – Size /Thk Cross Ref.) [Ph. 2] ...................................................................................... 44

q (CAD121 – Rating Cross Ref.) [Ph. 2]................ 45

(CAD121 – End Condition Cross Ref.) [Ph. 2].... 45

(CAD124 – Exceptions) [Ph. 2].......................... 46

(CAD200 – Allowed G/R Size) [Ph. 2]................. 47

(CAD370 – Selection Rules) [Ph. 2].............................................. 48

q (CAD390 – SQL Versions) [Ph. 2]............................................................ 48

(CAD400 – SQL Codes) [Ph. 2]................................................... 49

q PROJECT ACTIVITIES SCREEN [Ph. 2]............................................................................. 50

(CAD121_JOB – Project Ratings 00...99) [Ph. 2] .................... 51



(CAD122_JOB – Project End Conditions 00...99) [Ph. 2]......... 51

(CAD124_JOB – Project Exceptions 00...99) [Ph. 2]................ 51

(CAD370_JOB – Project SQL Selection Rules) [Ph. 2]................. 52

(CAD401 – Project SQL Code Version) [Ph. 2]............................ 52

(CAD110 – Export Specs to CAD) [Ph. 2] .................................. 53



q (CAD110_UC – UC Creation) [Ph. 2].......................................... 56

PROCUREMENT........................................................................................................................... 57

q Inquiry – Check on Due Date existence [Ph. 2].................................................................. 57

q Inquiry – Check on consistency between Issue date and Due date [Ph. 2]........................... 57

q Post Order - Enhanced display of Req. Item split by Units and quantities [Ph. 2]................. 58

q Post Order - Shipping Destination [Ph. 2].......................................................................... 64

q Reporting: “PO List” - Req. Alias [Ph. 2].......................................................................... 68

q Reporting: “PO Material Status” - Req. Alias [Ph. 2]......................................................... 68

q Reporting: “DELIVERY STATUS” - New fields [Ph. 2]...................................................... 69

q Reporting: “DELIVERY STATUS” - Printing Options [Ph. 2]............................................. 70

q Inquiry and PO data updated by eProcurement.................................................................. 71

CONSTRUCTION.......................................................................................................................... 72

q Enhanced ALLOCATION Process – minimum % of Allocation............................................. 72

q BOM Priority in Allocation Reports (URS 056).................................................................... 74

q BIN Field increase on Reports (URS 055)........................................................................... 74

Tickets......................................................................................................................................... 75

q Ticket No. 936451 - SQL Error when modifying sort fields on Delivery Status screen 75

q Ticket No. 214434 - Job Leading Zeros Dropped from Pricing Spreadsheet.. 75

q Ticket No. 429864 - G110 ECA type ? to B........................................................... 75

q Ticket No. 586441 - CSV Export of Table D561 ‘Exploded MTO (Cut File)’... 75

q Ticket No. 761676 - Copying Macros..................................................................... 75

q Ticket No. 714032 - Line List application does not close Excel........................ 75

q Ticket No. 587410 - Wrong size code in MTO import from PDS [Ph. 2]........... 75

q Ticket No. 323653 - Req. Index compared to previous Rev [Ph. 2]................... 75

q Ticket No. 767313 - Inconsistency between PO and MR data [Ph. 2].............. 75

q Ticket No. 557461 - Delivery Status Report [Ph. 2].............................................. 75

q Ticket No. 397479 - TAG REQ: calculation of tot. qty [Ph. 2]............................. 75

q Ticket No. 690472 - Change to Material Delivery Status [Ph. 2]....................... 75

q Ticket No. 153169 - Make Due Date a Mandatory Field in PUR120 [Ph. 2].... 75

q Ticket No. 388037 - TAG req. - Null TAG not allowed......................................... 75

Whatsnew - AMUSE X30.doc Page 2 of 76

Whatsnew - AMUSE X30.doc Page 3 of 76

AMUSE – Release X.3.0

J Ticket No. 154953 - TAG req. – Export MMS Data Table as .DOC file................................... 75

J Ticket No. 690472 - Change to Material Delivery Status [Ph. 2]........................................... 76

J Ticket No. 153169 - Make Due Date a Mandatory Field in PUR120 [Ph. 2]........................... 76

J Ticket No. 181710 - Requisition Alias print on reports [Ph. 2].............................................. 76

J Ticket No. 901810 - Split qty by plant unit in post order [Ph. 2]........................................... 76

J Ticket No. 353187 - Group material with same destination [Ph. 2]........................................ 76

J Ticket No. 989344 - Prevent save of TAG Req when out of user ECA competence [Ph. 2] ..... 76

Whatsnew - AMUSE X30.doc Page 4 of 76

AMUSE – Release X.3.0

GENERAL

Nouveaux écrans de départ en AMUSE System Menu [Ph. 2] 2]

AMUSE écran initial comprend maintenant la zone de connexion, sans écrans intermédiaires.

Il a également été révisé pour refléter la réorganisation de l'entreprise récente.

sélection de la section ca n être fait en cliquant sur le drapeau BU.

AMUSE – Release X.3.0

NB dernières sélections de connexion (Département, BU, Section et nom d'utilisateur) sont automatiquement préparés à l'ouverture de AMUSE, de sorte que le mot de passe est la seule entrée nécessaire (sauf si les informations de connexion doivent être modifiées).

L'écran principal après la connexion a été révisé: l'accès aux bibliothèques générales et activités du projet est maintenant grâce à des boutons uniques pour les modules entiers E / P / C.

Whatsnew - AMUSE X30.doc Page 5 of 76

Whatsnew - AMUSE X30.doc Page 6 of 76

AMUSE – Release X.3.0

 Formes unifiées pour les bibliothèques et les activités du projet

Ingénierie et d'approvisionnement et de construction des bibliothèques sont maintenant deux onglets de la même écran:

Whatsnew - AMUSE X30.doc Page 7 of 76

AMUSE – Release X.3.0

Aussi E / P / C Activités du projet sont maintenant disponibles en deux onglets de la même fenêtre, à la fois ciblée pour le projet sélectionné à la fenêtre supérieure.

Whatsnew - AMUSE X30.doc Page 8 of 76

AMUSE – Release X.3.0

 Search tool in Listbox

All applications adopting the standard AMUSE interface (typical for all Procurement and Construction applications and for all Engineering applications redesigned in this release) now provide a standard tool to search for a specific string inside any text columns in the look up table (numeric, date or long text columns are not searched).

If a sample string is input in the data field, at click on___________ (or Enter key) the table

is scanned starting from top and the first row containing that string in any text columns will be highlighted and scrolled into view.

Further clicks will search for the next matching rows, down to the table bottom.

Search will start again from table top with next click.

Editing of the sample string will restart search from table top.

 Windows 7 compatibility

Windows 7 graphic request for more space in title/menu bars was causing the appearance of unexpected scroll bars and, as a consequence, some objects were pushed out of initial form size.

Adjustment in the layout of most of the forms has become necessary.

Whatsnew - AMUSE X30.doc Page 9 of 76

AMUSE – Release X.3.0

 Resizable Forms [Ph. 2] Table Views are now resizable.

On monitors with resolution higher than 1024 x 768 it is possible to extend height and width of forms: this provides a wider view on table columns and rows.

Forms can be extended dragging borders (or even maximized double clicking on form’s title bar) but cannot be reduced below the initial size.

This functionality is available in all Procurement & Construction applications and in all Engineering applications re-designed to adopt the same standard interface (see dedicated bullet in ENGINEERING section later in this document)

See the sample screen shots on PO Header table:

Whatsnew - AMUSE X30.doc Page 10 of 76

AMUSE – Release X.3.0

 Job Opening Form

The User’s Manual Menu, accessible from all applications first screen, now includes the standard ‘Job Opening Form’ to be used to provide the administrator with the required info to properly initialize the general Job List (table NP01) and the Engineering Job Settings.

 Link to FW Ticket

System Libraries screen now provides a direct link to FW Ticket system.

Whatsnew - AMUSE X30.doc Page 11 of 76

AMUSE – Release X.3.0

ENGINEERING

 Engineering Applications – NEW USER INTERFACE

Almost all applications in Engineering Library and some applications in Engineering Project Activities have been re-designed to adopt the standard AMUSE interface already used by all application in Procurement & Construction modules.

Application interface re-design was also recommended due to the massive updates required by “URS 005a - Increase digits for MID” to Engineering Library applications.

This enhancement adds uniformity to AMUSE user interface across the entire system and improves engineering applications which can now take advantage of some typical functionality of the new interface, like:

· direct editing in table view. This ‘Excel like’ editing is more comfortable and provides a better visibility of edited rows.

· ability to insert, delete or modify rows in a single transaction

· modified application structure, where applicable, to better fit db structure and increase ease of data visibility and navigation (ex.: see MID Table / MID Char application, [X-D270]).

· new additional filtering objects to make querying data easier

· enhanced graphical presentation of data, in line with the rest of AMUSE application, to have an easier understanding of table content.

· Resizable forms

The only application not yet re-designed in Engineering Library is D440 – MACRO.

The applications already re-designed in Engineering Project Activities are:

G130 – Prj ECA Codes

D720 – Units / Areas

G250 – Sub Accounts

S950 – eMail Settings

D274 – Prj Numeric MID Characters

D512 – MTO Info List

 Engineering Libraries - User’s Manual [Ph. 2] User’s Manual has been completely revised.

 ECA Description length increased to 80 char [Ph. 2]

In order to allow a clearer description of Code of Accounts the length of field (XECA) has been extended from 40 to 80 characters. DB, screens and reports have been revised to accommodate this longer string.

Whatsnew - AMUSE X30.doc Page 12 of 76

AMUSE – Release X.3.0

 ECA Version – New Table & Application

A table has been added in Engineering Library (PCG100) to manage ECA versioning in AMUSE.

In Piping material library the basic Version – (matching GCCCA Rev.6) is related to ASME normative, but other alphabetical ECA Versions can be added to allow preparation of Piping libraries according to other Normative or even to manage all materials as itemized (TAG).

Example of possible Versions:

D = DIN

E = Euronorm

F = French normative

T = All Tagged materials (no bulk management for piping, all project materials itemized) This new table lists the available Versions, with description and remarks.

Since the use of these alphabetical Versions has to be limited to engineering module, they are not synchronized in Procurement ECA List and will not affect Vendor qualification in Vendor List.

An H (Hold) flag must be set in this table to all alphabetical Versions with the only exception of Version – (ASME): all Versions will be available when initializing Project ECA list in Engineering, while only not flagged Versions will be listed when initializing Project ECA list in Procurement.

Numeric ECA Versions (1, 2, 3, ...) must only be used for future possible revisions of FW GCCCA list whenever a specific ECA code meaning would change (N.B. changes in meaning for piping bulk ECA cannot be supported).

Whatsnew - AMUSE X30.doc Page 13 of 76

AMUSE – Release X.3.0

 Project ECA List – Initialization by ECA versions

When setting Project ECA codes (picking from ECA Library) a dialog box allows the selection of the Version to be used to initialize the project:

For each ECA code the selected Version, when available, will be used to initialize the Project ECA list (when not available Version – will be selected by default).

Of course any further adjustment of the selected version will be possible, for each single ECA code, directly editing the project table.

Whatsnew - AMUSE X30.doc Page 14 of 76

AMUSE – Release X.3.0

 Requisition Sets – New Table & Application

A new application is created to manage table ENG200 ‘Requisition Sets’, where Req. Sets are defined, with description and remarks.

Requisition Sets must be created in this table prior to use them in table D512 – MTO Info.

INSTALLATION NOTE

In already existing projects the Req. Set list will be automatically populated (at release installation) with the codes actually used in MTO info table: the Description of each Req Set can then be added, if deemed necessary, in table ENG200 (at least for on-going projects).

AMUSE – Release X.3.0

The new table ENG200 is used to look up Req Set code when preparing MTO Info List on project (app. [X-D512]): Req Set Description is also displayed for a better understanding of the Req Set assigned to the various MTO info codes.

 Piping Classes – New Filter by Spec in DET and MACRO applications

A preliminary filter on a specific Piping Class (selecting from a drop down list) can be optionally applied in the initial screen of these two applications so that all tables (Headers or Spec) are opened to show the selected Class only; this avoids, when working on a specific Class, the need to manually set up a By Example... filter at opening of each table.

Whatsnew - AMUSE X30.doc Page 15 of 76

At application opening this filter is set to ‘*ALL’ that means ‘no filter applied’.

Whatsnew - AMUSE X30.doc Page 16 of 76

AMUSE – Release X.3.0

 Piping Classes – Search tool in MIDCHAR Listbox

Looking ahead to the great number of codes that can be now defined in each MID table (see URS 005a) a special tool has been developed to facilitate MIDCHAR search when building MID composition: in the listbox for selection of MIDCHAR when typing a sample string in the dedicated search field the pick list content will be dynamically updated ‘asyou-type’ to show only the rows including such string in description, driving this way the user to the required MID characters, wherever they are located in the alphabetically ordered list of codes.

Whatsnew - AMUSE X30.doc Page 17 of 76

AMUSE – Release X.3.0

 FW Unique Codes (table D001) – Filtering Options and Full Decoding

The new redesigned application allow on-screen easy querying of table content to show

only FW Global or Project specific codes:

Full material decoding is always available just double-clicking a row:

AMUSE – Release X.3.0

 Client Codes (table D002) – New Filtering Options

In addition to the standard querying tools the new application allows on-screen easy querying of the table content, setting/combining pre-defined filters:

A) Only codes actually used in Piping Classes of a specific Job:

B) Only codes actually used in MTO of a specific Job:

AMUSE – Release X.3.0

D) Only FW Global or Project specific codes (in the example only ‘FW Global Codes’ of Client ‘HELPE’):

E) Only rows where Client Code is missing or where it already input:

Whatsnew - AMUSE X30.doc Page 19 of 76

AMUSE – Release X.3.0

 Client Codes (table D002) – Full Decoding and Editing Double-clicking a row will show full decoding of material.

Client Code can be input in both Table view and Full-decoding view

Editing allowed

Whatsnew - AMUSE X30.doc Page 20 of 76

AMUSE – Release X.3.0

 Client Codes (table D002) – Export / Import through Excel file [Ph. 2]

Rows from this table can be exported to an Excel: Client Codes can be input in the Excel file to be then uploaded back into this table.

Whatsnew - AMUSE X30.doc Page 21 of 76

Export Process

Export file is by default named Exported_ClientCodes.xls and it is stored into folder C:\AMUSE\ClientCodes (but the user can change both name and destination).

A sub-folder called \Inbox is also ready to store return files. Import process will search by default in this folder for XLS files.

At click on menu Item the export process starts and asks for export file name definition:

AMUSE – Release X.3.0

At the end of export process the following message is displayed:

And the just created Excel file is opened and it prompts for password input to protect the worksheet (protection is strongly recommended, it will prevent any modification of the Excel content except for the Client Code column, where input is expected).

Remember to Save file after protection.

Whatsnew - AMUSE X30.doc Page 22 of 76

AMUSE – Release X.3.0

Import Process

The return file compiled with Client Codes should be stored in \Inbox folder, and then a click on menu Item starts import process.

At the end the following screen shows the result of import:

Filtering objects are available to show where a code is input, where is missing, where it modifies the existing code (in case it was exported in the Excel file) and where it has been cleared (in case it was badly input previously).

AMUSE – Release X.3.0

Update can be selectively decided for New, Modified or Cleared codes.

The content of the table can be printed to get the following report:

Whatsnew - AMUSE X30.doc Page 24 of 76

AMUSE – Release X.3.0

The option buttons can easily filter the list to retrieve only rows with missing values.

The drop down list allows selecting the project requiring unitary weights input: only rows relevant to DET + Size actually used in MTO of the selected project are displayed.

Combining the two filters the list of rows to be updated is considerably reduced.

If Weight Library is regularly maintained the number of rows without weight to be updated should be quite limited.

 W/S/V Library (table D292) – New Filtering Options

Maintenance of Unitary Weights in table D292 is mandatory in order to have automatic weight calculation for piping material (several reports in Engineering and Construction show Piping material weight and also Allocation priority can be based on BOM weight).

Rows in table D292 are created during MTO explosion whenever a project requires a component that is still missing in the weight library: the relevant unitary weight can then be input in table D292.

Also Project Decoding tables (D591, D592 and D593) are updated during MTO Explosion, but unitary weights for new materials cannot be retrieved at this stage.

The lack of unitary weights input in table D593 becomes evident when Requisitions are built and table D593 is queried by relevant reporting: materials without unitary weight in table D593 will not show a valid weight in reports.

Rows in table D593 without a valid unit weight can be easily retrieved querying By Example... for NUNIT_W = 0:

At this point input in table D292 should be required, in order to then run Project weights refresh process and make all weights available for reporting.

The process that creates rows in table D292 starting from MTO input is quite complex: it classifies components based on their geometry, material weight class, size, thickness (converted into mm equivalent) and rating and/or facing when required (see Eng. Library User’s Manual – D290 - Weight / Surface / Volume Library for details).

For this reason it’s not easy to identify which rows in table D292 are strictly connected to the rows in project table D593: the list of rows that exactly match those without weight in D593 cannot be reached with a simple query on table D292.

Anyway in the new D290 W/S/V Library application two filtering tools are available: they can be used to restrict the number of rows in table D292 to be completed with unitary weight:

Whatsnew - AMUSE X30.doc Page 25 of 76

Whatsnew - AMUSE X30.doc Page 26 of 76

AMUSE – Release X.3.0

 MTO – Enhanced Macro Explosion Process [Ph. 2]

Explosion process has been enhanced in order to better manage Macros.

In this case Explosion Process returns an Error

If MACRO is Found then Explosion process uses it has defined in Bulk Spec Ref. (or Default Job = ‘*’ at last round)

YES

If MACRO is NOT Found then the Explosion process searches for that MACRO one last time inside Default Job = ‘*’

Is Search Job <> ‘*’

YES

Found ?

The Explosion process starts searching the MACRO composition inside MTO project itself (Project customized Macro).

MTO Project: 9BD0100A

YES

Found ?

MTO Project

If MACRO is NOT Found then the Explosion process searches again that MACRO inside the Bulk Spec Ref. Job (as defined in C410 - Job Settings).

If MACRO is Found then Explosion process uses it has defined in MTO Project

The following schema shows how the Explosion process now searches for MACRO composition (types Graphic Code and Macro Group):

Whatsnew - AMUSE X30.doc Page 27 of 76

AMUSE – Release X.3.0

The following schema shows how the Explosion process now searches for Coupling Set composition:


Example: Project: 9BD0100A		The Explosion process starts searching the Coupling Set composition inside MTO project itself (Project customized Coupling Set).

Whatsnew - AMUSE X30.doc Page 28 of 76

AMUSE – Release X.3.0

 Free Reporting – Export CSV files saved with ; as separator

All exported text files (CSV) are now exported having ; (semicolon) as field separator, in accordance with AMUSE standard for CSV export/import files.

 Free Reporting – MR Comparison with PO & Received Qty

Comparison report for new MRs has been enhanced to show also PO qty (reading from Actual PO) and MRS qty (received at site) for each Item.

Both complete and reduced (only MR qty changed) versions of this report are available. The new report also shows, where existing, Client material code.

In case MRS Received (GOOD) qty was greater than MR qty a red check mark is displayed beside MRS Qty

 Free Reporting – Number of output records automatically calculated

No more need to tick the check-box, record count is automatically performed at template selection:

AMUSE – Release X.3.0

 URS 005a - Extended Coding capability for piping material REQUIREMENT

“URS 005a - Increase digits for MID” asks to extend the number of codes allowed for each MID Table in Bulk Piping Library: some MID Table already ran out of coding possibility and for this reason the use of project specific coding (numeric MIDCHAR) has become too extensive.

MIDCHAR code has always been 1 character long, allowing up to 53 possible codes in each MID Table (26 Uppercase alphabetical + 26 Lowercase alphabetical + . (dot) = ‘not applicable’ system code).

IMPLEMENTED SOLUTION

MIDCHAR code is now increased to 2 characters (mandatory, single character not allowed): this extends coding possibility to 53 * 53 = 2809 different codes in each MID Table.

The introduction of such a basic update in Piping coding system (while keeping the validity of all existing data and a seamless continuity of operation) has been a big effort, requiring massive update in database structure, existing data, applications and reports.

1) The first assumption was to modify all existing MIDCHAR adding a . (dot) to the existing code (ex.: C becomes C.): this allows, when deemed useful, to insert up to 52 different new codes between one already existing code and the next one.

This approach allows insertion of the new codes in the most logical position inside the alphabetical listing.

USAGE NOTE

N.B. it is worth to remind that the new Search tool available for MIDCHAR selection when building Piping Classes (see dedicated bullet earlier in this document) helps finding anyway the required MIDCHAR quite easily wherever it is located in the pick list).


New codes

Whatsnew - AMUSE X30.doc Page 29 of 76

Whatsnew - AMUSE X30.doc Page 30 of 76

AMUSE – Release X.3.0

USAGE NOTE

In case the MID Table content was to be totally redefined utilizing the 2 characters coding, the existing codes (those automatically updated with the trailing . dot) cannot be deleted anyway, because this would invalidate all already created codes in the existing projects.

A possible solution is to set a ‘C’ (Cancelled) flag to the existing codes (so they will not be available anymore when building new Piping Classes) and add to the list the new ‘2 characters’ codes in the preferred order

2) Also project specific MIDCHAR (numeric) have been extended to 2 digits, and existing codes are automatically updated, adding a leading 0 (zero), at release installation.

This extends project coding capability to 100 possible codes in each Project MID Table (from code 00 to code 99)

3) As a consequence of MIDCHAR extension also MID1 and MID2 codes have been extended from 20/14 to 40/28 characters.

The same for FW Unique codes, increased from 9 to 10 characters.

INSTALLATION NOTE

All existing codes (MIDCHAR, MID, SIZETAB, SIZEK and UNIQUE CODES) will be automatically updated at release installation to keep consistency with the modified library codes).

A lot of applications, tables, batch processes and all related reporting are affected by this URS.

Libraries:

· MID Characters (D271)

· DET List (D230)

· MACRO Graphic codes (D441)

· Coupling Sets (D442)

· Size Library (D220)

· Schedule -> mm Conversion (D222)

· W/S/V Library (D292)

· FW Unique Codes (D001)

AMUSE – Release X.3.0

· Client Codes (D002)

· AMUSE -> CAD Cross Ref. (D120, D121, D122, D123)

· AMUSE -> CAD Exceptions (D124)

· CAD Allowed G/R Size (PDS100)

· Project Control Additional info (PCG400, PCG410, PCG420, PCG430)

Project Activities:

· Project MID Coding (D274)

· MTO Info Attribution Settings (D007)

· Piping Spec - DET (D301, D306, D311, D321)

· Piping Spec - MACRO (D401, D431)

· Piping Spec Release – Batch Process

· MTO (D505 – OOS components)

· MTO Explosion Process – Batch Process

· Decoding Maintenance (D591, D592, D593)

· Project Weights (D593)

· Bulk Summaries (D561, D570)

· Bulk Requisitions (D610)

· Requisition Building – Batch Process

· BOM Synchro (FLD571, FLD572)

· MRS Material Receipts (FLD080)

· TRS Material Transfer (FLD080)

· MIR Material Issue (FLD080)

· Allocation Process

Whatsnew - AMUSE X30.doc Page 31 of 76

Whatsnew - AMUSE X30.doc Page 32 of 76

AMUSE – Release X.3.0

 URS 038 - Enhanced Bulk Requisitions Title REQUIREMENT

“URS 038 – More detailed MR Description for Piping material” requires the possibility to enhance the Title of Material Requisitions for piping bulk material, since sometimes such title is too generic (it’s just the ECA code description) and do not allow an immediate identification of the real type of material in MR.

Ex.: 45° ELBOW and 90° ELBOW can share the same ECA code (1551H) and therefore the same MR title ‘C.S. REDUCING S.W. OR TH. FITTINGS’ not enough detailed to identify the type of component.

IMPLEMENTED SOLUTION

The agreed solution was to allow the user to define, for each ECA code, the technical information (MID Tech. Parameter) to be automatically decoded and added to MR Title by Requisition Building process.

In order to get this result a column has been added in General ECA List (table G110) in Engineering Library, to be filled picking one Parameter out of all those included in that ECA structure (table D272).

USAGE NOTE

The selected Parameter can be different from ECA to ECA.

Only one Parameter is allowed for each ECA.

Input of Parameter is not mandatory: it should be input only for ECA codes requiring a more detailed MR

Title.

INSTALLATION NOTE

The new column is empty just after AMUSE release installation: the proper Tech. Parameters to be decoded in MR Title must be set, in each BU, by the local Piping material managers.

During MR Building Process the Title of existing MR (those already released to Actual) will stay unchanged.

The new Title will be assigned only to new MR.

Ex.: for ECA 1551H, in case the selected Tech. Parameter was ‘DECODEFI’ then the MR Title would be different for 45° and 90° Elbows.

See this snapshot from MR table after MR Building:

Whatsnew - AMUSE X30.doc Page 33 of 76

AMUSE – Release X.3.0

 URS 005b - Increase digits for SPEC field [Ph. 2] REQUIREMENT

“URS 005b – Increase digits for SPECs” requires extending to 16 characters both SPEC code and Client Spec code.

IMPLEMENTED SOLUTION

Both fields have been extended in all Tables, screens and reports.

“Client Spec” code has been renamed as “Spec Alias” code for uniformity with the definition used for alternative code of Requisitions (“MR Alias” code).

The MTO import process from PDS has been changed to manage the longer Spec code, so the export files from PDS need to be modified accordingly. This update requires that MTO files submitted to import process are from now on in line with the extended SPEC code. Old type files cannot be imported since they generate errors during import.

 URS 006 - Improved Management of Client Codes [Ph. 2]

REQUIREMENT

Creation of Unique Codes and Client Codes at Piping Class creation stage.

IMPLEMENTED SOLUTION

See next point CAD INTERFACE - URS007.

AMUSE – Release X.3.0

 Automatic email at MR Summary building for missing Weights [Ph. 2]

When MR are created many reports are available that calculate and show the weight of each MR Item and of the entire MR. In order to allow this it is necessary that all materials

in MR can find the relevant Unitary Weight in

Whatsnew - AMUSE X30.doc Page 34 of 76

In order to have a timely maintenance of this library (table D292) a new automatic email can be optionally sent at MR summary building request (table TD570) to inform the owner of the library that some weights has to be input to satisfy the MR of the subject project.

Such mail is sent only in case at the end of Summary refresh any materials exist in table

D570 that cannot find a valid Unit Weight in (table D593).

Once the mail is received the owner of the Unit Weight library can utilize the new options available to filter the library table to view only the rows relevant to the MTO of the subject project where weight is Missing (see W/S/V Library dedicated bullet in this document).

In order to activate this mail a row must be added in project ___________________ (table

S950) for the task WEIGHT_SUMMARY, with recipients and input of optional mail texts:

Whatsnew - AMUSE X30.doc Page 35 of 76

AMUSE – Release X.3.0

When email is required but sending fails then a message appears as below:

Log file will show the reason for message: in case the reason of failure was the Summary Refresh process itself then the summary of errors in the batch process is recorded in the Log file, while in case the only problem was in sending the email then the Log file has only the following entry:

The details of the error can be read through Mail Monitor application (see also next bullet) so that corrective actions can be taken and the email can be re-sent without the need to run Summary Refresh again.

Whatsnew - AMUSE X30.doc Page 36 of 76

AMUSE – Release X.3.0

Here is a sample of the typical mail sent when missing weights are found:

 Automatic email at MR Summary building for missing Client Codes [Ph. 2]

Another automatic email can be optionally sent at MR summary building request (table TD570) to inform the owner of the library that some Client Codes has to be input to satisfy the MR of the subject project.

This applies only to Jobs where Client Code is requested (table C410_ Job settings).

Thsi mail is sent only in case at the end of Summary refresh any materials exist in table

D570 that cannot find the relevant Client Code in __________________ (table D002).

Once the mail is received the owner of the Client Code library can take advantage of the new options to show only the rows relevant to the MTO of the subject Job having Client Code still missing (see D002 dedicated bullet in this document).

In order to activate this mail a row must be added in project ___________________ (table

S950) for the task CLIENTCODE_MISSING, with recipients and input of optional mail texts:

This mail follows the same sending process and checks as for the mail for Missing Weights (see previous bullet).

 Mail Monitor [Ph. 2]

Currently automatic emails can be sent at Spec Release and Summary Refresh; possibly in the future other emails will be triggered by other events.

A new application ‘Mail Monitor’ has been developed in order to allow a better visibility and control of all emails sent by the AMUSE.

This application can be accessed from main screen menu of Bulk Spec Management

(D201) and Summaries (D570) applications:

AMUSE – Release X.3.0

Here is a sample of the typical mail sent when missing Client Codes exist (when more than 10 missing Codes exist they are not listed, just the total number of missing codes is shown)

Whatsnew - AMUSE X30.doc Page 37 of 76

Mails can be filtered by Status

by Task

or by Sender (User) name

Whatsnew - AMUSE X30.doc Page 38 of 76

AMUSE – Release X.3.0

The new application lists all emails sent (mails older than 30 days are automatically deleted) with dates and sending result:

Re-sending of failed mails can be forced in Mail Monitor (multple selection is allowed).

AMUSE – Release X.3.0

In case of bad addresses it is also possible to directly edit to/cc/bcc fields (only when is checked) to fix addresses before resending:

Whatsnew - AMUSE X30.doc Page 39 of 76

Whatsnew - AMUSE X30.doc Page 40 of 76

AMUSE – Release X.3.0

CAD INTERFACE

 URS 007 - AMUSE to SP3D interface [Ph. 2] REQUIREMENT

Scope of this URS is to define requirement to develop additional interface functionalities of Amuse to other CAD systems such as SP3D.

This URS requires deep modifications the export process of Piping Classes, introducing new functionalities like:

· creation of a set of new .CSV export files for ELENA (interface program to various CAD systems, including SP3D)

· keep active the option for creation of dedicated .TXT files for PDS

· split of Spec size ranges into single sizes

· management of different Geometry Standard practices in size split

· allow the use of ‘DET groups’ for a simpler definition of size split

· automatic generation of all missing Unique Codes before MTO execution

· management of a number of additional data into export files (weight code, material grade, etc.)

· modify the way some data are defined and managed during export process (Table Suffix, Option code, etc.)

· management of project MIDCHAR (00, ..., 99) across the entire process

· exceptions optionally applied based on 2 parameters match

· warning about multiple applicable exceptions

IMPLEMENTED SOLUTION

The export process has been completely re-designed to satisfy the above points and it required 11 new Library applications and 7 new Project applications to be developed, all of them adopting the standard user interface used by all application in Procurement & Construction modules.

As a byproduct of this development a new application project application has been created to allow anticipate the creation of FW Unique Codes (and Client Codes if requested by Project settings), for any selection of Classes out of all those released to Actual table D201, independently from MTO activity or export for CAD systems (URS006).

Whatsnew - AMUSE X30.doc Page 41 of 76

AMUSE – Release X.3.0

 LIBRARY APPLICATIONS SCREEN [Ph. 2]

The following screenshots show where the new applications are located in Engineering Library menu:

 ______________ (CAD020 - Geometric Standards) [Ph. 2]

This is the list of Practices for Geometry standards and the relative code ranges: it will be used by export process to select the proper Practice, based on Geometric code of

material, when querying table for Spec size range

explosion.

Whatsnew - AMUSE X30.doc Page 42 of 76

AMUSE – Release X.3.0

 _______________ (CAD030 - Library ‘owner’ DET codes) [Ph. 2]

This table allows defining the ‘owner' DET code to be used when querying three AMUSE=>CAD translation Libraries: Master Table (table CAD100), Exceptions (table CAD124) or G/R size (table CAD200).

In the example above two DET for flanges (FL1, FL2) make reference to FLG as ‘owner' of translation in all Master Table, Exceptions or G/R size: it will be enough preparing the rows relevant to FLG in these libraries to manage the translation of any of these DETs (they behave as a ‘Group of DETs’ in CAD Library).

Other DET (FLGFF, FLGRF, FLGSO, FLGSP) meke reference to FLG for Master Table and G/R size only, while they require their own rows in Exceptions.

USAGE NOTE

 reference must not be made to a DET that is not ‘owner' of that Library

 ‘owner' DET can be different, for the same DET, in each Library

 a DET can be ‘owner' in one library and make reference to another DET for another Library

This table is automatically synchronized with DET List (table D230) to show all type D DETs. At application opening a warning message is shown in case Engineering has modified anything in DET List, so that the synchro process can be run clicking on this button.

Whatsnew - AMUSE X30.doc Page 43 of 76

AMUSE – Release X.3.0

Filtering tools are available to simplify some querying about the use of all DET listed inside the library tables

 ___________________________ (CAD100 – MASTER Table) [Ph. 2]

This table provides rules and default values to be used for translation of materials from AMUSE coding to CAD coding.

Full screen single record view is also available.

AMUSE – Release X.3.0

This table is used to define, for all DET/ECA or MACRO/Graphic Code CAD code: Values at Green/Red points (End, Rating, Thk, Size range, Suffix), default values for various info, which technical parameters have to be decoded for short description creation, etc.

The only DET requiring input in this table are those defined ‘owner’ of Master Table in

table

 ___________________________ (CAD120 – Size /Thk Cross Ref.) [Ph. 2]

Here are prepared the conversion rules from AMUSE Library codes to CAD codes for Sizes and Thicknesses.

AMUSE – Release X.3.0

 ___________________________________ (CAD121 – Rating Cross Ref.) [Ph. 2]

Here are defined the conversion rules for Rating from AMUSE Library codes to CAD codes:

 ___________________________________ (CAD121 – End Condition Cross Ref.) [Ph. 2]

Here are defined the conversion rules for End Condition from AMUSE Library codes to CAD codes:

AMUSE – Release X.3.0

 (CAD124 – Exceptions) [Ph. 2]

In this table are listed all the exceptions to be used to update the various default values defined in Master Table (Suffix, Fabrication Categ., Model Code, Geometry Std, Modifier, Material Grade, Weight Code) and in Equiv. DETs (Option Code).

Based on the Library codes used in MID composition the relevant exception is prepared where necessary.

Up to 2 possible combinations of PARAMETER/MIDTAB/MIDCHAR can be used to determine the proper exception.

Whatsnew - AMUSE X30.doc Page 46 of 76

When retrieving applicable exceptions the export process will first search for a double match of PARAMETER/MIDTAB/MIDCHAR used in MID code: if match is found then exception is applied. Otherwise search will continue for a possible single match.

Decoding for the 2^nd set of three codes can be optionally shown/hidden (to save screen space):

Table content can be filtered by Exception Type

AMUSE – Release X.3.0

 (CAD200 – Allowed G/R Size) [Ph. 2]

All allowed Green and Red size pairs must be defined in this table, for each DET, according to the various Practice codes.

The content of this table will be used during export process when exploding Spec size range into all possible actual sizes of each component.

The only DET codes available for in this table are those defined ‘owner’ of G/R Sizes in

table

In case of DETs having one size only the 2^nd size must be filled with * (asterisk)

Whatsnew - AMUSE X30.doc Page 48 of 76

AMUSE – Release X.3.0

 (CAD370 – Selection Rules) [Ph. 2]

Here are defined the rules used to select the rows to be included in export .CSV files for ELENA.

Reference is made to the field names of the final export scratch table (CADB200).

Selection Criteria filed lists the value to be considered when exporting (ex.: rows concerning Bolted Components must have ‘Y.’ in field B200_F_BOLTED of table CADB200, etc.)

This table lists the versions of SQL code available during export of .CSV files for ELENA.

Different versions can be created in __________________ of the SQL code to be used to

build each export field content.

The version to be used in each Project must be defined in Project initialization (see Project Applications)

INSTALLATION NOTE

Version 0 will be initialized at installation.

AMUSE – Release X.3.0

 ______________________ (CAD400 – SQL Codes) [Ph. 2]

The final Select command used to create the export .CSV files for ELENA can be customized to get the required content in each field.

Version 0 is prepared at new version installation; other versions can be prepared later on, but a good knowledge of SQL language and of the structure of the final export scratch table CADB200 is mandatory.

Whatsnew - AMUSE X30.doc Page 49 of 76

AMUSE – Release X.3.0

 PROJECT ACTIVITIES SCREEN [Ph. 2]

The following screenshots show where the new applications are located in Engineering Project Activities menu.

Unique Codes creation

Project codes( 00...99) translation

Export CSV files for ELENA building rules

Export process of CSV files for PDS or ELENA

Whatsnew - AMUSE X30.doc Page 50 of 76

Whatsnew - AMUSE X30.doc Page 51 of 76

AMUSE – Release X.3.0

 (CAD121_JOB – Project Ratings 00...99) [Ph. 2]

This table allows translating project specific (numeric) rating codes.

The import process can be used to copy settings from other projects when applicable.

 _______________________ (CAD122_JOB – Project End Conditions 00...99) [Ph. 2]

Same as Project Rating.

 (CAD124_JOB – Project Exceptions 00...99) [Ph. 2]
Same as Project Rating.

Whatsnew - AMUSE X30.doc Page 52 of 76

AMUSE – Release X.3.0

 ______________________ (CAD370_JOB – Project SQL Selection Rules) [Ph. 2]

The rules used to select the rows to be included in export .CSV files for ELENA must be initialized: they can be copied from the Library table (CAD370) or imported from another project.

They can also be customized in each project (even if should rarely happen). Filling is mandatory if export for ELENA is required.

 ______________________ (CAD401 – Project SQL Code Version) [Ph. 2]

Here is defined the version of SQL code used to fill each field of the export .CSV files. Versions can be imported from General Library or form another projects. Filling is mandatory if export for ELENA is required.

Whatsnew - AMUSE X30.doc Page 53 of 76

AMUSE – Release X.3.0

 ______________________ (CAD110 – Export Specs to CAD) [Ph. 2]

This table lists all Piping Classes.

It is automatically synchronized with the Actual list of Piping Classes (table D201). Export process can be run from table menu bar:

Two different Export processes are executed according to export destination and different file types (.TXT for PDS, .CSV for ELENA) are created and stored in sub-folders of AMUSE\[Project]\ default export folder:

Together with the export Spec files also the PDF file of the errors is create.

Two columns show the timestamp of the last performed Export or UC Creation process for each Spec: since Export process also performs Creation of UC & Client codes, both timestamps are updated at the end of export.

AMUSE – Release X.3.0

Another type of process can be run from table menu bar, with the only purpose to create the missing Unique Codes (and Client Codes) only for all materials generated after explosion of Spec size ranges:

All UC / Client Codes are created during process but no export file is generated, except for ERRORS.pdf, stored in a dedicated folder:

Whatsnew - AMUSE X30.doc Page 54 of 76

Whatsnew - AMUSE X30.doc Page 55 of 76

AMUSE – Release X.3.0

These buttons allow easy querying of Spec List to show only the Specs which have been released after the last Export or the last UC Creation process.

These Specs may require a re-run of the relevant process to be sure that missing UC & Client Codes are created and CAD systems updated with the latest Spec content.

At Form opening this check is anyway performed and the relevant warning messages are displayed if necessary:

AMUSE – Release X.3.0

 ______________________ (CAD110_UC – UC Creation) [Ph. 2]

The UC creation process can be run also from this application.

This alternative way to run this process allows enabling Piping Spec owners (or anyone else deemed necessary) to perform, with just few clicks, UC creation whenever they want, through a free selection of Specs independently from any real activities of involvement of CAD users group.

Any editing in this application is prevented, whatever the user’s Access Level

Whatsnew - AMUSE X30.doc Page 56 of 76

Whatsnew - AMUSE X30.doc Page 57 of 76

AMUSE – Release X.3.0

PROCUREMENT

 Inquiry – Check on Due Date existence [Ph. 2]

Due Date is now a mandatory input in Inquiry Actual (table PUR120), while it is still not mandatory in Temporary (table PUR120_T).

In case Due Date was not defined:

At ‘Save Edits’ in Actual or at Release from Temporary the following messages are shown, the subject row is scrolled into view and Save / Release are prevented

 Inquiry – Check on consistency between Issue date and Due date [Ph. 2]

Also consistency between Issue date and Due date is now checked: Due Date must be later than (or equal to) Issue date. In case of inconsistent input the following message is shown and the Due date is automatically cleaned:

Now table EXP220 (Main PO Materials) shows the Plant Units relevant to each Item.

N.B. The same column listing Plant Units is available also in applications EXPEDITING Visits (EXP500), INSPECTION Visits (ISP500), IRN (EXP250) and SRN (EXP260) in screens where MR/Items are listed, and also in application ROS Date (PCG200)

Since Plant Units are read directly from actual tables of Engineering Requisitions (table D640 and D610) the latest released MR rev is found: it provides the most updated info about Units, regardless the MR rev that was actually purchased in each specific PO. Expediters can therefore address available quantities based on the most updated info to possibly optimize quantity in each delivery destination.

All Plant Units contributing to the final MR quantity are listed (comma separated) in a dedicated new column:

AMUSE – Release X.3.0

 Post Order - Enhanced display of Req. Item split by Units and quantities [Ph. 2]

Requisitions show the total qty required for each Item but do not specify which Plant Unit the Item belongs to (for TAG materials) nor the contribute of the various Plan Units to the total qty.

Knowing which Units are related to each Item and what is the contribute of each Unit to the total MR qty can be useful during post-order activity since Unit may affect delivery destination.

Whatsnew - AMUSE X30.doc Page 58 of 76

AMUSE – Release X.3.0

This new column can be queried ‘By Example’ to filter all Items having relation to a

specific Plant Unit:

The above ‘By Example...’ will return all rows having Unit 001 inside the list of all related Units:

USAGE NOTE

Due to the special technicality used to retrieve Unit codes from Engineering tables, multiple Units cannot be specified in ‘By Example’ querying: only one individual Unit code can be input.

Whatsnew - AMUSE X30.doc Page 59 of 76

Whatsnew - AMUSE X30.doc Page 60 of 76

AMUSE – Release X.3.0

A double-click on Plan Units cell opens the following dialog box, where the total current MR quantity of the Item is split to show the contribute of each Plant Unit (plus Overage and Surplus, if any).

The following screenshot is typical of an itemized (TAG) material:

This is the same form in case of Bulk materials:

AMUSE – Release X.3.0

The list content can be filtered to show only the rows containing a certain text string in ‘Unit’ or ‘Description’ fields:

The button_________ can be used to show the total quantity of any free selection of rows

in the list.

USAGE NOTE

This options can be useful to calculate the total quantity in each Material Destination (when it is the same for various Units) provided the destination is input in Unit ‘description’ field (table D720 – Plant Units in Engineering module) like in the following example:

Whatsnew - AMUSE X30.doc Page 61 of 76

AMUSE – Release X.3.0

USAGE NOTE

Quantities are read from Engineering tables (Actual) and are relevant to the latest MR rev released.

It is important to understand that the total quantity shown in this form are not necessarily related to the Item PO qty as it is shown in the specific row in table EXP220 Main PO Materials, for various possible reasons:

 MR quantity can be different from PO quantity (latest MR revs still to be purchased or purchased qty was partial/exceeding for some reason)

 MR quantity may have been purchased in different moments as MR revs were issued, thus in different PO revisions...

 ...or even with multiple POs to different suppliers

See the sample screenshots where Item 005 of Requisition 1541S/02 was purchased in three different PO revisions (Rev 1, 5 and 6 of PO = P IT028) for a total purchased qty = 576 m.

Whatsnew - AMUSE X30.doc Page 62 of 76

AMUSE – Release X.3.0

But still the latest MR qty is different (582 m) as it shows in the qty split Dialog box:

Missing qty could have been purchased in a different PO or not purchased at all.

Whatsnew - AMUSE X30.doc Page 63 of 76

Whatsnew - AMUSE X30.doc Page 64 of 76

AMUSE – Release X.3.0

 Post Order - Shipping Destination [Ph. 2]

During post order activity it may be useful to specify the delivery destination of materials in advance to final inspection and preparation for shipment.

Material Destination should be input for each material (table EXP220 – Main PO Materials): this could help building Inspection Release (IRN), Shipping Release (SRN) and Order for Shipment (OFS) for material with homogeneous destination. Material destination has to be visible during selection of materials to be included in each document.

USAGE NOTE

Material destination should not be input too much in advance to real shipment: this to reduce the risk that input destination is no more valid when real shipment occurs.

The existing field ‘Sub Lot Description’, available for each row of table EXP220, can be used to input Material Destination.

Input in this field is free and any text is accepted, but a double click on the cell shows the Listbox of available Delivery Addresses (read from table TRF100): this may help compiling this field with valid and homogeneous text for the materials having the same destination.

When a row is picked from the listbox the field is compiled chaining Delivery Address Code, City and Country:

Whatsnew - AMUSE X30.doc Page 65 of 76

AMUSE – Release X.3.0

Sub Lot Description (Material Destination) field is then made available when selecting materials for IRN, SRN or OFS:

This option can be used to make selection of materials having the same Shipment Destination easier (field name = ‘Description’ in column list):

AMUSE – Release X.3.0

Whatsnew - AMUSE X30.doc Page 66 of 76

AMUSE – Release X.3.0

Whatsnew - AMUSE X30.doc Page 67 of 76

 Reporting: “PO List” - Req. Alias [Ph. 2]

Req Alias code is now shown when printing PO List + MR version:

Whatsnew - AMUSE X30.doc Page 68 of 76

AMUSE – Release X.3.0

 Reporting: “PO Material Status” - Req. Alias [Ph. 2]

Req Alias code is now shown when printing PO Material Status

Whatsnew - AMUSE X30.doc Page 69 of 76

AMUSE – Release X.3.0

 Reporting: “DELIVERY STATUS” - New fields [Ph. 2]

Req. Alias code, Delivery Location (defined in PO), Sub Lot Description (material destination) and Item Remarks (coming from table EXP220) are now printed in DELIVERY STATUS report.

	Sub Lot Descr. (material destination)
Item Remarks	Sub Lot Descr. (material destination)	MR Alias

PO Delivery
location

AMUSE – Release X.3.0

 Reporting: “DELIVERY STATUS” - Printing Options [Ph. 2]

In DELIVERY STATUS final screen some options are available which allow getting shorter printout when deemed necessary.

Three check boxes can be un-ticked to suppress printing of Estimate Delivery date, PO Delivery Location, Sub Lot Description and Item remarks:

Example:

Whatsnew - AMUSE X30.doc Page 70 of 76

AMUSE – Release X.3.0

 Inquiry and PO data updated by eProcurement

Inquiry - Data Transfer from eProcurement to AMUSE

When eProcurement is used to Issue Inquiries and the following data is updated in eProcurement, this data will be transferred as below, to AMUSE Inquiry Actual (table PUR140) and Temporary (table PUR140_T) if the record is in both:

eProcurement Changes		AMUSE Changes/Updates
•	Decline on Supplier Side	Field: ‘Status’ – Updated with ‘Declined’
•	FW side update Decline via QR details	Field: ‘Status’ – Updated with ‘Declined’
•	FW side Decline via the Bid Status area	Field: ‘Status’ – Updated with ‘Declined’
•	Sealed QR-Received Bid (Un-Priced & Priced)	Field: ‘Status’ – Updated with ‘Received’ and
		Field: ‘Received’ - Updated with received date
•	Sealed QR-Received Bid (Un-Priced)	No Data Transfer (Requires Un-Priced and Priced)
•	Un-Sealed QR - Received BidField: ‘Status’	Field: ‘Status’ – Updated with ‘Received’ and
		Field: ‘Received’ Updated with received date
•	Yes – Not Electronic QR	No Data Transfer (Bids not received via eProcure)
•	Allow Bid Revision - Decline	Field: ‘Status’ – data Deleted
•	Allow Bid Revision - Received	Field: ‘Status’ – data Deleted and
		Field: ‘Received’ – data Deleted
•	Supplier Advise Will Quote	Field: ‘Promised’ – Updated with the due date
•	Supplier Requests Extension	Field: ‘Promised’ – Updated with the requested
		Extension Date
•	Extension Granted	Field: Extended Due –Updated with the Granted
		Extension Date

Purchase Order - Data Transfer from eProcurement to AMUSE

When eProcurement is used to Issue PO’s and a PO has been acknowledged in eProcurement (Supplier Side, FW side – Acknowledging individual and multiple POs), this date will be transferred to AMUSE Actual (table PUR590), field: PO Ackn.

Whatsnew - AMUSE X30.doc Page 71 of 76

Whatsnew - AMUSE X30.doc Page 72 of 76

AMUSE – Release X.3.0

CONSTRUCTION

 Enhanced ALLOCATION Process – minimum % of Allocation

When trying allocation it is now possible to set the minimum % acceptable, separately for Pipe and other components. In case the percentage was not reached no materials would be allocated on the BOM. This optimizes the use of materials.

At click on_____________ the following dialog form appears:

Click this button to accept any possible allocation (default setting)

To accept only 100% allocation of materials click on

..or input any user-defined value in the dedicated fields.

BOM(s) are then processed sequentially, according to the priority defined in BOM table of Allocation screen: in case the required % was not reached no material is allocated on that BOM and the process continues with the next BOM.

USAGE NOTE

When minimum % are actually defined different from 100% the Allocation process takes a longer time, due to the sequential processing and the intermediate checks performed for each BOM at allocation end.

Whatsnew - AMUSE X30.doc Page 73 of 76

AMUSE – Release X.3.0

Example:

Target is to find BOMs that can be Completely allocated.

1) Allocation run accepting any quantity...

...ends with partial allocation only, no BOMs can be allocated 100%

2) Allocation process run forcing Complete allocation...

...ends with 2 BOMs that can be allocated 100%

AMUSE – Release X.3.0

 BOM Priority in Allocation Reports (URS 056)

All allocation reports now show Priority code. BOM are printed exactly in the same order they have in allocation screen, thus by Priority (+ Alphabetical or BOM Weight or No. of Pieces as selected by the user).

 BIN Field increase on Reports (URS 055)

Reports have been revised to provide more space to BIN code (max length 8 char)

Whatsnew - AMUSE X30.doc Page 74 of 76

Whatsnew - AMUSE X30.doc Page 75 of 76

AMUSE – Release X.3.0

Tickets

u Ticket No. 936451 - SQL Error when modifying sort fields on Delivery Status screen Order by functions has been fixed.

u Ticket No. 214434 - Job Leading Zeros Dropped from Pricing Spreadsheet All XLS files have been modified to treat Job No as a text even when it looks like a number (instead as converting it to a number, as per Excel default formatting) Ex.: Job = 00123 will be considered text ‘00123’.

u Ticket No. 429864 - G110 ECA type ? to B

The new application ‘[X-G110] ECA General Library’ now allows changing undefined ECA types from ? to T or B as required.

u Ticket No. 586441 - CSV Export of Table D561 ‘Exploded MTO (Cut File)’

The new export has been modified to use semicolon (;) as field separator in accordance with AMUSE standard for CSV file creation. This will prevent misunderstanding of number symbols used as decimals/thousands separators.

u Ticket No. 761676 - Copying Macros

The problem has been identified and solved.

u Ticket No. 714032 - Line List application does not close Excel The problem has been identified and solved.

u Ticket No. 587410 - Wrong size code in MTO import from PDS [Ph. 2]

An additional check has been added to highlight when a size coming from PDS cannot be translated in table D120 (Matching Sizes). A question mark ? is written in table D507 (MTO Items) in case of failed size translation.

u Ticket No. 323653 - Req. Index compared to previous Rev [Ph. 2] The compare option was not working and causing a SQL error.

u Ticket No. 767313 - Inconsistency between PO and MR data [Ph. 2]

Item with Status = TBD in price PO Price List were wrongly dispatched to E/I Main PO Materials (Table EXP220). TBD is not a valid Status code to be considered as ‘purchased material’.

u Ticket No. 557461 - Delivery Status Report [Ph. 2]

Fixed error when comparing PO/IRN qty and MRS qty in case of Sublots.

u Ticket No. 397479 - TAG REQ: calculation of tot. qty [Ph. 2] Fixed error when calculating qty from multiple units.

u Ticket No. 690472 - Change to Material Delivery Status [Ph. 2] See dedicated bullet in PROCUREMENT chapter

u Ticket No. 153169 - Make Due Date a Mandatory Field in PUR120 [Ph. 2] See dedicated bullet in PROCUREMENT chapter

u Ticket No. 388037 - TAG req. - Null TAG not allowed Saving Item rows without a TAG name is no more allowed.

u Ticket No. 154953 - TAG req. – Export MMS Data Table as .DOC file

MMS data table can now be exported directly as .DOC file to be easily appended to MR and Issue Date can now be edited.

Whatsnew - AMUSE X30.doc Page 76 of 76

AMUSE – Release X.3.0

u Ticket No. 690472 - Change to Material Delivery Status [Ph. 2] See bullet in Procurement:

 Reporting: “DELIVERY STATUS” - New fields

u Ticket No. 153169 - Make Due Date a Mandatory Field in PUR120 [Ph. 2] See bullet in Procurement:

 Inquiry – Check on Due Date existence

 Inquiry – Check on consistency between Issue date and Due date

u Ticket No. 181710 - Requisition Alias print on reports [Ph. 2] See bullet in Procurement:

 Reporting: “PO List” - Req. Alias

 Reporting: “PO Material Status” - Req. Alias

u Ticket No. 901810 - Split qty by plant unit in post order [Ph. 2] See bullet in Procurement:

 Post Order - Enhanced display of Req. Item split by Units and quantities

u Ticket No. 353187 - Group material with same destination [Ph. 2] See bullet in Procurement:

 Post Order - Shipping Destination

u Ticket No. 989344 - Prevent save of TAG Req when out of user ECA competence

[Ph. 2]

Creation of REQ out of ECA Competence is prevented

Bonne Année

2012-01-04T12:52:00.000+01:00

Je vous souhaite à toutes et à tous une bonne et heureuse 2012, quel vous apporte santé, bonheur et tout le tralala habituel.

De son coté, la SNCF a décidé d'augmenté encore ses tarifs. Personnellement sur mon abonnement forfait mensuel je passe de 522,40€ à 529,90€... Ça ne représente que 7,50€ mais depuis 3 ans ça commence à faire beaucoup... J'en suis à ma 3ème année d'abonnement et donc au prix le plus bas....

Respect des horaires du mois de Décembre (à partir du 11 Décembre)

2012-01-01T12:20:00.002+01:00

Comme promis, nouveau horaire, nouveau suivi. Par défaut, je prends le train 2531 le matin (Nancy 6h17-Paris 7h46) et le le soir (Paris à 17h13-Nancy 18h43)

Lundi 12 Décembre : Train à l'heure matin et soir
Mardi 13 Décembre : Matin départ à l'heure, arrivée avec 4 min de retard à Paris (aucune explication) // Le soir affichage tardif du quai départ avec 5 min de retard arrivée à l'heure à Nancy.
Mercredi 14 Décembre : Train à l'heure matin et soir
Jeudi 15 Décembre : Train à l'heure matin et retard de 10 minute le soir sans explication.
Lundi 19 Décembre : Train en retard de 20 minutes le matin à l'arrivée à Paris cause neige.
Mardi 20 Décembre : Train à l'heure matin et soir
Mercredi 21 Décembre : Train à l'heure matin et soir
Jeudi 22 Décembre : Train à l'heure matin et soir

Vacances !!!!

Premières neiges

2011-12-19T11:10:00.000+01:00

Qui dit premières neiges, dit premier retard du au condition atmosphérique. Ce matin c'était légèrement risible. J'en ai même parlé sur mon compte twitter. A Nancy à 6h00 du matin, un centimètre maximum au sol, à Pont à Mousson à vu d’œil dans le train pas beaucoup plus.

Nous nous engageons sur la LGV sans problème et à vitesse maximale, puis au bout d'une demi heure le train ralentis subitement et rapidement, puis roule à une allure réduite. Bien entendu aucunes interventions des contrôleurs pour prévenir de quoique ce soit. Nous serons prévenu seulement 15 minutes avant l'arrivée du train que nous serons en retard du faites des conditions climatiques.

Bref, que par temps de neige, les trains et surtout les TGV ralentissent l'allure, je le conçois, mais si on commence à rouler à 170km/h avec un centimètre de neige, qu'est ce que cela va être quand nous en aurons 10 fois plus !!!!

Et je viens encore de rire en me renseignant sur infoligne : le retard est du à des conditions climatiques exceptionnelles...

Source photo : internet

Site SNCF dédié aux usagers du TGV Est

2011-12-16T08:02:00.005+01:00

En me balladant sur le site voyages-sncf.com, je me suis apercu qu'un espace dédié aux usagers de la ligne TGV Est était ouvert.

Séparé en deux parties principales, il permet une interraction entre le transporteur et nous.

Il suffit de s'y inscrire et le tour est joué.

C'est par ici que ça se passe : http://www.imaginetgv.com/tgvest

Les valises à roulettes

2011-12-15T11:32:00.000+01:00

On critique souvent la SNCF, mais pourquoi ne pas aussi parler de ses usagers ? Dans mon premier billet, je vous disais que je prenais le TGV entre Nancy et Paris depuis Aout 2009. J'en ai vu des choses. Aujourd'hui je vais vous parler de la satanée valise à roulettes, de toutes formes et de toutes tailles.

Source internet

Cet objet a pris une place de plus en plus importante sur les quais de la gare depuis quelques années. Même moi, j'ai succombé à cet objet. Le problème n'est pas tant l'objet qui est fort pratique je trouve, mais l'utilisation qu'en font les gens.
Beaucoup de personne se trouve supérieur avec cet objet et ne font plus attention aux autres. Combien de fois des gens m'ont roulé sur le pied en me doublant et me coupant la route ? Beaucoup ! Souvent même je me fais engueuler comme si c'était moi qui étais en tords... De plus les gens ne font pas attention à la place qu'ils prennent, tendent bien le bras et nous nous retrouvons vite avec un quai surchargé alors qu'il y a à peine 200 personnes qui se rendent à leur wagon. Dans les rames, certain pense qu'il faut absolument utiliser le système de roulette quitte à arracher les accoudoirs. Enfin certain pense qu'en prenant la moitié de leur appart ou maison dans leur valise, leur vie sera facilité... oui en parti mais dès qu'il y a des marches à monter, une valise à ranger, la valise certes à roulette mais paissant parfois son bon 30 kg est difficilement manœuvrable. On se retrouve alors souvent avec une valise énorme qui obstrue le passage.

Bref, tout cela pour dire que l’amélioration technique à ces avantages mais les gens se croient seul maitre du monde.

Un vieil article qui date d'avant l'arrivée de TGV Est

2011-12-14T13:25:00.000+01:00

Les nouveaux horaires

2011-12-10T13:26:00.000+01:00

A vrai dire, je m'en soucis peu. Mon train du matin partira à 6h17 au lieu de 6h15 et celui du soir à 17h13 au lieu de 17h12.

Je n'ai pas trop regardé nous plus les autres changement, mais en discutant avec plusieurs collègues de travail, je me suis aperçu que cela pouvait être assez handicapant : Trajet plus long, le train leur permettant de partir ce situe en periode blanche et non plus bleu, les correspondance qui ne sont plus ou mal assurées.

Je me dit que tout compte fait, j'ai bien de la chance.

D'ailleurs à partir de cette date du 11 décembre, je vais essayé de tenir un tableau des arrivées réelles de mon train et de faire un peu de statistique.

Suicide d'un syndicaliste à Vandières

2011-12-08T09:05:00.000+01:00

J'étais sur la route de retour d'Agen quand j'ai entendu que le trafic dans la région Est était fortement pertubé du à un accident de personne.

Vandières. Vers 6 h 30, hier, alors que le TGV Metz-Nice allait franchir le passage à niveau au cœur de Vandières, à la hauteur de la rue du Port en direction du stade, le conducteur a aperçu une forme humaine au milieu de la voie ferrée. L’agent SNCF a immédiatement enclenché l’alarme d’urgence déclenchant les freins. Lancé à quelque 120 kilomètres heure, le train n’a pu s’arrêter que 700 m plus loin, percutant et projetant la personne.
Arrivés très rapidement sur les lieux, les sapeurs-pompiers de Pont-à-Mousson, Vandières et Thiaucourt, les gendarmes dépendant de la compagnie de Toul, des agents de la SNCF ainsi que Claude Robert, maire de la commune, n’ont pu que constater le décès.
Aux premières constatations, effectuées sous le commandement du lieutenant Disse des pompiers mussipontains et du commandant Blaise de la gendarmerie touloise, tout indiquait qu’il n’y a eu aucun dysfonctionnement des barrières de sécurité, du feu clignotant ainsi que du signal sonore prévenant l’arrivée d’un train.
La victime a pu être assez rapidement identifiée. Il s’agit d’un salarié de la SNCF de 55 ans, délégué national du syndicat SUD Rail, domicilié à Vandières. La victime, dont le corps a été transporté à l’Institut médico-légal de Nancy, avait travaillé jusqu’en 2003 au service des essieux du technicentre de Montigny-lès-Metz, avant d’être détaché pour son syndicat, selon un responsable de Sud Rail, Daniel Tomaselli.

Le trafic a été en partie rétabli à 9 h45

« Toutes les conditions sont apparemment réunies pour que ça soit un suicide », a souligné hier le parquet de Nancy, tandis que la SNCF soulignait que le piéton s’était « jeté sous le train ». L’enquête a été confiée aux gendarmes de la brigade de Toul.
Le trafic ferroviaire, important sur cette artère, a été interrompu sur les deux voies trois heures durant, impliquant une forte perturbation entre la liaison Nancy et Metz. Douze TER ont dû être supprimés entre ces deux villes, lesquels ont été remplacés par douze bus. Alors que les trains à grande vitesse reliant Nancy à la capitale ont été détournés par l’ancienne voie. Les temps de retard sont estimés de cinquante minutes à deux heures au plus.
Le trafic pouvait reprendre « en marche à vue » dès 9 h 45, suite à l’accord des services de l’ordre.
V.S.

Accident de personnes à Bayon

2011-11-30T11:04:00.002+01:00

En raison d'un accident de personne vers Bayon, la circulation des trains a été interrompue sur la ligne Remiremont-Epinal-Nancy ce matin. Un service d'autocar de substitution a été mis en place. A 10h 30, la SNCF annonçait une reprise progressive de la circulation des trains dans ce secteur de Bayon. Mais les perturbations sont possibles jusqu'en début d'apres midi
C'est un homme de 41 ans, résidant dans le Bayonnais, qui se serait jeté sous le train qui circulait dans le sens Nancy- Epinal. Il était environ 6 h 30

Carte 12/30

2011-11-17T13:16:00.001+01:00

Racourssisement de la durée mais augmentation du nombre d'exemplaire mis en vente.

Perso toujours pas pris, car limite niveau finance.

source : http://www.voyages-sncf.com

Derniers jours !!! Les avantages de la carte 12-25 prolongés jusqu'à 30 ans

Lancée le 28 septembre dernier en édition limitée, la Carte 12-25 accessible jusqu'à 30 ans a connu un grand succès. La 400 000^ème carte a été vendue courant novembre.

Afin de permettre aux derniers clients de profiter de cette offre exceptionnelle, SNCF la remet en vente jusqu'au 30 novembre inclus.

Il vous suffit de sélectionner la Carte 12-25 et de remplir le formulaire associé. Une fois votre carte validée, sélectionnez la Carte 12-25 lors de vos achats et profitez de 25% à 60% de réduction sur tous vos voyages en train.

Le Départ des poilus, août 1914

2011-11-17T12:46:00.000+01:00

Hier, comme mon train partait de la voie 3, je suis passé par le Hall des départs et j'ai vu cette fresque :

Je n'y avais jamais porté attention. Je me suis donc renseigné en cherchant sur internet la signification, l'origine. J'ai voulu tout savoir.

Donc cette fresque s'appelle : Le Départ des poilus, août 1914.

Voici l'article present sur Wikipédia :

Albert Herter est connu en France pour être l'auteur d'une peinture monumentale de 60 m², Le Départ des poilus, août 1914, exposée depuis 1926 dans le hall des départs de la gare de Paris-Est à Paris. Cette toile illustre le départ pour le front des soldats français, les poilus, mobilisés en 1914. Elle fut peinte en souvenir de son fils, Everit Albert, tué près de Château-Thierry dans les derniers mois de la guerre et inaugurée en présence du Maréchal Joffre.
Lors de la rénovation de la gare pour l'accueil du TGV Est, la toile fut retirée en février 2006 sans que la SNCF ne fournisse d'informations sur sa future réinstallation. Un début de polémique naquit alors. Le sénateur de Moselle Jean Louis Masson posa une question au Sénat à la ministre de la Culture. En août 2007, dans une tribune du Figaro, Jean des Cars s'inquiétait du sort du tableau. Et c'est dans ce même journal, quelques jours plus tard, que le directeur général exécutif de la SNCF, Guillaume Pépy, indiqua que « ce tableau, à la fois historique et symbolique de la gare de l'Est, reviendra à sa place cet automne, après restauration complète ». Un article du Monde de septembre rapporte ces inquiétudes et résume le début de polémique.
Cette toile avait déjà été retirée en 1945 pour être nettoyée, les fumées des locomotives à vapeur l'ayant salie.

Problème de communication

2011-11-15T10:56:00.000+01:00

Ce matin, cela a du être la grosse panique à la Gare de l'est. Les tableaux déportés indiquant les voies de départ étaient en panne.

Il y avait certes des annonces sonores, mais ce n'est pas forcement très pratique. Je ne connais pas la fin de l'histoire car je suis partie prendre le métro.

Stand-by

2011-10-30T10:13:00.000+01:00

En plein déménagement, pas de mise à jour ces temps-ci.

Accident de voyageur à Vaires, suite

2011-10-24T12:36:00.002+02:00

Suicide sur la ligne TGV Est

Nancy.

Grosse pagaille hier soir sur le réseau ferroviaire Est à la suite d’un suicide survenu à hauteur de la gare SNCF de Vaire-Torcy en Seine-et-Marne, vers 17 h 30. Un homme d’une cinquantaine d’années s’est jeté sous un TGV circulant à 200 km/heure et son corps a été traîné sur 300 ou 400 m, « ce qui oblige à interrompre la circulation dans les deux sens », a indiqué une source policière.

Conséquence : si les lignes RER B et la ligne B du Transilien n’ont pas été impactées, en revanche tous les TGV en partance de la gare de l’Est sont restés à quai ou ont été retardés. Ainsi le TGV qui arrive normalement à 18 h 02 à Nancy s’est présenté à destination vers… 23 h. La liaison TGV vers Saint-Dié-des-Vosges a été annulée.

La SNCF a mis en place des itinéraires de substitution pour certains trajets, ou a affrété des autocars.

Orient Express

2011-10-20T09:28:00.000+02:00

Ce matin, j'arrive à la gare de l'Est et j'aime parfois regarder les tableaux d'affichage, surtout quand ils clignotent. Le clignotement indique le retard sur un train spécial marqué VSOE ??? Mais qu'est ce le VSOE ?

Arrivé dans le metro, je consulte mon téléphone, il s'agissait en faite de l'Orient Express. Je l'ai vu plusieurs fois en gare, mais je ne m'étais jamais posé la question de son appellation. C'est maintenant chose faite.

Si vous avez un bon porte-monnaie

Accident de voyageur à proximité de la LGV

2011-10-19T20:09:00.000+02:00

Alors que je somnolais dans le train du retour, quand le train s'est arreté en gare TGV Champagne Ardennes vers 17h45.

Attente, premiere annonce qui nous spécifie que nous sommes arreté (Ah bon !!!) puis une deuxieme pour nous dire qu'il y a eu un accident de personnes à l'entrée de la ligne TGV.

Puis on repart 10 minutes plus tard environ. Je pense qu'il voualis peut etre verifié si ce n'était pas notre train qui avait fauché la personne qui a voulu traverser les voies à Vaires. La personne a été fauchée en gare et cela a choqué pas mal de personne.

En zieuttant sur Twitter, tout les trains en direction de Paris sont arrêtés, et ceux aux départs de la Capitale de même. Selon infolignes, le trafic devrait reprendre vers 20h00 avec un possible passage par les anciennes voies (Epernay, Chalons en Champagne)

Bref, pour une fois j'ai de la chance et je ne suis pas bloqué. Mais bon, dans les gares il est marqué de ne pas traversé les voies sans y avoir été avisé.

Quartier Général : Grand Départ, les gares sous haute tension

2011-10-19T13:18:00.000+02:00

Diffusé Lundi soir en prime-time sur Direct 8, j'ai suivis ce reportage. Bien que je gueule souvent sur la SNCF, je m’intéresse fortement à eux.

Je connaissais pas mal de chose concernant le chef d'escale grâce à Ondine et son blog, mais j'ai découvert un métier très méconnu au sein de la SNCF : le chasseur !!

Pour suivre le reportage en entier, c'est par ici :

QG Grands Départs : Les gares sous haute tension

Comment occuper son temps suite à un retard

2011-10-13T18:49:00.000+02:00

A Nancy, on a trouvé la solution.
Une grève, un retard de train ! Rien de tel que de faire une machine ou de sécher son linge

Agression d'un controleur ... pagaie dans toute la France

2011-10-13T15:53:00.002+02:00

Jeudi Matin, un contrôleur de la SNCF s'est fait poignardé par un client. L'agression a eu lieu peut avant 11h00 du matin.

L'information s'est vite rependu sur les réseaux sociaux en particulier Twitter. Etant au courant, je décide donc de consulter le site infolignes géré par la SNCF. Et là, rien enfin pas grand chose. Je décide donc de faire comme si de rien n'était pour rentrer chez moi.

J'arrive donc à la gare peu avant 17h00. En temps normal, le quai est déjà affiché à mon arrivée. Là non, et je crains donc le pire sachant ce qui est arrivé le matin même sur la ligne Lyon-Strasbourg.

Jusqu'à 17h12 (heure de départ théorique de mon train), le TGV est annoncé à l'heure, puis quelques minutes plus tard, on annonce uniquement par les tableaux un retard probable de 10 puis 20 minutes. Toujours uniquement par tableau, à 17h30 mon train est noté SUPPRIME sans annonce vocale, sans solution à proposer. Je me dirige donc vers l'accueil, qui me dit de retarder mon départ.... Je veux bien mais je n'ai pas de pied à terre.

Bref, on n’est jamais mieux servi que par soi même. Sur le tableau d'affichage des arrivées/départ, un départ imminent pour Metz. Je décide donc de monter dedans car quelques minutes auparavant j'ai vu que le 18h12 en direction de Nancy était lui aussi annulé.

Départ un peu tardif du train histoire de récupéré quelques nancéens en perdition et direction Metz. Aucune annonce audible dans le train, pas vu un contrôleur. Bref, je descends à Metz sans savoir s'il y aurait un train, un car ou rien pour revenir sur Nancy. Par chance, un TER, certes omnibus était là. J'ai redécouvert la joie de faire plus de 10 arrêts en train pour arriver à bon port.

Je suis arrivée peu avant 21h00 à Nancy et je m'estime heureuse d'être arrivée que 2h00 plus tard que d'habitude. Dès que je suis rentrée chez moi, je me suis renseigné pour le lendemain et là encore rien, que dalle.

Je suis donc monté à la gare sans rien savoir, en me disant que s'il n'y a pas de train, cela m'aurait fait chier de me lever à 5h10 du matin pour rien. Et là : Miracle, un train, je cherche le contrôleur, parce que bon je vais pas monter à Paris si je ne peux pas revenir. Il me confirme un retour et me dit de consulté le site internet pour savoir ce sera lequel.

Je pars donc au boulot et j'ai beau chercher des informations toute au long de la journée, rien. Appli SNCF Direct bloqué, infoligne non mis à jour, le numéro vert surchargé. Je pars donc plus tôt du boulot pour espérer avoir un train et j'aurai donc le train de 16h12.

Bref, que les autres contrôleurs se mettent en grève soit, mais bon sang, une communication digne ne serait pas de trop.

Un train de retard

2011-10-13T08:34:00.000+02:00

Un site, complétement inutile mais tellement indispensable que j'ai découvert pendant mes mésaventures de la semaine dernière.

Et le petit lien : http://www.untrainderetard.com/

Accident à un passage à niveau

2011-10-13T05:25:00.000+02:00

Collision entre un camion et un train à un passage à niveau: deux morts

SAINT-MEDARD-SUR-ILLE (Ille-et-Vilaine) — Une collision entre un poids lourd et un train régional a fait mercredi deux morts, six blessés graves et 39 blessés légers à un passage à niveau près de Rennes, déjà marqué par un accident identique il y a quelques années, selon le dernier bilan des autorités.

Deux femmes de 43 et 55 ans sont décédées après un arrêt cardio-ventilatoire malgré les soins intensifs prodigués sur place, après l'accident survenu vers 17H30 au passage à niveau de Saint-Médard-sur-Ille, à une vingtaine de kilomètres au nord de Rennes.

"C'est une collision avec un camion qui transportait un engin de levage et qui est resté coincé sur la voie entre les barrières du passage à niveau", a expliqué Michel Cadot, le préfet de Bretagne.

Selon Jean-Claude Lebreton, un automobiliste qui se trouvait derrière le poids-lourd, "le camion est arrivé au feu rouge, les barrières n'étaient pas baissées... il a décidé de passer" alors que selon lui, "il aurait pu freiner". Lui-même s'est éloigné: "Je me suis dit, quand ça va cogner, ça faire des éclaboussures", a-t-il expliqué.

Selon un élu local ayant rencontré plusieurs victimes, une fois le camion engagé sur la voie, le chauffeur aurait tenté de faire marche arrière, puis une marche avant tandis que le train le percutait dans un choc violent.

"Le conducteur du train est sorti de sa cabine, il s'est jeté à terre", raconte Valérie, une passagère qui voyageait dans le wagon de tête. "On a tous été projetés, on a rien compris", a-t-elle raconté, enroulée dans une couverture de survie.

Emile, un sexagénaire qui se trouvait également à l'avant du train, s'est cramponné, a glissé sous le siège et s'en est tiré avec quelques contusions.

Témoin de la violence du choc, le tracteur du camion a été coupé de sa remorque, projetée à une vingtaine de mètres de là.

Le chauffeur du camion est indemne, a indiqué le président de la SNCF, Guillaume Pepy qui s'est rendu sur place dans la soirée.

"Le conducteur du train a eu les bons réflexes", a-t-il expliqué, en ajoutant que "le train était habilité à rouler à 140 kilomètres heure" mais que, lors du choc, il roulait "probablement à 110 kilomètres/heure". "Un train lancé à 140 kilomètres heure a besoin de 500 mètres pour s'arrêter", a précisé Guillaume Pepy.

Le ministre des Transports, Thierry Mariani, qui s'est également rendu sur les lieux, a affirmé que le passage à niveau de Saint-Médard "n'était pas classé comme préoccupant".

Le syndicat national professionnel des conducteurs de trains (FGAAC-CFDT) a pour sa part demandé, dans un communiqué, "l'accélération d'investissements nécessaires pour sécuriser les passages à niveau, soit au travers de sa suppression en créant un pont ou un souterrain, soit en améliorant ses abords".

Plus de 200 personnes ont été mobilisés pour secourir les 170 passagers du train express régional Rennes-Montreuil-sur-Ille.

Les blessés, d'abord soignés dans une salle municipale, ont été évacués vers les hôpitaux de Rennes, Fougères et Saint-Malo. Une cellule de crise a été activée à la préfecture qui a déclenché le plan rouge.

En novembre 2007, un poids-lourd avait percuté un train régional au même passage à niveau, faisant une quarantaine de blessés.

Suite à cet accident, des feux avaient été rajoutés devant les barrières pour en améliorer la visibilité, a indiqué une porte-parole du gestionnaire du réseau ferré RFF.

La circulation ferroviaire entre Rennes et Saint-Malo a été interrompue dans les deux sens et le trafic local sera interrompu jeudi, a indiqué la SNCF.

Dès le matin !!!

2011-10-11T16:50:00.000+02:00

Hier comme aujourd'hui le train n'était pas à quai à mon arrivée à la gare de Nancy.

Un petit aperçu du tableau d'affichage à 6h15..... Quand ça commence comme cela une journée, qui sait comment elle va terminer.

Un controleur agresser par un passager ! Le bordel !

2011-10-08T05:02:00.000+02:00

Actualisé à 10 h 10 - Le trafic était très perturbé vendredi sur le réseau SNCF avec 1 TER sur 4 et 1 TGV sur 3, à la suite de l'agression à coups de couteaux d'un contrôleur qui, selon le président de la SNCF Guillaume Pepy, était toujours dans un état grave, mais stabilisé.
"Il est dans un état grave, mais stabilisé", a déclaré sur RTL le patron des cheminots qui, tout en faisant part d'une "émotion très grande" à la SNCF, a néanmoins appelé les agents "à ne pas pénaliser davantage les usagers parce que quelqu'un de déséquilibré a commis un acte fou qui est rarissime".
De très nombreux agents ont fait valoir le droit de retrait à la suite de la violente agression commise jeudi dans un train circulant entre Lyon et Strasbourg.
Guillaume Pepy a indiqué qu'il recevrait les syndicats dans la matinée et des des assemblées générales de cheminots sont également prévues.
Gilbert Garrel, secrétaire général de la CGT-cheminots, a déclaré vendredi matin sur France Info: "la position de la CGT est claire: ne pas instrumentaliser un événement tragique et nous associer à la douleur du collègue agressé".
"Mais il faut aujourd'hui que les directions dans les établissements, dans les régions, rencontrent les organisations syndicales, discutent des conditions de travail, discutent de l'équipement des trains, discutent de la déshumanisation des gares et des trains que nous déplorons", a poursuivi le responsable du premier syndicat de cheminots.
Vendredi matin, le trafic était fortement perturbé sur une grande partie du réseau, mais les réseaux Transilien (Ile-de-France), Eurostar et Thalys semblaient épargnés.
La SNCF annonce un TER sur quatre et 1 TGV sur 3 mais avec "de fortes disparités selon les régions et les axes".
"Les perturbations sont plutôt concentrées sur le sud-est et le nord et plutôt moins sur l'Atlantique", a précisé Guillaume Pepy.
"Les évolutions de trafic seront précisées en fonction des reprises de travail constatées dans la matinée", indique l'entreprise qui invite les voyageurs à emprunter un autre moyen de transport dans la mesure du possible ou à reporter leur voyage.
Un numéro vert gratuit a été mis à la disposition du public (0 805 90 36 35).
Pour les voyageurs qui reporteraient leur voyage, tous les billets pourront être remboursés.
Les billets seront "remboursables ou échangeables sans aucun frais, quel que soit le type", a assuré M. Pepy.
"Nos clients comprendront ce qui s'est produit depuis hier (jeudi) et les perturbations qu'ont subi les trains si les contrôleurs savent se remettre rapidement au service des clients", a-t-il avancé.
Assurant que la "sécurité des agents et des voyageurs" était "la priorité absolue de la SNCF", M. Pepy a enfin rappelé que l'agression du contrôleur était un "acte fou" et "rarissime" qui "aurait pu se produire partout ailleurs".
"Quand un contrôleur de la SNCF est agressé avec une violence inouïe, c'est tout la SNCF qui se sent agressée", a-t-il fait valoir.
Le contrôleur, basé à Strasbourg, a été blessé de plusieurs coups de couteaux et opéré à l'hôpital de Besançon.
Secrétaire régional du syndicat CGT en Paca, Laurent Delours a déclaré à l'AFP: "Le but n'est pas de s'installer dans ce droit de retrait. On peut supposer que nous serons en capacité de nous remettre au travail, même si l'émotion est grandissante et qu'il faut vraiment régler les problèmes de sécurité à bord des trains".

le 07/10/2011 à 06:45 par Stéphanie LEROUGE / AFP

Les 30 ans du TGV

2011-09-26T10:00:00.000+02:00

Samedi soir avait lieu les festivités des 30 ans du TGV en France et la présentation du la nouvelle couleur du TGV Rhin-Rhone, qui sera par la suite aussi mis sur les trains intercité et trancielliens.

Voici la nouvelle mouture. Hâte de le voir sillonner la ligne TGV-Est.

source image : www.megamark.fr