DS-1xxx IMOS Setup for Automated Insertion Management System (AIMS)

Transcription

1 DS-1xxx IMOS Setup for Automated Insertion Management System (AIMS) Issue: 5 Date: 15 th October 2012 Page 1 of 37

2 Table of Contents 1.0 Introduction AIMS versions and Modes Rules for using Different AIMS Modes IMOS Setup Network Devices Setup in Engineer Screen Inserter Definition Setup AIMS Job Programing Job number control Modes Auto generated Manual entry Manual entry (no external checking) Read from Prime AIMS Control Modes Statistics Audit Verification LookUp Data logging Mode AIMS Compatible Statistics Mode OFFLINE PROCESSING Duplicates Job Number Piece ID Character Restrictions Summary for AIMS Security Check settings Data logging Logging to AIMS Datalogging From multiple Units Data-logging and AIMS Logging Final Destination in the Vertical Stacker (VS) Reporting Which Feeder Fed to AIMS Mapping a feeder because it is broken Mapping a feeder as it cannot feed the requested insert Mapping a feeder so it matches the data in a JAF Demanding multiple feeders from a single demand Mapping the prime feed unit to match a JAF Custom Codes Other Custom Codes Validation of Settings When Defining an AIMS Job If No piece id defined No job number defined No job number or piece id defined No label / reading is OFF for main datalogging unit No Label defined Run Screen when AIMS is Installed Starting a Job Job with Auto-generated Job number Job with Manual Entry Job Number AIMS Specific Fault Codes No Read on the First Document processed Autoending Scenarios When Running with AIMS Abandoning a Job that is Running with AIMS Re-setting the AIMS connection Appendix: Error Codes and Actions Page 2 of 37

3 1.0 Introduction NTL inserters (DS-1xxx) can be linked to the Automated Insertion Management System (AIMS) to allow a close loop solution. AIMS provides the following: Dynamic Dashboard of Inserter activity Statistical Analysis Reports for Jobs, Applications or Operators Real-Time Data-Logs of Mail Pieces processed Closed Loop functionality, when combined with Neopost OMS packages Integration facilities to link to third party Management Information Systems (MIS), including full solutions, Automated Document Factory (ADF) etc. This document explains the setup of IMOS to work with AIMS. All settings required as well as a brief explanation of the different modes will be explained 1.1 AIMS versions and Modes The table below shows the 3 versions of AIMS and their associated modes of operation. AIMS Versions Aims Modes Statistics Document data generated for MailRoom Management only Audit Trail created from data read on each document, file created on-the-fly Yes Yes Yes Yes Yes Yes Verification Closed Loop Each MailPiece checked against a file LookUp Closed Loop Each MailPiece checked, plus Control information held in file Yes Future Yes Yes Page 3 of 37

4 1.2 Rules for using Different AIMS Modes The following section outlines which modes and which settings are compatible when using AIMS modes on the Ds-1000 / Ds-1200 inserters I. When using AIMS statistics mode no piece id should be defined in the label II. III. IV. When using any AIMS modes the error destination cannot be set to the output If using customer ID grouping and AIMS then the mode should be audit and the piece id must be defined as the same portion of the label as the customer id If job number control mode is read from prime then reading must be Switched ON V. When using AIMS mode Look up (FBM) the database must contain the number of forms in a group so it can be sent to the inserter VI. For all AIMS modes except statistics the main data logging unit must have reading set to on 2.0 IMOS Setup 2.1 Network Devices Setup in Engineer Screen This screen shown below is used to set up the communications between the IMOS PC and the AIMS server. The two protocol timers should remain as displayed below. The IMOS and AIMS protocol uses 2 channels on 1 Ethernet cable. One is for the input and one is for output. The settings are always the same for both channels. Depending of the type of network being connected (or the network settings) either a Host name or IP address needs to be defined. The example below shows the Host name Ivs-primary The port number is currently always 2002 as displayed Page 4 of 37

5 The time out settings should be as shown Start-up Critical 1000 The lost connection setting should be set to never reconnect The IP address or the Host name is entered by the onscreen keyboard 2.2 Inserter Definition Setup When using a DS-1xxx inserter with AIMS it is important to identify each inserter by a name and ID. (This allows multiple inserters to be connected) Page 5 of 37

6 The Machine Name (inserter name) is what is displayed in AMIS dashboard and the status will update to show when the inserter is connected to AIMS For Machine name alphanumeric characters, blank spaces and underscores are permissible. However, all other symbols / special characters are not permissible, these include / : ;., *? and = The Machine ID is used internally if more than one inserter is connected to AIMS. The default settings if NO name entered is NeoDS_IMOS For machine ID only 8 numeric characters are permissible Page 6 of 37

7 3.0 AIMS Job Programing 3.1 Job number control Modes Job number is integral to AIMS for the system to function correctly. If a job number is not on the documents being processed it can be manually entered or automatically generated by IMOS (ALL modes of AIMS must have a job Number) Page 7 of 37

8 3.1.1 Auto generated In this mode the job number does not appear in the prime document. In this case IMOS will generate a job number for statistics and data logging (and for AIMS). The job number will be automatically incremented each time a new run is started. This mode can be used where a prime document is either dumb (no machine control marks), OMR, or only provides the Piece ID. When Auto-generated is selected the user will be prompted to change the job number or continue with the job number at the start of each run. This allows the user to dictate where his work will appear in statistics and data logging Manual entry In this mode the user can enter the job number. The job number will be sent to the AIMS (also sent to the inserter prime document channel so that the documents being processed can be checked against the job number. (If this security option is turned on) Manual entry (no external checking) Not used for AIMS jobs Read from Prime In this mode the job number is read from the first page to be processed on the prime document channel. The prime document channel is halted until the inserter/imos has confirmed with AIMS that it is a valid job and then continues processing. (When using the Read from prime mode the software uses the job number read for statistics and data logging) Page 8 of 37

9 3.2 AIMS Control Modes Depending on the stationery being processed and if the customer has a database, different modes of AIMS may be used Page 9 of 37

10 3.2.1 Statistics Used when no Label (BCR/2d/OCR) is read from the prime document to identify it. Note: This includes OMR BCR/2D operation as well as dumb applications. A document identifier is system-generated and used to create a piece ID in AIMS as it is processed by the inserter. This is done in order to generate data for the Dashboard and analysis modules of AIMS Audit This is used to create a log of each item processed by the inserter in AIMS, using a MailPiece ID read from the Label (BCR/2d/OCR) on the document. This also allows Hand-Mailed items to be updated or added. A Job Summary can then be created for internal or external use as proof of processing. The Dashboard and analysis modules are also simultaneously updated Verification This is used when a Job has been imported into AIMS to be processed. As each MailPiece ID is read from the Label, its existence, validity and status in an AIMS Job are verified before it is processed. Note: the information on how to process the document, must also be contained within the Label. As it is processed, the record in AIMS is updated with its new status Once all documents have been run on the inserter, Hand-Mailed items may be updated. A Reprint File can then be generated and sent back to the originating software, instructing it which items are missing or have been removed during the insertion process, allowing it to reprint the appropriate ones Once all MailPieces in a Job have been processed the Job can be closed, giving a complete Closed Loop record of completion LookUp This also requires a Job to have been imported into AIMS. The same verification process of MailPiece existence, validity and status also occurs. The significant difference to Verification Mode is that the information on how to process the document is only contained within the JAF file in AIMS. As the MailPiece is verified this information is sent back to the inserter, instructing it how to process the document. After completion, the Job can be further processed in the same way as for Verification Mode Page 10 of 37

11 3.3 Data logging Mode AIMS Compatible Statistics Mode This feature allows IMOS data logs to be identical to the data uploaded to AIMS. In the event of a server or network failure this allows all materials processed to be recorded in the IMOS data logs and then uploaded to AIMS when the network / server connection is restored this is for future development This allows the inserter to be used in a Disaster Recovery Mode This mode of data logging is automatically ON for AIMS stats mode, it ensures that all the required data (for AIMS) is data-logged regardless of the setting for mark reading (data logs are created when you are running fixed multiples or OMR) Data logging mode should be standard for all other AIMS modes OFFLINE PROCESSING If the connection to the server is down it is possible to still process must jobs that previously sent live data to the AIMS server. This cannot be done for lookup mode as all of the machine control is in the database. However if using any of the AIMS modes and the machine control is either contained in the document label, processing an intelligent job or if you are processing a fixed multiple, then all of the required data is logged by IMOS. These data logs can be used later when the server connection is reestablished and the data be sent to the AIMS server as if it had been processed with a live connection. To do this an extra NTL software upload utility must be used. The upload utility is due for release Q Please contact NTL IPSS for more details Duplicates All modes of AIMS except statistics duplicate detection. This means that if the same mailpiece id, as previously processed in the same job, is seen at the input a fault will be installed preventing this mail piece from being processed. Fault Code 1022 State Data Received Duplicate Document ID Action Document ID read has already been processed. Remove ALL documents from the unit and manually correct documents. This document and any other document fed from the feeder on the unit that detected the fault are forced to be removed. When re-starting the next document fed is checked to see if it is a duplicate or a new good mailpiece id Page 11 of 37

12 3.3 Label Setup When using a document with a label (OCR, barcode, 2D) with AIMS it is important to set the following settings (some settings are optional and some are not applicable for certain AIMS modes/job number control modes) Job Number If a Job Number is being read from the prime document then its position and length within the label must be defined Page 12 of 37

13 The Job number characters permissible are alphanumeric, blank spaces and underscore. Maximum number of characters is 15 Example of the warning message when an invalid character is used in the definition Job number Page 13 of 37

14 3.3.2 Piece ID For most AIMS modes a piece Id will be required on each label. The length and position within the label must be defined Piece ID Characters Permissible alphanumeric, blank spaces and underscore. Maximum number of characters is 10 IMOS Job Name alphanumeric and blank and underscore and + and and # Character Restrictions Summary for AIMS When defining items to be used with AIMS there are certain restrictions on the characters that can be used. This affects the following: Job number alphanumeric and blank and underscore Piece Id alphanumeric and blank and underscore IMOS Job Name alphanumeric and blank and underscore and + and and # Machine Id numeric up to 8 characters Machine name alphanumeric and blank underscore All other symbols / special characters are not ed (These include / : ;., *? and =) Page 14 of 37

15 This is one of the warning messages that is displayed if an illegal character is used when defining a restricted text entry (See next page for another example) The job name must also not be blank or the following warning message will be displayed Page 15 of 37

16 3.4 Security Check settings A new security setting is available if a job number is defined. Job Number Characters. This mode checks that the document groups being processed contain the same job identifier. If the job number changes unexpectedly within a job run then a fault is displayed (the error document is currently stopped as soon as possible within the processing unit) Page 16 of 37

17 3.5 Data logging The existing NTL data logs are still produced (if a label is being read or AIMS Compatible statistics is ON). It is recommended that input logging is also turned on when using job number and piece ID. (First page should also be selected as the piece id will change for each new customer) Page 17 of 37

18 3.6 Logging to AIMS Only the main (not necessarily the prime) unit should send the job number and piece id s to AIMS. This is setup by defining the main data-logging unit in the miscellaneous tab of the configuration screen in IMOS. Most cases this will be the prime (as this unit is reading a label) but it can be a downstream unit if the prime is non-intelligent or not the master 3.7 Datalogging From multiple Units If more than one unit is intelligent (reading) and the label information needs to be passed to the AIMS server then the units that are not the main data logging unit must have data logging enabled. This option can be found in the configuration screen. Select the unit and make sure the option for Data logging is set to ON Page 18 of 37

19 3.8 Data-logging and AIMS Logging Older DS-1xxx systems logged data when the envelope left the main inserter head. For AIMS it has been necessary to move logging locations to the final destination. Envelopes removed between the exit of the main inserter head and the final destination will be logged as a removal from the output area (uniquely identified -40) Final Destination in the Vertical Stacker (VS) The new logging as described above means a filled envelope is not logged (in AIMS or NTL data logs) as a good output until it reaches its final destination This section explains for a VS when we log good output and which envelopes are logged as good outputs or as a removal During a controlled stop (including autoending) no envelopes are left in the VS, they are put onto the VS conveyor and logged as a good output. The VS wheel will flush after an input jam so no envelopes are left in the VS wheel. When the inserter starts it performs a flush of the VS to double check no envelopes are present. A filled envelope is logged as a good output when it arrives on the VS output conveyor (and the VS wheel has completed its move) see Picture 1 All envelopes shown here are logged as a good output Picture 1 When a jam occurs at the VS wheel it is important to remove the correct envelopes If the VS wheel stalls before it completes its move then only the last envelope in the VS wheel should be removed (the other envelopes in front of it have already been logged as a good output) see Picture 2 and 3 Picture 2(only remove this envelope) Picture 3(only remove this envelope) Page 19 of 37

20 If the VS input stepper stalls then the VS wheel will flush (so no envelopes are left in it) then all other envelopes in the VS must be removed. On re-starting the VS will re-sync and flush to check no envelopes have been left in the VS. See Picture 4 If an envelope that should have been remove was not it will stop as shown during the VS start-up flush routine. This envelope is then forced to be removed Picture 4 If a VS wheel jam fault is displayed the envelope will be forced to be removed Fault Code 512 State Vertical Stacker Wheel Jam Action Remove ONLY the LAST Fed Envelope in the VS wheel (Clear the Jam.) Press Start to continue If the VS input has a jam then the envelope(s) at the VS entry / VS side guide must be removed. See Picture 5 All envelopes shown here must be removed Picture 5 Envelopes further up the VS can be left in position or removed. If they are physically removed then during the VS start-up flush routine they are logged as removals Page 20 of 37

21 The envelopes shown here are the ones that can be left in the VS, after certain faults or removed If they are NOT physically removed then during the VS start-up flush routine they are logged as good outputs and put onto the VS output conveyor If the envelopes are not removed when they should have been (depends on the exact fault and precisely when the fault occurred) then, again, during the VS start-up flush routine a VS wheel jam fault (code 512) will be installed and they will be force to be removed 3.9 Reporting Which Feeder Fed to AIMS When using AIMS it is possible to log the intended feeder rather than the physical feeder. This can be very useful as it means the results sent to AIMS match exactly what is in the Job Allocation File (JAF) regardless what hardware is fitted. The substitution (mapping) tables under the miscellaneous tab in the configuration settings is the master and should be used for making any AIMS related substitutions Above example has no feeder substitutions. To return to this setup select clear all Page 21 of 37

22 3.9.1 Mapping a feeder because it is broken Previously the main reason to use substitution tables was because the intended feeder was faulty. This is still possible and AIMS will report that the intended feeder fed rather than the actual feeder. See example below: Mapping a feeder as it cannot feed the requested insert Depending on the inserter configuration it may not be possible to feed the required insert from the unit number in a JAF. Using substitutions it is possible for the inserter to feed the required insert from any unit and report back that the feeder that fed was actually the feeder requested in the JAF. See example below: Mapping a feeder so it matches the data in a JAF Using substitutions it is possible for the inserter to feed the required insert from any unit and report back that the feeder that fed was actually the feeder requested in the JAF. Page 22 of 37

23 3.9.4 Demanding multiple feeders from a single demand A requirement may exist for multiple feeders to be commanded from a single feeder demand in a JAF. When this type of substitution is defined the reporting in AIMS will show that the additional feeders have fed along with the original (original feeder could also be substituted to match a JAF) See example below: Mapping the prime feed unit to match a JAF If using a JAF file that s used across multiple equipment manufactures or multiple inserters from the same supplier (but with different hardware configuration) it may be required to substitute the prime feeder so that the feeder reported to AIMS is the same as the feeder number in the JAF and not the physical feeder that fed the prime documents. See example below:- Page 23 of 37

24 4.0 Custom Codes Custom code 20 has been developed to be used with AIMS systems (LookUp mode). This code is designed to have very little (or none) inserter control in it, as the control is provided by the database. (See NTL BCR Specification for details) Form Sequence within a Group can be defined on the document and used if required The forms in group information MUST be in the database for Lookup mode and contained in the label for Verification mode (It is recommended that it is also in the label when using Audit mode) 4.1 Other Custom Codes Other custom codes may not all modes of AIMS. Please contact NTL IPSS for more information Page 24 of 37

25 5.0 Validation of Settings When Defining an AIMS Job 5.1 If No piece id defined The following warning is displayed 5.2 No job number defined The following warning is displayed 5.3 No job number or piece id defined The following warning is displayed 5.4 No label / reading is OFF for main datalogging unit Then one of the following warnings is displayed for the 5.5 No Label defined Mark reading is set incorrectly (OFF) so the above warning is displayed Page 25 of 37

26 5.6 Run Screen when AIMS is Installed The IMOS run screen shows the AIMS mode selected and if a connection is live to the server. (This is only displayed if network settings are defined to connect to AIMS) The following is shown if AIMS is defined in the IMOS settings but not being used for the current job run The following shows that the AIMS mode is Statistic and that the connection to the server is live (green arrows) Page 26 of 37

27 6.0 Starting a Job 6.1 Job with Auto-generated Job number When using Auto-generated job number and AIMS the following selection screen will be presented when the run button is pressed. This is where the job number to be used for this job run is defined. You can either use a new number or the previous one Connecting to AIMS at the start of a job run Finishing a job run with AIMS When running a job with AIMS the following screen will appear on the run screen when IMOS tries to connect to the server. Duration displayed depends on the connection speed Disconnecting from AIMS after a job run When finishing a job with AIMS the following screen will appear on the run screen whilst IMOS completes sending all the required messages to the server. Duration displayed depends on the connection speed When finishing a job with AIMS the following screen will appear on the run screen when IMOS tries to disconnect from the server. Duration displayed depends on the connection speed Page 27 of 37

28 6.2 Job with Manual Entry Job Number When using a manually entered job number and AIMS the following selection screen will be presented when the run button is pressed if no job number has been defined in the Job Settings screen. This is where the job number to be used for this job run is defined by the operator. 7.0 AIMS Specific Fault Codes For a full list of all the associated AIMS fault codes and some advanced trouble shooting information see Appendix 1 at the end of this document 7.1 No Read on the First Document processed If the Job number control mode is Read from Prime and a no read occurs the following fault will be installed Fault Code 613 State Job number confirmation has failed Action Document was a NO Read, so job number could not be confirmed. Remove Document and Press go to continue The inserter will re-attempt to connect to AIMS and validate the job number on the next successful good read processed Page 28 of 37

29 7.2 Autoending Scenarios When Running with AIMS Autoending a job run when running with an AIMS mode on, works as follows IF EOG a) The Feeder goes empty The following happens: feeder empty fault displayed, run pressed and the inserter tries to feed, if no new documents added (no EOG) then the sub group will be forced complete (set as a possible corrupt group) and diverted allowing the autoend sequence to complete and the AIMS connection is closed b) Autoend pressed midway through a job run (due to lunch break / shift change) The following happens: inserter feeds to the next EOG, completing the sub group and then completes the autoend sequence (leaving no documents in the inserter) and the AIMS connection is closed If FOG a) The Feeder goes empty The following happens: feeder empty fault displayed, run pressed and the inserter tries to feed, if no new documents added (no FOG) as last page has already been fed (feeder empty), then the sub group is assumed to be complete and sent to the output. The autoend sequence completes and the AIMS connection is closed. b) Autoend pressed midway through a job run (due to lunch break / shift change) The following happens: inserter feeds to next FOG, so EOG can be set completing the sub group already fed. The inserter then completes the autoend sequence leaving the last fed FOG doc / docs in the inserter and closes the AIMS connection. A fault message is then installed forcing these document(s) to be removed before the next job run (these documents have not been sent to AIMS so can be re-loaded into the feeder and processed) Fault Code 28 State FOG Document Needs to be Removed Action Autoending FOG documents with AIMS requires the next FOG to be removed at the completion of the job run 7.3 Abandoning a Job that is Running with AIMS Always autoend the current job run before leaving the run screen. It is not good practice to make setting changes in the middle of a job run If the Job is abandoned then all documents that have been fed and have sent an input message to AIMS will be logged as removed (uniquely identified as -11 in NTL data-logs and as an error document in AIMS) The operator will be forced to remove all documents from the inserter before allowing starting a new job run Page 29 of 37

30 7.4 Re-setting the AIMS connection If the initial connection routine fails (invalid database /server error) then IMOS will reset the previous connection to the AIMS server. The following message will be displayed A similar message will also be displayed if the job is abandoned. Page 30 of 37

31 Appendix: Error Codes and Actions AIMS specific faults and Recovery Information Error Error Message Recovery Information 27 Oversize Group Destination Not Compatible with AIMS 28 FOG Document Needs to be Removed 329 No Reply from AIMS 550 Duplicate Document in Sheet Divert Bin Duplicate Document in Sheet Divert Bin 2 Change the destination for oversize groups in the IMOS configuration settings so that they are not sent to the output Autoending FOG documents with AIMS requires the next FOG to be removed at the completion of the job run Remove all Documents from the collate upper conveyor. If Fault persists check all connections and check the AIMS Error log for more details Remove group from Divert 2 and manually correct Remove group from Divert 1 and manually correct Operator troubleshooting guide if fault persists N/A N/A Check the material being processed is for the correct job run. Also check with a supervisor that the job run has not been reprinted Check the material being processed is for the correct job run. Also check with a supervisor that the job run has not been reprinted Engineer troubleshooting Guide if Fault persists N/A N/A Inform IT department or production department that a job run has been repeated. Inform IT department or production department that a job run has been repeated. Page 31 of 37

32 Error Error Message 552 Invalid Piece ID on the Document in Sheet Divert Bin Invalid Piece ID on the Document in Sheet Divert Bin Piece ID Not Match 613 Job number confirmation has failed Recovery Information Remove Documents from Divert 1 and manually correct Remove Documents from Divert 2 and manually correct Remove ALL documents from the collate unit and manually check / correct Document was a NO Read, so job number could not be confirmed. Remove Document and Press go to continue 1001 NACK Error Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS 1002 Error Timeout Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Operator troubleshooting guide if fault persists Check the material being processed is for the correct job run. Also check with a supervisor that the job run has not been reprinted Check the material being processed is for the correct job run. Also check with a supervisor that the job run has not been reprinted Check the material being processed is in the correct page sequence Check the material being processed is for the correct job run. Engineer troubleshooting Guide if Fault persists Inform IT department or production department that a job run has been repeated. Inform IT department or production department that a job run has been repeated. Check the job is programmed correctly Inform IT department or production department that a job run has been repeated. Page 32 of 37

33 Error Error Message 1003 Error CMD NOT sent correctly 1004 Cancelled by User 1005 Duplicate Mail Piece 1006 Cannot Connect To AIMS Possible TCP/IP Error 1021 Data Received AIMS Error 1022 Data Received Duplicate Document ID Recovery Information Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Document ID read has already been processed. Remove ALL documents from the unit and manually correct documents Operator troubleshooting guide if fault persists Check the material being processed is for the correct job run. Also check with a supervisor that the job run has not been reprinted Check the material being processed is for the correct job run. Also check with a supervisor that the job run has not been reprinted Engineer troubleshooting Guide if Fault persists Inform IT department or production department that a job run has been repeated. Inform IT department or production department that a job run has been repeated. Page 33 of 37

34 Error Error Message 1023 Data Received Invalid Job Number 1024 Data Received Invalid Doc Number 1025 Data Received Invalid Data 1026 Data Received Invalid Page Number 1027 Data Received Invalid Process Type 1028 Data Received Piece Removed 1029 Data Received Piece Added Recovery Information Job Id has no Database on AIMS. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Piece Id read is not in the Database. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Operator troubleshooting guide if fault persists Check the material being processed is for the correct job run. Check to ensure that job has been copied to the AIMS server Check the material being processed is for the correct job run. Also check with a supervisor that the job run has not been reprinted Engineer troubleshooting Guide if Fault persists Inform IT department or production department that a job run is not valid. Inform IT department or production department that a job run is corrupt. Page 34 of 37

35 Error Error Message Recovery Information Operator troubleshooting guide if fault persists Engineer troubleshooting Guide if Fault persists 1030 Data Received Piece Removed Double 1031 Data Received Piece Added Double 1040 Create Connection Failure. No Response from AIMS 1041 Close Connection Failure 1042 Watchdog Not Received See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS 1043 Critical Error Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Page 35 of 37

36 Error Error Message 1044 General AIMS Error 1051 Error Connection Already Live with different Parameters 1052 Job ID is Not Valid 1053 Connection Already Open 1054 Process Type is Not Valid 1055 Create Connection Request Not Received 1056 Invalid Number of Arguments in the Data Recovery Information Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Job Id has no Database on AIMS. See AIMS and/or IMOS error log file for more details Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Operator troubleshooting guide if fault persists Engineer troubleshooting Guide if Fault persists Page 36 of 37

37 Error Error Message Packet Recovery Information Operator troubleshooting guide if fault persists Engineer troubleshooting Guide if Fault persists 1057 Invalid Argument in the Data Packet 1058 Invalid Packet or String Received 1997 AIMS Not Licenced For This product 1998 Error Detected in Database 1999 Job Has Already Been Closed Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS Check all connections and settings are correct. See AIMS and/or IMOS error log file for more details. If fault persists contact NTL IPSS See AIMS error log file for more details. If fault persists contact NTL IPSS Check Last Few Mail Pieces Processed are correctly logged in AIMS. See AIMS log file for more details. If fault persists contact NTL IPSS This job has already been processed and been closed by AIMS. Check the correct job number is being processed. If fault persists contact NTL IPSS Page 37 of 37