Attachment - Draft PWS SEESAW 8.docx
DOCX document 94 KB Posted
- Solicitation number
- FA875024RB006
About this file
This document is a Performance Work Statement (PWS) for the Systems Engineering and Evaluations, Systems Analysis Worldwide VIII (SEESAW VIII) contract opportunity.
The PWS outlines the services required to provide lifecycle management and technical support, systems analysis, and engineering operations and maintenance for programs within the Air Force Research Laboratory's (AFRL) cross domain, cloud storage, AI/ML, and data/information handling portfolio. Key tasks include O&M engineering, requirements analysis, implementation and integration, security testing, and operational maintenance. The contractor will also provide research, development, test and evaluation services to assist the intelligence agencies and cross domain community with planning, engineering, fielding and operating IT systems and resources. The contract is being competed by the Department of the Air Force Materiel Command Research Laboratory (AFRL) under Solicitation FA875024RB006. The PWS provides details on the service requirements, government-furnished items, and general information regarding safety, security, and other administrative matters.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Amend 1 - Sources Sought Notice SAM SEESAW 8 01 Jul 2024.docx | DOCX document | |
| Sources Sought Notice SAM SEESAW 8 28 Jun 2024.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
E512101
AIR FORCE RESEARCH LABORATORY
ROME RESEARCH SITE
ROME, NEW YORK
PERFORMANCE WORK STATEMENT (PWS)
FOR
SYSTEMS ENGINEERING AND EVALUATIONS, SYSTEMS ANALYSIS WORLDWIDE VIII (SEESAW VIII)
PCSN E51201
20 May 2024
(Sources Sought FA8750-24-R-B006)
TABLE OF CONTENTS
SECTION DESCRIPTION PAGE
| 1.0 | BACKGROUND | 3 |
| 2.0 | DESCRIPTION OF SERVICES | 4 |
| 3.0 | SERVICES SUMMARY | 31 |
| 4.0 | GOVERNMENT FURNISHED PROPERTY, | |
| BASE SUPPORT, AND SERVICES | 34 | |
| 5.0 | GENERAL INFORMATION AND APPENDIX | 34 |
| 1.0 | BACKGROUND |
| 1.1 | This effort provides lifecycle management and technical support, systems analysis and engineering Operations and Maintenance (O&M) for programs and efforts within the RIE cross domain, cloud storage, AI/ML and data and information handling portfolio. Technical support for the capabilities and associated programs require personnel with specific knowledge, expertise and experiences in the Intelligence and Command and Control (C2) Community. This effort will utilize the Software (SW) engineering lifecycle process to implement and integrate a cohesive approach for the development, maintenance and deployment of cross domain, cloud storage, hybrid multi-cloud architecture and infrastructure, Artificial Intelligence / Machine Learning (AI/ML), and other data and information handling program requirements and capabilities. The work includes: providing studies, analyses, designs, development, recommendations, enhancements, upgrades, integration management, configuration management, testing and evaluation of existing systems, new systems and their transition into the operational environment, prototyping, functional evaluations of installed systems, sustaining advanced technologies and capabilities, following DevSecOps processes including Continuous Integration/Continuous Development (CI/CD) for secure software development, data normalization, data and infrastructure standardization, Hardware (HW) and Software (SW) installation, system and network administration and operation. |
| 1.2 | Lifecycle Management and Technical Support: Design, develop, and implement lifecycle systems engineering for the information and intelligence requirements of Air Force Research Laboratory (AFRL), DoDIIS and intelligence community. Include user requirements, refinements, concept development, prototype, demonstrate, and technology evaluation. Lifecycle Management and Technical Support includes the following Programs: Cross Domain Collaboration Technology (CCOLT) SecureView (SV), Advanced Battle Management Systems (ABMS) DeviceOne SecureView (ADSV), Information Support Server Environment (ISSE), X-Domain Agile Rules Based Information Transfer Orchestrator (XARBITOR), Open Architecture Distributed Common Ground System (OA DCGS), and other Data and Information Handling programs. |
| 1.3 | System Analysis: Review, investigate, and analyze the Government’s functional requirements. Document further breakout and detail the requirements. Develop, compare and evaluate concepts or alternatives to meet or exceed requirements. Develop and implement prototypes and demonstrations to test or show the validity of the concept and recommend concepts or alternatives to the Government. Analysis activities support AFRL, Defense Intelligence Agency (DIA), Air Combat Command (ACC) and other Department of Defense (DoD) and Intelligence Community (IC) customers. |
| 1.4 | Engineering O&M: Perform general operation, maintenance and administration of data and information components, products or systems (hereinafter referred to as systems); and including engineering to address O&M problems. This effort is required to support information and intelligence requirements of AFRL, DIA, ACC and other DoD and IC customers. |
| 1.5 | System Procurement: Procure necessary material and engineering services to support delivery of systems covered under this task to various Government customers including DIA, ACC, DoD, and others. |
| 2.0 | DESCRIPTION OF SERVICES AND TASK AREAS: The Contractor shall perform the following: |
| 2.1 | O&M Engineering: Utilize the SW engineering lifecycle process to implement and integrate a cohesive approach for the enhancement of cross domain and other data and information handling program requirements. In addition, provide management and engineering for the enhancement, deployment, and operational maintenance of new and enhanced cross domain and data and information handling capabilities to a wide range of customers that include the Air Force (AF), IC, C2, ML Communities, Agencies and other Government entities. Provide engineering to address all programs, customers and functional capabilities within the portfolio. Cross domain and data and information handling capabilities include all aspects of requirements which include the creation, control, transfer, access and use of the data, information and functions across and within control environments. The work includes any or all life cycle phases, including: |
· Studies (i.e. Analytical, System Feasibility, System Trade-off)
· Analysis (i.e. Test and Evaluation, System, data processing)
· Technical support to system design
· SW specification and enhancement for existing systems
· Component and systems integration
· Functional evaluations of installed systems Provide O&M engineering in the following Task areas; specific details will be reflected in individual Work Plans.
| · Task Area 1 | Enterprise Planning | |
| · Task Area 2 | Requirements Analysis | |
| · Task Area 3 | Implementation and Integration | |
| · Task Area 4 | Security Accreditation Testing | |
| · Task Area 5 | Operational Maintenance | |
| 2.1.1 | Major Enhancements: Provide enhancements and sustainment to this effort’s baselined systems and subsystem component capabilities to enable system baseline improvements through the upgrades of individual hardware and software modules with newer modular components for key General Defense Intelligence Program requirements and other community customers. Substantial enhancements include items such as support for new interfaces, functions, data formats and/or user interface to existing capabilities. | |
| 2.1.2 | Minor Enhancements: Provide sustainment, minor enhancements and ongoing operational support and other lifecycle activities to support the existing baselines and changing technology. This includes activities related to emerging technologies, cross domain voice and chat, cross domain transfer, multi-level security and others as directed by the Government. | |
| 2.1.3 | Enterprise Planning: Provide technical and programmatic support to assist the intelligence agencies and the cross domain community with all aspects of planning, engineering, fielding and operating IT systems and resources. Provide cross domain technical and programmatic support for review, analysis and coordination of cross domain processes, policy, doctrine, directives, regulations and implementation of instructions. Provide recommendations to address changes and their impacts across strategic, tactical and operational planning, including consideration for policy, directives, acquisition planning, requirements definition, financial reporting, engineering, solution fielding, training, operations and customer support. | |
| 2.1.3.1 | Requirements: Provide technical analysis and dependency identification to refine Government identified requirements and decompose into program level requirements. | |
| 2.1.3.2 | Management: Collect, maintain, coordinate and distribute high level technical information and documentation associated with the Government project supported. | |
| 2.1.3.3 | Program Objective Memorandum (POM) and Budgets: Provide technical recommendations for solutions to technical problem areas for the Government to incorporate as one of the sources of information for POM and Budget submissions. Provide impact analysis of identified funding, policy and guidance changes, development of alternate solutions to meet funding limitations to include analysis of high level integration and dependency issues between projects. | |
| 2.1.3.4 | Technical Planning and Analysis: Analyze the Government’s strategic, tactical and operational plan(s) to determine the technical impacts and alternatives. Present the technical input to the Government for acceptance and incorporation into integrated visions and plans, roadmaps, exercise architectures, investment and divestment strategies. Continually assess technical compliance with the published guidance and directives, provide recommendations when variances are identified. Document how changes in doctrine and technology apply to enhance evolving operational capabilities. (See CDRLs, B009, C009, D009, E009, F009, G009, H009, J009, K009, L009) | |
| 2.1.3.5 | Programmatic Planning: Identify, verify and provide detailed descriptions of programmatic shortfalls, needs or required changes to the program or system caused by changes to applicable policies, directives and doctrine. This may include database design activities (logical and physical), applications SW modifications and enhancement, technology insertion activities (update documentation and demonstrate), information assurance activities, security engineering requirements and resource estimates. (See CDRLs, B004, B008, C004, C008, D004, D008, E004, E008, F004, F008, G004, G008, H004, H008, J004, J008, K004, K008, L004, L008) | |
| 2.1.3.6 | Working Groups: Participate in working groups as required to facilitate accomplishment of work and as approved by the Government. These may include Cross Domain Technology Forum (CDTF), National Cross Domain Strategy Management Office (NCDSMO) Working Groups, Interface Control Working Groups, Architecture Working Groups, management boards, Configuration Control Boards, User Groups, and Warfighter Requirements Working Group. Prepare briefings and white papers as necessary to present pertinent technical information and to support discussions. Document minutes of participation in each group meeting. (See CDRLs, B004, B005, B008, C004, C005, C008, D004, D005, D008, E004, E005, E008, F004, F005, F008 G004, G005, G008, H004, H005, H008, J004, J005, J008, K004, K005, K008, L004, L005, L008) | |
| 2.1.4 | Requirements Analysis: Provide support to the Government with requirements collection, analysis and definition to determine optimal cross-functional solutions integral to the integration process. Develop data collection tools, conduct surveys, hold meetings with customers, analyze data, and consolidate and refine user requirements. Document the results. (See CDRLs, B009, C009, D009, E009, F009, G009, H009, J009, K009, L009) | |
| 2.1.4.1 | Functional Requirements: Evaluate user functional requirements for: completeness; non-ambiguity; testability; simplicity; implementation ramifications; and cost effectiveness. Identify unclear or vague requirements to the Government. Update and modify requirements, as necessary, due to changes in the user environment. | |
| 2.1.4.2 | Component Product System and Performance Requirements: Perform engineering and analyses to generate system requirements that satisfy user, functional, and performance requirements. Allocate system requirements to HW and SW. | |
| 2.1.4.3 | HW Requirements: Determine the HW required to support user requirements and concepts. Assess current HW suites at user site(s) for its capability to support new user requirements and concepts. Identify shortcomings, incompatibilities and new HW required to support new and improved capabilities. Identify new and future HW technology and its ramifications to support advanced and improved capabilities. Update and modify HW requirements, as necessary, due to changes in the user site(s) and the HW industry. | |
| 2.1.4.4 | SW Requirements: Determine how SW will be used to satisfy user and system requirements. Determine how COTS, GOTS and developed SW are to be integrated to support user functional and system requirements. Determination shall include identification and impact of limited rights, proprietary, export controlled data and SW in accordance with Government regulations, contract clauses, policies and directives. | |
| 2.1.4.5 | Facility Requirements: Perform site surveys. Identify the amount of physical space required, ingress and egress measurements, cabling required, electrical, communication, network, power, heating and cooling requirements and other information needed to support requirements, concepts and systems. | |
| 2.1.4.6 | Security Requirements: Evaluate Intelligence Community Directives (ICD), NIST 800-53, NCDSMO and other sources of security requirements for applicability, compliance, and impact to programs. Recommend solutions to areas of non-compliance. | |
| 2.1.4.7 | Standards and Process Requirements: Evaluate Air Force, DoD, DODIIS, national, and other standards and processes for applicability, impact, compliance, compatibility to with work being performed and systems being developed. Identify areas where standards or processes are inadequate, need re-engineering, hinder development or impede adequate support to users and the warfighter. Recommend solutions to identified problems. | |
| 2.1.5 | Implementation and Integration: Select an integration strategy that considers all integration management components in order to recommend a standard, common, migration system, provide cost and economic analyses supporting the migration strategy, identify and evaluate risks inherent with the proposed strategy and provide a tentative implementation plan. | |
| 2.1.5.1 | Installation/Integration: Perform activities for the installation and integration of developed and upgraded capabilities into the targeted environment. Perform and document all activities for infrastructure configurations, integration and installation to include Security, environment specific configurations, system and site acceptance. Document trip reports as required. (See CDRLs B008, B010, C008, C010 D008, D010, E008, E010, F008, F010, G008, G010, H008, H010, J008, J010, K008, K010, L008, L010) | |
| 2.1.5.2 | Integration Management: Perform continuous lifecycle integration management for the support of system integration, resolution of integration problems, organization, conduct, and direction of integration efforts. Update the existing documentation. (See CDRLs, B008, C008, D008, E008, F008, G008, H008, J008, K008, L008) | |
| 2.1.5.3 | Technical Integration: Stage and perform first-level technical integration of the system HW and SW as necessary. Provide technical engineering for the integration of the SW within operational and experimental environments identified by the Government. Install and integrate identified systems. Provide technical support for the integration testing and evaluation, site acceptance testing, certification testing, and familiarization. Update the existing documentation. (See CDRLs, B004, B008, C004, C008, D004, D008, E004, E008, F004, F008, G004, G008, H004, H008, J004, J008, K004, K008, L004, L008) | |
| 2.1.5.4 | Cross-Functional Integration Support: Identify cross-functional applications and technical issues associated with supported programs and functional areas. Recommend opportunities for resolving issues in requirements, data, applications, integration and infrastructure elements. Provide input to the Government’s approach to plan, analyze and report programmatic impacts on the issues such as cost, risk analysis, return on investment, schedule dependencies, and recommend functional and technical solutions. Update the existing documentation. (See CDRLs, B008, C008, D008, E008, F008, G008, H008, J008, K008, L008) | |
| 2.1.6 | Security Accreditation Testing | |
| 2.1.6.1 | Security Assessment Testing and Support: Provide technical expertise to support system security accreditation test and evaluation. Provide system testing and documentation as described in the Government provided SW accreditation test plan, similar documentation or as requested by the Government to meet unique accreditation requirements. Work shall include providing copies of all security related documentation, explanation and demonstration of test procedures, resolution of anomalies, and preparation of the security accreditation test report or similar documentation. Testing participation shall include Secret and Below Interoperability (SABI) and Top Secret and Below Interoperability (TSABI) Lab Based Security Assessments (LBSA), and Site Based Security Assessment (SBSA) at operational mission sites at completion of installation. (See CDRLs, B008, C008, D008, E008, F008, G008, H008, J008, K008, L008) | |
| 2.1.6.2 | Security Requirements Analysis: Perform security requirements analysis to support security assessment testing to include, SABI and TSABI LBSA and SBSA at operational mission sites. (See CDRLs, B008, C008, D008, E008, F008, G008, H008, J008, K008, L008) | |
| 2.1.6.3 | Security Requirements Package Support: Provide technical expertise to support the preparation of security assessment packages for and in conjunction with operational mission sites. Work shall include preparation of Cross Domain Appendixes (CDA) and other related documentation for SABI lab and site based testing/installations, and all related documentation and reporting for TSABI testing and installations. Update the existing documentation. (See CDRLs, B008, C008, D008, E008, F008, G008, H008, J008, K008, L008) | |
| 2.1.7 | Operational Maintenance: Provide support services for all aspects of installing and maintaining approved cross domain and data and information handling systems. All services provided shall use and be integrated with approved DoD and Federal standard communications, security, data and other defined technical specifications. Provide planning, controlling, overseeing and conducting successful installation, development and conduct of initial training, conversion and acceptance testing of migration applications. Conduct site surveys, site planning, site installation, initial system file and table builds, data acquisition and conversion and installation tests. | |
| 2.1.7.1 | Operational Maintenance: Make system changes and enhancements to meet emerging user requirements, changing operating environments, and to resolve problems identified with the system. This maintenance shall include maintenance of the system, GOTS and application SW from multiple baselines and versions to include SW on workstations, clients, and servers. Changes to GOTS SW will be accomplished by the agency responsible for the SW in accordance with their change procedures. | |
| 2.1.7.1.1 | Provide central maintenance consisting of system and engineering support on site, or remotely from the Contractor’s facilities to maintain existing operational SW by identifying, correcting, testing, updating the resolution of SW or documentation problems. (See CDRLs, B008, C008, D008, E008, F008, G008, H008, J008, K008, L008) | |
| 2.1.7.1.2 | Provide baseline maintenance consisting of maintaining all system and SW configurations under the current operational baseline, a site baseline, or a Contractor maintained baseline. Update system documentation in accordance with original standards used to produce the documents. (See CDRLs, B008, C008, D008, E008, F008, G008, H008, J008, K008, L008) | |
| 2.1.7.1.3 | On-Site Support: Provide Contractor on-site Support at the following Government locations (AFRL, DIA, and United States Secret Service (USSS). Provide routine on-site operation and maintenance of Government designated systems and SW coincident with normal site duty hours. Provide on-call emergency on-site operation and maintenance of Government designated systems as required, including after normal site duty hours. Each on-site representative shall: (1) Identify, analyze, report, and resolve problems in accordance with program specific Configuration Management Plans, equivalent plan or process as requested by the Government. The on-site representative shall assist site personnel in writing Problem Reports (PR) and Change Requests (CR); (2) Provide on-call emergency site support as needed to maintain the operational capability of Government designated systems; (3) Install and test Government approved HW and SW upgrades to designated Systems; (4) Install operating system and data base management system changes for designated systems; (5) Provide support during exercises and special contingency situations required to maintain designated systems in operational status: (6) Perform HW configuration reviews for SW releases: (7) Assist site personnel in maintaining internal system and data base management tables and data; and (8) Provide on the job familiarization for site personnel for Government designated Systems. | |
| 2.1.7.1.4 | System Optimization: Analyze the operations of a current system based on Government identification of known problem areas. For each identified problem area, develop plans and procedures for collecting data that will quantify the nature and characteristics of the problem. Analyze the data that was collected and provide a report to the Government with alternative methods of providing a solution to the problem. For each alternative presented, identify dollar cost, manpower cost, implementation schedule and quantifiable measures of improvement. (See CDRLs, B009, C009, D009, E009, F009, G009, H009, J009, K009, L009) | |
| 2.2 | Research, Development, Test & Evaluation (RDT&E). Utilize the SW engineering lifecycle process to implement and integrate a cohesive approach for the development of cross domain and other data and information handling program requirements. In addition, provide management and engineering for the development and deployment of new cross domain and data and information handling capabilities to a wide range of customers that include the Air Force (AF), IC, C2 Communities, Agencies and other Government entities. Provide engineering to address all programs, customers and functional capabilities within the portfolio. Cross domain and data and information handling capabilities include all aspects of requirements which include the creation, control, transfer, access and use of the data, information and functions across and within control environments. The work includes any or all life cycle phases, including: |
· Studies (i.e. Analytical, System Feasibility, System Trade-off)
· Analysis (i.e. Test and Evaluation, System, data processing)
· Technical support to system design
· SW specification and development for existing systems
· System prototyping and simulations
· Component and systems integration
· Functional evaluations of installed systems Provide RDT & E engineering in the following task areas; specific details will be reflected in individual Work Plans.
TASK AREAS:
| · Task Area 1 | Enterprise Planning | |
| · Task Area 2 | Research and Analysis | |
| · Task Area 3 | Prototyping Design and Development | |
| · Task Area 4 | Requirements Analysis | |
| 2.2.1 | Enterprise Planning: This task area provides technical and programmatic support to assist the intelligence agencies and the cross domain community with all aspects of planning, engineering, fielding and operating IT systems and resources. Provide cross domain technical and programmatic support for review, analysis and coordination of cross domain processes, policy, doctrine, directives, regulations and implementation of instructions. Provide recommendations to address changes and their impacts across strategic, tactical and operational planning, including consideration for policy, directives, acquisition planning, requirements definition, financial reporting, engineering, solution fielding, training, operations and customer support. | |
| 2.2.1.1 | Requirements: Provide technical analysis and dependency identification to refine Government identified requirements and decompose into program level requirements. | |
| 2.2.1.2 | Management: Collect, maintain, coordinate and distribute high level technical information and documentation associated with the Government project supported. | |
| 2.2.1.3 | POM and Budgets: Provide technical recommendations for solutions to technical problem areas for the Government to incorporate as one of the sources of information for POM and Budget submissions. Provide impact analysis of identified funding, policy and guidance changes, development of alternate solutions to meet funding limitations to include analysis of high level integration and dependency issues between projects. | |
| 2.2.1.4 | Technical Planning and Analysis: Analyze the Government’s strategic, tactical and operational plan(s) to determine the technical impacts and alternatives. Present the technical input to the Government for acceptance and incorporation into integrated visions and plans, roadmaps, exercise architectures, investment and divestment strategies. Continually assess technical compliance with the published guidance and directives, provide recommendations when variances are identified. Document how changes in doctrine and technology apply to enhance evolving operational capabilities. (See CDRL, A010) | |
| 2.2.1.5 | Programmatic Planning: Identify, verify, and provide detailed descriptions of programmatic shortfalls, needs or required changes to the program or system caused by changes to applicable policies, directives and doctrine. This may include data base design activities (logical and physical), applications SW design and development, technology insertion activities (update documentation and demonstrate), information assurance activities, security engineering requirements and resource estimates. (See CDRLs, A004, A009) | |
| 2.2.1.6 | Working Groups: Participate in working groups as required to facilitate accomplishment of work and as approved by the Government. These may include Cross Domain Technology Forum (CDTF), National Cross Domain Strategy Management Office (NCDSMO) Working Groups, Interface Control Working Groups, Architecture Working Groups, management boards, Configuration Control Boards, User Groups, and Warfighter Requirements Working Group. Prepare briefings and white papers as necessary to present pertinent technical information and to support discussions. Document minutes of participation in each group meeting. (See CDRLs, A004, A005, A009) | |
| 2.2.2 | Research and Analysis: Provide input to the Government with analysis of program and cross domain requirements, emerging technologies, technical trade-offs, technical impacts, process shortfalls, integration and impact analysis of proposed changes. | |
| 2.2.2.1 | Analysis: Conduct analytical studies of program problem areas, risks, missions, and potential technology for implementation. Identify and document possible impacts, options and alternatives, indirect requirements, dependencies, risks and other factors effecting programmatic requirements. (See CDRL, A010) | |
| 2.2.2.1.1 | Analytical Studies: Conduct Analytical Studies to include technical evaluation of engineering problem areas and development of solutions to these problems. | |
| 2.2.2.1.2 | Feasibility Studies: Conduct System Feasibility Studies that include requirement definition and cost performance analysis. | |
| 2.2.2.1.3 | Risk Analysis: Conduct risk analysis studies to include technical and programmatic evaluations of proposed solutions and concepts to address all aspects of risk. | |
| 2.2.2.1.4 | Intelligence Analysis: Support mission capability requirements to include review of current requirements, intelligence data tasking, production, exploitation, distribution, dissemination, and reporting. | |
| 2.2.2.1.5 | Technology Assessment: Perform technical assessments of Government identified areas of Information Science & Technology (S&T). These assessments shall focus on the development of immediate near term or long term strategies to support development of technical solutions to problems and requirements. | |
| 2.2.2.1.6 | Product Assessment: Perform technical assessments of Government identified commercial Information S&T products. Recommend the most appropriate products to provide solutions to problems and requirements. Recommendations shall be based on a consideration of: cost; compatibility with existing HW and SW; unique capabilities; training required; and any other technical or business factors which affect the usability of the product. | |
| 2.2.2.1.7 | Technology Evaluation: For Government identified Information S&T topical areas, provide technology assessments regarding methods of evolutionary migration to take advantage of technology advances. In the assessment, compare current capabilities that can be achieved to future capabilities that could be achieved. Provide quantifiable estimates for improvement. Provide alternative methods for implementing, or evolving to the new technologies. For each alternative provide risk, projected dollar cost, manpower cost, and quantifiable measures of improvement over current operations. | |
| 2.2.2.2 | Emerging Technologies: Explore, analyze, assess, determine and document new, cross domain and multi-level solutions technologies and concepts for potential use to include impacts emerging technologies may have on the DoD and IC communities. Develop, document and coordinate solution recommendations and strategies in response to DoD/IC community needs that minimize the impacts identified. (See CDRL, A010) | |
| 2.2.2.3 | Modernization Analysis and Strategies: Evaluate, analyze, develop and document modernization strategies, integrated mission area plans, investment plans and divestment strategies, Command, Control, Communications, Computers, Intelligence (C4I) support plans, and associated documents for existing cross domain technologies and solutions. (See CDRL, A010) | |
| 2.2.2.4 | Concept of Operations (CONOPs) Plan: Develop and maintain a CONOPs Plan that documents how changes in doctrine and technology apply to enhance evolving operational capabilities. (See CDRL, A007) | |
| 2.2.2.5 | Impact Analysis: Perform feasibility and impact analysis, architecture analyses, system specification, design feasibility analysis, test and evaluation strategies and operations and maintenance impact assessments. | |
| 2.2.2.6 | System Trade-Off Studies: Conduct system trade-off studies that evaluate multiple solutions to problems and results in ranked technical analysis of the most technically appropriate solutions based on provided Government direction. | |
| 2.2.3 | Prototyping, Design and Development: Provide support to the Government in researching current market conditions and provide solutions to prevent premature systems obsolescence. Operate and maintain prototype applications and databases to determine optimal cross-functional solutions for integration concepts and problems integral to the integration process. Work with the Government to design, develop, document and test custom applications and their infrastructures. Standard, common, and migration application development will generally occur through modification of one or several legacy applications and will be built primarily by use of COTS and services. (See CDRL, A010) | |
| 2.2.3.1 | Prototype: Develop, evaluate, and assess prototypes and demonstrations to test or show the validity of a concept. Recommend concepts or alternatives to the Government. Prototypes and demonstrations shall be based on Government produced or Government approved Contractor produced demonstration scripts. Each script shall describe a purpose for the prototype and demonstration, and shall illustrate the principles of an operational model. Prototypes and demonstrations shall conform to applicable Government and Industry Standards, best practices, and Modular Open Systems Approach (MOSA) principles. Plan, coordinate, acquire all the logistics associated with providing resources to support required exercises and demonstrations. (See CDRL, A004) | |
| 2.2.3.1.1 | Prototype and Demonstration Evaluation: Develop User and Analyst feedback procedures and mechanisms, to provide detailed comments on any or all aspects of the utilization of a prototype, or the witnessing of a demonstration. Document and summarize comments and provide the summary to the Government along with a recommended action for each comment. (See CDRL, A010) | |
| 2.2.3.2 | Design: Develop and document engineering designs to include the following: (See CDRL, A010) | |
| 2.2.3.2.1 | Review, analyze, and provide recommendations to system designs based on Government provided constraints and Contractor developed design information. | |
| 2.2.3.2.2 | Designs shall be applicable to a single site, to multiple sites, or other Government specified environment. | |
| 2.2.3.2.3 | Designs shall address the Governments requirements, HW, SW, documentation, environmental constraints, policy and directives, security and documentation. | |
| 2.2.3.2.4 | Review the designs for conformance to specified Government and Industry Standards and Best Practices. | |
| 2.2.3.2.5 | Reviews shall consider unique factors associated with Intelligence Systems such as Security Accreditation Testing. | |
| 2.2.3.2.6 | Review the designs for compatibility with interfaces to existing systems, easily integrated into existing systems, scalable, and easily tailored to meet individual site requirements. | |
| 2.2.3.2.7 | Review the designs to conform to applicable Government and Industry Standards and Best Practices, in support of Service Oriented Architecture (SOA) and Enterprise Architectures. | |
| 2.2.3.2.8 | System Design: Review and evaluate system designs to ensure user and Functional requirements are satisfied in a sound technical and cost effective manner. Address SW requirements, HW requirements, network requirements, security requirements, personnel requirements, and facility requirements in the design. Ensure the design conforms to Government and Industry Standards, and Best Practices and are consistent with unique user, service, command or community oriented policies and procedures. | |
| 2.2.3.3 | Develop: Develop and implement SW based upon the design and Government requirements. Development may consist of engineering development to validate and demonstrate a design, as well as final system development for tools and infrastructure in support of core programs. Development activities shall include any or all of the following activities as applicable to meet or exceed Government requirements: (See CDRL, A009) |
· Analyst Support Tools
· Infrastructure Support and critical infrastructure systems modeling, simulation, and analysis
· Demonstration Code and Prototype
· Engineering Development for Validation of Requirements
· Enterprise Configuration Management
· Data analytics, including graph analytics, text analytics and data normalization
· Database Conversion, Validation and Management
· Data models and algorithms for Intelligence analysis, targeting and C2
· Secure data collection, processing, transfer, integration, and storage between robust infrastructure (i.e., high-capacity networks with large servers) and tactical environments, mobile devices and datalinks
· Cloud computing and cloud migration solutions
· Advanced algorithm development, integration, testing, and demonstration for big data analytics, machine learning, artificial intelligence, neural networks, and for identification and analysis of extended relationships within complex data sets
| 2.2.3.3.1 | Technical Analysis: Perform technical analysis of required HW, SW, information, and other required elements for SW prototyping and development. | |
| 2.2.3.3.2 | Execute: Upon Government approval, acquire, install, configure and develop the elements identified to accomplish the prototype and development. | |
| 2.2.3.3.3 | System Integration and Testing: Provide technical expertise to support system testing and evaluation based on the requirements and the technical nature of the design. | |
| 2.2.4 | Requirements Analysis: Provide support to the Government with requirements collection, analysis, and definition to determine optimal cross-functional solutions integral to the integration process. Develop data collection tools, conduct surveys, hold meetings with customers, analyze data, and consolidate and refine user requirements. Document the results. (See CDRL, A010) | |
| 2.2.4.1 | Functional Requirements: Evaluate user functional requirements for: completeness; non-ambiguity; testability; simplicity; implementation ramifications; and cost effectiveness. Identify unclear or vague requirements to the Government. Update and modify requirements, as necessary, due to changes in the user environment. | |
| 2.2.4.2 | Component Product System and Performance Requirements: Perform engineering and analyses to generate system requirements that satisfy user, functional, and performance requirements. Allocate system requirements to HW and SW. | |
| 2.2.4.3 | HW Requirements: Determine the HW required to support user requirements and concepts. Assess current HW suites at user site(s) for its capability to support new user requirements and concepts. Identify shortcomings, incompatibilities and new HW required to support new and improved capabilities. Identify new and future HW technology and its ramifications to support advanced and improved capabilities. Update and modify HW requirements, as necessary, due to changes in the user site(s) and the HW industry. | |
| 2.2.4.4 | SW Requirements: Determine how SW will be used to satisfy user and system requirements. Determine how COTS, GOTS and developed SW are to be integrated to support user functional and system requirements. Determination shall include identification and impact of limited rights, proprietary, export-controlled data, and SW in accordance with Government regulations, contract clauses, policies and directives. | |
| 2.2.4.5 | Facility Requirements: Perform site surveys. Identify the amount of physical space required, ingress and egress measurements, cabling required, electrical, communication, network, power, heating and cooling requirements and other information needed to support requirements, concepts, and systems. | |
| 2.2.4.6 | Security Requirements: Evaluate Intelligence Community Directives (ICD), NIST 800-53, NCDSMO and other sources of security requirements for applicability, compliance, and impact to programs. Recommend solutions to areas of non-compliance. | |
| 2.2.4.7 | Standards and Process Requirements: Evaluate Air Force, DoD, DODIIS, national, and other standards and processes for applicability, impact, compliance, compatibility to with work being performed and systems being developed. Identify areas where standards or processes are inadequate, need re-engineering, hinder development or impede adequate support to users and the warfighter. Recommend solutions to identified problems. | |
| 2.3 | Test and Evaluation: Provide technical support to early operational assessments, developmental testing, acceptance testing, operational testing, and evaluation of cross domain and data and information handling systems. | |
| 2.3.1 | Test Plan: Provide technical test criteria to evaluate against targeted goals. Document the results. (See CDRLs, A012, B011, C011, D011, E011, F011, G011, H011, J011, K011, L011) | |
| 2.3.2 | Government Acceptance Testing (GAT): Provide technical expertise to support system test and evaluation of HW and SW. Perform thorough testing of each release, enhancement and baseline of supported programs to ensure compliance with functional and security requirements. For each release, verify each tasked PR and CR has been resolved, that no other modules have been adversely affected, and that the functionality of the previous baseline has been maintained. | |
| 2.3.3 | HW and SW Installation: Provide HW and SW installation support for GAT, LBSA, and other formal test events. HW and SW installation support activities include verification that the HW and SW has been correctly installed. Provide HW and SW Installation support at other sites designated by the Government. | |
| 2.3.4 | GAT Report: Prepare and deliver a test report upon completion of GAT and SBSA as requested by the Government. Test report(s) will include test cases executed, expected test results, actual test results, issues encountered, test duration, hours executed for all tests, and metrics. (See CDRLs, A013, B012, C012, D012, E012, F012, G012, H012, J012, K012, L012) | |
| 2.3.5 | Interoperability Testing: Conduct interoperability testing and evaluation to ascertain adherence to DoD and intelligence community standards and requirements. Provide recommendations for making fielding decisions based on compliance with the DoD instructions, analysis of program documentation, and testing and evaluation. Evaluate applications for compliance with current and emerging DoD policies and requirements of Intelligence Mission Applications. Document each assessment and compliance recommendation. (See CDRLs, A013, B012, C012, D012, E012, F012, G012, H012, J012, K012, L012) | |
| 2.3.6 | Functionality Evaluations: Conduct functionality evaluations of the installed system. Perform functional analysis studies of the architecture, data, interfaces, functional system integration, and HW and SW demonstration efforts. Document and brief the evaluations and studies. (See CDRLs, A004, A010, B004, B009, C004, C009, D004, D009, E004, E009, F004, F009, G004, G009, H004, H009, J004, J009, K004, K009, L004, L009) | |
| 2.3.7 | Compatibility Testing: Provide technical engineering during preliminary in-plant HW and SW Compatibility Testing of potential additions to the system baseline. Document the results in a test report. (See CDRL, A013, B012, C012, D012, E012, F012, G012, H012, J012, K012, L012) | |
| 2.3.8 | Exercises and Demonstrations: Provide engineering support for exercises, demonstrations, and integration of SW within operational and experimental environments. Document activities performed and lessons learned from participating in the exercises, demonstrations, or integration activities. Update the existing documentation. (See CDRLs, A009, B008, C008, D008, E008, F008, G008, H008, J008, K008, L008) | |
| 2.4 | Installation | |
| 2.4.1 | Site Survey: Conduct site surveys to identify special setup requirements to support the installation and integration of the specified system. Update the Site Preparation Requirements, Installation and Integration Plan. Make site modifications to the integration facility as necessary to support successful integration. (See CDRLs, A009, A011, B008, B010, C008, C010, D008, D010, E008, E010, F008, F010, G008, G010, H008, H010, J008, J010, K008, K010, L008, L010) | |
| 2.4.2 | HW and SW Configuration Verification Review: Perform HW and SW configuration verification review of Government designated sites and compare it against the minimum HW and SW configuration requirements stated in the installation plan or similar documentation. Verify that all appropriate manufacturer HW, SW and firmware upgrades have been installed and that all version levels are correct as specified in the installation plan. This shall be performed forty five (45) days prior to scheduled installation activities. Notify the Government of sites that fail to meet the required configuration. | |
| 2.4.3 | Installation Readiness Review: Perform an installation readiness review (typically within thirty (30) days after approval of the results of in plant testing) to ensure that the Government designated site(s) and all participants are ready for the Beta Test. Areas to be considered during the installation readiness review include: availability of SW installation media and associated SW installation plan, availability of physical work space at the Beta Site, shipment of all material including documentation to the Beta Site, a HW configuration review to ensure that the site(s) have sufficient HW and necessary SW and architectures in place to support the installation, and availability of personnel at the site(s) to support installation, familiarization and testing activities. Prepare and deliver a trip report. (See CDRLs, A011, B010, C010, D010, E010, F010, G010, H010, J010, K010, L010) | |
| 2.4.4 | Operational Site Installation and Test: Provide technical expertise to support system installation, test and evaluation of site HW and SW. These activities are coordinated in advance with the Government and the site. Installation, testing and evaluation activities shall occur with minimal disruption to the operational requirements of the site. | |
| 2.4.5 | Operational Site HW and SW Installation: Provide HW and SW installation support at Government designated site(s). HW and SW installation will normally be performed by site personnel with Contractor assistance provided as described in the SW installation plan, similar documentation or as directed by the Government. HW and SW installation support activities also include verification that the HW and SW has been correctly installed. Installation activities shall occur with minimal disruption to the operational requirements of the site. | |
| 2.4.6 | Operational Site Installation Testing: Provide technical expertise to support system installation, test and evaluation at Government designated site(s), consisting of the execution of the operational (system) test procedures, and any site specific tests deemed necessary by the operational site or the Government. | |
| 2.4.7 | Post Installation Support: Provide post installation support as required (typically up to fourteen (14) consecutive days) at each Government designated site to correct or aid in the resolution of any post installation system, HW, SW, familiarization, or documentation problems. | |
| 2.4.8 | Installation Report: Prepare and deliver a trip report upon completion of each installation visit as described in the SW installation plan, similar documentation or as requested by the Government. Address any problems encountered during installation, procedures for correcting the problems, problems that could not be corrected and their impact on operational use of the system capabilities, and a list of the complete site HW and SW inventory, and configuration for the installation. (See CDRLs, A011, B010, C010, D010, E010, F010, G010, H010, J010, K010, L010) | |
| 2.4.9 | Familiarization: Perform and document all required familiarization materials of the installed capability required for operational accreditation, use and maintenance. (See CDRLs A004, A009, B004, B008, C004, C008, D004, D008, E004, E008, F004, F008, G004, G008, H004, H008, J004, J008, K004, K008, L004, L008) | |
| 2.4.9.1 | Familiarization Sessions: Provide customers with familiarization sessions to include system and subsystem overviews. Provide overviews for any functional subsystem or database in which new SW capabilities or enhancements have been integrated. | |
| 2.4.9.2 | Plan and Schedule: Update the plan and schedule for all familiarization sessions. Develop and revise materials for effective presentations. If travel is required, submit a trip report. (See CDRLs, A009, A011, B008, B010, C008, C010, D008, D010, E008, E010, F008, F010, G008, G010, H008, H010, J008, J010, K008, K010, L008, L010) | |
| 2.4.9.3 | Security Authorization Package Support: Perform security authorization package engineering support to customer organization. Assist sites with documentation of Risk Management Framework (RMF) security control compliance | |
| 2.5 | Managed Services: Provide acquisition of managed services, including specific service elements such as computer room production capacity, application maintenance, configuration management, network support, performance monitoring and tuning, system backup and recovery, database management, storage management, data protection and management, help desk, web services, system operations, infrastructure facilities, and information security. In the provision of managed services, the components used by the service provider may include: facilities, HW and SW, network connectivity, labor, and other infrastructure. | |
| 2.5.1 | Web Services: Provide web design and maintenance services consisting of programming, data, human resources web services design, development, and maintenance activities. This may also include foundational components for Service Oriented Architecture (SOA) such as: architecture definition and guiding principles, governance structures and processes, and development tools and methodologies. Web development support may include design and development of web-based tools for enhanced network visibility and defense. Provide web management services. Design, develop, and manage designated websites to include providing system engineering input and analysis to the Government, as required. | |
| 2.5.2 | Configuration Management: Provide Configuration Management (CM) engineering Plan in accordance with current Institute of Electrical and Electronic Engineers (IEEE) and Electronics Industries Association (EIA) standards as further defined by DoD and AFRL guidance. Implement an integrated process for managing the information and products associated with the development and integration of the deliverable SW. The CM process shall support the full SW lifecycle (i.e., System Requirements Analysis and Design, SW Requirements Analysis, Preliminary Design, Detailed Design, Coding and Computer SW Configuration Item Testing, and System Integration and Testing). Participate in technical and program reviews conducted for other development programs that may impact this effort. Maintain and enhance CM processes for all activities within the program. Coordinate, evaluate, prioritize and schedule updates to baselines. Administer a baseline media, information and document library. (See CDRLs, A014, B013, C013, D013, E013, F013, G013, H013, J013, K013, L013) | |
| 2.5.2.1 | Provide CM process to support the development program offices collection, management, and distribution of information and products associated with the development, integration, and maintenance of program products including tracking of system site baseline configurations, including HW and SW. | |
| 2.5.2.2 | Provide centralized CM support for the collection, management and distribution of information products between developers, program offices, customers, and other interested parties. | |
| 2.5.2.3 | Support the collection, management and distribution of information and products associated with discrepancies and proposed changes of the product and program(s) supported. For example, Problem Reports (PRs), Change Requests (CRs), Request for Changes (RFCs), Request for Information (RFIs), Document Discrepancy Reports (DDRs) and other CM items in accordance with established and approved CM processes. | |
| 2.5.2.4 | PR and CR Reporting: Report and update existing documentation on open PRs, CRs, and RFCs. (See CDRLs, A009, B008, C008, D008, E008, F008, G008, H008, J008, K008, L008) |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .