Foundations of Trusted Computational Information Systems

AMENDMENT 2 for BAA FA8750-17-S-7007 The purpose of this modification is to republish the original announcement, incorporating any previous amendments, pursuant to FAR 35.016(c). This republishing also includes the following changes: (a) This is amendment No. 2 to the BAA. The first amendment was incorrectly listed as amendment No. 3; (b) Updates the Contracting Focal Point throughout; (c) Section I, deletes technical area 3-Quantum Information Processing and renumbers the remaining technical areas; (d) Section III.2: updates the foreign participation/access language; (e) Section IV.3.c: updates the TPOC email for unclassified submissions; (f) Section V.2.b.2: updates the evaluation categories; (g) Section VI.1: updated to reference the most recent version of the RI-Specific Proposal Preparation Instructions, dated Jun 2018; (h) Section VI.4: updated to revise and add new Administrative and National Policy Requirements; (i) Section VI.7: added paragraph (d); (j) Section VII: Updated the technical point of contact (TPOC); (k) Section VII: Update the Alternate Ombudsman information. No other changes have been made. NAICS CODE: 541715 FEDERAL AGENCY NAME: Department of the Air Force, Air Force Materiel Command, AFRL - Rome Research Site, AFRL/Information Directorate, 26 Electronic Parkway, Rome, NY, 13441-4514 BROAD AGENCY ANNOUNCEMENT (BAA) TITLE: Foundations of Trusted Computational Information Systems BAA NUMBER: FA8750-17-S-7007 CATALOG OF FEDERAL DOMESTIC ASSISTANCE (CFDA) Number: 12.800 and 12.910 I. FUNDING OPPORTUNITY DESCRIPTION: The Air Force and Department of Defense (DoD) are dependent upon information technologies for almost everything they do, yet more needs to be done to secure the processing foundations upon which information technology infrastructure depends. Additionally, the sheer volume of data types being continuously being collected is now so voluminous that only a small subset of the data collected can effectively be refined into information, knowledge and actionable intelligence for decision makers. The Air Force Research Laboratory is soliciting white papers under this Broad Agency Announcement (BAA) for research, development, integration, test and evaluation of innovative technologies/techniques that establish trusted foundations for hardware and software that enable secure, resilient, affordable Command, Control, Communications, Computer, Intelligence and Cyber (C4+1I) information processing systems. Additional innovative technologies are sought to simultaneously increase the computational sophistication and decision aid capacities of these same systems. Of particular interest are technologies that support hardware and software foundations for high assurance, trusted/secure architectures, increased computational sophistication of general purpose and specialized processing, increased complex system functionality with improved resilience and embedded processing. Also of interest are technologies that can reduce warfighter decision latencies/response time, decrease system costs and system development times, automate labor-intensive/error-prone and costly aspects of system software development, and improve reliability, longevity, upgradability, and usability of emerging and legacy military information systems. Operation in a contested cyberspace domain requires that our systems must be resilient to unforeseen cyber-attacks. System characteristics dependent on geo-distribution, autonomy, and cooperation rely on trust within the system. Many mission critical systems and components currently lack the ability to adapt and be resilient to unforeseen failure and cyber-attacks. Methodologies and techniques to understand, maintain or reestablish trust in the system and its components to ensure mission success during execution and fight-through are non-existent. Resilient systems must possess self-healing capabilities that can dynamically effect change in the system to fight through unforeseen cyber-attacks (while maintaining mission essential functions (MEF)) as well as provide proof of continued or re-established trust in the system, as the dynamic change will have eroded mission/system trust based on the time-consuming, human-intensive and expensive Verification and Validation (V&V) established offline prior to mission deployment. To overcome these challenges, computing architectures require advances in resiliency technologies that enable fight through of unforeseen faults and cyber-attacks, while simultaneously assessing and/or reestablishing trust in near real-time to ensure mission success. This effort will investigate the research, development, and/or application of trusted/secure information processing architecture technologies, products and standards as they relate to the following technical areas: (1) Development of appropriate information technology to enhance the processing capabilities of current and future Air Force C4I systems: This technical area encompasses all information processing technology, both hardware and software, that could potentially contribute to enhancing the security, trustworthiness, functionality, performance, reliability, longevity, scalability, resiliency, upgradability, and usability of legacy or planned Air Force C4I processing systems. Examples of conventional hardware technologies include domain-specific/specialized processing engines (both digital and analog), heterogeneous and many-core processing architectures with emphasis on hardware support for graph analytics processing, semantic operations, energy-efficient and energy-aware processing architectures, high assurance/trusted/secure processing architectures, sophisticated memory controllers and performance optimization tools. (2) Trusted and Resilient Software-intensive Systems Engineering: The objective of the trusted and resilient software-intensive systems engineering technical area is to develop techniques, methodologies and tools to guarantee trust (as measured by correctness, security, reliability, predictability, and survivability) and maintain this trust as self-healing/resilient techniques fight through cyber-attacks to include zero-day attacks. This research area is seeking to extend and advance software development tools that will enable the development and/or execution of trusted and resilient software systems for enterprise and tactical level embedded cyber physical platforms. This area will focus on research and development to advance SW development tools, to include formal tools, model based techniques and/or architectures based approaches to enable the development of software (SW) systems that are both trusted and resilient. Research and development will also be focused on new approaches, methods and/or tools for continuous (runtime) V&V and runtime environments that can monitor and maintain a trusted and resilient envelope of operation. Technical areas of interest include: techniques to enable trust in model-based software engineering; model-based engineering for predictable software attributes; Formal methods tools; provably correct code generation; provably correct code repair, evidence-based software assurance; evolutionary approaches, trusted software and systems composability; modeling, analysis, and verification of autonomous software; novel architectural approaches, strategic "roots of trust," hardening and resiliency techniques such as artificial diversity, containment areas for execution of untrusted software, lightweight runtime monitoring techniques and utilization of hardware (HW) advances, trusted and resilient mechanisms to fight through software failures, cyber-attacks to include zero-day attack; human understanding and trust of automated software development, red teaming, metrics and measures of trustworthy systems, integration, validation and demonstration on a realistic mission critical embedded system exemplar, autonomous resilience, self-healing software systems, and pliable computing. (3) Trusted, secure, and resilient computational systems: The objective of this technical area is to research and develop the essential elements, tools and methodologies for trusted, secure and resilient computing environments, including both the underlying hardware and software, side by side with power, cost, performance, and reliability. Topics of interest include, but are not limited to: (a) Problems and challenges with current processor designs for trustworthiness and their solutions; (b) Problems and challenges with current computer architectures for trustworthiness and solutions to them; (c) Tools and methodologies for ensuring trustworthiness of integrated circuits (ICs) and systems targeting malicious inclusions, side-channel attacks, probing attacks, etc.; (d) New computer architectures for secure and reliable computing, including data integrity and code protection and verification; (e) Operating System level constructs, objects, functions and distributions that must be provided to complement the hardware to enable a trustworthy computing base; (f) State-of-the-art software-based assurance designs, methodologies or concepts which are better suited for implementation in hardware than software. This technical area is also interested in research and development for increasing the level of trustworthiness of IC designs, commodity ICs and currently available systems as a whole. Finally, this technical area is also interested in security enhancements possible in the software tool chain used for compiling and linking source code, runtime security as well as research in the implications of state-of-the-art commercially available processor architectures and specially designed processor architectures that will enable delivery of trustworthy, secure and timely information. (4) Cyber Physical Systems (CPS): The objective of this technical area is to develop the tools, methodologies, and foundational science to provide the scalability and interoperability necessary to make the integration and subsequent analysis of computational and physical components and the networks connecting them practicable. Technical areas of interest include: (a) Specification, modeling, and analysis such as heterogeneous models of computation and hybrid discrete and continuous systems; (b) Modularity, composability, predictability, and synthesis addressing the issues of scalability and the integration of legacy systems; and (c) Verification and validation techniques (assurance, simulation, formal methods, correct-and-secure-by-construction, etc.) applicable to these models. (5) Software Assurance: Achieving the degree of Software Assurance across the application space requires a holistic approach that agilely addresses all layers of the supply chain and enterprise including governance, partnerships, process, standards, and education. The objective of this area is to enhance and create the foundations of Software Assurance (SwA). To achieve this objective new and unique methods of conducting software assurance must be pursued. The use of machine learning in SwA analysis can enhance not only classes of tools, but should be used across all SwA activities. This can be applied as a smart SwA tool consolidation framework. The framework can then reason over the outputs of tools, then combined with previous data, or knowledge of the software under analysis, the framework can then guide other tools. This guidance should help one class of tool's strength's overcome another class of tool's weaknesses. Additional areas of interest include: Tools Assessment and Categorization; Prototype Software Assurance Demonstration; and SwA technology which advances the state of SwA by addressing technology gaps to improve SwA tools (e.g. precision and recall) and scalability (e.g. code size, expertise required, and execution time). II. AWARD INFORMATION: 1. FUNDING: Total funding for this BAA is approximately $24.9M. The anticipated funding to be obligated under this BAA is broken out by fiscal year as follows: FY17 - $1.9M FY18 - $5.8M FY19 - $5.8M FY20 - $5.8M FY21 - $5.6M Individual awards will not normally exceed 36 months with dollar amounts normally ranging from $100K to $3M. There is also the potential to make awards up to any dollar value as long as that amount does not exceed that BAA ceiling. The Government reserves the right to select all, part, or none of the proposals received, subject to the availability of funds. All potential Offerors should be aware that due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice. 2. FORM. Awards of efforts as a result of this announcement will be in the form of contracts, grants, cooperative agreements or other transactions depending upon the nature of the work proposed. 3. BAA TYPE: This is a two-step open broad agency announcement. This announcement constitutes the only solicitation. As STEP ONE - The Government is only soliciting white papers at this time. DO NOT SUBMIT A FORMAL PROPOSAL. Those white papers found to be consistent with the intent of this BAA may be invited to submit a technical and cost proposal, see Section VI of this announcement for further details regarding the proposal. III. ELIGIBILITY INFORMATION: 1. ELIGIBILITY: All qualified offerors who meet the requirements of this BAA may apply. 2. FOREIGN PARTICIPATION/ACCESS: a. This BAA is closed to foreign participation. This includes both foreign ownership and foreign nationals as employees or subcontractors. b. Exceptions. 1. Fundamental Research. If the work to be performed is unclassified, fundamental research, this must be clearly identified in the white paper and/or proposal. See Part II, Section I for more details regarding Fundamental Research. Offerors should still identify any performance by foreign nationals at any level (prime contractor or subcontractor) in their proposals. Please specify the nationals' country of origin, the type of visa or work permit under which they are performing and an explanation of their anticipated level of involvement. You may be asked to provide additional information during negotiations in order to verify the foreign citizen's eligibility to participate on any contract or assistance agreement issued as a result of this announcement 2. Foreign Ownership, Control or Influence (FOCI) companies who have mitigation plans/paperwork in place. Proof of approved mitigation documentation must be provided to the contracting office focal point, Amber Buckley, Contracting Officer, telephone +1 (555) 000-0000, or e-mail contact@example.gov prior to submitting a white paper and/or a proposal. For information on FOCI mitigation, contact the Defense Security Service. Additional details can be found at: https://www.dss.mil/ma/ctp/isia/bams/foci/foci_mitigation/ 3. Foreign Nationals as Employees or Subcontractors. Applicable to any effort not considered Fundamental Research. Offerors are responsible for ensuring that all employees and/or subcontractors who will work on a resulting contract are eligible to do so. Any employee who is not a U.S. citizen or a permanent resident will be restricted from working on any resultant contract unless prior approval of the Department of State or the Department of Commerce is obtained via a technical assistance agreement or an export license. Violations of these regulations can result in criminal or civil penalties. c. Information Regarding Non-US Citizens Assigned to this Project a. Contractor employees requiring access to USAF bases, AFRL facilities, and/or access to U.S. Government Information Technology (IT) networks in connection with the work on contracts, assistance instruments or other transactions awarded under this BAA must be U.S. citizens. For the purpose of base and network access, possession of a permanent resident card ("Green Card") does not equate to U.S. citizenship. This requirement does not apply to foreign nationals approved by the U.S. Department of Defense or U.S. State Department under international personnel exchange agreements with foreign governments. It also does not apply to dual citizens who possess US citizenship, to include Naturalized citizens. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. Specific format for waiver request will be provided upon request to the Contracting Officer. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC). b. For the purposes of Paragraph 1, it an IT network/system does not require AFRL to endorse a contractor's application to said network/system in order to gain access, the organization operating the IT network/system is responsible for controlling access to its system. If an IT network/system requires a U.S. Government sponsor to endorse the application in order for access to the IT network/system, AFRL will only endorse the following types of applications, consistent with the requirements above: a) Contractor employees who are U.S. citizens performing work under contracts, assistance instruments or other transactions awarded under this BAA. b) Contractor employees who are non-U.S. citizens and who have been granted a waiver. Any additional access restrictions established by the IT network/system owner apply. 3. FEDERALLY FUNDED RESEARCH AND DEVELOPMENT CENTERS AND GOVERNMENT ENTITIES: Federally Funded Research and Development Centers (FFRDCs) and Government entities (e.g., Government/National laboratories, military educational institutions, etc.) are subject to applicable direct competition limitations and cannot propose to this BAA in any capacity unless they meet the following conditions: a. FFRDCs: FFRDCs must clearly demonstrate that the proposed work is not otherwise available from the private sector; and FFRDCs must provide a letter on official letterhead from their sponsoring organization citing the specific authority establishing their eligibility to propose to Government solicitations and compete with industry, and their compliance with the associated FFRDC sponsor agreement's terms and conditions. This information is required for FFRDCs proposing to be prime contractors or sub-awardees. b. Government Entities: Government entities must clearly demonstrate that the work is not otherwise available from the private sector and provide written documentation citing the specific statutory authority and contractual authority, if relevant, establishing their ability to propose to Government solicitations. While 10 U.S.C. 2539b may be the appropriate statutory starting point for some entities, specific supporting regulatory guidance, together with evidence of agency approval, will still be required to fully establish eligibility. FFRDC and Government entity eligibility will be determined on a case-by-case basis; however, the burden to prove eligibility for all team members rests solely with the proposer. Government agencies interested in performing work related to this announcement should contact the Technical Point of Contact (TPOC). If resulting discussions reveal a mutual interest, cooperation may be pursued via other vehicles. IV. APPLICATION AND SUBMISSION INFORMATION: All responses to this announcement must be addressed to the Technical Point of Contact (TPOC) listed in SECTION VII. DO NOT send white papers to the Contracting Officer. 1. SUBMISSION DATES AND TIMES: It is recommended that white papers be received by 2 PM Eastern Standard Time (EST) on the following dates to maximize the possibility of award: FY17 by 31 May 2017 FY18 by 07 Dec 2017 FY19 by 06 Dec 2018 FY20 by 04 Dec 2019 FY21 by 03 Dec 2020 White papers will be accepted until 2 PM EST on 30 Sep 2021, but it is less likely that funding will be available in each respective fiscal year after the dates cited. This BAA will close on 30 Sep 2021. All offerors submitting white papers will be contacted by the TPOC, referenced in Section VII of this announcement. Offerors can email the TPOC for status of their white paper/proposal no earlier than 45 days after submission. 2. CONTENT AND FORMAT: Offerors are required to submit 1 copy of a 2 to 5 page white paper summarizing their proposed approach/solution. The purpose of the white paper is to preclude unwarranted effort on the part of an offeror whose proposed work is not of interest to the Government. The white paper will be formatted as follows: a. Section A: Title, Period of Performance, Estimated Cost, Name/Address of Company, Technical and Contracting Points of Contact (phone, fax and email)(this section is NOT included in the page count); b. Section B: Task Objective; and c. Section C: Technical Summary and Proposed Deliverables. All white papers shall be double spaced with a font no smaller than 12 point. In addition, respondents are requested to provide their Commercial and Government Entity (CAGE) Code, their unique entity identifier and the Electronic Funds Transfer Indicator (if applicable), a fax number, an e-mail address, and reference BAA FA8750-17-S-7007 with their submission. Multiple white papers within the purview of this announcement may be submitted by each offeror. If the offeror wishes to restrict its white papers, they must be marked with the restrictive language stated in FAR 15.609(a) and (b). 3. HANDLING AND MAILING INSTRUCTIONS: a. CLASSIFICATION GUIDANCE. All Proposers should review the NATIONAL INDUSTRIAL SECURITY PROGRAM OPERATING MANUAL, (NISPOM), dated February 28, 2006 and incorporating Change 2, dated May 18, 2016, as it provides baseline standards for the protection of classified information and prescribes the requirements concerning Contractor Developed Information under paragraph 4-105. Defense Security Service (DSS) Site for the NISPOM is: http://www.dss.mil/. In the event of a possible or actual compromise of classified information in the submission of your white paper or proposal, immediately but no later than 24 hours, bring this to the attention of your cognizant security authority and AFRL Rome Research Site Information Protection Office (IPO): Vincent Guza (contact only is there if a security issue) +1 (555) 000-0000 0730-1630 Monday-Friday +1 (555) 000-0000 Evenings and Weekends Email: contact@example.gov b. CLASSIFIED SUBMISSIONS. AFRL/RITA will accept classified responses to this BAA when the classification is mandated by classification guidance provided by an Original Classification Authority of the U.S. Government, or when the offeror believes the work, if successful, would merit classification. Security classification guidance in the form of a DD Form 254 (DoD Contract Security Classification Specification) will not be provided at this time since AFRL is soliciting ideas only. Offerors that intend to include classified information or data in their white paper submission or who are unsure about the appropriate classification of their white papers should contact the technical point of contact listed in Section VII for guidance and direction in advance of preparation. c. MAILING INSTRUCTIONS. Any mailed responses, unclassified/classified, to this announcement must be sent U.S. Postal Service, registered mail or similar service and addressed to AFRL/RITA, 525 Brooks Road, Rome NY 13441-4505, and reference BAA FA8750-17-S-7007. When mailing follow the directions regarding the number of copies required. Unclassified electronic submission to contact@example.gov will also be accepted. Encrypt or password-protect all proprietary information prior to sending. Offerors are responsible to confirm receipt with the TPOC listed in Section VII. AFRL is not responsible for undelivered documents. If electronic submission is used, only one copy of the documentation is required. Questions can be directed to the TPOC listed in Section VII. 4. OTHER SUBMISSION REQUIREMENTS/CONSIDERATIONS: a. COST SHARING OR MATCHING: Cost sharing is not a requirement. Cost sharing may be proposed and will be considered on a case-by-case basis. b. SYSTEM FOR AWARD MANAGEMENT (SAM). Offerors must be registered in the SAM database to receive a contract award, and remain registered during performance and through final payment of any contract or agreement. Processing time for registration in SAM, which normally takes forty-eight hours, should be taken into consideration when registering. Offerors who are not already registered should consider applying for registration before submitting a proposal. The provision at FAR 52.204-7, System for Award Management (Oct 2016) applies. c. EXECUTIVE COMPENSATION AND FIRST-TIER SUBCONTRACT/ SUBRECIPIENT AWARDS: Any contract award resulting from this announcement may contain the clause at FAR 52.204-10 - Reporting Executive Compensation and First-Tier Subcontract Awards (Oct 2016). Any grant or agreement award resulting from this announcement may contain the award term set forth in 2 CFR, Appendix A to Part 25 which can be viewed at: http://www.ecfr.gov/cgi-bin/text-idx?SID=8fb6c83606df57968c3e7e145e7d683c&mc=true&node=ap2.1.25_1360.a&rgn=div9 d. ALLOWABLE CHARGES: The cost of preparing white papers/proposals in response to this announcement is not considered an allowable direct charge to any resulting contract or any other contract, but may be an allowable expense to the normal bid and proposal indirect cost specified in FAR 31.205-18. Incurring pre-award costs for ASSISTANCE INSTRUMENTS ONLY are regulated by 2 CFR part 200.458, Pre-Award Costs. e. GOVERNMENT APPROVED ACCOUNTING SYSTEM: An offeror must have a government approved accounting system prior to award of a cost-reimbursement contract per limitations set forth in FAR 16.301-3(a) to ensure the system is adequate for determining costs applicable to the contract. The acceptability of an accounting system is determined based upon an audit performed by the Defense Contract Audit Agency (DCAA). IMPORTANT: If you do not have a DCAA approved accounting system access the following link for instructions: https://www.fbo.gov/index?s=opportunity&mode=form&id=1cffad228f48b58057072a6c9113799d&tab=core&_cview=1 f. HUMAN USE: All research involving human subjects, to include the use of human biological specimens and human data, selected for funding must comply with Federal regulations for human subject protection. Further, research involving human subjects that is conducted or supported by the DoD must comply with 32 CFR 219, "Protection of Human Subjects" found at: http://www.access.gpo.gov/nara/cfr/waisidx_07/32cfr219_07.html, and DoD Instruction 3216.02, "Protection of Human Subjects and Adherence to Ethical Standards in DoD-Supported Research" found at: http://www.dtic.mil/whs/directives/corres/pdf/321602p.pdf. 1) Institutions awarded funding for research involving human subjects must provide documentation of a current Assurance of Compliance with Federal regulations for human subject protection, for example a Department of Health and Human Services, Office of Human Research Protection Federal Wide Assurance found at: http://www.hhs.gov/ohrp. 2) All institutions engaged in human subject research, to include subcontractors, must have a valid assurance. In addition, personnel involved in human subject research must document the completion of appropriate training for the protection of human subjects. 3) For all research that will involve human subjects in the first year or phase of the project, the institution must submit evidence of a plan for review by an institutional review board (IRB) as part of the proposal. The IRB conducting the review must be the IRB identified on the institution's Assurance of Compliance. The protocol, separate from the proposal, must include a detailed description of the research plan, study population, risks and benefits of study participation, recruitment and consent process, data collection, and data analysis. The designated IRB should be consulted for guidance on writing the protocol. The informed consent document must comply with 32 CFR 219.116. A valid Assurance of Compliance and evidence of appropriate training by all investigators should accompany the protocol for review by the IRB. 4) In addition to a local IRB approval, an AFRL-level human subject regulatory review and approval is required for all research conducted or supported by the DoD. The Air Force office responsible for managing the award can provide guidance and information about the AFRL-level review process. Confirmation of a current Assurance of Compliance and appropriate human subjects protection training is required before AFRL-level approval can be issued. 5) The time required to complete the IRB review/approval process will vary depending on the complexity of the research and/or the level of risk to study participants; ample time should be allotted to complete the approval process. The IRB approval process can last between 1 to 3 months, followed by a DoD review that could last 3 to 6 months. No funding may be used toward human subject research until all approvals are granted. Therefore, in their cost proposals offerors should separate human use into a separate option. V. APPLICATION REVIEW INFORMATION: 1. CRITERIA: The following criteria, which are listed in descending order of importance and will be used to determine whether white papers and proposals submitted are consistent with the research areas of interest and expected results within the broad topic areas as described in the Funding Opportunity section of this BAA and of interest to the Government: a. Overall Scientific and Technical Merit - The extent to which the proposed technical approach to the development and/or enhancement of the proposed technology demonstrates scientific and technical merit, clearly defined and developed technical concepts and sufficient detail to support the proposed concepts and technical claims. b. Capabilities and Related Experience - The extent to which the offeror demonstrates relevant technology and domain knowledge to establish that the offeror has credible capability and experience to complete the proposed work. c. Openness, Maturity and Assurance of Solution - The extent to which existing capabilities and standards are leveraged and the relative maturity of the proposed technology in terms of reliability and robustness. d. Reasonableness and realism of proposed costs and fees (if any) No further evaluation criteria will be used in selecting white papers/proposals. White papers and proposals submitted will be evaluated as they are received. 2. REVIEW AND SELECTION PROCESS: a. Only Government employees will evaluate the white papers/proposals for selection. The Air Force Research Laboratory's Information Directorate has contracted for various business and staff support services, some of which require contractors to obtain administrative access to proprietary information submitted by other contractors. Administrative access is defined as "handling or having physical control over information for the sole purpose of accomplishing the administrative functions specified in the administrative support contract, which do not require the review, reading, and comprehension of the content of the information on the part of non-technical professionals assigned to accomplish the specified administrative tasks." These contractors have signed general non-disclosure agreements and organizational conflict of interest statements. The required administrative access will be granted to non-technical professionals. Examples of the administrative tasks performed include: a. Assembling and organizing information for R&D case files; b. Accessing library files for use by government personnel; and c. Handling and administration of proposals, contracts, contract funding and queries. Any objection to administrative access must be in writing to the Contracting Officer and shall include a detailed statement of the basis for the objection. b. WHITE PAPER/PROPOSAL REVIEW PROCESS: 1. FIRST STEP - White Paper Reviews: The Government will ...