Skip to content

Projects — Transactions

Overview

Projects is the operational core of SARA. Each project is both a cost center and an income center: all expenditures (hours, purchase orders, refunds, logistics) and all revenue (quotes, invoices, payments) are tracked against individual projects. Nearly every financial and operational record in the system is associated with a project.

For the end-to-end lifecycle, see: Workflow.

Note

For common UI patterns used across SARA (tables, filters, dynamic columns, naming conventions), see: Common Features

Projects

Overview

The main transaction where project managers, sales staff, and finance users track all projects across their full lifecycle — from creation through technical and financial closure.

What you will see

Columns in this list carry specific business meaning:

  • Internal code — auto-generated composite identifier built from the company prefix, sequential ID, country code, and project description (e.g., u.2.1728). Cannot be edited directly.
  • External code — the customer's reference identifier for this project (e.g., a customer PO or project number from their own system).
  • Compose name — a derived display name combining the internal code, customer name, date, and final product. Used to identify the project in a human-readable format across SARA.
  • Metric score — a weighted performance score generated from the project metrics panel. Shown once metrics have been rated for the project. Higher scores indicate stronger project health.
  • Cost / Real income / Current profit — live financial totals aggregated from all linked expenditures and invoices. Visible only with the view cost and income permission.
  • Potential income / Potential profit % — forecasted revenue and profit margin inherited from the linked quote. Read-only; they update if the quote changes.
  • Plants — the manufacturing facilities where project work takes place. A project can be linked to multiple plants.

The row action menu changes based on the project's current status. See Workflow for what each status allows.

What you can do here

  • Check technical pending and perform technical closure (technical closure permission, ACTV projects)

    The row menu shows "Check technical pending," which opens a panel listing any open logistics records or timesheets. Once all are resolved, the "Technical closure" button confirms the transition (ACTV → TCLS). After closure, no new hours, CPOs, refunds, or logistics can be recorded against the project.

  • Financial closure (finance closure permission, TCLS projects)

    The row menu shows "Financial closure" (or "Pending financial" if open items remain). The system validates all linked CPOs before closing: active or direction-pending CPOs block the action; amount mismatches prompt the user to notify direction for resolution. When all totals balance, the project is moved to FINA.

  • Finalize (edit permission, non-FINA projects)

    A red action in the row menu for exceptional cases — such as projects that will not follow the standard closure process. A written reason is required and permanently logged. This is a bypass; prefer the standard financial closure path.

  • Open project (edit permission, TCLS or FINA projects)

    Re-opens a closed project back to ACTV. All expenditure recording resumes. Requires a reason.

  • Assign departments (edit permission)

    Opens a hierarchical department tree picker to link the project to one or more cost centers. Department assignments control how costs are allocated in reporting.

  • Project metrics (project metrics permission, ACTV and TCLS)

    Opens the project metrics panel, accessible from the row action menu or the "Project metrics" button at the top of the list. Each performance dimension is rated on a 1–10 slider; ratings feed the metric score column.

  • Link quote

    Appears on projects that were created manually (without a linked quote). Allows matching the project to an existing quote retroactively.

  • CPOs (pos view permission)

    Opens the CPO (Customer Purchase Order) management screen for this project at /pos/{id}. Shows all linked CPOs with version history and approval status.

  • SPO items

    Opens the special purchase order items panel for this project.

  • Programmers reports

    Opens a resource utilization and activity report for the project's assigned collaborators.

Tabs (edit modal)

The edit modal organizes project configuration into five tabs:

  • Project information — Core project identity: short name, external code, start and end dates, plants, project type, final product, description, compose name, robot controllers, PLCs, quality standards, minimum weekly hours per collaborator, and week start day.
  • Resources — Assigned personnel: project manager, project leaders (multiple), external manager, external leader (customer-side contacts), hours granularity, and time report type. Time report type determines how timesheets for this project are approved (customer signature, email approval, or time clock).
  • Departments — Department tree assignment. Nodes from the organizational hierarchy are selected here to link the project to cost centers.
  • Budget — Budget line items per logistics node. Each line has a category (from the project budget catalog), an amount, and a currency. Multiple currencies are supported per project.
  • Equipment / Safety — PPE requirements for project work, configured by body region (head, body, arms, hands, feet). Defines mandatory safety equipment for collaborators assigned to the project.

Deliverables

Overview

Accessible from each project's row action menu, the deliverables panel tracks specific outputs that must be produced or handed off for the project. Each deliverable has its own lifecycle and can carry file attachments.

What you can do here

  • Create deliverables — Add items with a description, quantity, due date, and a responsible collaborator.
  • Mark as ready — Indicates the deliverable has been completed internally and is ready for handoff.
  • Mark as delivered — Confirms the deliverable has been handed off to the customer or stakeholder.
  • Cancel — Voids a deliverable that will no longer be fulfilled. Available until the deliverable reaches delivered or cancelled status.
  • Download documents — If files have been uploaded to a deliverable, they can be downloaded in bulk from the list.

Connections to other modules

Projects are the central record in SARA. The following modules all link to or depend on project data:

  • Sales / Quotes — Project creation is triggered by quote approval. The quote reference is stored on the project and displayed as a read-only column.
  • Timesheets — Hours are recorded against a project; the time report type configured on the project determines the timesheet approval flow.
  • Finance / Refunds — Expense reimbursements are assigned to a project budget node.
  • Purchasing / CPOs — Customer purchase orders are linked to project budget nodes. CPO totals feed the financial closure validation.
  • Logistics — Travel and accommodation records are associated with a project. Pending logistics block technical closure.
  • Departments — Department assignments on a project enable cost center allocation across all linked expenditures.

Permissions

Permissions

Access and actions are permission-driven. See: Permissions