ideci

Category: News

  • On Systems Architecture Principles & Practices

    On Systems Architecture Principles & Practices

    Attended a INCOSE seminar yesterday, on systems architecture. James N Martin shared his wealth of knowledge and experience in aerospace system development.

    New insights I’ve learned:

    • systems architecting is even less known than systems engineering
    • architecting is not only about the technical system
    • environmental, political, social, economical requirements also impact architectural design
    • architecture provides the bridge between  a company’s mission and the products it delivers
    • enterprise architecture provides a ‘framework’ that constrains the solution space
    • system architecture provides a ‘framework’ that constrains and supports the engineering solution
    • models are needed to develop system architecture
    • there are many ways (views) to look at system architecture, all serving different purposes

    I also noticed that there are quite a few concepts that came across from software development where system architecture and modelling (e.g. using UML) is more established.

    Modelling (e.g. using SysML) is being promoted within systems engineering as the way to go. Now if your working for NASA like companies like James does, you might be granted the time, budget and people to pull this off. But in many other cases it might be very difficult to find and convince sponsors within your company to get this going. Especially since it requires a strategic, long term view plus persistence to reap the benefits.

    If you believe in, or can no longer deny, the digitization trend, the only way to go forward is to model whatever product you deliver. Read my posts on that subject: your Company s next Top Model

    Alltogether: Systems Architecting is not new but only very few companies are aware of this aspect of system development. Of course all existing systems do have architecture, and it has emerged and evolved in a gradual manner. But next time when you consider your ‘next generation’, ‘new platform’, ‘extended product range’, it might be a good idea be more aware of what needs actually drive and shape the solution you want to offer to your customers.  Systems Architecting does exactly that.

    Want to learn more about Systems Engineering? Check out the Systems Engineering Concept.

  • 14 JUNI: DUTCH SYSTEMS ARCHITECTING CONFERENCE

    14 JUNI: DUTCH SYSTEMS ARCHITECTING CONFERENCE

    The first edition of the Dutch System Architecting Conference will be held at the Verkadefabriek in ‘s-Hertogenbosch, the Netherlands, on 14 June 2018. Through an inspiring programme, this all-event will bring together system architects to share successful and failed development cases.

    Keynote speaker: Henrik Balslev will explain why “it’s all about creating a common language”

    First System Architecting Conference web site
  • What’s in a name?

    What’s in a name?

    [av_heading tag=’h3′ padding=’10’ heading=’What’s in a name’ color=’custom-color-heading’ style=’blockquote modern-quote modern-centered’ custom_font=’#4fafdb’ size=’50’ subheading_active=” subheading_size=’15’ custom_class=” admin_preview_bg=” av-desktop-hide=” av-medium-hide=” av-small-hide=” av-mini-hide=” av-medium-font-size-title=” av-small-font-size-title=” av-mini-font-size-title=” av-medium-font-size=” av-small-font-size=” av-mini-font-size=”][/av_heading]

    [av_hr class=’default’ height=’50’ shadow=’no-shadow’ position=’center’ custom_border=’av-border-thin’ custom_width=’50px’ custom_border_color=” custom_margin_top=’30px’ custom_margin_bottom=’30px’ icon_select=’yes’ custom_icon_color=” icon=’ue808′]

    [av_image src=’http://ideci.nl/wp-content/uploads/2018/03/700×180-New-logo-en-naam-source.png’ attachment=’1146′ attachment_size=’full’ align=’center’ animation=’no-animation’ styling=” hover=’av-hover-grow’ link=” target=” caption=” font_size=” appearance=” overlay_opacity=’0.4′ overlay_color=’#000000′ overlay_text_color=’#ffffff’][/av_image]

    [av_textblock size=” font_color=” color=”]
    Well… it depends on what you see…

    i.d.e.c.i stands for “inter disciplinary engineering consultancy and integration”. You might think that it’s a bit too much of a name … , and you’re right about that. On the other hand it is what I do: bridging the gaps between technical engineering disciplines.

    The company logo reflects how I look at these matters:

    • the blue circle represents the mechanical discipline
    • the red circle represents the electrical discipline
    • the yellow circle represents the software discipline

    As you can see, they are overlapping and interlocked. The green circle is where it all comes together; the function, where technology serves humanity…and your customer pays for.

    Another way to look at it is:

    • the blue circle represents the product your company designs, produces, services and sells
    • the red circle represents the people within your company and all of their knowledge
    • the yellow circle represents the process that creates value for your company

    As you can see, they are overlapping and interlocked. The green circle is where it all comes together; the customer’s perception of product value, where technology serves humanity…and your customer pays for.

    The ‘eye’ is where it starts:

    “change the way you look at things, and the things you look at will change”

    So take another good look at that name, take a few steps back, change your perspective, pinch your eyes … and read again … maybe you’ll see a new idea … in ideci.

    If you need any help with that, just let me know; http://ideci.nl/contact/
    [/av_textblock]

    [av_social_share title=’Share this entry’ style=” buttons=” share_facebook=” share_twitter=” share_pinterest=” share_gplus=” share_reddit=” share_linkedin=” share_tumblr=” share_vk=” share_mail=” av-desktop-hide=” av-medium-hide=” av-small-hide=” av-mini-hide=”]