By industry Industrial project management software

Project management software for industry has to hold together projects of very different natures: a product launch, capital works on a line, equipment maintenance, requests from a technical department. The client is sometimes production or another site of the group, sometimes an external customer placing the order, and suppliers take their share. pylotik manages these commitments, their milestones and the workload of the teams on a single set of data.

The problem

What gets lost in an industrial project.

The technology is rarely at fault. What goes wrong sits between teams, sites and suppliers.

The same people on every front

The technician preparing the line shutdown is also the one called for this week's breakdown and for the new product trial. Without a workload plan, the project milestone slips in silence.

The internal client has no contract

When the client is production or another site, nothing is written down: neither the scope, nor the dates, nor what has been approved. Every change of request is argued from memory.

The supplier reports by email

The subcontractor delivering a piece of equipment sends progress when asked. The delay is found at receipt, when there is no margin left to recover it.

The usual reflex is to rebuild the tracking in a spreadsheet and a slide deck before every review. The information exists, but it is reliable only on the day someone copied it.

In practice

What pylotik brings to industry.

Design, production and maintenance tools stay in place. The management of the work, on the other hand, leaves the spreadsheet.

A contract for every project

Each project carries its contract, fixed-price with a milestone-based payment schedule or time and materials. Ordered, invoiced, paid, balance due, cost and margin are read in the same place.

Internal projects with a framework

A project run for production or for a site has a client, milestones, committees and validated minutes. Nobody has to chase a verbal agreement.

Maintenance managed as a commitment

A maintenance contract carries its period, its volume in days, its catalog and its committee. Interventions, in the background, are scheduled against real workload.

The real workload of the teams

Workload plan, weekly time entry, weekly report and team reviews: the milestone is checked against real availability.

Suppliers and customers placing orders, connected

A project connects one supplier and one client. Several subcontractors are managed by linking their projects to yours, with watched milestones. An integrator deploying a system at a client, with several suppliers, gets one project per part. See multi-project management for client and supplier projects.

Free client access

The external customer follows what concerns them and validates what is submitted to them, without seeing your margins or your workload.

Nobody is rated, nothing is scored: feedback goes to the recipient its author chooses. This is what we call operational commitment management: the commitments between a client and its supplier (deliverables, milestones, contract volumes, decisions), held as reference data that client and supplier each read according to their rights. The full tour is on the product page.

Product and service

A piece of equipment sold, from installation to the maintenance contract.

An equipment manufacturer does not just deliver a machine: it also commits to its installation, its commissioning, user training and, often, its maintenance. Each step is a commitment to the same client. pylotik tracks them in one place, next to the ERP that took the order.

Step 1

Installation, a project

One project per piece of equipment or per site, with its work packages, milestones, calendar and the workload of the teams involved. Subcontractors have their own project, linked to yours with the Extended Project module.

Step 2

Committees and validations

Site meetings are held on the pylotik screens: decisions, actions and risks are attached to them, and the minutes go to the client for validation.

Step 3

Commissioning

Commissioning is a milestone of the project. The minutes of the acceptance committee, validated by the client, keep a record of it.

Step 4

Interventions

An intervention is scheduled by the half-day on the technicians' actual workload, then validated by the client's signature, with the Interventions module, from the Business tier.

Step 5

The maintenance contract

A period, a volume in days, a catalogue, a committee and indicators shared with the client, fixed-price or time and materials. It is the same client's contract: its record gives access to the installation as well as to maintenance.

What stays elsewhere

Your business tools

The installed base, spare parts and preventive maintenance stay in the CMMS, orders, stock and invoicing in the ERP, manufacturing in the MES. pylotik does not replace them.

The same path applies to a technical distributor that delivers, installs and provides after-sales service. See where pylotik fits for product and service activities.

Around the project

An industrial project crosses four families of software.

Each keeps its role. pylotik holds what connects them: the commitment made to the client, and the workload of the teams who keep it.

ERP and MRP/production planning

Orders, purchasing, stock, bills of materials, costs and invoices. The project contract picks up what is ordered, invoiced and paid, and billing orders go to the ERP, which issues the invoices.

MES and APS

Scheduling, shop-floor execution, machine data and traceability stay in the MES. Nothing flows from it into pylotik automatically: the delivery delay that results is something to handle with the client.

CMMS

Asset base, equipment, spare parts and preventive maintenance stay in the CMMS. pylotik holds the maintenance contract agreed with the client, not the asset base.

Project ticketing and ITSM

Project ticketing, such as Jira, keeps the technical work, and pylotik connects to it through connectors built to your needs (optional, from the Business tier). ITSM handles incidents under service levels, which pylotik does not do.

Example: an integrator deploys an automated line at an industrial client, with two subcontractors. Each part has its own project, linked to the integrator's, with watched milestones. The client follows theirs and validates the minutes. At acceptance, a maintenance contract in days takes over.

The limits

What pylotik does not do in an industrial setting.

Out of scope pylotik is not an ERP, does not keep the books and does not issue invoices: it connects to the ERP, through a connector built to your needs, to send it billing orders. It is not a CMMS: no asset or equipment management, no spare parts, no preventive maintenance triggered by a meter. No routes, no geolocation, no offline mode for interventions. No production scheduling and no bill-of-materials management: that is the ground of the MES, the APS and production planning software. No service levels (SLA) or penalties.

What it carries sits alongside these tools: the commitments made to production, to sites and to customers placing orders, and the workload of the teams who keep them. Seat and module prices are public on the pricing page.

Frequently asked questions

What we are asked in industry.

How do I track the installation and maintenance of equipment sold to a client?

Installation is tracked as a project (work packages, milestones, calendar, committees validated by the client), maintenance as a contract (period, volume in days, catalogue, committee). Interventions are scheduled and validated by the client with the Interventions module. All of it is found on the client's record. The installed base, spare parts and preventive maintenance stay in the CMMS. See the path from installation to the maintenance contract.

Can I manage a project whose client is another site of the group?

Yes. The client of a project can be an internal team: a plant, production, a department. An internal client team within your organization takes a seat according to its role, while access for external client organizations is free.

Do you replace our CMMS?

No. The CMMS manages the asset base, equipment and spare parts. pylotik manages maintenance contracts, their volume, their interventions and their committees, with the maintenance client.

How do I track the milestones of an industrial project with several subcontractors?

Each subcontractor has its own project, linked to yours. Dependencies between projects and milestones are watched, with no automatic recalculation of dates: a milestone that slips at a supplier shows up on your side.

Are technicians' interventions accepted by the client?

With the Interventions module, available from the Business tier, an intervention is scheduled by the half-day against real workload. It is accepted by the client's signature, on mobile, in the portal or on paper, or refused with a reason.

Does pylotik manage service levels (SLAs) for a maintenance contract?

No. pylotik manages neither service levels nor penalties. A maintenance contract carries its period, its volume in days, its catalog and its committee, and the volume consumed is tracked. Incident service levels belong to an ITSM tool.

Does pylotik replace our MES or our ERP?

No. The MES runs and tracks manufacturing, the ERP handles orders, stock and accounting. pylotik manages the commitment made to the client and the workload of the teams who keep it.

Where is the data hosted?

In France. pylotik is designed and hosted in France by orgatypik SAS, in Toulouse.

Next

Going further.

See an industrial project managed

The demo runs on a data set that is already filled in: a project and its milestones, a maintenance contract, a team's workload, and what the client reads of it.