Skip to main content

Technical Standardisation

  • Chapter
  • First Online:
Strategic IT Management
  • 2869 Accesses

Abstract

Technical standardisation is what sets out the enterprise-specific standards which frame the development trajectory for your IT landscape. Even if the landscape you have at present is a heterogeneous patchwork, you can gradually usher it toward your vision by defining which technical standards are to apply in projects and maintenance measures (see Fig. 5.1).

If you want to build a ship, don't drum up the men to gather wood, divide the work and give orders. Instead, teach them to yearn for the vast and endless sea.

Antoine de Saint-Exupéry

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 54.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    Also termed standardisation status.

  2. 2.

    Conditions should be formulated in text form, e.g. “For use in sales support business segment only”.

  3. 3.

    Released only in exceptional cases; separate authorisation is required in each case.

  4. 4.

    Also termed “phase-out”.

  5. 5.

    For example when there are different technical standards at different enterprise locations.

  6. 6.

    Object Relational.

  7. 7.

    One-off costs for producing the technical standard, including items such as licensing costs plus ongoing cost such as for maintenance, training or support.

  8. 8.

    Whatever authority the board has, its scope for taking investment decisions will usually be substantially restricted.

  9. 9.

    Such as homogenisation of operating locations by merging data centers.

  10. 10.

    Possibly customized for your enterprise.

  11. 11.

    For example maintenance contracts.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Inge Hanschke .

Rights and permissions

Reprints and permissions

Copyright information

© 2010 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Hanschke, I. (2010). Technical Standardisation. In: Strategic IT Management. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-05034-3_5

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-05034-3_5

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-05033-6

  • Online ISBN: 978-3-642-05034-3

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics