Open Data Network

Budget - Expenses - Fiscal Year 2019-2020

Budgeted expenses for the County of Marin for Fiscal Years 2019-2020; 2018-2019; 2017-2018; and 2016-2017. Each Fiscal Year begins July 1 and ends the following June 30. Expenses are broken out by department, program, and budget category.

new 1

New businesses registered with the Secretary of State Corporation Division during the previous month. Data is updated on the first working day of each month.

Saint Mary's County Full and Part Time Jobs By Industry: Historic 2001 to 2013 and Projected 2015 to 2040

Total Jobs by Industry, Historic 2001 to 2013 and Projected 2015 to 2040 in Saint Mary's County by Industry and by Place of Work

Baltimore County Full and Part Time Jobs By Industry: Historic 2001 to 2013 and Projected 2015 to 2040

Total Jobs by Industry, Historic 2001 to 2013 and Projected 2015 to 2040 in Baltimore County by Industry and by Place of Work

Native HI in tourism by education

Cultural and Recreational Services: Employment and Total Expenses

2015 - 2016 Student Discipline Annual Report- AGE

New York City Department of Education 2015 - 2016 Student Discipline Annual Report - AGE.

Expense Financial Plan - Exec

This dataset contains agency summary level data for PS, OTPS and Total by type of funds. The dollar amount fields are rounded to the thousands. The Executive Budget report, published in April or May, contains previous fiscal year actuals, the current fiscal year Executive budget, eight month actuals and forecast plus four out years of data which coincide with the release of the published financial plan.

MCG Personnel Management Review (PMR)

The Montgomery County Government has a diverse workforce of employees that cross five generations and multiple age, race, gender and ethnic groups. The dataset is a summary of the County's size and composition by generational category, age, race, ethnicity, gender, years of service and job class. Update Frequency : Annually

Automation of Safety Analysis with SysML Models

<p>To provide economical, reliable and safe access to space, design weaknesses should be identified earlier in the engineering life cycle, using model-based systems engineering. The slow manual approach to performing Failure Modes and Effects Analysis (FMEA) is a barrier to early identification of weaknesses. To semi-automate the identification of failure modes and causes use a prototype FMEA Assistant, including a library with standard terminology, to classify components associated with failure modes and automatically identify candidate functions, infrastructure and failure modes. This automation will reduce cost and increase coverage, standardization and reuse. Early identification of design weaknesses can substantially reduce rework costs later in the life cycle, which are all too common in the testing phase. Use of SysML will closely link safety analysis with the overall engineering process, resulting in smoother collaboration and safer vehicles and missions. The resulting reusable model would become part of the model-based system engineering process.<p/><p>This project was a small proof-of-concept case study, generating SysML model information as a side effect of safety analysis. A prototype FMEA Assistant was used to semi-automate safety analysis that identifies failure modes and causes, using a library with standard SysML-compatible terminology to classify components associated with failure modes and to automatically identify candidate functions, infrastructure and failure modes. FMEA analysts select from standard functions and failures to systematically narrow down failure mode selection (presented in automatically created pick lists). Standard terminology from an existing Aerospace Ontology is used to classify components and automatically identify candidate functions and failure modes. With automatically created pick lists, analysts can easily and correctly select standard functions and failures for a SysML architecture model as a side effect of using FMEA Assistant.  A white paper reports on a concept for using SysML profiles for safety analysis, to standardize FMEA-related terminology for reuse in several types of safety analysis (hazard analyses, fault trees, reliability block diagrams). See related project:  Failure Modes and Effects Analysis (FMEA) Simulation Tool</p>