Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.

Guiding Principles for Technology Backplane Delivery Template

From MIKE2.0 Methodology

Jump to: navigation, search
This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.

Guiding Principles for Technology Backplane Delivery provide the following benefits:

  • Provide a clear linkage to business priorities
  • Guide the technology organisation
  • Facilitate communication of initiatives to business users
  • Help to simplify decision-making processes
  • Define best practices for implementation
  • These principles should be referred to throughout the implementation programme as they provide an overall guide for the implementation teams


Example for sample IT Guiding principles

Typical IT Guiding principles are listed below. For additional examples, refer to Guiding Principle samples.

  • Support a single Enterprise Wide Technical Architecture to the degree possible.
  • IT projects are to be consistent with the Enterprise Architecture.
  • Make an informed buy versus lease versus build decision before proceeding with any new development project.
  • Give preference to Open Source or End User Source solutions if functionality meets minimum requirements.
  • Keep current with emerging technologies and their applicability to enterprise architecture. * * Systems must be real-time or as close to real-time as possible.
  • Systems must be operational 24/7 or as close to this goal as possible. Four hours of downtime per week for unavoidable processing and maintenance is upper limit.
  • Manage information and data as enterprise-wide assets.
  • Reduce duplicate information systems. Data should only be collected once, electronically within a single interface, shared across systems.
  • Reduce duplicate databases and tables within databases. Data should be normalized, eliminating redundant data tables where possible. All tables that contain personal or regulated data must be secured, audited and all access logged for forensics.
  • Validate data as close to its source as possible.
  • Data shall be made available to individuals and applications from a single, authorized data source that utilizes consistent data definitions and business rules.
  • Enhance the ability to capitalize on and exploit business information; promote decision support technology.
  • Separate transactional processing systems from decision support systems per data warehousing model.
  • Technical architecture must be extensible and scalable. Possible changes must be designed for.
  • Reduce integration complexity.
  • Require shorter development cycle times.
  • Maximize infrastructure asset reuse.
  • Systems will support a limited number of hardware, software, and network choices consistent with product life cycle standards.
  • Sustain reliable connectivity.
  • Use appropriate middleware. For example, email should not be relied on for notifications or approvals. A Workflow design pattern and infrastructure must be used instead.
  • Reduce total cost of operation (TCO).
  • Customer perception is a measure of the quality of the automation processes.

Example for sample Conceptual Architecture principles

Optimize for the Enterprise


All products, solutions, tools, designs, applications, and methods used within the architecture shall be selected with the purpose of reducing complexity of the technology architecture, which should be optimized to provide the greatest benefit to the state as a whole, meaning that optimization should be end-to-end


  • Promotes information sharing
  • Reduces duplication
  • Lowers maintenance and training costs
  • Optimizes for total Return on Investment (ROI)
  • Minimizes platform configurations
  • Utilizes standard technology
  • Increases shared knowledge base
  • Creates clear migration path for future investments

Utilize Standard Technologies


Information technology solutions will use industry standard, main-stream technologies that will facilitate interoperation across the enterprise.


  • Ensures interoperability of agency-level solutions
  • Creates a shared knowledge base across the enterprise
  • Reduces risk
  • Promotes more efficient interagency collaboration
  • Strengthens enterprise security and reliability

Create Customer-Centric Services


All products, solutions, tools, designs, applications, and methods used within the architecture shall be designed to simplify customers interaction with state government.


  • Makes government more accessible
  • Promotes “one-stop-shopping” for services
  • Reduces confusion
  • Increases efficiency of government and effectiveness of its


Ensure Business Continuity


All products, solutions, tools, designs, applications, and methods used within the architecture shall take into consideration risk management and business continuity.


  • Critical systems will continue to function in the case of a


  • Data/information will remain in tact
  • Customers will continue to receive needed services

Secure the Enterprise


All products, solutions, tools, designs, applications, and methods used within the architecture must be implemented in adherence with all security, confidentiality, and privacy policies and statutes.


  • Ensures proper authorization and access
  • Maintains data, information, and system integrity
  • Ensures public trust
  • Mitigates risk
Wiki Contributors
Collapse Expand Close