Engineer to Order System
This chapter discusses:
Engineer to Order system.
Project life cycle.
Engineer to Order system features.
Engineer to Order tables.
Engineer to Order System
JD Edwards EnterpriseOne Engineer to Order enables companies whose business consists of engineer-to-order and make-to-order projects to increase the profitability of the projects that they run, improve efficiency, and leverage relevant data that they already possess. The JD Edwards EnterpriseOne Engineer to Order system accomplishes these goals by enabling you to:
Review and track detail information about projects.
Schedule project tasks.
Review up-to-date costing information.
In addition, JD Edwards EnterpriseOne Engineer to Order is fully integrated with the supply chain execution applications for efficient project execution.
JD Edwards EnterpriseOne Engineer to Order functions in the context of generally accepted project-management practices and strategies. The system provides information and mechanisms to move a project through these four phases that are commonly associated with projects:
Project initiation
Project planning
Project execution
Project close
During the project initiation phase, you analyze the request for a quote that is sent in by the customer, estimate the scope of the project, and define project information, such as work breakdown structure, task schedules, estimated cost, and so on, that is sufficient to provide the customer with a quote.
During the project planning phase, which begins after the customer accepts the quote, you refine the project scope, as well as the task, schedule, resource, and financial information that is associated with the project. For example, you assign resources to tasks and perform financial and inventory commitments to fulfill work order requirements. At the end of the planning phase, you establish the project baseline.
After you complete the planning and freeze the budgeted amounts, the project moves into the execution and control phase. In this phase, you complete the scheduled project tasks and measure project progress and performance to be able to take corrective action if the project does not progress as planned.
The project close phase consists of close-out activities that are related to tasks and product shipments, asset capitalization, and final reporting.
Project Life Cycle
This diagram provides an overview of the different stages that a project typically goes through:
Engineer to Order System Features
To help you create and execute large-scale projects, JD Edwards EnterpriseOne Engineer to Order provides these features, which enable you to complete the different tasks that are involved in managing a project:
|
Feature |
Description |
|
You can create and maintain cost amounts for projects that are created and initiated. Cost estimates are uploaded to the budgeted amount for a project when a quote is accepted. You can also set up budgets for projects to track cost overages. |
|
|
You can formulate a quote to send to prospective customers, providing an estimate of the price for the item or series of items for which the customer has requested a quote. |
|
|
You can create documentation pertaining to the product that has been requested, and the customer can review the documentation. |
|
|
You can suggest ordering requirements for project materials and give visibility to the supply and demand that is created by the project's activities. |
|
|
You can develop and maintain a time line within which all project activities can be tracked for on-time delivery of the end item for the project. |
|
|
You can provide alerts to the project manager when a project is not meeting scheduling, cost, and inventory requirements. |
Engineer to Order Tables
Because JD Edwards EnterpriseOne Engineer to Order integrates with many JD Edwards EnterpriseOne systems, you use the tables in these other systems when you create and work with engineer to order (ETO) projects. For example, you use the Work Order Master table (F4801) to store project header and task information. In addition, you also store project information in tables that are specific to JD Edwards EnterpriseOne Engineer to Order:
|
Table |
Description |
|
This table stores information that is entered for the project header, such as status information and the processing settings for a project. |
|
|
This table stores the header information for the quote that is related to the project, such as the version and the number of the customer for whom the quote is created. |
|
|
This table stores the detail lines from the work breakdown structure that you chose to include in the quote, together with the margin percent value and quote amount for each line. |
|
|
This table stores the task dependencies that you establish between the tasks on the work breakdown structure, including the lag time between tasks. |
|
|
This table stores the cost type and account mappings that are required to correctly roll up cost information for a project. |
|
|
This table is a work file that stores the scheduled dates created and deleted when the Project Workbench program (P31P001) is used to schedule. |
|
|
This table is a work file that stores record reservation details created and deleted when the Project Workbench program (P31P001) is viewed in the Edit Tasks or Edit and Lock All Tasks mode. |
|
|
This table stores project-specific inventory commitments. These records are deleted when the commitment is relieved. |
|
|
This table stores order information that the system uses to link the project descriptive task to the related orders. This table contains the descriptive task-order number and order type, and detail information from the related orders, such as document type, extended costs, and order status. |
|
|
This is a tag table to table F4801 that is used only for ETO. For every record in table F4801 that is associated with a project (PRJM not blank), there will be a corresponding record created in the F4801T1 table. |