CHANGE TYPE definition
CHANGE TYPE means type of service/feature change processed by the Contractor per the Customer’s Service Request. This is either a move, add, change, or delete.
CHANGE TYPE is the method used when submitting an RFC to indicate the type and nature of a change request.
CHANGE TYPE. CHECK APPLICABLE: SUBMITTED BY: ▇▇▇▇▇▇ ▇▇▇▇▇ CURRENT MANUFACTURING SITE: TOOL MOVE: PROCESS CHANGE: MATERIAL/MATERIAL SUPPLIER CHANGE: CAPACITY TOOL: FUTURE MANUFACTURING SITE: TE-Greensboro, NC (▇▇▇▇ ▇▇) SUPPLIER: TE Connectivity J6DRY DATE SUBMITTED: 4/12/2021 MADE TO DRAWING DATED: 12/17/2019 APPROVED: REJECTED: PRODUCT ENGINEERING SIGNATURE*: DATE: Apr 13, 2021 IDENTIFY WITH REMARKS AFFECTING PRODUCT ENGINEERING CRITICAL REQUIREMENTS *By signing this document, you state that you have verified the physical part/s with the drawing/s and agree with key dimensional data, notes and appearance.
More Definitions of CHANGE TYPE
CHANGE TYPE. Type of change. For example: integration change, request for additional functionality, change in SOW estimate based on design sessions, etc. (usually more applicable to Phase One (1) or Phase Two (2) projects.) Select one (1): Term Extension (zero (0) budget add) Term Extension (additional hours added) Change in Scope (additional hours added) Change in Scope (no addition hours added) Other (detail in request description) Impact Assessed by: List those assessing the impact. Normally the CSLLC EM, Functional or Integrations Consultant, and possibly someone on the Client side. Priority: High, Medium, or Low based on need for the change. Billing: Select one (1): ▇▇▇▇ under current project Bill separately under current project Bill separately under new project Contract Line Type: Describe the billing basis. For example: Time & Materials, Fixed Fee Installment/Milestone, Prepaid, Subscription. For “Bill under current project,” the billing basis of this Change Order MUST match the applicable SOW’s billing basis. Is new PO# required? Select one (1): New PO# (insert PO#) PO# to be created after receiving countersigned documents No new PO# needed <<Describe the change and why it is needed. It is important to describe why this was not estimated correctly in the SOW or where the change occurred. For example: If this CO is for an extension, please include the number of hours and budget remaining on current project. <<Describe the purpose/reason for change and be sure to explain the impact to NOT doing the change. For example: