SSP_50578-RevC.docx

International Space Station Cargo Certification Process

International Space Station Program

Revision C

April 2018

National Aeronautics and Space Administration International Space Station Program Johnson Space Center Houston, Texas Contract Number: NNJ12GA46C

SSP XXXXX BASELINE

SSP 50578

Revision C

REVISION AND HISTORY PAGE

DCN 002 (Reference per SSCD 009556, Effective 08-12-05) Incorporates NDC 50578-003

Incorporates NDC 50578-004, 50578-005 and 50578-006 09-01-11

Incorporates NDC 50578-007 08-03-12

Incorporates NDC 50578-008, NDC 50578-009, and

NDC 50578-010

PREFACE

International Space Station Cargo Certification Process SSP 50578, International Space Station Cargo Certification Process document defines the responsibilities and processes for organizational interaction between the Russian and American Sides (hereinafter referred to as Sides) during the certification of cargo interfaces.

This bi-lateral document is developed and maintained by the Joint Cargo Certification Team coordinating with RSC-E through the Notice of Document Change (NDC) process. The processes for cargo certification are under the control of the MVCB. This document is under the control and approval authority of the Multilateral Vehicle Control Board (MVCB).

See Directive Approval

06-04-18

Dana Weigel Manager, Vehicle Office National Aeronautics and Space Administration

Date v

INTERNATIONAL SPACE STATION PROGRAM

International Space Station Cargo Certification Process

CONCURRENCE

April 2018

INTERNATIONAL SPACE STATION PROGRAM

International Space Station Cargo Certification Process

LIST OF CHANGES

April 2018 All changes to paragraphs, tables, and figures in this document are shown below:

MVCB

Entry Date

Change

Paragraph(s)

April 2002

Baseline

All

DCN 001

DCN 002

August 2011

Revision A

All

July 2012

Revision B

All

April 2018

Revision C

All

TABLE OF CONTENTS

APPENDIX

TABLE

FIGURE

INTRODUCTION

Certification is the process by which the compliance of hardware with its requirements is confirmed and documented. Certification of cargoes encompasses three components: safety, functional performance, and interface compatibility. The bilateral safety process is documented and agreed to in SSP 50146, Attachment D. Functional performance certification is the responsibility of the cargo developer. Certification of interface compatibility is conducted through the Joint Cargo Certification Team (JCCT) via processes defined in this document. The result of these three activities is the flight readiness report of the Russian and US sides during Stage Operations Readiness Review (SORR). This is illustrated in Figure 7.

PURPOSE

This document defines the responsibilities, documents, and processes for organizational interaction between the Russian and American Sides (hereinafter referred to as Sides) during the certification of cargo interfaces.

AREA OF APPLICATION

This document extends to:

Russian cargoes transported on all International Partner (IP) Vehicles, including cargoes delivered on U.S. commercial vehicles, Russian cargoes that are operated on the International Space Station (ISS) U.S. On-Orbit Segment (USOS) and IP modules, U.S. cargoes including IP cargoes flown as part of the National Aeronautics and Space Administration (NASA) allocation that are operated on the Russian Segment (RS) of the ISS, including cargoes delivered on U.S. commercial vehicles, U.S. cargoes including IP cargoes flown as part of the NASA allocation that are transported on Russian transport vehicles or modules.

SCOPE

This document governs the:

CONTENT

This document contains:

Manifest review protocols for cargo certification, Hardware protocols for interface certification, ISS cargo interface certificates, Summarizing conclusion on interface certification (certificate for SORR).

DOCUMENT CONTROL

This document is under the control of the Multilateral Vehicle Control Board (MVCB). All changes to this document must be approved by the MVCB through its standard change process.

SSP 50578

Revision C

4-1

ORGANIZATIONAL SYSTEM

PROGRAM STRATEGY

The ISS Program strategy provides for a review of the readiness of the launch package to be launched on a transport vehicle and for integration and utilization as part of the ISS. The cargo readiness process is a part of the overall program Certification of Flight Readiness (CoFR) process. SSP 50108, Certification of Flight Readiness Process Document, defines the readiness review process. The coordination of the cargo interface certification is the responsibility of the bilateral JCCT. The JCCT is a working appendage of the Multilateral Vehicle Control Board (MVCB). To support the ISS Program in performing the readiness review process CoFR, the JCCT must report information on verification completion for cargo interfaces. The charter for the JCCT is included in Attachment 5 of this document.

DEFINITIONS

This document utilizes the definition of the words “cargo” and “reflight” agreed to in document SSP 50146, Attachment D.

Mechanical interface: A mechanical interface may be classified as simple or complex. Simple mechanical interfaces include Velcro, bungee, nets, tape, standard mounting shoes for standard mounting brackets such as seat tracks and camera mounts etc., Complex mechanical interfaces include latching mechanisms, threaded fasteners, guide or alignment pins, pneumatic and hydraulic fittings or disconnects, etc., Digital data- Data that is expressed in digital form. (i.e. Binary, Octal, Hexadecimal numeric systems), Digital Interface- the part of a cargo item whose function is to exchange digital data with another (one or more) device with the same digital interface. The physical means for transmitting digital interface data may be a wire or wireless. Passive Portable Storage Devices (e.g. CDs, diskettes) are not included in this definition of digital interface, Wireless Digital Interface- a digital interface that transmits digital data without a wired connection with another such digital interface. Cargo items that have wireless interfaces are sometimes referred to as “Intentional Transmitters”. The frequency and field intensity levels emitted by the cargo are measured during radiated Electromagnetic Capability (EMI) testing. The results of this testing is analyzed for interface and electromagnetic compatibility. These interfaces can either meet an industry standard (example: 802.11g) or be custom designed (example: IWIS).

RESPONSIBILITIES

2.3.1 The JCCT will coordinate the activity of both sides during cargo certification by performing the following tasks:

Review the manifest and make a list of reflight cargoes, new cargoes, and new cargoes with interfaces to a segment or other cargo, Develop protocols for cargoes with interfaces to a segment or other cargo, Coordinate work listed in the protocol, Release interface certificates based on the results of test or analysis, Manage Yellow tag process, Adhere to responsibilities regarding digital interfaces as identified in U/R-A-005 (Attachment 4), Issue a summarizing conclusion for CoFR on interface certification (Figure 1).

Note:

The cargo supplier is responsible for complying with the receiving Side’s cargo requirements. The cargo supplier is responsible for the timely delivery of the technical documentation and hardware for the verification of interface compatibility.

The receiving Side is responsible for verifying interfaces whenever it is jointly agreed that verification is necessary. The receiving side is also responsible for the timely return of the hardware following completion of interface verification testing.

In cases when a cargo supplier uses a piece of equipment of a third side as part of his hardware assembly, the cargo supplier is responsible for the interface verification between his hardware equipment and the equipment of the third side. The side receiving the cargo supplier’s hardware assembly into its segment in this case takes responsibility for interface verification of this hardware with the modules of his segment.

ISSUE AND PROBLEM RESOLUTION

The organization of ISS cargo interface certification work presumes both an exchange of information within the framework of this document and close interaction between the Sides to find timely solutions to any issues that arise. The structure of the organizational system for interaction between the Sides in implementing work associated with cargo interface certification has several levels for resolving problems.

The first level of issue resolution is through discussion and information exchange by teleconference, fax, e-mail, or meetings between curators and hardware providers. The second level of issue resolution is through the JCCT. The third level of issue resolution is through Team 0. The fourth level of issue resolution is through the Program Managers.

JOINT ACTIVITIES OF THE SIDES

The joint activity of the Sides shall be performed within the scope of the JCCT via exchange of information by telephone, e-mail, or facsimile, and by holding regular meetings at NASA and Rocket Space Corporation-Energia (RSC-E).

Joint activities of the Sides within the framework of JCCT shall be directed at specific launch implementation, and it shall start with manifest review, which defines the cargo load for each cargo vehicle for the cargo having interfaces. For cargoes with complex interfaces, including scientific equipment, the cooperation may start at the stage of hardware development. In this case, the work shall be coordinated in general by Team 0 and the program directors of both sides, thereby ensuring the necessary coordination with other areas of work on the ISS Program and development of strategic (directive) decisions on its implementation.

During the stage when tests are prepared and conducted, the joint activities of the Sides is focused on coordinating testing documents, conducting the tests and issuing testing protocols as well as interface certificates.

CERTIFICATION OF CARGO TO BE TRANSFERRED

Cargoes can be transferred from one ISS segment (USOS, RS) to another for operation only if the receiving Side has certified this equipment in accordance with Section 3. During actual flight, situations may arise requiring real-time decisions on the use of equipment. Flight directors at Mission Control Center-Moscow and Mission Control Center-Houston will make these decisions, creating subsequently certification documentation.

CERTIFICATION OF REFLIGHT CARGO

A "reflight subassembly" is an item that meets 1) or 2) above and was certified as part of a higher assembly. A "reflight cargo" may be a reflight item or a reflight subassembly.

A list of the reflight cargoes with interfaces can be found in the “Cargo Manifest Review Protocol and Certificate” (see Section 3.1).

TECHNICAL REQUIREMENTS

GENERAL

The technical interface design requirements subject to interface verification are contained in the documents listed in Section 2.8.2. For all the listed documents, in the event of conflicts in requirements for ISS stowage and operation on any segment, the bilateral or multilateral agreements shall take precedence. For cargo during the launch phase, the documentation applicable to the launch vehicle requirements shall take precedence. Any conflicts shall be discussed and dispositioned by the JCCT through use of appropriate ISS Program boards. The partners will ensure that any changes to these documents are coordinated jointly and incorporated into appropriate documents. These documents will be under configuration control, and the most recent release will be available through ISS Program resources.

APPLICABLE DOCUMENTATION

DATA REVIEW STATUS AND CERTIFICATION TRACKING DATABASE

The JCCT will use a Database Mission Integration Database Application System (MIDAS) as a tool to record the data review status and track the certificates. Development and maintenance of this database is the responsibility of the U.S. side. Output reports from the database will be provided to both sides on a regular basis to support JCCT work. Reports will include as a minimum: Part number, Part name, Certificate number, type of interface, and notes.

JOINT CERTIFICATION PROCESS FOR CARGO

MANIFEST REVIEW

The JCCT reviews the manifest (SSP 54100 “Increment Definition and Requirements Document (IDRD)”, Annex 1, flight specific) for each flight and prepares a list of those items needing interface verification with another partner’s interfaces including reflight cargoes.

This review is done for each flight of any transport vehicle. The output of this review is a “Cargo Manifest Review Protocol and Certificate” (see Figure 1). This document includes reflight items existing certification numbers and additional interface verification information, if required, in accordance with Section 2.2.7. The numbering format is as follows: X-Y, where X=flight number and Y=document revision number. When manifest changes are approved, the JCCT revises this document to reflect the changes. The first version of the protocol is generally issued 4 months prior to launch and another version, if required, one week prior to SORR. Cargoes included in the manifest after issuance of the preflight version of the manifest, which is published 7-10 days before launch, are included as urgent cargoes. Certification of urgent cargoes is performed in accordance with Section 3.

All cargo will be screened to determine the necessity for interface verification. The side that is the cargo owner must provide information on whether there are interfaces which require joint certification.

HARDWARE PROTOCOL AND INTERFACE CERTIFICATION CONCLUSIONS

Based on the results of the manifest review (see Section 3.1), the cargo provider and the curator from the Partner’s side shall draw up “Hardware Protocol and Interface Certification Conclusion” (Figure 2) whose objective is to:

A concurred list of tasks and tests, such as those in Figure 5, will be included in Section 4 of the document. The JCCT will assist cargo providers in developing the document and related negotiating discussions. See Figure 2 for the “Hardware Protocol and Interface Certification Conclusion” format. The numbering format is as follows: X-Y-Z, where X=flight number, Y=equipment group number and Z=next unused number from previous group protocols.

If there is a mechanical interface, the protocol will specify the required verifications for this interface in accordance with Attachment 1 and Figure 10.

If there is a digital interface, the protocol will specify the required verifications for this interface in accordance with Attachment 3 and Figure 11, per agreement U/R-A-005 (Attachment 4).

After the “Hardware Protocol” is signed, the receiving Side issues the organizational document (for example, the Technical Decision (TP) at RSC-Energia) which governs all work set forth in the Protocol.

After successful completion of all interface verification testing for the hardware (containing one or more components), and signing of the test result document, the “Hardware Protocol and Interface Certification Conclusion” will be approved and signed by JCCT.

Cargo interface documentation may include procedural, engineering design, and technical operational documentation, along with protocols from working meetings and scientific and organizational documentation, which the Sides forward to each other or issue jointly. Both Sides, depending on the type and scope of testing and the hardware interface, determine the content of said documentation for specific cargoes. The content of the documentation to be provided in support of cargo certification will generally include the following:

The groups identified in paragraph 2.3 will determine the content of the necessary data for cargoes to be jointly verified. Any changes relevant to interfaces made to the above documentation after presentation to the other Side and prior to testing will be discussed by both Sides and provided to the other Side.

INFORMATION EXCHANGE AND CLARIFICATION

Section 3.3 describes the normal information to exchange to allow both sides to complete work. The JCCT facilitates the exchange of information, and conducts telecons and meetings to allow the sides to discuss the information, clarify it, and determine any need for additional information. The specialists from the cargo providing and receiving sides shall participate in telecons and meetings to assure real-time exchange of information to allow testing to start. In addition to the technical information, the US Side will create a Notice of Document Change (NDC) to SSP 50136 and SSP 50137 as necessary.

HARDWARE EXCHANGE

Both sides have internal paperwork and activity that must be complete to allow the shipping of hardware from one side to the other. Completion of shipping forms, customs forms, arrangement for transportation to one side, return transportation from that side, and security clearance is not defined and regulated by this document.

TESTING

After receiving the hardware, incoming inspection will be conducted as well as the necessary testing determined by the test procedure. See Section 4.0. All interface verification tests shall be defined in a single “Test Program and Methods” (Test Procedure) signed by both sides. Interface verification tests shall be planned such that all tests to be performed at a certain facility may be accomplished in a single trip.

If the results of testing identify problems which require hardware modification, the problems shall be stipulated in the test results protocol. If the testing in the American partner’s facility is performed on an electrically analogous unit, then the providing partner will test the actual flight unit and provide results of test items identified in Figure 9 to the American side. The American side will review such results and either comment or approve via facsimile message.

If the results of testing identify problems which require hardware modification, the problems shall be stipulated in the test results protocol. If the testing in the receiving partner’s facility is performed on an analogous unit, then the providing partner will test the actual flight unit and provide results of test items identified in Figure 11 to the receiving side. The receiving side will review such results and either comment or approve via facsimile message. If the full scope of testing was conducted on the analogous unit per Figure 11, the flight unit can be treated as a reflight cargo per Section 2.7.2 of this document and will only require a functional test prior to flight.

E. Testing for verification of other interfaces shall be in accordance with the requirements defined by the technical teams assigned in Section 2.3 to be responsible for those interfaces.

YELLOW TAGS

A “Yellow Tag” label will be attached to the item, or the container the item is in, to notify the crew that the item is not approved for on orbit operations until completion of certification. The “Yellow Tag” will be removed after the certification is complete. The bilateral agreement that defines the Yellow Tag process is located in Attachment 2. The NASA JCCT will coordinate lists of “yellow tag” items for each flight and will release the Yellow Tag List to the Multilateral community at approximately Launch minus seven days (L-7days).

Yellow Tagging of equipment on ISS that does not conform to quality and safety requirements (for example, dismantled failed units) which could pose a hazard to the crew shall be done in most cases with a physical Yellow Tag, added to the yellow tag list and tracked in the Inventory Management System (IMS). The onboard crew will complete the information on the physical yellow tag and attach it to the equipment per ground personnel instructions. If the equipment is inaccessible, the Yellow Tagged equipment will be added to the yellow tag list and tracked in IMS. (Note: This paragraph supersedes the sentence in U/R-A-003 Agreement in Attachment 2: “The use of yellow tags for purposes other than those described in this agreement is to be determined.

SUMMARY DOCUMENT

The JCCT will verify that the summary status of interface verification in the “Cargo Manifest Review Protocol and Certificate” is valid and prepare an updated version, if necessary, prior to Stage Operations Readiness Review (SORR). See Figure 1.

ALGORITHM OF THE JOINT CERTIFICATION PROCESS FOR CARGO

The algorithm of joint certification for cargo described in this document is presented in the form of a flowchart in Figure 6. This flowchart is based on the following assumptions:

3.8.10 For reflight cargoes, the receiving Side’s curators shall verify applicability of previously issued hardware certificates for said flight.

3.8.11 JCCT work per this algorithm for a specific launch is complete only after the certificate is provided to the SORR, all open issues are closed, and all “Yellow Tags” are removed from the cargo of that launch.

3.8.12 If hardware/software testing is required in the Partner country the hardware provider should initiate the request to update the following documents: NASA/RSA Bilateral Hardware and Software Exchange Agreements, List, and Schedules (BHSEALS - SSP50136) and NASA/RSA Bilateral Data Exchange Agreement List and Schedule (BDEALS - SSP50137).

PROCEDURE FOR PREPARING AND CONDUCTING TESTS FOR CARGO

PROCESS FOR TESTING CARGO

The cargo interface verification process consists of two parts: verification analysis and the required testing. The acceptability of verification by analysis shall be based on the cargo documentation review. This type of verification is applicable to any type of cargo. For some cargoes, this method of verification, as a rule, will be the only technique required to accept the cargo for delivery to the ISS. This will be determined by the JCCT.

Both sides have existing analysis and verification activities that include qualification and acceptance testing, as well as pre- and post-ship inspections. The need for specific types of test or analysis data that may not be a part of the existing verification plans is to be identified based upon the requirements in Section 2.0. To comply with the requirements in Section 2.0, some additional testing or analyses may be required. However, should there be any special need for additional test or analysis data, this need will be identified through the JCCT and a list of such tests or analyses will be reflected in the “Hardware Protocol” concurred with by both Sides.

Each stage of testing is designed to accomplish certain tasks as follows:

QUALIFICATION TESTS

The content of qualification tests to be performed on a qualification article of the equipment should confirm its compliance with the documents specified in Section 2.8.2. By agreement between the Sides, individual qualification tests can be performed with participation of the other Side’s specialists if necessary and agreed to by the JCCT, and approved by Program Management. Hardware qualification tests must generally be completed and appropriate data exchanged before the acceptance and interface tests begin.

HARDWARE INTERFACE ACCEPTANCE TESTS

The interface acceptance tests shall be performed in the hardware manufacturer country’s facility. By agreement between the Sides, individual interface acceptance tests can be performed with participation of the other Side’s specialists if necessary and agreed to by the JCCT, and approved by Program Management.

INCOMING INSPECTION AND INTERFACE ACCEPTANCE TESTING WITH THE RECEIVING SIDE

When hardware is sent to the other side’s facilities for testing, incoming inspection and interface acceptance testing will be performed. A complete set of documents, according to Section 3.3, required to support the performance of an incoming inspection and hardware interface acceptance test shall be submitted to the other Side for concurrence no later than 1 month before the incoming inspection and interface acceptance test begins. The schedule shall be in accordance with the approved schedule of operations. The list of documents for submission must be agreed to by the Sides. The Sides will separately agree upon any exceptions to this rule.

An incoming inspection and interface acceptance test shall be performed when the hardware arrives at the testing complex or facility. The incoming inspection and interface acceptance tests shall always be performed with the participation of the facility owner and the hardware provider unless otherwise agreed.

The program and procedure for incoming inspection and interface acceptance testing are developed and concurred before the equipment is shipped to the Receiving Side. The program and procedure provide for the following operations:

INTEGRATED INTERFACE TEST

An integrated interface test shall be conducted at the partner’s test facility in accordance with the concurred procedure. The tests shall be performed with the joint participation of the facility owner and the hardware provider. During the integrated tests, hardware interfaces with onboard systems shall be checked.

Appendix a - Acronyms and abbreviations

Appendix b - glossary None

Appendix c - open work Table C-1 lists the specific To Be Determined (TBD) items in the document that are not yet known. The TBD is inserted as a placeholder wherever the required data is needed and is formatted in bold type within brackets. The TBD item is numbered based on the section where the first occurrence of the item is located as the first digit and a consecutive number as the second digit (i.e., <TBD 4-1> is the first undetermined item assigned in Section 4 of the document). As each TBD is solved, the updated text is inserted in each place that the TBD appears in the document and the item is removed from this table. As new TBD items are assigned, they will be added to this list in accordance with the above described numbering scheme. Original TBDs will not be renumbered.

Table C-1 to be determined items

Table C-2 lists the specific To Be Resolved (TBR) issues in the document that are not yet known. The TBR is inserted as a placeholder wherever the required data is needed and is formatted in bold type within brackets. The TBR issue is numbered based on the section where the first occurrence of the issue is located as the first digit and a consecutive number as the second digit (i.e., <TBR 4-1> is the first unresolved issue assigned in Section 4 of the document). As each TBR is resolved, the updated text is inserted in each place that the TBR appears in the document and the issue is removed from this table. As new TBR issues are assigned, they will be added to this list in accordance with the above described numbering scheme. Original TBRs will not be renumbered.

table C-2 TO BE RESOLVED ISSUES

D-7

Appendix d – FIGURES AND Attachments

Figure 1: Cargo Manifest Review Protocol and Certificate 1 of 3

Figure 1: Cargo Manifest Review Protocol and Certificate 2 of 3

Figure 1: Cargo Manifest Review Protocol and Certificate 3 of 3

Figure 2: Hardware Protocol and Interface Certification CONCLUSION (1 of 3)

(2 of 3)

(3 of 3)

This Figure Intentionally Left Blank

Figure 3: Interface Certificate

This Figure Intentionally Left Blank

Figure 4: Summary Document

Standard Table of Tasks for Electrical Power Interface Testing

1. Check of Hardware Completeness (Inventory)

2. Visual Inspection (Post-Shipment)

3. Check of Technical Documentation Completeness and Quality

4. Insulation Electrical Resistance Check

5. Insulation Electrical Strength Check

6. Starting Current Amplitude Check

7. Check of Energy Consumption in Operating Mode

8. Ground Continuity Check

9. Functionality Check (Post/Pre-shipment Health Check)

10. Functionality Check (Performed on Flight Electrical Analogous Test Stand)

11. Packing Check

Notes:

Test 1 performed in Providing country facility Test 2 performed in receiving country facility Figure 5: Standard Electrical Tests and Tasks

Figure 6 Algorithm of the Joint Certification Process for Cargo (Page 1 of 2)

Figure 6 Algorithm of the Joint Certification Process for Cargo (Page 2 of 2)

Revision C

D-9

CoFR

CoFR

CoFR

CoFR

Software Interface

MASCB

Interface Compatibility

JCCT

Cargo Functional Performance

NASA/RSC-E

Safety

SRP/JARSWG

Cargo Certification

Figure 7 General Joint Certification Process for Cargo

Figure 8 - Intentionally left blank. The Table of Acronyms was moved to Appendix A Figure 8 General Joint Certification Process for Cargo

SSP 50578

D-28

Requirement

Power Quality – SSP 52051, User Electric Power Specifications and Standards Volume 2 (Multi-Segment, Portable, 28 Volt DC Equipment)

Grounding & Bonding – SSP 30245 (Class S)

Total Path Continuity

Circuit Protection

Notes:

Figure 9 Standard Electrical Interface Tests and Tasks for Portable Equipment Interfacing with US ISS 28 Volt Power Sources

Attachment to the Protocol on Mechanical Interface Verification of Cargoes with the Partner's Vehicle or Segment.

No.

For verification of the cargo mechanical interface with the partner's vehicle (segment) the partner requests that:

1. The following must be submitted by the cargo provider:

Dimensional installation drawing to scale, with center of gravity location, moments of inertia with corresponding axes identified, and loading constraints.

Baseline data to determine the procedures for conducting an incoming inspection of the cargo at partner's processing facility.

List of additional equipment needed to unpack (and pack if needed), prepare, package and install the cargo into the partner's vehicle (segment). The cargo provider will deliver all fasteners and tools required for the installation into the partner's vehicle (segment).

A document describing the methods and procedures used for structural tests which have been performed.

The results of the tests and analyses used to confirm that the cargo's structural characteristics and its interface with the partner's vehicle (segment) frame (structure) are in compliance with the applicable requirements, with lowest margins of safety for the interface structure listed with the corresponding locations identified.

2. The following to be concurred with the partner:

Dimensional installation drawing.

Procedures for conducting an incoming inspection at a partner's processing facility.

Procedures for installing and removing the cargo from the partner's vehicle, transferring it to the ISS location of its utilization, and for installing it on the partner's segment.

Procedures for removing and reinstalling the cargo in the ground transport container.

Procedures for handling the cargo outside the shipping container.

Lowest margins of safety and their locations for the cargo/frame (structure) integrated assembly.

Figure 10 Attachment to the Protocol on Mechanical Interface Verification of Cargoes with the Partner's Vehicle or Segment

Table of Standard Digital Interface Certification Tasks