Amendment 0001 RFP - TAP W56HZV-19-R-0043.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing items 8 and 15, and returning ____________ copies of the amendments: (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting And Appropriation Data (If required)

13. THIS ITEM ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: The Changes Set Forth In Item 14 Are Made In

The Contract/Order No. In Item 10A.

B. The Above Numbered Contract/Order Is Modified To Reflect The Administrative Changes (such as changes in paying office, appropriation data, etc.) Set

Forth In Item 14, Pursuant To The Authority of FAR 43.103(b).

C. This Supplemental Agreement Is Entered Into Pursuant To Authority Of:

D. Other (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return _______________ copies to the Issuing Office.

14. Description Of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. Name And Title Of Signer (Type or print)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

By (Signature of person authorized to sign) (Signature of Contracting Officer)

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Cost Plus Fixed Fee

W56HZV

ACC-DTA

6501 E. 11 MILE RD.

DETROIT ARSENAL, MI 48397-5000

MIRA PATEL

EMAIL: MIRA.PATEL.CIV@MAIL.MIL

W56HZV-19-R-0043

2020FEB20

X

X 2020APR07 05:00pm

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 13

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: MIRA PATEL

Buyer Office Symbol/Telephone Number: CCTA-AHM-B/(586)282-6231

Type of Contract 1: Cost Plus Fixed Fee

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

1. The purpose of this amendment 0001, is to update the following:

a. Section C - Description/Specification/Work Statement

b. Section I - Add clause

c. Section J - Update CDRL A010

d. Section L - Add clause

e. Update the Proposal Response Due Date

2. Section C has been updated to add the following:

*C.2.9.1 The contractor shall conduct and host a Program Management Review (PMR) annually on site at Fort Hood, Texas, with the meeting being held approximately six months after contract award or as coordinated with the Government IAW CDRL A010.

3. Section I - Contract Clause - add DFARS clause 252.234-7004- Notice of Cost and Software Data Reporting System (Nov 2014)

4. Section J - CDRL A010 has been updated to include reference to C.2.9.1 and update Blocks 10/12/13.

5. Section L - Instructions, Conditions, and Notice to offerors - add DFARS Clause 252.234-7003 - Notice of Cost and Software Data

Reporting System (Nov 2014)

6. Proposal Response Due Date has been updated as follows:

From:

All proposals due by 5:00pm EST on 23 March 2020

TO:

All proposals due by 5:00pm EST on 07 April 2020

7. All other terms and conditions remain unchanged and in full force and effect.

*** END OF NARRATIVE A0003 ***

2 13

W56HZV-19-R-0043

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 GENERAL

C.1.1 Introduction. The contractor shall receive and test assets to identify No Evidence of Failures (NEOF) prior to repair induction.

The contractor shall stock, store, issue, and repair M1 Abrams, M2/ M3 Bradley, and M104 Wolverine Line Replacement Units (LRU) and Shop

Replacement Units (SRU), listed in Attachment 0001. The contractor shall repair LRUs and SRUs listed in Attachment 0001 in accordance with (IAW) repair criteria listed in each items respective Technical Manual (TM), or Original Equipment Manufacturer (OEM) standards for assets that require subcontractor repair. The contractor shall use the Logistics Modernization Program (LMP) to record receipt of assets, change item condition codes, create materiel release orders, and update stock records. The contractor shall perform this work in the Government-supplied facility located at Building 88037, Fort Hood, Texas.

C.2 Requirements/Performance Standards.

C.2.1 RECEIPT OF ASSETS

C.2.1.1 Requirement: The contractor shall receive all assets and document all receipts in LMP. All assets receipted shall be considered

Government Furnished Material (GFM) (Attachment 0001) and Government Furnished Property (GFP) (Attachment 0001), which the contractor shall account for per the GFP clauses and instructions provided in section H of this contract.

C.2.1.2 Performance Standard: The contractor shall record all GFM received into LMP within 3 calendar days. Refer to Accountability

Instructions in section H.3 of the contract. The contractor shall report status of all receipt documentation IAW Contract Data

Requirement List (CDRL) A001.

C.2.1.3 Acceptable Quality Level: The contractor shall record the GFM in LMP within 3 calendar days with an objective goal of 98%, and a threshold of 95%. If the timeliness or accuracy error rate is greater than 5%, an explanation of the errors shall be detailed and delivered IAW CDRL A001.

C.2.2 DETERMINATION OF CONDITION CODE

C.2.2.1 Requirement: The contractor shall determine the condition code of all assets received, including those requiring inspection and repair, IAW AP2.5 of DLM 4000.25-2, Military Standard Transaction Reporting and Accountability Procedures (MILSTRAP), dated 29 April

2016.

C.2.2.2 Performance Standard: The contractor shall inspect, determine condition codes and accurately post all assets in LMP within 7 calendar days of receipt and within 5 calendar days of receipt for assets deemed urgent by the Government (eg. PRI 1 would be urgent or by Contracting Officer Representatives (COR) direction. The contractor shall provide test results to the Government IAW CDRL A001.

C.2.2.3 Acceptable Quality Level: The contractor shall record all assets in LMP within 7 calendar days with an objective goal of 98%, and a threshold of 95%. If more than 7 calendar days are needed to determine and post condition codes for routine assets, or more than 5 calendar days are needed for assets designated as urgent, the contractor shall obtain COR concurrence and coordinate a revised schedule with the COR. If the timeliness or accuracy error rate is greater than 5%, an explanation of the errors shall be detailed and delivered

IAW CDRL A001.

C.2.3 STORAGE

C.2.3.1 Requirement: The contractor shall store all GFM listed in Attachment 0001 in a secure manner that ensures the condition is not degraded. The contractor shall restrict asset accessibility to authorized personnel only.

C.2.3.2 Performance Standard: The contractor shall package all GFM IAW Section D and record into LMP.

C.2.3.3 Acceptable Quality Level: No asset issued from TAP shall have a valid Supply Discrepancy Report (SDR) or Quality Deficiency

Report (QDR) found against it based on insufficient packaging or deficient storage.

C.2.4 ISSUE

C.2.4.1 Requirement: The contractor shall issue all assets directed for release via LMP.

C.2.4.2 Performance Standard: The processing time for all assets directed for release into LMP shall be equal to or less than the number of days defined by the priority number located on the Material Release Order (MRO) issued to the contractor through LMP. The contractor shall package all assets IAW Section D packaging and labeling requirements. The contractor shall record all shipment transactions in

LMP. All shipping documentation accompanying repaired assets returned to the Government must have the following statement annotated in the remarks portion of the shipping document: "RETURN FROM REPAIR, MARK FOR: (the document number under which the assets were received at the contractor location). NOTE: The quantity shipped under each document number must not exceed the quantity received under that same document number. The contractor shall document all shipments and report them to the Government IAW CDRL A001.

3 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.2.4.2.1 The contractor shall document any shipping type discrepancy and deliver it to the Government IAW CDRL A004.

C.2.4.2.2 The contractor shall document any transportation type discrepancy and deliver it to the Government IAW CDRL A005.

C.2.4.3 Acceptable Quality Level: 100% of shipments shall be executed within the specified time based on priority IAW C.2.4.2, above

(e.g. priority 02 = two business days or less). The contractor shall have no more than two total SDRs per year.

C.2.5 REPAIR

C.2.5.1 Requirement: The contractor shall repair unserviceable assets IAW the applicable TMs or for assets designated for subcontractor repair, to OEM standards. The contractor shall repair only the assets with a repair flag designation of yes detailed in Attachment 0001.

The COR will provide a repair list on a monthly basis that lists the repair quantity, priority and Maintenance Expenditure Limit (MEL).

The contractor shall repair up to the stated quantity designated for each asset. The contractor shall not initiate repair of an asset if the total cost to repair will exceed the associated MEL without prior approval from the COR.

C.2.5.1.1 Performance Standard: The contractor shall repair all unserviceable assets to condition code A IAW the TMs defined in

Attachment 0001, or IAW OEM standards. The contractor shall deliver an average repair cost report per National Item Identification

Number (NIIN) IAW CDRL A002. Average repair cost shall be represented as total costs by NIIN divided by total number of units repaired by NIIN over a 12 month period. To manage cost, the contract includes MEL limits for each NIIN authorized for repair to ensure repair costs do not exceed the economic cost to repair versus buying new.

C.2.5.1.2 Acceptable Quality Level: The contractor shall provide documentation of successful test results for all tests required by the applicable TMs defined in Attachment 0001. The contractor shall document and deliver all test results to the Government IAW CDRL A001.

The contractor shall have no more than two total QDRs per year on all repaired assets.

C.2.5.2 Requirement: Repair Turn Around Time (RTAT) is defined as the time between induction to repair and the completion of that repair. This includes assets sent to subcontractors. Induction to repair is when the asset goes from a condition code F to a condition code M. Completion is when the asset goes from a condition code M to a condition code A. The contractor shall deliver a report IAW CDRL

A010.

C.2.5.2.1 Performance Standard: RTAT for subcontractors shall be documented IAW CDRL A010.

C.2.5.2.2 Acceptable Quality Level: The contractor shall have an average RTAT equal to or fewer than 90 calendar days, 100% of the time.

C.2.6 UNIQUE IDENTIFICATION (UID) MARKING

C.2.6.1 Requirement: The contractor shall apply UID markings and register all qualified serviceable assets receipted or released from the TAP warehouse. The contractor shall query the Federal Logistics Data (FEDLOG) system to determine if UID is necessary for each part.

If FEDLOG indicates UID is required, the contractor shall apply UID tagging IAW DFARS 252.211-7003.

C.2.6.2 Performance Standard: The UID marked and registered assets shall be repackaged IAW Section D after marking and registering.

C.2.6.2.1 The contractor shall UID mark and register any repaired qualified asset before storage.

C.2.6.2.2 The contractor shall UID mark and register SRUs removed during repair before storage.

C.2.6.2.3 The contractor shall UID mark and register any field receipt asset received as serviceable before storage.

C.2.6.3 Acceptable Quality Level: All qualified serviceable assets shall have a registered UID marking. The contractor shall ensure 100% of parts shipped from TAP have UID tags IAW FEDLOG requirements.

C.2.7 TRACKERLITE FOR NON-FMS HIGH PRIORITY OCONUS SHIPMENTS

C.2.7.1 Requirement: The contractor shall utilize TrackerLite (Attachment 0003) and the Fort Hood Transportation system for the shipment of all high priority 02 and 03 Outside Continental United States (OCONUS) and also CONUS requisitions with an RDD (Requirement Delivery

Date) of N01 or 999, excluding Foreign Military Sales (FMS) requisitions. See Attachment 0003 TrackerLite System Instructions.

C.2.7.2 Performance Standard: The contractor shall create one or more user accounts in TrackerLite https://trackerlite.wpafb.af.mil/LTS

. This system requires a Common Access Card (CAC) to access, one CAC per user account.

C.2.7.2.2 The contractor shall ensure that all material released priority 02 and 03 requisitions for OCONUS, not to include FMS:

1. The contractor shall have its DD1149 created in TrackerLite.

4 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

2. The contractor shall have its TrackerLite DD1149 printed out and attached to the shipment.

3. The contractor shall have its hardware delivered to Fort Hood's Transportation Center, Building 89013 Quartermaster Lane, Fort Hood, TX 76544-5060, with its attached DD1149 prior to 0900. A hardcopy of the Army-Funded Transportation Funds Verification & Use

Authorization shall be handed over at the same time. This form will be provided to the contractor monthly by the Government COR.

4. The contractor shall obtain a copy of the Commercial Bill of Lading (CBL) from the transportation assistant at the Central Receiving and Shipping Point (CRSP). The CBL will include the shipping cost.

5. The contractor shall use the combination of CBL costs for any particular month to fulfill the paragraph C.3.3 report IAW CDRL A009.

C.2.7.3 Acceptance Quality Level: 100% of all non-FMS OCONUS requisitions with priority of 02 or 03 shall utilize TrackerLite and the

Fort Hood Transportation office for transportation and 05-15 Priorities with RDDs indicating expedited handling/NMC (555,777,999,N--,E--

) will be designated to W45QRE, address 89013 Quartermaster Lane, Fort Hood, TX. 76544-5060.

C.2.8 ANTI-TERRORISM (AT) / OPERATIONS SECURITY (OPSEC)

C.2.8.1 The contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation IAW Army Directive 2014-05 before CAC issuance. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple

DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

C.2.8.2 The contractor and its subcontractors shall be required to meet the following training requirements:

C.2.8.2.1 AT Level I: All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the Procuring Contracting Officer (PCO), within 30 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: https://Jkodirect.jten.mil/ for CAC holders. Non-CAC-holders may go to:

http://jko.jten.mil/courses/atl1/launch.html . IMPORTANT: The standalone course MUST be completed on the computer in which it is started. Course progress is not transferable between computers. The standalone course does provide a completion certificate but will not be tracked on Joint Knowledge Online (JKO) and no record will be maintained. For assistance regarding the Level I

Antiterrorism Awareness Training, contact the JKO Help Desk, Monday - Friday 0700-2300 EST at COMM: 757-203-5654 / DSN: 668-5654 or email ""mailto:jkohelpdesk@jten.mil " " ______________________________________

C.2.8.2.2 iWATCH: The contractor and all associated subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity Antiterrorism Officer (ATO)). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 30 calendar days after contract award.

http://www.myarmyonesource.com/familyprogramsandservices/iwatchprogram/default.aspx

C.2.8.2.3 OPSEC Program: The contractor shall be required to adhere to the OPSEC Standing Operating Procedure (SOP)/Plan developed and implemented by the PD MBTS, Government OPSEC Officer which they support. The contractor shall adhere to OPSEC measures as ordered by the commander. In addition, the contractor shall have an identified certified Level II OPSEC coordinator per AR 530-1.

C.2.8.2.3.1 OPSEC Training: Per AR 530-1 Operations Security, the contractor employees must complete Level I OPSEC Awareness training.

New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter. Level I OPSEC training is available at the following website: http://cdse.edu/catalog/elearning/GS130.html (Duration: 45 minutes).

C.2.8.2.3.2 OPSEC Plan: The contractor shall provide an OPSEC Plan IAW CDRL A011. The contractor shall document compliance with its

OPSEC Plan annually in the Material Status Report IAW A011.

C.2.8.2.4 Army Training Certification Tracking Systems (ATCTS) registration: All contractor employees with access to a Government info system must be registered in the ATCTS (Army Training Certification Tracking System) NLT 15 calendar days after contract award, and must successfully complete the DOD Cybersecurity Awareness prior to access to the IS and then annually thereafter.

5 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.2.8.2.5 Cybersecurity/Information Technology (IT) Training: All contractor employees and associated subcontractor employees must complete the DOD Cybersecurity awareness training before issuance of network access and annually thereafter. All contractor employees working Cybersecurity/IT functions must comply with DoD and Army training requirements in DoDD 8140.01, DoD 8570.01-M (Ch4) and AR 25-2 within six months of appointment to Cybersecurity/IT functions.

C.2.8.2.5.1 Cybersecurity/IT Certification: Per DoD 8570.01-M (Ch4) DFARS 252.239.7001 and AR 25-2, the contractor employees supporting

Cybersecurity/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DoD 8570.01-

M (Ch4) must be completed upon contract award.

C.2.8.2.6 Access and General Protection/Security Policy and Procedures: Contractor and all associated subcontractor employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation

Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection

Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

C.2.9 Start of Work Meeting: The Government will host a Start of Work Meeting with contractor leadership, ILSC leadership, the COR and

Contracting, no later than seven calendar days after award. The COR will coordinate with the contractor regarding mutually agreeable dates and location for the Government and contractor to meet to review the contract. The contractor shall host a second Start of Work

Meeting with contractor leadership, ILSC leadership, the COR and Contracting, 30 calendar days after the Period of Performance begins, when the contractor shall be Fully Mission Capable (FMC). The contractor shall brief the status of the approved transition-in.

*C.2.9.1 The contractor shall conduct and host a Program Management Review (PMR) annually on site at Fort Hood, Texas, with the meeting________________________________________________________________________________________________________________________________________ being held approximately six months after contract award or as coordinated with the Government IAW CDRL A010.____________________________________________________________________________________________________________

C.2.10 Manpower Information Retrieval and Reporting System (MIRARS).

All contractors shall comply with ILSC policies, which will be provided by the Government at the Start of Work, pertaining to MIRARS

Roll Call, an electronic application used daily to record each employees duty status, physical location, and emergency information. This information is utilized should an emergency evacuation or catastrophic event occur.

C.2.11 Government Furnished Equipment (GFE), Facility Badges, and CAC control. The contractor shall implement procedures to track and account for all GFE, facility badges, and CACs issued to the contractor by the Government; shall immediately report the loss or misplacement of any of these items to the Government; and shall also report within one business day any unauthorized use of Government-issued keys/CACs to the COR IAW CDRL A006.

C.3 DATA REQUIREMENTS

C.3.1 The contractor shall provide a monthly Contract Fund Status Report (CFSR) for each CLIN IAW CDRL A003.

C.3.2 The contractor shall use LMP to report Receipts, Inductions, Completions, Scrap, etc. IAW Defense Logistics Manual (DLM) 4000.25-

1, Military Standard Requisitioning and Issue Procedures (MILSTRIP), dated 29 April 2016. The contractor shall continually monitor LMP for generated email messages.

C.3.3 The contractor shall provide a monthly Shipping Cost Report IAW CDRL A009.

C.3.4 Contractor Manpower Reporting (CMR). The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor shall report all contractor manpower (including subcontractor manpower) required for performance of this contract. The contractor shall completely fill in all the information in the format using the following web address https://Contractormanpower.army.pentagon.mil . The contractor shall provide CMR as described in TACOM clause 52.237-4000 to report information related to the manpower required for performance of this contract on the provided secure Army website.

C.4 STANDARDS FOR RECEIPTS, DUE-INS AND ISSUES

C.4.1 The contractor shall implement an automated means that will satisfy the Governments requirements established in Army Regulation

725-50, Requisition, Receipt, and Issue System, dated 15 November 1995. The contractor shall ensure the policies and procedures are adhered to for the Government Accountable Property Officer (APO) to track and monitor assets while those assets are out of warehouse or in transit to a subcontractor.

6 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.4.1.1 Frequency: The contractor shall record receipt of assets, change item condition codes, create materiel release orders, and update stock records daily.

C.4.1.2 Systems Used: The Government will use LMP to transmit the following data to TAP: MRO, Disposal Release Orders (DRO), and MRO/DRO

Cancellation Request transactions. The Government will communicate updates in LMP to the contractor through automated messages from the

LMP system. The contractor shall input into LMP Receipts, Condition Code Changes, Shipment Confirmations, and Confirmation of

Cancellation transactions.

C.4.1.3 Reversals. The contractor shall send an e-mail notice to the COR and PCO to notify the Government when erroneous data was sent in a prior transmission, IAW CDRL A001.

C.4.1.4 Transactions. The actions and reporting information listed below are to be received and transmitted by the contractor. The required transactions have been designed to provide visibility of TACOM owned assets as stated in paragraphs C.4.1.4.1 thru C.4.1.4.5

C.4.1.4.1 Receipt from TAP of material from new production contracts.

C.4.1.4.2 Receipt from TAP of material from field returns, depots, components removed from repair assets, etc.

C.4.1.4.3 Receive from TACOM LCMC, MRO and DRO for shipment, and Request for Cancellation of MRO/DRO.

C.4.1.4.4 Receive from TAP shipment confirmations, and reply to cancellation requests.

C.4.1.4.5 Receive from TAP condition code changes.

C.4.1.5 The TAP-Fort Hood, TX Routing Identifier Code (RIC) coded, and Department of Defense Activity Address Code (DoDAAC) W90454, shall be used in all LMP communications.

C.4.1.6 Transactions Definitions are defined in AP2.1.6, Document Identifier Codes, of DLM 4000.25-1, MILSTRIP, dated 29 April 2016.

C.5 UNCLASSIFIED//FOR OFFICIAL USE ONLY (U//FOUO)

a. The contractor shall assign marking of UNCLASSIFIED//FOR OFFICIAL USE ONLY (U//FOUO) to information at the time of its creation in a

DOD User Agency. This marking is not authorized as a substitute for a security classification marking but it is used on official

Government information that may be withheld from the public under exemptions 2 through 9 of the Freedom of Information Act.

b. The contractor shall ensure that control, marking, and protection of U//FOUO information will be IAW this document and Army

Regulation 380-5, Chapter 5, para 5-1 through 5-6.

c. The contractor may disseminate "UNCLASSIFIED//FOR OFFICIAL USE ONLY" (U//FOUO) information to their employees who have a need to know for the information in connection with the contract.

d. DESTRUCTION: The contractor shall ensure that all U//FOUO material is destroyed by tearing or shredding to make unreadable. The contractor shall purge all electronic media with approved software or destroy it through physical process. All U//FOUO information related to this contract stored on a contractor's computer system shall be purged from the computer system no later than one year after the end of this contract. Contractors wishing to retain the information for a longer period of time must receive permission from the

PCO.

e. STORAGE: During working hours, the contractor shall place all U//FOUO information in an out of- sight location if the work area is accessible to persons who do not have a need for the information. During non-working hours, the information shall be stored to preclude unauthorized access. Filing such material with other unclassified records in unlocked files for desks is adequate when internal building security is provided during non-working hours. When such internal security control is not exercised, locked buildings or rooms will provide adequate after hours protection, or the material can be stored in locked receptacles such as file cabinets, desks, or bookcases.

f. ELECTRONIC COMMUNICATIONS: The contractor shall ensure that all sensitive information (U//FOUO, proprietary, operational information, Freedom of Information Act exemptions, etc.) is protected and may be sent over an installation Local Area Network (LAN) that is protected with a firewall, user ID, and passwords. However, this same information must be CAC encrypted when sent from an installation

LAN to individuals/organizations that are located at a different installation or a contractor location. When no longer needed, the contractor shall ensure that this information is shredded or torn to make it unreadable.

C.6 TRAINING

C.6.1 Requirement: The contractor shall allow maintenance training session(s) to be completed at the Ft. Hood, TX location with coordination from the COR. This training may include soldiers and/or civilians.

C.6.2 Performance Standard: The contractor shall accommodate a five week continual maintenance training session, up to ten times per

7 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

calendar year with one student per session. The student will shadow and observe the performance of the TAP contract as inspecting, testing, fault diagnosing, and repairing of SRUs and LRUs for M1 Abrams, M104 Wolverine, and M2/M3 Bradley Fighting Vehicle Systems take place.

C.6.2.1 The contractor shall comply with all International Traffic in Arms Regulations (ITAR) in the event that any student is a foreign national (FN).

C.7 TRANSITION

C.7.1 A transition period is scheduled upon contract award (Transition-In) for 30 calendar days and for 60 calendar days prior to contract end date (Transition-Out) to allow for orderly contract transition. In order to maximize the effectiveness of the transition process, an initial start-of-work meeting shall be held between the contractor leadership, ILSC leadership, the COR and Contracting team to address Transition-In requirements and responsibilities no later than seven business days after award. Any subsequent meetings will be held as determined by the PCO.

C.7.1.1 Transition-In Period: Transition-In operations shall not hinder or interfere with normal operations of the Transition-Out contractor and shall not result in loss of productivity. The Transition-In period shall not exceed 30 calendar days.

C.7.1.2 Transition-Out Period: The Government may extend the term of this contract by written notice to the contractor within 30 calendar days; provided that the Government gives the contractor a preliminary written notice of its intent to extend at least 60 calendar days before the contract expires. The preliminary notice does not commit the Government to an extension. The contractor shall remain responsible and liable for the completion of all requirements of this contract for which CDRL deliveries are due before the final day of this contract. The contractor shall not defer any requirements for the purpose of avoiding responsibility and transferring such responsibility to the successor contractor or the Government. The contractor shall fully cooperate with the successor contractor and the

Government and shall not interfere with work or duties.

C.7.1.2.1 Transition-Out Plan: The contractor shall provide the PCO with a Transition-Out plan no later than 60 calendar days prior to end of the contract completion unless the Government has provided a notice to extend the contract IAW the terms of the contract.

Transition-Out Plan shall detail disposition action for all furnishings, equipment, material, and documentation with Government input, outlining the contractors approach to fulfill the requirements of this contract, and applying all relevant factors and information gathered throughout the performance IAW CDRL A012.

C.8 Cost and Software Data Reporting (CSDR)

C.8.1 Cost and Software Data are the primary means by which the Department of Defense (DoD) collects data on the costs that contractors incur on DoD programs. Reliable and comprehensive cost data is essential to produce credible cost estimates as required in both statute and regulation. The Governments goals and use of CSDR data is to improve the quality of cost estimates; ensure proper resource allocation occurs within the DoD; and enable data driven decision making by program and department leadership.

The contractor shall systematically collect and report actual contract costs IAW CDRLs and Attachment 0008, the Contract Cost and

Software Data Reporting (CSDR) Plan:

Report Title CDRL

Resource Distribution Table A013

Cost and Hour Report (FlexFile) A014

Maintenance and Repair Report (DD Form 1921-M/R) A015

Contractor Business Data Report (DD Form 1921-3) A016

C.8.1.2 Application to Subcontractors

C.8.1.2.1 The contractor shall flow-down CSDR requirements referenced in section C.8 and its sub-paragraphs to subcontractors

(regardless of subcontractor tier) when the subcontract value is expected to exceed $20 million using the maximum allowable contract quantities, hours, or options (as applicable), as required by DoD 5000.04-M-1 - CSDR Manual. The contractor shall require subcontractors to electronically submit CSDR deliverables directly to the Defense Cost and Resource Center (DCARC). The contractor shall ensure that

Subcontractors subject to CSDR reporting thresholds collect data in sufficient detail to meet Attachment 0008 - CSDR Plan requirements.

The contractor shall collect and deliver data on all subcontractors to comply with Attachment 0009 and CDRL A013 - Resource Distribution

Table and Attachment 0008 - CSDR Plan requirements. A subcontract is any agreement, purchase order, or instrument other than a prime contract calling for work or for the material required for the performance of one or more prime contracts. A subcontract usually covers procurement of major components or subsystems that require the subcontractor to do extensive design, development, engineering, and testing to meet a prime contractors procurement specifications.

C.8.1.3 Resource Distribution Table (RDT)

C.8.1.3.1 The contractor shall prepare and submit the Resource Distribution Table (RDT) IAW CDRL A013. The Resource Distribution Table

(RDT) identifies the value of work assigned to the contractor and its subcontractors for each WBS element listed in Attachment 0008 -

CSDR Plan, and is the primary means of identifying subcontractors who qualify for CSDR reporting.

8 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

C.8.1.4 Contract Work Breakdown Structure (WBS) & Dictionary

C.8.1.4.1 The contractor shall utilize the Contract Work Breakdown Structure (WBS) identified in Attachment 0008 - CSDR Plan, as the primary framework for contract budgeting and reporting of incurred costs and hours to perform the contract. The contractor shall extend the WBS to provide adequate internal management, surveillance, and performance measurement of the contract. The contractor shall ensure all WBS oriented reporting is compliant with at least the levels identified in Attachment 0008 - CSDR Plan. The contractor shall develop and maintain a Contract Work Breakdown Structure (CWBS) Dictionary throughout the life of the contract, and shall submit the CWBS

Dictionary IAW CDRL A014. The CWBS Dictionary reports a description of the technical, cost, and work content of each WBS element.

C.8.1.5 Cost and Hour Report (FlexFile)

C.8.1.5.1 The contractor shall prepare and submit the Cost and Hour Report (FlexFile) in accordance with CDRL A014. The Cost and Hour

Report (FlexFile) reports incurred and forecasted costs and hours related business data in order to perform this contract.

C.8.1.6 Contractor Business Data Report (CBDR, DD Form 1921-3)

C.8.1.6.1 The contractor shall prepare and submit the Contractor Business Data Report (DD Form 1921-3) in accordance with CDRL A016. The

Contractor Business Data Report (DD Form 1921-3) reports data to facilitate estimating and analysis of indirect contract costs and rates.

C.8.1.7 Maintenance and repair Report (DD Form 1921-M/R)

C.8.1.7.1 The contractor shall prepare and submit the Maintenance and Repair Report (DD Form 1921-M/R) in accordance with CDRL A015. The

Maintenance and Repair Report (DD Form 1921-M/R) reports sustainment information including labor hours, parts consumption, overhead costs, material costs, and other direct and indirect cost, by maintenance event, vehicle, part number, and contract line item number.

C.8.1.8 Post-Award Cost and Software Reporting Conference

C.8.1.8.1 The contractor shall host a Post-Award CSDR Conference at the Contractors facility where CSDRs are prepared with the

Governments Cost Working Group Integrated Product Team (CWIPT) IAW DFARS 242.503-2(b) and DoD 5000.04-M-1 (CSDR Manual). The purpose of the Post-Award CSDR Conference is to review the contracts CSDR requirements and assess how the contractors accounting system satisfies the CSDR requirements found in DoD 5000.04-M-1, CSDR Manual and Attachment 0008 - CSDR Plan. In a briefing presented by the contractor in its own format, the contractor shall:

- Demonstrate how it collects cost data in its accounting system and how that data will be utilized to provide actual cost transactions and minimize cost allocations when preparing CSDR data deliverables.

- Describe how recurring vs. nonrecurring costs are segregated in its accounting system and for the purpose of CSDR reporting.

- Demonstrate how the data from its accounting system will be mapped into the CSDR reports required by Attachment 0008 - CSDR Plan and associated CDRLs.

- Present the methodologies used for mapping internal cost accounts to the WBS, specifically showing how individual WBS elements and functional element codes will be populated.

- Propose any changes to Attachment 0008 - CSDR Plan in order to tailor the plan to the contractors accounting system, to include any contractor recommended changes or additions to the WBS elements. These changes may include adjustments to the submission events and/or submission timelines, particularly in the case of a direct-reporting subcontractor performing against a different delivery schedule than the associated prime contractor.

The contractor and CWIPT will also review the initial submission of the Resource Distribution Table (RDT) (CDRL A013), in order to finalize which subcontractors will be required to provide CSDR reporting and electronic submission of deliverables directly to the DCARC and which subcontractors may qualify for a CSDR direct reporting subcontractor waiver.

The Post-Award Cost and Software Data Reporting Conference shall be held within 60 days of the Start of Work Meeting on a date mutually agreed to by the CWIPT and the contractor. This meeting has an anticipated duration of one business day.

C.9 Total Asset Visibility Contractor (TAV-C)

C.9.1 Army Materiel Command (AMC) and its units use TAV-C capability in its LMP to account for Government Furnished Equipment, Materiel, or Property (GFE/M/P) placed in the possession of contractors to support contracts for: 1) repair, modification, or upgrade work; 2) materials held for Stock, Store and Issue (SSI), or 3) New Production. Accounting records within LMP for this inventory are subject to verifying physical inventories and audits by the Army to ensure accuracy.

A. To use TAV-C, contractors shall request one of two TAV-C access methods below to exchange required inventory data with LMP: 1)

Defense Logistics Management Standards (DLMS) interface or 2) the Army TAV-C Portal. Approval of the contractors access method will be based first on the type of work being performed, second, the sufficiency of the contractors existing property accountability and connectivity to LMP, and third, request by the contractor to use the portal based on economic factors.

B. Contractors can choose between the two methods for accounting for Government property as further described below:

1. DLMS interfaces: Contractors that have accounting systems capable of using a DLMS interface (see: DLM 4000.25, DLMS on the

Defense Logistics Agency (DLA) website) shall request to use their accounting system and interface to account for GFE/M/P using

DLMS transactions.

NOTE: If a contractor does not currently have an established DLMS interchange with DLA Defense Automated Addressing System (DAAS), it

9 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

will be the contractors responsibility to contact DAAS to establish access to DAAS messaging system to support the exchange of DLMS transactions with the Army. DAAS provides a value added service for standard Military Standards (MILS) transactions providing the ability to receive, edit and route logistics transactions for the Military Services and Federal Agencies. Information on DAAS can be found at https://www.dla.mil/HQ/InformationOperations/DAAS/ .

2. Army TAV-C Portal: Contractors, who are determined to be allowed to use the TAV-C Portal, shall comply with prescribed processes to provide qualified workers to access the system to exchange data with LMP.

C. Portal Access Requirements. Contractor personnel who input data into the TAV-C Portal must meet qualification requirements specified in the TAV-C Portal Guide Detailed Procedures. The requirements are detailed in the TAV-C Portal Guide (Attachment 0010). These requirements include:

1. Contractor provided computer system: The contractor shall provide a computer system and internet connectivity that meets acceptable standards as identified in the TAV-C Portal Guide.

2. Security Requirements.

The Government requires contractor personnel accessing the LMP system to possess either a United States Government CAC or a DoD approved

External Certification Authority (ECA). To apply for these credentials, contractor personnel must possess a soft certification from a security credentialing firm.

* Updated through Amendment 0001________________________________

*** END OF NARRATIVE C0001 ***

10 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION I - CONTRACT CLAUSES

Status Regulatory Cite Title Date Status Regulatory Cite Title Date _______ _______________ ______________________________________________________________________ ____________ _______ _______________ ______________________________________________________________________ ____________

I-1 ADDED 252.234-7004 COST AND SOFTWARE DATA REPORTING SYSTEM--BASIC NOV/2014

11 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION J - LIST OF ATTACHMENTS

List of Number List of Number

Addenda Title Date of Pages Transmitted By Addenda Title Date of Pages Transmitted By________________ ____________________________________________________________ _______________ ____________ _______________________________ ____________________________________________________________ _______________ ____________ _______________

Exhibit A CONTRACT DATA REQUIREMENTS LIST

12 13

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

Status Regulatory Cite Title Date Status Regulatory Cite Title Date _______ _______________ ______________________________________________________________________ ____________ _______ _______________ ______________________________________________________________________ ____________

L-1 ADDED 252.234-7003 NOTICE OF COST AND SOFTWARE DATA REPORTING SYSTEM--BASIC NOV/2014

13 13

PIIN/SIIN

MOD/AMD

ATT/EXH ID

PAGE

Exhibit A

DD FORM 1423, FEB 2001

CONTRACT DATA REQUIREMENT LIST, PREVIOUS EDITION MAY BE USED Form Approval OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

. CONTRACT LINE ITEM NO.: A001

B. EXHIBIT: A

C. CATEGORY: TDP_ T M_ OTHER X__

D. SYSTEM/ITEM: TEAM ARMOR PARTNERSHIP (TAP)

E. CONTRACT/PR NO.: TBD

F. CONTRACTOR: TBD

1. DATA ITEM NO: A001

2. TITLE: Government Furnished Equipment Repair Status Report

3. SUBTITLE: Parts Technical Inspection Report

4. AUTHORITY: DI-ILSS-80620(T)

5. CONTRACT REFERENCE: C.2.1.2; C.2.1.3; C.2.2.2; C.2.2.3; C.2.4.2; C.2.5.1.2; C.4.1.3; H.3.1; and H.8.9.2

6. REQUIRING OFFICE: AMSTA-LCG-AA

7. DD250 REQ: LT

8. APP CODE:

9. DIST. STATEMENT REQ: D

10. FREQUENCY: MTHLY

11. AS OF DATE: 30 days after contract award

12. DATE OF FIRST SUBMISSION: 30 days after contract award

13. DATE OF SUBS. SUBMISSION: MTHLY

14. DISTRIBUTION:

A. ADDRESSEE: AMSTA-LCG-AA; CCTA-AHM-B

B. COPIES: 00

DRAFT: 00

FINAL: 01

REG REPRO: 00

15. TOTAL COPIES: 02

16. REMARKS:

DISTRIBUTION STATEMENT D: DISTRIBUTION AUTHORIZED TO THE DEPARTMENT OF DEFENSE AND U.S. DOD CONTRACTORS ONLY (CRITICAL TECHNOLOGY, 30

January 2019, TACOM-ILSC). OTHER REQUESTS SHALL BE REFERRED TO TACOM, US ARMY TACOM, ATTN: AMSTA- LCG-AA, 6501 E 11 MILE ROAD, MS 510, DETROIT ARSENAL, MI 48397-5000. EXPORT CONTROL WARNING. ALL TECHNICAL DOCUMENTS THAT ARE DETERMINED TO CONTAIN EXPORT-CONTROLLED

TECHNICAL DATA SHALL BE MARKED, "WARNING-THIS DOCUMENT CONTAINS TECHNICAL DATA WHOSE EXPORT IS RESTRICTED BY THE ARMS EXPORT CONTROL ACT

(TITLE 22, U.S.C., SEC 2751, ET. SEQ.) OR THE EXPORT ADMINISTRATION ACT OF 1979, AS AMENDED, TITLE 10, U.S.C., APP. 2401 ET.SEQ.

VIOLATIONS OF THESE EXPORT LAWS ARE SUBJECT TO SEVERE CRIMINAL PENALTIES. DISSEMINATE IN ACCORDANCE WITH PROVISIONS OF DOD DIRECTIVE

5230.25." WHEN IT IS TECHNICALLY INFEASIBLE TO USE THE ENTIRE STATEMENT, AN ABBREVIATED MARKING MAY BE USED, AND A COPY OF THE FULL

STATEMENT ADDED TO THE "NOTICE TO ACCOMPANY RELEASE OF EXPORT-CONTROLLED DATA" REQUIRED BY DOD DIRECTIVE 5230.25 (REFERENCE C)

Block 14:

The contractor shall provide notification within 7 calendar days detailing the National Stock Number (NSN), document number, quantity, and date of receipt for assets sent to the contractor in support of an overhaul / maintenance / repair program. The contractor shall submitted a report showing how many assets were repaired, scrapped and shipped back to the Government.

The contractor shall establish the capability to determine condition codes of assets within 5 calendar days of receipt for assets deemed urgent by the Government (eg PRI 1 would be urgent or by Contracting Officers Representative's (COR). direction). The contractor shall review and test new receipts based on priorities established by the Government, and upon direction from the COR. The contractor shall provide test results in a spreadsheet form that includes the following information for each asset tested that month: Weapon System, Location (Ft. Hood or outside Continental United States (OCONUS) location), Part Number, National Item Identification Number (NIIN), Nomenclature, Serial Number, LRU/SRU designation, Test Date, Description of Repair Needed, Failure Mode, Status, and Turn in Document

Number for all assets, DD 1577-2 TAG information for NEOF Assets.

All shipping documentation accompanying repaired assets returned to the Government must have the following statement annotated in the remarks portion of the shipping document: "RETURN FROM REPAIR, MARK FOR: (the document number under which the assets were received at the contractor location). NOTE: The quantity shipped under each document number must not exceed the quantity received under that same document number.

ATT/EXH ID

PAGE

Exhibit A

The contractor shall send an e-mail notice to notify the Government that erroneous data was sent in a prior transmission. The data must list the Document number, NSN, Document Identifier Code (DIC) and date/transmission the erroneous data was sent. The contractor shall provide a detailed explanation of the errors and the corrective action taken within 3 calendar days.

The contractor shall provide documentation of successful test results for all tests required by the applicable TMs. The contractor shall document and submit all test results as described above.

All data being provided by the contractor shall be delivered electronically in the format defined in data item description through https://safe.apps.mil/ and email to:

Contractor Accountability Teams mailbox:mailto:usarmy.detroit.tacom.mbx.ilsc-contractor-accountability-team@mail.mil.

AMSTA-LCG-AA = sarah.m.gregory11.civ@mail.mil

CCTA-AHM-B = roxanna.m.genova-lasecki.civ@mail.mil

17. PRICE GROUP:

18. ESTIMATED TOTAL PRICE:

A. CONTRACT LINE ITEM NO.: A002

B. EXHIBIT: A

C. CATEGORY: TDP_ T M_ OTHER X__

D. SYSTEM/ITEM: TEAM ARMOR PARTNERSHIP (TAP)

E. CONTRACT/PR NO.: TBD

F. CONTRACTOR: TBD

1. DATA…