Functional Area Information Systems Definition

Functional Area Information Systems Definition

Draft Federal InformationProcessing Standards Publication 1831993 December 21Announcing the Standard forINTEGRATION DEFINITION FOR FUNCTIONMODELING (IDEF0)Federal Information Processing Standards Publications (FIPS PUBS) are issued by the NationalInstitute of Standards and Technology after approval by the Secretary of Commerce pursuant toSection 111(d) of the Federal Property and Administrative Services Act of 1949 as amended bythe Computer Security Act of 1987, Public Law 100-235.1.Name of Standard.Integration Definition for Function Modeling (IDEF0).2.Category of Standard.Software Standard, Modeling Techniques.3.Explanation.This publication announces the adoption of the Integration DefinitionFunction Modeling (IDEF0) as a Federal Information Processing Standard (FIPS).

This standardis based on the Air Force Wright Aeronautical Laboratories Integrated Computer- AidedManufacturing (ICAM) Architecture, Part II, Volume IV - Function Modeling Manual (IDEF0),June 1981.This standard describes the IDEF0 modeling language (semantics and syntax), andassociated rules and techniques, for developing structured graphical representations of a systemor enterprise.

Use of this standard permits the construction of models comprising systemfunctions (activities, actions, processes, operations), functional relationships, and data(information or objects) that support systems integration.This standard is the reference authority for use by system or enterprise modelers requiredto utilize the IDEF0 modeling technique, by implementors in developing tools for implementingthis technique, and by other computer professionals in understanding the precise syntactic andsemantic rules of the standard.4.Approving Authority.Secretary of Commerce.5.Maintenance Agency.Department of Commerce, National Institute of Standardsand Technology, Computer Systems Laboratory.6.Cross Index.a.ICAM Architecture Part II-Volume IV - Function Modeling Manual (IDEF0),AFWAL-TR-81-4023, Materials Laboratory, Air Force Wright Aeronautical Laboratories, AirForce Systems Command, Wright-Patterson Air Force Base, Ohio 45433, June 1981.7.Related Documents.a.Federal Information Resources Management Regulations Subpart 201.20.303,Standards, and Subpart 201.39.1002, Federal Standards.b.Integrated Information Support System (IISS), Volume V - Common Data ModelSubsystem, Part 4 - Information Modeling Manual - IDEF1 Extended, December 1985.c.ICAM Architecture Part II, Volume V - Information Modeling Manual (IDEF1),AFWAL-TR-81-4023, Materials Laboratory, Air Force Wright Aeronautical Laboratories, AirForce Systems Command, Wright-Patterson Air Force Base, Ohio 45433, June 1981.d.ICAM Configuration Management, Volume II - ICAM Documentation Standardsfor Systems Development Methodology (SDM), AFWAL-TR-82-4157, Air Force SystemsCommand, Wright-Patterson Air Force Base, Ohio 45433, October 1983.8.Objectives.The primary objectives of this standard are:a.To provide a means for completely and consistently modeling the functions (activities,actions, processes, operations) required by a system or enterprise, and the functionalrelationships and data (information or objects) that support the integration of thoseb.To provide a modeling technique which is independent of Computer-Aided SoftwareEngineering (CASE) methods or tools, but which can be used in conjunction with thosec.To provide a modeling technique that has the following characteristics:-Generic (for analysis of systems of varying purpose, scope and complexity);-Rigorous and precise (for production of correct, usable models);-Concise (to facilitate understanding, communication, consensus and validation);-Conceptual (for representation of functional requirements rather than physical ororganizational implementations);-Flexible (to support several phases of the lifecycle of a project).9.Applicability.The use of this standard is strongly recommended for projects that:a.Require a modeling technique for the analysis, development, re-engineering,integration, or acquisition of information systems;b.Incorporate a systems or enterprise modeling technique into a business process analysisor software engineering methodology.The specifications of this standard are applicable when system or enterprise modelingtechniques are applied to the following:a.Projects requiring IDEF0 as the modeling technique;b.Development of automated software tools implementing the IDEF0 modelingThe specifications of this standard are not applicable to those projects requiring afunction modeling technique other than IDEF0.Nonstandard features of the IDEF0 technique should be used only when the neededoperation or function cannot reasonably be implemented with the standard features alone.Although nonstandard features can be very useful, it should be recognized that the use of these orany other nonstandard elements may make the integration of models more difficult and costly.10.Specifications.This standard adopts the Integration Definition for FunctionModeling (IDEF0) as a Federal Information Processing Standard (FIPS).11.Implementation.The implementation of this standard involves two areas of implementations and interpretation of the standard.11.1 Acquisition of IDEF0 Implementations.This publication (FIPS 183) iseffective June 30, 1994.

For Federal acquisitions after this date, projects utilizing the IDEF0function modeling technique, or software implementing the IDEF0 modeling technique, shouldconform to FIPS 183.

Conformance to this standard should be considered whether the project orsoftware utilizing the IDEF0 modeling technique is acquired as part of an ADP systemprocurement, acquired by separate procurement, used under an ADP leasing arrangement, orspecified for use in contracts for programming services.A transition period provides time for industry to develop products conforming to thisstandard.

The transition period begins on the effective date and continues for one (1) yearthereafter
functional area information systems definition

The provis
02neal 2per
2What If ...We had a plan, put together by experts from multiplesectors that -Was built around manufacturing functionsDefined the critical elements of manufacturingtechnologyDefined a vision for each important categoryProvided a migration plan to get us from where we areto where we need to bePresented the information in various levels of detailCould be used as a guide for our specific technologyneeds3IMTI Deliverables Format What If .

.....The IMTR roadmaps were living documents thatallowed me to:Select the topic of interest to meGo directly to the information that I needFind who has solutions and who is working in anyarea that I chooseSee where my tax dollars are being spent andhow I could apply the resultsCompare my technology strategies against agroup consensusAND4What If .


.The documents were kept current and on-lineThe key topics were defined and prioritizedValidated, key issues were identified as rallyingpoints for focused activityMore detailed roadmaps were developed thataddressed the most important topicsThe detailed plans were adopted by companies,research organizations, and the governmentfunding agenciesVolunteer Armies and Focus Groups workedtogether to leverage investments and deliversolutions?????????Thats the Promise of5To The Issue At HandSome tidbits from the RoadmapsInformation SystemsModeling and SimulationTechnologies for EnterpriseIntegrationCurrent State - InformationSystems Are RevolutionizingManufacturing EnterprisesHigh-speed networks link the manufacturingenterpriseCustomer empowered by information technologythrough electronic commerceConcept design and optimization becomingsystematized and integrated by linking modelingand simulation systems through networksInformation systems are linking knowledgebases, on-line sensing systems, and on-linemodeling and processing to achieve 100%correct product - first time and every timeProduct definition - total computer-sensiblerepresentation of the product - is a realityERP and PDM - tremendous impact!6Information SystemsFunctional ModelSystems for Manufacturing7Product Design, Definition,& Data InterchangeFROMTOPeople-dependent designprocesses - widely variantLimited exchange ofnational standardssuch as PDES/STEPDesign as a stand-alonefunction with emergingcollaboration andlittle on-line analysisFunctional and performancemodels in limited use fordesignProduct (and process)design and analysis -totally automatedProduct data seamlesslyexchanged - globally andfor all product life-cyclestagesAll enterprise elementsparticipate in design,supported by a rich toolsetfor analysisFunctional andperformance modelsintegrated for control ofevery step of productcreation and lifecycleAccess to All of the NeededInformation - a Necessity forProduct/process Design8Manufacturing Planning &ExecutionFROMTOLargely manual processdesignIntegrated Product &Process Developmentlargely means functionalcollaborationShop floor control(transaction)

as a separatefunction - large systemsManufacturing informationgenerated by disparatesystems and manualoperationsKnowledge-based designadvisorsIPPD matured toIntegrated ProductRealization - from conceptthough the lifecycleIntegrated schedulers andshop floor controlsystems for reactive andadaptive controlGenerative planningsystems create allmanufacturing informationas part of an integratedERM environmentAn Integrated ManufacturingPlanning Framework9Enterprise ResourceManagementFROMTOQuality FunctionDeployment to establishcustomer requirements;requirements managementsystems emergingSome skills databases,computer-based trainingemerging; productivityenhancement throughteamingDisparate accountingmethods, long delaybetween data collection , direct ordering,and customer driventradeoff for optimizationClear visibility of skillneeds, trends, availability;knowledge supply chain inoperation; integrated toolsfor teamingContinuous, real-timevisibility of financialinformation; financialmanagement a standardparameter in designEnterprise ResourceManagement (cont.)FROMTOBarriers in supply chain -legal, disparate systems,specific supplierqualification systemsLarge ERP systems withmajor overhead;increasing awarenessof need for flexibility andbest-in-class tools; earlyintegration withoperations systemsExtended enterpriseinteroperability; seamlessparticipation in multiplesupply chains; validatedvendor and enterprisecore competenciesModular, plug-and-playERM systems with best-in-class tools integrated withoperations systemsacross the enterprise10A Vision of EnterpriseResource ManagementEnabling growth innetwork capability,reliability, and capacityLabor-intensive datacollection andmanagement; large,custominformation systems usedto integrate dataKnowledge managementbeing discovered as amajor need; conversion ofdata to knowledge isexternal to data structureReal-time access to all neededinformation; zero-loss trans-mission; only net changestransmittedModular, reconfigurable, self-organizing informationsystemsManufacturing knowledgeavailable on demand throughshared repositories;knowledge systems pervasivein design and manufacturing;self-learning and self-healingkeep systems current11Manufacturing EnterpriseKnowledge BaseManufacturingKnowledge Sharing12Gold Nuggets

-Information Systems forManufacturing EnterprisesInformation-Driven Seamless EnterprisesShared Knowledge ManufacturingMature Integrated Product/Process DesignTotally Connected Extended EnterprisePlug-&-Play, Interoperable System ComponentsDesign & Operation AdvisorsSelf-Correcting, Adaptive Operational SystemsSelf-Learning SystemsIntegration of Multiple Design DomainsIn SummaryBy implementing this migration strategy,manufacturing systems will:Have real-time access to all of the informationthey need - instantly useableExecute optimized processes with all importantfactors continuously balanced and tunedAnticipate and solve problems before theyimpact performanceExploit opportunities to their fullest potential13So What?This total connected
© 2012 labroda
- Contact · Privacy Policy
Recent Posts