DOCSLIB.ORG

Worldwide Investments in CLUSTER MUNITIONS a Shared Responsibility

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Worldwide Investments in CLUSTER MUNITIONS a Shared Responsibility November 2014 update Worldwide investments in CLUSTER MUNITIONS a shared responsibility November 2014 Utrecht, November 2014 PAX has strived to achieve the highest level of accuracy in our reporting. However, at this point, there is still a marked lack of official information available in the public domain about the use, production, transfer, and stockpiling of cluster munitions, as well as about investments in companies that produce cluster munitions. The information in this report therefore reflects official information available in the public domain known to PAX. We welcome comments, clarifications, and corrections from governments, companies, financial institutions and others, in the spirit of dialogue, and in the common search for accurate and reliable information on an important subject. If you believe you have found an inaccuracy in our report or if you can provide additional information, please contact us. Authors Roos Boer (PAX) Anne Cukier (Profundo) Anniek Herder (Profundo) Suzanne Oosterwijk (PAX) Michel Riemersma (Profundo) Research by Roos Boer (PAX) Anne Cukier (Profundo) Anniek Herder (Profundo) Barbara Kuepper (Profundo) Suzanne Oosterwijk (PAX) Michel Riemersma (Profundo) Frank Slijper (PAX) Joeri de Wilde (Profundo) With thanks to Werner Anderson, Laura Boillot, Stan Brabant, Ningyu Cao, Cyrielle Chibaeff, Michelle Fahy, Eva Maria Fisher, Jan Willem van Gelder, Camille Gosselin, Paul Hannon, Barbara Happe, Katherine Harrison, Mark Hiznay, Erin Hunt, Ole Kirkelund, Thomas Küchenmeister, Martin Lagneau, Marion Libertucci, Amy Little, Richard MacCormac, Gro Nystuen, Lucy Pinches, Giuseppe Schiavello, Christophe Schreire, Petra Schroeter, Sigrid Rausing Trust, Susi Snyder, Miriam Struyk, Stijn Suijs, Lorel Thomas, Junko Utsumi, Esther Vanderbroucke, Hildegarde Vansintjan, Mary Wareham, Luc Weyn, Wilbert van der Zeijden, and all the representatives of the financial institutions who provided answers to our questions about their policy. Editor Isobel Mackie A publication by PAX, the Netherlands Lay out Studio het Mes, the Hague Cover photograph Germany, 15 October 2008 DM1348/155 mm artillery delivered cluster munitions. © Werner Anderson www.werneranderson.no For additional information please contact [email protected]. PAX (formerly IKV Pax Christi, the Netherlands) and FairFin (formerly Netwerk Vlaanderen, Belgium) published the first report on “Worldwide Investments in Cluster Munitions: a Shared Responsibility” in October 2009. It was a state - of - the - art report on financial institutions’ investment in companies that develop or produce cluster munitions, on financial institutions disinvesting from producers of cluster munitions and on states banning investments in cluster munitions. Updates of the report appeared in April 2010, May 2011, June 2012 and December 2013. This edition by PAX, dated November 2014, updates the earlier reports. 1 STATE - OF - THE - ART REPORT Contents Executive Summary, Recommendations and Methodology 8 Summary Tables 19 Introduction 30 Investing in Cluster Munitions: What’s at Stake? 30 Cluster Munitions and the Oslo Process 30 Financial Institutions’ Power and Responsibility 31 Our Research 32 Chapter 1 Hall of Shame: Financial Involvement and Investments 33 1.1 Red Flag List of Cluster Munitions Producers 33 1.1.0 Introduction and Methodology 33 1.1.1 ATK (United States) 35 1.1.2 China Aerospace Science and Technology (China) 36 1.1.3 Hanwha (South Korea) 36 1.1.4 Norinco (China) 38 1.1.5 Poongsan (South Korea) 38 1.1.6 Singapore Technologies Engineering (Singapore) 39 1.1.7 Textron (United States) 39 1.2 The Investments 42 1.2.0 Introduction and Methodology 42 1.2.1 Aberdeen Asset Management (United Kingdom) 44 1.2.2 Affiliated Managers Group (United States) 44 1.2.3 Aflac (United States) 44 1.2.4 Agricultural Bank of China (China) 45 1.2.5 AJO (United States) 45 1.2.6 Allianz (Germany) 45 1.2.7 Allstate Corporation (United States) 46 1.2.8 Amalgamated Bank of Chicago (United States) 46 1.2.9 American Beacon Advisors (United States) 46 1.2.10 American International Group (United States) 46 1.2.11 American United Mutual Insurance (United States) 47 1.2.12 Ameriprise Financial (United States) 47 1.2.13 APS Asset Management (Singapore) 47 1.2.14 Arovid Associates (United States) 47 1.2.15 Associated Banc-Corp (United States) 48 1.2.16 Banco de Sabadell (Spain) 48 1.2.17 BancPlus (United States) 48 1.2.18 Bank Hapoalim (Israel) 48 1.2.19 Bank of America (United States) 48 1.2.20 Bank of Beijing (China) 49 1.2.21 Bank of China (China) 50 1.2.22 Bank of Communications (China) 50 1.2.23 Bank of East Asia (China) 51 1.2.24 Bank of New York Mellon (United States) 51 2 1.2.25 Banner Bank (United States) 52 1.2.26 BB&T (United States) 52 1.2.27 BlackRock (United States) 52 1.2.28 California First National Bancorp (United States) 52 1.2.29 Capital Group (United States) 53 1.2.30 Carlyle Group (United States) 53 1.2.31 Cascade Bancorp (United States) 53 1.2.32 Causeway Capital Management (United States) 53 1.2.33 Central Pacific Financial Corporation (United States) 54 1.2.34 Cheonanbukil Foundation School (South Korea) 54 1.2.35 China Construction Bank (China) 54 1.2.36 China Development Bank (China) 54 1.2.37 China Everbright Group (China) 55 1.2.38 China Life Insurance (China) 55 1.2.39 China Merchants Bank (China) 55 1.2.40 China Minsheng Bank (China) 56 1.2.41 China Securities (China) 56 1.2.42 CITIC Group (China) 56 1.2.43 Citigroup (United States) 57 1.2.44 CNO Financial (United States) 57 1.2.45 Comerica (United States) 58 1.2.46 Consus Asset Management (South Korea) 58 1.2.47 Crédit Mutuel (France) 58 1.2.48 Credit Suisse (Switzerland) 58 1.2.49 Daewoo Securities (South Korea) 59 1.2.50 Davis Advisors (United States) 59 1.2.51 DBS (Singapore) 59 1.2.52 Deutsche Bank (Germany) 59 1.2.53 Dimensional Fund Advisors (United States) 60 1.2.54 Discovery Capital Management (United States) 60 1.2.55 Dongbu Group (South Korea) 60 1.2.56 E.SUN Financial (Taiwan) 60 1.2.57 Eastern Bank (United States) 61 1.2.58 Eaton Vance (United States) 61 1.2.59 Eugene Investment & Securities (South Korea) 61 1.2.60 Fidelity Investments (United States) 62 1.2.61 Fidelity Worldwide Investment (United Kingdom) 62 1.2.62 Fifth Third Bancorp (United States) 62 1.2.63 First Eagle Investment Management (United States) 63 1.2.64 First Niagara Financial (United States) 63 1.2.65 Fubon Group (Taiwan) 63 1.2.66 Gamco Investors (United States) 63 1.2.67 Genworth Financial (United States) 63 1.2.68 Goldman Sachs (United States) 64 1.2.69 Grantham, Mayo, Van Otterloo & Co. (GMO) (United States) 64 1.2.70 Groupe BPCE (France) 65 1.2.71 Guotai Junan Securities (China) 65 1.2.72 Haitong Securities (China) 65 1.2.73 Hana Financial (South Korea) 65 1.2.74 Hanwha Group (South Korea) 66 1.2.75 Hanyang Securities (South Korea) 67 1.2.76 Hartford Financial Services (United States) 67 1.2.77 Hong Yuan Securities (China) 67 3 1.2.78 Hua Nan Financial (Taiwan) 67 1.2.79 Hyundai Group (South Korea) 67 1.2.80 Hyundai Heavy Industries (South Korea) 68 1.2.81 Industrial Bank (China) 68 1.2.82 Industrial & Commercial Bank of China (ICBC) (China) 68 1.2.83 Invesco (United Kingdom) 69 1.2.84 JP Morgan Chase (United States) 69 1.2.85 KB Financial (South Korea) 70 1.2.86 KDB Financial Group (South Korea) 71 1.2.87 Keycorp (United States) 72 1.2.88 Knights of Columbus (United States) 72 1.2.89 Korea Investment Holdings (South Korea) 72 1.2.90 Land Bank of Taiwan (Taiwan) 73 1.2.91 LSV Asset Management (United States) 73 1.2.92 Macquarie Group (Australia) 73 1.2.93 MassMutual Financial (United States) 74 1.2.94 Matthews International Capital Management (United States) 74 1.2.95 MetLife (United States) 74 1.2.96 Mirae Asset Financial Group (South Korea) 75 1.2.97 Mitsubishi UFJ Financial (Japan) 75 1.2.98 Mizuho Financial (Japan) 76 1.2.99 Morgan Stanley (United States) 76 1.2.100 National Pension Service (South Korea) 76 1.2.101 Nationwide (United States) 77 1.2.102 Neuberger Berman (United States) 77 1.2.103 New York Life Insurance Company (United States) 77 1.2.104 Northern Trust (United States) 77 1.2.105 Old Mutual (United Kingdom) 78 1.2.106 Oversea-Chinese Banking Corporation (Singapore) 78 1.2.107 People’s Insurance Company (Group) of China (PICC) (China) 78 1.2.108 People’s United Financial (United States) 78 1.2.109 PNC Financial (United States) 79 1.2.110 Point72 Asset Management (United States) 79 1.2.111 Prudential (United Kingdom) 80 1.2.112 Prudential Financial (United States) 80 1.2.113 Raymond James Financial (United States) 80 1.2.114 Regions Financial (United States) 80 1.2.115 Royal Bank of Canada (Canada) 81 1.2.116 Samsung Group (South Korea) 81 1.2.117 Schroders (United Kingdom) 81 1.2.118 Sealand Securities (China) 82 1.2.119 Shenyin & Wanguo Securities (China) 82 1.2.120 Shinhan Financial Group (South Korea) 82 1.2.121 Shinyoung Asset Management (South Korea) 83 1.2.122 Siemens Financial Services (Germany) 83 1.2.123 SK Securities (South Korea) 83 1.2.124 Standard Life (United Kingdom) 84 1.2.125 State Bank of India (India) 84 1.2.126 State Street (United States) 84 1.2.127 Stifel Financial (United States) 84 1.2.128 Sumitomo Mitsui Financial Group (Japan) 85 1.2.129 Sun Life Financial (Canada) 85 1.2.130 SunTrust Bank (United States) 86 4 1.2.131 Synovus Financial Corporation (United States) 86 1.2.132 T.
Load more

Recommended publications
  • NOAA Technical Report NOS NGS 60
    NOAA Technical Report NOS NGS 60 NAD83 (NSR2007) National Readjustment Final Report Dale G. Pursell Mike Potterfield Rockville, MD August 2008 NOAA Technical Report NOS NGS 60 NAD 83(NSRS2007) National Readjustment Final Report Dale G. Pursell Mike Potterfield Silver Spring, MD August 2008 U.S. DEPARTMENT OF COMMERCE National Oceanic and Atmospheric Administration National Ocean Service Contents Overview ........................................................................................................................ 1 Part I. Background .................................................................................................... 5 1. North American Datum of 1983 (1986) .......................................................................... 5 2. High Accuracy Reference Networks (HARNs) .............................................................. 5 3. Continuously Operating Reference Stations (CORS) .................................................... 7 4. Federal Base Networks (FBNs) ...................................................................................... 8 5. National Readjustment .................................................................................................... 9 Part II. Data Inventory, Assessment and Input ....................................... 11 6. Preliminary GPS Project Analysis ................................................................................11 7. Master File .....................................................................................................................11
    [Show full text]
  • A Longitudinal and Cross-Dataset Study of Internet Latency and Path Stability
    A Longitudinal and Cross-Dataset Study of Internet Latency and Path Stability Mosharaf Chowdhury Rachit Agarwal Vyas Sekar Ion Stoica Electrical Engineering and Computer Sciences University of California at Berkeley Technical Report No. UCB/EECS-2014-172 http://www.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-172.html October 11, 2014 Copyright © 2014, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. A Longitudinal and Cross-Dataset Study of Internet Latency and Path Stability Mosharaf Chowdhury Rachit Agarwal Vyas Sekar Ion Stoica UC Berkeley UC Berkeley Carnegie Mellon University UC Berkeley ABSTRACT Even though our work does not provide new active mea- We present a retrospective and longitudinal study of Internet surement techniques or new datasets, we believe that there is value in this retrospective analysis on several fronts. First, it latency and path stability using three large-scale traceroute provides a historical and longitudinal perspective of Internet datasets collected over several years: Ark and iPlane from path properties that are surprisingly lacking in the measure- 2008 to 2013 and a proprietary CDN’s traceroute dataset spanning 2012 and 2013. Using these different “lenses”, we ment community today. Second, it can help us revisit and revisit classical properties of Internet paths such as end-to- reappraise classical assumptions about path latency and sta- end latency, stability, and of routing graph structure.
    [Show full text]
  • Misleading Stars: What Cannot Be Measured in the Internet?
    Noname manuscript No. (will be inserted by the editor) Misleading Stars: What Cannot Be Measured in the Internet? Yvonne-Anne Pignolet · Stefan Schmid · Gilles Tredan Abstract Traceroute measurements are one of the main in- set can help to determine global properties such as the con- struments to shed light onto the structure and properties of nectivity. today’s complex networks such as the Internet. This arti- cle studies the feasibility and infeasibility of inferring the network topology given traceroute data from a worst-case 1 Introduction perspective, i.e., without any probabilistic assumptions on, e.g., the nodes’ degree distribution. We attend to a scenario Surprisingly little is known about the structure of many im- where some of the routers are anonymous, and propose two portant complex networks such as the Internet. One reason fundamental axioms that model two basic assumptions on is the inherent difficulty of performing accurate, large-scale the traceroute data: (1) each trace corresponds to a real path and preferably synchronous measurements from a large in the network, and (2) the routing paths are at most a factor number of different vantage points. Another reason are pri- 1/α off the shortest paths, for some parameter α 2 (0; 1]. vacy and information hiding issues: for example, network In contrast to existing literature that focuses on the cardi- providers may seek to hide the details of their infrastructure nality of the set of (often only minimal) inferrable topolo- to avoid tailored attacks. gies, we argue that a large number of possible topologies Knowledge of the network characteristics is crucial for alone is often unproblematic, as long as the networks have many applications as well as for an efficient operation of the a similar structure.
    [Show full text]
  • PAX A920 Mobile Smart Terminal Quick Setup Guide
    PAX A920 QUICK SETUP GUIDE PAX A920 Mobile Smart Terminal Quick Setup Guide 2018000702 v1.8 1 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE PAX A920 Mobile Terminal Intelligence of an ECR in a handheld point of sale. The PAX A920 is an elegantly designed compact secure portable payment terminal powered by an Android operating system. The A920 comes with a large high definition color display. A thermal printer and includes NFC contactless and electronic signature capture. Great battery life for portable use. 2018000702 v1.8 2 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE 1 What’s in The Box The PAX A920 includes the following items in the box. 2018000702 v1.8 3 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE 2 A920 Charging Instructions Before starting the A920 battery should be fully charged by plugging the USB to micro USB cord to a PC or an AC power supply and then plug the other end with the micro USB connector into the micro USB port on the left side of the terminal. Charge the battery until full. Note: There is a protective cover on the new battery terminals that must be removed before charging the battery. See Remove and Replace Battery section. 2018000702 v1.8 4 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE 3 A920 Buttons and Functions Front Description 6 1 2 7 3 8 9 4 5 2018000702 v1.8 5 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE 3.1 A920 Buttons and Functions Front Description 1.
    [Show full text]
  • PAX-It! TM Applications the Paxcam Digital USB 2.0 Camera System
    Digital Imaging Workflow for Industrial From the Makers of PAX-it! TM Applications The PAXcam Digital USB 2.0 Camera System l Affordable camera for microscopy, with an easy-to-use interface l Beautiful, high-resolution images; true color rendition l Fully integrated package with camera and software l USB 2.0 interface for the fastest live digital color preview on the market l Easy-to-use interface for color balance, exposure & contrast control, including focus indicator tool l Adjustable capture resolution settings (true optical resolution -- no interpolation) l Auto exposure, auto white balance and manual color adjustment are supported l Create and apply templates and transparencies over the live image l Acquire images directly into the PAX-it archive for easy workflow l Easy one-cable connection to computer; can also be used on a laptop l Adjustable region of interest means smaller file sizes when capturing images l PAXcam interface can control multiple cameras from the same computer l Stored presets may be used to save all camera settings for repeat conditions Capture Images Directly to PAX-it Image Database Software Includes PAXcam Video Agent for motion video capture l Time lapse image capture l Combine still images to create movie files l Extract individual frames of video clips as bitmap images Live preview up to 40 fps PAX-it! l File & retrieve images in easy-to-use cabinet/folder structure l Store images, video clips, documents, and other standard digital file types l Images and other files are in a searchable database that you
    [Show full text]
  • Freebsd and Netbsd on Small X86 Based Systems
    FreeBSD and NetBSD on Small x86 Based Systems Dr. Adrian Steinmann <[email protected]> Asia BSD Conference in Tokyo, Japan March 17th, 2011 1 Introduction Who am I? • Ph.D. in Mathematical Physics (long time ago) • Webgroup Consulting AG (now) • IT Consulting Open Source, Security, Perl • FreeBSD since version 1.0 (1993) • NetBSD since version 3.0 (2005) • Traveling, Sculpting, Go AsiaBSDCon Tutorial March 17, 2011 in Tokyo, Japan “Installing and Running FreeBSD and NetBSD on Small x86 Based Systems” Dr. Adrian Steinmann <[email protected]> 2 Focus on Installing and Running FreeBSD and NetBSD on Compact Flash Systems (1) Overview of suitable SW for small x86 based systems with compact flash (CF) (2) Live CD / USB dists to try out and bootstrap onto a CF (3) Overview of HW for small x86 systems (4) Installation strategies: what needs special attention when doing installations to CF (5) Building your own custom Install/Maintenance RAMdisk AsiaBSDCon Tutorial March 17, 2011 in Tokyo, Japan “Installing and Running FreeBSD and NetBSD on Small x86 Based Systems” Dr. Adrian Steinmann <[email protected]> 3 FreeBSD for Small HW Many choices! – Too many? • PicoBSD / TinyBSD • miniBSD & m0n0wall • pfSense • FreeBSD livefs, memstick • NanoBSD • STYX. Others: druidbsd, Beastiebox, Cauldron Project, ... AsiaBSDCon Tutorial March 17, 2011 in Tokyo, Japan “Installing and Running FreeBSD and NetBSD on Small x86 Based Systems” Dr. Adrian Steinmann <[email protected]> 4 PicoBSD & miniBSD • PicoBSD (1998): Initial import into src/release/picobsd/ by Andrzej Bialecki <[email protected]
    [Show full text]
  • Parallel MPI I/O in Cube: Design & Implementation
    Parallel MPI I/O in Cube: Design & Implementation Bine Brank A master thesis presented for the degree of M.Sc. Computer Simulation in Science Supervisors: Prof. Dr. Norbert Eicker Dr. Pavel Saviankou Bergische Universit¨atWuppertal in cooperation with Forschungszentrum J¨ulich September, 2018 Erkl¨arung Ich versichere, dass ich die Arbeit selbstst¨andigverfasst und keine anderen als die angegebenen Quellen und Hilfsmittel benutzt sowie Zitate kenntlich gemacht habe. Mit Abgabe der Abschlussarbeit erkenne ich an, dass die Arbeit durch Dritte eingesehen und unter Wahrung urheberrechtlicher Grunds¨atzezi- tiert werden darf. Ferner stimme ich zu, dass die Arbeit durch das Fachgebiet an Dritte zur Einsichtnahme herausgegeben werden darf. Wuppertal, 27.8.2017 Bine Brank 1 Acknowledgements Foremost, I would like to express my deepest and sincere gratitude to Dr. Pavel Saviankou. Not only did he introduce me to this interesting topic, but his way of guiding and supporting me was beyond anything I could ever hoped for. Always happy to discuss ideas and answer any of my questions, he has truly set an example of excellence as a researcher, mentor and a friend. In addition, I would like to thank Prof. Dr. Norbert Eicker for agreeing to supervise my thesis. I am very thankful for all remarks, corrections and help that he provided. I would also like to thank Ilya Zhukov for helping me with the correct in- stallation/configuration of the CP2K software. 2 Contents 1 Introduction 7 2 HPC ecosystem 8 2.1 Origins of HPC . 8 2.2 Parallel programming . 9 2.3 Automatic performance analysis . 10 2.4 Tools .
    [Show full text]
  • Release 0.11.0
    mpiFileUtils Documentation Release 0.11.0 HPC Sep 29, 2021 Contents 1 Overview 1 2 User Guide 3 2.1 Project Design Principles........................................3 2.1.1 Scale..............................................3 2.1.2 Performance...........................................3 2.1.3 Portability............................................3 2.1.4 Composability..........................................4 2.2 Utilities..................................................4 2.3 Experimental Utilities..........................................4 2.4 libmfu..................................................4 2.4.1 libmfu: the mpiFileUtils common library...........................5 2.4.2 mfu_flist.............................................5 2.4.3 mfu_path............................................5 2.4.4 mfu_param_path........................................5 2.4.5 mfu_io..............................................5 2.4.6 mfu_util.............................................6 2.5 Build...................................................6 2.5.1 Build everything with Spack..................................6 2.5.2 Build everything directly....................................6 2.5.3 Build everything directly with DAOS support.........................8 2.5.4 Build mpiFileUtils directly, build its dependencies with Spack................8 3 Man Pages 9 3.1 dbcast...................................................9 3.1.1 SYNOPSIS...........................................9 3.1.2 DESCRIPTION.........................................9 3.1.3 OPTIONS............................................9
    [Show full text]
  • Z/VM Version 7 Release 2
    z/VM Version 7 Release 2 OpenExtensions User's Guide IBM SC24-6299-01 Note: Before you use this information and the product it supports, read the information in “Notices” on page 201. This edition applies to Version 7.2 of IBM z/VM (product number 5741-A09) and to all subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2020-09-08 © Copyright International Business Machines Corporation 1993, 2020. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures................................................................................................................. xi Tables................................................................................................................ xiii About this Document........................................................................................... xv Intended Audience..................................................................................................................................... xv Conventions Used in This Document......................................................................................................... xv Escape Character Notation................................................................................................................... xv Case-Sensitivity.....................................................................................................................................xv Typography............................................................................................................................................xv
    [Show full text]
  • The Emaginepos Guide to Pax / Emv / Broadpos
    THE EMAGINEPOS GUIDE TO PAX / EMV / BROADPOS Author Davis Ford <[email protected]> Last Updated 9/22/2016 THE EMAGINEPOS GUIDE TO PAX / EMV / BROADPOS What Is BroadPOS? Some things you can do with BroadPOS What Processors Are Currently Supported? How To Login To BroadPOS Support Checklist Step -1: Things Specific To Processors Tokenization (attach credit card): Batch Out Step 0: Get One Or More VAR Sheets for the Merchant Step 1: Create a New Merchant (if necessary) Step 2: Add the Serial Numbers of the New Terminal(s) Step 3: Create A New Template TSYS Parameters TSYS Tab => Merchant Parameters TSYS Tab => Host Feature First Data Omaha Parameters First Data Omaha Tab => Host Features, Host URLs First Data Rapid Connect Parameters FirstData RapidConnect Tab => Host Features FirstData RapidConnect Tab => Host URLs Heartland Portico Parameters Hsptc Tab => Host Features Hsptc Tab => Merchant Parameters Hsptc Tab => Host URLs Hsptc Tab => Dial Parameters Misc Tab => Communication Tab => General Communication Tab => LAN Communication Tab => Communication between ECR/POS and PAX terminal Communication => POS System Feature (Ethernet Only) Step 4: Deploy The Template Step 5: Install the Browser Extension for Emagine Payments Step 6: Setup Payment Terminals in the Backoffice Step 7: Create New Payment Type for EMV (if necessary) Step 8: Test The Terminal Frequently Asked Questions / Troubleshooting PAX Frequently Asked Questions List CONNECT ERROR when I try to execute a transaction SWIPE ONLY error when I try to Void or Adjust NOTES on First
    [Show full text]
  • An Airborne Network Telemetry Link for the Inet Technical Demonstration System
    An Airborne Network Telemetry Link for the iNET Technical Demonstration System Item Type text; Proceedings Authors Temple, Kip; Laird, Daniel Publisher International Foundation for Telemetering Journal International Telemetering Conference Proceedings Rights Copyright © held by the author; distribution rights International Foundation for Telemetering Download date 25/09/2021 05:15:29 Link to Item http://hdl.handle.net/10150/606170 AN AIRBORNE NETWORK TELEMETRY LINK FOR THE INET TECHNICAL DEMONSTRATION SYSTEM Kip Temple Air Force Flight Test Center, Edwards AFB CA Daniel Laird Air Force Flight Test Center, Edwards AFB CA ABSTRACT A previous paper was presented [1] detailing the design and testing of the first networked demonstration system (ITC 2006) for iNET. This paper extends that work by testing a commercial off the shelf (COTS) solution for the wireless network connection of the Telemetry Network System (TmNS). This paper will briefly discuss specific pieces of the airborne and ground station system but will concentrate on the new wireless network link, how it was tested, and how well it performed. Flight testing results will be presented accessing the performance of the wireless network link. KEY WORDS integrated Networked Enhanced Telemetry (iNET), wireless network link, Telemetry Network System (TmNS), serial streaming telemetry INTRODUCTION The iNET Team has assembled a Demonstration System to not only assess COTS wireless network link performance within the aeronautical test environment but also to demonstrate the potential uses of a network linked system. The TmNS is shown pictorially in Figure 1. The four components are the vehicular network, or the Test Article Segment (TAS), the interface to the ground station, or Ground Station Segment (GSS), the wireless network link that ties the two networks together, and the legacy serial streaming telemetry (SST) link.
    [Show full text]
  • LDM7 Deployment Guidance
    LDM­7 Deployment Guidance Steve Emmerson, University Corporation for Atmospheric Research ([email protected]) ​ ​ Malathi Veeraraghavan, University of Virginia ([email protected]) ​ ​ Multicast network test To install LDM­7, you will need a Linux/Unix machine and a copy of the LDM­7 software package. Also, you need to make sure the network that LDM­7 is going to run on supports and has enabled multicast. To test whether multicast is supported, please follow the link https://github.com/shawnsschen/CC­NIE­Toolbox/tree/master/generic/mcast_test and obtain the two C files. One is for multicast sender and the other for receiver. If there are more than one network interfaces in the sender’s system, you have to manually update the routing table with one new entry: route add 224.0.0.1 dev eth1. Then use route ­n to check the updated routing ​ ​ ​ table. You will be able to see something like: Note that the entry we added is only matching a particular multicast address 224.0.0.1, not a subnet. If the multicast address changes, you need to manually change the configuration or use a subnet address. Now you have a multicast network (though not sure if it works), next step is to upload the mcast_send.c onto the sender system and mcast_recv.c onto all the receiver systems (more than one in a multicast network). Use the following command to compile them, respectively: gcc ­o send mcast_send.c gcc ­o recv mcast_recv.c send is a multicast sender­side test program, it sends out a “hello multicast world” message every second to multicast group 224.0.0.1:5173.
    [Show full text]