IUIDBOM-SOWSolInstructions2007-12-21.doc

U.S. General Services Administration

Federal Acquisition Service, Great Lakes Region Acquisition Operations Division

Code 5QZA, Room 3280

230 South Dearborn Street

Chicago, Illinois 60604-1696 U.S. General Services Administration

IUID Data Labels – Draft PWS

Solicitation ITSS# 5TS57070224

DRAFT

Bill of Materials / Statement of Work

Solicitation Instructions And Evaluation Criteria

For

Item Unique Identification (IUID) Data Labels

And IUID Data Label Processing and Management Services

A procurement by the U.S. General Services Administration on behalf of

The United States Air Force Air Force Automatic Identification Technology Program Management Office (AF/AIT/PMO) Solicitation Number / Contract Number

GSA ITSS # 5TS57070224 / To Be Determined NAICS 339943 – Marking Device Manufacturing IUID Data Labels

And

IUID Data Label Processing and Management Services Table of Contents

Page

SECTION I – PERFORMANCE WORK STATEMENT

1.

Procurement Objective 2.

Introduction 3.

Background 3.1 Government Mission 3.2 Air Force Purpose for this Solicitation.

3.3 Project History 4.

Scope 4.1 General Scope of Work.

4.2 Resources

4.3 Placement and Management of Work.

4.4 Customers 4.5 Location of Work 4.6 Period of Performance.

5.

Definitions 6.

Schedule of Items/Services and Prices 7.

Performance Objectives.

7.1 Performance Objective #1 IUID Data Label-Requests.

7.2 Performance Objective #2 IUID Data Label-Data Process, Report, & Mgt.

7.3 Performance Objective #3 IUID Data Label Process Development.

7.4 Performance Objective #4 IUID Data Label Specifications.

8.

Contract Implementation Phases.

8.1 Phase 1 – Initiation Phase.

8.2 Phase 2 – Full Operational Phase.

9.

Quality Assurance/Quality Control.

9.1 Contractor QA/QC Responsibility 9.2 Quality Assurance Surveillance Plan (QSAP).

10.

Special Performance Requirements.

10.1 Location of Work 10.2 Time of Work 10.3 Performance During Crisis – Not Applicable.

10.4 Travel 10.5 Limitations on Contractor Performance – Not Applicable.

10.6 Key Personnel 10.7 Privacy Act Requirements.

10.8 Personal Services Compliance – Not Applicable 10.9 Rehabilitation Act Compliance (Section 508).

10.10 Security Requirements 10.11 Disclosure of Information 10.12 Limited Use Data 10.13 Productive Direct Labor Hours 10.14 Payment for Unauthorized Work.

10.15 Description of Supporting Requirements.

11.

Government Furnished Items.

11.1 Data 11.2 Equipment – Not Applicable 11.3 Materials – Not Applicable.

11.4 Facilities 12.

Performance Eligibility.

13.

Government Delay.

14.

Notices 15.

Contact Information.

15.1 Contractor Contacts

15.2 Government Contacts

16.

Delivery and Performance.

16.1 Clauses Incorporated by Reference.

16.2 Delivery Dates and Places.

17.

Packing, Marking, and Shipping.

17.1 Preservation, Packaging and Packing 17.2 Packing List 17.3 Pack, Marking and Storage of Equipment.

17.4 Shipment.

18.

Inspection and Acceptance.

18.1 Inspection 18.2 Acceptance 18.2 Contractor Acceptance or Rejection Notice 18.2 General Acceptance Criteria for Data Deliverables 19.

Post Award Evaluation of Contractor Performance.

19.1 Contractor Performance Evaluations.

19.2 Electronic Access to Contractor Performance Evaluations 20.

Additional PWS Provisions.

21.

PWS Attachments.

Attachment 1 Data Item Descriptions, DD Form 1423-1s Attachment 2 Mil-Std-130M, 2 Dec 2005

SECTION II – PROPOSAL

22.

Proposal Contents 22.1 Describe IUID Data Label Processing and Management system .

22.2 Describe IUID Data Labels.

22.3 Confirm Delivery 22.4 Price

22.5 GSA FSS Contract Reference (if applicable) 22.6 Warranty 22.7 Section 508 of the Rehabilitation Act of 1973 22.8 Central Contractor Registration (CCR) 22.9 Representations & Certifications, DUNS No. & TIN.

23.

Proposal / Quotation Submission Instructions.

23.1 Submission 23.2 E-Buy Attachment Restrictions 23.3 ITSS Registration Requirement 23.4 Proposal/Quotation Retention 24.

Proposal Preparation Costs 25.

Representations and Certifications 26.

Subcontracting Plan 27.

Proposal Privacy 28.

Requests for Changes, Clarifications, Clarification or Additional Information

SECTION III – PROPOSAL EVALUATION

29.

Technical Evaluation 30.

Past Performance Evaluation.

31.

Price Evaluation 32.

Other Evaluation Requirements.

SECTION IV – AWARD

AWARD

33.

Award

33.1 Type of Contract 33.2 Basis of Award 33.3 Award Format and Contents 34.

Invoicing and Payment 35.

Funding

IUID Data Labels

And

IUID Data Label Processing and Management Services

SECTION I – PERFORMANCE WORK STATEMENT

1.

Procurement Objective

This procurement is for the establishment of an indefinite quantity contract or BPA (Blanket Purchase Agreement) for purchasing Item Unique Identification Data Labels, hereafter referred to as IUID Data Labels, and IUID Data Label Processing and Management Services for the U.S Air Force.

Introduction The Item Unique Identification Program is an initiative of the Office of the Under Secretary of Defense for Acquisition, Technology, and Logistics (OUSD [AT&L]) and is being administered for the Air Force by the Air Force Automatic Identification Technology Program Management Office (AF/AIT/PMO), Air force Packaging Technology and Engineering Facility (AFPTEF), Wright Patterson AFB.

The government proposes to award a contract or BPA under GSA Federal Supply Schedule for this requirement. Following award of the indefinite quantity contract or BPA, the Government will place orders for the required items and services as needed. The estimated order ceiling will be approximately 5 million IUID Data Labels over a 5 year period. Proposals that fail to comply with the requirements of these instructions will be considered to be non-responsive.

3.

Background:

3.1 Government Mission

The Department of Defense (DoD) must uniquely identify tangible items to provide for better asset accountability, valuation, and life cycle management. The mission of the Air Force Automatic Identification Technology Program Management Office (AF/AIT/PMO), Air force Packaging Technology and Engineering Facility (AFPTEF), is to manage the tangible assets of the Air Force. One of the performance objects of AF/AIT/PMOU is to positively identify and track the location and movement of all tangible assets (goods and equipment).

3.2 Air Force Purpose of this Solicitation The purpose of this Performance Work Statement (PWS) is to define the requirement for processing requests, producing, supplying, and managing inventory control and accountability of IUID Data Labels. The primary object of this solicitation is to engage a contractor to furnish an IUID Data Label Processing and Management Service and supply IUID Data Labels, thus enabling the Air Force to meet IUID requirements.

3.3 Project History

Item Unique Identification (IUID) is the set of data for tangible assets that is globally unique and unambiguous, ensures data integrity and data quality throughout the life cycle, and supports multi-faceted business applications and users. IUID provides the opportunity to differentiate an individual item from all others throughout the DoD supply chain, commencing with acquisition and terminating with disposal or reutilization.

The Office of the Under Secretary of Defense for Acquisition, Technology, and Logistics (OUSD [AT&L]) has issued policy guidance for use of IUID within the Department. The policy establishes a strategic imperative for uniquely identifying tangible items relying to the maximum extent practical on international standards and commercial item markings and while not imposing unique government data requirements. The Air Force will comply with this guidance.

The Air Force Unique Identification Program has been established to manage and implement developing policy disseminated by the OSD (AT&L). The IUID program began as one of DoD's solutions for addressing non-compliance issues associated with the Chief Financial Officers' Act of 1990. This act calls for improved financial management, item accountability and cost reduction, and emphasizes results-oriented management. IUID provides DoD with the capability for enhanced total asset visibility, improved lifecycle item management and accountability, and clean financial audits. In summary, it allows the DoD to identify individual assets at any time throughout the lifecycle and provides the means to relate them to their historical engineering and logistics support data. The July 29, 2003 OUSD (AT&L) policy memorandum and subsequent memoranda mandate IUID on all DoD solicitations issued on or after January 1, 2004.

Tangible assets subject to IUID labeling include:

· All delivered items for which the Government's unit acquisition cost is $5,000 or more.

· Items for which the Government's unit acquisition cost is less than $5,000, when identified by the requiring activity as serially managed, mission essential, or controlled inventory.

· When the Government's unit acquisition cost is less than $5,000 and the requiring activity determines that permanent identification is required.

· Regardless of value, (i) any DOD serially managed subassembly, components, or part embedded within a delivered item and, (ii) the parent item (as defined in DFARS 252.211-7003(a)) that contains the embedded subassembly, component or part.

In response to this requirement, the Air Force is executing a multi-phased approach to comply with the IUID policy mandate issued by OUSD (AT&L) in a memorandum dated 23 Dec 04, which directs all Military Departments to apply IUID policy to qualifying legacy items. The Air Force seeks to implement a standardized IUID Data Labeling Strategy in conjunction with IUID implementation.

The IUID Data Labeling Strategy calls for the implementation of an aggressive “seek and mark” process for labeling legacy items and the establishment of a “just in time” label production and placement process integrated into the standard maintenance cycle. Outsourcing the production of IUID labels will augment the ongoing organic label production process and will free resources to allow the Air Force maintenance to concentrate on its core area of expertise; repairing and operating weapon systems.

IUID Data Label implementation will be executed in two phases.

· AFEMS Phase 1: AFEMS pilot project, marking approximately 25k assets located at WPAFB, OH.

· AFEMS Phase 2: AFEMS project executed by region, marking approximately 5.2M assets. Implement “Seek & Mark” strategy targeting groups of assets tracked in other systems and equipment locations.

4.

Scope 4.1 General Scope of Work

The contractor will provide the IUID Data Labels, and IUID Data Label Processing and Management Services per the following purchase description and statement of work provisions. The IUID Data Labels, and IUID Data Label Processing and Management Services shall be commercial off-the-shelf (COTS) items. The IUID Data Label Processing and Management Services and the manufacture and delivery of IUID Data Labels shall be a turn-key operation planned and executed by the Contractor. All components and all costs associated with this requirement shall be included in the item prices proposed by the Contractor and accepted by the government as stated in the BPA/contract and on individual IUID Data Label requests.

4.2 Resources

Under this contract, unless otherwise stipulated, the Contractor shall furnish all resources to deliver services and items described herein. The Contractor shall be responsible for managing and overseeing the activities of all contractor personnel, as well as subcontractor efforts used in performance of this effort. The Contractor’s management responsibilities shall include all activities necessary to ensure the accomplishment of timely and effective contract performance in accordance with the requirements contained in this performance work statement.

4.3 Placement and Management of Work

The Contractor shall perform all work at the Contractor’s place of business. Processing and management of IUID Data Label requests shall be provided by an electronic interface or by other communication channels as defined below. Government employees shall have access to this system to place IUID Data Label requests and monitor processing, shipment, and delivery.

4.4 Customers

The customer and recipient of all items and services delivered under this contract is the U. S. Air Force. Customers include Air Force organizations, worldwide, that have items mandated for marking.

4.5 Location of Work – Place of Performance

The Contractor support team shall perform at the Contractor’s facilities. In-process reviews and management meetings will be conducted via teleconference or as otherwise mutually agreed upon by the parties to this contract.

4.6 Period of Performance

The period of performance for the IUID Data Label Processing and Management services will begin upon award of this contract. The indefinite quantity contract or BPA will continue for five years from date of award during which time orders will be placed to fulfill this requirement.

5.

Definitions

5.1 AF/AIT/PMO refers to the Air Force Automatic Identification Technology Program Management Office. This office is responsible for administering the IUID Data Label program for the U.S. Air Force.

5.2 Unique Identification (UID) refers to all initiatives to uniquely identify tangible personal property, real property, personnel, organizations, and financial transactions.

5.3 Item Unique Identification (IUID) refers to the policy about uniquely identifying tangible personal property assets.

5.4 Unique Item Identifier (UII) refers to the unique serial number physically marked on an item, in the form of the ECC 200 data matrix, which is globally unique and unambiguous.

5.5 IUID Data Label refers to a label containing item unique identification (IUID) information of the part/equipment on which the label is affixed. The label contains IUID information in 2D machine readable data matrix as well a human readable format. The label can be made out of a variety materials as established by industry standard (i.e. Aluminum, Steel, Vinyl, Polyester…etc). The IUID information can be applied to the data label using a variety of methods as established by industry standard (i.e. embossing, dot-peen, laser etching, laser printing, chemical etching…etc).

5.6 IUID Data Label Process and Management System – The IUID Data Label Process and Management System is an automated system set up by the Contractor for (1) receiving IUID Data Label requests, including Government property identification information, (2) processing the requests, (3) delivering IUID Data Labels, (4) monitoring the IUID Data request process, and (5) providing IUID Data Label process reports.

5.7 IUID Data Label Requests – The IUID Data Label Requests are requests made by individual Government offices for the production and delivery of IUID Data Labels. IUID Label Requests should not be confused with the contractual ordering process by which funded orders are placed against the Contractor’s indefinite delivery/indefinite quantity (ID/IQ) contract or Blanket Purchase Agreement (BPA) for a certain quantity of IUID Data Labels. Only contractual orders will obligate funds for the purchase of IUID Labels.

6.

Schedule of Items/Services and Prices

IUID Data Labels & IUID Data Label Processing & Management Services NOTE: The following is an example of line items.

Day

each

Each

Each

Each

Each

Each

Each

Each

Each

Etc.

Each

Each

Etc.

TOTAL

7.

Performance Objective(s) / Purchase Description

To fulfill this requirement the Government proposes to purchase IUID Data Label Processing and Management Services and IUID Data Labels.

7.1 Objective 1 – IUID Data Label Processing and Management Service - Requests The Government has a need to be able to easily request IUID Data Labels from any Air Force facility or location and have them quickly delivered to locations within the Continental United States for Project Phase 1 and to locations worldwide for Project Phase 2.

7.1.1 Requesting IUID Data Labels

The Contractor shall provide a means whereby government personnel can request IUID Data Labels.

7.1.1.1 Communication Medium - The requesting method shall be compatible for use over the Internet (email and web application), and by phone or facsimile to allow those limited to any one of these communication mediums to place IUID Data Label requests.

7.1.1.2 Self-Service - The requesting method shall be established as a requestor “self-service” system.

7.1.1.3 Request Execution - The method for making IUID Data Label requests must be relatively simple and straight forward and easy to execute.

7.1.1.4 Requestor Training - The requesting method should require minimal requestor training and ideally require no formal requestor training. The Contractor shall provide training materials that will include an online ordering procedure manual.

7.1.1.5 Request Form Completion - The requesting method shall prompt the requestor for how to complete each entry on the request form and ideally will provide easy access to helps and explanations if required. These can be in the form of an IUID Data Label processing instruction or procedure manual. The help screens or manuals shall guide the user through the process of making and monitoring IUID Data Label requests. These manuals shall be available online, as an electronic down-loadable file, and in hard-copy format.

7.1.1.6 Delivery Times - The requesting method must be capable of handling a range of IUID Data Label processing and delivery time frames based on the size of individual requests; from normal processing and delivery times to expedited processing and delivery times. Normal processing and delivery should not exceed 14 calendar days. The desired expedited processing and delivery time should be no more than 48 hours. A Contractor provided matrix establishing delivery time options associated with order size shall be included in the IUID Data Label request functions and instructions. (Note: The Government’s objective is to be able to obtain up to 5000 IUID Data Labels every 48 hours.)

7.1.1.7 Request Options - The requesting method should include information on all IUID Data Label configurations and options for easy selection by the requestor, whether placing orders electronically or in hard-copy format. The options shall include all the materials available for IUID Data Label construction, size, color, and data content that are listed in the contract.

7.1.1 Sample Ordering Scenario GSA, on behalf of an Air Force activity, will place a funded Delivery Order against the ID/IQ Contract or BPA for a ceiling dollar amount. Subsequently, offices within that Air Force Activity will notify the Contractor of their need for IUID data labels via a web-based interface, email, the phone or facsimile. The Government requesting organization shall supply the Contractor with the applicable data for UII creation via the Contractor’s ordering solution. The requestor shall select the applicable IUID Data Label options of size, material, quantity, and delivery time as provided on the request form. The requestor shall verify the data on the request and send the request to the Contractor to fill the request. While the request is being processed by the Contractor the requestor may monitor the status of the request through the web-based IUID Data Label management tools. The requestor shall receive, inspect, and accept the IUID Data Labels and annotate the request as being fulfilled via the web-based IUID Data Label management tool. The cost of the requested and delivered IUID Data Labels will be charged and billed against the designated Delivery Order until the cost ceiling is reached.

7.2 Objective 2 – IUID Data Label Processing and Management Service – Data, Process, and Report Management The Government has a need to monitor and track IUID Data Label requests from the time of their inception, through request processing, production, shipping, and delivery at their ultimate destination.

The Government has a need for access to data and reports concerning all IUID Data Label activities, including request, numbering, process time, delivery, and payment.

7.2.1 Managing IUID Data Label Data

The Contractor shall provide a means whereby government personnel can track all IUID Data Labels processing activities and obtain reports.

7.2.1.1 The IUID Data Label processing solution shall give authorized government personnel the ability to monitor all IUID Data Label processing activities in real time.

7.2.1.2 The IUID Data Label processing solution shall allow authorized government personnel to monitor, as a minimum, all information on IUID Data Label requests including time of entry or submission, IUID Data Label numbering, Contractor IUID Data Label request processing time, verification of delivery location, verification of delivery time, and invoicing and payment status.

7.2.1.3 The IUID Data Label processing solution shall provide secure access capability to protect sensitive business and Air Force tangible asset identification information.

7.2.1.4 The IUID Data Label processing solution shall provide the means for the requestor to annotate the request as having been successfully fulfilled or to submit a request for corrective action if the IUID Data Label request is not filled as originally placed. The IUID Data Label processing solution shall also provide a way for the requestor to provide feedback regarding his or her experience with the request process and the condition of the delivered items, including a way to report the delivery of defective IUID Data Labels and request corrective action.

7.2.1.5 The Contractor shall provide over-the-phone assistance to answer questions and provide assistance with all aspects of the IUID Data Label process (making requests, tracking request, verifying IUID Data Label quality, coordinating returns and replacement of defective items. This phone assistance line shall be available between the hours of 7 A.M and 4 P.M Eastern Time for Phase 1 and between the hours of 7 A.M and 8 P.M Eastern Time for Phase 2.

7.2.1.6 The IUID Data Label processing solution shall provide a means for notifying the AIT PMO if any difficulty should arise that will delay timely delivery of 48 hours IUID Data Label requests.

7.2.2 IUID Data Label Data Access and Report Generation The Contractor shall provide a means whereby government personnel can access all IUID Data Labels processing activities and obtain reports.

7.2.2.1 UII and Birth Record Transmission - The IUID Data Label processing solution shall enable the SNT IUID Project Office to obtain, on at least a weekly basis, the UIIs assigned by the Contractor along with birth record information and transmission date (for registration at the DoD UID registry). Transmission via a flat file attached in an email is an acceptable transmission method. The IUID Data Label processing solution shall enable the Contractor to ensure successful data transmission through verbal or written conformation with a representative from the project office. The data fields contained within the UIIs and birth record information are as follows:

· ShipTo Code – Requesting site ID

· UID – Unique Identifier for the data label

7.2.2.2 Quality Assurance Verification Statistics - The IUID Data Label solution shall incorporate a process for maintaining and collecting the Contractor’s quality assurance verification statistics and shall provide the means for government AIT PMO access to this information on a real time or quick turn around access basis. The QA verification statistics shall ensure visibility of the following:

· Number of data labels requiring replacement after delivery to the government due to inadequate form and/or function

· Number and frequency of instances that the Contractor could not meet the required 48 hour turn around

· Number of data labels requested

· Number of data labels produced

· Number of data labels delivered

7.2.2.3 Access Security - The IUID Data Label solution shall incorporate system security features that will only allow authorized users make IUID Data Label requests or access processing data or reports. This should include user access verification using Government furnished authorization codes and passwords and authorized user lists.

7.2.3 IUID Data Label Data System Configuration The Contractor shall be responsible for configuring and initiating the IUID Data Label Processing and Management System. Prior to initiating this effort, Contractor representatives shall meet with Government program official to review all aspects of the contract statement of work and the system configuration to ensure all Government requirements will be meet.

7.3 Objective 3 – IUID Data Label Processing and Management Service Development If the IUID Data Label Processing and Management Services described in Objectives 1 and 2, above, are not commercially available, the Government also has the need for IUID Data Label Processing and Management Services development.

7.3.1 IUID Data Label System Development and Configuration The Contractor shall work with Government personnel to develop a system that will perform all of the functions of this requirement.

Note: During IUID Data Label System Development the AF SNT/IUID project office will manage the process development for item identification, serialization, data plate request, funding, delivery, UII verification, and quality, henceforth referred to as the IUID Data Label Business Process. The IUID Data Label Business Process development will be a temporary effort instituted to mature the current process established by the SNT IUID project office for interfacing and utilizing the Contractor’s services.

7.3.2 IUID Data Label Data System Work Breakdown Structure (WBS) The development of an accurate Work Breakdown Structure (WBS) provides the framework from which to integrate the project schedule, cost, and performance data. Key Contractor personnel will prepare a WBS (in Microsoft Project format) at the initiation of the IUID Data Label Data System Business Process development. The Contractor’s technical lead and the AF SNT/IUID project office will then monitor the WBS. The WBS will be updated monthly as part of the Monthly IPR Report (see para 7.3.4.2, below).

7.3.3 IUID Data Label Data System Development Milestones The following table provides suggested milestones for system development.

Table 1.5‑1 Key Milestones

Project Management

IUID Data Label Processing and Management Services

Familiarization Training

· Online Ordering request & tracking Procedures Manual 25 working days following award

7.3.4 Review and Oversight of IUID Data Label Data System Development and Configuration 7.3.4.1 Status Meetings

Once the IUID Data Label Processing and Management System is initiated, the Contractor shall conduct status meetings with the AF SNT/IUID project office via teleconference or by other mutually agree upon venue. The Contractor shall develop a meeting agenda template, including a place for issue/action item tracking. Prior to each meeting the Contractor shall prepare an agenda using the template. The Contractor shall take minutes of each status meeting including a record of issues and action items. The minutes shall be published and disseminated to the participants. Open action items will be carried forward to the next meeting minutes. The Contractor shall plan on conducting these meetings on a weekly basis or at other intervals mutually agreed upon by the parties throughout system development, Phase I, or until the AF SNT/IUID project office deems them no longer necessary.

7.3.4.2 System In-Process Reviews (IPRs)

Each month, the team will conduct an In-Process Review (IPR). (Note: This meeting will replace the weekly status meeting, para 7.3.4.1, during the week in which it is held.) The Contractor shall develop the Monthly IPR Agenda, and materials will be distributed to all participants in advance via e-mail in the form of a draft Monthly IPR Report. During the IPR, the Contractor shall provide, at a minimum:

· Schedule Status Report

· Funding and Expense Status Report

· Key Issues and Risks

· Accomplishments since last IPR

· Planned Activities before next IPR

· Document Results and Issues/Action Items

Following the IPR, the Monthly IPR Report will be finalized.

7.3.4.3 Process Development Technical Interchange Meetings (TIMs)

The Contractor shall support Technical Interchange Meetings (TIMs), presentations, and demonstrations as required. The Contractor shall provide Technical Interchange Meeting Minutes for any TIMs conducted.

7.3.4.4 Project Management The Contractor shall provide appropriate project management for the IUID Data Label Processing and Management Services development effort. To facilitate Government-Contractor communications the Contractor shall provide a Project Manager to oversee this effort, including the transition into the operational mode. The Project Manager shall be the primary technical and managerial interface between the Contractor, the Contracting Officer (CO), and the Contracting Officer’s Technical Representative (COTR). The name and contact information (email address, phone, etc.) of the Project Manager (or alternate) shall be provided to the Government upon contract award. The Contractor shall notify the Government, providing similar contact information should the Project Manager be replaced during contract performance. The Project Manager, or designated alternate, shall have full authority to act for the Contractor on all matters relating to daily operations of the contract. The Project Manager, or in his or her absence the designated alternate, must be available during normal duty hours and to meet with Government personnel. The Project Manager shall meet with the CO/COTR as necessary to maintain satisfactory performance and to resolve other issues pertaining to Government/Contractor procedures.

7.4 Objective 4 – IUID Data Label Specifications and Production

The Government has the need for the delivery of IUID Data Labels that meet the following specifications

7.4.1 IUID Data Label Product Description / Specification Data labels shall be manufactured to conform to the following specifications, standards and requirements.

7.4.1.1 Materials - IUID Data Labels shall be constructed of one of several materials. The material selected for each request will be most suitable for the labeling application. The Contractor shall provide the following material choices.

7.4.1.1.1 anodized photosensitive aluminum substrate that exceeds the DOD requirements outlined in Mil-Std-130M;

7.4.1.1.2 Brass;

7.4.1.1.3 Steel;

7.4.1.1.4 other metallic material;

7.4.1.1.5 Vinyl;

7.4.1.1.6 tesa tape;

7.4.1.1.7 polyester media

7.4.1.2 IUID Data Label Attachment Methods - The Contractor shall provide several attachment method options appropriate for a wide variety of applications. The Contractor shall provide application instructions with each shipment of IUID Data Labels. Application method options shall include:

7.4.1.2.1 Adhesives

7.4.1.2.2 Rivets

7.4.1.3 Size - The Contractor shall furnish IUID Data Labels in three sizes. The dimensions shall be as follows:

7.4.1.3.1 The Standard size shall be 1.75 inch wide by 0.75 inch high.

[Note: Industry input on sizes, materials, thicknesses, and data impression options is specifically requested.] 7.4.1.3.2 Other A

7.4.1.3.3 Other B

7.4.1.4 Construct #1 Requirement - IUID Data labels shall be manufactured in accordance with use UID construct #1 as specified in the latest version of the OSD Unique Identification Guide.

7.4.1.5 IUID Data Label Information - In addition to the information required for construct #1, the Contractor shall include the following marking information on each IUID Data Label, ensuring that it is coded correctly. This information shall be applied, per the Government specification, in both a machine readable data matrix bar code and human-readable alphanumeric text, including nomenclature (in English).

7.4.1.5.1 Original Equipment Manufacturer’s CAGE

7.4.1.5.1 Item Serial Number

7.4.1.5.1 Original Part Number

7.4.1.5.1 Nomenclature (human readable only)

7.4.1.6 Affixing IUID Data Label Information to the Media – The Contractor shall be responsible for affixing the IUID Data Label information to the data label media. Depending on the label media the Contractor shall apply the label information using embossing, dot-peen, laser etching, laser printing, chemical etching, or other industry standard methods meeting Government requirement.

7.4.1.7 Bar Code Semantics - The Contractor shall provide all machine readable 2D bar codes using ISO 15418 semantics with DIs (See MILSTD 130M paragraph 5.2)

7.4.1.8 Bar Code Syntax - The Contractor shall provide all machine readable 2D bar codes using ISO 15434 syntax (See MILSTD 130M paragraph 5.2) 2 http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=27661 2 http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=43692

The Contractor shall manufacture IUID Data Labels using the standard layout adopted by the AIT PMO, which is represented in the following graphic.

7.4.2 IUID Data Label Compliant UII Generation

The Contractor shall be responsible for generating and placing UIIs on data labels. The Contractor shall generate UIIs based on the DoD guidelines and syntax provided by the Air Force IUID PMO. These guidelines and syntax shall be provided to the Contractor, in writing, within 5 business days after contract award. The Contractor will retain responsibility for the uniqueness of the UIIs. When generating UIIs the Contractor shall use its (the Contractor’s) CAGE code as the unique enterprise identifier.

[Note: The above paragraph 7.4.2 is not a firm requirement for this procurement and may be removed from the final solicitation.]

8.

Contract Implementation Phases

8.1 Phase 1 – Service Initiation and Testing

Initially the IUID Data Processing and Management Systems shall be set up for access by a limited number of users in the AFEMS community. During this phase the all system capabilities will be tested and corrective action shall be taken by the Contractor to correct any system errors and make system configuration improvements. During this period the Government anticipates ordering approximately 25,000 IUID Data Labels. This phase will include all four objectives, if development is required, otherwise it will include only Phases 1, 2, and 4.

8.1 Phase 2 – Full Operation with Expanded User Base

In Phase 2 the Contractor shall perform all tasks required to meet the objectives of Phases 1, 2, and 4 for and expanded AFEMS clientele and other Air Force offices (under AIT PMO oversight) not connected to the AFEMS project. During this period the Government anticipates ordering as many as 5.2 million IUID Data Labels.

9.

Quality Assurance and Quality Control

9.1 Contractor QA/QC Responsibility

The Contractor shall be responsible for quality assurance and quality control of all deliverables and of the operation of the IUID Data Label Processing and Management System.

9.2 Quality Assurance Surveillance Plan (QASP) The Contractor shall be responsible for developing and delivering a Quality Assurance Surveillance Plan (QASP). The Government will evaluate the Contractor performance in accordance with the (QASP). The QASP shall set forth the quality verification procedures and standards for all deliverables. An example regarding IUID Data Labels should read as follows: The Contractor is expected to verify the quality and machine-readability of all IUID Data Labels prior to shipment. For data labels created in sheets, verification of the labels on each corner will be considered verification of the entire uncut sheet. Quality assurance verification statistics will be maintained by the contractor for periodic government review.

10.

Special Performance Requirements 10.1 Location of Work

The Contractor shall perform all work at it own facility.

10.2 Time of Work

The Contractor shall be responsible for managing its workforce. However, the Contractor shall provide phone support as stipulated in Paragraph 7.2.1.4. Additionally, the Contractor shall insure that the Web based IUID Data Label Processing and Management System is available 24 hours a day, every day of the year with 99.9 percent up-time between the hours of 7 A.M and 8 P.M Eastern time.

10.3 Performance of Services During a Crisis Declared by the National Command Authority or Overseas Combatant Commander

Not Applicable 10.4 Travel

The Contractor shall conduct travel in support of this PWS as identified and authorized by the Government. Travel shall be provided on a cost-reimbursement basis in accordance with the Federal Joint Travel Regulations (JTR). All travel shall be coordinated in advance with the AF AIT PMO and shall not exceed an expense of $10,000 annually.

[Note: The above paragraph 10.4 is not a firm requirement for this procurement and may be removed from the final solicitation.]

10.5 Limitations on Contractor Performance

Not Applicable 10.6 Key Personnel

Key Personnel Designation is not applicable to this performance work statement.

Key Personnel are defined as those individuals who are so essential to the work being performed that the contractor shall not divert them to other projects or replaced them without receiving prior approval from the Contracting Officer.

10.7 Privacy Act Requirements

Work on this project may require that personnel have access to Privacy Information. The Contractor personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations.

10.8 Personal Services Compliance

Not Applicable 10.9 Rehabilitation Act Compliance (Section 508)

Any/all electronic and information technology (EIT) procured through this effort must meet the applicable accessibility standards at 36 CDR 1194. 36 CFR 1194 implements Section 508 of the Rehabilitation Act of 1973, as amended, and is viewable at http://www.section508.gov.

10.10 Security Requirements

10.10.1 Government Facility and Data Access Requirements - If needed, the Contract Manager or Alternate shall complete DD Form 1172-2, Application for Department of Defense Common Access Card-DEERS, May 2004 and DD Form 2842, DoD Public Key Infrastructure (PKI) Subscriber Certificate Acceptance and Acknowledgement of Responsibilities, September 2002, for each Contractor employee requiring access to WPAFB or any other Government installation. The Government shall provide a completed Identification Credential, AFMC Form 387, which shall be issued, displayed and surrendered as directed in AFI 31.101, The Air Force Installation Security Program March 2003.

10.10.2 Security Badges - The Contractor shall ensure all employees properly display and wear Identification (ID) Badges at all times during duty performance. Contractor employees shall be easily recognized as Contractor employees with an ID Badge that includes, as a minimum, a person’s name, the name of the contractor, and the word “Contractor.” Each employee shall wear the Badge on the outer clothing on the front of the body between the neck and the waist so that the ID Badge is visible at all times. (Note: If wearing an ID Badge jeopardizes safety of contractor personnel in performance of their duties, the Badge will be removed until the job is completed and the hazard is no longer present.)

10.10.3 Security Provision Compliance - The Contractor shall observe and comply with all USAF, AFMC, and site specific security provisions in effect during the contract period of performance.

10.11 Disclosure of Information

Information made available to the contractor by the Government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the written agreement of the AIT PMO.

The contractor agrees to assume responsibility for protecting the confidentiality of Government records, which are not public information. Each contractor or employee of the contractor to whom information may be made available or disclosed shall be notified in writing by the contractor. The contractor or employee of the Contractor will sign a non-disclosure agreement supplied by the government acknowledging such information may be disclosed only for a purpose and to the extent authorized by the AIT PMO.

10.12 Limited Use of Data

Performance of this effort may require the contractor to access and use data and information proprietary to a Government agency or Government contractor which is of such a nature that its dissemination or use, other than in performance of this effort, would be adverse to the interests of the Government and/or others. Contractor and/or contractor personnel shall not divulge or release data or information developed or obtained in performance of this effort, until made public by the Government, except to authorized Government personnel who will be identified and given written approval by the AIT PMO. Nothing herein shall preclude the use of any data independently acquired by the contractor without such limitations or prohibit an agreement at no cost to the government between the contractor and the data owner which provides for greater rights to the contractor.

10.13 Productive Direct Labor Hours

If this contract includes the purchase of labor hours for system development, implementation, configuration, the Contractor shall be able to bill for labor hours at the rates established in the contract item and service schedule. The contractor can only charge the Government for “Productive Direct Labor Hours”. “Productive Direct Labor Hours” are defined as those hours expended by contractor personnel in performing work under this effort. This does not include sick leave, vacation, Government or contractor holidays, jury duty, military leave, or any other kind of administrative leave.

10.14 Payment for Unauthorized Work No payments will be made for any unauthorized supplies and/or services or for any unauthorized changes to the work specified herein. This includes any services performed by the contractor at their own volition or at the request of an individual other than a duly appointed CO. Only a duly appointed CO is authorized to change the specifications, terms, or conditions under this effort.

10.15 Description of Supporting Requirements (Supplies) 10.15.1 Operations and Maintenance Manuals - TBD 10.15.2 Warranty - TBD 10.15.3 Recommended Spare Parts List - TBD 10.15.4 Spare Parts - TBD 10.15.4 Training Manual - TBD 11.

Government Furnished Items 11.1 Data

11.1.1 The Government shall provide passwords and funding authorization codes to those Government personnel authorized to use the IUID Data Label System. These passwords and funding authorizations will be provided to the Contractor for system implementation.

11.1.2 The Air Force IUID PMO will provide to the Contractor the DoD guidelines and syntax for generating Unique Item Identifiers (UIIs). These guidelines and syntax shall be provided to the Contractor, in writing, within 5 business days after contract award.

11.1.3 The Air Force personnel who request IUID Data Labels shall provide the Contractor with data specific to the tangible asset being labeled for inclusion in the Unique Item Identifiers (UIIs). This data shall be provided as part of the request process.

11.1.4 Confidentiality and Non-Disclosure Agreement (example). This document shall be provided to the Contractor, in writing, within 5 business days after contract award or at other such time as required for contract performance as agreed between the parties. (Ref. Para. 10-11) 11.2 Equipment

Not Applicable

11.3 Materials

Not Applicable

11.4 Facilities

The Government will provide necessary and reasonable access to buildings, system equipment, hardware and software required, personnel, and will provide appropriate working space for Contractor personnel at the implementation sites as required.

12.

Special Requirement for Performance Eligibility

There are no special requirements that would preclude a vendor from being eligible to perform this requirement. However, please be aware of the security requirements that may be imposed on the Contractor during performance as found in Paragraph 10.10, above.

13.

Government Delays in Reviewing Deliverables or Furnishing Items

If contractor performance or submission of deliverables is contingent upon receipt of government furnished items (data, equipment, materials, facilities, and support) or input, or upon government review and approval of interim items or draft documents (collectively referred to as Government Performance), the government shall specify when it will provide such items or input, or the time it will need to perform reviews or give approvals. If the government fails to meet item, input, review, or approval deadlines, contractor performance or submission of deliverables shall automatically be extended one calendar day for each day of government delay. The contractor shall promptly advise the Contracting Officer of any delays in receipt of government furnished items, input, reviews, or approvals. If dates for Government performance are not specified in this contract/order or associated task directives, this clause will not apply, and contractor delays must be handled or negotiated under other provisions of this contract or order.

14.

Notices

CONTRACTING OFFICER’S REPRESENTATIVE

The work to be performed under this contract is subject to monitoring by an assigned Contracting Officer’s Technical Representative (COTR). The COTR appointment letter, outlining the COTR responsibilities under this contract/order, will be provided to the contractor under separate cover. Questions concerning COTR appointments should be addressed to the Contracting Officer.

15.

Contact Information

15.1 Contractor Contacts

Contractor contact information will be added to this section upon contract award.

15.2 Government Contacts

15.2.1 Correspondence

To promote timely and effective administration, correspondence shall be subject to the following procedures:

· Technical correspondence (where technical issues relating to compliance with the requirements herein) shall be addressed to the COTR with an information copy to the CO.

· All other correspondence, including invoices, (that which proposed or otherwise involves waivers, deviations, or modifications to the requirements, terms or conditions of this performance work statement) shall be addressed to the CO with an information copy to the COTR.

15.2.2 Air Force AIT Program Manager Mr. Mark Reboulet is the Air Force AIT Program Manager.

15.2.3 Air Force AIT PMO Representative

The AF AIT PMO representative for this project will be:

Edwin Chase, Project Manager

AFMC LSO/LOA

5215 Thurlow Street, Suite 4 Building 70, Area C

Wright-Patterson AFB OH 45433-5006

Phone: (937) 257-7186, DSN 787-7186.

Email: edwin.chase@wpafb.af.mil.

15.2.4 Contracting Officer’s Technical Representative (COTR) [To be provided on or before the time of contract award.]

15.2.4 Contracting Officer Mr. Eben Greybourne

GSA Region 5, 5ZAQ, Room 3280

230 South Dearborn Street

Chicago, Illinois 60604

Phone: 312 / 886-3811

Fax: 312 / 886-3827

E-mail: eben.greybourne@gsa.gov 16.

Deliveries or Performance Requirements 16.1 52.252-2 Clauses Incorporated by Reference (FEB 1998)

This contract incorporates one or more Federal Acquisition Regulation (FAR) clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available.

16.2 Delivery Dates and Places

For purposes of this contract, three delivery schedules shall apply.

16.2.1 IUID Data Labels – IUID Data Labels shall be delivered at the time and to the location specified in each individual IUID Data Label Request. (Note: Per a function of the IUID Data Label Processing and Management System, the Government shall be notified immediately if requested deliver time and/or location can not be met.)

16.2.2 Data Items – Data items listed in the following Contract Data Requirements List (CDRL) shall be delivered at the times and to the locations indicated. The Contractor may propose an alternate delivery schedule; however, delivery dates (established at time of contract award) and places may be adjusted after contract award only with written authorization of the Contracting Officer. Upon delivery, all contractor deliverables will be the property of the government and, as such, will be delivered using non-proprietary information and formats. A detailed description and information pertaining to each data item is provided on the attached DD Form 1423-1s.

DATA ITEMS DELIVERY SCHEDULE

Table 1.6-1 Contract Data Requirements List (CDRL)

All items shall be delivered to location A, below.