text: Important Note: The space (blank) character used in file names may not work on all operating systems. To avoid possible failure during file transport, the Intel Business Group and TE who wish to use this feature will need to ensure that both operating systems support this capability during the integration process.
  In the Intel File Transfer system, it is possible to exchange a file with the same filename multiple times. Under certain conditions, this can cause a conflict between two or more instances of the file. These scenarios are detailed below.
  The receiver of a file, Trading Entity A, is using an asynchronous method to download files such as PartnerConnect or FTP/SSL.
  Intel uploads a file destined for Trading Entity A. Before Trading Entity A downloads that file, Intel uploads another file with the same name.
  The Trading Entity A downloads this new file to, or the file is uploaded to, their download directory.
  The most efficient way to resolve the conflicts described above is to avoid them altogether. This can be achieved by requiring a unique filename for each file transmitted between an Intel Business Group and a TE. A simple way to create unique file names would be to add a time/date stamp or a unique id number to a file name (e.g. myfile_20040403_1613.txt).
  If unique file names are not used, a conflict resolution mechanism must be implemented. There are two industry standard solutions.
  Overwriting is the only option currently supported by the Hubspan Transaction Delivery Network Service and PartnerConnect. Specific Intel Business Groups or trading entities not using PartnerConnect may implement other conflict resolution mechanisms.
  Certain events in the Intel File Transfer System can trigger Event Notifications, which are sent to a TE. These are used by the TE both for reconciliation, and as a call to action (e.g. to manually download a file from Hubspan). This section details how they are delivered, which party (Intel or Hubspan) delivers them, and the options for receiving these notifications.