Search
You can find the results of your search below.
Matching pagenames:
Fulltext results:
- EU Project Delivery
- agement ===== Trigger ===== This process starts at the beginning of each active EU project reporting... ===== Steps ===== - **Deliverable mapping** — At the start of each project period (or quarter), Ks... corecard metric]] in OpenProject. Any deliverable at risk goes on the [[pub:company:traction#issues_li... contributor produces the deliverable content. Format follows the project consortium's template. Stored
- Customer Onboarding
- (Mautic notification) or via a direct outreach that results in a trial account being created. ===== ... / - **7-day check-in** — Automated Mautic email at day 7: "How is it going?" with link to feedback f... the customer is active (logged in ≥ 3 times, has at least one framework mapped), initiate a conversio... //erp.unicis.tech|Dolibarr]] * The customer has at least one framework mapped in the platform * Th
- Invoicing & Billing
- Commission ==== - **Commission calculated** — At the end of each month, Predrag reviews partner-re... Predrag prepares the financial report in the format required by the project grant agreement. \\//Tool... ndard subscriptions. This process will be updated at that point. * All financial records are confidential. Store only in [[https://erp.unicis.tech|Dolib
- Platform Release
- a set of features/fixes is ready to ship — either at the end of a planned sprint or when a critical fi... Rs and issues in GitHub. Agrees with Predrag on what is in scope for the release. Creates a GitHub mil... All in-scope PRs reviewed and merged to ''main''. At least one reviewer per PR (Peter or designated re... , PDF, HTML) renders correctly \\ * REST API (at ''/api-docs'') returns correct responses \\ *
- Core Processes
- ==== This section documents the Core Processes that run Unicis. A Core Process is a named, repeatable workflow that produces a consistent result. Every process has a... the process working correctly * **Trigger** — what starts the process * **Steps** — numbered, in order, with tool references * **Output** — what a successful completion looks like * **Tools**
- Process Template
- === Purpose ==== [Why does this process exist? What problem does it solve? One or two sentences.] ==== Owner ==== **[Full name]** — [Seat / Role] The owner is accountable for this proces... s starts when: [describe the event or condition that initiates this process — e.g., "a new trial signu... eps ==== - **[Step name]** — [Description of what happens, who does it, and which tool is used] -
- Support Resolution
- ===== > 🔄 **Status: Draft** — Review and approve at next Quarterly Session. [[pub:processes:start|← ... Alexander as a new conversation. GitHub Issues that are support requests (not bug reports) are also l