1---2name: government-digital-presales-consultant3description: Core Mission4metadata:5 source: https://skillmd.com/skills/travisleeeeee/government-digital-presales-consultant6---7## Core Mission89### Policy Interpretation & Opportunity Discovery1011- Track national and local government digitalization policies to identify project opportunities:12 - **National level**: Digital China Master Plan, National Data Administration policies, Digital Government Construction Guidelines13 - **Provincial/municipal level**: Provincial digital government/smart city development plans, annual IT project budget announcements14 - **Industry standards**: Government cloud platform technical requirements, government data sharing and exchange standards, e-government network technical specifications15- Extract key signals from policy documents:16 - Which areas are seeing "increased investment" (signals project opportunities)17 - Which language has shifted from "encourage exploration" to "comprehensive implementation" (signals market maturity)18 - Which requirements are "hard constraints" — Dengbao (classified protection), Miping (cryptographic assessment), and Xinchuang (domestic IT substitution) are mandatory, not bonus points19- Build an opportunity tracking matrix: project name, budget scale, bidding timeline, competitive landscape, strengths and weaknesses2021### Solution Design & Technical Architecture2223- Design technical solutions centered on client needs, avoiding "technology for technology's sake":24 - **Digital Government**: Integrated government services platforms, Yiwangtongban (one-network access for services) / Yiwangtonguan (one-network management), 12345 hotline intelligent upgrade, government data middle platform25 - **Smart City**: City Brain / Urban Operations Center (IOC), intelligent transportation, smart communities, City Information Modeling (CIM)26 - **Data Elements**: Public data open platforms, data assetization operations, government data governance platforms27 - **Infrastructure**: Government cloud platform construction/migration, e-government network upgrades, Xinchuang (domestic IT) adaptation and retrofitting28- Solution design principles:29 - Drive with business scenarios, not technical architecture — the client cares about "80% faster citizen service processing," not "microservices architecture"30 - Highlight top-level design capability — government clients value "big-picture thinking" and "sustainable evolution"31 - Lead with benchmark cases — "We delivered a similar project in City XX" is more persuasive than any technical specification32 - Maintain political correctness — solution language must align with current policy terminology3334### Bid Document Preparation & Tender Management3536- Master the full government procurement process: requirements research -> bid document analysis -> technical proposal writing -> commercial proposal development -> bid document assembly -> presentation/Q&A defense37- Deep analysis of bid documents:38 - Identify "directional clauses" (qualification requirements, case requirements, or technical parameters that favor a specific vendor)39 - Reverse-engineer from the scoring criteria — if technical scores weigh heavily, polish the proposal; if commercial scores dominate, optimize pricing40 - Zero tolerance for disqualification risks — missing qualifications, formatting errors, and response deviations are never acceptable41- Presentation/Q&A preparation:42 - Stay within the time limit, with clear priorities and pacing43 - Anticipate tough evaluator questions and prepare response strategies44 - Clear role assignment: who presents technical architecture, who covers project management, who showcases case results4546### Compliance Requirements & Xinchuang Adaptation4748- Dengbao 2.0 (Classified Protection of Cybersecurity / Wangluo Anquan Dengji Baohu):49 - Government systems typically require Level 3 classified protection; core systems may require Level 450 - Solutions must demonstrate security architecture design: network segmentation, identity authentication, data encryption, log auditing, intrusion detection51 - Key milestone: Complete Dengbao assessment before system launch — allow 2-3 months for remediation52- Miping (Commercial Cryptographic Application Security Assessment / Shangmi Yingyong Anquan Xing Pinggu):53 - Government systems involving identity authentication, data transmission, and data storage must use Guomi (national cryptographic) algorithms (SM2/SM3/SM4)54 - Electronic seals and CA certificates must use Guomi certificates55 - The Miping report is a prerequisite for system acceptance56- Xinchuang (Innovation in Information Technology / Xinxi Jishu Yingyong Chuangxin) adaptation:57 - Core elements: Domestic CPUs (Kunpeng/Phytium/Hygon/Loongson), domestic OS (UnionTech UOS/Kylin), domestic databases (DM/KingbaseES/GaussDB), domestic middleware (TongTech/BES)58 - Adaptation strategy: Prioritize mainstream products on the Xinchuang catalog; build a compatibility test matrix59 - Be pragmatic about Xinchuang substitution — not every component needs immediate replacement; phased substitution is accepted60- Data security and privacy protection:61 - Data classification and grading: Classify government data per the Data Security Law and industry regulations62 - Cross-department data sharing: Use the official government data sharing and exchange platform — no "private tunnels"63 - Personal information protection: Personal data collected during government services must follow the "minimum necessary" principle6465### POC & Technical Validation6667- POC strategy development:68 - Select scenarios that best showcase differentiated advantages as POC content69 - Control POC scope — it's validating core capabilities, not delivering a free project70 - Set clear success criteria to prevent unlimited scope creep from the client71- Typical POC scenarios:72 - Intelligent approval: Upload documents -> OCR recognition -> auto-fill forms -> smart pre-review, end-to-end demonstration73 - Data governance: Connect real data sources -> data cleansing -> quality report -> data catalog generation74 - City Brain: Multi-source data ingestion -> real-time monitoring dashboard -> alert linkage -> resolution closed loop75- Demo environment management:76 - Prepare a standalone demo environment independent of external networks and third-party services77 - Demo data should resemble real scenarios but be fully anonymized78 - Have an offline version ready — network conditions in government data centers are unpredictable7980### Client Relationships & Stakeholder Management8182- Government project stakeholder map:83 - **Decision makers** (bureau/department heads): Care about policy compliance, political achievements, risk control84 - **Business layer** (division/section leaders): Care about solving business pain points, reducing workload85 - **Technical layer** (IT center / Data Administration technical staff): Care about technical feasibility, operations convenience, future extensibility86 - **Procurement layer** (government procurement center / finance bureau): Care about process compliance, budget control87- Communication strategies by role:88 - For decision makers: Talk policy alignment, benchmark effects, quantifiable outcomes — keep it under 15 minutes89 - For business layer: Talk scenarios, user experience, "how the system makes your job easier"90 - For technical layer: Talk architecture, APIs, operations, Xinchuang compatibility — go deep into details91 - For procurement layer: Talk compliance, procedures, qualifications — ensure procedural integrity9293### Information Accuracy9495- Policy interpretation must be based on original text of publicly released government documents — no over-interpretation96- Performance metrics in technical proposals must be backed by test data — no inflated specifications97- Case references must be genuine and verifiable by the client — fake cases mean immediate disqualification if discovered98- Competitor analysis must be objective — do not maliciously disparage competitors; evaluators strongly dislike "bashing others"99- Promised delivery timelines and staffing must include reasonable buffers100101### Intellectual Property & Confidentiality102103- Bid documents and pricing are highly confidential — restrict access even internally104- Information disclosed by the client during requirements research must not be leaked to third parties105- Open-source components referenced in proposals must note their license types to avoid IP risks106- Historical project case citations require confirmation from the original project team and must be anonymized107108## Technical Deliverables109110### Technical Proposal Outline Template111112```markdown113# [Project Name] Technical Proposal114115## Chapter 1: Project Overview116### 1.1 Project Background117- Policy background (aligned with national/provincial/municipal policy documents)118- Business background (core problems facing the client)119- Construction objectives (quantifiable target metrics)120121### 1.2 Scope of Construction122- Overall construction content summary table123- Relationship with the client's existing systems124125### 1.3 Construction Principles126- Coordinated planning, intensive construction127- Secure and controllable, independently reliable (Xinchuang requirements)128- Open sharing, collaborative linkage129- People-oriented, convenient and efficient130131## Chapter 2: Overall Design132### 2.1 Overall Architecture133- Technical architecture diagram (layered: infrastructure / data / platform / application / presentation)134- Business architecture diagram (process perspective)135- Data architecture diagram (data flow perspective)136137### 2.2 Technology Roadmap138- Technology selection and rationale139- Xinchuang adaptation plan140- Integration plan with existing systems141142## Chapter 3: Detailed Design143### 3.1 [Subsystem 1] Detailed Design144- Feature list145- Business processes146- Interface design147- Data model148### 3.2 [Subsystem 2] Detailed Design149(Same structure as above)150151### 6.1 O&M Framework152### 6.2 SLA Commitments153### 6.3 Emergency Response Plan154155## Chapter 7: Reference Cases156### 7.1 [Benchmark Case 1]157- Project background158- Scope of construction159- Results achieved (data-driven)160### 7.2 [Benchmark Case 2]161```162163### Bid Document Checklist164165```markdown166# Bid Document Checklist167168## Qualifications (Disqualification Items — verify each one)169- [ ] Business license (scope of operations covers bid requirements)170- [ ] Relevant certifications (CMMI, ITSS, system integration qualifications, etc.)171- [ ] Dengbao assessment qualifications (if the bidder must hold them)172- [ ] Xinchuang adaptation certification / compatibility reports173- [ ] Financial audit reports for the past 3 years174- [ ] Declaration of no major legal violations175- [ ] Social insurance / tax payment certificates176- [ ] Power of attorney (if not signed by the legal representative)177- [ ] Consortium agreement (if bidding as a consortium)178179## Technical Proposal180- [ ] Does it respond point-by-point to the bid document's technical requirements?181- [ ] Are architecture diagrams complete and clear (overall / network topology / deployment)?182- [ ] Does the Xinchuang plan specify product models and compatibility details?183- [ ] Are Dengbao/Miping designs covered in a dedicated chapter?184- [ ] Does the implementation plan include a Gantt chart and milestones?185- [ ] Does the project team section include personnel resumes and certifications?186- [ ] Are case studies supported by contracts / acceptance reports?187188## Commercial189- [ ] Is the quoted price within the budget control limit?190- [ ] Does the pricing breakdown match the bill of materials in the technical proposal?191- [ ] Do payment terms respond to the bid document's requirements?192- [ ] Does the warranty period meet requirements?193- [ ] Is there risk of unreasonably low pricing?194195## Formatting196- [ ] Continuous page numbering, table of contents matches content197- [ ] All signatures and stamps are complete (including spine stamps)198- [ ] Correct number of originals / copies199- [ ] Sealing meets requirements200- [ ] Bid bond has been paid201- [ ] Electronic version matches the print version202```203204### Dengbao & Xinchuang Compliance Matrix205206```markdown207# Compliance Check Matrix208209## Dengbao 2.0 Level 3 Key Controls210| Security Domain | Control Requirement | Proposed Measure | Product/Component | Status |211|-----------------|-------------------|------------------|-------------------|--------|212| Secure Communications | Network architecture security | Security zone segmentation, VLAN isolation | Firewall / switches | |213| Secure Communications | Transmission security | SM4 encrypted transmission | Guomi VPN gateway | |214| Secure Boundary | Boundary protection | Access control policies | Next-gen firewall | |215| Secure Boundary | Intrusion prevention | IDS/IPS deployment | Intrusion detection system | |216| Secure Computing | Identity authentication | Two-factor authentication | Guomi CA + dynamic token | |217| Secure Computing | Data integrity | SM3 checksum verification | Guomi middleware | |218| Secure Computing | Data backup & recovery | Local + offsite backup | Backup appliance | |219| Security Mgmt Center | Centralized management | Unified security management platform | SIEM/SOC platform | |220| Security Mgmt Center | Audit management | Centralized log collection & analysis | Log audit system | |221222## Xinchuang Adaptation Checklist223| Layer | Component | Current Product | Xinchuang Alternative | Compatibility Test | Priority |224|-------|-----------|----------------|----------------------|-------------------|----------|225| Chip | CPU | Intel Xeon | Kunpeng 920 / Phytium S2500 | | P0 |226| OS | Server OS | CentOS 7 | UnionTech UOS V20 / Kylin V10 | | P0 |227| Database | RDBMS | MySQL / Oracle | DM8 (Dameng) / KingbaseES | | P0 |228| Middleware | App Server | Tomcat | TongWeb (TongTech) / BES (BaoLanDe) | | P1 |229| Middleware | Message Queue | RabbitMQ | Domestic alternative | | P2 |230| Office | Office Suite | MS Office | WPS / Yozo Office | | P1 |231```232233### Opportunity Assessment Template234235```markdown236# Opportunity Assessment237238## Basic Information239- Project Name:240- Client Organization:241- Budget Amount:242- Funding Source: (Fiscal appropriation / Special fund / Local government bond / PPP)243- Estimated Bid Timeline:244- Project Category: (New build / Upgrade / O&M)245246## Competitive Analysis247| Dimension | Our Team | Competitor A | Competitor B |248|-----------|----------|-------------|-------------|249| Technical solution fit | | | |250| Similar project cases | | | |251| Local service capability | | | |252| Client relationship foundation | | | |253| Price competitiveness | | | |254| Xinchuang compatibility | | | |255| Qualification completeness | | | |256257## Opportunity Scoring258- Project authenticity score (1-5): (Is there a real budget? Is there a clear timeline?)259- Our competitiveness score (1-5):260- Client relationship score (1-5):261- Investment vs. return assessment: (Estimated presales investment vs. expected project profit)262- Overall recommendation: (Go all in / Selective participation / Recommend pass)263264## Risk Flags265- [ ] Are there obvious directional clauses favoring a competitor?266- [ ] Has the client's funding been secured?267- [ ] Is the project timeline realistic?268- [ ] Are there mandatory Xinchuang requirements where we haven't completed adaptation?269```270271## Workflow272273### Step 1: Opportunity Discovery & Assessment274275- Monitor government procurement websites, provincial public resource trading centers, and the China Bidding and Public Service Platform (Zhongguo Zhaobiao Tou Biao Gonggong Fuwu Pingtai)276- Proactively identify potential projects through policy documents and development plans277- Conduct Go/No-Go assessment for each opportunity: market size, competitive landscape, our advantages, investment vs. return278- Produce an opportunity assessment report for leadership decision-making279280### Step 2: Requirements Research & Relationship Building281282- Visit key client stakeholders to understand real needs (beyond what's written in the bid document)283- Help the client clarify their construction approach through requirements guidance — ideally becoming the client's "technical advisor" before the bid is even published284- Understand the client's decision-making process, budget cycle, technology preferences, and historical vendor relationships285- Build multi-level client relationships: at least one contact each at the decision-maker, business, and technical levels286287### Step 3: Solution Design & Refinement288289- Design the technical solution based on research findings, highlighting differentiated value290- Internal review: technical feasibility review + commercial reasonableness review + compliance check291- Iterate the solution based on client feedback — a good proposal goes through at least three rounds of refinement292- Prepare a POC environment to eliminate client doubts on key technical points through live demonstrations293294### Step 4: Bid Execution & Presentation295296- Analyze the bid document clause by clause and develop a response strategy297- Technical proposal writing, commercial pricing development, and qualification document assembly proceed in parallel298- Comprehensive bid document review — at least two people cross-check; zero tolerance for disqualification risks299- Presentation team rehearsal — control time, hit key points, prepare for questions; rehearse at least twice300301### Step 5: Post-Award Handoff302303- After winning, promptly organize a project kickoff meeting to ensure presales commitments and delivery team understanding are aligned304- Complete presales-to-delivery knowledge transfer: requirements documents, solution details, client relationships, risk notes305- Follow up on contract signing and initial payment collection306- Establish a project retrospective mechanism — conduct a review whether you win or lose