上汽集團API管理平臺方案交流書

1、上汽集團API管理平臺方案建議Why Accenture交流議題API讓上汽和上下游伙伴實現(xiàn)共贏埃森哲對本項目的理解從戰(zhàn)略到業(yè)務(wù)，從平臺到運營埃森哲API管理最佳實踐汽車行業(yè)正在進入全新時代埃森哲對汽車行業(yè)的理解2引入全球客戶的領(lǐng)先實踐埃森哲全球API管理案例分享12345汽車行業(yè)將在未來5-7年經(jīng)歷過去一百年從所未有的變革社交網(wǎng)絡(luò)智能設(shè)備的廣泛應(yīng)用定制和個性化開放連接的汽車新能源汽車消費業(yè)務(wù)模式轉(zhuǎn)型標準化無所不能的寬帶網(wǎng)絡(luò)Applicationsproliferation低成本的傳統(tǒng)服務(wù)技術(shù)設(shè)備成本降低vs.功能提升更領(lǐng)先的視頻技術(shù)WORLD IN 2017超過50%的新車都被連接2.11億

2、聯(lián)網(wǎng)的乘用車和商用車WORLD IN 2022+500億鏈接的設(shè)備 & 14+萬億美元的市場世界人口將達到73億大約1500億各種Apps被下載28億 3G & 4.47億 4G 連接2.8萬API基于位置的廣告營銷34顯而易見，新的市場進入者更注重汽車科技的創(chuàng)新，尤其是車載智能/電子技術(shù)將更大程度上決定消費者的購買決定讓消費者為車內(nèi)服務(wù)付費始終是一個巨大挑戰(zhàn)車內(nèi)科技將更大程度上決定消費者的購買決定客戶期待著更為創(chuàng)新和個性化的服務(wù)將各種數(shù)字化渠道連接到汽車帶來更大的市場商機62% are initiating the process online67% buying decision depe

3、nds on the in-car technology42% consumers says that digital will disrupt the entire process 19% of customers are using the digital technology57% confirms that it is imperative and will use it 52% customers expect individualized through digital/social medium before they enter into the showroomOEM/s a

4、re adopting multiple channelsOnly 26% prefer a monthly fee payment option28% would prefer free based services subject to in car advertising (with a possibility to upgrade to premium version for a fee)新的行業(yè)玩家正在打破傳統(tǒng)行業(yè)布局New entrants are placing the end user at the center of every digital experienceDisru

5、pting the age old 100 years models through innovation and technology 5構(gòu)建一個集成的客戶體驗將是主機廠未來的關(guān)鍵業(yè)務(wù)戰(zhàn)略6埃森哲定義的汽車行業(yè)應(yīng)用架構(gòu)支持服務(wù)Enterprise ManagementFinancial ManagementProcurement (indirect)Information ManagementHuman ResourcesEnvironment, Health & Safety ManagementEnterprise Asset ManagementLegal Compliance客戶服務(wù)

6、Customer Relationship ManagementService ManagementMarketing Strategy PlanningCustomer StrategyService Strategy & OfferingService MarketingService Event MgmtService SellingCustomer Account ManagementProfessional ServicesCall Center ManagementIndustrial & commercial control核心服務(wù)能力Sourcing & Procurement

7、Procurement StrategyStrategic Sourcing & Category ManagementRequisition to PaySupplier Relationship ManagementSales & MarketingBrand ManagementProduct & Service MarketingChannel Integration & Management Dealer NetworkChannel Integration & Management - Other Channels Product and Service Sales - Vehic

8、lesProduct Development Product EngineeringProduct Lifecycle ManagementEngineering Change ManagementAfter Sales PartsForecasting & PlanningProduct Design & ManagementSales & MarketingProcurement & Inbound LogisticsWarehouse ManagementOutbound LogisticsAfter Sales ServiceService StrategyTechnical Supp

9、ortWarranty & Recall campaign managementMobilityField Force TransformationSales Force AutomationAnalyticsManagement DashboardWarranty Analytics Reliability Analytics Vehicle Diagnostic Analytics Connected VehicleBusiness DirectionBusiness RealizationBusiness ExecutionProduction & LogisticsProduction

10、 Forecasting, Planning & SchedulingInbound LogisticsManufacturing & AssemblyOutbound Logistics - Built UpOutbound Logistics - CKDCross Core FunctionsCross functional Planning BTOCross functional Planning BTSOrder ManagementQuality ManagementRemanufacturingSupply Chain PlanningWhy Accenture交流議題API讓上汽

11、和上下游伙伴實現(xiàn)共贏埃森哲對本項目的理解從戰(zhàn)略到業(yè)務(wù)，從平臺到運營埃森哲API管理最佳實踐汽車行業(yè)正在進入全新時代埃森哲對汽車行業(yè)的理解7引入全球客戶的領(lǐng)先實踐埃森哲全球API管理案例分享123458典型的API商業(yè)模式激勵開發(fā)者/合作伙伴間接提升企業(yè)收入B2B集成提升合作伙伴運營效率利用外部力量進行R&D研發(fā)提升某些業(yè)務(wù)能力或資產(chǎn)的知名度用戶使用即付費促進收入增長促進高效運營/降低運營成本對于企業(yè)擁有的任何業(yè)務(wù)資產(chǎn)，需要定義合理而清晰的業(yè)務(wù)目標和商業(yè)/盈利模式，API將是實現(xiàn)定義的商業(yè)目標的重要技術(shù)手段之一1234569典型API商業(yè)模式在行業(yè)巨頭中的應(yīng)用用戶喜好行業(yè)熱點品牌美譽度危機事件追

12、蹤二手車檢測二手車認證二手車估值二手車質(zhì)保全品牌配件庫零配件技術(shù)參數(shù)零配件供應(yīng)商信息同質(zhì)件認證維修保養(yǎng)記錄事故記錄主機廠經(jīng)銷商配件商維修站保險公司汽車行業(yè)輿情和政策汽車配件二手車檢測和認證維修保養(yǎng)5213上汽API管理平臺業(yè)務(wù)價值分析車享網(wǎng)場景人的數(shù)據(jù)汽車感知數(shù)據(jù)駕駛行為數(shù)據(jù)產(chǎn)業(yè)鏈數(shù)據(jù)保養(yǎng)預(yù)約安防救援車況檢測異常報警客戶駕駛習(xí)慣分析品牌關(guān)注度分析品牌美譽度分析客戶偏好分析維修保養(yǎng)聲量分析改裝熱點分析二手車關(guān)注點分析車輛使用情況分析車輛事故情況分析保險定價保險理賠廣告發(fā)布引流服務(wù)廣告商車主經(jīng)銷商保險公司主機廠提供個性化服務(wù)，增加用戶粘性提供一手市場信息，支持市場決策提供市場行情與客戶偏好，便于營

13、銷決策提供準確的車況，便于定價，加速理賠流程增加流量，以及廣告定向投放，精準營銷52134上汽API管理平臺業(yè)務(wù)價值分析斑馬汽車場景12埃森哲將幫助上汽設(shè)計和實施一個“最合適”的API管理平臺來支撐上汽生態(tài)建設(shè)Systems of Engagement靈活的系統(tǒng)Systems of Record 后端系統(tǒng)API管理平臺IoT DevicesEnterprise Service BusBPMService AService BService nOther access services車主畫像財務(wù)服務(wù)支付服務(wù)會員服務(wù)其他系統(tǒng)整車服務(wù)商務(wù)服務(wù)API ServicesManage, SecureDe

14、veloper ServicesDesign Tools Analytic ServicesE2E VisibilityAPI Management Tool and Gateway埃森哲和全球主流API廠商建立了合作伙伴關(guān)系，可以聯(lián)合為上汽建設(shè)世界領(lǐng)先的API管理平臺13API管理平臺高階部署架構(gòu)服務(wù)設(shè)計者：設(shè)計者根據(jù)業(yè)務(wù)需求設(shè)計、開發(fā)和封裝服務(wù)，設(shè)計者可以創(chuàng)建服務(wù)和接口并實現(xiàn)它，但不能管理服務(wù)的全生命周期服務(wù)發(fā)布者：發(fā)布者是統(tǒng)一管理服務(wù)生命周期的管理角色，將平臺上的服務(wù)發(fā)布出去供使用者使用，并監(jiān)控管理服務(wù)的使用情況等服務(wù)使用者：通過服務(wù)管理平臺搜索、發(fā)現(xiàn)并使用服務(wù)，可以根據(jù)使用情況對服務(wù)進

15、行評價和推薦等服務(wù)引擎關(guān)鍵用戶14API管理平臺關(guān)鍵技術(shù)能力（一）多租戶機制 每個租戶擁有隔離的Domain，每個Domain下創(chuàng)建多個管理用戶，管理自己的數(shù)據(jù)和服務(wù)API 每個Domain分配完整的服務(wù)資源 超級租戶有自己的配置和權(quán)限機制 每個租戶有自己的安全特性，分配一套用戶和權(quán)限1支持單點登SSO2 API Manager可以做User Store API Manager可以做Identity Server和Service Provider 使用MySQL/Oracle數(shù)據(jù)庫支持緩存Cache3API Gateway cacheResource cacheKey Manager cach

16、eResponse cache支持多種平臺數(shù)據(jù)庫4Setting up IBM DB2Setting up DerbySetting up H2Setting up IBM InformixSetting up Microsoft SQLtruetruetrue/EnableKeyMgtValidationInfoCache Setting up MySQLSetting up MySQL ClusterSetting up OpenEdgeSetting up OracleSetting up Oracle RACSetting up PostgreSQL15API管理平臺關(guān)鍵技術(shù)能力（二）

17、獨立的API生產(chǎn)環(huán)境和Sandbox環(huán)境5 單Gateway處理轉(zhuǎn)發(fā)請求到生產(chǎn)和Sandbox環(huán)境 多Gateway分別處理請求到生產(chǎn)和Sandbox環(huán)境支持多種傳輸協(xié)議6HTTP PassThrough TransportHTTP-NIO TransportHTTPS-NIO TransportHTTP Servlet TransportHTTPS Servlet TransportFIX TransportJMS TransportVFS TransportLocal TransportMailTo TransportMSMQ TransportRabbitMQ AMQP Transpor

18、tTCP TransportUDP TransportHL7 TransportMulti-HTTPS TransportMQTT Transport16API管理平臺關(guān)鍵技術(shù)能力（三）JSON message builders and formattersXML representation of JSON payloadsConverting a payload between XML and JSON請求報文格式的轉(zhuǎn)換7mons.json.JsonStreamBuildermons.json.JsonStreamFormattermons.json.JsonBuildermons.jso

19、n.JsonFormatterJson Stream格式處理器Json XML格式處理器API限流功能安全考慮To protect your APIs from common types of security attacks such asdenial of service (DOS)可用性考慮To regulate traffic according to infrastructure availability計費考慮To make an API, application or a resource available to a consumer at different levels o

20、f service, usually for monetization purposeOS-level settingsJVM-level settingsWSO2 Carbon platform-level settingsAPIM-level settings不同級別的性能調(diào)優(yōu)方法8917埃森哲建議上汽引入DevOps方法來實施API管理平臺目標人員組織運作流程工具支撐工具開發(fā)機制服務(wù)化灰度發(fā)布預(yù)發(fā)布大小迭代版本火車應(yīng)用監(jiān)控RallySVN自動化審核/構(gòu)建/集成/測試/部署敏捷高效“二段三步”“三方協(xié)作”版本需求版本原型版本上線需求討論需求設(shè)計UI設(shè)計代碼開發(fā)測試驗證切換驗證業(yè)務(wù)BA開發(fā)業(yè)

21、務(wù)BA開發(fā)業(yè)務(wù)BA開發(fā)業(yè)務(wù)BA開發(fā)業(yè)務(wù)BA開發(fā)在確定的目標下，業(yè)務(wù)/系統(tǒng)分析/開發(fā)三個角色緊密協(xié)作，敏捷迭代Software EngineersAPI運營CoE示例BackendIntegrationsSolutionArchitectsQABig Data公司級領(lǐng)導(dǎo)支持DeveloperCommunityManagerPartnerSupportBusinessLiaisons核心技術(shù)成員，多年API后端及Web研發(fā)架構(gòu)經(jīng)驗業(yè)務(wù)和IT領(lǐng)導(dǎo)層的聯(lián)合管理委員會Social, technical, evangelistInternal transformation and development

22、skillsCreative, hands-on business development skillsAPI產(chǎn)品經(jīng)理APIDesignerAPIDevOps +Configuration多年軟件產(chǎn)品研發(fā)管理經(jīng)驗Strong web-centric data architecture skillsIn depth platform expertiseSecurity* Business department-specificWhy Accenture交流議題API讓上汽和上下游伙伴實現(xiàn)共贏埃森哲對本項目的理解從戰(zhàn)略到業(yè)務(wù)，從平臺到運營埃森哲API管理最佳實踐汽車行業(yè)正在進入全新時代埃森哲對汽車

23、行業(yè)的理解19引入全球客戶的領(lǐng)先實踐埃森哲全球API管理案例分享1234520埃森哲建議參考開放API能力模型來規(guī)劃、設(shè)計、建設(shè)和運營API平臺及相關(guān)生態(tài)體系 API管理框架 Ecosystem 生態(tài)建設(shè) API 開發(fā)和部署 生命周期管理和支持 API 技術(shù)和架構(gòu)埃森哲API能力模型API Management TechnologyAPI Management tool selectionTooling & ImplementationAPI ArchitectureReference ArchitectureStandards & Guidelines 戰(zhàn)略和價值 API StrategyA

24、nalysisPrioritisationUse CasesIdentificationAPI to Use Case MappingBusiness CaseServices BundlingMonetisation 12InfrastructureDesign and Deployment3Governance & Operating ModelAPI GovernanceAPI Operating Model within BankIndustry Working Group Operating Model& MethodologiesStakeholder ManagementProg

25、ram ManagementMetrics & ReportingService DeliveryGo Live & Production ReleaseRelease ManagementService SupportDeveloper & Portal SupportIncident ManagementService OptimisationOptimisation & AnalyticsAPI PerformanceAgile SprintsDesign , BuildTest , DocumentBeta LaunchAPI MarketingHackathons Events &

26、Focus GroupsInnovation Days Partner ManagementIdentification & EngagementOnboardingLegal and Contractual FrameworkInitial Set-upDesign PatternsShared identitySecurityEnvironment set-up564API SandboxAPI CatalogueStubbed Developer PortalAnalytics & DashboardReference Apps我們的能力模型基于全球最佳實踐和跨越多個行業(yè)的項目經(jīng)驗來構(gòu)建

27、，建立在成功交付了全球超過100個大型企業(yè)客戶的基礎(chǔ)之上21埃森哲認為，只有“技術(shù)”層面的APIs是遠遠不夠的我們建議制定一個戰(zhàn)略驅(qū)動的API管理/開發(fā)和運營方法來實現(xiàn)企業(yè)業(yè)務(wù)目標驅(qū)動API定義個管控想做什么？Implement Mobility ProgramAccelerate DevelopmentDirect MonetizationDrive Brand Awareness需要什么數(shù)據(jù)?CustomerEnd-UserContent目標用戶是誰?InternalBusiness PartnerPaid userFree user如何訪問?SecurityCachingTransfor

28、mationTraffic Shaping如何判斷成功標準?SLAPass through RevenueReduced Implementation TimeValue of 3rd Party ApplicationsIncreased Web Traffic策略和監(jiān)控22埃森哲建議的統(tǒng)一的API建設(shè)方法指引API全生命周期管理以下5個過程回答了常見的“企業(yè)如何構(gòu)建好的API”的問題Strategy Sets the business goals and value proposition, Answers key questions like “what do you want your

29、 APIs to do” and how you measure success”Governance Accounts for the risk and responsibility Identifies the API owners and sponsorshipsDesign Defines the needed APIs and “what each API does” from a technical perspective Results in a set of API definitionsBuild Uses standard implementation patterns f

30、or consistent application of best practices Implements the APIsOperate/ Evolve Leverages API management tools to manage and monitor Feeds back into analytics 埃森哲觀點：API建設(shè)不是一次性構(gòu)建過程，而是一個不斷循環(huán)的優(yōu)化過程 231、Strategy: 設(shè)定明確的業(yè)務(wù)目標和商業(yè)模式，回答某個API的商業(yè)模式是什么API商業(yè)模式在最近10年經(jīng)歷和發(fā)展了很多，如：Google free use, eBay developer pay for

31、 use, A developer gets paid via a revenue share model, S indirect，等等。242、Governance: 立足于API的管控機制，如API擁有者是誰，以及他們的管理職責(zé)等識別API影響的數(shù)據(jù)識別數(shù)據(jù)的所有者定義保護數(shù)據(jù)的策略讓所有者授權(quán)和確定API的訪問范圍API所有者和數(shù)據(jù)所有者共同監(jiān)控API的訪問識別數(shù)據(jù)和所有者: Each data owner (the owner or controller is the one with responsibility for the data) has developed procedu

32、res, data formats, and terminology that fit its unique situation and preferences. Governance is needed to integrate data possibly from different owners in a reliable, accurate, and secure manner制定數(shù)據(jù)保護策略: E.g., the data provided by your API might be misused and can result in rights infringement. For

33、example, Craigslist sued Padmapper and 3Taps for copyright infringement. One of the ways to mitigate the risk is to build a rights management system to allow filtering of data for different users as part of your data governance strategy.數(shù)據(jù)訪問授權(quán): Understanding your competitive advantages and protectin

34、g them is a critical aspect of your API design and offering. Governance ensures that you to expose the right assets to the right audiences, allowing you to protect yourself from your competitors. The data owner works with the API sponsor (the business champion who drives the business case and tracks

35、 the development for the API) to ensure that enough scope is enabled while balancing exposure so that business goals are met.253、Design: 從技術(shù)層面定義和設(shè)計API的功能，回答“每個API干什么”的問題技術(shù)層面要考慮如下6方面的設(shè)計要素安全管理 Safeguards API access to match authorization levels.主動監(jiān)控 catches operations problems while theyre small.流量管理

36、rate limits usage or redirects requests so that the API stays up, regardless of traffic spikes caused by legitimate interest, buggy clients, or malicious attacks.版本管理 ensures the functioning of client applications using an old API version even with the release new versions. 技術(shù)實現(xiàn) determines the inter

37、faces (REST v SOAP) and the representation (JSON v XML)使用分析 provides information to make future decisions (e.g., what APIs are used, by whom, are SLAs met)BasicAPISecurity ManagementProactiveMonitoringTraffic ManagementVersioningManagementAnalyticsAPI設(shè)計要素Technical Implementation263、Design: 借鑒和應(yīng)用設(shè)計最佳

38、實踐來設(shè)計和實現(xiàn)API，最小化風(fēng)險和返工的可能性PatternBehaviorDecision CriteriaConsequenceCache as SoR (System of Record)All data cached before hand- Smaller data set- Limited parameters- Low volatility data- High cache hit %- DB offline operation- Best synchronous performance- Published contractRead-through cacheData cac

39、hed on-demand- Larger data set- Limited parameters- Volatile data- High cache hit %- Synchronous- Requires HA DB- Published contractDirect readsAlways read from the DB- OData queries- Volatile data- Large data set- Low cache hit % or data isnt cacheable- Synchronous- Requires HA DB- Schema changesWr

40、ite through serviceService performs write operation- Granular changes- Highly scalable- Asynchronous write- DB offline operation- Published contractPublish / SubscribeReal-time notification- Always publish (its free!)- Highly scalable- Real time updates- DB offline operation- Published contract- Asy

41、nchronous- Loosely coupled systems以下僅僅列出可以借鑒的部分設(shè)計模式來優(yōu)化API的設(shè)計和開發(fā)，很多成熟的設(shè)計模式（Faade/Gataway/Cache/Throtting等）都要在設(shè)計和實現(xiàn)過程中加以合理化應(yīng)用274、Build: 合理利用API管理工具/平臺來管理和監(jiān)控API后端服務(wù)提供者RequestAPI faade URLAPI網(wǎng)關(guān)在服務(wù)請求的路徑上和服務(wù)返回的路徑上可以應(yīng)用一系列策略來進行服務(wù)的安全、路由、轉(zhuǎn)換等處理可以增加的Policy：流量管理 protects your backend services from high traffic (

42、e.g., rate limit, cache)安全控制 who can access your APIs (e.g., OAuth)中介服務(wù) provides data transformations (e.g., JSON, XML)擴展服務(wù) implement custom behaviors (e.g., Java, Javascript, Python, mash-up via service callouts)分析監(jiān)控 monitors the use and health of APIs Target URLTarget URLTarget URLRate LimitOAuthM

43、ash-upXML JSONAve. DelayAPI網(wǎng)關(guān)提供了管理Faade來隔離API使用者和后端服務(wù)提供者，在這里可以提供雙向的各種策略性配置和管控285、Operate: 持續(xù)收集API使用信息，分析后進行必要的戰(zhàn)略和運營調(diào)整API管理工具或平臺都可以進行API監(jiān)控和分析，幫助API運營企業(yè)持續(xù)優(yōu)化和調(diào)整API戰(zhàn)略和運營方向，以下是典型的API運營KPI市場Developer RegistrationsDeveloper portal funnelTraffic SourcesEvent Metrics支持能力Support ticketsResponse TimesCommunity

44、 Metrics商業(yè)Direct RevenueIndirect RevenueMarket ShareCosts流量Total CallsTop MethodsCall ChainsEvent MetricsQuota faults開發(fā)者TotalActiveTrending AppsRetention服務(wù)PerformanceAvailabilityError RatesCode Defects29埃森哲API管理平臺參考架構(gòu)埃森哲API管理平臺參考架構(gòu)較全面的識別和定義了企業(yè)開放API的關(guān)鍵技術(shù)能力，對于企業(yè)構(gòu)建自己的API管理平臺具有指導(dǎo)意義開發(fā)者Portal規(guī)則 &合同Create

45、/ EditAssign to APIs & AppsAppID / ApiKeySupportHierarchical Permissions監(jiān)控Custom ReportsReal TimeMonitoringAd HocReportingReport SchedulingAPI訂閱CollaborationSelf ServiceRegistrationDev ConsoleSandboxDocumentation& SDKsDashboardsAPI發(fā)布API/APPProvisioningAPI/APP VersioningCreate Policies & ContractsAPI

46、/APPPermissionsAPI Key ManagementDiscovery(Search)Portal 管理User ManagementGateway ManagementManagementDashboardsGateway MonitoringDelegated AdministrationSupport TicketSystem其他Portal BrandingContent ManagementManagement APIPolicy/ContractEditor UIRuntime治理規(guī)則OperationalComplianceQoSSecurityMediationA

47、ggregation(Policy Sets)合同Consumer(AppID/ApiKey)End UserAnonymousHierarchical AssignmentSet Valid Dates/TimesSLAs其他TemplatesWorkflow IntegrationManagement APIGatewayTraffic 管理QoS SupportSpike LimitTransactionLimitSLAEnforcementConcurrent Users Limit高可用ClusteringHealth ChecksLoad BalancingDisasterReco

48、veryRuntime處理SSLTerminationURL MappingEncryption/DecryptionPolicy / ContractEnforcementCORS SupportPolicy / Contract Caching后臺管理WSDL / WADLSupportMiddleware ConnectorsIdentity ImpersonationError Handling& MaskingNative Runtime AgentsSOA / ESBIntegrationData CachingSSL Termination& Pass Through安全Auth

49、enticationAuthorizationIAM IntegrationNon-repudiation運維支持Error HandlingLoggingSystemsMonitoringEvent Notifications增值服務(wù)協(xié)議和消息管理ProtocolTranslationMessageTransformationMessageEnrichmentMessageValidationMessage Compression數(shù)據(jù)服務(wù)Direct Data AccessSystem of Record ServicesCodes TableMetadata ServicesCold Ca

50、chingmBaaSGeolocation ServicesNative Mobile AgentsPush Notification ServicesMobile SDKsGovernance MonitoringBig DataBusiness IntelligenceEdge AnalyticsMonitoring Tool Integration產(chǎn)品化Monetization ServicesBilling ServicesOEM BundlingThird Party API IntegrationCustomer of Customer SvcsService Level Cont

51、ract MgmtCRM IntegrationIdentity ManagementPhase1Phase2Phase3Why Accenture交流議題API讓上汽和上下游伙伴實現(xiàn)共贏埃森哲對本項目的理解從戰(zhàn)略到業(yè)務(wù)，從平臺到運營埃森哲API管理最佳實踐汽車行業(yè)正在進入全新時代埃森哲對汽車行業(yè)的理解30引入全球客戶的領(lǐng)先實踐埃森哲全球API管理案例分享12345開始能力對外開放起初開放的僅為10+個API每個月的能力調(diào)用次數(shù)約為3億次20102012.62013.12對外開放API有78個第三方開發(fā)人員約有24,000個每個月的能力調(diào)用次數(shù)約為60億次對外開放API有1,455個第三方開發(fā)

52、人員超過30,000個每個月的能力調(diào)用次數(shù)約為82.5億次AT&T 能力開放過程：在外部市場快速變化的時代，“能力開放平臺項目”是我們架構(gòu)上的選擇，來協(xié)助企業(yè)加速。 John Donovan 公司副總，技術(shù)與網(wǎng)絡(luò)運營部門, 2012）五年內(nèi)，我們要達到全公司API化（能力服務(wù)化） Laura Merling 公司副總，生態(tài)系統(tǒng)與解決方案部門, 2013）AT&T 早在2010年認知，面對外在的快速變化與OTT競爭，唯有利用自身的行業(yè)能力優(yōu)勢并加以開放，同時吸引合作伙伴共同創(chuàng)新，才是生存之道AT&T 開放的能力非常多樣化，從核心的BSS/OSS能力，到多樣的產(chǎn)業(yè)平臺能力，提供合作伙伴豐富的創(chuàng)造空

53、間AT&T U-verse Enabled:提供網(wǎng)絡(luò)電視用戶與移動用戶的信息交互AT&T M2X:透過網(wǎng)絡(luò)為物聯(lián)網(wǎng)提供相關(guān)云存儲服務(wù)AT&T Mobile Identity API Toolkit:保證移動用戶的交易安全AT&T Sponsored Data API:客戶在使用某些APP時無需付費，使用某些服務(wù)時，還可贏得流量Other API Platforms：語音辨識與轉(zhuǎn)換:提供19個國家語音轉(zhuǎn)文字，以及文字轉(zhuǎn)語音能力短信發(fā)送:發(fā)送及時短消息多媒體消息發(fā)送:發(fā)送影音、視頻In-APP Messaging:發(fā)送并接收來自APP的消息賬單與收款:借由AT&T賬單進行出賬與收款手機廣告:合作伙

54、伴可提成高達80%移動設(shè)備信息:用戶移動設(shè)備的型號、廠商、固件版本手機通信錄:創(chuàng)建、存儲與獲取手機通信錄信息Voice：Messaging：Monetization：Information：AT&T 在打造友善的能力開放平臺生態(tài)環(huán)境，吸引開放者踴躍創(chuàng)新上非常成功，主要有以下舉措：提供開發(fā)者APP調(diào)優(yōu)工具快速反應(yīng)開放者問題時常舉辦編程馬拉松 (hackathon)完善且友善的能力開放平臺1AT&T開放了多樣化的能力，攜手埃森哲、Apigee等廠商，提供簡易上手、獨立的開發(fā)編程環(huán)境，以及完善的開發(fā)文檔與編程示例，建立了非常友善的開發(fā)平臺。透過開發(fā)者編程馬拉松，設(shè)定不同專題引導(dǎo)創(chuàng)新，設(shè)立獎項吸引開發(fā)

55、者，與優(yōu)勝團隊合作推廣商業(yè)應(yīng)用。2012年AT&T共舉辦了28場編程馬拉松，平均一個月超過2場，一共超過3,000個開發(fā)者參加。開放者的技術(shù)能力不一，AT&T有專門團隊為開發(fā)者解答問題，降低開發(fā)困難度，讓開發(fā)者保持熱情。建立開發(fā)者線上論壇，提供開發(fā)者相互討論的空間。AT&T 為開發(fā)者提供了多種免費的APP的調(diào)優(yōu)工具 - Application Resource Optimizer (ARO)，幫助開發(fā)者做出更效能更好、更省電的應(yīng)用APP。發(fā)布工具文檔，并舉辦相關(guān)講座。234案例借鑒：1. 企業(yè)級能力開放平臺需要具備全面的管理能力MobilityAnalyticsCloudDigital Bus

56、iness Area Traffic ManagementSecurityMediationMobile OptimizationScale to Multiple RegionsPartner CustomizationOnboardingVersioningAPI DocumentationAnalyticsDeveloper AuthenticationTransformationMonetization (API的格式轉(zhuǎn)換)(安全管理)(流量管理)(配合合作伙伴的客制化能力)(移動裝置API的最佳化)(管理多區(qū)域并統(tǒng)一運營)(標準的API版本管理)(自動化、流暢的開發(fā)者注冊與開發(fā))(開

57、發(fā)者認證)(API文檔管理)(API使用分析)(靈活的收費模式)案例借鑒：2. 能力開放需要從企業(yè)范圍整體考量，尤其包含與其他平臺的合作電子渠道三方渠道產(chǎn)品合作伙伴開發(fā)社區(qū)CP/SP移動支付.移動終端車聯(lián)網(wǎng)企業(yè)級能力開放平臺短信平臺CRMBOSS大數(shù)據(jù)音樂基地閱讀基地物聯(lián)網(wǎng)位置基地.企業(yè)級服務(wù)總線（開發(fā)者與使用者）（企業(yè)內(nèi)部，能力提供與平臺運營）API Strategy & GovernanceAPI ManagementAPI PlanningApp DevelopmentAPI Analytics設(shè)定業(yè)務(wù)目標并建立業(yè)務(wù)模式與整體價值展現(xiàn)完整、統(tǒng)一的API生命周期管理（從設(shè)計、開發(fā)到運營）選

58、定API owner/ sponsors，在既定的戰(zhàn)略下，負責(zé)執(zhí)行與風(fēng)險管控定義API平臺管控模式，并明確與現(xiàn)有IT管控的關(guān)系建立提供數(shù)據(jù)與服務(wù)的機制，來滿足業(yè)務(wù)需求創(chuàng)建API，并透過開放將其變現(xiàn)提供對現(xiàn)有的產(chǎn)品與API加值的平臺對重復(fù)、低效率的API進行審核、改善或淘汰管理開發(fā)者平臺，包括注冊、審批、協(xié)作與安全等規(guī)劃階段：明確開發(fā)的APP能驅(qū)動業(yè)務(wù)創(chuàng)新、業(yè)務(wù)轉(zhuǎn)型或業(yè)務(wù)價值設(shè)計階段：明確APP的設(shè)計能支持業(yè)務(wù)戰(zhàn)略與用戶以及合作伙伴密切協(xié)作建立一套對現(xiàn)有API清楚了解并可分析、管理的機制 對API項目迭代、演進的分析管理對API生態(tài)系統(tǒng)至少要有以下的分析管理：API管理分析、APP分析、后臺系統(tǒng)

59、分析以及外部開發(fā)者分析新API開發(fā)，將現(xiàn)有系統(tǒng)接口API化設(shè)計階段：從技術(shù)角度出發(fā)，審視API功能，進而驅(qū)動戰(zhàn)略，并滿足管控要求開發(fā)階段：結(jié)構(gòu)性的開發(fā)方法來降低開發(fā)風(fēng)險，并提升效能，DevOps：以互聯(lián)網(wǎng)產(chǎn)品開發(fā)方式，迅速開發(fā)、部署APP案例借鑒：3. API生態(tài)系統(tǒng)關(guān)注重點一些埃森哲API客戶及開發(fā)者社區(qū)/門戶37/index.htmlGM Open API示例38Why Accenture交流議題API讓上汽和上下游伙伴實現(xiàn)共贏埃森哲對本項目的理解從戰(zhàn)略到業(yè)務(wù)，從平臺到運營埃森哲API管理最佳實踐汽車行業(yè)正在進入全新時代埃森哲對汽車行業(yè)的理解39引入全球客戶的領(lǐng)先實踐埃森哲全球API管理案

60、例分享1234540行業(yè)方面，埃森哲全球有超過3000位汽車行業(yè)解決方案專家，為全球各大車企以及汽車服務(wù)類企業(yè)提供專業(yè)服務(wù)特定專業(yè)領(lǐng)域Engineering, Product Development and PLMSales & Marketing developing dealers and managing campaignsAfter SalesManufacturing, LogisticsFinance and Performance Management providing shared services to major clients globallyHuman Resourc