IT Department Network Infrastructure - 7.3 Design and Development Requirements

[JJ777]

Would this be applicable to a Networks section within an IT department. Let us assume that a network infrastructure in a building needs an upgrade or a total new building needs a network infrastructure. Do they have to follow the design and development clause 7.3.

One problem I foresee is that this is very technical and only a network specialist would know how the design would look and if it will serve the business need. Who will sign the specification to say "yes that is what I need" from the requester if they do not have any knowledge of a network infrastructure. The only want to receive e-mails and connect to the web and if I show them a drawing of severs switches bandwith specs etc. they will not know what I'm talking about.

 

[Coury Ferguson]

Re: 7.3 Design and Development

Would this be applicable to a Networks section within an IT department. Let us assume that a network infrastructure in a building needs an upgrade or a total new building needs a network infrastructure. Do they have to follow the design and development clause 7.3.

One problem I foresee is that this is very technical and only a network specialist would know how the design would look and if it will serve the business need. Who will sign the specification to say "yes that is what I need" from the requester if they do not have any knowledge of a network infrastructure. The only want to receive e-mails and connect to the web and if I show them a drawing of severs switches bandwith specs etc. they will not know what I'm talking about.

My opinion: Yes it would fall under Design and Development

Have the IT department write and/or assist in writing the procedure.

 

[alspread]

Re: 7.3 Design and Development

7.3.1 The organization shall plan and control the design and development of product.

If the network is a product, then yes.

If the network supports the organization then, no.

6.3 The organization shall determine, provide and maintain the infrastructure needed... Infrastructure includes, as applicable,... supporting services (such as transport, communication or information systems).



Good Luck

 

[Marc]

Section 7.3 is related to product and specifically addresses customer requirements (which *can* be internal customers when you think about it), but...

I think the bottom line is that any company that 'does' Network Infrastructure has to design it. A Network Infrastructure isn't a napkin back process. Whether or not it is your company's product or an internal job you will be defining inputs and outputs. I would be surprised if there isn't a design verification step early on before build (will all this work together?). I would also be surprised if there wasn't a final system validation prior to going 'live' (Does it work as expected?).

Even if it is technically not 'required' by ISO 9001 because it is not your company's 'product', it is done because 7.3 is nothing more than the basics of a design system. You may look at some relief in a few of the 7.3 sub-clauses, but none the less these are the basics.

My question is: Is there anything in section 7.3 that you are not already doing when you 'do' Network Infrastructure?

 

[alspread]

I think the bottom line is that any company that 'does' Network Infrastructure has to design it. A Network Infrastructure isn't a napkin back process.

Wouldn't/couldn't this logic apply to any large project in a company? What about a complete new HVAC system, or a new ERP/MRP software, moving from one building to another?

We're often involved with many large projects that aren't 'napkin back' that demand a lot of detail, design, and management of resources, but that doesn't put them into 7.3.



Good Luck

 

[SteelMaiden]

imho, I would say that an HVAC contractor would be responsible for design.

 

[Marc]

Wouldn't/couldn't this logic apply to any large project in a company? What about a complete new HVAC system, or a new ERP/MRP software, moving from one building to another?

We're often involved with many large projects that aren't 'napkin back' that demand a lot of detail, design, and management of resources, but that doesn't put them into 7.3.



Good Luck

Your bottom line is that the registrar's auditors won't audit that aspect of the business. I tend to agree with you. But then again, they didn't used to audit IT at all in the 'old days'. These days they do. "Tell me about your data backup plan..." isn't an unusual question. There used to be an ISO 9003 for Service companies (as far as I know no company was ever registered to it, but it did exist). That went away when the paradigm shifted from design applying only to widgets, but also to processes. Yes, service companies absolutely do design. Their product is a service which they design.

It would absolutely apply to any large project in a company. If your company does not *design* large projects, I'd be amazed. Do they do any writing of what their plan is or do workers just come in and take a look around and say "Well, OK - Let's get on with it and see what we have to do as we go along..." if they're putting in a new HVAC system? Even moving from one building to another is often a seriously thought out (designed) plan. Would you consider moving a whole plant without a plan (aka Design")?

Design is done and typically it is done in a way that 7.3 outlines, so it's a moot point. 7.3 is just the basic elements of a basic design system regardless of it being a requirement of ISO 9001.

Back when I did implementations, large and small, I did what is in my paradigm 'design'. I called it a project, but the hallmarks of design were everywhere. I drew up a project plan in MS Project. I defined inputs and outputs for each step. There were meetings to discuss the plan (design verification) where all the steps were considered. We followed the plan. Prior to the registration audit we audited the systems internally to ensure they were working as planned (design validation). We did every step in 7.3, not because it is required by ISO 9001, but because that is the essence of planning and design.

7.3.1 Design and Development Planning
7.3.2 Design and Development Inputs
7.3.3 Design and Development Outputs
7.3.4 Design and Development Review
7.3.5 Design and Development Verification
7.3.6 Design and Development Validation
7.3.7 Control of Design and Development Changes

Now - If one is going through a registration audit, for example, I doubt that the auditor is going to the in-house IT people and ask to see the design plan for the IT infrastructure. But - If it was a company I was running I'd be ready to show them just because that's the way it's done.