Module: C.O.P.S. Implementation & Operational Guide

Transcription

1 Module: C.O.P.S. Implementation & Operational Guide

2 TABLE OF CONTENTS Chapter 1: C.O.P.S. Module... 3 C.O.P.S. Configuration Overview... 4 Deployment Type... 4 Special Data Handling... 4 Decision Deadlines... 5 Enhanced Security Features... 5 Additional Features... 5 Notification Methods... 5 C.O.P.S. Deployment & Data Handling Options... 7 Active Control=Yes Immediate Release=No... 7 Active Control=Yes Immediate Release=YES... 9 Active Control=Yes Multiple Release Windows=YES Active Control=NO API=YES C.O.P.S. Data Formats C.O.P.S. Daily ACH Input Files C.O.P.S. Output Files C.O.P.S. Custom File Exchange Options C.O.P.S. Import Data Files Client Configuration Companies Payment Recipients (Approved List) C.O.P.S. User Company ID Mapping C.O.P.S. User Access Rights Chapter 2: Training C.O.P.S. Training Agenda General Process Flow Chapter 3: Appendix Chapter 4: Exhibits Version 1.1 Page 2 of 27

3 Chapter 1: C.O.P.S. MODULE C.O.P.S. protects account holders originating ACH credits from account takeover schemes. FIs nationwide use C.O.P.S. as their preferred Credit Origination Positive Pay solution. C.O.P.S. patented processes provide end-to-end automation, enabling FIs to quickly alert originators when funds are being sent to a destination bank and account they ve never been sent to before. C.O.P.S. can simply inserted into the process flow. Financial institutions who are able to load their ACH origination files into C.O.P.S. prior to processing them out to the ACH Operator can leverage C.O.P.S. Financial institutions who work with vendors that have integrated with C.O.P.S. API can also leverage C.O.P.S. protection without loading files. C.O.P.S. boast an array of configurable options to meet the needs of the diverse group of FIs we service. This guide is designed to outline all the implementation and configuration options available today and the steps required to complete them. In addition, user documentation and information to aid in supporting day-to-day operational processing is provided with the goal of insuring a successful, efficient implementation and excellent on-going experience for our FIs customers and their originating Clients. The following user guides for C.O.P.S. are defined below and can be found attached in the appendix. Client User Guide FI User Guide Appendix A: C.O.P.S. Client User Guide Appendix B: C.O.P.S. FI User Guide ACH Alert provides tools to help FIs sell C.O.P.S. to their Clients. They include: Client Sales Videos Client Training Videos Sample marketing collateral Service introduction letter Rack cards/statement stuffers/brochures Web banner, lobby signage, window signage Click Here Click Here Ask your Account Manager for details. Version 1.1 Page 3 of 27

4 C.O.P.S. CONFIGURATION OVERVIEW The C.O.P.S. module is highly configurable to help each financial institution define the experience for themselves and their Clients. A brief overview of each configuration option is summarized below. More details can be find in the C.O.P.S. Special Configuration Options portion of this guide. Product Name End of Day Alert Methods Alert Content Undeliverable Alerts The default product name is C.O.P.S., however, FIs that elect to brand the application can define their own product name to appear as the module name in the FI & Client portals. Each FI can specify a daily cut-off time/zone for C.O.P.S. to apply the default setting (approve or reject) to any ACH batch still in a pending status. and SMS text alerting are available. FIs may choose to allow one or both. The FI can specify the From and Reply To content of the alerts. FIs can specify where they want undelivered alerts to be sent to within their organization. DEPLOYMENT TYPE Active Control ACH Alert API Fiserv PEP+ API Pipe Delimited When active control is set to YES, C.O.P.S. will accept ACH files and build ACH output files, minus any rejected batches once every batch in the file has been resolved. If set to NO, files can be loaded for status purposes, but output files will NOT be created. FIs and/or vendor partners can leverage C.O.P.S. API to send transactions within a batch for evaluation and receive batch status updates such as approved, rejected or pending. API details can be found in Exhibit 4: C.O.P.S. API Documentation FIs using PEP+ can leverage the API integration available between C.O.P.S. and PEP+. Contact an ACH Alert representative to setup a conference call with the appropriate Fiserv representative. By default, C.O.P.S. accepts NACHA formatted files, however, FIs can elect to load data in pipe delimited format as an alternative. CSV specifications can be found in Exhibit 5: C.O.P.S. CSV Format & Sample Output files are NOT created. CSV data is used for status purposes only. SPECIAL DATA HANDLING C.O.P.S. offers a wide array of special configuration options to support how data loaded will be handled. They are as follows: Days to Pend Immediate Release Multiple Release Windows Originator or Batch Level Rejection & Override FIs may choose to defer application of the default setting beyond EOD cut-off time (1, 2 or 3 additional days) to allow originators extended time to act on pending batches. This setting supports continuous processing. As batches within loaded files are resolved, C.O.P.S. builds output files with resolved batches. A single file with multiple batches can result in multiple files being released. FIs can request a maximum of 2 release windows to run prior to EOD. C.O.P.S. will build files with resolved batches at those times. FIs must define a global rule for how to handle batches for an originating Client if a batch is rejected. Reject all batches for that Client (Originator Level) or just the batch rejected (Batch Level). However, FIs may request the ability to override the global setting at the Client level. Issuance Batch Handling FIs can choose to require originators to approve issuance data loaded by the FI before payment recipients are added to their approved list or the FI can load issuance data that immediately adds payment recipients to a Client s approved list. Version 1.1 Page 4 of 27

5 DECISION DEADLINES EOD Days to Pend By default, the system will apply the default setting for the originating Company ID (approve or reject) at EOD, unless days to pend is set to 1, 2 or 3. The options to extend the decision window beyond cut-off time are 1, 2 or 3. Batches that can pend beyond EOD will be released once resolved. Batches that remain in pending status will have the default setting applied at EOD next day (1), EOD two days later (2) or EOD three days later (3). ENHANCED SECURITY FEATURES OTPC Attempts Admin Alerts-Protected Roles FI Protected Roles FIs can specify the number of times an invalid one-time passcode can be entered before a pending batch is locked. The options are 1-3 attempts. Client Admin users (managed by FI) will receive an alert any time a normal client user is granted a protected (manage batches, manage issuance batch) role. If enabled, Client Admin users can set up normal client users, but protected roles must be granted by the FI. ADDITIONAL FEATURES ACH Notify Enable Warehouse By default, C.O.P.S. will only alert enrolled originators when a suspect batch is identified. If this feature is enabled, originators will receive an alert for every batch received by C.O.P.S. The alert will contain transaction and dollar counts for the batch. If enabled, authorized FI users can manage pending batches on behalf of Clients without obtaining their OPTC code and can add payment recipients to an originator s approved list. Reminder Alerts FIs can request that originators with pending batches receive reminder alerts every 15 minutes. FIs must provide ACH Alert with a desired start and end time for alerts. FIs may also specify if reminder alerts will be global or if override is allowed per Client. NOTIFICATION METHODS C.O.P.S. supports (2) two notification methods. SMS Text This section of the guide will outline information important to note about each method. notification capabilities are standard with C.O.P.S. The Notification Delivery Report in the FI portal provides information for undeliverable s. notifications can be customized, inserting the FIs name as outlined in Exhibit 2: C.O.P.S. Branding Message. Version 1.1 Page 5 of 27

6 SMS TEXT SMS text notifications are an option and are highly recommended for alerting originators of exceptions. FIs must decide during implementation if this is a notification method they want to utilize. There is an additional charge for each SMS text message. ACH Alert s agreement with the SMS gateway provider requires a pass-through agreement. This requirement from the carrier can be found in the ACH Alert Master Services Agreement executed when signing up for the service with ACH Alert. When setting up Client users, the cell phone field MUST be populated, however, the Alert method drop down allows the option to select or not select SMS text as an alert option. Be sure to request permission (opt-in) from a user before selecting SMS text as an alert option and provide the user with information on how to request the SMS text option to be removed (opt-out). ACH Alert currently uses a shared short code for SMS text delivery. This is the number that will be displayed as the sender of a text message. The short code being displayed today is: NOTE: If the Client has ever opted out of receiving SMS text messages from another company that shares this short code, SMS text messages will not be delivered to the Client. ACH Alert reserves the right to change the short code without notice. The Notification Delivery Report within the FI portal will display any undelivered SMS text messages. Version 1.1 Page 6 of 27

7 C.O.P.S. DEPLOYMENT & DATA HANDLING OPTIONS The diagrams below are intended to aid FIs in visualizing the deployment and data handling options available. ACTIVE CONTROL=YES IMMEDIATE RELEASE=NO FIIT can be provided by ACH Alert to FIs that want to securely deliver origination files (encrypted via SFTP) to C.O.P.S. as outlined in Appendix C: FIIT Implementation & Operational Guide and User Guide. Files loaded will be released when every batch in the file has been resolved. Version 1.1 Page 7 of 27

8 EXAMPLE: A file is loaded at 1:00 p.m. with 4 batches with a cut-off time at 5:00 p.m. At load: batch 1 contains debits only batch 2 is for a company that is not enrolled (non-subscriber) batch 3 & 4 have suspect transactions that result in a pending status. At 1:30 p.m. the originator of batch 3 approves the batch. At 2:30 p.m. the originator of batch 4 rejects the batch. Although EOD is not scheduled to run until 5:00 p.m., FIIT connects to the C.O.P.S. host to pull down the fully resolved file (with 3 batches only, the rejected batch is removed) by 2:40 p.m. NOTE: If the originator of batch 3 or 4 took no action by EOD, the file would not be available until after 5:00 p.m. when the default setting is applied. Version 1.1 Page 8 of 27

9 ACTIVE CONTROL=YES IMMEDIATE RELEASE=YES Version 1.1 Page 9 of 27

10 EXAMPLE: A file is loaded at 1:00 p.m. with 4 batches with a cut-off time at 5:00 p.m. At load Batch 1 contains debits only Batch 2 is for a company that is not enrolled (non-subscriber) Batch 3 & 4 have suspect transactions that result in a pending status. At 1:30 p.m. the originator of batch 3 approves the batch. At 2:30 p.m. the originator of batch 4 rejects the batch. Although EOD is not scheduled to run until 5:00 p.m., FIIT connects to the C.O.P.S. host to pull down a P1 file by 1:10 p.m. that contains batch 1 & 2 FIIT connects to the C.O.P.S. host to pull down a P2 file by at 1:40 to pull down batch 3. Batch 4 is released back to FIIT as the c file to indicate the original input file resolution is complete, however, there is only a file header and control record with no content, so FIs generally never process the C file. NOTE: If the originator of batch 4 took no action by EOD, the batch would not be available until after 5:00 p.m. when the default setting is applied. Version 1.1 Page 10 of 27

11 ACTIVE CONTROL=YES MULTIPLE RELEASE WINDOWS=YES Version 1.1 Page 11 of 27

12 EXAMPLE: EOD cut-off is set for 4:00 p.m. but 2 earlier release windows are set for 2:00 and 3:00 p.m. File is loaded at 1:00 p.m. with 5 batches. Batch 1 contains debits only Batch 2 is for a company that is not enrolled (non-subscriber) Batch 3, 4 & 5 have suspect transactions that result in a pending status. At 1:30 p.m. the originator of batch 3 approves the batch. By 2:10 p.m. FIIT has connected to the C.O.P.S. host to pull down a file with 3 batches. Batch 4 is still pending. At 2:45 the originator of batch 4 approves the batch. By 3:10 p.m. FIIT has connected to the C.O.P.S. host to pull down a file with 1 batch. The originator of batch 5 takes no action on the pending batch, the default setting is approved. At EOD (4:00 p.m.) batch 5 is released and pulled down by FIIT no later than 5:10 p.m. NOTE: If the originator of batch 5 took no action by EOD and the default setting was reject, a C file (empty file with file header and control record) would be available by 4:10 p.m. in FIIT. Version 1.1 Page 12 of 27

13 ACTIVE CONTROL=NO API=YES In the diagram above, the scenario depicts an API call to C.O.P.S. from an online banking system when a batch is originated. FIIT is NOT used in this scenario, data and status values are exchanged by systems via API. Version 1.1 Page 13 of 27

14 C.O.P.S. DATA FORMATS An ACH formatted file is ACH Alert s standard for loading originated ACH transactions into C.O.P.S. C.O.P.S. standard end-of-day (EOD) output files are NACHA formatted ACH Files. ACH Alert also supports receipt of data in CSV format or via API. C.O.P.S. DAILY ACH INPUT FILES FIIT will accept and deliver an ACH formatted file to be delivered to ACH Alert s MFT server. FIs building an ACH file for Direct Send (not using FIIT) must deliver a complete and properly formatted ACH file to ACH Alert with some record terminator. The file name MUST be unique and the extension MUST be.ach. <Unique File Name><Date Time: YYMMDDHH24MI><File Modifier>.ach Example: Transaction File name = UniqueName170115A.ach Direct Send FIs must upload the file to the following folder: /cops/upload/ach_files NOTE: Direct Send FIs that choose to encrypt the file should follow the standard file naming convention plus the extension of.pgp. Version 1.1 Page 14 of 27

15 DUPLICATE FILE DETECTION C.O.P.S. will flag files as duplicate that have the same file name, date/time stamp and modifier ID in the file header record. It is possible to load a file with the same name if the date/time, modifier ID is different, but it is NOT recommended. EOD-CUT-OFF TIME FIs determine the daily EOD time so batches in pending status can be systematically handled at that time. The EOD time can be specified in hours, minutes and time zone. The EOD time is sometimes referred to as the cut-off time. Files loaded before the daily cut-off time generate EOD files the same day. Files loaded after cut-off time generate EOD files the next business day. DAYS TO PEND HANDLING By default, C.O.P.S. will apply the system default to all pending batches at EOD/cut-off time, however FIs can choose to extend the decision time past EOD/cut-off time with the days to pend configuration setting. The maximum number of days to pend a batch is 3 Days to Pend=1 Days to Pend=2 Days to Pend=3 Files loaded before EOD today with suspect batches (Active Control-Y/Immediate Release N) or suspect batches (Active Control Y/Immediate Release Y or Multiple Release Windows Y) will remain in C.O.P.S. until EOD tomorrow if originating Client takes no action. At that time, the default setting for that originating company ID will be applied. Files loaded before EOD today with suspect batches (Active Control-Y/Immediate Release N) or suspect batches (Active Control Y/Immediate Release Y or Multiple Release Windows Y) will remain in C.O.P.S. until EOD day after tomorrow if originating Client takes no action. At that time, the default setting for that originating company ID will be applied. Files loaded before EOD today with suspect batches (Active Control-Y/Immediate Release N) or suspect batches (Active Control Y/Immediate Release Y or Multiple Release Windows Y) will remain in C.O.P.S. until EOD the third day if originating Client takes no action. At that time, the default setting for that originating company ID will be applied. HOLIDAYS & WEEKENDS C.O.P.S. EOD releases will only occur on a business banking day. C.O.P.S. does NOT release files on banking holidays or weekends. By default, the Fed holiday calendar is observed. ACH Alert does offer FIs the ability to customize their annual holiday calendar. Custom holiday calendar request must be made via the Helpdesk no later than December 1 each calendar year. Professional services fees will apply. INPUT FILE CONFIRMATION When an input file is received by C.O.P.S., an confirmation is NOT sent to the FI unless the file is deemed invalid. FIs can view ACH file status through the FI portal. See FI C.O.P.S. user documentation for more details. Version 1.1 Page 15 of 27

16 C.O.P.S. OUTPUT FILES C.O.P.S. systematically creates NACHA formatted ACH output files when Active Control=Y. When files are created, the output naming convention varies depending on the deployment type and/or data handling configuration options elected by the FI. It is important to note that EOD in C.O.P.S. is simply the time of day that the system applies the default setting for batches that are in the system still in pending status. As a rule, (Active Control=Y Immediate Release=N) C.O.P.S. will create an EOD file/files for every input file, using the same name as the input file, even though the content in the file could be different. For instance, a file with 4 batches is loaded, 3 batches are eligible for release and 1 batch is rejected at EOD, C.O.P.S. will release the file using the same file name as loaded, but the file will contain only 3 batches and the 9 record will be different than the input file. <Original Name>.ach Example: Input File name = A.dat Output File name = A.ach When special data handling configurations are used that result in multiple output files for one input file (Active Control=Y Immediate Release=Y or Multiple Release Windows=Y), C.O.P.S. will append the file name with a P (for partial) and a number (1, 2, 3, file number) in front of the file name. When the last batch is resolved (approved or rejected) a c.file is released to indicate the input file has been completely resolved. If the last batch in the file is rejected, a c.file is released but it will have only a header and control record with no content. FIIT will monitor the C.O.P.S. host every 10 minutes to pick up output files available. Direct Send FIs must downloaded from the following folder: /cops/download/ach_files NOTE: FIs that choose file encryption should expect files to contain the standard naming convention plus the extension.pgp Version 1.1 Page 16 of 27

17 P FILE A P file is only applicable if an FI is using Immediate Release or Multiple Release Window configuration options. The P file is built by C.O.P.S. in ACH format (system builds the header and control record) to allow financial institutions to process batches as they have been resolved. More than one P file can be created when batches from an input file are resolved more than 5 minutes apart. If a second P file is applicable, the file will be named P2, if a third file is applicable P3 etc. FILE NAMING CONVENTION <Original Name>.ach Example: Input File name = A.dat Output P File name = P A.ach C FILE A C file is only applicable if an FI is using Immediate Release or Multiple Release Window configuration options. The C file is built by C.O.P.S. in ACH format to allow financial institutions to know when the last batch of an input file has been resolved. Only one C file will be created per input file. If the last batch resolved was approved, the C file will contain batch information, if the last batch resolved was rejected, the C file will contain only a header and control record. FILE NAMING CONVENTION <Original Name>.ach Example: Input File name = A.dat Output C File name = C A.ach Version 1.1 Page 17 of 27

18 C.O.P.S. CUSTOM FILE EXCHANGE OPTIONS ACH Alert offers several other file input and data exchange methods. They are: Pipe delimited format C.O.P.S. API Fiserv PEP+ API This section of the guide will outline the purpose of each file type, content, and format. PIPE DELIMITED FORMAT FIs who are unable to load a properly formatted ACH file into C.O.P.S. (often because online banking systems feed an ACH warehouse directly) can leverage the pipe delimited capabilities of C.O.P.S. by extracting data from an ACH warehouse to load into C.O.P.S. for evaluation. C.O.P.S. will assign a load status and display a status in the FI and Client portals, but C.O.P.S. will NOT release an EOD Pipe delimited file. FIs must use C.O.P.S. status information to determine if any batches should be handled within their ACH warehouse system before release. The pipe delimited file specifications and a sample can be found as Exhibit 5: C.O.P.S. CSV Format & Sample. FILE NAMING CONVENTION <Original Name>.csv Example: Input File name = A.csv Output File = Not applicable C.O.P.S. API FIs and/or their vendors can interface with C.O.P.S. to exchange information via an API in lieu of loading files. Transactions submitted via the API are analyzed by C.O.P.S. and status information is exchanged at initial evaluation and as status information is updated. C.O.P.S. API specifications are attached as Exhibit 4: C.O.P.S. API Documentation. FISERV PEP+ API ACH Alert has developed an API with Fiserv s PEP+ system. FIs interested in obtaining more information must contact their ACH Alert and Fiserv representatives to coordinate a discussion. Version 1.1 Page 18 of 27

19 C.O.P.S. IMPORT DATA FILES ACH Alert offers FIs the ability to automate the setup of Client information as an alternative to manually keying the data into the C.O.P.S. FI portal. The following data sets can be imported using the specifications provided in this section of the guide. Companies Payment Recipients (Approved List) Enhanced import capabilities are available upon receipt of a Change Request. They include: Alert Method Client Users Company ID Mapping Client Users Access Rights FIs must deliver all import information in the format defined below. Exhibit 3: C.O.P.S. Import Template is an excel document that can be used to create these files. Version 1.1 Page 19 of 27

20 CLIENT CONFIGURATION File Format Delimited Flat File Record Delimiter Pipe Null Record Indicator Blank record (nothing between pipes) File Name COPS_ClientConfiguration.dat Column Name Data Type Max Digits Required? Description Client Code Character 100 Yes Unique identifier for the Client, and will be used to relate companies to a Client. Receive Reminder Character 1 Yes Y= Yes N= No Rejection Level (Override) Character 1 Yes B= Batch O= Originator Version 1.1 Page 20 of 27

21 COMPANIES File Format Delimited Flat File Record Delimiter Pipe Null Record Indicator Blank record (nothing between pipes) File Name COPS_CompaniesLoad.dat Column Name Data Type Max Digits Required? Description Client Code Character 100 Yes Unique identifier for the Client, and will be used to relate company ID's to a Client. Company ID # Character 10 Yes Unique identifier for the originating entity. If category Id's are used, this data does not have to be unique but category ID must be unique. Company Name Character 16 Yes Name of originating entity. Category ID Character 50 No Unique identifier used only with ProfitStars FIs using ACH Client. Bank Code Character 8 No Billing Routing # Character 9 See Required only if FI uses more than one routing Description number. Billing Account # Character 17 Yes Account # used for Company ID level billing items. Use C.O.P.S. Service Character 1 Yes Y= Yes N= No Default Setting (Action) Character 1 Yes A= Approve R = Reject ACH Notify Service Character 1 Yes Y= Yes N= No Version 1.1 Page 21 of 27

22 PAYMENT RECIPIENTS (APPROVED LIST) File Format Delimited Flat File Record Delimiter Pipe Null Record Indicator Blank record (nothing between pipes) File Name COPS_AppListLoad.dat Column Name Data Type Max Digits Required? Description Client Code Character 100 Yes Unique Identifier for the Client, and will be used to relate payment recipients to a Client. Company ID Character 10 Yes Unique identifier for the Company ID and will be used to relate payment recipients to a Company ID. Category ID Character 50 No Unique identifier for the Category ID and will be used to relate payment recipients to a Category ID. Individual Name Character 22 Yes Name to identify payee. Only one payee per record. If wishing to apply this approved list entry to multiple Company IDs or Category IDs, repeat the line with a different Company ID Routing # Character 9 Yes Used to identify bank where the payee s account resides. Only one routing # per record. If wishing to apply this approved list entry to multiple Company IDs or Category IDs, repeat the line with a different Company ID Account # Character 17 Yes Used to identify the payee s account number. Only one account number per record. If wishing to apply this Approved List entry to multiple Company IDs, repeat the line with a different Company ID. Version 1.1 Page 22 of 27

23 C.O.P.S. USER COMPANY ID MAPPING File Format Delimited Flat File Record Delimiter Pipe Null Record Indicator Blank record (nothing between pipes) File Name COPS_ CoIDMapping.dat Column Name Data Type Max Digits Required? Description Client Code Character 100 Yes Unique identifier for the Client, and will be used to relate companies to a Client. Company ID # Character 10 Yes Company ID # that the user is authorized to interact with. Category ID # Character 50 No Category ID # that the user is authorized to interact with. Used only with ProfitStars FIs using ACH Client. User Name Character 30 Yes if Standard Security SSO ID Character 50 Yes if SSO Alert Method Character 1 Yes E= S= SMS Text B= Both & SMS Text NOTE: There will be one record per company ID per user. Version 1.1 Page 23 of 27

24 C.O.P.S. USER ACCESS RIGHTS File Format Delimited Flat File Record Delimiter Pipe Null Record Indicator Blank record (nothing between pipes) File Name COPS_ ClientUserAccessRights.dat Column Name Data Type Max Digits Required? Description Client Code Character 100 Yes Unique identifier for the Client, and will be used to relate companies to a Client. User Name Character 30 Yes if Standard Security SSO ID Character 50 Yes if SSO Access Right: Manage Batches Character 1 Yes Y = Yes N = No Access Right: Approve Issuance File Character 1 Yes Y = Yes N = No Access Right: Approved List Character 1 Yes Y = Yes N = No Version 1.1 Page 24 of 27

25 Chapter 2: TRAINING ACH Alert s project manager can provide an agenda for each type of training. An example of the training services provided is outlined below. C.O.P.S. TRAINING AGENDA GENERAL Discuss purpose of C.O.P.S. Discuss how C.O.P.S. will integrate into process flow Review User Documentation for FI & Clients PROCESS FLOW C.O.P.S. compares every outgoing ACH credit to list of approved payment recipients. Exceptions trigger an ALERT to the Client, requiring action to: Reject the batch Approve the batch, and/or Add Payment Recipients to the Approved List for all future ACH credits Client User FI User Performed As Task Manage>Batches Manage>Issuance File Manage>Approved List Manage>Companies Manage>Batches Reports>Approved List View>Warehouse (if configured) Files>Load Issuance Files>ACH File Status Files>ACH Issuance File Status Version 1.1 Page 25 of 27

26 Chapter 3: APPENDIX Appendix A: C.O.P.S. Client User Guide Appendix B: C.O.P.S. FI User Guide Appendix C: FIIT Implementation & Operational Guide and User Guide Appendix D: FIIT Installation Appendix E: FIIT Installing Java 8 and the Cryptographic Extensions Click Here Click Here Click Here Click Here Click Here Version 1.1 Page 26 of 27

27 Chapter 4: EXHIBITS Exhibit 1: C.O.P.S. Implementation Questionnaire Exhibit 2: C.O.P.S. Branding Message Questionnaire Exhibit 3: C.O.P.S. Import Template Exhibit 4: C.O.P.S. API Documentation Exhibit 5: C.O.P.S. CSV Format & Sample Exhibit 6: C.O.P.S. Video Questionnaire Click Here Click Here Click Here Click Here Click Here Click Here Version 1.1 Page 27 of 27