{"text_format":"1","workbook":"xlsx","n_sheets":2,"sheets":["AspectsConcerns","print"],"not_rendered":{"charts":0,"images":0,"macros":1,"external_links":0,"defined_names":2,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"AspectsConcerns","index":0,"n_rows":115,"n_cols":13,"rows_kept":115,"cut":false,"hidden":false,"merged":[]}
[{"$f":"NOW()","v":"2016-10-07T14:25:31.200"},null,null,null,"CPS Framework: Aspects and Concerns"]
[]
[null,null,"Technology level (Device, System, System of Systems)"]
[null,null,"Technology scope description (text)"]
[null,null,"Zone of Concerns (text -- Enterprise, Field, Mobile, Premises)"]
["Nest","Concern","Aspect/Concern","Source","Description","Is Concern Discussed (y/n)?","Discussion of Concern","Discussion Reference(s)","Is a Solution Provided?","Solution","Solution Reference(s)","External References","Additional Notes"]
[0,"Functional",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A7),\" \",AspectsConcerns!B7)","v":" Functional"},"CPSFramework","Concerns about function including sensing, actuation, control, communications, physicality, etc.","yes","in general","n/a"]
[1,"physical actuation",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A8),\" \",AspectsConcerns!B8)","v":"      physical actuation"},"CPSFramework","Concerns related to the ability of the CPS to effect change in the physical world.","yes","in general","n/a"]
[1,"communication",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A9),\" \",AspectsConcerns!B9)","v":"      communication"},"CPSFramework","Concerns related to the exchange of information internal to the CPS and between the CPS and other entities.","yes","in general and interworking technologies","n/a"]
[2,"Syntactic Interoperability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A10),\" \",AspectsConcerns!B10)","v":"           Syntactic Interoperability"},"GWAC-Syntactic Interoperability(3)","Concerns about the presentation and exchange patterns of data","not applicable"]
[3,"OSI-Application",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A11),\" \",AspectsConcerns!B11)","v":"                OSI-Application"},"OSI-Application(7)","Concerns about application layer exchange patterns","yes","oneM2M service layer resides on top of application layer(e.g. HTTP, CoAP).","TS-0001","yes","oneM2M service layer resides on top of application layer(e.g. HTTP, CoAP).","TS-0001"]
[3,"OSI-Presentation",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A12),\" \",AspectsConcerns!B12)","v":"                OSI-Presentation"},"OSI-Presentation(6)","Concerns about the syntax of message encoding","yes","commonly used serialization scheme should be provided","TS-0004","yes","XML and JSON serialization","TS-0004 clause 8.3 for XML, 8.4 for JSON","W3C, Extensible Markup Language (XML) 1.0 \nW3C XMLSchemaP2: \"W3C Recommendation (2004)\nIETF RFC 7159: \"The JavaScript Object Notation (JSON) \nIETF RFC 2045: \"Multipurpose Internet Mail Extensions (MIME) Part One"]
[2,"Network Interoperability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A13),\" \",AspectsConcerns!B13)","v":"           Network Interoperability"},"GWAC-Network Interoperability(2)","Concerns about networked message exchange","not applicable"]
[3,"OSI-Session",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A14),\" \",AspectsConcerns!B14)","v":"                OSI-Session"},"OSI-Session(5)","Concerns about session creation, maintainance, and tear-down","yes","application session should be supported","TS-0002 OSR-003","yes","study for service layer session (re-usable service layer context) and solution for security sessions","TR-0020 and TS-0003","RFC 4566 - SDP: Session Description Protocol\nIETF RFC 5246: \"The Transport Layer Security (TLS) Protocol Version 1.2\"\nIETF RFC 6347: \"Datagram Transport Layer Security Version 1.2\""]
[3,"OSI-Transport",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A15),\" \",AspectsConcerns!B15)","v":"                OSI-Transport"},"OSI-Transport(4)","Concerns about information transport","yes","oneM2M is basically over the IP","TS-0002","no"]
[3,"OSI-Network",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A16),\" \",AspectsConcerns!B16)","v":"                OSI-Network"},"OSI-Network(3)","Concerns about networked exchange","yes","oneM2M is basically over the IP","TS-0002","no"]
[2,"Basic Connectivity",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A17),\" \",AspectsConcerns!B17)","v":"           Basic Connectivity"},"GWAC-Basic Connectivity(1)","Concerns about connectivity of CPSDevices","not applicable"]
[3,"OSI-Data Link",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A18),\" \",AspectsConcerns!B18)","v":"                OSI-Data Link"},"OSI-Data Link(2)","Concerns about data links","yes","oneM2M is basically over the IP","TS-0002","no"]
[3,"OSI-Physical",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A19),\" \",AspectsConcerns!B19)","v":"                OSI-Physical"},"OSI-Physical(1)","Concerns about physical communication links","yes","oneM2M is basically over the IP","TS-0002","no"]
[1,"controllability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A20),\" \",AspectsConcerns!B20)","v":"      controllability"},"CPSFramework","Ability of a CPS to control a property of a physical thing. There are many challenges to implementing control systems with CPS including the non-determinism of cyber systems, the uncertainty of location, time and observations or actions, their reliability and security, and complexity. Concerns related to the ability to modify a CPS or its function, if necessary.","yes","discussed in general"]
[1,"functionality",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A21),\" \",AspectsConcerns!B21)","v":"      functionality"},"CPSFramework","Concerns related to the function that a CPS provides.","yes","common functions should be provided as a service layer platform","TS-0001","yes","all the common services function(CSF)s","TS-0001 clause 6.2"]
[1,"measurability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A22),\" \",AspectsConcerns!B22)","v":"      measurability"},"CPSFramework","Concerns related to the ability to measure the characteristics of the CPS.","yes","in general"]
[1,"monitorability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A23),\" \",AspectsConcerns!B23)","v":"      monitorability"},"CPSFramework","Concerns related to the ease and reliability with which authorized entities can gain and maintain awareness of the state of a CPS and its operations. Includes logging and audit functionality.","yes","charging and accounting related requirements are defined","TS-0002 clause 6.5 and 6.6","yes ","charging and accounting are supported as resource API by a service provider cloud. also event logging function is supported by devices/gateway/cloud\n(this is only valid for the Infrastructure Domain)","TS-0001 clause 9.6.23 to 9.6.25","IETF RFC 3588: \"Diameter Base Protocol\"."]
[1,"performance",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A24),\" \",AspectsConcerns!B24)","v":"      performance"},"CPSFramework","Concerns related to the ability of a CPS to meet required operational targets.","yes","design principles","TS-0004","no"]
[1,"physical",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A25),\" \",AspectsConcerns!B25)","v":"      physical"},"CPSFramework","Concerns about purely physical properties of CPS including seals, locks, safety, and EMI.","no (out-of-scope)"]
[1,"physical context",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A26),\" \",AspectsConcerns!B26)","v":"      physical context"},"CPSFramework","Concerns relating to the need to understand a specific observation or a desired action relative to its physical position (and uncertainty.) While this information is often implied and not explicit in traditional physical systems, the distributed, mobile nature of CPS makes this a critical concern.","yes","E.g. geo-graphic location information can be provided to applications","TS-0001","yes","locationPolicy resource type provides a means of getting oneM2M entity's location info."]
[1,"physical sensing",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A27),\" \",AspectsConcerns!B27)","v":"      physical sensing"},"CPSFramework","Concerns related to the ability of a CPS to develop the situational awareness required to perform to its function.","yes","E.g. location information and semantic information should be supported","TS-0002 OSR-047/48 and clause 6.3","yes","location information can be delivered to applications and even can be used for access control as context information. semantic information is supported, so semantic query is also enabled.","TS-0001 clause 9.6.10 and 9.6.30","W3C RDF 1.1 Concepts and Abstract Syntax.\nW3C SPARQL 1.1 Query Language.\nOMA-TS-MLP-V3-4-20130226-C: \"Mobile Location Protocol\", Version 3.4.\nOMA-TS-REST-NetAPI_TerminalLocation-V1_0-20130924-A"]
[1,"uncertainty",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A28),\" \",AspectsConcerns!B28)","v":"      uncertainty"},"CPSFramework","Managing the effects of uncertainties is a fundamental challenge in CPS. Sources of uncertainty in CPS can be grouped into statistical (aleatoric), lack of knowledge (epistemic) uncertainty, or systematic uncertainty. In CPS statistical uncertainty is caused by randomness of accuracy of sensing and actuation, often caused by uncertainty of manufacturing processes. Systematic uncertainty is caused by incomplete knowledge either due to limits of acquired knowledge or due to simplification in modeling. Typical manifestations of epistemic uncertainty are limited validity of models of physical processes or limits of computability of properties of mathematical models.","no (out-of-scope)"]
[1,"statesAndModes",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A29),\" \",AspectsConcerns!B29)","v":"      statesAndModes"},"GWAC - Transaction & State Mgt(CC)","Concerns about states and modes of a CPS.","yes","in general","n/a"]
[1,"manageability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A30),\" \",AspectsConcerns!B30)","v":"      manageability"},null,"Concerns about managing a CPS through its life cycle."]
[2,"configurationManagement",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A31),\" \",AspectsConcerns!B31)","v":"           configurationManagement"},"FCAPS - Configuration Management, \nFCAPS - Administration Management,\nNISTIR SG.CM","configuration management is a key functional concern with dimensions of configuration, versioning, ...","yes","M2M device/gateway configuration should be supported","TS-0002","yes","Interworking with exisitng Device Management technologies such as OMA DM, LWM2M, BBF-TR-069","TS-0005/6/14","Broadband Forum TR-069: \"CPE WAN Management Protocol Issue\"\nOMA-DM: \"OMA Device Management Protocol\"\nLWM2M: \"OMA LightweightM2M\""]
[2,"configurationForLeastFunctionality",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A32),\" \",AspectsConcerns!B32)","v":"           configurationForLeastFunctionality"},"NISTIR SG.CM-7","Concerns about minimizing the configuration needed.","yes","zero-configuration concept was discussed"]
[2,"Component Inventory",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A33),\" \",AspectsConcerns!B33)","v":"           Component Inventory"},"NISTIR SG.CM-8","Concerns about component inventory and versioning.","no"]
[0,"Business",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A34),\" \",AspectsConcerns!B34)","v":" Business"},"CPSFramework","Concerns about enterprise, time to market, environment, regulation, cost, etc.","no (out-of-scope)","the whole \"business\" section may need to get feedback from SC not TP"]
[1,"enterprise",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A35),\" \",AspectsConcerns!B35)","v":"      enterprise"},"CPSFramework","Concerns related to the economic aspects of CPS throughout their lifecycle.","no (out-of-scope)"]
[1,"reputation",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A36),\" \",AspectsConcerns!B36)","v":"      reputation"},"ConsensusPPI","Concerns related to the repuation of the enterprise as effected by the CPS.","no (out-of-scope)"]
[1,"cost",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A37),\" \",AspectsConcerns!B37)","v":"      cost"},"CPSFramework","Concerns related to the direct and indirect investment or monetary flow or other resources required by the CPS throughout its lifecycle. ","no (out-of-scope)"]
[1,"environment",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A38),\" \",AspectsConcerns!B38)","v":"      environment"},"CPSFramework","Concerns related to the impacts of the engineering and operation of a CPS on the physical world.","no (out-of-scope)"]
[1,"policy",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A39),\" \",AspectsConcerns!B39)","v":"      policy"},"CPSFramework","Concerns related to the impacts of treaties, statutes, and doctrines on a CPS throughout its lifecycle.","no (out-of-scope)"]
[1,"quality",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A40),\" \",AspectsConcerns!B40)","v":"      quality"},"CPSFramework","Concerns related to the ease and reliability of assessing whether a CPS meets stakeholder (especially customer) expectations.","no (out-of-scope)"]
[1,"regulatory",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A41),\" \",AspectsConcerns!B41)","v":"      regulatory"},"CPSFramework","Concerns related to regulatory requirements and certifications.","yes","certification program is under construction","TP-2016-0180-CT Report to TP24","on-going"]
[1,"time to market",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A42),\" \",AspectsConcerns!B42)","v":"      time to market"},"CPSFramework","Concerns related to the time period required to bring a CPS from need realization through deployment.","yes","time-to-market is important issue","n/a","no"]
[1,"utility",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A43),\" \",AspectsConcerns!B43)","v":"      utility"},"CPSFramework","Concerns related to the ability of a CPS to provide benefit or satisfaction through its operation. Utility reflects a business concern, especially when considered as the numerator when computing value, which equals utility divided by costs.","no (out-of-scope)"]
[1,"planning",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A44),\" \",AspectsConcerns!B44)","v":"      planning"},"CPSFramework","Concerns about planning.","no (out-of-scope)"]
[0,"Human",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A45),\" \",AspectsConcerns!B45)","v":" Human"},"CPSFramework","Concerns about human interaction with and as part of a CPS.","no (out-of-scope)","this section is for Human-to-Machine Interface(HMI) which is not the scope of oneM2M"]
[1,"human factors",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A46),\" \",AspectsConcerns!B46)","v":"      human factors"},"CPSFramework","Concern about the characteristics of CPS with respect to how they are used by humans.","no (out-of-scope)"]
[1,"usability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A47),\" \",AspectsConcerns!B47)","v":"      usability"},"CPSFramework","Concerns related to the ability of CPS to be used to achieve its functional objectives effectively, efficiently, and to the satisfaction of users (adapted from ISO 9241-210.) The combination of physical and cyber into complex systems creates challenges in meeting usability goals. Complexity is a major issue. The diversity of interfaces creates a significant learning curve for human interaction.","no (out-of-scope)"]
[1,"human as participant in CPS",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A48),\" \",AspectsConcerns!B48)","v":"      human as participant in CPS"},null,"Concerns about how humans interact with other components of the CPS to achieve the system goals. ","no (out-of-scope)"]
[1,"social",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A49),\" \",AspectsConcerns!B49)","v":"      social"},"ConsensusPPI","Concerns about groups of humans and the CPS (human factors, usability, human as participant) ","no (out-of-scope)"]
[0,"Trustworthiness",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A50),\" \",AspectsConcerns!B50)","v":" Trustworthiness"},"CPSFramework"," Add to spreadsheet"]
[1,"privacy",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A51),\" \",AspectsConcerns!B51)","v":"      privacy"},"CPSFramework","Concerns related to the ability of the CPS to prevent entities (people, machines) from gaining access to data stored in, created by, or transiting a CPS or its components such that individuals or groups cannot seclude themselves or information about themselves from others. Privacy is a condition that results from the establishment and maintenance of a collection of methods to support the mitigation of risks to individuals arising from the processing of their personal information within or among systems or through the manipulation of physical environments.","yes","authorization, privacy and all the security requirements are defined","TS-0002 clause 6.4","yes","Use proper access control settings under control of the data subject (individual whose privacy is exposed by the data)","TS-0003 Clause 7","eXtensible Access Control Markup Language (XACML) \nGuide to Attribute Based Access Control (ABAC) Definition and Considerations"]
[1,"reliability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A52),\" \",AspectsConcerns!B52)","v":"      reliability"},"CPSFramework","Concerns related to the ability of the CPS to deliver stable and predictable performance in expected conditions.","yes","in terms of message delivery, yes","tbd","yes","CMDH(connection management and delivery handling) CSF and its resource types","TS-0001 clause 6.2.2"]
[1,"resilience",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A53),\" \",AspectsConcerns!B53)","v":"      resilience"},"CPSFramework","Concerns related to the ability of the CPS to withstand instability, unexpected conditions, and gracefully return to predictable, but possibly degraded, performance.","yes","in terms of message delivery, yes","tbd","yes","CMDH(connection management and delivery handling) CSF and its resource types","TS-0001 clause 6.2.2"]
[1,"safety",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A54),\" \",AspectsConcerns!B54)","v":"      safety"},"CPSFramework","Concerns related to the ability of the CPS to ensure the absence of catastrophic consequences on the life, health, property, or data of CPS stakeholders and the physical environment.","yes","Every deployment requires a risk and vulnerability assessment","TR-0008","yes","Perform proper risk and vulnerability assessment and mitigate unacceptable risks","Any Risk assessment methodology. See TR-0008","ISO/IEC 29115 Information technology- Security Techniques - Entity authentication assurance framework\nISO/IEC 15408: \"Information technology - Security techniques - Evaluation criteria for IT security\"."]
[1,"security",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A55),\" \",AspectsConcerns!B55)","v":"      security"},"CPSFramework","Concerns related to the ability of the CPS to ensure that all of its processes, mechanisms, physical and data, and services are afforded internal or external protection from unintended and unauthorized access, change, damage, destruction, or use. \nConfidentiality: \nIntegrity: \nAvailability:  ","yes","all the security requirements are defined","TS-0002 clause 6.4, TR-0008","yes","Definition of 4 protection levels suitable for different exposures. Definitrion of security frameworks to protect assets","TS-0003"]
[2,"cybersecurity",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A56),\" \",AspectsConcerns!B56)","v":"           cybersecurity"},"CPSFramework","Concerns about cybsersecurity.","yes","all the security requirements are defined","TS-0002 clause 6.4","yes","CPS security implies cybersecurity with additional challenges. Sdolutions exist to mitigate risks down to acceptable levels!","TR-0008; TS-0003"]
[3,"confidentiality",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A57),\" \",AspectsConcerns!B57)","v":"                confidentiality"},"CPSFramework","Preserving authorized restrictions on access and disclosure. ","yes","all the security requirements are defined","TS-0002 clause 6.4","yes","Access Control and Authorization","TS-0003 clause 7","eXtensible Access Control Markup Language (XACML) \nGuide to Attribute Based Access Control (ABAC) Definition and Considerations"]
[3,"integrity",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A58),\" \",AspectsConcerns!B58)","v":"                integrity"},"CPSFramework","Guarding against improper modification or destruction of system, and includes ensuring non-repudiation and authenticity.","yes","all the security requirements are defined","TS-0002 clause 6.4","yes","implement proper protection level","TR-0008; TS-0003"]
[3,"availability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A59),\" \",AspectsConcerns!B59)","v":"                availability"},"CPSFramework","Ensuring timely and reliable access to and use of a system.","yes","Risks related to Denial of Service must be mitigated ","TR-0008","partially","Some mitigation mechanisms exist","TR-0008, TS-0003"]
[2,"physicalsecurity",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A60),\" \",AspectsConcerns!B60)","v":"           physicalsecurity"},"CPSFramework","Concerns about physical security.","no (out-of-scope)"]
[0,"Timing",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A61),\" \",AspectsConcerns!B61)","v":" Timing"},"CPSFramework","Concerns about time and frequency in CPS, including the generation and transport of time and frequency signals, timestamping, managing latency, timing composability, etc.","yes","time related requirements"]
[1,"logical time",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A62),\" \",AspectsConcerns!B62)","v":"      logical time"},"CPSFramework","Concerns related to the order in which things happen (causal order relation). ","yes","action triggering mechanism",null,"yes","study is on-going for action triggering mechanism","TR-0021"]
[1,"managing timing and latency",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A63),\" \",AspectsConcerns!B63)","v":"      managing timing and latency"},"CPSFramework","Control and measurement applications in CPS generally require specific management of timing and latency. General important concerns for managing timing and latency include the coordination of timing domains and multiple timing references; latency management and control, including scheduling of network timing guarantees; and the mixing of time-sensitive and best-effort data in both networks and CPS nodes. ","yes","in general",null,"yes","CMDH and more"]
[1,"synchronization",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A64),\" \",AspectsConcerns!B64)","v":"      synchronization"},"CPSFramework","Synchronization implies that all associated nodes have access to the same reference timing signals. There are three kinds of synchronization: time, phase, and frequency synchronization, although frequency synchronization is also called syntonization. ","yes","time sync requirements are defined",null,"no"]
[1,"time awareness",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A65),\" \",AspectsConcerns!B65)","v":"      time awareness"},"CPSFramework","Concerns that allow time correctness by design. The presence or absence of explicit time in the models used to describe, analyze, and design CPS and in the actual operation of the components.","yes","time related requirements",null,"yes","there are many timestamps in request and response message. timestamp handling procedures are specified. time series data is also supported, so that missing data can be detected and reported.","TS-0004"]
[1,"time-interval and latency control",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A66),\" \",AspectsConcerns!B66)","v":"      time-interval and latency control"},"CPSFramework","A time-interval is the duration between two instants read on the same timescale. CPS timing requirements are generally expressed as constraints on the time intervals (TI) between pairs of system significant events. There can be more general constraints on TIs that can be categorized based on their degree of time awareness in terms of bounded TIs or latency, deterministic TIs, and accurate TIs. ","yes","periodic data report and missing data detection should be supported for industrial domain"]
[0,"Data",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A67),\" \",AspectsConcerns!B67)","v":" Data"},"CPSFramework","Concerns about data interoperability including fusion, metadata, type, identity, etc.","yes","semantic requirements","TS-0002 clause 6.2","yes"]
[1,"data semantics",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A68),\" \",AspectsConcerns!B68)","v":"      data semantics"},"CPSFramework","Concerns related to the agreed and shared meaning(s) of data held within, generated by, and transiting a system. ","yes","semantic requirements","TS-0002 clause 6.2","yes","semantic description and oneM2M base ontology","TS-0001 clause 9.6.30 and TS-0012","W3C Recommendation: \"RDF 1.1 Concepts and Abstract Syntax\""]
[2,"data models",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A69),\" \",AspectsConcerns!B69)","v":"           data models"},"CPSFramework","Structure of data/information","yes","in general (& smart home?)",null,"yes?","Home Appliances Information Model","TS-0023","Home Gateway Initiative Smart Device Template\nJava coding rule"]
[2,"granularity",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A70),\" \",AspectsConcerns!B70)","v":"           granularity"},"CPSFramework","Granularity of data","yes","data models should be in detail to provide interoperability"]
[2,"meaning",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A71),\" \",AspectsConcerns!B71)","v":"           meaning"},"CPSFramework","semantic meaning of data elements","yes","semantic requirements","TS-0002 clause 6.2","yes","semantic description and oneM2M base ontology","TS-0001 clause 9.6.30 and TS-0012","W3C Recommendation: \"RDF 1.1 Concepts and Abstract Syntax\""]
[1,"identity",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A72),\" \",AspectsConcerns!B72)","v":"      identity"},"CPSFramework","Concerns related to the ability to accurately recognize entities (people, machines, and data) when interacting with or being leveraged by a CPS. ","yes","identification","tbd","yes","oneM2M identifiers","TS-0001 clause 7","IETF RFC 3986: \"Uniform Resource Identifier (URI): General Syntax\".\nRecommendation ITU-T X.660 | ISO/IEC 9834-1: \"Information technology - Procedures for the operation of object identifier registration authorities: General procedures and top arcs of the international object identifier tree\"\noneM2M TR-0008: \"Analysis of Security Solutions for oneM2M System\"\nIETF RFC 4122: \"A Universally Unique IDentifier (UUID) URN Namespace\""]
[2,"resourceIdentification",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A73),\" \",AspectsConcerns!B73)","v":"           resourceIdentification"},"GWAC-Resource Identification(CC)","identificatio of data","yes","identification","tbd","yes","resource identification and addressing","TS-0001 clause 7.2 and 9.3"]
[3,"userIdentification",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A74),\" \",AspectsConcerns!B74)","v":"                userIdentification"},"NISTIR SG.IA-4",null,"yes","identification"]
[3,"deviceIdentification",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A75),\" \",AspectsConcerns!B75)","v":"                deviceIdentification"},"NISTIR SG.IA-5",null,"yes","identification"]
[3,"objectIdentification",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A76),\" \",AspectsConcerns!B76)","v":"                objectIdentification"},"TBD",null,"yes","identification"]
[3,"classIdentification",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A77),\" \",AspectsConcerns!B77)","v":"                classIdentification"},null,null,"???"]
[2,"authentication",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A78),\" \",AspectsConcerns!B78)","v":"           authentication"},"CPSFramework","authenticity of data","yes","message authentication","TS-0002 SEC-058","tbd","tbd"]
[2,"authorization",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A79),\" \",AspectsConcerns!B79)","v":"           authorization"},"CPSFramework","authorizations constraining access to data","yes","authorization (access control) for data/service","TS-0002 OSR-049","yes","authorization for data/service access","TS-0003 clause 7","IETF RFC 3986: \"Uniform Resource Identifier (URI): General Syntax\".\nRecommendation ITU-T X.660 | ISO/IEC 9834-1: \"Information technology - Procedures for the operation of object identifier registration authorities: General procedures and top arcs of the international object identifier tree\"\noneM2M TR-0008: \"Analysis of Security Solutions for oneM2M System\"\nIETF RFC 4122: \"A Universally Unique IDentifier (UUID) URN Namespace\""]
[2,"verification",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A80),\" \",AspectsConcerns!B80)","v":"           verification"},"CPSFramework","verification of the identity of data","yes","data integrity",null,"tbd","tbd"]
[2,"integrity",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A81),\" \",AspectsConcerns!B81)","v":"           integrity"},"CPSFramework","integrity of the data elements","yes","data integrity","TS-0002 SEC-0003","yes","tbd","TS-0003 ","IETF RFC 2104: \"HMAC: Keyed-Hashing for Message Authentication\""]
[2,"configuration",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A82),\" \",AspectsConcerns!B82)","v":"           configuration"},"CPSFramework","management of the configuration of data producing entities","yes","device management and provisioning",null,"yes","device management and provisioning","TS-0001 clause 6.2.4","Broadband Forum TR-069: \"CPE WAN Management Protocol Issue\"\nOMA-DM: \"OMA Device Management Protocol\"\nLWM2M: \"OMA LightweightM2M\""]
[2,"provenance",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A83),\" \",AspectsConcerns!B83)","v":"           provenance"},"CPSFramework","provenance of the source of data","yes","tbd","TS-0002 SEC-046","yes","\"creator\" attribute setting mechanism","TS-0001 claus 9.6.6 for example"]
[1,"operations on data",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A84),\" \",AspectsConcerns!B84)","v":"      operations on data"},"CPSFramework","Concerns related to the ability to create/read/update/delete system data and how the integrity of CPS data and behaviors may be affected.","yes","oneM2M follows RESTful architecture",null,"yes",null,"TS-0001 and TS-0004"]
[2,"analytics",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A85),\" \",AspectsConcerns!B85)","v":"           analytics"},"CPSFramework","analytics","yes","data analytics support based on semantc descriptions","TS-0002 clause 6.3.6","no","not yet specified"]
[2,"fusion",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A86),\" \",AspectsConcerns!B86)","v":"           fusion"},"CPSFramework","Concerns related to the fusion and aggregation of data.","yes","\"virtual\" thinig requirement, message/data aggregation","TS-0002 OSR-064, CMR-008  and ONT-002","yes","semantics, group, time series data"]
[2,"storage",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A87),\" \",AspectsConcerns!B87)","v":"           storage"},"CPSFramework","Concerns related to the volume and storage of data.","yes",null,null,"yes","max instance number and max byte size of container","TS-0001 clause 9.6.6"]
[2,"aggregation/disaggregation",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A88),\" \",AspectsConcerns!B88)","v":"           aggregation/disaggregation"},"CPSFramework","aggregation of data to form summaries or collections from multiple source","yes","data aggregation is fundamental feature of service platform"]
[2,"transformation",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A89),\" \",AspectsConcerns!B89)","v":"           transformation"},"CPSFramework","transformation of data from one form/semantic to another","yes","semantics and ontology",null,"? yes","tbd"]
[1,"relationship between data",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A90),\" \",AspectsConcerns!B90)","v":"      relationship between data"},"CPSFramework","Concerns related to how and why sets of data must, may, or may not be associated with each other and the value or harm that can be derived from those associations.","yes","annotation and ontology"]
[2,"time of data",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A91),\" \",AspectsConcerns!B91)","v":"           time of data"},"CPSFramework","time stamping of data through its life cycle","yes","timestamp support for CSFs","TS-0002 OSR-058","yes","all the timestamps parameters and their handling","TS-0001 clause 8.1.2 and 8.1.3, TS-0004"]
[2,"related data (including metadata)",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A92),\" \",AspectsConcerns!B92)","v":"           related data (including metadata)"},"CPSFramework","metadata and other related data","yes","annotation and ontology",null,"yes","semantic description and content reference","TS-0001 clause 9.6.30 and 9.6.7"]
[2,"location of data",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A93),\" \",AspectsConcerns!B93)","v":"           location of data"},"CPSFramework","location of data","yes","HATEOAS of RESTful architecture",null,"yes","\"link\" attribute of announced resources and childRef in XSDs","TS-0001 clause 9.6.26"]
[2,"inheritance",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A94),\" \",AspectsConcerns!B94)","v":"           inheritance"},"CPSFramework","inheritance relationships of data","yes","annotation and ontology",null,"yes","accessControlPolicyID inheritence for example","TS-0001 clause 9.6.6"]
[2,"polymorphism",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A95),\" \",AspectsConcerns!B95)","v":"           polymorphism"},"CPSFramework","polymorphism of data","???"]
[2,"directionality of relationships",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A96),\" \",AspectsConcerns!B96)","v":"           directionality of relationships"},"CPSFramework","directional/non-directional relationships between data","yes","HATEOAS of RESTful architecture",null,"yes","link relationship between resources","TS-0001 clause 9.4.2"]
[2,"quality",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A97),\" \",AspectsConcerns!B97)","v":"           quality"},"CPSFramework","associated quality metrics of data","not applicable"]
[1,"velocity",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A98),\" \",AspectsConcerns!B98)","v":"      velocity"},"CPSFramework","Concerns related to the velocity of data.","yes","timestamps handling and message QoS"]
[0,"Boundaries",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A99),\" \",AspectsConcerns!B99)","v":" Boundaries"},"CPSFramework","Concerns related to demarcations of topological, functional, organizational, or other forms of interactions."]
[1,"behavioral",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A100),\" \",AspectsConcerns!B100)","v":"      behavioral"},"CPSFramework","Concerns related to interdependence among behavioral domains. Concerns related to the ability to successfully operate a CPS in multiple application areas.","yes","horizontal/common service platform",null,"yes","oneM2M system itself","TS-0001"]
[1,"networkability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A101),\" \",AspectsConcerns!B101)","v":"      networkability"},"CPSFramework","Concerns related to the ease and reliability with which a CPS can be incorporated within a (new or existing) network of other systems.","no (out-of-scope)","# oneM2M has never been incorporated within something"]
[1,"responsibility",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A102),\" \",AspectsConcerns!B102)","v":"      responsibility"},"CPSFramework","Concerns related to the ability to identify the entity or entities authorized to control the operation of a CPS.","yes","authentication and role-based access control","TS-0002 OSR-059","yes","authentication and role-based access control","TS-0001 and TS-0004","IETF RFC 3986: \"Uniform Resource Identifier (URI): General Syntax\".\nRecommendation ITU-T X.660 | ISO/IEC 9834-1: \"Information technology - Procedures for the operation of object identifier registration authorities: General procedures and top arcs of the international object identifier tree\"\noneM2M TR-0008: \"Analysis of Security Solutions for oneM2M System\"\nIETF RFC 4122: \"A Universally Unique IDentifier (UUID) URN Namespace\""]
[0,"Composition",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A103),\" \",AspectsConcerns!B103)","v":" Composition"},"CPSFramework","Concerns related to the ability to compute selected properties of a component assembly from the properties of its components. Compositionality requires components that are composable: they do not change their properties in an assembly. Timing composability is particularly difficult."]
[1,"adaptability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A104),\" \",AspectsConcerns!B104)","v":"      adaptability"},"CPSFramework","Concerns related to the ability of the CPS to achieve an intended purpose in the face of changing external conditions such as the need to upgrade or otherwise reconfigure a CPS to meet new conditions, needs, or objectives.","yes","device management","TS-0002 clause 6.2","yes","device management related resource types and interworking technologies","TS-0001 clause 9.6.15 and TS-0006/7"]
[1,"complexity",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A105),\" \",AspectsConcerns!B105)","v":"      complexity"},"CPSFramework","Concerns related to our understanding of the behavior of CPS due to the richness and heterogeneity of interactions among its components, such as existence of legacy and the variety of interfaces.","yes","interworking with other systems including legacies","TS-0002 OSR-096","yes","interworking with AllJoyn, LWM2M, OCF, 3GPP Rel-13 network and generic area network interworking\n(in terms of 3GPP Rel-13 interworking, device triggering function is only valid for the Infrastructure Domain)","TS-0001 and TS-0012"]
[1,"constructivity",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A106),\" \",AspectsConcerns!B106)","v":"      constructivity"},"CPSFramework","Concerns related to the ability to combine CPS modular components (hardware, software, and data) to satisfy user requirements.","yes","in general","n/a",null,"CSFs and resource types are modular concepts","TS-0001 "]
[1,"discoverability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A107),\" \",AspectsConcerns!B107)","v":"      discoverability"},"CPSFramework","Concerns related to the ease and reliability with which a CPS component can be observed and understood (for purposes of leveraging the component’s functionality) by an entity (human, machines). Concerns related to the ease and reliability with which a CPS component’s functions can be ascertained (for purposes of leveraging that functionality) by an entity (human, machines).","yes","discovery of data/function/service/entity should be supported ","TS-0002"]
[0,"Lifecycle",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A108),\" \",AspectsConcerns!B108)","v":" Lifecycle"},"CPSFramework","Concerns about the lifecycle of CPS including its components.","not applicable"]
[1,"deployability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A109),\" \",AspectsConcerns!B109)","v":"      deployability"},"CPSFramework","Concerns related to the ease and reliability with which a CPS can be brought into productive use.","no (out-of-scope)"]
[1,"disposability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A110),\" \",AspectsConcerns!B110)","v":"      disposability"},"CPSFramework","Concerns related to the impacts that may occur when the CPS is taken physically out of service.","no (out-of-scope)"]
[1,"engineerability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A111),\" \",AspectsConcerns!B111)","v":"      engineerability"},"CPSFramework","Concerns related to the ease and reliability with which a CPS design concept can successfully be realized via a structured engineering process.","no (out-of-scope)"]
[1,"maintainability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A112),\" \",AspectsConcerns!B112)","v":"      maintainability"},"CPSFramework","Concerns related to the ease and reliability with which the CPS can be kept in working order.","no (out-of-scope)"]
[1,"operatability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A113),\" \",AspectsConcerns!B113)","v":"      operatability"},"CPSFramework","Concerns related to the operation of the CPS when deployed.","no (out-of-scope)"]
[1,"procureability",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A114),\" \",AspectsConcerns!B114)","v":"      procureability"},"CPSFramework","Concerns related to the ease and reliability with which a CPS can be obtained.","no (out-of-scope)"]
[1,"producibility",{"$f":"CONCATENATE(REPT(\"     \",AspectsConcerns!A115),\" \",AspectsConcerns!B115)","v":"      producibility"},"CPSFramework","Concerns related to the ease and reliability with which a CPS design can be successfully manufactured. ","no (out-of-scope)"]

{"sheet":"print","index":1,"n_rows":110,"n_cols":3,"rows_kept":110,"cut":false,"hidden":false,"merged":[]}
["ROW#","REQ#","DESCRIPTION"]
[6,null,"Concerns about function including sensing, actuation, control, communications, physicality, etc."]
[7,null,"Concerns related to the ability of the CPS to effect change in the physical world."]
[8,null,"Concerns related to the exchange of information internal to the CPS and between the CPS and other entities."]
[9,null,"Concerns about the presentation and exchange patterns of data"]
[10,null,"Concerns about application layer exchange patterns"]
[11,null,"Concerns about the syntax of message encoding"]
[12,null,"Concerns about networked message exchange"]
[13,null,"Concerns about session creation, maintainance, and tear-down"]
[14,null,"Concerns about information transport"]
[15,null,"Concerns about networked exchange"]
[16,null,"Concerns about connectivity of CPSDevices"]
[17,null,"Concerns about data links"]
[18,null,"Concerns about physical communication links"]
[19,null,"Ability of a CPS to control a property of a physical thing. There are many challenges to implementing control systems with CPS including the non-determinism of cyber systems, the uncertainty of location, time and observations or actions, their reliability and security, and complexity. Concerns related to the ability to modify a CPS or its function, if necessary."]
[20,null,"Concerns related to the function that a CPS provides."]
[21,null,"Concerns related to the ability to measure the characteristics of the CPS."]
[22,null,"Concerns related to the ease and reliability with which authorized entities can gain and maintain awareness of the state of a CPS and its operations. Includes logging and audit functionality."]
[23,null,"Concerns related to the ability of a CPS to meet required operational targets."]
[24,null,"Concerns about purely physical properties of CPS including seals, locks, safety, and EMI."]
[25,null,"Concerns relating to the need to understand a specific observation or a desired action relative to its physical position (and uncertainty.) While this information is often implied and not explicit in traditional physical systems, the distributed, mobile nature of CPS makes this a critical concern."]
[26,null,"Concerns related to the ability of a CPS to develop the situational awareness required to perform to its function."]
[27,null,"Managing the effects of uncertainties is a fundamental challenge in CPS. Sources of uncertainty in CPS can be grouped into statistical (aleatoric), lack of knowledge (epistemic) uncertainty, or systematic uncertainty. In CPS statistical uncertainty is caused by randomness of accuracy of sensing and actuation, often caused by uncertainty of manufacturing processes. Systematic uncertainty is caused by incomplete knowledge either due to limits of acquired knowledge or due to simplification in modeling. Typical manifestations of epistemic uncertainty are limited validity of models of physical processes or limits of computability of properties of mathematical models."]
[28,null,"Concerns about states and modes of a CPS."]
[29,null,"Concerns about managing a CPS through its life cycle."]
[30,null,"configuration management is a key functional concern with dimensions of configuration, versioning, ..."]
[31,null,"Concerns about minimizing the configuration needed."]
[32,null,"Concerns about component inventory and versioning."]
[33,null,"Concerns about enterprise, time to market, environment, regulation, cost, etc."]
[34,null,"Concerns related to the economic aspects of CPS throughout their lifecycle."]
[35,null,"Concerns related to the repuation of the enterprise as effected by the CPS."]
[36,null,"Concerns related to the direct and indirect investment or monetary flow or other resources required by the CPS throughout its lifecycle. "]
[37,null,"Concerns related to the impacts of the engineering and operation of a CPS on the physical world."]
[38,null,"Concerns related to the impacts of treaties, statutes, and doctrines on a CPS throughout its lifecycle."]
[39,null,"Concerns related to the ease and reliability of assessing whether a CPS meets stakeholder (especially customer) expectations."]
[40,null,"Concerns related to regulatory requirements and certifications."]
[41,null,"Concerns related to the time period required to bring a CPS from need realization through deployment."]
[42,null,"Concerns related to the ability of a CPS to provide benefit or satisfaction through its operation. Utility reflects a business concern, especially when considered as the numerator when computing value, which equals utility divided by costs."]
[43,null,"Concerns about planning."]
[44,null,"Concerns about human interaction with and as part of a CPS."]
[45,null,"Concern about the characteristics of CPS with respect to how they are used by humans."]
[46,null,"Concerns related to the ability of CPS to be used to achieve its functional objectives effectively, efficiently, and to the satisfaction of users (adapted from ISO 9241-210.) The combination of physical and cyber into complex systems creates challenges in meeting usability goals. Complexity is a major issue. The diversity of interfaces creates a significant learning curve for human interaction."]
[47,null,"Concerns about how humans interact with other components of the CPS to achieve the system goals. "]
[48,null,"Concerns about groups of humans and the CPS (human factors, usability, human as participant) "]
[49,null," Add to spreadsheet"]
[50,null,"Concerns related to the ability of the CPS to prevent entities (people, machines) from gaining access to data stored in, created by, or transiting a CPS or its components such that individuals or groups cannot seclude themselves or information about themselves from others. Privacy is a condition that results from the establishment and maintenance of a collection of methods to support the mitigation of risks to individuals arising from the processing of their personal information within or among systems or through the manipulation of physical environments."]
[51,null,"Concerns related to the ability of the CPS to deliver stable and predictable performance in expected conditions."]
[52,null,"Concerns related to the ability of the CPS to withstand instability, unexpected conditions, and gracefully return to predictable, but possibly degraded, performance."]
[53,null,"Concerns related to the ability of the CPS to ensure the absence of catastrophic consequences on the life, health, property, or data of CPS stakeholders and the physical environment."]
[54,null,"Concerns related to the ability of the CPS to ensure that all of its processes, mechanisms, physical and data, and services are afforded internal or external protection from unintended and unauthorized access, change, damage, destruction, or use. \nConfidentiality: \nIntegrity: \nAvailability:  "]
[55,null,"Concerns about cybsersecurity."]
[56,null,"Preserving authorized restrictions on access and disclosure. "]
[57,null,"Guarding against improper modification or destruction of system, and includes ensuring non-repudiation and authenticity."]
[58,null,"Ensuring timely and reliable access to and use of a system."]
[59,null,"Concerns about physical security."]
[60,null,"Concerns about time and frequency in CPS, including the generation and transport of time and frequency signals, timestamping, managing latency, timing composability, etc."]
[61,null,"Concerns related to the order in which things happen (causal order relation). "]
[62,null,"Control and measurement applications in CPS generally require specific management of timing and latency. General important concerns for managing timing and latency include the coordination of timing domains and multiple timing references; latency management and control, including scheduling of network timing guarantees; and the mixing of time-sensitive and best-effort data in both networks and CPS nodes. "]
[63,null,"Synchronization implies that all associated nodes have access to the same reference timing signals. There are three kinds of synchronization: time, phase, and frequency synchronization, although frequency synchronization is also called syntonization. "]
[64,null,"Concerns that allow time correctness by design. The presence or absence of explicit time in the models used to describe, analyze, and design CPS and in the actual operation of the components."]
[65,null,"A time-interval is the duration between two instants read on the same timescale. CPS timing requirements are generally expressed as constraints on the time intervals (TI) between pairs of system significant events. There can be more general constraints on TIs that can be categorized based on their degree of time awareness in terms of bounded TIs or latency, deterministic TIs, and accurate TIs. "]
[66,null,"Concerns about data interoperability including fusion, metadata, type, identity, etc."]
[67,null,"Concerns related to the agreed and shared meaning(s) of data held within, generated by, and transiting a system. "]
[68,null,"Structure of data/information"]
[69,null,"Granularity of data"]
[70,null,"semantic meaning of data elements"]
[71,null,"Concerns related to the ability to accurately recognize entities (people, machines, and data) when interacting with or being leveraged by a CPS. "]
[72,null,"identificatio of data"]
[73]
[74]
[75]
[76]
[77,null,"authenticity of data"]
[78,null,"authorizations constraining access to data"]
[79,null,"verification of the identity of data"]
[80,null,"integrity of the data elements"]
[81,null,"management of the configuration of data producing entities"]
[82,null,"provenance of the source of data"]
[83,null,"Concerns related to the ability to create/read/update/delete system data and how the integrity of CPS data and behaviors may be affected."]
[84,null,"analytics"]
[85,null,"Concerns related to the fusion and aggregation of data."]
[86,null,"Concerns related to the volume and storage of data."]
[87,null,"aggregation of data to form summaries or collections from multiple source"]
[88,null,"transformation of data from one form/semantic to another"]
[89,null,"Concerns related to how and why sets of data must, may, or may not be associated with each other and the value or harm that can be derived from those associations."]
[90,null,"time stamping of data through its life cycle"]
[91,null,"metadata and other related data"]
[92,null,"location of data"]
[93,null,"inheritance relationships of data"]
[94,null,"polymorphism of data"]
[95,null,"directional/non-directional relationships between data"]
[96,null,"associated quality metrics of data"]
[97,null,"Concerns related to the velocity of data."]
[98,null,"Concerns related to demarcations of topological, functional, organizational, or other forms of interactions."]
[99,null,"Concerns related to interdependence among behavioral domains. Concerns related to the ability to successfully operate a CPS in multiple application areas."]
[100,null,"Concerns related to the ease and reliability with which a CPS can be incorporated within a (new or existing) network of other systems."]
[101,null,"Concerns related to the ability to identify the entity or entities authorized to control the operation of a CPS."]
[102,null,"Concerns related to the ability to compute selected properties of a component assembly from the properties of its components. Compositionality requires components that are composable: they do not change their properties in an assembly. Timing composability is particularly difficult."]
[103,null,"Concerns related to the ability of the CPS to achieve an intended purpose in the face of changing external conditions such as the need to upgrade or otherwise reconfigure a CPS to meet new conditions, needs, or objectives."]
[104,null,"Concerns related to our understanding of the behavior of CPS due to the richness and heterogeneity of interactions among its components, such as existence of legacy and the variety of interfaces."]
[105,null,"Concerns related to the ability to combine CPS modular components (hardware, software, and data) to satisfy user requirements."]
[106,null,"Concerns related to the ease and reliability with which a CPS component can be observed and understood (for purposes of leveraging the component’s functionality) by an entity (human, machines). Concerns related to the ease and reliability with which a CPS component’s functions can be ascertained (for purposes of leveraging that functionality) by an entity (human, machines)."]
[107,null,"Concerns about the lifecycle of CPS including its components."]
[108,null,"Concerns related to the ease and reliability with which a CPS can be brought into productive use."]
[109,null,"Concerns related to the impacts that may occur when the CPS is taken physically out of service."]
[110,null,"Concerns related to the ease and reliability with which a CPS design concept can successfully be realized via a structured engineering process."]
[111,null,"Concerns related to the ease and reliability with which the CPS can be kept in working order."]
[112,null,"Concerns related to the operation of the CPS when deployed."]
[113,null,"Concerns related to the ease and reliability with which a CPS can be obtained."]
[114,null,"Concerns related to the ease and reliability with which a CPS design can be successfully manufactured. "]