Deprecated: Creation of dynamic property AAL_Main::$notifications is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/aryo-activity-log/aryo-activity-log.php on line 103

Deprecated: Creation of dynamic property AAL_Main::$export is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/aryo-activity-log/aryo-activity-log.php on line 104

Deprecated: Return type of FS_Key_Value_Storage::offsetExists($k) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 309

Deprecated: Return type of FS_Key_Value_Storage::offsetGet($k) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 317

Deprecated: Return type of FS_Key_Value_Storage::offsetSet($k, $v) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 301

Deprecated: Return type of FS_Key_Value_Storage::offsetUnset($k) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 313

Deprecated: Return type of FS_Key_Value_Storage::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 328

Deprecated: Return type of FS_Key_Value_Storage::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 339

Deprecated: Return type of FS_Key_Value_Storage::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 350

Deprecated: Return type of FS_Key_Value_Storage::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 362

Deprecated: Return type of FS_Key_Value_Storage::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 375

Deprecated: Return type of FS_Key_Value_Storage::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/yjjsh1yw/public_html/wp-content/plugins/easy-post-views-count/freemius/includes/managers/class-fs-key-value-storage.php on line 389

Deprecated: Creation of dynamic property Mongoose_Page_Plugin::$settings_page_url is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/facebook-page-feed-graph-api/inc/class-mongoose-page-plugin.php on line 228

Deprecated: Creation of dynamic property Post_Views_Counter::$settings_api is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 128

Deprecated: Creation of dynamic property Post_Views_Counter::$functions is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 139

Deprecated: Creation of dynamic property Post_Views_Counter::$update is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 140

Deprecated: Creation of dynamic property Post_Views_Counter::$settings is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 141

Deprecated: Creation of dynamic property Post_Views_Counter::$admin is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 142

Deprecated: Creation of dynamic property Post_Views_Counter::$query is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 143

Deprecated: Creation of dynamic property Post_Views_Counter::$cron is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 144

Deprecated: Creation of dynamic property Post_Views_Counter::$counter is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 145

Deprecated: Creation of dynamic property Post_Views_Counter::$columns is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 146

Deprecated: Creation of dynamic property Post_Views_Counter::$crawler_detect is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 147

Deprecated: Creation of dynamic property Post_Views_Counter::$frontend is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 148

Deprecated: Creation of dynamic property Post_Views_Counter::$dashboard is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 149

Deprecated: Creation of dynamic property Post_Views_Counter::$widgets is deprecated in /home2/yjjsh1yw/public_html/wp-content/plugins/post-views-counter/post-views-counter.php on line 150
又造假!這家豐田系企業跌落「神壇」,剩下滿地「假數據」 – 有海水的地方就有中國人

又造假!這家豐田系企業跌落「神壇」,剩下滿地「假數據」

又造假!這家豐田系企業跌落「神壇」,剩下滿地「假數據」
2,401

又造假!這家豐田系企業跌落「神壇」,剩下滿地「假數據」

2月16日,日本汽車零部件巨頭曙光制動器工業公司發布了汽車用制動器等四種產品發生數據造假,造假數據可以確認到2001年1月份,總共涉及11萬4000件產品。並且聲稱,雖然數據造假,可是並沒有違反相關法令,也不會影響產品的質量性能。但是這個可是與生命安全直接相關聯的「制動產品」啊,連續20年生產的產品數據都有問題,怎麼能夠讓人放心?

又造假!這家豐田系企業跌落「神壇」,剩下滿地「假數據」

這些產品已經交付給10家汽車廠家,該公司的社長在網上記者招待會上說:這是不允許的事情,正在全力制定再發生對策。這些產品是曙光制動器工業公司的山形縣以及福島縣等子公司所生產的,生產之後更改了產品的強度數據,並且還在沒有實施的項目當中填寫上數值。可是這家公司並不打算召回,因為在他們的事後測試當中發現,這些產品不會對性能造成影響。

又造假!這家豐田系企業跌落「神壇」,剩下滿地「假數據」

很早我就知道這家企業的存在,畢竟是日本汽車部品製造業的大手,在制動器領域還是十分有名的。豐田汽車是這家公司的大股東,占據了11.59%的份額;其次是五十鈴汽車,占據9.06%的份額;同屬於豐田系企業的愛信精機,占據這家公司2.34%的份額。所以從股份所有上來看,這家公司是完完全全的豐田系公司。

2016年這家企業還因為開發量產了高性能汽車制動部品而獲得日本機械學會技術獎項,但是在此之後好景並不長,2019年1月29日申請了事業再生ADR(法庭外紛爭解決手續,適用於因為經營不善但又不想破產的企業)。這項制度相當於是與債權人私下解決問題的手段,其實主要是日本各個金融機構,不會影響到產品的生產以及交付。

又造假!這家豐田系企業跌落「神壇」,剩下滿地「假數據」

當時這家公司陷入經營危機的最主要原因是北美市場的蕭條,雖然這家公司是豐田系企業,可是也有許多其他客戶,比如日產、GM等,因為在北美市場之上,失去了GM的訂單,使得在北美市場陷入被動,雖然在2019年的中間決算時還依然維持了盈利,可是從債權上來看,已經陷入了經營危機當中。

又造假!這家豐田系企業跌落「神壇」,剩下滿地「假數據」

曙光制動器工業的產品

當時這件事讓我也陷入了思考,因為無論是日本汽車製造廠家還是日本汽車零部件製造廠家,都十分地重視北美市場,一個是因為北美市場是他們重要的美元資金來源,第二個是北美市場汽車銷量確實不錯,利潤率很高。但是從2017年以後,北美市場逐漸發生著異變。整車市場更加重視集中銷售的戰略,開始建設車型系列,對零部件廠家的價格要求也越來越嚴格。 引發曙光制動器工業申請再生ADR的原因就是失去了北美市場的訂單,這一方面與車廠更換車型有關,也與價格有直接的關聯。

為什麼我要講之前這家公司經營不善的事情呢?因為與本次數據造假一事有著直接的關聯。

又造假!這家豐田系企業跌落「神壇」,剩下滿地「假數據」

因為曙光制動器工業申請了事業再生ADR,經過多方面的協調,在2019年10月開始了新的經營體制。在2019年11月份,該公司的品質部門就向當時的社長提出位於山形縣的工廠生產的制動器零部件數據造假。在收到此報告後,在2020年3月中旬的董事會上,成立了特別調查委員會,開始正式的社內調查。經過將近一年的調查,在今年的2月16日由該公司社長對外宣布,曙光制動器工業大規模數據造假。

日本汽車產業確實是十分的發達,但是數據造假一事,其實也是「常態」。被爆出來的有很多,日本TAKATA株式會社,那麼大的一家公司,還是生產安全部品的企業,同樣是因為造假醜聞破產;三菱汽車,隱瞞召回信息,自己修改燃油數據;日產汽車,為了整車檢查順利通過,用無資格人員進行整車檢查;斯巴魯,在整車檢車的時候,也是自己修改燃油數據;鈴木汽車就更狠了,直接修改了整車檢查的多個數據,而且還省掉了一部分的工序;羅列起來簡直數不勝數。

又造假!這家豐田系企業跌落「神壇」,剩下滿地「假數據」

我認為日本企業總是爆出自己修改數據的事件是有原因的,那就是日本汽車製造業過於「自負」以及來自成本的壓力。許多日本企業會採取「從嚴管理」的方式,比如要求數據值為10的話,內部就按照8來管理,即便是內部超限,也是有一定的餘量。

做過製造業的都知道,即便是CPK指數再好,工程內總是會出現一定的不良產品,而不良就相當於「浪費」。汽車產業要求「0收1退」,特別是對於零部件來說,如果發現一個不良,整批就直接退回了。所以一些汽車零部件生產廠家在生產交付與成本的壓力下,鋌而走險!而這一切,就是建立在他們自認為自己的產品性能過剩,即便是稍微有些瑕疵,也是不會影響產品性能的基礎之上。這一點,從曙光制動器工業對應上,就可以看出!

我與不少日本汽車行業的工程師都交流過,從這些交流的內容,我可以肯定地說:日本汽車零部件廠家數據造假的事件還有很多,之後還會爆出,曙光制動器工業絕不是最後一個!到時候,剩下的,真的就是滿地「假數據」!

Leave a Reply

Your email address will not be published. Required fields are marked *

You cannot copy content of this page

error: Content is protected !!
%d bloggers like this: