Monday, November 16, 2015

Automotive SPICE Provisional Assessor Training in Bangalore

intacsTM Certified Provisional Assessor (Automotive SPICE) Training is scheduled by IQI Consulting Services Pvt. Ltd. as per following details:

Friday, August 28, 2015

Rating & Aggregation Rule

My this article is intended to Assessor community &
NOT to Process Improvement practitioners.
Rating Rule:
Existing rule: ISO/IEC 15504 Part 2 requires to rate Process Attribute (PA).
In Practice: In most of the  assessments, BPs & sometimes GPs are also rated. These ratings have been used to derive Process Attribute rating.
Solution: ISO/IEC 33020 (which replaces ISO/IEC 15504 Part 2) now defines three types of rating, R1, R2 & R3. The meaning of these ratings is:
a) Characterize process outcomes, i.e., Characterize BP for each process instance 
b) Characterize process attribute outcomes, i.e., Characterize GP for each process instance
c) Aggregate BP characterization of all process instances to PA1.1 rating
d) Aggregate GP characterization of all process instances to respective PA rating

a) Characterize process attribute for each process instance 
b) Aggregate process attribute characterization of all instances to PA rating
Rate process attribute for each process instance without aggregation.
Aggregation method:

Existing rule: ISO/IEC TR 15504 Part-7 defines derive CL of each process & converting to aggregated CL rating.

In Practice: Concept of SCAMPI-A method with expert judgment had been used frequently in ML assessment.
Solution: ISO/IEC 33020 now defines two major concept of aggregating characterization to derive rating.
1. Expert Judgment
2. Mathematical approach: Using Mean or Median
To apply mathematical approach, first convert ordinal scale (N, P, L, F) characterization to corresponding interval scale (0, 1, 2, 3) or (N, P-, P+, L-, L+, F) to (0, 1, 2, 3, 4, 5).
2.1 Mean:
  • Calculate mean value of all characterization for particular Process Attribute
  • Round-off the value in case of decimal value
  • Convert to corresponding Ordinal scale (N, P, L, F)
2.2 Median:
  • Calculate median of all characterization for particular Process Attribute
  • In case of even count, calculate mean of center two numbers
  • Convert to corresponding Ordinal scale (N, P, L, F)  
Note: Mathematical concept shall be applied when sufficient number of data points are available. Class 1 & Class 2 type of assessment are potential candidate to apply this concept.

Thursday, August 27, 2015

Automotive SPICE v3.0: New Rating Scale

Rating Scale:

Rating  scale: Automotive SPICE V2.5 & V3.0

  Not achieved   0 to ≤ 15% achievement
  Partially achieved   > 15% to ≤ 50% achievement
  Largely achieved   > 50% to ≤ 85% achievement
  Fully achieved   > 85% to ≤ 100% achievement

In V3.0, this scale has been further detailed for “P” & “L”
  P-   Partially achieved -   > 15% to ≤ 32.5% achievement
  P+   Partially achieved +   > 32.5 to ≤ 50% achievement
  L-   Largely achieved -   > 50% to ≤ 67.5% achievement
  L+   Largely achieved +   > 67.5% to ≤ 85% achievement
Rating & aggregation rule has been defined in ISO 33020, which shall be used while conducting assessment based on Automotive SPICE 3.0.

Please visit again for explanation on rating & aggregation rule.

Tuesday, August 18, 2015

Automotive SPICE v3.0: Plug-in Concept

Automotive SPICE v2.5 has Engineering Processes as ENG.1 ~ ENG.10 covering system & software domain processes. Automotive SPICE v3.0 has been upgraded with concept of "Plug-in" domain specific processes.

System Engineering process have been separated with SYS.1 ~ SYS.5 on top level of architecture. Domain specific processes, i.e., Software Engineering have been defined as SWE.1 ~ SWE.6. The placeholder for Hardware Engineering (HWE.1 ~ HWE.4) & Mechanical Engineering (MEE.1 ~ MEE.4) have been created.

In future, with the availability of Hardware engineering & Mechanical Engineering processes, Process scope can be enlarged. 

For details visit or write to us on

Wednesday, August 12, 2015

Automotive SPICE v3.0: Software Engineering Processes

Software Engineering Processes (ENG.4 ~ ENG.8) in v2.5 has been split to synchronize with ISO 26262 clauses. Pictorial representation below provides clear view:

Monday, August 3, 2015

Automotive SPICE v3.0 Changes

Overview of Changes:
  • PRM & PAM: Instead of two separate documents as PRM V4.5 & PAM V2.5; PRM & PAM have been merged into single document Automotive SPICE PRM, PAM V3.0
  • Measurement Scale: V 2.5 did not include measurement scale where as V3.0 defines “Process Attribute Rating scale, Rating & Aggregation method (by reference to ISO 33020), Capability level Model.
  • Process ID: Engineering process ID has been changed to clearly indicate System & Software Level processes. ENG.1 ~ ENG.3 & ENG.9 & ENG.10  SYS.1 ~ SYS.3, SYS,4 & SYS.5. Similar software processes ENG.4 ~ ENG.8 has been changed to SWE.1 ~ SWE.6.
  • Re-organization of Software Design & Construction process: Software Design (ENG.5) & Software Construction (ENG.6) has been aligned with ISO 26262 Part 6 clauses. ENG.5 & ENG.6 has been divided into three process as SWE.2 (Software Architecture), SWE.3 (Software Design & Unit Construction) & SWE.4 (Software Unit Verification). ENG.8 (Software Testing) has been named as SWE.6 Software Qualification Test.
  • Adding “Consistency” as BP: One BP as “Ensure Consistency” has been included after traceability BP to emphasize the usage of traceability matrix in review.
  •  Removal of “Proceedings” BP: Proceeding base practice from SUP.9 & SUP.10 have been removed & included as notes.
For details on changes & description of each point with expert comment, write to us on   

Monday, July 20, 2015

Automotive SPICE 3.0

Automotive SPICE 3.0 has been released & available for download at

Highlights of changes:
- PRM & PAM has been merged into single document
- Structural changes like realigning system & software engineering processes, ENG.5 & ENG.6 process
- Clarifications (with notes) 
- Utilization of traceability by adding one BP as "Ensure consistency"
- Rating : There is addition on rating concept which was practices quite often, i.e., rating of BP & GP. This  has been introduced as "outcome rating for process & process attributes". Rating of outcomes is not mandatory  but rating method to be decided as the time of process assessment planning.

For further details on changes, please visit again ...