G-2_AIS_Data_Collection_Requirements_Template_-_29_Oct_15.xlsx
XLSX spreadsheet 1 MB Posted
- Attached to
- AFCAA Cost Estimating Modeling (CEM) Support Federal contract opportunity
- Solicitation number
- FA7014-16-R-5004
About this file
G-2 AIS Data Collection Templates (DRAFT) 29 Oct 15
View the file
Other files for this federal contract opportunity
Show all 19
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
OY2 CRM
| COMMENT TYPE CODES (Column G) | |
| A | Administrative (grammar, punctuation, style, etc.) that should be addressed |
| M | Major (Material as is may lead to unnecessary confusion…should be a better way to deal with it |
| C | Critical (Contentious issue that will cause non-concurrence with publication) |
| N | Suggestion, New Requirement |
| Comment # | Your Name | Your Organization | Template/Tab | Row or WBS Number | WBS/CRS/Technical Parameter | Comment Type | |||||||
| (See table above) | Comment on WBS Item (W), Definiton (D) or Other Comment (O) | Observation, Comment, Suggested Edit or Question | Rationale | AIS Commodity Adjudication | Status | ||||||||
| 1 | AFCAA CEM Tech Lead | M | O | Tech Lead direction to standardize CEM templates | Standardizing CEM worksheets where possible aids in developing instructions and in training data providers | Accepted. | On-going | ||||||
| 2 | Ms. Woods | AFCAA | WBS, Software, O&S | M | O | Evaluate AIS CEM template's O&S Mnx and O&S Enhacement WBS and Worksheets | Need standard WBS for software enhancements vs modifications less than full system redesign. | Action item from 2nd Quarterly review. Accepted. | Resolved within O&S and MAIS WGs. Single AIS software O&S worksheet and standardized WBS is complete | ||||
| 3 | MAIS WG | WBS | 1.1.1, 1.1.2, 1.1.3, 1.1.4 | M | W | Eliminate subsystem hadware (Appdx K) | AIS CEM Hardware uses 1.1.5 (dev h/w), 1.5.3 SIL (test h/w) and 1.10.n.1.1 (Prod h/w). Removing subsystem h/w from 1.1.1 through 1.1.4 eliminates extraneous hardware WBS elements. | Accepted | Complete 5 Oct 15 | ||||
| 4 | MAIS WG | WBS | 1.5.3 | M | W | Add same level of hardware detail from Dev h/w (1.1.5) to SIL (WBS 1.5.3) | Hardware detail for Systems Integration Lab is an important component of the full system hardware picture so level of h/w detail for test hardware should be expanded. | Accepted | Complete 5 Oct 15 | ||||
| 5 | Rich Mabe / AIS and C3I CEM Leads | AFCAA, CEM Team | PMP, Parts, Config Templates | Dev, Test, Prod hardware WBS | Dev, Test, Prod hardware parameters | N, M | O | C2 groundstation and AIS hardware are very similar. Recommendation was to standarize on hardware elements and technical parameters | Capture best of both CEMs. Improves data collection and future CER development efforts | Accepted | First iteration done. AIS and C3I CEM teams and AOs are reviewing | ||
| 6 | MAIS WG | Hardware / Infrastructure | WBS | M | O | Infrastructure as an enterprise service is not specifically called out in the AIS CEM WBS | Where infrastructure is provided as an enterprise service the WBS needs to include that and have associated technical parameters | Accepted. Added IAAS to Dev (1.1.5), Test (1.5.3) and Production (1.10.n.1.1) hardware elements where hardware is not procured but is paid for as a service (DISA, etc) | Draft complete. Follow-up review with MAIS WG pending | ||||
| 7 | |||||||||||||
| 8 | |||||||||||||
| 9 | |||||||||||||
| 10 | |||||||||||||
| 11 | |||||||||||||
| 12 | |||||||||||||
| 13 | |||||||||||||
| 14 | |||||||||||||
| 15 |
Program
| ProgramTemplate | UNCLASSIFIED, FOR OFFICIAL USE ONLY | TagName1 | TagValue1 |
| AFCAA CEM Templates | TagName2 | TagValue2 | |
| Program Template | TagName3 | TagValue3 |
| ColumnHead | Parameter Name | Value | Unit of Measure | Estimate or Actual | Source | Notes | Definition of Parameter | VocabularyID |
| Program Name | Program Name | DCARCMetadata | ||||||
| Program Name | DCARC defined Program Name | DCARCMetadata | ||||||
| Name - Short | DCARC defined, acronym | CEMVocab | ||||||
| Name - Popular | An optional alternative name | CEMVocab | ||||||
| Program Description | DCARC defined program description | CEMVocab | ||||||
| Program Number | Program Number | DCARCMetadata | ||||||
| Mil-Handbook | Mil-STD-881 Appendix | DCARCMetadata | ||||||
| Weapon System Type | DCARC defined | DCARCMetadata | ||||||
| Lead Service | DCARC defined Service/Component | DCARCMetadata | ||||||
| Other Services | If a program is "Joint", then list other services involved in the program. | DCARCMetadata | ||||||
| Procuring Organization | SysCom | DCARCMetadata | ||||||
| Test Agency | List Agencies | CEMVocab | ||||||
| Program Office | PEO or Program Office | DCARCMetadata | ||||||
| Information Assurance Certification Level | DIACAP / JITC Certification Level | CEMVocab | ||||||
| Release Number | Release Number | CEMVocab | ||||||
| Initial Selected Acquisition Review (SAR) | Date from DAMIR | DCARCMetadata | ||||||
| Latest Selected Acquisition Review (SAR) | Date from DAMIR | DCARCMetadata | ||||||
| Upgrade/Modernization | Yes/No category | CEMVocab | ||||||
| Subprogram Name | Subprogram name if applicable | CEMVocab | ||||||
| Model | Specific configuration or designated model number | CEMVocab |
UOM is N/A for this sheet. Column included only for shape consistency.
Est/Act is N/A for this sheet. Column included only for shape consistency.
Enter text for each parameter.
Milestone Table
| MilestoneTable | UNCLASSIFIED, FOR OFFICIAL USE ONLY | TagName1 | TagValue1 |
| CEM Template | TagName2 | TagValue2 | |
| Milestone Table | TagName3 | TagValue3 |
| ColumnHead | Subprogram Name | |||||||||||||
| Parameter Name | Value | Units | Unit Qualifier | Estimate (Planned) or Actual | Source | Notes | Value | Units | Estimate or Actual | Source | Notes | Definition of Parameter | VocabularyID | |
| Material Development Decision | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||||||
| Completion of AoA, BCA, or Equivalent | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||||||
| Milestone A | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||||||
| Technology Maturation and Risk Reduction Contract Award | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||||||
| Capability Development Document (CDD) Validation | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||||||
| Development RFP Release Decision | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||||||
| Risk Reduction Build | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||||||
| Preliminary Design Review (PDR) | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||||||
| Milestone B | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||||||
| EMD Contract Award | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||||||
| Increment 1..n Begin | Date | DDMMMYY | Milestone Date | CEMVocab | ||||||||||
| Build 1..n Begin | Date | DDMMMYY | Milestone Date | CEMVocab | ||||||||||
| Increment 1..n End | Date | DDMMMYY | Milestone Date | CEMVocab | ||||||||||
| Build 1..n End | Date | DDMMMYY | Milestone Date | CEMVocab | ||||||||||
| System Requirements Review (SRR) |
Manzo, James F. WDC Tecolote: Manzo, James F. WDC Tecolote:
| SRR, PDR and CDR are more acquisition (contract specific) events. Do these events fit better on the Acquisition tab? When does SRR occur? PDR occurs before M/S B. | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| Critical Design Review (CDR) | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| First Delivery | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| Development Test & Evaluation Begin | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| Development Test & Evaluation End | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| Operational Test & Evaluation Begin | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| Operational Test & Evaluation End | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| Limited Deployment Decision (1..n) | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| Integration Build 1..n | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| Milestone C | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| Limited Deployment (1..n) | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| Operational Test & Evaluation Begin | Date | DDMMMYY | Milestone Date | CEMVocab | ||||||
| Operational Test & Evaluation End | Date | DDMMMYY | Milestone Date | CEMVocab | ||||||
| Full Deployment Decision (FDD) | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| Initial Operational Capability (IOC) | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| Full Deployment (FD) | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab | |||||
| Full Operational Capability (FOC) | Date | DDMMMYY | DDMMMYY | Milestone Date | CEMVocab |
Enter parameter values as a single date value in this column.
Identify if the parameter value is an actual value or an estimated value.
Enter parameter values as a single date value in this column.
Identify if the parameter value is an actual value or an estimated value
If these columns are expanded and used to convey a second subprogram or model, take care to each case in the first column heading cell.
When any parameter calls for additional detail, insert rows underneath and indent sub-names as needed.
For additional columns to express alternative designs, hit Ungroup button above.
Acquisition Table
| AcquisitionTable | UNCLASSIFIED, FOR OFFICIAL USE ONLY | TagName1 | TagValue1 |
| CEM Template | TagName2 | TagValue2 | |
| Acquisition Table | TagName3 | TagValue3 |
ColumnHead Material Solution Analysis Technology Maturation and Risk Reduction Engineering and Manufacturing Development/Development & Deployment Increments/Builds Manzo, James F. WDC Tecolote:
Increments/Builds consistent with 5000.02.
| I1/B1 | |||||||||||||||
| Manzo, James F. WDC Tecolote: Increment1/Build1 (I1/B1) to be consistent with DODI 5000.02 terminology. | I1/B2 | I2/B1 | I2/B2 | I2/B3 | In/Bn | ||||||||||
| Parameter Name | Value | Value | Value | Value | Value | Value | Value | Value | Value | Units | Units Qualifier | Definition of Parameter | VocabularyID | ||
| Short Name or Popular Name of Phase or Lot | Text | The common name of this phase or lot. | CEMVocab | ||||||||||||
| Award or Begin Date | Date | DDMMMYY | Date of contract award announcement or beginning of phase. | CEMVocab | |||||||||||
| First Delivery Date | Date | DDMMMYY | The date of the first delivery. | CEMVocab | |||||||||||
| End Date | Date | DDMMMYY | The end data of this phase or lot. | CEMVocab | |||||||||||
| Contracting Strategy During this Phase/Release | Description | Describe this phase's acquisition strategy. | CEMVocab | ||||||||||||
| Competition During this Phase/Release | List | List the Competition Approach: None; Full Phase Competed; Competition thru CDR; etc. | CEMVocab | ||||||||||||
| Warranty Included (Y/N) | List | Y/N | Is there a warranty for this lot? | CEMVocab | |||||||||||
| Warranty Type | Description | Describe Warranty | CEMVocab | ||||||||||||
| Capital Investment (Y/N) | List | Y/N | Is this the first lot to benefit from capital investment, tooling, plant rearrangement, etc.? | CEMVocab | |||||||||||
| Capital Investment Description | Description | Describe capital improvements. | CEMVocab | ||||||||||||
| Government Test Agency | List | List Agencies and MIPR or WR numbers | CEMVocab | ||||||||||||
| Contractor Name | Text | Name of contractor | CEMVocab | ||||||||||||
| Special Cases | Text | Additional text as needed | CEMVocab | ||||||||||||
| Additional Information | Text | Additional text as needed | CEMVocab | ||||||||||||
| Funding Appropriation | Code | A/N | Appropriation code | CEMVocab | |||||||||||
| Funding Year | Numeric | YYYY | Funding year(s) | CEMVocab |
| Acquisition Table - Contract Detail | ||||
| Contract Number(s) | Text | A/N | Prime contract number | CEMVocab |
| Option Number(s) | Text | A/N | Contract option number if applicable | CEMVocab |
| Subcontract Number(s) | Text | A/N | Subcontract number. | CEMVocab |
Describe each Phase/Release/Increment
The column headings shown are an example only. Modify headings and insert additional columns as needed to fully describe the program model.
Add contract details if applicable List all planned Phases/Releases/Increments in sequence. Insert additional columns as needed.
Provide quantitiy information on the Acquisition and O&S Time Phased Table.
Quantities and O&S Time Phased
| TimePhasedTableQuantity | UNCLASSIFIED, FOR OFFICIAL USE ONLY | TagName1 | TagValue1 |
| CEM Template | TagName2 | TagValue2 | |
| Acquisition Quantities, Fielding, and O&S Time Phased Table | TagName3 | TagValue3 |
| ColumnHead | Item Name | YR 1 | YR 2 | YR 3 | YR 4 | YR 5 | YR 6 | YR 7 | YR 8 | YR 9 | YR 10 | YR n … | Long Lead Requirements | Unit of Measure | Unit Qualifier | Source | Notes | VocabularyID |
| Designate each column as Estimate or Actual ---> |
| Development/Test/O&S System Quantity | Quantity | Dev, Test, O&S | CEMVocab |
| End Item #1 | |||
| End Item #2 | |||
| End Item #3 | |||
| End Item #4 | |||
| … | |||
| Training Item #1 | |||
| Training Item #2 | |||
| … | |||
| Support Equipment Item #1 | |||
| Support Equipment Item #2 | |||
| … |
| Procurement Quantity | Quantity | Procurement Items | CEMVocab |
| End Item #1 | |||
| End Item #2 | |||
| End Item #3 | |||
| End Item #4 | |||
| … | |||
| Training Item #1 | Quantity | Training Items | CEMVocab |
| Training Item #2 | |||
| … | |||
| Support Equipment Item #1 | |||
| Support Equipment Item #2 | |||
| … |
| Deliveries/Installs | Quantity | Procurement Items | CEMVocab |
| End Item #1 | |||
| End Item #2 | |||
| End Item #3 | |||
| End Item #4 | |||
| … | |||
| Training Item #1 | |||
| Training Item #2 | |||
| … | |||
| Support Equipment Item #1 | |||
| Support Equipment Item #2 | |||
| … |
| Inventory/Fielded Density (by Item) | Quantity | Procurement Items | CEMVocab |
| End Item #1 | |||
| End Item #2 | |||
| End Item #3 | |||
| End Item #4 | |||
| … | |||
| Training Item #1 | |||
| Training Item #2 | |||
| … | |||
| Support Equipment Item #1 | |||
| Support Equipment Item #2 | |||
| … |
| Inventory/Fielded Density (by Location) | Quantity | Procurement Items | CEMVocab |
| Base #1 or Primary or COOP infrastructure site(s) | |||
| End Item #1 | |||
| End Item #2 | |||
| End Item #3 | |||
| End Item #4 | |||
| … | |||
| Training Item #1 | |||
| Training Item #2 | |||
| … | |||
| Support Equipment Item #1 | |||
| Support Equipment Item #2 | |||
| … | |||
| Base #1 or Primary or COOP infrastructure site(s) | |||
| End Item #1 | |||
| End Item #2 | |||
| End Item #3 | |||
| End Item #4 | |||
| … | |||
| Training Item #1 | |||
| Training Item #2 | |||
| … | |||
| Support Equipment Item #1 | |||
| Support Equipment Item #2 | |||
| … | |||
| … |
| Operational Activity |
| Number of Users |
| Number of Concurrent Users |
| System Throughput (Transactions) |
| Data Storage |
| Demilitarization/Disposal | Quantity | Procurement Items | CEMVocab |
| End Item #1 | |||
| End Item #2 | |||
| End Item #3 | |||
| End Item #4 | |||
| … | |||
| Training Item #1 | |||
| Training Item #2 | |||
| … | |||
| Support Equipment Item #1 | |||
| Support Equipment Item #2 | |||
| … |
| NDI Refresh Events |
| End Item #1 |
| End Item #2 |
| End Item #3 |
| End Item #4 |
| … |
| Training Item #1 |
| Training Item #2 |
| … |
| Support Equipment Item #1 |
| Support Equipment Item #2 |
| … |
| Training Events |
| Class #1 |
| Class #2 |
| Class #3 |
| Class #4 |
| System/Release/Location Activation |
| Sites Activated |
| Operator Training |
| Maintainer Training |
| … |
Enter name of item.
Use headings in bold and indent wherever it is useful to do so.
All entries below are examples only.
Enter annual values here.
Note early years may be known and future years forecasted. Designate in row 6.
For procurement quantities, enter text describing long lead requirements. Could be expressed as a percent of funds or names of specific items that must be purchased early.
Otherwise leave blank.
Unit of Measure is Aircraft, Engines, AURs, Radars, Silos, Sites, etc.
Enter annual Dev/Test/Sustainment COTS HW and SW quantities here.
Include non-PME (i.e., Training, CSE, PSE units) as well as PME.
Enter annual procurement COTS HW and SW quantity installed or delivered here.
This is pertinent for modeling fielding event costs.
Examples only Enter the cumulative quantities delivered and supported here.
This is pertinent for modeling O&S costs.
Show ramp-down of items leaving service at end of useful life.
Enter quantity of sites activated here.
Entries often will simply be 1 if each site is explicitly named in column D.
This is pertinent for modeling base activation costs and to begin O&S of location costs.
Enter annual quantity of items leaving service at end of useful life.
This is pertinent for modeling disposal costs as well as density ramp-down.
Begin at earliest year quantity data is applicable.
List all program years. Avoid using Prior and To-complete columns - be explicit.
Enter the cumulative quantities delivered and supported by location here.
This is pertinent for modeling O&S costs.
Show ramp-down of items leaving service at end of useful life.
Enter annual COTS HW and SW procurement quantities here. Include non-PME as well as PME.
Enter annual quantity of NDI refresh events here.
This is pertinent for modeling refresh cycle costs.
Enter annual activity. Expand by Location or End Item as needed.
This column is WBS/CRS on other templates.
But there does not appear to be a compelling need to have these table entries numbered
Roles Table
| RolesTable | UNCLASSIFIED, FOR OFFICIAL USE ONLY | TagName1 | TagValue1 |
| CEM Template | TagName2 | TagValue2 | |
| Roles Table | TagName3 | TagValue3 |
| ColumnHead | WBS/CRS Number | WBS/CRS Element | Government Role | Prime Contractor | Secondary Subcontractor/Supplier/Third Party | Tertiary Subcontractor/Supplier/Third Party | Notes |
| 1.0 | Automated Information System (AIS) Investment | ||||||
| 1.1 | AIS Prime Mission Product Release | ||||||
| 1.1.1 | Custom Application Software | ||||||
| 1.1.1.2 | Subsystem Software CSCI 1…n (Specify) | ||||||
| 1.1.1.3 | Subsystem Software Integraton, Assembly, Test and Checkout | ||||||
| 1.1.2 | Enterprise Service Element | ||||||
| 1.1.2.2 | Enterprise Service Element Software CSCI 1…n (Specify) | ||||||
| 1.1.2.3 | Enterprise Service Element Software Integraton, Assembly, Test and Checkout | ||||||
| 1.1.3 | Enterprise Information System | ||||||
| 1.1.3.2 | Business Area Software CSCI 1…n (Specify) | ||||||
| 1.1.3.3 | Business Area Integration, Assembly, Test and Checkout | ||||||
| 1.1.4 | External System Interface Development 1…n (Specify) | ||||||
| 1.1.4.2 | External System Interface Software CSCI 1…n (Specify) | ||||||
| 1.1.4.3 | External System Interface Integration, Assembly, Test and Checkout | ||||||
| 1.1.5 | Development Suite Hardware | ||||||
| 1.1.5.1 | Servers | ||||||
| 1.1.5.1.1 | Web Servers | ||||||
| 1.1.5.1.2 | Application Servers | ||||||
| 1.1.5.1.3 | Database Servers | ||||||
| 1.1.5.1.4 | Other | ||||||
| 1.1.5.2 | Data Storage | ||||||
| 1.1.5.3 | Workstations | ||||||
| 1.1.5.4 | Communication Hardware | ||||||
| 1.1.5.4.1 | Wide-Area Gateways | ||||||
| 1.1.5.4.2 | Wide-Area Networks (WAN) | ||||||
| 1.1.5.4.3 | Local Area Networks (LAN) | ||||||
| 1.1.5.4.4 | Modems & Switches | ||||||
| 1.1.5.4.5 | Crypto | ||||||
| 1.1.5.4.6 | Other Comm. Hardware | ||||||
| 1.1.5.5 | Peripheral Devices | ||||||
| 1.1.5.6 | Other Hardware | ||||||
| 1.1.5.7 | Developmente Hardware Integration | ||||||
| 1.1.5.8 | Enterprise Services | ||||||
| 1.1.5.8.1 | Infrastructure as a Service (IAAS) | ||||||
| 1.1.5.8.2 | Software as a Service (SAAS) | ||||||
| 1.1.5.8.3 | Other Enterprise Services | ||||||
| 1.1.6 | System Level Integration | ||||||
| 1.2 | System Engineering | ||||||
| 1.3 | Program Management | ||||||
| 1.4 | Change Management | ||||||
| 1.5 | System Test and Evaluation | ||||||
| 1.5.1 | Development Test and Evaluation (DT&E) | ||||||
| 1.5.1.1 | System Integration Test (SIT) | ||||||
| 1.5.1.2 | System Acceptance Test (SAT) | ||||||
| 1.5.2 | Operational Test and Evaluation (OT&E) | ||||||
| 1.5.2.1 | Limited User Evaluation (LUE/M-LUT/FUE) | ||||||
| 1.5.2.2 | Interoperability Testing (IOP with IA/OT&E) | ||||||
| 1.5.3 | Mock-ups/ System Integration Labs (SIL) | ||||||
| 1.5.3.1 | Servers | ||||||
| 1.5.3.1.1 | Web Servers | ||||||
| 1.5.3.1.2 | Application Servers | ||||||
| 1.5.3.1.3 | Database Servers | ||||||
| 1.5.3.1.4 | Other Servers | ||||||
| 1.5.3.2 | Data Storage | ||||||
| 1.5.3.3 | Workstations | ||||||
| 1.5.3.4 | Communication Hardware | ||||||
| 1.5.3.4.1 | Wide-Area Gateways | ||||||
| 1.5.3.4.2 | Wide-Area Networks (WAN) | ||||||
| 1.5.3.4.3 | Local Area Networks (LAN) | ||||||
| 1.5.3.4.4 | Modems & Switches | ||||||
| 1.5.3.4.5 | Crypto | ||||||
| 1.5.3.4.6 | Other Comm. Hardware | ||||||
| 1.5.3.5 | Peripheral Devices | ||||||
| 1.5.3.6 | Other Hardware | ||||||
| 1.5.3.7 | Test Hardware (SIL) Integration | ||||||
| 1.5.3.8 | Enterprise Services | ||||||
| 1.5.3.8.1 | Infrastructure as a Service (IAAS) | ||||||
| 1.5.3.8.2 | Software as a Service (SAAS) | ||||||
| 1.5.3.8.3 | Other Enterprise Services | ||||||
| 1.5.4 | Test and Evaluation Support | ||||||
| 1.5.5 | Test Facilities | ||||||
| 1.6 | Training | ||||||
| 1.6.1 | Equipment | ||||||
| 1.6.2 | Services | ||||||
| 1.6.3 | Facilities | ||||||
| 1.7 | Data | ||||||
| 1.7.1 | Technical Publications | ||||||
| 1.7.2 | Engineering Data | ||||||
| 1.7.3 | Management Data | ||||||
| 1.7.4 | Support Data | ||||||
| 1.7.5 | Data Depository | ||||||
| 1.8 | Peculiar Support Equipment | ||||||
| 1.8.1 | Test and Measurement Equipment | ||||||
| 1.8.2 | Support and Handling Equipment | ||||||
| 1.9 | Common Support Equipment | ||||||
| 1.9.1 | Test and Measurement Equipment | ||||||
| 1.9.2 | Support and Handling Equipment | ||||||
| 1.10 | Operational/Site Activation | ||||||
| 1.10.n | Production Site/Environment (1…n) | ||||||
| 1.10.n.1 | Production Site Hardware and Software | ||||||
| 1.10.n.1.1 | Hardware | ||||||
| 1.10.n.1.1.1 | Servers | ||||||
| 1.10.n.1.1.1.1 | Web Servers | ||||||
| 1.10.n.1.1.1.2 | Application Servers | ||||||
| 1.10.n.1.1.1.3 | Database Servers | ||||||
| 1.10.n.1.1.1.4 | Other | ||||||
| 1.10.n.1.1.2 | Data Storage | ||||||
| 1.10.n.1.1.3 | Workstations | ||||||
| 1.10.n.1.1.4 | Communication Hardware | ||||||
| 1.10.n.1.1.4.1 | Wide-Area Gateways | ||||||
| 1.10.n.1.1.4.2 | Wide-Area Networks (WAN) | ||||||
| 1.10.n.1.1.4.3 | Local Area Networks (LAN) | ||||||
| 1.10.n.1.1.4.4 | Modems & Switches | ||||||
| 1.10.n.1.1.4.5 | Crypto | ||||||
| 1.10.n.1.1.4.6 | Other Comm. Hardware | ||||||
| 1.10.n.1.1.5 | Peripheral Devices | ||||||
| 1.10.n.1.1.6 | Other Hardware | ||||||
| 1.10.n.1.1.7 | Production Hardware Integration | ||||||
| 1.10.n.1.2 | Software (See SW Template) | ||||||
| 1.10.n.2 | Enterprise Services | ||||||
| 1.10.n.2.1 | Infrastructure as a Service (IAAS) | ||||||
| 1.10.n.2.2 | Software as a Service (SAAS) | ||||||
| 1.10.n.2.3 | Other Enterprise Services | ||||||
| 1.10.n.3 | User Documentation | ||||||
| 1.10.n.4 | Site Activation | ||||||
| 1.10.n.5 | User Training | ||||||
| 1.10.n.6 | Data Migration | ||||||
| 1.10.n.7 | Management/Engineering Support | ||||||
| 1.10.n.8 | Interim Logistics Support | ||||||
| 1.11 | Site Construction/Conversion | ||||||
| 1.12 | Initial Spares and Repair Parts |
| 2.0 | AIS Sustainment Effort |
| 2.1 | Unit Level Manpower |
| 2.2 | Unit Level Operations |
| 2.3 | Maintenance |
| 2.4 | Sustaining Support |
| 2.4.1 | System -Specific Training |
| 2.4.2 | Support Equipment Replacement and Repair |
| 2.4.3 | Sustaining/Systems Engineering |
| 2.4.4 | Program Management |
| 2.4.5 | Information Systems |
| 2.4.5.1 | Tech Refresh |
| 2.4.5.1.1 | Servers |
| 2.4.5.1.1.1 | Web Servers |
| 2.4.5.1.1.2 | Application Servers |
| 2.4.5.1.1.3 | Database Servers |
| 2.4.5.1.1.4 | Other |
| 2.4.5.1.2 | Data Storage |
| 2.4.5.1.3 | Workstations |
| 2.4.5.1.4 | Communication Hardware |
| 2.4.5.1.4.1 | Wide-Area Gateways |
| 2.4.5.1.4.2 | Wide-Area Networks (WAN) |
| 2.4.5.1.4.3 | Local Area Networks (LAN) |
| 2.4.5.1.4.4 | Modems & Switches |
| 2.4.5.1.4.5 | Crypto |
| 2.4.5.1.4.6 | Other Comm. Hardware |
| 2.4.5.1.5 | Peripheral Devices |
| 2.4.5.1.6 | Other Hardware |
| 2.4.5.2 | License Fees (Software) |
| 2.4.5.3 | System Support |
| 2.4.5.3.1 | Help Desk |
| 2.4.5.3.1.1 | Tier 1 |
| 2.4.5.3.1.2 | Tier 2 |
| 2.4.5.3.1.3 | Tier 3 |
| 2.4.5.3.2 | System Database/Administration (DISA, Commercial Hosting) 1…n |
| 2.4.5.3.3 | Follow-on User Training |
| 2.4.5.3.4 | Acceditation (Recurring) |
| 2.4.5.3.5 | Independent Verification and Validation (IV&V) |
| 2.4.6 | Data and Technical Publications |
| 2.4.7 | Simulator Operations |
| 2.4.8 | Other Sustaining Support |
| 2.5 | Continuing System Improvements |
| 2.5.1 | Hardware Modifications |
| 2.5.2 | Software Maintenance or Modification |
| 2.5.2.1 | Software Change |
| 2.5.2.1.1…n | Release 1…n |
| 2.5.2.2 | Project Management |
| 2.5.2.3 | Software License Management |
| 2.5.2.4 | Cybersecurity |
| 2.5.2.5 | System Facilities |
| 2.5.2.6 | Sustaining Engineering |
| 2.5.2.7 | Field Software Engineering (FSE) |
| 2.5.2.8 | Operational Management |
Specify Government's Role by WBS Element (e.g., GFE, Test, Hosting Site(s)).
Specify Prime Contractor Name by WBS Element.
Specify Subcontractor/Supplier/3rd Party by name. Elaborate on specific role or contracting arrangement in Notes, if needed.
PMP Hardware Technical Table
| UNCLASSIFIED, FOR OFFICIAL USE ONLY | Unit Qualifier |
| CEM Template | |
| PMP Hardware Technical Table |
| Primary Data Set (Government) | Second Reference Design (e.g. Contractor A) | Third Reference Design (e.g. Contractor B) | |||||||||||||||||||||||||||||||||||||||||||||||
| WBS Number | WBS Element | Parameter name | 1921-T Priority (1, 2 or 3) | Value | Low | High | Margin | Units | Unit Qualifier | Estimated or Actual | Objective | Threshold | Source | Notes | Value | Low | High | Margin | Units | Unit Qualifier | Estimated or Actual | Objective | Threshold | Source | Notes | Value | Low | High | Margin | Units | Unit Qualifier | Estimated or Actual | Objective | Threshold | Source | Notes | Definition of Parameter | Vocabulary ID | List Item 1 | List Item 2 | List Item 3 | List Item 4 | List Item 5 | List Item 6 | List Item 7 | List Item 8 | List Item 9 | List Item 10 | List Item 1..n |
| 1.1.5 | Development Suite Hardware (HW) | HW suite utilized for developing and configuring an AIS. | |||||||||||||||||||||||||||||||||||||||||||||||
| 1.1.5.1 | Servers | Roll-Up of servers defined below. | |||||||||||||||||||||||||||||||||||||||||||||||
| 1.1.5.1.1 | Web Servers | Web servers provide access to the Internet through the HyperText Transfer Protocol (HTTP). Files in a web server use HyperText Markup Language (HTML) to display content on web browsers. A web server usually receives requests from a web browser and sends back the requested HTML file and related graphic files. | |||||||||||||||||||||||||||||||||||||||||||||||
| Processor Type (data, signal, other) | Text | Text | Text | Description of the processor used in the server, including manufacturer, version number, etc. | |||||||||||||||||||||||||||||||||||||||||||||
| Weight | 3 | lbs | lbs | lbs | Physical weight of the item. | ||||||||||||||||||||||||||||||||||||||||||||
| Length | 3 | inches | inches | inches | The length of the item. |
Width 3 inches inches inches The width of the item.
Depth 3 inches inches inches The depth of the item.
Performance (Throughput) 1 FLOPS Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
| The amount of useful work accomplished by a computer system compared to the time or resources inFloating Point Operations Per Second (FLOPS) | ||||||||||||||
| Memory Capacity | 1 | Gigabytes (GB) | Gigabytes (GB) | Gigabytes (GB) | How many Gigabytes (GB) of Random Access Memory (RAM) is installed on each individual server system? | |||||||||
| Data Rate | 1 | Mega bits per second | Mega bits per second | Mega bytes per second | The speed at which information is transferred through a communications or computing medium; measured in bytes per second. | |||||||||
| # Chips | ||||||||||||||
| per System | 2 | Chips per System | Chips per System | Chips per System | Total number of processors (chips) integrated into each individual server system (e.g. two quad-core processors = 2 chips) | |||||||||
| # Threads/Core | ||||||||||||||
| per System | 2 | Threads per Core | Threads per Core | Threads per Core | The total number of threads each core can run simultaneously. (A thread is an application process that is run by the processor. Multi-thread processors can run multiple threads at once without queuing.) | |||||||||
| Clock Speed | 1 | MHz | MHz | MHz | Megahertz (MHz) is the processor clock speed, how many instruction cycles per second a processor can perform. | |||||||||
| Operating System | 2 | Text | Text | Text | Identify what operating system is loaded on the server system. | |||||||||
| 1.1.5.1.2 | Application Servers | Application servers are dedicated to running certain software applications. The application server often serves to connect database servers with the end-user, thus acting as a kind of "middleware" that releases stored information requested by said user. The server is usually responsible for properly decoding and recoding data and providing security over connections. |
McDowell, Jeff HSV Tecolote: C.4.2.1 Airframe. This element comprises the structural framework that provides the aerodynamic shape, mounting surfaces and environmental protection for the air vehicle components, which are not directly applicable to other specific Level 3 air vehicle subsystems.
Includes, for example:
a. Wings and fins that provide aerodynamic flight control in response to electro-mechanical signals and are attached to the air vehicle body
b. Structural body assemblies including the structure, fuel tanks that integral with the structure, covers, skins, adhesives, and fairings not directly applicable to any other Level 3 air vehicle subsystem
c. Protection devices for stressing environmental conditions such as thermal protection system or rain erosion that are not directly applicable to other Level 3 air vehicle subsystems
| Processor Type (data, signal, other) | Text | Text | Text | Description of the processor used in the server, including manufacturer, version number, etc. | |
| Weight | 3 | lbs | lbs | lbs | Physical weight of the item. |
| Length | 3 | inches | inches | inches | The length of the item. |
Width 3 inches inches inches The width of the item.
Depth 3 inches inches inches The depth of the item.
Performance (Throughput) 1 FLOPS Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
| The amount of useful work accomplished by a computer system compared to the time or resources inFloating Point Operations Per Second (FLOPS) | ||||||||||||||
| Memory Capacity | 1 | Gigabytes (GB) | Gigabytes (GB) | Gigabytes (GB) | How many Gigabytes (GB) of Random Access Memory (RAM) is installed on each individual server system? | |||||||||
| Data Rate | 1 | Mega bits per second | Mega bits per second | Mega bytes per second | The speed at which information is transferred through a communications or computing medium; measured in bytes per second. | |||||||||
| # Chips | ||||||||||||||
| per System | 2 | Chips per System | Chips per System | Chips per System | Total number of processors (chips) integrated into each individual server system (e.g. two quad-core processors = 2 chips) | |||||||||
| # Threads/Core | ||||||||||||||
| per System | 2 | Threads per Core | Threads per Core | Threads per Core | The total number of threads each core can run simultaneously. (A thread is an application process that is run by the processor. Multi-thread processors can run multiple threads at once without queuing.) | |||||||||
| Clock Speed | 1 | MHz | MHz | MHz | Megahertz (MHz) is the processor clock speed, how many instruction cycles per second a processor can perform. | |||||||||
| Operating System | 2 | Text | Text | Text | Identify what operating system is loaded on the server system. | |||||||||
| 1.1.5.1.3 | Database Servers | These servers manage the database that is stored in that server using the Structured Query Language (SQL) database management system. A client request is sent in the form of an SQL query to the server. That server in turn searches through the database for the requested information and sends the results to the client. | ||||||||||||
| Processor Type (data, signal, other) | Text | Text | Text | Description of the processor used in the server, including manufacturer, version number, etc. | ||||||||||
| Weight | 3 | lbs | lbs | lbs | Physical weight of the item. | |||||||||
| Length | 3 | inches | inches | inches | The length of the item. |
Width 3 inches inches inches The width of the item.
Depth 3 inches inches inches The depth of the item.
Performance (Throughput) 1 FLOPS Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
| The amount of useful work accomplished by a computer system compared to the time or resources inFloating Point Operations Per Second (FLOPS) | ||||||||||||||
| Memory Capacity | 1 | Gigabytes (GB) | Gigabytes (GB) | Gigabytes (GB) | How many Gigabytes (GB) of Random Access Memory (RAM) is installed on each individual server system? | |||||||||
| Data Rate | 1 | Mega bits per second | Mega bits per second | Mega bytes per second | The speed at which information is transferred through a communications or computing medium; measured in bytes per second. | |||||||||
| # Chips | ||||||||||||||
| per System | 2 | Chips per System | Chips per System | Chips per System | Total number of processors (chips) integrated into each individual server system (e.g. two quad-core processors = 2 chips) | |||||||||
| # Threads/Core | ||||||||||||||
| per System | 2 | Threads per Core | Threads per Core | Threads per Core | The total number of threads each core can run simultaneously. (A thread is an application process that is run by the processor. Multi-thread processors can run multiple threads at once without queuing.) | |||||||||
| Clock Speed | 1 | MHz | MHz | MHz | Megahertz (MHz) is the processor clock speed, how many instruction cycles per second a processor can perform. | |||||||||
| Operating System | 2 | Text | Text | Text | Identify what operating system is loaded on the server system. | |||||||||
| 1.1.5.1.4 | Other Servers | Any servers providing functions other than for web connections, applications or database. | ||||||||||||
| Processor Type (data, signal, other) | Text | Text | Text | Description of the processor used in the server, including manufacturer, version number, etc. | ||||||||||
| Weight | 3 | lbs | lbs | lbs | Physical weight of the item. | |||||||||
| Length | 3 | inches | inches | inches | The length of the item. |
Width 3 inches inches inches The width of the item.
Depth 3 inches inches inches The depth of the item.
Performance (Throughput) 1 FLOPS Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
| The amount of useful work accomplished by a computer system compared to the time or resources inFloating Point Operations Per Second (FLOPS) | ||||||||||||||
| Memory Capacity | 1 | Gigabytes (GB) | Gigabytes (GB) | Gigabytes (GB) | How many Gigabytes (GB) of Random Access Memory (RAM) is installed on each individual server system? | |||||||||
| Data Rate | 1 | Mega bits per second | Mega bits per second | Mega bytes per second | The speed at which information is transferred through a communications or computing medium; measured in bytes per second. | |||||||||
| # Chips | ||||||||||||||
| per System | 2 | Chips per System | Chips per System | Chips per System | Total number of processors (chips) integrated into each individual server system (e.g. two quad-core processors = 2 chips) | |||||||||
| # Threads/Core | ||||||||||||||
| per System | 2 | Threads per Core | Threads per Core | Threads per Core | The total number of threads each core can run simultaneously. (A thread is an application process that is run by the processor. Multi-thread processors can run multiple threads at once without queuing.) | |||||||||
| Clock Speed | 1 | MHz | MHz | MHz | Megahertz (MHz) is the processor clock speed, how many instruction cycles per second a processor can perform. | |||||||||
| Operating System | 2 | Text | Text | Text | Identify what operating system is loaded on the server system. | |||||||||
| 1.1.5.2 | Data Storage | Data storage is a general term for archiving data in electromagnetic or other forms for use by a computer or device. Different types of data storage play different roles in a computing environment. In addition to forms of hard data storage, there are now new options for remote data storage, such as cloud computing, that can revolutionize the ways that users access data. | ||||||||||||
| Storage Capacity | 1 | Terabytes | Count | Count | Specify 0,1,3,4,5,6. In computer storage, the level of configuration of striping, mirroring, or parity to create large readable data stores from multiple general purpose computer hard disk drives. | |||||||||
| RAID Level | 1 | List | List | List | The output unit that gives a visual representation of the data | |||||||||
| 1.1.5.3 | Workstations | A workstation (WS) is a computer dedicated to a user or group of users engaged in business or professional work. It includes one or more high resolution displays and a faster processor than a personal computer (PC). A workstation also has greater multitasking capability because of additional random access memory (RAM), drives and drive capacity. A workstation may also have a higher-speed graphics adapters and more connected peripherals. The term workstation also has been used to reference a PC or mainframe terminal. These workstations may share network resources with one or more large client computers and network servers. | ||||||||||||
| Performance | 1 | FLOPS | Text | Text | The type of WS. | |||||||||
| Clock Speed | 1 | MHz | Text | Text | Description of the data storage hardware. | |||||||||
| Memory - RAM | 1 | Megabytes | Text | Text | Then environment to which the Hardware is dedicated. Examples are OE, COOP, or NPE. | |||||||||
| 1.1.5.4 | Communications Hardware (HW) | The devices and connections of a communications network that connect the communication circuit between the data source and destination (the Data Terminal Equipment or DTE). A modem is the most common kind of Data Communications Equipment (DCE). | ||||||||||||
| 1.1.5.4.1 | Wide-Area Gateways (Server) | In telecommunications networking, a residential gateway allows the connection of a Local-Area Network (LAN) to a Wide-Area Network (WAN). The WAN can be a larger computer network (such as a municipal WAN that provides connectivity to the residences within the municipality), or the Internet. | ||||||||||||
| Processor Type (data, signal, other) | Text | Text | Text | Description of the processor used in the server, including manufacturer, version number, etc. | ||||||||||
| Weight | 3 | lbs | lbs | lbs | Physical weight of the item. | |||||||||
| Length | 3 | inches | inches | inches | The length of the item. |
Width 3 inches inches inches The width of the item.
Depth 3 inches inches inches The depth of the item.
Performance (Throughput) 1 FLOPS Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
| The amount of useful work accomplished by a computer system compared to the time or resources inFloating Point Operations Per Second (FLOPS) | ||||||||||||||
| Memory Capacity | 1 | Gigabytes (GB) | Gigabytes (GB) | Gigabytes (GB) | How many Gigabytes (GB) of Random Access Memory (RAM) is installed on each individual server system? | |||||||||
| Data Rate | 1 | Mega bits per second | Mega bits per second | Mega bytes per second | The speed at which information is transferred through a communications or computing medium; measured in bytes per second. | |||||||||
| # Chips | ||||||||||||||
| per System | 2 | Chips per System | Chips per System | Chips per System | Total number of processors (chips) integrated into each individual server system (e.g. two quad-core processors = 2 chips) | |||||||||
| # Threads/Core | ||||||||||||||
| per System | 2 | Threads per Core | Threads per Core | Threads per Core | The total number of threads each core can run simultaneously. (A thread is an application process that is run by the processor. Multi-thread processors can run multiple threads at once without queuing.) | |||||||||
| Clock Speed | 1 | MHz | MHz | MHz | Megahertz (MHz) is the processor clock speed, how many instruction cycles per second a processor can perform. | |||||||||
| Operating System | 2 | Text | Text | Text | Identify what operating system is loaded on the server system. | |||||||||
| 1.1.5.4.2 | WAN | A computer network that spans a relatively large geographical area. Typically, a WAN consists of two or more LANs. | ||||||||||||
| WAN Devices (VPN, Point to Point, Frame Relay, Other) | 1 | List | Text | Text | The name of the manufacturer. | |||||||||
| Bandwidth | 1 | Gigabits Per Second | Text | Text | The type of WAN (if applicable). | |||||||||
| Geographic Description | 2 | Text | Text | Text | Description of the data storage hardware. | |||||||||
| 1.1.5.4.3 | LAN | |||||||||||||
| Nodes | 1 | Count | Text | Text | The name of the manufacturer. | |||||||||
| Geographic Description | 1 | Text | Text | Text | The type of LAN (if applicable). | |||||||||
| 1.1.5.4.4 | Modems and Switches | A modem is a device or program that enables a computer to transmit data over, for example, telephone or cable lines. Computer information is stored digitally, whereas information transmitted over telephone lines is transmitted in the form of analog waves. A modem converts between these two forms. A switch is used to network multiple computers together. Switches made for the consumer market are typically small, flat boxes with 4 to 8 Ethernet ports. These ports can connect to computers, cable or DSL modems, and other switches. High-end switches can have more than 50 ports and often are rack mounted. | ||||||||||||
| Number of Interfaces | 1 | Quantity | Quantity | Quantity | A shared boundary between two functional units, defined by specific attributes, such as functional characteristics, common physical interconnection characteristics, and signal characteristics. Examples include: 1553 bus, Ethernet, RF, ARINC-429 | |||||||||
| Throughput | 1 | Bits per second | Bits per second | Bits per second | The number of bits, characters, or blocks passing through a data communication system, or portion of that system. Note: throughput is expressed in data units per period of time. | |||||||||
| Switch Type | 1 | Text | Text | Text | Ethernet switches could be Modular (allows for expansion modules), or Fixed Configuration which can include Unmanaged switches, Smart switches, or Fully Managed switches. The Modular switch can expand for application specific mudules such as Firewalls or Wireless modules. The Fixed Configuration has a fixed number of ports, and typically does not allow for expansion. The Fully Managed switches allow for the greatest control over the network, and typically can support L2 switching and L3 IP routing. The Unmanaged switches typically provide for only a basic layer 2 switching. The Smart switches can provide some management and security benefits over the Unmanaged switches. | |||||||||
| Power Over Internet (PoE) | 2 | PoE facilitates powering a device over the same cable as the data traffic, such as s an IP phone or a Wireless Access Point. | ||||||||||||
| Standard Ethernet Ports | 2 | Standard Ethernet Ports typically come in Fixed Configurations of switches, with Port configuration quanitities typically at either 5, 8, 10, 16, 24, 28, 48, or 52. | ||||||||||||
| Additional GbE Ports | 2 | GbE Ports can be added to networks using Modular Ethernet switches. The quantity of desired additional ports can be added based on using various configurations of switches added to the network. | ||||||||||||
| SFP+ Dedicated Ports | 3 | Small Form-Factor Pluggable Plus (SFP+) allows for data transfer at around 10 Gigabits per Second (10 Gb/s) or higher, as compared with SFP at around 5 Gb/s. Dedicated ports are used solely for a single server hosting a single IP address (vice a Port linked to a server which will host multiple website domains in a shared hosting environment). | ||||||||||||
| SFP Combo Ports | 3 | SPF allows for data transfer at rates of around 5 Gb/s. This combo port is typically shared between the SFP and the Copper Port. | ||||||||||||
| RJ45 Combo Ports | 3 | RJ45 are standard Ethernet Ports which utilize CAT 5 or CAT 6 cables. There are RJ45 Combo ports which have both the RJ45 connecter(s) and Universial Serial Bus (USB) connector(s). | ||||||||||||
| QSFP+ Dedicated Ports | 3 | Quad Small Form-Factor Pluggable Plus (QSFP+) has four port connections. | ||||||||||||
| Switch Fabric Capacity | 3 | Switch Fabric Capacity is sometimes referenced as Bandwidth, this reflects the maximum amount of network traffic a switch can handle at the same time. An example for a 24-port switch, and each port has a 2 Gbps, the Switch Fabric Capacity would be 48 Gbp/s. | ||||||||||||
| Forwarding Rate | 3 | The Forwarding Rate is typically half of the Bandwidth since this reflects the destination (and Bandwidth is the aggregate of the transmitting destination and the incoming data received). | ||||||||||||
| CPU Memory | 2 | Mb | Mb | Mb | The amount of application and data storage available on a computer, typically measured in Megabits (Mb) or Terabits (Tb). | |||||||||
| Flash Memory | 3 | Mb | Mb | Mb | The amount of data storage available on a computer, typically measured in Megabits (Mb) or Terabits (Tb). | |||||||||
| Buffer | 3 | A region of temporary memory storage while it is being transferred (sometimes a CPU Random Access Memory or RAM can be used). | ||||||||||||
| 1.1.5.4.5 | Crypto (Security HW) | |||||||||||||
| Weight | 2 | Pounds | Pounds | Pounds | Physical weight of the item. | |||||||||
| Length | 2 | Inches | Inches | Inches | The length of the item. |
Width 2 Inches Inches Inches The width of the item.
Depth 2 Inches Inches Inches The depth of the item.
| Number of Interfaces | 1 | Quantity | Quantity | Quantity | A shared boundary between two functional units, defined by specific attributes, such as functional characteristics, common physical interconnection characteristics, and signal characteristics. Examples include: 1553 bus, Ethernet, RF, ARINC-429 | ||
| Data Rate | 1 | Mega bits per second | Mega bits per second | Mega bits per second | The speed at which information is transferred through a communications or computing medium; measured in bytes per second. | ||
| Encryption Type | 1 | Text | Text | Text | Specify Encryption Type. Examples include Wired Equivalent Privacy (WEP), Wi-Fi Protected Access (WPA), WPA2, | ||
| Encryption Strength | 1 | Bits | Bits | Bits | Bits of the key in a cryptographic algorithm | ||
| FIPS Certification Level | 1 | List | List | List | Four levels of security as defined by Federal Information Processing Standard (FIPS) Publication 140-2. Ranked lowest (1) - highest (4) | ||
| Design Reuse | 2 | List | List | List | Choice List: 1) New Design; 2) Modified Design; 3) Complete Reuse | ||
| 1.1.5.4.6 | Other Communications HW | ||||||
| Number of Interfaces | 1 | Quantity | Quantity | Quantity | A shared boundary between two functional units, defined by specific attributes, such as functional characteristics, common physical interconnection characteristics, and signal characteristics. Examples include: 1553 bus, Ethernet, RF, ARINC-429 | ||
| Data Rate | 1 | Mega bits per second | Mega bits per second | Mega bits per second | The speed at which information is transferred through a communications or computing medium; measured in bytes per second. | ||
| 1.1.5.5 | Peripheral Devices | A peripheral device is an internal or external device that connects directly to a computer but does not contribute to the computer's primary function, such as computing. It helps end users access and use the functionalities of a computer. | |||||
| Description | 1 | Text | Text | Text | Description of the data storage hardware. | ||
| 1.1.5.6 | Other HW | Other communications HW which is not defined in previous Work Breakdown Structure (WBS) elements. | |||||
| Description | 1 | Text | Text | Text | The name of the manufacturer. | ||
| 1.1.5.8 | Infrastructure as a Service | (If Dev Infrastructure is Service-based vs procured) | |||||
| Software System Type (DBMS, ERP, Other) | 1 | List | |||||
| Total Number of Developers | 1 | Quantity | |||||
| Number of Concurrent Developers | 2 | Quantity | |||||
| Throughput (TPH) | 1 | Quantity | |||||
| Response time (seconds) | 1 | Seconds | |||||
| Think time (seconds) | 2 | Seconds | |||||
| System Availability (0-100%) | 1 | Percentage | |||||
| IT Security level Requirements (FIPS 1-4) | 2 | List | |||||
| System Complexity (Low, Medium High) | 1 | List | |||||
| Network Speed (T1, DSL, Modem, etc…) | 1 | Description |
Bowman, Keith WDC Tecolote: Bowman, Keith WDC Tecolote:
What is the maximum network speed for processing user transactions (e.g. 3 T1 lines, etc.)
| 1.5.3 | Test Suite Hardware (HW) | HW suite utilized for developing and configuring an AIS. | |||||
| 1.5.3.1 | Servers | Roll-Up of servers defined below. | |||||
| 1.5.3.1.1 | Web Servers | Web servers provide access to the Internet through the HyperText Transfer Protocol (HTTP). Files in a web server use HyperText Markup Language (HTML) to display content on web browsers. A web server usually receives requests from a web browser and sends back the requested HTML file and related graphic files. | |||||
| Processor Type (data, signal, other) | Text | Text | Text | Description of the processor used in the server, including manufacturer, version number, etc. | |||
| Weight | 3 | lbs | lbs | lbs | Physical weight of the item. | ||
| Length | 3 | inches | inches | inches | The length of the item. |
Width 3 inches inches inches The width of the item.
Depth 3 inches inches inches The depth of the item.
Performance (Throughput) 1 FLOPS Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
| The amount of useful work accomplished by a computer system compared to the time or resources inFloating Point Operations Per Second (FLOPS) | ||||||||||||||
| Memory Capacity | 1 | Gigabytes (GB) | Gigabytes (GB) | Gigabytes (GB) | How many Gigabytes (GB) of Random Access Memory (RAM) is installed on each individual server system? | |||||||||
| Data Rate | 1 | Mega bits per second | Mega bits per second | Mega bytes per second | The speed at which information is transferred through a communications or computing medium; measured in bytes per second. | |||||||||
| # Chips | ||||||||||||||
| per System | 2 | Chips per System | Chips per System | Chips per System | Total number of processors (chips) integrated into each individual server system (e.g. two quad-core processors = 2 chips) | |||||||||
| # Threads/Core | ||||||||||||||
| per System | 2 | Threads per Core | Threads per Core | Threads per Core | The total number of threads each core can run simultaneously. (A thread is an application process that is run by the processor. Multi-thread processors can run multiple threads at once without queuing.) | |||||||||
| Clock Speed | 1 | MHz | MHz | MHz | Megahertz (MHz) is the processor clock speed, how many instruction cycles per second a processor can perform. | |||||||||
| Operating System | 2 | Text | Text | Text | Identify what operating system is loaded on the server system. | |||||||||
| 1.5.3.1.2 | Application Servers | Application servers are dedicated to running certain software applications. The application server often serves to connect database servers with the end-user, thus acting as a kind of "middleware" that releases stored information requested by said user. The server is usually responsible for properly decoding and recoding data and providing security over connections. |
McDowell, Jeff HSV Tecolote: C.4.2.1 Airframe. This element comprises the structural framework that provides the aerodynamic shape, mounting surfaces and environmental protection for the air vehicle components, which are not directly applicable to other specific Level 3 air vehicle subsystems.
Includes, for example:
a. Wings and fins that provide aerodynamic flight control in response to electro-mechanical signals and are attached to the air vehicle body
b. Structural body assemblies including the structure, fuel tanks that integral with the structure, covers, skins, adhesives, and fairings not directly applicable to any other Level 3 air vehicle subsystem
c. Protection devices for stressing environmental conditions such as thermal protection system or rain erosion that are not directly applicable to other Level 3 air vehicle subsystems
| Processor Type (data, signal, other) | Text | Text | Text | Description of the processor used in the server, including manufacturer, version number, etc. | |
| Weight | 3 | lbs | lbs | lbs | Physical weight of the item. |
| Length | 3 | inches | inches | inches | The length of the item. |
Width 3 inches inches inches The width of the item.
Depth 3 inches inches inches The depth of the item.
Performance (Throughput) 1 FLOPS Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
FLOPS
Bowman, Keith WDC Tecolote: Floating Point Operations per Second
| The amount of useful work accomplished by a computer system compared to the time or resources inFloating Point Operations Per Second (FLOPS) | ||||||||||||||
| Memory Capacity | 1 | Gigabytes (GB) | Gigabytes (GB) | Gigabytes (GB) | How many Gigabytes (GB) of Random Access Memory (RAM) is installed on each individual server system? | |||||||||
| Data Rate | 1 | Mega bits per second | Mega bits per second | Mega bytes per second | The speed at which information is transferred through a communications or computing medium; measured in bytes per second. | |||||||||
| # Chips | ||||||||||||||
| per System | 2 | Chips per System | Chips per System | Chips per System | Total number of processors (chips) integrated into each individual server system (e.g. two quad-core processors = 2 chips) | |||||||||
| # Threads/Core |
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 .