BIQ01 - What is the official project or programme name, who is the sponsoring organisation, and who is the accountable executive contact?
The project is the National Mining License Monitoring System (NMLMS), presented in the ProjectInfo export as National Licence Monitoring. The Government of Nigeria is the project owner and key beneficiary, with relevant ministries including mining, environment, and finance. The accountable executive contact is not yet specified.
BIQ02 - What strategic need or business problem is the project intended to address?
The project addresses weaknesses in monitoring exploration and mining licence holders in Nigeria. These weaknesses include underutilisation of resources, non-compliance with environmental standards, reduced transparency, and loss of revenue.
BIQ03 - What are the principal project objectives, and how will success be measured?
The principal objectives are to create a centralised digital monitoring platform, collect and analyse data on mining activity, improve regulatory and environmental compliance, optimise revenue generation, and build user capacity. Success will be demonstrated through real-time tracking, more accurate reporting of production and royalties, better compliance evidence, and trained government and stakeholder users. Formal success measures are not yet defined.
BIQ04 - What is included within the approved scope, and what is explicitly excluded?
The approved scope includes system design and development, web and mobile monitoring applications, integration with existing databases and systems, pilot testing in key mining regions, nationwide rollout, stakeholder training, and ongoing monitoring and improvement. Explicit exclusions are not yet listed.
BIQ05 - What lifecycle stage is the project currently in, and what are the next formal decision or approval gates?
The project is presented as a proposed project and PHC deployment approach rather than as an already confirmed active delivery stage. The planned lifecycle moves from system design through nationwide rollout and continuous improvement. Formal approval gates are not yet specified.
BIQ06 - What governance structure applies, including boards, delegated authorities, decision rights and escalation routes?
The governance approach places PHC at the NMLMS national level and at individual mining licence-holder level, with integration between those implementations. PHC consultants, stakeholders, regulators, and licence holders all have governance roles. Formal boards, delegated authorities, decision rights, and escalation routes are not yet defined in detail.
BIQ07 - Which legal, regulatory, contractual, safety, security or policy obligations most strongly shape the project?
The project is shaped by mining-sector regulatory and environmental obligations, including compliance with the Nigerian Minerals and Mining Act and environmental regulations. Transparency, compliance, governance, and data sharing across stakeholders are core requirements.
BIQ08 - What are the most important assumptions, constraints and external dependencies?
Important assumptions and dependencies include stakeholder alignment, access to licence-holder activity data, integration with existing databases and systems, cooperation from mining licence holders, and government adoption of the monitoring framework. PHC adoption by licence holders is assumed as part of the governance model, but the mandate itself is not yet confirmed as approved.
BIQ09 - What approved baselines currently exist for scope, schedule, cost, risk and benefits, and when were they last reviewed?
Proposed scope, schedule, cost ranges, and expected benefits exist. Approved baselines for scope, schedule, cost, risk, or benefits, and the dates of any baseline reviews, are not yet identified.
BIQ10 - What are the three most important decisions or control improvements required in the next 90 days?
The three most important near-term control priorities are to confirm the governance and monitoring framework, define integration and data-sharing protocols for licence holders and existing systems, and clarify cost, funding, risk, and stakeholder responsibilities before deployment.
PSQ01 - What delivery model is proposed, and how is the programme divided into workstreams, projects or major packages?
The project uses a phased delivery model: system design and development, pilot testing and deployment, nationwide rollout and training, and continuous monitoring and improvement. The PHC service model adds a 3-month setup phase followed by 12+ months of full deployment and continuation.
PSQ02 - What are the principal deliverables, and what acceptance criteria will demonstrate that each is complete and fit for purpose?
Principal deliverables include the central monitoring platform, web and mobile applications, integrations with existing databases and systems, pilot deployment outputs, nationwide rollout, training programmes, PHC monitoring tools, governance templates, periodic PHC reports, and post-implementation review material. Acceptance criteria are not yet formally defined.
PSQ03 - What are the key milestones, schedule drivers and current critical or near-critical paths?
Indicative schedule phases are 6-8 months for design and development, 4-6 months for pilot testing and deployment, 6-8 months for nationwide rollout and training, followed by ongoing monitoring and improvement. The total duration is estimated at 18-24 months. Critical paths are not yet identified.
PSQ04 - How are risks and opportunities identified, assessed, quantified, owned, treated and escalated?
Risk identification and mitigation planning are included during setup, with particular attention to data-sharing discrepancies and compliance challenges. Real-time problem resolution is intended to use PHC decision-making methods. Detailed risk assessment, ownership, quantification, and escalation processes are not yet specified.
PSQ05 - How are scope, design, schedule, cost and organisational changes proposed, assessed, approved and incorporated into the baseline?
A formal change-control process for scope, design, schedule, cost, or organisational changes is not yet described. Pilot testing should lead to iterative improvements based on feedback.
PSQ06 - What assurance reviews, stage gates, peer reviews or independent challenges are required, and who has authority to accept the findings?
The assurance approach includes ongoing monitoring and evaluation, periodic PHC reports, and a comprehensive post-implementation review. Independent assurance reviews, formal stage gates, peer reviews, and acceptance authorities are not yet defined.
PSQ07 - How will quality requirements, verification, validation, inspection, testing and non-conformance be controlled?
Quality control is not yet described as a separate management process. Verification will rely on pilot testing, iterative improvement from feedback, continuous data collection and analysis, and ongoing monitoring of compliance and system performance.
PSQ08 - What are the most important technical, organisational and contractual interfaces, and how are they managed?
Important interfaces include the national NMLMS platform, individual mining licence-holder PHC services, mining companies, government ministries, environmental regulatory bodies, local communities, industry representatives, existing databases and systems, and PHC consultants. Integration protocols need to be established, and detailed interface-management procedures are not yet defined.
PSQ09 - What procurement and supply-chain strategy applies, particularly for specialist, long-lead or safety-significant items?
A procurement or supply-chain strategy is not yet defined. Relevant cost areas include PHC service costs, cloud/data storage costs, training, travel/logistics, risk management, and other costs that remain to be determined.
PSQ10 - How will commissioning, handover, operational readiness and benefits realisation be planned and evidenced?
Nationwide rollout and training will be followed by continuous monitoring and improvement. Post-implementation support should include comprehensive review, lessons learned, and recommendations for system enhancement. Detailed commissioning, handover, operational readiness, and benefits-realisation evidence is not yet specified.
PEQ01 - Which systems are the authoritative sources for scope, schedule, cost, risk, actions, changes, documents and evidence?
The central digital monitoring platform and NMLMS-level PHC platform are intended sources for monitoring, reporting, and governance information. The project also depends on integration with existing databases and systems. Authoritative systems for scope, schedule, cost, risk, actions, changes, documents, and evidence are not yet named.
PEQ02 - How are documents numbered, reviewed, approved, revised, distributed, retained and withdrawn from use?
Document numbering, review, approval, revision, distribution, retention, and withdrawal rules are not yet specified.
PEQ03 - What evidence is required to substantiate reported progress, completed actions, accepted deliverables and closed risks or concerns?
Required evidence should include data on operational status, production levels, environmental impact, licence-holder compliance, data shared by individual PHC implementations, and periodic PHC reports. A formal evidence standard for completed actions, accepted deliverables, or closed risks is not yet defined.
PEQ04 - How are configuration, version and baseline changes controlled so that teams know which information is current?
Configuration, version, and baseline change-control arrangements are not yet described.
PEQ05 - What data-quality rules apply, and who is responsible for checking completeness, consistency, timeliness and accuracy?
The project depends on consistent and reliable data reporting across licence holders. Improved data accuracy and availability are intended benefits, and data-sharing discrepancies are a known risk. Detailed data-quality rules and named data owners are not yet defined.
PEQ06 - How are confidentiality, security classification, access permissions and personal or commercially sensitive information managed?
Confidentiality, security classification, access permissions, privacy, and commercial sensitivity controls are not yet specified. Wider workforce access is expected through browser-based username/password access, with a proprietary database providing limited seats for the PHC team and selected stakeholder staff.
PEQ07 - What reporting cycle is used, which dashboards or reports are produced, and who relies on each output for decisions?
Reporting will include ongoing monitoring, periodic PHC reports aggregating data from licence holders, and real-time reporting supported by cloud services and data storage. The reporting cycle, dashboard catalogue, and decision owners for each report are not yet defined.
PEQ08 - How are schedule, cost, risk, actions, changes, decisions and evidence linked so that impacts can be traced across the programme?
The traceability model for linking schedule, cost, risk, actions, changes, decisions, and evidence is not yet specified. Individual PHC implementations should integrate with the national PHC platform to improve data sharing and decision-making.
PEQ09 - What backup, disaster-recovery, cyber-resilience and business-continuity arrangements protect project information?
Backup, disaster recovery, cyber resilience, and business continuity arrangements are not yet described.
PEQ10 - What current information gaps, duplicated systems or manual workarounds create the greatest control risk?
The greatest likely control risks are fragmented or inconsistent licence-holder data, discrepancies in data sharing, compliance challenges, and integration with existing databases and systems. Current duplicated systems and manual workarounds are not yet identified.
PQ01 - Who holds the principal accountable roles, and what are their responsibilities and delegated authorities?
The Government of Nigeria is the project owner and key beneficiary. Mining licence holders are accountable for their own compliance through PHC adoption. Order Efficiency Ltd provides the PHC Service. Technical development teams are responsible for system design and deployment, and PHC consultants support strategy, analysis, administration, integration, and governance. Named accountable individuals and delegated authorities are not yet provided.
PQ02 - What organisation structure is currently in place, and which key posts are vacant, interim, duplicated or unclear?
The organisation structure includes government ministries, mining licence holders, technical development teams, environmental regulators, local communities, industry representatives, PHC consultants, and trainees. A formal organisation chart and details of vacant, interim, duplicated, or unclear posts are not yet provided.
PQ03 - What capabilities and experience are essential for the current phase, and where are the most significant gaps?
Essential capabilities include digital platform development, integration with existing systems, mining-sector regulatory compliance, environmental monitoring, data collection and analysis, governance, reporting, stakeholder engagement, and training. Current capability gaps are not yet assessed.
PQ04 - What resource plan exists, including mobilisation dates, demand peaks, scarce skills and reliance on contractors or secondees?
A detailed resource plan is not yet provided. Each PHC deployment may engage up to 20 trainees, with 3 trainees costed during setup and 20 trainees costed during continuation if the trainee option is used.
PQ05 - How are contractors, consultants, delivery partners and suppliers selected, instructed, supervised and held accountable?
Order Efficiency Ltd is the PHC Service provider, and technical development teams are responsible for system design and deployment. Contractor, consultant, partner, and supplier selection, instruction, supervision, and accountability arrangements are not yet defined.
PQ06 - Which organisational interfaces are most vulnerable to gaps, duplication, delay or conflicting authority?
Potentially vulnerable interfaces include government ministries, regulators, licence holders, technical development teams, PHC consultants, local communities, and industry representatives. Particular control attention is needed around protocols to integrate individual PHC services with the NMLMS PHC platform and around data sharing and compliance risks.
PQ07 - What is the formal meeting, review and decision-making rhythm, and how are actions and decisions recorded?
A formal meeting, review, and decision-making rhythm is not yet defined. The operating rhythm should cover stakeholder alignment, ongoing monitoring and evaluation, periodic PHC reports, and post-implementation review.
PQ08 - What escalation routes and thresholds apply when safety, cost, schedule, quality, commercial or regulatory limits are threatened?
Real-time problem resolution and PHC decision-making are part of the intended operating model, but escalation thresholds for safety, cost, schedule, quality, commercial, and regulatory limits are not yet defined.
PQ09 - What workload, continuity, succession or key-person risks could weaken delivery or assurance?
Workload, continuity, succession, and key-person risks are not yet identified. Training and optional trainee engagement provide a route to develop local capacity and sustainability.
PQ10 - What behaviours, incentives or cultural factors may discourage challenge, delay escalation or distort reporting?
Behaviours, incentives, and cultural factors that could discourage challenge, delay escalation, or distort reporting are not yet assessed.
FQ01 - What funding sources, approvals and financial commitments currently support the project?
Confirmed funding sources, approvals, and financial commitments are not yet identified. Trainee costs may optionally be treated as part of a Corporate Social Responsibility budget.
FQ02 - What is the current estimate or budget, what is its basis, and what level of confidence or maturity does it have?
The estimated system development and deployment cost is $3-5 million. Training and capacity building is estimated at $500,000. Ongoing maintenance and support is estimated at $1-2 million per year. The total estimated cost is $5-7 million, excluding ongoing operational costs. Separate PHC estimates include setup costs of $61,160, continuation costs of $917,280, and cloud services/data storage of $1,900, with several other categories still undetermined. Estimate confidence or maturity is not yet stated.
FQ03 - How are the cost baseline, contingency, management reserve and quantified risk exposure established and controlled?
The cost baseline, contingency, management reserve, and quantified risk exposure are not yet defined. Risk management remains an undetermined cost category, and other costs need early definition after PHC Service start.
FQ04 - How are actual cost, commitments, accruals, forecast outturn and variance reported and reconciled?
Actual cost, commitments, accruals, forecast outturn, and variance reporting and reconciliation arrangements are not yet specified.
FQ05 - Which contract and commercial models are proposed, and where do liability, incentive or risk-allocation concerns remain?
The commercial model includes PHC Service deployment by Order Efficiency Ltd and PHC adoption by individual licence holders. Contract models, liability, incentives, and risk allocation are not yet defined.
FQ06 - What major procurement commitments or long-lead decisions must be made before full certainty is available?
Major procurement commitments and long-lead decisions are not yet listed. Platform development, integration, cloud/data storage, training, travel/logistics, and risk-management arrangements will need to be clarified.
FQ07 - What current or foreseeable changes, claims, disputes or commercial exposures could materially affect the project?
Current or foreseeable changes, claims, disputes, and commercial exposures are not yet identified.
FQ08 - How are value, affordability, whole-life cost and alternative options challenged before major commitments are approved?
A formal process for challenging value, affordability, whole-life cost, and alternative options before major commitments is not yet described.
FQ09 - What financial controls, segregation of duties, audit rights and record-keeping requirements apply?
Financial controls, segregation of duties, audit rights, and record-keeping requirements are not yet specified.
FQ10 - What affordability, cash-flow or funding thresholds could cause delay, rephasing or loss of project viability?
Affordability, cash-flow, and funding thresholds are not yet defined. Several costs remain undetermined, so early cost definition is needed before firm viability judgements.
MQ01 - Who are the principal internal and external stakeholders, and what authority, influence or exposure does each have?
Principal stakeholders include the Government of Nigeria and relevant ministries, mining licence holders, Order Efficiency Ltd, technical development teams, environmental regulatory bodies, local communities, industry representatives, PHC consultants, and trainees. Their detailed authority, influence, and exposure are not yet mapped.
MQ02 - What are the principal expectations, concerns and potential points of conflict among those stakeholders?
Likely stakeholder concerns include regulatory compliance, environmental standards, transparent data sharing, revenue optimisation, accurate reporting, and the burden on regulators. Stakeholder-specific expectations and conflict points are not yet documented.
MQ03 - What communication and engagement channels are used, and how is feedback converted into controlled actions or decisions?
Engagement will include stakeholder alignment, training, periodic PHC reports, and data sharing through integrated PHC implementations. Communication channels and the process for converting feedback into controlled actions or decisions are not yet defined.
MQ04 - How are regulatory, governmental and local-authority relationships coordinated and documented?
Government ministries and environmental regulatory bodies are core stakeholders and beneficiaries. The coordination and documentation process for regulatory, governmental, and local-authority relationships is not yet described.
MQ05 - What impacts, benefits or burdens may be experienced by communities, workers, customers and the local economy?
Expected benefits include increased government revenue, improved regulatory compliance, transparency and accountability, environmental protection, data-driven decision-making, and local capacity development through training and trainee participation. Local communities are stakeholders, but specific community burdens or local economic impacts are not yet detailed.
MQ06 - What consultation commitments, undertakings or stakeholder promises have been made, and how are they tracked?
Consultation commitments, undertakings, stakeholder promises, and tracking arrangements are not yet identified.
MQ07 - What reputational risks, misinformation or unresolved public concerns could undermine confidence in the project?
Reputational risks, misinformation, and unresolved public concerns are not yet directly assessed. Confidence risks would arise if transparency, compliance, environmental protection, or data accuracy are not achieved.
MQ08 - What information should be transparent, and what information must remain restricted for legal, commercial, privacy or security reasons?
Information suitable for transparency includes licence-holder activity, compliance, production, royalties, environmental impact, and aggregated monitoring reports. Restricted-information rules for legal, commercial, privacy, or security reasons are not yet specified.
MQ09 - How are lessons learned, stakeholder feedback and operating experience captured and incorporated into future decisions?
Post-implementation support should include comprehensive review, lessons learned, and recommendations for system enhancement. Pilot testing should also use feedback for iterative improvements.
MQ10 - What concise evidence-based update could be issued regularly to demonstrate project health without overstating certainty?
A regular evidence-based project-health update should summarise licence-holder reporting coverage, compliance status, production and royalty reporting completeness, environmental-impact monitoring, unresolved risks, data-quality issues, training progress, and decisions requiring escalation. The exact report format is not yet specified.