Review standards with saved public change notes or run the live AI source update from Standards Overview.
Saved Customers
Customer profiles are shown here as simple cards with a short account description. Open a card only when you need the saved standards, projects, website, or hypercare controls.
Standards and Compliance Intelligence
Track cybersecurity and functional safety standards, add internal service notes, and watch public changes that may affect customer projects or hypercare outreach.
Standards and Regulations
Short, readable descriptions for standards used in testing, assessments, gap analyses, certifications, and market access planning.
Live standards enrichment uses the saved AWS API endpoint, fetches official source links in Lambda, and asks AI to summarize the source material.
Cybersecurity Standards and Regulations
Cybersecurity references for connected products, vehicles, OT, information security, software-defined systems, and market access requirements.
Functional Safety Standards
Functional safety references for vehicles, machinery, process systems, medical devices, and safety lifecycle assessments.
Market Access and Other References
Regional conformity, market-entry, and regulatory references that support assessments, certifications, and customer engagement planning.
Daily Watch Dashboard
Quick answer to the core question: which customers are tied to which standards, what changed, and who needs follow-up.
Decide whether a standard change is relevant for a saved customer, project, or hypercare account.
If outreach is needed, create a customer notification task and assign an owner and due date.
Mark the customer notified or close the review so the dashboard only shows active work.
Customers, tasks, reviews, and users sync through the saved API endpoint when Lambda has app-state storage connected.
Customer and standards enrichment can use the saved AWS endpoint. AI output still needs source review before customer use.
The hub creates follow-up tasks here. Email or Teams notifications are not connected yet.
Today's Command Center
Operational snapshot for reviews, owners, due dates, and customer notifications.
Open Impact Reviews
Customer-standard impact reviews that still need a decision, notification task, or closure.
Owned Follow-Up Tasks
Customer notification tasks created during impact review, grouped by priority and status.
Change Notifications
Impacted Customers
Standards Changed Recently
Notification Watch List
Customer-Standard Overview
This is the operating view: every saved customer, the standards attached to them, recent change exposure, and whether the customer is in notification watch.
Missing Links to Fix
These are the gaps that make the system less useful. Fixing them improves change impact alerts.
Settings
Administrative controls for deletion requests, customer-list maintenance, and AI backend connection settings. This area should be restricted before the hub is shared broadly. Team roles here are shared workspace settings until real authentication is connected.
Admin Area
Deletion requests and maintenance actions are staged here. Customer notification tasks are handled from the Daily Watch command center.
Team Members
Users here can own impact reviews and customer notification tasks. Shared user data is stored through the AWS backend when app-state storage is connected.
Daily Update Schedule
Admin-only schedule controls for a future daily standards and customer-watch update. This saves the preferred schedule to shared app state; it does not start an AWS automation yet.
Daily update automation is not connected yet.
AI Backend Configuration
API keys must stay in AWS Lambda environment variables. This browser page stores only the API Gateway endpoint URL used to call the secured enrichment backend for customers and standards source checks.
In the Lambda function, add an API Gateway HTTP API trigger with a POST route named /enrich.
Add ANTHROPIC_API_KEY, ANTHROPIC_MODEL, and ALLOWED_ORIGIN in Lambda environment variables.
Use the full API Gateway invoke URL. It may end in /enrich or in the Lambda trigger path AWS created.
Use the API Gateway endpoint connected to the enrichment Lambda.
S3 static site -> API Gateway HTTP API -> Lambda -> Claude Haiku -> optional DynamoDB -> future EventBridge watch