CoBaseKRM’s Features
One Framework for Managing Your Research & Engineering Knowledge
KRM or Knowledge Relationship Management is a new paradigm for guiding & managing engineering thinking & project design. With CoBaseKRM, you can guide your teams thinking and behaviour to follow your processes, workflows, & best research pratices.
Network Map
Track and manage your work by recording project steps as nodes and storing data in each node.
Data Governance
Keep data formatted consistently across your organization so data is easy to find, understand, and utilize.
Collaboration
Collaborate and assign access levels and restrictions. Protect intellectual property. Work effectively and seamlessly.
Network Map
Record Research Initiatives in Full Detail
Build project histories in real time, documenting the data, conversations and documents produced every step of the way.
Explore Solutions and Innovate in Real Time
Research is fluid. Innovate and explore new approaches, make project pivots and track research changes.
Make Connections In Your Research
Explore data and build connections between research steps with linking parameters to uncover relationships between data sets and make discoveries.
Share Results with Automated Reporting
Share your results with others through CoBaseKRM's automated reporting. Package results and supporting data for easy editing and sharing. Deliver compelling, actionable outcomes.
Nodes
Data from research, experiments, analyses are stored in nodes. Each node stores the data, documents and conversations that took pace during the research activity represented by the node.
There Are Three Node Types:
Hypothesis Node
By default, the first node in a network map. Hypothesis nodes serve as the repository for the research objective, preliminary data, citations and pertinent notes.
Includes: Wiki, section to upload preliminary data such as databases or spreadsheets
Experiment Node
The standard node for uploading and managing research data. CoBaseKRM looks after the tedious work of logging every entry and keeping data units standard, which allows researchers to focus on their work.
Includes: Wiki, Data, Discussions, Protocol, Recipe, Inventory, Tasks
Conclusion Node
When results are achieved, researchers can create conclusion nodes. This gives researchers the ability to select past data and pertinent findings, and importing that data in one location for easy reporting.
Includes: Wiki, Data, Report
Custom Node
Everyone's work is different. Create custom node categories or node types for your unique process steps or experimentation.
Includes: Wiki, Data, Discussions, Protocol, Recipe, Inventory, Tasks
Data Stored In Nodes
Nodes store quantitative, qualitative, and contextual information from each experiment. Below, we will explore the specific data formats nodes offer.
Quantitative Observations
Stored as Data Templates
CoBaseKRM stores quantitative information inside structured data tables. Tables use parameters and observations to structure data across all projects and nodes.
You can upload your data from directly to CoBaseKRM or from a spreadsheet using CoBaseKRM's spreadsheet validator.
Qualitative Observations
Stored as Electronic Lab Notebook (ELN) Journal Cards
CoBaseKRM offers a feature called ELN 'Journal Cards'.
The key difference with journal cards is that they are tightly connected to every aspect of the knowledge work: parameter, experiment, observation, analyst, model.
Journal cards allow researchers to keep personal notes, while the rest of the team can access mission-critical notes as journal cards in each node.
Documents, Messages and Wikis
Referenced Through API Tags
CoBaseKRM stores supplementary information from documents, files, digital messages, and team wiki entries. This information is integrated into project nodes through APIs and tagging,
Allowing users to share messages and documents through their communication platforms and pin critical messages and documents to nodes.
Uploading Data With the CoBaseKRM Spreadsheet Validator
Data that is uploaded to CoBaseKRM are maintained under data version control (DVC)
When you want to upload your data, CoBaseKRM's validator examines your spreadsheet to make sure your parameters continue to match those in the CoBaseKRM data table, insuring consistent structured data & uunits
Node data tables have unique ID tags for each parameter that can be assigned when designing projects.
Using ID tags, CoBaseKRM produces spreadsheets with the same ID tags automatically included, allowing you to format your spreadsheet however you like without changing how data is structured in CoBaseKRM.
CoBaseKRM's validator examines your spreadsheet to make sure that your parameters, the factors and responses involved in the research, follow your standards. This ensure consistent and correct naming and structure and that means that it can be found and even repurposed, multiple times.
Regulatory Inquiries
All activities are tracked and reside in an audit log and data are version controlled ensuring that you are always audit-ready.
Regulatory Inquiries Instead of requiring a team to attend multiple meetings over days, weeks, or even months to identify and collate details, an individual can do so more efficiently on their own, in hours, if not minutes.
Data Version Control
Any data that is uploaded directly to CoBaseKRM or through the spreadsheet uploader are recorded via data version controlling.
No matter what happens, whether someone accidentally overwrites data, or new data is uploaded in place of old data, that change is recorded and shown in the record history of that record and the node that contains it. Additionally, a log is maintained for audit purposes.
Data version control is at the heart of the Spreadsheet Validator, mentioned above. Using data version control, the validator detects changes between records that were uploaded, ensuring that uploaded data is correct when entered into CoBaseKRM.
Data Governance
Data governance is essential to project success. CoBaseKRM's actionable data governance tools make keeping parameter titles, units, and project data consistent across your organization.
Globally Define Your Units
CoBaseKRM lets managers define a global set of units to be used across all of their organization's projects. This ensures that every data table produced by your teams uses consistent units.
Create Parameters
Select and assign research factors and responses to parameters. In CoBaseKRM, every parameter has a unique ID that allows data to be indexed and easily searchable. You can update parameter names any time with historical data now being searchable by new names or edits of parameters namese
Create and Assign Dataset Templates to Projects
Reduce time designing datasets. Create a dataset template and assign many research steps and projects.
Search
Find project data immediately. CoBaseKRM's Search Engine provides instant access to the data you require, and eliminates wasted time searching manually.
Repurpose your prior knowledge work instead of regenerating it by easily finding relevant prior experiments. Conduct machine learning on observations collected across experiments. Review the related journal cards to see what others have said about observations, experiments and models. Add your own thoughts.
Find Project Data
Search projects by parameter to recover important project data and share instantly with others.
Apply Historical Data
Solve new problems with the data that you already own.
Search for and apply historical data to your current analytical work.
Win Regulatory Audits
Search for and share complete project datasets to support regulatroy audits.
With search, you can produce any data point from your research work.
Collaboration: User Access
CoBaseKRM uses Role-Based Access to grant and restrict what users can do.
Customize user access to your needs, control who can access & see your data. With Role Based Control Access, you will be in control of who gets access and who doesn't.
System Administrators (IT / CTO)
Purchaser or the “True Tenant of the Account.” All permissions. Define data governance standards, build data templates, assign tasks, design experiments, manage progress.
Ability to customize permissions for lower roles, giving some or all management permissions. Restricted from billing abilities.
Audit logs
Our Audit Logs provide regulatory compliance with title 21 CFR Part 11, GDPR, GLP & GMP. Track file deletions, changes to data, uploads, downloads, and people who perform these actions. Any changes made to the system can be reported in the system and the Audit log can be easily download.
CoBaseKRM ensures Data Integrity across the application by recording & logging data changes with our Data Version Control and Audit Log.
