A MANAGEMENT INFORMATION SYSTEM IS AN ORGANISED SET OF PEOPLE, PROCEDURES AND TECHNOLOGY THAT COLLECTS, PROCESSES, STORES AND DISTRIBUTES INFORMATION TO SUPPORT DECISION-MAKING, COORDINATION AND CONTROL. THE DISTINCTION THAT DEFINES THE SUBJECT: DATA are raw facts — "450 bags of cement issued". INFORMATION is data PROCESSED INTO A FORM THAT SUPPORTS A DECISION — "cement consumption is 12% above the estimate for the concrete poured to date". KNOWLEDGE is information combined with experience and judgement — "that overconsumption pattern usually means wastage at the mixing platform, not theft". AN MIS THAT DELIVERS DATA RATHER THAN INFORMATION HAS FAILED EVEN IF EVERY FIGURE IN IT IS CORRECT. THE COMPONENTS: PEOPLE — users, data entry staff, analysts, the managers who act. THE MOST OFTEN NEGLECTED COMPONENT, and the one that determines whether the system is used. PROCEDURES — how data is captured, validated, processed and reported; who is responsible for each step. DATA — the stored records and the database. HARDWARE AND SOFTWARE. NETWORK — the connectivity that makes it accessible from site. THE PYRAMID OF SYSTEMS, by management level — a standard examinable classification: ┌─────────────────────────────────┐ │ EIS — Executive Information │ STRATEGIC │ highly summarised, external, │ (top management) │ trend and exception oriented │ ├─────────────────────────────────┤ │ DSS — Decision Support System │ TACTICAL │ models, what-if analysis, │ (middle management) │ semi-structured decisions │ ├─────────────────────────────────┤ │ MIS — routine periodic reports │ MANAGEMENT CONTROL │ summaries, variances │ ├─────────────────────────────────┤ │ TPS — Transaction Processing │ OPERATIONAL │ every invoice, delivery note, │ (supervisors) │ timesheet, measurement │ └─────────────────────────────────┘ THE INFORMATION FLOWS UPWARD AND IS COMPRESSED AT EACH LEVEL. A site supervisor needs every delivery note; a director needs one line saying whether procurement is on plan. THE SAME UNDERLYING TRANSACTION APPEARS AT EVERY LEVEL, AT DIFFERENT RESOLUTION. ── PROJECT MANAGEMENT INFORMATION SYSTEM (PMIS) ──────────── The project-specific instance, covering: · SCHEDULE — network, Gantt, progress, critical path · COST — budget, commitments, actuals, earned value, cash flow · RESOURCES — labour, plant, materials, availability · PROCUREMENT — tenders, contracts, orders, deliveries · QUALITY — inspection records, non-conformances, test results · DOCUMENTS — drawings with REVISION CONTROL, specifications, correspondence · RISK — the register, with status and owners · HSE — incidents, near misses, inspections · CHANGE — the change log and its approvals THE ESSENTIAL FEATURE IS INTEGRATION: the same physical progress figure should drive the schedule update, the earned value calculation and the payment certificate. WHERE THESE ARE SEPARATE SYSTEMS THEY DIVERGE, and reconciling them consumes more effort than maintaining them would have.

THE QUALITIES OF USEFUL INFORMATION — the standard list, and each one is a way an MIS can fail: RELEVANT to the decision at hand ACCURATE — but note the trade-off with timeliness TIMELY available while action is still possible COMPLETE nothing material omitted CONCISE summarised to the level of the recipient CONSISTENT comparable between periods ACCESSIBLE reaching the person who must act COST-EFFECTIVE worth more than it costs to produce THE ACCURACY-TIMELINESS TENSION IS THE REAL DESIGN PROBLEM: A ROUGH FIGURE TODAY IS USUALLY WORTH MORE THAN AN EXACT ONE NEXT MONTH, because the decision it informs will have been made either way. Insisting on perfect data is a common way to make a reporting system useless. ── THE REPORTING HIERARCHY ───────────────────────────────── DAILY — site diary, labour and plant returns, weather, progress, incidents WEEKLY — progress against programme, look-ahead, issues MONTHLY — the formal report: physical and financial progress, earned value, cash flow, risks, changes, safety, forecast completion EXCEPTION — issued immediately when a threshold is breached, regardless of the calendar MILESTONE — at defined gates MANAGEMENT BY EXCEPTION IS THE ORGANISING PRINCIPLE: report routinely on what has DEVIATED beyond a defined tolerance, not on everything. It respects the scarcest resource in any project, which is senior attention. ── THE DASHBOARD ─────────────────────────────────────────── A single screen of KEY PERFORMANCE INDICATORS, typically: SPI and CPI · % physical completion · cash flow against the S-curve · open high-severity risks · safety incidents · outstanding changes · forecast completion date DESIGN RULE: EVERY INDICATOR MUST BE ATTACHED TO A DECISION SOMEONE CAN TAKE. An indicator nobody acts on is decoration, and it dilutes attention from the ones that matter. ── WHY MIS IMPLEMENTATIONS FAIL ──────────────────────────── 1. GARBAGE IN, GARBAGE OUT. The system is only as good as the site data entered into it, and site staff have every incentive to report optimistically. THE DATA QUALITY PROBLEM IS ORGANISATIONAL, NOT TECHNICAL, and no software solves it. 2. INFORMATION OVERLOAD — reports too long to read. 3. LATE DATA — accurate reports arriving after the decision point. 4. NO ONE ACTS ON IT. Reports produced, filed and ignored. IF NOTHING EVER CHANGES BECAUSE OF A REPORT, THE REPORT SHOULD BE DISCONTINUED — and saying so is a defensible exam answer. 5. RESISTANCE FROM USERS who see it as surveillance rather than support, particularly when it exposes their own variances. 6. OVER-ENGINEERING — a system requiring more effort to feed than the project can spare. On a small project a spreadsheet honestly maintained beats an enterprise package badly maintained. 7. NO INTEGRATION — separate schedule, cost and procurement systems that disagree with one another. ── IN THE NEPALI CONTEXT ─────────────────────────────────── · The government's LINE MINISTRY BUDGETARY INFORMATION SYSTEM (LMBIS) and the Treasury Single Account system handle budget and expenditure. · The PUBLIC PROCUREMENT MONITORING OFFICE operates the e-GP (ELECTRONIC GOVERNMENT PROCUREMENT) portal, through which public tenders are now issued and submitted — a genuine reduction in the opportunity for collusion at the bid-submission stage. · Practical constraints remain real: connectivity at remote sites, power reliability, and the availability of trained staff. A SYSTEM DESIGN THAT ASSUMES CONTINUOUS CONNECTIVITY WILL NOT WORK ON A HIGH-ALTITUDE CONSTRUCTION SITE, and offline capture with periodic synchronisation is the realistic pattern.