Appendix J-7 Technology Needs Assessment Template.dotx.docx
DOCX document 702 KB Posted
- Solicitation number
- SAQMMA11R0186
About this file
Appendix J-7 Technology Needs Assessment Template
View the file
Other files
Show 40 more
Latest 50 of 55 listed here. See the rest on GovTribe.
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
Appendix J-7
<Product / System name> Technology Needs Assessment Version <0.0>
Produced for:
| Department of State |
| Technology Development Branch |
Produced by:
Systems Development & Engineering
| DS/FSE/TDB, SA-24 |
| 5800 Barclay Drive |
Alexandria, VA 22315
DATE: <MM/DD/YYYY>
Equipment type: <xxxxxx>
EXECUTIVE SUMMARY
Technology Needs Assessment: <Product / System name> Content Description (1-3 paragraphs):
· Who is the customer?
· What is the customer’s mission?
· What technology is required? What should it be able to do?
· What technology features are required?
· How will current / new technology answer current / future needs?
· PUBLICATION HISTORY
| Date |
| Version |
| Description |
| Author |
| 0.0 |
| <Product / System name> Technology Needs Assessment |
This document can be found on the OpenNet at:
https://intranet.ds.state.sbu/DS/C/ST/FSE/TDB/default.aspx Please refer to the TDB website for the latest version.
Corrections, comments, or questions should be sent to:
Department of State ATTN: ISE Section Chief
DS/TDB/ISE, SA-24
5800 Barclay Drive Alexandria, VA 22315
Table of Contents
| 1 | Document Definition / Objectives | 3 |
| 1.1 | References | 3 |
| 2 | Overview | 3 |
| 2.1 | Areas of Operations | 3 |
| 2.2 | General Technology Requirements | 3 |
| 2.2.1 | Required Capabilities: | 3 |
| 2.2.2 | Additional Capabilities | 3 |
| 2.2.3 | Constraints | 3 |
| 3 | Technology Review | 3 |
| 3.1 | Technology 1 | 3 |
| 3.1.1 | Description | 3 |
| 3.1.2 | Approximate Cost | 3 |
| 3.1.3 | Potential Benefits | 3 |
| 3.1.4 | Current Needs | 3 |
| 3.1.5 | Envisioned Future Needs | 3 |
| 3.2 | Technology 2 | 3 |
| 3.2.1 | Description | 3 |
| 3.2.2 | Approximate Cost | 3 |
| 3.2.3 | Potential Benefits | 3 |
| 3.2.4 | Current Needs | 3 |
| 3.2.5 | Envisioned Future Needs | 3 |
| 3.3 | Technology 3, etc. | 3 |
| 4 | Budget / Costs | 3 |
| 5 | Lifecycle | 3 |
| 6 | Projected Schedule | 3 |
| 7 | Conclusion | 3 |
| 7.1 | Impact of Disapproval | 3 |
| 7.2 | Major Issues | 3 |
| 7.3 | TBDs | 3 |
| 7.4 | Assumptions | 3 |
| 8 | Appendices / References | 3 |
List of Tables
| Table 2 Budget / Costs | 3 |
| Table 3 Lifecycle Comparison | 3 |
| Table 4 Projected Schedule | 3 |
Solicitation S-AQMMA-11-R-0186 Appendix J-7 Department of State Supply Chain Management
Solicitation S-AQMMA-11-R-0186 Appendix J-7 Department of State
Document Definition / Objectives
This Technology Needs Assessment document is intended to support the management decision-making process in establishing the need for changes in currently used technology, i.e. whether new technology should be evaluated. Approval of the Technology Needs Assessment leads to the creation of a Concept of Operations document for new technology evaluation.
The Technology Needs Assessment considers whether customer technology requirements can be met by new technology. This document will outline current customer needs, describe options for new technology and their respective benefits, and establish potential future needs.
References
· Customer Technology Requirements Document
Overview
<Content Description :>
· What are the customer technology requirements?
· Is this new / current technology?
· Describe available technology.
· Describe potential benefits.
· Describe current / future customer needs.
Areas of Operations
<List specifics. EX: CAA or Non-CAA? For Domestic or World Wide use?>
General Technology Requirements
Required Capabilities:
<List bullet points.> Additional Capabilities
<List bullet points.>
Constraints
<List bullet points.>
Technology Review
Review <Product / System name.>
Technology 1
Description
Approximate Cost
Potential Benefits
Current Needs
Envisioned Future Needs
Technology 2
Description
Approximate Cost
Potential Benefits
Current Needs
Envisioned Future Needs Technology 3, etc.
Budget / Costs
Budget / Costs
| Initial startup |
| Lifecycle |
<Current Year> (Costs associated with initial startup placed in this column) <Insert relevant years to lifecycle of technology (i.e. 2010-2017)> (Costs associated with lifecycle of technology placed in this column)
Technology Costs:
Cost of technology/system.
Additional Costs:
Can include, but not limited to, preparation costs, pre-installation costs, costs installation and components, costs of updating interconnected systems, costs associated with maintaining the technology, etc. These costs should be mandatory for the use of the technology/system.
Optional Costs: Can include, but not limited to, optional components that increase technology/system desirability but are not necessary for operational use.
Total Costs
Table 1 Budget / Costs
Lifecycle
<Include description of the technology/system lifecycle. What is the technology/system lifecycle and usability life?>
Lifecycle Comparison
| Product Lifecycle (in years) |
| Usability Life (in years) |
| Approx. Total Cost |
Technology 1
Technology 2
Technology 3 (add or delete as needed)
Table 2 Lifecycle Comparison
Projected Schedule
<This section will include a description of a projected schedule for the outlined technology/technologies. This section should include/take into account how long it will take to acquire samples to test or see demonstrations from vendors, and also how long it will take to actually test/evaluate the technology/system. This section should also take into account the proposed schedule as provided by the customer. Is this schedule possible/realistic? If it is not, please provide reasoning to help the customer understand what is realistic and possible. >
Projected Schedule
| Purpose |
| Process |
| Outcome |
| Projected Due Date |
| Phase 1 |
| Insert purpose |
| Required steps |
| Expected outcomes |
| Expected completion date |
| Phase 2 |
| Insert purpose |
| Required steps |
| Expected outcomes |
| Expected completion date |
| Phase 3 [add or delete phases as needed] |
| Insert purpose |
| Required steps |
| Expected outcomes |
| Expected completion date |
Table 3 Projected Schedule
Conclusion <General summary of document>
Impact of Disapproval <Briefly discuss the impact of not receiving approval on the program, including impacts on current and planned missions and capabilities.> Major Issues <Include any known or envisioned issues related to any area associated to the new technology.> TBDs
Assumptions
1. The initiation phase is started.
2. The technology strategy team has been staffed and trained in technology analysis.
Appendices / References
Solicitation S-AQMMA-11-R-0186 Appendix J-7 Department of State
<Month date, year>
UNCLASSIFIED
ACTION MEMORANDUM FOR<Department name and Manager/Director> FROM: <Department name and Manager/Director>
SUBJECT: Technology Needs Assessment
Recommendation:
That you authorize DS/FSE/TDB, to move to the next phase of the <product name> evaluation flow, ConOps or Technology Evaluation.
Approve_________________ Disapprove_________________
DS/ST/FSE – Mr. Michael J. Barela Date
Background:
This Technology Needs Assessment document is intended to support the management decision-making process in establishing the need for changes in currently used technology, that is, whether new technology should be evaluated. This document is evaluated and it is determined through managerial review whether or not to proceed in the process of fulfilling the customer’s needs. If chosen to move forward, a ConOps document will be generated for new technology or a Technology Evaluation will be generated for old or similar technology.
image1.png image2.png image3.png
File details come from the government source that posted it. Updated .