<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ff/ODM/odm_ff_chm" xml:lang="it">
   <Header>
      <Title> Gestione modifiche</Title>
      <Keyword type="header" order="d1e365793">
         <Level1>Functions and features</Level1>
         <Level2>Gestione modifiche</Level2>
      </Keyword>
      <Keyword type="header" order="d1e365799">
         <Level1>Gestione modifiche</Level1>
         <Level2>functions and features</Level2>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>
         <GUIRef href="/baanerp/dm/chm" role="module">Gestione modifiche</GUIRef> deals with the
		fundamental concept of change. This module controls the processes of product
		changes. Change, particularly in industry, is a constant and critical factor.
		Effectively, in the real time scenario, the frequent upgrade and customization
		of products--due to quality improvements, cost reductions, manufacturing
		innovations, and customer satisfaction issues--requires an accurate and
		foolproof method to manage the change implementation process.</Paragraph>
   </AimSection>
   <GeneralSection>
      <List>
         <ListItemHead>
            <Link href="/baanerp/dm/onlinemanual/000012" role="manual">Richiesta di modifica</Link>
         </ListItemHead>
         <ListItem>
            <Paragraph>The <Link href="/baanerp/dm/glossary/glossary#000004" role="glossary">change request</Link> is the preliminary step in a change process. You can initiate
			 change from various sources (internal or external to the organization) in the
			 form of change request. These requests are processed by eliminating trivial
			 requests, or by combining similar requests. An authorised user can create a
			 change request.</Paragraph>
         </ListItem>
         <ListItemHead>
            <Link href="/baanerp/dm/onlinemanual/000013" role="manual">Modifica</Link>
         </ListItemHead>
         <ListItem>
            <Paragraph>The change refers to
			 the change header. All related change requests are linked to one change. If you
			 create a new change, the first version of change proposal is created
			 automatically. You can also create a change without a change
			 request.</Paragraph>
         </ListItem>
         <ListItemHead>
            <Link href="/baanerp/dm/onlinemanual/000014" role="manual">Proposta di modifica</Link>
         </ListItemHead>
         <ListItem>
            <Paragraph>The <Link href="/baanerp/dm/glossary/glossary#000005" role="glossary">change proposal</Link> is a version-controlled entity of a change. A new change
			 proposal is created by default when a change is created. The proposal can be
			 approved or rejected. When the proposal is approved, the status of change
			 changes to Approved. If the proposal is rejected, the status remains the same (
			 Created). If the proposal is rejected, you can create a new proposal with all
			 the linked entities.</Paragraph>
         </ListItem>
         <ListItemHead>
            <Link href="/baanerp/dm/onlinemanual/000015" role="manual">Ordine di modifica</Link>
         </ListItemHead>
         <ListItem>
            <Paragraph>A version of the change proposal has a list of proposed
			 effectivity dates, which are recorded as <Link href="/baanerp/dm/glossary/glossary#000006" role="glossary">change orders</Link>. A change order can exist independently of a change proposal.
			 Change orders are linked to the change proposal. A change order can be selected
			 for effectivity dates. To control the effective and expire dates of more than
			 one change order, you can define a parent child dependency between two change
			 orders. The hierarchical dependency between two change orders, creates a bill
			 of change orders (BOCO). A BOCO has two levels of hierarchy. You can link the
			 change orders in BOCO to the change proposal.</Paragraph>
         </ListItem>
         <ListItemHead>Change committee</ListItemHead>
         <ListItem>
            <Paragraph>The committee of a chairperson and reviewers who implement a
			 change using change management. Only authorized users can create a change
			 committee. the reviewers of the change committee submit the change proposal for
			 review. The reviewers provide their recommendations and the final decision lies
			 with the chairperson of the committee.</Paragraph>
         </ListItem>
      </List>
   </GeneralSection>
</ManualTopic>