PAS PMDX Services Commissioning Test Procedure

PAS PMDX Services Commissioning Test Procedure
Revision History Date Started 19/02/2001 24/02/2001 27/02/2001 Date released 22/02/2001 26/02/2001 Revision Draft 1.0 Draft 1.01 Draft 1.02 Description Initial Draft Revised with Redundancy Some more test cases added Added Fitel Feedback Author Anand Ballabh, John Yeh Rajesh Ohri Anand Ballabh
24/04/2001
Draft 1.0.3
Anand Ballabh Kanwaldeep Singh

Table of Contents
1. 1.1 1.2 1.3 1.4 INTRODUCTION:.........................................................................................................5 Scope of Document ................................................................................................5 Target Audience.....................................................................................................5 Definitions, Symbols and Abbreviations ....................................................................5 References.............................................................................................................6
2. TEST SETUP INFORMATION.............................................................................................7 2.1 PDX System in the FITEL Network ..........................................................................7
2.2 PDX Test Setup......................................................................................................7 2.2.1 Lab Setup Information .........................................................................................................................7 2.2.2 Test Entry Criteria .......................................................................................................................................7 3. TEST ITEMS ......................................................................................................................8 3.1 Functional Features.......................................................................................................8 3.1.1 Using man machine interface:..........................................................................................................8 3.1.2 Access to PDX services:......................................................................................................................8 3.1.3 DDI-P online sign-up process:..........................................................................................................9 3.1.4 Authentication of Subscriber:..........................................................................................................9 3.1.5 Sign-up Authentication: ...................................................................................................................10 3.1.6 Signup Database verification:.........................................................................................................10 3.1.7 Connection to PMDX services refused: .......................................................................................11 3.1.8 Services hand by Sign up server: .............................................................................................11 led 3.1.9 CCC function:.....................................................................................................................................11 3.1.10 Requirement:.......................................................................................................................................12 3.1.11 GUI supporting features:.................................................................................................................12 3.1.12 Session with ICPs..............................................................................................................................12 3.1.13 Services Offered:................................................................................................................................12 3.1.14 Forwarding of emails:.......................................................................................................................13 3.1.14.1 ...Store and forward function ............................................................................................................13 3.1.15 Storage capacity..................................................................................................................................13 3.1.16 Error Notification ..............................................................................................................................14 3.1.17 Mail Size too large:............................................................................................................................14 3.1.18 Message Delivery size:......................................................................................................................14 3.1.19 E-mails with attachments:...............................................................................................................15 3.1.20 Melody, bitmap & animation Files................................................................................................15 3.1.21 Mail box full:.......................................................................................................................................15 3.1.22 Mail receive notification: .................................................................................................................16 3.1.23 Store and forward option: ...............................................................................................................16 3.1.24 Storing of Attachments:...................................................................................................................16 3.1.25 Special mail sending:.........................................................................................................................16 3.1.26 New Mail Notification:......................................................................................................................16 3.1.27 CDR Mediation: .................................................................................................................................17 3.1.28 CDR Format:......................................................................................................................................17 3.1.29 Content Services:................................................................................................................................17 3.1.30 Accessing WEB content on PS:......................................................................................................18 3.1.31 List of URLs:.....................................................................................................................................18 . 3.1.32 MTA Server:.......................................................................................................................................18 3.2 Management Features .................................................................................................18

3.2.1 Pricing Information..............................................................................................................................18 3.2.2 Performance management ..................................................................................................................18 3.3 System Performance test.............................................................................................18 3.3.1 Redundancy of Application servers.........................................................................................................18 3.3.2 Redundancy of Sign-up servers.................................................................................................................19 3.3.3 Redundancy of Email Gateway servers..................................................................................................19 3.3.4 Load sharing of MTA servers....................................................................................................................19 4. COMMISSION TEST PLAN FLOW ....................................................................................20 4.1 System Acceptance Test Process.................................................................................20 4.2 Commissioning Test Development and Process.............................................................20 4.2 Commissioning Test Development and Process.............................................................21 APPENDIX A: COMMISSIONING TEST SIGN-OFF FORM ....................................................23 APPENDIX C: COMPLETE VOICE NETWORK ACCEPTANCE TEST MATRICES .................25
PAS PMDX Services Commissioning Test Procedure 1. Introduction:

UTStarcoms PAS is an end-to-end solution to provide the PHS services. Fitels PHS network shall be based on this system. The network services include both the basic voice services and value added services (VAS). The VAS include location, short message and data services. The data services on the handset refer to the services offered using the Pmail Deluxe protocol. These services include email and information service.
1.1
Scope of Document
This document specifies Acceptance Test Procedure (ATP) for PMDX services to be carried out for FITEL. Chapter 1 and 2 describes the scope of this document and the network description. Chapter 3 contains the detailed test procedures. Chapter 4 describes how this document is used in an acceptance process. The Appendices contains samples of testing sign-off sheets, punch list, and the complete acceptance-testing matrix.
1.2
Target Audience
This document is targeted for the following primary audiences: 1. System engineers in the development lab to ensure the system integrity in the field. 2. Field engineers at the customer site to execute various acceptance test phases. 3. Project managers to quantitatively evaluate whether the contractual obligation had been filled. 4. Customer operators as a technical reference material to the system operations.
1.3
Definitions, Symbols and Abbreviations

AS CDR CGI CGW DN ICP LS MTBF PDX PHS POP3 PS
Application Server Call Detail Record Common Gateway Interface Contents Gateway Dialed Number Internet Content Provider Location Server Mean Time Between Failures P-mail Deluxe Protocol Personal Handy phone System Post Office Protocol v3 Personal Station 5

SAM SMSC SMSGW TN VAS
Subscriber Application Management Short Message Service Center Short Message Service Gateway Telephone Number Value Added Services
1.4 References [1] PDX Subsystem verification matrices: http://huts.utstar.com.cn/fitel/index.htm [2] SMS Subsystem verification matrices: http://huts.utstar.com.cn/fitel/index.htm [3] LS Subsystem verification matrices: http://huts.utstar.com.cn/fitel/index.htm [4] Mediation Device Subsystem verification matrices: http://huts.utstar.com.cn/fitel/index.htm [5] Document #: NET2000-12-21-19: FITELs PHS Network Technical Descriptions, version 1.9 [6] Document #: WLL-PAS 00-01: PAS Short Message Service System Requirement Specifications, version 1.7 [7] Document #: IAGATP 2001-01-01-18: iAG Subsystem Commissioning Test Procedures, version 2.0 [8] Document #: LSATP 2001-01-02-18: Location Service Commissioning Test Procedures, version 1.2 [9] Document #: PDXATP 2001-01-02-23: PDX Subsystem Commissioning Test Procedure [10] Node Load Test In-Progress Test Report, Document #: VNLTP -2001-02-02-10, version 1.0 [11] FITEL software release note version 1.4, released on February 12 th , 2001. [12] FITEL software release note version 1.3, released on February 3rd, 2001. [13] FITEL software release note version 2.0, released on February 26th , 2001.
PAS PMDX Services Commissioning Test Procedure 2. Test Setup Information

This section specifies the software and hardware entry criteria for beginning the commissioning test.
2.1
PDX System in the FITEL Network
Figure 1 of reference document [5] shows how the PDX system fits into the FITEL network. Figure 13 of the reference document [5] shows more details on the PDX network architecture.
2.2
PDX Test Setup
This section specifies the software and hardware entry criteria for beginning the commissioning test. This section also contains the lab test setup information. 2.2.1 Lab Setup In formation The lab test setup used to verify the commissioning test procedure items in this document can be found in reference [10] section 4.1. 2.2.2 Test Entry Criteria Before this commissioning test can be executed on-site, the following criteria must be verified. 1. 2. 3. 4. 5. The PDX system has been configured in the network as per the Installation guide iAG and PDX iAG are configured. SMSC and LS system has been configured. Voice network is installed and commissioned. CDR is working.
PAS PMDX Services Commissioning Test Procedure 3. Test Items

This section specifies the feature and system level testing to be carried out for the PMDX services. 3.1 Functional Features This section contains the test items related to the functional feature of the overall system. 3.1.1 Using man machine interface: From the hand set sending of location information, i.e. RSSID and CSID as a part of ISDN setup message, for PDX services can be enabled or disabled. Test procedure:

From the handset menu go to Location Information (F87) In the hand set screen left arrow for enabling and right arrow for disabling. To enable press left arrow. Input the password. To disable press the right key.
Expected Result:
Handset screen shows operation successful.
3.1.2 Access to PDX services: The subscribers can choose to sign-up online using the handset.(First time signup is only through handset) Test procedure:

From the handset menu go to Signup (F*11) Press talk key Hand set screen shows two options 1---- Start 3-----End Type 1 and press call key. Input the nick name and follow the instructions.
Expected Result:
Subscriber information enters in the tsignup table in signup data base.

3.1.3 DDI-P online sign-up process: Note: A subscriber, who has already signed-up for email service, can signup to modify his/her profile. The following options are supported. Option 1 and 2 are mutually exclusive, the subscriber may either enable the auto email receive function or new email notification function. It is also possible to disable both the functions. Enable/Disable Auto Email Receive Enable/Disable New Email Notification Enable/Disable Stop mail receive temporary Enable/Disable Mailbox Full Notification Enable/Disable Mail Forwarding Enable/Disable Advertisement mail Enable/Disable Refuse mail Test procedure:

From the handset menu go to Signup (F*11) Press talk key Hand set screen shows two options 1---- Start 3-----End Type 1 and press call key. Go to main menu. Handset screen shows following options 1 New mail notification 2 Auto receive 3 Mail box full 4 Stop receiving mail temporary 5 Refuse mail 6 Mail forward 7 Advertisement 99 Current configuration 00 Stop Select the desired option and follow the instructions.
Expected Result:
If selected item 1 subscriber gets the notification for new mail, if selected item 2 subscriber automatically receives the mail and after receiving it gets an alert for the mail, and so on for the other options. If any one of the above option is cha nged it gets recorded in the TSIGNUP table in the Signup database.
3.1.4 Authentication of Subscriber:

For each sign-up request subscriber is authenticated. Test procedure:

Take a PS, which has different authentication key in WRT and in PS. Try to signup with the PS. Now make the same authentication key in PS and WRT. And again try to signup.
Expected Result:

In the first case signup is not successful. In the second case signup is successful.
3.1.5 Sign-up Authentication: For each email request, the sign-up database is referred if the subscriber has not signedup the connection is refused. Test procedure:

Take a PS (subscriber), who has not signed up. Send an email with the PS. Now signup from the PS. And again try to send email.
Expected Result:

In the first case email request is refused. In the second email request is successful.
3.1.6 Signup Database verification: When subscriber signup first time all the information given by him are recorded in the TSIGNUP table of signup database. Afterwards if subscriber modifies his or her profile using signup the TSIGNUP table gets modified accordingly Test procedure:

Signup first time from a new handset ( Sign up procedure is in section 3.1.2) Check in the TSIGNUP table in the signup database
10

Now change the profile of the subscriber using signup from handset or from web server. Check again in the TSIGNUP table in the signup database.
Expected Result:

All the information input by subscriber should be recorded in TSIGNUP table in signup database. After changing the subscriber profile the information in TSIGNUP table also changes.
3.1.7 Connection to PMDX services refused: If the voice service of the subscriber is suspended connection to the Pmdx server is refused Test procedure:

Suspend the voice services of a subscriber from CDR and SAM. Now try to signup or to send a mail.
Expected Result:
Connection to the PMDX services is refused.
3.1.8 Services handled by Sign up server: This is the internal function of the system how does it works; it is automatically covered in section 2.1.2,2.1.5 and 2.1.6. Handles sign up request originated from PS Handles sign up request originated from Fitel provided web site. 3.1.9 CCC function: The CCC will configure subscriber profile to signup server through web interface Same as signup process in section 3.1.2
11

3.1.10 Requirement: Dedicated terminal with Windows 98, Chinese edition for @ MENU tool To be provided by Fitel 3.1.11 GUI supporting features: User-friendly GUI supporting features like system configuration upload and download cgwmenu.txt file from application server, editing the menu tree and saving the menu files Fitel has to provide the GUI 3.1.12 Session with ICPs Interactive session with ICPs (cgwmst.txt file contains this information) Note: This feature means when a subscriber access the content services, different options are shown in the hand set such as which site he want to access and what are the charges for the site and what is the mode of payment, etc. Test procedure:

From the handset menu go to Air info. (F*02) Press F, type @MENU and press the talk key. Hand set screen shows different URLs in the screen Select the desired option (URL). Now the handset screen shows different options or the charge schemes for the site.
Expected Result: The interactive session passes the test.
3.1.13 Services Offered: Based upon the location of the subscriber (PS), information about facilities (e.g., restaurants, parking lots, hospitals etc.) with in the specified distance. It will be shown in next version
12

The subscriber will be able to access email account hosted by remote server (POP accounts) using the PS handset It will be shown in next version 3.1.14 Forwarding of emails: Forwarding of emails from existing email accounts to the PDX account and keeping the copy of email in the server (for the subscribers who already have the corporate account and subscribe to the PDX services) Test procedure:

Open any existing e-mail account in Yahoo, hotmail or any other site. (The site must have the mail forwarding option) Forward the mail to the PDX account, nickname@domainname. (Mail size must be in the limit of PDX)
Expected Result:
The mail is received in the mail box of the subscriber (nickname@domainname)
3.1.14.1 Store and forward function Store and forward function for the subscribers who want to forward mails from PDX account to other accounts. Test procedure:

In PS1 set the mail forward feature to another PS2 (Procedure for this is same as described in section 3.1.3) Send a mail to PS1.
Expected Result:
Both the PS1 and PS2 receives the mail.
3.1.15 Storage capacity Maximum 1 MB storage is allowed to one subscriber. Not clear how to test it
13

3.1.16 Error Notification The MTA server receives the email from Internet if the email id is not valid; sender is notified with an error. Test procedure:

Open any existing e-mail account in Yahoo, hotmail or any other site. Send a mail to the PDX account, nickname@domainname. Which does not exist i.e. nickname is not created.
Expected Result:
The sender is notified with an error unknown user.
3.1.17 Mail Size too large: If the mail size of the message exceeds 5KB, the e-mail gateway notifies the sender "mail is too big to deliver a PHS subscriber" and deleted from the server. Test procedure:

Open any existing e-mail account in Yahoo, hotmail or any other site. Send a mail to the PDX account, nickname@domainname such that the mail size is more than 5KB. Send a mail from Internet (Outlook) to the PDX account.
Expected Result:

The sender is notified with an error mail is too big to deliver a PHS subscriber. In the case, mail send from Internet (outlook) the MTA sends error message mail is too big to deliver a PHS subscriber.
3.1.18 Message Delivery size: If the mail id is valid and the size of the message exceeds 5000bytes and less than 1MB, the message is truncated to the max size i.e. 5000bytes the sender is notified and message is delivered to subscribers mail box Now the feature has changed if the mail size is more than 5KB the receiver will not receive the mail and sender gets error message mail is too large
14

3.1.19 E-mails with attachments: Send and receive Email with attachments (Bitmap, melody and Animation) files to/from PS Test procedure:

From PS send a mail with attachment to the other PS. Attachment could be bitmap, melody or animation file. Send the attachments to any Internet mail account from the PS.
Expected Result:

The PS receives the attachment. The Internet mail account also receives the attachments.
Note: At present sending bitmap, animation and melody file attachments from Internet to a PS does not work. 3.1.20 Melody, bitmap & animation Files Attach. Files are melody, bitmap & animation Same as section 2.1.19 3.1.21 Mail box full: If the receivers mailbox is full the sender is notified with an error. Test procedure:

Open any existing e-mail account in Yahoo, hotmail or any other site. Send a mail to the PDX account, from above accounts or from PDX account. Make sure that receivers mailbox is full.
Expected Result:

The sender is notified with an error. The receiver of the mail is notified that the mailbox is full.
15

3.1.22 Mail receive notification: If there is enough space in mailbox the mail is stored there and the subscriber is notified via SMSC, for new email. Test procedure:

Open any existing e-mail account in Yahoo, hotmail or any other site. Send a mail to the PDX subscriber account, from above account s or from PDX account. Make sure that receivers mailbox has enough space.
Expected Result:

Mail is received and stored in the inbox of the subscriber. The receiver of the mail is notified that he has a new mail.
3.1.23 Store and forward option: As a part of signup process it is possible to set store and forward option for each incoming mail. The email gateway stores and forwards the email to the specified destination. This is covered in section 3.1.3 3.1.24 Storing of Attachments: Attachments can be stored in the handset for play back. This is a hand set feature 3.1.25 Special mail sending: Special mail includes animation, melody files. Sending of such files is already covered in section 3.1.19
3.1.26 New Mail Notification: When a new email is received for a subscriber in the PDX center, whose email auto receive function is enabled (ON), the PDX center notifies the PS handset via UUI message that new email(s) are received for the subscriber.
16

Test procedure:

Open any existing e-mail account in Yahoo, hotmail or any other site. Enable Auto email receive function of a PDX subscriber. Send a mail to the PDX subscriber account, from above accounts or from PDX account. Make sure that receivers mailbox has enough space.
Expected Result:

Subscriber receives a message for new mails received. PS downloads the messages and stores in the handset memory.
3.1.27 CDR Mediation: Usage records are stored and can be retrieved by CDR Mediation subsystem periodically. Test procedure:

CDR system retrieves the billing information from PDX system periodically. The CDR for PDX are stored in /opt/fitel/data/in/pdx directory of CDR
Expected Result:
Check the PDX CDR in /opt/fitel/data/in/pdx directory of CDR.
3.1.28 CDR Format: CDR body -send mail 3.1.28.1 CDR body- receive mail 3.1.28.2 CDR body -save mail 3.1.28.3 CDR body -new email notification 3.1.28.4 CDR body -email deletion notification 3.1.28.5 CDR body -mail box full notification 3.1.28.6 CDR body -mail forwarding notification 3.1.28.7 CDR body -online sign up 3.1.28.8 CDR body -customer control Test in section 3.1.27 shows CDR for all above options. 3.1.29 Content Services:
17

For content services the ICP may choose charge policy. This is related to content providers 3.1.30 Accessing WEB content on PS: This test is covered in section 3.1.12 3.1.31 List of URLs: Subscribers can get list of URLs to be accessed. This test is covered in section 3.1.12
3.1.32 MTA Server: MTA server receives the mail from Internet and forwards them to email gateway This is one of the functions of how the PMDX network works. 3.2 Management Features This section contains test items related to the management features for the PMDX network. Some test items may need to be completed jointly with 3rd party service vendors. 3.2.1 Pricing Information
Configuration i.e. provisioning of pricing information for various URLs and @MENU entry 3.2.2 Performance management
Statics and logs. This will be tested in next version 3.3 System Performance test 3.3.1 Redundancy of Application servers. There are two application servers installed and both of them are in an independent environment. The case is that whe n one of the server goes down the other should take up for making calls. But as of now the issue has been raised with Beijing and the test results are awaited for the same.
18

3.3.2 Redundancy of Sign-up servers. Test procedure:

Check the signup processes on active server by ps command. Issue haswitch standby-hostname logical-hostname on active server. Repeat step 1.
Expected Result:
All the services switches to the redundant server.
3.3.3 Redundancy of Email Gateway servers. Test procedure:

Check the egw processes on active server by ps command. Issue haswitch standby-hostname logical-hostname on active server. Repeat step 1.
Expected Result:
All the services switches to the redundant server.
3.3.4 Load sharing of MTA servers. Test procedure:

Send some mails to the Internet. Check the session statistics on Ace load balancer in stats/slb/gr 3.
Expected Result:
ACE distributes load evenly on both the MTA servers.
19
PAS PMDX Services Commissioning Test Procedure 4. Commission Test Plan Flow
This section describes how this document should be generated and used in the network deployment process.
4.1 System Acceptance Test Process Figure 4-1 outlines the significance of the acceptance testing process in the contract. After the contract is signed, the first acceptance test stage will be witness testing This stage signifies the arrival of subsystem components on-site. In many cases, the witness test may not be an actual functional testing, because these subsystem components cannot exercise any functionality until further on-site commissioning and integration effort. All the systems interconnections and essential functionality will be verified at the commissioning test stage. This is the last opportunity to make any intrusive testing to the system before the actual or tria l operation can begin. Upon completing this stage with no service-affecting items pending, customer will grant a conditional acceptance of the system. Upon passing the commissioning test stage, the system is ready to enter trial or actual operations. From then on, actual traffic will occur on the system. The final testing is the last stage of the acceptance testing process. With the actual traffic running, the final testing usually focus on coverage and system loading (capacity) issues.
Figure 4-1 Acceptance Testing Process
Witness Test
On-Site Integration
Commission Test Operation Readiness Final Test Capacity Coverage
Conditional Acceptance
Final Acceptance 20

4.2 Commissioning Test Development and Process Figure 4-2 outlines the entire deployment process. The deployment starts with the signoff of the contract, followed by details in the technical specifications. The system engineering team will consolidate both old and new requirement into the verification matrix form. Verification matrices specify for each detailed feature where and how this particular shall be verified. Of all the detailed requirement, some subset o f the requirement will be verified through commissioning test. Each commissioning test items shall represent the following importance: This test item will be used to verify on -site interconnections. This test item will be used to verify service-affecting items. This test item will be used to verify maintenance-affecting items. Commissioning test items signify certain degree of the official product acceptance by the customers. Thus the commissioning test plan will be communicated to the customers before the actual commissioning testing starts. Once the commissioning test plan has been reviewed and agreed by the customers, detailed test procedures and entrance criteria will be developed. Every item of the commissioning test item shall be dry-run in the l b or on-site before the actual test a demonstration in front of the customers. Upon successful demonstration of the commissioning test items, the customers will issue appropriate certificates to signify conditional or total acceptance of the system. Appendix A shows a form that will be used to conduct the actual commissioning testing in front of the customers. Each test item will have clear start and stop times, UT and Customer initials for passing or failing, and column for additional comments. The duration of test time will also be closely tracked to optimize the test execution time. In many cases, the commissioning test is completed with punch list items generated. Conditional or total acceptance will be granted only when all service-affecting punc h- list items are cleared. Clearing of the service-affecting punch list items is also an entrance condition for the system users to enter service. Appendix B is an example of this punch list.
21

Figure 4-2 Commissioning Testing Development
Contract
Technical Spec.
Verify Matrix
Based on: Interconnect Service Maintenance
Accept Test Matrix
Witness Test Items
Commissionig Test Items
Final Test Items
Customer Review
Detail Procedure
Entrance Criteria
Dry-run in Lab or on Site
On-Site Execution
22
PAS PMDX Services Commissioning Test Procedure Appendix A: Commissioning Test Sign-Off Form
This form is used to capture the results of the commissioning test. All fields must be recorded and signed off for the commissioning test to be completed. This form will be used in conjunction of the punch list shown in Appendix B as part of the official acceptance documents.
Table A-1 Commissioning Test Sign-Off Form
Please refer to Documentation: Commissioning Test Sign-Off LS.xls
23

Appendix B: Punch List
At any stage of the acceptance testing process, there may be issues raised by customers or by the vendors which may or may not be covered in the original contract or the subsequent detailed technical specifications. In this case, all issue should be captured in a punch list as shown in this Appendix.
To prioritize all the issues, and to identify whether the system is ready for operation, each punch list item is classified into different seventies: Severity 1: This item is service-affecting in this deployment phase. Severity 2: This item is maintenance-affecting in this deployment phase. Severity 3: This item is service-affecting in the future deployment phases. Severity 4: This item is maintenance-affecting in the future deployment phases. The conditional acceptance can not be granted by the customers and the system can not enter trial/official operation unless all the severity 1 punch list item are closed.
Table B-1 Sample Punch List Format
Issues closed Issue raised for more than 30 days Issues raised for more than 20 days
No. Originato UTSI r Rcvd. 1 P.S. Guo 1-Sep Issue Name Brief Description
Severity 1 Critical: Phase 1 serv ice affecting Severity 2 Severe: Phase 1 maintenance affecting Severity 3 Major: Future phase service affecting Severity 4 Minor: Future phase maintenance affecting
UTSI Severit Done Contact y

3 10-Oct
Comments/Results
2 3
John Y. 28-Sep III

15-Oct
VPN feature Quote a schedule so Jeffery availability the FITEL can plan Zhang accordingly XXXX YYYY ZZ JJJ KKK LLL
2 2
N N
WW MMM
24
PAS PMDX Services Commissioning Test Procedure Appendix C: Complete Voice Network Acceptance Test Matrices
The matrices shown in this section is used to develop the detailed procedure in this document. This set of tables can be used as a reference for how each specific test was developed for the acceptance testing. The matrices paragraph references can be traced to reference documents [1], [2], [3], and [4].
Table C-1 Complete Voice Network Acceptance Test Matrices
The Matrix Please refer to Documentation: Appendix_matrix.xls
25

PAS PMDX Services Commissioning Test Procedure

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

PAS PMDX Services Commissioning Test Procedure

Hochgeladen von

Copyright:

Verfügbare Formate

PAS PMDX Services Commissioning Test Procedure