FBODaily.com | FedBizOpps: MOD | 58 | Amendment 01 Motorola Dispatch Consoles - Amendment 1

FBO DAILY - FEDBIZOPPS ISSUE OF SEPTEMBER 18, 2016 FBO #5413
MODIFICATION

58 -- Amendment 01 Motorola Dispatch Consoles - Amendment 1

Notice Date: 9/16/2016
Notice Type: Modification/Amendment
NAICS: 334220 — Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing
Contracting Office: Department of the Air Force, Air Education and Training Command, Maxwell AFB Contracting Squadron, 50 LeMay Plaza South, Bldg 804, Maxwell AFB, Alabama, 36112-6334
ZIP Code: 36112-6334
Solicitation Number: F2X3C76193A001
Archive Date: 10/4/2016
Point of Contact: Marco Antonio G. Castaneda, Phone: 334-953-7461, Marcus Abram, Phone: 334-953-3526
E-Mail Address: Marcoantonio.Castaneda.ph@us.af.mil, marcus.abram@maxwell.af.mil
(Marcoantonio.Castaneda.ph@us.af.mil, marcus.abram@maxwell.af.mil)
Small Business Set-Aside: N/A
Description: Amendment 01 to Motorola Dispatch Consoles *****************************AMENDMENT 0001****************************** 1. The purpose of this amendment is to incorporate the following changes: a. Revise the "General Information" section to update DPN and Important Notes b. Revise the "Schedule Of Supplies/Services" section to update CLINs 0001 and 0002 c. Revise the "Delivery Information" section to update the Delivery Table d. Revise the "List of Attachments" to delete references to certain attachments and renumbered accordingly. e. Revise the "Instruction Preparation Instructions" and "Basis for Award" by updating various paragraphs. f. Revise Provision 52.212-3. g. Revise Attachment 1, Statement of Requirements paragraphs 4.3.1 - 4.3.3.4.5. h. Revise Attachment 2, Price List CLIN 0002. i. Extend the solicitation response date from 5:00 P.M. Central Daylight Time (CSDT), Friday 16 September 2016 to 5:00 P.M. Central Daylight Time (CDT) Monday 19 September 2016. 2. All changes to this amendment are identified by strikethrough, barline, and/or underline. 3. Offerors who submit an updated quote, must do so IAW with the terms and conditions of this solicitation. If an offeror does not intend on submitting a revised quote, the offeror must respond acknowledge receipt of this amendment in writing by stating "No Changes" will be submitted. 4. Responses to this amendment shall be provided by 5:00 P.M. Central Standard Daylight Time (C S DT), Friday Monday, 16 19 September 2016. 5. POCs for this amendment are: SrA Marco Castaneda, Contract Specialist; Phone (334) 953-7461, FAX (334) 953-3543 and Marcus Abram, Lead Contract Specialist, Phone: 334-953-3526. GENERAL INFORMATION The 42nd Contracting Squadron, 50 LeMay Plaza, Building 804, Maxwell AFB, AL has a requirement to purchase items as described in this document. This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in FAR Subpart 12.6 as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued. This requirement is issued as a Request for Quote (RFQ) Motorola Dispatch Consoles and Consolettes. The solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 2005-89 (15 Aug 2016) and the DPN 20160811 20160830 effective 11 30 Aug 2016. A Firm Fixed Price contract award will be made in accordance with the following: NAICS Code: 334220 ; size standard: 1, 250 employees The Defense Priorities and Allocations System rating is C9E. IMPORTANT NOTES : •1. THE GOVERNMENT IS SOLICITING FOR "OPEN MARKET" QUOTES ONLY. GENERAL SERVICES ADMINISTRATION (GSA) QUOTES WILL NOT BE CONSIDERED. •2. ALL PRODUCTS MUST BE NEW; NO REFURBISHED OR USED ITEMS WILL BE ACCEPTED. •3. ALL OFFERORS MUST BE AN AUTHORIZED MOTOROLA "PRODUCTS AND SERVICE PROVIDER" and comply with Sections 4 to 10 on the attached Statement of requirement SOR. 4. DUE NETWORK PROBLEMS, OFFERORS ARE ENCOURAGED TO VALIDATE RECEIPT OF THEIR RESPONSES TO THIS SOLICITATION (SEE INSTRUCTIONS TO OFFEORS, PARA 1.8.). NATURE OF ACQUISITON: Maxwell Air Force Base has a requirement to purchase the MOTOROLA brand name items listed below in the "Schedule of Supplies/Services" for the primary and alternate Emergency Communication Centers (ECC) of at Maxwell-Gunther Air Force Base. The Redacted brand name justification attached. This procurement will be awarded as full and open competition under Simplified Acquisition Procedures. SCHEDULE OF SUPPLIES/SERVICES : CLIN 0001 The contractor shall provide Motorola Dispatch Consoles and Motorola Consolettes in accordance with (IAW) Attachment 1, Statement of Requirements (SOR) paragraphs 4.1.1 - 4.6 and provide pricing on Attachment 2, Price List. Qty: 1 Lot CLIN 0002 The contractor shall provide system integration, installation, acceptance testing and training of all equipment IAW Attachment 1, SOR paragraphs 6 - 9. and provide pricing on Attachment 2, Price List. Qty: 1 Each DELIVERY INFORMATION: Shipping will be FOB Destination. The following items will be delivered to the location listed in the Delivery Table: Delivery Table Description Qty Location Motorola MCC 7100 IP Dispatch Consoles for the ECC 4 Maxwell AFB, AL Bldg 929 Motorola MCC 7100 IP Dispatch Console for the Alternate ECC 2 Maxwell-Gunter Annex Bldg 834 HF R1 APX 7500 Consolettes 3 Maxwell AFB, AL Bldg 929 UHF R1 and 7/800 MHz Dual Band APX 7500 Consolettes 1 Maxwell AFB, AL Bldg 929 UHF R1 APX 7500 Consolettes 3 Maxwell-Gunter Annex Bldg 834 UHF R1 and 7/800 MHz Dual Band APX 7500 Consolettes 1 Maxwell-Gunter Annex Bldg 834 Description Qty Location Motorola MCC 7100 IP Dispatch Console for the Alternate ECC 2 Maxwell-Gunter Annex Bldg 834 UHF R1 APX 7500 Consolettes 3 Maxwell-Gunter Annex Bldg 834 UHF R1 and 7/800 MHz Dual Band APX 7500 Consolettes 1 Maxwell-Gunter Annex Bldg 834 Motorola MCC 7100 IP Dispatch Consoles for the ECC 4 Maxwell AFB, AL Bldg 929 HF R1 APX 7500 Consolettes 3 Maxwell AFB, AL Bldg 929 UHF R1 and 7/800 MHz Dual Band APX 7500 Consolettes 1 Maxwell AFB, AL Bldg 929 Attachment(s): 1. Contract Clauses 2 1. Statement of Requirements (SOR) 3 2. Price List 4. Contract Provisions 5 3. Redacted Brand Name Justification 1.0 INSTRUCTIONS TO OFFERORS: 1.1 To ensure timely and equitable evaluation of quotes, offerors must comply with instructions contained herein. Quotes must be complete, self-sufficient, and respond directly to the requirements of this RFQ. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. 1.2 Offerors must submit a dated quote on company letterhead with unit prices and extended prices recorded on Attachment 2, Price List in response to this solicitation. In doing so and without taking any exception to the requirements of this RFQ, including specifications included in the SOR the vendor contractor accedes to all solicitation requirements. 1.3 The contractor items recorded on Attachment 2, Price List must meet the minimum requirements referenced in Attachment 2 1, SOR paragraphs 4. 1 3. 1 - 4. 3.2.3 6. 1.4 Project Milestone Plan (PMP) : The contractor offeror shall provide a PMP that shows a general timeline from the effective date of the delivery order to the date products are to be delivered to the location identified in this solicitation. The PMP shall include, at a minimum, a timeline for: Description Days after Delivery Order Product Ordering Product Delivery Configuration/Installation Training Total # Number of Days to Contract Completion 1.5 The offeror shall complete only paragraph (b) of provision at FAR 52.212-3, Alternate I, Offeror Representations and Certifications - Commercial Items provision if the Offeror has completed the annual representations and certification electronically via the System for Award Management (SAM) Web site accessed through http://www.sam.gov/portal. If the Offeror has not completed the annual representations and certifications electronically, the Offeror shall complete only paragraphs (c) through (r) of this provision. 1.6 Interested parties capable of providing the requirement must submit a written quote to include discount terms, tax identification number, cage code, and DUNS. 1.7 To be eligible to receive an award resulting from this RFQ, contractors must be registered in the DoD Systems for Award Management database, no exceptions. To register, please visit http://www.sam.gov or by calling 1-866-606-8220. 1.8 Responses to this notice shall be provided in writing via e-mail to SrA Marco Castaneda at marco_antonio.castaneda@us.af.mil or Marcus Abram at marcus.abram@us.af.mil. All responses shall be received NLT 4:00 PM Central Standard Time (CST) on 16 Sep 5:00 P.M. Central Standard Daylight Time (C S DT), Friday Monday 16 19 September 2016. Email is the preferred method. 2.0 BASIS FOR CONTRACT AWARD This is a competitive best value acquisition utilizing Simplified Acquisition Procedures authorized by FAR 13.5, "Simplified Procedures for Certain Commercial Items." Technical acceptability and price be the two determining criteria for award. Award will be made to the lowest priced offer that has an acceptable technical rating. For quotes determined technically acceptable, a best value selection will be based on price. The evaluation will proceed as follows: 2.1 Award will be based on technical acceptability and price. For quotes determined technically acceptable, a best value selection will be based on price. 2. 1 2.Technical Acceptability. Initially, the Government's technical evaluation team shall evaluate each contractor's quote against the following technical criteria: The contractor items recorded on Attachment 2, Price List must clearly meet the minimum requirements referenced in Attachment 2 1, SOR paragraphs 4.1.1 - 4.6. 2. 1 2.1. The Government will evaluate for completeness Attachment 2, Price List to ensure the minimum requirements referenced in Attachment 2 1, SOR paragraphs 4.3. - 4.3.2.3. 4.1.1 - 4.6 have been met. 2. 1 2.2. Project Milestone Plan (PMP) : The contractor offeror's shall provide a PMP will be evaluated for reasonableness to ensure a general that shows a timeline from the effective date of the delivery order to the date products are to be delivered to the location identified in this solicitation has been met. The PMP shall include, at a minimum, a timeline for: Description Days after Delivery Order Product Ordering Product Delivery Configuration/Installation Training Total # of Days to Contract Completion Quotes will be assigned ratings of acceptable (clearly meets the minimum requirement) or unacceptable (does not clearly meet the minimum requirements). 2.3. Price: Finally, t he Government may use any of the following price analysis techniques IAW FAR 13.106-3(a) to determine price reasonableness: competitive quotes, comparison of the proposed price with prices found reasonable on previous purchases, a comparison with similar items in a related industry, comparison to an independent Government estimate, or any other reasonable basis. Attachment 1 - Contract Clauses CONTRACT TERMS AND CONDITIONS: The following clauses apply: By Reference: 52.202-1 Definitions (NOV 2013) 52.203-3 Gratuities (APR 1984) 52.203-6 Alt I Restrictions on Subcontractor Sales to the Government (SEP 2006) 52.203-12 Limitation on Payments to Influence Certain Federal Transactions (OCT 2010) 52.203-17 Contractor Employee Whistleblower Rights and Requirement to Inform Employees of Whistleblower Rights (APR 2014) 52.204-4 Printed or Copied Double-Sided on Postconsumer Fiber Content Paper (MAY 2011) 52.204-9 Personal Identity Verification of Contractor Personnel (Jan 2011) 52.204-10 Reporting Executive Compensation and First-Tier Subcontract Awards (OCT 2015) 52.204-13 System for Award Management Maintenance (JUL 2013) 52.209-6 Protecting the Government's Interest When Subcontracting with Contractors Debarred, Suspended, or Proposed for Debarment (OCT 2015) 52.209-9 Updates of Publicly Available Information Regarding Responsibility Matters (JUL 2013) 52.212-4 Contract Terms and Conditions -- Commercial Items (MAY 2015) 52.219-4 Notice of Price Evaluation for HUBZone Small Business Concerns (OCT 2014) 52.219-8 Utilization of Small Business Concerns (OCT 2014) 52.219-28 Post-Award Small Business Program Representation (JUL 2013) 52.222-19 Child Labor-Cooperation with Authorities and Remedies (FEB 2016) 52.222-22 Previous Contracts and Compliance Reports (FEB 1999) 52.223-18 Encouraging Contractor Policies to Ban Text Messaging While Driving (AUG 2011) 52.225-13 Restriction on Certain Foreign Purchases (JUN 2008) 52.232-18 Availability of Funds (Apr 1984) 52.232-33 Payment by Electronic Funds Transfer-- System for Award Management (JUL 2013) 52.232-39 Unenforceability of Unauthorized Obligations (JUN 2013) 52.232-40 Providing Accelerated Payments to Small Business Subcontractors (DEC 2013) 52.233-3 Protest after Award (AUG 1996) 52.233-4 Applicable Law for Breach of Contract Claim (OCT 2004) 52.242-13 Bankruptcy (JUL 1995) 252.203-7000 Requirements Relating To Compensation of Former D o D Officials (SEP 2011) 252.203-7002 Requirement To Inform Employees Of Whistleblower Rights (SEP 2013) 252.204-7003 Control Of Government Personnel Work Product (APR 1992) 252.204-7012 Safeguarding Of Unclassified Controlled Technical Information (DEC 2015) 252.205-7000 Provision of Information to Cooperative Agreement Holders (DEC 1991) 252.209-7004 Subcontracting With Firms That Are Owned Or Controlled By The Government Of A Country that is a State Sponsor of Terrorism (OCT 2015) 252.211-7008 Use of Government-Assigned Serial Numbers (SEP 2010) 252.223-7006 Prohibition on Storage, Treatment, and Disposal of Toxic or Hazardous Materials Basic (Sep 2014) 252.223-7008 Prohibition Of Hexavalent Chromium (JUN 2013) 252.225-7012 Preference For Certain Domestic Commodities (AUG 2016) 252.226-7001 Utilization Of Indian Organizations, Indian-Owned Economic Enterprises, And Native Hawaiian Small Business Concerns (SEP 2004) 252.232-7003 Electronic Submission Of Payment Requests And Receiving Reports (JUN 2012) 252.232-7010 Levies On Contract Payments (DEC 2006) 252.243-7001 Pricing Of Contract Modifications (DEC 1991) 252.243-7002 Requests For Equitable Adjustment (DEC 2012) 252.244-7000 Subcontracts For Commercial Items And Commercial Components (DoD Contracts) (JUN 2013) 252.247-7023 Transportation Of Supplies By Sea-Basic (APR 2014) By Full Text: 52.252-2 -- Clauses Incorporated by Reference. (FEB 1998) This contract incorporates one or more 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. Also, the full text of a clause may be accessed electronically at this/these address(es): http://farsite.hill.af.mil/ (End of Clause) 52.252-6 Authorized Deviations in Clauses (APR 1984) (a) The use in this solicitation or contract of any Federal Acquisition Regulation (48 CFR Chapter 1) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the date of the clause. (b) The use in this solicitation or contract of any Defense Federal Acquisition Regulation Supplement (48 CFR Chapter 2) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the name of the regulation. (End of Clause) 252.211-7003 Item Unique Identification and Valuation (MAR 2016) (a) Definitions. As used in this clause- "Automatic identification device" means a device, such as a reader or interrogator, used to retrieve data encoded on machine-readable media. "Concatenated unique item identifier" means- (1) For items that are serialized within the enterprise identifier, the linking together of the unique identifier data elements in order of the issuing agency code, enterprise identifier, and unique serial number within the enterprise identifier; or (2) For items that are serialized within the original part, lot, or batch number, the linking together of the unique identifier data elements in order of the issuing agency code; enterprise identifier; original part, lot, or batch number; and serial number within the original part, lot, or batch number. "Data matrix" means a two-dimensional matrix symbology, which is made up of square or, in some cases, round modules arranged within a perimeter finder pattern and uses the Error Checking and Correction 200 (ECC200) specification found within International Standards Organization (ISO)/International Electrotechnical Commission (IEC) 16022. "Data qualifier" means a specified character (or string of characters) that immediately precedes a data field that defines the general category or intended use of the data that follows. "DoD recognized unique identification equivalent" means a unique identification method that is in commercial use and has been recognized by DoD. All DoD recognized unique identification equivalents are listed at http://www.acq.osd.mil/dpap/pdi/uid/iuid_equivalents.html. "DoD item unique identification" means a system of marking items delivered to DoD with unique item identifiers that have machine-readable data elements to distinguish an item from all other like and unlike items. For items that are serialized within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier and a unique serial number. For items that are serialized within the part, lot, or batch number within the enterprise identifier, the unique item identifier shall include the data elements of the enterprise identifier; the original part, lot, or batch number; and the serial number. "Enterprise" means the entity (e.g., a manufacturer or vendor contractor ) responsible for assigning unique item identifiers to items. "Enterprise identifier" means a code that is uniquely assigned to an enterprise by an issuing agency. "Government's unit acquisition cost" means- (1) For fixed-price type line, subline, or exhibit line items, the unit price identified in the contract at the time of delivery; (2) For cost-type or undefinitized line, subline, or exhibit line items, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery; and (3) For items produced under a time-and-materials contract, the Contractor's estimated fully burdened unit cost to the Government at the time of delivery. "Issuing agency" means an organization responsible for assigning a globally unique identifier to an enterprise, as indicated in the Register of Issuing Agency Codes for ISO/IEC 15459, located at http://www.aimglobal.org/?Reg_Authority15459. "Issuing agency code" means a code that designates the registration (or controlling) authority for the enterprise identifier. "Item" means a single hardware article or a single unit formed by a grouping of subassemblies, components, or constituent parts. "Lot or batch number" means an identifying number assigned by the enterprise to a designated group of items, usually referred to as either a lot or a batch, all of which were manufactured under identical conditions. "Machine-readable" means an automatic identification technology media, such as bar codes, contact memory buttons, radio frequency identification, or optical memory cards. "Original part number" means a combination of numbers or letters assigned by the enterprise at item creation to a class of items with the same form, fit, function, and interface. "Parent item" means the item assembly, intermediate component, or subassembly that has an embedded item with a unique item identifier or DoD recognized unique identification equivalent. "Serial number within the enterprise identifier" means a combination of numbers, letters, or symbols assigned by the enterprise to an item that provides for the differentiation of that item from any other like and unlike item and is never used again within the enterprise. "Serial number within the part, lot, or batch number" means a combination of numbers or letters assigned by the enterprise to an item that provides for the differentiation of that item from any other like item within a part, lot, or batch number assignment. "Serialization within the enterprise identifier" means each item produced is assigned a serial number that is unique among all the tangible items produced by the enterprise and is never used again. The enterprise is responsible for ensuring unique serialization within the enterprise identifier. "Serialization within the part, lot, or batch number" means each item of a particular part, lot, or batch number is assigned a unique serial number within that part, lot, or batch number assignment. The enterprise is responsible for ensuring unique serialization within the part, lot, or batch number within the enterprise identifier. "Type designation" means a combination of letters and numerals assigned by the Government to a major end item, assembly or subassembly, as appropriate, to provide a convenient means of differentiating between items having the same basic name and to indicate modifications and changes thereto. "Unique item identifier" means a set of data elements marked on items that is globally unique and unambiguous. The term includes a concatenated unique item identifier or a DoD recognized unique identification equivalent. "Unique item identifier type" means a designator to indicate which method of uniquely identifying a part has been used. The current list of accepted unique item identifier types is maintained at http://www.acq.osd.mil/dpap/pdi/uid/uii_types.html. (b) The Contractor shall deliver all items under a contract line, subline, or exhibit line item. (c) Unique item identifier. (1) The Contractor shall provide a unique item identifier for the following: (i) Delivered items for which the Government's unit acquisition cost is $5,000 or more, except for the following line items: Contract Line, Subline, or Exhibit Line Item Number Item Description ___________________________________________________________________ ___________________________________________________________________ ___________________________________________________________________ (ii) Items for which the Government's unit acquisition cost is less than $5,000 that are identified in the Schedule or the following table: Contract Line, Subline, or Exhibit Line Item Number Item Description ___________________________________________________________________ ___________________________________________________________________ ___________________________________________________________________ (If items are identified in the Schedule, insert "See Schedule in this table.) (iii) Subassemblies, components, and parts embedded within delivered items, items with warranty requirements, DoD serially managed reparables and DoD serially managed nonreparables as specified in Attachment Number ____. (iv) Any item of special tooling or special test equipment as defined in FAR 2.101 that have been designated for preservation and storage for a Major Defense Acquisition Program as specified in Attachment Number ____. (v) Any item not included in (i), (ii), (iii), or (iv) for which the contractor creates and marks a unique item identifier for traceability. (2) The unique item identifier assignment and its component data element combination shall not be duplicated on any other item marked or registered in the DoD Item Unique Identification Registry by the contractor. (3) The unique item identifier component data elements shall be marked on an item using two dimensional data matrix symbology that complies with ISO/IEC International Standard 16022, Information technology - International symbology specification - Data matrix; ECC200 data matrix specification. (4) Data syntax and semantics of unique item identifiers. The Contractor shall ensure that- (i) The data elements (except issuing agency code) of the unique item identifier are encoded within the data matrix symbol that is marked on the item using one of the following three types of data qualifiers, as determined by the Contractor: (A) Application Identifiers (AIs) (Format Indicator 05 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology - EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard. (B) Data Identifiers (DIs) (Format Indicator 06 of ISO/IEC International Standard 15434), in accordance with ISO/IEC International Standard 15418, Information Technology - EAN/UCC Application Identifiers and Fact Data Identifiers and Maintenance and ANSI MH 10.8.2 Data Identifier and Application Identifier Standard. (C) Text Element Identifiers (TEIs) (Format Indicator 12 of ISO/IEC International Standard 15434), in accordance with the Air Transport Association Common Support Data Dictionary; and (ii) The encoded data elements of the unique item identifier conform to the transfer structure, syntax, and coding of messages and data formats specified for Format Indicators 05, 06, and 12 in ISO/IEC International Standard 15434, Information Technology - Transfer Syntax for High Capacity Automatic Data Capture Media. (5) Unique item identifier. (i) The Contractor shall- (A) Determine whether to- (1) Serialize within the enterprise identifier; (2) Serialize within the part, lot, or batch number; or (3) Use a DoD recognized unique identification equivalent (e.g. Vehicle Identification Number); and (B) Place the data elements of the unique item identifier (enterprise identifier; serial number; DoD recognized unique identification equivalent; and for serialization within the part, lot, or batch number only: original part, lot, or batch number) on items requiring marking by paragraph (c)(1) of this clause, based on the criteria provided in MIL-STD-130, Identification Marking of U.S. Military Property, latest version; (C) Label shipments, storage containers and packages that contain uniquely identified items in accordance with the requirements of MIL-STD-129, Military Marking for Shipment and Storage, latest version; and (D) Verify that the marks on items and labels on shipments, storage containers, and packages are machine readable and conform to the applicable standards. The contractor shall use an automatic identification technology device for this verification that has been programmed to the requirements of Appendix A, MIL-STD-130, latest version. (ii) The issuing agency code- (A) Shall not be placed on the item; and (B) Shall be derived from the data qualifier for the enterprise identifier. (d) For each item that requires item unique identification under paragraph (c)(1)(i), (ii), or (iv) of this clause or when item unique identification is provided under paragraph (c)(1)(v), in addition to the information provided as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the Contractor shall report at the time of delivery, as part of the Material Inspection and Receiving Report, the following information: (1) Unique item identifier. (2) Unique item identifier type. (3) Issuing agency code (if concatenated unique item identifier is used). (4) Enterprise identifier (if concatenated unique item identifier is used). (5) Original part number (if there is serialization within the original part number). (6) Lot or batch number (if there is serialization within the lot or batch number). (7) Current part number (optional and only if not the same as the original part number). (8) Current part number effective date (optional and only if current part number is used). (9) Serial number (if concatenated unique item identifier is used). (10) Government's unit acquisition cost. (11) Unit of measure. (12) Type designation of the item as specified in the contract schedule, if any. (13) Whether the item is an item of Special Tooling or Special Test Equipment. (14) Whether the item is covered by a warranty. (e) For embedded subassemblies, components, and parts that require DoD item unique identification under paragraph (c)(1)(iii) of this clause or when item unique identification is provided under paragraph (c)(1)(v), the Contractor shall report as part of the Material Inspection and Receiving Report specified elsewhere in this contract, the following information: (1) Unique item identifier of the parent item under paragraph (c)(1) of this clause that contains the embedded subassembly, component, or part. (2) Unique item identifier of the embedded subassembly, component, or part. (3) Unique item identifier type.** (4) Issuing agency code (if concatenated unique item identifier is used).** (5) Enterprise identifier (if concatenated unique item identifier is used).** (6) Original part number (if there is serialization within the original part number).** (7) Lot or batch number (if there is serialization within the lot or batch number).** (8) Current part number (optional and only if not the same as the original part number).** (9) Current part number effective date (optional and only if current part number is used).** (10) Serial number (if concatenated unique item identifier is used).** (11) Description. ** Once per item. (f) The Contractor shall submit the information required by paragraphs (d) and (e) of this clause as follows: (1) End items shall be reported using the receiving report capability in Wide Area WorkFlow (WAWF) in accordance with the clause at 252.232-7003. If WAWF is not required by this contract, and the contractor is not using WAWF, follow the procedures at http://dodprocurementtoolbox.com/site/uidregistry/. (2) Embedded items shall be reported by one of the following methods- (i) Use of the embedded items capability in WAWF; (ii) Direct data submission to the IUID Registry following the procedures and formats at http://dodprocurementtoolbox.com/site/uidregistry/ ; or (iii) Via WAWF as a deliverable attachment for exhibit line item number (fill in) ___, Unique Item Identifier Report for Embedded Items, Contract Data Requirements List, DD Form 1423. (g) Subcontracts. If the Contractor acquires by subcontract, any item(s) for which item unique identification is required in accordance with paragraph (c)(1) of this clause, the Contractor shall include this clause, including this paragraph (g), in the applicable subcontract(s), including subcontracts for commercial items. (End of clause) 252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013) (a) Definitions. As used in this clause-- Department of Defense Activity Address Code (DoDAAC) is a six position code that uniquely identifies a unit, activity, or organization. Document type means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF). Local processing office (LPO) is the office responsible for payment certification when payment certification is done external to the entitlement system. (b) Electronic invoicing. The WAWF system is the method to electronically process vendor contractor payment requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports. (c) WAWF access. To access WAWF, the Contractor shall-- (1) Have a designated electronic business point of contact in the System for Award Management at https://www.acquisition.gov; and (2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this Web site. (d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the "Web Based Training" link on the WAWF home page at https://wawf.eb.mil/. (e) WAWF methods of document submission. Document submissions may be via Web entry, Electronic Data Interchange, or File Transfer Protocol. (f) WAWF payment instructions. The Contractor must use the following information when submitting payment requests and receiving reports in WAWF for this contract/order: (1) Document type. The Contractor shall use the following document type(s). Invoice and Receiving Report (Combo) (2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in WAWF, as specified by the contracting officer. Inspection location: Government Acceptance location: Government (3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system. Routing Data Table* -------------------------------------------------------------------------------------------- Field Name in WAWF Data to be entered in WAWF -------------------------------------------------------------------------------------------- Pay Official DoDAAC F87700 Issue By DoDAAC FA3300 Admin DoDAAC FA3300 Inspect By DoDAAC F2X3C7 Ship To Code F2X3C7 Ship From Code Not applicable. Mark For Code Not applicable. Service Approver (DoDAAC) Not applicable. Service Acceptor (DoDAAC) F2X3C7 Accept at Other DoDAAC Not applicable. LPO DoDAAC Not applicable. DCAA Auditor DoDAAC Not applicable. Other DoDAAC(s) Not applicable. -------------------------------------------------------------------------------------------- (4) Payment request and supporting documentation. The Contractor shall ensure a payment request includes appropriate contract line item and subline item descriptions of the work performed or supplies delivered, unit price/cost per unit, fee (if applicable), and all relevant back-up documentation, as defined in DFARS Appendix F, (e.g. timesheets) in support of each payment request. (5) WAWF email notifications. The Contractor shall enter the email address identified below in the "Send Additional Email Notifications" field of WAWF once a document is submitted in the system. sandra.turner.1@us.af.mil marco_antonio.castaneda@us.af.mi reginald.sprouse@us.af.mil (g) WAWF point of contact. (1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact. Not applicable. (2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988. (End of clause) 5352.201-9101 OMBUDSMAN JUN 2016 (a) An ombudsman has been appointed to hear and facilitate the resolution of concerns from offerors, potential offerors, and others for this acquisition. When requested, the ombudsman will maintain strict confidentiality as to the source of the concern. The existence of the ombudsman does not affect the authority of the program manager, contracting officer, or source selection official. Further, the ombudsman does not participate in the evaluation of proposals, the source selection process, or the adjudication of protests or formal contract disputes. The ombudsman may refer the interested party to another official who can resolve the concern. (b) Before consulting with an ombudsman, interested parties must first address their concerns, issues, disagreements, and/or recommendations to the contracting officer for resolution. Consulting an ombudsman does not alter or postpone the timelines for any other processes (e.g., agency level bid protests, GAO bid protests, requests for debriefings, employee-employer actions, contests of OMB Circular A-76 competition performance decisions). (c) If resolution cannot be made by the contracting officer, the interested party may contact the ombudsman, Primary: Mr. David E. Jones, Deputy Chief, Contracting Division, HQ AFICA/KT; Alternate: Mr. Stephen G. Smith, Chief, Acquisition Support Branch, HQ AFICA/KTC; Address: 2035 First Street West, Ste 1, JBSA Randolph AFB TX 78150-4324; Telephone Numbers: (210) 652-7907 or (210) 652-7075; and E-mail Addresses: david.jones.3@us.af.mil or stephen.smith@us.af.mil. Concerns, issues, disagreements, and recommendations that cannot be resolved at the Center/MAJCOM/DRU/SMC ombudsman level, may be brought by the interested party for further consideration to the Air Force ombudsman, Associate Deputy Assistant Secretary (ADAS) (Contracting), SAF/AQC, 1060 Air Force Pentagon, Washington DC 20330-1060, phone number (571) 256-2395, facsimile number (571) 256-2431. (d) The ombudsman has no authority to render a decision that binds the agency. (e) Do not contact the ombudsman to request copies of the solicitation, verify offer due date, or clarify technical requirements. Such inquiries shall be directed to the Contracting Officer. (End of clause) The following provisions apply: By Reference: 52.203-11 Certification and Disclosure Regarding Payments to Influence Certain Federal Transactions (SEP 2007) 52.204-7 System for Award Management (JUL 2013) 52.209-7 Information Regarding Responsibility Matters (JUL 2013) 52.212-1 Instructions to Offerors -- Commercial Items (OCT 2015) 52.225-25 Prohibition on Contracting with Entities Engaging in Certain Activities or Transactions Relating to Iran-Representation and Certifications (OCT 2015) 252.204-7004 Alternate A, System For Award Management (FEB 2014) 252.204-7011 Alternative Line Item Structure (SEP 2011) 252.205-7000 Provision Of Information To Cooperative Agreement Holders (DEC 1991) 252.211-7006 Passive Radio Frequency Identification (JUN 2016) 252.215-7007 Notice Of Intent To Resolicit (JUN 2012) 252.215-7008 Only One Offer (OCT 2013) By Full Text: 52.212-3, Alt 1 -- Offeror Representations and Certifications -- Commercial Items. (JUL 2016) with its Alternate 1 ( Feb 2000) Offerors are reminded that Representations and Certifications are maintained at the following website: https://www.sam.gov/. In the event Representations and Certifications are not on file, Offerors must include a completed copy of the provisions at FAR Part 52 or on on-line at http://farsite.hill.af.mil. (May 2014) 52.233-2 -- Service of Protest. (SEP 2006) (a) Protests, as defined in section 33.101 of the Federal Acquisition Regulation, that are filed directly with an agency, and copies of any protests that are filed with the Government Accountability Office (GAO), shall be served on the Contracting Officer (addressed as follows) by obtaining written and dated acknowledgment of receipt from: Sandra K. Turner 50 South LeMay Plaza Bldg 804 Maxwell AFB, Al 36112. (b) The copy of any protest shall be received in the office designated above within one day of filing a protest with the GAO. (End of Provision) 52.252-1 -- Solicitation Provisions Incorporated by Reference. (FEB 1998) This solicitation incorporates one or more solicitation provisions 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. The offeror is cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at this/these address(es): http://farsite.hill.af.mil/ (End of Provision) Attachment 2 1 : Maxwell Air Force Base Statement of Requirements (SOR) For Installation Command and Control Upgrade Enterprise Land-Mobile Radio Command & Control Upgrade Date: 23 August 2016 CONTENTS SECTION 1............ PURPOSE SECTION 2............. EXECUTIVE SUMMARY SECTION 3............. PROJECT OVERVIEW SECTION 4............. BASIC SYSTEM REQUIREMENTS 4.4............. IP-BASED DISPATCH 4.5.............GUNTER ANNEX AUXILIARY INPUTS AND OUTPUTS 4.3............ SOLUTION CONNECTIVITY SECTION 5.............INFORMATION ASSURANCE SECTION 6.............SYSTEM INTEGRATION SECTION 7.............INSTALLATION SECTION 8.............ACCEPTANCE TESTING SECTION 9.............PERSONNEL TRAINING SECTION 10............WARRANTY LIST OF SOR ATTACHMENTS Attachment 1 - Detailed Product Specifications Attachment 2 - Drawings Attachment 1 STATEMENT OF REQUIREMENTS (SOR) Emergency Communication Center/C2 ELMR Upgrade 1. PURPOSE: The contractor shall replace portions of the current Enterprise Land-Mobile-Radio (ELMR) equipment in the primary and alternate Emergency Communication Centers (ECC) that is at the end of sustainment lifecycle. Current Motorola Gold Elite consoles are at the end of their lifecycle and will not be compatible ELMR infrastructure, Project 25 (P25) capabilities, will not comply with C&A criteria in projected 2017 system upgrade. Upgrade will also include fire station alerting requirements as part of the critical infrastructure. Failure to support this equipment upgrade will hinder critical communications between emergency responders and other command and control (C2)/mission areas in support of emergency operations. There are considerable risks for the safety and security of personnel with limited C2 functionality. 1.1. Operator Positions shall be IP based (Motorola MCC-7100) and provide IP wire line End-to-End AES FIPS 140-2 Level 3 encryption between Maxwell AFB and the Motorola Core at Lackland AFB. The dispatch solution must be natively connected to the AETC Enterprise LMR system and cannot use a non-native Console Sub-System Interface (CSSI) or bridging connection. The consoles must be able to be administered and managed via the AETC Enterprise Radio Network Management Suite. 1.2. All encryption hardware and software/firmware shall be certified in accordance with the National Institute of Standards and Technology (NIST). All system encryption shall be managed by the same encryption management subsystem. For technology employing link-encryption; those locations where extension to the operator position is provided by media conversion with controllable access on the military installation, either due to space, cost, or existing security measures, the encryption requirement may be waived by the Government for that particular link. The consoles must be capable of being sustained to ensure ELMR system upgrades and Software patches are included at the same cadence as other elements on the Maxwell portion of the AETC system. 1.3. The proposed dispatch console must have the same Graphical User Interface (GUI) as the existing Gold Elite Consoles in order to minimize user training. Operator Positions shall include a laptop with (1) headset or operate on a traditional desktop computer with a keyboard, mouse, up to 8 audio speakers, and audio accessories. 1.4 At a minimum, each console should have the capability to monitor up to 20 simultaneous talk-paths and the ability to access talk-groups on the P25 channels via the AETC AFB Core. The Dispatch Consoles shall provide the ability for AETC bases to facilitate cooperative dispatching in the event of emergency situation. 1.5 The operator positions shall be capable of providing the following features: 1.5.1 Aliasing 1.5.2 Announcement Group Calls 1.5.3 Auxiliary Input / Output Control via GFE SDM 3000 1.5.4 Call Alert 1.5.5 Conventional (mutual-aid) Interfaces via CCGW 1.5.6 Emergency Calls 1.5.7 Instant Recall Recorder 1.5.8 Multi-Select 1.5.9 Over-the-Ethernet Rekeying 1.5.10 Private Calls 1.5.11 Talk-Group Text Messaging 1.5.12 Talk-Group Calls 1.5.13 Talk-Group Patch 1.5.14 VU Meter for click and drag on-screen functionality 2. EXECUITIVE SUMMARY: The current ELMR system operates in a hub-spoke fashion with the core for AETC being at Lackland AFB. The planned AETC ELMR system core (Hub) upgrade in 2017 will render Maxwell's current Motorola Gold Elite consoles obsolete. The Motorola Gold Elite consoles are at the end of life span. New ELMR dispatch consoles are required to replace antiquated existing Motorola Gold Elite consoles. C2/Emergency Management capability will be greatly hindered if upgrade is not accomplished since existing consoles will lose the capability to link with the ELMR network core system in the near future. Maxwell will replace 6 existing Motorola Gold Elite Consoles with new integrated P25 ELMR consoles equipped with hardened operating system (OS) and latest radio dispatch Graphical User Interface (GUI) at each dispatch location; integrated with existing ELMR network core located at JBSA-Lackland in San Antonio, TX; configure/network all equipment meeting all information assurance requirements; configure consoles to support all existing operational capabilities to include remote fire station alert tones/public address systems/bunkroom & vehicle stall lights/garage doors controls, functional talk groups, and back-up radio operations; configure Over the Air Rekeying (OTAR) computer to recognize/interface with the new consoles to allow required encryption; and extend TLMR network to console locations over Government furnished equipment (GFE) dark fiber. 3. PROJECT OVERVIEW. The information in this section is provided to assist the contractor in preparing responses to this solicitation and is for reference only. The contractor is responsible for verifying all information provided in this solicitation. The contractor shall provide all labor, material, equipment and services in support of the program. 3.1 The required Command and Control Upgrade will need to provide the following credentials: 3.1.1. An upgrade to the current ELMR system platform p roviding dependable, secure, secure communications for first responders and other users at Maxwell Air Force Base; 3.1.2. The ELMR upgrade is required to maintain the ELMR system characteristics and u ser knowledge base currently in-place ; 3.1.3. This upgrade shall be autonomous with the Maxwell AFB E LMR operations; 3.1.4. At project completion, shared sustainment and centralized system management will result in a reduction of the number of system administrators required for operation; 3.1.5. ELMR system upgrade will protect responder operations and information from unauthorized individuals and inhibit unauthorized system access, thus avoiding system risks. 4. BASIC SYSTEM REQUIREMENTS 4.1. The Command and Control Upgrade shall provide the following functionality following functionality : 4.1.1. The existing Maxwell AFB Console Subsystem shall be upgraded to the latest technology and connected to the AETC Core. Scalability and seamless connection to an IPbased enterprise zone core is essential. It is the intent of Maxwell AFB to leverage an existing master site in order to provide Project 25 (P25) Frequency Division Multiple Access (FDMA) trunked communications. 4.2. The contractor shall upgrade the current Gold Elite equipment at Maxwell AFB. The Gold Elite dispatch console will have to be replaced with dispatch consoles. The contractor shall utilize existing equipment, when feasible. 4.3. Based on the requirements outlined above, the essential design features shall include: 4.3.1. Maxwell AFB 4.3.1. 1. Four Motorola MCC 7100 IP Dispatch Consoles for the ECC, Bldg 929 on Maxwell AFB 4.3.3. Four mutual aid and fallback radios for the ECC, bldg. 929 4.3.3 1. 2.Three UHF R1 APX 7500 Consolettes 4.3.3 1.2 3. One UHF R1 and 7/800 MHz Dual Band APX 7500 Consolettes 4.3.2. Gunter Annex 4.3.2. 1. Two Motorola MCC 7100 IP Dispatch Console for the Alternate ECC, Bldg 834 Gunter Annex 4.3.3.3. Four mutual aid and fallback radios for the Gunter Annex, bldg. 834 4.3. 4 2. 2. Three UHF R1 APX 7500 Consolettes 4.3.23. 3.4.5 One UHF R1 and 7/800 MHz Dual Band APX 7500 Consolettes 4.4 IP-BASED DISPATCH The existing consoles will need to be replaced with Motorola MCC 7100 dispatch consoles; these consoles offer interoperability, sustainment savings and security advantages. For compatibility purposes, t he MCC 7100 consoles shall be required to allow for IPbased dispatching on the proposed network of ASTRO 25 RF sites. These console positions will also be required to interface with the ASTRO 25 network directly through a router at the dispatch site. Maxwell AFB is seeking to reduce the time required to learn and perform typical dispatch tasks. By utilizing the requested console, the base will be able to increase communications and security with integrated, endtoend AES voice encryption. The contractor will provide a Motorola MCC 7100 ELMR radio console that includes a certified workstation and touch screen monitor, a voice processing module, desktop speakers, two headphones, two headset jacks, two desktop gooseneck microphones and one footswitch. The MCC 7100 consoles shall provide the following features: •· Prioritized emergency calls that connect no matter how busy the network •· Endtoend encryption that keeps all communications secure •· Optimized voice quality that eliminates clipped or degraded audio •· Continuous high quality audio to include peak user ELMR network traffic loads •· ELMR user activation in fractions of a second regardless of system size •· Automated call traffic rerouting in the event of core and/or IPnetwork failure •· Enhanced dispatch performance and e fficient use of bandwidth with IP multicast technology •· Centralized configuration/fault management of ELMR consoles, user accounts and sites 4.5 GUNTER ANNEX AUXILIARY INPUTS AND OUTPUTS The MCC 7100 consoles at Gunter Annex will need to be able to access the trunked talk-groups on the Maxwell AFB system through the Graphical User Interface on the console. The system will require a Motorola SDM3000 Interface box that can enable the integration of fire station public address systems, activation (raising) of response vehicle doors and activation of bunkroom and vehicle stall lighting as needed to facilitate emergency response. The set-up and configuration will be similar to existing capability (SDM 3000) linking the Maxwell fire station, bldg. 1092 and primary ECC, bldg. 929. The contractor will identify limited site work at the Gunter Annex fire station, bldg. 834 to enable this integration. 4.6 SOLUTION CONNECTIVITY This upgrade requirement shall provide the ASTRO 25 system to leverage government furnished, fiberbased connectivity at each proposed LMR site. Ethernet routers will be needed for each site to serve as point of demarcation between Motorola furnished and Government furnished connectivity at that site. All Government furnished connections must meet Ethernet site link specifications. 5. INFORMATION ASSURANCE As a government agency, Maxwell AFB will need an upgrade system that is compliance with relevant IA regulations and legal requirements. This system will be required to operate with a Risk Management Framework (RMF) that optimizes an ASTRO 25 network's operational resilience and enables the components of the upgrade to comply with the relevant policies, procedures, processes, internal standards and security controls requirements. Existing and emerging DoD Information Assurance, NIST and DHS policies are to be consider when designing this communication solution. In addition, network security and data protection services shall be available to mitigate risk in the months and years following system acceptance. There should be an integration of current and future cyber-security requirements built in to the engineering of this ASTRO 25 product. The contractor will be responsible for implementing an information assurance program and for a defenseindepth security architecture that will protect the network. Engineering and technical services to perform configuration, hardening and documentation in support of the Information Assurance capabilities included in the proposed IA design is required. The proposed communication system must be sustained, expanded and managed over its lifecycle to address new or evolving security threats. Based on certification requirements, engineering must provide cyber-security professionals from the system architecture to product development; implementation and lifecycle support shall be offered to provide a compliant, secure LMR system that meets all stated operational, DoD, and National Institute of Standards and Technology (NIST) requirements. 6. SYSTEM INTEGRATION Implementation of the proposed system will require that The contractor shall provide a Project Manager as a single point of contact; this individual will work closely with the personnel of Maxwell AFB through each phase of the project to deliver a fully compliant solution with the expected level of quality. The contractor shall furnish the required cable and equipment to connect to the Government's designated circuit demarcation point. The contractor shall identify by location all demarcation points and responsibilities for both contractor and base. In addition to the Project Manager, a System Engineer will be responsible for the design of the technical solution that is focused on meeting the specific communications requirements. The design process may include information gathered during site surveys, user interviews and Radio Frequency coverage studies. After completing the design, the engineer shall be available to the personnel at Maxwell AFB t hroughout the rest of the implementation process, including activities such as preshipment integration, installation, and acceptance testing. Upon completion of equipment installation, contractor shall be responsible for an audit for compliance quality standards shall be performed.. Following the audit, a Federal System Technologist(s) (FST) the contractor will be required to perform final infield adjustments of the system infrastructure to ensure optimal operation and functionality. Personnel of Maxwell AFB, Fire Department, Security Forces, and Communications Sq u adron will observe the audit. 7. INSTALLATION Maxwell AFB requires that all work performed must be in compliance with commercial practices, applicable manufacturer installation and maintenance manuals. Implementation of the Standards and Guidelines for Communication Sites (R56) procedures shall be utilized. These published standards draw from numerous sources, including American National Standards Institute (ANSI), FAA, Institute of Electrical and Electronics Engineers (IEEE), Mil Standards, National Electrical Manufacturers Association (NEMA), National Fire Protection Association (NFPA), Telecommunications Industry Association (TIA), Electronic Industries Alliance (EIA), Occupational Safety & Health Administration (OHSA) and Underwriters Laboratories (UL), and conform to established commercial standards within the communications industry. Subcontractors used in the installation process shall be well established in the wireless communications solutions community. The Project Manager will be required to work with the selected subcontractors during installation to ensure the required installation standards are adhered to using R56 standards as a baseline, as well as local building and electrical codes. 8. ACCEPTANCE TESTING Maxwell AFB requires that the contractor establish and execute an Acceptance Test Plan within ?? days prior to after project acceptance that is specifically designed for this Command & Control Upgrade. The testing procedures shall ensure that the installed communication system and all subsystems meet or exceed all technical, operational, and coverage design requirements. The equipment and engineering methodologies associated with this upgrade will be required to have met extensive testing to demonstrate that system performance meets the expectations as outlined in this SOR for Maxwell AFB. As part of the Acceptance Testing, the contractor will demonstrate that the Quality Assurance Standards have been achieved. 9. PERSONNEL TRAINING The on-base personnel and personnel at the auxiliary locations shall be provided comprehensive training by experienced instructors. This educational phase of the project shall include design specific courseware and integrated lab activities. T raining should focus on the personnel's needs and experience level. Two classes focused for Console Users (for 10 dispatchers) and one class focused on Emergency Communication Supervisors and Mobile Radio System technicians (for 6 personnel). Training should cover all applicable subject matter topics, system features, functionality and operation. This training will be required to the conducted on-site and training materials shall be provided. The curriculum provided shall be geared to teach the Maxwell AFB personnel how to best utilize t he system at its maximum potential. Scheduling of training classes will be achieved by mutual determination. Requested training dates, the final class dates and presentation will be determined mutually and based upon instructor and student availability. 10. WARRANTY It is required that The contractor offer shall provide a standard oneyear manufacturer's limited commercial warranty to correct possible defects in materials and workmanship. Warranty services will include repair service to correct possible defects in materials and workmanship during normal business hours, Monday through Friday, excluding holidays. SOR ATTACHMENT 2 SOR ATTACHMENT 3 Attachment 3 2 - Price List PRICE LIST Offerors must provide a detailed breakdown of the items to meet the requirements of this Request for Quote in the price list below. If you require extra space, you may add additional rows or you may submit additional pages with your proposal. Please indicate that additional pages are provided at the end of this attachment. Item 0001 Motorola Dispatch Consoles and Motorola Consolettes Line# Part # Manufacturer Product Description QTY Unit of Measurement Unit Price Extended Price Total Price Item 0002 System integration, Installation, Acceptance testing and Training Line# Part # Description of work Labor Category Number of Hours Labor Rate Extended Price Total Price
Web Link: FBO.gov Permalink
(https://www.fbo.gov/spg/USAF/AETC/MaxAFBCS/F2X3C76193A001/listing.html)
Place of Performance: Address: Maxwell AFB, Montgomery, Alabama, 36113, United States; Zip Code: 36113
Record: SN04275432-W 20160918/160916234937-503cd4115d2f55424af983d77361dfb6 (fbodaily.com)
Source: FedBizOpps Link to This Notice
(may not be valid after Archive Date)

| FSG Index | This Issue's Index | Today's FBO Daily Index Page |

Loren Data's SAM Daily™

58 -- Amendment 01 Motorola Dispatch Consoles - Amendment 1