Microsoft Office User 2026-03-13T10:28:40+00:00 Calc LibreOffice 7.3 tetml={filename={D:\Drim\repository\projects\drim_66_0\metadata\5\d\5d5d21b294ca3d5fd953cbf8e24cd126\5d5d21b294ca3d5fd953cbf8e24cd126.tet.xml} elements={annotations=false bookmarks=false destinations=false fields=false javascripts = false} } granularity=word contentanalysis={punctuationbreaks=false dehyphenate=false} layoutanalysis={tabledetect=0 layoutdetect=0} Compliance status Proposed text Criticality Parent heading Compliant (STD) Novatra Systems Technical Component NA Compliant (STD) Requirement Specifications: NA Compliant (STD) Overhead Access Module (OAM) Project Series: CX90, CX91 NA Not Applicable/Not Relevant Doc NST-512873 Number: These NST-2025-00024 module requirement specifications NA 1 Introduction (NST-467451) Not Applicable/Not Relevant (German: NST-4764956 KLH) For define reasons the technical of linguistic and simplicity, procedural references to NA 1 Introduction (NST-467451) Not Applicable/Not Relevant individuals NST-467449 may Within appear this in document, the masculine the term form. “shall” All references, is to be NA 1 Introduction (NST-467451) Not Applicable/Not Relevant interpreted NST-467450 as Together equivalent with to the “must”. supporting documentation NA 1.1 Document Landscape (NST-467449) Not Applicable/Not Relevant referenced NST-467451 herein, References these to specifications other documents constitute are provided the binding NA 1.1 Document Landscape (NST-467449) Compliant (STD) square NST-467457 brackets, This e.g. document [LHV 310 is generated 00x]. Such directly documents from are the listed NA 1.1.1 Document Creation (NST-467456) Compliant (STD) requirements NST-467454 Each management content element system is maintained assigned a by unique Novatra NA 1.1.1 Document Creation (NST-467456) Compliant (STD) • identifier ID aligned (ID) left, for text traceability. aligned right IDs may (requirement) appear in the following NA 1.1.1 Document Creation (NST-467456) Compliant (STD) • ID placed directly below the requirement text NA 1.1.1 Document Creation (NST-467456) Compliant (STD) • ID shown in brackets after a heading NA 1.1.1 Document Creation (NST-467456) Compliant (STD) NST-867453 The Integrator may also receive requirements NA 1.1.1 Document Creation (NST-467456) Compliant (STD) through NST-1079018 database Italicized export text packages. within a PDF export indicates NA 1.1.1 Document Creation (NST-467456) Clarification Required classification NST-467458 The metadata document associated “Common with Requirements the requirement ID. NA 1.1.2 Common Requirements (NST-467455) Compliant (STD) Pertaining NST-467462 to In the case Component of discrepancies Specifications” between [LHV this 310 00x] NA 1.1.2 Common Requirements (NST-467455) Compliant (STD) specification NST-467459 Chapters and the Common or clauses Requirements in [LHV 310 00x] [LHV are 310 00x], NA 1.1.2 Common Requirements (NST-467455) Compliant (STD) referenced NST-467460 by CRCS-3339913 their requirement in the ID Common rather than Requirements chapter NA 1.1.2 Common Requirements (NST-467455) Compliant (STD) describes NST-467464 structural For each updates sourcing to scope, the specification the Integrator template. receives a NA 1.1.3 Logistics Component Requirement Specifications (NST- Compliant (STD) corresponding NST-4750936 For Logistics each sourcing Requirement scope, Specification the Client’s [LOG Purchasing KLH], NA 467465) 1.1.3 Logistics Component Requirement Specifications (NST- Compliant (STD) Department <table border="1"><tr><th provides a logistics cellId="1524241" framework. This style="text- framework is NA 467465) Table 1: Test Parameters Compliant (STD) align:center">Tape NST-6750936 The components width<br>mm</th><th described in cellId="1524242" this section are NA 2.1.3 System Context (NST-467962) Clarification Required part PV_LCH-43752 of the Celura The Illumination LCH consists Network of a Prime (CIN) Controller located within Node 3 2.1.4 Requirements for Components Involved 2.1.4.1 Open (PCN) PV_LCH-43768 and multiple The Optic LCH receives Flow Arrays control (OFAs). instructions The OFAs through are NA Component 2.1.4 Requirements Contribution for Components – Luminara Involved Control Hub 2.1.4.1 (LCH) Compliant (STD) the PV_LCH-43715 LNX Communication Colors are Layer transmitted (LNX- as Trispectrum (RGB) NA Component 2.1.4 Requirements Contribution for Components – Luminara Involved Control Hub 2.1.4.1 (LCH) Compliant (STD) values. PV_LCH-43711 Each SLPU Target computes light images the required may be pulse-width transmitted to the NA Component 2.1.4 Requirements Contribution for Components – Luminara Involved Control Hub 2.1.4.1 (LCH) Compliant (STD) PV_LCH-43720 and subsequently The PCN forwarded must be able to the to SLPUs. control Execution a configurable can NA Component 2.1.4.1.1 Component Contribution Tasks – Luminara (PV_LCH-43746) Control Hub (LCH) Clarification Required subset PV_LCH-43739 of TSEs within Up to n the SLPUs OFAs may via be the deployed. assigned SLPUs. The number of NA 2.1.4.1.1 Component Tasks (PV_LCH-43746) Compliant (STD) TSEs PV_LCH-43760 (m) must be The allocated PCN transmits using the display parameter commands to the NA 2.1.4.1.1.1.2 Communication (PV_LCH-43707) Compliant (STD) relevant PV_LCH-43744 SLPUs. For These reliability, are addressed identical according user data to may the be LNX-CL NA 2.1.4.1.1.1.2 Communication (PV_LCH-43707) Compliant (STD) cyclically PV_LCH-43692 re-sent All (e.g., required every signals 500 ms) for if LCH no new and instructions SLPUs, along are NA 2.1.4.1.1.1.2 Communication (PV_LCH-43707) Compliant (STD) with PV_LCH-43698 their expected The LCH behavior, is addressed are specified via the in LNX-CL the schedule, NA 2.1.4.1.1.1.2 Communication (PV_LCH-43707) Compliant (STD) with PV_LCH-43728 each SLPU The allocated LCH must a dedicated evaluate data the LNX-CL set. schedule to NA 2.1.4.1.1.1.2 Communication (PV_LCH-43707) Compliant (STD) determine PV_LCH-43705 which Up SLPU-specific to 16 SLPUs can data be is addressed relevant for execution. NA 2.1.4.1.1.1.2 Communication (PV_LCH-43707) Compliant (STD) simultaneously. PV_LCH-43763 This Each addressing must be assigned is configured an individual via the parameter fixed NA 2.1.4.1.1.1.2 Communication (PV_LCH-43707) Open PALC_SLPU-n-address_[n]=[1…16]. (Requirement reserved for addressing-specific definitions, 4 2.1.4.1.1.1.3 Addressing (PV_LCH-43742) Compliant (STD) already 2.1.4.1.1.1.4 aligned Control with LNX-CL of Color addressing (PV_LCH-13702) scheme.) PV_LCH-43723 NA 2.1.4.1.1.1.3 Addressing (PV_LCH-43742) Compliant (STD) Color PV_LCH-43713 transmission The occurs LCH must via the convert “Trispectrum the received color Trispectrum value” NA 2.1.4.1.1.1.3 Addressing (PV_LCH-43742) Compliant (STD) color PV_LCH-43762 value into Elementary the calibrated color target red shall color. be displayed at NA 2.1.4.1.1.1.3 Addressing (PV_LCH-43742) Compliant (STD) values PV_LCH-43691 = 4094/0/0, Elementary activating color only green the red shall chip be of displayed the TSE at NA 2.1.4.1.1.1.3 Addressing (PV_LCH-43742) Compliant (STD) values PV_LCH-43735 = 0/4094/0. If an PV_LCH-43755 IDLE value is received, Elementary the color LCH must blue shall NA 2.1.4.1.1.1.3 Addressing (PV_LCH-43742) Compliant (STD) disregard PV_LCH-43734 the corresponding If a color value command falls outside without the set interrupting of valid IDs NA 2.1.4.1.1.1.3 Addressing (PV_LCH-43742) Compliant (STD) defined 2.1.4.1.1.1.5 by the Brightness Client, the Control LCH must (PV_LCH-43738) discard the command. PV_LCH- 2 2.1.4.1.1.1.3 Addressing (PV_LCH-43742) Clarification Required 43710 PV_LCH-43745 Brightness The is LCH controlled shall perform via the linear “Trispectrum interpolation brightness 3 2.1.4.1.1.1.6 Dimming Behavior (Interpolation) (PV_LCH- Compliant (STD) between PV_LCH-43695 values Interpolation transmitted by can the be PCN enabled at 6.25 or disabled fps up to via 100 NA 43719) 2.1.4.1.1.1.6 Dimming Behavior (Interpolation) (PV_LCH- Compliant (STD) the PV_LCH-43743 “Execution request” Additional signal. details on interpolation are provided NA 43719) 2.1.4.1.1.1.6 Dimming Behavior (Interpolation) (PV_LCH- Compliant (STD) in 2.1.4.1.1.1.7 the technical Memory lighting Management content section (PV_LCH-43716) of the KLH. PV_LCH- NA 43719) 2.1.4.1.1.1.6 Dimming Behavior (Interpolation) (PV_LCH- Compliant (STD) 1. 43697 Executing The LCH working shall provide memorytwo distinct memory areas: NA 43719) 2.1.4.1.1.1.6 Dimming Behavior (Interpolation) (PV_LCH- Compliant (STD) 2. Buffer memory NA 43719) 2.1.4.1.1.1.6 Dimming Behavior (Interpolation) (PV_LCH- Compliant (STD) PV_LCH-43766 Light images must be preloaded into the buffer NA 43719) 2.1.4.1.1.1.6 Dimming Behavior (Interpolation) (PV_LCH- Compliant (STD) memory PV_LCH-43733 independently A command of data defined the in executing the .ldf file memory. shall be used NA 43719) 2.1.4.1.1.1.6 Dimming Behavior (Interpolation) (PV_LCH- Compliant (STD) to PV_LCH-51002 transfer preloaded Different images execution from the types buffer are available, into executing NA 43719) 2.1.4.1.1.1.8 Execution Request (PV_LCH-51001) Compliant (STD) defining PV_LCH-51003 how the The LCH execution processes type incoming is transmitted instructions. via the NA 2.1.4.1.1.1.8 Execution Request (PV_LCH-51001) Compliant (STD) “Execution PV_LCH-51005 request” When signal. set to IDLE, the addressed LCH shall NA 2.1.4.1.1.1.8.1 IDLE (PV_LCH-51004) Compliant (STD) ignore PV_LCH-51006 all user data Note: in The the IDLE received mode request. is primarily Ongoing used for NA 2.1.4.1.1.1.8.1 IDLE (PV_LCH-51004) Compliant (STD) synchronization PV_LCH-51008 All of SLPUs individual shall sequences. transfer data stored in buffer NA 2.1.4.1.1.1.8.2 EXE (PV_LCH-51007) Compliant (STD) memory PV_LCH-51010 into working All SLPUs memory shall transfer and begin received interpolated data into NA 2.1.4.1.1.1.8.3 LOAD (PV_LCH-51009) Compliant (STD) buffer <table memory border="1"><tr><td when the value cellId="1524262" = LOAD. Ongoing style="text- operations NA 2.1.4.1.1.1.8.3 LOAD (PV_LCH-51009) align:center" colspan="2"></td><td cellId="1524263" Compliant (STD) 2.1.4.1.1.1.8.4 NDEF & SNA (PV_LCH-51011) PV_LCH-51012 NA 2.1.4.1.1.1.8.3 LOAD (PV_LCH-51009) Compliant (STD) The PV_LCH-51013 must interpret If the value value = NDEF/SNA, range 2…3 the as NDEF LCH shall (Not ignore NA 2.1.4.1.1.1.8.3 LOAD (PV_LCH-51009) Compliant (STD) or 2.1.4.1.1.1.9 discard all Initialization information in After the Reset execution (PV_LCH-51014) request. Ongoing PV_LCH- NA 2.1.4.1.1.1.8.3 LOAD (PV_LCH-51009) Compliant (STD) • 51015 Trispectrum After a restart, value = the 0 / 0 LCH / 0shall initialize buffer memory NA 2.1.4.1.1.1.8.3 LOAD (PV_LCH-51009) Compliant (STD) • Execution type = IDLE NA 2.1.4.1.1.1.8.3 LOAD (PV_LCH-51009) Compliant (STD) • Interpolation = OFF NA 2.1.4.1.1.1.8.3 LOAD (PV_LCH-51009) Compliant (STD) PV_LCH-51017 The time since the last valid message must be NA 2.1.4.1.1.1.10 Function Aborted Due to Timeout (PV_LCH- Non-Compliant monitored. PV_LCH-51018 Each If valid the monitored message resets time exceeds the timer a configurable to 0. 5 51016) 2.1.4.1.1.1.10 Function Aborted Due to Timeout (PV_LCH- Compliant (STD) parameter 2.1.4.1.2.1.1.1 (0…3600s, Signal – with Color 0 = Request timer disabled), (PV_LCH-51022) the current NA 51016) 2.1.4.1.2.1.1 LNX-CL (PV_LCH-51021) Compliant (STD) PV_LCH-51023 PV_LCH-51024 Description: The corresponding Defines 12-bit color/brightness Trispectrum request (R / G / NA 2.1.4.1.2.1.1 LNX-CL (PV_LCH-51021) Compliant (STD) B) PV_LCH-51026 values are transmitted Description: via Defines the signal: the execution mode for NA 2.1.4.1.2.1.1.2 Signal – Execution Request (PV_LCH-51025) Compliant (STD) PV_LCH-51029 the LCH. PV_LCH-51027 The output The interface execution is described request is in transmitted the KLH. NA 2.1.4.1.2.2 Output Interface (PV_LCH-51028) Compliant (STD) PV_LCH-51031 See EE KLH of the LCH. NA 2.1.4.1.3 Voltage Range / Current Values / Power Compliant (STD) NST-51035 Each function description contains preconditions, NA Specifications 2.1.5.1.1 Notes (PV_LCH-51030) on the Following Function Descriptions (NST- Compliant (STD) prerequisites, NST-51036 Precondition: triggers, abort A condition conditions, required and end before conditions. a NA 51034) 2.1.5.1.1 Notes on the Following Function Descriptions (NST- Compliant (STD) function NST-51037 is initiated. Functional It may prerequisite not remain without valid triggering throughout role: A NA 51034) 2.1.5.1.1 Notes on the Following Function Descriptions (NST- Compliant (STD) condition NST-51038 that Functional must hold prerequisite true throughout with triggering execution role: but A NA 51034) 2.1.5.1.1 Notes on the Following Function Descriptions (NST- Compliant (STD) prerequisite NST-51039 Functional that, in combination trigger: An with event a that trigger, initiates activates the the NA 51034) 2.1.5.1.1 Notes on the Following Function Descriptions (NST- Compliant (STD) • function. Flank-based: only on change (e.g., button press). NA 51034) 2.1.5.1.1 Notes on the Following Function Descriptions (NST- Compliant (STD) • Status-based: constant condition (e.g., manual switch ON). NA 51034) 2.1.5.1.1 Notes on the Following Function Descriptions (NST- Compliant (STD) NST-51040 Abortion condition: An explicit condition that NA 51034) 2.1.5.1.1 Notes on the Following Function Descriptions (NST- Compliant (STD) aborts NST-51041 execution End condition: immediately When (e.g., fulfilled, opposite the command function input). NA 51034) 2.1.5.1.1 Notes on the Following Function Descriptions (NST- Compliant (STD) terminates NST-51042 Logical as planned dependencies (e.g., end position between reached). conditions must be NA 51034) 2.1.5.1.1 Notes on the Following Function Descriptions (NST- indicated (AND / OR). 51034) granularity=word contentanalysis={punctuationbreaks=false dehyphenate=false} layoutanalysis={tabledetect=0 layoutdetect=0} Compliant (STD) NST-51044 The component shall support multiple power NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) states: 1. Sleep Mode – All peripheral elements off, current NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) consumption 2. On Mode – within Component sleep limits. fully active; periphery powered, NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) communication 3. Power Safe Mode active, – Activated light sources if brightness enabled on = 0 request. for a duration NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) a. defined Recovery in PLCH_PowerSafe_[t]. to active mode must Non-essential occur in <100 submodules ms. are NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) b. Communication remains active unless LNX-CL enters sleep. NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) c. If LNX-CL sleep occurs without timeout, the component also NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) enters d. If LNX-CL Sleep timeout Mode. occurs, all periphery must shut down and NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) Mode. enter Sleep NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) e. Diagnostic mode entry from Power Safe Mode must be NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) possible. 4. Communication Off Mode – If brightness > 0 while LNX-CL is NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) a. in A sleep, timer the starts LEDs when remain LNX-CL active enters in the sleep. last set NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) b. If no valid LNX-CL message is received before NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) PLCH_CoMtimeout_[t] c. Every valid message resets expires, the the timer system (including enters “idle” Sleep Mode. NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) messages). d. Parameter PLCH_CoMtimeout_[t] is distinct from the NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) standard e. Diagnostic LNX-CL mode timeout. entry from Communication Off Mode must NA 2.1.5.1.2 Power Status Management (NST-51043) Compliant (STD) be NST-52002 possible.The Integrator shall provide a valid Supplier-ID to NA 2.1.5.1.3 LNX-CL Performance (NST-52001) Compliant (STD) the NST-52003 Client. If The such component an ID is not shall available, support the a baud Integrator rate of shall 19.2 NA 2.1.5.1.3 LNX-CL Performance (NST-52001) Compliant (STD) kbaud. NST-52004 Note: Timing intervals are defined to ensure that NA 2.1.5.1.3 LNX-CL Performance (NST-52001) Compliant (STD) user NST-52005 actions The are component executed without shall be perceptible capable of delay. waking up NA 2.1.5.1.3 LNX-CL Performance (NST-52001) Compliant (STD) within NST-52006 ms At the from latest, Sleep the Mode second to perform Prime Controller a requested Node NA 2.1.5.1.3 LNX-CL Performance (NST-52001) (PCN) request in the functional schedule must be evaluated Compliant (STD) NST-52008 The component shall implement the LNX-CL signal NA 2.1.5.1.4 LNX-CL Signals (NST-52007) Compliant (STD) interface NST-52010 in During compliance initial with startup, the current each Photon LDF (LNX Driver description (PD) shall NA 2.1.5.1.5 Photon Driver Initialization (NST-52009) Compliant (STD) store NST-52011 its assigned If the selected address in PDs non-volatile do not support memory. non-volatile NA 2.1.5.1.5 Photon Driver Initialization (NST-52009) Compliant (STD) storage NST-52012 (e.g., Each state time machine the component limitations), powers the following on (from Sleep, NA 2.1.5.1.5 Photon Driver Initialization (NST-52009) Compliant (STD) Power NST-52013 Safe During Mode, initialization, or after interruptions), the internal all master PD addresses logic shall NA 2.1.5.1.5 Photon Driver Initialization (NST-52009) Compliant (STD) ensure NST-52014 that The all PDs expected are properly number addressed of PDs or and communication synchronized. NA 2.1.5.1.5 Photon Driver Initialization (NST-52009) Compliant (STD) slaves NST-52015 per OFA If the shall detected be derived PDs deviate from coding from parameters the expected and NA 2.1.5.1.5 Photon Driver Initialization (NST-52009) Compliant (STD) count, NST-52016 the system No Trispectrum shall broadcast Emitters a configuration (TSEs) shall activate error on the NA 2.1.5.1.5 Photon Driver Initialization (NST-52009) Compliant (STD) during NST-52017 initialization, The Integrator and no shall visual design feedback the electronic is permitted. circuitry NA 2.1.5.1.5 Photon Driver Initialization (NST-52009) Compliant (STD) to NST-52019 prevent voltage This function dips at is the triggered PD power via the supply diagnostic that could NA 2.1.5.1.5.1 Initialization Routine (NST-52018) Compliant (STD) interface. NST-52021 NST-52020 This function It shall shall be run implemented as a synchronous as the routine, DiagExec NA 2.1.5.1.5.1 Initialization Routine (NST-52018) Compliant (STD) since NST-52022 execution The routine may exceed shall 60 only seconds. run if explicitly invoked via NA 2.1.5.1.5.1 Initialization Routine (NST-52018) Compliant (STD) the NST-52023 diagnostic If regular interface. addressing is required, visual feedback NA 2.1.5.1.5.1 Initialization Routine (NST-52018) Compliant (STD) NST-52025 shall only be An provided extended when diagnostic the diagnostic session service must be is active. externally NA 2.1.5.1.5.1.1 Precondition (NST-52024) Compliant (STD) NST-52027 The routine shall be invoked through the diagnostic NA 2.1.5.1.5.1.2 Function Trigger (NST-52026) Compliant (STD) interface NST-52029 using The the PCN corresponding shall readdress execution all internal command slaves or NA 2.1.5.1.5.1.3 Function Execution (NST-52028) Compliant (STD) Photon NST-52030 Drivers All monitoring both left functions and right must OFAs remain via the active internal during bus NA 2.1.5.1.5.1.3 Function Execution (NST-52028) Compliant (STD) the NST-52032 routine.The function shall be aborted if a stopRoutine NA 2.1.5.1.5.1.4 Abortion Condition (NST-52031) Compliant (STD) NST-52034 command is The received function via execution the diagnostic shall interface. conclude normally. NA 2.1.5.1.5.1.5 End Condition (NST-52033) Compliant (STD) NST-52035 If monitoring concludes with a fault, the respective NA 2.1.5.1.5.1.5 End Condition (NST-52033) Compliant (STD) failure NST-52036 signal After shall completing be transmitted. the initialization routine, the NA 2.1.5.1.5.1.5 End Condition (NST-52033) Compliant (STD) component • If successful: shall all provide TSEs illuminate visual feedback GREEN at through full brightness the TSEs:for NA 2.1.5.1.5.1.5 End Condition (NST-52033) Compliant (STD) 10 • If seconds. a fault occurs: all TSEs blink RED at full brightness, 0.5 Hz NA 2.1.5.1.5.1.5 End Condition (NST-52033) Compliant (STD) for • If 10 partial seconds. operation only is possible, the maximum available NA 2.1.5.1.5.1.5 End Condition (NST-52033) Compliant (STD) TSEs NST-52037 shall activate. The return value shall be sent when the addressing NA 2.1.5.1.5.1.5 End Condition (NST-52033) Open routine NST-52038 completes, Definitions though of the visual Trispectrum feedback colors may continue (GREEN, RED, NA 2.1.5.1.5.1.5 End Condition (NST-52033) Open BLUE) NST-52042 are described All requirements in Chapter for 10229574: Trispectrum Lighting Emitters Function. (TSEs) NA 2.1.5.1.6.1.1 General Light Source Requirements (NST-52041) Compliant (STD) and NST-52044 their RGB The values positioning are valid and only design if TSEs of the are component, installed in the NA 2.1.5.1.6.1.2 Assembly Integration Requirements (NST-52043) Open including NST-52045 integration, The Integrator must must be coordinated align material with and the color Client. NA 2.1.5.1.6.1.2 Assembly Integration Requirements (NST-52043) Compliant (STD) properties NST-52046 of Any surrounding surrounding components materials (affecting visibility optical must NA 2.1.5.1.6.1.2 Assembly Integration Requirements (NST-52043) Compliant (STD) be NST-52047 coordinated All interfaces with the development shall be validated. authority NST-52048 prior to Carry- blank NA 2.1.5.1.6.1.2 Assembly Integration Requirements (NST-52043) Compliant (STD) over NST-52049 interfaces Design must and be development validated for implementation each release cycle. must be NA 2.1.5.1.6.1.2 Assembly Integration Requirements (NST-52043) Compliant (STD) coordinated NST-52050 In with the all Client’s adjacent Cooperation modules.Kickoff Meeting, NA 2.1.5.1.6.1.2 Assembly Integration Requirements (NST-52043) Compliant (STD) milestones NST-52052 (e.g., Light sources blank or must tool release) comply with shall AEC-Q be coordinated automotive NA 2.1.5.1.6.1.3 Light Source Requirements (NST-52051) Compliant (STD) certification. NST-52053 Final light source selection (including binning) must NA 2.1.5.1.6.1.3 Light Source Requirements (NST-52051) Compliant (STD) be NST-52054 approved Light by the source Client’s datasheet development limits must team. not be NA 2.1.5.1.6.1.3 Light Source Requirements (NST-52051) Compliant (STD) exceeded. NST-52055 Real-world Light sources boundary shall not conditions emit radiation shall be in the validated NA 2.1.5.1.6.1.3 Light Source Requirements (NST-52051) Open ultraviolet NST-52056 range. Light sources must be safeguarded against NA 2.1.5.1.6.1.3 Light Source Requirements (NST-52051) Open excessive NST-52057 self-heating The design and must external allow replacement heating. of a light NA 2.1.5.1.6.1.3 Light Source Requirements (NST-52051) Open source NST-52058 with Second-source an equivalent from alternatives another must manufacturer be identified (form, and NA 2.1.5.1.6.1.3 Light Source Requirements (NST-52051) Compliant (STD) validated NST-52059 without Production further processes modification. (e.g., pick-and-place vacuum NA 2.1.5.1.6.1.3 Light Source Requirements (NST-52051) Compliant (STD) pipettes) NST-52060 must Lighting be suitable concepts for shall TSEs prioritize and approved designs by that the avoid NA 2.1.5.1.6.1.3 Light Source Requirements (NST-52051) Compliant (STD) additional 2.1.5.1.6.1.3.1 calibration Defect (brightness and Deactivation or color) of Multi-Emitter during Light NA 2.1.5.1.6.1.3 Light Source Requirements (NST-52051) Compliant (STD) Sources NST-6359123 (NST-6359121) If a single NST-6359122 emitter within Any a Trispectrum defect occurring Emitter in NA 2.1.5.1.6.1.3 Light Source Requirements (NST-52051) Compliant (STD) (TSE) NST-6359124 or pixel is Following defective, detection, this failure the must affected be detected. multi-emitter NA 2.1.5.1.6.1.3 Light Source Requirements (NST-52051) Compliant (STD) TSE NST-6359125 / pixel shall Strategies be automatically for handling deactivated. multiple defects shall be NA 2.1.5.1.6.1.3 Light Source Requirements (NST-52051) Compliant (STD) coordinated <table border="1"><tr><th with the client cellId="1524213" (Novatra Systems). style="text- NA Table 2: Temperature Compliant (STD) align:center">Temperature NST-6359131 The Integrator Class</th><th shall coordinate cellId="1524214" market-specific NA 2.2 General Specifications (NST-6359130) Compliant (STD) launch NST-6359132 curves The with Integrator Novatra Systems should deliver to align a precisely new compiled with NA 2.2 General Specifications (NST-6359130) Non-Compliant software NST-6359133 binary If the with Integrator every development deems it essential loop. for project 3 2.2 General Specifications (NST-6359130) Non-Compliant performance, NST-6359141 The it may Unified appoint Cybersecurity a resident engineer Terms (UCT) to facilitate shall be NA 2.3 Security and Protection (NST-6359140) Compliant (STD) complied NST-6359142 with. If For the execution Integrator of does the not assignment, operate proprietary diagnosis of NA 2.3 Security and Protection (NST-6359140) Open • software UCT for for Secure SAC Access management, Credentials the KeyMesh [MSS 10916] Manager (KMM) NA 2.3 Security and Protection (NST-6359140) Open • UCT for Key Mesh Manager [MSS 10917] NA 2.3 Security and Protection (NST-6359140) Open NST-6359142 If the Integrator does not operate proprietary NA 2.3 Security and Protection (NST-6359140) Open software NST-6359143 for SAC Both management, SAC and KMM the are KeyMesh governed Manager under the (KMM) UCT NA 2.3 Security and Protection (NST-6359140) Open • framework, UCT for Secure consisting Access of Credentials the following [MSS governing 10916] documents: NA 2.3 Security and Protection (NST-6359140) Open • UCT for Key Mesh Manager [MSS 10917] NA 2.3 Security and Protection (NST-6359140) 0.00 0.00 0.00