Corporate Procedure
No. 505.32
Date issued
August 6, 2004
Subject
Replaces issue dated
June 3, 2003
PRODUCT/SOLUTION DESIGN AND TEST
This Corporate Procedure (“Procedure”) shall be followed by Nortel Networks Corporation (“NNC”) and its subsidiaries and other controlled businesses globally, whether incorporated or unincorporated (collectively, “Nortel Networks”).
1.0 Purpose
The purpose of this Procedure is to provide the operating requirements and functional responsibilities necessary to ensure the maximum effective use of process discipline for product design and test in every phase of a product’s life cycle. This Procedure serves as a key element for implementation of Corporate Policy 700.02 – Product Design and Life Cycle Management; and Corporate Procedure 505.31 – Product Life Cycle Management.
2.0 Interpretation
The General Manager(s) of each applicable product portfolio, in coordination with the technology prime(s), are responsible for implementing this Procedure in a consistent manner that fits the needs of their business and adheres to Corporate Policy 500.04 – Quality and Customer Satisfaction.
3.0 Definitions
3.1 “Business Decision Point” is an event driven evaluation used to set common expectations on market-based goals, evaluate market
performance, consider/analyze risks, make decisions on project/product content, direction, quality, funding, schedule, and resource levels, and empower the project team to execute project plans in accordance with Nortel Networks Corporate Policies, Procedures and Standards.
3.2 “Corporate Policy” is a Nortel Networks statement of a governing principle.
3.3 “Corporate Procedure” is a Nortel Networks document governing the implementation of a Corporate Policy and related processes.
3.4 “Corporate Standard” is a Nortel Networks document used to define the requirements necessary to meet industry standards and specific Nortel Networks requirements. Corporate Standards shall be adhered to by Nortel Networks, and where applicable, by suppliers, contractors and sub-contractors. (See Corporate Policy 500.16 – Corporate Standards).
3.5 “Customer Requirements Analysis” is the initial design stage used to capture/document customer and feature requirements, establish and communicate program priorities, select primes, initiate the design project, identify commercial and operations requirements, and identify the architecture to be used for product design.
3.6 “Design Maintenance” is the final design phase in a product’s life cycle. Design changes are made and validated only to resolve service impacting conditions and/or as contracts dictate. Completion of the Design Maintenance phase shall align with the End of Life (“EOL”) Business Decision Point and associated plans to exit the market, including disposition of all related intellectual property (reference Corporate Procedure 505.31 - Product Life Cycle Management - Retirement Phase).
3.7 “Design Phase 0” is the product design phase used to define system function, begin generating the system architecture, and to capture all design considerations for commercial (sellable products, models, services, and associated pricing) and operational (order, engineer, manufacture, test, deliver, install, repair, and service) support. Dependability charactization for product/network and/or solution is identified. Performance parameters are defined, feasibility and risks documented, and partitioning of the system is completed. Product development (material, resource, etc.) and cost targets are established. Supply chain planning begins. Completion and output of this phase is an input to the Market Readiness Business Decision Point (reference Corporate Procedure 505.31 - Product Life Cycle Management - Opportunity Phase).
3.8 “Design Phase 1” is where the high level design is completed and a commitment to design delivery is made. This phase is used to select and approve, the design technology, define software and hardware architecture, complete the functional description, identify projections for performance and engineering impacts, interoperability, establish test strategy, provide administration and maintenance (alarms, diagnostics, etc.) strategy, and establish plans to update design, test, and field support tools for the associated geography targeted for product deployment. Include consideration for product models, services, pricing, and the associated requirements for ordering, engineering, manufacture, test, installation, dependability, repair, optimal human interface, accessibility (physical and remote), product safety and service. Requirements for environmental (design for environment, restriction of hazardous materials and recyclabililty performance and regulatory compliance must also be considered. Agree to financial and resource budgets per product introduction business case boundaries and establish the resource plans needed to commit delivery to the customer. Completion of Design Phase 1 shall align with the Business Readiness Business Decision Point (reference Corporate Procedure 505.31 – Product Life Cycle Management - Definition Phase).
3.9 “Design Phase 2” is the product design phase used to develop, inspect, execute and validate as much of the new and modified software code as possible. Unit and feature interaction testing should be completed in this phase. White box subsystem testing is performed for success paths, error paths, interaction between new features and existing features, and “what if” scenarios. Hardware design is documented, prototyped, and tested to ensure functional and physical requirements are met. Environmental (design for environment, restriction of hazardous materials and recyclabililty) and product safety guidelines are tested as appropriate. Design integration and system test plans are developed. System engineering impacts are updated. Design, test and field supportability tools are updated. Process work continues to satisfy commercial and operational requirements. The hardware and software design shall be improved - as needed - to eliminate defects identified during designer testing.
3.10 “Design Phase 3” is the product design phase used to perform and complete hardware and software design integration testing and ensure that all mutually impacting capabilities function appropriately together. The hardware and software design shall be improved - as needed - to eliminate defects identified during integration testing. Environmental (design for environment, restriction of hazardous materials and recyclabililty) and product safety guidelines are tested as appropriate Completion is critical to the execution and completion of product verification activities in System Test Phase 1.
3.11 “Design Support” is the design phase used to support the product once System Test Phase 3 is completed and the product is in volume production. Product performance, quality, and cost improvements are defined, validated, and implemented - as warranted - by customer response and/or business need. Periodic retesting is funded and performed to ensure system level functionality and performance continues to meet and/or exceed pre-established quality targets. Completion of the Design Support phase shall align with the End of Life Readiness (“EOLR”) Business Decision Point and associated plans to manufacture discontinue the product (reference Corporate Procedure 505.31 - Product Life Cycle Management - Production Phase).
3.12 “IPT” means Integrated Project Team and is a term used to describe a cross-functional team, chaired by a team leader, who is accountable for the success of the project to meet customer/business needs, developing/implementing portfolio project plans, and is accountable to the Portfolio Management Team throughout the duration of the project.
3.13 “Portfolio Management Team” is a decision making team, chaired by the portfolio leader (i.e. General Manager or delegate), which is accountable for portfolio strategy, resource allocation, and ongoing portfolio management/decisions relative to market timing, customer need, and business priorities. This appropriate cross-functional team is accountable for the performance of all products within the portfolio and to ensure those products are supported by an accountable IPT leader or product owner.
3.14 “System Test Phase 1” is the product/system verification phase used to finalize/execute verification test plans - inclusive of customer input, complete product verification testing, and ensure the development effort has not compromised product quality or reliability. Environmental (design for environment, restriction of hazardous materials and recyclability) and product safety guidelines are tested as appropriate. The hardware and software design shall be improved - as needed - to eliminate defects and supporting documentation is prepared for formal release.
3.15 “System Test Phase 2” is the system test phase used to finalize internal/external validation test plans (inclusive of customer input) and ensure all product test cases have been executed and quality levels attained. Large system overload limits and interoperability must be tested for intended performance. Environmental (design for environment, restriction of hazardous materials and recyclability) and product safety guidelines are tested as appropriate. Commercial and operational requirements and processes are validated. First customer/market test plans are finalized for System Test Phase 3 execution. The hardware and software design shall be improved (as needed) and supporting documentation is formally released for the first production build. These results, including all supporting budgetary considerations, will be used to determine if the product is ready for deployment and System Test Phase 3 validation. Completion of this phase shall align with the Customer Readiness Business Decision Point (reference Corporate Procedure 505.31 – Product Life Cycle Management - Implementation Phase).
3.16 “System Test Phase 3” is the system validation phase used to validate quality and performance of the formally released product in a live customer environment. Each new feature is validated (test coverage) and the in-service (soak time) target is completed. Results must indicate that the product, all planned offerings and applications, and all supporting operational processes (order, engineer, manufacture, test, deliver, install, repair, and service) are ready for volume production and general availability. Out of box product sampling is performed. The hardware and software design shall be improved (as needed), supporting documentation updated, and formally released. Completion of System Test Phase 3 shall align with the Channel Readiness Business Decision Point (reference Corporate Procedure 505.31 - Product Life Cycle Management - Deployment Phase).
4.0 Responsibility
4.1 In support of the product quality differentiation Nortel Networks is striving to achieve as a corporation, the General Manager for each product portfolio shall:
(a) Ensure accountability to the responsibilities outlined in this Procedure in support of Corporate Policy 700.02 - Product Design and Life Cycle Management.
(b) Ensure accountability to the responsibilities outlined in Corporate Procedure 505.31 - Product Life Cycle Management.
(c) Ensure process discipline in product design, test, and support is consistently applied per the framework and milestones documented in this Procedure.
(d) Establish assurance programs to ensure product design quality, performance targets, and schedule commitments are defined, progressive, and consistently measured, per the design scorecard, to demonstrate use and alignment to the framework and milestones described in this Procedure.
(e) Ensure that all aspects of product design, test, delivery, support, maintenance, and potential recovery meet applicable legal, contractual, environmental and regulatory requirements - in all applicable global markets - and intellectual property associated with said design is adequately protected.
(f) Assume responsibility for customer satisfaction and all aspects of product performance.
4.2 The Portfolio Management Team for each product portfolio shall:
(a) Ensure an effective, multi-disciplined, decision making body is in place to evaluate and qualify each of the product design and test phases (Customer Requirements Analysis through System Test Phase 3). This decision making body shall include a business, design, service, and project prime (verification, validation, trials, first office, and/or ramp).
(b) Ensure that when System Test Phase 3 is completed (in alignment with the Channel Readiness Business Decision Point – reference Corporate Procedure 505.31 – Product Life Cycle Management), all operational support elements are in place and ongoing design support requirements/responsibilities are clearly defined, transitioned as required, and appropriately funded.
(c) Ensure that when the Design Support phase is completed (as scheduled per the End of Life Readiness Business Decision Point – reference Corporate Procedure 505.31 – Product Life Cycle Management), ongoing Design Maintenance requirements/ responsibilities are clearly defined, transitioned as required, and appropriately funded.
4.3 In support of the product design and test phases (Design Phase 2 through System Test Phase 3), the decision making body, as assigned in Section 4.2, shall track, measure, and report on performance to originally committed design delivery schedules and any out of bounds conditions that may alter the schedule.
4.4 In support of each phase in the product’s life cycle (as defined in Corporate Procedure 505.31 – Product Life Cycle Management), the IPT leader (or product owner) shall:
(a) Ensure each design and test phase – and the associated exit criteria for each phase - is clearly defined and aligned to the critical product introduction phase Business Decision Points (Market through Channel Readiness – reference Corporate Procedure 505.31 - Product Life Cycle Management).
(b) Ensure external customer trials (i.e. alpha and/or beta) and associated performance results, risks, and actions are clearly aligned to the appropriate design and test phase and the higher level Customer Readiness Business Decision Point (reference Corporate Procedure 505.31 - Product Life Cycle Management).
(c) Ensure that product knowledge is transferred to all key sales, supply, and service primes - including channel partners - in support of the formal design release (reference System Test Phase 2) and any formally released changes that occur thereafter.
(d) Ensure that product design performance/quality targets are continuously monitored, met, and/or consistently improved upon - take actions as appropriate.
(e) Ensure that all design changes/improvements made during the Design Support and Design Maintenance phases are timely, cost justified, verified and validated, and implemented as needed. Track feature churn to ensure product offering remains consistent with the Channel Ready Business Decision Point (reference Corporate Procedure 505.31 - Product Life Cycle Management) commercial/design intent.
5.0 Process
5.1 To achieve a consistently high level of product quality, process discipline must be established and maintained throughout a product’s life cycle. For product introduction, this design process discipline is achieved through the initial analysis of customer requirements and a seven-phased process (4 Design/3 Test) that concludes with system validation and general availability. Each phase - as supplemented by the design scorecard - provides the checks and balances to ensure the design is captured, customer desired features are included, operational process requirements are considered, and regression, interoperability, supportability, integrity, and system overload conditions are validated.
Concurrent design is encouraged and phase activities are to be managed in parallel wherever possible. Each phase is generic enough in nature to map to other supporting design and test processes. Release over release improvement targets must be established.
For ongoing design support, consistent improvement, and customer satisfaction, the same level of design process discipline must be applied during production and maintained through the retirement phase of a product’s life cycle.
In support thereof, the following high level process framework is required to ensure consistent discipline in product design across the business.
Product Design Phases
Primary Phase Objective
Key Phase Activities
Customer Requirements Analysis
Capture and document customer and functional requirements.
(a) Initiate design project and select primes.
(b) Capture/document customer requirements.
(c) State product concept and identify the requirements and architecture to be used.
(d) Identify high level view of resources and labs required.
Design
Phase 0
Define System Architecture.
(a) Begin generation of proposed system architecture.
(b) Define system design – include high level product structure, subsystems, and functionality, alarms, diagnostics, maintenance, and performance levels.
(c) Capture all design considerations for commercial support (sellable products, models, services, and associated pricing).
(d) Identify design considerations for operational support (order, configure, procure, manufacture, integrate, test, move, installation, dependability, optimal human interface, accessibility, repair, and technical support).
(e) Establish preliminary development plan.
(f) Identify key resources and capital requirements for Product Design, development, test, and validation – include consideration for external design and supply contracts.
(g) Ensure development plan and system design can be supported by the strategy for product/solution delivery.
(h) Establish product cost and development cost (“R&D”) targets (business case input) – include for consideration items such as: commercial (sellable products, models, services, and associated prices) and operational (order, configure, procure, manufacture, integrate, test, move, install, repair and technical support requirements.
(i) Identify design considerations for legal, contractual, environmental, and regulatory requirements – give special consideration to security and import/export controls.
(k) Dependability requirements defined.
(k) Hardware and software architecture dependability analysis.
(l) System reliability block diagram.
(m) Establish and communicate program priorities.
(n) Ensure 10% Release over Release plan is established for the current release and obtain Product Line Management commitment.
(o) Establish intervals and exit criteria and align to overall Design Phase 0 completion target.
(p) Update customer requirements ensuring lead markets and customers are identified.
(q) Conduct a “Lessons Learned” exercise to identify design process improvements and preventive actions.
(r) Align phase completion and results to the Market Readiness Business Decision Point (ref. Corporate Procedure 505.31 – Product Life Cycle Management).
Design
Phase 1
Complete High Level Design and Commit to Design Delivery.
System
i. Approve System. Architecture
ii. Review design with key customers.
iii. Ensure high level design aligns with commercial requirements (sellable products, models, services, and associated pricing).
iv. Perform hardware failure analysis at block diagram level to identify risks and potential failures.
v. Update design summary to reflect commitment to delivery and product performance criteria, data schema, billing, accounting, logs, and operational measurements/stats.
vi. Establish plan for design, test, and field support tool updates.
vii. Approve selection of hardware and software technology.
viii. Identify hardware and software dependencies to maximize reuse of available technologies.
ix. Identify any export control impact related to proposed software design and hardware dependencies especially associated with the incorporation of encryption algorithms.
x. Identify design considerations for legal, contractual, environmental, intellectual property and regulatory requirements – give special consideration to security and import/export controls.
xi. Establish strategy for product test.
xii. Revise and update design and test resource plan for approval at Business Readiness Business Decision Point milestone.
xiii. Draft plan for first customer applications (Alpha, Beta, and/or formally released product).
xiv. Establish plan to achieve release over release improvements (features, processes, etc. - 10% minimum as measured by a reduction in the arrival rate of customer reported problems).
xv.Agree to financial and resource budgets – ensure compliance to business case for product introduction.
xvi. Map system design to the customer and feature requirements.
xvii. Network and Network Element Reliability Walkthrough.
Hardware
i. Review and assess risks.
ii. Develop and review design specifications.
iii. Partition product into functional blocks.
iv. Define and describe internal and external interfaces.
v. Assess in-service fault coverage and identify weaknesses, diagnostic requirements, and areas for improvement.
vi. Ensure the key elements for hardware design, test, and support are included in the plan for product/solution delivery.
vii. Identify new technology and critical components.
viii. Identify components and/or materials subject to environmental/ safety regulations
ix. Develop initial bill of material (i.e. stock list) – identify source, quality, and/or environmental risks and contingency plans.
x. Identify unique components and component qualification plan.
xi. Provide budget estimates (such as: product cost, development cost and resources, and capital requirements).
xii. Complete circuit design – perform timing simulation and analysis.
xiii. Simulate functionality and performance – document list of configurations and tools used.
xiv. Identify product integrity test requirements – establish preliminary plan.
xv. Establish hardware reliability targets.
xvii. Perform hardware failure mode analysis to identify risks and potential failures.
xvii. Identify Design for Environment requirements and complete DfE audit.
Software
i. Define features for data base tracking.
ii. Commit to feature design and delivery schedule.
iii. Forecast memory engineering impacts.
iv. Forecast real time impacts.
v. Forecast restart upgrade impacts.
vi. Forecast release to release upgrade impacts.
vii. Establish strategy for unit testing.
(a) Capture design considerations and requirements for order, configure, procure, manufacture, integration, test, installation, move, repair, dependability, optimal human interface, accessibility, and technical support – include plans for product design support.
(b) Establish intervals and exit criteria unique to the system, hardware, and software design activities within this phase – align to overall Design Phase 1 completion target.
(c) Update customer requirements ensuring lead markets and customers are identified.
(d) Conduct a “Lessons Learned” exercise to identify design process improvements and preventive actions.
(e) Align phase completion and results to the Business Readiness Business Decision Point (ref. Corporate Procedure 505.31 – Product Life Cycle Management.
Design
Phase 2
Complete hardware design implementation and designer testing. Complete software design, coding, code inspection, and unit testing.
System
i. Obtain agreement to design integration test plan.
ii. Complete customer documentation portion of the supporting design documentation.
iii. Revalidate dependencies on related hardware/ software products and functions to maximize reuse of available technologies.
iv. Finalize product test plan.
v. Continue process work to ensure commercial and operational requirements can be satisfied.
vi. Update plan to achieve release over release improvement (10% minimum arrival rate reduction in customer reported problems).
vii. Track and ensure adherence to budgeted resources and finance.
viii. Update strategy for product test.
ix. Revise and update design and test resource plan.
x. Update NPI validation plans such as: customer applications (Alpha, Beta, and/or formally released product).
xi. Obtain agreement to design integration test plan.
Hardware
i. Achieve functional agreement to ensure the design is stable and ready for layout.
ii. Achieve component placement agreement(s) to ensure all printed circuit boards can be manufactured.
iii. Achieve physical agreements to ensure the mechanical and layout designs are ready for manufacturing and test.
iv. Order and build prototypes – capture first piece evaluation for design improvements.
v. Test and debug first manufacturing built hardware (i.e. prototypes) – include power, firmware, signal quality, radio frequency, and margin performance.
vi. Execute component qualification plan.
vii. Recycle hardware design, as required, for additional prototypes, testing, and/or design integration.
viii. Update environmental and product integrity test requirements – finalize plan.
ix. Perform hardware failure mode analysis to identify risks and potential failures.
Software
i. Complete functional specification and other required elements of detailed design.
ii. Finalize unit test plan.
iii. Unit test cases captured and documented.
iv. Pass all unit test cases – document results and exceptions.
v. Identify and resolve any memory leaks and real time impacts
vi. Submit all code to the appropriate repository.
vii. Update product record status to mark completion date of unit testing.
viii. Ensure design unit test case results map to requirement documents.
ix. Software failure rate prediction as part of the dependability program.
x. Identify memory engineering, real time and overload control impacts.
xi. Forecast restart upgrade impacts.
xii. Forecast release to release upgrade impacts.
xiii. Establish strategy for unit testing.
xiv. Ensure 100% code inspection for new and modified code.
(a) Establish intervals and exit criteria unique to the system, hardware, and software design activities within this phase – align to overall Design Phase 2 completion target.
(b) Manage internal and phase to phase activities in parallel wherever possible.
(c) Conduct a “Lessons Learned” exercise to identify design process improvements and preventive actions.
Design
Phase 3
Complete hardware and software design integration.
System
i. Integration test cases captured and documented in appropriate repository.
ii. Execute 100% new features test cases with a 95% pass rate – document results and exceptions.
iii. Ensure test case results map to documented customer and feature requirements.
iv. Resolve all priority 1 and 2 problems open at the end of Test Phase 3 of the previous release with the fewest possible exceptions.
v. Ensure all components used in hardware and software test also pass integration test.
vi. Update agreement to design integration test plan.
vii. Complete customer documentation portion of the supporting design documentation.
viii. Revalidate dependencies on related hardware /software products and functions to maximize reuse of available technologies.
ix. Finalize product test plan.
x. Continue process work to ensure commercial and operational requirements can be satisfied
xi. Ensure 100% code inspection for new and modified code.
xii. Update and validate Release over Release plan to achieve release over release improvement (10% minimum arrival rate reduction in customer reported problems).
xiii. Complete all system level design documentation.
xiv. Track and ensure adherence to budgeted resources and finance.
Hardware
i. Recycle hardware design and design files as needed.
ii. Update functional, component placement, and physical agreements as needed.
iii. Update component qualification plan – identify % complete and potential risks/impacts to schedule.
iv. Update environmental product integrity test plan – identify results to date and remaining activities.
v. Complete all hardware design documentation.
Software
i. Test for memory leaks and real time impacts and resolve any identified, as applicable
ii. Update, debug, and compile software code as needed.
iii. Submit any code changes to the appropriate repository.
iv. Complete all software design documentation.
v. Software failure rate prediction as part of the dependability program.
vi. Ensure design test case results map to requirement documents.
(a) Establish intervals and exit criteria unique to the system, hardware, and software design activities within this phase – align to overall Design Phase 3 completion target.
(b) Manage internal and phase to phase activities in parallel wherever possible.
(c) Conduct a “Lessons Learned” exercise to identify design process improvements and preventive actions.
System Test Phase 1
Finalize and execute verification test plans – complete product verification.
(a) Design integration test criteria met.
(b) Execute product test plan (100%) at least once with a 99.5% pass rate.
(c) Ensure any product impacting issues have a resolution plan.
(d) Ensure any export control impacting issues have a resolution plan.
(e) Execute regression suite and traffic; testing and feature interoperability testing with other products and systems as applicable.
(f) Ensure verification test case results map to requirement documents.
(g) Execute release upgrade plan with no critical problems.
(h) Execute system recovery with no critical problems without a resolution plan.
(i) Validate all service and support tools, including required customer tools.
(j) Verify documentation accuracy.
(k) Product integrity test criteria met – including goals for product functionality, capacity, real time, performance, and cost.
(l) Update and validate plans for Release over Release metrics (10% minimum arrival rate reduction in customer reported problems).
(m) Recycle hardware design and design files as needed.
(n) Ensure all components are qualified.
(o) Update, debug, and compile software code as needed.
(p) Submit any code changes to the appropriate repository.
(q) Ensure all software delivery mechanisms are in place.
(r) Prepare for formal release of the hardware and software design.
(s) Track and ensure adherence to budgeted resources and finance.
(t) Conduct a “Lessons Learned” exercise to identify product verification process improvements and preventive actions.
(u) Establish intervals and exit criteria unique to the system, hardware, and software design activities within this phase – align to overall System Test Phase 1 completion target.
(v) Manage internal and phase to phase activities in parallel wherever possible.
System Test Phase 2
Finalize internal/external validation test plans and complete system validation.
(a) Execute product component system validation, 100% of test cases executed.
(b) Execute regression suite and traffic testing, 100% of test cases.
(c) Ensure verification test case results map to requirement documents, including churn items.
(d) Execute release upgrade plan with no critical problems.
(e) Execute system recovery with no critical problems.
(f) Test large system overload limits and interoperability for intended performance.
(g) Update and validate plans for release over release metrics (10% minimum arrival rate reduction in customer reported problems).
(h) Finalize first customer/market test plans for System Test Phase 3 execution.
(i) Ensure budgeted resources and finances are in place to support design requirements for System Test Phase 3.
(j) Validate commercial and operational requirements – include consideration for software load delivery, patching, maintenance, etc.
(k) Ensure all elements of the hardware and software design have been formally released for production and support.
(l) Conduct a “Lessons Learned” exercise to identify product verification process improvements and preventive actions.
(m) Align System Test Phase 2 completion and results to the Customer Readiness Business Decision Point (ref. Corporate Procedure 505.31 – Product Life Cycle Management).
System Test Phase 3
Validate formally released product in a live customer environment.
(a) Finalize software delivery and management plans.
(b) Ensure any required export licenses and applicable support processes are in place.
(c) Ensure the network upgrade plan is tested and ready.
(d) Ensure all new features and feature churn have been validated and exercised per established project metrics and requirements including interoperability for intended performance.
(e) Ensure system in service soak time (days/weeks) has been completed.
(f) Ensure out of box sampling is performed.
(g) Ensure all product design documentation is updated, formally released, and implemented, as required, to support volume production.
(h) Ensure all applicable commercial requirements have been satisfied and the supporting operational processes are implemented, validated, and ready for volume production.
(i) Update plan to achieve release over release improvements during the Design Support phase – identify intervals and targets.
(j) Report on variances in budgeted resources and finance.
(k) Establish plan and ensure budgeted resources and finances are in place for ongoing design support.
(l) Ensure delivery risk assessment has been performed and is acceptable.
(m) Ensure verification test case results map to requirement documents.
(n) Conduct a “Lessons Learned” exercise to identify product validation process improvements and preventive actions.
(o) Align System Test Phase 3 completion and results to the Channel Readiness Business Decision Point (ref. Corporate Procedure 505.31 – Product Life Cycle Management).
Design Support
Provide ongoing product support to achieve improvements in quality, performance, and cost through efficiencies in design.
(a) Monitor product performance, quality, and customer satisfaction ensuring closure of Case Reports.
(b) Design, test, validate, and implement improvements as required – ensure knowledge transfer to key functional primes and channel partners.
(c) Identify potential hardware cost improvements and implement as approved by the business unit.
(d) Report on plan for release over release improvements and the associated results.
(e) Track feature churn to ensure product offering remains consistent with commercial/design intent.
(f) Perform periodic retesting to ensure system level functionality and performance continue to meet and/or exceed pre-established quality targets – take action as required.
(g) Report on variances in budgeted resources and finance.
(h) Establish and execute plan to transition from design support to maintenance in alignment with the End of Life readiness Business Decision Point.
Design Maintenance
Maintain product to ensure performance does not impact service and/or network reliability.
(a) Monitor product for service impacting issues only – ensure closure of CR’s.
(b) Design, test, validate, and implement improvements as justified and approved by the IPT leader and/or product owner-ensure knowledge transfer to key functional primes and channel partners.
(c) Establish and execute plan to stop all design maintenance activities in alignment with the End of Life Business Decision Point (ref. Corporate Procedure 505.31 – Product Life Cycle Management) - include disposition of all Intellectual Property.
5.2 In association with the key phase activities, product specific metrics shall be established and documented to determine the exit criteria for each design and test phase. Performance to these metrics shall be captured and maintained to ensure all conditions are met for phase completion. Reporting of metrics shall be the responsibility of the IPT Release Leader as identified in section 3.12 above.
6.0 Approvals
In addition to the Senior Executives listed on the title page of this Procedure, Senior Executives of the following Operating Entities have also approved and agreed to adopt this Procedure for implementation across the product portfolios for which they are accountable:
President – Enterprise Networks
President – Optical Networks
President – Wireline Networks
President – Wireless Networks
7.0 Reference Documents
Corporate Policy 400.04 – Export Controls Compliance
Corporate Policy 500.04 - Quality and Customer Satisfaction
Corporate Policy 500.16 – Corporate Standards
Corporate Policy 500.22 – Acquisition of Goods and Services
Corporate Policy 700.01 – Research and Development Investment
Corporate Policy 700.02 – Product Design and Life Cycle Management
Corporate Procedure 505.01 – Quality Management Systems
Corporate Procedure 505.31 – Product Life Cycle Management
Corporate Procedure 505.33 – Product/Solution Delivery
Corporate Procedure 601.01 – Research and Development Program
Corporate Standard 1505.00 – Contract Manufacturers Products
Introduction Process
Corporate Standard 1509.00 – Dependability Program
Corporate Standard 1509.01 – Dependability Program Supplemental
Documentation
Corporate Standard 1512.00 – Designing for Global Installability
Corporate Standard 1513.01 – Design for Testability
Dependability/Reliability Guidelines located at http://navigate.us.nortel.com/imds?pg=/eng/dfr
TR-0S03-119-2004- Design for Environment
Nortel Networks Corporate Policies and Procedures are available on the Nortel Networks intranet:
Services @ Work – Corporate Information - Corporate Policies & Procedures
http://services-canada.ca.nortel.com/Livelink/livelink.exe?func=ll&objId=38150&objAction=sawbrowse
Nortel Networks Corporate Standards are available on the Nortel Networks intranet:
Global Web - Global Quality - Corporate Standards
http://navigate.us.nortel.com/imds?pg=/ops/qual/standards
8.0 Review
This Procedure shall be reviewed every three years, or earlier, as required.
End of Document
Issued by:
Abdul Khawar
Global Quality Systems
Approved by:
Greg Mumford
Chief Technology Officer