Assign clear ownership for each element of ledger integration with existing systems across the functions involved.
Designing Strategies to Integrate Distributed Ledgers with Existing Systems
Practical training in ledger integration with existing systems, grounded in real cases and applied to your own operation.
📍 Tunis🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Systems supporting ledger integration with existing systems fail in ways that are obvious afterwards and invisible before. Security and delivery speed are traded against each other in existing systems whether or not anyone says so. The result is the confidence to make and defend decisions about this part of technology and systems delivery under scrutiny. Discussion is anchored to worked examples of ledger integration with existing systems rather than to abstract argument. Post-incident reviews keep identifying weaknesses in this aspect of technology and systems delivery that were visible long before the incident. Buying a tool rarely fixes existing systems; the underlying capability has to be built internally first. Participants leave with a method for ledger integration with existing systems, not a set of opinions about it. The level assumes working familiarity with the technical platform but no prior formal training in existing systems. It ends with a prioritised list of changes to the technology and systems delivery discipline that the participant is prepared to defend internally.
Expected Learning Outcomes
Test the organisation's response to existing systems under conditions that are less than ideal.
Assess and manage third-party and cloud dependencies in ledger integration with existing systems.
Apply data protection and retention requirements within existing systems.
Build the deployment pipeline for ledger integration with existing systems so releases are routine rather than events.
Plan the migration or decommissioning of legacy components in existing systems.
Define the scope and boundaries of ledger integration with existing systems so that responsibility for it is unambiguous.
Who Should Attend
Project managers delivering changes to ledger integration with existing systems.
IT governance and audit staff reviewing existing systems.
Service desk and support leads handling incidents in ledger integration with existing systems.
Training and development staff building internal capability in existing systems.
Network and communications engineers supporting ledger integration with existing systems.
Officers preparing reports on existing systems for boards or oversight committees.
Course Modules
Ledger integration with existing systems: documentation, support and handover
2 sessions · 8 pointsSession 1Documenting ledger integration with existing systems so someone else can operate it
- Measure current load on ledger integration with existing systems and project it forward twelve months.
- Remove steps in existing systems that add effort without adding assurance.
- Benchmark the organisation's ledger integration with existing systems against comparable operations.
- Identify the data already collected that bears on existing systems.
Session 2Comparing existing systems with recognised practice
- Restore a backup of ledger integration with existing systems in a test environment and time it.
- Compare the cost of existing systems with the cost of its absence.
- Configure alerting on ledger integration with existing systems that reflects what users experience.
- Define incident severity levels for existing systems and the response each triggers.
Existing systems: capacity, performance and load
2 sessions · 8 pointsSession 1Running an incident on existing systems calmly
- Estimate the resource ledger integration with existing systems requires to run as designed.
- Plan the sequence in which improvements to existing systems will be introduced.
- Draft the minimum viable technical standard for ledger integration with existing systems.
- Rank the weaknesses in existing systems by consequence rather than by ease of fixing.
Session 2Least privilege in existing systems without blocking the work
- Assess the exit route from any cloud or vendor dependency in ledger integration with existing systems.
- Define the trigger that would require existing systems to be redesigned.
- Confirm the support model and escalation path for ledger integration with existing systems.
- Review logging on existing systems for coverage and retention.
Existing systems: build, pipeline and release discipline
2 sessions · 8 pointsSession 1Reading the current state of existing systems honestly
- Name a single owner for each element of ledger integration with existing systems.
- State the availability and recovery objectives for existing systems as numbers.
- Review whether ledger integration with existing systems is aligned with the objectives of the technical platform.
- Document the runbook for existing systems to the level a new engineer could use.
Session 2Proving the backup of ledger integration with existing systems by restoring it
- Run a load test on ledger integration with existing systems at expected peak plus a margin.
- Apply change control to existing systems including emergency changes.
- Review access rights on ledger integration with existing systems and remove what is no longer needed.
- Establish what evidence demonstrates existing systems is under control.
Existing systems: incident response and severity
2 sessions · 8 pointsSession 1Making releases of existing systems routine instead of risky
- Inventory third-party dependencies inside ledger integration with existing systems and their update status.
- Identify single points of dependency in existing systems and reduce them.
- Collect evidence on the present handling of ledger integration with existing systems before proposing changes.
- Rehearse the briefing on existing systems that would follow an incident.
Session 2Keeping existing systems alive after the initial push
- Set delivery and reliability indicators for ledger integration with existing systems the team trusts.
- Plan the decommissioning of the legacy component existing systems replaces.
- Confirm that those complying with ledger integration with existing systems understand why it exists.
- Confirm every release of existing systems can be rolled back within a defined time.
Choose the package that suits you
Silver Package
At least 3 people
USD1,250
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Gold Package
At least 3 people
USD1,850
- 5-night stay in a 5-star hotel
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Complete your registration
We will contact you within one business day to confirm.