WINDS_PWS_Nov_21_2018.docx
DOCX document 98 KB Posted
- Attached to
- WINDS Follow-On Project
- Solicitation number
- FA8224-19-Q-6695
View the file
Other files
| File | Type | Posted |
|---|---|---|
| WINDS_FO_CDRL_A002.pdf | ||
| Solicitation.pdf | ||
| WINDS_FO_CDRL_A012.pdf | ||
| WINDS_FO_CDRL_A014.pdf | ||
| WINDS_FO_CDRL_A009.pdf | ||
| WINDS_FO_CDRL_A001.pdf | ||
| WINDS_FO_CDRL_A013.pdf | ||
| WINDS_FO_CDRL_A006.pdf | ||
| WINDS_FO_CDRL_A007.pdf | ||
| WINDS_FO_CDRL_A004.pdf | ||
| WINDS_FO_CDRL_A015.pdf | ||
| WINDS_FO_CDRL_A021.pdf | ||
| WINDS_FO_CDRL_A016.pdf | ||
| WINDS_FO_CDRL_A019.pdf | ||
| WINDS_FO_CDRL_A017.pdf | ||
| WINDS_FO_CDRL_A005.pdf | ||
| WINDS_FO_CDRL_A008.pdf | ||
| WINDS_FO_CDRL_A020.pdf | ||
| WINDS_FO_CDRL_A010.pdf | ||
| WINDS_FO_CDRL_A018.pdf | ||
| WINDS_FO_CDRL_A011.pdf | ||
| WINDS_FO_CDRL_A003.pdf |
Show all 22
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
PERFORMANCE-BASED WORK STATEMENT
FOR
Weather Information Network Display System (WINDS)
FOR THE
516th SOFTWARE MAINTENANCE SQUADRON
(516 SMXS/MXDPF)
Hill AFB, Utah
21 Nov 2018
TABLE OF CONTENTS
SECTION 1 – DESCRIPTION OF SERVICES 3
SECTION 2 – SCOPE 3
SECTION 3 – BASIC SERVICES 4
SECTION 4 – REPORTS 13
SECTION 4.1 – PROJECT PLAN 13
SECTION 4.2 – MONTHLY STATUS REPORT 14
SECTION 5 – SERVICE SUMMARY 15
SECTION 6 – GENERAL INFORMATION 16
SECTION 6.1 – SECURITY REQUIREMENS 16
SECTION 6.2 – QUALITY CONTROL 16
SECTION 6.3 – QUALITY CONTROL PROGRAM 16
SECTION 6.4 – MANPOWER REPORTING 17
SECTION 6.5 – TRAVEL 17
SECTION 7 – GOVERNMENT FURNISHED PROPERTY AND SERVICES 17
SECTION 7.2 – GOVERNMENT FURNISHED INFORMATION 17
SECTION 8 – DATA RIGHTS 18
APPENDIX A – ACRONYMNS AND ABBREVATIONS 19
APPENDIX B – TOOLS/DOCUMENTATION 20
APPENDIX C – Contract Data Requirement Lists (CDRLs) (DD Form 1423s) 21
1. Description of Services
1.1 The 309th SMXS MXDPF currently holds contract number FA8222-12-D-0013, utilizing a DESP III contract vehicle. Under open competition, KIHOMAC was awarded the WINDS replacement contract (FA8222-12-D-0013). The program and contractor have been successful through the Installation Readiness Review (IRR) milestone. On June 18, 2018 a manufacturing defect was discovered during integration of power supplies that were specified at WINDS Critical Design Review (CDR). It will take the power supply manufacturer several months to provide an analysis and resolution of the failure. Meanwhile, Test Readiness Review (TRR), Developmental Test & Evaluation (DT&E) and Functional and Physical Configuration Audit (FCA/PCA) milestones remain to complete the program. All DESP III contract POPs are mandated to terminate NLT 10 Jan, 2019. Due to the power supply issue, there will not be sufficient time for the contractor to complete all milestones/CDRLS and closeout the DESP III contract.
1.2 WINDS mission is to provide 24‐hours‐a‐day, 7‐days‐a‐week data collection to the Eastern Range (ER) operators and users. This data allows the AF and its launch customers to successfully complete their missions under a variety of weather conditions at the CCAFS (Cape Canaveral Air Force Station) and KSC (Kennedy Space Center). To support this requirement, the WINDS replacement is developing side by side with the existing WINDS system. A follow on contract is required for new sensors to be moved to the existing location; otherwise, the system is unusable with the current configuration.
This service is a bridge contract for the existing contractor (KIHOMAC) to continue and complete the current DESP III FA8222-12-D-0013 contract and follow on work.
2. Scope
Sections 2.1 to 2.4 to continue the current the DESP III contract.
2.1 The scope of this effort is development, installation and test of an Eastern Range program. The WINDS replacement includes full system replacement according to the WINDS Technical Requirements Document #15-004, Revision # 4.0, and Eastern Range Instrumentation Handbook (WINDS Section). In addition, replacement of towers and instrumentation of towers 003, 511, 512 and 513 are to be included in program scope. The contractor skills shall include Electrical Engineering, Hardware Engineering, System Engineering, Software and Test Engineering. The contractor shall have expertise in the development of WINDS Operation and Maintenance (O&M) manuals, as well as CAD proficiency. These skills are in support of design and installation of the WINDS system, and associated project milestone deliverables. The contractor shall accomplish a Function and Interface (FI) redesign, prototype fabrication, test, delivery and install. The WINDS replacement shall meet all legacy specifications, performance, and operational requirements. The contractor shall provide; traceability to the Test Requirement Document (TRD), new Technical Orders (TO), accurate red-line TO changes on existing TOs and user manuals. Monthly status reports addressing technical progress/concerns, schedule and cost status shall be provided. The Contractor shall build and deliver FI prototypes which will meet or exceed system requirements. The WINDS system shall pass testing and performance requirements. The contractor shall design, document, fabricate, install and test the FI prototypes and associated hardware. A total of 32 weather instrumented towers, 29 towers from current WINDS system, and the addition of towers 511, 512 and 513. Tower 0003 physical structure shall be replaced with a new tilt down tower that does not impede wind measurements.
2.2 Replacement of the WINDS system includes: a site survey(s), replacement of towers 511, 512, 513 and 0003. Design and installation of required network infrastructure, design and installation of weather sensors to towers and poles, integration of new sensors to server database, server system design and integration (Processing & Display), WINDS interface to REIN, ERDAS and MIDDS, test of hardware & software, and updates/development of the technical data package used by Operations, Maintenance and Sustainment (OM&S) personnel.
2.3 The contractor shall provide a technical writer to perform technical writing activities which include writing and editing O&M, operator and other required manuals for the WINDS system. In addition to the 32 WINDS towers, there are five external towers operated by the launch customers near their respective launch pads. These towers will not be upgraded, but the data from these towers shall be collected and integrated into the WINDS system.
2.4 The contractor shall provide services including: removal/repositioning of the sensors equipment, removal of tower 0003, documentation of the new sensor location and disposition of legacy equipment.
2.5 This is a bridge contract for 12 months.
3. Basic Services
The Contractor shall provide engineering and technical services for the efforts described below. The Contractor shall coordinate with the government Technical Program Manager (TPM) to set a schedule for completion of assigned tasks of the full system.
The contractor shall design, develop, test, integrate and install a full WINDS system. Support may be required outside of normal duty hours to support launch activity, significant weather events or other significant occurrences involving integration and testing actions.
The skills necessary to accomplish assigned tasks may change substantially during the term of the contract. Changes in the assigned tasks may occur on short notice depending on changes in customer requirements and priorities. The contractor shall have the capability to adapt its skills to the assigned work.
3.1 Program Management
The Contractor shall establish and maintain a formal organization to manage this contract and subcontracts. The Contractor shall designate a Program Manager who has responsibility for all aspects of this contract. The Contractor shall organize, provide for, coordinate, and control the program activities to ensure compliance with the contract requirements and the timely delivery of the required products.
3.1.1 Integrated Master Schedule (IMS)
The Contractor shall deliver an Integrated Master Schedule (IMS) to track and report project activities that includes, at a minimum, remaining milestones, reviews and follow on (including those events described in Section 3.1.17), as well as completion of DD250, planned meetings, site-surveys, CDRL deliveries, activities related to installation, integration, and DT&E. The Contractor shall provide a critical path analysis on the project schedule with each IMS delivery. The Contractor shall include in the IMS major subcontractor activities and deliverable schedules (CDRL A007).
When developing the IMS, the Contractor shall take into account there may be on average 11 Working Days per month, excluding holidays, when site operations may limit or prevent their access to the site.
The Contractor shall coordinate with SMC, 1 ROPS, 45WS, RGNext and KSC to utilize WINDS OM&S contractor scheduling when scheduling site operations.
3.1.2 Hardware and Any Associated Software
The Contractor shall redesign the WINDS Replacement System as follows:
a. The Contractor shall implement current technology to replace the WINDS.
b. The contractor shall accomplish an FI redesign, prototype fabrication, test, delivery and install effort by redesigning the WINDS to meet requirements documents (MIL-STD-38784, MIL-PRF-38807C, MIL-DTL-87929C, MIL-STD-100C, WINDS ER Handbook, WINDS TRD, WINDS COMP).
c. Upgrade of 29 instrumented meteorological towers at CCAFS, NASA KSC, and remote sites surrounding CCAFS and KSC.
d. Data incorporation of five external towers operated by the launch customers near their respective launch pads. These towers will not be upgraded, but the data from these towers shall be collected and integrated into the WINDS system.
e. The contractor shall replace existing tower 0003 with tilt-down functionality similar to tower 211, in addition to updating with new instrumentation.
f. Replacement of towers 511, 512 and 513. These towers shall have the same capability as the other 29 towers.
g. Modernize and customize WINDS Data Acquisition and Processing & Display, utilizing Tempest Universal Data Acquisition Server (DAS), Tempest Hydro-Met Analysis System, Tempest DCP Monitor and Tempest DCS Toolkit or equivalent. The Processing & Display produces the data for display on various monitors and TV screens for the weather forecasters.
h. If Special Test Equipment (STE) is required, the Contractor shall develop, test and deliver STE to test the form, fit, function, and interface of WINDS prototypes. The STE delivery shall include all associated hardware, test equipment, operating software, FI, Program Software (PS), all user manuals, operating instructions, SRD, TRDs, etc. The contractor shall develop and deliver a Software Requirements Specifications (SRS), Software Production Specification (SPS) and, Software Version Description (SVD) for the STE. The contractor shall deliver applicable data for this work effort according to 3.1.17 to 3.1.23.
3.1.3 Engineering Data
The contractor shall develop/produce/maintain a Technical Data Package (TDP) (CDRL A008) that accurately depicts the final product of any item developed under this effort. The TDP shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product, without additional design engineering effort or recourse to the original design activity. The contractor shall provide sufficient test and performance data to allow re-qualification and procurement of suitable future replacement WINDS and all associated STE. The engineering data includes but is not limited to the following:
a. Design requirements specification for new WINDS, including towers 511, 512 and 513
b. Test criteria of the full system
c. Production level drawings and specifications that accurately depict the final products
d. STE and all associated hardware, if applicable
e. The contractor shall provide TRDs for any new item developed and tested under this effort for WINDS
3.1.4 Engineering Data Guidance Conference
The Contractor shall support and co-chair a Guidance Conference for engineering data within 45 working days after contract award. The Conference shall be convened by teleconference and on a date agreed upon by the Government Program Manager and the Contractor. The Guidance Conference shall be held, when possible, in conjunction with other meetings and conferences. The Contractor shall prepare an agenda and record the minutes of the WINDS Guidance conference (CDRL A002 & A004). The contractor shall address, discuss, and provide status on the following:
a. Understanding of all Contract Data Requirements List (CDRL) requirements, applicable Data Item Descriptions (DID), specifications and standards.
b. TDP review requirements and schedules.
c. TDP delivery requirements and schedules.
d. Contractor’s drafting practices/Test Procedures/test result/TDP drawing formats.
e. The Contractor’s quality assurance procedures relating to TDP documents, including quality control of subcontractor and vendor data.
f. Digital TDP deliverables.
g. The role of subcontractors and vendors who may deliver TDP documents under this contract.
h. The Contractor’s configuration management system, including methods for releasing documents, approving documents, and incorporating changes into documents.
i. Understanding of all tests results, including installation test, and Final Integration Acceptance Test.
3.1.5 In-Process Review (IPR) of the TDP
When data has reached the 35%/75% completion points, the Contractor shall electronically submit the TDP for IPR. The contractor shall host, support, and co-chair an IPR of the engineering drawings and associated lists and other documentation to be included in the TDP. The IPR shall be conducted only after the contractor's quality assurance personnel have completely reviewed the data and determined that data are of sufficient quality that government time will be effectively utilized during the review. IPR may be scheduled when data has reached the 35%/75% completion points and shall be held, when possible, in conjunction with other reviews (e.g., DT&E). The contractor shall notify the Government a minimum of 30 working days prior to the anticipated date of the completion point. The IPR shall focus on the contractor's progress in the preparation of the TDP. The contractor shall support and provide the necessary resources, e.g., meeting agenda, conference room, applicable data, minutes, and appropriate personnel available to answer any questions to perform the IPR effectively. The contractor shall correct all discrepancies identified in the IPR. All subcontractor/vendor data shall be made available for review. If the quantity of subcontractor/vendor data is of sufficient magnitude, the government may schedule a separate IPR at the subcontractor's/vendor's facility if required. Minutes shall include all briefing materials as an attachment.
3.1.6 Relationship of Contractor with Subcontractors/Vendors
The Contractor shall levy on sub-contractors and sub-vendors the same requirements for Technical Data Packages (TDPs) as are levied on them by this contract. This requirement shall apply to all tiers of sub-contractor/vendor levels associated with the program.
All work provided shall be accomplished within 5% of developed schedule and contain less than 10% defect density upon review. The Contractor shall have a proficient knowledge of tower installation, including customer towers and towers 511, 512 and 513. Tower 0003 structure replacement will require a civil site survey. The survey shall determine the location, the structural materials needed, level of effort, and estimated time to install. The contractor shall have experience with installation work at KSC and CCAFS.
3.1.7 Data Accession List (DAL)
All data developed under this task shall become property of the government. The contractor shall provide a DAL listing all data, hardware, and software developed by the contractor in accomplishment of the Basic contract. The contractor shall provide the government access to any of this data or software at the request of the government. The government's access to the contractor's data is not limited to that contained in the DAL, but is limited to that data and software developed under this task. (CDRL A016).
3.1.8 Test Plan, Test Procedures, and Test Report
Contractor shall develop and submit the Test Plan to be utilized in accordance with the approved IMS (CDRL A001) for Government approval. The Test Plan allows the Government to plan for the witnessing of selected testing. The Contractor shall provide the Test Procedures used to verify and validate the hardware, software, and STE (if applicable) final products. The Test Plan allows the Government to review the following assumptions: the test concept, objectives and requirements to be satisfied, test methods and responsible activities associated with the testing (CDRL A009, A010).
The Contractor shall deliver the test reports in accordance with the approved IMS. This test report allows the Government to verify that the format, function, and performance requirements for the new WINDS are met by the specific and discrete task requirements (CDRL A011).
3.1.9 Techniques Development
The contractor shall supply a development system to the 516th consisting of 1 set of tower instruments and all associated hardware and software at Hill AFB for test, validation, verification and inspection of the design concept. Limited software development/configuration due to Commercial Off The Shelf solution.
3.1.10 Application of Research
The contractor shall evaluate weather observing systems, sensors and weather forecasting technologies and design and develop the WINDS system, including towers 511, 512 and 513 to support Launch Range Facility weather operations. Design shall include but is not limited to automated quality control algorithms, concepts of deployment and operation and methods for data integration or display.
3.1.11 Prototype of Technology and Techniques
The contractor shall provide analytical, statistical and other appropriate techniques for the purpose of assessing the efficacy of system enhancements and training effectiveness.
The contractor shall develop training aids in a format and style appropriate for operational users to support DT&E Testing.
3.1.12 Technical Writing Services
The Contractor shall perform technical writing activities to include writing and editing O&M manuals, TOs and Software User Manual (SUM). All work provided shall be accomplished within 5% of developed schedule and contain less than 10% defect density upon review. The Contractor shall have a proficient knowledge of writing technical documents in a Launch Test Range environment. The contractor shall have a proficient knowledge in using Microsoft Word, FrameMaker, or other writing tools. The Contractor shall have a proficient knowledge of importing and manipulating drawings from CAD products such as Autocad, Altium and Solid Works.
Tasks shall include:
Prepare O&M Manuals, SUM, and TOs through 100% review (CDRL A020) Conduct and support O&M manual reviews to include Validation/Verification.
3.1.13 Computer Aided Drafting Services
The Contractor shall perform computer aided drafting activities to include the documentation of electronic and mechanical chassis drawings to the level defined by WINDSHIELD repository regulations. All work provided shall contain less than 10% defect density upon review and be accomplished within 5% of developed schedule milestones. The Contractor shall be proficient in the use of AutoCAD and AutoCAD Inventor. The Contractor shall be capable of learning other CAD software. The Contractor shall have a proficient knowledge of drafting in a Launch Test Range environment (CDRL A012).
Tasks may include:
· Prepare CAD drawings using AutoCAD
· Transform engineering conceptual drawings into three dimensional mechanical CAD drawings
· Transform engineering electronic drawings from hand drawn hard copy documents to CAD drawings
· Import engineering electronic drawings from other software drawing packages into AutoCAD
· Prepare Cable Drawings when necessary
· Prepare hardware assembly drawings and interconnect diagrams
· Conduct and support drawing review activities to include hardware to drawings review
3.1.14 Engineering Technician Services
The Contractor shall perform activities related to troubleshooting or installation of 32 instrumented meteorological towers at CCAFS, NASA KSC, and remote sites surrounding CCAFS and KSC. In addition, there are five external towers operated by the launch customers near their respective launch pads. Contractor shall have knowledge in soldering and cable manufacturing and the ability to troubleshoot problems in each activity.
Tasks may include:
· Manufacture of custom cables using contractor purchased materials
· Debug and repair of damaged or non-functioning tower cables (DMARC to sensor suite)
· Troubleshooting and installation
3.1.15 WINDS Engineering Services
The Contractor shall perform engineering services related to the design, development, integration and installation of the WINDS system, including customer towers and towers 511, 512 and 513. Tower 0003 structure replacement will require a civil site survey. The survey shall determine the location, the structural materials needed, level of effort, and estimated time to install. The contractor shall have experience with installation work at KSC and CCAFS.
The WINDS replacement system shall use communication (COMM) paths consisting of copper cables and/or fiber optic cables from the MOC to each tower or DEMARC. In addition, electrical power will be available at each tower or DEMARC. The contractor shall provide WINDS COMM hardware in accordance with “WINDS COMM Equipment.xlsx.” The COMM hardware will be installed and acceptance tested by the 516th SMXS.
All weather instrumentation sensors with the exception of tower 313 are to be installed at the same elevation as current sensors. Sensors are to be installed on booms adjacent to current sensors.
Tower 313 instrumentation sensors are to be installed on current booms, approximately ½ way between the tower and existing weather sensors. The new WINDS sensors will be moved to the correct position (end of boom) after the legacy equipment is removed following acceptance. Removal of legacy WINDS equipment is in scope of this effort.
Boom materials must meet CCAFS corrosion resistant standards, and not consist of cold galvanized materials.
All work tasks shall be accomplished within 5% of developed schedule milestones.
3.1.16 Data Gathering
The Contractor shall provide services related to the identification of information, tracking, and archiving the data necessary to complete the full system integration and test. Data shall be archived in the government designated area.
3.1.17 Product Reviews
The Contractor shall lead or participate in product reviews of assigned subsystems and the reviews of other subsystems. These reviews may include internal product (e.g. peer) and milestone reviews for test readiness, and product demonstration and acceptance activities.
The Contractor shall have sufficient expertise to accomplish the following system development activities (section 3.1.18 to 3.1.23)
The contractor shall work with Government engineers on the following tasks during Product Development and prepare deliverable items for Test Readiness Review below:
· Finalize CDRLs from PDR and CDR
· Build assigned subsystem with COTS hardware
· Develop software installation procedure for O&M manuals
· Product Indenture Report (PIR) (CDRL A018)
· Test/Inspection Report (A011)
· Type 1 and User Training (CDRL A019)
· Finalized Tower Installation Plan
· Final Information Assurance Certification and Accreditation (C&A) Package (CDRL A021)
· Final Technical Requirement Document (TRD)
· Final Spare Part List Report (CDRL A017)
3.1.18 Installation, integration and test
The contractor shall install all hardware and software for the WINDS system, including new towers 511, 512, 513, and 0003, and any hardware and/or software required to integrate customer owned tower data into the system.
The contractor shall install all hardware and software for the WINDS System.
The Contractor shall perform developmental testing to verify all allocated requirements are met.
The Contractor shall develop, update with project Integrated Product Team (IPT) comment resolution, and deliver Test Procedures and Reports.
The Contractor shall invite the Government to witness all formal verification & validation events, NLT 5 Working Days prior to start of each verification event.
The Contractor shall perform an operational check-out to validate performance of the modification.
The Contractor shall not change, modify, test, or interface with operational systems or facilities.
3.1.19 Developmental Test & Evaluation (DT&E)
The Contractor shall be the system subject matter expert to the government in a successful demonstration of the WINDS system at the deployed locations.
3.1.20 Functional Configuration Audit (FCA)
The Contractor shall be the system subject matter expert to the government in a scheduled Functional Configuration Audit to ensure that any system software and hardware developed functionally satisfies the TRD requirements at the conclusion of the product development activities.
3.1.21 Physical Configuration Audit (PCA)
The Contractor shall be the system subject matter expert to the government in a scheduled Physical Configuration Audit to ensure that any system hardware developed physically matches the associated technical data at the conclusion of the product development activities.
3.1.22 FDE/Operation Test & Evaluation (OT&E)
The Contractor shall be available as the system subject matter expert to the government for 30 days during Operational Acceptance and Test phase. The Contractor will aid in a successful demonstration of the WINDS and system at the deployed locations.
3.1.23 Follow on work
The Contractor shall provide services including: removal/repositioning of the sensor equipment, removal of tower 0003, update documentation (section 3.1.12 & 3.1.13) reflecting new sensor locations and disposition of legacy equipment.
Prior to equipment repositioning, the Contractor shall provide a method and related documentation to verify correct sensor and system operation for Government approval.
The Contractor shall coordinate with SMC, 1 ROPS, 45 WS, RGNext, and KSC to utilize OM&S contractor scheduling when scheduling site operations.
4. Reports
4.1 Project Plan
The Contractor shall prepare for, conduct, attend, and participate in program meetings, assessments, and reviews to be held at both the Contractor and Government facilities. Reviews will be held to determine the Contractor’s progress against the plan; ensuring obligations under contract to the Air Force are being fulfilled. A Government representative will chair meetings/reviews. The Contractor shall be prepared to explain the reasoning, assumption, and methodologies in arriving at particular conclusions, recommendations, or alternatives in the accomplishment of the tasks required by the contract. The Contractor shall prepare drawings and other data to aid in the presentations. The Contractor shall have key personnel and support available to carry out the meeting/review. The Contractor shall make facilities available for Government-only meetings when hosting. Subcontractors shall attend meetings and reviews when required to address key elements.
The Contractor shall attend scheduled IPT meetings, Technical Interchange Meetings (TIM), program status reviews, and other meetings as approved by the Government Program Manager. The purpose of these meetings shall be to brief the progress of each assigned task, and to solicit input and concurrence of work performed. The Contractor shall generate presentation materials as required to aid in the discussion of technical risks/issues and shall support TIM Meetings/Reviews. The Contractor shall provide conference agendas and meeting minutes, and track Action Items associated with the aforementioned meetings/reviews as directed by the government.
CDRL A002 Conference Agenda CDRL A003 Briefing Material CDRL A004 Conference Minutes, Technical Report (Action Items) CDRL A005 Risk Management Plan
Prior to any work commencing, the contractor shall create a Project Plan and deliver to the government for approval. At a minimum the Project Plan shall include: (Service Summary) (CDRL A001)
4.1.1 A description of the project, its scope, and the key people involved.
4.1.2 A project task list.
4.1.3 A project schedule showing remaining milestones (to include design review meeting) and time-related dependencies between different project tasks.
4.1.4 The Contractor shall provide assignment of duties and monitor status as required by the Government in a timely manner to accomplish project milestones as a function of the tasks.
4.1.5 CDRLs listed in Appendix C
4.2 Monthly Status Report
4.2.1 The Contractor shall provide a Monthly Status Report to the TPM and Contactor Officer Representative of the program. The Monthly Status Report shall focus on a roll-up of the tasks including the identification of work accomplished; program risks; program issues or problems; labor hours expended; program cost (per month and cumulatively); and estimates to complete the support of PWS taskings. Monthly reports shall be delivered electronically to the TPM, and the COR. Delivery shall be on the 10th day of the month in contractor format.
4.2.2 Contractor’s performance in comparison to the planned delivery schedule for each product, any concerns related to the status of parts and equipment that are on order, and when schedules need to be slipped with an update to the delivery schedule and explanations as to why the schedule changed.
4.2.3 Status of task order progress for each product (status of the actual percent (%) complete and the planned percent complete as of the reporting date).
4.2.4 Issues/concerns and associated recommendations (any risks that would cause a change in schedule or cost, associated recommendations to mitigate the issue).
4.3 Data / Software Update Requests
4.3.1 The contractor shall provide updates to previously delivered data, as requested by user during DT&E.
5. Service Summary
| Performance Objective |
| PWS |
| Performance Threshold |
| The contractor shall provide Project Plan (continued and following on) |
| 4.1 |
| Delivered 21 days after award of contract (CDRL A00) |
| The contractor shall provide conference agenda, briefing material and report |
| 3.1.4, |
3.1.5, 3.1.17 to 3.1.23 & 4.1 Delivered 5 days prior to the meeting (CDRL A002 – A003)
| The contractor shall provide conference and meeting/minutes |
| 3.1.4, |
3.1.5, 3.1.17 to 3.1.23 & 4.1 Delivered 7 days after the meeting has been held (CDRL A004)
| The contractor shall review risk as required |
| 4.1 |
| Delivered 15 days after Government request (CDRL A005) |
| The contractor shall provide Monthly Status Report |
| 4.2 |
| Delivered 30th day of the month following the first month of the contract (CDRL A006) |
| The contractor shall Integrated Master Schedule (continued and following on) |
| 3.1.1 |
| Delivered 15th day of the month (CDRL A007) |
| The contractor shall provide technical data package as required |
| 3.1.3, 3.1.5, 3.1.17 to 3.1.23 |
| Delivered 15 days after Government request (CDRL A008) |
| The contractor shall provide the final Test Plan |
| 3.1.8, 3.1.17 to 3.1.23 |
| Delivered 15 days prior to DT&E, update as required (CDRL A009) |
| The contractor shall provide the final Test Procedures |
| 3.1.8, 3.1.17 to 3.1.23 |
| Delivered 15 days prior to DT&E, update as required (CDRL A010) |
| The contractor shall provide the test report |
| 3.1.8 & 3.1.19 |
| Delivered 21 days after DT&E (CDRL A011) |
| The contractor shall provide product drawings, models, and associated list as required |
| 3.1.13, 3.1.17 to 3.1.23 |
| Delivered 30 days prior to PCA (CDRL A012) |
| The contractor shall provide the final Software Version Description (SVD), Software Product Specification (SPS), and Software Requirements Specification (SRS). |
| 3.1.2 & 3.1.17 |
| Delivered 15 days prior to DT&E dry run (CDRL A013, CDRL A014, and CDRL A015) |
| The contractor shall provide data accession list as required |
| 3.1.7 |
| Delivered 15 days after Government request (CDRL A016) |
| The contractor shall provide final proposed spare part list and product indenture report |
| 3.1.17 |
| Delivered 15 days prior to TRR (CDRL A017 and CDRL A018) |
| The contractor shall provide Type 1 and User Training |
| 3.1.17 to 3.1.23 |
| Delivered 15 days after DT&E (CDRL A019) |
| The contractor shall provide O&M Manuals, SUM and Technical Orders |
| 3.1.12 & 3.1.17 to 3.1.23 |
| Delivered 15 days prior to review (CDRL A020) |
| The contractor shall provide final C&A Package |
| 3.1.17 to 3.1.23 |
| Delivered 15 days prior to TRR and updated as Government request (CDRL A021) |
6. General Information
6.1 Security Requirements
6.1.1 The contractor shall not divulge any information about files, data, processing activities or functions, user IDs, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. The contractor/contract personnel shall abide by all Agency rules, procedures and standards of conduct. All contractor personnel will sign a Non-Disclosure Agreement (NDA).
6.1.2 The contractor shall comply with Operations Security (OPSEC) requirements.
6.2 Quality Control
6.2.1 The Contracting Officer Representative (COR) is the authorized individual who will perform assessments of the contractor’s performance.
6.2.2 The COR or alternate(s) will inform the contractor when discrepancies occur and will request corrective action.
6.2.3 Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the Contracting Officer.
6.2.4 The services to be performed by the contractor during the period of this contract shall at all times and places are subject to review by the CO and or authorized COR.
6.3 Quality Control Program
6.3.1 The contractor shall establish a complete Quality Control Program and submit with proposal to ensure the requirements of this contract are provided as specified. The CO will notify the contractor of acceptance or required modifications to the plan before the contract start date. The contractor shall make appropriate changes (at no additional costs to the government) and obtain acceptance of the plan by the CO before the start of the first operational performance period.
6.3.2 The government will periodically evaluate the contractor’s performance by appointing a COR to monitor performance to ensure services are received. The COR will evaluate the contractor’s performance through intermittent on-site inspections of the contractor's quality control program and receipt of complaints from base personnel. The government may inspect each task as completed or increase the number of quality control inspections, if deemed appropriate because of repeated failures discovered during quality control inspections or because of repeated customer complaints.
6.4 Manpower Reporting
6.4.1 The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for this WINDS.
6.4.2 Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year.
6.4.3 Please report contractor labor hours Contract Funds Status Report.
6.5 Travel
6.5.1 The contractor shall travel to CCAFS/KSC to support the following reviews; DT&E (Up to 2 weeks) for the WINDS system and follow on work (Multiple trips). The Contractor will be advised of dates and locations of travel as soon as the information becomes available to the Government so that the most advantageous prices may be obtained. Actual travel expenses are limited by Government Travel Regulations and must be pre-approved by the Government Program Manager. The contractor shall provide information concerning airfare, car rental, per diem, and miscellaneous expenses if necessary. Travel must be in accordance with FAR 31 and Federal Travel Regulations.
7. Government Furnished Property and Services
7.1 No Government Furnished Property is provided for this effort
7.2 Government Furnished Information
7.2.1 All materials shall remain the property of the Government and will be returned to the Technical Program Manager at the end of the Task Order period of performance. Copies of reference materials cited in PWS paragraph 3.1.2b will be provided to the Contractor upon request.
8. Data Rights
8.1 The government shall have unlimited rights to all intellectual property developed by the contractor, and/or its subcontractor, under this contract. The government may use such items for any other purpose as stated in the Defense Federal Acquisition Regulation Supplement (DFARS) definition of “unlimited rights”.
8.2 In addition, all materials, if supplied to the contractor is the sole property of the Government and may not be used for any other purpose except for what it was intended.
APPENDIX A
ACRONYMS AND ABBREVIATIONS
| AFB |
| Air Force Base |
| CAD |
| Computer Aided Drafting |
| CDRL |
| Contract Data Requirements List |
| DT&E |
| Development Test and Evaluation |
| PWS |
| Performance-Based Work Statement |
| QAE |
| Quality Assurance Evaluator |
| SMXG |
| 309th Software Maintenance Group |
| SMXS |
| 516th Software Maintenance Squadron |
| SUM |
| Software User Manual |
| TO |
| Technical Orders |
| TPM |
| Technical Program Manager |
| TRD |
| Test Requirements Document |
| TRR |
| Test Readiness Review |
APPENDIX B
Tools/Documentation
| Name |
| Used for |
| Technical Requirements Document (TRD) for Launch and Test Range System (LTRS) Eastern Range (ER) Weather Information Network Display System (WINDS) Replacement #15-004, Revision #4.0 14 August 2018 |
| Existing TRD at Hill AFB, UT and Peterson AFB, CO. |
| WINDS Requirements Allocation Spreadsheet (RAS) |
| Existing RAS at Hill AFB, UT and Peterson AFB, CO. |
APPENDIX C
Contract Data Requirement Lists (CDRLs) (DD Form 1423s)
| CDRL |
| Data Item Description |
| Description |
| CET Paragraph |
| Frequency |
| Submit |
| A001 |
| DI-MGMT-81650 |
Superseded by DI-MGMT-81862
| Project Plan |
| 4.1 |
| Once |
| NLT 21 days after award of contract |
| A002 |
| DI-ADMN-81249A |
| Conference Agenda |
| 3.1.4, 3.1.5, 3.1.17 to 3.1.23 & 4.1 |
| As Required |
| NLT 5 days prior to meeting |
| A003 |
| DI-MGMT-81605 |
| Briefing Material |
| 3.1.4, 3.1.5, 3.1.17 to 3.1.23 & 4.1 |
| As Required |
| NLT 5 days prior to meeting |
| A004 |
| DI-ADMN-81505 |
| Conference Minutes, Technical Report (Action Items) |
| 3.1.4, 3.1.5, 3.1.17 to 3.1.23 & 4.1 |
| As Required |
| NLT 7 days after meeting has been held |
| A005 |
| DI-MGMT-81808 |
| Risk Management Plan |
| 4.1 |
| As Required |
| NLT 15 days after Government request |
| A006 |
| DI-ADMN-81505 |
| Monthly Status Report |
| 4.2 |
| Monthly |
| 30th day of the month following the first month of the contract |
| A007 |
| DI-MGMT-81650 |
Superseded by DI-MGMT-81862
| Integrated Master Schedule |
| 3.1.1 |
| Monthly |
| 15th day of the month following the first month of the contract |
| A008 |
| DI-SESS-80776A |
| Technical Data Package |
| 3.1.3, 3.1.5, 3.1.17 to 3.1.23 |
| As Required |
| NLT 15 days after Government request |
| A009 |
| DI-NDTI-80566A |
| Final Test Plan |
| 3.1.8, 3.1.17 to 3.1.23 |
| As Required |
| NLT 15 days prior to start of testing and updated as required |
| A010 |
| DI-NDTI-80603A |
| Final Test Procedure |
| 3.1.8, 3.1.17 to 3.1.23 |
| As Required |
| NLT 15 days prior to start of testing and updated as required |
| A011 |
| DI-NDTI-80809B |
| Test Report (DT&E) |
| 3.1.8 & 3.1.19 |
| Once |
| NLT 21 days after completion of test |
| A012 |
| DI-SESS-81000D/T |
| Product Drawings/Models and Associated Lists |
| 3.1.13, 3.1.17 to 3.1.23 |
| As Required |
| NLT 30 days prior to PCA |
| A013 |
| DI-IPSC-81442A |
| Final Software Version Description (SVD) |
| 3.1.2 & 3.1.17 |
| At Milestone Reviews |
| NLT 15 days prior to DT&E dry run |
| A014 |
| DI-IPSC-81441A |
| Final Software Product |
Specification (SPS)
| 3.1.2 & 3.1.17 |
| At Milestone Reviews |
| NLT 15 days prior to DT&E dry run |
| A015 |
| DI-IPSC-81433A |
| Final Software Requirements Specification (SRS) |
| 3.1.2 & 3.1.17 |
| At Milestone Reviews |
| NLT 15 days prior to DT&E dry run |
| A016 |
| DI-MGMT-81453A |
| Data Accession List |
| 3.1.7 |
| As required |
| NLT 15 days after Government request |
| A017 |
| DI-ILSS-80134A |
| Final Proposed Spare Parts List |
| 3.1.17 |
| At Milestone Reviews |
| NLT 15 days prior to TRR |
| A018 |
| DI-SESS-81121A |
| Product Indenture Report (PIR) |
| 3.1.17 |
| Once |
| NLT 15 days prior to TRR |
| A019 |
| DI-SESS-81517B |
| Type 1 and User Training |
| 3.1.17 to 3.1.23 |
| Once at end of program |
| NLT 15 days after DT&E |
| A020 |
| DI-IPSC-81443A |
| O&M Manuals and Technical Orders |
| 3.1.12 & 3.1.17 to 3.1.23 |
| At Milestone Reviews |
| NLT 15 days prior to the review |
| A021 |
| DI-MGMT-82000 |
| Information Assurance Certification and Accreditation (C&A) Package Inputs |
| 3.1.17 to 3.1.23 |
| At Milestone Reviews |
| NLT 15 days prior to TRR and updated as Government request |
image1.png
File details come from the government source that posted it.