Sophie

Sophie

distrib > Fedora > 15 > i386 > by-pkgid > 54cac1c2268db633d66eeff1b4faa585 > files > 31

frepple-doc-0.8.1-3.fc15.noarch.rpm

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
  <meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
  <title>Frepple / Modeling </title>
  <link rel='stylesheet' href='../styles.css' type='text/css' />
  <!--PageHeaderFmt-->  
</head>
<body>
<div id="container">

<div id="menubar">
  
<div id="logo" align="center">
<br/><img src='../frepple.bmp' alt="frepple" /><br/>
<a href='http://www.frepple.com/'>
<strong>a Free<br/>Production Planning<br/>Library</strong>
</a></div>
<div id="menu">
<br/>
<h3><a href='../Main/HomePage.html'>Main</a></h3>
<h3><a href='../UI/Main.html'>User Manual</a></h3>
<h3><a href='../Tutorial/Main.html'>Tutorial</a></h3>
<h3><a href='Main.html'>Reference Manual</a></h3>
<h3><a href='../Main/FAQ.html'>FAQ</a></h3>
<h3><a href='../reference/index.html'>C++ API</a></h3>
<br/><div>
</div>  
</div>
</div>

<div id="content">
<br/>
<!--PageText-->
<div id='wikitext'>
<p><a class='wikilink' href='../Main/HomePage.html'>Main</a> &gt; <span class='wikitrail'><a class='wikilink' href='Main.html'>Reference Manual</a> > <a class='selflink' href='Modeling.html'>Modeling</a></span>
</p>
<p class='vspace'>This chapter describe the frePPLe data entities, their fields and relationships.
</p>
<p class='vspace'>A couple of initial remarks:
</p>
<div class='vspace'></div><ul><li>FrePPLe limits itself to the data fields that are relevant for planning.<br />  An ERP or similar system is more transaction-oriented and will contain plenty of more detailed information.
<div class='vspace'></div></li><li>The frePPLe data model is designed to be pretty "atomic" in order to be as generic as possible. Quite often an entity in a source system will map into a collection or sequence of frePPLe entities.<br />  For instance, frePPLe doesn't have a model to represent a bill-of-material. Instead the material relations from the BOM are represented as flows on the manufacturing operations.
<div class='vspace'></div></li><li>The native data format is XML.<br />  FrePPLe doesn't support namespaces in the XML-data: 
<ul><li>The XML-data should not be placed in any namespace.
</li><li>FrePPLe XML schema to validate the input data. See the files frepple.xsd and frepple_core.xsd for the definition of the supported constructs.
</li><li>To support subclassing the namespace xsi must be defined as "<code class='escaped'>http://www.w3.org/2001/XMLSchema-instance</code>".
</li></ul>Considering the above, frePPLe XML files typically start with the following lines:
</li></ul><pre>      &lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
      &lt;plan xmlns:xsi=&quot;<code class='escaped'>http://www.w3.org/2001/XMLSchema-instance</code>&quot;&gt;
      ...
      &lt;/plan&gt;
</pre><div class='vspace'></div><ul><li>FrePPLe has a very rich Python API.<br />  Detailed programming and scripting of the frePPLe application is possible in this way. For complex integration tasks and for customization of the algorithms using Python is the recommended way of working.
<div class='vspace'></div></li><li>FrePPLe translates input data to the native encoding on your system (as set by the LC_ALL environment variable on Linux, or the code page on Windows).<br />  The string manipulations inside frePPLe are compatible with the UTF-8 Unicode encoding, but NOT with the UTF-16 or UTF-32 encoding.
</li></ul><p class='vspace'>Before diving into the details, have a look at the domain model diagram. It shows clear and simple the main entities and their relationships.
</p>
<div class='vspace'></div><ol><li><a class='wikilink' href='ModelingDomainmodel.html'>Domain model</a>
</li><li><a class='wikilink' href='ModelingEnvVariables.html'>Environment variables</a>
</li><li><a class='wikilink' href='Python.html'>Python Interpreter</a>
</li><li><a class='wikilink' href='ModelingGlobal.html'>Global parameters</a>
</li><li><a class='wikilink' href='ModelingBuffer.html'>Buffer</a>
</li><li><a class='wikilink' href='ModelingCalendar.html'>Calendar</a>
</li><li><a class='wikilink' href='ModelingCustomer.html'>Customer</a>
</li><li><a class='wikilink' href='ModelingDemand.html'>Demand</a>
</li><li><a class='wikilink' href='ModelingFlow.html'>Flow</a>
</li><li><a class='wikilink' href='ModelingItem.html'>Item</a>
</li><li><a class='wikilink' href='ModelingLoad.html'>Load</a>
</li><li><a class='wikilink' href='ModelingLocation.html'>Location</a>
</li><li><a class='wikilink' href='ModelingOperation.html'>Operation</a>
</li><li><a class='wikilink' href='ModelingOperationPlan.html'>OperationPlan</a>
</li><li><a class='wikilink' href='ModelingProblem.html'>Problem</a>
</li><li><a class='wikilink' href='ModelingResource.html'>Resource</a>
</li><li><a class='wikilink' href='ModelingSetupmatrix.html'>SetupMatrix</a>
</li><li><a class='wikilink' href='ModelingSolver.html'>Solver</a>
</li></ol>
</div>

<!--PageFooterFmt-->
<!--HTMLFooter-->
</div></div>
</body>
</html>