iMove
iMove Overview
iMove updates addresses for members that have moved.
Performs updates in real-time. No need to export your entire database for processing.
Uses the Datatech SmartSoft AccuMail Move™ software for real-time NCOALink® change of address processing. It processes any moves made in the past 18 months.
Reduces costs by only validating addresses you select.
Generates documents required for resorted discount certification on USPS First Class and Standard Mail.
Pricing is scaled to the number of addresses certified.
iMove Basic System Requirements
The following system specifications are required to successfully run iMove:
UDP port 1434 must be open on the SQL server
Both inbound and outbound traffic must be allowed on port 443 to 173.45.128.38
Windows 7 or higher
iMIS must be installed to run iMove
iMIS 15.2 or higher
Microsoft .NET Framework 4.0
SQL Server 2008 or higher
iMove Installation (First Time Install)
Download iMove from https://customer.csiinc.com to your workstation.
You will need your CSI Website User Name and password. If you do not have this information, contact support@csiinc.com.
Unzip the file to the intended installation location.
Run the AccuMailIMoveUpdateSetup.exe to install the AccuMail Move Toolkit.
NOTE: This MUST be installed before installing or updating iMove.
You will then receive prompts for the installation of the AccuMail Move Toolkit, for which you will have to complete the installation wizard.
Next, click on iMove_v2_x_x_setup.exe. This will launch the Installer Wizard for iMove. Click Next in the dialogue box to begin installation.
Choose "I accept the terms in the license agreement" and click Next.
Choose Install. The Installation Wizard will let you know the progress of the installation.
A dialog box will appear letting you know that iMove was installed successfully. Click Finish.
Restart your computer if prompted by the installer.
Troubleshooting Installation:
Error Message: "Could not load the file or assembly 'NCOATools_NET.dll' or one of its dependencies. The specified module could not be found."
If you get this error message after launching iMove and logging in, you have some additional install steps.
NCOA Toolkit is looking for files that are not present on your computer
You must download and install the "Visual C++ Redistributable for Visual Studio 2015" from here:
https://www.microsoft.com/en-us/download/details.aspx?id=48145
Press the download button
Select vc_redist.x64.exe – if your computer is 64 bit
Select vc_redist.x86.exe – If your computer is 32 bit
After downloading double click on the executable file and follow the installation instructions.
When finished installing, you must restart your computer.
Run iMove again and login, you should no longer get the error message.
Upgrading iMove - (in place upgrade) if your version is 2.4.4 or older
Note: It is best practice for all users to be on the same version of iMove.
Login to the CSI Portal and download iMove to your workstation.
You will need your CSI Website User Name and password. If you do not have this information, please contact support@csiinc.com
Copy the following files to a temporary folder. You will need to copy these filed to a new location after the upgrade has completed.
NCOACustInfo.bin
NCOASetup.bin
PAFData.bin
These files will be in the \Smartsoft\NCOA\ folder. For most instances, that folder will be in the root drive of your PC (e.g. C:\Smartsoft\NCOA). However, that folder may exist elsewhere in your specific install.)
Uninstall AccuMail Toolkit (via Windows Control Panel).
Unzip the file to the intended installation location.
Run the AccuMailIMoveUpdateSetup.exe from the downloaded iMove to install the AccuMail Move Toolkit.
NOTE: This MUST be installed before installing or updating iMove.
Run the iMove_v2_x_x_Setup.exe
After installation is complete, move the three files you previously copied to the proper Smartsoft directory.
iMove is now ready for use.
Upgrading iMove (in place upgrade) - if your version is 2.4.5 or newer
Note: It is best practice for all users to be on the same version of iMove. You do not need to run the Accumail Move program if you are upgrading from iMove 2.4.5 or newer
Login to the CSI Portal at https://customer.csiinc.com and download iMove to your workstation.
You will need your CSI Website User Name and password. If you do not have this information, please contact support@csiinc.com
Unzip the downloaded zip file and right click to Run as Admin the iMove_v2_x_x_Setup.exe file
iMove is now ready for use.
Note: Beginning with iMove 2.5.4, if your backup is exceptionally large, iMove will require it to be truncated before the program can proceed. You will be given the following warning
and you must click OK in order to continue. This will purge the backup table and the product will ensure that the table will not grow excessively provided you have the Automatic Purge Setup under Tools - Options. CSI recommends this be set to no more than 3.
About the License Key
When you first log into iMove, the license process will attempt to register your license key automatically by calling back to CSI to get your iMIS information. If the information that CSI has on record is accurate then you will not be prompted with any license key information. It will update your license information automatically.
If the process cannot call CSI or the license key information does not check out with what CSI has on record, then you will be prompted to enter a license key manually. You will need to obtain this key by contacting CSI Support. After the license key has been validated and entered, you will be able to use iMove on your iMIS database. Since the license key is stored in your iMIS database, you will only need to enter this key once per database. Installing iMove on a new computer will not require you to re-enter your license key.
Note: Changing the "Licensed To:" name for iMIS will require a new license key. If the license key detects a change in this, it will follow the same process as above trying to call back to CSI to verify your product information. In most cases, if you are prompted for license information it is likely that CSI does not have your updated iMIS information. Contact CSI at support@csiinc.com with a screen shot of the current iMIS System Setup and a new key will be emailed to you.
Log into iMIS as an administrator (manager)
Click on File > System Setup in the top toolbar
Copy and send to support@csiinc.com
iMove Setup
iMove Launch and Login
Launch iMove from Start > All Programs > CSI Programs > iMove
Log into iMove using your iMIS user name and password.
DSN represents your iMIS 10 ODBC server location. Note: This information is provided for archive purposes only. iMIS 10.6 is no longer supported as of version 2.3.21.
The web server represents your iMIS 15 (and above) application server location.
The first time you log into iMove you will need to create new objects on the database. When prompted, click OK.
Enter your iMIS SQL server user name (usually SA) and its Password and click OK.
Setting Up iMove
1. When you purchase iMove, CSI places a PAF order with SmartSoft on your organization’s behalf. The License Key and Toolkit Key are generated by SmartSoft and sent to both you and CSI. These keys are required to set up iMove. Help can be found here: https://ncoa.smartsoftdq.com/pafms/Help/html/948e3bbd-a19f-4e10-8cd2-7c375f43a664.htm
2. The first time you log into iMove, you will receive the error below. This section walks you through setting up the PAF, so the error should not appear again.
3. Navigate to Tools > NCOA > NCOA Setup… > PAF Setup...
4. A browser window will open and direct to https://ncoa.smartsoftdq.com/pafms/Account/Login. Click Register.
5. Enter your username, License Key (both provided by SmartSoft) and your email address. You can now log into the PAF Management System. Ensure your PAF is listed and has a Status of Enabled.
6. In iMove, go to Tools > NCOA > NCOA Setup… > Account…
7. Enter User Name, Web Service License Key, and Toolkit License. Click OK.
8. Click Refresh PAF List… The Selected PAF dropdown and Account Statistics section will populate.
9. After doing this, you can run iMove.
Using iMove
On the iMove Data Pull screen, there are multiple options for selecting addresses to be sent for verification. Specific Member Types, Categories, Statuses, and Addresses can be selected. The values displayed are pulled from the iMIS database.
Note: On the bottom bar of the interface, iMove displays when your NCOA credit account expires (NOTE: new PAFs only need to be remitted when there are changes to it; it will not expire). When applicable, the quantity of credits remaining will also display (i.e., if you do not have unlimited credits).
Checking All or leaving all individual values unchecked in each section will select everything.
Checking Mail, Bill or Ship in the Addresses section will select the corresponding preferred address for verification.
Click Load Data to return the records from your defined criteria.
The minimum record set for verification is 100. The current record count is displayed just below the Addresses section.
Alternately, you may pull the addresses with a SQL statement. Refer to Handling Large Record Sets Using SQL Mode.
Click Get Address Corrections. You will be prompted to load the data first. Press OK to load the data. Then select Get Address Corrections again.
If there are insufficient credits to send the data or if the NCOA credit account will expire soon, the below dialog box will display, respectively.
An NCOA Web Services dialogue box will open displaying user name, license key, PAF name, PAF ID, the current record count for verification and the remaining number of verification credits on your account. If the address credits are running low please contact sales@csiinc.com to order additional credits. Click OK.
The dialogue box will display the status of the verification process.
Once complete, you will receive a Web Services Results window that allows you to view NCOA results for you address data, if desired.
These reports are saved automatically as PDF in a folder called NCOAOut. The folder is automatically created in the same path where you chose to save the comma separated value file previously.
If desired, you may view the data prior to importing into iMIS by selecting the report you wish to view and clicking on View/Print.
Click Close and the data import to iMIS will begin. A progress will display at the bottom of the iMove window.
Click OK to continue once the import completes. The NCOA results will display in the iMove Data Pull window.
On the next few pages you will find a list of NCOA Result, Move Type, and NCOA Correction code definitions that correspond to the NCOA Result, NCOA Corrections, and Effective Date columns below. The NCOA address verification and import to iMIS is now complete.
Handling Large Record Sets Using SQL Mode
When verifying a large set of addresses, it is best to break them up into smaller groups. iMove should be able to handle up to 400,000 addresses in a single set. However, if you have a single member type/status combination that contains more than 400,000 records, you can use SQL Mode to split them up for processing.
To use SQL Mode, write a query in the space provided, or write it in Management Studio and paste it in the window. The query should only return two fields: the ID of the record and the address number field for the address you want to verify. Address number fields for the preferred mail, bill and ship addresses can be found in the iMIS Name table at: MAIL_ADDRESS_NUM, BILL_ADDRESS_NUM or SHIP_ADDRESS_NUM.
Here is an example query that would verify the preferred mail address for "C" member type records, with a status of "A":
Select ID,
MAIL_ADDRESS_NUM
From Name
Where MEMBER_TYPE = 'C' and
STATUS = 'A'
You can substitute member type and status values that apply to your organization, as well as add other types of filters to refine the query.
Important: Please remember, the ID field is a varchar field and as such, will not work well when using between or greater than or equal unless you convert the field to integer. So consider "convert(INT,ID)" instead of ID when using ID in a where clause. For example:
Select ID, MAIL_ADDRESS_NUM FROM Name where convert(int,ID)>100000 and convert(int,ID)<200000
Another method to break up a large record set in SQL Mode is by using the MODULO operator. The MODULO operator is expressed using: %. You can refer to the following link for more information on MODULO:
This operator is used to divide a number by another number and return the remainder of the division only. For example, if we take any sequence of numbers and divide them each by 3 using MODULO, the result will of each will always be one of three numbers: 0, 1, 2. Here is an example, using the query above:
SelectID,
MAIL_ADDRESS_NUM
From Name
Where MEMBER_TYPE = 'C' and
STATUS = 'A' and
convert(int,ID) % 3 = 0
Using this pattern, you would run address verification, change the 0 to a 1 and run it again, then finally change the 1 to a 2 and run the final verification. This effectively divided the record set into thirds for processing.
iMove Options
There are several options available for customization of iMove.
Click on Tools > Options to open the Options window.
Countries To Send
Include Blank Countries – selects addresses where country is "blank" – most users should pick this option. Currently, NCOA processing can only occur on U.S. addresses. In the future, when foreign country processing becomes available, you may select additional countries from the checkbox list.
Import Options (From NCOA to iMIS)
Option | Explanation |
---|---|
Import Business moves | NCOA Move code is "B" |
Import Family moves | NCOA Move Code is "F" |
Import Individual moves | NCOA Move Code is "I" |
Log all address changes | All address changes will be logged regardless of which address tab they appear on. The Name_Log entries take the form: |
Flowdown address changes to child records | This will force address changes from the first address tab (Address Number 1) parent record to flow down to child records, if the child record's first address tabs full address matches the parent record's full address. Please note, if you have this option on, avoid selecting child records, since the order of updates may result in the same child record getting updated by both flowdown and NCOA processing. |
Ignore the Address 2 and Address 3 fields | Do not send Address 2 and Address 3 fields to SmartSoft.
|
Use standard options | Use default options to process address updates. If you choose to use standard options, you cannot use a stored procedure. |
Use csi_sp_iMoveImportCriteria stored procedure | You will need to write this stored procedure for usage – see example in User Guide. Also note, if you select this option, the import Business, Family, and Individual moves options will be disabled, as well as the option "Update Records that did not move (Zip+4 & Address Standardization)". |
Call stored procedure after updates | Allows for a user-written stored procedure to be called following the NCOA address updates. Enter the name of the stored procedure in the textbox provided. |
Ignore Move Effective Date | If checked moves that occur in the future are imported – providing they meet the criteria below |
Update records that did not move (Zip+4 & Address Standardization) | Enable this option to update ZIP+4, CRRT, BAR_CODE and DPB values for records that did not move, but a good match was found. Enabling this option is highly recommended. |
NCOA Backup Data Purge
iMove maintains its own backup table of all address corrections. As this table can grow quite large, we have added the ability to automatically purge older records from this table. To view the number of records you have in this table, you can run this statement (from SSMS)
select COUNT(*) From csi_Ncoa_backupdata
There will be a prompt, upon starting the iMove program (below), the first time iMove is run. The default setting retains the 2 most recent set of records only.
After opening iMove, this setting can be modified, or turned off, at any time. Go to Options, and change the number of record sets to keep by entering that number in the box (Automatically Purge ID/Address Backups). Entering the number 0 will turn this option off.
Clicking 'PURGE NOW' will display a window showing how many records it will be purging, before proceeding.
Bad Address Mapping
This feature is available to users who have the BAD_ADDRESS general lookup table in their iMIS database and have selected the "Use standard options" import option.
Use iMove to automatically update "bad" addresses in iMIS.
Note: In order for this feature to work, you must have "Update records that did not move (Zip+4 & Address Standardization)" enabled.
During processing records are first checked against the Accumail Database to ensure they are a true mailable address. If the Accumail Result Code (see Accumail Result Codes) is a zero (0) then the address is then sent for National Change of Address processing. Therefore, any Accumail Result code other than zero (0) can be assumed to be a "Un-mailable Address" and could be marked as such.
However, any address that does pass Accumail processing and is determined to be a mailable address, is sent to the National Change of Address database to see if the address has a move on file (Remember, only moves in the last 18 months are returned). NCOA Result Codes of A, N91, and N92 can be assumed to be a valid move and as such, if the address was marked LOST, it could now have this status cleared.
In the example below, an address is marked lost, and we would clear this Status if the NCOA Result Code of A, N91, or N92 was returned.
Configuration
1. Prepare the BAD_ADDRESS table
a. Create BAD_ADDRESS, general lookup/validation table
This link may be helpful when attempting the setup: https://help.imis.com/classic/Default.htm#Desktop/General_lookup_validation_tables/BAD_ADDRESS_Validation.htm?Highlight=BAD_ADDRESS
b. Per your company business rules, populate BAD_ADDRESS with the relevant code(s).
Now these values will be available in iMove
Note: Bad address mapping and using iMove to change the BAD_ADDRESS flag is a configuration that is specific to your needs. You should make the sure the results match what you are expecting by running on a smaller data set. In general, Accumail Result codes other than 0 indicate a non-deliverable address, and these will NOT be sent for National Change of Address processing. Only Accumail result codes of 0 are processed by the National Change of Address system. Therefore, a result code of 0 for Accumail should not be used.
2. Map Accumail and NCOA Result Codes to the BAD_ADDRESS table
a. In iMove, Tools > Options
b. Enter a valid code in NCOA Result Code
See Accumail Result Codes Definitions and NCOA Result Code Definitions (within this document) or, click the links on iMove’s Options to view descriptions for each code.
c. To flag an address as bad based on the result code, select a status other than “Blank Out” from the Bad Address Status drop down list:
Note: After new values are entered in BAD_ADDRESS, the Options window must be closed and reopened to refresh the Bad Address Status drop-down list.
d. To unflag an address as bad based on the result code, select the status "Blank Out".
3. A sample of mapping of the Accumail Result Codes (see Accumail Result Codes above) might look like:
Numbers 1-16 are Accumail result codes (see Accumail Result Codes) and indicate the address is not real or deliverable. They were and are not processed for NCOA.
4. The NCOA Result Codes are listed in the section NCOA Result Codes (NCOA_COA_CODE). If your organization uses the BAD_ADDRESS field in iMIS and addresses are manually marked bad when mail is returned, then the recommendation is to blank out the BAD_ADDRESS field when the NCOA Result is A, N91, or N92.
In the above example, we have created Bad Address status codes to let us know exactly why an address is bad - numbers 1-16 are Accumail result codes and indicate the address is not real or deliverable. Codes A, N91, and N92 reflect that the address is deliverable and that there was a move found as such, IF the BAD_ADDRESS flag was set in iMIS, we are blanking it out.
In Order to setup the above:
• Mapping grid rows may be deleted by selecting the row header and then pressing the <Delete> button.
• Users choosing to use the “Use csi_sp_iMoveImportCriteria stored procedure” import option instead can still access the NCOA Code to Bad Address mapping by accessing the csi_iMoveNCOACodeBadAddressMappings table in their custom SQL.
Accumail and NCOA Code Definitions
Accumail Result Codes
This column will contain only one of the following codes for each address:
Code | Explanation |
0 | The address has been successfully coded. |
1 | The address is coded but undeliverable (i.e. on side of street known to contain no houses). |
2 | The ZIP code was not found and the city and state cannot be used to determine a geographical area to search. |
3 | Coding would result in changing both ZIP and city. This is illegal for PO BOX and route type addresses. |
4 | The best match would result in too many suspicious changes. |
5 | The street was identified as an alias but was out of the range restricted for that alias. |
6 | No street address was given. |
7 | There are no street name matches in the given ZIP code or in any geographically-related ZIP code. |
8 | The street may contain superfluous components which cannot be discarded with confidence. |
9 | The house number could not be matched. |
10 | The best match was made to a ZIPMOVE record but was not an exact match. |
11 | A ZIPMOVE match was made but no exact match could be found in the new ZIP. |
12 | The Early Warning System indicates that an exact match will become available in the next database update. |
13 | There are multiple matches with the same degree of confidence. This may indicate an inconsistency in the USPS data. |
14 | Incorrect suffix, directional, street name, or unit resulted in multiple matches with the same degree of confidence. |
15 | Incorrect ZIP, city, or urbanization resulted in multiple matches with the same degree of confidence. |
16 | A corrected field was too long to fit into the supplied field. |
17 | Media Error. The database could not be read because of a hardware or system problem. |
18 | Process Fault. Processing was interrupted due to serious program error. Please contact technical support. |
19 | DPV No Match. The address was found in the Zip+4 data, but not matched in the DPV reference. |
NCOA_MOVE_TYPE
This column can contain exactly one of the following coded for each address:
Code | Explanation |
B | Business Move |
F | Family Move |
I | Individual Move |
NCOA Result Codes (NCOA_COA_CODE)
If the address passes the Accumail validity test (indicated by an Accumail Result Code = 0), the address is matched up against the National Change of Address (NCOA) database to determine if a change of address has occurred. One of the following result codes will be returned indicating the result of the attempted match:
Code | Explanation |
---|---|
A | COA Match |
N00 | NO Match |
N01 | Found COA: Foreign Move |
N02 | Found COA: Moved Left No Address(MLNA) |
N03 | Found COA: Box Closed No Order(BCNO) |
N04 | Cannot Match COA: Street Address with Secondary |
N05 | Found COA: New 11-digit DPBC is Ambiguous |
N06 | Cannot Match COA: Conflicting Directions: Middle Name Related |
N07 | Cannot Match COA: Conflicting Directions: Gender Related |
N08 | Cannot Match COA: Other Conflicting Instructions |
N09 | Cannot Match COA: High-rise Default |
N10 | Cannot Match COA: Rural Default |
N11 | Cannot Match COA: Individual Match: Insufficient COA Name for Match |
N12 | Cannot Match COA: Middle Name Test Failed |
N13 | Cannot Match COA: Gender Test Failed |
N14 | Found COA: New Address Would Not Convert at Run Time |
N15 | Cannot Match COA: Individual Name Insufficient |
N16 | Cannot Match COA: Secondary Number Discrepancy |
N17 | Cannot Match COA: Other Insufficient Name |
N18 | Cannot Match COA: General Delivery |
N19 | Cannot Match COA: New Address not ZIP+4 coded, New address primary number not DPV confirmable or Temporary Change Of Address |
N20 | Cannot Match COA: Conflicting Directions after re-chaining |
N66 | Daily Delete |
N91 | COA Match: Secondary Number dropped from COA |
N92 | COA Match: Secondary Number dropped from input address |
EM | Expired Move (Address change was found, but is older than 18 months and therefore no change has been made) |
NCOA_CORRECTIONS
This column can contain zero or more of the following codes for each address:
Code | Explanation | Code | Explanation |
A | Normal street match | S | Urbanization corrected |
B | PO BOX match | T | ZIP+4 corrected |
C | Route type match | U | House number corrected |
D | 'Unique ZIP' match | V | Unit number corrected |
E | 'Small town' match | W | Secondary unit designator corrected |
F | Alias match | X | Firm corrected |
G | 'Highrise alternate match | Y | Street swapped with firm |
H | Firm match | Z | Street swapped with alternate |
I | Highrise match | 0 | Dual address changed to PO BOX |
J | Highrise default match | 1 | Dual address street match |
K | Route default match | 2 | Input city is not preferred but is acceptable |
L | Street name corrected | 3 | Street standardized |
M | Street suffix corrected | 4 | Unit not verified |
N | Predirectional corrected | 5 | Leftovers found |
O | Postdirectional corrected | 6 | ZIPMOVE match |
P | City corrected | 7 | LACSLINK match |
Q | State corrected | 8 | SuiteLink Match |
R | ZIP corrected |
Choose Save Directory
Use this option to set up the folder where the newly created address files from NCOA will be stored.
Stored Procedure Example
This stored procedure imports all records with move updates that have already occurred as long as they are a successfully coded match or an EWS (Early Warning System) match.
CREATE Proc [dbo].[csi_sp_iMoveImportCriteria](
@id varchar(10),
@addrNum int,
@firstName varchar(20),
@lastName varchar(30),
@company varchar(80),
@streetAddr1 varchar(40),
@streetAddr2 varchar(40),
@streetAddr3 varchar(40),
@city varchar(40),
@stateProvince varchar(15),
@zip varchar(10),
@ncoaEffectiveDate datetime,
@ncoaResult varchar(2),
@ncoaMoveType varchar(2),
@ncoaCorrections varchar(40),
@ncoaCoaCode varchar(5),
@errorMessage varchar(255) output
)
AS
--From NCOA Documentation
/*
@ncoaEffectiveDate = contains the date of a move (may be null):
--The date returned is the date the move started
@ncoaResult = can contain exactly one of the following codes:
0 "The address has been successfully coded."
1 "The address is coded but undeliverable (i.e. on
side of street known to contain no houses)."
2 "The ZIP code was not found and the city and
state cannot be used to determine a geographical
area to search."
3 "Coding would result in changing both ZIP and
city. This is illegal for PO BOX and route
type addresses."
4 "The best match would result in too many
suspicious changes."
5 "The street was identified as an alias but was
out of the range restricted for that alias."
6 "No street address was given."
7 "There are no street name matches in the given
ZIP code or in any geographically-related ZIP code."
8 "The street may contain superfluous components which
cannot be discarded with confidence."
9 "The house number could not be matched."
10 “The best match was made to a ZIPMOVE record but
was not an exact match."
11 A ZIPMOVE match was made but no exact match could
be found in the new ZIP."
12 "The Early Warning System indicates that an exact match
will become available in the next database update."
13 "There are multiple matches with the same degree of
confidence. This may indicate an inconsistency in the
USPS data."
14 "Incorrect suffix, directional, street name, or unit
resulted in multiple matches with the same degree of
confidence."
15 "Incorrect ZIP, city, or urbanization resulted in
multiple matches with the same degree of confidence."
16 "A corrected field was too long to fit into the
supplied field."
17 "Media Error. The database could not be read because
of a hardware or system problem."
18 "Process Fault. Processing was interrupted due to serious
program error. Please contact technical support."
19 "DPV No Match. The address was found in the Zip+4 data,
but not matched in the DPV reference."
--Example format: 15
--Means: "Incorrect ZIP,city,or urbanization resulted in
multiple matches with the same degree of confidence."
@ncoaMoveType = can contain exactly one of the following codes:
B - "Business Move"
F - "Family Move"
I - "Individual Move"
--Example format: F
--Means: This was a family move
@ncoaCorrections = can contain 0 or more of the following codes:
A "Normal streetmatch"
B "PO BOX match"
C "Route type match"
D "'Unique ZIP'match"
E "'Small town'match"
F "Alias match"
G "'Highrise alternate'match"
H "Firm match"
I "Highrise match"
J "Highrise default match"
K "Route default match"
L "Street name corrected"
M "Street suffix corrected"
N "Predirectional corrected"
O "Postdirectional corrected"
P "City corrected"
Q "State corrected"
R "ZIP corrected"
S "Urbanization corrected"
T "ZIP+4 corrected"
U "House number corrected"
V "Unit number corrected"
W "Secondary unit designator corrected"
X "Firm corrected"
Y "Street swapped with firm"
Z "Street swapped with alternate"
0 "Dual address changed to PO BOX"
1 "Dual address street match"
2 "Input city is not preferred but is acceptable"
3 "Street standardized"
4 "Unit not verified"
5 "Leftovers found"
6 "ZIPMOVE match"
7 "LACSLINK match"
8 "SuiteLink Match"
--Example format: AHT
--Means: "Normal streetmatch","Firm match",and "ZIP+4
corrected"
*/
DECLARE @recordMoved bit --Set to 1 (below), if there was a
--move of any type, otherwise 0
SET @errorMessage = '' --If this is NON-BLANK when we send it
--back, the next step will try and import
--Was their a "MOVE Update"?
SET @recordMoved = 0 IF @ncoaMoveType <> ''
BEGIN
SET @recordMoved = 1 --Set Move Here
END
--See above for what these codes mean
IF @ncoaResult not in (0, 12)
BEGIN
--Only Allow - successful or Early Warning updates –
--anything else - Do Not Import
SET @errorMessage ='Return code is not a match or an EWS match'
GOTO ErrorExit
END
--Check to see if move has occured
IF @ncoaEffectiveDate > GETDATE() AND @ncoaEffectiveDate is not null
BEGIN
--The person is probably moving but it has not happened
--yet, do not update record
SET @errorMessage ='Move code was returned but this move has not occurred'
GOTO ErrorExit
END
ErrorExit:
RETURN
GO
GRANT EXEC ON [csi_sp_iMoveImportCriteria] TO IMIS
GO
Another stored procedure example can be found below.
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- =============================================
-- Author: Justen
-- Create date: 3/5/2015
-- Description: Sample for Stored procedure to run after iMove completes
-- This is a simple example and should not be run, but used as a template
-- =============================================
CREATE PROCEDURE csi_sp_RunAfterImoveSample
-- Add any parameters for the stored procedure here
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;
-- This will update the initiation dates for members
-- within a specific university
UPDATE Demo_Individual
SET IN_INITIATION_DATE = GETDATE()
WHERE IN_INIT_UNIVERSITY = 'Example University'
-- Insert into the name_log table for event logging
INSERT into Name_Log
VALUES (GetDate(), 'CHANGE', 'CHANGE', '999999', 0, 'Changed by iMove after run stored procedure')
END
GO
Setting Up iMove on a Second Machine
Since iMove requires some files to be created as part of the setup of the system, including the PAF file, Customer Info, and FTP information. This information may need to be transferred to a different machine so you can have 2 or more machines with iMove on them. To do this, follow the following procedure.
On the machine that you originally set up iMove, and submitted your PAF files (Processing Acknowledgement Form), locate your iMove NCOA Toolkit directory.
C:\Smartsoft\NCOA
In this directory there will be many files…copy the following files:
(Note: By default, these directories are hidden. In order to copy the 3 Bin files to their new location, you will need to change your folder options to 'Show hidden files'.)
NCOACustInfo.bin
NCOASetup.bin
PAF.pdf
PAFData.bin
Install iMove on the second machine.
Locate the iMove NCOA Toolkit directory on the second machine directory.
C:\Smartsoft\NCOA
Ensuring iMove is closed, copy the files you copied in step 1 to the appropriate directory.
Then open iMove on the second machine. Once logged in, verify your settings have transferred.
Click on Tools → NCOA → NCOA Setup. Then Verify your User Name, License Key and Toolkit License Key and the PAF selected from the drop down are correct.
Remitting a PAF Form
PAF forms must be signed and remitted when new accounts are created or when information on the PAF changes.
Go to Tools > NCOA > NCOA Setup…> PAF Setup.
Login to the Smart Soft website
From the PAF Management System Dashboard, Create a New PAF (Note you cannot modify an existing form.)
Complete the PAF form. Click Save.
Sign the PAF form (digitally or handwritten).
Digital signature option
Click Sign Now
Sign your name (requires all capital letters).
Specify if you are a List Owner or a Broker/List Administrator
Click OK.
Remit the form. You may print the form out and fax it to SmartSoft, but most iMove users will send the form to paf@smartsoftusa.com with the subject of “Revised PAF from for [Company x]”.
Handwritten signature option
Click Print Interim Copy. The PAF form will open.
Print and sign the form.
Remit the form. You may print the form out and fax it to SmartSoft, but most iMove users will send the form to paf@smartsoftusa.com with the subject of “Revised PAF from for [Company x]”.
Once completed, return to iMove.
Open Tools → NCOA → NCOA Setup,
Click Refresh PAF List
Select your new PAF
Warning Notifications
The remaining number of verification credits is less than the current record count for verification.
If there are insufficient credits to process the requested records a notification will be displayed. Please contact CSI, Inc. at sales@csiinc.com if you need more address credits added to your account.
The NCOA credit account will expire soon.
Contact sales@csiinc.com to purchase additional address credits or update the account.
The NCOA credit account has expired.
Contact sales@csiinc.com to purchase additional address credits or update the account.
Advanced Troubleshooting Options
NCOA Customer Info
The information on the NCOA Customer Info screen is automatically filled in during the setup of the Company.
NCOA Test
For verifying connections to the DataTech SmartSoft servers.
Note: This is used only for testing
Set user info (DLL API only)
Run user Info.
Run the process
Run the setup
Validate (DLL API only)
View results (DLL API only)
Run exe checkbox
NCOA Toolkit
By default the NCOA Toolkit is stored in a subdirectory of iMove. If you want to move the location of the toolkit, or point to a toolkit installed in a different directory, you can use this menu option. This is an advanced feature that most users will not need to use.
PAF Createdispatch Error
Open a Command Prompt window and copy in the following command verbatim (all one line):
Regsvr32 "C:\Program Files\Computer System Innovations\iMove\NCOA Toolkit\pdfcreactivex.dll"
This should fix the problem. Otherwise, ignore it.
Account Setup Not Valid
Follow the instructions for moving the .bin files in the Upgrading iMove section of this manual.
Mail Returned with "Unable to Forward" Label
In csi_ncoa_BackupData, the address record(s) will likely have an IMOVE_RESULT value of "Record is marked as not a move, and these records are excluded in options." The mail pieces you are getting returned are ones where the recipient moved, but did not file a change of address with the USPS. The NCOA processor iMove uses only updates addresses where a specific person, family or business files an actual change of address form with the USPS, and within the last 1.5 years.
Create Backup File
Navigating to Actions > Create Backup File you have the ability to save a backup file of the information most recently loaded in iMove. This will include iMISID, FULL_ADDRESS, NCOA_RESULT, and NCOA_DESCRIPTION.
Delete Backup Table
Navigating to Actions > Create Backup Table you have the ability to delete all rows from csi_ncoa_BackupData table.
Process Returned NCOA File…
By navigating to Actions > Process Returned NCOA File… you can load an NCOA File that have returned the processed data.
iMove Troubleshooting
If you have any issues with iMove, please contact CSI Support at support@csiinc.com. Tickets are normally responded to within 1 to 2 business days after they are submitted.
Check out an iMove Best Practices video below!
iMove Release Notes
Version | Date | Notes |
---|---|---|
2.6 | 10/25/2022 |
|
2.5.5 | 8/19/2022 | Fix error "The multi-part identifier "Addr%PrintCompany.ShortValue" could not be bound." when running in SQL mode. |
2.5.4 | 2/14/2022 |
|
2.4.14 | 4/26/2021 | Bug Fix Purge Option |
2.4.13 | 7/23/2020 | Fix index out-of-range error on View Recent Address Changes form. |
2.4.12 | 5/11/2020 | Include parameter @ncoaCoaCode in validation check (CW 94407) |
2.4.11 | 11/6/2019 | International license update |
2.4.10 | 8/15/2019 |
|
2.4.9 | 5/13/2019 | Updated Accumail and NCOA heading on options page (CW 85208) |
2.4.8 | 5/2/2019 | Enhancement to tie Bad Address to NCOA (CW 85208) |
2.4.7 | 3/11/2019 | Modified options grid to accurately read “US Address Correction Result” (CW 83634). |
2.4.6 | 3/7/2019 | Add Export Grid Data button (CW 83634) |
2.4.5 | 3/6/2019 | Add NCOA COA Code to Backup Data table (CW 83817) |
2.4.4 | 11/30/2018 | Additional updates for NCOA Toolkit 2.0 (CW 79096) |
2.4.0 | 11/15/2018 | Update iMove for NCOA Toolkit 2.0 (CW 79096) |
2.3.32 | 9/4/2018 | Update full address when ignore address 2 and 3 is checked (CW 77046) |
2.3.31 | 6/5/2018 | Enhance runtime performance in script csi_sp_UpdateAddressFromNCOA. |
2.3.30 | 1/18/2018 | Added auto purging of NCOA back up table functionality. (CW 72690) |
2.3.29 | 1/11/2018 | Updated licensing in CSI.Core. (CW 72484) |
2.3.28 | 11/10/2017 | Truncate NCOA data backup table when user starts application. (CW 64923) |
2.3.27 | 4/11/2016 | Update user interface to scale correctly with increased font size. (CW 57541) |
2.3.25 | 8/5/2015 | Update Options window. (CW 45718) |
2.3.24 | 7/162015 | Enhancements to login control and iMIS URL handling. (CW 48242) |
2.3.23 | 7/8/2015 | Add support for NCOA Toolkit version 1.6.0.2640 (CW 45718) |
2.3.22 | 6/1/2015 |
|
2.3.20 | 5/5/2015 | Enhancements for Licensing error handling (CW 46315) |
2.3.19 | 4/8/2015 | Enhancements for Licensing, Login and About dialog windows (CW 46315) |
2.3.18 | 3/10/2015 | Include AccuMail Move Toolkit setup during installation (CW #45718) |
2.3.17 | 2/12/2015 |
|
2.3.16 | 12/1/2014 |
|
2.3.10 | 10/23/2014 | Fix Include non-blank COUNTRY option not saving correctly in user interface (CW #43091) |
2.3.9 | 8/22/2014 | Added SELECT, INSERT, DELETE, UPDATE rights for iMIS user on NCOABackupData table(CW #41300) |
2.3.8 | 7/17/2014 |
|
2.3.5 | 7/2/2014 | Remove Bad Address updates when no mapping exists (CW #40501) |
2.3.3 | 5/8/2014 |
|
2.3.2 | 3/19/2014 |
|
2.3.0 | 2/6/2014 |
|
2.2.9 | 12/16/2013 |
|
2.2.8 | 8/9/2013 | Fix the issue of login control Web Server Url (remove "/cs" or "/cs2") for iMIS 20 |
2.2.6 | 8/2/2013 |
|
2.2.5 | 7/30/2013 | Install database objects using the same logic as Meeting Closer, and all other products |
2.2.3 | 7/29/2013 |
|
2.2.2 | 7/26/2013 |
|
2.2.1 | 7/24/2013 | Apply Error Reporting Mechanism |
2.1.11 | 7/11/2013 | Apply Login Control support for iMIS 20 |
2.1.9 | 6/5/2012 | Integrate with new Login Control |
2.1.8 | 4/20/2012 | Support for iMIS 15.2.0 |
2.1.7 | 2/23/2012 | Corrected options from persisting their intended state |
2.1.6 | 10/11/2011 | Added new NCOA toolkit compatibility |
2.1.4 |
| |
2 | 12/23/2009 |
|
1.3 | 10/7/2009 |
|
1.2 |
| |
1.1 | 4/9/2009 | Initial release |