Pleximod records
Pleximod-owned records, primary text, and primary rules
v1.4 · Requirements Baseline
pleximod-management-proposal
by
Janvi shah
Janvi shahCould you please create a proposal
Comments (0)
Sign in to leave a comment
Proposal sections 01–06 · current: 01 Context
01Context/ 06
Document identity
- Document
- Pleximod Management System
- Volume
- Software Requirements Document
- Version
- 1.4
- Prepared for
- Shanil and the Pleximod team
- Date
- 8 October 2026
- Status
- Requirements baseline for proposal preparation
One system.Head office, factory,franchise.
Section 04Maintenance
Register every machine and its separately maintained components with an identifier, type, location, current reading, usage unit, service rule, and opening reading; record usage; show usage since service, the configured service limit, remaining service allowance, and approaching or overdue reminders; and record service or replacement while restarting only the relevant counter and retaining prior and lifetime history. Entered readings only — no sensors, controller connections, or automatic readings.
Access and ownership key · 05 codes
Colour is the code. Each layer of the maintenance record is marked by its owner or state, so the financial firewall between Pleximod and a franchise can be read before any machine record is opened.
KEY-01
Pleximod records
Pleximod-owned records: factory machinery and its service history, held under head-office ownership.
KEY-02
Pleximod controls and payment gates
Pleximod controls and payment gates: section boundaries, active markers, and dispatch gate states.
KEY-03
Franchise records and accepted or paid states
Franchise-owned records and accepted or paid states: franchise stock, retail invoices, and recorded customer payments.
KEY-04
Credit exception and incomplete cost
Credit exception and incomplete cost: authorised exceptions and cost entries still awaiting a value.
KEY-05
Shared master data
Shared master data: usage units, service rules, and location profiles used across every organisation.
Machine and component register
Module MCH-01 · Factory maintenance record
Maintenance state filter · usage units and service limits are configured separately for each machine or component
Register
Register, all states · 3 of 3 machines and components
| Identifier | Machine type | Location | Component | Usage unit | Service rule | Opening reading | Current reading | Usage since service | Service limit | Remaining allowance | Maintenance state | Availability | Last service date |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| MCH-PRESS-01 | Cold hydraulic press | Factory | Hydraulic pump unit | sheets | Service limit 12000 sheets | 0 | 8420 | 8420 | 12000 | 3580 | Approaching | Available | 2026-06-14 |
| MCH-EDGEBAND-02 | Edge banding machine | Factory | Glue pot assembly | operating hours | Calendar interval 500 operating hours | 0 | 512 | 512 | 500 | -12 | Overdue | Available | 2026-03-02 |
| MCH-MULTIBORE-03 | Multi-boring machine | Factory | Boring head spindle | cycles | Service limit 40000 cycles | 0 | 21460 | 21460 | 40000 | 18540 | Within limit | Available | 2026-08-21 |
Maintenance reminders
- MCH-EDGEBAND-02 · Glue pot assembly
- MCH-PRESS-01 · Hydraulic pump unit
Selected machine and component
Select a register row to read the selected machine or component: its configured service rule, usage since service, service limit, remaining allowance, reminder point and last service date.
Registration form · Cfg-06 register entry
Register machine or component
Usage units and service limits are configured separately for each machine or component. The initial implementation uses entered readings only.
Machine sensors, controller connections, automatic readings and predictive maintenance are excluded. Only readings entered by staff are recorded.
Scope statements
- Usage units, service limits and reminder points are configured separately for each machine or component.
- The register records entered readings only. Machine sensors, controller connections, automatic readings and predictive maintenance are excluded.
- Component replacement retains the prior and lifetime service history; only the relevant service counter restarts.
- This register holds factory maintenance records only. It does not display Pleximod material costs, profit figures or another franchise's records.
Record machine/component usage reading
Enter the usage reading taken from a registered machine or component counter. The sheet returns the usage since service, the configured service limit, and the remaining service allowance as a ruled counter row.
Usage reading recordDocument sheet · entered readings only · no automatic capture
Machine / component selector
3 registered itemsUsage reading form
Select a machine to beginSelect a machine or component from the register to open its reading form.
Entered readings only; no sensors or automatic readings.
Pleximod-owned equipment records. No material costs, profit figures, or another franchise's records are shown on this sheet.
Section 03 · MCH-05Factory · Service and replacement record
Service, replacement and counter restart
Record a service or component replacement against a machine or component whose service or replacement is due, restart only the counter affected by that action, and retain the prior service and lifetime history.
Machine service record · entered readings only
Service and replacement register
The machine selector below is limited to machines and components whose maintenance state is Approaching or Overdue and whose service or replacement is therefore due.
- Machines due
- 2
- Service records retained
- 2
- Selected
- —
01 · Machine and component selector
Condition: service or replacement due04 · Service and lifetime history
No machine selectedSelect a machine or component whose service or replacement is due to read its retained service and lifetime history.
Scope boundary
The service and lifetime history separates the current service counter from the retained lifetime reading. Only the counter named in the restart block is restarted; prior service records and lifetime history are kept and never erased. Service records use entered readings and staff-entered details only — no sensors, controller connections, automatic readings, or predictive maintenance are included in this scope.
Maintenance module register
Accepted baseline IDs for the maintenance scope, set small-caps in the left margin so each row can be audited against the requirements baseline. Scope item MCH-01 – APP-04.
- Pleximod
- Franchise
- Shared
| ID | Module and requirement | Owner |
|---|---|---|
| MCH-01 | Machinery register Maintain a machine and component register with the identifier, machine type, location, tracked component, usage unit, and configured service rule, so every reading and service action links to a defined asset. | Pleximod |
| MCH-02 | Usage readings Record entered usage readings against a machine or component with reading date and responsible user, and present usage since service, the configured service limit, and the remaining service allowance. | Pleximod |
| MCH-03 | Service and replacement records Record a service or component replacement with its action date, reading at action, responsible user, and availability after the action, restarting only the relevant service counter. | Pleximod |
| MCH-04 | Service history retention Retain prior service and replacement history for each machine and component, and derive maintenance state from the recorded readings against the configured reminder point and service limit. | Pleximod |
| CFG-06 | Maintenance configuration Configure per-machine and per-component service rules, maintenance units, limits, and reminder points without hard-coded universal numeric limits or commercial terms. | Pleximod |
| SAF-09 | Restricted cost and maintenance data Safeguard restricted material costs and profit data, and protect machinery and component service-history records from unauthorised change. | Pleximod |
| SAF-10 | Organisation record ownership Enforce role- and organisation-based responsibilities so a franchise user reaches only its own records and never Pleximod material costs, profit figures, or another franchise’s records. | Shared |
| APP-04 | Location coverage Support head-office, factory, and franchise locations from the start, with record ownership maintained separately for each organisation. | Franchise |
Maintenance scope rows 8 of 8 · baseline scope MCH-01 – APP-04
Colour code: Pleximod · franchise · shared master data
06Colophon of record
- Document
- Pleximod Management System
- Volume
- Software Requirements Document
- Version
- 1.4
- Prepared for
- Shanil and the Pleximod team
- Date
- 8 October 2026
- Status
- Requirements baseline for proposal preparation
Maintenance scope boundary
All machinery types and their relevant components are registered with an identifier, machine type, location, current reading, component, usage unit, service rule, and maintenance details. Each machine or component carries its own usage unit and service rule, supporting sheets, cuts, cycles, pieces, operating hours, or a calendar interval. For every registered machine or component the register shows the usage since the relevant service, the configured service limit, the remaining service allowance, and the approaching or overdue reminder state at its configured reminder point. Service and component-replacement history records the action date, the action, the component, the reading at action, the responsible user, the counter restarted, and the machine availability after the action. Only the relevant service counter restarts, and prior and lifetime service history is retained. The initial implementation uses entered readings only. Machine sensors, controller connections, automatic readings, and predictive maintenance are excluded. Where a reading is missing it is marked unknown or incomplete rather than estimated or invented.
Active proposal section 01 Context
01Context06
ScopeHead office, factory, franchise · desktop, tablet, mobile
StructureSix sections, 01–06, selected after the proposal
Pleximod recordsFranchise recordsCredit exceptionShared master data
Access code key
Five coded layers identify who owns each record and where a payment gate or credit exception applies.
Franchise records
Franchise-owned records and accepted or paid states
Credit exception
Authorised credit exceptions and incomplete-cost flags
Incomplete cost
Missing or partly entered material cost, never treated as a confirmed zero
Shared master data
Shared master data, metadata, and column captions
Proposal Index
Section 01
Context
Pleximod manufactures modular wardrobes, modular kitchens, beds, side tables, centre tables, cabinets, TV units, dressing units, luggage racks, and kettle and fridge units for residential properties, weekend villas, hotels, and hospitals.
Pleximod Management System · Software Requirements Document · Version 1.4
04 · Access Model
One network. Two money lines that never touch.
Head office, factory, and three franchise studios share one system, one customer master, and one product catalogue. What they do not share is money: Pleximod invoices its studios, and each studio invoices its own customers on its own books. The map below is the firewall.
Pleximod recordsPleximod-owned records, primary text, and primary rules
Franchise recordsFranchise-owned records and accepted or paid states
Credit exceptionAuthorised credit exceptions and incomplete-cost flags
Incomplete costMissing or partly entered material cost, never treated as a confirmed zero
Shared master dataShared master data, metadata, and column captions
Pleximod → franchiseDealer-price supply invoiced by head office to the studio. Pleximod-owned records.
Franchise → customerStudio retail invoice and customer collections. Franchise-owned records, private to head office.
Node = locationHead office, factory, and franchise studios hold separate stock records and separate owners.
Shared master dataCustomer, product, and quotation masters are common to both layers; money lines are not.
Stock movementReceipt and issue recorded per location and owner.
Partial shipmentOrder quantities released across multiple dispatches.
Installation sign-offStudio fitting followed by final customer acceptance.
Service limitMachine usage against its configured service allowance.
DSP-01 · FRN-02 · APP-04
Goods can be delivered from the factory to a franchise studio or directly to its customer’s site. Goods supplied to a franchise belong to that franchise, and its retail invoice and customer collections stay on the studio’s books — separate from Pleximod’s invoice to the studio.
Shop-floor fit-out spans residential properties, weekend villas, hotels, and hospitals. Made-to-order production covers modular wardrobes and kitchens, beds, side tables, centre tables, cabinets, TV units, dressing units, luggage racks, and kettle and fridge units.
03 · Modules
Requirement & module register
Accepted baseline requirement IDs with their owning layer, so the proposal can be audited line by line against the delivered modules.
01 Context · 03 ModulesModule register · requirements baseline v1.4 · owner coded
| Requirement ID | Module | Requirement | Owner |
|---|---|---|---|
| INV-01 | Inventory | InventoryRecord stock received and stock issued, with item, quantity, unit, date, location, transaction reference, and responsible user. | pleximod |
| QTN-04 | Quotations | QuotationsGenerate professional English quotation PDFs using Pleximod's branding. | pleximod |
| ORD-05 | Orders | OrdersRequire full payment of the applicable Pleximod invoice for normal factory dispatch; permit selected credit cases only through an authorised exception with entered credit days or due date, reason, and audit history. | pleximod |
| BIL-06 | Billing | BillingAllow entered billing discounts and the use of available credit while retaining the original amount, adjustment, final amount, and audit record. | pleximod |
| PRJ-04 | Projects | ProjectsShow Pleximod's project sales value, assigned material cost, and the difference between them for authorised head-office users. | pleximod |
| DSP-01 | Dispatch | DispatchGenerate packing lists and delivery challans linked to the order and dispatch. | pleximod |
| PRD-03 | Production | ProductionInclude a quality-check stage with photo capture and the responsible user's record. | pleximod |
| MCH-03 | Maintenance | MaintenanceRecord usage and show usage since the relevant service, the configured service limit, remaining usage where applicable, and approaching or overdue maintenance reminders. | pleximod |
| PNL-04 | Reports | ReportsClearly label order, project, and monthly reports as material-based P&L and state that labour, electricity, machine running costs, maintenance, transport, installation, rent, and other expenses are excluded. | pleximod |
| TIM-02 | Fulfilment dates | Fulfilment datesRecord actual dates and show planned versus actual progress and elapsed time between clearly named events. | pleximod |
| FRN-09 | Franchise portal | Franchise portalLet authorised franchise users create and download their own customer invoices and record customer payments and outstanding amounts. | franchise |
| APP-05 | Common application | Common applicationControl access by user role, organisation, and permitted actions. | shared |
Module registerRequirements baseline v1.4 · owner coded
INV-01pleximod
Inventory
Record stock received and stock issued, with item, quantity, unit, date, location, transaction reference, and responsible user.
QTN-04pleximod
Quotations
Generate professional English quotation PDFs using Pleximod's branding.
ORD-05pleximod
Orders
Require full payment of the applicable Pleximod invoice for normal factory dispatch; permit selected credit cases only through an authorised exception with entered credit days or due date, reason, and audit history.
BIL-06pleximod
Billing
Allow entered billing discounts and the use of available credit while retaining the original amount, adjustment, final amount, and audit record.
PRJ-04pleximod
Projects
Show Pleximod's project sales value, assigned material cost, and the difference between them for authorised head-office users.
DSP-01pleximod
Dispatch
Generate packing lists and delivery challans linked to the order and dispatch.
PRD-03pleximod
Production
Include a quality-check stage with photo capture and the responsible user's record.
MCH-03pleximod
Maintenance
Record usage and show usage since the relevant service, the configured service limit, remaining usage where applicable, and approaching or overdue maintenance reminders.
PNL-04pleximod
Reports
Clearly label order, project, and monthly reports as material-based P&L and state that labour, electricity, machine running costs, maintenance, transport, installation, rent, and other expenses are excluded.
TIM-02pleximod
Fulfilment dates
Record actual dates and show planned versus actual progress and elapsed time between clearly named events.
FRN-09franchise
Franchise portal
Let authorised franchise users create and download their own customer invoices and record customer payments and outstanding amounts.
APP-05shared
Common application
Control access by user role, organisation, and permitted actions.
12 accepted requirement IDsOwner coding: Pleximod-owned records in black, franchise-owned records in green, shared master data in grey.
Payment-Before-Dispatch Gate
One ruled object carries the rule that governs the whole factory floor: dispatch is released by payment, or by an authorised credit exception that is entered, attributed, and auditable.
ORD-05Full payment required for normal factory dispatchBR-05Credit exception requires authorisation, reason, and audit history
Factory dispatch gate · normal caseIllustrative ruled row · no live order data
Invoice amount (INR)4,86,200.00Pleximod invoice · GST applied
Paid amount (INR)0.00Balance 4,86,200.00 · not fully paid
Dispatch gate
HoldNo dispatch instruction permitted
Credit exception
Credit exceptionAuthorised by:Head Office AccountsCredit days:30Reason:Retained for the project milestoneAudit:Exception entry, authorising user, and due date retained
Normal factory dispatch requires full payment of the applicable Pleximod invoice. Selected credit cases are permitted only through an authorised exception carrying entered credit days or due date, a stated reason, and an audit record.
A credit exception does not pay the invoice. It suspends the gate for a documented period while the Pleximod-to-franchise balance remains unchanged and traceable.
HOLD — invoice not fully paid
RELEASE — invoice fully paid
CREDIT EXCEPTION — authorised by head office accounts
04Material-based P&L
Material-based P&L
Order, project, and monthly reports are labelled material-based P&L: sales value minus assigned material cost. They are not a full net-profit statement.
CalculationPNL-04
Material-based profit=Sales value − Assigned material cost
- Sales value
- Order or project sales value recorded for the Pleximod layer.
- ₹18,40,000
- Assigned material cost — estimated
- Material cost estimated when the order was accepted.
- ₹10,10,000
- Assigned material cost — actual
- Actual material cost entered against the order, including revisions.
- ₹10,62,500
- Assigned material cost — incomplete entry
- Not every material line has a cost entered, so this is not treated as a confirmed zero.
- Pending Incomplete cost
- Material-based profit — from actual cost
- Difference between sales value and the actual assigned material cost entered.
- ₹7,77,500 Excludes incomplete lines
Not included in this reportPNL-04
- Labour
- Electricity
- Machine running costs
- Maintenance
- Transport
- Installation
- Rent
- Other expenses
These expense categories are outside the material-based P&L scope.
Order and project reports
Show sales value minus material costs, comparing estimated and actual material costs, and flag incomplete cost entry rather than reading it as a confirmed zero.
Pleximod totals
Franchise retail invoices and franchise customer payments are private to the issuing franchise and are not counted in Pleximod’s totals.
05 Phases
Delivery phase plan
Module priorities and delivery milestones are selected after the proposal is agreed. Each phase identifies the requirements it includes and the acceptance criteria that apply to them.
Delivery planning boundaryEach phase identifies its included requirements and the applicable acceptance criteria; phase selection is confirmed with the proposal, not by this baseline.Pleximod Management System · Software Requirements Document · Version 1.4
Document of record
- Document
- Pleximod Management System
- Type
- Software Requirements Document
- Version
- 1.4
- Prepared for
- Shanil and the Pleximod team
- Date
- 8 October 2026
- Status
- Requirements baseline for proposal preparation
Project pleximod-management-proposal, prepared from requirements baseline v1.4 for head office, factory, and franchise users.
No comments yet. Be the first!