Encoding. The encoding value indicates the serial encoding mechanism that is the nominal design target of the particular SFP transceiver. The value shall be contained in the serial data. The defined encoding values are shown in Table 3.5. code Description of encoding mechanism 00h Unspecified 01h 8B10B 02h 4B5B 03h NRZ 04h Manchester 05h -FFh Reserved The nominal bit rate (BR, nominal) is specified in units of 100 Megabits per second, rounded off to the nearest 100 Megabits per second. The bit rate includes those bits necessary to encode and delimit the signal as well as those bits carrying data information. A value of 0 indicates that the bit rate is not specified and must be determined from the transceiver technology. The actual information transfer rate will depend on the encoding of the data, as defined by the encoding value. Addition to EEPROM data from original GBIC definition. This value specifies the link length that is supported by the SFP transceiver while operating in compliance with the applicable standards using single mode fiber. The value is in units of kilometers. A value of 255 means that the transceiver supports a link length greater than 254 km. A value of zero means that the transceiver does not support single mode fiber or that the length information must be determined from the transceiver technology. This value specifies the link length that is supported by the SFP transceiver while operating in compliance with the applicable standards using single mode fiber. The value is in units of 100 meters. A value of 255 means that the transceiver supports a link length greater than 25.4 km. A value of zero means that the SFP transceiver does not support single mode fiber or that the length information must be determined from the transceiver technology. This value specifies the link length that is supported by the SFP transceiver while operating in compliance with the applicable standards using 50 micron multi-mode fiber. The value is in units of 10 meters. A value of 255 means that the SFP transceiver supports a link length greater than 2.54 km. A value of zero means that the transceiver does not support 50 micron multi-mode fiber or that the length information must be determined from the transceiver technology.
Encoding. Fiserv will encode the dollar amount on all items needing encoding and presented to Fiserv as part of the PROOF function described above.
(a) Fiserv may encode additional fields, such as account numbers, deposit ticket totals or other items as specified by Client. Any such encoding will be according to terms agreed to by Fiserv.
Encoding. In order to take advantage of a Stat Mux pool, Sharer and Xxxxxx may implement a single common encoding pool. Each of Sharer and Xxxxxx shall have the right to monitor in real time and audit the Shared Channel’s encoding system to ensure compliance
2.1. Each of Sharer and Xxxxxx shall make all records of such encoding available to the other upon written request during normal business hours.
Encoding. In order to take advantage of a Stat Mux pool, the parties shall implement a single common encoding pool. Each party shall have the right to monitor and audit the Shared Channel’s encoding system to ensure compliance with Section 2.1. Each party shall make all records of such encoding available to the other upon written request during normal business hours.
Encoding. IMNTV will encode feeds to be delivered to Distributor.
Encoding. In order to take advantage of a Stat Mux pool, Sharer and Xxxxxx must implement a shared encoding pool. Each of Sharer and Xxxxxx shall have the right to monitor and
Encoding. Out of Specs The Mag stripe encoding on a personalized plastic is outside the specifications for encoded data as measured by a margin card or a Mag-Tek InSpec 9000 card reader. OR: Incomplete due to an invalid character in the acct. data stream. OR: Contains embossed acct. information on front, but no encoded information on mag stripe. Relationship Sev 1 Yes Yes Form: Damaged/Defective Forms received from vendor are torn/damaged (including D Hole), have extraneous ink/faded ink, Registration off, Back of pre-printed form doesn’t match pre-printed front for Simplex Product (Print Class A & B). All COLOR Ink defects are ‘Form Defective’ Black Ink from vendor also ‘Form Defective’. But ALL Black Tonor issues are under ‘Form Poor Print Quality’ Damaged during Production: Dirty/Foreign matter (other than toner or vendor ink) that measures at least 1/4” in any direction. or totally obscures or causes the omission of any single Relationship Sev 3 Yes If requested character. (Oil Spots, dirt, belt marks, etc) Torn: >/= 1⁄4” on edges or In body of form. OR Remit stub >1/2 torn from body of form. Wrinkle: Totally obscures or causes the omission of any single character, OR Any jagged wrinkle >3” measured from the 2 furthest points. Form: Print Alignment Wrong Printed Toner not aligned per specifications for Clients’ form. (i.e. ‘H’ alignment, perf-xxxx alignment, skewing, etc.) OR Printed on form upside down or backwards, OR MICR/OCR issues caused by Print Alignment. Relationship Sev 3 Yes If requested Exhibit X-0 X-0 - 00 XXXX / Xxxxx Data Confidential Form: Poor Print Quality Toner missing or unused, or excessive. Toner totally obscures any single character, or omission of any single character. OR Toner issues that cause Unscannable Barcodes (i.e. Formscan, MSAS, Zip-Code, or OMR Marks). OR Any Toner marks that are clearly not part of the programmed printed form. OR Using Wrong Toner- Print Class A & E should be Regular, Class B & F should be MICR. Relationship Sev 3 Yes If requested Form: Fold Wrong Fold is off Perforation OR Incorrect Nesting OR using incorrect Fold style: Z, C for 11” forms, or Double Bi-fold vs Accordian Fold for 14”. OR fold is not aligned following unique client specifications. per special handling. Relationship Sev 2 Yes If exceeds threshold Form: Cut—Bottom / Top Top/Bottom cuts that are not within tolerance per cut template if applicable. OR Missing or mutilated text in any direction OR >1/8” of another form attached per client specificati...
Encoding. The parties may elect to have separate encoding facilities and have one combiner to join the separate streams together for transmission if technically possible, or the parties may elect to have one encoding pool. Each party shall have the right to monitor and audit the Shared Channel’s encoding system to ensure compliance with Section 2.1. Each party shall make all records of such encoding available to the other upon written request during normal business hours.
Encoding. The encoding used for the ASIL decomposition optimisation is much simpler than that used for the architectural optimisation. Rather than have a hierarchical tree structure to represent the makeup of the system, the ASIL optimisation simply uses the set of relevant basic events and assigns each of them an ASIL value between 0 (QM) and 4 (ASIL D). Thus each encoding can in fact be represented as a string of numbers between 0 and 4. This effectively serves as the ‘genes’ of each individual; successful individuals will have some or all of their encoding string preserved in the next generation (meaning that some or all of their ASIL assignments remain the same), whereas unsuccessful allocations of ASILs will tend to die out instead. The format of the encoding is very similar to that of the SRA, which means they can be output upon completion of the optimisation almost directly.
Encoding. Conforming Gateways SHALL support text encoding.
