|
Tenders are invited for Integrated ERP/BPM Platform Scope of Work 2.1 Core Modules The proposed Integrated ERP/BPM Platform must cover, at minimum, the following functional modules. A native Business Process Management (BPM) engine is mandatory to actualize full institutional digitisation. It must be capable of modelling, executing, monitoring, and auditing cross-module business processes ensuring that no institutional record is committed until the appropriate workflow has reached an approved terminal state. Vendors must indicate in their compliance matrix whether each module is native to the platform or delivered via certified third-party integration: Human Capital Management (HCM): staff records, recruitment, on boarding, leave management, performance appraisal, disciplinary processes, payroll with CONTISS/CONUASS salary structures, and pension administration Financial Information System (FIS): general ledger, accounts payable/receivable, budgeting and budget control, procurement and purchasing, fixed asset management, and financial reporting Health Information System (HIS): student and staff clinic management, patient records, pharmacy, referrals, appointment scheduling, and health analytics Learning Management System (LMS): course delivery, e-learning content, assessments, and virtual classroom integration (Moodle LMS and BigBlueButton); vendors must specify whether LMS is native or externally integrated Student Information System (SIS): admissions, student records, course registration, grading, transcript generation, fees management, and virtual Senate Research Management System (RMS): postgraduate management, grant tracking, ethics review, publication records, and research output reporting Document Management System (DMS) / BPM Backbone: a native document and workflow engine governing all cross-module processes; no canonical record should be committed without an approved workflow terminal state; Governance, Quality Assurance & Compliance: institutional policy management, accreditation support (NUC), audit trails, and regulatory reporting Student Life & Campus Services: student portal, counselling, disciplinary processes, sports, campus events, and alumni relations Digital & ICT Services: ICT helpdesk, identity and access management (IAM), Single Sign-On (SSO), and API integration layer for third-party systems Library Management: catalogue, circulation, e-resources, and inter-library loan management 2.2 Non-Functional Requirements Native BPM/workflow engine capable of designing, executing, monitoring, and auditing multi-step, cross-module institutional processes with configurable approval chains BPM-centric architecture: all transactions and records must be governed by a document/workflow state machine before commitment to any canonical data store Cloud-native deployment on a reputable cloud platform (e.g., AWS, Azure, GCP, or equivalent), with an option for on-premise or hybrid deployment Role-based access control (RBAC) with granular permissions per module and workflow stage Strong data security, encryption at rest and in transit, and compliance with NDPR and applicable Nigerian data protection regulations Open API / RESTful integration layer for third-party systems (Paystack/Flutterwave, Termii SMS, Moodle, BigBlueButton, JAMB, NUC portals) Mobile-responsive access across all core modules Comprehensive audit trail and reporting across all modules and workflow events 3. Submission Requirements Interested vendors must submit the following: a. Cover letter introducing the company and confirming interest in the Integrated ERP/BPM Platform procurement b. Evidence of CAC registration c. Audited accounts for the last three years d. Evidence of tax compliance and VAT registration e. Affidavit confirming authenticity of submitted documents f. Evidence of relevant experience, including at least three verifiable ERP/BPM deployments, with at least one in a university or comparable tertiary institution g. Client references with contact details, specifically referencing what module deployments where applicable h. Technical proposal and implementation plan, specifying the BPM/workflow engine architecture and DMS integration approach i. Module coverage statement: a clear declaration of which modules (HCM, FIS, HIS, LMS, SIS, RMS, DMS/BPM, etc.) are native versus third-party integrations j. Training and support plan covering all proposed modules k. Compliance matrix mapped against all functional and non-functional requirements in this ITT l. Itemised cost proposal broken down by module, implementation phase, licensing, and annual maintenance 4. Submission Format & Method In alignment with the Universitys commitment to a fully paperless, digitally driven environment, all submissions shall be made exclusively through electronic means. No hard-copy submissions will be accepted at any stage of this process. Tender Link : https://etenders.com.ng/western-delta-university-oghara-delta-state-invitation-to-tender-itt-for-an-integrated-erp-bpm-platform/
|
