ࡱ> 9 bjbj 4Tdd48-B LYoooY)Y)Y)fBhBhBhBhBhBhB$EYHBY)Y)Y)Y)Y)Boo By.y.y.Y)FoofBy.Y)fBy.y...o`M켽)F.RBB0B.I)VI.I.TY)Y)y.Y)Y)Y)Y)Y)BB;,>Y)Y)Y)BY)Y)Y)Y)IY)Y)Y)Y)Y)Y)Y)Y)Y) : Where necessary, to identify the applicable parties under the following clauses, Contractor shall mean Seller, Contracting Officer shall mean ϰſֱ Procurement Representative, Contract means this subcontract and Government means ϰſֱ. However, the words Government and Contracting Officer do not change: (1) when a right, act, authorization or obligation can be granted or performed only by the Government or the Prime Contract Contracting Officer or duly authorized representative, including but not limited to (i) audit rights to Sellers proprietary business records or (ii) any indemnification or limitation of liability obligation, which obligation shall remain with the Government; (2) when title to property is to be transferred directly to the Government, and (3) when the Government is granted ownership or other rights to Sellers intellectual property or technical data. Full Text Clauses Section D Clauses -- Packaging and Marking: D-01 PACKAGING AND MARKING OF TECHNICAL DATA (APR 2009) (Applicable to all purchase orders/subcontracts involving the shipment of data and documentation.) Technical data items shall be preserved, packaged, packed, and marked in accordance with the best commercial practices to meet the packaging requirements of the carrier and insure safe delivery at destination. Classified reports, data and documentation shall be prepared for shipment in accordance with the current National Industrial Security Program Operating Manual (NISPOM), DOD 5220.22-M. D-02 PACKAGING AND MARKING OF HARDWARE ITEMS (APR 2009) (Applicable to all purchase orders/subcontracts involving the shipment of any hardware.) a. The contractor shall utilize best commercial practices for the preservation, packaging, marking and labeling of any hardware delivered under this contract to insure safe delivery at final destination. However, the contractor should also note the requirements of DFARS 252.211-7003, Item Identification and Valuation, if applicable. b. Packaging and marking of hazardous materials shall comply with Title 49 of the Code of Federal Regulation and the International Maritime Dangerous Goods Code. c. MARKING INSTRUCTIONS FOR MISSILE DEFENSE AGENCY (MDA) REQUIREMENTS Request for marking instructions shall be submitted electronically at least 90 days prior to required delivery date, the PCO and COR identified in clause G-01. Section G Clauses Contract Administration Data: G-13 NOTICE OF THE GOVERNMENT'S USE OF OUTSIDE CONTRACTORS TO REVIEW SUBMITTED INVOICES, PAYMENT REQUESTS, AND MATERIAL INSPECTION AND RECEIVING REPORTS (MAY 2009) (Applicable to all purchase orders/subcontracts.) The Government may utilize support contractors to assist the Government in the review and evaluation of the offeror's invoices, payment requests, material inspection and receiving reports, and similar requests for payment or evidence of delivery. These contractors will be provided access to these and other records which may contain the proprietary information of the offeror, to include awarded contracts, to support Government officials in reviewing and reconciling invoices, payment records, and the Government's financial and budgetary records, and in facilitating the timely payment of submitted invoices. The support contractors are prohibited from obtaining proprietary information to which their employees will have access in the performance of their responsibilities and are required to promptly notify the contracting officer of any breach of their employees' non-disclosure obligations. Each of the contractor employees has also been required to execute a non-disclosure agreement which acknowledges their responsibilities to only use proprietary information in performance of the above tasks and for no other reason; that they will not share proprietary information with their employers; that they will not use such information for personal or other benefit; and that they will promptly notify their employers of any breaches of their responsibilities. Unless the offeror specifically objects in writing, the offeror agrees, by the submission of a proposal, to allow the Government's support contractors to have access to the offeror's proprietary information for the purposes described above. Section H Clauses -- Special Contract Requirements: H-06 INSURANCE (APR 2009) (Applicable to all purchase orders/subcontracts.) In accordance with FAR Part 28.307-2, the Contractor shall maintain the types of insurance and coverage listed below: TYPES OF INSURANCE MINIMUM AMOUNT Workmen's Compensation and all occupational disease As required by Federal and State law Employer's Liability including all occupational disease $100,000 per accident when not covered by Workmen's Compensation above General Liability (Comprehensive) Bodily Injury $500,000 per occurrence Automobile Liability (Comprehensive) Bodily Injury per person $200,000 Bodily Injury per accident $500,000 Property Damage per accident $ 20,000 H-08 PUBLIC RELEASE OF INFORMATION (JUN 2013) (Applicable to all purchase orders/ subcontracts. All references to communications and data submittals to the COR shall be through the ϰſֱ Procurement Representative.) a. The policies and procedures outlined herein apply to information submitted by the Contractor and his subcontractors for approval for public release. Prior to public release, all information must be cleared as shown in the National Industrial Security Program Operations Manual (DoD 5220.22-M). At a minimum, these materials may be technical papers, presentations, articles for publication and speeches or mass media material, such as press releases, photographs, fact sheets, advertising, posters, compact discs, videos, etc. b. All materials which relate to the work performed by the contractor under this contract must be submitted to MDA for review and approval prior to release to the public. Subcontractor public information materials must be submitted for approval through the prime contractor to MDA. c. Upon request, the Contracting Officers Representative (COR) will provide the contractor the MDA Form 003, Security and Policy Review or any superseding MDA form. The contractor must complete Sections A-C and E-H of the Form 003 (or comply with the instructions of any superseding form) and submit it to the COR with the materials to be cleared. If the information was previously cleared, provide the Public Release Case Number, if available, and a copy of the previous document highlighting the updated information. d. The contractor must submit the following to the COR at least 60 days in advance of the proposed release date: (1) the completed Form 003 and one (1) electronic copy of the material to be reviewed. File size must not exceed 25MB; and, (2) a written statement, including: (a) to whom the material is to be released; (b) the desired date for public release; (c) a statement that the material has been reviewed and approved by officials of the contractor or the subcontractor, for public release; and, (d) the contract number. e. The items submitted must be complete. Photographs must have captions. f. Outlines, rough drafts, marked-up copy (with handwritten notes), incorrect distribution statements, For Official Use Only (FOUO) information, export controlled, or International Traffic in Arms Regulations (ITAR) information will not be accepted or cleared. g. Abstracts or abbreviated materials may be submitted if the intent is to determine the feasibility of going further in preparing a complete paper for clearance. However, clearance of abstracts or abbreviated materials does not satisfy the requirement for clearance of the entire paper. h. The MDA Director of Public Affairs (MDA/PA) is responsible for coordinating the public release review. MDA/PA will work directly with the COR if there are questions or concerns regarding submissions. MDA/PA will not work with contractors who have not gone through their COR. i. The COR will notify the contractor of the agencys final decision regarding the status of the request. j. Once information has been cleared for public release, it is in the public domain and must always be used in its originally cleared context and format. Information previously cleared for public release but containing new, modified or further developed information must be submitted again for public release following the steps outlined in items a. through h. above. H-09 ORGANIZATIONAL CONFLICT OF INTEREST (JUN 2012) (Applicable to all purchase orders/ subcontracts.) a. Purpose: The primary purpose of this clause is to aid in ensuring that: (1) the Contractor's objectivity and judgment are not biased because of its present or planned interests which relate to work under this contract; (2) the Contractor does not obtain unfair competitive advantage by virtue of its access to non-public information regarding the Government's program plans and actual or anticipated resources; and (3) the Contractor does not obtain unfair competitive advantage by virtue of its access to proprietary information belonging to others. b. Scope: Organizational Conflict of Interest (OCI) rules, procedures and responsibilities as described in FAR Subpart 9.5 shall be applicable to this contract and any resulting subcontracts. (1) The general rules in FAR 9.505-1 through 9.505-4 and the restrictions described herein shall apply to performance or participation by the Contractor and any of its affiliates or their successors-in-interest (hereinafter collectively referred to as "Contractor") in the activities covered by this contract as prime Contractor, subcontractor, co-sponsor, joint venturer, consultant, or in any similar capacity. (2) The Missile Defense Agency's OCI policy is in Attachment X of this contract. c. Access to and Use of Nonpublic Information: If the Contractor, in performance of this contract, obtains access to nonpublic information such as plans, policies, reports, studies, financial plans, or data which has not been released or otherwise made available to the public, the Contractor agrees that without prior written approval of the Contracting Officer, it shall not: (1) use such information for any private purpose; (2) release such information. d. Access to and Protection of Proprietary Information: The Contractor agrees to exercise diligent effort to protect proprietary information from misuse or unauthorized disclosure in accordance with the provisions of FAR 9.505-4. The Contractor may be required to enter into a written non-disclosure agreement with the third party asserting proprietary restrictions. e. Subcontracts: The Contractor shall include this clause in consulting agreements, teaming agreements, subcontracts, or other arrangements for provision of services or supplies of any tier. The terms "contract", "Contractor", and "Contracting Officer" shall be appropriately modified to preserve the Government's rights. f. Representations and Disclosures: (1) The Contractor represents that it has disclosed to the Contracting Officer, prior to award, all facts relevant to the existence or potential existence of organizational conflicts of interest as that term is used in FAR Subpart 9.5. To facilitate disclosure and Contracting Officer approval, the Contractor shall complete an OCI Analysis/Disclosure Form for each MDA, Ballistic Missile Defense (BMD), and BMD-related contract or subcontract (form shall be requested from the Procuring Contracting Officer). (2) The Contractor represents that if it discovers an organizational conflict of interest or potential conflict of interest after award, a prompt and full disclosure shall be made in writing to the Contracting Officer. This disclosure shall include a description of the action the Contractor has taken or proposes to take in order to avoid or mitigate such conflicts. g. Remedies and Waiver: (1) For breach of any of the above restrictions or for non-disclosure or misrepresentation of any relevant facts required to be disclosed concerning this contract, the Government may: terminate this contract for default; disqualify the Contractor from subsequent related contractual efforts if necessary to neutralize a resulting organizational conflict of interest; and pursue such other remedies as may be permitted by law or this contract. If, however, in compliance with this clause, the Contractor discovers and promptly reports an organizational conflict of interest (or the potential thereof) subsequent to contract award, the Contracting Officer may terminate this contract for convenience if such termination is deemed to be in the best interest of the Government or take other appropriate actions. (2) The parties recognize that this clause has potential effects which will survive the performance of this contract and that it is impossible to foresee each circumstance to which it might be applied in the future. Accordingly, the Contractor may at any time seek a waiver from the Director, MDA, (via the Contracting Officer) by submitting a full written description of the requested waiver and the reasons in support thereof. H-10 ENABLING CLAUSE FOR BMD INTERFACE SUPPORT (APR 2009) (Applicable to all purchase orders/subcontracts.) a. It is anticipated that, during the performance of this contract, the Contractor will be required to support Technical Interface/Integration Meetings (TIMS) with other Ballistic Missile Defense (BMD) Contractors and other Government agencies. Appropriate organizational conflicts of interest clauses and additional costs, if any, will be negotiated as needed to protect the rights of the Contractor and the Government. b. Interface support deals with activities associated with the integration of the requirements of this contract into BMD system plans and the support of key Missile Defense Agency (MDA) program reviews. c. The Contractor agrees to cooperate with BMD Contractors by providing access to technical matters, provided, however, the Contractor will not be required to provide proprietary information to non-Government entities or personnel in the absence of a non-disclosure agreement between the Contractor and such entities. d. The Contractor further agrees to include a clause in each subcontract requiring compliance with paragraph c. above, subject to coordination with the Contractor. This agreement does not relieve the Contractor of its responsibility to manage its subcontracts effectively, nor is it intended to establish privity of contract between the Government and such subcontractors. e. Personnel from BMD Contractors or other Government agencies or Contractors are not authorized to direct the Contractor in any manner. f. This clause shall not prejudice the Contractor or its subcontractors from negotiating separate organizational conflict of interest agreements with BMD Contractors; however, these agreements shall not restrict any of the Government's rights established pursuant to this clause or any other contract. H-11 MDA VISIT AUTHORIZATION PROCEDURES (AUG 2014) (Applicable to purchase orders/ subcontracts with scope requiring travel to MDA office(s) in support of meetings/reviews/ briefings) a. The Contractor shall submit all required visit clearances in accordance with current NISPOM regulations. Visit clearances shall identify the contract number. For Visit Requests to the National Capital Region send to: JPAS SMO Code: DDAAU4 Missile Defense Agency Attn: Access Control Center 5700 18th Street, Bldg 245 Fort Belvoir, VA 22060-5573 571-231-8249 571-231-8099 FAX  HYPERLINK "mailto:ACC@MDA.mil" ACC@MDA.mil For Visit Requests to Huntsville, AL send to: Missile Defense Agency, JPAS SMO Code: DDAAUH Attn: Visitor Control Bldg 5224 Martin Road Redstone Arsenal, AL 35898 256-450-3214 or 256-450-3216 256-450-3222 FAX  HYPERLINK "mailto:mdaaccesscontrolhsv@mda.mil" mdaaccesscontrolhsv@mda.mil For Visit Requests to Colorado Springs, CO send to: Missile Defense Agency, SMO Code: DDAAUJ Attn: Visitor Control 720 Irwin Drive, Bldg 720 Room 125 Schriever AFB, CO 80912 719-721-0362 or 719-721-8230 719-721-8399 FAX  HYPERLINK "mailto:dosscosvar@mda.mil" dosscosvar@mda.mil b. The COR is authorized to approve visit requests for the Contracting Officer. H-12 CONTROL OF ACCESS TO MDA SPACES AND INFORMATION SYSTEMS (SEP 2013) (Applicable if H-11 applies) a. To maintain the security of the MDA spaces and information systems, the contractor shall notify the COR in writing whenever a prime or subcontractor employee included on the current visit authorization request/letter no longer supports this contract. This requirement shall apply to both contractor and employee initiated termination of services and to temporary suspension of services. b. The contractor will cooperate with COR in facilitating the employees return of all government issued credentials, e.g., badges, common access cards (CACs), SIPRNet tokens. Specifically, upon notification, the COR will work with the organizations Security Operations Center and the MDA Service Desk to ensure timely action to: (1) remove the employee from the current visit authorization request/letter; (2) cancel Government issued credentials pursuant to the visit authorization request/letter; and, (3) terminate the MDA LAN account/access privileges. c. In addition to actions related to MDA access control, the contractor shall maintain accountability for Government issued credentials provided under this contract. Government issued credentials are the property of the U.S. Government and shall not be retained by cardholders upon expiration, replacement, or when the DoD affiliation of employees has been terminated. The contractor shall coordinate with the COR to ensure government issued credentials are retrieved in accordance with local command or installation procedures. Unauthorized possession of an official credential, like a CAC, can be prosecuted criminally under section 701, title 18, United States Code. d. The contractor shall identify the reason for and date of termination or expected period of suspension and submit the notification to the COR within five (5) working days prior to service discontinuation. For unplanned termination or suspension of services, notification shall be made on the same working day as the termination/suspension action. H-28 DISTRIBUTION CONTROL OF TECHNICAL INFORMATION (AUG 2014) (Applicable to all purchase orders/subcontracts.) a. The following terms applicable to this clause are defined as follows: 1. DoD Official. Serves in DoD in one of the following positions: Program Director, Deputy Program Director, Program Manager, Deputy Program Manager, Procuring Contracting Officer, Administrative Contracting Officer, or Contracting Officers Representative. 2. Technical Document. Any recorded information (including software) that conveys scientific and technical information or technical data. 3. Scientific and Technical Information. Communicable knowledge or information resulting from or pertaining to the conduct or management of effort under this contract. (Includes programmatic information). 4. Technical Data. As defined in DFARS 252.227-7013. b. Except as otherwise set forth in the Contract Data Requirements List (CDRL), DD Form 1423 the distribution of any technical documents prepared under this contract, in any stage of development or completion, is prohibited outside of the contractor and applicable subcontractors under this contract unless authorized by the Contracting Officer in writing. However, distribution of technical data is permissible to DOD officials having a need to know in connection with this contract or any other MDA contract provided that the technical data is properly marked according to the terms and conditions of this contract. When there is any doubt as to need to know for purposes of this paragraph, the Contracting Officer or the Contracting Officers Representative will provide direction. Authorization to distribute technical data by the Contracting Officer or the Contracting Officers Representative does not constitute a warranty of the technical data as it pertains to its accuracy, completeness, or adequacy. The contactor shall distribute this technical data relying on its own corporate best practices and the terms and conditions of this contract. Consequently, the Government assumes no responsibility for the distribution of such technical data nor will the Government have any liability, including third party liability, for such technical data should it be inaccurate, incomplete, improperly marked or otherwise defective. Therefore, such a distribution shall not violate 18 United States Code 1905. c. All technical documents prepared under this contract shall be marked with the following distribution statement, warning, and destruction notice identified in sub-paragraphs 1, 2, and 3 below. When it is technically not feasible to use the entire WARNING 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. 1. DISTRIBUTION - DISTRIBUTION STATEMENT D. Distribution authorized to Department of Defense and U.S. DoD contractors only (reason) (date of determination). Other requests for this document shall be referred to MDA/TC Contracting Office. 2. 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 (Title 50, U.S.C., App. 2401 et seq), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25 3. DESTRUCTION NOTICE - For classified documents follow the procedures in DOD 5220.22-M, National Industrial Security Program Operating Manual, February 2006, Incorporating Change 1, March 28, 2013, Chapter 5, Section 7, or DoDM 5200.01-Volume 3, DoD Information Security Program: Protection of Classified Information, Enclosure 3, Section 17. For controlled unclassified information follow the procedures in DoDM 5200.01-Volume 4, Information Security Program: Controlled Unclassified Information. d. The Contractor shall insert the substance of this clause, including this paragraph, in all subcontracts. H-29 COMMERCIAL COMPUTER SOFTWARE LICENSE (MAR 2013) (Applicable to all purchase orders/subcontracts that will use commercial computer software with license restrictions.) a. Unless otherwise approved by the PCO, commercial computer software licenses shall, upon delivery and acceptance, designate the U.S. Government as a contingent licensee, able to replace the Contractor as the primary licensee upon notifying the licensor. A copy of the negotiated license shall be furnished to the PCO. The terms of the licenses cannot be inconsistent with Federal procurement law and must satisfy user needs. This includes the Contractor's / subcontractor's needs for the software to perform this contract and the Government's needs for the software to accomplish the Government's ultimate objectives. At a minimum, this shall include the rights to make an archive copy of the software, to relocate the computer on which the software resides, to re-host the software on a different computer, to permit access by support contractors, and to permit the Government to transfer the license to another contractor. b. Nothing in this clause shall take precedence over any other clause or provision of this contract. Government concurrence, as defined in paragraph a above, does not in any way affect the Government's technical data rights as established by the terms and conditions of this contract. H-33 PROGRAM SYNCHRONIZATION (NOV 2010) (Applicable for all purchase orders/subcontracts.) a. The Missile Defense Agency (MDA) requires the synchronized integration of platforms, sensors, and other components of the BMDS which were or are under separate development by multiple contractors. MDA uses the concept of End-to-End (EtE) performance to serve as the organizing principle that aligns and synchronizes these efforts to achieve the desired operational end-state for the BMDS. Synchronization is defined as the logical alignment of management, design, development, integration, modification, verification and validation, and test activities and processes such that sensors, data links, command and control (C2), and interceptors smoothly and optimally integrate within well-defined and commonly understood requirements and interfaces. b. During the performance of this contract, the Contractor shall provide technical data and other information (to include limited and restricted rights data as defined by DFARS 252.227-7013 and 252.227-7014 or information protected under the Freedom of Information Act Exemption 4) to other Ballistic Missile Defense (BMD) Contractors and Government agencies to facilitate MDA objectives. c. Pursuant to paragraphs (a) and (b) above the Contractor shall negotiate appropriate Associate Contractor Agreements (ACAs) and Non-Disclosure Agreements (NDAs) with other Contractors as necessary to implement the exchanges of technical data and other information required, ensure total system EtE performance, and also to protect technical data and other information from unauthorized disclosure or use. These agreements must not restrict any of the Governments rights established pursuant to this or any other contract. A copy of each ACA and amendments to ACAs shall be provided to the PCO in order for the Government to document the flow of information. d. When associate contracts have been entered into or modified as described in this clause, the associate contractors and general information on the purpose of the associate contracts will be incorporated into this clause as shown below: Company Name Contract # and Description ACA Purpose XXX Complete as Appropriate e. The ACAs shall, at a minimum, include the following general information: (1) Identify the associate contractors and their relationships; (2) Identify the program involved and the relevant Government contracts of the associate contractors; (3) Describe the associate contractor interfaces by general subject matter; (4) Specify the categories of information to be exchanged or support to be provided; (5) Include the expiration date (or event) of the ACA; and (6) Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of technical data or other information and restrictions on employees. f. The Contractors performance with respect to integration support, cooperation, and the exchange and sharing of information with other BMD contractors, shall comply with security classification requirements as outlined in the DD Form 254 incorporated into this contract. g. Nothing in this clause shall take precedence over any other clause or provision of this contract nor does it in any way effect the Governments technical data rights. H-35 INCORPORATING COMMERCIAL AND OPEN SOURCE SOFTWARE (AUG 2012) (Applicable if Seller will be providing anything with computer software. Communication with the Contracting Officer shall be through ϰſֱ.) a. DFARS 252.227-7014(d) requires the written approval of the PCO before the Contractor may incorporate any copyrighted computer software in the software to be delivered under this contract. b. A request for approval to incorporate Commercial Computer Software should be accompanied by a license that conforms with the requirements of the Commercial Computer Software Licenses clause of this contract. c. A request for approval to incorporate Open Source Software must be accompanied by the applicable license, a detailed description of the source of the software and how it has been or will be used, and an explanation of the restrictions imposed and potential risks and liabilities. d. Nothing in this clause shall take precedence over any other clause or provision of this contract. Government concurrence, as defined in paragraph a above, does not in any way affect the Government's technical data rights as established by the terms and conditions of this contract. H-36 CONTRACTOR IDENTIFICATION AND ASSERTION OF RESTRICTIONS ON THE GOVERNMENTS USE, RELEASE, OR DISCLOSURE OF NON-COMMERCIAL TECHNICAL DATA OR COMPUTER SOFTWARE (DEC 2011) (Applicable to all purchase orders/subcontracts.) a. The contractor and its subcontractors shall provide a completed Attachment in accordance with DFARS 252.227-7017 entitled "Identification and Assertion of Restrictions on the Government's Use, Release, or Disclosure of Technical Data or Computer Software" that is signed and dated by a responsible official of the Contractor. This Attachment is incorporated herein by reference as if fully set forth. The Attachment identifies and provides information pertaining to technical data (including computer software documentation) and computer software that the contractor and subcontractors claim to qualify for delivery with less than Unlimited Rights. The contractor agrees not to withhold delivery of the technical data or software based on its claims. The Government shall investigate the validity of the contractor's claims and therefore reserves all its rights regarding the technical data/software in question, to include those rights set forth in: DFARS 252.227-7013, Rights in Technical Data - Noncommercial Items; DFARS 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation; DFARS 252.227-7019, Validation of Asserted Restrictions--Computer Software; DFARS 252.227-7028, Technical Data or Computer Software Previously Delivered To the Government; and, DFAR 252.227-7037, Validation Of Restrictive Markings On Technical Data clauses until a determination is made. b. The contractor shall have, maintain, and follow written procedures sufficient to assure that restrictive markings/legends are used only when authorized by the terms of this contract and shall maintain records sufficient to justify the validity of any restrictive markings/legends on any technical data or computer software or computer software documentation delivered under this contract. The Contractor agrees that the Government has Unlimited Rights as defined by DFARS 252.227-7013 and 252.227-7014 in any deliverable technical data or computer software or computer software documentation not listed in the Attachment and that such data or software will not be subject to any restrictive markings or legends. H-37 INSERTION OF LIMITED OR RESTRICTED RIGHTS (DEC 2010) (Applicable to all purchase orders/subcontracts. Communication with our Customer shall be through ϰſֱ.) a. Hardware items which are subject to Limited Rights in their associated technical data as defined in DFARS 252.227-7013 and software items which are subject to Restricted Rights as defined in DFARS 252.227-7014 shall not be incorporated into the design of any systems, or models/simulations thereof under this contract without the prior written authorization of the PCO. The Contractors request shall include a rough order of magnitude (ROM) estimate to perform development if the data or software cannot be used as requested. If the PCO does not provide a decision within 30 days of the request, the request is considered denied. In the event the PCO authorizes inclusion of the Limited Rights technical data and/or Restricted software, such data or software will be added as an attachment within Section J. b. Using Government assets in an Independent Research and Development (IRAD) project may be authorized on a case by case basis. The Contractors request shall include an offer of consideration for use of such Government assets. The Government will evaluate the request, including the Contractors offer of consideration, and either approve, deny, or offer an alternative form of consideration. Any such consideration will be mutually agreed to by the parties prior to use of Government assets. Consideration should include, at a minimum, specially negotiated rights granting the Government a license for Government Purpose Rights IAW DFARS 252.227-7013 and 252.227-7014 in the subject IRAD project. When the Contractor requests the use of Government assets for an IRAD project, the request shall include the purpose of the IRAD project and the potential benefit to the Government. The Contractor will be required to execute a bailment agreement prior to the transfer or use of Government assets. H-40 INDEMNIFICATION AGAINST UNUSUALLY HAZARDOUS RISKS (APR 2012) (Applicable to purchase orders/subcontracts involving unusually hazardous risks Indemnification is not provided automatically. Subcontract applications are to be sent to ϰſֱ for submittal to the Government.) The legal authority to indemnify contractors for unusually hazardous risks for research, development and testing activities is 10 USC 2354. Previous indemnification from other contracts does not carry over to this resulting contract. The Contractor may request indemnification for effort under this contract at any time. Contractor requests for indemnification must be prepared in accordance with the requirements of FAR 50.104-3. The MDA will fairly process request(s) in good faith to the applicable approving authority within the Department of Defense. The MDA will not, however, make adjustments to the estimated cost or schedule of this contract if indemnification is not granted through this process. H-41 COST ESTIMATING METHODS (MAR 2015) (Applicable to all purchase orders/subcontracts.) The following cost estimating methods shall be used as requested by the Government: a. Planning Estimate - The purpose of a planning estimate is to support Government planning. Planning estimates may only be requested by the PCO. A planning estimate shall be provided to the Government in calendar days or as designated by the PCO. This estimate is very limited in scope, involves minimal pricing ground rules and assumptions from the Government, and is generally comprised of ranges/parametrics. Documentation provided shall be high level scope and funding estimates by Government fiscal year sent via email. b. Rough Order of Magnitude (ROM) - The purpose of a ROM estimate is to support Government budgetary decisions and potential authorization of unpriced actions in the event there is insufficient time for a Not-to-Exceed (NTE) estimate. ROM estimates may only be requested by the PCO. ROM estimates shall be provided to the Government within calendar days or as designated by the PCO. This non-binding estimate is limited in scope, involves limited analysis, and develops a high level baseline to include a high level SOW, schedule, and equipment lists. The ROM estimate is not generated based on formal Basis of Estimates (BOEs) and by design provides limited supporting rationale. Subcontractor input will be included if schedule allows. Documentation provided shall include scope and funding estimates by Government fiscal year in a briefing package submitted by contracts letter to the Government. c. Not-to-Exceed (NTE) - The purpose of an NTE estimate is to support critical Government budgetary decisions, and a binding basis on which to issue unpriced actions. NTEs may only be requested by the PCO. NTE estimates shall be provided to the Government within calendar days or as designated by the PCO. This estimate involves more in depth analysis, develops a baseline to include a statement of work, schedule, and required equipment lists. The NTE estimate shall be based on Basis of Estimate (BOEs) and estimated materials (as required), including supporting rationale. Applicable subcontractor input shall be included as required. Documentation required shall include scope and funding estimates by Government fiscal year in a briefing package submitted by contracts letter to the Government. The Contractors NTE must be valid for a minimum of one hundred eighty (180) calendar days. H-43 IMPACT OF GOVERNMENT TEAM PARTICIPATION/ACCESS (JUN 2012) (Applicable to all purchase orders/subcontracts. Seller is required to notify the ϰſֱ Procurement Representative when Seller is contacted directly by the Government.) The Government/Contractor organizational/interface approach (e.g., Integrated Product Teams, Team Execution Reviews, Technical Interchange Meetings, and/or Working Groups), will require frequent, close interaction and/or surveillance between the Government and Contractor/subcontractor team members during contract performance. For this purpose the Contractor, recognizing its privity of contract with the Government, authorizes the Government to communicate directly with, and where appropriate visit as well as monitor, the Contractor's subcontractors. This access/interface is necessary to support the Government's quality and program management approach which emphasizes systematic surveillance and evaluation techniques used to assess Contractor /subcontractor performance. Government team members may offer advice, information, support, and facilitate rapid Government feedback on team-related products, provide clarification, and review Contractor/subcontractor progress; however, the responsibility and accountability for successfully accomplishing the requirements of this contract remain solely with the Contractor. Neither the Contractor nor the subcontractor shall construe such advice, surveillance, reviews and clarifications by Government team members as Government-directed changes to the terms of this contract. The PCO is the only individual authorized to direct or approve any change to the terms of this contract. H-45 AS IS GOVERNMENT FURNISHED DATA/DOCUMENTATION AND COMPUTER SOFTWARE (JAN 2013) (Applicable to all purchase orders/subcontracts.) All technical data and computer software (as defined in DFARS 252.227-7013 and DFARS 252.227-7014) furnished by the Government is in an "as is" condition without any warranty as to its accuracy, completeness, or adequacy. The contractor shall use this technical data and computer software at its own risk. The Government assumes no responsibility for such furnished data/documentation/computer software nor will the Government have any liability for equitable adjustments to the terms and conditions of this contract should such data/documentation/computer software prove to be inaccurate, incomplete, or otherwise defective. FAR Clauses 52.203-7, Anti-Kickback Procedures (May 2014) 52.203-19, Prohibition on Requiring Certain Internal Confidentiality Agreements or Statements (Jan 2017) (Applicable to all purchase orders/subcontracts, including purchase orders/subcontracts for commercial items.) 52.216-16 Incentive Price Revision Firm Target (Oct 1997) (Applicable if this purchase order/subcontract is a fixed price incentive contract. "Contracting Officer", "contract administrative office" and "Government" mean "ϰſֱ." Paragraph (i) is deleted. The blanks in the clause are completed with the amounts specified in the purchase order/subcontract.) 52.219-9, Small Business Subcontracting Plan (DEVIATION) (Aug 2016) (The version of the clause in DoD Class Deviation 2016-O0009 applies in lieu of the standard FAR version of the clause.) 52.224-3, Privacy Training (Jan 2017) (Applicable if Seller will (1) have access to a system of records; (2) create, collect, use, process, store, maintain, disseminate, disclose, dispose, or otherwise handle personally identifiable information; or (3) design, develop, maintain, or operate a system of records. In paragraph (d), "contracting officer" means "ϰſֱ and the contracting officer.") 52.227-1, Authorization and Consent (Dec 2007) and Alternate I (Apr 1984) (Alternate I also applies.) 52.232-16, Progress Payments (Apr 2012) (Applicable if progress payments are used under this purchase order/subcontract. "Contracting Officer" means "ϰſֱ" except in paragraph (g) where it means "ϰſֱ or Contracting Officer." "Government" means "ϰſֱ" except: (1) in paragraphs (d), (e) and (j)(5) where the term is unchanged and (2) in paragraphs (g) and (i) where it means "ϰſֱ and the Government.") 52.232-17, Interest (May 2014) (Applicable if this purchase order/subcontract contains any clauses which refers to an Interest clause. Government means ϰſֱ.) 52.232-39, Unenforceability of Unauthorized Obligations (Jun 2013) (Applicable to all purchase orders/ subcontracts where software or services will be retransferred to the Government.) 52.243-1, Changes Fixed Price (Aug 1987) and Alternate V (Apr 1984) (Alternate V will also apply if this purchase order/subcontract is for research and development.) 52.243-2, Changes Cost Reimbursement (Aug 1987) and Alternate V (Apr 1984) (Alternate V will also apply if this purchase order/subcontract is for research and development.) 52.244-6, Subcontracts for Commercial Items (Jan 2017) 52.245-9, Use and Charges (Apr 2012) (Applicable for all purchase orders/subcontracts where FAR 52.245-1 is inserted. Communications with the Government under this clause will be made through ϰſֱ.) 52.246-2, Inspection of Supplies Fixed Price (Aug 1996) and Alternate I (Jul 1985) (Alternate I will also apply if this purchase order/subcontract is a fixed price incentive contract.) 52.246-7 Inspection of Research and Development -- Fixed-Price (Aug 1996) (Applicable if this purchase order/subcontract is fixed price and for research and development. "Government" means "ϰſֱ and the Government" in paragraphs (a), (b) and (c). "Government" means "ϰſֱ" in paragraphs (d), (e), and (f). "Contracting Officer" means "ϰſֱ".) 52.246-8, Inspection of Research and Development Cost Reimbursement (May 2001) (Applicable if Seller has a cost reimbursement purchase order/subcontract that is for research and development. "Government" means "ϰſֱ" except (1) in paragraphs (b), (c) and (d) where it means "ϰſֱ and the Government" and in paragraph (k) where the term is unchanged.) 52.249-9, Default (Fixed-Price Research and Development) (Apr 1984) (Applicable if Seller has a fixed price purchase order/subcontract for research and development. "Government" and "Contracting Officer" mean "ϰſֱ" except in paragraph (c) where the term "Government" is unchanged.) DFARS Clauses 252.204-7000, Disclosure of Information (Oct 2016) (Applicable to all purchase orders/subcontracts. In paragraph (b) "Contracting Officer" means "ϰſֱ" and "10 days" means "20 days.") 252.208-7000, Intent to Furnish Precious Metals as Government-Furnished Material (Dec 1991) (Applicable for all purchase orders/subcontracts that involve precious metals.) 252.211-7007, Reporting of Government-Furnished Property (Aug 2012) (Applicable if Seller will be in possession of Government property for the performance of this purchase order/subcontract.) 252.211-7008, Use of Government-Assigned Serial Numbers (Sep 2010) (Applicable to purchase orders/ subcontracts where the seller will be in the possession of Government property for the performance of the purchase order/subcontract. If ϰſֱ will assume responsibility for marking the property, the clause may be excluded from the purchase order/subcontract.) 252.219-7003, Small Business Subcontracting Plan (DoD Contracts) (DEVIATION) (Aug 2016) (The version of the clause in DoD Class Deviation 2016-O0009 applies in lieu of the standard DFARS version of the clause.) 252.219-7004, Small Business Subcontracting Plan (Test Program) (Oct 2014) (Applicable if Seller participates in the DoD test program described in DFARS 219.702.) 252.234-7002, Earned Value Management System (DEVIATION) (Sep 2015) (The version of the clause in DoD Class Deviation 2015-O0017 applies in lieu of the standard DFARS version of the clause. Applicable if Seller is listed in paragraph (k) of this clause in the prime contract. "Government" means "ϰſֱ and Government." Paragraphs (i) and (j) are deleted.) 252.234-7004, Cost and Software Data Reporting System--Basic (Nov 2014) (Applicable if this purchase orders/subcontracts in excess of $50,000,000. In paragraph (b), "Government" means ϰſֱ.) 252.235-7011, Final Scientific or Technical Report (Jan 2015) (Applicable for all purchase orders/subcontracts for research and development.) 252.243-7002, Requests for Equitable Adjustment (Dec 2012) (Applicable for all purchase orders/subcontracts over $150,000. Government means ϰſֱ) 252.245-7001, Tagging, Labeling, and Marking of Government-Furnished Property (Apr 2012) (Applicable for purchase orders/subcontracts where the items furnished by Seller will be subject to serialized tracking.) 252.245-7004, Reporting, Reutilization, and Disposal (Sep 2016) (Applicable to all purchase orders/ subcontracts containing the clause at 52.245-1, Government Property. "Contracting Officer" means ϰſֱ.) 252.246-7000, Material Inspection and Receiving Report (Mar 2008) (Applicable if direct shipments will be made to the Government.) 252.246-7001, Warranty of Data (Mar 2014) and Alternate I (Mar 2014) (Applicable if Seller will be delivering data. "Government" means "ϰſֱ or the Government." "Contracting Officer" means "ϰſֱ." The last sentence in paragraph (b) is changed to read as follows: The warranty period shall extend for three years after completion of delivery of the data to ϰſֱ, or if the data is delivered to the Government, either by ϰſֱ or Seller, the warranty period shall extend for three years after delivery to the Government." Alternate I applies if this is a fixed-price incentive purchase order/subcontract.) 252.246-7006, Warranty Tracking of Serialized Items (Mar 2016) (Applicable if DFARS 252.211-7003 applies.) Additional Clauses -- Special Contract Requirements from Prime SOW: Note: The following clause only applies to Labor Services suppliers. Enterprise-wide Contractor Manpower Reporting Application (eCMRA) The Subcontractor shall report ALL Subcontractor labor hours required for performance of services provided under this contract for the Missile Defense Agency via a secure data collection site. The Subcontractor is required to completely fill in all required data field using the following web address: http://www.ecmra.mil. Beginning January 1, 2013, reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 20. While inputs may be reported at any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2013. Subcontractor may direct questions to the help desk at  HYPERLINK "http://www.ecmra.mil" http://www.ecmra.mil. Contract Closeout The Contractor shall execute contract closeout activities at the end of the period of performance. The Contractor shall disposition all GFP in accordance with Management of Government Property. The Contractor shall consolidate and transfer all program data and documentation stored on the IDE to removable media storage devices that are protected by encryption and readable on Government systems, such as Digital Video Disc (DVD) or solid state disk drives and provide them to the Government at completion of this contract. Management of Government Property Per FAR Clause 52.245-1, Government Property (GP) is all property owned or leased by the Government. GP includes both GFP and CAP which includes material, equipment, special tooling, special test equipment, and real property. The Contractor shall identify, request, track, and report the status of GP with title belonging to the Government, and Rent-Free Non-Interference property needed for the Contractors design solution. The Contractor shall provide notice to the Procurement Contracting Officer 80 days prior to GFP need date. The Contractor shall use a government approved Property Management System to meet the requirements of FAR Clause 52.245-1 and DFARS Clause 252.245-7003. The Contractor shall obtain Government approval prior to modification or repair of GP. The Contractor shall update part numbers to reflect modifications applied. The Contractor shall maintain GP to Federal Condition Codes, and Supply Condition Code B4 of DoD 4000.25-2-M (CD#42). The Contractor shall track and manage GP in accordance with FAR 52.245-1. The Contractor shall identify GP as required by DFARS Clause 252.245-7001 and report the loss of any GP using the procedures listed in DFARS Clause 252.245-7002. The Contractor shall inspect GP upon receipt. The Contractor shall record discrepancies on shipping documents (e.g. DD Form 1149), or commercial bill of lading, and provide signed copies to the Government. DD Form 1150 shall be used to transfer accountability of GP between the Government and the Contractor. The Contractor shall coordinate with and obtain Government approval for disposition of GP prior to executing the procedure in DFARS Clause 252.245-7004. The list of available Government Furnished Property (GFP) for the Contractors use in the effort is identified in the contract per the applicable Appendix/Attachment/Enclosure. Security/Cybersecurity Requirements The following Security/Cybersecurity Requirements sections apply to all suppliers. 3.6.2 The Contractor shall provide a comprehensive Cybersecurity design that implements the applicable baseline Cybersecurity controls from: DoD Instruction 8500.01 Cybersecurity (CCD#1); DoD Instruction (DoDI) 8510.01 (CCD#5), Risk Management Framework (RMF); National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53 - Security and Privacy Controls for Federal Information Systems and Organizations (CCD#3); Committee for National Security Systems Instruction (CNSSI) 1253 - Security Categorization and Control Selection For National Security Systems (CCD#4) as defined in the System Security Plan and other Cybersecurity compliance documents. 3.6.2.3 The Contractor shall ensure that Cybersecurity risks are identified and managed as part of the overall risk management process. Contractor shall document all cyber incidents and compromises (Prime CDRL A044). 3.6.2.4 The Contractors Cybersecurity workforce shall maintain compliance with the Cybersecurity. Contractor qualifications to include training and certification requirements in DoD Directive (DoDD) 8570.01 (CCD#6) and DoD 8570.01-M (CCD#7) and meet the investigative level requirements established in DoD 5200.01-R (CCD#8). 3.6.2.7 The contractor shall provide any planned or implemented risk mitigations to counter risks in accordance with ISO/IEC 27036 - Information Security for Supplier Relationships (CCD#15). The Contractor shall flow down Supply Chain Risk Management (SCRM) provisions in all subcontracts for all suppliers at all tiers and report discrepancies to the MDA Supply Chain Risk Management/Trusted Systems and Networks Integration Council (MSTIC). The Contractor shall continuously monitor the supplier list for impacts of MDA SCRM Advisories, Technical Bulletins, Government Industry Data Exchange Program (GIDEP) Alerts, or any other similar information from other program. Components affected by these alerts shall not be used without additional analysis and approval by the MSTIC. Any component or supply chain vulnerability issue discovered by the Contractor in the course of development shall be reported to the MSTIC for review. Cybersecurity The Contractor shall comply with Cybersecurity (formerly known as Information Assurance (IA)) information protection requirements for all Assembly, Integration, and Test (AI&T) facilities, analysis tools and facilities, and the target system. When applicable, the Contractor shall comply with all Cybersecurity Compliance Documents listed below, in accordance with the Cybersecurity requirements as listed in the Security/Cybersecurity Requirements section above of this flow down document. CYBER COMPLIANCE DOCUMENTS CCD # Document # or Short Title Compliance Document Title Date 1 DoD Instruction 8500.01 Cybersecurity 14 March 2014 2 DoD 5220.22-M NISPOM National Industrial Security Program Operating Manual (NISPOM) 28 February 2006 3 SP 800-53 NIST Special Publication (SP) 800-53 - Security and Privacy Controls for Federal Information Systems and Organization April 2013 4 CNSSI 1253 Committee for National Security Systems Instruction (CNSSI) 1253 - Security Categorization and Control Selection For National Security Systems 27 March 2014 5 DoDI 8510.01 Risk Management Framework (RMF) 24 May 2016 6 DoDD 8570.01 DoDD 8570.01 Information Assurance Workforce Improvement Program 23 April 2007 7 DoD 8570.01-M Information Assurance Workforce Improvement Program, change 3 10 Nov 2015 8 DoD 5200.01 Manual DoD Information Security Program: Overview, Classification, and Declassification 24 February 20129 STIGS DISA Security Technical Implementation Guides (STIGS) Various 10 DoDI 8582.01, Enclosure 3 Security of Unclassified DoD Information on Non-DoD Information Systems 6 June 2012 11 NIST SP 800-171 Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations June 2015 12 IEEE/EIA-12207 Systems and Software Engineering - Software Life Cycle Processes 2008 13 ISO/IEC 15288 Systems and software engineering - System Life Cycle Processes 1 February 2008 14 ISO/IEC 27034 Information technology - Security Techniques - Application Security, w/ chs dtd 15 Jan 2014 15 Nov 2011 15 ISO/IEC 27036 Information Security for Supplier Relationships Parts 1-3 2013-2014 16 ISO/IEC TR 24772 Information technology - Programming Languages - Guidance to Avoiding Vulnerabilities in Programming Languages Through Language Selection and Use 1 March 2013       05/17/2018 Document No. SMD022, Rev. 3 Flowdowns for Prime Contract HQ0147-18-C-0007, MBRV / RVSM Configuration 2 (C2) Document No. SMD022, Rev. 3  PAGE 18 of 18   t u v 9fnpqyz˼ˠ˼vkcUJh(5CJ\aJhP;lh(5CJ\aJh6CJaJhh\fCJaJh%h\fCJ\aJh%h\f5CJ\aJh\fCJaJh31CJaJh\fh\fCJaJ hLc`h\f5B*CJaJphhLc`h\fB*CJaJphhLc`h\f5CJ\aJhLc`h(5CJ\aJhP;lhr5CJ\aJhP;lh6#CJaJ u v opq|}#gd(gd(gd31gd\fgd6#gd6#7$8$gd6#z{HI\oxyz|}vʵʖxm__Vhf{,CJ\aJhP;lhr5CJ\aJhf{,h6CJaJh]CJaJh(hyHCJaJh(h(CJaJh(CJaJh%Qh(CJ\aJhP0h(CJaJhP0h(5CJaJh(5CJaJhfh(5CJaJhP;lh(5CJ\aJh%h(5CJ\aJh(h(5CJ\aJJKB  1Xgd / gd5gd5gdrgd"2 gd(FGHIJK2O!!!C"D""ynfnfn^fnfnh*~CJaJhY{CJaJhY{hY{CJaJh*~h /CJaJhP;lh /B*CJaJphh%hY{B*CJaJphh%hY{5CJaJh 5CJaJh*~5CJaJhP;lh /5CJaJh9{h"2 B*phh"2 CJaJhh"2 CJaJh*5CJaJhh"2 5CJaJ$!!C"D"""""##<#=#####0$1$6%7%`gdY{h`hgdY{gd*gdY{gd /""""##<#=#####0$1$%%6%7%W&X&n'o'''I)J)K)L))))..v//;;;;;;<<<==w>ƷƬvh-_hY{CJaJhehY{CJaJhuhY{CJaJhY{5CJaJh-_hY{5CJaJh%hyHCJaJh%hY{B*CJaJphh%hY{CJaJh%hY{5CJaJhCJaJh*CJaJhY{hY{CJaJhY{CJaJ.7%W&X&n'o'''J)L)))****Y+Z+++,,A.B...h`hgd5h`hgdY{#gdY{ gdgd*gdY{.00A0B0`0a0113383937585666699;;<<==w>gd*h`hgdY{gdY{w>x>??,A-AAABBCC@DAD|D}DDDDDD EEJEKEyEzE`gdY{gdY{gd*gdY{w>>??,-AABB(89*CJaJh5>*B*CJaJphh?o5>*B*CJaJph#h?hY{5>*B*CJaJphh?hY{>*CJaJhY{>*CJaJhJ"hY{>*CJaJh-_hY{CJaJhY{CJaJ&zEEEEEE FFmFnFFFFFFGG:GKGGGGG?H@HIIKKgdY{`gdY{F1FLFNFOFjFkFnFFFKGLG_GqGsGtGGGGGGHHH H!H>H?H@HIIKK`KaKKKKKLLNNOO+PȿȿȰ}h%hvX5CJaJhvXCJaJh?oCJaJhJ"hY{CJaJhP0hY{5CJaJhP0hY{B*CJaJphhY{5CJaJhJ"hY{5CJaJh hY{0JCJaJjhY{CJUaJhY{hY{CJaJhY{CJaJ-K`KaKKKKKNNOOgPhPPPQQ?R@R SSCSDS/Y0YZgd?oh`hgdvXgdvXgdY{h`hgdY{+P1P5PfPgPhPPPQQ?R@R SSCSDSTT/Y0YZZZ[[[[U]V]H_I____c`d`dd e"eAeCeIe}eɾؾuh%QhFjxCJaJh{ 5CJaJh%QhFjx5CJaJhvXh?oCJaJh?oh?oCJaJhvXCJaJhvXhvXCJaJh%hvXCJaJh%hvXB*CJaJphh%hvXB*CJaJphh%hvX5CJaJhLc`hvX5CJaJ+ZZ[[U]V]I_J___c`d`dd!e"e}e~elhmhiillwmgdFjxgdY{h`hgdvXgdvXh`hgd5gd?o}e~elhmhiillvmwmxmmTpUpfqgqrr-rKrMrNrTrcrirrrrssttuuvvjwvwxwwww,}-}23ՃփúϩϚϒσh%QhFjxB*CJaJphh:CJaJh%QhFjxB*CJaJphh :CJaJhFjx5CJaJhR5CJaJh%QhFjx5CJaJh%QhFjxCJaJh*~CJaJhfhFjxCJaJhFjxhFjxCJaJhFjxCJaJ3wmxmmmmmTpUpfqgqrrrrssttuuvvww,}-} x`gdFjxgdFjxh^hgdFjxgd /Ճփ݈ވQRjktugdI !gdmgdFjxgd /փۈ܈݈ވɋʋPR(ǻwk`QwwHhI !>*CJaJh%hmB*CJaJphh%hmCJaJhShm5CJaJhmCJaJhmhmCJaJ%h& hmB*CJOJQJaJphhhmB*CJaJphh|PhmB*CJaJphhmB*CJaJph h"Jhm5B*CJaJphh|Phm5CJaJhm5CJaJhFjxCJaJhFjxhFjxCJaJ()jkȏɏ stu[]cdprFG ȹȮ墙ȹ}rdhP;lh2x5CJ\aJhP;lhfCJaJhYCJaJhFjxCJaJhmB*CJaJphhm5CJaJh(hm5CJaJh%hmCJaJh%hmB*CJaJphh%hm5CJaJhI !>*CJaJhEECJaJhmCJaJhmhmCJaJhI !CJaJ& FG STQRĦŦgd agdAfgdigdNI8#gd5gdygd4`pgd:ugdC9gd /gdmFGOPRßߟ \hkoøìui^V^Guh(ghy5>*CJ\aJh :CJaJh(ghyCJaJh(ghyCJ\aJh(ghy5CJ\aJ h(gh4`p;B*CJaJphh(ghCJ\aJhWJhn&CJ\aJh(gh4`pCJ\aJh(ghCJaJh(gh4`pCJaJh(gh5CJaJh(gh4`p5CJaJh(gh:u5CJaJh(gh:u5CJ\aJڡRSTYZ[\^npsvwz4Rz3BFõõõõõéõxoxaULh :CJ\aJh(gh aCJ\aJh(gh a5CJ\aJh"JCJ\aJh(ghAfCJ\aJh(ghAf5CJ\aJh(ghiCJaJh(ghiCJ\aJh(ghNI8CJ\aJh(ghi5CJ\aJh(ghNI85CJ\aJhn&hn&CJ\aJhGCJ\aJhghGCJ\aJhghG5CJ\aJFŦ}~ŧƧӧ'*wڨ -ڹ~p~aUIh(gh} <5CJaJh(ghN85CJaJh(ghN85>*CJ\aJh(ghK5CJ\aJh(gh1q5CJ\aJh(ghN85CJ\aJh(gh1qCJ\aJh :CJaJh(gh1qCJaJh(gh1q5CJaJh :CJ\aJh(gh a5CJaJh(gh aCJaJh(gh a5CJ\aJh(gh aCJ\aJ)*٨ڨήϮgd[ugdgdq}: d+gdHgdHgdC9gdN8gd1qgd a]gd a-56Z[n;[_op~۷ۜxoxdVdxoxVdxoxdxh(ghH5CJ\aJh(ghHCJaJh}'CJ\aJh(ghHCJ\aJh(ghH5CJaJh(gh,ZRCJ\aJh(ghCJ\aJh(gh} <B*CJaJphh(ghoCJ\aJh(gh*CJ\aJh6CJ\aJhy CJ\aJhlCJ\aJh(gh~CJ\aJJ]jk:;!EWZfg|#(̶wiwiwiw]h_Yh_YCJ\aJh_Yh'T5CJ\aJh_Yh'TCJ\aJh'Thheh'T5CJ\aJhxhh'TCJ\aJh'TCJ\aJh_Yh'T5CJaJh_Yh'TCJaJh_Yhe"OCJaJh_Yh4NCJaJh_Yhy CJaJh_Yh6CJaJ#h_Yhy 5B*CJ\aJph!;fg -.=>#gd'T #'dQgd'Tgdxh.EJ<ACؼzozdVh_Yh5 5CJ\aJh_Yh5 CJaJh_Yh cCJaJh_Yh]CJaJh_YhbCJaJh_Yhe"OCJaJh_Yh4NCJaJh_Yh6CJaJh_Yhy CJaJh_Yhy 5CJ\aJh_Yh'T5CJ\aJh_Yh'TCJ\aJh_Yh_YCJ\aJh_Yh_Y5>*CJ\aJ.4 #$Ifgdxhgdxh 'dQgd e#gdxh -.357prnp]_![^=@ #z}34578:;=>@ACDhU&h=dj h;h=dOJQJUhbpjhbpUhcWh5 CJ\aJh_Yh5 CJaJh_Yh5CJaJh_Yhy 5CJ\aJh_Yh5 5CJ\aJh_Yh55CJ\aJ8458Q`o^UUUU #$Ifgdxhkd$$Ifl\(X' (0'44 layt5ops^UUUU #$Ifgdxhkd$$Ifl\(X' (0'44 layt5am^UUUU #$IfgdxhkdH$$Ifl\(X' (0'44 layt5mnq} ^UUUU #$Ifgdxhkd$$Ifl\(X' (0'44 layt5 .O\^UUUU #$Ifgdxhkd$$Ifl\(X' (0'44 layt5\]`n^UUUU #$Ifgdxhkd4$$Ifl\(X' (0'44 layt5^UUUU #$Ifgdxhkd$$Ifl\(X' (0'44 layt5"6^UUUU #$Ifgdxhkd|$$Ifl\(X' (0'44 layt5^UUUU #$Ifgdxhkd $$Ifl\(X' (0'44 layt5MZ^UUUU #$Ifgdxhkd$$Ifl\(X' (0'44 layt5Z[_p^UUUU #$Ifgdxhkdh$$Ifl\(X' (0'44 layt56<^UUUU #$Ifgdxhkd $$Ifl\(X' (0'44 layt5<=AP^UUUU #$Ifgdxhkd$$Ifl\(X' (0'44 layt5^UUUU #$IfgdxhkdT$$Ifl\(X' (0'44 layt5 $3ny^UUUU #$Ifgdxhkd$$Ifl\(X' (0'44 layt5yz~$2^UUUUU #$Ifgdxhkd $$Ifl\(X' (0'44 layt5234679:<=?@^YWWWWWWWWgdxhkd@ $$Ifl\(X' (0'44 layt5 DEFHMO`bijklzǿ컱쐄hcWh5 CJ\aJhbp h#0J hYm0Jh30JmHnHu h=d0Jjh=d0JUh\fh\fh\f5 hx5 h"2 5hmBh=d5h]h=d5h hmBh=dh=dheh'ThU&hxh"@NOklgdxh$ !`''dQa$gdn&  !`'gd6$a$$ !`''dQa$gdn& $ !`'a$gdO$ !`''dQa$gdn& 21h:ph</ =!8"8#$% $$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5$$If!vh#v#v #v#v(:V l0'55 55(ayt5G Dd GVH  c $A?blSfpŤ( -nlSfpŤPNG  IHDRNk^gAMAPLTEƜkkkcccΔ{ssbjYYbQƵέscƜΤrjֽƽs{skskckcYbY֔΄ֽcscYjYzzQbQBRBrr{{{{rzέ֥s{{JRRΜƓbkƋrBsƃAYbsR{Jsb9c{1Zs9Zsz{kBc9Z{!Jsr9Rs8j1Js)Z0jJZ!9s0rRc!Z b{jrbj(0Y9B{!ZJR19s jZbRRZYYbJJRQQbޔ{{))s!!sjrZbjzrkcQIJBIA800(( zbjr֔Ό΃zZ0 )zjscYI8 (rƽjYYAJ1A(8 R9rjRjIZ9Z9I(rQ{RY8{RrIc9zΔrƌkbεzޜrεﵔ޽ZYQbޜjsk{RJZέz޽ֵέ凜sƭ΃jrYzƥrｵƽsksbYbRJRֵ֋rZJZj{c{zj֭޽{csﵥߩIDATx\p}=Yo\coۢ&)V$ҴR䏛Jg\ 'iAkg:o/-NLx&P;T= *1$ H}۽ɒl?to߾}}}])B'ӗZhBş)C8fb%֑k`8<F?4cGa-;|KE+4+2Y%0SX$&|%ْ*ґ~2"DH6ݒT7 FMǟW|7k@ .tW$$e+MCTN$JDDaT"阑/oOpڔmk{| raB*H"S|]1S@^/ר@2!dT ՖШ ^}cH 30C5Nh7e.;%UŠ>:?`Y p@I&*0dC*i(A5#l(ؠR8e74&b!JpXAG S1梄fI8! wa\9Y4)ZVx0bd.,CVa֬fg1/r1`uf!')/= p*?$V'$a.4=7r.Z\jͨ_qÈ]1=ЪEC*X5m&*IKfPqOΑdqf-܋C' "̳ qwDʋhn8Gf^LZI>P&AuO*C՞5m+9R!*vhǑ޲$T2%+1]cމ/ ˉOE7BE9q-4[°ܛ`nKDŽH.]]5D#rXu !*;# jsm펼8ܔPԢ^\Ҹ7k Jz@?CepdD \32HTi#o}$ݐ+s9nihi>y51v7!PX֮74vg vsFy;Ucjrh7\as5<|#\G䩤]\*ZUVvXCoVasp\?F"Rn*,fl\f Izd*_5+#A#?'3, -ߵ\0p%"4TOCɚn_`] r=i8b z 3]_W6gYVF$#"O SQqTC;Cnqy`L|ĸKNӨ2MElFRz[,R!.vrµ׌Opo1C![{S Ɋl'hpA3niG_aa ۩xzWӌZIimRwh |9"}a=ZϼvtvvttttwtwAG&ݎG=[3;ӝl6tꞞ[};6膪L&7h7d2# 8QvUK{?f5 :<*rm Z@,Aܢ&bOիmDczŗsP|≧~xχv,S*BdeVV6[mvvQf;vdwW6׷Kvها/'V}S(XX߶}۶m߃-[m-۾[2 Gq ozX{zT LzZ*Л-Ǡαcoӯʛ/KGy<#CCCb bw;-§XpOE^]"JVs_94n6z5v=i6"ю"U3}wJc[iyI%*aܻ(3Rzˇ>{/˯ڋO>g8/>o=KPȨ GHSkPP;Vc0JD0kذ$Ab*;enLXkHl40Ԫ&T0jL[ S 2>>62{cE^yW_y ʑgZJ⌙~T]F,lKlxi[J/_z٘ Dz1cGшC x}aʳZ'cm:9ij {$[ׅR0w9!̻@/sԶey s8NtTB2C d.]_=otث%1ZV7b 9l<b6t];H rA>Q`M$H$T&tz0ЀK fk#y.*3J *ϕ'(ixBn h^ $UI((/C IcܒAhiE[oZ @4&}"5`C3hSOw&8*D` cY*F&PV:jIyDPwØ\ c<aWG_1/70][u"vcΓM$o ^{l6(Ղs J\usj;PE*sNpEpe;<` ֿ'#[IxL-?#q3$ҺpP]Ȅ'A }ob%a'.ɹ^~EݕgN QZ&FV%/  sD^EBݸp{F#<+e O(s}fP` Mq".}qq -H Yл q'~+Ri _tR} C .QSUσ%3@l#6h8H7-MKf<}+_ י`ͥz'KZņoJsZ= ʡ ˲Z7snvR)@Py9 5'<Mx%ZXAѓ*6!1˅"ʷ^Ӵ>`i_eڷ.0-O>wP&UN>\S n8$ !(m@NMw 5/I7`L'&^@]Iu2EqS1"]s~3XA)J|=ݴep{}LfCKM[ɚP ~e>hD^'}=Etoz_P@"k#m57 @IC֯;87R66Έf i.z_U疯ҹInGk|i hiǾ_0Mh wbJWMNYƵ"4loΙpO(> aˡ5tm R?xj̋.|CıPŶj "JpwG{ytAr [)Y(wLe11\h@?F]ꚶ$qU/C5Y(c7 w?0,BslӥkFSzk];JPBɵ]7ilkSxf T/`:5k*{; ]if|{0hV&m 9K%"ajVd&\y%l`A2=6VYE8`3jc=X+E8AD*M0tMO5S #3' LW٧Ϝ9sG~cz4^=y";.L(# ;^ ;M*n9ޘC4*K2}L@dt|-;z!AC$Cꘘ̾('dp]Hnc YSٌ 0Q;p2+r7 0xCvRnr6Ϳw&1L8x-W}vr*alEf栯ITiGu;6*?&!ξO?;{~ǫGǕBT'|n>KlcU_x|/F$sel_q_pᢢ05uBY8DpaJG_dWǒ!V+)r 䣩3=I!E1 ig^k3'2A} 7aQB?I2wQla!]B(H -RUxN$(!P+1ACB9avgw|۹ݻ$ٛyo}̛o4B֚\z=ΩQ -EΈ (`kAdʈG_{Q.5g+aKR= uIph4INsnlh)­`Z9h[ *}Y  BtnҔd(L->lm+na ~}h{^) 0Aeq>fy73TXGI0ihL6J#bz/  QLNu#+$ 6ɘ79}ɛߕϏ67[.JltJ2_I2BfL 7U]_y׉`D =! {&V =^bEhݞy© Z#G8r^ʌJ*x]Vm8QD(pjk]_!1Q)sN}d'}ơa0{w+-S>!kKl tЊQL Kcq:;{)Q@ "y6n_RiX32zACZٹv*' ڦWe!qB+/q"͕BP/Q y5L(Wy(I% 0ԞYIҳ8/)MiN !/U!L91*nq).nE;01M4*^h~ӉjՊ(!-|ۖX~$I+-M|i_)%Cb@όZ#5~Upu "N}=<;$tDwrt]dpW酸ț;ܛ (+p+l@>  Heading 1$@& 5>*\@@  Heading 2$$@&a$5\::  Heading 3$@&5\NN co6 Heading 5 <@&56CJ\]aJDA`D Default Paragraph FontVi@V  Table Normal :V 44 la (k (No List 4@4 Header  !4 @4 %0Footer  !4B4 Body Text5\*W !* Strong5\NQ2N co6 Paragraph 5 56CJ\]aJHCBH 7OBody Text Indenthx^h<PR<  Body Text 2 dxR^bR Y Normal (Web)dd[$\$CJOJQJaJ.)@q. { Page NumberXX N{DFARS h*xS @@@@@@d@KHOJQJaJHH N{ Balloon TextCJOJQJ^JaJB' B {sComment ReferenceCJaJ<< {s Comment TextCJaJ:: {sComment Text Char6/6 Z Header CharCJaJ6U`6 % Hyperlink >*B*ph>>  J% Footnote TextCJaJ<< J%Footnote Text Char@& @ J%Footnote ReferenceH*FV !F 1FollowedHyperlink >*B*phVo2V oDefault #7$8$H$!B*CJ_HaJmH phsH tH FBF f{,A-1$$0^`0a$ B*aJph6/Q6 f{,0 Footer CharCJaJ@j@ '4NComment Subject&5\F/qF &4NComment Subject Char5\PK![Content_Types].xmlN0EH-J@%ǎǢ|ș$زULTB l,3;rØJB+$G]7O٭VGRU1a$N% ʣꂣKЛjVkUDRKQj/dR*SxMPsʧJ5$4vq^WCʽ D{>̳`3REB=꽻Ut Qy@֐\.X7<:+& 0h @>nƭBVqu ѡ{5kP?O&Cנ Aw0kPo۵(h[5($=CVs]mY2zw`nKDC]j%KXK 'P@$I=Y%C%gx'$!V(ekڤք'Qt!x7xbJ7 o߼W_y|nʒ;Fido/_1z/L?>o_;9:33`=—S,FĔ觑@)R8elmEv|!ո/,Ә%qh|'1:`ij.̳u'k CZ^WcK0'E8S߱sˮdΙ`K}A"NșM1I/AeހQתGF@A~eh-QR9C 5 ~d"9 0exp<^!͸~J7䒜t L䈝c\)Ic8E&]Sf~@Aw?'r3Ȱ&2@7k}̬naWJ}N1XGVh`L%Z`=`VKb*X=z%"sI<&n| .qc:?7/N<Z*`]u-]e|aѸ¾|mH{m3CԚ .ÕnAr)[;-ݑ$$`:Ʊ>NVl%kv:Ns _OuCX=mO4m's߸d|0n;pt2e}:zOrgI( 'B='8\L`"Ǚ 4F+8JI$rՑVLvVxNN";fVYx-,JfV<+k>hP!aLfh:HHX WQXt,:JU{,Z BpB)sֻڙӇiE4(=U\.O. +x"aMB[F7x"ytѫиK-zz>F>75eo5C9Z%c7ܼ%6M2ˊ 9B" N "1(IzZ~>Yr]H+9pd\4n(Kg\V$=]B,lוDA=eX)Ly5ot e㈮bW3gp : j$/g*QjZTa!e9#i5*j5ö fE`514g{7vnO(^ ,j~V9;kvv"adV݊oTAn7jah+y^@ARhW.GMuO "/e5[s󿬅`Z'WfPt~f}kA'0z|>ܙ|Uw{@՘tAm'`4T֠2j ۣhvWwA9 ZNU+Awvhv36V`^PK! ѐ'theme/theme/_rels/themeManager.xml.relsM 0wooӺ&݈Э5 6?$Q ,.aic21h:qm@RN;d`o7gK(M&$R(.1r'JЊT8V"AȻHu}|$b{P8g/]QAsم(#L[PK-![Content_Types].xmlPK-!֧6 0_rels/.relsPK-!kytheme/theme/themeManager.xmlPK-!g theme/theme/theme1.xmlPK-! ѐ' theme/theme/_rels/themeManager.xml.relsPK] T z"w>+փ(-4ڶ67%.>Zɳ;4<y2@prtvwxz|~=<=H=>N>j>K?s??3VkXXXX!  p0e0e     5% 8c8c     ?1 d0u0@Ty2 NP'p<'pA)BCD|E||"60e @    ?  4444-@ABC DEFGHIJK5%LMNOPQRSTUWYZ[ \]^_ `abN 5%  N 5%  N    5%    !"?N@ABC DEFGHIJK5%LMNOPQRSTUWYZ[ \]^_ `ab?@A BCDEF GHZZȈ@H 0(  0(  B S  ?4679:<=?@4679:<=?@ <@<<J=z==>k>n>HHII@JiJK!KӴ]^a} 6Mp6P 3n$34679:<=?@CDEFHO\ijl  o p U U V V W W v J!K!&&v''>k>SSKjKjMjNjvoxo)iiɇ ߗSTRRAAaayy3446779:<=?@BBCKL|GT z ^ `zo(()KL|22u8n9 *3W(g} :O[jK~|(G[&J Jnou4.A,j l"D34M[% 'B G R ] x N ! "2 = Ny { # r    / T n y   " _$ b6 k< t gfP[NmO=?RTir c]RuIr VE_fG{K3OT?y!1W#Y'/N=<N<Z<d<\ =:"=7=+A=O=\=]=>6>04?B?I?l?r?u?@[M@g@ol@8FA0RACUALqA3B9BE"Cf/CD D8DFDEE^EidEFdFr8FRF/aFeFxFO~Fe~F!G3GH8G49GEKGmGyG*{G( Hq@H7MHI/IzLIdJ:JJ"J-JrMJOdJ-lJuJKKN)KfKiK|KILa MM&MHM4N;N9ZNZbN[OO<Oe"O,OP-P(PFPBPP^WPu[P\pP Q[2QcQyQ {Qo8RqIR,ZRn]RRS*)SES{RSTSTT'T+T>TCTUTtT~U%U,ULUVmU rUuUkVuVWcWcW mW~WXCXV'X?KX3MXYX^XeX_Y*Yr/YpYoZS#Z$Z%Z+4Z4Zm6Z[1[4[k[/\?\P\e\{\]]] ]]~]xY]z]#^$^o^%_0_Q_w_1`Lr`caaa SaS]adva*b18b{:byb cc*Mcec~c$d4,dqd ehe)eEeMe f7f'f0fdf# gW.gBgYg:hFh?VhDZhYii\ioiui+jEjZj[jljsjl`lP;lnlS~lYmlmD:nHnRnw_n,o.o9o?oBoopMp4`pbpbp<&q,q1qM9q$UqUqgq sqq*r.rkr prN>sWs{sqt.tW3tPtgtu:u:uSu9WuJhu!vG)v6vPvXv(w()w*wSw2`wxw?xx x1x`xFjxyyy1yOyYyeyz+z z{X{Y{|h|T}X}Z ~*~C~iw57mU^i%-FFFcLG\9fj /[]oI[`a'^1EXSV\$9Ms8%DDSHs<fr5G8gJuYrw 'ESfw $UvX@k[!+I7Ohi2_:Y* MVZqz07=cqux S0Riy) b"#-p/sf>"'?8<Gxh7G)Sr/fw5]=PS6klm )p@SMwm <"z/QQ8hpRhlZac=%''$I aYJ`uf[hvy8:9xEp< k!8Kl{s7WCff~N83Dae$)4j%uq  _+.hNi9/gyJV\aln[$To} J7[Z]eh(|Whg%%189=g&~ 0=0MWe_ ACFJ} mB"W. /Oi!Af|n7rQU.R]% 8#FZaj'w':>NEL *6/4z~-+Mw#>E!3X\Hbo2x(Nv|#y'$VMw QAWb]ltvAq5 6yFKUmnGlOOtS|U3+YZ+_cVAPoU[Eh]')WcY^ g3!k,5GFH[q,QAo[u&|o !)-.<Ykn&5qlh<x@Edf{ Y-:g'y!H]l^ ]#%-3I'(+8iDs+`&iw,El % ^4O\(}-=d] ` 0>2P[Vz\ffJ U&[./!^~~dG!+y./82NenvrN{L;HV|p}'';se:2c<5JhMp]d:?be +1:"'*337E_Gl*nMrPQ/ET`l2t5A"T2FRa/fbIQ]7DVAf{"J"^!m,Nm{#|G|P@W{p~6 ?"cA _ga-]:yHFY[\|C7=?wb Fox&[(KMbmCt{ P'J,I\ 568Z_Ob~-*<UpKM[ -N18WY9*;4k46@@Unknown G*Cx Times New Roman5Symbol3.*Cx ArialCNComic Sans MSG. .Cx HelveticaArial7. [ @VerdanaMCentury Schoolbook5..[`)TahomaC.,*{ @Calibri Light7.*@CalibriA$BCambria Math"hegeg[Ɇ fεOfεO8xr43qHX ?T2! xx"U +Flowdowns for MKV Contract W9113M-04-D-0001Michael B WallaceLeigh Anne Swanson Oh+'0 0< \ h t ,Flowdowns for MKV Contract W9113M-04-D-0001Michael B Wallace Normal.dotmLeigh Anne Swanson3Microsoft Office Word@d@>4<@𺡽fε ՜.+,D՜.+,t0 px  ϰſֱO ,Flowdowns for MKV Contract W9113M-04-D-0001 TitleD     !-5 _PID_HLINKSSensitivityIDLM SIP Document SensitivityDocument AuthorDocument Sensitivity ThirdPartyOCI Restriction OCI Additional Info Allow Header Overwrite Allow Footer Overwrite Multiple Selected SIPLongWordingcheckedProgramsCount ExpCountryAC http://www.ecmra.mil/\gmailto:dosscosvar@mda.mil\|#mailto:mdaaccesscontrolhsv@mda.milJmmailto:ACC@MDA.mil0ACCT01\swansonl1  -1  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~Root Entry F@Data ++1Table/IWordDocument 4TSummaryInformation(DocumentSummaryInformation8MsoDataStore`M켽`M켽H1VJ4HJDU==2`M켽`M켽Item  PropertiesUCompObj r   F Microsoft Word 97-2003 Document MSWordDocWord.Document.89q