Cognite InField 9.0

We are very proud to present this major release of InField that offers you the option to add measurement readings to checklists based on templates. To include measurement readings in a checklist, you must first allow for this in the checklist template. You'll notice a new checkbox in the Create new template window.As you fill in the template items, you get the option to add fields for measurement readings. These fields are Name (required), Unit (required), and Min. and Max. values (optional). For checklists based on this template, the measurement reading fields are available on each checklist item. You can add and edit integers and decimal numbers, and if min/max values were added in the template, any deviations are marked with a red line.The PDF report you can create from either the checklist or the template also shows the measurement readings in a separate section.And there's more! Find operation IDs (if you're using SAP) or activity IDs (if you're using WorkMate) with the new filter field you'll see on the Checklist page when a work order has operations/activities attached. Note that on a mobile device, you'll find this menu option under the More options (...) icon. Vi har store nyheter i denne versjonen av InField! Nå kan du legge til måleravlesinger i sjekklister som er basert på maler. Først må feltene som skal brukes til måleravlesningen legges til i malen. Dette gjør du ved å merke avkrysningsfeltet Inkluder måleravlesninger i malen som du finner i vinduet Opprett ny mal.Når du deretter oppretter oppgaver i malen, kan du legge til felt for måleravlesninger. Disse feltene er Navn (påkrevd), Enhet (påkrevd) og Min. og Maks. verdi (valgfritt).For sjekklister som er basert på slik maler, er feltene for måleravlesning tilgjengelig for hver oppgave i sjekklisten. Du kan legge til og redigere heltall og desimaler, og avvik fra min. og maks.verdier vises med en rød strek.PDF-rapporten du kan opprette fra sjekklister og maler viser måleravlesningene i en egen seksjon.Filtrer på aktvititeter I denne versjonen kan du også enkelt finne frem til en aktivitet på en arbeidsordre med et nytt filtreringsfelt. Feltet vises på Sjekkliste-siden når en sjekkliste inneholder aktiviteter for arbeidsorder. På mobile enheter finner du dette menyvalget under ikonet Flere valg (...).#

Related products:Cognite InField

Cognite Data Fusion - April 2021 update

Cognite Data Fusion (CDF) is the industrial data operations and contextualization platform that makes traditionally siloed operational, engineering and IT data instantly available to users across the organization, enabling better decision making and intelligent workflow automation to improve operational performance.This release focuses on the end-to-end data journey with fast and secure authentication to all Cognite applications using your organization's IdP. We currently support Microsoft's Azure Active Directory (Azure AD).Also, speed up time spent getting value for operations using the new sample function for contextualization and add events to a Grafana dashboard to visualize and analyze your CDF data. Manage access with OpenID ConnectRegister the CDF portal application and other Cognite applications in your IdP (Identity Provider) and use OpenID Connect and your IdP framework to manage user and service principal (app) identities securely. We currently support Microsoft's Azure Active Directory (Azure AD).Visit the Manage access to CDF quickstart to learn more about the basic authentication concepts and terminology, secure access to CDF, and the different ways an application can access CDF data. Explore the docs for the technical details. SQL Transformations CLI and Cognite Extractors support OpenID Connect authenticationTransformations CLI users, scheduled transformation jobs, and Cognite extractors can now authenticate using OpenID Connect and Azure AD. Accelerate data set contextualizationSpeed up your contextualization with the entity_matching.suggest.fields function. Supply the function with data samples to return suggested fields you can use for entity matching in the API, SDK, or UI. Learn more here.Use existing matches to automatically generate matching rules to apply to all your data. Learn more here.Add input naming variations to the entity matching model to improve the suggested matches, for example, pmp for pump and bhp for bottom hole pressure. To create a list of synonyms, use replacements in the API. Learn more here. Visualize, track, and analyze events in GrafanaBoost your insights by adding the CDF events resource type to your Grafana dashboard. To visualize events, you can customize the time range and events to display and rename and organize columns according to your needs.By default, the events annotation query returns events that are active within a time range, but you can customize the query with additional time filters.Learn more: Visualize events Templates (Early adopter program)With Templates, you build your view of the data you have available in CDF and simplify the applications and solutions you are working on by accessing data through templates. Templates remove the gap between the application’s data model and the preexisting structure of the relevant data. It is easy to scale your solution across more data without changing or redeploying your application code or configuration. Instead, you can work with your template in CDF, and use the tooling available to scale to more data with governance.Learn more: Manage templates Charts (Early adopter program)Use Charts to explore, trend, and analyze industrial data. Find, understand, and troubleshoot for actionable insights from time series and contextualized P&IDs already in the CDF portal application or other Cognite applications then share the chart for collaboration. Charts runs securely with a single, secure sign-in.Learn more: Get started with ChartsNOTETo join an Early Adopter program, contact your Cognite representative.

Related products:Cognite Data Fusion

Cognite’s new identity provider support is here!

At last, Cognite’s long awaited standard support for external identity providers is here! Over the last year or so, it has been referred to as "native token", "OIDC support", "support for Azure Active Directory", and "proper OAuth2". Alas, it can be hard to understand, so let me try to explain in "not-so-technical" terms what all this is about.So, what do our customers get with this release that they didn’t have before? We have supported external identity providers, like Google login before, right?The answer is simple: they now get total control over who can access what data in Cognite Data Fusion (CDF) and which applications the users can use, and which applications are allowed to access data. No more extractors or applications that can run as long as you have an API key. And no more mix of accounts created in Cognite Data Fusion and the identity provider like Azure Active Directory (AAD) or Google. Access control is now enterprise grade and according to how enterprises typically manage access internally for other applications and services.Give me the 5-minute spiel…!Alright, hold on tight! This section is to arm you with the basic understanding!Your customer needs an Identity Provider that supports standard OAuth2 and Open ID Connect (OIDC) AND the ability to share security group memberships into the so-called OAuth2 token. Google does not support this last bit, Azure Active Directory (AAD) does, and in this release, we have fully tested and validated Azure Active Directory.The customer CDF project is first configured to trust the customer’s instance of Azure Active Directory, and then AAD is configured to recognise the CDF SaaS service. This allows users to log in with their corporate account. Then, groups are created in CDF for each set of access rights needed by something or someone connecting to CDF: users, applications, extractors, dashboards, Power BI, and so on. To be precise, this is not one group per entity accessing CDF, but just one group per each set of access rights. Each group is then configured to map to a corresponding group in AAD by using the id of the group in AAD.For each user that will access CDF, the customer uses the existing company user accounts and adds them to one of these AAD groups that are mapped to CDF groups. For each piece of code (like applications, extractors, dashboards and so on) to grant access to, they create a so-called app registration in Azure Active Directory and adds them to the correct group(s).When CDF receives a request for access, it will check the identity of the connecting user or application by receiving a "statement of access rights" (a token) from the customer’s Azure Active Directory. Through this token, CDF can verify the identity, get the list of group memberships and grant access to the right data!This means that it’s not possible anymore to create a service account in the CDF project and use an API key to access data (i.e. once the project is configured with an external Identity Provider).Give me more!"That’s fine, but I really want to understand a bit more than that!"Alright then, read on! This section introduces the basic concepts of cloud service authentication and authorisation in a way everybody(?!) can understand. The basic building blocks are introduced first, before these are explored using an analogy of a hotel room with key cards to control access.A crash course in the basic conceptsAt its core, the problem is very simple: you go to an application living on a web page (let’s say https://fusion.cognite.com/ and prove your Identity (typically your email address) by using a password, a one-time code, or another way to prove that you are you. The web page will guide you through the login process, but in the background, it will contact a service that has a register of people (i.e. identities) who are allowed to access this application. This service is called the "Identity Provider". Typically, when you log into Facebook or another web app, you see no difference between the two. Facebook is its own Identity Provider.When you work for a company, your company typically has its own Identity Provider, like Azure Active Directory (AAD). If you as a corporate user can log into many different applications and systems using the same username/email and password (i.e., you are "authenticating" using the same Identity), it’s because all these will communicate and authenticate with the same Identity Provider owned by your company. Now we can introduce another challenge: what if you have access to an application your colleague does not have access to? This is referred to as "authorization", knowing where and what you have access to.So, to summarize: we have the Identity (who to approve access for), the Identity Provider (the decision maker verifying your identity and granting access), the process of authenticating (verifying that you are the identity you claim to be), and finally authorization (granting you access to the application you want to access). There’s one final and important thing to understand: the application you access in your browser is the "go-between" in the interaction between you and the Identity Provider to verify your identity and grant you access. But exactly what do you get access to? The application in your browser itself or the data in CDF in the cloud? Or both?In fact, as long as you sit in front of your browser, the browser app will communicate with the cloud CDF services as if it’s you. Practically, this is done by an elaborate process to give the web app a token. This token is basically a very targeted key to get access to your data using your identity and it will expire quickly, so it will have to be refreshed regularly (which happens in the background). We say that the web application is a client and that the CDF cloud services is the resource that the client accesses.In the case of an extractor or if you make a python application where you use the CDF SaaS service directly, the extractor or application could of course do the same as the CDF Fusion application and be a client that uses a token that gives access to your data. However, since these applications may run over longer time (and a token is short-lived) and without you watching over them, it makes more sense to give them their own identity instead of using yours. This identity is often called a service principal to differentiate them from people identities.A hotel room as an analogy"Wow, that was a bit rough… How can I get my head around this?!"It is often easier to keep things straight in your head if it’s possible to relate all the terms to something you already know, something physical. So, let’s use a hotel room with a key card and lock as an analogy. You have reserved a room (the resource to access, so this is the CDF SaaS service). At the front desk, they register your identity in the hotel computer system. From here on the hotel computer system will act as the identity provider.Now you will get a key card that will open the lock to the right door for a time-limited period (authorised by the hotel system). The key card is the token you use to get into the room. As you probably recognise, you are now acting as a service principal, you access your own resource (the room) with your own identity, and you use a token that is made out to you. You enter the room and find that the lights are not working. You return to the lobby and requests that it’s fixed while you eat a snack in the restaurant. As this is a security conscious hotel, they request you to authorise access to the room for their janitor the next hour only. You approve, and the janitor’s key card is updated with access to the room.As you order your food, the janitor accesses the room exactly the way your web browser accesses CDF cloud services, both are authorised by you with time-limited access, but now the janitor (the browser) uses a key card (token) issued to him that gives access to the room (the resource), and you used your identity to authorise the janitor to get the token (similar to logging in).Trust is established and kept through these exchanges between you, the front desk, the hotel security system, the lock on the door, and by loading tokens onto the key cards that are used to open the lock. Trust is essential to any computer system. The various software components involved, like the app in the browser, the CDF SaaS services, and the Identity Provider, all need to communicate with each other and trust each other. Very often security issues arise as a result of a weak way of establishing trust. For example, if you used your passport to prove your identity to the hotel the first time, that may have been a strong trust. However, if you only have to say your name the next time, the trust chain is broken because anybody can walk into the hotel and claim they are you. The security of the rest of the system does not matter anymore.If you still have appetite for more, head over to the quickstart course and the configuration documentation!

Related products:Cognite Data Fusion

Cognite InField 8.4

Select different states for elements in a checklist based on a template. The available states depend on the setup of the template. Here you see the full range.To include these states when you create a template, use the new option Checklist states in the Create new template window. Select the states you want to use, but note that To do and OK are required. When you have created a template, you can click Template settings on top of the page to re-visit this window and make further changes.If a checklist is already created from the template, no template updates are displayed in the checklist. These will only be visible in the checklist created in the first calendar week following the template update.The checklist states are also reflected if you create a PDF report. The Complete column shows an overall status, and each weekday is marked with one of the state icons.We've also made some minor improvements. Click a tag in a checklist, and the Tag page opens, then go back, and InField will navigate back to your starting point and highlight the tag you clicked. You'll also see that re-ordering long lists on templates now scroll flawlessly. This was an issue for some users running Infield on Windows OS.  Nå kan du velge blant ulike statuser for oppgaver i sjekklister som er basert på en mal. Hvilke statuser som vises, avhenger av oppsettet til malen. Her ser du alle.For å inkludere ulike statuser når du oppretter en mal, bruker du det nye valget Status - sjekklister i vinduet Opprett ny mal. Velg de statusene du vil bruke, men merk at Skal utføres og OK må brukes. Når du har opprettet en mal, kan du klikke Innstillinger for mal, som du finner øverst på siden, for å åpne dette vinduet på nytt og gjøre flere endringer.Hvis en sjekkliste allerede er opprettet fra denne malen, vises ikke oppdateringer av malen i denne sjekklisten. De vises i sjekklisten som opprettes i første kalender-uke etter oppdatering av malen.De ulike statusene vises også når du åpner en PDF-rapport fra en sjekkliste. Kolonnen Utført viser en sammenlagt status og hver ukedag viser de ulike status-ikonene.Denne versjonen av InField innholder også noen mindre forbedringer. Klikk på en tagg i en sjekkliste og gå deretter tilbake. InField navigerer til utgangspunktet og fremhver taggen du klikket på. Vi har også fikset en feil med sortering av lange lister i maler som oppsto for noen av brukerne som kjører InField på Windows OS. 

Related products:Cognite InField

Cognite Data Fusion - February 2021 update

Cognite Data Fusion (CDF) is the industrial data operations and contextualization platform that makes traditionally siloed operational, engineering and IT data instantly available to users across the organization, enabling better decision making and intelligent workflow automation to improve operational performance.This release focuses on improving usability across CDF as well as laying the foundation for future features. We are also very proud of our Cognite Power Bi Connector, which is now certified by Microsoft. The Cognite Power BI Connector is out of BetaWe're excited to announce that Microsoft has certified the Cognite Power BI Connector and that the connector is now out of Beta. The Cognite Power BI Connector enables data consumers to easily read, analyze, and present data from Cognite Data Fusion (CDF) in compelling visualizations in Power BI Desktop and the Power BI service.You can find the connector in the Other category of the Get Data dialog in Power BI. Learn more in our in-depth article.Enrich contextualized assets with 3D modelsIncrease the value outtake of contextualization by connecting assets to a 3D model with the new easy-to-use option under Match entities in the CDF user interface. Visually inspect assets and zoom into details to get tangible information.Learn more: 3D contextualizationAccelerate finding and filtering relevant dataFinding the data you need is now even easier in the CDF Data explorer. Navigate between different parts of CDF with the new drop-down navigation in the top bar and shift between multiple CDF resources with more descriptive tab names.Use the new Quick search in the top navigation to search for the resource names and explore data from anywhere in CDF. Filter on metadata and hide the empty fields for any resource and show aggregated values of metadata keys for assets to get unique values ordered by frequency (if enabled in the API). You'll also notice that date points are added to the time series sparkline to better visualize missing data for a given range.Learn more: Data explorerLabels and relationships in SQL transformationsCreate and delete data related to the Relationships and Labels resource types when you use SQL queries in CDF Transformations to transform data from the CDF staging area into the CDF data model.Learn more: CDF TransformationsEnhanced results page for entity matching pipelinesGet more information about the results, rules, and rule conflicts for matches from your Entity matching pipelines in CDF and improve rule predictions by selecting particular matches to CDF.Learn more: Entity matching 

Related products:Cognite Data Fusion