NCTS R2.6.0 - Congrex

Raul Alarcon
Quality Assurance & Management Section
NCTS & ESPC Industry Workshop Day
22 September 2008
Product Assurance and Safety
Technical and Quality Management
0
Sep08

Why a NC control system?
ECSS-Q-20-09B, Non-conformance Control System,
Clause 8.2 Quality Record Requirements
The supplier should maintain a database of non-conformances.
The non-conformance database should be used for NCR followup,
for the generation of a NCR summary status report, and
as an electronic tool for complete NCR processing.
Product Assurance and Safety
Technical and Quality Management
1
Sep08

What does NCTS offer?
► NCTS provides secure web access to all users (even outside ESA
firewall)
► NCTS fully complies with ECSS-Q-20-09A and implements its
process
► NCTS provides a common source and common system throughout
the project life-cycle
► NCTS maintains privacy of data by user access levels and product
tree access
► NCTS is under configuration control by TEC-Q
► NCTS is customizable to specific project needs
► NCTS interfaces with Industry tools and MS Excel
► NCTS stored data is now also portable (ZIP file)
Product Assurance and Safety
Technical and Quality Management
2
Sep08

NCTS Figures
Projects in Operation
► More than 1,300 users, with 25%
growth the last 9 months.
► Number of users expected to grow
close to 1,500 by the end of 2008
► 11 projects and more than 2,000
NCRs
► Number of projects can increase
significantly after NCTS R2.7
Projects in Test/Training
► Training projects allow familiarisation of
users with environment and are a
precursor to projects in real operation
► Training/testing access provided to both
internal and external users
► More than 700 users in test/training and
growing continuously
► 9 projects, with some moving soon to
real environment
22
24
0
3
16%
8%
5% 114
78 76
83 86 86
24
AlphaSat AlphaBus CryoSat 2 SWARM SM OS M icroscope BepiColombo GAIA JWST LISA PF Galileo IOV
2
3
63
69
10
Production Users Jan 08
Production Users Sep 08
% Total NCRs Sep08
11
0
25
62
92
Training Users Jan 08
Training Users Sep 08
4
1
5
Product Assurance and Safety
Technical and Quality Management
16%
20
111
20
190
114
0
21%
120
1
156
299
20%
177
324
23%
330
418
332 332
AlphaSat GAIN SmallGEO M SG HSF EOP ExoM ars SRE GAL
3
Sep08

NCTS History
2005
2006
2007
2008
• NCTS R2.0.0: First release of new NCTS application.
• NCTS R2.1.0: New look and feel; multiple internal NRB; PA role; archive email notification; new product
tree administrator tool; save query functionality; enhanced reporting.
• NCTS R2.2.0: New safety fields in NCR; length of fields; NRB classification values retained;
• NCTS R2.2.1: Enhanced NC status list report
• NCTS R2.2.2: Email notification enhancement
• NCTS R2.2.3: RoboHelp included; change of labels; Galileo project requirements implemented
• NCTS R2.2.4: Scripts to migrate EOP data from NCR Tracking R1.5.4 to NCTS
• NCTS R2.2.5: EOP-only release. Improved performance.
• NCTS R2.2.6: EOP, SRE and Galileo. Patched to fix problems with file uploads on Oracle 9i server. Deployed
on external servers.
• NCTS R2.3.0: Implemented requirements from Galileo, fixes to EOP, enhanced notification.
• NCTS R2.3.1: Patch release to fix SPAM filter problem, label changes, SPR fixes for EOP. All servers.
• NCTS R2.4.0: Validated XML Import of NCRs from TAS and Astrium. Not installed in production…
• NCTS R2.5.0: XML Export of NCRs to TAS and Astrium. Validated in February 2008 with Industry. Enrolled in
all servers (together with R2.4.0-Import). First release developed and installed under full configuration control by
TEC-Q. Included a series of enhancements and SPR fixes identified on R2.3.1 (reporting, field errors, etc). This
is the current release in production on APP, EOP, SRE* and HSF production servers.
Product Assurance and Safety
Technical and Quality Management
4
Sep08

What is happening and what is next?
► NCTS XML Pilot Phase Configuration
• SRE-GAIA � SFTP server, folder structure and mapping file configured. First successful
exchange with Astrium in July 2008.
• R2.5.0.1: Patch release to fix SPR identified during GAIA Pilot Phase (could not export
NCRs with actions where the Internal Ref field was null).
• Galileo training meeting 23.09.2008 � Trigger start of Pilot Phase with test data
► NCTS R2.5.1 – XML Export by Industry PA Manager
• Successfully validated by ESA in August 2008.
► NCTS R2.6.0 – XLS data exchange and NC data package generation (End Sep08)
• MS Excel NCR upload. Template automatically generated by NCTS.
• NCR ZIP File (with NCR in pdf and all attachments). Multiple NCRs can be selected.
► NCTS R2.7.0 – Specific requirements from HSF Payload Projects (Start Oct08, tbc)
• NCRs processed according to GPQ-PR-01-1. To be project configurable functions.
Product Assurance and Safety
Technical and Quality Management
5
Sep08

XML Interface with Industry tools
Functional requirements
• Data exchange complies with the standard set up in ECSS-M-50B and XML (extensible mark-up)
• Data imported is read-only (the origin industry remains the master for its own NCR data)
• Imported NCRs cannot be exported back to the original application
• NCTS generates the Code Mapping file required by Industry to perform the code translation. The
files are maintained by the industrial partner.
• Before importing/exporting the datapack, the XML file is validated against the NCTS Data Exchange
XML Schema agreed with Industry
• Each NCTS NCR is exported with all customer NRBs, actions and attachments.
Performance
• NCTS can import/export the selected NCRs in real-time.
• The overall performance is affected by the total size of all attachments: current limit is 100 MB.
• The Export functionality is now available in both external and internal servers.
Security
• File transfer method (SFTP).
• NCTS security rules: only ESA/Industry PA managers and NCTS administrators can import/export.
Product Assurance and Safety
Technical and Quality Management
6
Sep08

XML Interface Deployment Diagram
NCTS is enrolled in 4 dual-servers:
SRE, EOP, APP and HSF
Product Assurance and Safety
Technical and Quality Management
7
Sep08

Ground rules for data exchange
► Each company must:
• Establish its own NC management system
• Maintain & use its NCR information to improve its products
• Fulfill the legal & contractual requirements
► Each company is responsible to:
• Report its NCRs using NCTS according to contract requirement
• Manage information about its products in NCTS
• Define access rights related to its NCR (enforced in NCTS)
► NCTS used as a reporting tool for all contractually required instances
► NCTS project to be maintained up to date (common reference for
whole project)
► Each company may transfer data only according to defined access
rights
Product Assurance and Safety
Technical and Quality Management
8
Sep08