Att_21_-_STEP.pdf

PDF 301 KB Posted

Attached to
Global Security Engineering & Supply Chain
Solicitation number
SAQMMA17R0168
Issued by

About this file

Att 21 - STEP

View the file

Other files

File Type Posted
SAQMMA17R0168_Amendment_0002.pdf PDF
Att_31_-_Evaluation_factors...0002.docx DOCX document
Att_40_-_Summary_of_Prof_Emp_Benefits.docx DOCX document
SAQMMA17R0168_Amendment_0001.pdf PDF
Att_08_-_Catalog_items_0001.xlsx XLSX spreadsheet
Att_28_-_Addl_instructions_conditions...0001.docx DOCX document
Questions_and_Answers_--_SAQMMA17R0168.docx DOCX document
Att_32_-_Projected_Annual_Catalog_Qty_0001.xlsx XLSX spreadsheet
Att_31_-_Evaluation_factors...0001.docx DOCX document
Att_14_-_Current_SCM_Facilities.pdf PDF
Att_10_-_OY3_PRs.xlsx XLSX spreadsheet
Att_06_-_PR_Approval_Process.pdf PDF
Att_13_-_PRs_by_Shipping_Method.xlsx XLSX spreadsheet
Att_15_-_CRP_Security_Procedures.pdf PDF
Att_18_-_Repairable_Items.xlsx XLSX spreadsheet
Att_33_-_Scenario_1,_Field_Support.pdf PDF
Att_05_-_TDB_Projected_FY18_Projects.pdf PDF
Att_03_-_ST_Organization.pdf PDF
Att_01_-_Performance_Work_Statement_2017-12-19.pdf PDF
Att_23_-_GSA_Container_SOP.pdf PDF
Att_11_-_OY4_PRs.xlsx XLSX spreadsheet
Att_20_-_ACA_CCR_Facilities.pdf PDF
Att_25_-_RMC_Workload.pdf PDF
Att_35_-_Scenario_3,_Rapid_Response.pdf PDF
Att_12_-_Physical_Addresses.xlsx XLSX spreadsheet
Att_34_-_Scenario_2,_Security_Engineering.pdf PDF
Att_17_-_GOCM_Inventory.xlsx XLSX spreadsheet
Att_09_-_OY2_PRs.xlsx XLSX spreadsheet
Att_31_-__Evaluation_factors_for_award.pdf PDF
Request_for_Proposals_SAQMMA17R0168.pdf PDF
Att_22_-_Secure_Key_Systems_SOP.pdf PDF
Att_07_-_HOV_By_Fullfillment.pdf PDF
Att_28_-_Addl_Instructions,_Conditions,_Notices.pdf PDF
Att_24_-_Lock_and_Core_SOP.pdf PDF
Att_32_-_Projected_Annual_Catalog_Order_Quantities.xlsx XLSX spreadsheet
Att_30_-_Service_Level_Agreement_Template.docx DOCX document
Att_02_-_Bidders_DD_Form_254_with_supplements.pdf PDF
Att_36_-_Equipment_List_for_Scenario_3.pdf PDF
Att_08_-_Catalog_items.xlsx XLSX spreadsheet
Att_04_-_Historical_Order_Volume.pdf PDF
Att_27_-_Acctng_and_Approp_Data.pdf PDF
Att_19_-_ACA_Facilities.pdf PDF
Att_37_-_Scenario_4,_La_Paz_TSU.pdf PDF
Att_29_-_Past_Performance_Customer_Satisfaction_Survey.docx DOCX document
Att_26_-_Consolidated_Warehouse.pdf PDF
Att_39_-_La_Paz_Post_Information_for_Scenario_4.pdf PDF
SAQMMA17R0168_Industry_Day_Q&As_Final.pdf PDF
Industry_Day_Brief_Final.pdf PDF
PostEventIndustryDayCompanyList.pdf PDF
IndustryDaySignInSheet.docx DOCX document
Show all 50

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

Customer Technology Requirements (CTR): The requirements of the technology or product. This should only contain requirements that can be measured in an evaluation. Installation requirements, such as “must be installed in conduit” is not a technology requirement and shall not be listed. The requirements document may have desired features for use in evaluation.

Concept of Operations (CONOPS) with Technology Needs Assessment (TNA): The TNA is intended to support the management decision-making process in establishing the need for changes in current technology (i.e., whether new technology should be evaluated), outline current customer needs, describe options for new technology and their respective benefits, and establish potential future needs. How the technology will be used with the Department of State (DOS). Include flowcharts or diagrams if useful.

Pilot Project Plan (Beta): This plan shall reflect how the pilot project will be conducted in the field (locations, testing duration, resources required, etc.). It shall include products required, cost estimates, and field labor responsibilities . This portion includes the Pilot Project period and the testing plan.

Product Evaluation (Alpha): Each product selected will be evaluated against the requirements and return on investment .

Product Comparison and Cost Analysis: As a result of market research (internet search, tradeshows, etc.), this will compare 3-5 COTS products that will be evaluated (alpha test). If the requirement is unique to DoS and market research does not yield a COTS product, a Request for Information (RFI) may be required. An RFI is a formal process through AQM, Acquisitions, to publish requirements on FedBizOps so vendors can submit their requests to evaluate their products. A cost analysis of the solution will be performed that includes the equipment, installation, maintenance, and licensing costs over the life cycle. This cost analysis will also compare the cost for the present solution.

Technical Bulletin (TB): If there is an issue with a product (defect, warranty issue, wiring issue, etc.), a technical bulletin is sent out to the field. This bulletins require review and input from various DS/ST branches. These documents are usually later included into a DDP.

New Product Announcements (NPA): Once a product is approved or a replacement product is found for an obsolete product, a NPA is sent out to the field (with DS/STO/OSB approval)

Deployment Documentation Package (DDP): The DDP is the guidance to the field on survey, installation, maintenance and user guidance on the product. This document includes policy guidance on the design and utilization of the product in the DoS environment. Major revisions of this document require review and input from multiple DS/ST branches. These documents form the basis for DS/ST training. Not all products need a DDP.

Completed Documentation is filed in TDB and only DDPs, NPAs, TB and MSBs are uploaded into the Equipment and Reference Library (EaRL). Only the latest document should appear in EaRL. Manufacturer’s documents shall also be uploaded into EaRL.

End of Life (EOL): Product/System Obsolescence shall be determined. If a product has reached EOL, then the process starts at the Product Evaluation (Alpha) until a new product is found to replace the obsolete product. If a system has reached EOL, then the process starts at the beginning to find a replacement system.

Tier 3 Technical Support: CMMS Work Orders assigned to TDB must be resolved within 7 working days.

Study Period Implementation Period Operations Period User

Requirements Definition

Phase

Concept Definition

Phase

System Specification

Phase

Acquisition Preparation

Phase

Source Selection

Phase

Development Phase

Verification Phase

Deployment Phase

Operations and Maintenance

Phase

De-activation

Phase

*EaRL documentation

DOS Request for Proposals No. SAQMMA17R0168, Attachment 21 DS/FSE/TDB – Security Technology Engineering Process

Deployment Documentatio n Package

DDP*

Technical Bulletin* or Mandatory

Service Bulletin*

New Product Announceme nts

NPA*

Pilot Project Plan

(Beta) Document

TDB Security Technology Engineering Deliverables

Concept of Operations

CONOPS with Technology

Needs Assessment

Customer Technology

Requirements

CTR

Product Comparison Document and Cost Analysis

(possible RFI)

Product Evaluation

(Alpha) Document

Beta Test Report and

Decision Memo

Customer Technology

Requirements

CTR

Concept of Operations

CONOPS

Market Survey

Product Comparison

PCT

Product Evaluation

(Alpha)

PET

Final Documentation and Catalog Number Creation

Tier 3 Technical Support

End of Life

EOL

Technology Needs

Assessment

TNA

TDB Security Technology Engineering Process

Technology Brainstorm

Pilot Project Plan

(Beta)

PPP

New Products Existing Products

Projects

Gate/

STEP

Review

Gate/

STEP

Review

Gate/

STEP

Review

Gate/

STEP

Review

Gate/

STEP

Review

Gate/

STEP

Review

Beta Test Report and Decision Memo: This documents the installation, results and findings from the Beta test. After the beta pilot project has completed field testing usually 90 day period, the decision memo formally documents approval or denial of the product or equipment.

Mandatory Service Bulletin (MSB): If there is a safety or major vulnerability issue with a product, a mandatory service bulletin is sent out to the field. This bulletins require review and input from various DS/ST branches and usually requires immediate action from field elements. These documents are usually later included into a DDP.

File details come from the government source that posted it.