Section D _ Packaging Marking.pdf

SIR 693KA8-20-R-00008

PART I – SECTION D

PACKAGING AND MARKING

D.1.0 PRESERVATION, PACKAGING, AND PACKING

All deliverables under this contract, with the exception of those identified in D.1.1 and D.2.0, must be preserved and packaged in accordance with the most economical rates and best commercial practices to assure delivery at the destination. The Contractor must be responsible for the preservation, potential storage, packaging, and packing of all items to be delivered under the terms of this contract in such a manner that adequate protection is provided against corrosion, deterioration, and physical damage during shipment and handling from the source of supply to the ultimate destination. The Contractor must be fully liable for any damage, deterioration, or losses incurred during shipment, handling, and installation that are attributable to improper packaging.

D.1.1 CONTRACTOR DEPOT LOGISTICS SUPPORT (CDLS)

All components and equipment must be preserved, packaged, and packed in accordance with

ASTM-D-3951. Electrostatic Discharge Sensitive items must be packaged in accordance with best commercial practices.

D.2.0 MARKING OF REPORTS/OTHER DOCUMENTATION/PACKAGES

/DELIVERABLES

Reports and other documentation not delivered electronically must be packaged, packed, and marked to endure arrival at destination in a satisfactory condition and must conform to the best commercial practice.

The Contractor must mark all deliverables as follows:

a. Contract Number and Delivery/Task Order Number under which the item is being delivered

b. Identify the Contract Line Item Number (CLIN) or “Report Requirement” which requires the delivered item

c. National Stock Number (NSN) as applicable: Report Title

d. Serial Number

e. Model/Part Number

D.3.0 MARKING OF SHIPMENTS

All shipments after Government acceptance must be marked on the outside of the package with the following:

a. Contract number and CLIN number

b. Contractor’s name and address

c. List of contents including NSN, Serial numbers, and part numbers, as applicable.

d. Name of item and FAA type designation (nomenclature)

e. Quantity and Unit of Issue

f. Gross Weight of the Container

g. Manufacturer’s Part Number

h. Level of Protection and Date Packed

i. Warranty expiration date

D.3.1 CONTRACTOR DEPOT LOGISTICS SUPPORT (CDLS)

All components, equipment and spares with a consignee other than the FAA Logistics Center

(FAALC) must be marked with the marking requirements of ASTM-D-3951. In addition, each unit, intermediate, and exterior-shipping container, must be marked with the following information:

a. Serial Number

b. Part Number

c. Warranty Expiration Date

d. Contract Number

e. Contract Line Item Number

f. Manufacturer

D.3.2 IDENTIFICATION MARKINGS

The Contractor must provide identification markings on all system packaging and containers. The following identification information must be marked on all containers. Additional identification markings may be required by the contract and must be placed either below these markings or in a conspicuous location on the identification-marked side(s) of the container. In the case of multiple items in single shipping containers, the shipping container will have a packing list that identifies all items within it, and each item must follow these marking requirements:

a. NSN (National Stock Number). The in-the-clear NSN will include spaces or dashes and any prefix or suffix specified in the contract or solicitation. The bar coded NSN and human readable interpretation (HRI) below the bar code will not include spaces or dashes, unless otherwise specified in the contract or solicitation.

b. CAGE code. The Commercial and Government Entity (CAGE) code of the company awarded the contract for the item being shipped. The CAGE code is a unique identifier assigned to suppliers as well as to government agencies and various organizations.

c. PN (Part Number). If a PN is specified in the contract or order, then only that PN must be shown. The PN specified in the contract may be the PN assigned by the Government procuring activity, or it may be the PN of the actual manufacturer or the PN assigned to the item by the company awarded the contract. The letters “PN” or “P/N” must be used to identify this information. If the item has no PN assigned to it or if no PN is cited, then nothing is shown.

d. Item description or nomenclature. The exact name and description of an item as it appears in the contract, purchase order or requisition must be shown. Item description may be marked on more than one line if required due to space limitations. Standard abbreviations, although not desired, may be used if marking length is excessive.

e. Quantity and Unit Issue (UI). A non-definitive UI must be accompanied by a quantitative expression such as “1 RO (100 FT).”

f. Contract number or purchase order number (Procurement Instrument Identification

Number (PIIN)) including four-digit delivery order or call number, modification for change order number, and lot number must be shown. The in-the-clear contract number will include the dashes as shown in the contract, i.e., XXXXXX-XX-X-XXXX. Additional information may be required by the contract or purchase order.

g. Shelf-life markings, if applicable, must be applied as in Section D.4.3.

h. Serial number(s). When an item is assigned a serial number, that number must be applied and preceded by the abbreviation “SER NO.”

i. Gross weight. The capital letters “WT” must precede the gross weight. The gross weight will be expressed in pounds rounded up to the nearest pound.

D.4.0 BAR CODE TRACKING SYSTEM

The Contractor must ensure that each DC BUS delivered to the FAA has a bar code identifying the item in accordance with the FAA approved Bar Code. Other equipment delivered to the FAA, as deemed appropriate by the CO or COR upon ordering, must have a bar code identifying the item in accordance with the FAA approved Bar Code.

Each DC BUS will be named, described, identified, classified, and numbered (cataloged) in accordance with Federal Property Management Regulations, specifically Personal Property

Management, FAA Order 4600.27C and the FAA Asset Identification Process and Procedure

Guide. The Contractor must provide valid national stock number(s) (NSN) for each individual item of DC BUS specified in Section B when ordered. If no NSN has been assigned to an item, the

Contractor must provide sufficient descriptive data to obtain NSN(s) from the Defense Logistics

Information Service (DLIS).

D.4.1 FAA SCANNING PROCESS

The FAA has undertaken a scanning initiative as part of the Life Cycle Asset Tracking System

(LCATS). While the following process has been generated by the FAA, the FAA does not consider the process to be significantly different from the processes Contractor’s use as part scanning and data collection activity for shipping and tracking.

The steps to be performed by the Contractor are described below:

a. Contractor employees capture the barcode that relates to the DC BUS serial number of the units placed on a shipment.

b. Contractor will generate the required XML file. This file will be in FAA specified format and should be saved with the following file name: items

Scanned_YYYYMMDD_hhmmss_<faa provided designator>.xml, where YYYY = year, MM = month, DD = day, hh = hour, mm = minute, ss=second and <faa provided designator> will be the contractor identifier provided by the FAA.

This file will contain the LRU item scan information for each LRU per shipment file and will be in the FAA designated xml format which will contain the fields as follows per LRU item: Scanned Barcode, Part Name (FAA provided per part number), Receiving/Sending/Inventorying (a flag), Intended Destination as text (FAA can provide information), Contractor Identifier as user name (FAA provided), Contractor Location

(FAA provided), Contractor facility type (FAA provided), Date and Time stamp of scan, and other FAA provided placeholder fields.

c. Contractor will transfer the XML file described in step b. via email to a designated FAA office (may be contractor support) for processing. The file should be sent when an outgoing shipment is ready to send, upon receipt of a shipment of FAA equipment, or at the completion of an FAA requested inventory.

d. Contractor will generate a second required XML file. This file will be in the FAA specified format and should be saved with the following file name: Items ScanFieldData_

YYYYMMDD_hhmmss _<faa provided designator>.xml where YYYY = year, MM = month, DD = day, hh = hour, mm = minute, ss=second and <faa provided designator> will be the contractor identifier provided by the FAA. This file will contain the LRU scanned barcode for each LRU per shipment file and will be in the FAA designated .xml format which contains the fields as follows: shipment carrier name and shipment carrier tracking code for outbound shipments, and the FAA voucher number for returns

e. Contractor will transfer the XML file described in step d. via email to a designated FAA office (may be contractor support) for processing when the information is obtained for either:

1. Carrier Name and Tracking Number when Shipment Carrier has taken the shipment.

2. FAA Voucher Number when Equipment is scanned in as a return for a repair or warranty concern.

D.4.2 PRODUCTION DATA REQUIREMENTS

The Contractor will support the FAA with scanning for tracking production units from their point of shipment originating at the production facility to receipt of production units at FAA designated location. To support this effort, the Contractor will record the unit serial numbers in the FAA tracking format. The Contractor will also attach the tracking information to the shipment in a separate file. The Contractor must align the barcode scanning process to allow the interface with the FAA data collection system.

The Contractor must modify any existing processes to work with the FAA Scanning Process. The

Contractor must support a pilot run of this FAA Scanning Process with FAA representatives to ensure data transfer takes place as intended. The Contractor may, as an option, accept as

Government Furnished Equipment (GFE) a handheld barcode scanner and GFE software that creates the required xml files from scanning equipment off the production line. If the Contractor elects to use the GFE process, the Contractor must have a scanner operator that can scan the equipment off the production line and then send tracking information for outgoing shipments when they leave the dock.

D.4.3 BAR CODE MARKINGS

Bar code markings, as applicable, are required for contractor-originated shipments, unless specifically exempted in the contract. The Bar Code Markings, as shown in Figure D-1, must include all identification marking requirements of Section D.3.0 and Section D.3.2 above plus the following individual item identifiers described in this section.

Figure D.1

Sample 15434 Compliant Barcode

D.4.3.1 INDIVIDUAL ITEM MARKING REQUIREMENTS

The following barcode requirements that identify the DC BUS unit must be placed in 2D Barcode format as specified in this section on the outside of the individual container and on the DC BUS unit itself. Identification bar code markings must not be obscured by application of strapping or tape and must be readily readable by a barcode scanner upon installation. Table D-1 provides an example of 2D Data Matrix with Part Number, Cage Code, Serial Number and GS1

(http://www.gs1.org) Global Individual Asset Identifier (GIAI).

Message Header [)>

Message Separator <<RS>>

Format Header 05

Group Separator <<GS>>

Application Identifier (GIAI) 8004

Company Prefix 0614141

Individual Asset Reference 0048500AX20791

Record Separator <<RS>>

Format Header 12

Group Separator <<GS>>

Application Identifier (Internal)

CAGE Code CAG 12345

Group Separator <<GS>>

Application Identifier (Internal)

Original Part Number PNO ABC123

Group Separator <<GS>>

Application Identifier (Internal)

Serial Sequence Number SEQ 7890

Record Separator <<RS>>

End of Transmission <<EOT>>

Table D.1 2D Data Matrix with Part Number, Cage Code, Serial Number and GS1 GIAI 15434

Compliant

Scan Output of the 2D barcode described in Table D-1 must be as shown below:

]d1[)>[ RS]05[ GS]800406141410048500AX20791[ RS]12[ GS]CAG 12345[ GS]PNO ABC123[

GS]SEQ 7890[ RS][EOT]

Where “]d1” is the Symbology Identifier for the Data Matrix data carrier and it represents an

ECC200 Data Matrix. A list of the Symbology Identifiers can be found in ISO/IEC 15424

D.4.3.2 APPLYING IDENTIFICATION BAR CODES

D.4.3.2.1 APPLYING IDENTIFICATION BAR CODES ON CONTAINERS

Bar code markings must be applied by labeling or by direct printing on the container. When specified in the contract or purchase order, identification bar code labels generated on thermal printers may be used. Thermal labels must be durable, buff-colored stock, or equivalent. All labels must have protection from becoming illegible through contact with water, be capable of withstanding normal commercial handling, and remain securely in position, assuming commercial shipping practices and environment.

Bar code markings must be legible and visible when shipped (e.g., palletized) from the Contractor facility. Any shrink-wrap, packaging tape, etc., must not interfere with the legibility and readability of the bar code markings.

D.4.3.2.2 APPLYING IDENTIFICATION BAR CODES ON DC BUS UNITS

Bar code markings must be legible and visible, and applied to a surface of the DC BUS Unit not subjected to thermal or mechanical wear. All labels must have protection from becoming illegible through contact with water, be capable of withstanding normal commercial handling, and remain securely in position.

D.4.3.3 HUMAN READABLE INTERPRETATION (HRI)

The HRI for each of the bar codes should appear above, below, or in line with the 2D bar.

Examples of acceptable sizing and 2D barcode layout with HRI are included in figure D.2. The label should include the following HRI information:

CAG <cage code>

SEQ <manufacturer serial number>

PNO <manufacturer part number>

UII <Global Individual Asset Identifier>

FIGURE D.2

Sample Label