Attachment 0005 CM Scope

Attachment 0005- Configuration Management (CM) Scope

C.3.5.1 Configuration Management (CM) Requirements: The Contractor shall execute a CM program for configuration planning and management, identification, change management (control), status accounting, verification, audit, and data management of the FHTV Protection Kits to meet all aspects of this scope of work, the contract, and TDP requirements. The Contractor shall comply with the Society of Automotive Engineers (SAE) International, Electronic Industries Association (EIA) specification 649-1 (SAE EIA-649-1, "Configuration Management Requirements for Defense Contracts”) and use SAE EIA-649 “Configuration Management Standard” as a reference for CM and data management. This contract does not contain software and therefore references to software within SAE EIA-649-1, "Configuration Management Requirements for Defense Contracts”, do not apply.

C.3.5.1.1 Configuration Management Plan (CMP): The Contractor shall prepare, maintain, and deliver a CMP IAW SAE EIA-649-1, "Configuration Management Requirements for Defense Contracts” and CDRL A013, “Configuration Management Plan”.

C.3.5.1.2 Configuration Identification: The Contractor shall organize, define, identify, and maintain consistency of the FHTV Protection Kit Product Configuration Documentation (PCD). The definition of PCD is located in SAE EIA-649-1 “Configuration Management Requirements for Defense Contracts”, Section 2.3.

C.3.5.1.3 Configuration Control and Product Baseline: The Government has configuration control of the FHTV Protection Kit Product Baseline (PBL) at contract award. The Government provided FHTV Protection Kit TDPs (found at Attachments 0001-0005) are the official production baseline configuration. The Contractor shall not incorporate a change or variance to the production configuration baseline without prior written approval by the Contracting Officer; this includes Configuration Control Board (CCB) approved Engineering Change Proposals (ECP), Value ECPs (VECP), and Request for Variances (RFV).

C.3.5.1.3.1 The Contractor shall maintain the FHTV Protection Kits PBL(s) throughout the contract performance period to ensure the status of the design can be determined during the life cycle. The Contractor shall ensure each succeeding PBL is traceable to, and a detailed extension of, the preceding PBL. The Government will review configuration baseline status at the Initial Design Review, Program IPT Meetings, PMRs, and Final Design Review.

C.3.5.1.4 Indentured Bill of Material (IBOM): The Contractor shall create and maintain an Indentured Bill of Material (IBOM) IAW CDRL A005 “Indentured Bill of Material” and incorporate approved changes. The Contractor shall update and deliver the IBOMs incrementally to incorporate Government approved changes throughout the contract period of performance.

C.3.5.1.5 Product and Enterprise Identifiers: Product identifiers are the Part or Identifying Number (PIN). The Contractor shall not use National Stock Numbers (NSNs) to establish unique product and enterprise identification. Enterprise identifiers are the Commercial and Government Entity (CAGE) code. The Contractor shall comply with item identification (i.e., PIN-CAGE) and marking requirements to identify FHTV Protection Kit products and their PCD, in accordance with the following:

C.3.5.1.5.1 SAE EIA-649-1, “Configuration Management Requirements for Defense Contracts” Configuration Identification and Configuration Identifiers (sections 3.2 through 3.2.1 and 3.2.4 through 3.2.4.2 in the 2014 version).

C.3.5.1.5.2 ASME Y14.100, “Engineering Drawing Practices” Marking for item identification requirements (Appendix B-6 and Section 4.25 in 2013 version).

C.3.5.1.5.3 ASME Y14.100, “Engineering Drawing Practices” Numbering, Coding, and Identification requirements (Appendix D and Section 6 in 2013 version).

C.3.5.1.5.4 ASME Y14.24, “Types and Applications of Engineering Drawings” Item Identification and Administrative Control Numbers for Modifying, Control, and Special Application drawings, (Sections 8, 10, and 15, in 2012 version).

C.3.5.1.5.5 ASME Y14.24, “Types and Applications of Engineering Drawings” selection of types of drawings (Appendix A, Table A-1, and Fig A-1 in 2012 version)

C.3.5.1.5.6 MIL-STD-31000B and TDP requirements in Attachment 0013-Production Government Format Technical Data Package.

C.3.5.1.6 Identifier Requirements:

C.3.5.1.6.1 Government Original Design Activity (ODA) Products The Contractor shall use Government identifiers when the Government is the ODA. The Government is the ODA for all FHTV Protection Kit products developed or modified under this contract. Army Ordnance Part Numbers (AOPNs) are the same as Government PINs for Army products.

C.3.5.1.6.2 FHTV Protection Kit Unique Products - Government PIN-CAGE:

The Contractor shall assign a Government PIN-CAGE as unique identifiers to products newly designed or modified under this contract to meet the Government’s FHTV Protection Kit products requirements. The Contractor shall assign Government PIN-CAGE to PCD documenting products on altered item, vendor item control, or source control drawings and 3D models. For joint programs, the Contractor shall segregate the products by Government design activity and request a unique range of PINs, for each Government CAGE code. The Contractor shall request Government-issued PINs by e-mail to the FHTV Protection Kit Lead Engineer based on the following:

C.3.5.1.6.2.1 1) The Contractor shall use the following PIN format for TACOM design activity products: The end item (e.g., top-level assembly) shall utilize a 7-character TACOM PIN (i.e., 87Txxxx). Kits (e.g., repair, accessory, conversion kits) shall utilize a 7-character TACOM PIN (i.e., 57Kxxxx). All other details, assemblies, instructions, installations, shall utilize an 8-digit TACOM PIN (i.e., 12xxxxxx). The CAGE code for TACOM PINs shall be 19207.

C.3.5.1.6.2.2 The Contractor shall use the PIN-CAGE format for Non-TACOM design activity products.

C.3.5.1.6.3 Existing Government ODA Products. The Contractor shall retain the Government PIN-CAGE and not re-identify existing products with Government-issued CAGE Codes and PINs that are used as-is.

C.3.5.1.6.4 Modified Products: When one or more products are modified under this contract to the point that they are not interchangeable with the original product or the next higher assembly, the Contractor shall also identify the new next higher assembly(s) up to the level at which interchangeability is re-established. The Contractor shall maintain configuration records that links or otherwise retains history of the original part number and CAGE code to the new part number and CAGE code.

C.3.5.1.6.4.1 Modified Government Products: Products having Government-issued CAGE Codes and PINs that undergo modification for the FHTV Protection Kits shall reflect a new Government CAGE code and PIN. The Contractor shall request Government-issued CAGE Codes and PINs from the FHTV Protection Kit Lead Engineer. The Contractor shall maintain configuration records that link or otherwise retain history of the original Government part number and CAGE code to the new Government part number and CAGE code for the modified part.

C.3.5.1.6.5 Other Design Activity Products:

The Contractor shall use the PIN-CAGE format for product and enterprise identifiers, C.3.5.1.6.5.1 When Products Defined by Standardization Documents exist:

C.3.5.1.6.5.1.1 The Contractor shall comply with MIL-STD-31000, “DoD Standard Practice Technical Data Packages” and ASME Y14.100 “Engineering Drawing Practices”, Appendix D to identify products defined by standardization documents.

C.3.5.1.6.5.1.2 The Contractor shall investigate and convert Contractor, Supplier, Vendor, or other PINs to the PIN-CAGE format and use the CAGE of the corresponding standardization document. The Contractor shall refer to

C.3.5.1.6.5.1.2.1 Public Logistics Data (PUB LOG) Federal Logistics Information Services (FLIS) at:,http://www.dla.mil/HQ/InformationOperations/LogisticsInformationServices/FOIAReading.aspx, for researching part numbers

C.3.5.1.6.5.1.2.2 The Defense Logistics Agency (DLA) customer service at: http://www.dla.mil/CustomerSupport.aspx, for assistance with web access, accounts, or assistance in finding part numbers for products defined by standardization documents.

C.3.5.1.6.5.2 When Commercial and Noncommercial Products exist:

Commercial and noncommercial products (not otherwise defined by standardization documents) consist of the Contractor’s purchased items controlled by vendor documentation as well as the Contractor proprietary products that were privately developed 100% with the Contractor’s funds. The Government requires that all purchased items, including any proprietary products for which the Contractor has not granted the Government additional rights, shall be documented on control drawings and 3D models (per decision diagram in ASME Y14.24 “Types and Applications of Engineering Drawings”, Fig. A-1). The Contractor shall document these products in accordance with ASME Y14.24, Section 10 and Appendix A, using a Government PIN-CAGE format. The Contractor shall deliver Vendor Item Control Drawings (VICDs) and Source Control Drawings (SCDs), for these unaltered commercial and noncommercial products. These VICDs and SCDs provide form, fit and function requirements without divulging Contractor proprietary information, therefore, eliminating Contractor-imposed restrictive markings on the PCD for these products. The Contractor shall not use Procurement Control Drawings within the TDP.

C.3.5.1.6.6 Change Management: The Contractor shall propose changes to the production baseline configuration via the submission of ECPs, VECPs and RFVs. ECPs affect a permanent change to the production baseline configuration and the FHTV Protection Kits TDP. VECPs affect permanent changes to the production configuration where cost savings are applicable due to impacts related to the FHTV Protection Kits TDP, Integrated Logistics Support (ILS), Manpower Personnel Integration (MANPRINT), and Life Cycle Cost (LCC). RFVs temporarily deviate or waive from production baseline requirements for a range of serial numbers. All ECP, VECP and RFV submittals shall contain supporting data in order for the Government to evaluate each proposed change.

The Contractor shall include new technical data and redlined technical data with each change submittal. The Contractor shall develop and deliver all new and redlined technical data IAW the following:

C.3.5.1.6.6.1 MIL-STD-31000, “Department of Defense Standard Practice: Technical Data Packages”

C.3.5.1.6.6.2 Attachment 0001- Production Government Format Technical Data Package.

C.3.5.1.6.6.3 Attachment 0002-TARDEC CAD SOP

C.3.5.1.6.6.4 ASME Y14.100, “Engineering Drawing Practices”

C.3.5.1.6.6.5 ASME Y14.34, “Associated Lists”

C.3.5.1.6.6.6 ASME Y14.35, “Revision of Engineering Drawings and Associated Documents”

C.3.5.1.6.6.7 ASME Y14.24, “Types and Applications of Engineering Drawings”

The Contractor shall use tolerance methods per ASME Y14.5, Dimensioning and Tolerancing. Engineering drawings and associated lists shall provide the design, engineering, manufacturing and quality assurance information sufficient to procure and or manufacture an item without additional design engineering effort or recourse to the original design activity. An item, component, or process that has been, or will be developed exclusively with Government funds by the Contractor or Subcontractor(s) shall be delivered to the Government with unlimited rights. For data deliverables, the Contractor shall deliver to the Government all technical data and computer software required under this Scope of Work (SOW). The Contractor shall deliver, mark, and grant rights in all noncommercial technical data and computer software deliverables in accordance with DFARS 252.227-7013 and 252.227-7014.

C.3.5.1.6.7 Engineering Release System: Engineering release formally approves configuration documentation and makes configuration documentation available for its intended use. The Contractor shall have an engineering release process (e.g., Change Notice, Engineering Change Notice (ECN), Engineering Release Record (ERR)) in place at contract award to incrementally incorporate approved changes into the hardware and PCD. The Contractor shall release new PCD and approved changes to the PCD by engineering release to establish and update the PBL, verifying incorporation of approved changes, for the entire contract performance period. The Contractor shall record this release information in the Configuration Status Accounting (CSA) system and provide CSAI updates IAW CDRL A015 “Configuration Status Accounting Information” and at Program IPT Meeting and PMRs. The Contractor shall have an engineering release process in place at contract award and include a detailed description of the Contractor’s release process in the CMP.

C.3.5.1.6.8 Engineering Release Record Submittal And Approval: The Contractor shall prevent premature release of PCD related to an approved engineering change until the Government has approved an ERR within the PDMLink workflow. The Contractor shall prepare and deliver the Engineering Release with revised PCD for FHTV Protection Kit PBL changes to release PCD products in accordance with CDRL A016, “Engineering Release Record”. The Contractor shall not incorporate multiple engineering changes on a single ERR. The Contractor shall not submit missing, unreleased, or erroneous down parts, references, interface data, or other deficiencies in the ERR package.

C.3.5.1.6.8.1 ERR Number: The Contractor shall request ERR number(s) from the FHTV Protection Kit Lead Engineer prior to finalization of changes to FHTV Protection Kit PCD. The Contractor shall use the Government-assigned 3-character prefix and the 5-character alphanumeric suffix as the authorization number to release TDP documentation. When preceded by an approved engineering change, the ERR number shall be the same as the engineering change number. The Contractor shall apply the 8-character ERR number in accordance with the TDP requirements in Attachment 0013- Production Government Format Technical Data Package.

C.3.5.1.6.9 Engineering Change Proposals (ECPs): Upon the determination of a need for an engineering change, the Contractor shall prepare and submit all ECPs IAW CDRL A017, “Engineering Change Proposal (ECP) and Value Engineering Change Proposal (VECP). The Contractor shall submit and describe proposed changes to non-CAD digital data (e.g., specifications) IAW CDRL A018, “Notice of Revision (NOR)”. NORs are not required if digital data is electronically marked-up to show proposed changes or if CAD files serve as CAD mark-ups or ‘preliminary’ data showing the revisions incorporated, with a copy of the previous revision for comparison. ECP submittal requires the entire document or drawing (all sheets). The Contractor shall e-mail requests for ECP Numbers to the FHTV Protection Kit Lead Engineer.

C.3.5.1.6.9.1 Change Classification-Major (Class I): The Government defines changes classified as Major (Class I) as defined in form DD 1692, “Engineering Change Proposal”.

C.3.5.1.6.9.2 Change Classification-Minor (Class II): Minor ECPs do not impact the Major (Class I) criteria for changes. The Government defines changes classified as Minor (Class II) as defined in form DD 1692, “Engineering Change Proposal”. The Contractor shall submit the ECP to the cognizant ACO for classification prior to submitting the ECP to the PdM-HTV. The Contractor shall submit the ECP package to PdM-HTV and include ACO concurrence as part of the ECP submittal.

C.3.5.1.6.9.3 ECP Numbers: The Contractor shall request via e-mail to the FHTV Protection Kit Lead Engineer and apply the Government assigned ECP number(s) to all ECPs. The Contractor shall use the Government-assigned 3-character prefix and the 5-character alphanumeric suffix as the ECP number. The Contractor shall use each number on an individual basis as a control identifier for ECPs. The Contractor shall retain the first submission assigned ECP number of a change proposal for all subsequent submissions of that change proposal, using C1, C2, etc., as a suffix for minor, corrected ECPs, and R1, R2, etc., as a suffix for major, reworked ECPs. The Contractor shall maintain ECP records that track the usage of each number in terms of when or where usage.

C.3.5.1.6.10 Value Engineering Change Proposals (VECPs): The Contractor shall prepare and submit VECPs IAW CDRL A017, “Engineering Change Proposal (ECP) and Value Engineering Change Proposal (VECP)” and pursuant to the Value Engineering Clause FAR 52.248-1.

C.3.5.1.6.11 Variances. When Contractor requests to deviate from the FHTV Protection Kit requirements for a specific number of kits, the Contractor shall submit an RFV IAW CDRL A019, “Request for Variance”. The Contractor shall use the Government-assigned 3-character prefix and the 5-character alphanumeric suffix as the RFV number. The Contractor shall request RFV numbers via e-mail to the FHTV Protection Kit Lead Engineer. The Government will not approve Critical RFVs, as they have a profound impact on safety. The Government may reject recurring variances effecting a change to the Final Product Baseline documentation

C.3.5.1.6.12 Contractor Initiated Changes

C.3.5.1.12.1 Review, Approval, and Implementation: The Government reserves the right to require the contractor to perform additional validation tests to verify acceptability of any contractor proposed changes at no additional cost to the Government prior to Government approval of the proposed change. The Government will determine the extent of the additional testing required. The Procuring Contracting Officer (PCO) will notify the Contractor via contract modification of the Government's approval and the effectivity date. The Contractor shall incrementally update the PCD, including the IBOM, incorporating each approved change, and deliver a copy of the resulting documentation via CDRL A016, “Engineering Release Record”.

C.3.5.1.6.12.2 Responsibility for Failure Due to Changes: The Government’s approval of a Contractor requested change does not relieve the Contractor from adherence to all other contract requirements and the Contractor’s responsibility to furnish conforming parts. The Contractor shall accept full responsibility for failure that renders the FHTV Protection Kit non-mission capable.

C.3.5.1.12.3 Responsibility for Cost of Changes:

(1) The Contractor shall be responsible for all costs associated with Contractor initiated changes affecting the FHTV Protection Kit PBL and PCD. The Government will not be responsible for additional costs the Contractor incurs associated with changes the Contractor submits unless the PCO approves the change and modifies the requested change into the contract. The Contractor shall use the ECP process to identify costs for Contractor proposed changes to enhance FHTV Protection Kit performance.

(2) When a change results in reduced costs to the Contractor, the Government may obtain an equitable reduction in contract price. The Contractor shall provide cost and pricing data in order for the Government to determine price reasonableness. The Contractor may be required to certify cost impacts and the Government may conduct post-change approval audits.

C.3.5.1.12.4 Government Initiated Changes: In the event the Government requires an engineering change, the PCO will solicit the Contractor for technical and price proposal (with certified cost and pricing data when required) covering the configuration change(s). The Contractor shall furnish the proposal at no additional cost to the Government.

C.3.5.1.12.5 Changes Impacting Data Rights.

Once the Contractor grants additional data rights to the Government for a given item, component, or process, the Government will retain those additional rights for an alternate, replaced, swapped, switched, or substituted item, component, or process. The Contractor shall not restrict the Government’s data rights beyond the rights granted for the original items, components, or processes.

C.3.5.1.12.6 Effectivity Certification.

The Contractor shall incorporate changes resulting from Government approved ECPs, VECPs and RFVs to the FHTV Protection Kit production line at a single end item cut-in point (a single kit)within six months of the approved change. The Contractor shall not execute changes until receipt of PCO change approval via contract modification. The modification will confirm effectivity certification and the Contractor shall maintain the original effectivity point certification on file for all Government approved ECPs, VECPs, and RFVs. The Contractor shall use a CSAI system to maintain effectivity information and provide the information per CDRL A015, “Configuration Status Accounting Information”.

C.3.5.1.12.7 Obsolescence of Components.

The Contractor shall notify the FHTV Protection Kit APM and the FHTV Protection Kit Lead Engineer in writing via email of component obsolescence within ten business days of discovery. The Contractor shall include a plan for replacing the obsolete component and the anticipated ECP submittal date within the notification.

C.3.5.1.12.8 Configuration Status Accounting (CSA) Information The Contractor shall comply with SAE EIA-649-1, “"Configuration Management Requirements for Defense Contracts” Configuration Status Accounting (CSA) requirements. The Contractor shall record and maintain CSA information for the term of this contract. The Contractor shall prepare and deliver CSA information IAW CDRL A015 “Configuration Status Accounting (CSA) Information”. The Contractor shall include performance metrics for CSA analysis as listed in SAE EIA-649-1, “"Configuration Management Requirements for Defense Contracts” section 3.11. CSA Information shall include product serial/registration number effectivity cut-in point and date and also include SAE EIA-649-1, paragraphs 3.3.2(6), and 3.4.1(3).e, f, h, and j. The Contractor shall update the PCD incrementally, as changes are approved, and reported in sync with the time period covered by each CSA submittal The Contractor shall prepare to discuss monthly submissions at Program IPT Meetings and PMRs.

C.3.5.1.12.9 Functional Configuration Audit (FCA)

A Functional Configuration Audit is not required and therefore section 3.5.2 through section 3.5.2.1 (3) of SAE EIA-649-1 “"Configuration Management Requirements For Defense Contracts” do not apply to this contract.

C.3.5.1.12.9.1 Physical Configuration Audit (PCA)

C.3.5.1.12.9.2 PCA Plan: The Contractor shall submit a PCA Plan IAW SAE EIA-649-1 “"Configuration Management Requirements for Defense Contracts” and CDRL A020, “Physical Configuration Plan (PCA Plan)”.

C.3.5.1.12.9.3 Physical Configuration Audit (PCA): FHTV Protection Kit stakeholders will witness PCA events throughout the PCA process at the Contractor’s facilities. The Contractor shall conduct a PCA utilizing First Article Inspection (FAI) build kits and surrogate data collected from the Component First Article Test (CFAT) and FAI. The Government will commence the PCA 21 business days after Contractor receipt of the initial hardware shipment. During the PCA the Government will verify that the FHTV Protection Kit hardware satisfies the TDP (Attachments 0001-0005) and contract requirements. The Contractor shall perform the PCA on the entire FHTV Protection Kit including dimensions, tolerances, material certifications, welding, painting, drawing notes, and kit packaging. The Contractor shall complete the PCA ten business days after the Contractor completes the FAI kit builds. The Contractor shall have each of the FAI build kits available for reference during the PCA. Incongruences between the Contractor’s FAI build pilot kits and their respective TDPs inclusive of Government approved ECPs, VECPs, and RFVs will result in a deficient PCA. The Contractor shall take action to correct the deficiencies.

The Contractor shall provide PCA results as part of the PCA Configuration Audit Summary Report IAW CDRL A021, “Physical Configuration Audit Report”.

C.3.5.1.12.9.4 Contractor PCA Responsibilities: The Contractor shall comply with the PCA responsibilities in SAE EIA-649-1 "Configuration Management Requirements For Defense Contracts”, sections 3.5.3.1(1)a1 through 8, 11, 12, 14 through 21, (2),(3), and shall also:

C.3.5.1.12.9.4.1 Identify support personnel and establish teams C.3.5.1.12.9.4.2 Participate with PdM-HTV during kick-off, audit activities, and closeout meetings, adhere to ground rules, daily schedule, audit and closeout actions.

C.3.5.1.12.9.4.3 Provide a safe, indoor physical location at the production facility for the Government to witness the PCA execution, conduct PCA planning reviews, perform PCA part examination and data gathering, and lead PCA submission events per the PCA plan. The audit location shall not interfere with production or other shop floor activities.

C.3.5.1.12.9.4.4 Provide access to a copy machine for PdM-HTV and Government personnel to utilize during the PCA.

C.3.5.1.12.9.4.5 Provide access to CAD files, CAD software and CAD viewers to open, review, and manipulate CAD files.

C.3.5.1.12.9.4.6 Obtain and have readily available in the audit location:

i. Each assembly, subassembly, and part subject to audit. The Contractor shall provide hard copies of all assembly, subassembly, and part drawings.

ii. All engineering changes and variances applicable to each part undergoing the audit

iii. Company manuals and other internal documents applicable to each part undergoing the audit

iv. Sufficient outlets for plugging in laptops

v. Wi-Fi or LAN access to the Government network

vi. Appropriate, calibrated tools for use in verifying part dimensions

vii. Safety equipment C.3.5.1.12.9.4.7 Return parts to their location after audit completion C.3.5.1.12.9.4.8 Incorporate Government approved ECPs resulting from the PCA to the Protection Kits and Protection Kit parts used for the PCA.

For SAE EIA-649-1 "Configuration Management Requirements For Defense Contracts” section 3.5.3.1(1)b, “FCA” shall be substituted with “since the beginning of the contract”. The paragraph shall be “Identification of any difference between the physical configurations of the selected production CI(s) and the development CI(s) used since the beginning of the contract, including certifications or demonstrations that these differences do not degrade the functional characteristics of the selected CI(s)”.

C.3.5.1.12.11 Product Data Management System (PDMS): The Contractor shall use an authoritative product data, engineering, or configuration management system and processes to effectively manage, securely store, release, validate, and track multiple versions and iterations of the as-designed and as-built configuration baselines. The Contractor shall ensure the PDMS contains management of product structures, product definition information, product operational information, Government-Furnished Information (GFI), changes, variances, and other Product Configuration Index (PCI).

C.3.5.1.12.11.1: PDMLink is the Government's PDMS for Configuration Management, Product Data, and TDPs. The PDMLink workflow is the automation of a business process in whole or in part, during which participants pass documents, information, or tasks among each other for action, according to a set of procedural rules. A workflow instance coordinates user and system participants, together with data resources, to achieve defined objectives by set deadlines. The Contractor shall submit all ECPs, VECPs, RFVs, NORs, and ERRs via PDMLink.

C.3.5.1.12.11.2 PDMLink Training: The Contractor shall attend PDMLink training and comply with requirements of Windchill PDMLink. The Contractor may request training via a formal e-mail request to the FHTV Protection Kit Lead Engineer.

The Government will provide training at the Contractor’s facility.

C.3.5.1.12.11.3 PDMLink Access: The Contractor shall obtain a login and password to PDMLink for Contractor personnel responsible for either object creation or submittal of ERRs, ECPs, VECPs, and RFVs to the Government. Contractor personnel who may have a need to search, view, and print in PDMLink, should also obtain a login and password for read-only permissions. Contractor personnel who require access to PDMLink shall coordinate with the FHTV Protection Kit Lead Engineer. The ACE Support Team Representative will assist in access form completion. Forms are at https://ace2.tacom.army.mil/newuser/. Complete the ACE Access Request Form. The Contractor shall submit a copy of the contract Section C with each PDMLink access request form.

C.3.5.1.12.11.4 PDMLink Submittal:

The Contractor shall notify the FHTV Protection Kit Lead Engineer via e-mail within one business day of submission of ERRs, ECPs, VECPs, or RFVs to the PDMLink workflow. For deliverables classified SECRET, the Contractor shall submit an Unclassified-FOUO report to the PDMLink workflow to that contains the date the SECRET deliverable was submitted via registered mail to the FHTV Protection Kit classified mailing address:

Security Manager

PEO CS&CSS

AMSTA-CS-S

Mail Stop#105 6501 E. 11 Mile Rd.

Warren, MI 48397-5000