Trace: » Life cycle of a machine

Life cycle of a machine

Objectives

  • Able to manage a machine from its delivery
  • Facilitate the entry of information on a new machine
  • Manage the networking of the machine
  • Treat the case of machines that are under repair
  • Be able to scrap a machine

Components used

To manage the complete life cycle of a machine, we use 4 elements:

  • The plugin injection CSV files (data_injection)
  • A native of GLPI functionality for connecting automatic machines
  • Uninstall the plugin machinery in GLPI
  • The plugin removeMachinesFromOCS removal machines in OCS

Plugin injection CSV files (data_injection)

The plugin has been designed to:

  • Retrieving data from another fleet manager (in the case of migration)
  • Inject data from suppliers in a supply of material

Data injection

Allows you to inject data into GLPI:

  • CSV
  • Injects inventory data:
    • Computer, monitor, printer
    • Network equipment, phone
    • Device
    • Cartridge, consumable
    • User group
    • Contract, and supplier contact
  • Injects data plugins (since version 1.2 for GLPI 0.71)

Type of injection

Injecting a “clean” file

  • Created and updated through the framework GLPI
  • Management history
  • Respect for the permissions for users

CSV file format input

  • No limit on the number of line (but pay attention to the memory allocated to PHP). It is therefore preferable to work with files of reasonable size.
  • Choice of field separator:, or tabs for example
  • Auto-sensing for ISO8859-1 and UTF8
  • Supports formats dates DD-MM-YYYY, MM-DD-YYYY, YYYY-MM-DD
  • Possibility of injecting CSV files without header

Models

Creating models of CSV files:

  • Data_injection allows replay CSV files
  • Containing the same number of fields
  • Contain the same header
  • A model allows you not to reenter the matching fields

Match Fields

Additional information

Can enter values common to all lines injected

  • At the time of import
  • For the person who will make the import

The definition of input data is made when creating the model.

Data can be:

  • Fields of an object (place, user, type, manufacturer, etc.)
  • Special status (eg available)
  • Financial information (date of purchase, warranty period, etc.)
  • Templates

Report injection

The plugin generates a report of the injection in the following formats:

  • HTML
  • PDF
  • All injections indicates successful or unsuccessful with error message

The plugin generates a CSV file with all the lines not injected.

Linking machines

GLPI 0.70 and higher includes a concept of linked machines

  • During the first upload of a machine from OCS
    • Verify that the machine has not been created by hand or injected into GLPI
    • Link machine automatically GLPI with OCS
    • Adds an event in the history
    • Automatically change its status (eg Production)

The link can only be performed by an automatic process

  • Cron integrated GLPI
  • Plugin import mass OCS

Configuring the connection in the way OCSNG GLPI

In the following screen capture: find the machine in GLPI

  • The same serial number
  • Whose status is “in stock”

Uninstall plugin

Uninstall Computer plugin allows you to remove a machine

  • Transfer the machine itself
  • Remove some more information
    • Name
    • Network, IP, domain
    • Software, software history
    • Budget
    • User contact
  • Change the status of the machine if necessary

Can treat the following cases

  • Reduced machine shop for repair
  • Machine made reform (disposal)

Choose a status that allows the connection when the machine is back. Plugin removal machines in the OCS

RemoveMachineFromOCS plugin that allows machines to remove the base OCS

  • Deletion OCS machines removed from GLPI
  • Script to remove the machines that were OCS
    • Removed from GLPI
    • Which have not risen since inventory xx months

Used to purge the OCS for use on large parks

Status

GLPI has a concept of status:

  • Indicates the status of a material at a T
  • The statutes are adaptable to suit your needs
  • Ability to search by status
  • Some changes to statutes are automatic
    • Import from OCS
    • Connection / disconnection device
    • Removing a machine

picture Sample status in GLPI

Management of machines in stock

All machines must be in the inventory:

  • Even those not on the network
  • Even if they remain in storage 6 months

The solution

  • Retrieve information on machines
    • Ask the supplier with a CSV file with information on delivery (serial numbers, MAC address, etc.)
    • Use a bar code reader to generate a file of serial numbers
  • Inject them with the plugin injection CSV files (data_injection)
  • In networking, the machine will be automatically linked

picture: Schema migration to OCS / GLPI

Machinery repair and Reformed

2 cases are quite similar:

  • Machine repair: should be removed temporarily counting licenses, OS, etc.
  • Machine Reformed finally came out of the inventory

The solution:

  • Use the plugin to “uninstall” of a machine
    • For compensation: when the machine will be repaired and reassigned, it will go back from SCO, and will be linked to the machine GLPI
    • Reformed: the machine never goes back to SCO in GLPI

Deletion of the final machine in OCS

The plugin allows to clean removeMachinesFromOCS the OCS by deleting:

  • The machines have already been removed from GLPI
  • The machines that are no longer linked to a machine OCS (uninstalled)

Conclusion

Historical example of the life cycle of a machine