TMS, File Workflow & Deliverables — business view

1. Business Summary

Manages source/in/out folders, phase splitting and merging, pre-translation, deliverables packaging, and ownCloud-backed file storage.

2. Business Value

The backbone of production — file integrity from client to vendor and back.

3. Users / Stakeholders

PMs, engineers, linguists, reviewers, clients.

4. Workflows

• Phase setup; file ingest; task-to-file binding; splitting/merging; pre-translation; deliverables; cleanup.

5. Sub-Features

• Phase management.
• ownCloud cache synchronisation.
• Memsource integration.
• Folder/zip operations.

6. Business Rules

• File path conventions are standardised.
• Memsource flow includes a deliberate wait for analysis.
• Uncompleted segments can be split for parallel work.

7. Data Entities

Phase, Job Auto-plan File, ownCloud cache tables, File, Entity File.

8. Entry Points

• TMS screens.
• Cloud helper screens.
• Mobile API for uploads/downloads.

9. Inputs & Outputs

• Inputs: source files, TMS responses.
• Outputs: phase-aware file structure, deliverables, downloads.

10. Integrations

• Memsource (TMS), ownCloud, partner systems for source ingest.

11. Calculations / Logic

• Weighted-word analysis from TMS feeds pricing.

12. Status Lifecycle

• File phase progression: source → in → out → deliverable.

13. Permissions

• PM, engineer, vendor (per task).

14. Reports & KPIs

• Files per job, deliverables, cache health.

15. Risks & Observations

• File-cache vs. filesystem drift can lose access to files.
• Hard-coded paths.
• Memsource sync includes a long synchronous wait.

16. Source Code Evidence

• app/Controller/TmsController.php, CloudController.php.