OK, so we're developing a project management software (of sorts, way wider scope) where we basically divide everything into 3 levels, organizations, projects and roles.
However, there has been some complaining that we're using the word 'project' too loosely, i.e. involving cases that do not really have any goals/endpoints. Also, it would make a lot of sense for us to separate the static project type from normal projects. Having a good label for it would also help design work.
A few cases:
1) Organization X is developing software Y for some client Z. Person A contributes in the developer role, person B as a designer and person C as a manager. This activity can clearly be called a project and the product is a piece of software.
2) Client Z outsources some static, repetitive sales work to organization X. Person A contributes as a salesman, person B handles management and person C the bureaucracy work. The product can be seen as a service, and the activity is ???
So far the top candidates are
The problem with this is that all of the roles are technically jobs and it would seem unnatural to have a role inside a job.
This seems wrong as service seems to be to 2) what software is to 1). What we need is what X is to 2) where project is to 1).
Other than that, we're drawing blanks, probably partly due to not being native English speakers. It's a silly issue, but something we still need to solve well.
Bonus points for the term not being overly technical.