乐于分享
好东西不私藏

第二章第二节,2.2 客户信息收集模板:人员、职务、背景、过往合作项目

第二章第二节,2.2 客户信息收集模板:人员、职务、背景、过往合作项目

第二章第二节,2.2 客户信息收集模板:人员、职务、背景、过往合作项目

2.2 Client Information Collection Template: Personnel, Positions, Backgrounds, and Past Cooperative Projects

在客户来访准备工作中,有一项看似简单却至关重要的工作:客户信息收集。

很多模塑工厂的接待人员,在接到客户来访通知后,往往只关注谁来、什么时候来、几个人来这些基本信息,然后就匆忙开始准备。这种做法,看似高效,实则埋下了诸多隐患。因为缺少对客户人员信息的深入了解,我们可能安排错接待人员、准备错交流内容、错过建立共鸣的机会。

客户信息收集,不是简单的登记造册,而是为整个接待工作奠定基础的关键一步。它决定了我们能否做到对等接待精准对接共鸣共情。 

In preparing for client visits, one task that appears simple but is critically important is client information collection.

Many reception staff at molding factories, upon receiving a visit notice, only focus on basic information such as who is coming, when, and how many people, then rush into preparation. While this seems efficient, it actually hides many potential risks. Without in-depth understanding of client personnel, we may assign inappropriate hosts, prepare irrelevant content, and miss opportunities to build rapport.

Client information collection is more than just registration; it is a key step that lays the foundation for the entire reception. It determines whether we can achieve equivalent-level reception, precise matching, and effective empathy.

一、人员数量:决定接待规模与资源配置

I. Number of Visitors: Determining Reception Scale and Resource Allocation

客户来访的人员数量,是接待准备工作的起点。它直接影响我们如何配置接待资源、如何安排接待场地、如何规划接待流程。

The number of visitors is the starting point of preparation. It directly influences how we allocate resources, arrange venues, and design the process.

数量决定接待规模

在模塑工厂的客户接待中,有一个基本原则:接待人员的数量,一般应与来访人员的数量相当。这不是简单的人海战术,而是出于几个方面的考虑。

首先,数量相当才能保证服务质量。如果客户来了五个人,我们只安排一个人接待,就会出现一个人应付不过来的情况——这边在回答A的问题,那边B已经在等待;这边在引导参观,那边C已经掉队。客户会感受到被冷落被忽视

其次,数量相当才能体现重视程度。客户来访,尤其是重要客户的来访,接待人员的配置本身就是一种信号。当客户看到我们派出了与己方人数相当的接待团队,他们会感受到这家公司很重视我们。反之,如果接待人员明显少于来访人员,客户可能会产生我们不被重视的感觉。

第三,数量相当才能实现有效对接。不同职能的客户人员,需要与我们对口的人员进行交流。如果接待人员数量不足,就无法实现这种点对点的精准对接,很多交流就无法深入。

当然,数量相当不等于一一对应。在某些情况下,我们的一位接待人员可以对接客户的多位人员,比如一位技术总监可以同时对接客户的技术经理和工程师。但总体上,接待团队的规模应与来访团队大致匹配。

Quantity determines reception scale

A basic principle in molding factory client reception: the size of the host team should generally match the number of visitors. This is not simply crowd tactics; it is based on practical considerations:

Ensuring service quality

If five clients arrive with only one host, they will feel neglected or ignored as the host cannot attend to everyone at once.

Reflecting attention

A matching host team signals that we value the client. An obviously undersized team may give the impression of being unimportant.

Enabling effective matching

Clients from different functions need counterparts in our team. Insufficient hosts prevent in-depth, targeted communication. Matching scale does not mean one-on-one pairing. For example, one Technical Director can interface with both a clients Technical Manager and engineers. Overall, however, the host team should be roughly comparable in size.

数量决定资源调配

来访人员的数量,还决定了我们如何调配各种资源。

会议室的大小要根据人数选择。客户来了两个人,用大会议室显得空旷;客户来了八个人,用小会议室显得拥挤。会议室的空间感,会影响交流的氛围和效果。

参观的分组要考虑人数。如果客户人数较多(比如超过六人),可能需要分组参观,或者安排多名讲解人员分别引导。否则,走在后面的人可能听不清讲解,看不到重点。

用餐的安排要根据人数确定。人数少,可以选择包间或安静的区域;人数多,可能需要更大的空间,或者考虑自助餐形式。

交通的安排也要考虑人数。客户来了几个人,需要几辆车?是否需要安排商务车或中巴?这些细节,都需要提前规划。

Quantity determines resource allocation

Meeting room size must fit the group: too large feels empty; too small feels crowded.

Tour grouping: For groups over six people, split into smaller groups or use multiple guides to ensure everyone can hear and see clearly.

Dining arrangement: Small groups may use private rooms; larger groups may need bigger spaces or buffet.

Transportation: Number of vehicles, type (business car, van) based on headcount.

数量背后的信息

除了有多少人,我们还要关注是什么人。同样是五个人,如果都是技术人员,和五个人涵盖采购、质量、技术、项目等多个职能,接待的重点和方式是截然不同的。因此,人员数量信息需要与职务、背景信息结合使用,才能发挥最大价值。

Information behind the numbers

Beyond how many people are coming, we must understand who they are. A group of five technicians requires very different preparation from a cross-functional group including procurement, quality, engineering, and project members. Thus, quantity must be combined with positions and backgrounds to be truly useful.

二、来访人员职务:决定对等接待层级

II. Positions of Visitors: Determining Equivalent-Level Reception

在商务交往中,对等接待是一项基本原则。所谓对等接待,是指我方派出的人员层级,应与客户来访人员的层级相当或略高。

In business communication, equivalent-level reception is a fundamental principle: the seniority of our hosts should match or be slightly higher than that of the visitors.

职务决定接待层级

为什么要有对等接待?原因很简单:职务层级背后,是决策权限、关注重点、交流方式的差异。

如果客户来的是采购总监,我们派一个销售专员去接待,客户会觉得这家公司不重视我们。如果客户来的是技术工程师,我们却派出总经理全程陪同,客户可能会觉得压力太大、不自在。对等接待,是对客户身份的基本尊重,也是高效交流的前提。

在实际操作中,我们通常遵循一个原则:我方接待人员的职务,一般比来访人员高半级或一级。比如,客户来的是经理级,我们可以安排高级经理或总监级接待;客户来的是总监级,我们可以安排副总经理或总经理接待。这种略高的安排,体现了对客户的尊重,同时又不至于让客户感到压力。

当然,这个原则要灵活运用。对于长期合作的老客户、关系紧密的合作伙伴,可以适当简化层级,更注重熟悉的人对等交流。对于新客户、重要客户,则要严格执行对等原则,甚至适当提高接待层级,以示重视。

Position determines reception level

Position reflects decision-making authority, focus areas, and communication style.

A Procurement Director visiting should not be received only by a sales representative.

A technical engineer should not be overly accompanied by the General Manager, which may cause discomfort.

Equivalent-level reception shows basic respect and enables efficient communication.

In practice, we usually follow this guideline:

our host is one-half to one level higher than the visitor.

Manager-level client  Senior Manager / Director

Director-level client  Deputy General Manager / General Manager

This slight elevation shows respect without creating pressure. For long-term partners, the rule can be more flexible. For new or key clients, we strictly follow the principle or even upgrade the host level.

职务决定交流内容

来访人员的职务,还决定了我们与他们的交流内容和方式。

高层管理者(如总经理、副总裁、总监级),关注的往往是战略层面的问题——公司的发展方向、技术路线图、产能布局、合作前景。与高层交流,我们要准备宏观层面的内容,展示公司的战略思维和长远规划。

中层管理者(如经理、高级工程师级),关注的是执行层面的问题——项目进度、质量表现、成本控制、风险管控。与中层交流,我们要准备具体的项目数据、管理指标、改进措施。

基层人员(如工程师、专员级),关注的是操作层面的问题——技术细节、工艺参数、检测方法、操作规范。与基层交流,我们要准备专业的技术内容、详细的操作说明、具体的案例分享。

如果我们不了解来访人员的职务,就可能出现对高层讲细节、对基层讲战略的错位,让客户觉得这家公司不懂我们

Position determines communication content

Senior executives (GM, VP, Director): focus on strategy, development direction, technology roadmap, capacity layout, cooperation vision. We prepare macro-level content.

Middle managers (Manager, Senior Engineer): focus on execution  project progress, quality, cost control, risk management. We provide data and indicators.

Junior staff (Engineer, Specialist): focus on operations  technical details, process parameters, testing methods, standards. We share professional and practical content.

Without knowing positions, we risk mismatching: talking about details to executives and strategy to frontline staff, making clients feel misunderstood.

职务决定参与人员

来访人员的职务,还决定了我们应该安排哪些人员参与接待。

如果客户来访人员中有高层管理者,我方也要有相应层级的管理者参与。这不仅是对客户的尊重,也是因为高层之间的交流,往往能更快地达成共识、推动决策。

如果客户来访人员以技术人员为主,我方就要安排技术骨干参与,确保技术交流的深度和质量。如果客户来访人员中有质量人员,我方就要安排质量部门的人员参与,便于质量问题的深入探讨。

在实际操作中,我们可以根据客户来访人员的职务构成,组建一个对等的接待团队。这个团队可能包括:与客户高层对等的公司高管、与客户中层对等的部门负责人、与客户基层对等的技术骨干。通过这种分层对等,确保每一个层级的交流都能顺畅高效。

Position determines participant selection

If client executives attend, our corresponding management must be present to facilitate consensus and decision-making.

If the group is mostly technical, our technical backbone leads the discussion.

If quality personnel join, our quality team participates for in-depth quality dialogue.

We form a layered, counterpart host team to ensure smooth and efficient communication at every level.

三、背景信息:决定技术对接的精准性

III. Background Information: Determining Precision of Technical Matching

来访人员的职务告诉我们他们是谁,而背景信息告诉我们他们擅长什么、关心什么。背景信息的收集,是精准对接的关键。

Position tells us who visitors are; background tells us what they specialize in and care about. Background collection is key to precise technical docking.

职务背景决定技术对接模块

在模塑工厂,不同背景的客户人员,关注的技术领域是不同的。

如果来访人员有模具设计背景,他们会关注模具结构、浇口设计、冷却系统、顶出方式等技术细节。我们在交流时,可以深入探讨这些内容,甚至可以展示模具设计图纸、模流分析报告,与他们进行专业层面的对话。

如果来访人员有注塑工艺背景,他们会关注成型参数、工艺窗口、缺陷分析、周期优化等内容。我们可以安排他们参观注塑车间,现场讲解工艺参数设置、过程控制方法,甚至可以讨论具体的工艺优化案例。

如果来访人员有质量管理背景,他们会关注质量体系、检测手段、过程控制、不良率统计、问题解决方法。我们可以重点展示实验室、质量看板、SPC数据、8D报告等,让他们看到我们的质量管理能力。

如果来访人员有项目管理背景,他们会关注项目进度、风险管控、资源协调、沟通机制。我们可以重点展示项目进度表、风险登记册、会议纪要等项目管理文件。

如果我们不了解来访人员的背景,就可能出现对模具背景的人讲工艺、对质量背景的人讲模具的错位,无法真正引起他们的兴趣和共鸣。

Professional background determines technical focus

In molding, different backgrounds lead to different technical concerns:

Mold design background: mold structure, gating, cooling system, ejection. We share drawings and mold flow analysis.

Injection process background: parameters, process window, defect analysis, cycle optimization. We focus on the injection workshop.

Quality management background: quality system, testing, SPC, defect rate, 8D reports. We highlight the laboratory and quality dashboards.

Project management background: schedule, risk control, coordination, communication mechanisms. We present project plans and meeting minutes.

Without background awareness, we may talk about processes to mold experts or mold design to quality specialists, failing to resonate.

背景信息如何收集

背景信息的收集,需要我们在日常沟通中保持敏感。

一种途径是通过客户对接人了解。在预约来访时,我们可以主动询问:这次来访的几位领导,分别负责哪些领域?我们好安排相应的人员对接。客户对接人通常会乐于提供这些信息。

另一种途径是通过公开信息了解。领英、公司官网、行业活动等渠道,都可能提供客户人员的背景信息。比如,通过领英可以看到对方的职业经历、教育背景、专业技能标签;通过公司官网可以看到对方的职务职责、发表的文章、参与的行业活动。

还有一种途径是通过过往交往了解。如果客户是老客户,我们可能已经与某些人员有过接触。回顾过往的邮件、会议记录、交往经历,可以获取有价值的信息。

How to collect background information

Ask the client contact directly:

Which areas do your visitors mainly oversee so we can arrange suitable counterparts?

Public information: LinkedIn, official website, industry events, published articles.

Historical interaction: review past emails, meeting minutes, and cooperation records for existing clients.

背景信息的应用

收集到背景信息后,我们要将其应用到接待准备中。

首先,根据背景信息,确定由谁来对接。模具背景的客户,安排模具工程师对接;质量背景的客户,安排质量工程师对接;项目背景的客户,安排项目经理对接。这种专业对口的安排,能确保交流的深度和质量。

其次,根据背景信息,准备针对性的交流内容。对于模具背景的客户,我们可以准备模具设计图纸、模流分析报告、模具加工案例;对于质量背景的客户,我们可以准备质量数据、检测报告、问题分析案例。让客户看到,我们不仅知道他们是谁,还知道他们关心什么。

第三,根据背景信息,设计参观的重点。模具背景的客户,参观时可以多停留模具车间;质量背景的客户,参观时可以多停留实验室;工艺背景的客户,参观时可以多停留注塑机台旁。这种投其所好的安排,能让客户感受到我们的用心。

Application of background information

Assign matching hosts: mold engineer for mold experts; quality engineer for quality specialists.

Prepare targeted content: relevant reports, data, cases, and samples.

Design customized tour routes:

mold workshop for mold experts; laboratory for quality specialists; injection machines for process engineers. This tailored arrangement shows thoughtfulness and professionalism.

四、过往合作项目:建立共鸣与信任的桥梁

IV. Past Cooperative Projects: Building Rapport and Trust

如果说人员数量、职务、背景信息是基础信息,那么过往合作项目信息就是增值信息。它承载着双方共同的经历、共同的记忆、共同的成果,是建立共鸣和信任的宝贵资源。

While personnel, position, and background are basic information, past cooperative projects are value-added information. They represent shared experience, memory, and achievement, serving as a bridge to trust.

过往合作项目的价值

在客户来访中,如果能提及双方过往的合作项目,往往能起到意想不到的效果。

首先,它能建立我们不是陌生人的感觉。当客户听到我们提起上次那个XX项目时,他们会觉得这家公司记得我们,从而拉近心理距离。

其次,它能展示我们的专业积累。当我们能熟练地回顾过往项目的经验、数据、成果时,客户会相信我们是真正理解他们业务的人,而不是泛泛之交。

第三,它能引出“lesson learn”,展示我们的成长。每个项目都有成功和失败,都有经验教训。当我们能够坦诚地分享过往项目中的教训,以及我们如何改进时,客户会看到我们的反思能力和持续进步的态度。

第四,它能创造共同话题。过往项目中的某个技术难点、某个紧急交付、某个联合攻关,都可能成为双方共同的记忆。在来访中提起这些,能迅速拉近关系,创造轻松愉快的交流氛围。

如何收集过往合作项目信息

过往合作项目信息的收集,需要建立一个系统的客户档案

对于新客户,过往合作项目信息可能较少,但我们可以通过行业信息、共同服务过的客户等,寻找潜在的共同点。比如,我们之前为XX品牌做过类似产品,如果客户也熟悉那个品牌,就能建立连接。

对于老客户,过往合作项目信息的价值更大。我们要建立完整的客户项目档案,包括:项目名称、产品类型、模具规格、交付时间、项目成果、客户反馈、经验教训等。这些信息,是客户来访时的重要谈资

在收集信息时,要特别注意“lesson learn”。每个项目都有成功之处,也都有可以改进的地方。成功之处要总结,作为展示能力的素材;失败之处也要总结,不是为了自我批评,而是为了展示我们从中学到了什么、改进了什么。这种坦诚,反而能赢得客户的尊重。

过往合作项目的应用场景

在客户来访中,过往合作项目信息可以在多个场景下应用。

在开场破冰时,可以提及过往项目的共同记忆。上次XX项目的时候,我们合作得非常愉快,特别是那次紧急交付,贵方的配合让我们印象深刻。这样的话语,能迅速拉近距离。

在技术交流时,可以引用过往项目的经验。类似的结构,我们在XX项目中采用过这种方案,效果很好,建议这次也可以参考。这种引用,能让技术建议更有说服力。

在参观讲解时,可以展示过往项目的成果。这套模具就是为XX项目做的,现在已经稳定生产了XX万件,良品率保持在XX%以上。这种展示,能让参观内容更加生动。

在小结交流时,可以展望未来合作的延续。上次XX项目我们积累了很多经验,这次的新项目可以在此基础上进一步优化。这种展望,能让客户看到持续合作的价值。

注意事项:避免翻旧账

在提及过往合作项目时,要特别注意分寸。过往项目中的问题,可以提及,但要把握好角度。不要变成翻旧账”“相互指责,而要聚焦于我们从中学到了什么”“我们如何改进。如果客户主动提起过往的问题,我们要坦诚面对、积极回应,而不是回避或推诿。

同时,要尊重客户的商业机密。过往项目中的敏感信息,不要在公开场合提及;不同客户之间的信息,更不要混淆使用。保密意识,是专业素养的重要体现。

Value of past projects

Build familiarity: Mentioning a previous project creates a we are not strangers feeling.

Demonstrate expertise: Fluently reviewing past data and results shows deep understanding of their business.

Show improvement: Sharing lessons learned and improvements reflects accountability and growth.

Create common topics: Technical challenges, urgent deliveries, joint efforts become natural icebreakers.

How to collect past project information

New clients: Look for indirect links, such as serving the same brand or industry.

Existing clients: Establish a complete client project file including:

project name, product type, mold specification, delivery time, results, feedback, lessons learned.

Pay special attention to lessons learned: summarize both successes and areas improved, not for self-criticism but to show growth.

Application scenarios

Icebreaking:

We really appreciated your support during the urgent delivery of the XX project.

Technical discussion:

We used a similar solution in the XX project with excellent results.

Tour explanation:

This mold was for the XX project and has stably produced over XX pieces.

Closing summary:

We can build on our experience from XX project to optimize the new project.

Cautions

Avoid bringing up old grudges. Focus on improvement, not blame.

Respect confidentiality: do not disclose sensitive information in public.

Do not mix or compare information between different clients.

五、构建客户信息收集模板

V. Building a Client Information Collection Template

综合以上四个维度,我们可以构建一个实用的客户信息收集模板。这个模板可以在预约来访后立即启动,作为接待准备工作的起点。

Based on the four dimensions, we can build a practical template to use immediately after appointment confirmation.

基本信息模块

  • 公司名称
  • 来访日期
  • 来访总人数
  • 预计到达/离开时间
  • 来访目的(验厂/技术交流/项目跟进/问题解决/高层互访)

人员信息模块(每位来访人员单独记录)

  • 姓名
  • 职务
  • 部门
  • 联系电话/邮箱
  • 照片(如有)

背景信息模块(每位来访人员单独记录)

  • 专业背景(模具/注塑/质量/项目/采购/其他)
  • 技术专长(如精密模具/双色注塑/自动化等)
  • 过往经历(在哪些公司工作过、参与过哪些重要项目)
  • 性格特点(严肃/随和/健谈/内敛等)

过往合作信息模块

  • 合作项目列表(项目名称、时间、产品类型、规模)
  • 项目成果(交付情况、质量表现、客户反馈)
  • 经验教训(成功经验、改进点)
  • 关键联系人(过往项目中的对接人)

接待安排建议模块(基于以上信息生成)

  • 建议接待人员(职务、部门、姓名)
  • 建议交流重点
  • 建议参观重点
  • 建议用餐安排
  • 特别注意事项

这个模板,可以在每次客户来访时使用。随着使用次数的增加,信息会越来越丰富,接待准备的精准度也会越来越高。

Basic Information Module

Company name

Visit date

Total number of visitors

Estimated arrival / departure time

Visit purpose (factory audit / technical exchange / project follow-up / problem-solving / executive exchange)

Personnel Information Module (per visitor)

Full name

Position

Department

Phone / email

Photo (if available)

Background Information Module (per visitor)

Professional background (mold / injection / quality / project / procurement / other)

Technical expertise (precision mold, two-color molding, automation, etc.)

Career experience (previous employers, key projects)

Personality traits (serious / easy-going / talkative / reserved)

Past Cooperation Module

List of cooperative projects (name, date, product type, scale)

Project results (delivery, quality, client feedback)

Lessons learned (successes, improvements)

Key historical contacts

Recommended Reception Arrangement Module

Recommended host(s) (position, department, name)

Recommended communication focus

Recommended tour highlights

Recommended dining arrangement

Special precautions

This template can be reused for every visit. Over time, the information becomes richer, and preparation becomes increasingly precise.

基本 文件 流程 错误 SQL 调试
  1. 请求信息 : 2026-04-24 13:32:00 HTTP/1.1 GET : https://www.yeyulingfeng.com/a/554890.html
  2. 运行时间 : 0.120949s [ 吞吐率:8.27req/s ] 内存消耗:4,728.60kb 文件加载:145
  3. 缓存信息 : 0 reads,0 writes
  4. 会话信息 : SESSION_ID=c1c6bcf9f747f5da4cf0ed2f740109c4
  1. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/public/index.php ( 0.79 KB )
  2. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/autoload.php ( 0.17 KB )
  3. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/composer/autoload_real.php ( 2.49 KB )
  4. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/composer/platform_check.php ( 0.90 KB )
  5. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/composer/ClassLoader.php ( 14.03 KB )
  6. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/composer/autoload_static.php ( 6.05 KB )
  7. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/helper.php ( 8.34 KB )
  8. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-validate/src/helper.php ( 2.19 KB )
  9. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/ralouphie/getallheaders/src/getallheaders.php ( 1.60 KB )
  10. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/helper.php ( 1.47 KB )
  11. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/stubs/load_stubs.php ( 0.16 KB )
  12. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Exception.php ( 1.69 KB )
  13. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-container/src/Facade.php ( 2.71 KB )
  14. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/deprecation-contracts/function.php ( 0.99 KB )
  15. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/polyfill-mbstring/bootstrap.php ( 8.26 KB )
  16. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/polyfill-mbstring/bootstrap80.php ( 9.78 KB )
  17. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/var-dumper/Resources/functions/dump.php ( 1.49 KB )
  18. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-dumper/src/helper.php ( 0.18 KB )
  19. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/symfony/var-dumper/VarDumper.php ( 4.30 KB )
  20. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/guzzlehttp/guzzle/src/functions_include.php ( 0.16 KB )
  21. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/guzzlehttp/guzzle/src/functions.php ( 5.54 KB )
  22. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/App.php ( 15.30 KB )
  23. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-container/src/Container.php ( 15.76 KB )
  24. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/psr/container/src/ContainerInterface.php ( 1.02 KB )
  25. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/provider.php ( 0.19 KB )
  26. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Http.php ( 6.04 KB )
  27. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/helper/Str.php ( 7.29 KB )
  28. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Env.php ( 4.68 KB )
  29. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/common.php ( 0.03 KB )
  30. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/helper.php ( 18.78 KB )
  31. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Config.php ( 5.54 KB )
  32. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/alipay.php ( 3.59 KB )
  33. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/facade/Env.php ( 1.67 KB )
  34. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/app.php ( 0.95 KB )
  35. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/cache.php ( 0.78 KB )
  36. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/console.php ( 0.23 KB )
  37. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/cookie.php ( 0.56 KB )
  38. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/database.php ( 2.48 KB )
  39. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/filesystem.php ( 0.61 KB )
  40. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/lang.php ( 0.91 KB )
  41. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/log.php ( 1.35 KB )
  42. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/middleware.php ( 0.19 KB )
  43. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/route.php ( 1.89 KB )
  44. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/session.php ( 0.57 KB )
  45. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/trace.php ( 0.34 KB )
  46. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/config/view.php ( 0.82 KB )
  47. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/event.php ( 0.25 KB )
  48. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Event.php ( 7.67 KB )
  49. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/service.php ( 0.13 KB )
  50. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/AppService.php ( 0.26 KB )
  51. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Service.php ( 1.64 KB )
  52. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Lang.php ( 7.35 KB )
  53. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/lang/zh-cn.php ( 13.70 KB )
  54. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/initializer/Error.php ( 3.31 KB )
  55. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/initializer/RegisterService.php ( 1.33 KB )
  56. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/services.php ( 0.14 KB )
  57. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/service/PaginatorService.php ( 1.52 KB )
  58. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/service/ValidateService.php ( 0.99 KB )
  59. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/service/ModelService.php ( 2.04 KB )
  60. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-trace/src/Service.php ( 0.77 KB )
  61. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Middleware.php ( 6.72 KB )
  62. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/initializer/BootService.php ( 0.77 KB )
  63. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/Paginator.php ( 11.86 KB )
  64. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-validate/src/Validate.php ( 63.20 KB )
  65. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/Model.php ( 23.55 KB )
  66. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/Attribute.php ( 21.05 KB )
  67. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/AutoWriteData.php ( 4.21 KB )
  68. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/Conversion.php ( 6.44 KB )
  69. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/DbConnect.php ( 5.16 KB )
  70. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/ModelEvent.php ( 2.33 KB )
  71. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/concern/RelationShip.php ( 28.29 KB )
  72. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/contract/Arrayable.php ( 0.09 KB )
  73. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/contract/Jsonable.php ( 0.13 KB )
  74. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/model/contract/Modelable.php ( 0.09 KB )
  75. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Db.php ( 2.88 KB )
  76. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/DbManager.php ( 8.52 KB )
  77. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Log.php ( 6.28 KB )
  78. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Manager.php ( 3.92 KB )
  79. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/psr/log/src/LoggerTrait.php ( 2.69 KB )
  80. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/psr/log/src/LoggerInterface.php ( 2.71 KB )
  81. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Cache.php ( 4.92 KB )
  82. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/psr/simple-cache/src/CacheInterface.php ( 4.71 KB )
  83. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/helper/Arr.php ( 16.63 KB )
  84. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/cache/driver/File.php ( 7.84 KB )
  85. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/cache/Driver.php ( 9.03 KB )
  86. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/contract/CacheHandlerInterface.php ( 1.99 KB )
  87. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/Request.php ( 0.09 KB )
  88. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Request.php ( 55.78 KB )
  89. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/middleware.php ( 0.25 KB )
  90. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Pipeline.php ( 2.61 KB )
  91. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-trace/src/TraceDebug.php ( 3.40 KB )
  92. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/middleware/SessionInit.php ( 1.94 KB )
  93. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Session.php ( 1.80 KB )
  94. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/session/driver/File.php ( 6.27 KB )
  95. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/contract/SessionHandlerInterface.php ( 0.87 KB )
  96. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/session/Store.php ( 7.12 KB )
  97. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Route.php ( 23.73 KB )
  98. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/RuleName.php ( 5.75 KB )
  99. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/Domain.php ( 2.53 KB )
  100. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/RuleGroup.php ( 22.43 KB )
  101. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/Rule.php ( 26.95 KB )
  102. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/RuleItem.php ( 9.78 KB )
  103. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/route/app.php ( 3.94 KB )
  104. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/facade/Route.php ( 4.70 KB )
  105. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/dispatch/Controller.php ( 4.74 KB )
  106. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/route/Dispatch.php ( 10.44 KB )
  107. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/controller/Index.php ( 9.87 KB )
  108. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/BaseController.php ( 2.05 KB )
  109. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/facade/Db.php ( 0.93 KB )
  110. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/connector/Mysql.php ( 5.44 KB )
  111. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/PDOConnection.php ( 52.47 KB )
  112. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/Connection.php ( 8.39 KB )
  113. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/ConnectionInterface.php ( 4.57 KB )
  114. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/builder/Mysql.php ( 16.58 KB )
  115. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/Builder.php ( 24.06 KB )
  116. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/BaseBuilder.php ( 27.50 KB )
  117. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/Query.php ( 15.71 KB )
  118. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/BaseQuery.php ( 45.13 KB )
  119. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/TimeFieldQuery.php ( 7.43 KB )
  120. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/AggregateQuery.php ( 3.26 KB )
  121. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/ModelRelationQuery.php ( 20.07 KB )
  122. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/ParamsBind.php ( 3.66 KB )
  123. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/ResultOperation.php ( 7.01 KB )
  124. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/WhereQuery.php ( 19.37 KB )
  125. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/JoinAndViewQuery.php ( 7.11 KB )
  126. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/TableFieldInfo.php ( 2.63 KB )
  127. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-orm/src/db/concern/Transaction.php ( 2.77 KB )
  128. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/log/driver/File.php ( 5.96 KB )
  129. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/contract/LogHandlerInterface.php ( 0.86 KB )
  130. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/log/Channel.php ( 3.89 KB )
  131. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/event/LogRecord.php ( 1.02 KB )
  132. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-helper/src/Collection.php ( 16.47 KB )
  133. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/facade/View.php ( 1.70 KB )
  134. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/View.php ( 4.39 KB )
  135. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/app/controller/Es.php ( 3.30 KB )
  136. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Response.php ( 8.81 KB )
  137. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/response/View.php ( 3.29 KB )
  138. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/Cookie.php ( 6.06 KB )
  139. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-view/src/Think.php ( 8.38 KB )
  140. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/framework/src/think/contract/TemplateHandlerInterface.php ( 1.60 KB )
  141. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-template/src/Template.php ( 46.61 KB )
  142. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-template/src/template/driver/File.php ( 2.41 KB )
  143. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-template/src/template/contract/DriverInterface.php ( 0.86 KB )
  144. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/runtime/temp/c935550e3e8a3a4c27dd94e439343fdf.php ( 31.80 KB )
  145. /yingpanguazai/ssd/ssd1/www/wwww.yeyulingfeng.com/vendor/topthink/think-trace/src/Html.php ( 4.42 KB )
  1. CONNECT:[ UseTime:0.000472s ] mysql:host=127.0.0.1;port=3306;dbname=wenku;charset=utf8mb4
  2. SHOW FULL COLUMNS FROM `fenlei` [ RunTime:0.000790s ]
  3. SELECT * FROM `fenlei` WHERE `fid` = 0 [ RunTime:0.000323s ]
  4. SELECT * FROM `fenlei` WHERE `fid` = 63 [ RunTime:0.000263s ]
  5. SHOW FULL COLUMNS FROM `set` [ RunTime:0.000621s ]
  6. SELECT * FROM `set` [ RunTime:0.000256s ]
  7. SHOW FULL COLUMNS FROM `article` [ RunTime:0.000651s ]
  8. SELECT * FROM `article` WHERE `id` = 554890 LIMIT 1 [ RunTime:0.000509s ]
  9. UPDATE `article` SET `lasttime` = 1777008721 WHERE `id` = 554890 [ RunTime:0.002523s ]
  10. SELECT * FROM `fenlei` WHERE `id` = 64 LIMIT 1 [ RunTime:0.000331s ]
  11. SELECT * FROM `article` WHERE `id` < 554890 ORDER BY `id` DESC LIMIT 1 [ RunTime:0.001623s ]
  12. SELECT * FROM `article` WHERE `id` > 554890 ORDER BY `id` ASC LIMIT 1 [ RunTime:0.000709s ]
  13. SELECT * FROM `article` WHERE `id` < 554890 ORDER BY `id` DESC LIMIT 10 [ RunTime:0.002943s ]
  14. SELECT * FROM `article` WHERE `id` < 554890 ORDER BY `id` DESC LIMIT 10,10 [ RunTime:0.007354s ]
  15. SELECT * FROM `article` WHERE `id` < 554890 ORDER BY `id` DESC LIMIT 20,10 [ RunTime:0.000776s ]
0.122572s