<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tp/onlinemanual/000063" xml:lang="en">
   <Header>
      <Title>To use elements</Title>
      <Keyword type="header" order="d1e2598387">
         <Level1>Project</Level1>
         <Level2>elements</Level2>
      </Keyword>
      <Keyword type="header" order="d1e2598392">
         <Level1>Project elements</Level1>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>You can use elements and/or <Link href="/baanerp/tp/glossary/glossary#000005" role="glossary">activities</Link> in your project,
		depending on the type of project budget and control you want to use.</Paragraph>
      <List>
         <ListIntro>Elements versus activities</ListIntro>
         <ListItem>Elements are static whereas activities are dynamic in the sense
		  that they can be used in a plan. Elements cannot be scheduled.</ListItem>
         <ListItem>Elements can be used as a framework whereas if the control is
		  on an Activity Budget (see the <GUIRef href="/baanerp/tp/pdm/tppdm6100m000" role="session">Projects (tppdm6100m000)</GUIRef> session) the linked
		  activities are used to monitor the project.</ListItem>
      </List>
      <List>
         <ListIntro>An element structure has three benefits:</ListIntro>
         <ListItem>You can define quantities on the relations between elements.
		  For example, the project is a house which needs four doors. The elements House
		  and Door have a relationship with the quantity four. This means that each
		  activity on the budget line is mentioned four times.</ListItem>
         <ListItem>You can define an element with multiple parents. This saves
		  time when you must budget repetitive work (scope). For example, the project is
		  a street with four houses. All these houses need doors, so the house element is
		  present multiple times and the door has a frequency factor of four. This method
		  saves budget lines. Each activity is only mentioned once as a budget line with
		  the same frequency.</ListItem>
         <ListItem>An element structure can have multiple tops. This is especially
		  useful for an estimating structure. This way flexibility is supported.</ListItem>
      </List>
      <Paragraph>In an element budget, elements (see the <Link href="/baanerp/tp/onlinemanual/000307" role="manual">To create a project</Link> topic) are used for the
		main structure with which you build your budget. In the element structure, you
		can link the <Link href="/baanerp/tp/glossary/glossary#000003" role="glossary">cost objects</Link> that are
		necessary for your project budget to the element budget lines. In other words,
		you can break down a project into elements. Additionally, when you use an
		activity budget in project control, you can define one or more activities to an
		element. If you only use one activity per element, you can define this relation
		on element relations. If you want to use more than one relation, you must
		define the activity on the element budget line.</Paragraph>
      <Paragraph>To enter elements in the project First create the <Link href="/baanerp/tp/glossary/glossary#000083" role="glossary">top element</Link>, which is the
		top of the tree structure. All the other elements in a project structure must
		be linked to this top either directly or indirectly and are called child.
		Use the <GUIRef href="/baanerp/tp/ptc/tpptc1100s000" role="session">Element (tpptc1100s000)</GUIRef> session to create an element and to specify parameters
		relating to a <Link href="/baanerp/tp/glossary/glossary#000100" role="glossary">budget line</Link> quantity,
		progress recording, <Link href="/baanerp/tp/glossary/glossary#000092" role="glossary">cost control</Link> and, if
		applicable, <Link href="/baanerp/tp/glossary/glossary#000092" role="glossary">extensions</Link>, settlements, and
		invoice amounts.</Paragraph>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/tp/onlinemanual/000064" role="manual">To use an element structure</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>