• LinkedIn
  • Subcribe to Our RSS Feed
Apr08

Permissions in CORE - Part 1

by bmaddox

CORE’s access control and project permissions give you the complete control over access to CORE as well as projects, elements, and even individual attributes if desired. This article is the first in a two part series of posts related to access control and permissions. Let’s first discuss the foundation of permissions, managing users and groups.


CORE is packaged with a single user account (Administrator) with the default password of “admin”. This Administrator account (or any account with system administrator privileges) can create and delete CORE user accounts from the Users and Groups segment of the Administrative Tools panel. (To access the Administrative Tools panel, log into CORE and click Tools > Administrative Tools.)



The User Properties window is opened by double-clicking on a user and allows the CORE system administrator to edit individual user account properties. Here you can set the password, force the user to change their password, disable the account and more. Under User Privileges you can grant specific system permissions to the user.


The System Administrator option will grant the user CORE system administrator privileges. This will grant the user access to the Users & Groups tool, allow administration of sessions, the API, and CORE2net. This option is only set by automatically for the default Administrator account.


Project Creation will allow the user to create a new project. This is recommended for all users and is granted to new users by default. If you wish to restrict this privilege, you must manually remove this option after creating a new user.


We recommend two best practices in relation to User accounts:

  1. Use the default Administrator only for system administration. Even you if you are using CORE in a Local Repository for a single-person project, login using a separate user account to do your work.
  2. If your company policy permits this, disable a user account rather than deleting the user. This will maintain the history of user access.

Groups are a collection of user accounts and have the same permission properties as a user account. When permissions are granted to a group all members of the group receive those permissions as well. A user can be a member of more than one group. Over time, groups are far more stable than individual team members who may join/leave the team or change roles. It’s considered a best practice in CORE to grant permissions to groups rather than individuals. When your team changes, you can simply change the group membership, rather than adding or removing permissions (which may be very in depth) for individuals.


Groups are created using the Users and Groups section of the Administrative Tools panel. Double click on a group to view the Group Properties window.



CORE is packaged with a single group, All Users, that includes the Administrator account. As new accounts are created they are added to the All Users group automatically.


The second post in this series will address Permissions. Do you have a questions about Access Control? Post a comment and I’ll address it!


Tags: , , , , , ,

Categories: CORE Software | Tips and Tricks | Vitech

Feb17

A Primer for Model-Based Systems Engineering

by Administrator

Vitech is pleased to announce the electronic publication of our MBSE Primer. The document in its entirety can be downloaded below.


A Primer for Model-Based Systems Engineering


The primer addresses the basic concepts of model-based systems engineering. It covers the Model, Language, Behavior, Process, Architecture and Verification and Validation. It is a call to the consideration of the foundational principles behind those concepts. It is not designed to present novel insights into MBSE so much as to provide a guided tour of the touchstones of systems design. It is a guide to the new MBSE acolyte and a reminder to the experienced practitioner. It is suitable for use by a systems engineer new to the practice of “model-based” systems engineering, an experienced systems engineer who has been introduced to “model-based” concepts in an ad hoc fashion or by any professional knowledgeable of systems thinking and practice. It is not intended as a comprehensive guide or as practice handbook.


Why such a basic approach? Without this grounding it can become easy to lose the sense of relationship between techniques and the design itself. For example, reading and pondering the sections on Models and Language bring into focus the difference between representations of the model and the model itself. A map may be an extensive, informative and important representation of the underlying terrain represented but it is simply that- a representation. Likewise, a set of diagrams may be useful, clear and detailed but they are not the model of the system itself. Without returning to the concepts of model, language, process and behavior we can easily become mistakenly convinced that the process of drafting a “full set” of representations is the same thing as constructing a model. It is in understanding the basics that we understand the distinctions.


The importance of knowing and executing the basics is the driving force behind this primer. It is the reason for not beginning with a collection of essays on more advanced topics. This revisiting of the basic aspects of model-based systems engineering (MBSE) is the foundation and the first step of our journey to advance the cause of sound systems design. We look forward to your comments and your company as we journey onward. We have dedicated a section of our Forums to facilitate the opportunity for discussion.


Tags: , , , ,

Categories: MBSE | Primer

Jan25

Vitech MySupport Resources

by bmaddox

The Customer Care Team here at Vitech has been working hard lately to expand the resources that we make available to our customers. One tangible result of that effort is the new MySupport section of our website. This section is open to all customers who are current on maintenance. Simply register using your serial number and you will have access.


Here’s a quick rundown of what you’ll find there:


Priority Support Request – By using this support request form, we’ll bump your request up to the top of our list. We’re not often queued up, but when we are, we’ll escalate you to the top of the queue.


Live Web Chat Support – This option also bumps you right up to the top. We’re logged in Monday through Friday 9-6 EST.


Knowledge Base – For the last few years, we’ve been documenting our most common questions and their answers. Here you’ll find a searchable database of that information. These are detailed answers that often have step by step instructions. This is a great option if you prefer self-service solutions, or have questions after hours.


Premium Screencasts – This is the section I’m most proud of. It’s safe to say that this is my “baby” here at Vitech. I’ve been recording these video tutorials just for our customers. In fact, today I’m releasing a new screencast. The latest installment is related to CORE 7 and covers Users and Groups. There will be many more screencasts to come. If there’s a topic you’d like to see covered, let me know.


Premium Webinars – You’ll find a list of the webinars we are hosting that are exclusively for our existing customers. We have one today that introduces our MBSE Primer. Have you signed up yet?


If you haven’t yet registered to use the MySupport section of our website, now is the time. Let me know what you think? Are we missing a resource that you would find valuable?

Tags: , , ,

Categories: Primer | Tips and Tricks | Vitech

how to catch a cheater