Products and modules
| Term | Meaning | Field of study |
|---|---|---|
| Pulse of the functions | The block on the Management Today page that only top management sees: the status, score, change and open-risk count of each function; problematic ones at the top. | Section 4 |
| Organization | The organization around which everything in the application is arranged. Users are members of an organization, every record belongs to an organization, and a user sees only the records of the organization they are a member of. | Sections 0, 3 |
| Module | A unit that can be enabled individually for an organization; each product consists of one or several modules. | Sections 0, 1 |
| Shared agenda | On the Management Today page: the meetings of the coming days, company events, order deliveries, collection promises, work-order completions and the number of people on leave; overdue items stay in a separate strip at the top. | Section 4 |
| Shared foundation | The product whose module is PULS Connect and whose surface on top of it is Reports. | Sections 0, 2, 8 |
| Features | Described in Section 17. | Section 17 |
| PULS Connect | The module through which records enter PULS: file upload, automatic pull with a bridge that reads from the organization’s database, or sending with an API key. Incoming records are mapped to PULS fields and transferred to the tables of the relevant module. | Sections 0, 2 |
| Standards and incentives | Described in Section 16. | Sections 0, 16 |
| Management today | The summary page the manager opens when starting the day: pending decisions and approvals, what has changed since yesterday, the agenda and the health status of the functions. It does not produce its own score; it reads health information from the Business Health measurement. | Section 4 |
| Where it occurs | A section that exists in some products in addition to the modules and reads the records of several modules together. | Section 0 |
Access and permissions
| Term | Meaning | Field of study |
|---|---|---|
| Trial period | The 30-day period that begins together with the organization, in an organization opened by the PULS team. | Section 1 |
| View scope | On CRM’s screens filtered by person (e.g. Today, Visits, Collection Desk), showing the whole organization to a user who carries the crm.manage permission and only their own records to a user tied to a sales rep code. | Section 12 |
| Leave | The key that a role carries and that names a single operation (e.g. crm.view, crm.manage); screens and write requests are checked on the server with this key. | Sections 1, 3 |
| Organization isolation | Determining from membership which organization a request belongs to; for changes and deletions, the organization is read from the record itself, not from the value in the request. | Chapter 3 |
| License | Which modules are enabled in the organization. The license together with the permissions carried by the user’s role determines which sections the user sees. | Sections 0, 1, 3 |
| Salary permission | The hr.salary.view permission that opens up salary and wage information; the organization owner and the organization administrator see it without this permission being checked. Salary data is not sent from the server to a user without the permission, and the labor component does not appear on Production’s cost screens. | Sections 3, 13, 14 |
| Top management | A user in the organization owner or administrator role, or one who carries the health.view permission. Sees the whole company and goes directly to the Management Today page after signing in. | Section 4 |
Data and connection
| Term | Meaning | Field of study |
|---|---|---|
| Carry-forward row | The row looked for in the source of the Debt Aging screen. If the source has no carry-forward row, the amount is not the real account balance but the difference between invoices and payments within the movement window; suppliers whose carry-forward row comes in inconsistent are not included in the totals and are listed with the reason. | Section 9 |
| Mapping | The step that connects the columns of incoming records to PULS fields; mapped records are transferred to the tables of the relevant module. | Chapter 2 |
| Snapshot date | The day the data belongs to, on the stock screens, Finance’s aging screens and the Collection Desk screen. The «as of» selector on the stock screens marks the newest one with «(latest)»; the selected date is written to the address bar. | Sections 9, 11, 12 |
| KVKK approval | The tick next to a field that carries personal data on the mapping screen. The field is not saved without the tick; the server also rejects a personal field without approval. | Sections 2, 3 |
| Automatic fetch | PULS itself picking up a file that sits in the cloud and that you update, or the files that the PULS bridge produces from your database. | Chapter 2 |
| PULS Connect stages | The four steps by which data enters PULS: «Connect data», «Map», «Transfer» and «Validate»; each stage has its own screen. | Chapter 2 |
| PULS bridge | The connection that reads from the organization’s own database (MSSQL or PostgreSQL) and produces files for the automatic pull. | Sections 0, 2 |
| Report reconciliation | The screen that compares the receivables or sales report you obtained from your source system with the figures in PULS. The file is read in your browser, only totals are sent to PULS and the result is not saved. | Sections 2, 3 |
Measures and health
| Term | Meaning | Field of study |
|---|---|---|
| Component | A part that makes up a health area. A component that cannot be measured is not removed from the list; it stays as a gray row. | Section 5 |
| Business Health score | The measure that combines the company’s function areas into a single health score between 0 and 100; the coverage rate is always written next to it. | Section 5 |
| Coverage rate | The ratio of the weight of the measurable areas to the total weight; a score with low coverage rests on a small number of areas. | Section 5 |
| Mixed window | The note that appears when areas are measured in different time windows; in that case, instead of comparing the overall score of two days, one looks at the area cards. | Section 5 |
| Not comparable | The expression that appears next to the score in place of the band if an area’s measurement for that day is faulty; the sentence next to it explains the reason. | Section 5 |
| Not measurable | The expression stating that there is no data, that it could not be read, or that the denominator is empty. In this case zero is not written; an amount that cannot be measured is not included in the totals. | Sections 5, 6, 9, 15 |
| Health band | The range the score falls into: Critical (below 40), At risk (40–55), To be monitored (55–70) and Healthy (70 and above). If the score cannot be calculated, it says «Waiting for data». | Section 5 |
| Health Setup | The screen that sets, according to your business’s own answers, how much weight each area carries in the overall score; changing it requires health.manage. | Section 5 |
Opportunity and risk
| Term | Meaning | Field of study |
|---|---|---|
| Finding | In Opportunities & Risks, a single situation caught by the scanner that looks at the records of more than one module; it is shown as a card with its title, amount, severity, the modules it touches and its evidence. | Section 6 |
| Finding status | The decision given for a finding: «Open», «Seen», «Resolved» and «Wrong finding». | Section 6 |
| Value ledger | The section that shows open exposure, the breakdown by status, and whether closed findings reappear in the next scan, independently of the filter, across findings in all statuses (except «No scanner» cards). | Section 6 |
| Opportunity | Missed gain — it has not happened yet. | Section 6 |
| Risk | Value about to be lost — it is happening. | Section 6 |
| Scanner thresholds | The screen of the numbers that determine when scanners count a situation as a finding. A threshold not saved for the organization works with the product’s default value. | Section 6 |
| Upper bound | The badge on a finding card showing that the amount is written with the prefix «at most»; the amount of these cards is not added to the total. | Section 6 |
Business intelligence and reports
| Term | Meaning | Field of study |
|---|---|---|
| Area (Business Intelligence) | The section in Business Intelligence that reads the records of a module. Some read the change over time («Trends»), some read the current state («Snapshot»). | Section 7 |
| Briefing | The «Executive briefing» page that opens when you enter Business Intelligence; the indicator tiles are measured only for the areas the user can see. | Section 7 |
| Where Did This Number Come From? | The page that opens when you click a card’s number in Reports and shows the records that make up that number; its tabs are Summary, Breakdown and Records. | Section 8 |
| Explorer | The surface where you build your own question: breakdown, measure, filter and chart type are chosen, and the result can be exported. In Reports it also opens as one of the modes of a ready-made report. | Sections 7, 8, 11 |
| MCP connection | The address from which the Lens and Explorer tools can be called from the user’s own model client; on this path the model runs on the user’s side. | Section 7 |
| Lens | A measurement that answers a single question over a module’s records, whose name and description are defined in the application. If the module is disabled in the organization or the user cannot see it, the lens returns «disabled» without running a query. | Section 7 |
| PULS Assistant | The surface where you ask questions. The model can call only the lenses in the menu and the defined Explorer queries, for at most 4 rounds; raw record rows do not go to the model. | Section 7 |
| Scenario | The mode in Explorer and ready-made reports that changes measures as a percentage with sliders; «Reset» returns to the beginning. | Sections 7, 8 |
| Freshness strip | The strip at the top of Reports’ function, report and evidence pages that states which dates the data covers. | Section 8 |
| Trends | A tab of an area: «What changed in this ledger this month». | Section 7 |
Finance, sales and stock
| Term | Meaning | Field of study |
|---|---|---|
| Balance subject to interest | The entire balance of an account whose average due date has passed; kept separate from the «Overdue» amount. | Sections 9, 12 |
| Financial Health score | The score and its band on the Financial Health screen: below 40 Critical, below 60 At risk, below 75 To be monitored, above that Healthy. The score is scaled only over the dimensions that can be calculated; missing data is not counted as zero points. | Section 9 |
| Hidden cost | A preliminary impact calculation that totals, on an annual basis, the burdens that do not appear as separate rows in finance tables (cash leakage and opportunity cost); it is not a definitive report. | Section 9 |
| Brand attribution | Linking a brand to a stock item. If the material has been sold, the brand on the sale is used and the attribution is counted as «Exact»; if it has not been sold, the brand derived from the stock label is used and the attribution is an inference. | Section 11 |
| Net revenue | In Sales Analysis, the sales amount including returns; margin (profit / net revenue) and return rate are calculated on this amount. | Section 10 |
| Forecast freezing | Saving the forecast of a period on the Financial Health screen. It cannot be done retroactively, and the same period cannot be frozen a second time; the «Forecast & management discipline» dimension can be measured only if past forecasts have been frozen. | Section 9 |
| Overdue | Overdue amount per invoice. If there is no invoice-level breakdown, it shows «not measurable» instead of zero. | Sections 9, 12 |
Customers and sales team
| Term | Meaning | Field of study |
|---|---|---|
| Contraction | A customer who is still buying but whose basket is shrinking; those who buy nothing at all are counted on the Going Quiet screen and are not double-counted here. | Section 12 |
| Ledger freshness strip | A strip above the CRM pages that shows the date of the newest record in the ledgers; up to 7 days old it appears fresh, up to 30 days old late, and anything older stale. | Section 12 |
| Customer 360 | The details card that opens when you click a customer and does not appear in the menu: the customer's sales, opportunities, visits, and contacts. | Section 12 |
| Going silent | A break in the purchasing rhythm of a customer who buys regularly; the yardstick is not a fixed threshold but the customer's own history. | Section 12 |
| Collections desk | The collection agenda that lists, one by one, the customers who have overdue receivables or receivables subject to interest, as of the selected cut-off date. | Section 12 |
| Payment promise | The promise date, amount, and note entered for a customer with «Get promise» on the Collection Desk screen; promises also appear in the shared agenda of the Management Today page. | Chapters 4, 12 |
| Commercial status | The customer's commercial status (Active, Under monitoring, Credit limit exceeded, Frozen, Bad debt, and Disputed). The statuses Credit limit exceeded, Frozen, Bad debt, and Disputed remove the customer from the sales action lists; collection work does not stop in any status. | Section 12 |
Human resources
| Term | Meaning | Field of study |
|---|---|---|
| 9-Box | A view that shows performance and potential assessments in a nine-cell matrix; scores are entered between 0 and 10 in half-point steps. | Chapter 13 |
| Sub-package | A package in HR that is enabled separately, outside the base license (İK360, PULS Engage, and PULS Performance). On a screen that is not in your package, a lock panel appears instead of the content. | Chapter 13 |
| Pulse survey | A survey opened to employees. In an anonymous survey, the server does not return individual responses, and aggregate results (response count, average score, eNPS) become available once at least 5 responses have been collected. | Chapter 13 |
| Expertise shape | The shape derived from an employee's skill records. I is deep expertise in a single area; T is deep expertise in one area with basic competence in other areas; M is deep expertise in more than one area, plus breadth. | Chapter 13 |
| Insufficient data | The wording shown instead of a score when the measurable weight of a department or an employee on HR's Health screen falls below the 50% threshold; no score is made up. | Chapter 13 |
Production and operations
| Term | Meaning | Field of study |
|---|---|---|
| Six big losses | The six classes into which losses are divided: Breakdown, Adjustment and preparation, Minor stoppage, Speed loss (derived), Startup scrap, and Production scrap; each falls under the A, P, or Q axis. | Chapter 14 |
| Link suggestion | Suggesting, for an unlinked machine, a shipment of the same customer that was delivered no more than 30 days before the machine was commissioned; if there are several candidates, the closest one is suggested. | Chapter 15 |
| Bottleneck | The machine with the highest ratio of planned load to measured capacity, where that ratio exceeds 100%; the ratio is the same as the calculation on the Capacity and Load screen. If no machine exceeds it, the screen states that there is no bottleneck and shows the most heavily loaded machine. | Chapter 14 |
| Joint | A link between two modules in the Operations Ring; it is written as «number / denominator» and as a percentage. If the denominator is empty, if the link has not been established, or if one of the two modules is disabled or unauthorized, it writes «Not measurable» instead of a number. | Chapter 15 |
| Machine passport | The page that opens when you tap a serial number in Installed Base: life line, breakdown frequency, linked problems, commercial status, and shipment link. Each neighboring piece of information is read with the permission of its own module. | Chapter 15 |
| Cost bridge | A view on the Cost screen that breaks down the difference between two work orders, or between a work order and the standard, term by term; without the labor (salary) permission, the difference is not broken down into terms. | Chapter 14 |
| OEE | On the OEE and Constraint screen, the product of the availability (A), performance (P), and quality (Q) ratios (A×P×Q). Card colors are only a screen tone, not a verdict. | Chapter 14 |
| Operations ring | The page that shows the Purchasing, Spare Parts, Service, Solution, Installed Base, and Logistics modules in a single ring; it opens if at least one of the modules has a license and view permission. | Chapter 15 |
| Promise slippage | The difference between the date confirmed by the supplier and the requested date in Purchasing's supply promise ledger (confirmed − requested). | Chapter 15 |
| Due date clusters | The single cluster each open work order falls into on the Due Date Risk screen: «Due date at risk», «Defective data», and «Fits». The due date is the planned finish of the work order. | Chapter 14 |
| Age band | The bands into which installed machines are divided by commissioning date: 0–1 years, 1–3 years, 3–5 years, 5–10 years, 10+ years, Future-dated, and Commissioning not entered. | Chapter 15 |