48 CFR 311.7000 - Defining electronic information technology requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 48 Federal Acquisition Regulations System 4 2011-10-01 2011-10-01 false Defining electronic information technology requirements. 311.7000 Section 311.7000 Federal Acquisition Regulations System HEALTH... Accessibility Standards 311.7000 Defining electronic information technology requirements. HHS staff that define...

48 CFR 311.7000 - Defining electronic information technology requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 48 Federal Acquisition Regulations System 4 2014-10-01 2014-10-01 false Defining electronic information technology requirements. 311.7000 Section 311.7000 Federal Acquisition Regulations System HEALTH... Accessibility Standards 311.7000 Defining electronic information technology requirements. HHS staff that define...

48 CFR 311.7000 - Defining electronic information technology requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 48 Federal Acquisition Regulations System 4 2013-10-01 2013-10-01 false Defining electronic information technology requirements. 311.7000 Section 311.7000 Federal Acquisition Regulations System HEALTH... Accessibility Standards 311.7000 Defining electronic information technology requirements. HHS staff that define...

48 CFR 311.7000 - Defining electronic information technology requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 48 Federal Acquisition Regulations System 4 2012-10-01 2012-10-01 false Defining electronic information technology requirements. 311.7000 Section 311.7000 Federal Acquisition Regulations System HEALTH... Accessibility Standards 311.7000 Defining electronic information technology requirements. HHS staff that define...

48 CFR 311.7000 - Defining electronic information technology requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 48 Federal Acquisition Regulations System 4 2010-10-01 2010-10-01 false Defining electronic information technology requirements. 311.7000 Section 311.7000 Federal Acquisition Regulations System HEALTH... Accessibility Standards 311.7000 Defining electronic information technology requirements. HHS staff that define...

Development of vendor evaluation criteria and post-implementation considerations for MSFC center-wide executive information system

NASA Technical Reports Server (NTRS)

Moynihan, Gary P.

1992-01-01

In June 1991, the MITRE Corporation submitted a series of recommendations as part of a Marshall Space Flight Center (MSFC) Management Information System Requirements Study, initiated by the Information Systems Office (ISO). A major recommendation of the study was to develop an Executive Information System (EIS) for MSFC executives. ISO was directed, by center management, to proceed with the development of a Center-Wide Executive Information System. Existing EIS prototypes, developed by the Space Shuttle Projects Office and the Payload Projects Office, were reviewed. These existing MSFC prototypes were considered not to encompass the required functionality needed on a center-wide basis. A follow-up study by MITRE provided top-level system requirements. These were later incorporated into a final requirements specification document by Boeing Computer Support Services.

Information security requirements in patient-centred healthcare support systems.

PubMed

Alsalamah, Shada; Gray, W Alex; Hilton, Jeremy; Alsalamah, Hessah

2013-01-01

Enabling Patient-Centred (PC) care in modern healthcare requires the flow of medical information with the patient between different healthcare providers as they follow the patient's treatment plan. However, PC care threatens the stability of the balance of information security in the support systems since legacy systems fall short of attaining a security balance when sharing their information due to compromises made between its availability, integrity, and confidentiality. Results show that the main reason for this is that information security implementation in discrete legacy systems focused mainly on information confidentiality and integrity leaving availability a challenge in collaboration. Through an empirical study using domain analysis, observations, and interviews, this paper identifies a need for six information security requirements in legacy systems to cope with this situation in order to attain the security balance in systems supporting PC care implementation in modern healthcare.

Pilot's Automated Weather Support System (PAWSS) concepts demonstration project. Phase 1: Pilot's weather information requirements and implications for weather data systems design

NASA Technical Reports Server (NTRS)

Crabill, Norman L.; Dash, Ernie R.

1991-01-01

The weather information requirements for pilots and the deficiencies of the current aviation weather support system in meeting these requirements are defined. As the amount of data available to pilots increases significantly in the near future, expert system technology will be needed to assist pilots in assimilating that information. Some other desirable characteristics of an automation-assisted system for weather data acquisition, dissemination, and assimilation are also described.

Understanding requirements of novel healthcare information systems for management of advanced prostate cancer.

PubMed

Wagholikar, Amol S; Fung, Maggie; Nelson, Colleen C

2012-01-01

Effective management of chronic diseases is a global health priority. A healthcare information system offers opportunities to address challenges of chronic disease management. However, the requirements of health information systems are often not well understood. The accuracy of requirements has a direct impact on the successful design and implementation of a health information system. Our research describes methods used to understand the requirements of health information systems for advanced prostate cancer management. The research conducted a survey to identify heterogeneous sources of clinical records. Our research showed that the General Practitioner was the common source of patient's clinical records (41%) followed by the Urologist (14%) and other clinicians (14%). Our research describes a method to identify diverse data sources and proposes a novel patient journey browser prototype that integrates disparate data sources.

Formalization of software requirements for information systems using fuzzy logic

NASA Astrophysics Data System (ADS)

Yegorov, Y. S.; Milov, V. R.; Kvasov, A. S.; Sorokoumova, S. N.; Suvorova, O. V.

2018-05-01

The paper considers an approach to the design of information systems based on flexible software development methodologies. The possibility of improving the management of the life cycle of information systems by assessing the functional relationship between requirements and business objectives is described. An approach is proposed to establish the relationship between the degree of achievement of business objectives and the fulfillment of requirements for the projected information system. It describes solutions that allow one to formalize the process of formation of functional and non-functional requirements with the help of fuzzy logic apparatus. The form of the objective function is formed on the basis of expert knowledge and is specified via learning from very small data set.

Recognition and categorization considerations for information assurance requirements development and speficication

NASA Astrophysics Data System (ADS)

Stytz, Martin R.; May, Michael; Banks, Sheila B.

2009-04-01

Department of Defense (DoD) Information Technology (IT) systems operate in an environment different from the commercial world, the differences arise from the differences in the types of attacks, the interdependencies between DoD software systems, and the reliance upon commercial software to provide basic capabilities. The challenge that we face is determining how to specify the information assurance requirements for a system without requiring changes to the commercial software and in light of the interdependencies between systems. As a result of the interdependencies and interconnections between systems introduced by the global information grid (GIG), an assessment of the IA requirements for a system must consider three facets of a system's IA capabilities: 1) the IA vulnerabilities of the system, 2) the ability of a system to repel IA attacks, and 3) the ability of a system to insure that any IA attack that penetrates the system is contained within the system and does not spread. Each facet should be assessed independently and the requirements should be derived independently from the assessments. In addition to the desired IA technology capabilities of the system, a complete assessment of the system's overall IA security technology readiness level cannot be accomplished without an assessment of the capabilities required of the system for its capability to recover from and remediate IA vulnerabilities and compromises. To allow us to accomplish these three formidable tasks, we propose a general system architecture designed to separate the system's IA capabilities from its other capability requirements; thereby allowing the IA capabilities to be developed and assessed separately from the other system capabilities. The architecture also enables independent requirements specification, implementation, assessment, measurement, and improvement of a system's IA capabilities without requiring modification of the underlying application software.

Modeling traceability information and functionality requirement in export-oriented tilapia chain.

PubMed

Zhang, Xiaoshuan; Feng, Jianying; Xu, Mark; Hu, Jinyou

2011-05-01

Tilapia has been named as the 'food fish of the 21st century' and has become the most important farmed fish. China is the world leader in tilapia production and export. Identifying information and functional requirements is critical in developing an efficient traceability system because traceability has become a fundamental prerequisite for exporting aquaculture products. This paper examines the export-oriented tilapia chains and information flow in the chains, and identifies the key actors, information requirements and information-capturing points. Unified Modeling Language (UML) technology is adopted to describe the information and functionality requirement for chain traceability. The barriers of traceability system adoption are also identified. The results show that the traceability data consist of four categories that must be recorded by each link in the chain. The functionality requirement is classified into four categories from the fundamental information record to decisive quality control; the top three barriers to the traceability system adoption are: high costs of implementing the system, lack of experienced and professional staff; and low level of government involvement and support. Copyright © 2011 Society of Chemical Industry.

A Methodological Framework for Enterprise Information System Requirements Derivation

NASA Astrophysics Data System (ADS)

Caplinskas, Albertas; Paškevičiūtė, Lina

Current information systems (IS) are enterprise-wide systems supporting strategic goals of the enterprise and meeting its operational business needs. They are supported by information and communication technologies (ICT) and other software that should be fully integrated. To develop software responding to real business needs, we need requirements engineering (RE) methodology that ensures the alignment of requirements for all levels of enterprise system. The main contribution of this chapter is a requirement-oriented methodological framework allowing to transform business requirements level by level into software ones. The structure of the proposed framework reflects the structure of Zachman's framework. However, it has other intentions and is purposed to support not the design but the RE issues.

Work Smarter Not Harder: Utilizing an Environmental Management Information System to Meet Regulatory Compliance and Reporting Requirements for a Major Source Title V Facility

DTIC Science & Technology

2011-05-10

Environmental Management Information System to Meet Regulatory Compliance and Reporting Requirements for a Major Source Title V Facility. Tannis Danley...AND SUBTITLE Work Smarter Not Harder: Utilizing an Environmental Management Information System to Meet Regulatory Compliance and Reporting...Carson) – EMS (Hawaii Garrison, West Virginia National Guard) Environmental Management Information System (EMIS) National Defense Center for Energy and

Requirements, Verification, and Compliance (RVC) Database Tool

NASA Technical Reports Server (NTRS)

Rainwater, Neil E., II; McDuffee, Patrick B.; Thomas, L. Dale

2001-01-01

This paper describes the development, design, and implementation of the Requirements, Verification, and Compliance (RVC) database used on the International Space Welding Experiment (ISWE) project managed at Marshall Space Flight Center. The RVC is a systems engineer's tool for automating and managing the following information: requirements; requirements traceability; verification requirements; verification planning; verification success criteria; and compliance status. This information normally contained within documents (e.g. specifications, plans) is contained in an electronic database that allows the project team members to access, query, and status the requirements, verification, and compliance information from their individual desktop computers. Using commercial-off-the-shelf (COTS) database software that contains networking capabilities, the RVC was developed not only with cost savings in mind but primarily for the purpose of providing a more efficient and effective automated method of maintaining and distributing the systems engineering information. In addition, the RVC approach provides the systems engineer the capability to develop and tailor various reports containing the requirements, verification, and compliance information that meets the needs of the project team members. The automated approach of the RVC for capturing and distributing the information improves the productivity of the systems engineer by allowing that person to concentrate more on the job of developing good requirements and verification programs and not on the effort of being a "document developer".

45 CFR 205.35 - Mechanized claims processing and information retrieval systems; definitions.

Code of Federal Regulations, 2010 CFR

2010-10-01

... State plan requirements for an automated statewide management information system, conditions for FFP and... produce utilization and management information about such aid and services as required by the single State... 45 Public Welfare 2 2010-10-01 2010-10-01 false Mechanized claims processing and information...

77 FR 7 - Revisions to Labeling Requirements for Blood and Blood Components, Including Source Plasma

Federal Register 2010, 2011, 2012, 2013, 2014

2012-01-03

... requirements will facilitate the use of a labeling system using machine-readable information that would be... components. Furthermore, we proposed the use of a labeling system using machine-readable information that...; Facilitates the use of a labeling system using machine- readable information that would be acceptable as a...

Patient Accounting Systems: Are They Fit with the Users' Requirements?

PubMed

Ayatollahi, Haleh; Nazemi, Zahra; Haghani, Hamid

2016-01-01

A patient accounting system is a subsystem of a hospital information system. This system like other information systems should be carefully designed to be able to meet users' requirements. The main aim of this research was to investigate users' requirements and to determine whether current patient accounting systems meet users' needs or not. This was a survey study, and the participants were the users of six patient accounting systems used in 24 teaching hospitals. A stratified sampling method was used to select the participants (n = 216). The research instruments were a questionnaire and a checklist. The mean value of ≥3 showed the importance of each data element and the capability of the system. Generally, the findings showed that the current patient accounting systems had some weaknesses and were able to meet between 70% and 80% of users' requirements. The current patient accounting systems need to be improved to be able to meet users' requirements. This approach can also help to provide hospitals with more usable and reliable financial information.

36 CFR 1192.61 - Public information system.

Code of Federal Regulations, 2010 CFR

2010-07-01

... 36 Parks, Forests, and Public Property 3 2010-07-01 2010-07-01 false Public information system... Rapid Rail Vehicles and Systems § 1192.61 Public information system. (a)(1) Requirements. Each vehicle... line identification information. (2) Exception. Where station announcement systems provide information...

Freight advanced traveler information system : functional requirements.

DOT National Transportation Integrated Search

2012-08-01

This report describes the System Requirement Specifications (SyRS) for a Freight Advanced Traveler Information System (FRATIS). The SyRS is based on user needs described in the FRATIS Concept of Operations (ConOps), which cover the essential function...

[Information technology use in preventing infection].

PubMed

Ohmagari, Norio

2011-11-01

Infection prevention requires handling enormous amounts of medical information collection, analysis, and delivery--a cumbersome, inefficient process. Hospital information system (HIS) data not intended for preventing infection cannot be used directly for such prevention. The rapid introduction of information technology in infection prevention can potentially solve these problems. The IT-based infection prevention system (ITIPS) structure depends on the purpose specified, however, and using this information in hospitals requires that the detailed HIS structure be clarified, especially the connection between HIS and ITIPS. The future ITIPS role is envisioned in early infection detection and warning. This, in turn, requires that ITIPS field operational support systems for medical staff mature further.

Information systems - Issues in global habitability

NASA Technical Reports Server (NTRS)

Norman, S. D.; Brass, J. A.; Jones, H.; Morse, D. R.

1984-01-01

The present investigation is concerned with fundamental issues, related to information considerations, which arise in an interdisciplinary approach to questions of global habitability. Information system problems and issues are illustrated with the aid of an example involving biochemical cycling and biochemical productivity. The estimation of net primary production (NPP) as an important consideration in the overall global habitability issue is discussed. The NPP model requires three types of data, related to meteorological information, a land surface inventory, and the vegetation structure. Approaches for obtaining and processing these data are discussed. Attention is given to user requirements, information system requirements, workstations, network communications, hardware/software access, and data management.

The Design and Implement of Tourism Information System Based on GIS

NASA Astrophysics Data System (ADS)

Chunchang, Fu; Nan, Zhang

From the geographical information system concept, discusses the main contents of the geographic information system, and the current of the geographic information system key technological measures of tourism information system, the application of tourism information system for specific requirements and goals, and analyzes a relational database model based on the tourist information system in GIS application methods of realization.

Using task analysis to improve the requirements elicitation in health information system.

PubMed

Teixeira, Leonor; Ferreira, Carlos; Santos, Beatriz Sousa

2007-01-01

This paper describes the application of task analysis within the design process of a Web-based information system for managing clinical information in hemophilia care, in order to improve the requirements elicitation and, consequently, to validate the domain model obtained in a previous phase of the design process (system analysis). The use of task analysis in this case proved to be a practical and efficient way to improve the requirements engineering process by involving users in the design process.

Exploration Planetary Surface Structural Systems: Design Requirements and Compliance

NASA Technical Reports Server (NTRS)

Dorsey, John T.

2011-01-01

The Lunar Surface Systems Project developed system concepts that would be necessary to establish and maintain a permanent human presence on the Lunar surface. A variety of specific system implementations were generated as a part of the scenarios, some level of system definition was completed, and masses estimated for each system. Because the architecture studies generally spawned a large number of system concepts and the studies were executed in a short amount of time, the resulting system definitions had very low design fidelity. This paper describes the development sequence required to field a particular structural system: 1) Define Requirements, 2) Develop the Design and 3) Demonstrate Compliance of the Design to all Requirements. This paper also outlines and describes in detail the information and data that are required to establish structural design requirements and outlines the information that would comprise a planetary surface system Structures Requirements document.

Communication Challenges in Requirements Definition: A Classroom Simulation

ERIC Educational Resources Information Center

Ramiller, Neil C.; Wagner, Erica L.

2011-01-01

Systems analysis and design is a standard course offering within information systems programs and often an important lecture topic in Information Systems core courses. Given the persistent difficulty that organizations experience in implementing systems that meet their requirements, it is important to help students in these courses get a tangible…

Information systems requirements for the Microgravity Science and Applications Program

NASA Technical Reports Server (NTRS)

Kicza, M. E.; Kreer, J. R.

1991-01-01

NASA's Microgravity Science and Applications (MSAD) Program is presented. Additionally, the types of information produced wiithin the program and the anticipated growth in information system requirements as the program transitions to Space Station Freedom utilization are discussed. Plans for payload operations support in the Freedom era are addressed, as well as current activities to define research community requirements for data and sample archives.

Information systems requirements for the microgravity science and applications program

NASA Technical Reports Server (NTRS)

Kicza, M. E.; Kreer, J. R.

1990-01-01

NASA's Microgravity Science and Applications (MSAD) Program is presented. Additionally, the types of information produced within the program and the anticipated growth in information system requirements as the program transitions to Space Station Freedom utilization are discussed. Plans for payload operations support in the Freedom era are addressed, as well as current activities to define research community requirements for data and sample archives.

76 FR 42536 - Real-Time System Management Information Program

Federal Register 2010, 2011, 2012, 2013, 2014

2011-07-19

...-Time System Management Information Program AGENCY: Federal Highway Administration (FHWA), DOT. ACTION... Real-Time System Management Information Program and general information about current and planned... establishing requirements for the Real-Time System Management Information Program on November 8, 2010, at 75 FR...

78 FR 55060 - Proposed Information Collection; Comment Request; Expanded Vessel Monitoring System Requirement...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-09-09

... DEPARTMENT OF COMMERCE National Oceanic and Atmospheric Administration Proposed Information Collection; Comment Request; Expanded Vessel Monitoring System Requirement in the Pacific Coast Groundfish... and use a vessel monitoring system (VMS) that automatically sends hourly position reports. Exemptions...

CMMI(Registered) for Services, Version 1.3

DTIC Science & Technology

2010-11-01

ISO 2008b] ISO /IEC 27001 :2005 Information technology – Security techniques – Information Security Management Systems – Requirements [ ISO /IEC 2005...Commission. ISO /IEC 27001 Information Technology – Security Techniques – Information Security Management Systems – Requirements, 2005. http...CMM or International Organization for Standardization ( ISO ) 9001, you will immediately recognize many similarities in their structure and content

The Core Curricula of Information Systems Undergraduate Programs: A Survey of AACSB-Accredited Colleges in the United States

ERIC Educational Resources Information Center

Yang, Samuel C.

2016-01-01

The author examines the present state of information systems undergraduate programs in the United States. He reviewed 516 institutions and collected data on 234 institutions offering information systems (IS) undergraduate programs. Of seven core courses required by the IS 2010 curriculum model, four are required by more than 50% of the programs,…

The Co-Creation of Information Systems

ERIC Educational Resources Information Center

Gomillion, David

2013-01-01

In information systems development, end-users have shifted in their role: from consumers of information to informants for requirements to developers of systems. This shift in the role of users has also changed how information systems are developed. Instead of systems developers creating specifications for software or end-users creating small…

Computer-assisted engineering data base

NASA Technical Reports Server (NTRS)

Dube, R. P.; Johnson, H. R.

1983-01-01

General capabilities of data base management technology are described. Information requirements posed by the space station life cycle are discussed, and it is asserted that data base management technology supporting engineering/manufacturing in a heterogeneous hardware/data base management system environment should be applied to meeting these requirements. Today's commercial systems do not satisfy all of these requirements. The features of an R&D data base management system being developed to investigate data base management in the engineering/manufacturing environment are discussed. Features of this system represent only a partial solution to space station requirements. Areas where this system should be extended to meet full space station information management requirements are discussed.

48 CFR 1352.239-72 - Security requirements for information technology resources.

Code of Federal Regulations, 2011 CFR

2011-10-01

... information technology resources. 1352.239-72 Section 1352.239-72 Federal Acquisition Regulations System... Clauses 1352.239-72 Security requirements for information technology resources. As prescribed in 48 CFR 1339.270(b), insert the following clause: Security Requirements for Information Technology Resources...

48 CFR 1804.470 - Security requirements for unclassified information technology (IT) resources.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 48 Federal Acquisition Regulations System 6 2013-10-01 2013-10-01 false Security requirements for unclassified information technology (IT) resources. 1804.470 Section 1804.470 Federal Acquisition Regulations... Classified Information Within Industry 1804.470 Security requirements for unclassified information technology...

48 CFR 1804.470 - Security requirements for unclassified information technology (IT) resources.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 48 Federal Acquisition Regulations System 6 2011-10-01 2011-10-01 false Security requirements for unclassified information technology (IT) resources. 1804.470 Section 1804.470 Federal Acquisition Regulations... Classified Information Within Industry 1804.470 Security requirements for unclassified information technology...

48 CFR 1804.470 - Security requirements for unclassified information technology (IT) resources.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 48 Federal Acquisition Regulations System 6 2014-10-01 2014-10-01 false Security requirements for unclassified information technology (IT) resources. 1804.470 Section 1804.470 Federal Acquisition Regulations... Classified Information Within Industry 1804.470 Security requirements for unclassified information technology...

48 CFR 1804.470 - Security requirements for unclassified information technology (IT) resources.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 48 Federal Acquisition Regulations System 6 2012-10-01 2012-10-01 false Security requirements for unclassified information technology (IT) resources. 1804.470 Section 1804.470 Federal Acquisition Regulations... Classified Information Within Industry 1804.470 Security requirements for unclassified information technology...

48 CFR 1804.470 - Security requirements for unclassified information technology (IT) resources.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 48 Federal Acquisition Regulations System 6 2010-10-01 2010-10-01 true Security requirements for unclassified information technology (IT) resources. 1804.470 Section 1804.470 Federal Acquisition Regulations... Classified Information Within Industry 1804.470 Security requirements for unclassified information technology...

48 CFR 1352.239-72 - Security requirements for information technology resources.

Code of Federal Regulations, 2013 CFR

2013-10-01

... information technology resources. 1352.239-72 Section 1352.239-72 Federal Acquisition Regulations System... Clauses 1352.239-72 Security requirements for information technology resources. As prescribed in 48 CFR 1339.270(b), insert the following clause: Security Requirements for Information Technology Resources...

48 CFR 1352.239-72 - Security requirements for information technology resources.

Code of Federal Regulations, 2012 CFR

2012-10-01

... information technology resources. 1352.239-72 Section 1352.239-72 Federal Acquisition Regulations System... Clauses 1352.239-72 Security requirements for information technology resources. As prescribed in 48 CFR 1339.270(b), insert the following clause: Security Requirements for Information Technology Resources...

48 CFR 1352.239-72 - Security requirements for information technology resources.

Code of Federal Regulations, 2014 CFR

2014-10-01

... information technology resources. 1352.239-72 Section 1352.239-72 Federal Acquisition Regulations System... Clauses 1352.239-72 Security requirements for information technology resources. As prescribed in 48 CFR 1339.270(b), insert the following clause: Security Requirements for Information Technology Resources...

48 CFR 1352.239-72 - Security requirements for information technology resources.

Code of Federal Regulations, 2010 CFR

2010-10-01

... information technology resources. 1352.239-72 Section 1352.239-72 Federal Acquisition Regulations System... Clauses 1352.239-72 Security requirements for information technology resources. As prescribed in 48 CFR 1339.270(b), insert the following clause: Security Requirements for Information Technology Resources...

76 FR 36905 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Taxes

Federal Register 2010, 2011, 2012, 2013, 2014

2011-06-23

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Taxes AGENCY: Defense Acquisition Regulations System, Department of Defense (DoD). [[Page 36906

Medicaid management information systems performance standards: Health Care Financing Administration. Notice with comment period.

PubMed

1981-06-30

This notice contains performance standards (review elements and factors). We are required by section 1903(r)(6)(E) of the Social Security Act to notify all States of proposed procedures, standards, and other requirements at least one quarter prior to the fiscal year in which the procedures, standards, and other requirements will be used for Medicaid Management Information Systems reapproval reviews. This Notice meets that statutory requirements. By October 1, 1981, we will use the performance standards and existing systems requirements when conducting the annual review of State system performance.

48 CFR 3439.702 - Department security requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... ACQUISITION REGULATION SPECIAL CATEGORIES OF CONTRACTING ACQUISITION OF INFORMATION TECHNOLOGY Department Requirements for Acquisition of Information Technology 3439.702 Department security requirements. The...) involves the design, operation, repair, or maintenance of information systems and access to sensitive but...

48 CFR 3439.702 - Department security requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... ACQUISITION REGULATION SPECIAL CATEGORIES OF CONTRACTING ACQUISITION OF INFORMATION TECHNOLOGY Department Requirements for Acquisition of Information Technology 3439.702 Department security requirements. The...) involves the design, operation, repair, or maintenance of information systems and access to sensitive but...

48 CFR 3439.702 - Department security requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... ACQUISITION REGULATION SPECIAL CATEGORIES OF CONTRACTING ACQUISITION OF INFORMATION TECHNOLOGY Department Requirements for Acquisition of Information Technology 3439.702 Department security requirements. The...) involves the design, operation, repair, or maintenance of information systems and access to sensitive but...

40 CFR 264.1064 - Recordkeeping requirements.

Code of Federal Regulations, 2010 CFR

2010-07-01

... management units in one recordkeeping system if the system identifies each record by each hazardous waste management unit. (b) Owners and operators must record the following information in the facility operating... monitoring, operating, and inspection information for each closed-vent system and control device required to...

77 FR 36488 - Proposed Information Collection; Comment Request; Vessel Monitoring System Requirements Under the...

Federal Register 2010, 2011, 2012, 2013, 2014

2012-06-19

... DEPARTMENT OF COMMERCE National Oceanic and Atmospheric Administration Proposed Information Collection; Comment Request; Vessel Monitoring System Requirements Under the Western and Central Pacific...-fixing transmitters (``Vessel Monitoring System-VMS-units'') at all times except when the vessel is in...

Information Requirements Specification II: Brainstorming Collective Decision-Making Technique.

ERIC Educational Resources Information Center

Telem, Moshe

1988-01-01

Information requirements specification (IRS) constitutes an Achilles heel in the system life cycle of management information systems. This article establishes a systematic overall IRS technique applicable to organizations of all types and sizes. The technique's integration of brainstorming and theory Z principles creates an effective, stimulating,…

Information requirements of the National Aeronautics and Space Administration's safety, environmental health, and occupational medicine programs

NASA Technical Reports Server (NTRS)

Whyte, A. A.

1978-01-01

A survey of the internal and external reporting and recordkeeping procedures of these programs was conducted and the major problems associated with them are outlined. The impact of probable future requirements on existing information systems is evaluated. This report also presents the benefits of combining the safety and health information systems into one computerized system and recommendations for the development and scope of that system.

Patient Accounting Systems: Are They Fit with the Users' Requirements?

PubMed Central

Ayatollahi, Haleh; Nazemi, Zahra

2016-01-01

Objectives A patient accounting system is a subsystem of a hospital information system. This system like other information systems should be carefully designed to be able to meet users' requirements. The main aim of this research was to investigate users' requirements and to determine whether current patient accounting systems meet users' needs or not. Methods This was a survey study, and the participants were the users of six patient accounting systems used in 24 teaching hospitals. A stratified sampling method was used to select the participants (n = 216). The research instruments were a questionnaire and a checklist. The mean value of ≥3 showed the importance of each data element and the capability of the system. Results Generally, the findings showed that the current patient accounting systems had some weaknesses and were able to meet between 70% and 80% of users' requirements. Conclusions The current patient accounting systems need to be improved to be able to meet users' requirements. This approach can also help to provide hospitals with more usable and reliable financial information. PMID:26893945

Functional Requirements Study

DTIC Science & Technology

2008-07-01

Identification System, AIS, Vessel Traffic Services, VTS, Transmit, Broadcast, Functional Requirements, United States Coast Guard, USCG, Mariner, Electronic ...Chart Systems, ECS, Vessel Operators, National Oceanic Atmospheric Administration, NOAA, US Army Corp of Engineers , USACE, ECDIS 18. Distribution...and River Information Service COPT Captain of the Port DGPS Differential Global Positioning System ECDIS Electronic Chart Display Information System

Transforming user needs into functional requirements for an antibiotic clinical decision support system: explicating content analysis for system design.

PubMed

Bright, T J

2013-01-01

Many informatics studies use content analysis to generate functional requirements for system development. Explication of this translational process from qualitative data to functional requirements can strengthen the understanding and scientific rigor when applying content analysis in informatics studies. To describe a user-centered approach transforming emergent themes derived from focus group data into functional requirements for informatics solutions and to illustrate these methods to the development of an antibiotic clinical decision support system (CDS). THE APPROACH CONSISTED OF FIVE STEPS: 1) identify unmet therapeutic planning information needs via Focus Group Study-I, 2) develop a coding framework of therapeutic planning themes to refine the domain scope to antibiotic therapeutic planning, 3) identify functional requirements of an antibiotic CDS system via Focus Group Study-II, 4) discover informatics solutions and functional requirements from coded data, and 5) determine the types of information needed to support the antibiotic CDS system and link with the identified informatics solutions and functional requirements. The coding framework for Focus Group Study-I revealed unmet therapeutic planning needs. Twelve subthemes emerged and were clustered into four themes; analysis indicated a need for an antibiotic CDS intervention. Focus Group Study-II included five types of information needs. Comments from the Barrier/Challenge to information access and Function/Feature themes produced three informatics solutions and 13 functional requirements of an antibiotic CDS system. Comments from the Patient, Institution, and Domain themes generated required data elements for each informatics solution. This study presents one example explicating content analysis of focus group data and the analysis process to functional requirements from narrative data. Illustration of this 5-step method was used to develop an antibiotic CDS system, resolving unmet antibiotic prescribing needs. As a reusable approach, these techniques can be refined and applied to resolve unmet information needs with informatics interventions in additional domains.

49 CFR 37.213 - Information collection requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... Analysis & Information System 1200 New Jersey Avenue, SE., Washington, D.C. 20590. [66 FR 9053, Feb. 6... 49 Transportation 1 2011-10-01 2011-10-01 false Information collection requirements. 37.213... INDIVIDUALS WITH DISABILITIES (ADA) Over-the-Road Buses (OTRBs) § 37.213 Information collection requirements...

Report: Improvements Needed in Key EPA Information System Security Practices

EPA Pesticide Factsheets

Report #10-P-0146, June 15, 2010. Williams Adley found that EPA program offices lacked evidence that they planned and executed tests of information system security controls as required by federal requirements.

32 CFR 505.14 - Recordkeeping requirements under the Privacy Act.

Code of Federal Regulations, 2011 CFR

2011-07-01

... under the Privacy Act. (a) AR 25-400-2, The Army Records Information Management System (ARIMS). To maintain privacy records are required by the Army Records Information Management System (ARIMS) to provide...

32 CFR 505.14 - Recordkeeping requirements under the Privacy Act.

Code of Federal Regulations, 2013 CFR

2013-07-01

... under the Privacy Act. (a) AR 25-400-2, The Army Records Information Management System (ARIMS). To maintain privacy records are required by the Army Records Information Management System (ARIMS) to provide...

32 CFR 505.14 - Recordkeeping requirements under the Privacy Act.

Code of Federal Regulations, 2012 CFR

2012-07-01

... under the Privacy Act. (a) AR 25-400-2, The Army Records Information Management System (ARIMS). To maintain privacy records are required by the Army Records Information Management System (ARIMS) to provide...

32 CFR 505.14 - Recordkeeping requirements under the Privacy Act.

Code of Federal Regulations, 2014 CFR

2014-07-01

... under the Privacy Act. (a) AR 25-400-2, The Army Records Information Management System (ARIMS). To maintain privacy records are required by the Army Records Information Management System (ARIMS) to provide...

Majoring in Information Systems: Reasons Why Students Select (or Not) Information Systems as a Major

ERIC Educational Resources Information Center

Snyder, Johnny; Slauson, Gayla Jo

2014-01-01

Filling the pipeline for information systems workers is critical in the information era. Projected growth rates for jobs requiring information systems expertise are significantly higher than the projected growth rates for other jobs. Why then do relatively few students choose to major in information systems? This paper reviews survey results from…

Information Models, Data Requirements, and Agile Data Curation

NASA Astrophysics Data System (ADS)

Hughes, John S.; Crichton, Dan; Ritschel, Bernd; Hardman, Sean; Joyner, Ron

2015-04-01

The Planetary Data System's next generation system, PDS4, is an example of the successful use of an ontology-based Information Model (IM) to drive the development and operations of a data system. In traditional systems engineering, requirements or statements about what is necessary for the system are collected and analyzed for input into the design stage of systems development. With the advent of big data the requirements associated with data have begun to dominate and an ontology-based information model can be used to provide a formalized and rigorous set of data requirements. These requirements address not only the usual issues of data quantity, quality, and disposition but also data representation, integrity, provenance, context, and semantics. In addition the use of these data requirements during system's development has many characteristics of Agile Curation as proposed by Young et al. [Taking Another Look at the Data Management Life Cycle: Deconstruction, Agile, and Community, AGU 2014], namely adaptive planning, evolutionary development, early delivery, continuous improvement, and rapid and flexible response to change. For example customers can be satisfied through early and continuous delivery of system software and services that are configured directly from the information model. This presentation will describe the PDS4 architecture and its three principle parts: the ontology-based Information Model (IM), the federated registries and repositories, and the REST-based service layer for search, retrieval, and distribution. The development of the IM will be highlighted with special emphasis on knowledge acquisition, the impact of the IM on development and operations, and the use of shared ontologies at multiple governance levels to promote system interoperability and data correlation.

2 CFR 200.58 - Information technology systems.

Code of Federal Regulations, 2014 CFR

2014-01-01

... 2 Grants and Agreements 1 2014-01-01 2014-01-01 false Information technology systems. 200.58..., AND AUDIT REQUIREMENTS FOR FEDERAL AWARDS Acronyms and Definitions Acronyms § 200.58 Information technology systems. Information technology systems means computing devices, ancillary equipment, software...

Delivering Training for Highly Demanding Information Systems

ERIC Educational Resources Information Center

Norton, Andrew Lawrence; Coulson-Thomas, Yvette May; Coulson-Thomas, Colin Joseph; Ashurst, Colin

2012-01-01

Purpose: There is a lack of research covering the training requirements of organisations implementing highly demanding information systems (HDISs). The aim of this paper is to help in the understanding of appropriate training requirements for such systems. Design/methodology/approach: This research investigates the training delivery within a…

48 CFR 252.203-7002 - Requirement to Inform Employees of Whistleblower Rights.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 48 Federal Acquisition Regulations System 3 2014-10-01 2014-10-01 false Requirement to Inform Employees of Whistleblower Rights. 252.203-7002 Section 252.203-7002 Federal Acquisition Regulations System DEFENSE ACQUISITION REGULATIONS SYSTEM, DEPARTMENT OF DEFENSE CLAUSES AND FORMS SOLICITATION PROVISIONS...

48 CFR 252.203-7002 - Requirement to Inform Employees of Whistleblower Rights.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 48 Federal Acquisition Regulations System 3 2013-10-01 2013-10-01 false Requirement to Inform Employees of Whistleblower Rights. 252.203-7002 Section 252.203-7002 Federal Acquisition Regulations System DEFENSE ACQUISITION REGULATIONS SYSTEM, DEPARTMENT OF DEFENSE CLAUSES AND FORMS SOLICITATION PROVISIONS...

Activity Theory in Information Systems Research and Practice: Theoretical Underpinnings for an Information Systems Development Model

ERIC Educational Resources Information Center

Mursu, Anja; Luukkonen, Irmeli; Toivanen, Marika; Korpela, Mikko

2007-01-01

Introduction: The purpose of information systems is to facilitate work activities: here we consider how Activity Theory can be applied in information systems development. Method. The requirements for an analytical model for emancipatory, work-oriented information systems research and practice are specified. Previous research work in Activity…

Environmental Files and Data Bases. Part A. Introduction and Oceanographic Management Information System.

DTIC Science & Technology

1981-09-01

Management Information System Naval Oceanography Program Naval Oceanographic Requirements Acoustic Reference Service Research Vehicle...THE OCEANOGRAPHIC MANAGEMENT INFORMATION SYSTEM . .. .... 2-1 3. ACOUSTIC DATA .. .. .... ......... ...... 3-1 4. GEOLOGICAL AND GEOPHYSICAL DATA...36 CHAPTER 2 THE OCEANOGRAPHIC MANAGEMENT INFORMATION SYSTEM 2-i CHAPTER 2 THE OCEANOGRAPHIC MANAGEMENT INFORMATION SYSTEM CONTENTS Page

Systems Security Engineering

DTIC Science & Technology

2010-08-22

Commission (IEC). “Information technology — Security techniques — Code of practice for information security management ( ISO /IEC 27002 ...Information technology — Security techniques — Information security management systems —Requirements ( ISO /IEC 27002 ),”, “Information technology — Security...was a draft ISO standard on Systems and software engineering, Systems and software assurance [18]. Created by systems engineers for systems

78 FR 5787 - Privacy Act of 1974; System of Records

Federal Register 2010, 2011, 2012, 2013, 2014

2013-01-28

... Act System of Records entitled ``Public Affairs Management Information System.'' This notice responds..., 2012. FOR FURTHER INFORMATION CONTACT: Mrs. Cindy Allard at (571) 372-0461. SUPPLEMENTARY INFORMATION... 4, DoD Information Security Program, Controlled Unclassified Information (CUI) requires that...

Seaway Information System Management and Control Requirements

DOT National Transportation Integrated Search

1973-10-01

This report examines in detail the control and information system requirements of the St. Lawrence Seaway development program in terms of the needs of the vessel traffic controllers and the management users. Structural control models of Seaway operat...

49 CFR 601.45 - Required information.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 49 Transportation 7 2012-10-01 2012-10-01 false Required information. 601.45 Section 601.45 Transportation Other Regulations Relating to Transportation (Continued) FEDERAL TRANSIT ADMINISTRATION... Transportation Systems § 601.45 Required information. A petition for relief under this section shall: (a...

Parameter Requirements for Description of Alternative LINC Systems. Final Report.

ERIC Educational Resources Information Center

Center for Applied Linguistics, Washington, DC. Language Information Network and Clearinghouse System.

This study was undertaken for the Center for Applied Linguistics to survey and analyze its information system program for the language sciences. The study identifies and defines the generalized sets of parameters required for subsequent quantitative analysis of proposed alternative Language Information Network and Clearinghouse Systems by means of…

48 CFR 3439.702 - Department security requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... requirements. 3439.702 Section 3439.702 Federal Acquisition Regulations System DEPARTMENT OF EDUCATION ACQUISITION REGULATION SPECIAL CATEGORIES OF CONTRACTING ACQUISITION OF INFORMATION TECHNOLOGY Department Requirements for Acquisition of Information Technology 3439.702 Department security requirements. The...

Digital Avionics Information System (DAIS): Training Requirements Analysis Model (TRAMOD).

ERIC Educational Resources Information Center

Czuchry, Andrew J.; And Others

The training requirements analysis model (TRAMOD) described in this report represents an important portion of the larger effort called the Digital Avionics Information System (DAIS) Life Cycle Cost (LCC) Study. TRAMOD is the second of three models that comprise an LCC impact modeling system for use in the early stages of system development. As…

Central American information system for energy planning (in English; Spanish)

DOE Office of Scientific and Technical Information (OSTI.GOV)

Fonseca, M.G.; Lyon, P.C.; Heskett, J.C.

1991-04-01

SICAPE (Sistema de Information Centroamericano para Planificacion Energetica) is an expandable information system designed for energy planning. Its objective is to satisfy ongoing information requirements by means of a menu driver operational environment. SICAPE is as easily used by the novice computer user as those with more experience. Moreover, the system is capable of evolving concurrently with future requirements of the individual country. The expansion is accomplished by menu restructuring as data and user requirements change. The new menu configurations require no programming effort. The use and modification of SICAPE are separate menu-driven processes that allow for rapid data query,more » minimal training, and effortless continued growth. SICAPE's data is organized by country or region. Information is available in the following areas: energy balance, macro economics, electricity generation capacity, and electricity and petroleum product pricing. (JF)« less

Transforming User Needs into Functional Requirements for an Antibiotic Clinical Decision Support System

PubMed Central

Bright, T.J.

2013-01-01

Summary Background Many informatics studies use content analysis to generate functional requirements for system development. Explication of this translational process from qualitative data to functional requirements can strengthen the understanding and scientific rigor when applying content analysis in informatics studies. Objective To describe a user-centered approach transforming emergent themes derived from focus group data into functional requirements for informatics solutions and to illustrate these methods to the development of an antibiotic clinical decision support system (CDS). Methods The approach consisted of five steps: 1) identify unmet therapeutic planning information needs via Focus Group Study-I, 2) develop a coding framework of therapeutic planning themes to refine the domain scope to antibiotic therapeutic planning, 3) identify functional requirements of an antibiotic CDS system via Focus Group Study-II, 4) discover informatics solutions and functional requirements from coded data, and 5) determine the types of information needed to support the antibiotic CDS system and link with the identified informatics solutions and functional requirements. Results The coding framework for Focus Group Study-I revealed unmet therapeutic planning needs. Twelve subthemes emerged and were clustered into four themes; analysis indicated a need for an antibiotic CDS intervention. Focus Group Study-II included five types of information needs. Comments from the Barrier/Challenge to information access and Function/Feature themes produced three informatics solutions and 13 functional requirements of an antibiotic CDS system. Comments from the Patient, Institution, and Domain themes generated required data elements for each informatics solution. Conclusion This study presents one example explicating content analysis of focus group data and the analysis process to functional requirements from narrative data. Illustration of this 5-step method was used to develop an antibiotic CDS system, resolving unmet antibiotic prescribing needs. As a reusable approach, these techniques can be refined and applied to resolve unmet information needs with informatics interventions in additional domains. PMID:24454586

The educational needs of health information managers in an electronic environment: what information technology and health informatics skills and knowledge are required?

PubMed

Robertson, Merryn; Callen, Joanne

The profile of health information managers (HIMs) employed within one metropolitan area health service in New South Wales (NSW) was identified, together with which information technology and health informatics knowledge and skills they possess, and which ones they require in their workplace. The subjects worked in a variety of roles: 26% were employed in the area's Information Systems Division developing and implementing point-of-care clinical systems. Health information managers perceived they needed further continuing and formal education in point-of-care clinical systems, decision support systems, the electronic health record, privacy and security, health data collections, and database applications.

Workshop proceedings: Information Systems for Space Astrophysics in the 21st Century, volume 1

NASA Technical Reports Server (NTRS)

Cutts, James (Editor); Ng, Edward (Editor)

1991-01-01

The Astrophysical Information Systems Workshop was one of the three Integrated Technology Planning workshops. Its objectives were to develop an understanding of future mission requirements for information systems, the potential role of technology in meeting these requirements, and the areas in which NASA investment might have the greatest impact. Workshop participants were briefed on the astrophysical mission set with an emphasis on those missions that drive information systems technology, the existing NASA space-science operations infrastructure, and the ongoing and planned NASA information systems technology programs. Program plans and recommendations were prepared in five technical areas: Mission Planning and Operations; Space-Borne Data Processing; Space-to-Earth Communications; Science Data Systems; and Data Analysis, Integration, and Visualization.

78 FR 67133 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-11-08

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System [Docket Number DARS-2013-0038] Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Publicizing Contract Actions AGENCY: Defense Acquisition Regulation System, Department of Defense (DoD). ACTION: Notice and...

76 FR 72916 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-11-28

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System [OMB Control Number 0704-0454] Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Administrative Matters AGENCY: Defense Acquisition Regulations System, Department of Defense (DoD). ACTION: Notice; request for...

78 FR 70294 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-11-25

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System [Docket Number DARS 2013-0046] Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Administrative Matters AGENCY: Defense Acquisition Regulations System, Department of Defense (DoD). ACTION: Notice and request...

Analysis of information systems for hydropower operations

NASA Technical Reports Server (NTRS)

Sohn, R. L.; Becker, L.; Estes, J.; Simonett, D.; Yeh, W. W. G.

1976-01-01

The operations of hydropower systems were analyzed with emphasis on water resource management, to determine how aerospace derived information system technologies can increase energy output. Better utilization of water resources was sought through improved reservoir inflow forecasting based on use of hydrometeorologic information systems with new or improved sensors, satellite data relay systems, and use of advanced scheduling techniques for water release. Specific mechanisms for increased energy output were determined, principally the use of more timely and accurate short term (0-7 days) inflow information to reduce spillage caused by unanticipated dynamic high inflow events. The hydrometeorologic models used in predicting inflows were examined to determine the sensitivity of inflow prediction accuracy to the many variables employed in the models, and the results used to establish information system requirements. Sensor and data handling system capabilities were reviewed and compared to the requirements, and an improved information system concept outlined.

The impact of prospective pricing on the information system in the health care industry.

PubMed

Matta, K F

1988-02-01

The move from a retrospective payment system (value added) to a prospective payment system (diagnostic related) has not only influenced the health care business but also changed their information systems' requirements. The change in requirements can be attributed both to an increase in data processing tasks and also to an increase in the need for information to more effectively manage the organization. A survey was administered to capture the response of health care institutions, in the area of information systems, to the prospective payment system. The survey results indicate that the majority of health care institutions have responded by increasing their information resources, both in terms of hardware and software, and have moved to integrate the medical and financial data. In addition, the role of the information system has changed from a cost accounting system to one intended to provide a competitive edge in a highly competitive marketing environment.

Analysis of information systems for hydropower operations: Executive summary

NASA Technical Reports Server (NTRS)

Sohn, R. L.; Becker, L.; Estes, J.; Simonett, D.; Yeh, W.

1976-01-01

An analysis was performed of the operations of hydropower systems, with emphasis on water resource management, to determine how aerospace derived information system technologies can effectively increase energy output. Better utilization of water resources was sought through improved reservoir inflow forecasting based on use of hydrometeorologic information systems with new or improved sensors, satellite data relay systems, and use of advanced scheduling techniques for water release. Specific mechanisms for increased energy output were determined, principally the use of more timely and accurate short term (0-7 days) inflow information to reduce spillage caused by unanticipated dynamic high inflow events. The hydrometeorologic models used in predicting inflows were examined in detail to determine the sensitivity of inflow prediction accuracy to the many variables employed in the models, and the results were used to establish information system requirements. Sensor and data handling system capabilities were reviewed and compared to the requirements, and an improved information system concept was outlined.

The Global Emergency Observation and Warning System

NASA Technical Reports Server (NTRS)

Bukley, Angelia P.; Mulqueen, John A.

1994-01-01

Based on an extensive characterization of natural hazards, and an evaluation of their impacts on humanity, a set of functional technical requirements for a global warning and relief system was developed. Since no technological breakthroughs are required to implement a global system capable of performing the functions required to provide sufficient information for prevention, preparedness, warning, and relief from natural disaster effects, a system is proposed which would combine the elements of remote sensing, data processing, information distribution, and communications support on a global scale for disaster mitigation.

Detailed requirements document for Stowage List and Hardware Tracking System (SLAHTS). [computer based information management system in support of space shuttle orbiter stowage configuration

NASA Technical Reports Server (NTRS)

Keltner, D. J.

1975-01-01

The stowage list and hardware tracking system, a computer based information management system, used in support of the space shuttle orbiter stowage configuration and the Johnson Space Center hardware tracking is described. The input, processing, and output requirements that serve as a baseline for system development are defined.

Identification of specific requirements for a NASA aerospace law information system and identification of the acquisition requirements for an aerospace law collection for the NASA law library

NASA Technical Reports Server (NTRS)

Morenoff, J.; Roth, D. L.; Singleton, J. W.

1972-01-01

The study to develop, implement, and maintain a space law library and information system is summarized. The survey plan; major interviews with individuals representative of potential sources, users and producers of information related to aerospace law; and system trade-off analyses are discussed along with the NASA/RECON system capability. The NASA publications of STAR and IAA are described, and the NASA legal micro-thesaurus is included.

Requirements for a Global Greenhouse Gas Information System

NASA Astrophysics Data System (ADS)

Duren, R.; Boland, S.; Lempert, R.; Miller, C.

2008-12-01

A global greenhouse gas information system will prove a critical component of any successful effort to mitigate climate change which relies on limiting the atmospheric concentration of greenhouse gases. The system will provide the situational awareness necessary to actively reduce emissions, influence land use change, and sequester carbon. The information from such a system will be subject to intense scrutiny. Therefore, an effective system must openly and transparently produce data of unassailable quality. A global greenhouse gas information system will likely require a combination of space-and air-based remote- sensing assets, ground-based measurements, carbon cycle modeling and self-reporting. The specific requirements on such a system will be shaped by the degree of international cooperation it enjoys and the needs of the policy regime it aims to support, which might range from verifying treaty obligations, to certifying the tradable permits and offsets underlying a market in greenhouse gas emission reductions, to providing a comprehensive inventory of high and low emitters that could be used by non-governmental organizations and other international actors. While some technical studies have examined particular system components in single scenarios, there remains a need for a comprehensive survey of the range of potential requirements, options, and strategies for the overall system. We have initiated such a survey and recently hosted a workshop which engaged a diverse community of stakeholders to begin synthesizing requirements for such a system, with an initial focus on carbon dioxide. In this paper we describe our plan for completing the definition of the requirements, options, and strategies for a global greenhouse gas monitoring system. We discuss our overall approach and provide a status on the initial requirements synthesis activity.

Teaching Management Information Systems as a General Education Requirement (GER) Capstone

ERIC Educational Resources Information Center

Hoanca, Bogdan

2012-01-01

Although many IS programs nationwide use capstone courses in the major, this paper reports on the use of an upper division Management Information Systems (MIS) class as a general education requirements (GER) capstone. The class is a core requirement for all majors in the Bachelor of Business Administration (BBA) program at the University of Alaska…

17 CFR 249.821 - Form PILOT, information required of self-regulatory organizations operating pilot trading systems...

Code of Federal Regulations, 2010 CFR

2010-04-01

... required of self-regulatory organizations operating pilot trading systems pursuant to § 240.19b-5 of this... (CONTINUED) FORMS, SECURITIES EXCHANGE ACT OF 1934 Forms for Self-Regulatory Organization Rule Changes and... Associations § 249.821 Form PILOT, information required of self-regulatory organizations operating pilot...

17 CFR 249.821 - Form PILOT, information required of self-regulatory organizations operating pilot trading systems...

Code of Federal Regulations, 2011 CFR

2011-04-01

... required of self-regulatory organizations operating pilot trading systems pursuant to § 240.19b-5 of this... (CONTINUED) FORMS, SECURITIES EXCHANGE ACT OF 1934 Forms for Self-Regulatory Organization Rule Changes and... Associations § 249.821 Form PILOT, information required of self-regulatory organizations operating pilot...

17 CFR 249.821 - Form PILOT, information required of self-regulatory organizations operating pilot trading systems...

Code of Federal Regulations, 2013 CFR

2013-04-01

... required of self-regulatory organizations operating pilot trading systems pursuant to § 240.19b-5 of this... (CONTINUED) FORMS, SECURITIES EXCHANGE ACT OF 1934 Forms for Self-Regulatory Organization Rule Changes and... Associations § 249.821 Form PILOT, information required of self-regulatory organizations operating pilot...

17 CFR 249.821 - Form PILOT, information required of self-regulatory organizations operating pilot trading systems...

Code of Federal Regulations, 2012 CFR

2012-04-01

... required of self-regulatory organizations operating pilot trading systems pursuant to § 240.19b-5 of this... (CONTINUED) FORMS, SECURITIES EXCHANGE ACT OF 1934 Forms for Self-Regulatory Organization Rule Changes and... Associations § 249.821 Form PILOT, information required of self-regulatory organizations operating pilot...

17 CFR 249.821 - Form PILOT, information required of self-regulatory organizations operating pilot trading systems...

Code of Federal Regulations, 2014 CFR

2014-04-01

... required of self-regulatory organizations operating pilot trading systems pursuant to § 240.19b-5 of this... (CONTINUED) FORMS, SECURITIES EXCHANGE ACT OF 1934 Forms for Self-Regulatory Organization Rule Changes and... Associations § 249.821 Form PILOT, information required of self-regulatory organizations operating pilot...

Facebook for scientists: requirements and services for optimizing how scientific collaborations are established.

PubMed

Schleyer, Titus; Spallek, Heiko; Butler, Brian S; Subramanian, Sushmita; Weiss, Daniel; Poythress, M Louisa; Rattanathikun, Phijarana; Mueller, Gregory

2008-08-13

As biomedical research projects become increasingly interdisciplinary and complex, collaboration with appropriate individuals, teams, and institutions becomes ever more crucial to project success. While social networks are extremely important in determining how scientific collaborations are formed, social networking technologies have not yet been studied as a tool to help form scientific collaborations. Many currently emerging expertise locating systems include social networking technologies, but it is unclear whether they make the process of finding collaborators more efficient and effective. This study was conducted to answer the following questions: (1) Which requirements should systems for finding collaborators in biomedical science fulfill? and (2) Which information technology services can address these requirements? The background research phase encompassed a thorough review of the literature, affinity diagramming, contextual inquiry, and semistructured interviews. This phase yielded five themes suggestive of requirements for systems to support the formation of collaborations. In the next phase, the generative phase, we brainstormed and selected design ideas for formal concept validation with end users. Then, three related, well-validated ideas were selected for implementation and evaluation in a prototype. Five main themes of systems requirements emerged: (1) beyond expertise, successful collaborations require compatibility with respect to personality, work style, productivity, and many other factors (compatibility); (2) finding appropriate collaborators requires the ability to effectively search in domains other than your own using information that is comprehensive and descriptive (communication); (3) social networks are important for finding potential collaborators, assessing their suitability and compatibility, and establishing contact with them (intermediation); (4) information profiles must be complete, correct, up-to-date, and comprehensive and allow fine-grained control over access to information by different audiences (information quality and access); (5) keeping online profiles up-to-date should require little or no effort and be integrated into the scientist's existing workflow (motivation). Based on the requirements, 16 design ideas underwent formal validation with end users. Of those, three were chosen to be implemented and evaluated in a system prototype, "Digital|Vita": maintaining, formatting, and semi-automated updating of biographical information; searching for experts; and building and maintaining the social network and managing document flow. In addition to quantitative and factual information about potential collaborators, social connectedness, personal and professional compatibility, and power differentials also influence whether collaborations are formed. Current systems only partially model these requirements. Services in Digital|Vita combine an existing workflow, maintaining and formatting biographical information, with collaboration-searching functions in a novel way. Several barriers to the adoption of systems such as Digital|Vita exist, such as potential adoption asymmetries between junior and senior researchers and the tension between public and private information. Developers and researchers may consider one or more of the services described in this paper for implementation in their own expertise locating systems.

POLARIS: Helping Managers Get Answers Fast!

NASA Technical Reports Server (NTRS)

Corcoran, Patricia M.; Webster, Jeffery

2007-01-01

This viewgraph presentation reviews the Project Online Library and Resource Information System (POLARIS) system. It is NASA-wide, web-based system, providing access to information related to Program and Project Management. It will provide a one-stop shop for access to: a searchable, sortable database of all requirements for all product lines, project life cycle diagrams with reviews, project life cycle diagrams with reviews, project review definitions with products review information from NPR 7123.1, NASA Systems Engineering Processes and Requirements, templates and examples of products, project standard WBSs with dictionaries, and requirements for implementation and approval, information from NASA s Metadata Manager (MdM): Attributes of Missions, Themes, Programs & Projects, NPR7120.5 waiver form and instructions and much more. The presentation reviews the plans and timelines for future revisions and modifications.

An Approach for Implementation of Project Management Information Systems

NASA Astrophysics Data System (ADS)

Běrziša, Solvita; Grabis, Jānis

Project management is governed by project management methodologies, standards, and other regulatory requirements. This chapter proposes an approach for implementing and configuring project management information systems according to requirements defined by these methodologies. The approach uses a project management specification framework to describe project management methodologies in a standardized manner. This specification is used to automatically configure the project management information system by applying appropriate transformation mechanisms. Development of the standardized framework is based on analysis of typical project management concepts and process and existing XML-based representations of project management. A demonstration example of project management information system's configuration is provided.

19 CFR 192.14 - Electronic information for outward cargo required in advance of departure.

Code of Federal Regulations, 2014 CFR

2014-04-01

... Information Through the Automated Export System (AES) § 192.14 Electronic information for outward cargo... Automated Export System (AES)). (b) Presentation of data—(1) Time for presenting data. USPPIs or their... regulatory authority to do so. The CBP will also continue to require 72-hour advance notice for used vehicle...

19 CFR 192.14 - Electronic information for outward cargo required in advance of departure.

Code of Federal Regulations, 2013 CFR

2013-04-01

... Information Through the Automated Export System (AES) § 192.14 Electronic information for outward cargo... Automated Export System (AES)). (b) Presentation of data—(1) Time for presenting data. USPPIs or their... regulatory authority to do so. The CBP will also continue to require 72-hour advance notice for used vehicle...

19 CFR 192.14 - Electronic information for outward cargo required in advance of departure.

Code of Federal Regulations, 2012 CFR

2012-04-01

... Information Through the Automated Export System (AES) § 192.14 Electronic information for outward cargo... Automated Export System (AES)). (b) Presentation of data—(1) Time for presenting data. USPPIs or their... regulatory authority to do so. The CBP will also continue to require 72-hour advance notice for used vehicle...

19 CFR 192.14 - Electronic information for outward cargo required in advance of departure.

Code of Federal Regulations, 2011 CFR

2011-04-01

... Information Through the Automated Export System (AES) § 192.14 Electronic information for outward cargo... Automated Export System (AES)). (b) Presentation of data—(1) Time for presenting data. USPPIs or their... regulatory authority to do so. The CBP will also continue to require 72-hour advance notice for used vehicle...

78 FR 67132 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Contract...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-11-08

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System [Docket Number DARS-2013-0039] Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Contract Pricing AGENCY: Defense Acquisition Regulations System, Department of Defense (DoD). ACTION: Notice and request for...

76 FR 71558 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Requests...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-11-18

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System [Docket No. DARS 2011-0069-0002] Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Requests for Equitable Adjustment (OMB Control Number 0704-0397) AGENCY: Defense Acquisition Regulations System, Department of...

75 FR 45104 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Contract...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-08-02

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Contract Pricing (OMB Control Number 0704-0232) AGENCY: Defense Acquisition Regulations System, Department of Defense (DoD). ACTION: Notice and request for...

78 FR 68830 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Service...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-11-15

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Service Contracting AGENCY: Defense Acquisition Regulation System, Department of Defense (DoD). ACTION: Notice and request for comments regarding a proposed...

78 FR 68829 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Contract...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-11-15

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Contract Financing AGENCY: Defense Acquisition Regulations System, Department of Defense (DoD). ACTION: Notice and request for comments regarding a proposed...

75 FR 47561 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Contract...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-08-06

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Contract Financing (OMB Control Number 0704- 0359) AGENCY: Defense Acquisition Regulations System, Department of Defense (DoD). ACTION: Notice and request...

78 FR 48632 - Releasing Information; General Provisions; Accounting and Reporting Requirements; Reports of...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-08-09

... the confidentiality of borrower information. The system of internal controls, at a minimum, must... and maintain an effective system of internal controls over the data included in the report of accounts... system of internal controls, at a minimum, must comply with the requirements of applicable Farm Credit...

Development of Integrated Programs for Aerospace-Vehicle Design (IPAD) - IPAD user requirements

NASA Technical Reports Server (NTRS)

Anderton, G. L.

1979-01-01

Results of a requirements analysis task for Integrated Programs for Aerospace Vehicle Design (IPAD) are presented. User requirements which, in part, will shape the IPAD system design are given. Requirements considered were: generation, modification, storage, retrieval, communication, reporting, and protection of information. Data manipulation and controls on the system and the information were also considered. Specific needs relative to the product design process are also discussed.

Transforming Legacy Systems to Obtain Information Superiority

DTIC Science & Technology

2001-01-01

is imperative that innovative technologies be developed to enable legacy weapon systems to exploit the information revolution, achieve information ... dominance , and meet the required operational tempo. This paper presents an embedded-system architecture, open system middleware services, and a software

The study on knowledge transferring incentive for information system requirement development

DOE Office of Scientific and Technical Information (OSTI.GOV)

Li, Yang

2015-03-10

Information system requirement development is a process of users’ knowledge sharing and transferring. However the tacit requirements developing is a main problem during requirement development process, for the reason of difficult to encoding, express, and communicate. Knowledge fusion and corporate effort is needed to finding tacit requirements. Under this background, our paper try to find out the rule of effort dynamic evolutionary of software developer and user by building an evolutionary game model on the condition of incentive system. And in addition this paper provides an in depth discussion at the end of this paper.

Basic Concepts Required in the Development of a Planning Information System.

ERIC Educational Resources Information Center

Kennedy, F. D.

This report, the result of developmental research on a planning information system for North Carolina, describes the planning process at higher levels of State government, defines a general information system and derives a planning information system from various types of planning, provides guidelines for system design and evaluation, and…

Information data systems for a global change technology initiative architecture trade study

NASA Technical Reports Server (NTRS)

Murray, Nicholas D.

1991-01-01

The Global Change Technology Initiative (GCTI) was established to develop technology which will enable use of satellite systems of Earth observations on a global scale, enable use of the observations to predictively model Earth's changes, and provide scientists, government, business, and industry with quick access to the resulting information. At LaRC, a GCTI Architecture Trade Study was undertaken to develop and evaluate the architectural implications to meet the requirements of the global change studies and the eventual implementation of a global change system. The output of the trade study are recommended technologies for the GCTI. That portion of the study concerned with the information data system is documented. The information data system for an earth global change modeling system can be very extensive and beyond affordability in terms of today's costs. Therefore, an incremental approach to gaining a system is most likely. An options approach to levels of capability versus needed technologies was developed. The primary drivers of the requirements for the information data system evaluation were the needed science products, the science measurements, the spacecraft orbits, the instruments configurations, and the spacecraft configurations and their attendant architectures. The science products requirements were not studied here; however, some consideration of the product needs were included in the evaluation results. The information data system technology items were identified from the viewpoint of the desirable overall information system characteristics.

Engineering Safety- and Security-Related Requirements for Software-Intensive Systems

DTIC Science & Technology

2010-04-27

Requirements Negative (shall not) Requirements Hardware Requirements equ remen s System / Documentation Requirements eve oper Requirements Operational ...Validation Actual / Proposed Defensibility C li Operational Vulnerability Analysis VulnerabilityVulnerability Safety Vulnerability performs System ...including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson

Information Requirements for Integrating Spatially Discrete, Feature-Based Earth Observations

NASA Astrophysics Data System (ADS)

Horsburgh, J. S.; Aufdenkampe, A. K.; Lehnert, K. A.; Mayorga, E.; Hsu, L.; Song, L.; Zaslavsky, I.; Valentine, D. L.

2014-12-01

Several cyberinfrastructures have emerged for sharing observational data collected at densely sampled and/or highly instrumented field sites. These include the CUAHSI Hydrologic Information System (HIS), the Critical Zone Observatory Integrated Data Management System (CZOData), the Integrated Earth Data Applications (IEDA) and EarthChem system, and the Integrated Ocean Observing System (IOOS). These systems rely on standard data encodings and, in some cases, standard semantics for classes of geoscience data. Their focus is on sharing data on the Internet via web services in domain specific encodings or markup languages. While they have made progress in making data available, it still takes investigators significant effort to discover and access datasets from multiple repositories because of inconsistencies in the way domain systems describe, encode, and share data. Yet, there are many scenarios that require efficient integration of these data types across different domains. For example, understanding a soil profile's geochemical response to extreme weather events requires integration of hydrologic and atmospheric time series with geochemical data from soil samples collected over various depth intervals from soil cores or pits at different positions on a landscape. Integrated access to and analysis of data for such studies are hindered because common characteristics of data, including time, location, provenance, methods, and units are described differently within different systems. Integration requires syntactic and semantic translations that can be manual, error-prone, and lossy. We report information requirements identified as part of our work to define an information model for a broad class of earth science data - i.e., spatially-discrete, feature-based earth observations resulting from in-situ sensors and environmental samples. We sought to answer the question: "What information must accompany observational data for them to be archivable and discoverable within a publication system as well as interpretable once retrieved from such a system for analysis and (re)use?" We also describe development of multiple functional schemas (i.e., physical implementations for data storage, transfer, and archival) for the information model that capture the requirements reported here.

Information services platforms at geosynchronous earth orbit: A requirements analysis

NASA Technical Reports Server (NTRS)

1978-01-01

The potential user requirements for Information Services Platforms at geosynchronous orbits were investigated. A rationale for identifying the corollary system requirements and supporting research and technology needs was provided.

Methodology. Volume 3

DTIC Science & Technology

1997-02-01

modification, test, and production System operation, support, and maturation Weapon System Life Cycle Management Weapon systems Attainment...information management systems • Weapon systems electronics context – Focuses on many types of interactions » Information » Jamming » Support – Deals with...concepts • C4I context – Focuses on C4I information management systems – Defines the C4I systems and their information interchange requirements

48 CFR 30.202-4 - Privileged and confidential information.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 48 Federal Acquisition Regulations System 1 2010-10-01 2010-10-01 false Privileged and confidential information. 30.202-4 Section 30.202-4 Federal Acquisition Regulations System FEDERAL ACQUISITION REGULATION GENERAL CONTRACTING REQUIREMENTS COST ACCOUNTING STANDARDS ADMINISTRATION CAS Program Requirements...

76 FR 50461 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Types of...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-08-15

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System [OMB Control Number 0704-0259] Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Types of Contracts AGENCY: Defense Acquisition Regulations System, Department of Defense (DoD). ACTION: Notice and request...

48 CFR 30.202-4 - Privileged and confidential information.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 48 Federal Acquisition Regulations System 1 2011-10-01 2011-10-01 false Privileged and confidential information. 30.202-4 Section 30.202-4 Federal Acquisition Regulations System FEDERAL ACQUISITION REGULATION GENERAL CONTRACTING REQUIREMENTS COST ACCOUNTING STANDARDS ADMINISTRATION CAS Program Requirements...

75 FR 20825 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; DoD Pilot...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-04-21

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System [OMB Control Number 0704-0332] Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; DoD Pilot Mentor-Protege Program AGENCY: Defense Acquisition Regulations System, Department of Defense (DoD). ACTION...

48 CFR 9.105-1 - Obtaining information.

Code of Federal Regulations, 2010 CFR

2010-10-01

... information required concerning the adequacy of prospective contractors' accounting systems and these systems... accounting systems, and these systems' suitability for use in administering the proposed type of contract. (3... 48 Federal Acquisition Regulations System 1 2010-10-01 2010-10-01 false Obtaining information. 9...

77 FR 51783 - Federal Acquisition Regulation; Information Collection; Contractors' Purchasing Systems Reviews

Federal Register 2010, 2011, 2012, 2013, 2014

2012-08-27

...; Information Collection; Contractors' Purchasing Systems Reviews AGENCY: Department of Defense (DOD), General... collection requirement concerning contractors' purchasing systems reviews. Public comments are particularly... Information Collection 9000- 0132, Contractors' Purchasing Systems Reviews, by any of the following methods...

Managing Information On Technical Requirements

NASA Technical Reports Server (NTRS)

Mauldin, Lemuel E., III; Hammond, Dana P.

1993-01-01

Technical Requirements Analysis and Control Systems/Initial Operating Capability (TRACS/IOC) computer program provides supplemental software tools for analysis, control, and interchange of project requirements so qualified project members have access to pertinent project information, even if in different locations. Enables users to analyze and control requirements, serves as focal point for project requirements, and integrates system supporting efficient and consistent operations. TRACS/IOC is HyperCard stack for use on Macintosh computers running HyperCard 1.2 or later and Oracle 1.2 or later.

Standards Advisor-Advanced Information Technology for Advanced Information Delivery

NASA Technical Reports Server (NTRS)

Hawker, J. Scott

2003-01-01

Developers of space systems must deal with an increasing amount of information in responding to extensive requirements and standards from numerous sources. Accessing these requirements and standards, understanding them, comparing them, negotiating them and responding to them is often an overwhelming task. There are resources to aid the space systems developer, such as lessons learned and best practices. Again, though, accessing, understanding, and using this information is often more difficult than helpful. This results in space systems that: 1. Do not meet all their requirements. 2. Do not incorporate prior engineering experience. 3. Cost more to develop. 4. Take longer to develop. The NASA Technical Standards Program (NTSP) web site at http://standards.nasa.gov has made significant improvements in making standards, lessons learned, and related material available to space systems developers agency-wide. The Standards Advisor was conceived to take the next steps beyond the current product, continuing to apply evolving information technology that continues to improve information delivery to space systems developers. This report describes the features of the Standards Advisor and suggests a technical approach to its development.

System requirements for a computerised patient record information system at a busy primary health care clinic.

PubMed

Blignaut, P J; McDonald, T; Tolmie, C J

2001-05-01

A prototyping approach was used to determine the essential system requirements of a computerised patient record information system for a typical township primary health care clinic. A pilot clinic was identified and the existing manual system and business processes in this clinic was studied intensively before the first prototype was implemented. Interviews with users, incidental observations and analysis of actual data entered were used as primary techniques to refine the prototype system iteratively until a system with an acceptable data set and adequate functionalities were in place. Several non-functional and user-related requirements were also discovered during the prototyping period.

Requirements for CEC POP Machine Protection System

DOE Office of Scientific and Technical Information (OSTI.GOV)

Pinayev, I.

2015-02-18

The requirements of CEC POP machine protection system are meant to prevent damage to a vacuum chamber by a missteered electron beam. In this example, beam energy = 22 MeV, Maximal bunch charge = 5 nC, Maximal repetition rate = 78 kHz, Normalized emittance = 5 mm mrad, Minimal β-function = 1 m. From this information the requirements of the protection system can be calculated by factoring the information into equations to find beam densities and temperature excursions.

Section 508 Electronic Information Accessibility Requirements for Software Development

NASA Technical Reports Server (NTRS)

Ellis, Rebecca

2014-01-01

Section 508 Subpart B 1194.21 outlines requirements for operating system and software development in order to create a product that is accessible to users with various disabilities. This portion of Section 508 contains a variety of standards to enable those using assistive technology and with visual, hearing, cognitive and motor difficulties to access all information provided in software. The focus on requirements was limited to the Microsoft Windows® operating system as it is the predominant operating system used at this center. Compliance with this portion of the requirements can be obtained by integrating the requirements into the software development cycle early and by remediating issues in legacy software if possible. There are certain circumstances with software that may arise necessitating an exemption from these requirements, such as design or engineering software using dynamically changing graphics or numbers to convey information. These exceptions can be discussed with the Section 508 Coordinator and another method of accommodation used.

46 CFR 162.060-14 - Information requirements for the ballast water management system (BWMS) application.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 6 2012-10-01 2012-10-01 false Information requirements for the ballast water management system (BWMS) application. 162.060-14 Section 162.060-14 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) EQUIPMENT, CONSTRUCTION, AND MATERIALS: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Ballast Water Management Systems §...

Functional requirements of computer systems for the U.S. Geological Survey, Water Resources Division, 1988-97

USGS Publications Warehouse

Hathaway, R.M.; McNellis, J.M.

1989-01-01

Investigating the occurrence, quantity, quality, distribution, and movement of the Nation 's water resources is the principal mission of the U.S. Geological Survey 's Water Resources Division. Reports of these investigations are published and available to the public. To accomplish this mission, the Division requires substantial computer technology to process, store, and analyze data from more than 57,000 hydrologic sites. The Division 's computer resources are organized through the Distributed Information System Program Office that manages the nationwide network of computers. The contract that provides the major computer components for the Water Resources Division 's Distributed information System expires in 1991. Five work groups were organized to collect the information needed to procure a new generation of computer systems for the U. S. Geological Survey, Water Resources Division. Each group was assigned a major Division activity and asked to describe its functional requirements of computer systems for the next decade. The work groups and major activities are: (1) hydrologic information; (2) hydrologic applications; (3) geographic information systems; (4) reports and electronic publishing; and (5) administrative. The work groups identified 42 functions and described their functional requirements for 1988, 1992, and 1997. A few new functions such as Decision Support Systems and Executive Information Systems, were identified, but most are the same as performed today. Although the number of functions will remain about the same, steady growth in the size, complexity, and frequency of many functions is predicted for the next decade. No compensating increase in the Division 's staff is anticipated during this period. To handle the increased workload and perform these functions, new approaches will be developed that use advanced computer technology. The advanced technology is required in a unified, tightly coupled system that will support all functions simultaneously. The new approaches and expanded use of computers will require substantial increases in the quantity and sophistication of the Division 's computer resources. The requirements presented in this report will be used to develop technical specifications that describe the computer resources needed during the 1990's. (USGS)

Automating the Air Force Retail-Level Equipment Management Process: An Application of Microcomputer-Based Information Systems Techniques

DTIC Science & Technology

1988-09-01

could use the assistance of a microcomputer-based management information system . However, adequate system design and development requires an in-depth...understanding of the Equipment Management Section and the environment in which it functions were asked and answered. Then, a management information system was...designed, developed, and tested. The management information system is called the Equipment Management Information System (EMIS).

49 CFR 232.303 - General requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... repair vehicle is used to conduct the repairs. (2) Major repair means a repair that normally would... automated tracking system approved for use by FRA, shall contain the following information about the... may use an electronic or automated tracking system to track the required information and the...

49 CFR 232.303 - General requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... repair vehicle is used to conduct the repairs. (2) Major repair means a repair that normally would... automated tracking system approved for use by FRA, shall contain the following information about the... may use an electronic or automated tracking system to track the required information and the...

49 CFR 232.303 - General requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... repair vehicle is used to conduct the repairs. (2) Major repair means a repair that normally would... automated tracking system approved for use by FRA, shall contain the following information about the... may use an electronic or automated tracking system to track the required information and the...

49 CFR 232.303 - General requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... repair vehicle is used to conduct the repairs. (2) Major repair means a repair that normally would... automated tracking system approved for use by FRA, shall contain the following information about the... may use an electronic or automated tracking system to track the required information and the...

49 CFR 232.303 - General requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... repair vehicle is used to conduct the repairs. (2) Major repair means a repair that normally would... automated tracking system approved for use by FRA, shall contain the following information about the... may use an electronic or automated tracking system to track the required information and the...

High efficiency coherent optical memory with warm rubidium vapour

PubMed Central

Hosseini, M.; Sparkes, B.M.; Campbell, G.; Lam, P.K.; Buchler, B.C.

2011-01-01

By harnessing aspects of quantum mechanics, communication and information processing could be radically transformed. Promising forms of quantum information technology include optical quantum cryptographic systems and computing using photons for quantum logic operations. As with current information processing systems, some form of memory will be required. Quantum repeaters, which are required for long distance quantum key distribution, require quantum optical memory as do deterministic logic gates for optical quantum computing. Here, we present results from a coherent optical memory based on warm rubidium vapour and show 87% efficient recall of light pulses, the highest efficiency measured to date for any coherent optical memory suitable for quantum information applications. We also show storage and recall of up to 20 pulses from our system. These results show that simple warm atomic vapour systems have clear potential as a platform for quantum memory. PMID:21285952

High efficiency coherent optical memory with warm rubidium vapour.

PubMed

Hosseini, M; Sparkes, B M; Campbell, G; Lam, P K; Buchler, B C

2011-02-01

By harnessing aspects of quantum mechanics, communication and information processing could be radically transformed. Promising forms of quantum information technology include optical quantum cryptographic systems and computing using photons for quantum logic operations. As with current information processing systems, some form of memory will be required. Quantum repeaters, which are required for long distance quantum key distribution, require quantum optical memory as do deterministic logic gates for optical quantum computing. Here, we present results from a coherent optical memory based on warm rubidium vapour and show 87% efficient recall of light pulses, the highest efficiency measured to date for any coherent optical memory suitable for quantum information applications. We also show storage and recall of up to 20 pulses from our system. These results show that simple warm atomic vapour systems have clear potential as a platform for quantum memory.

Requirements Specification Document

DOT National Transportation Integrated Search

1996-04-26

The System Definition Document identifies the top level processes, data flows, : and system controls for the Gary-Chicago-Milwaukee (GCM) Corridor Transportation Information Center (C-TIC). This Requirements Specification establishes the requirements...

Designing a Model for Integration of Information and Communication Technologies (ICTs) in the Iranian Agricultural Research System

ERIC Educational Resources Information Center

Sharifzadeh, Aboulqasem; Abdollahzadeh, Gholam Hossein; Sharifi, Mahnoosh

2009-01-01

Capacity Development is needed in the Iranian Agricultural System. Integrating Information and Communication Technologies (ICTs) in the agricultural research system is an appropriate capacity development mechanism. The appropriate application of ICTs and information such as a National Agricultural Information System requires a systemically…

Prototype Input and Output Data Elements for the Occupational Health and Safety Information System

NASA Technical Reports Server (NTRS)

Whyte, A. A.

1980-01-01

The National Aeronautics and Space Administration plans to implement a NASA-wide computerized information system for occupational health and safety. The system is necessary to administer the occupational health and safety programs and to meet the legal and regulatory reporting, recordkeeping, and surveillance requirements. Some of the potential data elements that NASA will require as input and output for the new occupational health and safety information system are illustrated. The data elements are shown on sample forms that have been compiled from various sources, including NASA Centers and industry.

Recommendations for an Executive Information System (EIS) for the NASA Accounting and Financial Information System (NAFIS)

NASA Technical Reports Server (NTRS)

Goss, Ernest Preston

1991-01-01

The objectives were to: (1) survey state-of-the-art computing architectures, tools, and technologies for implementing an Executive Information System (EIS); (2) review MSFC capabilities and efforts in developing an EIS for Shuttle Projects Office and the Payloads Project Office; (3) review management reporting requirements for the NASA Accounting and Financial Information System (NAFIS) Project in the areas of cost, schedule, and technical performance, and insure that the EIS fully supports these requirements; and (4) develop and implement a pilot concept for a NAFIS EIS. A summary of the findings of this work is presented.

Models Extracted from Text for System-Software Safety Analyses

NASA Technical Reports Server (NTRS)

Malin, Jane T.

2010-01-01

This presentation describes extraction and integration of requirements information and safety information in visualizations to support early review of completeness, correctness, and consistency of lengthy and diverse system safety analyses. Software tools have been developed and extended to perform the following tasks: 1) extract model parts and safety information from text in interface requirements documents, failure modes and effects analyses and hazard reports; 2) map and integrate the information to develop system architecture models and visualizations for safety analysts; and 3) provide model output to support virtual system integration testing. This presentation illustrates the methods and products with a rocket motor initiation case.

75 FR 22844 - Construction Fall Protection Systems Criteria and Practices and Training Requirements; Extension...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-04-30

...] Construction Fall Protection Systems Criteria and Practices and Training Requirements; Extension of the Office of Management and Budget's (OMB) Approval of Information Collection (Paperwork) Requirements AGENCY... requirements contained in the construction standards on Fall Protection Systems Criteria and Practices (29 CFR...

NASIS data base management system - IBM 360/370 OS MVT implementation. 2: Overviews

NASA Technical Reports Server (NTRS)

1973-01-01

The systems overviews of the NASA Aerospace Safety Information System (NASIS) are presented. The overviews are directed toward informing management of a system's capabilities and requirements. The intent of the overviews is to introduce the system features to interested individuals. Each overview contains a description of the component's activities and roles in the overall system. The description includes charts and diagrams and a discussion of the performance requirements and growth potential of the module.

SPAN security policies and guidelines

NASA Technical Reports Server (NTRS)

Sisson, Patricia L.; Green, James L.

1989-01-01

A guide is provided to system security with emphasis on requirements and guidelines that are necessary to maintain an acceptable level of security on the network. To have security for the network, each node on the network must be secure. Therefore, each system manager, must strictly adhere to the requirements and must consider implementing the guidelines discussed. There are areas of vulnerability within the operating system that may not be addressed. However, when a requirement or guideline is discussed, implementation techniques are included. Information related to computer and data security is discussed to provide information on implementation options. The information is presented as it relates to a VAX computer environment.

San Juan National Forest Land Management Planning Support System (LMPSS) requirements definition

NASA Technical Reports Server (NTRS)

Werth, L. F. (Principal Investigator)

1981-01-01

The role of remote sensing data as it relates to a three-component land management planning system (geographic information, data base management, and planning model) can be understood only when user requirements are known. Personnel at the San Juan National Forest in southwestern Colorado were interviewed to determine data needs for managing and monitoring timber, rangelands, wildlife, fisheries, soils, water, geology and recreation facilities. While all the information required for land management planning cannot be obtained using remote sensing techniques, valuable information can be provided for the geographic information system. A wide range of sensors such as small and large format cameras, synthetic aperture radar, and LANDSAT data should be utilized. Because of the detail and accuracy required, high altitude color infrared photography should serve as the baseline data base and be supplemented and updated with data from the other sensors.

Hemodialysis Adequacy Monitoring Information System: Minimum Data Set and Capabilities Required.

PubMed

Jebraeily, Mohamad; Ghazisaeidi, Marjan; Safdari, Reza; Makhdoomi, Khadijeh; Rahimi, Bahlol

2015-08-01

In dialysis centers both nephrologists and nurses are faced with the challenge of ensuring reliable and efficient care accordance with the clinical guideline. Hemodialysis adequacy monitoring information system therefore enable the automation of tasks, which ultimately allows doctors and nursing staff more time to dedicate to the individual treatment of patients. Development of the information systems in healthcare has made the use of the Minimum data set inevitable. The purpose of this study was determined MDS and capabilities required in hemodialysis adequacy monitoring information system. This is a cross-sectional survey conducted with participation of 320 nephrology specialists in 2015. Data were collected using an electronic questionnaire which was estimated as both reliable and valid. The data were analyzed by SPSS software descriptive statistics and analytical statistics. Overall 42 data elements were determined as final set in 4 major categories (patient demographics, medical history, treatment plan and hemodialysis adequacy). The most capabilities required of hemodialysis information system were related to calculate of dialysis adequacy Index (4.80), advice optimal dose of dialysis for each patient (4.63), Easy access to information system without restrictions of time and place (4.61), providing alerts when dialysis adequacy index below the standard (4.55) and Interchange to other information systems in hospitals (4.46) respectively. In design and implementation of information systems focus on MDS and identification IS capabilities based on the users' needs, due to the wide participation users and also the success of the information system. Therefore it is necessary that MDS evaluated carefully with regard to the intended uses of the data. Also information systems based on capabilities the ability to meet the needs of their users.

Systems Security Engineering

DTIC Science & Technology

2010-08-22

practice for information security management ( ISO /IEC 27002 ),” “Information technology — Security techniques — Information security management...systems —Requirements ( ISO /IEC 27002 ),”, “Information technology — Security techniques — Information security risk management ( ISO /IEC 27005).” from...associated practice aids. Perhaps the most germane discovery from this effort was a draft ISO standard on Systems and software engineering, Systems and

Principles and core functions of integrated child health information systems.

PubMed

Hinman, Alan R; Atkinson, Delton; Diehn, Tonya Norvell; Eichwald, John; Heberer, Jennifer; Hoyle, Therese; King, Pam; Kossack, Robert E; Williams, Donna C; Zimmerman, Amy

2004-11-01

Infants undergo a series of preventive and therapeutic health interventions and activities. Typically, each activity includes collection and submission of data to a dedicated information system. Subsequently, health care providers, families, and health programs must query each information system to determine the child's status in a given area. Efforts are underway to integrate information in these separate information systems. This requires specifying the core functions that integrated information systems must perform.

Role of information systems in public health services.

PubMed

Hartshorne, J E; Carstens, I L

1990-07-01

The purpose of this review is to establish a conceptual framework on the role of information systems in public health care. Information is indispensable for effective management and development of health services and therefore considered as an important operational asset or resource. A Health Information System is mainly required to support management and operations at four levels: namely transactional and functional; operational control; management planning and control; and strategic planning. To provide the necessary information needs of users at these levels of management in the health care system, a structured information system coupled with appropriate information technology is required. Adequate and relevant information is needed regarding population characteristics, resources available and expended, output and outcome of health care activities. Additionally information needs to be reliable, accurate, timely, easily accessible and presented in a compact and meaningful form. With a well-planned health information system health authorities would be in a position to provide a quality, cost-effective and efficient health service for as many people as need it, optimal utilisation of resources and to maintain and improve the community's health status.

75 FR 58014 - Pipeline Safety: Information Collection Activity; Request for Comments

Federal Register 2010, 2011, 2012, 2013, 2014

2010-09-23

... detection systems must comply with the standards set out in American Petroleum Institute (API) publication API 1130. API 1130 requires operators to record and retain certain information regarding the operation and testing of CPM systems. Compliance with API 1130, including its recordkeeping requirements...

Impact of Hospital Information Systems on Emergency Patient Processing

PubMed Central

Rusnak, James E.

1981-01-01

The Emergency Department offers the Hospital Information System's designer some unique problems to solve in the operational areas of patient registration, order entry, charge recording, and treatment processing. In a number of instances, Hospital Information Systems implementers have encountered serious difficulties in trying to design system components to support the requirements of the Emergency Services Department's operations. Washington Hospital has developed a very effective system for Emergency Services. The system's features are designed to meet the special requirements of the department and to maximize the use of the data captured by the Hospital Information System. The system supports accurate and timely charging for services. The treatment of the patient has been dramatically improved through the use of a computerized order processing and control. The installed systems resulted in a higher quality of care and cost effective operations.

Archival Information Management System.

DTIC Science & Technology

1995-02-01

management system named Archival Information Management System (AIMS), designed to meet the audit trail requirement for studies completed under the...are to be archived to the extent that future reproducibility and interrogation of results will exist. This report presents a prototype information

Advanced information processing system: Input/output network management software

NASA Technical Reports Server (NTRS)

Nagle, Gail; Alger, Linda; Kemp, Alexander

1988-01-01

The purpose of this document is to provide the software requirements and specifications for the Input/Output Network Management Services for the Advanced Information Processing System. This introduction and overview section is provided to briefly outline the overall architecture and software requirements of the AIPS system before discussing the details of the design requirements and specifications of the AIPS I/O Network Management software. A brief overview of the AIPS architecture followed by a more detailed description of the network architecture.

Two Paths from the Same Place: Task Driven and Human Centered Evolution of a Group Information Surface

NASA Technical Reports Server (NTRS)

Russell, Daniel M.; Trimble, Jay; Wales, Roxana; Clancy, Daniel (Technical Monitor)

2003-01-01

This is the tale of two different implementations of a collaborative information tool, that started from the same design source. The Blueboard, developed at IBM Research, is a tool for groups to use in exchanging information in a lightweight, informal collaborative way. It began as a large display surface for walk-by use in a corporate setting and has evolved in response to task demands and user needs. At NASA, the MERBoard is being designed to support surface operations for the upcoming Mars Exploration Rover Missions. The MERBoard is a tool that was inspired by the Blueboard design, extending this design to support the collaboration requirements for viewing, annotating, linking and distributing information for the science and engineering teams that will operate two rovers on the surface of Mars. The ways in which each group transformed the system reflects not only technical requirements, but also the needs of users in each setting and embedding of the system within the larger socio-technical environment. Lessons about how task requirements, information flow requirements and work practice drive the evolution of a system are illustrated.

Facebook for Scientists: Requirements and Services for Optimizing How Scientific Collaborations Are Established

PubMed Central

Spallek, Heiko; Butler, Brian S; Subramanian, Sushmita; Weiss, Daniel; Poythress, M Louisa; Rattanathikun, Phijarana; Mueller, Gregory

2008-01-01

Background As biomedical research projects become increasingly interdisciplinary and complex, collaboration with appropriate individuals, teams, and institutions becomes ever more crucial to project success. While social networks are extremely important in determining how scientific collaborations are formed, social networking technologies have not yet been studied as a tool to help form scientific collaborations. Many currently emerging expertise locating systems include social networking technologies, but it is unclear whether they make the process of finding collaborators more efficient and effective. Objective This study was conducted to answer the following questions: (1) Which requirements should systems for finding collaborators in biomedical science fulfill? and (2) Which information technology services can address these requirements? Methods The background research phase encompassed a thorough review of the literature, affinity diagramming, contextual inquiry, and semistructured interviews. This phase yielded five themes suggestive of requirements for systems to support the formation of collaborations. In the next phase, the generative phase, we brainstormed and selected design ideas for formal concept validation with end users. Then, three related, well-validated ideas were selected for implementation and evaluation in a prototype. Results Five main themes of systems requirements emerged: (1) beyond expertise, successful collaborations require compatibility with respect to personality, work style, productivity, and many other factors (compatibility); (2) finding appropriate collaborators requires the ability to effectively search in domains other than your own using information that is comprehensive and descriptive (communication); (3) social networks are important for finding potential collaborators, assessing their suitability and compatibility, and establishing contact with them (intermediation); (4) information profiles must be complete, correct, up-to-date, and comprehensive and allow fine-grained control over access to information by different audiences (information quality and access); (5) keeping online profiles up-to-date should require little or no effort and be integrated into the scientist’s existing workflow (motivation). Based on the requirements, 16 design ideas underwent formal validation with end users. Of those, three were chosen to be implemented and evaluated in a system prototype, “Digital|Vita”: maintaining, formatting, and semi-automated updating of biographical information; searching for experts; and building and maintaining the social network and managing document flow. Conclusions In addition to quantitative and factual information about potential collaborators, social connectedness, personal and professional compatibility, and power differentials also influence whether collaborations are formed. Current systems only partially model these requirements. Services in Digital|Vita combine an existing workflow, maintaining and formatting biographical information, with collaboration-searching functions in a novel way. Several barriers to the adoption of systems such as Digital|Vita exist, such as potential adoption asymmetries between junior and senior researchers and the tension between public and private information. Developers and researchers may consider one or more of the services described in this paper for implementation in their own expertise locating systems. PMID:18701421

Next Generation Multimedia Distributed Data Base Systems

NASA Technical Reports Server (NTRS)

Pendleton, Stuart E.

1997-01-01

The paradigm of client/server computing is changing. The model of a server running a monolithic application and supporting clients at the desktop is giving way to a different model that blurs the line between client and server. We are on the verge of plunging into the next generation of computing technology--distributed object-oriented computing. This is not only a change in requirements but a change in opportunities, and requires a new way of thinking for Information System (IS) developers. The information system demands caused by global competition are requiring even more access to decision making tools. Simply, object-oriented technology has been developed to supersede the current design process of information systems which is not capable of handling next generation multimedia.

Tank waste remediation system privatization infrastructure program requirements and document management process guide

DOE Office of Scientific and Technical Information (OSTI.GOV)

ROOT, R.W.

1999-05-18

This guide provides the Tank Waste Remediation System Privatization Infrastructure Program management with processes and requirements to appropriately control information and documents in accordance with the Tank Waste Remediation System Configuration Management Plan (Vann 1998b). This includes documents and information created by the program, as well as non-program generated materials submitted to the project. It provides appropriate approval/control, distribution and filing systems.

48 CFR 1804.470-2 - Policy.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 1804.470-2 Federal Acquisition Regulations System NATIONAL AERONAUTICS AND SPACE ADMINISTRATION GENERAL...) 2810, Security of Information Technology; NASA Procedural Requirements (NPR) 2810, Security of Information Technology; and interim policy updates in the form of NASA Information Technology Requirements...

48 CFR 1804.470-2 - Policy.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 1804.470-2 Federal Acquisition Regulations System NATIONAL AERONAUTICS AND SPACE ADMINISTRATION GENERAL...) 2810, Security of Information Technology; NASA Procedural Requirements (NPR) 2810, Security of Information Technology; and interim policy updates in the form of NASA Information Technology Requirements...

Design for interaction between humans and intelligent systems during real-time fault management

NASA Technical Reports Server (NTRS)

Malin, Jane T.; Schreckenghost, Debra L.; Thronesbery, Carroll G.

1992-01-01

Initial results are reported to provide guidance and assistance for designers of intelligent systems and their human interfaces. The objective is to achieve more effective human-computer interaction (HCI) for real time fault management support systems. Studies of the development of intelligent fault management systems within NASA have resulted in a new perspective of the user. If the user is viewed as one of the subsystems in a heterogeneous, distributed system, system design becomes the design of a flexible architecture for accomplishing system tasks with both human and computer agents. HCI requirements and design should be distinguished from user interface (displays and controls) requirements and design. Effective HCI design for multi-agent systems requires explicit identification of activities and information that support coordination and communication between agents. The effects are characterized of HCI design on overall system design and approaches are identified to addressing HCI requirements in system design. The results include definition of (1) guidance based on information level requirements analysis of HCI, (2) high level requirements for a design methodology that integrates the HCI perspective into system design, and (3) requirements for embedding HCI design tools into intelligent system development environments.

Using case-mix information in strategic hospital marketing. Deriving market research from patient data.

PubMed

Little, A

1992-01-01

Hospital survival requires adaptation, adaptation requires understanding, and understanding requires information. These are the basic equations behind hospital strategic marketing, and one of the answers may lie in hospitals' own patient-data systems. Marketers' and administrators' enlightened application of case-mix information could become one more hospital survival tool.

A Transparent Translation from Legacy System Model into Common Information Model: Preprint

DOE Office of Scientific and Technical Information (OSTI.GOV)

Ding, Fei; Simpson, Jeffrey; Zhang, Yingchen

Advance in smart grid is forcing utilities towards better monitoring, control and analysis of distribution systems, and requires extensive cyber-based intelligent systems and applications to realize various functionalities. The ability of systems, or components within systems, to interact and exchange services or information with each other is the key to the success of smart grid technologies, and it requires efficient information exchanging and data sharing infrastructure. The Common Information Model (CIM) is a standard that allows different applications to exchange information about an electrical system, and it has become a widely accepted solution for information exchange among different platforms andmore » applications. However, most existing legacy systems are not developed using CIM, but using their own languages. Integrating such legacy systems is a challenge for utilities, and the appropriate utilization of the integrated legacy systems is even more intricate. Thus, this paper has developed an approach and open-source tool in order to translate legacy system models into CIM format. The developed tool is tested for a commercial distribution management system and simulation results have proved its effectiveness.« less

48 CFR 215.403-3 - Requiring information other than cost or pricing data.

Code of Federal Regulations, 2010 CFR

2010-10-01

... other than cost or pricing data. 215.403-3 Section 215.403-3 Federal Acquisition Regulations System DEFENSE ACQUISITION REGULATIONS SYSTEM, DEPARTMENT OF DEFENSE CONTRACTING METHODS AND CONTRACT TYPES CONTRACTING BY NEGOTIATION Contract Pricing 215.403-3 Requiring information other than cost or pricing data...

48 CFR 215.403-3 - Requiring information other than cost or pricing data.

Code of Federal Regulations, 2012 CFR

2012-10-01

... other than cost or pricing data. 215.403-3 Section 215.403-3 Federal Acquisition Regulations System DEFENSE ACQUISITION REGULATIONS SYSTEM, DEPARTMENT OF DEFENSE CONTRACTING METHODS AND CONTRACT TYPES CONTRACTING BY NEGOTIATION Contract Pricing 215.403-3 Requiring information other than cost or pricing data...

48 CFR 215.403-3 - Requiring information other than cost or pricing data.

Code of Federal Regulations, 2011 CFR

2011-10-01

... other than cost or pricing data. 215.403-3 Section 215.403-3 Federal Acquisition Regulations System DEFENSE ACQUISITION REGULATIONS SYSTEM, DEPARTMENT OF DEFENSE CONTRACTING METHODS AND CONTRACT TYPES CONTRACTING BY NEGOTIATION Contract Pricing 215.403-3 Requiring information other than cost or pricing data...

2 CFR 25.215 - Requirements for agency information systems.

Code of Federal Regulations, 2012 CFR

2012-01-01

... 2 Grants and Agreements 1 2012-01-01 2012-01-01 false Requirements for agency information systems. 25.215 Section 25.215 Grants and Agreements Office of Management and Budget Guidance for Grants and Agreements OFFICE OF MANAGEMENT AND BUDGET GOVERNMENTWIDE GUIDANCE FOR GRANTS AND AGREEMENTS PRE-AWARD...

2 CFR 25.215 - Requirements for agency information systems.

Code of Federal Regulations, 2013 CFR

2013-01-01

... 2 Grants and Agreements 1 2013-01-01 2013-01-01 false Requirements for agency information systems. 25.215 Section 25.215 Grants and Agreements Office of Management and Budget Guidance for Grants and Agreements OFFICE OF MANAGEMENT AND BUDGET GOVERNMENTWIDE GUIDANCE FOR GRANTS AND AGREEMENTS PRE-AWARD...

2 CFR 25.215 - Requirements for agency information systems.

Code of Federal Regulations, 2014 CFR

2014-01-01

... 2 Grants and Agreements 1 2014-01-01 2014-01-01 false Requirements for agency information systems. 25.215 Section 25.215 Grants and Agreements Office of Management and Budget Guidance for Grants and Agreements OFFICE OF MANAGEMENT AND BUDGET GOVERNMENTWIDE GUIDANCE FOR GRANTS AND AGREEMENTS Reserved...

2 CFR 25.215 - Requirements for agency information systems.

Code of Federal Regulations, 2011 CFR

2011-01-01

... 2 Grants and Agreements 1 2011-01-01 2011-01-01 false Requirements for agency information systems. 25.215 Section 25.215 Grants and Agreements Office of Management and Budget Guidance for Grants and Agreements OFFICE OF MANAGEMENT AND BUDGET GOVERNMENTWIDE GUIDANCE FOR GRANTS AND AGREEMENTS Pre-award...

48 CFR 1852.203-71 - Requirement to inform employees of whistleblower rights.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 48 Federal Acquisition Regulations System 6 2014-10-01 2014-10-01 false Requirement to inform employees of whistleblower rights. 1852.203-71 Section 1852.203-71 Federal Acquisition Regulations System... native language of the workforce, of contractor employee whistleblower rights and protections under 10 U...

Technical parameters for specifying imagery requirements

NASA Technical Reports Server (NTRS)

Coan, Paul P.; Dunnette, Sheri J.

1994-01-01

Providing visual information acquired from remote events to various operators, researchers, and practitioners has become progressively more important as the application of special skills in alien or hazardous situations increases. To provide an understanding of the technical parameters required to specify imagery, we have identified, defined, and discussed seven salient characteristics of images: spatial resolution, linearity, luminance resolution, spectral discrimination, temporal discrimination, edge definition, and signal-to-noise ratio. We then describe a generalizing imaging system and identified how various parts of the system affect the image data. To emphasize the different applications of imagery, we have constrasted the common television system with the significant parameters of a televisual imaging system for technical applications. Finally, we have established a method by which the required visual information can be specified by describing certain technical parameters which are directly related to the information content of the imagery. This method requires the user to complete a form listing all pertinent data requirements for the imagery.

Software Documentation for the Bartlesville Public Schools: Part One. The Bartlesville System Total Guidance Information Support System.

ERIC Educational Resources Information Center

Roberts, Tommy L.; And Others

The Total Guidance Information Support System (TGISS), is an information storage and retrieval system for counselors. The total TGISS, including hardware and software, extends the counselor's capabilities by providing ready access to student information under secure conditions. The hardware required includes: (1) IBM 360/50 central processing…

Responses to Information Systems Graduate Preparation and Job Needs: Implications for Higher Education

ERIC Educational Resources Information Center

Simon, DeShea; Jackson, Kanata

2015-01-01

This study examined the perspectives on academic preparation and job skill needs of Information Systems program graduates from an Eastern state in the US. A historical review of the literature surrounding information systems skill requirements was conducted for this study, to provide an understanding of the changes in information systems over the…

Aviation Weather Information Communications Study (AWIN). Phase 1 and 2

NASA Technical Reports Server (NTRS)

Ball, J. W.; Herron, R. G.; Nozawa, E. T.; Thomas, E. A.; Witchey, R. D.

2000-01-01

This two part study examines the communication requirements to provide weather information in the cockpit as well as public and private communication systems available to address the requirements. Ongoing research projects combined with user needs for weather related information are used to identify and describe potential weather products that address decision support in three time frames: Far-Term Strategic, Near-Term Strategic and Tactical. Data requirements of these future products are identified and quantified. Communications systems and technologies available in the public as well as private sector are analyzed to identify potential solutions. Recommendations for further research identify cost, performance, and safety benefits to justify the investment. The study concludes that not all weather information has the same level of urgency to safety-of-flight and some information is more critical to one category of flight than another. Specific weather products need to be matched with communication systems with appropriate levels of reliability to support the criticality of the information. Available bandwidth for highly critical information should be preserved and dedicated to safety. Meanwhile, systems designed for in-flight-entertainment and other passenger/crew services could be used to support less critical information that is used only for planning and economic decision support.

Advanced information processing system: Local system services

NASA Technical Reports Server (NTRS)

Burkhardt, Laura; Alger, Linda; Whittredge, Roy; Stasiowski, Peter

1989-01-01

The Advanced Information Processing System (AIPS) is a multi-computer architecture composed of hardware and software building blocks that can be configured to meet a broad range of application requirements. The hardware building blocks are fault-tolerant, general-purpose computers, fault-and damage-tolerant networks (both computer and input/output), and interfaces between the networks and the computers. The software building blocks are the major software functions: local system services, input/output, system services, inter-computer system services, and the system manager. The foundation of the local system services is an operating system with the functions required for a traditional real-time multi-tasking computer, such as task scheduling, inter-task communication, memory management, interrupt handling, and time maintenance. Resting on this foundation are the redundancy management functions necessary in a redundant computer and the status reporting functions required for an operator interface. The functional requirements, functional design and detailed specifications for all the local system services are documented.

An informal paper on large-scale dynamic systems

NASA Technical Reports Server (NTRS)

Ho, Y. C.

1975-01-01

Large scale systems are defined as systems requiring more than one decision maker to control the system. Decentralized control and decomposition are discussed for large scale dynamic systems. Information and many-person decision problems are analyzed.

Health information management: an introduction to disease classification and coding.

PubMed

Mony, Prem Kumar; Nagaraj, C

2007-01-01

Morbidity and mortality data constitute an important component of a health information system and their coding enables uniform data collation and analysis as well as meaningful comparisons between regions or countries. Strengthening the recording and reporting systems for health monitoring is a basic requirement for an efficient health information management system. Increased advocacy for and awareness of a uniform coding system together with adequate capacity building of physicians, coders and other allied health and information technology personnel would pave the way for a valid and reliable health information management system in India. The core requirements for the implementation of disease coding are: (i) support from national/institutional health administrators, (ii) widespread availability of the ICD-10 material for morbidity and mortality coding; (iii) enhanced human and financial resources; and (iv) optimal use of informatics. We describe the methodology of a disease classification and codification system as also its applications for developing and maintaining an effective health information management system for India.

Extracting Social Information from Chemosensory Cues: Consideration of Several Scenarios and Their Functional Implications

PubMed Central

Ben-Shaul, Yoram

2015-01-01

Across all sensory modalities, stimuli can vary along multiple dimensions. Efficient extraction of information requires sensitivity to those stimulus dimensions that provide behaviorally relevant information. To derive social information from chemosensory cues, sensory systems must embed information about the relationships between behaviorally relevant traits of individuals and the distributions of the chemical cues that are informative about these traits. In simple cases, the mere presence of one particular compound is sufficient to guide appropriate behavior. However, more generally, chemosensory information is conveyed via relative levels of multiple chemical cues, in non-trivial ways. The computations and networks needed to derive information from multi-molecule stimuli are distinct from those required by single molecule cues. Our current knowledge about how socially relevant information is encoded by chemical blends, and how it is extracted by chemosensory systems is very limited. This manuscript explores several scenarios and the neuronal computations required to identify them. PMID:26635515

On-board Attitude Determination System (OADS). [for advanced spacecraft missions

NASA Technical Reports Server (NTRS)

Carney, P.; Milillo, M.; Tate, V.; Wilson, J.; Yong, K.

1978-01-01

The requirements, capabilities and system design for an on-board attitude determination system (OADS) to be flown on advanced spacecraft missions were determined. Based upon the OADS requirements and system performance evaluation, a preliminary on-board attitude determination system is proposed. The proposed OADS system consists of one NASA Standard IRU (DRIRU-2) as the primary attitude determination sensor, two improved NASA Standard star tracker (SST) for periodic update of attitude information, a GPS receiver to provide on-board space vehicle position and velocity vector information, and a multiple microcomputer system for data processing and attitude determination functions. The functional block diagram of the proposed OADS system is shown. The computational requirements are evaluated based upon this proposed OADS system.

Systems Analysis and Design: Know Your Audience

ERIC Educational Resources Information Center

Reinicke, Bryan A.

2012-01-01

Systems analysis and design (SAD) classes are required in both Information Systems and Accounting programs, but these audiences have very different needs for these skills. This article will review the requirements for SAD within each of these disciplines and compare and contrast the different requirements for teaching systems analysis and design…

Measuring Integrated Information from the Decoding Perspective

PubMed Central

Oizumi, Masafumi; Amari, Shun-ichi; Yanagawa, Toru; Fujii, Naotaka; Tsuchiya, Naotsugu

2016-01-01

Accumulating evidence indicates that the capacity to integrate information in the brain is a prerequisite for consciousness. Integrated Information Theory (IIT) of consciousness provides a mathematical approach to quantifying the information integrated in a system, called integrated information, Φ. Integrated information is defined theoretically as the amount of information a system generates as a whole, above and beyond the amount of information its parts independently generate. IIT predicts that the amount of integrated information in the brain should reflect levels of consciousness. Empirical evaluation of this theory requires computing integrated information from neural data acquired from experiments, although difficulties with using the original measure Φ precludes such computations. Although some practical measures have been previously proposed, we found that these measures fail to satisfy the theoretical requirements as a measure of integrated information. Measures of integrated information should satisfy the lower and upper bounds as follows: The lower bound of integrated information should be 0 and is equal to 0 when the system does not generate information (no information) or when the system comprises independent parts (no integration). The upper bound of integrated information is the amount of information generated by the whole system. Here we derive the novel practical measure Φ* by introducing a concept of mismatched decoding developed from information theory. We show that Φ* is properly bounded from below and above, as required, as a measure of integrated information. We derive the analytical expression of Φ* under the Gaussian assumption, which makes it readily applicable to experimental data. Our novel measure Φ* can generally be used as a measure of integrated information in research on consciousness, and also as a tool for network analysis on diverse areas of biology. PMID:26796119

42 CFR 495.302 - Definitions.

Code of Federal Regulations, 2010 CFR

2010-10-01

... management information system (MMIS) means a mechanized claims processing and information retrieval system—referred to as Medicaid Management Information Systems (MMIS)—that meets specified requirements and that... include claims processing and retrieval of utilization and management information necessary for program...

Project #8, Task 3 - Travel Information Services (TIS), Requirements Analysis Report

DOT National Transportation Integrated Search

1995-03-24

THE L-95 CORRIDOR COALITION'S TRAVELER INFORMATION SERVICES (TIS) PROJECT IS INTENDED TO IMPLEMENT AN ADVANCED TRAVELER INFORMATION SYSTEM TAILORED TO THE UNIQUE NEEDS OF THE NORTHEAST CORRIDOR. THE SYSTEM WILL ACQUIRE AND DISSEMINATE INFORMATION ON ...

Public Service Communications Satellite User Requirements Workshop

NASA Technical Reports Server (NTRS)

Wolff, E. A.

1977-01-01

Information on user requirements for public service communications was acquired to provide the basis of a study to determine the optimum satellite system to satisfy user requirements. The concept for such a system is described: Topics discussed included requirements for data and message services, elementary and secondary education, extension and continuing education, environmental communications, library services, medical education, medical services, public broadcasting, public safety, religious applications, state and local communications, and voluntary services. Information was also obtained on procedures to follow to make the transfer to commercial services.

Medical Information Management System (MIMS): A generalized interactive information system

NASA Technical Reports Server (NTRS)

Alterescu, S.; Friedman, C. A.; Hipkins, K. R.

1975-01-01

An interactive information system is described. It is a general purpose, free format system which offers immediate assistance where manipulation of large data bases is required. The medical area is a prime area of application. Examples of the system's operation, commentary on the examples, and a complete listing of the system program are included.

39 CFR 501.7 - Postage Evidencing System requirements.

Code of Federal Regulations, 2014 CFR

2014-07-01

... Information-Based Indicia and Security Architecture for Open IBI Postage Evidencing Systems or Performance Criteria for Information-Based Indicia and Security Architecture for Closed IBI Postage Metering Systems...

Nonmaterialized Relations and the Support of Information Retrieval Applications by Relational Database Systems.

ERIC Educational Resources Information Center

Lynch, Clifford A.

1991-01-01

Describes several aspects of the problem of supporting information retrieval system query requirements in the relational database management system (RDBMS) environment and proposes an extension to query processing called nonmaterialized relations. User interactions with information retrieval systems are discussed, and nonmaterialized relations are…

48 CFR 239.7102-3 - Information assurance contractor training and certification.

Code of Federal Regulations, 2011 CFR

2011-10-01

... ACQUISITION OF INFORMATION TECHNOLOGY Security and Privacy for Computer Systems 239.7102-3 Information..., certification maintenance, and continuing education or sustainment training required for the information... 48 Federal Acquisition Regulations System 3 2011-10-01 2011-10-01 false Information assurance...

48 CFR 239.7102-3 - Information assurance contractor training and certification.

Code of Federal Regulations, 2014 CFR

2014-10-01

... ACQUISITION OF INFORMATION TECHNOLOGY Security and Privacy for Computer Systems 239.7102-3 Information..., certification maintenance, and continuing education or sustainment training required for the information... 48 Federal Acquisition Regulations System 3 2014-10-01 2014-10-01 false Information assurance...

48 CFR 239.7102-3 - Information assurance contractor training and certification.

Code of Federal Regulations, 2012 CFR

2012-10-01

... ACQUISITION OF INFORMATION TECHNOLOGY Security and Privacy for Computer Systems 239.7102-3 Information..., certification maintenance, and continuing education or sustainment training required for the information... 48 Federal Acquisition Regulations System 3 2012-10-01 2012-10-01 false Information assurance...

48 CFR 239.7102-3 - Information assurance contractor training and certification.

Code of Federal Regulations, 2013 CFR

2013-10-01

... ACQUISITION OF INFORMATION TECHNOLOGY Security and Privacy for Computer Systems 239.7102-3 Information..., certification maintenance, and continuing education or sustainment training required for the information... 48 Federal Acquisition Regulations System 3 2013-10-01 2013-10-01 false Information assurance...

48 CFR 239.7102-3 - Information assurance contractor training and certification.

Code of Federal Regulations, 2010 CFR

2010-10-01

... ACQUISITION OF INFORMATION TECHNOLOGY Security and Privacy for Computer Systems 239.7102-3 Information..., certification maintenance, and continuing education or sustainment training required for the information... 48 Federal Acquisition Regulations System 3 2010-10-01 2010-10-01 false Information assurance...

Requisite Skills and Knowledge for Entry-Level IT Auditors

ERIC Educational Resources Information Center

Merhout, Jeffrey W.; Buchman, Sarah E.

2007-01-01

Information technology auditing has become a career in high demand in recent years due to factors such as increasing compliance requirements with regards to information technology governance. Nonetheless, many information technology, management information systems, and accounting information systems educators may not have paid significant…

NICA project management information system

NASA Astrophysics Data System (ADS)

Bashashin, M. V.; Kekelidze, D. V.; Kostromin, S. A.; Korenkov, V. V.; Kuniaev, S. V.; Morozov, V. V.; Potrebenikov, Yu. K.; Trubnikov, G. V.; Philippov, A. V.

2016-09-01

The science projects growth, changing of the efficiency criteria during the project implementation require not only increasing of the management specialization level but also pose the problem of selecting the effective planning methods, monitoring of deadlines and interaction of participants involved in research projects. This paper is devoted to choosing the project management information system for the new heavy-ion collider NICA (Nuclotron based Ion Collider fAcility). We formulate the requirements for the project management information system with taking into account the specifics of the Joint Institute for Nuclear Research (JINR, Dubna, Russia) as an international intergovernmental research organization, which is developed on the basis of a flexible and effective information system for the NICA project management.

Office of university affairs management information system: Users guide and documentation

NASA Technical Reports Server (NTRS)

Distin, J.; Goodwin, D.; Greene, W. A.

1977-01-01

Data on the NASA-University relationship are reported that encompass research in over 600 schools through several thousand grants and contracts. This user-driven system is capable of producing a variety of cyclical and query-type reports describing the total NASA-University profile. The capabilities, designed as part of the system, require a minimum of user maintenance in order to ensure system efficiency and data validity to meet the recurrent Statutory and Executive Branch information requirements as well as ad hoc inquiries from NASA general management, Congress, other Federal agencies, private sector organizations, universities and individuals. The data base contains information on each university, the individual projects and the financial details, current and historic, on all contracts and grants. Complete details are given on the system from its unique design features to the actual steps required for daily operation.

39 CFR 501.7 - Postage Evidencing System requirements.

Code of Federal Regulations, 2013 CFR

2013-07-01

... Performance Criteria for Information-Based Indicia and Security Architecture for Open IBI Postage Evidencing Systems or Performance Criteria for Information-Based Indicia and Security Architecture for Closed IBI... Information-Based Indicia and Security Architecture for Open IBI Postage Evidencing Systems or Performance...

39 CFR 501.7 - Postage Evidencing System requirements.

Code of Federal Regulations, 2012 CFR

2012-07-01

... Performance Criteria for Information-Based Indicia and Security Architecture for Open IBI Postage Evidencing Systems or Performance Criteria for Information-Based Indicia and Security Architecture for Closed IBI... Information-Based Indicia and Security Architecture for Open IBI Postage Evidencing Systems or Performance...

Pilot Task Profiles, Human Factors, And Image Realism

NASA Astrophysics Data System (ADS)

McCormick, Dennis

1982-06-01

Computer Image Generation (CIG) visual systems provide real time scenes for state-of-the-art flight training simulators. The visual system reauires a greater understanding of training tasks, human factors, and the concept of image realism to produce an effective and efficient training scene than is required by other types of visual systems. Image realism must be defined in terms of pilot visual information reauirements. Human factors analysis of training and perception is necessary to determine the pilot's information requirements. System analysis then determines how the CIG and display device can best provide essential information to the pilot. This analysis procedure ensures optimum training effectiveness and system performance.

Earth Sciences Requirements for the Information Sciences Experiment System

NASA Technical Reports Server (NTRS)

Bowker, David E. (Editor); Katzberg, Steve J. (Editor); Wilson, R. Gale (Editor)

1990-01-01

The purpose of the workshop was to further explore and define the earth sciences requirements for the Information Sciences Experiment System (ISES), a proposed onboard data processor with real-time communications capability intended to support the Earth Observing System (Eos). A review of representative Eos instrument types is given and a preliminary set of real-time data needs has been established. An executive summary is included.

Intelligent Information Fusion in the Aviation Domain: A Semantic-Web based Approach

NASA Technical Reports Server (NTRS)

Ashish, Naveen; Goforth, Andre

2005-01-01

Information fusion from multiple sources is a critical requirement for System Wide Information Management in the National Airspace (NAS). NASA and the FAA envision creating an "integrated pool" of information originally coming from different sources, which users, intelligent agents and NAS decision support tools can tap into. In this paper we present the results of our initial investigations into the requirements and prototype development of such an integrated information pool for the NAS. We have attempted to ascertain key requirements for such an integrated pool based on a survey of DSS tools that will benefit from this integrated pool. We then advocate key technologies from computer science research areas such as the semantic web, information integration, and intelligent agents that we believe are well suited to achieving the envisioned system wide information management capabilities.

Security and privacy of EHR systems--ethical, social and legal requirements.

PubMed

Kluge, Eike-Henner W

2003-01-01

This paper addresses social, ethical and legal concerns about security and privacy that arise in the development of international interoperable health information systems. The paper deals with these concerns under four rubrics: the ethical status of electronic health records, the social and legal embedding of interoperable health information systems, the overall information-requirements healthcare as such, and the role of health information professionals as facilitators. It argues that the concerns that arise can be met if the development of interoperability protocols is guided by the seven basic principles of information ethics that have been enunciated in the IMIA Code of Ethics for Health Information Professionals and that are central to the ethical treatment of electronic health records.

76 FR 3680 - Proposed Collection; Comment Request

Federal Register 2010, 2011, 2012, 2013, 2014

2011-01-20

... requirements to provide customers with account information (approximately 683,969 hours) and requirements to update customer account information (approximately 777,436 hours). In addition, Rule 17a-3 contains... customers with account information, and costs for equipment and systems development. The Commission...

A prototype expert/information system for examining environmental risks of KSC activities

NASA Technical Reports Server (NTRS)

Engel, Bernard A.

1993-01-01

Protection of the environment and natural resources at the Kennedy Space Center (KSC) is of great concern. An expert/information system to replace the paper-based KSC Environmental Checklist was developed. The computer-based system requests information only as a required and supplies assistance as needed. The most comprehensive portion of the system provides information about endangered species habitat at KSC. This module uses geographic information system (GIS) data and tools, expert rules, color graphics, computer-based video, and hypertext to provide information.

10 CFR 1017.28 - Processing on Automated Information Systems (AIS).

Code of Federal Regulations, 2010 CFR

2010-01-01

... 10 Energy 4 2010-01-01 2010-01-01 false Processing on Automated Information Systems (AIS). 1017.28... UNCLASSIFIED CONTROLLED NUCLEAR INFORMATION Physical Protection Requirements § 1017.28 Processing on Automated Information Systems (AIS). UCNI may be processed or produced on any AIS that complies with the guidance in OMB...

42 CFR 431.806 - State plan requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... processing assessment system. Except in a State that has an approved Medicaid Management Information System... Medicaid quality control claims processing assessment system that meets the requirements of §§ 431.830...

76 FR 34886 - General Services Administration Acquisition Regulation; Implementation of Information Technology...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-06-15

... Acquisition Regulation; Implementation of Information Technology Security Provision AGENCY: Office of... information technology (IT) supplies, services and systems with security requirements. DATES: Effective Date... effective date that include information technology (IT) supplies, services and systems with security...

An integrated approach to system design, reliability, and diagnosis

NASA Technical Reports Server (NTRS)

Patterson-Hine, F. A.; Iverson, David L.

1990-01-01

The requirement for ultradependability of computer systems in future avionics and space applications necessitates a top-down, integrated systems ingeneering approach for design, implementation, testing, and operation. The functional analyses of hardware and software systems must be combined by models that are flexible enough to represent their interactions and behavior. The information contained in these models must be accessible throughout all phases of the system life cycle in order to maintain consistency and accuracy in design and operational decisions. One approach being taken by researchers at Ames Research Center is the creation of an object-oriented environment that integrates information about system components required in the reliability evaluation with behavioral information useful for diagnostic algorithms.

Analysis and preliminary design of Kunming land use and planning management information system

NASA Astrophysics Data System (ADS)

Li, Li; Chen, Zhenjie

2007-06-01

This article analyzes Kunming land use planning and management information system from the system building objectives and system building requirements aspects, nails down the system's users, functional requirements and construction requirements. On these bases, the three-tier system architecture based on C/S and B/S is defined: the user interface layer, the business logic layer and the data services layer. According to requirements for the construction of land use planning and management information database derived from standards of the Ministry of Land and Resources and the construction program of the Golden Land Project, this paper divides system databases into planning document database, planning implementation database, working map database and system maintenance database. In the design of the system interface, this paper uses various methods and data formats for data transmission and sharing between upper and lower levels. According to the system analysis results, main modules of the system are designed as follows: planning data management, the planning and annual plan preparation and control function, day-to-day planning management, planning revision management, decision-making support, thematic inquiry statistics, planning public participation and so on; besides that, the system realization technologies are discussed from the system operation mode, development platform and other aspects.

40 CFR 270.21 - Specific part B information requirements for landfills.

Code of Federal Regulations, 2010 CFR

2010-07-01

... surface water at any future time; (ii) The double liner and leak (leachate) detection, collection, and... exemption from the requirements for double liners and a leak detection, collection, and removal system or... information; (iii) If the leak detection system is located in a saturated zone, submit detailed plans and an...

Empowering Freshmen with Technology Skills: Wireless Routers

ERIC Educational Resources Information Center

VanderClock, William

2015-01-01

Most freshmen taking required, introductory information systems courses do not understand why they are required to take such courses and can't imagine that they will learn anything they don't already know. This paper presents an exercise that will excite and enthuse students about their computers and Information Systems in general. Every freshman…

Using simulation and virtual machines to identify information assurance requirements

NASA Astrophysics Data System (ADS)

Banks, Sheila B.; Stytz, Martin R.

2010-04-01

The US military is changing its philosophy, approach, and technologies used for warfare. In the process of achieving this vision for high-speed, highly mobile warfare, there are a number of issues that must be addressed and solved; issues that are not addressed by commercial systems because Department of Defense (DoD) Information Technology (IT) systems operate in an environment different from the commercial world. The differences arise from the differences in the scope and skill used in attacks upon DoD systems, the interdependencies between DoD software systems used for network centric warfare (NCW), and the need to rely upon commercial software components in virtually every DoD system. As a result, while NCW promises more effective and efficient means for employing DoD resources, it also increases the vulnerability and allure of DoD systems to cyber attack. A further challenge arises due to the rapid changes in software and information assurance (IA) requirements and technologies over the course of a project. Therefore, the four challenges that must be addressed are determining how to specify the information assurance requirements for a DoD system, minimizing changes to commercial software, incorporation of new system and IA requirements in a timely manner with minimal impact, and insuring that the interdependencies between systems do not result in cyber attack vulnerabilities. In this paper, we address all four issues. In addition to addressing the four challenges outlined above, the interdependencies and interconnections between systems indicate that the IA requirements for a system must consider two important facets of a system's IA defensive capabilities. The facets are the types of IA attacks that the system must repel and the ability of a system to insure that any IA attack that penetrates the system is contained within the system and does not spread. The IA requirements should be derived from threat assessments for the system as well as for the need to address the four requirements challenges outlined above. To address these issues, we developed a system architecture and acquisition approach designed to separate the system's IA capabilities requirements and development from the other system capability requirements; thereby, allowing the IA capabilities to be developed rapidly and assessed separately from the other system capabilities. Simulation environments and technologies allow us to test and evaluate solutions to the issues while also insuring that the system being tested and the solution are not exposed to real-world threats.

Information Infrastructure, Information Environments, and Long-Term Collaboration

NASA Astrophysics Data System (ADS)

Baker, K. S.; Pennington, D. D.

2009-12-01

Information infrastructure that supports collaborative science is a complex system of people, organizational arrangements, and tools that require co-management. Contemporary studies are exploring how to establish and characterize effective collaborative information environments. Collaboration depends on the flow of information across the human and technical system components through mechanisms that create linkages, both conceptual and technical. This transcends the need for requirements solicitation and usability studies, highlighting synergistic interactions between humans and technology that can lead to emergence of group level cognitive properties. We consider the ramifications of placing priority on establishing new metaphors and new types of learning environments located near-to-data-origin for the field sciences. In addition to changes in terms of participant engagement, there are implications in terms of innovative contributions to the design of information systems and data exchange. While data integration occurs in the minds of individual participants, it may be facilitated by collaborative thinking and community infrastructure. Existing learning frameworks - from Maslow’s hierarchy of needs to organizational learning - require modification and extension if effective approaches to decentralized information management and systems design are to emerge. Case studies relating to data integration include ecological community projects: development of cross-disciplinary conceptual maps and of a community unit registry.

Information Requirements for Supervisory Air Traffic Controllers in Support of a Wake Vortex Departure System

NASA Technical Reports Server (NTRS)

Lohr, Gary W.; Williams, Daniel M.; Trujillo, Anna C.

2008-01-01

Closely Space Parallel Runway (CSPR) configurations are capacity limited for departures due to the requirement to apply wake vortex separation standards from traffic departing on the adjacent parallel runway. To mitigate the effects of this constraint, a concept focusing on wind dependent departure operations has been developed, known as the Wake Turbulence Mitigation for Departures (WTMD). This concept takes advantage of the fact that crosswinds of sufficient velocity blow wakes generated by aircraft departing from the downwind runway away from the upwind runway. Consequently, under certain conditions, wake separations on the upwind runway would not be required based on wakes generated by aircraft on the downwind runway, as is currently the case. It follows that information requirements, and sources for this information, would need to be determined for airport traffic control tower (ATCT) supervisory personnel who would be charged with decisions regarding use of the procedure. To determine the information requirements, data were collected from ATCT supervisors and controller-in-charge qualified individuals at Lambert-St. Louis International Airport (STL) and George Bush Houston Intercontinental Airport (IAH). STL and IAH were chosen as data collection sites based on the implementation of a WTMD prototype system, operating in shadow mode, at these locations. The 17 total subjects (STL: 5, IAH: 12) represented a broad-base of air traffic experience. Results indicated that the following information was required to support the conduct of WTMD operations: current and forecast weather information, current and forecast traffic demand and traffic flow restrictions, and WTMD System status information and alerting. Subjects further indicated that the requisite information is currently available in the tower cab with the exception of the WTMD status and alerting. Subjects were given a demonstration of a display supporting the prototype systems and unanimously stated that the WTMD status information they felt important was represented. Overwhelmingly, subjects felt that approving, monitoring and terminating the WTMD procedure could be integrated into their supervisory workload.

Implementing and integrating a clinically driven electronic medical record for radiation oncology in a large medical enterprise.

PubMed

Kirkpatrick, John P; Light, Kim L; Walker, Robyn M; Georgas, Debra L; Antoine, Phillip A; Clough, Robert W; Cozart, Heidi B; Yin, Fang-Fang; Yoo, Sua; Willett, Christopher G

2013-01-01

While our department is heavily invested in computer-based treatment planning, we historically relied on paper-based charts for management of Radiation Oncology patients. In early 2009, we initiated the process of conversion to an electronic medical record (EMR) eliminating the need for paper charts. Key goals included the ability to readily access information wherever and whenever needed, without compromising safety, treatment quality, confidentiality, or productivity. In February, 2009, we formed a multi-disciplinary team of Radiation Oncology physicians, nurses, therapists, administrators, physicists/dosimetrists, and information technology (IT) specialists, along with staff from the Duke Health System IT department. The team identified all existing processes and associated information/reports, established the framework for the EMR system and generated, tested and implemented specific EMR processes. Two broad classes of information were identified: information which must be readily accessed by anyone in the health system versus that used solely within the Radiation Oncology department. Examples of the former are consultation reports, weekly treatment check notes, and treatment summaries; the latter includes treatment plans, daily therapy records, and quality assurance reports. To manage the former, we utilized the enterprise-wide system, which required an intensive effort to design and implement procedures to export information from Radiation Oncology into that system. To manage "Radiation Oncology" data, we used our existing system (ARIA, Varian Medical Systems.) The ability to access both systems simultaneously from a single workstation (WS) was essential, requiring new WS and modified software. As of January, 2010, all new treatments were managed solely with an EMR. We find that an EMR makes information more widely accessible and does not compromise patient safety, treatment quality, or confidentiality. However, compared to paper charts, time required by clinicians to access/enter patient information has substantially increased. While productivity is improving with experience, substantial growth will require better integration of the system components, decreased access times, and improved user interfaces. $127K was spent on new hardware and software; elimination of paper yields projected savings of $21K/year. One year after conversion to an EMR, more than 90% of department staff favored the EMR over the previous paper charts. Successful implementation of a Radiation Oncology EMR required not only the effort and commitment of all functions of the department, but support from senior health system management, corporate IT, and vendors. Realization of the full benefits of an EMR will require experience, faster/better integrated software, and continual improvement in underlying clinical processes.

Modeling the dynamics of multipartite quantum systems created departing from two-level systems using general local and non-local interactions

NASA Astrophysics Data System (ADS)

Delgado, Francisco

2017-12-01

Quantum information is an emergent area merging physics, mathematics, computer science and engineering. To reach its technological goals, it is requiring adequate approaches to understand how to combine physical restrictions, computational approaches and technological requirements to get functional universal quantum information processing. This work presents the modeling and the analysis of certain general type of Hamiltonian representing several physical systems used in quantum information and establishing a dynamics reduction in a natural grammar for bipartite processing based on entangled states.

Requirements Engineering for inter-organizational health information systems with functions for spatial analyses: modeling a WHO safe community applying Use Case Maps.

PubMed

Olvingson, C; Hallberg, N; Timpka, T; Lindqvist, K

2002-01-01

To evaluate Use Case Maps (UCMs) as a technique for Requirements Engineering (RE) in the development of information systems with functions for spatial analyses in inter-organizational public health settings. In this study, Participatory Action Research (PAR) is used to explore the UCM notation for requirements elicitation and to gather the opinions of the users. The Delphi technique is used to reach consensus in the construction of UCMs. The results show that UCMs can provide a visualization of the system's functionality and in combination with PAR provide a sound basis for gathering requirements in inter-organizational settings. UCMs were found to represent a suitable level for describing the organization and the dynamic flux of information including spatial resolution to all stakeholders. Moreover, by using PAR, the voices of the users and their tacit knowledge is intercepted. Further, UCMs are found useful in generating intuitive requirements by the creation of use cases. With UCMs and PAR it is possible to study the effects of design changes in the general information display and the spatial resolution in the same context. Both requirements on the information system in general and the functions for spatial analyses are possible to elicit when identifying the different responsibilities and the demands on spatial resolution associated to the actions of each administrative unit. However, the development process of UCM is not well documented and needs further investigation and formulation of guidelines.

A cloud-based home health care information sharing system to connect patients with home healthcare staff -A case report of a study in a mountainous region.

PubMed

Nomoto, Shinichi; Utsumi, Momoe; Sasayama, Satoshi; Dekigai, Hiroshi

2017-01-01

We have developed a cloud system, the e-Renraku Notebook (e-RN) for sharing of home care information based on the concept of "patient-centricity". In order to assess the likelihood that our system will enhance the communication and sharing of information between home healthcare staff members and home-care patients, we selected patients who were residing in mountainous regions for inclusion in our study. We herein report the findings.Eighteen staff members from 7 medical facilities and 9 patients participated in the present study.The e-RN was developed for two reasons: to allow patients to independently report their health status and to have staff members view and respond to the information received. The patients and staff members were given iPads with the pre-installed applications and the information being exchanged was reviewed over a 54-day period.Information was mainly input by the patients (61.6%), followed by the nurses who performed home visits (19.9%). The amount of information input by patients requiring high-level nursing care and their corresponding staff member was significantly greater than that input by patients who required low-level of nursing care.This patient-centric system in which patients can independently report and share information with a member of the healthcare staff provides a sense of security. It also allows staff members to understand the patient's health status before making a home visit, thereby giving them a sense of security and confidence. It was also noteworthy that elderly patients requiring high-level nursing care and their staff counterpart input information in the system significantly more frequently than patients who required low-level care.

47 CFR 25.111 - Additional information.

Code of Federal Regulations, 2010 CFR

2010-10-01

... information it requires for the Advance Publication, Coordination and Notification of frequency assignments... information required by the ITU Radiocommunication Bureau to advance publish, coordinate and notify the frequencies to be used for tracking, telemetry and control functions of DBS systems. [56 FR 24016, May 28...

Master's Degree in Management Information Systems with a Supply Chain Management Focus

ERIC Educational Resources Information Center

Ramaswamy, Kizhanatham V.; Boyd, Joseph L.; Desai, Mayur

2007-01-01

A graduate curriculum in Management Information Systems with a Supply Chain Management focus is presented. The motivation for this endeavor stems from the fact that the global scope of modern business organizations and the competitive environment in which they operate, requires an information system leveraged supply chain management system (SCM)…

Increasing the Utility of Information Systems in Schools: Lessons from the Literature. Multilevel Evaluation Systems Project.

ERIC Educational Resources Information Center

Herman, Joan

The Multilevel Evaluation Systems Project is exploring the requirements for information systems that could help teachers and administrators sort through, analyze, and apply comprehensive information about their students, community, instructional processes, and outcomes to improve their schools. Toward this end, a multi-disciplinary literature…

Sharik 1.0: User Needs and System Requirements for a Web-Based Tool to Support Collaborative Sensemaking

DTIC Science & Technology

2016-05-01

Sharik 1.0: User Needs and System Requirements for a Web -Based Tool to Support Collaborative Sensemaking Shadi Ghajar-Khosravi...share the new intelligence items with their peers. In this report, the authors describe Sharik (SHAring Resources, Information, and Knowledge), a web ...SHAring Resources, Information and Knowledge, soit le partage des ressources, de l’information et des connaissances), un outil Web qui facilite le

An Object-Based Requirements Modeling Method.

ERIC Educational Resources Information Center

Cordes, David W.; Carver, Doris L.

1992-01-01

Discusses system modeling and specification as it relates to object-based information systems development and software development. An automated system model based on the objects in the initial requirements document is described, the requirements document translator is explained, and a sample application of the technique is provided. (12…

Software Requirements Analysis as Fault Predictor

NASA Technical Reports Server (NTRS)

Wallace, Dolores

2003-01-01

Waiting until the integration and system test phase to discover errors leads to more costly rework than resolving those same errors earlier in the lifecycle. Costs increase even more significantly once a software system has become operational. WE can assess the quality of system requirements, but do little to correlate this information either to system assurance activities or long-term reliability projections - both of which remain unclear and anecdotal. Extending earlier work on requirements accomplished by the ARM tool, measuring requirements quality information against code complexity and test data for the same system may be used to predict specific software modules containing high impact or deeply embedded faults now escaping in operational systems. Such knowledge would lead to more effective and efficient test programs. It may enable insight into whether a program should be maintained or started over.

Decentralized event-triggered consensus control strategy for leader-follower networked systems

NASA Astrophysics Data System (ADS)

Zhang, Shouxu; Xie, Duosi; Yan, Weisheng

2017-08-01

In this paper, the consensus problem of leader-follower networked systems is addressed. At first, a centralized and a decentralized event-triggered control strategy are proposed, which make the control actuators of followers update at aperiodic invent interval. In particular, the latter one makes each follower requires the local information only. After that, an improved triggering function that only uses the follower's own information and the neighbors' states at their latest event instants is developed to relax the requirement of the continuous state of the neighbors. In addition, the strategy does not require the information of the topology, nor the eigenvalues of the Laplacian matrix. And if the follower does not have direct connection to the leader, the leader's information is not required either. It is analytically shown that by using the proposed strategy the leader-follower networked system is able to reach consensus without continuous communication among followers. Simulation examples are given to show effectiveness of the proposed control strategy.

Space Station data system analysis/architecture study. Task 1: Functional requirements definition, DR-5

NASA Technical Reports Server (NTRS)

1985-01-01

The initial task in the Space Station Data System (SSDS) Analysis/Architecture Study is the definition of the functional and key performance requirements for the SSDS. The SSDS is the set of hardware and software, both on the ground and in space, that provides the basic data management services for Space Station customers and systems. The primary purpose of the requirements development activity was to provide a coordinated, documented requirements set as a basis for the system definition of the SSDS and for other subsequent study activities. These requirements should also prove useful to other Space Station activities in that they provide an indication of the scope of the information services and systems that will be needed in the Space Station program. The major results of the requirements development task are as follows: (1) identification of a conceptual topology and architecture for the end-to-end Space Station Information Systems (SSIS); (2) development of a complete set of functional requirements and design drivers for the SSIS; (3) development of functional requirements and key performance requirements for the Space Station Data System (SSDS); and (4) definition of an operating concept for the SSIS. The operating concept was developed both from a Space Station payload customer and operator perspective in order to allow a requirements practicality assessment.

Conceptual Problems.

ERIC Educational Resources Information Center

Foley, Walter J.

A systems theory approach to information requirements in education and in evaluation strategies is applied to decision making. Educational decision making itself involves long range planning, system structuring to implement goals, system allocation (cost), and system monitoring which provides the feedback. Each level requires differential…

An Internet-Based Accounting Information Systems Project

ERIC Educational Resources Information Center

Miller, Louise

2012-01-01

This paper describes a student project assignment used in an accounting information systems course. We are now truly immersed in the internet age, and while many required accounting information systems courses and textbooks introduce database design, accounting software development, cloud computing, and internet security, projects involving the…

12 CFR 252.135 - Data and information required to be submitted in support of the Board's analyses.

Code of Federal Regulations, 2013 CFR

2013-01-01

... 12 Banks and Banking 4 2013-01-01 2013-01-01 false Data and information required to be submitted in support of the Board's analyses. 252.135 Section 252.135 Banks and Banking FEDERAL RESERVE SYSTEM... (REGULATION YY) Supervisory Stress Test Requirements for Covered Companies § 252.135 Data and information...

12 CFR 252.135 - Data and information required to be submitted in support of the Board's analyses.

Code of Federal Regulations, 2014 CFR

2014-01-01

... 12 Banks and Banking 4 2014-01-01 2014-01-01 false Data and information required to be submitted in support of the Board's analyses. 252.135 Section 252.135 Banks and Banking FEDERAL RESERVE SYSTEM... (REGULATION YY) Supervisory Stress Test Requirements for Covered Companies § 252.135 Data and information...

Step 1:Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Collision Avoidance

NASA Technical Reports Server (NTRS)

2007-01-01

This document provides definition of technology human interface requirements for Collision Avoidance (CA). This was performed through a review of CA-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Access 5 CA work package were considered... Beginning with the HSI high-level functional requirement for CA, and CA technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge CA system status, and (2) the control capability needed by the pilot to obtain CA information and affect an avoidance maneuver. Fundamentally, these requirements provide the candidate CA technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how CA operations and functions should interface with the pilot to provide the necessary CA functionality to the UA-pilot system .Requirements and guidelines for CA are partitioned into four categories: (1) General, (2) Alerting, (3) Guidance, and (4) Cockpit Display of Traffic Information. Each requirement is stated and is supported with a rationale and associated reference(s).

Organizations and Information Processing: A Field Study of Research and Development Units within the United States Air Force Systems Command.

DTIC Science & Technology

1984-08-01

Requirements 63 3.3.1 Hypothesis 4: Relationship Between Unit Technology and Information Source Requirements..................64 3.3.2 Hypothesis 5... Relationship Between Environ- mental Uncertainty and Information Source Requirements..................65 3.3.3 Hypothesis 6: Relationship Between Inter-Unit...Sources. ............ 67 3.4.1 Hypothesis 1: Relationship Between Unit Structure and the Accessibility and Quality of Information Sources .. ........ 68

50 CFR 660.113 - Trawl fishery-recordkeeping and reporting.

Code of Federal Regulations, 2012 CFR

2012-10-01

... materials as well as other information stored in or accessible through a computer or other information retrieval system; worksheets; weight slips; preliminary, interim, and final tally sheets; receipts; checks... compliance with all reporting requirements described in this paragraph. (i) Required information. All IFQ...

50 CFR 660.113 - Trawl fishery-recordkeeping and reporting.

Code of Federal Regulations, 2013 CFR

2013-10-01

... materials as well as other information stored in or accessible through a computer or other information retrieval system; worksheets; weight slips; preliminary, interim, and final tally sheets; receipts; checks... compliance with all reporting requirements described in this paragraph. (i) Required information. All IFQ...

50 CFR 660.113 - Trawl fishery-recordkeeping and reporting.

Code of Federal Regulations, 2014 CFR

2014-10-01

... materials as well as other information stored in or accessible through a computer or other information retrieval system; worksheets; weight slips; preliminary, interim, and final tally sheets; receipts; checks... compliance with all reporting requirements described in this paragraph. (i) Required information. All IFQ...

Data vs. information: A system paradigm

NASA Technical Reports Server (NTRS)

Billingsley, F. C.

1982-01-01

The data system designer requires data parameters, and is dependent on the user to convert information needs to these data parameters. This conversion will be done with more or less accuracy, beginning a chain of inaccuracies which propagate through the system, and which, in the end, may prevent the user from converting the data received into the information required. The concept to be pursued is that errors occur in various parts of the system, and, having occurred, propagate to the end. Modeling of the system may allow an estimation of the effects at any point and the final accumulated effect, and may prove a method of allocating an error budget among the system components. The selection of the various technical parameters which a data system must meet must be done in relation to the ability of the user to turn the cold, impersonal data into a live, personal decision or piece of information.

Knowledge structure representation and automated updates in intelligent information management systems

NASA Technical Reports Server (NTRS)

Corey, Stephen; Carnahan, Richard S., Jr.

1990-01-01

A continuing effort to apply rapid prototyping and Artificial Intelligence techniques to problems associated with projected Space Station-era information management systems is examined. In particular, timely updating of the various databases and knowledge structures within the proposed intelligent information management system (IIMS) is critical to support decision making processes. Because of the significantly large amounts of data entering the IIMS on a daily basis, information updates will need to be automatically performed with some systems requiring that data be incorporated and made available to users within a few hours. Meeting these demands depends first, on the design and implementation of information structures that are easily modified and expanded, and second, on the incorporation of intelligent automated update techniques that will allow meaningful information relationships to be established. Potential techniques are studied for developing such an automated update capability and IIMS update requirements are examined in light of results obtained from the IIMS prototyping effort.

The Boston Marathon Bombings Mass Casualty Incident: One Emergency Department's Information Systems Challenges and Opportunities.

PubMed

Landman, Adam; Teich, Jonathan M; Pruitt, Peter; Moore, Samantha E; Theriault, Jennifer; Dorisca, Elizabeth; Harris, Sheila; Crim, Heidi; Lurie, Nicole; Goralnick, Eric

2015-07-01

Emergency department (ED) information systems are designed to support efficient and safe emergency care. These same systems often play a critical role in disasters to facilitate real-time situation awareness, information management, and communication. In this article, we describe one ED's experiences with ED information systems during the April 2013 Boston Marathon bombings. During postevent debriefings, staff shared that our ED information systems and workflow did not optimally support this incident; we found challenges with our unidentified patient naming convention, real-time situational awareness of patient location, and documentation of assessments, orders, and procedures. As a result, before our next mass gathering event, we changed our unidentified patient naming convention to more clearly distinguish multiple, simultaneous, unidentified patients. We also made changes to the disaster registration workflow and enhanced roles and responsibilities for updating electronic systems. Health systems should conduct disaster drills using their ED information systems to identify inefficiencies before an actual incident. ED information systems may require enhancements to better support disasters. Newer technologies, such as radiofrequency identification, could further improve disaster information management and communication but require careful evaluation and implementation into daily ED workflow. Copyright © 2014 American College of Emergency Physicians. Published by Elsevier Inc. All rights reserved.

75 FR 43487 - Proposed Information Collection; Comment Request; Vessel Monitoring System Requirements in...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-07-26

... Monitoring System Requirements in the Western Pacific Pelagic Longline Fishery), OMB Control No. 0648-0519... requirement from OMB Control No. 0648-0584 (Permitting, Vessel Identification and Vessel Monitoring System... one collection (OMB Control No. 0648-0441). II. Method of Collection Automatic. III. Data OMB Control...

The application of use case modeling in designing medical imaging information systems.

PubMed

Safdari, Reza; Farzi, Jebraeil; Ghazisaeidi, Marjan; Mirzaee, Mahboobeh; Goodini, Azadeh

2013-01-01

Introduction. The essay at hand is aimed at examining the application of use case modeling in analyzing and designing information systems to support Medical Imaging services. Methods. The application of use case modeling in analyzing and designing health information systems was examined using electronic databases (Pubmed, Google scholar) resources and the characteristics of the modeling system and its effect on the development and design of the health information systems were analyzed. Results. Analyzing the subject indicated that Provident modeling of health information systems should provide for quick access to many health data resources in a way that patients' data can be used in order to expand distant services and comprehensive Medical Imaging advices. Also these experiences show that progress in the infrastructure development stages through gradual and repeated evolution process of user requirements is stronger and this can lead to a decline in the cycle of requirements engineering process in the design of Medical Imaging information systems. Conclusion. Use case modeling approach can be effective in directing the problems of health and Medical Imaging information systems towards understanding, focusing on the start and analysis, better planning, repetition, and control.

Advanced information processing system: Input/output system services

NASA Technical Reports Server (NTRS)

Masotto, Tom; Alger, Linda

1989-01-01

The functional requirements and detailed specifications for the Input/Output (I/O) Systems Services of the Advanced Information Processing System (AIPS) are discussed. The introductory section is provided to outline the overall architecture and functional requirements of the AIPS system. Section 1.1 gives a brief overview of the AIPS architecture as well as a detailed description of the AIPS fault tolerant network architecture, while section 1.2 provides an introduction to the AIPS systems software. Sections 2 and 3 describe the functional requirements and design and detailed specifications of the I/O User Interface and Communications Management modules of the I/O System Services, respectively. Section 4 illustrates the use of the I/O System Services, while Section 5 concludes with a summary of results and suggestions for future work in this area.

Development of Integrated Programs for Aerospace-vehicle design (IPAD): Integrated information processing requirements

NASA Technical Reports Server (NTRS)

Southall, J. W.

1979-01-01

The engineering-specified requirements for integrated information processing by means of the Integrated Programs for Aerospace-Vehicle Design (IPAD) system are presented. A data model is described and is based on the design process of a typical aerospace vehicle. General data management requirements are specified for data storage, retrieval, generation, communication, and maintenance. Information management requirements are specified for a two-component data model. In the general portion, data sets are managed as entities, and in the specific portion, data elements and the relationships between elements are managed by the system, allowing user access to individual elements for the purpose of query. Computer program management requirements are specified for support of a computer program library, control of computer programs, and installation of computer programs into IPAD.

[Application of classified protection of information security in the information system of air pollution and health impact monitoring].

PubMed

Hao, Shuxin; Lü, Yiran; Liu, Jie; Liu, Yue; Xu, Dongqun

2018-01-01

To study the application of classified protection of information security in the information system of air pollution and health impact monitoring, so as to solve the possible safety risk of the information system. According to the relevant national standards and requirements for the information system security classified protection, and the professional characteristics of the information system, to design and implement the security architecture of information system, also to determine the protection level of information system. Basic security measures for the information system were developed in the technical safety and management safety aspects according to the protection levels, which effectively prevented the security risk of the information system. The information system established relatively complete information security protection measures, to enhanced the security of professional information and system service, and to ensure the safety of air pollution and health impact monitoring project carried out smoothly.

Detailed requirements document for common software of shuttle program information management system

NASA Technical Reports Server (NTRS)

Everette, J. M.; Bradfield, L. D.; Horton, C. L.

1975-01-01

Common software was investigated as a method for minimizing development and maintenance cost of the shuttle program information management system (SPIMS) applications while reducing the time-frame of their development. Those requirements satisfying these criteria are presented along with the stand-alone modules which may be used directly by applications. The SPIMS applications operating on the CYBER 74 computer, are specialized information management systems which use System 2000 as a data base manager. Common software provides the features to support user interactions on a CRT terminal using form input and command response capabilities. These features are available as subroutines to the applications.

Information management system study results. Volume 2: IMS study results appendixes

NASA Technical Reports Server (NTRS)

1971-01-01

Computer systems program specifications are presented for the modular space station information management system. These are the computer program contract end item, data bus system, data bus breadboard, and display interface adapter specifications. The performance, design, tests, and qualification requirements are established for the implementation of the information management system. For Vol. 1, see N72-19972.

On the management and processing of earth resources information

NASA Technical Reports Server (NTRS)

Skinner, C. W.; Gonzalez, R. C.

1973-01-01

The basic concepts of a recently completed large-scale earth resources information system plan are reported. Attention is focused throughout the paper on the information management and processing requirements. After the development of the principal system concepts, a model system for implementation at the state level is discussed.

In-Vehicle Signing Functions and Systems Concepts

DOT National Transportation Integrated Search

1996-01-01

This paper describes functional requirements and system concepts for an In-Vehicle Signing (IVS) system, which will bring information from roadway signs, signals, and pavement markings into the vehicle for presentation to the driver. Information filt...

User Working Group Charter

Atmospheric Science Data Center

2014-04-29

... Earth Observing System (EOS) Program through the EOS Data Information System (EOSDIS) Project and the Langley ASDC, located at NASA ... of the ASDC user interface, development of the Information Management System (IMS), and ASDC user conferences requirements for and ...

Quality Requirements for Electronic Health Record Systems*. A Japanese-German Information Management Perspective.

PubMed

Winter, Alfred; Takabayashi, Katsuhiko; Jahn, Franziska; Kimura, Eizen; Engelbrecht, Rolf; Haux, Reinhold; Honda, Masayuki; Hübner, Ursula H; Inoue, Sozo; Kohl, Christian D; Matsumoto, Takehiro; Matsumura, Yasushi; Miyo, Kengo; Nakashima, Naoki; Prokosch, Hans-Ulrich; Staemmler, Martin

2017-08-07

For more than 30 years, there has been close cooperation between Japanese and German scientists with regard to information systems in health care. Collaboration has been formalized by an agreement between the respective scientific associations. Following this agreement, two joint workshops took place to explore the similarities and differences of electronic health record systems (EHRS) against the background of the two national healthcare systems that share many commonalities. To establish a framework and requirements for the quality of EHRS that may also serve as a basis for comparing different EHRS. Donabedian's three dimensions of quality of medical care were adapted to the outcome, process, and structural quality of EHRS and their management. These quality dimensions were proposed before the first workshop of EHRS experts and enriched during the discussions. The Quality Requirements Framework of EHRS (QRF-EHRS) was defined and complemented by requirements for high quality EHRS. The framework integrates three quality dimensions (outcome, process, and structural quality), three layers of information systems (processes and data, applications, and physical tools) and three dimensions of information management (strategic, tactical, and operational information management). Describing and comparing the quality of EHRS is in fact a multidimensional problem as given by the QRF-EHRS framework. This framework will be utilized to compare Japanese and German EHRS, notably those that were presented at the second workshop.

Data Requirements for Oceanic Processes in the Open Ocean, Coastal Zone, and Cryosphere

NASA Technical Reports Server (NTRS)

Nagler, R. G.; Mccandless, S. W., Jr.

1978-01-01

The type of information system that is needed to meet the requirements of ocean, coastal, and polar region users was examined. The requisite qualities of the system are: (1) availability, (2) accessibility, (3) responsiveness, (4) utility, (5) continuity, and (6) NASA participation. The system would not displace existing capabilities, but would have to integrate and expand the capabilities of existing systems and resolve the deficiencies that currently exist in producer-to-user information delivery options.

Making the case for a clinical information system: the chief information officer view.

PubMed

Cotter, Carole M

2007-03-01

Adequate decision support for clinicians and other caregivers requires accessible and reliable patient information. Powerful societal and economic forces are moving us toward an integrated, patient-centered health care information system that will allow caregivers to exchange up-to-date patient health information quickly and easily. These forces include patient safety, potential health care cost savings, empowerment of consumers (and their subsequent demands for quality), new federal policies, and growing regional health care initiatives. Underspending on health care information technologies has gone on for many years; and the creation and implementation of a comprehensive clinical information system will entail many difficulties, particularly in regard to patients' privacy and control of their information, standardization of electronic health records, cost of adopting information technology, unbalanced financial incentives, and the varying levels of preparation across caregivers. There will also be potential effects on the physician-patient relationship. Ultimately, an integrated system will require a concerted transformation of the health care industry that is akin to what the banking industry has accomplished with electronic automation. Critical care units provide a good starting point for how information system technologies can be used and electronic patient information collected, although the robust systems designed for intensive care units are not always used to their potential.

Requirements for SPIRES II. An External Specification for the Stanford Public Information Retrieval System.

ERIC Educational Resources Information Center

Parker, Edwin B.

SPIRES (Stanford Public Information Retrieval System) is a computerized information storage and retrieval system intended for use by students and faculty members who have little knowledge of computers but who need rapid and sophisticated retrieval and analysis. The functions and capabilities of the system from the user's point of view are…

Modelling health care processes for eliciting user requirements: a way to link a quality paradigm and clinical information system design.

PubMed

Staccini, P; Joubert, M; Quaranta, J F; Fieschi, D; Fieschi, M

2000-01-01

Hospital information systems have to support quality improvement objectives. The design issues of health care information system can be classified into three categories: 1) time-oriented and event-labelled storage of patient data; 2) contextual support of decision-making; 3) capabilities for modular upgrading. The elicitation of the requirements has to meet users' needs in relation to both the quality (efficacy, safety) and the monitoring of all health care activities (traceability). Information analysts need methods to conceptualize clinical information systems that provide actors with individual benefits and guide behavioural changes. A methodology is proposed to elicit and structure users' requirements using a process-oriented analysis, and it is applied to the field of blood transfusion. An object-oriented data model of a process has been defined in order to identify its main components: activity, sub-process, resources, constrains, guidelines, parameters and indicators. Although some aspects of activity, such as "where", "what else", and "why" are poorly represented by the data model alone, this method of requirement elicitation fits the dynamic of data input for the process to be traced. A hierarchical representation of hospital activities has to be found for this approach to be generalised within the organisation, for the processes to be interrelated, and for their characteristics to be shared.

User-centered requirements engineering in health information systems: a study in the hemophilia field.

PubMed

Teixeira, Leonor; Ferreira, Carlos; Santos, Beatriz Sousa

2012-06-01

The use of sophisticated information and communication technologies (ICTs) in the health care domain is a way to improve the quality of services. However, there are also hazards associated with the introduction of ICTs in this domain and a great number of projects have failed due to the lack of systematic consideration of human and other non-technology issues throughout the design or implementation process, particularly in the requirements engineering process. This paper presents the methodological approach followed in the design process of a web-based information system (WbIS) for managing the clinical information in hemophilia care, which integrates the values and practices of user-centered design (UCD) activities into the principles of software engineering, particularly in the phase of requirements engineering (RE). This process followed a paradigm that combines a grounded theory for data collection with an evolutionary design based on constant development and refinement of the generic domain model using three well-known methodological approaches: (a) object-oriented system analysis; (b) task analysis; and, (c) prototyping, in a triangulation work. This approach seems to be a good solution for the requirements engineering process in this particular case of the health care domain, since the inherent weaknesses of individual methods are reduced, and emergent requirements are easier to elicit. Moreover, the requirements triangulation matrix gives the opportunity to look across the results of all used methods and decide what requirements are critical for the system success. Copyright © 2010 Elsevier Ireland Ltd. All rights reserved.

Information Integration for Concurrent Engineering (IICE) IDEF3 Process Description Capture Method Report

DTIC Science & Technology

1992-05-01

methodology, knowledge acquisition, 140 requirements definition, information systems, information engineering, 16. PRICE CODE systems engineering...and knowledge resources. Like manpower, materials, and machines, information and knowledge assets are recognized as vital resources that can be...evolve towards an information -integrated enterprise. These technologies are designed to leverage information and knowledge resources as the key

An information system for epidemiology based on a computer-based medical record.

PubMed

Verdier, C; Flory, A

1994-12-01

A new way is presented to build an information system addressed to problems in epidemiology. Based on our analysis of current and future requirements, a system is proposed which allows for collection, organization and distribution of data within a computer network. In this application, two broad communities of users-physicians and epidemiologists-can be identified, each with their own perspectives and goals. The different requirements of each community lead us to a client-service centered architecture which provides the functionality requirements of the two groups. The resulting physician workstation provides help for recording and querying medical information about patients and from a pharmacological database. All information is classified and coded in order to be retrieved for pharmaco-economic studies. The service center receives information from physician workstations and permits organizations that are in charge of statistical studies to work with "real" data recorded during patient encounters. This leads to a new approach in epidemiology. Studies can be carried out with a more efficient data acquisition. For modelling the information system, we use an object-oriented approach. We have observed that the object-oriented representation, particularly its concepts of generalization, aggregation and encapsulation, are very usable for our problem.

Highway Economic Requirements System - v. III. User's Guide.

DOT National Transportation Integrated Search

1998-05-18

The Branson Travel and Recreational Information Program (TRIP) in Branson, Missouri, and the I-40 Traveler and Tourist Information System (TTIS) in the I-40 corridor of northern Arizona are two field Operational Tests (FOTs) of Traveler Information S...

Challenges to managing natural resource information

Treesearch

William L. Halvorson

2005-01-01

One of the most important issues facing resource managers today is that of information. In order to handle the numerous and diverse requirements for information, landscape-scale information management systems are needed that allow individual land management units to view their resource information in a regional context. The characteristics of such a system are: (1) the...

Disaster at a University: A Case Study in Information Security

ERIC Educational Resources Information Center

Ayyagari, Ramakrishna; Tyks, Jonathan

2012-01-01

Security and disaster training is identified as a top Information Technology (IT) required skill that needs to be taught in Information Systems (IS) curriculums. Accordingly, information security and privacy have become core concepts in information system education. Providing IT security on a shoestring budget is always difficult and many small…

Integrating policy-based management and SLA performance monitoring

NASA Astrophysics Data System (ADS)

Liu, Tzong-Jye; Lin, Chin-Yi; Chang, Shu-Hsin; Yen, Meng-Tzu

2001-10-01

Policy-based management system provides the configuration capability for the system administrators to focus on the requirements of customers. The service level agreement performance monitoring mechanism helps system administrators to verify the correctness of policies. However, it is difficult for a device to process the policies directly because the policies are the management concept. This paper proposes a mechanism to decompose a policy into rules that can be efficiently processed by a device. Thus, the device may process the rule and collect the performance statistics information efficiently; and the policy-based management system may collect these performance statistics information and report the service-level agreement performance monitoring information to the system administrator. The proposed policy-based management system achieves both the policy configuration and service-level agreement performance monitoring requirements. A policy consists of a condition part and an action part. The condition part is a Boolean expression of a source host IP group, a destination host IP group, etc. The action part is the parameters of services. We say that an address group is compact if it only consists of a range of IP address that can be denoted by a pair of IP address and corresponding IP mask. If the condition part of a policy only consists of the compact address group, we say that the policy is a rule. Since a device can efficiently process a compact address and a system administrator prefers to define a range of IP address, the policy-based management system has to translate policy into rules and supplements the gaps between policy and rules. The proposed policy-based management system builds the relationships between VPN and policies, policy and rules. Since the system administrator wants to monitor the system performance information of VPNs and policies, the proposed policy-based management system downloads the relationships among VPNs, policies and rules to the SNMP agents. The SNMP agents build the management information base (MIB) of all VPNs, policies and rules according to the relationships obtained from the management server. Thus, the proposed policy-based management system may get all performance monitoring information of VPNs and policies from agents. The proposed policy-based manager achieves two goals: a) provide a management environment for the system administrator to configure their network only considering the policy requirement issues and b) let the device have only to process the packet and then collect the required performance information. These two things make the proposed management system satisfy both the user and device requirements.

AGIS: Integration of new technologies used in ATLAS Distributed Computing

NASA Astrophysics Data System (ADS)

Anisenkov, Alexey; Di Girolamo, Alessandro; Alandes Pradillo, Maria

2017-10-01

The variety of the ATLAS Distributed Computing infrastructure requires a central information system to define the topology of computing resources and to store different parameters and configuration data which are needed by various ATLAS software components. The ATLAS Grid Information System (AGIS) is the system designed to integrate configuration and status information about resources, services and topology of the computing infrastructure used by ATLAS Distributed Computing applications and services. Being an intermediate middleware system between clients and external information sources (like central BDII, GOCDB, MyOSG), AGIS defines the relations between experiment specific used resources and physical distributed computing capabilities. Being in production during LHC Runl AGIS became the central information system for Distributed Computing in ATLAS and it is continuously evolving to fulfil new user requests, enable enhanced operations and follow the extension of the ATLAS Computing model. The ATLAS Computing model and data structures used by Distributed Computing applications and services are continuously evolving and trend to fit newer requirements from ADC community. In this note, we describe the evolution and the recent developments of AGIS functionalities, related to integration of new technologies recently become widely used in ATLAS Computing, like flexible computing utilization of opportunistic Cloud and HPC resources, ObjectStore services integration for Distributed Data Management (Rucio) and ATLAS workload management (PanDA) systems, unified storage protocols declaration required for PandDA Pilot site movers and others. The improvements of information model and general updates are also shown, in particular we explain how other collaborations outside ATLAS could benefit the system as a computing resources information catalogue. AGIS is evolving towards a common information system, not coupled to a specific experiment.

Exploration Medical System Trade Study Tools Overview

NASA Technical Reports Server (NTRS)

Mindock, J.; Myers, J.; Latorella, K.; Cerro, J.; Hanson, A.; Hailey, M.; Middour, C.

2018-01-01

ExMC is creating an ecosystem of tools to enable well-informed medical system trade studies. The suite of tools address important system implementation aspects of the space medical capabilities trade space and are being built using knowledge from the medical community regarding the unique aspects of space flight. Two integrating models, a systems engineering model and a medical risk analysis model, tie the tools together to produce an integrated assessment of the medical system and its ability to achieve medical system target requirements. This presentation will provide an overview of the various tools that are a part of the tool ecosystem. Initially, the presentation's focus will address the tools that supply the foundational information to the ecosystem. Specifically, the talk will describe how information that describes how medicine will be practiced is captured and categorized for efficient utilization in the tool suite. For example, the talk will include capturing what conditions will be planned for in-mission treatment, planned medical activities (e.g., periodic physical exam), required medical capabilities (e.g., provide imaging), and options to implement the capabilities (e.g., an ultrasound device). Database storage and configuration management will also be discussed. The presentation will include an overview of how these information tools will be tied to parameters in a Systems Modeling Language (SysML) model, allowing traceability to system behavioral, structural, and requirements content. The discussion will also describe an HRP-led enhanced risk assessment model developed to provide quantitative insight into each capability's contribution to mission success. Key outputs from these various tools, to be shared with the space medical and exploration mission development communities, will be assessments of medical system implementation option satisfaction of requirements and per-capability contributions toward achieving requirements.

Multi-Modal Traveler Information System - Gateway Functional Requirements

DOT National Transportation Integrated Search

1997-11-17

The Multi-Modal Traveler Information System (MMTIS) project involves a large number of Intelligent Transportation System (ITS) related tasks. It involves research of all ITS initiatives in the Gary-Chicago-Milwaukee (GCM) Corridor which are currently...

Multi-Modal Traveler Information System - Gateway Interface Control Requirements

DOT National Transportation Integrated Search

1997-10-30

The Multi-Modal Traveler Information System (MMTIS) project involves a large number of Intelligent Transportation System (ITS) related tasks. It involves research of all ITS initiatives in the Gary-Chicago-Milwaukee (GCM) Corridor which are currently...

A project management system for the X-29A flight test program

NASA Technical Reports Server (NTRS)

Stewart, J. F.; Bauer, C. A.

1983-01-01

The project-management system developed for NASA's participation in the X-29A aircraft development program is characterized from a theoretical perspective, as an example of a system appropriate to advanced, highly integrated technology projects. System-control theory is applied to the analysis of classical project-management techniques and structures, which are found to be of closed-loop multivariable type; and the effects of increasing project complexity and integration are evaluated. The importance of information flow, sampling frequency, information holding, and delays is stressed. The X-29A system is developed in four stages: establishment of overall objectives and requirements, determination of information processes (block diagrams) definition of personnel functional roles and relationships, and development of a detailed work-breakdown structure. The resulting system is shown to require a greater information flow to management than conventional methods. Sample block diagrams are provided.

Benchmark requirements for the the Energy Emergency Management Information System (EEMIS). Phase 1: Work plan

NASA Astrophysics Data System (ADS)

1980-09-01

The energy emergency management information system (EEMIS) has responsibility for providing special information and communication services to government officials at Federal and state levels, who must deal with energy emergencies. Because of proprietary information residing in the data base used for federal purposes, a special system (EEMIS-S) must be established for use by the states. It is planned to acquire teleprocessing services for EEMIS-S from a time-sharing commercial vendor, and the process for procurement must meet guidelines for approval. The work plan and schedule for meeting these guidelines are discussed. Tasks to be included contain estimates of time, cost, and resources required, all of which are briefly described.

A next generation advanced traveler information precursor system (ATIS 2.0 precursor system) system requirements.

DOT National Transportation Integrated Search

2016-12-01

Advanced Traveler Information Systems (ATIS) have experienced significant growth since their initial inception in the 1990s. Technologies have continued to evolve at a rapid pace, enabling the integration of advanced solutions for traveler informatio...

The Information Science Experiment System - The computer for science experiments in space

NASA Technical Reports Server (NTRS)

Foudriat, Edwin C.; Husson, Charles

1989-01-01

The concept of the Information Science Experiment System (ISES), potential experiments, and system requirements are reviewed. The ISES is conceived as a computer resource in space whose aim is to assist computer, earth, and space science experiments, to develop and demonstrate new information processing concepts, and to provide an experiment base for developing new information technology for use in space systems. The discussion covers system hardware and architecture, operating system software, the user interface, and the ground communication link.

Evaluation of the Executive Information Requirements for the Market Research Process.

ERIC Educational Resources Information Center

Lanser, Michael A.

A study examined the marketing research information required by those executives of Lakeshore Technical College (Wisconsin) whose decisions affect the college's direction. Data were gathered from the following sources: literature review; development of a data dictionary framework; analysis of the college's current information system through…

Information Technology in Sport Management Curricula

ERIC Educational Resources Information Center

Barneva, Reneta P.; Hite, Penny D.

2017-01-01

We study the breadth of inclusion of information technology in sport management (SM) programs, surveying program sponsoring colleges and universities within a prominent state-university system. Our results indicate a very low number of SM programs require any type of information technology courses as part of their core requirements. In fact, only…

78 FR 17186 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement (DFARS...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-03-20

... Requirements for Critical Safety Items AGENCY: Defense Acquisition Regulations System, Department of Defense... of the burden of the proposed information collection; (c) ways to enhance the quality, utility, and... technology. The Office of Management and Budget (OMB) has approved this information collection for use...

22 CFR 62.70 - SEVIS reporting requirements.

Code of Federal Regulations, 2010 CFR

2010-04-01

... Student and Exchange Visitor Information System (SEVIS) § 62.70 SEVIS reporting requirements. (a... children if a SEVIS record has been created for the participant; (5) Utilize SEVIS to up-date information... information for participants within 21 days of being notified by a participant of a change in his or her...

A Management Information System in a Library Environment.

ERIC Educational Resources Information Center

Sutton, Michael J.; Black, John B.

More effective use of diminishing resources was needed to provide the best possible services at the University of Guelph (Ontario, Canada) library. This required the improved decision-making processes of a Library Management Information System (LMIS) to provide systematic information analysis. An information flow model was created, and an…

IMIS: Integrated Maintenance Information System. A maintenance information delivery concept

NASA Technical Reports Server (NTRS)

Vonholle, Joseph C.

1987-01-01

The Integrated Maintenance Information System (IMIS) will optimize the use of available manpower, enhance technical performance, improve training, and reduce the support equipment and documentation needed for deployment. It will serve as the technician's single, integrated source of all the technical information required to perform modern aircraft maintenance.

Tank waste remediation system functions and requirements document

DOE Office of Scientific and Technical Information (OSTI.GOV)

Carpenter, K.E

1996-10-03

This is the Tank Waste Remediation System (TWRS) Functions and Requirements Document derived from the TWRS Technical Baseline. The document consists of several text sections that provide the purpose, scope, background information, and an explanation of how this document assists the application of Systems Engineering to the TWRS. The primary functions identified in the TWRS Functions and Requirements Document are identified in Figure 4.1 (Section 4.0) Currently, this document is part of the overall effort to develop the TWRS Functional Requirements Baseline, and contains the functions and requirements needed to properly define the top three TWRS function levels. TWRS Technicalmore » Baseline information (RDD-100 database) included in the appendices of the attached document contain the TWRS functions, requirements, and architecture necessary to define the TWRS Functional Requirements Baseline. Document organization and user directions are provided in the introductory text. This document will continue to be modified during the TWRS life-cycle.« less

76 FR 59660 - Proposed Information Collection; Comment Request; Permitting, Vessel Identification, and Vessel...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-09-27

... DEPARTMENT OF COMMERCE National Oceanic and Atmospheric Administration Proposed Information Collection; Comment Request; Permitting, Vessel Identification, and Vessel Monitoring System Requirements for... satellite- based vessel monitoring system (VMS). This collection of information is needed for permit...

Weather Requirements and Procedures for Step 1: High Altitude Long Endurance (HALE) Unmanned Aircraft System (UAS) Flight Operations in the National Air Space (NAS)

NASA Technical Reports Server (NTRS)

2007-01-01

This cover sheet is for version 2 of the weather requirements document along with Appendix A. The purpose of the requirements document was to identify and to list the weather functional requirements needed to achieve the Access 5 vision of "operating High Altitude, Long Endurance (HALE) Unmanned Aircraft Systems (UAS) routinely, safely, and reliably in the National Airspace System (NAS) for Step 1." A discussion of the Federal Aviation Administration (FAA) references and related policies, procedures, and standards is provided as basis for the recommendations supported within this document. Additional procedures and reference documentation related to weather functional requirements is also provided for background. The functional requirements and related information are to be proposed to the FAA and various standards organizations for consideration and approval. The appendix was designed to show that sources of flight weather information are readily available to UAS pilots conducting missions in the NAS. All weather information for this presentation was obtained from the public internet.

Information Fusion Issues in the UK Environmental Science Community

NASA Astrophysics Data System (ADS)

Giles, J. R.

2010-12-01

The Earth is a complex, interacting system which cannot be neatly divided by discipline boundaries. To gain an holistic understanding of even a component of an Earth System requires researchers to draw information from multiple disciplines and integrate these to develop a broader understanding. But the barriers to achieving this are formidable. Research funders attempting to encourage the integration of information across disciplines need to take into account culture issues, the impact of intrusion of projects on existing information systems, ontologies and semantics, scale issues, heterogeneity and the uncertainties associated with combining information from diverse sources. Culture - There is a cultural dualism in the environmental sciences were information sharing is both rewarded and discouraged. Researchers who share information both gain new opportunities and risk reducing their chances of being first author in an high-impact journal. The culture of the environmental science community has to be managed to ensure that information fusion activities are encouraged. Intrusion - Existing information systems have an inertia of there own because of the intellectual and financial capital invested within them. Information fusion activities must recognise and seek to minimise the potential impact of their projects on existing systems. Low intrusion information fusions systems such as OGC web-service and the OpenMI Standard are to be preferred to whole-sale replacement of existing systems. Ontology and Semantics - Linking information across disciplines requires a clear understanding of the concepts deployed in the vocabulary used to describe them. Such work is a critical first step to creating routine information fusion. It is essential that national bodies, such as geological surveys organisations, document and publish their ontologies, semantics, etc. Scale - Environmental processes operate at scales ranging from microns to the scale of the Solar System and potentially beyond. The many different scales involved provide serious challenges to information fusion which need to be researched. Heterogeneity - Natural systems are heterogeneous, that is a system consisting of multiple components each of which may have considerable internal variation. Modelling Earth Systems requires recognition of the inherent complexity. Uncertainty - Understanding the uncertainties within a single information source can be difficult. Understanding the uncertainties across a system of linked models, each drawn from multiple information resources, represents a considerable challenge that must be addressed. The challenges to overcome appear insurmountable to individual research groups; but the potential rewards, in terms of a fuller scientific understanding of Earth Systems, are significant. A major international effort must be mounted to tackle these barriers and enable routine information fusion.

A hierarchical modeling methodology for the definition and selection of requirements

NASA Astrophysics Data System (ADS)

Dufresne, Stephane

This dissertation describes the development of a requirements analysis methodology that takes into account the concept of operations and the hierarchical decomposition of aerospace systems. At the core of the methodology, the Analytic Network Process (ANP) is used to ensure the traceability between the qualitative and quantitative information present in the hierarchical model. The proposed methodology is implemented to the requirements definition of a hurricane tracker Unmanned Aerial Vehicle. Three research objectives are identified in this work; (1) improve the requirements mapping process by matching the stakeholder expectations with the concept of operations, systems and available resources; (2) reduce the epistemic uncertainty surrounding the requirements and requirements mapping; and (3) improve the requirements down-selection process by taking into account the level of importance of the criteria and the available resources. Several challenges are associated with the identification and definition of requirements. The complexity of the system implies that a large number of requirements are needed to define the systems. These requirements are defined early in the conceptual design, where the level of knowledge is relatively low and the level of uncertainty is large. The proposed methodology intends to increase the level of knowledge and reduce the level of uncertainty by guiding the design team through a structured process. To address these challenges, a new methodology is created to flow-down the requirements from the stakeholder expectations to the systems alternatives. A taxonomy of requirements is created to classify the information gathered during the problem definition. Subsequently, the operational and systems functions and measures of effectiveness are integrated to a hierarchical model to allow the traceability of the information. Monte Carlo methods are used to evaluate the variations of the hierarchical model elements and consequently reduce the epistemic uncertainty. The proposed methodology is applied to the design of a hurricane tracker Unmanned Aerial Vehicles to demonstrate the origin and impact of requirements on the concept of operations and systems alternatives. This research demonstrates that the hierarchical modeling methodology provides a traceable flow-down of the requirements from the problem definition to the systems alternatives phases of conceptual design.

Top DoD Management Challenges, Fiscal Year 2018

DTIC Science & Technology

2018-01-01

Afghan Human Resource Information Management System to validate ANDSF personnel numbers and salaries; • Afghan Personnel Pay System to facilitate...unit strength accountability and personnel verification; and • Core Information Management System to improve accountability of equipment inventories...ACQUISITION AND CONTRACT MANAGEMENT Federal Acquisition Regulation requires contractor performance information be collected in the Contractor

IDEF3 Formalization Report

DTIC Science & Technology

1991-10-01

SUBJECT TERMS 15. NUMBER OF PAGES engineering management information systems method formalization 60 information engineering process modeling 16 PRICE...CODE information systems requirements definition methods knowlede acquisition methods systems engineering 17. SECURITY CLASSIFICATION ji. SECURITY... Management , Inc., Santa Monica, California. CORYNEN, G. C., 1975, A Mathematical Theory of Modeling and Simula- tion. Ph.D. Dissertation, Department

Information Systems Security and Computer Crime in the IS Curriculum: A Detailed Examination

ERIC Educational Resources Information Center

Foltz, C. Bryan; Renwick, Janet S.

2011-01-01

The authors examined the extent to which information systems (IS) security and computer crime are covered in information systems programs. Results suggest that IS faculty believe security coverage should be increased in required, elective, and non-IS courses. However, respondent faculty members are concerned that existing curricula leave little…

Information Systems Security Job Advertisement Analysis: Skills Review and Implications for Information Systems Curriculum

ERIC Educational Resources Information Center

Brooks, Nita G.; Greer, Timothy H.; Morris, Steven A.

2018-01-01

The authors' focus was the assessment of skill requirements for information systems security positions to understand expectations for security jobs and to highlight issues relevant to curriculum management. The analysis of 798 job advertisements involved the exploration of domain-related and soft skills as well as degree and certification…

Information transfer satellite concept study. Volume 1: Summary

NASA Technical Reports Server (NTRS)

Bergin, P.; Kincade, C.; Kurpiewski, D.; Leinhaupel, F.; Millican, F.; Onstad, R.

1971-01-01

A wide range of information transfer demands were identified and analyzed. They were then combined into an appropriate set of requirements for satellite communication services. In this process the demands were ranked and combined into single and multipurpose satellite systems. A detailed analysis was performed on each satellite system to determine: total system cost, including both ground and space segments; sensitivities of the systems to various system tradeoffs; and forcing functions which control the system variations. A listing of candidate missions for detailed study is presented, along with a description of the conceptual system design and an identification of the technology developments required to bring these systems to fruition.

FBI fingerprint identification automation study: AIDS 3 evaluation report. Volume 9: Functional requirements

NASA Technical Reports Server (NTRS)

1980-01-01

The current system and subsystem used by the Identification Division are described. System constraints that dictate the system environment are discussed and boundaries within which solutions must be found are described. The functional requirements were related to the performance requirements. These performance requirements were then related to their applicable subsystems. The flow of data, documents, or other pieces of information from one subsystem to another or from the external world into the identification system is described. Requirements and design standards for a computer based system are presented.

Demonstration of SLUMIS: a clinical database and management information system for a multi organ transplant program.

PubMed Central

Kurtz, M.; Bennett, T.; Garvin, P.; Manuel, F.; Williams, M.; Langreder, S.

1991-01-01

Because of the rapid evolution of the heart, heart/lung, liver, kidney and kidney/pancreas transplant programs at our institution, and because of a lack of an existing comprehensive database, we were required to develop a computerized management information system capable of supporting both clinical and research requirements of a multifaceted transplant program. SLUMIS (ST. LOUIS UNIVERSITY MULTI-ORGAN INFORMATION SYSTEM) was developed for the following reasons: 1) to comply with the reporting requirements of various transplant registries, 2) for reporting to an increasing number of government agencies and insurance carriers, 3) to obtain updates of our operative experience at regular intervals, 4) to integrate the Histocompatibility and Immunogenetics Laboratory (HLA) for online test result reporting, and 5) to facilitate clinical investigation. PMID:1807741

Extending NASA's SPICE ancillary information system to meet future mission needs

NASA Technical Reports Server (NTRS)

Acton, C.; Bachman, N.; Elson, L.; Semenov, B.; Turner, F.; Wright, E.

2002-01-01

This paper summarizes the architecture, capabilities, characteristics and uses of the current SPICE ancillary information system, and then outlines plans and ideas for how this system can be extended to meet future space mission requirements.

Multi-Modal Traveler Information System - GCM Corridor Architecture Interface Control Requirements

DOT National Transportation Integrated Search

1997-10-31

The Multi-Modal Traveler Information System (MMTIS) project involves a large number of Intelligent Transportation System (ITS) related tasks. It involves research of all ITS initiatives in the Gary-Chicago-Milwaukee (GCM) Corridor which are currently...

Multi-Modal Traveler Information System - GCM Corridor Architecture Functional Requirements

DOT National Transportation Integrated Search

1997-11-17

The Multi-Modal Traveler Information System (MMTIS) project involves a large number of Intelligent Transportation System (ITS) related tasks. It involves research of all ITS initiatives in the Gary-Chicago-Milwaukee (GCM) Corridor which are currently...

Intelligent Work Process Engineering System

NASA Technical Reports Server (NTRS)

Williams, Kent E.

2003-01-01

Optimizing performance on work activities and processes requires metrics of performance for management to monitor and analyze in order to support further improvements in efficiency, effectiveness, safety, reliability and cost. Information systems are therefore required to assist management in making timely, informed decisions regarding these work processes and activities. Currently information systems regarding Space Shuttle maintenance and servicing do not exist to make such timely decisions. The work to be presented details a system which incorporates various automated and intelligent processes and analysis tools to capture organize and analyze work process related data, to make the necessary decisions to meet KSC organizational goals. The advantages and disadvantages of design alternatives to the development of such a system will be discussed including technologies, which would need to bedesigned, prototyped and evaluated.

The Open System Interconnection as a building block in a health sciences information network.

PubMed Central

Boss, R W

1985-01-01

The interconnection of integrated health sciences library systems with other health sciences computer systems to achieve information networks will require either custom linkages among specific devices or the adoption of standards that all systems support. The most appropriate standards appear to be those being developed under the Open System Interconnection (OSI) reference model, which specifies a set of rules and functions that computers must follow to exchange information. The protocols have been modularized into seven different layers. The lowest three layers are generally available as off-the-shelf interfacing products. The higher layers require special development for particular applications. This paper describes the OSI, its application in health sciences networks, and specific tasks that remain to be undertaken. PMID:4052672

A study on building data warehouse of hospital information system.

PubMed

Li, Ping; Wu, Tao; Chen, Mu; Zhou, Bin; Xu, Wei-guo

2011-08-01

Existing hospital information systems with simple statistical functions cannot meet current management needs. It is well known that hospital resources are distributed with private property rights among hospitals, such as in the case of the regional coordination of medical services. In this study, to integrate and make full use of medical data effectively, we propose a data warehouse modeling method for the hospital information system. The method can also be employed for a distributed-hospital medical service system. To ensure that hospital information supports the diverse needs of health care, the framework of the hospital information system has three layers: datacenter layer, system-function layer, and user-interface layer. This paper discusses the role of a data warehouse management system in handling hospital information from the establishment of the data theme to the design of a data model to the establishment of a data warehouse. Online analytical processing tools assist user-friendly multidimensional analysis from a number of different angles to extract the required data and information. Use of the data warehouse improves online analytical processing and mitigates deficiencies in the decision support system. The hospital information system based on a data warehouse effectively employs statistical analysis and data mining technology to handle massive quantities of historical data, and summarizes from clinical and hospital information for decision making. This paper proposes the use of a data warehouse for a hospital information system, specifically a data warehouse for the theme of hospital information to determine latitude, modeling and so on. The processing of patient information is given as an example that demonstrates the usefulness of this method in the case of hospital information management. Data warehouse technology is an evolving technology, and more and more decision support information extracted by data mining and with decision-making technology is required for further research.

A conceptual persistent healthcare quality improvement process for software development management.

PubMed

Lin, Jen-Chiun; Su, Mei-Ju; Cheng, Po-Hsun; Weng, Yung-Chien; Chen, Sao-Jie; Lai, Jin-Shin; Lai, Feipei

2007-01-01

This paper illustrates a sustained conceptual service quality improvement process for the management of software development within a healthcare enterprise. Our proposed process is revised from Niland's healthcare quality information system (HQIS). This process includes functions to survey the satisfaction of system functions, describe the operation bylaws on-line, and provide on-demand training. To achieve these goals, we integrate five information systems in National Taiwan University Hospital, including healthcare information systems, health quality information system, requirement management system, executive information system, and digital learning system, to form a full Deming cycle. A preliminary user satisfaction survey showed that our outpatient information system scored an average of 71.31 in 2006.

The Database Query Support Processor (QSP)

NASA Technical Reports Server (NTRS)

1993-01-01

The number and diversity of databases available to users continues to increase dramatically. Currently, the trend is towards decentralized, client server architectures that (on the surface) are less expensive to acquire, operate, and maintain than information architectures based on centralized, monolithic mainframes. The database query support processor (QSP) effort evaluates the performance of a network level, heterogeneous database access capability. Air Force Material Command's Rome Laboratory has developed an approach, based on ANSI standard X3.138 - 1988, 'The Information Resource Dictionary System (IRDS)' to seamless access to heterogeneous databases based on extensions to data dictionary technology. To successfully query a decentralized information system, users must know what data are available from which source, or have the knowledge and system privileges necessary to find out this information. Privacy and security considerations prohibit free and open access to every information system in every network. Even in completely open systems, time required to locate relevant data (in systems of any appreciable size) would be better spent analyzing the data, assuming the original question was not forgotten. Extensions to data dictionary technology have the potential to more fully automate the search and retrieval for relevant data in a decentralized environment. Substantial amounts of time and money could be saved by not having to teach users what data resides in which systems and how to access each of those systems. Information describing data and how to get it could be removed from the application and placed in a dedicated repository where it belongs. The result simplified applications that are less brittle and less expensive to build and maintain. Software technology providing the required functionality is off the shelf. The key difficulty is in defining the metadata required to support the process. The database query support processor effort will provide quantitative data on the amount of effort required to implement an extended data dictionary at the network level, add new systems, adapt to changing user needs, and provide sound estimates on operations and maintenance costs and savings.

MODIS information, data and control system (MIDACS) level 2 functional requirements

NASA Technical Reports Server (NTRS)

Han, D.; Salomonson, V.; Ormsby, J.; Sharts, B.; Folta, D.; Ardanuy, P.; Mckay, A.; Hoyt, D.; Jaffin, S.; Vallette, B.

1988-01-01

The MODIS Information, Data and Control System (MIDACS) Level 2 Functional Requirements Document establishes the functional requirements for MIDACS and provides a basis for the mutual understanding between the users and the designers of the EosDIS, including the requirements, operating environment, external interfaces, and development plan. In defining the requirements and scope of the system, this document describes how MIDACS will operate as an element of the EOS within the EosDIS environment. This version of the Level 2 Requirements Document follows an earlier release of a preliminary draft version. The sections on functional and performance requirements do not yet fully represent the requirements of the data system needed to achieve the scientific objectives of the MODIS instruments and science teams. Indeed, the team members have not yet been selected and the team has not yet been formed; however, it has been possible to identify many relevant requirements based on the present concept of EosDIS and through interviews and meetings with key members of the scientific community. These requirements have been grouped by functional component of the data system, and by function within each component. These requirements have been merged with the complete set of Level 1 and Level 2 context diagrams, data flow diagrams, and data dictionary.

The Importance of Information Requirements in Designing Acquisition to Information Systems

NASA Technical Reports Server (NTRS)

Davis, Bruce A.; Hill, Chuck; Maughan, Paul M.

1998-01-01

The partnership model used by NASA's Commercial Remote Sensing Program has been successful in better defining remote sensing functional requirements and translation to technical specifications to address environmental needs of the 21st century.

32 CFR 154.18 - Certain positions not necessarily requiring access to classified information.

Code of Federal Regulations, 2013 CFR

2013-07-01

... to meet the high standards required. At a minimum, all such personnel shall have had a favorably... information systems may be assigned to one of three position sensitivity designations (in accordance with...

32 CFR 154.18 - Certain positions not necessarily requiring access to classified information.

Code of Federal Regulations, 2014 CFR

2014-07-01

... to meet the high standards required. At a minimum, all such personnel shall have had a favorably... information systems may be assigned to one of three position sensitivity designations (in accordance with...

An integrated approach to system design, reliability, and diagnosis

NASA Technical Reports Server (NTRS)

Patterson-Hine, F. A.; Iverson, David L.

1990-01-01

The requirement for ultradependability of computer systems in future avionics and space applications necessitates a top-down, integrated systems engineering approach for design, implementation, testing, and operation. The functional analyses of hardware and software systems must be combined by models that are flexible enough to represent their interactions and behavior. The information contained in these models must be accessible throughout all phases of the system life cycle in order to maintain consistency and accuracy in design and operational decisions. One approach being taken by researchers at Ames Research Center is the creation of an object-oriented environment that integrates information about system components required in the reliability evaluation with behavioral information useful for diagnostic algorithms. Procedures have been developed at Ames that perform reliability evaluations during design and failure diagnoses during system operation. These procedures utilize information from a central source, structured as object-oriented fault trees. Fault trees were selected because they are a flexible model widely used in aerospace applications and because they give a concise, structured representation of system behavior. The utility of this integrated environment for aerospace applications in light of our experiences during its development and use is described. The techniques for reliability evaluation and failure diagnosis are discussed, and current extensions of the environment and areas requiring further development are summarized.

An integrated approach to system design, reliability, and diagnosis

NASA Astrophysics Data System (ADS)

Patterson-Hine, F. A.; Iverson, David L.

1990-12-01

The requirement for ultradependability of computer systems in future avionics and space applications necessitates a top-down, integrated systems engineering approach for design, implementation, testing, and operation. The functional analyses of hardware and software systems must be combined by models that are flexible enough to represent their interactions and behavior. The information contained in these models must be accessible throughout all phases of the system life cycle in order to maintain consistency and accuracy in design and operational decisions. One approach being taken by researchers at Ames Research Center is the creation of an object-oriented environment that integrates information about system components required in the reliability evaluation with behavioral information useful for diagnostic algorithms. Procedures have been developed at Ames that perform reliability evaluations during design and failure diagnoses during system operation. These procedures utilize information from a central source, structured as object-oriented fault trees. Fault trees were selected because they are a flexible model widely used in aerospace applications and because they give a concise, structured representation of system behavior. The utility of this integrated environment for aerospace applications in light of our experiences during its development and use is described. The techniques for reliability evaluation and failure diagnosis are discussed, and current extensions of the environment and areas requiring further development are summarized.

TERSSE: Definition of the Total Earth Resources System for the Shuttle Era. Volume 5: Detailed system requirements: Two case studies

NASA Technical Reports Server (NTRS)

1974-01-01

Major resource management missions to be performed by the TERSSE are examined in order to develop an understanding of the form and function of a system designed to perform an operational mission. Factors discussed include: resource manager (user) functions, methods of performing their function, the information flows and information requirements embodied in their function, and the characteristics of the observation system which assists in the management of the resource involved. The missions selected for study are: world crop survey and land resources management. These missions are found to represent opposite ends of the TERSSE spectrum and to support the conclusion that different missions require different systems and must be analyzed in detail to permit proper system development decisions.

Combining cognitive engineering and information fusion architectures to build effective joint systems

NASA Astrophysics Data System (ADS)

Sliva, Amy L.; Gorman, Joe; Voshell, Martin; Tittle, James; Bowman, Christopher

2016-05-01

The Dual Node Decision Wheels (DNDW) architecture concept was previously described as a novel approach toward integrating analytic and decision-making processes in joint human/automation systems in highly complex sociotechnical settings. In this paper, we extend the DNDW construct with a description of components in this framework, combining structures of the Dual Node Network (DNN) for Information Fusion and Resource Management with extensions on Rasmussen's Decision Ladder (DL) to provide guidance on constructing information systems that better serve decision-making support requirements. The DNN takes a component-centered approach to system design, decomposing each asset in terms of data inputs and outputs according to their roles and interactions in a fusion network. However, to ensure relevancy to and organizational fitment within command and control (C2) processes, principles from cognitive systems engineering emphasize that system design must take a human-centered systems view, integrating information needs and decision making requirements to drive the architecture design and capabilities of network assets. In the current work, we present an approach for structuring and assessing DNDW systems that uses a unique hybrid DNN top-down system design with a human-centered process design, combining DNN node decomposition with artifacts from cognitive analysis (i.e., system abstraction decomposition models, decision ladders) to provide work domain and task-level insights at different levels in an example intelligence, surveillance, and reconnaissance (ISR) system setting. This DNDW structure will ensure not only that the information fusion technologies and processes are structured effectively, but that the resulting information products will align with the requirements of human decision makers and be adaptable to different work settings .

Analysis of data systems requirements for global crop production forecasting in the 1985 time frame

NASA Technical Reports Server (NTRS)

Downs, S. W.; Larsen, P. A.; Gerstner, D. A.

1978-01-01

Data systems concepts that would be needed to implement the objective of the global crop production forecasting in an orderly transition from experimental to operational status in the 1985 time frame were examined. Information needs of users were converted into data system requirements, and the influence of these requirements on the formulation of a conceptual data system was analyzed. Any potential problem areas in meeting these data system requirements were identified in an iterative process.

Natural Resource Information System. Volume 1: Overall description

NASA Technical Reports Server (NTRS)

1972-01-01

A prototype computer-based Natural Resource Information System was designed which could store, process, and display data of maximum usefulness to land management decision making. The system includes graphic input and display, the use of remote sensing as a data source, and it is useful at multiple management levels. A survey established current decision making processes and functions, information requirements, and data collection and processing procedures. The applications of remote sensing data and processing requirements were established. Processing software was constructed and a data base established using high-altitude imagery and map coverage of selected areas of SE Arizona. Finally a demonstration of system processing functions was conducted utilizing material from the data base.

Transparent Information Systems through Gateways, Front Ends, Intermediaries, and Interfaces.

ERIC Educational Resources Information Center

Williams, Martha E.

1986-01-01

Provides overview of design requirements for transparent information retrieval (implies that user sees through complexity of retrieval activities sequence). Highlights include need for transparent systems; history of transparent retrieval research; information retrieval functions (automated converters, routers, selectors, evaluators/analyzers);…

42 CFR 493.1231 - Standard: Confidentiality of patient information.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 42 Public Health 5 2011-10-01 2011-10-01 false Standard: Confidentiality of patient information... AND HUMAN SERVICES (CONTINUED) STANDARDS AND CERTIFICATION LABORATORY REQUIREMENTS Quality System for Nonwaived Testing General Laboratory Systems § 493.1231 Standard: Confidentiality of patient information...

42 CFR 493.1231 - Standard: Confidentiality of patient information.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 42 Public Health 5 2012-10-01 2012-10-01 false Standard: Confidentiality of patient information... AND HUMAN SERVICES (CONTINUED) STANDARDS AND CERTIFICATION LABORATORY REQUIREMENTS Quality System for Nonwaived Testing General Laboratory Systems § 493.1231 Standard: Confidentiality of patient information...

42 CFR 493.1231 - Standard: Confidentiality of patient information.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 42 Public Health 5 2014-10-01 2014-10-01 false Standard: Confidentiality of patient information... AND HUMAN SERVICES (CONTINUED) STANDARDS AND CERTIFICATION LABORATORY REQUIREMENTS Quality System for Nonwaived Testing General Laboratory Systems § 493.1231 Standard: Confidentiality of patient information...

42 CFR 493.1231 - Standard: Confidentiality of patient information.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 42 Public Health 5 2013-10-01 2013-10-01 false Standard: Confidentiality of patient information... AND HUMAN SERVICES (CONTINUED) STANDARDS AND CERTIFICATION LABORATORY REQUIREMENTS Quality System for Nonwaived Testing General Laboratory Systems § 493.1231 Standard: Confidentiality of patient information...

49 CFR 535.8 - Reporting requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... information. (2) Manufacturers must submit information electronically through the EPA database system as the... year 2012 the agencies are not prepared to receive information through the EPA database system... applications for certificates of conformity in accordance through the EPA database including both GHG emissions...

[Measures to prevent patient identification errors in blood collection/physiological function testing utilizing a laboratory information system].

PubMed

Shimazu, Chisato; Hoshino, Satoshi; Furukawa, Taiji

2013-08-01

We constructed an integrated personal identification workflow chart using both bar code reading and an all in-one laboratory information system. The information system not only handles test data but also the information needed for patient guidance in the laboratory department. The reception terminals at the entrance, displays for patient guidance and patient identification tools at blood-sampling booths are all controlled by the information system. The number of patient identification errors was greatly reduced by the system. However, identification errors have not been abolished in the ultrasound department. After re-evaluation of the patient identification process in this department, we recognized that the major reason for the errors came from excessive identification workflow. Ordinarily, an ultrasound test requires patient identification 3 times, because 3 different systems are required during the entire test process, i.e. ultrasound modality system, laboratory information system and a system for producing reports. We are trying to connect the 3 different systems to develop a one-time identification workflow, but it is not a simple task and has not been completed yet. Utilization of the laboratory information system is effective, but is not yet perfect for patient identification. The most fundamental procedure for patient identification is to ask a person's name even today. Everyday checks in the ordinary workflow and everyone's participation in safety-management activity are important for the prevention of patient identification errors.

Managing the Security of Nursing Data in the Electronic Health Record

PubMed Central

Samadbeik, Mahnaz; Gorzin, Zahra; Khoshkam, Masomeh; Roudbari, Masoud

2015-01-01

Background: The Electronic Health Record (EHR) is a patient care information resource for clinicians and nursing documentation is an essential part of comprehensive patient care. Ensuring privacy and the security of health information is a key component to building the trust required to realize the potential benefits of electronic health information exchange. This study was aimed to manage nursing data security in the EHR and also discover the viewpoints of hospital information system vendors (computer companies) and hospital information technology specialists about nursing data security. Methods: This research is a cross sectional analytic-descriptive study. The study populations were IT experts at the academic hospitals and computer companies of Tehran city in Iran. Data was collected by a self-developed questionnaire whose validity and reliability were confirmed using the experts’ opinions and Cronbach’s alpha coefficient respectively. Data was analyzed through Spss Version 18 and by descriptive and analytic statistics. Results: The findings of the study revealed that user name and password were the most important methods to authenticate the nurses, with mean percent of 95% and 80%, respectively, and also the most significant level of information security protection were assigned to administrative and logical controls. There was no significant difference between opinions of both groups studied about the levels of information security protection and security requirements (p>0.05). Moreover the access to servers by authorized people, periodic security update, and the application of authentication and authorization were defined as the most basic security requirements from the viewpoint of more than 88 percent of recently-mentioned participants. Conclusions: Computer companies as system designers and hospitals information technology specialists as systems users and stakeholders present many important views about security requirements for EHR systems and nursing electronic documentation systems. Prioritizing of these requirements helps policy makers to decide what to do when planning for EHR implementation. Therefore, to make appropriate security decisions and to achieve the expected level of protection of the electronic nursing information, it is suggested to consider the priorities of both groups of experts about security principles and also discuss the issues seem to be different between two groups of participants in the research. PMID:25870490

Managing the security of nursing data in the electronic health record.

PubMed

Samadbeik, Mahnaz; Gorzin, Zahra; Khoshkam, Masomeh; Roudbari, Masoud

2015-02-01

The Electronic Health Record (EHR) is a patient care information resource for clinicians and nursing documentation is an essential part of comprehensive patient care. Ensuring privacy and the security of health information is a key component to building the trust required to realize the potential benefits of electronic health information exchange. This study was aimed to manage nursing data security in the EHR and also discover the viewpoints of hospital information system vendors (computer companies) and hospital information technology specialists about nursing data security. This research is a cross sectional analytic-descriptive study. The study populations were IT experts at the academic hospitals and computer companies of Tehran city in Iran. Data was collected by a self-developed questionnaire whose validity and reliability were confirmed using the experts' opinions and Cronbach's alpha coefficient respectively. Data was analyzed through Spss Version 18 and by descriptive and analytic statistics. The findings of the study revealed that user name and password were the most important methods to authenticate the nurses, with mean percent of 95% and 80%, respectively, and also the most significant level of information security protection were assigned to administrative and logical controls. There was no significant difference between opinions of both groups studied about the levels of information security protection and security requirements (p>0.05). Moreover the access to servers by authorized people, periodic security update, and the application of authentication and authorization were defined as the most basic security requirements from the viewpoint of more than 88 percent of recently-mentioned participants. Computer companies as system designers and hospitals information technology specialists as systems users and stakeholders present many important views about security requirements for EHR systems and nursing electronic documentation systems. Prioritizing of these requirements helps policy makers to decide what to do when planning for EHR implementation. Therefore, to make appropriate security decisions and to achieve the expected level of protection of the electronic nursing information, it is suggested to consider the priorities of both groups of experts about security principles and also discuss the issues seem to be different between two groups of participants in the research.

Functional requirements document for NASA/MSFC Earth Science and Applications Division: Data and information system (ESAD-DIS). Interoperability, 1992

NASA Technical Reports Server (NTRS)

Stephens, J. Briscoe; Grider, Gary W.

1992-01-01

These Earth Science and Applications Division-Data and Information System (ESAD-DIS) interoperability requirements are designed to quantify the Earth Science and Application Division's hardware and software requirements in terms of communications between personal and visualization workstation, and mainframe computers. The electronic mail requirements and local area network (LAN) requirements are addressed. These interoperability requirements are top-level requirements framed around defining the existing ESAD-DIS interoperability and projecting known near-term requirements for both operational support and for management planning. Detailed requirements will be submitted on a case-by-case basis. This document is also intended as an overview of ESAD-DIs interoperability for new-comers and management not familiar with these activities. It is intended as background documentation to support requests for resources and support requirements.

Generalized Information Architecture for Managing Requirements in IBM?s Rational DOORS(r) Application.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Aragon, Kathryn M.; Eaton, Shelley M.; McCornack, Marjorie Turner

When a requirements engineering effort fails to meet expectations, often times the requirements management tool is blamed. Working with numerous project teams at Sandia National Laboratories over the last fifteen years has shown us that the tool is rarely the culprit; usually it is the lack of a viable information architecture with well- designed processes to support requirements engineering. This document illustrates design concepts with rationale, as well as a proven information architecture to structure and manage information in support of requirements engineering activities for any size or type of project. This generalized information architecture is specific to IBM's Rationalmore » DOORS (Dynamic Object Oriented Requirements System) software application, which is the requirements management tool in Sandia's CEE (Common Engineering Environment). This generalized information architecture can be used as presented or as a foundation for designing a tailored information architecture for project-specific needs. It may also be tailored for another software tool. Version 1.0 4 November 201« less

Medical-Information-Management System

NASA Technical Reports Server (NTRS)

Alterescu, Sidney; Friedman, Carl A.; Frankowski, James W.

1989-01-01

Medical Information Management System (MIMS) computer program interactive, general-purpose software system for storage and retrieval of information. Offers immediate assistance where manipulation of large data bases required. User quickly and efficiently extracts, displays, and analyzes data. Used in management of medical data and handling all aspects of data related to care of patients. Other applications include management of data on occupational safety in public and private sectors, handling judicial information, systemizing purchasing and procurement systems, and analyses of cost structures of organizations. Written in Microsoft FORTRAN 77.

Long-term care information systems: an overview of the selection process.

PubMed

Nahm, Eun-Shim; Mills, Mary Etta; Feege, Barbara

2006-06-01

Under the current Medicare Prospective Payment System method and the ever-changing managed care environment, the long-term care information system is vital to providing quality care and to surviving in business. system selection process should be an interdisciplinary effort involving all necessary stakeholders for the proposed system. The system selection process can be modeled following the Systems Developmental Life Cycle: identifying problems, opportunities, and objectives; determining information requirements; analyzing system needs; designing the recommended system; and developing and documenting software.

The Bartlesville System; TGISS Software Documentation.

ERIC Educational Resources Information Center

Roberts, Tommy L.; And Others

TGISS (Total Guidance Information Support System) is an information storage and retrieval system specifically designed to meet the needs and requirements of a counselor in the Bartlesville Public School environment. The system, which is a combination of man/machine capabilities, includes the hardware and software necessary to extend the…

SYSTEMS ANALYSIS - MILITARY PERSONNEL AUTHORIZED VERSUS ON HAND

DTIC Science & Technology

The purpose of the report is to describe the systems analysis required to produce information on ’Military Personnel, Authorized Versus On Hand,’ for LMI R1 during the period of manual operation of the USAREUR Logistics Management Information System.

Step 1: Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Command, Control, and Communications (C3)

NASA Technical Reports Server (NTRS)

2005-01-01

The document provides the Human System Integration(HSI) high-level functional C3 HSI requirements for the interface to the pilot. Description includes (1) the information required by the pilot to have knowledge C3 system status, and (2) the control capability needed by the pilot to obtain C3 information. Fundamentally, these requirements provide the candidate C3 technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how C3 operations and functions should interface with the pilot to provide the necessary C3 functionality to the UA-pilot system. Requirements and guidelines for C3 are partitioned into three categories: (1) Pilot-Air Traffic Control (ATC) Voice Communications (2) Pilot-ATC Data Communications, and (3) command and control of the unmanned aircraft (UA). Each requirement is stated and is supported with a rationale and associated reference(s).

Digital Avionics Information System (DAIS): Training Requirements Analysis Model Users Guide. Final Report.

ERIC Educational Resources Information Center

Czuchry, Andrew J.; And Others

This user's guide describes the functions, logical operations and subroutines, input data requirements, and available outputs of the Training Requirements Analysis Model (TRAMOD), a computerized analytical life cycle cost modeling system for use in the early stages of system design. Operable in a stand-alone mode, TRAMOD can be used for the…

75 FR 24945 - Agency Information Collection Activities; Submission to OMB for Review and Approval; Comment...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-05-06

... Emission Standards for Hazardous Air Pollutants (NESHAP) for Mineral Wool Production (40 CFR part 63... wool production plants are required to install fabric filter bag leak detection systems and then... Air Act. The required information consists of emissions data and other information that have been...

Hospital information management system: an evolutionary knowledge management perspective.

PubMed

Wadhwa, S; Saxena, Avneet; Wadhwa, Bharat

2007-01-01

The evolving paradigm shift resulting from IT, social and technological changes has created a need for developing an innovative knowledge-based healthcare system, which can effectively meet global healthcare system demands and also cater to future trends. The Hospital Information Management System (HIMS) is developed with this sole aim in mind, which helps in processing and management of hospital information not only inside the boundary, but also beyond the hospital boundary, e.g., telemedicine or e-healthcare. The purpose of this paper is to present such kind of functional HIMS, which can efficiently satisfy the current and future system requirements by using Knowledge Management (KM) and data management systems. The HIMS is developed in a KM context, wherein users can share and use the knowledge more effectively. The proposed system is fully compatible with future technical, social, managerial and economical requirements.

Implementing Information Assurance - Beyond Process

DTIC Science & Technology

2009-01-01

disabled or properly configured. Tools and scripts are available to expedite the configuration process on some platforms, For example, approved Windows...in the System Security Plan (SSP) or Information Security Plan (lSP). Any PPSs not required for operation by the system must be disabled , This...Services must be disabled , Implementing an 1M capability within the boundary carries many policy and documentation requirements. Usemame and passwords

Strategic planning for health care management information systems.

PubMed

Rosenberger, H R; Kaiser, K M

1985-01-01

Using a planning methodology and a structured design technique for analyzing data and data flow, information requirements can be derived to produce a strategic plan for a management information system. Such a long-range plan classifies information groups and assigns them priorities according to the goals of the organization. The approach emphasizes user involvement.

Report: EPA’s Information Systems and Data Are at Risk Due to Insufficient Training of Personnel With Significant Information Security Responsibilities

EPA Pesticide Factsheets

Report #14-P-0142, March 21, 2014. The EPA places its information systems and data at risk due to an organizational structure that has not specified required duties and responsibilities to ensure personnel are trained on key information security roles.

77 FR 1640 - Federal Acquisition Regulation; Public Access to the Federal Awardee Performance and Integrity...

Federal Register 2010, 2011, 2012, 2013, 2014

2012-01-11

... Performance and Integrity Information System; Correction AGENCY: Department of Defense (DoD), General Services... requires that the information in the Federal Awardee Performance and Integrity Information System (FAPIIS.... With regard to information entered by the Government into FAPIIS on and after January 17, 2012-- (1...

Diffusion and utilization of scientific and technological knowledge within state and local governments: Executive summary

NASA Technical Reports Server (NTRS)

Feller, I.; Flanary, P. E.

1979-01-01

The requirements for technology transfer among the state and local governments are analyzed. Topics discussed include: information systems, federal funding, delivery channels, state executive programs, and state legislature requirements for scientific information.

Health Care Financing Administration--Medicaid program; Medicaid management information systems. Final rule.

PubMed

1980-03-05

These regulations set forth a new procedure to improve Medicaid management by explicitly authorizing HCFA to expand or revise State Medicaid Management Information Systems (MMIS) as necessary to meet program needs. Under this procedure, HCFA will publish major new requirements for comment before deciding to adopt them, and will provide increased Federal matching and reasonable phase-in time for their implementation. HCFA will also periodically review ongoing systems to determine whether all system requirements and performance standards are being met and may reduce the level of Federal matching for those MMIS systems which do not meet prescribed standards.

Model tracking system for low-level radioactive waste disposal facilities: License application interrogatories and responses

DOE Office of Scientific and Technical Information (OSTI.GOV)

Benbennick, M.E.; Broton, M.S.; Fuoto, J.S.

This report describes a model tracking system for a low-level radioactive waste (LLW) disposal facility license application. In particular, the model tracks interrogatories (questions, requests for information, comments) and responses. A set of requirements and desired features for the model tracking system was developed, including required structure and computer screens. Nine tracking systems were then reviewed against the model system requirements and only two were found to meet all requirements. Using Kepner-Tregoe decision analysis, a model tracking system was selected.

78 FR 79058 - Proposed Information Collection Request; Notice of New Requirements and Procedures for Grant...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-12-27

...The DOT invites the public and other Federal agencies to comment on a revision to a previously approved information collection concerning new requirements and procedures for grant payment request submission. DOT will submit the proposed renewal of information collection request to the Office of Management and Budget (OMB) for review, as required by the Paperwork Reduction Act of 1995 (PRA) (44 U.S.C. 3506 (c)(2)(A)). This notice sets forth new requirements and procedures for grantees that submit and receive payments from DOT Operating Administrations (OAs).\\1\\ DOT is updating systems that support grant payments and there will be changes to the way grantees complete and submit payment requests. Simplifying the DOT grant payment process will save both the grantee and the Federal Government time and expense that come with paper-based grant application and payment administration. Note: At this time, this requirement is not applicable to DOT grant recipients requesting payment electronically through the National Highway Traffic Safety Administration's Grant Tracking System (GTS), the Federal Highway Administration's Rapid Approval State Payment System (RASPS), or Federal Transit Administration (FTA) grant recipients requesting payment through the Electronic Clearing House Operation System (ECHO-Web). ---------------------------------------------------------------------------

Using the Work System Method with Freshman Information Systems Students

ERIC Educational Resources Information Center

Recker, Jan; Alter, Steven

2012-01-01

Recent surveys of information technology management professionals show that understanding business domains in terms of business productivity and cost reduction potential, knowledge of different vertical industry segments and their information requirements, understanding of business processes and client-facing skills are more critical for…

7 CFR 400.683 - Administration and maintenance.

Code of Federal Regulations, 2010 CFR

2010-01-01

... any program pursuant to this subpart. This system contains identifying information of the ineligible... ineligibility, and time period for ineligibility. (2) Information in the Ineligible Tracking System may be used... require such information in the performance of their duties in connection with any program administered...

78 FR 23935 - Federal Acquisition Regulation; Information Collection; Contractor Use of Interagency Fleet...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-04-23

...; Information Collection; Contractor Use of Interagency Fleet Management System Vehicles AGENCY: Department of... previously approved information collection requirement concerning contractor use of interagency fleet... Collection 9000- 0032, Contractor Use of Interagency Fleet Management System Vehicles, by any of the...

78 FR 54954 - Reports, Forms, and Record Keeping Requirements

Federal Register 2010, 2011, 2012, 2013, 2014

2013-09-06

... assumptions used; (iii) How to enhance the quality, utility, and clarity of the information to be collected... information: Title: National Automotive Sampling System (NASS) Law Enforcement Information Type of Request.... NHTSA's National Automotive Sampling System (NASS) collects crash data on a nationally representative...

Towards a Methodology for Identifying Program Constraints During Requirements Analysis

NASA Technical Reports Server (NTRS)

Romo, Lilly; Gates, Ann Q.; Della-Piana, Connie Kubo

1997-01-01

Requirements analysis is the activity that involves determining the needs of the customer, identifying the services that the software system should provide and understanding the constraints on the solution. The result of this activity is a natural language document, typically referred to as the requirements definition document. Some of the problems that exist in defining requirements in large scale software projects includes synthesizing knowledge from various domain experts and communicating this information across multiple levels of personnel. One approach that addresses part of this problem is called context monitoring and involves identifying the properties of and relationships between objects that the system will manipulate. This paper examines several software development methodologies, discusses the support that each provide for eliciting such information from experts and specifying the information, and suggests refinements to these methodologies.

The Potential Impact of Offshore Outsourcing on Information Systems Education Programs

ERIC Educational Resources Information Center

Pollack, Thomas A.

2004-01-01

As recently as the 1999-2000 academic year, the most sought after graduates were those completing degree requirements in a wide variety of information systems based programs. Many graduates were enticed by lucrative signing bonuses as organizations prepared for the dreaded uncertainty of Y2K. Information systems and computer science programs and…

Information System Life-Cycle And Documentation Standards (SMAP DIDS)

NASA Technical Reports Server (NTRS)

1990-01-01

Although not computer program, SMAP DIDS written to provide systematic, NASA-wide structure for documenting information system development projects. Each DID (data item description) outlines document required for top-quality software development. When combined with management, assurance, and life cycle standards, Standards protect all parties who participate in design and operation of new information system.

Enhancing the Graduate Information Systems Curriculum: A Career Skills Oriented Approach

ERIC Educational Resources Information Center

Khoo, Benjamin; Harris, Peter

2009-01-01

The Information Systems (IS) curriculum needs to be updated frequently due to the rapid rate of advances in information systems (IS) and the technologies that drive IS, and also industry's skill requirement of IS graduates. This paper describes a Career Skills Oriented Approach to enhance the graduate IS curriculum based on current information…

A Computerized Information System Model for Decision Making for the Oklahoma State Department of Vocational and Technical Education.

ERIC Educational Resources Information Center

Smith, Hubert Gene

The objectives of the study presented in the dissertation were to identify present and anticipated information requirements of the various departments within the Oklahoma State Department of Vocational and Technical Education, to design a computerized information system model utilizing an integrated systems concept to meet information…

Knowing the Score. A National Review of the State and Territory Training Authority Statistical Systems. Final Report.

ERIC Educational Resources Information Center

National Centre for Vocational Education Research, Leabrook (Australia).

This report presents results of a project to produce a set of strategies to ensure the compatibility of Australian state and territory information systems with the requirements of the National Management Information and Statistics System (NATMISS) and the Australian Vocational Education and Training Management Information Statistical Standard…

Solid waste information and tracking system server conversion project management plan

DOE Office of Scientific and Technical Information (OSTI.GOV)

MAY, D.L.

1999-04-12

The Project Management Plan governing the conversion of Solid Waste Information and Tracking System (SWITS) to a client-server architecture. The Solid Waste Information and Tracking System Project Management Plan (PMP) describes the background, planning and management of the SWITS conversion. Requirements and specification documentation needed for the SWITS conversion will be released as supporting documents.

Management Information Systems for Faculty Allocations in Institutions of Higher Education: A Case Study for the Universidad de Santiago de Chile.

ERIC Educational Resources Information Center

Karadima, Oscar

The transformation of the present manual system of data manipulation at the Universidad de Santiago de Chile into a computer-based information system capable of supporting decision making is proposed. The information system would be used to determine the number of faculty required by each academic department, based on the number of weekly hours…

System Support/Sustainment Plan Platform for the Defense Enterprise Accounting Management System (DEAMS)

DTIC Science & Technology

2006-12-01

warfighters requirements and identifies system performance short-comings over its life cycle. 15. NUMBER OF PAGES 89 14. SUBJECT TERMS Information...the system performs to warfighters requirements and identifies system performance short-comings over its life cycle. vi...3 II. DEFENSE ACQUISITION LIFE CYCLE CURRENT STAGE ANALYSIS.......5 A. INTRODUCTION

Requirements for company-wide management

NASA Technical Reports Server (NTRS)

Southall, J. W.

1980-01-01

Computing system requirements were developed for company-wide management of information and computer programs in an engineering data processing environment. The requirements are essential to the successful implementation of a computer-based engineering data management system; they exceed the capabilities provided by the commercially available data base management systems. These requirements were derived from a study entitled The Design Process, which was prepared by design engineers experienced in development of aerospace products.

Concepts for a global resources information system

NASA Technical Reports Server (NTRS)

Billingsley, F. C.; Urena, J. L.

1984-01-01

The objective of the Global Resources Information System (GRIS) is to establish an effective and efficient information management system to meet the data access requirements of NASA and NASA-related scientists conducting large-scale, multi-disciplinary, multi-mission scientific investigations. Using standard interfaces and operating guidelines, diverse data systems can be integrated to provide the capabilities to access and process multiple geographically dispersed data sets and to develop the necessary procedures and algorithms to derive global resource information.

75 FR 62098 - Proposed Information Collection; Comment Request; Expanded Vessel Monitoring System Requirement...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-10-07

... Collection; Comment Request; Expanded Vessel Monitoring System Requirement in the Pacific Coast Groundfish... and use a vessel monitoring system (VMS) that automatically sends hourly position reports. Exemptions... declaration reporting system are not expected to change the public reporting burden. II. Method of Collection...

Earth Sciences Data and Information System (ESDIS) program planning and evaluation methodology development

NASA Technical Reports Server (NTRS)

Dickinson, William B.

1995-01-01

An Earth Sciences Data and Information System (ESDIS) Project Management Plan (PMP) is prepared. An ESDIS Project Systems Engineering Management Plan (SEMP) consistent with the developed PMP is also prepared. ESDIS and related EOS program requirements developments, management and analysis processes are evaluated. Opportunities to improve the effectiveness of these processes and program/project responsiveness to requirements are identified. Overall ESDIS cost estimation processes are evaluated, and recommendations to improve cost estimating and modeling techniques are developed. ESDIS schedules and scheduling tools are evaluated. Risk assessment, risk mitigation strategies and approaches, and use of risk information in management decision-making are addressed.

[Development method of healthcare information system integration based on business collaboration model].

PubMed

Li, Shasha; Nie, Hongchao; Lu, Xudong; Duan, Huilong

2015-02-01

Integration of heterogeneous systems is the key to hospital information construction due to complexity of the healthcare environment. Currently, during the process of healthcare information system integration, people participating in integration project usually communicate by free-format document, which impairs the efficiency and adaptability of integration. A method utilizing business process model and notation (BPMN) to model integration requirement and automatically transforming it to executable integration configuration was proposed in this paper. Based on the method, a tool was developed to model integration requirement and transform it to integration configuration. In addition, an integration case in radiology scenario was used to verify the method.

Establishment of Requirements and Methodology for the Development and Implementation of GreyMatters, a Memory Clinic Information System.

PubMed

Tapuria, Archana; Evans, Matt; Curcin, Vasa; Austin, Tony; Lea, Nathan; Kalra, Dipak

2017-01-01

The aim of the paper is to establish the requirements and methodology for the development process of GreyMatters, a memory clinic system, outlining the conceptual, practical, technical and ethical challenges, and the experiences of capturing clinical and research oriented data along with the implementation of the system. The methodology for development of the information system involved phases of requirements gathering, modeling and prototype creation, and 'bench testing' the prototype with experts. The standard Institute of Electrical and Electronics Engineers (IEEE) recommended approach for the specifications of software requirements was adopted. An electronic health record (EHR) standard, EN13606 was used, and clinical modelling was done through archetypes and the project complied with data protection and privacy legislation. The requirements for GreyMatters were established. Though the initial development was complex, the requirements, methodology and standards adopted made the construction, deployment, adoption and population of a memory clinic and research database feasible. The electronic patient data including the assessment scales provides a rich source of objective data for audits and research and to establish study feasibility and identify potential participants for the clinical trials. The establishment of requirements and methodology, addressing issues of data security and confidentiality, future data compatibility and interoperability and medico-legal aspects such as access controls and audit trails, led to a robust and useful system. The evaluation supports that the system is an acceptable tool for clinical, administrative, and research use and forms a useful part of the wider information architecture.

14 CFR 1212.605 - Safeguarding information in systems of records.

Code of Federal Regulations, 2010 CFR

2010-01-01

... requirements applicable to the system of records. (c) When records or copies of records are distributed to... 14 Aeronautics and Space 5 2010-01-01 2010-01-01 false Safeguarding information in systems of... systems of records. (a) Safeguards appropriate for a NASA system of records shall be developed by the...

Information/Knowledge Acquisition Methods for Decision Support Systems and Expert Systems.

ERIC Educational Resources Information Center

Yang, Heng-Li

1995-01-01

Compares information requirement-elicitation (IRE) methods for decision support systems (DSS) with knowledge acquisition (KA) methods for expert systems (ES) development. The definition and architectures of ES and DSS are compared and the systems' development cycles and IRE/KA methods are discussed. Differences are noted between ES and DSS…

Drainage information analysis and mapping system.

DOT National Transportation Integrated Search

2012-10-01

The primary objective of this research is to develop a Drainage Information Analysis and Mapping System (DIAMS), with online inspection : data submission, which will comply with the necessary requirements, mandated by both the Governmental Accounting...

Software Development With Application Generators: The Naval Aviation Logistics Command Management Information System Case

DTIC Science & Technology

1992-09-01

Aviation Logistics Command Management Information System (NALCOMIS) prototyping development effort, the critical success factors required to implement prototyping with application generators in other areas of DoD.

Facilitating access to information in large documents with an intelligent hypertext system

NASA Technical Reports Server (NTRS)

Mathe, Nathalie

1993-01-01

Retrieving specific information from large amounts of documentation is not an easy task. It could be facilitated if information relevant in the current problem solving context could be automatically supplied to the user. As a first step towards this goal, we have developed an intelligent hypertext system called CID (Computer Integrated Documentation) and tested it on the Space Station Freedom requirement documents. The CID system enables integration of various technical documents in a hypertext framework and includes an intelligent context-sensitive indexing and retrieval mechanism. This mechanism utilizes on-line user information requirements and relevance feedback either to reinforce current indexing in case of success or to generate new knowledge in case of failure. This allows the CID system to provide helpful responses, based on previous usage of the documentation, and to improve its performance over time.

78 FR 58286 - Proposed Information Collection; Comment Request; Western Region Vessel Monitoring System and Pre...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-09-23

... Collection; Comment Request; Western Region Vessel Monitoring System and Pre-Trip Reporting Requirements... information or new problems in the fisheries. Vessel Monitoring System (VMS) units will facilitate enforcement... monitoring system (VMS) activation reports, 15 minutes; pre-trip reports, 5 minutes. Estimated Burden Hours...

Utilizing findings from the APACHE III research to develop operational information system for the ICU--the APACHE III ICU Management System.

PubMed Central

Knaus, W. A.; Draper, E. A.; Wagner, D. P.

1991-01-01

The APACHE III data base reflects the disease, physiologic status, and outcome data from 17,400 ICU patients at 40 hospitals, 26 of which were randomly selected from representative geographic regions, bed size, and teaching status. This provides a nationally representative standard for measuring several important aspects of ICU performance. Results from the study have now been used to develop an automated information system to provide real time information about expected ICU patient outcome, length of stay, production cost, and ICU performance. The information system provides several new capabilities to ICU clinicians, clinic, and hospital administrators. Among the system's capabilities are: the ability to compare local ICU performance against predetermined criteria; the ability to forecast nursing requirements; and, the ability to make both individual and group patient outcome predictions. The system also provides improved administrative support by tracking ICU charges at the point of origin and reduces staff workload eliminating the requirement for several manually maintained logs and patient lists. APACHE III has the capability to electronically interface with and utilize data already captured in existing hospital information systems, automated laboratory information systems, and patient monitoring systems. APACHE III will also be completely integrated with several CIS vendors' products. PMID:1807779

System requirements and benefits of a terminal information system for the Kansas City railroads

DOT National Transportation Integrated Search

1976-08-31

The Kansas City Terminal Railway Company proposed that the Federal Railroad Administration assist in funding the implementation of a Terminal Information and Message Exchange system (TIME), designed to enhance the operations of the twelve railroads i...

40 CFR 265.1064 - Recordkeeping requirements.

Code of Federal Regulations, 2010 CFR

2010-07-01

... waste management units in one recordkeeping system if the system identifies each record by each...) Design documentation and monitoring, operating, and inspection information for each closed-vent system...) An up-to-date analysis and the supporting information and data used to determine whether or not...

Research and development for Onboard Navigation (ONAV) ground based expert/trainer system: ONAV entry knowledge requirements specification update

NASA Technical Reports Server (NTRS)

Bochsler, Daniel C.

1988-01-01

A revised version of expert knowledge for the onboard navigation (ONAV) entry system is given. Included is some brief background information together with information describing the knowledge that the system does contain.

78 FR 70025 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-11-22

.... Needs and Uses: Administrative contracting officers use this information in making decisions to grant, withhold, or withdraw purchasing system approval at the conclusion of a purchasing system review. Withdrawal of purchasing system approval would necessitate Government consent to individual subcontracts...

Requirements for the Military Message System (MMS) Family: Data Types and User Commands.

DTIC Science & Technology

1986-04-11

AD-A167 126 REQUIREMENTS FOR THE MILITARY MESSASE SYSTEM (NHS) i FRILY: DATA TYPES AND USER CONNNDS(U) NAVAL RESEARCH LAB WASHINGTON DC C L HEITHEVER... System (MMS) Family: Data Types and User Commands CONSTANCE L. HEITMEYER Computer Science and Systems Branch I Information Technology Division April 11...Security Classification) Requirements for the Military Message System (MMS) Family: Data Types and User Commands 12. PERSONAL AUTHOR(S) Heitmeer, Constance

Policy implications in developing a land use management information systems

NASA Technical Reports Server (NTRS)

Landini, A. J.

1975-01-01

The current land use map for the city of Los Angeles was developed by the guesstimation process and provides single stage information for each level in the critical geographical hierarchy for land use planning management. Processing and incorporation of LANDSAT data in the land use information system requires special funding; however, computergraphic maps are able to provide a viable information system for city planning and management.

48 CFR 339.7103 - Solicitation and contract clause.

Code of Federal Regulations, 2010 CFR

2010-10-01

... SPECIAL CATEGORIES OF CONTRACTING ACQUISITION OF INFORMATION TECHNOLOGY Information Security Management...-72, Security Requirements for Federal Information Technology Resources, in solicitations and contracts that involve contractor access to Federal information or Federal information systems. ...

76 FR 35424 - Information Collection Requirements; Defense Federal Acquisition Regulation Supplement...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-06-17

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System Information Collection Requirements; Defense Federal Acquisition Regulation Supplement; Construction and Architect-Engineer Contracts AGENCY..., Construction and Architect-Engineer Contracts, and Related Clauses at DFARS 252.236; OMB Control Number 0704...

75 FR 45104 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-08-02

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System [OMB Control Number 0704-0225] Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Administrative Matters... Supplement (DFARS) Part 204, Administrative Matters, and related clauses at DFARS 252.204; DD Form 2051...

Multidisciplinary approach to successful implementation of production information system (PRISM)

DOE Office of Scientific and Technical Information (OSTI.GOV)

Shariff, M.R.; Gopalakrishnan, S.G.; Francis, N.

1995-12-31

A company wide corporate and regional production database supporting all production areas was envisaged critical to the current expansion within Petronas Carigali Sdn Bhd (PCSB). A multi disciplinary project team was thus formed to analyze the requirements prior to developing, testing, implementing and training users. PCSB has currently evolved into a mature E & P company on par with other E & P companies within the region. This expansion necessitates a common Production Information System for the efficient dissemination of vital Production Information for Production Surveillance, Reservoir Management, Reserve Assessment, Special Studies and Standardized Group-wide Reporting. This paper will discussmore » all the phases involved in the project which includes Systems Requirement Study, Data Migration, System Development, System Implementation and Post-Implementation Plan.« less

An information based approach to improving overhead imagery collection

NASA Astrophysics Data System (ADS)

Sourwine, Matthew J.; Hintz, Kenneth J.

2011-06-01

Recent growth in commercial imaging satellite development has resulted in a complex and diverse set of systems. To simplify this environment for both customer and vendor, an information based sensor management model was built to integrate tasking and scheduling systems. By establishing a relationship between image quality and information, tasking by NIIRS can be utilized to measure the customer's required information content. Focused on a reduction in uncertainty about a target of interest, the sensor manager finds the best sensors to complete the task given the active suite of imaging sensors' functions. This is done through determination of which satellite will meet customer information and timeliness requirements with low likelihood of interference at the highest rate of return.

Proximal—distal pattern formation in Drosophila: cell autonomous requirement for Distal-less gene activity in limb development

PubMed Central

Cohen, Stephen M.; Jürgens, Gerd

1989-01-01

Limb development in the Drosophila embryo requires a pattern-forming system to organize positional information along the proximal–distal axis of the limb. This system must function in the context of the well characterized anterior–posterior and dorsal–ventral pattern-forming systems that are required to organize the body plan of the embryo. By genetic criteria the Distal-less gene appears to play a central role in limb development. Lack-of-function Distal-less mutations cause the deletion of a specific subset of embryonic peripheral sense organs that represent the evolutionary remnants of larval limbs. Distal-less activity is also required in the imaginal discs for the development of adult limbs. This requirement is cell autonomous and region specific within the developing limb primordium. Production of genetically mosaic imaginal discs, in which clones of cells lack Distal-less activity, indicates the existence of an organized proximal–distal positional information in very young imaginal disc primordia. We suggest that this graded positional information may depend on the activity of the Distal-less gene. Images PMID:16453891

Study of data collection platform concepts: Data collection system user requirements

NASA Technical Reports Server (NTRS)

1973-01-01

The overall purpose of the survey was to provide real world data on user requirements. The intent was to assess data collection system user requirements by questioning actual potential users rather than speculating on requirements. The end results of the survey are baseline requirements models for both a data collection platform and a data collection system. These models were derived from the survey results. The real value of these models lies in the fact that they are based on actual user requirements as delineated in the survey questionnaires. Some users desire data collection platforms of small size and light weight. These sizes and weights are beyond the present state of the art. Also, the survey provided a wealth of information on the nature and constituency of the data collection user community as well as information on user applications for data collection systems. Finally, the data sheds light on the generalized platform concept. That is, the diversity of user requirements shown in the data indicates the difficulty that can be anticipated in attempting to implement such a concept.

Data policy and availability supporting global change research, development, and decision-making: An information perspective

NASA Technical Reports Server (NTRS)

Carroll, Bonnie C.; Jack, Robert F.; Cotter, Gladys A.

1990-01-01

An explosion of information has created a crisis for today's information age. It has to be determined how to use the best available information sources, tools, and technology. To do this it is necessary to have leadership at the interagency level to promote a coherent information policy. It is also important to find ways to educate the users of information regarding the tools available to them. Advances in technology resulted in efforts to shift from Disciplinary and Mission-oriented Systems to Decision Support Systems and Personalized Information Systems. One such effort is being made by the Interagency Working Group on Data Management for Global Change (IAWGDMGC). Five federal agencies - the Department of Commerce (DOC), Department of Energy (DOE), National Aeronautics and Space Administration (NASA), National Library of Medicine (NLM), and Department of Defense (DOD) - have an on-going cooperative information management group, CENDI (Commerce, Energy, NASA, NLM, and Defense Information), that is meeting the challenge of coordinating and integrating their information management systems. Although it is beginning to be technically feasible to have a system with text, bibliographic, and numeric data online for the user to manipulate at the user's own workstation, it will require national recognition that the resource investment in such a system is worthwhile, in order to promote its full development. It also requires close cooperation between the producers and users of the information - that is, the research and policy community, and the information community. National resources need to be mobilized in a coordinated manner to move people into the next generation of information support systems.

The Johnson Space Center Management Information Systems (JSCMIS). 1: Requirements Definition and Design Specifications for Versions 2.1 and 2.1.1. 2: Documented Test Scenario Environments. 3: Security Design and Specifications

NASA Technical Reports Server (NTRS)

1986-01-01

The Johnson Space Center Management Information System (JSCMIS) is an interface to computer data bases at NASA Johnson which allows an authorized user to browse and retrieve information from a variety of sources with minimum effort. This issue gives requirements definition and design specifications for versions 2.1 and 2.1.1, along with documented test scenario environments, and security object design and specifications.

Step 1: Human System Integration (HSI) FY05 Pilot-Technology Interface Requirements for Contingency Management

NASA Technical Reports Server (NTRS)

2005-01-01

This document involves definition of technology interface requirements for Contingency Management. This was performed through a review of Contingency Management-related, HSI requirements documents, standards, and recommended practices. Technology concepts in use by the Contingency Management Work Package were considered. Beginning with HSI high-level functional requirements for Contingency Management, and Contingency Management technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge of system failures and associated contingency procedures, and (2) the control capability needed by the pilot to obtain system status and procedure information. Fundamentally, these requirements provide the candidate Contingency Management technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how Contingency Management operations and functions should interface with the pilot to provide the necessary Contingency Management functionality to the UA-pilot system. Requirements and guidelines for Contingency Management are partitioned into four categories: (1) Health and Status and (2) Contingency Management. Each requirement is stated and is supported with a rationale and associated reference(s).

TERSSE: Definition of the Total Earth Resources System for the Shuttle Era. Volume 3: Mission and System Requirements for the Total Earth Resources System

NASA Technical Reports Server (NTRS)

1974-01-01

Resource management missions to be performed by TERSSE are described. Mission and user requirements are defined along with information flows developed for each major resource management mission. Other topics discussed include: remote sensing platforms, remote sensor requirements, ground system architecture, and such related issues as cloud cover, resolution, orbit mechanics, and aircraft versus satellite.

The design of the automated control system for warehouse equipment under radio-electronic manufacturing

NASA Astrophysics Data System (ADS)

Kapulin, D. V.; Chemidov, I. V.; Kazantsev, M. A.

2017-01-01

In the paper, the aspects of design, development and implementation of the automated control system for warehousing under the manufacturing process of the radio-electronic enterprise JSC «Radiosvyaz» are discussed. The architecture of the automated control system for warehousing proposed in the paper consists of a server which is connected to the physically separated information networks: the network with a database server, which stores information about the orders for picking, and the network with the automated storage and retrieval system. This principle allows implementing the requirements for differentiation of access, ensuring the information safety and security requirements. Also, the efficiency of the developed automated solutions in terms of optimizing the warehouse’s logistic characteristics is researched.

System Engineering Analysis For Improved Scout Business Information Systems

DOE Office of Scientific and Technical Information (OSTI.GOV)

Van Slyke, D. A.

The project uses system engineering principles to address the need of Boy Scout leaders for an integrated system to facilitate advancement and awards records, leader training and planning for meetings and activities. Existing products to address needs of Scout leaders and relevant stakeholders function to support record keeping and some communication functions but opportunity exists for a better system to fully integrate these functions with training delivery and recording, activity planning along with feedback and information gathering from stakeholders. Key stakeholders for the sytem include Scouts and their families, leaders, training providers, sellers of supplies and awards, content generators andmore » facilities that serve Scout activities. Key performance parameters for the system are protection of personal information, availability of current information, information accuracy and information content that has depth. Implementation concepts considered for the system include (1) owned and operated by Boy Scouts of America, (2) Contracted out to a vendor (3) distributed system that functions with BSA managed interfaces. The selected concept is to contract out to a vendor to maximize the likelihood of successful integration and take advantage of the best technology. Development of requirements considers three key use cases (1) System facilitates planning a hike with training needed satisfied in advance and advancement recording real time (2) Scheduling and documenting in-person training, (3) Family interested in Scouting receives information and can request follow-up. Non-functional requirements are analyzed with the Quality Function Deployment tool. Requirement addressing frequency of backup, compatibility with legacy and new technology, language support, software update are developed to address system reliability and intuitive interface. System functions analyzed include update of activity database, maintenance of advancement status, archive of documents, and monitoring of content that is accessible. The study examines risks associated with information security, technological change and continued popularity of Scouting. Mitigation is based on system functions that are defined. The approach to developing an improved system for facilitating Boy Scout leader functions was iterative with insights into capabilities coming in the course of working through the used cases and sequence diagrams.« less

Space shuttle program information control and retrieval system feasibility study report

NASA Technical Reports Server (NTRS)

Lingle, C. P.

1973-01-01

The feasibility of having a common information management network for space shuttle data, is studied. Identified are the information types required, sources and users of the information, and existing techniques for acquiring, storing and retrieving the data. The study concluded that a decentralized system is feasible, and described a recommended development plan for it.

76 FR 19333 - Commission Information Collection Activities (FERC-725B); Comment Request; Submitted for OMB Review

Federal Register 2010, 2011, 2012, 2013, 2014

2011-04-07

... the Bulk-Power System to comply with specific requirements to safeguard critical cyber assets.\\2\\ These standards help protect the nation's Bulk-Power System against potential disruptions from cyber... recordkeeping requirements. Specifically, CIP- 008-1 requires responsible entities to report cyber security...

76 FR 52581 - Automated Data Processing and Information Retrieval System Requirements

Federal Register 2010, 2011, 2012, 2013, 2014

2011-08-23

..., however, conduct pre and/or post implementation reviews. These reviews would be intended to: Evaluate... payment accuracy. This proposed rule would also specify the requirements for submission of a test plan... eligibility systems are adequately reviewed and tested. The law requires accountability for ensuring test...

48 CFR 3052.204-70 - Security requirements for unclassified information technology resources.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 48 Federal Acquisition Regulations System 7 2014-10-01 2014-10-01 false Security requirements for... System DEPARTMENT OF HOMELAND SECURITY, HOMELAND SECURITY ACQUISITION REGULATION (HSAR) CLAUSES AND FORMS SOLICITATION PROVISIONS AND CONTRACT CLAUSES Text of Provisions and Clauses 3052.204-70 Security requirements...

48 CFR 3052.204-70 - Security requirements for unclassified information technology resources.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 48 Federal Acquisition Regulations System 7 2013-10-01 2012-10-01 true Security requirements for... System DEPARTMENT OF HOMELAND SECURITY, HOMELAND SECURITY ACQUISITION REGULATION (HSAR) CLAUSES AND FORMS SOLICITATION PROVISIONS AND CONTRACT CLAUSES Text of Provisions and Clauses 3052.204-70 Security requirements...

Methods for Environments and Contaminants: Drinking Water

EPA Pesticide Factsheets

EPA’s Safe Drinking Water Information System Federal Version (SDWIS/FED) includes information on populations served and violations of maximum contaminant levels or required treatment techniques by the nation’s 160,000 public water systems.

Data systems can boost nursing care. Nurse management information systems in resource management.

PubMed

Wilson, J

1992-02-01

Resource management aims to improve patient care by matching resources with patient needs. Nurse management information systems provide data on skill mix, rostering requirements, ward costs and patient dependency levels, enabling a nursing strategy to be planned for the ward.

78 FR 77554 - Reports, Forms and Record Keeping Requirements; Agency Information Collection Activity Under OMB...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-12-23

... information described is the ``Consolidated Child Restraint System Registration, Labeling and Defect...: National Highway Traffic Safety Administration Title: Consolidated Child Restraint System Registration... the Federal motor vehicle safety standard for child restraint systems (CRSs) to expand its...

Guide to remote-sensor data systems

NASA Technical Reports Server (NTRS)

Dewitt, R. R.; Ellison, J. L.

1980-01-01

Remote sensing data-handbook presents theoretical and practical information on spaceborne sensors and associated systems for Earth-resources applications. Handbook provides discussion on historical information, principles of operations, factors affecting performances, nature of data output, and system required to process data and trends in research and development.

National Parks of New York Harbor Traveler Information System : Functional Requirements

DOT National Transportation Integrated Search

2011-12-23

The purpose of this planning project is to analyze alternatives and design a Traveler Information System (TIS) that will enhance the experience of visitors to the NYNH parks and other sites managed by federal, state and local partners. The system wil...

Substance abuse treatment management information systems: balancing federal, state, and service provider needs.

PubMed

Camp, J M; Krakow, M; McCarty, D; Argeriou, M

1992-01-01

There is increased interest in documenting the characteristics and treatment outcomes of clients served with Alcohol, Drug Abuse, and Mental Health Block Grant funds. The evolution of federal client-based management systems for substance abuse treatment services demonstrates that data collection systems are important but require continued support. A review of the Massachusetts substance abuse management information system illustrates the utility of a client-based data set. The development and implementation of a comprehensive information system require overcoming organizational barriers and project delays, fostering collaborative efforts among staff from diverse agencies, and employing considerable resources. In addition, the need to develop mechanisms for increasing the reliability of the data and ongoing training for the users is presented. Finally, three applications of the management information system's role in shaping policy are reviewed: developing services for special populations (communities of color, women, and pregnant substance abusers, and injection drug users), utilizing MIS data for evaluation purposes, and determining funding allocations.

Application of structured analysis to a telerobotic system

NASA Technical Reports Server (NTRS)

Dashman, Eric; Mclin, David; Harrison, F. W.; Soloway, Donald; Young, Steven

1990-01-01

The analysis and evaluation of a multiple arm telerobotic research and demonstration system developed by the NASA Intelligent Systems Research Laboratory (ISRL) is described. Structured analysis techniques were used to develop a detailed requirements model of an existing telerobotic testbed. Performance models generated during this process were used to further evaluate the total system. A commercial CASE tool called Teamwork was used to carry out the structured analysis and development of the functional requirements model. A structured analysis and design process using the ISRL telerobotic system as a model is described. Evaluation of this system focused on the identification of bottlenecks in this implementation. The results demonstrate that the use of structured methods and analysis tools can give useful performance information early in a design cycle. This information can be used to ensure that the proposed system meets its design requirements before it is built.

A federated information management system for the Deep Space Network. M.S. Thesis - Univ. of Southern California

NASA Technical Reports Server (NTRS)

Dobinson, E.

1982-01-01

General requirements for an information management system for the deep space network (DSN) are examined. A concise review of available database management system technology is presented. It is recommended that a federation of logically decentralized databases be implemented for the Network Information Management System of the DSN. Overall characteristics of the federation are specified, as well as reasons for adopting this approach.

Wildland fire management. Volume 2: Wildland fire control 1985-1995. [satellite information system for California fire problems

NASA Technical Reports Server (NTRS)

Saveker, D. R. (Editor)

1973-01-01

The preliminary design of a satellite plus computer earth resources information system is proposed for potential uses in fire prevention and control in the wildland fire community. Suggested are satellite characteristics, sensor characteristics, discrimination algorithms, data communication techniques, data processing requirements, display characteristics, and costs in achieving the integrated wildland fire information system.

Reassessing the Skills Required of Graduates of an Information Systems Program: An Updated Analysis

ERIC Educational Resources Information Center

Legier, John; Woodward, Belle; Martin, Nancy

2013-01-01

The study involves an updated analysis of the job characteristics of information systems graduates based on the status of the job market as well as the perceptions of 72 graduates from an information systems program of a Midwestern university. Approximately one-third of the graduates were working in positions related to technical support.…

Space station integrated propulsion and fluid system study: Fluid systems configuration databook

NASA Technical Reports Server (NTRS)

Rose, L.; Bicknell, B.; Bergman, D.; Wilson, S.

1987-01-01

This databook contains fluid system requirements and system descriptions for Space Station program elements including the United States and International modules, integrated fluid systems, attached payloads, fluid servicers and vehicle accommodation facilities. Separate sections are devoted to each of the program elements and include a discussion of the overall system requirements, specific fluid systems requirements and systems descriptions. The systems descriptions contain configurations, fluid inventory data and component lists. In addition, a list of information sources is referenced at the end of each section.

78 FR 63462 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-10-24

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System [Docket Number DARS-2013-0035] Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Organizational Conflict..., Department of Defense (DoD). ACTION: Notice and request for comments regarding a proposed extension of an...

Man-systems requirements for the control of teleoperators in space

NASA Technical Reports Server (NTRS)

Shields, Nicholas L., Jr.

1988-01-01

The microgravity of the space environment has profound effects on humans and, consequently, on the design requirements for subsystems and components with which humans interact. There are changes in the anthropometry, vision, the perception of orientation, posture, and the ways in which we exert energy. The design requirements for proper human engineering must reflect each of the changes that results, and this is especially true in the exercise of control over remote and teleoperated systems where the operator is removed from any direct sense of control. The National Aeronautics and Space Administration has recently completed the first NASA-wide human factors standard for microgravity. The Man-Systems Integration Standard, NASA-STD-3000, contains considerable information on the appropriate design criteria for microgravity, and there is information that is useful in the design for teleoperated systems. There is not, however, a dedicated collection of data which pertains directly to the special cases of remote and robotic operations. The design considerations for human-system interaction in the control of remote systems in space are discussed, with brief details on the information to be found in the NASA-STD-3000, and arguments for a dedicated section within the Standard which deals with robotic, teleoperated and remote systems and the design requirements for effective human control of these systems in the space environment, and from the space environment.

Strategic Plan for Information Systems and Technology, Fiscal Years 1994-1998.

ERIC Educational Resources Information Center

National Archives and Records Administration, Washington, DC.

The information systems and technology management program of the National Archives and Records Administration (NARA) establishes broad policy guidance and technical standards for information management to ensure that appropriate resource sharing can occur, while providing cost-effective support for mission requirements of program offices. The NARA…

75 FR 59717 - Agency Information Collection Activities: Announcement of Board Approval Under Delegated...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-09-28

... FEDERAL RESERVE SYSTEM Agency Information Collection Activities: Announcement of Board Approval... approval of proposed information collection by the Board of Governors of the Federal Reserve System (Board... docket files. The Federal Reserve may not conduct or sponsor, and the respondent is not required to...

Using Collaboration to Provide Students with an Internship Experience in an Information Systems Course

ERIC Educational Resources Information Center

Wallace, Patricia

2007-01-01

This paper describes an instructional technique in an Information Systems course that provides students with actual work experience as part of an internship and/or apprenticeship assignment while completing additional course requirements. The course, Information Resource Management, provides students with a comprehensive overview of Information…

76 FR 30150 - Establishment of a New System of Records for Personal Information Collected by the Environmental...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-05-24

... the entire information system with respect to computer security, prohibition and detection of any.... Safeguards: --Computer-stored information is protected in accordance with the Agency's security requirements..., loaner car agreement, cash incentives agreement (includes social security number for mandatory tax...

77 FR 61582 - Privacy Act of 1974; System of Records

Federal Register 2010, 2011, 2012, 2013, 2014

2012-10-10

... change, including any personal identifiers or contact information FOR FURTHER INFORMATION CONTACT: Mr..., have been published in FOR FURTHER INFORMATION CONTACT. The proposed system report, as required by 5 U...: Delete entry and replace with ``Social Security Number (SSN), name, home address, phone numbers or other...

Earth observing system. Output data products and input requirements, version 2.0. Volume 3: Algorithm summary tables and non-EOS data products

NASA Technical Reports Server (NTRS)

Lu, Yun-Chi; Chang, Hyo Duck; Krupp, Brian; Kumar, Ravindar; Swaroop, Anand

1992-01-01

Volume 3 assists Earth Observing System (EOS) investigators in locating required non-EOS data products by identifying their non-EOS input requirements and providing the information on data sets available at various Distributed Active Archive Centers (DAAC's), including those from Pathfinder Activities and Earth Probes. Volume 3 is intended to complement, not to duplicate, the the EOSDIS Science Data Plan (SDP) by providing detailed data set information which was not presented in the SDP. Section 9 of this volume discusses the algorithm summary tables containing information on retrieval algorithms, expected outputs and required input data. Section 10 describes the non-EOS input requirements of instrument teams and IDS investigators. Also described are the current and future data holdings of the original seven DAACS and data products planned from the future missions and projects including Earth Probes and Pathfinder Activities. Section 11 describes source of information used in compiling data set information presented in this volume. A list of data set attributes used to describe various data sets is presented in section 12 along with their descriptions. Finally, Section 13 presents the SPSO's future plan to improve this report .

Earth observing system. Output data products and input requirements, version 2.0. Volume 1: Instrument data product characteristics

NASA Technical Reports Server (NTRS)

Lu, Yun-Chi; Chang, Hyo Duck; Krupp, Brian; Kumar, Ravindra; Swaroop, Anand

1992-01-01

Information on Earth Observing System (EOS) output data products and input data requirements that has been compiled by the Science Processing Support Office (SPSO) at GSFC is presented. Since Version 1.0 of the SPSO Report was released in August 1991, there have been significant changes in the EOS program. In anticipation of a likely budget cut for the EOS Project, NASA HQ restructured the EOS program. An initial program consisting of two large platforms was replaced by plans for multiple, smaller platforms, and some EOS instruments were either deselected or descoped. Updated payload information reflecting the restructured EOS program superseding the August 1991 version of the SPSO report is included. This report has been expanded to cover information on non-EOS data products, and consists of three volumes (Volumes 1, 2, and 3). Volume 1 provides information on instrument outputs and input requirements. Volume 2 is devoted to Interdisciplinary Science (IDS) outputs and input requirements, including the 'best' and 'alternative' match analysis. Volume 3 provides information about retrieval algorithms, non-EOS input requirements of instrument teams and IDS investigators, and availability of non-EOS data products at seven primary Distributed Active Archive Centers (DAAC's).

32 CFR 322.7 - Exempt systems of records.

Code of Federal Regulations, 2010 CFR

2010-07-01

... information permits more informed decision-making by the Department when making required suitability... becomes clear. Such information permits more informed decision-making by the Department when making... becomes clear. Such information permits more informed decision-making by the Department when making...

Mixed Traffic Information Collection System based on Pressure Sensor

NASA Astrophysics Data System (ADS)

Liao, Wenzhe; Liu, Mingsheng; Meng, Qingli

The traffic information collection is the base of Intelligent Traffic.At present, there exist mixed traffic situation in urban road in China. This paper researched and implemented a system through collecting the vehicle and bicycle mixed traffic flow parameters based on pressure sensor. According to information collection requirements, we selected pressure sensor, designed the data collection, storage and other hardware circuitries and information processing software. The experiment shows that the system can meet the demand of traffic information collection in the actual.

Support of an Active Science Project by a Large Information System: Lessons for the EOS Era

NASA Technical Reports Server (NTRS)

Angelici, Gary L.; Skiles, J. W.; Popovici, Lidia Z.

1993-01-01

The ability of large information systems to support the changing data requirements of active science projects is being tested in a NASA collaborative study. This paper briefly profiles both the active science project and the large information system involved in this effort and offers some observations about the effectiveness of the project support. This is followed by lessons that are important for those participating in large information systems that need to support active science projects or that make available the valuable data produced by these projects. We learned in this work that it is difficult for a large information system focused on long term data management to satisfy the requirements of an on-going science project. For example, in order to provide the best service, it is important for all information system staff to keep focused on the needs and constraints of the scientists in the development of appropriate services. If the lessons learned in this and other science support experiences are not applied by those involved with large information systems of the EOS (Earth Observing System) era, then the final data products produced by future science projects may not be robust or of high quality, thereby making the conduct of the project science less efficacious and reducing the value of these unique suites of data for future research.

A new generation of real-time DOS technology for mission-oriented system integration and operation

NASA Technical Reports Server (NTRS)

Jensen, E. Douglas

1988-01-01

Information is given on system integration and operation (SIO) requirements and a new generation of technical approaches for SIO. Real-time, distribution, survivability, and adaptability requirements and technical approaches are covered. An Alpha operating system program management overview is outlined.

Rotorcraft Diagnostics

NASA Technical Reports Server (NTRS)

Haste, Deepak; Azam, Mohammad; Ghoshal, Sudipto; Monte, James

2012-01-01

Health management (HM) in any engineering systems requires adequate understanding about the system s functioning; a sufficient amount of monitored data; the capability to extract, analyze, and collate information; and the capability to combine understanding and information for HM-related estimation and decision-making. Rotorcraft systems are, in general, highly complex. Obtaining adequate understanding about functioning of such systems is quite difficult, because of the proprietary (restricted access) nature of their designs and dynamic models. Development of an EIM (exact inverse map) solution for rotorcraft requires a process that can overcome the abovementioned difficulties and maximally utilize monitored information for HM facilitation via employing advanced analytic techniques. The goal was to develop a versatile HM solution for rotorcraft for facilitation of the Condition Based Maintenance Plus (CBM+) capabilities. The effort was geared towards developing analytic and reasoning techniques, and proving the ability to embed the required capabilities on a rotorcraft platform, paving the way for implementing the solution on an aircraft-level system for consolidation and reporting. The solution for rotorcraft can he used offboard or embedded directly onto a rotorcraft system. The envisioned solution utilizes available monitored and archived data for real-time fault detection and identification, failure precursor identification, and offline fault detection and diagnostics, health condition forecasting, optimal guided troubleshooting, and maintenance decision support. A variant of the onboard version is a self-contained hardware and software (HW+SW) package that can be embedded on rotorcraft systems. The HM solution comprises components that gather/ingest data and information, perform information/feature extraction, analyze information in conjunction with the dependency/diagnostic model of the target system, facilitate optimal guided troubleshooting, and offer decision support for optimal maintenance.

SPIRES (Stanford Physics Information REtrieval System) 1969-70 Annual Report.

ERIC Educational Resources Information Center

Stanford Univ., CA. Inst. for Communication Research.

For those unfamiliar with the Stanford Physics Information Retrieval System (SPIRES) an introduction and background section is provided in this 1969-70 annual report. This is followed by: (1) the SPIRES I prototype, (2) developing a production system--SPIRES II and (3) system scope and requirements analysis. The appendices present: (1) Stanford…

Information Retrieval System Design Issues in a Microcomputer-Based Relational DBMS Environment.

ERIC Educational Resources Information Center

Wolfram, Dietmar

1992-01-01

Outlines the file structure requirements for a microcomputer-based information retrieval system using FoxPro, a relational database management system (DBMS). Issues relating to the design and implementation of such systems are discussed, and two possible designs are examined in terms of space economy and practicality of implementation. (15…

75 FR 67363 - Notice of Public Information Collection(s) Being Reviewed by the Federal Communications...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-11-02

... proceeding were required to file system security statements under the Commission's rules. (Security systems..., including broadband Internet access and interconnected VoIP providers, must file updates to their systems... Commission's rules, the information in the CALEA security system filings and petitions will not be made...

Inventorying national forest resources...for planning-programing-budgeting system

Treesearch

Miles R. Hill; Elliot L. Amidon

1968-01-01

New systems for analyzing resource management problems, such as Planning-Programing-Budgeting, will require automated procedures to collect and assemble resource inventory data. A computer - oriented system called Map Information Assembly and Display System developed for this purpose was tested on a National Forest in California. It provided information on eight forest...

A proposal for cervical screening information systems in developing countries.

PubMed

Marrett, Loraine D; Robles, Sylvia; Ashbury, Fredrick D; Green, Bo; Goel, Vivek; Luciani, Silvana

2002-11-20

The effective and efficient delivery of cervical screening programs requires information for planning, management, delivery and evaluation. Specially designed systems are generally required to meet these needs. In many developing countries, lack of information systems constitutes an important barrier to development of comprehensive screening programs and the effective control of cervical cancer. Our report outlines a framework for creating such systems in developing countries and describes a conceptual model for a cervical screening information system. The proposed system is modular, recognizing that there will be considerable between-region heterogeneity in current status and priorities. The proposed system is centered on modules that would allow for the assembly and computerization of data on Pap tests, since these represent the main screening modality at the present time. Additional modules would process data and create and maintain a screening database (e.g., standardize, edit, link and update modules) and allow for the integration of other types of data, such as cervical histopathology results. An open systems development model is proposed, since it is most compatible with the goals of local stakeholder involvement and capacity-building. Copyright 2002 Wiley-Liss, Inc.

Trust information-based privacy architecture for ubiquitous health.

PubMed

Ruotsalainen, Pekka Sakari; Blobel, Bernd; Seppälä, Antto; Nykänen, Pirkko

2013-10-08

Ubiquitous health is defined as a dynamic network of interconnected systems that offers health services independent of time and location to a data subject (DS). The network takes place in open and unsecure information space. It is created and managed by the DS who sets rules that regulate the way personal health information is collected and used. Compared to health care, it is impossible in ubiquitous health to assume the existence of a priori trust between the DS and service providers and to produce privacy using static security services. In ubiquitous health features, business goals and regulations systems followed often remain unknown. Furthermore, health care-specific regulations do not rule the ways health data is processed and shared. To be successful, ubiquitous health requires novel privacy architecture. The goal of this study was to develop a privacy management architecture that helps the DS to create and dynamically manage the network and to maintain information privacy. The architecture should enable the DS to dynamically define service and system-specific rules that regulate the way subject data is processed. The architecture should provide to the DS reliable trust information about systems and assist in the formulation of privacy policies. Furthermore, the architecture should give feedback upon how systems follow the policies of DS and offer protection against privacy and trust threats existing in ubiquitous environments. A sequential method that combines methodologies used in system theory, systems engineering, requirement analysis, and system design was used in the study. In the first phase, principles, trust and privacy models, and viewpoints were selected. Thereafter, functional requirements and services were developed on the basis of a careful analysis of existing research published in journals and conference proceedings. Based on principles, models, and requirements, architectural components and their interconnections were developed using system analysis. The architecture mimics the way humans use trust information in decision making, and enables the DS to design system-specific privacy policies using computational trust information that is based on systems' measured features. The trust attributes that were developed describe the level systems for support awareness and transparency, and how they follow general and domain-specific regulations and laws. The monitoring component of the architecture offers dynamic feedback concerning how the system enforces the polices of DS. The privacy management architecture developed in this study enables the DS to dynamically manage information privacy in ubiquitous health and to define individual policies for all systems considering their trust value and corresponding attributes. The DS can also set policies for secondary use and reuse of health information. The architecture offers protection against privacy threats existing in ubiquitous environments. Although the architecture is targeted to ubiquitous health, it can easily be modified to other ubiquitous applications.

The drainage information and control system of smart city

NASA Astrophysics Data System (ADS)

Mao, Tonglei; Li, Lei; Liu, JiChang; Cheng, Liang; Zhang, Jing; Song, Zengzhong; Liu, Lianhai; Hu, Zichen

2018-03-01

At present, due to the continuous expansion of city and the increase of the municipal drainage facilities, which leads to a serious lack of management and operation personnel, the existing production management pattern already can't adapt to the new requirements. In this paper, according to river drainage management, flood control, water management, auditing, administrative license, etc. different business management requirement, an information management system for water planning and design of smart city based on WebGIS in Linyi was introduced, which can collect the various information of gate dam, water pump, bridge sensor and traffic guide terminal nodes etc. together. The practical application show that the system can not only implement the sharing, resources integration and collaborative application for the regional water information, but also improve the level of the integrated water management.

AIAA/NASA International Symposium on Space Information Systems, 2nd, Pasadena, CA, Sept. 17-19, 1990, Proceedings. Vols. 1 & 2

NASA Technical Reports Server (NTRS)

Tavenner, Leslie A. (Editor)

1991-01-01

These proceedings overview major space information system projects and lessons learned from current missions. Other topics include the science information system requirements for the 1990s, an information systems design approach for major programs, the technology needs and projections, the standards for space data information systems, the artificial intelligence technology and applications, international interoperability, and spacecraft data systems and architectures advanced communications. Other topics include the software engineering technology and applications, the multimission multidiscipline information system architectures, the distributed planning and scheduling systems and operations, and the computer and information systems architectures. Paper presented include prospects for scientific data analysis systems for solar-terrestrial physics in the 1990s, the Columbus data management system, data storage technologies for the future, the German aerospace research establishment, and launching artificial intelligence in NASA ground systems.

A Theory of Information Quality and a Framework for its Implementation in the Requirements Engineering Process

NASA Astrophysics Data System (ADS)

Grenn, Michael W.

This dissertation introduces a theory of information quality to explain macroscopic behavior observed in the systems engineering process. The theory extends principles of Shannon's mathematical theory of communication [1948] and statistical mechanics to information development processes concerned with the flow, transformation, and meaning of information. The meaning of requirements information in the systems engineering context is estimated or measured in terms of the cumulative requirements quality Q which corresponds to the distribution of the requirements among the available quality levels. The requirements entropy framework (REF) implements the theory to address the requirements engineering problem. The REF defines the relationship between requirements changes, requirements volatility, requirements quality, requirements entropy and uncertainty, and engineering effort. The REF is evaluated via simulation experiments to assess its practical utility as a new method for measuring, monitoring and predicting requirements trends and engineering effort at any given time in the process. The REF treats the requirements engineering process as an open system in which the requirements are discrete information entities that transition from initial states of high entropy, disorder and uncertainty toward the desired state of minimum entropy as engineering effort is input and requirements increase in quality. The distribution of the total number of requirements R among the N discrete quality levels is determined by the number of defined quality attributes accumulated by R at any given time. Quantum statistics are used to estimate the number of possibilities P for arranging R among the available quality levels. The requirements entropy H R is estimated using R, N and P by extending principles of information theory and statistical mechanics to the requirements engineering process. The information I increases as HR and uncertainty decrease, and the change in information AI needed to reach the desired state of quality is estimated from the perspective of the receiver. The HR may increase, decrease or remain steady depending on the degree to which additions, deletions and revisions impact the distribution of R among the quality levels. Current requirements trend metrics generally treat additions, deletions and revisions the same and simply measure the quantity of these changes over time. The REF evaluates the quantity of requirements changes over time, distinguishes between their positive and negative effects by calculating their impact on HR, Q, and AI, and forecasts when the desired state will be reached, enabling more accurate assessment of the status and progress of the requirements engineering effort. Results from random variable simulations suggest the REF is an improved leading indicator of requirements trends that can be readily combined with current methods. The increase in I, or decrease in H R and uncertainty, is proportional to the engineering effort E input into the requirements engineering process. The REF estimates the AE needed to transition R from their current state of quality to the desired end state or some other interim state of interest. Simulation results are compared with measured engineering effort data for Department of Defense programs published in the SE literature, and the results suggest the REF is a promising new method for estimation of AE.

Software Requirements Specification of A Proposed Plant Property Management Information System for the Naval Postgraduate School.

DTIC Science & Technology

1982-12-01

information system (MIS) to support Plant Account equipment related functions could eliminate data handling redundancy and improved Plant Account...system users and accountability for more than 2000 individual equipment items worth over seven million dollars. Implementation of a management

75 FR 26739 - Information Collection Requirement; Defense Federal Acquisition Regulation Supplement; Part 244...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-05-12

.... Needs and Uses: Administrative contracting officers use this information in making decisions to grant, withhold, or withdraw purchasing system approval at the conclusion of a purchasing system review... for correcting deficiencies or making improvements to its purchasing system. Ynette R. Shelkin, Editor...

DESIGN INFORMATION ON FINE PORE AERATION SYSTEMS

EPA Science Inventory

Field studies were conducted over several years at municipal wastewater treatment plants employing line pore diffused aeration systems. These studies were designed to produce reliable information on the performance and operational requirements of fine pore devices under process ...

Integrated Compliance Information System (ICIS)

EPA Pesticide Factsheets

The purpose of ICIS is to meet evolving Enforcement and Compliance business needs for EPA and State users by integrating information into a single integrated data system that supports both management and programmatic requirements of the Enforcement and Compliance programs.

Design and implementation of an identification system in construction site safety for proactive accident prevention.

PubMed

Yang, Huanjia; Chew, David A S; Wu, Weiwei; Zhou, Zhipeng; Li, Qiming

2012-09-01

Identifying accident precursors using real-time identity information has great potential to improve safety performance in construction industry, which is still suffering from day to day records of accident fatality and injury. Based on the requirements analysis for identifying precursor and the discussion of enabling technology solutions for acquiring and sharing real-time automatic identification information on construction site, this paper proposes an identification system design for proactive accident prevention to improve construction site safety. Firstly, a case study is conducted to analyze the automatic identification requirements for identifying accident precursors in construction site. Results show that it mainly consists of three aspects, namely access control, training and inspection information and operation authority. The system is then designed to fulfill these requirements based on ZigBee enabled wireless sensor network (WSN), radio frequency identification (RFID) technology and an integrated ZigBee RFID sensor network structure. At the same time, an information database is also designed and implemented, which includes 15 tables, 54 queries and several reports and forms. In the end, a demonstration system based on the proposed system design is developed as a proof of concept prototype. The contributions of this study include the requirement analysis and technical design of a real-time identity information tracking solution for proactive accident prevention on construction sites. The technical solution proposed in this paper has a significant importance in improving safety performance on construction sites. Moreover, this study can serve as a reference design for future system integrations where more functions, such as environment monitoring and location tracking, can be added. Copyright © 2011 Elsevier Ltd. All rights reserved.

Changes, disruption and innovation: An investigation of the introduction of new health information technology in a microbiology laboratory.

PubMed

Toouli, George; Georgiou, Andrew; Westbrook, Johanna

2012-01-01

It is expected that health information technology (HIT) will deliver a safer, more efficient and effective health care system. The aim of this study was to undertake a qualitative and video-ethnographic examination of the impact of information technologies on work processes in the reception area of a Microbiology Department, to ascertain what changed, how it changed and the impact of the change. The setting for this study was the microbiology laboratory of a large tertiary hospital in Sydney. The study consisted of qualitative (interview and focus group) data and observation sessions for the period August 2005 to October 2006 along with video footage shot in three sessions covering the original system and the two stages of the Cerner implementation. Data analysis was assisted by NVivo software and process maps were produced from the video footage. There were two laboratory information systems observed in the video footage with computerized provider order entry introduced four months later. Process maps highlighted the large number of pre data entry steps with the original system whilst the newer system incorporated many of these steps in to the data entry stage. However, any time saved with the new system was offset by the requirement to complete some data entry of patient information not previously required. Other changes noted included the change of responsibilities for the reception staff and the physical changes required to accommodate the increased activity around the data entry area. Implementing a new HIT is always an exciting time for any environment but ensuring that the implementation goes smoothly and with minimal trouble requires the administrator and their team to plan well in advance for staff training, physical layout and possible staff resource reallocation.

Detailed requirements document for the Interactive Financial Management System (IFMS), volume 1

NASA Technical Reports Server (NTRS)

Dodson, D. B.

1975-01-01

The detailed requirements for phase 1 (online fund control, subauthorization accounting, and accounts receivable functional capabilities) of the Interactive Financial Management System (IFMS) are described. This includes information on the following: systems requirements, performance requirements, test requirements, and production implementation. Most of the work is centered on systems requirements, and includes discussions on the following processes: resources authority, allotment, primary work authorization, reimbursable order acceptance, purchase request, obligation, cost accrual, cost distribution, disbursement, subauthorization performance, travel, accounts receivable, payroll, property, edit table maintenance, end-of-year, backup input. Other subjects covered include: external systems interfaces, general inquiries, general report requirements, communication requirements, and miscellaneous. Subjects covered under performance requirements include: response time, processing volumes, system reliability, and accuracy. Under test requirements come test data sources, general test approach, and acceptance criteria. Under production implementation come data base establishment, operational stages, and operational requirements.

Cost and results of information systems for health and poverty indicators in the United Republic of Tanzania.

PubMed Central

Rommelmann, Vanessa; Setel, Philip W.; Hemed, Yusuf; Angeles, Gustavo; Mponezya, Hamisi; Whiting, David; Boerma, Ties

2005-01-01

OBJECTIVE: To examine the costs of complementary information generation activities in a resource-constrained setting and compare the costs and outputs of information subsystems that generate the statistics on poverty, health and survival required for monitoring, evaluation and reporting on health programmes in the United Republic of Tanzania. METHODS: Nine systems used by four government agencies or ministries were assessed. Costs were calculated from budgets and expenditure data made available by information system managers. System coverage, quality assurance and information production were reviewed using questionnaires and interviews. Information production was characterized in terms of 38 key sociodemographic indicators required for national programme monitoring. FINDINGS: In 2002-03 approximately US$ 0.53 was spent per Tanzanian citizen on the nine information subsystems that generated information on 37 of the 38 selected indicators. The census and reporting system for routine health service statistics had the largest participating populations and highest total costs. Nationally representative household surveys and demographic surveillance systems (which are not based on nationally representative samples) produced more than half the indicators and used the most rigorous quality assurance. Five systems produced fewer than 13 indicators and had comparatively high costs per participant. CONCLUSION: Policy-makers and programme planners should be aware of the many trade-offs with respect to system costs, coverage, production, representativeness and quality control when making investment choices for monitoring and evaluation. In future, formal cost-effectiveness studies of complementary information systems would help guide investments in the monitoring, evaluation and planning needed to demonstrate the impact of poverty-reduction and health programmes. PMID:16184275

14 CFR 101.29 - Information requirements.

Code of Federal Regulations, 2013 CFR

2013-01-01

...—High-Power Rocket requires a certificate of waiver or authorization, the person planning the operation... certificate of waiver or authorization the person planning the operation must provide the information below... characteristics for the entire flight profile, (4) A description of all major rocket systems, including structural...

14 CFR 101.29 - Information requirements.

Code of Federal Regulations, 2014 CFR

2014-01-01

...—High-Power Rocket requires a certificate of waiver or authorization, the person planning the operation... certificate of waiver or authorization the person planning the operation must provide the information below... characteristics for the entire flight profile, (4) A description of all major rocket systems, including structural...

14 CFR 101.29 - Information requirements.

Code of Federal Regulations, 2012 CFR

2012-01-01

...—High-Power Rocket requires a certificate of waiver or authorization, the person planning the operation... certificate of waiver or authorization the person planning the operation must provide the information below... characteristics for the entire flight profile, (4) A description of all major rocket systems, including structural...

14 CFR 101.29 - Information requirements.

Code of Federal Regulations, 2011 CFR

2011-01-01

...—High-Power Rocket requires a certificate of waiver or authorization, the person planning the operation... certificate of waiver or authorization the person planning the operation must provide the information below... characteristics for the entire flight profile, (4) A description of all major rocket systems, including structural...

Information technologies for Marine Corps combat medicine.

PubMed

Carey, N B; Rattelman, C R; Nguyen, H Q

1998-09-01

Future Marine Corps warfighting concepts will make it more difficult to locate casualties, which will complicate casualty evacuation, lengthen casualty wait times, and require infantrymen or corpsmen to provide more extensive treatment. In these future scenarios, information flow and communications will be critical to medical functions. We asked, for Navy medical support to the Marines, what information will future combat medicine require and what technologies should supply those information needs? Based on analyses of patient data streams, focus groups of Navy medical personnel, and our estimates of the cost and feasibility of communications systems, we recommend the following: (1) increase medical training for some fraction of Marines, especially in hemorrhage control; (2) augment corpsmen's training; (3) furnish data systems for evacuation and supply that would provide in-transit visibility and simplify requests; (4) provide all ground medical personnel with access to treatment information systems and limited voice communications; and (5) exploit e-mail systems to reduce reliance on voice communications. Implementation time frames are discussed.

Design of an intelligent information system for in-flight emergency assistance

NASA Technical Reports Server (NTRS)

Feyock, Stefan; Karamouzis, Stamos

1991-01-01

The present research has as its goal the development of AI tools to help flight crews cope with in-flight malfunctions. The relevant tasks in such situations include diagnosis, prognosis, and recovery plan generation. Investigation of the information requirements of these tasks has shown that the determination of paths figures largely: what components or systems are connected to what others, how are they connected, whether connections satisfying certain criteria exist, and a number of related queries. The formulation of such queries frequently requires capabilities of the second-order predicate calculus. An information system is described that features second-order logic capabilities, and is oriented toward efficient formulation and execution of such queries.

Investigation of the current requirements engineering practices among software developers at the Universiti Utara Malaysia Information Technology (UUMIT) centre

NASA Astrophysics Data System (ADS)

Hussain, Azham; Mkpojiogu, Emmanuel O. C.; Abdullah, Inam

2016-08-01

Requirements Engineering (RE) is a systemic and integrated process of eliciting, elaborating, negotiating, validating and managing of the requirements of a system in a software development project. UUM has been supported by various systems developed and maintained by the UUM Information Technology (UUMIT) Centre. The aim of this study was to assess the current requirements engineering practices at UUMIT. The main problem that prompted this research is the lack of studies that support software development activities at the UUMIT. The study is geared at helping UUMIT produce quality but time and cost saving software products by implementing cutting edge and state of the art requirements engineering practices. Also, the study contributes to UUM by identifying the activities needed for software development so that the management will be able to allocate budget to provide adequate and precise training for the software developers. Three variables were investigated: Requirement Description, Requirements Development (comprising: Requirements Elicitation, Requirements Analysis and Negotiation, Requirements Validation), and Requirement Management. The results from the study showed that the current practice of requirement engineering in UUMIT is encouraging, but still need further development and improvement because a few RE practices were seldom practiced.

Real-time alerts and reminders using information systems.

PubMed

Wanderer, Jonathan P; Sandberg, Warren S; Ehrenfeld, Jesse M

2011-09-01

Adoption of information systems throughout the hospital environment has enabled the development of real-time physiologic alerts and clinician reminder systems. These clinical tools can be made available through the deployment of anesthesia information management systems (AIMS). Creating usable alert systems requires understanding of technical considerations. Various successful implementations are reviewed, encompassing cost reduction, improved revenue capture, timely antibiotic administration, and postoperative nausea and vomiting prophylaxis. Challenges to the widespread use of real-time alerts and reminders include AIMS adoption rates and the difficulty in choosing appropriate areas and approaches for information systems support. Copyright © 2011 Elsevier Inc. All rights reserved.

The Road to Information Dominance: "System of Systems" Concept for the United States Armed Forces.

DTIC Science & Technology

1998-04-06

information dominance through the U.S. Armed Forces "System of Systems" concept. It addresses and analyzes current and future strategic implications and requirements for U.S. warfighting communications and information systems. It proposes a more flexible, reliable, responsive, robust and survivable high capacity throughput communications and "bitways" system to support future force projection operations for the Force and/or Army After Next. Lastly, it concludes with a suggested methodology to implement the "System of Systems" concept to enable

A Requirements Analysis for an Integrated Maintenance Information System Application Into Theater Air Control System Maintenance

DTIC Science & Technology

1994-09-01

133 v List of Tables Table Page 1. Line Item Changes in Proposed Ground TACS SSS Matrix...39 2. Percentage of Line Item Changes in Proposed SSS Matrix for G round T A C S...modified to meet Theater Air Control System requirements. The small amount of changes required to modify the aircraft matrix in order to satisfy ground

Information transfer satellite concept study. Volume 2: Technical

NASA Technical Reports Server (NTRS)

Bergin, P.; Kincade, C.; Kurpiewski, D.; Leinhaupel, F.; Millican, F.; Onstad, R.

1971-01-01

The ITS concept study is preceded by two requirements studies whose primary objectives are to identify viable demands and to develop the functional requirements associated with these demands. In addition to continuing this basic activity the ITS concept study objectives are to: (1) develop tools and techniques for planning advanced information transfer satellite communications systems, and to (2) select viable systems for further analysis both in their near-term and in the far-term aspects.

Battlefield Management System: Data Requirements to Support Passage of Company Level Tactical Information.

DTIC Science & Technology

1987-03-01

intelligent way, assemble those documents and data in usable formats, examine the communications tapes available for this project, and to develop a sampling...Lifetime Learning Publications, Belmont. CA. 1982. Rowe. Neil C.. Artifcial Intelligence , Draft Copv, Class Notes for Winter Quarter. CS 33 10, \\aval...AT2 122 BATTLEFIELD MANAGEMENT SYSTEM DATA REQUIRENTS TO 1/2 SUPPORT PASSAGE OF COMPANY LEVEL TACTICAL INFORMATION (U) NVALE POSTGRADUATE SCHOOL

Health information systems.

PubMed

Hovenga, Evelyn J S; Grain, Heather

2013-01-01

Health information provides the foundation for all decision making in healthcare whether clinical at the bed side, or at a national government level. This information is generally collected as part of systems which support administrative or clinical workflow and practice. This chapter describes the many and varied features of systems such as electronic health records (EHRs), how they fit with health information systems and how they collectively manage information flow. Systems engineering methods and tools are described together with their use to suit the health industry. This focuses on the need for suitable system architectures and semantic interoperability. These concepts and their relevance to the health industry are explained. The relationship and requirements for appropriate data governance in these systems is also considered.

41 CFR 300-70.2 - What information must we report, and when must we report it?

Code of Federal Regulations, 2014 CFR

2014-07-01

... 41 Public Contracts and Property Management 4 2014-07-01 2014-07-01 false What information must we report, and when must we report it? 300-70.2 Section 300-70.2 Public Contracts and Property Management Federal Travel Regulation System GENERAL AGENCY REQUIREMENTS 70-AGENCY REPORTING REQUIREMENTS Requirement To Report Agency Payments for Employee...

41 CFR 300-70.2 - What information must we report, and when must we report it?

Code of Federal Regulations, 2013 CFR

2013-07-01

... 41 Public Contracts and Property Management 4 2013-07-01 2012-07-01 true What information must we report, and when must we report it? 300-70.2 Section 300-70.2 Public Contracts and Property Management Federal Travel Regulation System GENERAL AGENCY REQUIREMENTS 70-AGENCY REPORTING REQUIREMENTS Requirement To Report Agency Payments for Employee...

41 CFR 300-70.2 - What information must we report, and when must we report it?

Code of Federal Regulations, 2012 CFR

2012-07-01

... 41 Public Contracts and Property Management 4 2012-07-01 2012-07-01 false What information must we report, and when must we report it? 300-70.2 Section 300-70.2 Public Contracts and Property Management Federal Travel Regulation System GENERAL AGENCY REQUIREMENTS 70-AGENCY REPORTING REQUIREMENTS Requirement To Report Agency Payments for Employee...

Space station data system analysis/architecture study. Task 1: Functional requirements definition, DR-5. Appendix: Requirements data base

NASA Technical Reports Server (NTRS)

1985-01-01

Appendix A contains data that characterize the system functions in sufficient depth as to determine the requirements for the Space Station Data System (SSDS). This data is in the form of: (1) top down traceability report; (2) bottom up traceability report; (3) requirements data sheets; and (4) cross index of requirements paragraphs of the source documents and the requirements numbers. A data base users guide is included that interested parties can use to access the requirements data base and get up to date information about the functions.

Information Management System for the California State Water Resources Control Board (SWRCB)

NASA Technical Reports Server (NTRS)

Heald, T. C.; Redmann, G. H.

1973-01-01

A study was made to establish the requirements for an integrated state-wide information management system for water quality control and water quality rights for the State of California. The data sources and end requirements were analyzed for the data collected and used by the numerous agencies, both State and Federal, as well as the nine Regional Boards under the jurisdiction of the State Board. The report details the data interfaces and outlines the system design. A program plan and statement of work for implementation of the project is included.

[Development of Hospital Equipment Maintenance Information System].

PubMed

Zhou, Zhixin

2015-11-01

Hospital equipment maintenance information system plays an important role in improving medical treatment quality and efficiency. By requirement analysis of hospital equipment maintenance, the system function diagram is drawed. According to analysis of input and output data, tables and reports in connection with equipment maintenance process, relationships between entity and attribute is found out, and E-R diagram is drawed and relational database table is established. Software development should meet actual process requirement of maintenance and have a friendly user interface and flexible operation. The software can analyze failure cause by statistical analysis.

Development of system design information for carbon dioxide using an amine type sorber

NASA Technical Reports Server (NTRS)

Rankin, R. L.; Roehlich, F.; Vancheri, F.

1971-01-01

Development work on system design information for amine type carbon dioxide sorber is reported. Amberlite IR-45, an aminated styrene divinyl benzene matrix, was investigated to determine the influence of design parameters of sorber particle size, process flow rate, CO2 partial pressure, total pressure, and bed designs. CO2 capacity and energy requirements for a 4-man size system were related mathematically to important operational parameters. Some fundamental studies in CO2 sorber capacity, energy requirements, and process operation were also performed.

Information Integration for Concurrent Engineering (IICE) IDEF3 Process Description Capture Method Report

DTIC Science & Technology

1995-09-01

vital processes of a business. process, IDEF, method, methodology, modeling, knowledge acquisition, requirements definition, information systems... knowledge resources. Like manpower, materials, and machines, information and knowledge assets are recognized as vital resources that can be leveraged to...integrated enterprise. These technologies are designed to leverage information and knowledge resources as the key enablers for high quality systems

Performance monitor system functional simulator, environmental data, orbiter 101(HFT)

NASA Technical Reports Server (NTRS)

Parker, F. W.

1974-01-01

Information concerning the environment component of the space shuttle performance monitor system simulator (PMSS) and those subsystems operational on the shuttle orbiter 101 used for horizontal flight test (HFT) is provided, along with detailed data for the shuttle performance monitor system (PMS) whose software requirements evolve from three basic PMS functions: (1) fault detection and annunciation; (2) subsystem measurement management; and (3) subsystem configuration management. Information relative to the design and operation of Orbiter systems for HFT is also presented, and the functional paths are identified to the lowest level at which the crew can control the system functions. Measurement requirements are given which are necessary to adequately monitor the health status of the system. PMS process requirements, relative to the measurements which are necessary for fault detection and annunciation of a failed functional path, consist of measurement characteristics, tolerance limits, precondition tests, and correlation measurements.

Trust Information-Based Privacy Architecture for Ubiquitous Health

PubMed Central

2013-01-01

Background Ubiquitous health is defined as a dynamic network of interconnected systems that offers health services independent of time and location to a data subject (DS). The network takes place in open and unsecure information space. It is created and managed by the DS who sets rules that regulate the way personal health information is collected and used. Compared to health care, it is impossible in ubiquitous health to assume the existence of a priori trust between the DS and service providers and to produce privacy using static security services. In ubiquitous health features, business goals and regulations systems followed often remain unknown. Furthermore, health care-specific regulations do not rule the ways health data is processed and shared. To be successful, ubiquitous health requires novel privacy architecture. Objective The goal of this study was to develop a privacy management architecture that helps the DS to create and dynamically manage the network and to maintain information privacy. The architecture should enable the DS to dynamically define service and system-specific rules that regulate the way subject data is processed. The architecture should provide to the DS reliable trust information about systems and assist in the formulation of privacy policies. Furthermore, the architecture should give feedback upon how systems follow the policies of DS and offer protection against privacy and trust threats existing in ubiquitous environments. Methods A sequential method that combines methodologies used in system theory, systems engineering, requirement analysis, and system design was used in the study. In the first phase, principles, trust and privacy models, and viewpoints were selected. Thereafter, functional requirements and services were developed on the basis of a careful analysis of existing research published in journals and conference proceedings. Based on principles, models, and requirements, architectural components and their interconnections were developed using system analysis. Results The architecture mimics the way humans use trust information in decision making, and enables the DS to design system-specific privacy policies using computational trust information that is based on systems’ measured features. The trust attributes that were developed describe the level systems for support awareness and transparency, and how they follow general and domain-specific regulations and laws. The monitoring component of the architecture offers dynamic feedback concerning how the system enforces the polices of DS. Conclusions The privacy management architecture developed in this study enables the DS to dynamically manage information privacy in ubiquitous health and to define individual policies for all systems considering their trust value and corresponding attributes. The DS can also set policies for secondary use and reuse of health information. The architecture offers protection against privacy threats existing in ubiquitous environments. Although the architecture is targeted to ubiquitous health, it can easily be modified to other ubiquitous applications. PMID:25099213

Integrity mechanism for eHealth tele-monitoring system in smart home environment.

PubMed

Mantas, Georgios; Lymberopoulos, Dimitrios; Komninos, Nikos

2009-01-01

During the past few years, a lot of effort has been invested in research and development of eHealth tele-monitoring systems that will provide many benefits for healthcare delivery from the healthcare provider to the patient's home. However, there is a plethora of security requirements in eHealth tele-monitoring systems. Data integrity of the transferred medical data is one of the most important security requirements that should be satisfied in these systems, since medical information is extremely sensitive information, and even sometimes life threatening information. In this paper, we present a data integrity mechanism for eHealth tele-monitoring system that operates in a smart home environment. Agent technology is applied to achieve data integrity with the use of cryptographic smart cards. Furthermore, the overall security infrastructure and its various components are described.

34 CFR 361.23 - Requirements related to the statewide workforce investment system.

Code of Federal Regulations, 2011 CFR

2011-07-01

... technology for individuals with disabilities; (ii) The use of information and financial management systems... 34 Education 2 2011-07-01 2010-07-01 true Requirements related to the statewide workforce investment system. 361.23 Section 361.23 Education Regulations of the Offices of the Department of Education...

76 FR 54233 - Information Collections Being Submitted for Review and Approval to the Office of Management and...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-08-31

... lowest unit charge. Broadcast stations and cable systems are also required to review their advertising... Communications Act directs broadcast stations and cable operators to charge political candidates the ``lowest... CFR 73.1942 requires broadcast licensees and 47 CFR 76.206 requires cable television systems to...

Defense Enterprise Accounting and Management System-Increment 1 (DEAMS Inc 1)

DTIC Science & Technology

2016-03-01

information accurately and in conformance with Generally Accepted Accounting Principles , to comply with Congressional requirements of the Chief Financial ...2016 Major Automated Information System Annual Report Defense Enterprise Accounting and Management System-Increment 1 (DEAMS Inc 1) Defense...Phone: 937-257-2714 Fax: DSN Phone: 787-2714 DSN Fax: Date Assigned: August 17, 2015 Program Information Program Name Defense Enterprise Accounting

Method and device for maximizing memory system bandwidth by accessing data in a dynamically determined order

NASA Technical Reports Server (NTRS)

Schwab, Andrew J. (Inventor); Aylor, James (Inventor); Hitchcock, Charles Young (Inventor); Wulf, William A. (Inventor); McKee, Sally A. (Inventor); Moyer, Stephen A. (Inventor); Klenke, Robert (Inventor)

2000-01-01

A data processing system is disclosed which comprises a data processor and memory control device for controlling the access of information from the memory. The memory control device includes temporary storage and decision ability for determining what order to execute the memory accesses. The compiler detects the requirements of the data processor and selects the data to stream to the memory control device which determines a memory access order. The order in which to access said information is selected based on the location of information stored in the memory. The information is repeatedly accessed from memory and stored in the temporary storage until all streamed information is accessed. The information is stored until required by the data processor. The selection of the order in which to access information maximizes bandwidth and decreases the retrieval time.

Geographic Information Systems as Applied to the Manipulation of Environmental Data.

ERIC Educational Resources Information Center

Hill, J. M.; And Others

1983-01-01

Discusses two aspects of a Geographic Information System (GIS), a computerized system for processing geographic and/or mapped data and components/implementation of a GIS and GIS demonstration in natural resources management. Demonstrations related to lignite mining permit requirements in coastal zone, and location of potential landfills/hazardous…

78 FR 77557 - Releasing Information; General Provisions; Accounting and Reporting Requirements; Reports of...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-12-24

..., including controls for maintaining the confidentiality of borrower information. The system of internal... develop and implement an effective system of internal controls over the central data repository to ensure..., and maintain an effective system of internal controls over the data included in the report of accounts...

78 FR 19247 - Privacy Act of 1974; System of Records

Federal Register 2010, 2011, 2012, 2013, 2014

2013-03-29

... Privacy Act system of records. SUMMARY: In accordance with the requirements of the Privacy Act of 1974, as... subject to the Privacy Act of 1974. This system of records maintains information on patent applicants and... notices. The storage and safeguard information has been updated to include electronic records. The...

Enabling information management systems in tactical network environments

NASA Astrophysics Data System (ADS)

Carvalho, Marco; Uszok, Andrzej; Suri, Niranjan; Bradshaw, Jeffrey M.; Ceccio, Philip J.; Hanna, James P.; Sinclair, Asher

2009-05-01

Net-Centric Information Management (IM) and sharing in tactical environments promises to revolutionize forward command and control capabilities by providing ubiquitous shared situational awareness to the warfighter. This vision can be realized by leveraging the tactical and Mobile Ad hoc Networks (MANET) which provide the underlying communications infrastructure, but, significant technical challenges remain. Enabling information management in these highly dynamic environments will require multiple support services and protocols which are affected by, and highly dependent on, the underlying capabilities and dynamics of the tactical network infrastructure. In this paper we investigate, discuss, and evaluate the effects of realistic tactical and mobile communications network environments on mission-critical information management systems. We motivate our discussion by introducing the Advanced Information Management System (AIMS) which is targeted for deployment in tactical sensor systems. We present some operational requirements for AIMS and highlight how critical IM support services such as discovery, transport, federation, and Quality of Service (QoS) management are necessary to meet these requirements. Our goal is to provide a qualitative analysis of the impact of underlying assumptions of availability and performance of some of the critical services supporting tactical information management. We will also propose and describe a number of technologies and capabilities that have been developed to address these challenges, providing alternative approaches for transport, service discovery, and federation services for tactical networks.

The evaluation and extension of TAE in the development of a user interface management system

NASA Technical Reports Server (NTRS)

Burkhart, Brenda; Sugar, Ross

1986-01-01

The development of a user interface management system (UIMS) for an information gathering and display system is discussed. The system interface requirements are outlined along with the UIMS functional characteristics. Those systems requirements which are supported by the current Transportable Applications Executive (TAE) are listed and necessary modifications to the TAE are described.

User Requirements for a Chronic Kidney Disease Clinical Decision Support Tool to Promote Timely Referral.

PubMed

Gulla, Joy; Neri, Pamela M; Bates, David W; Samal, Lipika

2017-05-01

Timely referral of patients with CKD has been associated with cost and mortality benefits, but referrals are often done too late in the course of the disease. Clinical decision support (CDS) offers a potential solution, but interventions have failed because they were not designed to support the physician workflow. We sought to identify user requirements for a chronic kidney disease (CKD) CDS system to promote timely referral. We interviewed primary care physicians (PCPs) to identify data needs for a CKD CDS system that would encourage timely referral and also gathered information about workflow to assess risk factors for progression of CKD. Interviewees were general internists recruited from a network of 14 primary care clinics affiliated with Brigham and Women's Hospital (BWH). We then performed a qualitative analysis to identify user requirements and system attributes for a CKD CDS system. Of the 12 participants, 25% were women, the mean age was 53 (range 37-82), mean years in clinical practice was 27 (range 11-58). We identified 21 user requirements. Seven of these user requirements were related to support for the referral process workflow, including access to pertinent information and support for longitudinal co-management. Six user requirements were relevant to PCP management of CKD, including management of risk factors for progression, interpretation of biomarkers of CKD severity, and diagnosis of the cause of CKD. Finally, eight user requirements addressed user-centered design of CDS, including the need for actionable information, links to guidelines and reference materials, and visualization of trends. These 21 user requirements can be used to design an intuitive and usable CDS system with the attributes necessary to promote timely referral. Copyright © 2017 Elsevier B.V. All rights reserved.

A PROPOSED CHEMICAL INFORMATION AND DATA SYSTEM. VOLUME I.

DTIC Science & Technology

CHEMICAL COMPOUNDS, *DATA PROCESSING, *INFORMATION RETRIEVAL, * CHEMICAL ANALYSIS, INPUT OUTPUT DEVICES, COMPUTER PROGRAMMING, CLASSIFICATION...CONFIGURATIONS, DATA STORAGE SYSTEMS, ATOMS, MOLECULES, PERFORMANCE( ENGINEERING ), MAINTENANCE, SUBJECT INDEXING, MAGNETIC TAPE, AUTOMATIC, MILITARY REQUIREMENTS, TYPEWRITERS, OPTICS, TOPOLOGY, STATISTICAL ANALYSIS, FLOW CHARTING.

Culvert information management system : demonstration project, final report, August 2009.

DOT National Transportation Integrated Search

2009-08-01

The overall objective of the research was to develop a pilot scale Culvert Information Management System (CIMS) that will : comply with both requirements stipulated by the Governmental Accounting Standards Board (GASB-34) and new federal : storm wate...

Hazardous Materials Information System (HMIS) Data Quality Review

DOT National Transportation Integrated Search

1997-05-01

The Hazardous Materials Information System (HMIS) is used to manage data required for the use, transportation, storage and disposal of hazardous material by the US Government. In response to concerns expressed by some users, DORO was tasked to conduc...

Evaluating and selecting an information system, Part 1.

PubMed

Neal, T

1993-01-01

Initial steps in the process of evaluating and selecting a computerized information system for the pharmacy department are described. The first step in the selection process is to establish a steering committee and a project committee. The steering committee oversees the project, providing policy guidance, making major decisions, and allocating budgeted expenditures. The project committee conducts the departmental needs assessment, identifies system requirements, performs day-to-day functions, evaluates vendor proposals, trains personnel, and implements the system chosen. The second step is the assessment of needs in terms of personnel, workload, physical layout, and operating requirements. The needs assessment should be based on the department's mission statement and strategic plan. The third step is the development of a request for information (RFI) and a request for proposal (RFP). The RFI is a document designed for gathering preliminary information from a wide range of vendors; this general information is used in deciding whether to send the RFP to a given vendor. The RFP requests more detailed information and gives the purchaser's exact specifications for a system; the RFP also includes contractual information. To help ensure project success, many institutions turn to computer consultants for guidance. The initial steps in selecting a computerized pharmacy information system are establishing computerization committees, conducting a needs assessment, and writing an RFI and an RFP. A crucial early decision is whether to seek a consultant's expertise.

Design of a Personnel and Training Information System for Educational R&D Personnel. Final Report.

ERIC Educational Resources Information Center

Hood, Paul D.; McCutchan, Nancy A.

The primary objective of this project was to design a system to provide information services that would fulfill the information requirements of federal planners, instructional material developers, training program directors and instructors, students, interns, employers, and practitioners concerned with problems relating to personnel and training…

Automated Text Markup for Information Retrieval from an Electronic Textbook of Infectious Disease

PubMed Central

Berrios, Daniel C.; Kehler, Andrew; Kim, David K.; Yu, Victor L.; Fagan, Lawrence M.

1998-01-01

The information needs of practicing clinicians frequently require textbook or journal searches. Making these sources available in electronic form improves the speed of these searches, but precision (i.e., the fraction of relevant to total documents retrieved) remains low. Improving the traditional keyword search by transforming search terms into canonical concepts does not improve search precision greatly. Kim et al. have designed and built a prototype system (MYCIN II) for computer-based information retrieval from a forthcoming electronic textbook of infectious disease. The system requires manual indexing by experts in the form of complex text markup. However, this mark-up process is time consuming (about 3 person-hours to generate, review, and transcribe the index for each of 218 chapters). We have designed and implemented a system to semiautomate the markup process. The system, information extraction for semiautomated indexing of documents (ISAID), uses query models and existing information-extraction tools to provide support for any user, including the author of the source material, to mark up tertiary information sources quickly and accurately.

Autonomous Attitude Determination System (AADS). Volume 1: System description

NASA Technical Reports Server (NTRS)

Saralkar, K.; Frenkel, Y.; Klitsch, G.; Liu, K. S.; Lefferts, E.; Tasaki, K.; Snow, F.; Garrahan, J.

1982-01-01

Information necessary to understand the Autonomous Attitude Determination System (AADS) is presented. Topics include AADS requirements, program structure, algorithms, and system generation and execution.

78 FR 69086 - Federal Acquisition Regulation; Submission for OMB Review; Preaward Survey Forms (Standard Forms...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-11-18

.... Standard Form 1408--Preaward Survey of Prospective Contractor Accounting System Respondents: 354. Responses... and approve an extension of a previously approved information collection requirement concerning... not challenge the propriety of this underlying information collection requirement. Response: FAR 9.106...

47 CFR 2.1517 - Data recording/reporting requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... comparative information. (e) A description of any modifications made to the EUT or other system components.../reporting requirements. The test report for an EPIRB shall contain the following information: (a) Specific... individual responsible, either directly or indirectly, for production or marketing of the device tested that...

40 CFR 125.124 - Information required to be submitted by applicant.

Code of Federal Regulations, 2011 CFR

2011-07-01

... 40 Protection of Environment 22 2011-07-01 2011-07-01 false Information required to be submitted by applicant. 125.124 Section 125.124 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) WATER PROGRAMS CRITERIA AND STANDARDS FOR THE NATIONAL POLLUTANT DISCHARGE ELIMINATION SYSTEM...

40 CFR 125.124 - Information required to be submitted by applicant.

Code of Federal Regulations, 2010 CFR

2010-07-01

... 40 Protection of Environment 21 2010-07-01 2010-07-01 false Information required to be submitted by applicant. 125.124 Section 125.124 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY (CONTINUED) WATER PROGRAMS CRITERIA AND STANDARDS FOR THE NATIONAL POLLUTANT DISCHARGE ELIMINATION SYSTEM...

Advanced approach to information security management system model for industrial control system.

PubMed

Park, Sanghyun; Lee, Kyungho

2014-01-01

Organizations make use of important information in day-to-day business. Protecting sensitive information is imperative and must be managed. Companies in many parts of the world protect sensitive information using the international standard known as the information security management system (ISMS). ISO 27000 series is the international standard ISMS used to protect confidentiality, integrity, and availability of sensitive information. While an ISMS based on ISO 27000 series has no particular flaws for general information systems, it is unfit to manage sensitive information for industrial control systems (ICSs) because the first priority of industrial control is safety of the system. Therefore, a new information security management system based on confidentiality, integrity, and availability as well as safety is required for ICSs. This new ISMS must be mutually exclusive of an ICS. This paper provides a new paradigm of ISMS for ICSs, which will be shown to be more suitable than the existing ISMS.

Advanced Approach to Information Security Management System Model for Industrial Control System

PubMed Central

2014-01-01

Organizations make use of important information in day-to-day business. Protecting sensitive information is imperative and must be managed. Companies in many parts of the world protect sensitive information using the international standard known as the information security management system (ISMS). ISO 27000 series is the international standard ISMS used to protect confidentiality, integrity, and availability of sensitive information. While an ISMS based on ISO 27000 series has no particular flaws for general information systems, it is unfit to manage sensitive information for industrial control systems (ICSs) because the first priority of industrial control is safety of the system. Therefore, a new information security management system based on confidentiality, integrity, and availability as well as safety is required for ICSs. This new ISMS must be mutually exclusive of an ICS. This paper provides a new paradigm of ISMS for ICSs, which will be shown to be more suitable than the existing ISMS. PMID:25136659

Implementation of Consolidated HIS: Improving Quality and Efficiency of Healthcare

PubMed Central

Choi, Jinwook; Seo, Jeong-Wook; Chung, Chun Kee; Kim, Kyung-Hwan; Kim, Ju Han; Kim, Jong Hyo; Chie, Eui Kyu; Cho, Hyun-Jai; Goo, Jin Mo; Lee, Hyuk-Joon; Wee, Won Ryang; Nam, Sang Mo; Lim, Mi-Sun; Kim, Young-Ah; Yang, Seung Hoon; Jo, Eun Mi; Hwang, Min-A; Kim, Wan Suk; Lee, Eun Hye; Choi, Su Hi

2010-01-01

Objectives Adoption of hospital information systems offers distinctive advantages in healthcare delivery. First, implementation of consolidated hospital information system in Seoul National University Hospital led to significant improvements in quality of healthcare and efficiency of hospital management. Methods The hospital information system in Seoul National University Hospital consists of component applications: clinical information systems, clinical research support systems, administrative information systems, management information systems, education support systems, and referral systems that operate to generate utmost performance when delivering healthcare services. Results Clinical information systems, which consist of such applications as electronic medical records, picture archiving and communication systems, primarily support clinical activities. Clinical research support system provides valuable resources supporting various aspects of clinical activities, ranging from management of clinical laboratory tests to establishing care-giving procedures. Conclusions Seoul National University Hospital strives to move its hospital information system to a whole new level, which enables customized healthcare service and fulfills individual requirements. The current information strategy is being formulated as an initial step of development, promoting the establishment of next-generation hospital information system. PMID:21818449

The Importance of Water for High Fidelity Information Processing and for Life

NASA Technical Reports Server (NTRS)

Hoehler, Tori M.; Pohorille, Andrew

2011-01-01

Is water an absolute prerequisite for life? Life depends on a variety of non-covalent interactions among molecules, the nature of which is determined as much by the solvent in which they occur as by the molecules themselves. Catalysis and information processing, two essential functions of life, require non-covalent molecular recognition with very high specificity. For example, to correctly reproduce a string consisting of 600,000 units of information (e.g ., 600 kilobases, equivalent to the genome of the smallest free living terrestrial organisms) with a 90% success rate requires specificity > 107 : 1 for the target molecule vs. incorrect alternatives. Such specificity requires (i) that the correct molecular association is energetically stabilized by at least 40 kJ/mol relative to alternatives, and (ii) that the system is able to sample among possible states (alternative molecular associations) rapidly enough to allow the system to fall under thermodynamic control and express the energetic stabilization. We argue that electrostatic interactions are required to confer the necessary energetic stabilization vs. a large library of molecular alternatives, and that a solvent with polarity and dielectric properties comparable to water is required for the system to sample among possible states and express thermodynamic control. Electrostatic associations can be made in non-polar solvents, but the resulting complexes are too stable to be "unmade" with sufficient frequency to confer thermodynamic control on the system. An electrostatic molecular complex representing 3 units of information (e.g., 3 base pairs) with specificity > 107 per unit has a stability in non-polar solvent comparable to that of a carbon-carbon bond at room temperature. These considerations suggest that water, or a solvent with properties very like water, is necessary to support high-fidelity information processing, and can therefore be considered a critical prerequisite for life.

New York State Educational Information System (NYSEIS) Systems Design. Volume I, Phase II. Final Report.

ERIC Educational Resources Information Center

Price Waterhouse and Co., New York, NY.

This volume on Phase II of the New York State Educational Information System (NYSEIS) describes the Gross Systems Analysis and Design, which includes the general flow diagram and processing chart for each of the student, personnel, and financial subsystems. Volume II, Functional Specifications, includes input/output requirements and file…

Information system life-cycle and documentation standards, volume 1

NASA Technical Reports Server (NTRS)

Callender, E. David; Steinbacher, Jody

1989-01-01

The Software Management and Assurance Program (SMAP) Information System Life-Cycle and Documentation Standards Document describes the Version 4 standard information system life-cycle in terms of processes, products, and reviews. The description of the products includes detailed documentation standards. The standards in this document set can be applied to the life-cycle, i.e., to each phase in the system's development, and to the documentation of all NASA information systems. This provides consistency across the agency as well as visibility into the completeness of the information recorded. An information system is software-intensive, but consists of any combination of software, hardware, and operational procedures required to process, store, or transmit data. This document defines a standard life-cycle model and content for associated documentation.

Requirements management: keeping your technology acquisition project under control.

PubMed

Carr, J J

2000-03-01

Whether you are acquiring clinical or business information systems, patient monitoring systems, or therapeutic and diagnostic systems, the odds are good that the project will be delivered late, will cost far more than predicted, and will not provide all the features promised. The principal reason for project failure is improper management of the requirements of the system. Requirements engineering and management is a skill from the systems engineering profession that can be learned by nearly any professional who is managing a technology acquisition project. The author discusses what requirements engineering and management is and how it is done.

Cyberspace Security Econometrics System (CSES)

DOE Office of Scientific and Technical Information (OSTI.GOV)

2012-07-27

Information security continues to evolve in response to disruptive changes with a persistent focus on information-centric controls and a healthy debate about balancing endpoint and network protection, with a goal of improved enterprise/business risk management. Economic uncertainty, intensively collaborative styles of work, virtualization, increased outsourcing and ongoing complance pressures require careful consideration and adaption. The CSES provides a measure (i.e. a quantitative indication) of reliability, performance, and/or safety of a system that accounts for the criticality of each requirement as a function of one or more stakeholders' interests in that requirement. For a given stakeholder, CSES accounts for the variancemore » that may exist among the stakes one attaches to meeting each requirement.« less