Request For Resources (RFR) — business view

Technical trace: Request For Resources (RFR)

1. Business Summary

A formal lifecycle object that a PM or VM raises to source talent for a job/task: created in draft, validated, published, matched (manually or via selection), assigned, delivered, closed. Extensions and reopens are supported.

2. Business Value

Standardises how the business sources, fulfils, and audits resourcing requests — connects production demand to vendor supply.

3. Users / Stakeholders

Project managers, vendor managers, account managers.

4. Workflows

  • Create. Draft RFR with account/project/job/task context, language pair, specifications.
  • Validate & publish. Validator approves; selection is triggered.
  • Match resources. Selection engine returns candidates; PM/VM approves or rejects.
  • Assign & notify. Assigned resources are notified.
  • Deliver & close. Final billing follows.
  • Extend / reopen. Optional, with reasons.

5. Sub-Features

  • Per-task RFR breakdown.
  • Candidate pool (pre-resource trial).
  • Selected resources with delivery tracking.
  • Information items (notes/files).
  • Logs (audit trail).
  • Extensions and reopens.

6. Business Rules

  • Validator gate before publication.
  • Status drives downstream actions.
  • Email-driven inline RFR creation through the Command engine.

7. Data Entities

Request For Resource, RFR Task, RFR Candidate, RFR Resource, RFR Log, RFR Information, Request Extension Status, Reopen Reason, Resource Request Type.

8. Entry Points

  • RFR screens.
  • Email command engine.

9. Inputs & Outputs

  • Inputs: account/job/task context, specs, validator decisions.
  • Outputs: matched resources, logs, status changes, downstream vendor invoices.

10. Integrations

  • Selection engine, email, partner systems (Welocalize/Junction/Moravia), finance.

11. Calculations / Logic

  • Time-share, deadline propagation, extension impact.

12. Status Lifecycle

  • Draft → published → selected → assigned → delivered → closed; can reopen.

13. Permissions

  • PM, VM, AM, validator, qualifier.

14. Reports & KPIs

  • Time-to-fill, fill rate, extensions, reopens.

15. Risks & Observations

  • The email-driven creation grammar is sensitive to malformed input — operational risk.
  • State transitions are implicit; no formal state machine enforces them.

16. Source Code Evidence

  • app/Plugin/resources/Model/RequestForResource*.php.
  • app/Controller/CommandController.php.

← Deep dives index