1 / 15

Single Point of Entry (SPOE)

label. class. label. drawing_. product_data_type. document. document_with_. class. document_. type. id. revision_id. identifier. kind. description. text. document. label. name. label. file_name. source. relating_document. digital_file. subject_element_value. identifier.

stephanie
Download Presentation

Single Point of Entry (SPOE)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. label class label drawing_ product_data_type document document_with_ class document_ type id revision_id identifier kind description text document label name label file_name source relating_document digital_file subject_element_value identifier related_document document_usage_ text constraint name viewer size description subject_element document_ relationship description associated_ name program text label SPOE Smart Grid Smart Services Smart Data Single Point of Entry(SPOE) A Service-Oriented Strategy For Enterprise Integration Trading Partner Visibility

  2. Defense Supply Chain Visibility Gap

  3. label class label drawing_ product_data_type document document_with_ class document_ type id revision_id identifier kind description text document label name label file_name source relating_document digital_file subject_element_value identifier related_document document_usage_ text constraint name viewer size description subject_element document_ relationship description associated_ name program text label Solution & Capability Shared Global Network Smart Grid

  4. SPOE Visibility • Improve defense industrial visibility by providing industry with a common net-centric integration solution for connecting their information systems with the government enterprise • A web services framework of the standards, processes, business rules, and business integration language for business process flow through a shared network • Specify, develop, demonstrate, initiate SPOE operations

  5. SPOE Benefits Business Process TransformationDemands Integration Across Boundaries • Eliminate point-to-point connectivity between defense contractors and government sites • Automate system acquisition products delivery • Facilitate end-to-end supply chain and other processes • Enable new processes and alternative business models • Enable dynamic UID (asset accountability, configuration management)

  6. SPOE ELEMENTS • Published protocols for exchange of data and services • Trading partners implement protocols to connect with SPOE Grid • Based on commercial best practices • Compliant with net-centricity • Includes security, information assurance Web Services Grid Framework

  7. Operational site for management of data indexed with SPOE Provides services associated with data hub Supports additional business processes as required Multiple sites: government, industry, value-added Enforces the framework Supports error recovery, continuity of operations COTS based SPOE Elements SPOE Enterprise Server

  8. Current business information objects encoded as formal information models --Business Information Objects (BIOS) Based on internationally recognized standards, i.e., Product Life Cycle Support (PLCS ISO 10303) Based on advanced information web languages label class label drawing_ product_data_type document document_with_ class document_ type id revision_id identifier kind description text document label name label file_name source relating_document digital_file subject_element_value identifier related_document document_usage_ text constraint name viewer size description subject_element document_ relationship description associated_ name program text label SPOE Features Smart Information Standards Model-driven Exchange

  9. label class label drawing_ product_data_type document document_with_ class document_ type id revision_id identifier kind description text document label name label file_name source relating_document digital_file subject_element_value identifier related_document document_usage_ text constraint name viewer size description subject_element document_ relationship description associated_ name program text label Three-Tier Architecture 3. EnterpriseServices Tier 2. Information Integration Tier 1. Connectivity Tier

  10. SPOE Integrates industrial base Feeds are all industrial tiers May interact with industry information brokers Addresses commercial integration standards Addresses and complies with commercial security considerations in an open environment SPOE is not a single site; it is netcentric EIDE Integrates government enclave Feeds are Service/Agency Integrated Data Environments Interaction with outside information brokers unknown Integration procedures negotiated within DoD Addresses DoD security requirements in a closed environment Site specificity of EIDE unclear SPOE Versus EIDE

  11. FY-05 SPOE Requirements Definition Operational Description Document Operational architecture and SPOE Enterprise Server system architecture Use case collection based on JSF Business information object collection FY-06 Design & Prototype Framework creation, coordination, publication Prototype site selection Initial industry and government user base Initial use cases and business information objects Prototype server acquisition and installation Prototype operations, test, evaluation & validation SPOE Action Plan

  12. FY-07 Initial Operating Capability Refine formally publish framework Expand operations of prototype SPOE Enterprise Server and site Publish SPOE Enterprise Server Specification Extend use cases if required Convert additional business information objects Formalize business case/model FY-08 Full Operating Capability Convert additional business information objects Add additional SPOE services, if required Support SPOE Site developers/installers SPOE Action Plan

  13. Good News • Virtual exchange vice fixed integration point • Not platform dependent • Not site dependent • Can accommodate multiple coop/security strategies • Incremental integration vice big bang • New integrations do not disturb legacy integrations • Synchronization of budgets and schedules not required • Enterprise context versus stovepiping • Local information models are maintained as enterprise interoperability is achieved • Reduction of glue code over point to point integration • Mediation requires less custom code than point to point integration • SPOE eliminates Interface Adaptor requirements

  14. SPOE JSF Single Point of EntryWeb-Services Protocols & Business Information ObjectsEnabling Information Interoperability Among Qualified Trading Partners

  15. SPOE Sikorsky Single Point of EntryWeb-Services Protocols & Business Information ObjectsEnabling Information Interoperability Among Qualified Trading Partners

More Related