After you create the data structure for a design, you can start the design process. This chapter provides an overview and instructions on starting the designs for the components that will be used by the users in Primavera Unifier:
- The shells or projects
- The configurable managers
- The business processes
- The asset classes
- The plans
- The resources
- The spaces and levels for facilities management
Starting a new design begins a different process, depending on what you are creating—a shell/project, manager, business process, asset class, plan, or spaces and levels.
- Most of your designs will be for business processes, and for most of these, the design routine includes creating the forms and workflows that will dictate how your business activities function. For example, a complex business process can dictate how costs move through the approval process
- For other designs, you will create single records to collect company or project information necessary for the proper operation of components in Primavera Unifier.
- For managers, the design process can include creating a pool of resources or classes of assets that will be used in Primavera Unifier.
- For configurable managers, you will be designing the sheets on which users will track items and a pool of codes for organizing the items.
- For shells, you will be designing a pool of shell types that can be organized into a hierarchy in Primavera Unifier.
Before you continue further, it may help to review Business Processes Overview. That topic contains links to descriptions of each business process type and what it needs, design-wise, to operate effectively. What each manager needs to become active in Primavera Unifier is described in the topics describing each manager.
You will be using uDesigner to build the forms, workflows (where required), and logs that constitute a business process or other Primavera Unifier component. What you create in uDesigner is what the user will use in Primavera Unifier.
