Home

Results 1 - 10 of 270,506 for busy components. Search took 1.498 seconds.  
Sort by date/Sort by relevance
The CCTS key concepts are based on two levels of abstraction — core components and business information entities. 5.1 Core Components The foundational concept of this specification is the core component. (...) Core components are the linchpin for creating interoperable business process models and business documents. (...) Equally, the term business information entity is used as a generic term encompassing aggregate business information entities, basic business information entities, and association business information entities and their properties. 5.1.1 Aggregate Core Component An Aggregate Core Component (ACC) is a collection of related pieces of information that together convey a distinct meaning, independent of any business context.
Language:English
Score: 971558.8 - https://unece.org/fileadmin/DA...ortrade/CCTS/CCTS-Version3.pdf
Data Source: un
Core components are the linchpin for537 creating interoperable business process models and business documents. (...) Relationships Between Core Components and Business Information669 Entities670 The relationships between CCs and BIEs are described in Figure 5-2. (...) If a BCC or706 ASCC has the cardinality [0..*], the derived BBIE or ASBIE may have the same707 5 The Core Components’ Context mechanism provides the more detailed linkage between specific business data and the exact circumstances of its business use.
Language:English
Score: 968433.6 - https://unece.org/fileadmin/DA.../CCTS-SecondIteration-ODP6.pdf
Data Source: un
Finance Core Components P4. Finance Business Process Modelling P5. (...) Business neutral core component Library Project leader: Sue Probert ( Sue.Probert@commerceone.com ) 1. (...) Deliverables The deliverables from the project are the basis of the Global Core Components Library: • A catalogue of Business Neutral Core Components including Core Component Type, Basic Core Components and Aggregate Core Components. • Data Dictionary. • Vocabulary of referenced terms. 3.
Language:English
Score: 954877.3 - https://unece.org/fileadmin/DA...nary/plenary02/docs/02cf15.pdf
Data Source: un
An RSM includes the conceptual data model (from BRS), canonical data model, business information entity library references, and core component library references. (...) (a) RSM is initiated within TBG by a project team and is completed when existing Core Components have been identified and candidate Core Components have been proposed to satisfy the business requirements defined in the BRS; (b) The new and amended business information entities (BIEs) requested in the RSM are processed for implementation by the TBG harmonization working group (TBG17). (...) For example, a bulk submission is possible when a specific sector submits a set of candidate Core Components and/or UML artefacts that it has extracted from an existing repository of business processes.
Language:English
Score: 940673.4 - https://unece.org/fileadmin/DA...lenary/plenary09/cf_09_19E.pdf
Data Source: un
UN/CEFACT eBTWG Project Organization eBTWG consists of eleven project teams as shown in Fig. 1: • UN/CEFACT eBusiness Architecture (UEA) • Business Collaboration Patterns and Monitored Commitments (BCP&MC) • Business Entity Library (BEL) • Business Collaboration Protocol Specification (BCP) • Common Business Process Catalog (BP CAT) • Business Process Information Model Exchange Schema (BPIMES) • Core Components (CC) • Core Components Supplement (CCS) • Core Components Realization (CCR) • Business Process Specification Schema (BPSS) • UML to XML Design Rules (UML2XML) Current ebXML Organization Legend:Legend: UMMUMM = UN/CEFACT Modeling Methodology BCP+MCBCP+MC= Business Collaboration Patterns and Monitored Commitments BELBEL = Business Entity Library BCPBCP = Business Collaboration Protocol Specification BP CATBP CAT = Common Business Process Catalog BPIMESBPIMES = Business Process Information Model Exchange Schema CCCC= Core Component Specification CCS = Core Component Supplement CCRCCR= Core Component Realization BPSS 2.0BPSS 2.0= Business Process Specification Schema short-term fixup BPSS 3.0BPSS 3.0= BPSS next generation UMLUML -->XML>XML= UML to XML Design Rules CPPACPPA= OASIS ebXML CPPA MSGMSG = OASIS ebXML Messaging REG/REPREG/REP= OASIS ebXML Registry / Repository IIC IIC = Implementation, Interoperability, and Conformance ArchitectureArchitecture CCCCBELBELBCPBCP BCP+MCBCP+MC UMLUML-->>XMLXML CCRCCR BP CATBP CAT BPIMESBPIMESCPPACPPA MSGMSG REG/REPREG/REP BPSS 2.0BPSS 2.0 BPSS 3.0BPSS 3.0 UMMUMM Storage format CCSCCS Source: eBTWG IICIIC The UN/CEFACT Modeling Methodology (UMM) provides the framework under which the eBTWG project teams concurrently develop technical specifications that fit seamlessly together with sufficient detail for eBTWG conformant implementation. (...) In turn, reusable blocks of core components/business information entities are harvested in creating the initial content of a CC library. CCR provides the technical specification for ‘realizing’ conceptual core components/business information entities in XML format so that they can be stored and retrieved in (from) the ebXML REG/REP.
Language:English
Score: 937764.1 - https://unece.org/fileadmin/DA...nary/plenary02/docs/02cf37.pdf
Data Source: un
Core Components Business Document Assembly (CCBDA) | UNECE Skip to main content English Advanced Search   Main navigation About UNECE Executive Secretary Mission Organizational structure Secretariat Executive Committee Commission Legal instruments Work with us Our work Economic Cooperation & Integration Environmental Policy Forests Housing & Land Population Sustainable Energy Statistics Trade Transport Themes High-impact Areas Circular Economy Gender SPECA Technical cooperation THE PEP UN SG's Special Envoy for Road Safety UN Road Safety Fund UN cooperation in the UNECE region Regional Forum on Sustainable Development SDGs Open UNECE Events Meetings & Events Information for Delegates Coronavirus Advisory Publications Media Executive Secretary's Blog News Press Releases Covid-19 Press Releases Speeches Stories UNECE Weekly Videos UNECE Trade Trade Facilitation and E-business(UN/CEFACT) Core Components Business Document Assembly (CCBDA) More options Trade Facilitation and E-business(UN/CEFACT) Trade Programme Trade Facilitation and E-business - UN/CEFACT COVID-19 Response About us Introduction UN/CEFACT Heads of Delegation Bureau Programme Development Areas (PDAs) Memoranda of Understanding (MoUs) UN/LOCODE Advisory Group Advisory Group on Advanced Technologies (AGAT) Traceability of Sustainable Value Chains Domains Projects Public Reviews Outputs Recommendations Trade Facilitation Recommendations Code List Recommendations Standards Streamlined presentation of UN/CEFACT standards UN/LOCODE UN/LOCODE Code List by Country and Territory UN/LOCODE Country Subdivisions ISO 3166-2 UN/LOCODE National Focal Points UN/LOCODE since 1981 e-Basel e-CERT UN/FLUX standard e-Invoice Business Requirement Specifications (BRS) Reference Data Models (RDM) Core Components Library (UN/CCL) UNCCL - Archives ISO/TC 154 Requirements Specification Mappings (RSM) XML Schemas UN/EDIFACT Introducing UN/EDIFACT Directories 2021 2011-2020 2000-2010 1995-1999 Download Service Codes Data Maintenance Requests (DMR) DMR forms DMRs by Regional log number Archives by UN log number Archives by Regional log number Messages in Development (MID) UNTDED-ISO7372 Technical Specifications CCTS Data Type Catalogue Core Component Technical Specification Core Components Business Document Assembly UML Profile for Core Components XML Naming and Design Rules Exchange Header Envelope (XHE) Procedures For Reference Data Model (RDM) & Associated Artefacts Publication UN/CEFACT Modelling Methodology (UMM) Guidance Material Meetings and Events Publications Join UN/CEFACT Policies, Procedures and Terms of Reference ARCHIVES-Policies, Procedures and Terms of Reference Case Study Repositories Single Window Repository UNECE NTFB Repository NTFB - Background UN/LOCODE Child Code Repository Call to Action on Improved Digitalization Through the Use of UN/CEFACT Standards Highlights (Archives) Media Clippings Core Components Business Document Assembly (CCBDA) Document Title Download Core Components Business Document Assembly Technical Specification (CCBDA) version 1.1 pdf Core Components Business Document Assembly Technical Specification (CCBDA) version 1.0 pdf ABOUT UNECE Mission Executive Secretary Organizational Structure OPPORTUNITIES Vacancies Internship Programme RESOURCES Statistical Database Evaluations Follow UNECE Facebook Twitter Contact us Flickr Rss Youtube Instagram © United Nations Economic Commission for Europe | Terms and Conditions of Use | Privacy Notice Contact us
Language:English
Score: 933018.75 - https://unece.org/trade/uncefact/ccbda
Data Source: un
UN/CEFACT United Nations Centre for Trade Facilitation and Electronic Business © UN/CEFACT Core Components Data Type Catalogue Version 3.0 Page 1 of 88 UN/CEFACT Core Components Data Type Catalogue Version 3.0 29 September 2009 UN/CEFACT United Nations Centre for Trade Facilitation and Electronic Business © UN/CEFACT Core Components Data Type Catalogue Version 3.0 Page 2 of 88 Abstract CCTS 3.0 defines the rules for developing Core Data Types and Business Data Types to define the value domains for Basic Core Compo- nents Basic Core Component Properties, Basic Business Information Entities, and Basic Business Information Entity Properties. (...) UN/CEFACT United Nations Centre for Trade Facilitation and Electronic Business © UN/CEFACT Core Components Data Type Catalogue Version 3.0 Page 27 of 88 4.1.7 Amount. (...) UN/CEFACT United Nations Centre for Trade Facilitation and Electronic Business © UN/CEFACT Core Components Data Type Catalogue Version 3.0 Page 39 of 88 Use of Week and Ordinal date components in particular business contexts: business may need this representation (as for truncated dates), it is up to the business to decide on their use, considering systems’ interoperability.
Language:English
Score: 932966.2 - https://unece.org/fileadmin/DA...ade/CCTS-CatalogueVersion3.pdf
Data Source: un
For example, currently, the work of Core Component definition is under ATG. I think it is misplaced. The work of Core Component definition should be the work of ICG. In the division of work among the Groups, all the related people should be involved for correct placement of the various types of work. (...) The change I propose is as follows: Project Name Current Working Goup Proposed Group Accounting and Auditing Core Components EWG (P7) TBG Business Collaboration Patterns and Monitored Commitments Specification eBTWG TMG Business Collaboration Protocol Specification eBTWG TMG Business Neutral Core Component Library EWG (P1) ICG Business Entity Library eBTWG TBG and/or ICG Business Process Information Model Exchange Schema eBTWG ATG and/or TMG Business Process Specification Schema eBTWG TMG Common Business Process Catalogue Specification eBTWG TBG and/or ICG Common Business Process Catalogue Definitions EBTWG/BPAWG TBG and/or ICG TRADE/CEFACT/2002/34 page3 Core Component Realization Schema eBTWG TMG Core Component Specification eBTWG ICG and/or TMG Core Components Supplements eBTWG TBG and/or ICG e-Business Architecture Specification eBTWG TMG Finance Business Process Modelling EWG (P4) TBG Finance Core Components EWG (P3) TBG Harmonization Documentation EWG (P2) TBG Insurance Core Components EWG (P6) TBG Travel, Tourism and Leisure Core Components EWG (P5) TBG UML to XML Design Rules eBTWG ATG As I indicated, many projects cannot be clearly put into only one group because they need coordination and harmonization among multiple groups.
Language:English
Score: 931735.2 - https://unece.org/fileadmin/DA...nary/plenary02/docs/02cf34.pdf
Data Source: un
This was good news!!! Core Component Realization Specification Originally titled "XML Business Document Library" the project was renamed to "Core Component Realization (CCR)". (...) The synergy between the Business Process and Core Component members was more than one could have expected after some negative email exchanges before the meeting. (...) In turn, reusable blocks of core components/business information entities are harvested in creating the initial content of a CC library.
Language:English
Score: 925336.9 - https://unece.org/fileadmin/DA...nary/plenary02/docs/02cf16.pdf
Data Source: un
UN/CEFACT delivered a Core Component Technical Specification (CCTS), a Modelling Methodology, a basic set of Core Components and a number of Business Requirements Specifications. (...) The Forum is developing its methodology, its Core Component Technical Specifications, its Core Component Library, the Business Requirements Specifications and the Repository. (...) The eTendering harmonization of Core Components and Business Information Entities has been finalized.
Language:English
Score: 924126.2 - https://unece.org/fileadmin/DA...ry/plenary06/trd_cf_06_07e.pdf
Data Source: un