D – ATMS Data

Table of Contents

ATMS Data #

The flowchart in Figure 2 shows the steps to follow to enter data into ATMS in order to start running the application.

Follow the arrows backwards. For example, if you want to input your Machines into the system, you might first want to create your Cost Centres, define your Units (of Speed, Feed, Power, Torque and/or Pressure) and define your Machine Groups. And before adding your Machine Groups, you might want to define your Preset Adaptors.

The weight and shape of the lines in the graph define the characteristics of the data or the relationship (check bottom of figure).

Straight corner rectangles are References, where plain line indicates Recommended Reference and dotted line Optional Reference. Round corner rectangles indicate other data; a bold line indicates core data and a plain line further data.

Bold arrows indicate a mandatory relationship (e.g. you need to have at least one Point of Issue, before creating an ATMS User; and at least one Site, before creating a Point of Issue). Plain arrows indicate a recommended relationship (e.g. although it is not absolutely necessary, it is better to define your Points of Issue and your Families, before creating your Items and before going live). Dotted arrows indicate an optional relationship, (e.g. it is good to have your Cost Centres for reporting purposes, but it is something you can leave for a second stage in your implementation.

System Configuration will define, in a way, how the data you enter into ATMS will behave once you start running. It has been created to make the system more flexible. In the graph it is shown comprising all the system but it is not part of the flowchart because it can be defined at any time during the data entry process. Even though, it should necessarily be established before you go live.