URL Monitoring is based on sending URL (Uniform Resource Locator) requests to the edinn server.

In the monitoring, we must select the source edinnHIP to use this method.

Possible URLs that can be sent are:

  • Production: this URL is to indicate that the process has produced results. To avoid communication overhead, it is recommended (not mandatory) that this URL is sent periodically (for example every 5 seconds), and not everytime a result is produced, so in this case the caller must be able to maintain the counter.

In case the caller maintains a counter and sends the absolute value, the syntax is as follows:

http://ecloud.edinn.com/edinnM2/monitor?Id_Company=0123456789&PType=0&Id_Proc=A001&Val=1000&Upd=20130821100000&Pass=password&Response_type=html

In case de caller just sends the increments, the syntax is as follows:

http://ecloud.edinn.com/edinnM2/monitor?Id_Company=0123456789&PType=0&Id_Proc=A001&Inc=1&Upd=20130821100000&Pass=password&Response_type=html

Where:

    • Id_Company: is the company identifier.
    • PType: fixed value 0.
    • Id_Proc: is the Id of the process as configured in the system.
    • Val or Inc: Val or Inc must be present, not both, but at least one.
      • Val: is the value of the counter of total results produced. This value must:
        • reset to 0 at 32.000. This is 31.999 -> 0. It must never reset under no other circumstance.
        • always increase. If it decreases, the system will interpret that a reset has occured and will assume that 32.000 results were produced.
        • not count empty results: this is the counter of the total results produced, so it must never count without a result being really generated by the process.
      • Inc: is the value that indicates how many results where obtained. This value must:
        • not count empty results: it must never count without a result being really generated by the process.
    • Upd (optional): is the date time when the result was generated in format YYYYMMDDhhmmss. This parameter is optional, if not provided, the system will assume the actual date and time.
    • Pass: password as indicated in the monitoring server console or in the monitoring step in the configuration wizard.
    • Response_type (optional): indicates in which format the response is needed. It can have the values xml and html. In case this parameter is not present, html will be asumed. In case it is html, and the response is ok, the explorer will close automatically.
  • Scrap: this URL is to indicate that the process has produced scrap results. This URL should not be sent every time a new scrap result is generated, as this could overload the communication with the system. It is recommended that this URL is sent periodically (for example every 5 seconds) so the caller must be able to accumulate the counter.

In case the caller maintains a counter and sends the absolute value, the syntax is as follows:

http://ecloud.edinn.com/edinnM2/monitor?Id_Company=0123456789&PType=1&Id_Proc=A001&Val=1000&Upd=20130821100000&Pass=password&Response_type=html

In case de caller just sends the increments, the syntax is as follows:

http://ecloud.edinn.com/edinnM2/monitor?Id_Company=0123456789&PType=1&Id_Proc=A001&Inc=1&Upd=20130821100000&Pass=password&Response_type=html

Where:

    • Id_Company: is the company identifier.
    • PType: fixed value 1.
    • Id_Proc: is the Id of the process as configured in the system.
    • Val or Inc: Val or Inc must be present, not both, but at least one.
      • Val: is the value of the counter of total results produced. This value must:
        • reset to 0 at 32.000. This is 31.999 -> 0. It must never reset under no other circumstance.
        • always increase. If it decreases, the system will interpret that a reset has occured and will assume that 32.000 results were produced.
        • not count empty results: this is the counter of the total results produced, so it must never count without a result being really generated by the process.
      • Inc: is the value that indicates how many results where obtained. This value must:
        • not count empty results: it must never count without a result being really generated by the process.
    • Upd (optional): is the date time when the result was generated in format YYYYMMDDhhmmss. This parameter is optional, if not provided, the system will assume the actual date and time.
    • Pass: password as indicated in the monitoring server console or in the monitoring step in the configuration wizard.
    • Response_type (optional): indicates in which format the response is needed. It can have the values xml and html. In case this parameter is not present, html will be asumed. In case it is html, and the response is ok, the explorer will close automatically.
  • Rework: this URL is to indicate that the process has produced reworked results. This URL should not be sent every time a new reworked result is generated, as this could overload the communication with the system. It is recommended that this URL is sent periodically (for example every 5 seconds) so the caller must be able to accumulate the counter.

In case the caller maintains a counter and sends the absolute value, the syntax is as follows:

http://ecloud.edinn.com/edinnM2/monitor?Id_Company=0123456789&PType=2&Id_Proc=A001&Val=1000&Upd=20130821100000&Pass=password&Response_type=html

In case de caller just sends the increments, the syntax is as follows:

http://ecloud.edinn.com/edinnM2/monitor?Id_Company=0123456789&PType=2&Id_Proc=A001&Inc=1&Upd=20130821100000&Pass=password&Response_type=html

Where:

    • Id_Company: is the company identifier.
    • PType: fixed value 2.
    • Id_Proc: is the Id of the process as configured in the system.
    • Val or Inc: Val or Inc must be present, not both, but at least one.
      • Val: is the value of the counter of total results produced. This value must:
        • reset to 0 at 32.000. This is 31.999 -> 0. It must never reset under no other circumstance.
        • always increase. If it decreases, the system will interpret that a reset has occured and will assume that 32.000 results were produced.
        • not count empty results: this is the counter of the total results produced, so it must never count without a result being really generated by the process.
      • Inc: is the value that indicates how many results where obtained. This value must:
        • not count empty results: so it must never count without a result being really generated by the process.
    • Upd (optional): is the date time when the result was generated in format YYYYMMDDhhmmss. This parameter is optional, if not provided, the system will assume the actual date and time.
    • Pass: password as indicated in the monitoring server console or in the monitoring step in the configuration wizard.
    • Response_type (optional): indicates in which format the response is needed. It can have the values xml and html. In case this parameter is not present, html will be asumed. In case it is html, and the response is ok, the explorer will close automatically.
  • Consumption: this URL is to indicate that the process has consumed. This URL should not be sent every time a new consumption is generated, as this could overload the communication with the system. It is recommended that this URL is sent periodically (for example every 5 seconds) so the caller must be able to maintain the counter.

In case the caller maintains a counter and sends the absolute value, the syntax is as follows:

http://ecloud.edinn.com/edinnM2/monitor?Id_Company=0123456789&PType=3&Id_Proc=A001&Id_Coty=ELEC&Val=1000&Upd=20130821100000&Pass=password&Response_type=html

In case de caller just sends the increments, the syntax is as follows:

http://ecloud.edinn.com/edinnM2/monitor?Id_Company=0123456789&PType=3&Id_Proc=A001&Id_Coty=ELEC&Inc=1&Upd=20130821100000&Pass=password&Response_type=html

Where:

    • Id_Company: is the company identifier.
    • PType: fixed value 3.
    • Id_Proc: is the Id of the process as configured in the system.
    • Id_Coty: is the consumption type (electricity, water, gas, etc.) Id as configured in the system.
    • Val: is the value of the counter of total consumption. This value must:
      • reset to 0 at 32.000. This is 31.999 -> 0. It must never reset under no other circumstance.
      • always increase. If it decreases, the system will interpret that a reset has occured and will assume that 32.000 units were consumed.
      • not count empty consumption: this is the counter of the total consumed, so it must never count without a consumption being really generated by the process.
    • Upd (optional): is the date time when the consumption was generated in format YYYYMMDDhhmmss. This parameter is optional, if not provided, the system will assume the actual date and time.
    • Pass: password as indicated in the monitoring server console or in the monitoring step in the configuration wizard.
    • Response_type (optional): indicates in which format the response is needed. It can have the values xml and html. In case this parameter is not present, html will be asumed. In case it is html, and the response is ok, the explorer will close automatically.
  • Generic: this URL is to indicate that a signal has changed. This URL must be sent every time the signal changes.

The syntax for this URLs is:

http://ecloud.edinn.com/edinnM2/monitor?Id_Company=0123456789&PType=4&Id=10&Val=99&Upd=20130821100000&Pass=password&Response_type=html

Where:

    • Id_Company: is the company identifier.
    • PType: fixed value 4.
    • Id: the id of the signal as configured in the system.
    • Val: is the value of the signal.
    • Upd (optional): is the date time when the signal changed in format YYYYMMDDhhmmss. This parameter is optional, if not provided, the system will assume the actual date and time.
    • Pass: password as indicated in the monitoring server console or in the monitoring step in the configuration wizard.
    • Response_type (optional): indicates in which format the response is needed. It can have the values xml and html. In case this parameter is not present, html will be asumed. In case it is html, and the response is ok, the explorer will close automatically.
  • Available product: this URL is to indicate that there is available product at the entrance of a process. This URL must be sent every time the signal changes.

The syntax for this URLs is:

http://ecloud.edinn.com/edinnM2/monitor?Id_Company=0123456789&PType=5&Id_Proc=A001&Val=1&Upd=20130821100000&Pass=password&Response_type=html

Where:

    • Id_Company: is the company identifier.
    • PType: fixed value 5.
    • Id_Proc: is the Id of the process as configured in the system.
    • Val: must be 0 when there is NO available product and 1 when there is available product.
    • Upd (optional): is the date time when the signal changed in format YYYYMMDDhhmmss. This parameter is optional, if not provided, the system will assume the actual date and time.
    • Pass: password as indicated in the monitoring server console or in the monitoring step in the configuration wizard.
    • Response_type (optional): indicates in which format the response is needed. It can have the values xml and html. In case this parameter is not present, html will be asumed. In case it is html, and the response is ok, the explorer will close automatically.
  • Saturation: this URL is to indicate that there is saturation of products at the exit of a process. This URL must be sent every time the signal changes.

The syntax for this URLs is:

http://ecloud.edinn.com/edinnM2/monitor?Id_Company=0123456789&PType=6&Id_Proc=A001&Val=1&Upd=20130821100000&Pass=password&Response_type=html

Where:

    • Id_Company: is the company identifier.
    • PType: fixed value 6.
    • Id_Proc: is the Id of the process as configured in the system.
    • Val: must be 0 when there is NO saturation and 1 when there is saturation.
    • Upd (optional): is the date time when the signal changed in format YYYYMMDDhhmmss. This parameter is optional, if not provided, the system will assume the actual date and time.
    • Pass: password as indicated in the monitoring server console or in the monitoring step in the configuration wizard.
    • Response_type (optional): indicates in which format the response is needed. It can have the values xml and html. In case this parameter is not present, html will be asumed. In case it is html, and the response is ok, the explorer will close automatically.
  • On/Off: this URL is to indicate that the process is working or stopped. This URL must be sent every time the signal changes. It is important to understand that the system does not need this signal to know that a process is working, so this signal is optional and is useful for those processes of very long Cycle Time which need an additional On/Off signal for more precision.

The syntax for this URLs is:

http://ecloud.edinn.com/edinnM2/monitor?Id_Company=0123456789&PType=10&Id_Proc=A001&Val=1&Upd=20130821100000&Pass=password&Response_type=html

Where:

    • Id_Company: is the company identifier.
    • PType: fixed value 10.
    • Id_Proc: is the Id of the process as configured in the system.
    • Val: must be 0 when the process is not working and 1 when there process is working.
    • Upd (optional): is the date time when the signal changed in format YYYYMMDDhhmmss. This parameter is optional, if not provided, the system will assume the actual date and time.
    • Pass: password as indicated in the monitoring server console or in the monitoring step in the configuration wizard.
    • Response_type (optional): indicates in which format the response is needed. It can have the values xml and html. In case this parameter is not present, html will be asumed. In case it is html, and the response is ok, the explorer will close automatically.